What to look at in live data
The standard data includes the check engine light status as the ECU sees it (on or off, with the number of stored codes) and, on many cars, the time run with the light on. Compare it with the dashboard: if the ECU says the light is on and the dashboard shows it off, or the other way round, the command isn't reaching the light.
Test it at switch-on too: with the ignition on and the engine off the light should come on for a few seconds, then go out after starting if there are no faults. If it never comes on, the fault is in the link between ECU and instrument cluster, or in the cluster itself; on newer cars the cluster lights it on a network message, so it is worth reading the cluster's codes too. Until the light works, read the codes now and then: a real fault might give no sign on the dashboard.
How serious is it and can you drive?
For the engine, severity is low. You can drive if you can see the speed and the important warning lights. If the cluster goes dark or you can't see the danger lights, have it checked before long trips.
Read P0650 on your car
With an OBD2 adapter, DrivePulse reads your car's fault codes and tells you what they mean, whether you can drive and what to check. It's read-only: it writes nothing to the ECU.
Get DrivePulseWhat it means
The engine control unit turns the light on when it finds a fault that affects emissions or how the engine runs. On older cars it does this through a wire that goes straight to the instrument cluster; on recent ones it sends a message over the car's network and the cluster lights the lamp.
Either way the control unit monitors the circuit: if the current or the response isn't what it expects, it stores P0650. The code doesn't say the engine has a problem; it says the warning about a problem might not work.
Symptoms
- The check engine light doesn't come on for a few seconds when you switch on the ignition, as it should.
- Or the light stays on all the time, even with no other codes.
- Other warning lights or gauges on the cluster behaving oddly.
- Often no symptoms while driving.
Most likely causes, in order
- The bulb or LED of the light in the instrument cluster, on cars with a direct wire.
- A connector behind the cluster, loose or corroded.
- A broken or shorted wire between the control unit and the cluster, sometimes after work behind the dashboard.
- A weak battery or a loose cluster ground, which throws off the measurements.
- The instrument cluster or the control unit failing, which is rarer.
What to check before the garage
- Switch on the ignition without starting the engine: for a few seconds the check engine light should come on with the others, then go off once the engine is running. If it never comes on, the circuit really has a problem.
- Note whether other lights or gauges act up too: then the problem is more likely in the cluster.
- Check the battery: low voltage often makes the cluster misbehave.
The risk is what you don't see
With P0650 the engine often runs perfectly. The problem is different: if a real fault turns up tomorrow, a misfire or a failing sensor, the light might stay off and you wouldn't know. A light flashing for misfires, for example, tells you to stop: without the light, that warning is missing.
So it's worth fixing even if the car seems fine. Until then, reading the codes now and then tells you whether something else is stored.
At the garage: what to ask
Reading the codes of all control units, testing the light with the diagnostic tool, which turns it on and off on command, and checking the wires and connectors between control unit and cluster. In order of cost: bulb or connector, wiring repair, and only then the cluster or the control unit.
What DrivePulse shows
DrivePulse reads P0650 and opens the instrument cluster card, with the advice to check the battery and to note whether the problem changes with heat, cold or bumps; it also tells you whether the code is pending or confirmed.
Above all, DrivePulse reads the codes straight from the control unit: until the light is fixed, a check now and then tells you whether there's a fault the light isn't showing you. In Health, the battery voltage with the engine off and during cranking tells you whether the cluster's power supply is borderline.
Frequently asked questions
Can I drive with P0650?
Yes, if you can see the speed and the important warning lights. Have the light fixed soon, because it might not warn you about other faults.
Does a check engine light that's off mean all is well?
Not with P0650: the light might not come on. Until it's fixed, reading the codes with an OBD2 adapter tells you.
What's the difference from U0155?
U0155 says a control unit can no longer hear the instrument cluster. P0650 is only about the check engine light's circuit.
Related codes
Related guides
- Buying a used car? What to check: a code cleared just before the sale shows up in the distance driven since the last clear.
What you need to read it
All you need is an ELM327 OBD2 adapter, plugged into the diagnostic port, usually under the steering wheel. On iPhone it has to be Bluetooth Low Energy (BLE) or Wi-Fi, like the Veepeak OBDCheck BLE or the Vgate iCar Pro 2S; on Android classic Bluetooth adapters work too, once paired in the phone's settings. Veepeak recommends DrivePulse to its customers, and the Vgate is the one the Italian site Macitynet tested together with the app. The full list is on Which adapters work.
DrivePulse is on iPhone and Android. It's read-only: it writes nothing to the ECU and doesn't clear codes. You try it for 7 days from the first connection or for 15 trips, whichever comes first, then unlock it with a single purchase, no subscription and no account.