5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHElectrical gremlins
Leading reported evidence
Run low at times
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
Was off road a bit doing work...battery definitely ran low at times but e.g.
Leading evidence: 'Run low at times' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check ignition feed and do a vehicle handover' (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 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
The only things an Indy could do was check the ignition feed and do a vehicle handover ..
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.
911uk: 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: 20261027T031046Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Not sure if these are related....but noticed both at same time.
Context...2004 996.2 tt tip. Was off road a bit doing work...battery definitely ran low at times but e.g. trip mileage not reset.
Issue 1 - clock keeps going down 1 hr shortly after start. Not sure if this some summer time/gps thing (does the 996.2 have that?)
Issue 2 - the stereo started either not coming on or taking a lot of time to come on (like 10mins+). When it does come on the preset number pad and few other buttons dont work. Some buttons do e.g. frequency search...
Frustrating and odd. Any tips?
Regards
Karl
Ok .. well i'm afraid both faults are related .. the PCM is in charge of the time shown in the instrument cluster ..
The pcm takes ages to actually start working and it's giving incorrect info to the instrument cluster .. this to me indicates a problem with the pcm it self .
basically this unit has an earth wire , a battery 12 volt feed and an ignition 12 volt feed .. unless something like the ignition switch is not giving it a 12 volt feed .. but is 10 mins later then its the pcm at fault ..
Btw .. ignition switch causing this whilst possible would be a new one on me .
There was a post recently on where to send these units to be repaired ... not sure if 997 or 996 but the same place can repair them .
EDIT
The only things an Indy could do was check the ignition feed and do a vehicle handover .. a .. well .. a basic wakeup of items but it's more like turning them off then back on again .
Im dubious it will make any difference but thats all i would do before sending the unit for repair .
Thanks as ever DeMort.
Only things I am going to try are 1) pull the fuse in the box...2) replace the fuse behind the unit (since the unit isnt even lighting now). Not hopeful.
I have a new head unit anyway...so i guess it might just be time to get on with that job....and send the pcm off for check.
Regards
Karl
This is a source reference. Confirm exact model applicability in the original material.
