9 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHDash lights head-scratcher
Leading reported evidence
Disconnect last night (didn't want
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
But I disconnected last night (didn't want to go out to a dead battery).
Leading evidence: 'Disconnect last night (didn't want' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Disconnect [' (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.
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.
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.
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.
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.
9 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.
2 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
Codes were mostly smog related (because a cylinder wasn't firing), but it wasn't clear what was causing the CEL, so clearing the codes gave us a closer look at the issue, then we fixed it.
At the track, testing yesterday - car ran great.
Today at the races, it's running just a wee bit rough and a CEL appears.
Ran a scan - could be a number of things, so we clear the codes and go back out. This time, I don't make a full lap - really rough. Scan says cylinder 5 fault. The spark plug and the coil are toast. So we replace them and all is well - motor strong, solid laps.
BUT now the dash lights (speedo, air temp, clock, odometer, etc) stay on....all the time. Everything else shuts off at key removal (radio, climate control, etc)...but not the dash. Locked the doors with windows up, etc. But they still stay on. I'm worried I'll wake up to a dead battery.
Any ideas???
"could be a number of things, so we clear the codes" - Thanks for the help with the awesome diagnostic info. :P Maybe write that **** down before you and your ham-fisted buddies clear the codes?
996 electrical gremlins are generally one of two things: Your car is wet, and the electronics are toasted, or the ignition switch is worn out and everything is going to turn to **** until you replace it.
How concise - thank you
We're at a racetrack, trying to get back to an operating condition under very trying circumstances!
The car is certainly not wet, and you might be right about the ignition, but your ham-fisted attitude is certainly causing this post to turn to ****.
hahaha I am saying nothing. It's usually me that gets the **** flying my way. Now it's your turn schnell.. I suggest you put some WD 40 on your bum coz someone wants to shove their diagnostic tool up it ...hahaha
Codes were mostly smog related (because a cylinder wasn't firing), but it wasn't clear what was causing the CEL, so clearing the codes gave us a closer look at the issue, then we fixed it.
The only issue, discovered later was the dash led's. Tried a battery reset - didn't work. But I disconnected last night (didn't want to go out to a dead battery). Going now to reconnect - fingers crossed.
FWIW - the dash on my car stays on for a few minutes after shut down and key removal. I've never timed it but I would say for like for maybe two minutes, then it all shuts off. Maybe not really a problem but just the way it is? Also, doesn't matter if I lock it...still stays on until it decides to shut off.
This is a source reference. Confirm exact model applicability in the original material.
