5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCAN fault codes
Leading reported evidence
Check wiring in accordance
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
I don't think you have much choice other than to check the wiring in accordance with the diagnostic sheets.
Leading evidence: 'Check wiring in accordance' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check wiring in accordance' (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 · Original poster
I would have considered the battery myself except my Yuasa Silver battery is only 6 months old and I keep in trickle charged using a CTEK MXS 7.0 every weekend.
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 would have considered the battery myself except my Yuasa Silver battery is only 6 months old and I keep in trickle charged using a CTEK MXS 7.0 every weekend.
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: 20261026T163944Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
My 2004 996 turbo throws up a couple of recurring fault codes every so often and would appreciate any advice how to proceed with diagnosis to establishing the fault.
The first is a DME fault code P1601 (CAN timeout instrument cluster) and the second is a Tiptronic fault code 40 (on PIWIS2, CAN instrument cluster communication disturbed). Everything is functioning normally with no lights on, all buttons working and the car drives well. After I clear the faults, it can recur within the day or not for a couple of weeks. Apart from needing to make sure the connector to the instrument cluster is secure, the prospect of back probing wires to the respective computers is daunting. However if anyone has embarked on a journey to establish a similar fault, your guidance to carrying it out will be most helpful.
Not of direct help, but I look at a lot of fault codes and the can bus seems to produce a lot of ‘soft errors’. I attribute this to perhaps a corrupted command or loss of power (flat battery).
I would have considered the battery myself except my Yuasa Silver battery is only 6 months old and I keep in trickle charged using a CTEK MXS 7.0 every weekend. I tested it with a conductance tester and battery is atill producing 110% of the rated 850A EN capacity. Alternator is working fine with 13.5V while the engine is running.
I don't think you have much choice other than to check the wiring in accordance with the diagnostic sheets. I would start with the Tip error 40 sheet, as there is less to it. If the wiring checks out, then the cluster is faulty, but if it isn't causing any problems then it would be best to live with the fault codes.
I'll email you the diagnostic sheets in case you don't have them.
Thank you Richard. Car is running perfectly so I’ll have a look at the sheets and see what is involved and do what i can that doesn’t involve too much dismantling.
This is a source reference. Confirm exact model applicability in the original material.
