16 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHLitronic problem
Leading reported evidence
Check ground points and they are also in different places
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
Also checked ground points and they are also in different places.
Leading evidence: 'Check ground points and they are also in different places' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'issue' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check ground points and they are also in different places' (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 removed and cleaned an already sparkling head light switch, checked it with an ohm meter and then a test light once reinstalled.
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 suspect 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.
Suspected cause
If one light was intermittently not working, I'd suspect the ballast; if both are functioning the same way (they either both light or don't), the switch is probably the issue.
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 suspect 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.
Suspected cause
If both fail to turn on, it's probably the 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.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
issue
No successful repair reported for this finding.
0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that suspect 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.
Suspected cause
If one light was intermittently not working, I'd suspect the ballast; if both are functioning the same way (they either both light or don't), the switch is probably the issue.
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.
16 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: 20261026T122219Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I searched but did not find this specific issue. On occasion, my (02 C2) headlights will not turn on. Flick the high beams and that works with the lights off but no low beams. Turn it on and off, key on and off, still nothing. Different day they work fine. Where to start? Thanks in advance.
If both fail to turn on, it's probably the switch. The litronics - like aftermarket HID kits - have a ballast for each light. If one light was intermittently not working, I'd suspect the ballast; if both are functioning the same way (they either both light or don't), the switch is probably the issue.
Thanks all. Is there some way to take it apart and clean it? Pretty sure I can get it out in one piece. Is it possible for the connector to be intermittent or corroded?
@Zookie - is there only one ballast for both lights? That seems a likely solution because when they don't work I occasionally see a faint flicker like they're trying to come on.
I removed and cleaned an already sparkling head light switch, checked it with an ohm meter and then a test light once reinstalled. Still no joy. Fuses A9 and A10 (R and L low beams) both have power when the key is on and the headlight switch is on BUT the light is very dim relative to other fuses. I measured voltages of 5.7 (motor on or off) on both fuses while others are ~12 with motor off and 14.6 with motor running. Will start tracing the wiring diagrams for next step. Any ideas anyone? Levelers look like they're working too.
Forgot one more thing. Zookie said ballast but it seems like each light has its own so doubtful that both went at the same time unless there is a current draw across the circuit. As is said, time to trace the wiring diagrams.
Oh yeah? Which one?
Each headlight has its own ballast. Since the OP says neither headlight is working, that would mean that both ballasts went out at the same time. That will never happen. You'd have a better chance of winning the lottery.
NO. He's wrong.
its either your headlight switch or the bright/dim stalk switch as these are
the only 2 points that affect both headlights.
We are talking about the headlight switch, not the ignition switch.
Did you spray the cleaner
inside the switch?
Down around the shaft?
Its the contacts inside that get carbon build up, not the connections on the back of the switch.
Yes but will do it again. Can't hurt. Also traced the power supply wiring to the headlights. Both circuits also supply the headlight washers and they work fine (first time I ever tried them). Also tried pulling the headlight washer relay but again no joy. I agree with you that it's got to be the stalk or the switch. Low voltage seems to imply corrosion of some kind. Also checked ground points and they are also in different places. Maybe the overall chassis ground? Not enough current to fire up the lights? Clearly starting to grasp at straws.
Thanks for the feedback. This forum truly rocks.
Fixed! I sprayed the s#*it out of the switch and worked it back and forth for a good while. Reinstalled and works perfectly. I imagine the lights will come in handy with the shorter days ahead. Still can't figure out the circuit that cuts the headlights with the key off but we'll save that for another day. Thanks again for the help!
