7 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCentral Locking Odd Behavior / Codes
Reported or suspected cause
passenger door door lock assembly
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that report identifying a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Reported cause
The problem was traced to the passenger door door lock assembly.
Leading evidence: 'passenger door door lock assembly' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'passenger door door lock assembly' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Set horn beeping' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that report identifying a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Reported cause
The problem was traced to the passenger door door lock assembly.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that report identifying a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Reported cause
I followed this guys instructions to confirm my issue was weak soldering joints and then carefully took the latch apart taking lots of pictures and boom!!!!
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
I read related threads here, but really haven't found anything relevant - but I may have just used stupid search terms.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
At this point the inside sensor is still activated and leaving a dog inside will set the horn beeping.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Reported cause
I followed this guys instructions to confirm my issue was weak soldering joints and then carefully took the latch apart taking lots of pictures and boom!!!!
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
7 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T181445Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi, All;
Within the past 2 weeks, I've noticed that my central locking "lock" light indication has been coming on by itself for no apparent reason.
Car: 2001 C2
I usually do not lock it, since it's parked in my garage and that way I don't have to handle the "5-days-and-keyless remote-goes-to-lalaland" operation.
The keyless remote works just fine. Key in door operation is just fine.
I usually do not lock the doors while driving, and apparently the operation is set to the "never auto-lock the doors" mode.
If I get in the car and press the "key image" portion of the central locking switch, the doors lock fine. If I press the unlock side of the switch, the doors unlock just fine.
HOWEVER: just driving along, sometimes the red lock indication comes on. If I hit the unlock side of the switch, it turns the light off, but also gives the double-beep signal that something's amiss.
Connected my Durametric today. Got 3 codes:
47: central locking synchronization.
Status: not present
Occurance Count: 2
"This fault is display for information purposes. It is not an indication that repair is needed".
60 Central locking limit position Lock not reached
Status: Not present
Occurance Counter: 1
This fault is display for information purposes. It is not an indication that repair is needed".
61: Central locking limit position Unlock not reached
Status: not present
Occurance Counter: 2
This fault is display for information purposes. It is not an indication that repair is needed".
I read related threads here, but really haven't found anything relevant - but I may have just used stupid search terms. I did find one thread that suggested the renntech "door microswitch" debugging topic, but at this point I'm just not sure if that is relevant to my issue.
Any hints/suggestions?
Mine is a 99 job. can't quite figure out whats happening with yours BUT. This is how things should work. One push of remote locks the car along with 2 flashes of indicators no horn sound. At this point the inside sensor is still activated and leaving a dog inside will set the horn beeping. The other way is two pushes of the button cancels out the inside activated part. It lets you know by one horn beep. The first method (one push of the button) if something is still unlocked liked engine lid or door of middle console compartment, you get 2 indicator flashes and one horn beep. So one click of the remote you should hear no horn, get 2 flashes and the car is armed. If you hear a beep, something is unlocked. On unlocking, use one click, you get one flash and the inside lights come on. If you do not open the car by hand for a minute. The alarm locks the car up again and the inside lights go off. Hope that helps a bit.
Yup - exactly as my manual describes is. That part is just fine. It's just the strange lock indication illumination coming on that has me baffled, along with the fault codes.
FWIW my Boxster started to manifest the behavior of illuminating the door lock LED on the dash with the added behavior of even when I pushed the unlock button which extinguished the LED and unlocked the doors (I could hear this) occassionally the LED would come back on in a few moments with the doors making their locking sounds. (There were other symptoms/odd behaviors, too.)
The problem was traced to the passenger door door lock assembly. This is (at least in my Boxster) a rather large plastic/alum. housing with both mechanical and electrical/electronic hardware.
There were security system error codes but I do not know what they were. The tech pulled these and then removed the door panel and performed some other tests to eliminate the various micro-switches before settling on the door lock assembly as the culprit. His diagnosis was correct as all the odd behavior was absent afterwards.
I had the same issue. 2001 996 C4 Cab. The lock light on the dash would stay on. The horn would beep twice when you tried to lock it. It would randomly try to lock and beep twice while driving down the road. Windows would not index when you opened the doors...
I found the PROBLEM and the SOLUTION and it only cost me about 3 hours of labor and $0.
Bottom line - the solder joint on the PC board inside the door lock actuator is bad.
Step 1 - find video for how to remove door panel
Step 2 - jiggle the wire harness connector going into the actuator...if it clicks and beeps every time you move it, you have a bad solder joint
Step 3 - find video for how to remove actuator
Step 4 - separate the actuator from the door latch mechanism. Remove the white cover from the actuator. Where the wiring harness meets the silicone board, re-solder those joints. Put the white cover back on (to hold everything in place) and test in the car before mating with door latch...make sure to test BOTH sides
Step 5 - do the above in reverse.
No more beeps when I lock or unlock...just lights flashing and doors actually locking and unlocking. ALSO...the windows index properly when opening and closing the doors.
i normally just lurk and read and never post. But I had to make an account just to say thank you to this guy! THANK YOU! After paying $1200 to get a new immobilizer due to water damage I was having problems with alarm codes 61 and 47. Seemed to be the passenger side latch. I looked up ordering a replacement and it was $800!!!! Ack!! I followed this guys instructions to confirm my issue was weak soldering joints and then carefully took the latch apart taking lots of pictures and boom!!!! No more faults!!! Thanks again!
This is a source reference. Confirm exact model applicability in the original material.
