8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHEngine no-start after alternator change
Leading reported evidence
Check of the connections
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
Yeah, I checked all of the connections before I put the air cleaner back on, but easy enough to have moved something doing that.
Leading evidence: 'Check of the connections' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check bouncy tach;' (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.
Clean contacts, re-installed alarm module, cleared all faults
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
Cleaned all contacts, re-installed alarm module, cleared all faults.
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
Cleaned all contacts, re-installed alarm module, cleared all faults.
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.
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
I'll check the bouncy tach; that was my diagnostic for my 944's flywheel sensor also, took me ages to discover that.
Replace voltage regulator; i still get a double-beep
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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
For months, I would get a double-beep when locking car with key, but everything else was fine until I replaced voltage regulator; I still get a double-beep when locking with key, (no beeps when unlocking with key or fob), but car will not run now.
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.
8 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: 20261026T152433Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi, would appreciate some technical help on my 2000 996 C2. I've read some of the many issues with door locks and the immobilizer module, I think I have a different issue.
I recently changed the alternator. As I'd had the left window open, some rain got into the car during a thunderstorm, the carpeting was damp but not soggy. After re-connecting the battery, car would crank but not fire. The Duratec indicated faults in the alarm unit/immobilizer. All of the alarm control functions in the Duratec routine for the control unit seemed to work: horn, locks, lights. All functions associated with the fuse (E1) work, e.g., radio, lights, etc. I cleared the faults and same no-start issue. I removed the alarm control unit and saw that the board is clean and dry. As the door locks activate during the Duratec scan, does that eliminate the door lock issues others have had? At this point, I could send the unit off to be tested (ECU Doctors?), but are there any recommendations for troubleshooting this further before I do that?
Yes, both fuses (E1 and on control unit) are good. Cleaned all contacts, re-installed alarm module, cleared all faults. I tried to start with 1/2-throttle, engine runs very rough and would not idle. Durametric faults at the alarm I32/I48 are now both "47: Control Locking Synchronization".
For months, I would get a double-beep when locking car with key, but everything else was fine until I replaced voltage regulator; I still get a double-beep when locking with key, (no beeps when unlocking with key or fob), but car will not run now. There are no faults shown anywhere else other than the alarm module.
Based on the many issues with this alarm system posted in forums, it doesn't seem like people get a no-start:
do these faults in the alarm system prevent the car from running?
What type/brand of voltage regulator? Or did you replace the entire alternator? Always go over your last job if the car was running correctly beforehand.
I'll check the bouncy tach; that was my diagnostic for my 944's flywheel sensor also, took me ages to discover that. Will check fuel pressure as well. Voltage regulator was Bosch unit with same part number, from Pelican. Yeah, I checked all of the connections before I put the air cleaner back on, but easy enough to have moved something doing that. I so much love working on my '72 BMW vs. the 996; simplicity has its merits.
you should check voltage at jump terminal in engine bay for AC voltage leak.
you can switch your multi meter to AC volts and measure output at terminal. Anything over .5 volts AC will confuse vehicle electronics.
This is a source reference. Confirm exact model applicability in the original material.
