14 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH23:59
Leading reported evidence
Check with the engine
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
On the turbo the oil level is checked with the engine running and via the OBC.
Leading evidence: 'Check with the engine' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'pcm' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check with the engine' (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
I think it is more likely to be the cluster, as it is that which displays the wrong time first, although the odd CD track behaviour would be more likely the PCM.
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
No fault codes with either and no low voltage codes which are usually logged from previous battery change attempts or a weak battery.
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
Do you have any test kit to drop test the Battery?
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
Do you have any test kit to drop test the Battery?
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
pcm
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
I think it is more likely to be the cluster, as it is that which displays the wrong time first, although the odd CD track behaviour would be more likely the PCM.
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.
14 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: 20261026T130754Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Every so often when I turn on the ignition, my dashboard clock says 23:59 and PCM clock is the correct time. Only a few seconds after I start the car do both clocks synchronise and show the correct time. Anyone else have the same anomaly? My battery is new and fighting fit, the alternator is charging fine and there are no faults on diagnostics.
I don't know if it is related but the single CD player on the PCM always starts from the first track again the next day instead of carrying on from where it was last stopped.
Perhaps it's trying to tell us something, and not something good either............[&:][
]
http://www.amazon.co.uk/One-Minute-Midnight-Kennedy-Krushchev/dp/0091796660
No fault codes with either and no low voltage codes which are usually logged from previous battery change attempts or a weak battery. As explosive as the acceleration of the turbo is, I suspect it wouldn't be quite the bang suggested by tscaptain.
Could it just be the countdown timer for when the oil level measurement will be valid from? Normally mine shows just a few seconds, but when you turn on the ignition shortly after using the car it shows a much higher value...
Surely the car shutting down because the battery is low. 23:59
We now how hungry these things are when left especially if unlocked.
Do you have any test kit to drop test the Battery?
These are quite good http://cpc.farnell.com/act-meters/gold-ibt/sla-battery-tester/dp/IN02529
I use mine a lot so it pays for its self, But if its not going to be used a lot, its a bit pricey.
Maybe ebay has something.
Just to reiterate on that.
Its the Amp hours that you are of interest not the voltage.
A flat will still read 12v without load.
And I'm not jealous of your turbo honest.
I have checked all that. The battery is new, my digital battery tester says the battery has 70% capacity and my old battery load tester shows a consistent 11.5v with a 10 sec load. It is definitely the clock doing strange things. When I turn the ignition on it says 23.59 and if you leave it a while or start the car it corrects itself. The are no fault codes logged on the PST or PIWIS.
Hmmmm,
It would seem od if the the Battery were still able to turn the car but low enough to cause a fault.
Perhaps someone at Porsche stuck a rugby receiver in there.
Difficult to know if it is the instrument cluster or the PCM which is causing the problem. Obviously they are synching shortly after you switch on the ignition. I think it is more likely to be the cluster, as it is that which displays the wrong time first, although the odd CD track behaviour would be more likely the PCM. The clock on my instrument cluster consistently loses time (about a minute a week) and I get the occasional "power supply" fault on the cluster. You could try re-booting the PCM with the 1-4-8 reset, to see if that makes any difference.
