10 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHNew owner, having a few problems
Reported or suspected cause
on
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
That will at least tell you the circuit the issue is on.
Leading evidence: 'on' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'on' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Disconnect altinator amd see if' (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 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
I will go further to say thats its been installed incorrectly with the power wiring messed up and possibly an amplifier in there somewhere running full time...
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
Thats a 'red herring' as all brakes are used anyway.
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
If pulling fuses doesnt stop the draw, next disconnect the altinator amd see if that stops the draw.
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 will go further to say thats its been installed incorrectly with the power wiring messed up and possibly an amplifier in there somewhere running full time...
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
I will go further to say thats its been installed incorrectly with the power wiring messed up and possibly an amplifier in there somewhere running full time...
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 will go further to say thats its been installed incorrectly with the power wiring messed up and possibly an amplifier in there somewhere running full time...
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.
10 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.
1 acknowledgements have no verified action link; they do not establish a repair result.
Bought a 2001 996 recently but have not been able to drive it much because of work and a few issues. The main problem I am having is that the battery dies if the car sits for as few as 2 days (the battery is only 2 months old). The following are some things I have noticed which could be the cause of the drain:
1) Anytime I turn off the car - when I turn it back on the radio memory is
erased (e.g. the presets are not remembered, etc.) so I assume the
radio wiring is not hooked up correctly
2) When I lock the car with the remote the, horn beeps twice which I read
indicated a fault with the alarm system. Not sure if that fault could be the
cause.
3) After turning off the car the lights for the hood release/trunkrelease/
seat memory buttons - all remain lit when the car is off 24/7. I assume that
is not normal but not sure what the fix would be.
Thanks in advance.
OK, I am guessing that you have an aftermarket stereo. I will go further to say thats its been installed incorrectly with the power wiring messed up and possibly an amplifier in there somewhere running full time... Get it checked out.
I agree that some idiotic PO has been messing with the electrics without knowing what the hell he was doing. Thats what pisses me off with some owners of these cars. Radio not loud enough. Muffler not loud enough. The deaf bastards. They mod themselves to death and F*** up a perfectly good car in the doing thereof. Then the next owner has to suffer the consequences. Same on mine. The inside light doesnt work as the doors are opened. There is no lock on the gas door. Did the PPI tell me about those faults. NOOOOOOOOOOOOO. Because the seller only told me the things he wanted to tell me. **** like the brakes have 30% left in them. Thats a 'red herring' as all brakes are used anyway. Thats why I say. Get an independant PPI and know everything there is to know about these cars before buying. I will run a mile if I find out that one thing has been modified from stock in my next Porche car. So thats me off the soap box till next time.
I am so angry I could crush a grape.
I would assume these are all related. A circuit is open causing the alarm to double-signal and that circuit is causing the battery to drain, given the radio presets - I would focus on the radio wiring.
Well you guys were right. Took it to a shop. Guy said it was wired to iginition a certain way, yada yada, the amp was permanently on draining the battery. Took him 10 minutes and problem solved. So that is one off the list. Of course the following day a new issue arose...
Welcome to the marvels of German Engineering! These are awesome cars but they attract gremlins. Remember, your new car is over a decade old and new issues will arise. Embrace these quirks...and your wallet.
Put an amp meter on the battery and pull fuses one at a time till the draw stops. That will at least tell you the circuit the issue is on. If pulling fuses doesnt stop the draw, next disconnect the altinator amd see if that stops the draw.
This is a source reference. Confirm exact model applicability in the original material.
