13 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCan you solve this riddle.
Leading reported evidence
Check physical wiring connections
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
Maybe checking the physical wiring connections to the reader port might yield something.
Leading evidence: 'Check physical wiring connections' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check physical wiring connections' (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.
Suggestion
just crashed my car..."KC: replace ignition switch."
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
Are you saying the engine was running when the obdii scanner was connected but once you disconnected it, the engine died?
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: 20261026T094842Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Car wont start. Battery is fine, sure of that. Lights, fuel pump energizes. It just won't engage the starter. Soooooo I plug an OBD scanner to see if it's throwing any codes before it's off to my indie. It has no codes. I select the "clear codes" anyway and clear the codes. With the OBD reader still plugged in I attempt to start and varoom it fires right up. So I'm happy now and upplug the OBD and car dies. I plug it back in do the clear codes function again and car starts again. Unplug and car dies. 996 87XXX everything else is normal. Any ideas?
If it's a stick shift, check or jump the clutch starter interlock switch.
Are you saying the engine was running when the obdii scanner was connected but once you disconnected it, the engine died? That would he very strange. I think the obdii is red herring.
Doesn't matter what the problem. That's what KC always says.
Alarm goes off... "KC: replace ignition switch"... Car won't start..."KC: replace ignition switch"... car has white smoke upon startup..."KC: replace ignition switch".... flat tire...."KC: replace ignition switch"... just crashed my car..."KC: replace ignition switch."
I think he mentioned that he keeps a dozen or so spare ignition switches on hand.
Well, you could just leave the OBDII reader plugged in and drive around that way. JK
Usual no start problems:
1. Ignition switch (known to cause all manner of weird electrical gremlins)
2. Clutch interlock switch
3. Corrosion on positive wiring leading to starter (the jumper point in the engine bay and on the starter itself)
4. Corrosion on grounding points (battery ground and engine ground)
I cannot guess why it works with the reader plugged in, other than the reader is either making a connection that needs to be made, or is breaking a connection. Maybe checking the physical wiring connections to the reader port might yield something. Usually codes stored in the ECU relate to emissions and engine functions, but do not stop the engine from starting.
I'd be inclined to think that the OBD-II port being used or unused would be coincidental. Maybe it isn't, but you spend a lot more time and money once you start adding red herrings to the flowchart.
