P0650
PowertrainMalfunction Indicator Lamp (MIL) Control Circuit
Most of the time this comes down to wiring or a connector problem between the engine ECU and the dashboard, rather than anything wrong with the engine itself. The ECU drives the check-engine light through its own control circuit, and P0650 means it has detected that circuit isn't behaving. Either the light won't come on when it should, it stays on for no reason, or the ECU sees an open or short where it expects a clean signal. It's a fault about the warning system, not the thing the warning system is meant to tell you about.
ⓘ Information only. This page provides general educational information about fault code P0650. We do not assess the urgency or safety implications of any specific fault. That requires in-person diagnosis by a qualified mechanic. Full terms.
Recommended next steps
Whether a fault is urgent, drivable, or routine depends entirely on the cause on a specific vehicle, and that can only be determined by a qualified mechanic with diagnostic equipment. If a warning light is illuminated, the most reliable next step is professional diagnosis.
What does P0650 mean?
P0650 is a Powertrain (engine, transmission, fuel system) fault code. It indicates: Malfunction Indicator Lamp (MIL) Control Circuit.
This is a standardised OBD-II code. The technical definition is the same regardless of the make or model of vehicle, although specific causes and symptoms can vary between vehicles.
Symptoms commonly associated with this code
Symptoms that drivers often report alongside this code. Not all may apply to every case:
- • Check-engine light doesn't come on at all when you turn the key to position two, when normally it should glow for a few seconds during the bulb check
- • Warning light stays lit constantly even though a scan shows no other faults stored
- • Light flickers or comes on and off at random, often over bumps or when the steering column flexes
- • Other genuine faults develop but you get no dashboard warning, because the lamp circuit is dead
- • Occasional odd behaviour from other warning lamps in the cluster on cars where they share a control feed
Possible causes
Causes commonly associated with P0650, listed in approximate order of typical investigation. The actual cause on a specific vehicle can only be confirmed by professional diagnosis.
- 1. Chafed, corroded or broken wiring between the ECU and the instrument cluster, the usual offender, especially where looms pass through the bulkhead grommet and flex over time
- 2. Corroded or backed-out pins in the cluster connector or the ECU connector, very common on older cars and anything that's lived near the coast
- 3. A blown fuse on the supply feeding the MIL circuit
- 4. The warning bulb itself or a failed LED inside the cluster on cars that still use a separate bulb
- 5. Internal fault on the instrument cluster circuit board, more likely on high-mileage cars with a history of cluster gremlins
- 6. Communication fault between the body control module and the cluster on models that route the MIL signal over the CAN network
- 7. Failed driver transistor inside the ECU, rare, and worth ruling everything else out before you go near it
How mechanics typically diagnose
A typical diagnostic sequence used by mechanics, provided here for educational reference only. Diagnostic work should be performed by a qualified mechanic with the appropriate tools and training.
- 1. Watch the cluster as you turn the ignition on without cranking. A working MIL should light up for a few seconds then go out. No glow at all, or one that never goes out, tells you straight away which way the fault is pointing
- 2. Pull the relevant fuse and check it. A blown fuse is a five minute fix and people skip it
- 3. Wiggle-test the loom and connectors at the ECU and behind the cluster while watching live data or the lamp itself. Intermittent P0650s are nearly always a connection that moves
- 4. Back-probe the MIL control wire with a multimeter and check for continuity to the cluster and proper voltage when the ECU commands the lamp on
- 5. On a CAN-equipped car, scan for U-codes alongside the P0650. If the cluster has dropped off the network the lamp fault is a symptom, not the cause
- 6. If the wiring, fuse and bulb all check out and there are no comms faults, you're looking at the cluster or, last of all, the ECU driver
Common questions about P0650
Will my car fail the MOT with a P0650 stored? +
What the tester cares about is the MIL behaving correctly during the bulb-check sequence when the ignition is switched on. If the light doesn't illuminate at all when it should, or it's stuck on permanently, that's a fail under the current rules. A working light that goes out properly is fine even if a code is sitting in memory. So with P0650 specifically you're at risk either way, because the whole point of the code is that the lamp isn't doing its job. Get the lamp itself working correctly before you book the test.
Roughly what am I looking at to put this right? +
Depends entirely on what's actually causing it. A blown fuse or a duff bulb is a few pounds in parts and ten minutes of your own time. Tracing and repairing a chafed wire or cleaning up a corroded connector at an independent garage usually lands somewhere around £60 to £150 depending on how buried the loom is. A faulty instrument cluster is the painful one, anywhere from £150 for a used unit and coding up to £400 plus at a main dealer once you add diagnosis and programming. An ECU at fault is rare but the dearest outcome, into four figures with reprogramming. Independents will save you a fair bit over a franchised dealer on all but the coding-locked jobs.
How do I work out which of these it actually is on my car? +
Start with the cheap stuff. Check the fuse first, then the bulb. If both are good, the way the light misbehaves narrows it right down. A light that's dead all the time points at an open circuit, a blown feed or a duff bulb. One that's stuck on points at a short to earth or a failed driver. A flickering light that comes and goes over bumps is a loose or corroded connection, full stop, and a wiggle test at the cluster and ECU plugs usually finds it. If everything wires out clean and the cluster's gone quiet on a scan, it's the cluster or the network feeding it.
Can I sort this myself without taking it to a garage? +
The easy half, yes. Anyone can swap a fuse and most people can get to the warning bulb on older cars. Cleaning a green, crusty connector with contact cleaner and re-seating it fixes a good number of these. Where it gets beyond a home job is chasing a break inside the loom or condemning a cluster, because you need a wiring diagram for your exact model and the patience to back-probe pins under the dash. Clearing the code without fixing the circuit just brings it straight back, and on a coded cluster you may need a dealer or auto-electrician to marry a replacement to the car anyway.
Information only, not professional advice
The information on this page is provided for general guidance and educational purposes only. It is not a substitute for diagnosis or repair advice from a qualified mechanic. Always verify any fault before paying for repairs. carfaultcodes.co.uk accepts no liability for decisions made based on this information. Full terms →