13 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHUnusual Instrument Cluster Malfunction
Reported or suspected cause
ignition switch
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
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 report identifying 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.
Reported cause
Come to find out it was the ignition switch that was faulty.
Leading evidence: 'ignition switch' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'ignition switch' (1 discussions; 1 report identifying it and 0 suggest it). 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
So far, Ive gone through the fuse panel & checked for power across each fuse, cleaned each connecting point, special attention to B1, B10, E1.
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
So far, Ive gone through the fuse panel & checked for power across each fuse, cleaned each connecting point, special attention to B1, B10, E1.
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.
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
- No oil pressure (sending unit replaced appx 1 yr ago w/ new OEM)
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'll inspect/clean the ground points as you suggest (I have a location chart) and also gently move some wiring while it's switched on in hopes that may reveal a troubled connection.
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.
13 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 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: 20261026T172408Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi All - Problem with my 2004 C2 Tip. I've had the car for 15 yrs and put most of the miles on it. This issue began with a speedometer failure, now devolved to:
- No oil pressure (sending unit replaced appx 1 yr ago w/ new OEM)
- No fuel level (pump, level sensor never touched)
- Tach seems to lose power or signal for an instant at a regular interval (see video)
- clock, though set for military time has implausible numbers
- Haven't driven the car, but speedometer assumed inoperable
So far, Ive gone through the fuse panel & checked for power across each fuse, cleaned each connecting point, special attention to B1, B10, E1. I swapped out the electrical cylinder of the ignition switch. I swapped out relay number 24. None of these things changed anything. Any suggestions appreciated!
Seems like a problem with your instrument cluster and maybe the connections. Pull the cluster and check the connectors. Might just be a loose connector.
Mav & KC, thanks for the heads up. Ok, so the bales on the three connectors were secure and the pins on all three pristine. Nevertheless, gave everything a spray of contact cleaner on reassembly, but sadly no love. Well at least a potential fault eliminated.
I drove a '99 that had a gauge cluster (and other electronics) that were flickering on and off. I know the guy that owns the car. It had been sitting up for 2 years. Come to find out it was the ignition switch that was faulty. Replaced and all is fine in that car's world again.
Seems like you have done all the logical steps. Your 2004 cluster has the PCB board and there could be a fault somewhere on the board. I would contact Palo Alto Speedometer. You may have to send the entire cluster to them for repair.
http://www.paspeedo.com/porsche.htm
Poor ground connections can cause electrical problems and affect multiple systems at once. Check that all ground points related to the instrument cluster and ECU are clean, secure, and free of corrosion. Focus on the main grounding points in the engine bay and the ground connections behind the dashboard.
I think this evening I'll do a couple of things. I'll inspect/clean the ground points as you suggest (I have a location chart) and also gently move some wiring while it's switched on in hopes that may reveal a troubled connection. Merci, Pierre!
Bad ground connection for the win! Discussed with a friend who runs a general automotive repair service, who immediately said "it's gonna be a bad ground, drop it by". I did. He's a big fan of all things snap-on, including their software and diagnostics, and somehow pinpointed a grounding point behind the dash that he could get an end wrench on to loosen, scuff & reseat. Everything has returned to full function. Thanks to everyone for the help and interest.
This is a source reference. Confirm exact model applicability in the original material.
