8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHFault Codes - Please help Richard!!!
Leading reported evidence
Replace the alternator went this week
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
- The alternator went this week and has been replaced.
Leading evidence: 'Replace the alternator went this week' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check connectors' (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 · Original poster
I reset the codes and the cluster fault disappeared.
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 would check the connectors, but if everything on the cluster is working, then I would just live with it.
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
- When I did a fault code check just on the airbag it said there were no faults, yet when I do a full system check it states the air bag was "not found"!?
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.
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
- When I did a fault code check just on the airbag it said there were no faults, yet when I do a full system check it states the air bag was "not found"!?
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.
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: 20261026T061123Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
My car is now of the age where it's starting to have a few 'wear & tear' niggles! For instance, the ABS and PSM warning lights are going on and off.
Anyway, I've purchased a Durametric Diagnostic Kit and just plugged it in. Here are the fault codes I got:
P1601
: Porsche fault code 660 - CAN timeout - instrument cluster.
P0045
: Boost pressure control valve final stage Open circuit.
4205
: Front left speed sensor - op. circa./GND/+ short.
26
: Potentiometer left mirror Open circuit vertical.
To note
:
- Under the
Alarm I32
section it stated "Current Fault Codes" with an amber explanation mark, but did not list the codes??
- It also stated that "The following modules were not found in the vehicle: Airbag, Park Assist"
Amplifying information
:
- My wife has been using the car for the last 6 weeks as I've been in hospital. This week, when back in the car for the first time in a while, I noticed I was only getting 0.4 on the boost gauge when I used to get up to 0.6.
- The alternator went this week and has been replaced.
- When the alternator was replaced the garage noted the 4205 fault and gave the connector a clean. The warning lights didn't come on for the journey home, however they now go on and off intermittently...generally when it's cold.
- When I did a fault code check just on the airbag it said there were no faults, yet when I do a full system check it states the air bag was "not found"!?
- It doesn't have park assist, so it's right there!
I eagerly await your thoughts...
Cheers
Here's how the diagnostic manual describes the faults:
Fault code 4205 (PSM)
Speed sensor lead, front left
Diagnostic conditions:
"¢ Ignition on
Possible cause of fault:
♦ Short circuit to B+ / ground or open circuit between control unit and speed sensor
♦ Speed sensor faulty
♦ Control unit faulty
P0045 (DME)
Charge Pressure Control Valve Output Stage - Open Circuit
Diagnosis conditions:
"¢ Ignition on
Possible fault cause:
♦ Charge pressure control valve (coil) open circuit
♦ Open circuit in wiring
P1601 (DME)
CAN timeout instrument cluster - open circuit
Diagnosis conditions:
"¢ Battery positive voltage greater than 10 V
"¢ Ignition on
Possible fault cause:
♦ Wiring harness faulty
♦ Plug on instrument cluster not connected
♦ Instrument cluster faulty
Fault code 26 (seat Memory System)
Pot. mirror left vertical - open circuit
Diagnostic conditions:
"¢ Ignition on
"¢ Switch for memory seat adjustment actuated
Possible cause of fault:
♦ Open circuit in supply lead to pot. for left rearview mirror
♦ Potentiometer faulty
♦ Control module faulty
Firstly, I would clear the fault codes, drive it a mile or so, and read them out again to see what comes back.
The instrument cluster fault is either a bad connection, bad wiring, or a faulty cluster. I would check the connectors, but if everything on the cluster is working, then I would just live with it.
The low boost is because the DME is running in 'limp mode'. Probably due to a faulty valve, bad connection, or faulty wiring.
The speed sensor fault is either the sensor, or a wiring/connection problem.
The mirror problem could well be just a bad connection. I would take the mirror casing off and look for obvious signs of damage. Also. there is a round multi-pole plug & socket where the wiring comes through to the top of the door which can be a weak area.
If you want the diagnostic sheets for these faults, drop me an email.
Richard,
I clicked on the 'Email' icon under your profile picture and sent you a long-winded message! Just received your email anyway...thanks. I've sent a reply with a few other Qs.
Cheers
I thought I'd keep this post going purely in case it helps anyone in the future.
I reset the codes and the cluster fault disappeared.
As for the mirror, I'm going to live with that for the time being as I don't actually know what issue it's creating i.e. the mirror moves when I adjust it and it also resets to position 1 & 2 as per the seat memories.
I had a look at the speed/ABS sensor connector and it looked very clean. Gave it another spray and clean anyway. I sprayed penetrating oil on the torx bolt that holds in the actual sensor, however when I tried to unscrew the bolt it turned the star into a circle! If the PSM & ABS lights went out, I'd leave it for the time being, however they haven't, so I'm going to drill out the sensor and install a new one. I'll keep you posted...
As for the boost pressure control valve (part no. 996 605 155 00), it would appear that it could either be:
- Elec plug either corroded or actually come off.
- One of the 3 pipes split or come off.
- The valve itself has died.
The air filter and 'Y' pipe have to be removed to get to the valve, so I'll crack that this weekend. Interestingly, Richard pointed out to me that the cheapest place to get a new valve is from an OPC at £18.58. All the usual parts' stockists don't have them...only foreign parts' specialists stock them and the cheapest was 21.80EUR from
Seek Part 24
.
Once I've sorted the issues I'll post it here for future ref.
As ever, thanks to Richard for his advice. I must admit, I'm also already seeing the benefit of having purchased a Durametric Diagnostic Kit.
This is a source reference. Confirm exact model applicability in the original material.