5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCentral locking problem. Can anyone help please?
Leading reported evidence
Use locking button
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
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 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
All the advise I get is that it is probably the lock but as it only happened when I used the locking button on the dashboard for the first time, then it seemed too much of a coincidence that it happened to break just then.
Leading evidence: 'Use locking button' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'lock' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Replace drivers side lock and all is fine now' (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 suspect 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.
Suspected cause · Original poster
All the advise I get is that it is probably the lock but as it only happened when I used the locking button on the dashboard for the first time, then it seemed too much of a coincidence that it happened to break just then.
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
I had to replace the drivers side lock and all is fine now.
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 · Original poster
It has been suggested that a door locking microswitch may have failed but as it was only by using the dashboard button that the problem arose I am reluctant to accept that as the explanation as I understand I have to buy the whole lock assembly.
Use dashboard button the remote and locking/alarm worked perfectly
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
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 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 · Original poster
Prior to using the dashboard button the remote and locking/alarm worked perfectly.
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 · Original poster
It has been suggested that a door locking microswitch may have failed but as it was only by using the dashboard button that the problem arose I am reluctant to accept that as the explanation as I understand I have to buy the whole lock assembly.
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
All the advise I get is that it is probably the lock but as it only happened when I used the locking button on the dashboard for the first time, then it seemed too much of a coincidence that it happened to break just then.
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 · Original poster
I have tried various combinations of locking with the dashboard button and opening the door, locking from the dashboard and using the remote to open from the inside but nothing seems to get it working properly again.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
lock
No successful repair reported for this finding.
0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that suspect 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.
Suspected cause · Original poster
All the advise I get is that it is probably the lock but as it only happened when I used the locking button on the dashboard for the first time, then it seemed too much of a coincidence that it happened to break just then.
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.
5 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Porsche Club GB: 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: 20261026T124918Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
My 1998 996 C2 tiptronic has developed a fault with the central locking and any advise would be appreciated.
I have owned the car for over two years but never used the locking button on the dashboard until last week. Immediately afterwards the car would not lock correctly pressing the key remote, or rather it did but then unlocked itself again with a double beep on the alarm horn. The car can now only be locked by using the key in the lock. When unlocking, pressing the key remote seems to deactivate the alarm but does not open the lock and I have to use the key in the lock but if I don’t press the remote first the alarm goes off.
I have tried various combinations of locking with the dashboard button and opening the door, locking from the dashboard and using the remote to open from the inside but nothing seems to get it working properly again.
When locking from the dashboard the light on the switch comes on and it goes off when it is pressed to unlock. When locking by key, the dashboard switch flashes for a few seconds before going out.
Prior to using the dashboard button the remote and locking/alarm worked perfectly.
It has been suggested that a door locking microswitch may have failed but as it was only by using the dashboard button that the problem arose I am reluctant to accept that as the explanation as I understand I have to buy the whole lock assembly.
Has anyone any thoughts on how I can fix the problem please?
I would put my money on a fault in the door lock. It might be a microswitch if it locks and immediately unlocks when using the remote. If it doesn't lock on the remote, it might be the lock motor.
The only real way of knowing is to plug in a Porsche tester, which can read the signals from the microswitches, and the lock motor. The double-beep means there is a system fault, and will have stored a fault code in the fault memory.
I had a locking problem similar to this recently but it locked and immediately unlocked from the remote. There was also the double beep.
I had to replace the drivers side lock and all is fine now.
Thanks for the response. All the advise I get is that it is probably the lock but as it only happened when I used the locking button on the dashboard for the first time, then it seemed too much of a coincidence that it happened to break just then. Anyway I'll probably use it as it is, with it beeping at me when I open it, for a little while before taking a trip to a garage.
This is a source reference. Confirm exact model applicability in the original material.
