10 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCDR-23 just says "Porsche"
Leading reported evidence
Check leads and how well they are seated)
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
(both due to poor connection - check leads and how well they are seated)
Leading evidence: 'Check leads and how well they are seated)' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check leads and how well they are seated)' (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.
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.
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: 20261026T122219Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
A couple of times recently when turning the unit on all the illumination comes on but the display just says "porsche" and nothing else happens. Turning off and on again does nothing. Only cure seems to be switching off the ignition, taking the key out and putting it back in, which has returned it to normal both times.
Anyone else experienced this or know what's causing it?
Might be a MOST malfunction or sloppy connector. (both due to poor connection - check leads and how well they are seated)
The PORSCHE logo implies a power outage or removal trigger to the units security system.
Thanks.
I always get the Porsche logo at first but usually this sticks around only for a couple of seconds before the radio springs to life. I'd assumed that was normal. :dont know:
The security code of the CDR23 is stored in the DME, and "Porsche" is displayed while the head unit and DME communicate when you switch on to agree the code. It sounds like they aren't always communicating first time, but are successful when you switch the ignition on the second time, but I have no idea why.
The system thinks it is "alien" to the car (for example due theft removal or other power loss) until it is correctly identified.
It requires the MOST to unlock the head unit, if the head unit is indeed "matched" to the car, which I am sure the OP's is, but just has trouble with the automated "handshake".
This "handshake" failure can pressumably be as simple as a loose connector, but Richard, your post reads like you think there may be a deeper reason (ie more systematic failure linked to DME initiation, rather than random open ciruits from dodgy connector).
Well, there is no MOST connection to the DME, so it must be communicating via MOST & Comfort CAN. That gives more possibilities, but I wouldn't know where to start, other than trying a diagnostic test to see if there are any faults recorded.
I guess it depends how often it happens, and how much of a nuisance it is, as to whether it is worth delving further or not.
Cheers guys.
It's only just started happening this weekend so I'll check for obvious loose connections and see if it happens again, or with increasing regularity before booking it in anywhere.
GT4, sorry for the confusion, the original post IS the problem, my subsequent post was just to check that what happens 99% of the time is normal behaviour.
