BradC
18th March 2022, 11:23 AM
I've seen loads of "my code reader gave me these codes, what does it mean" posts. Here's a 30 second run-down on how to help us help you.
Firstly, when you read a fault code, it comes in 2 parts separated by a hyphen. Pxxx-4D for example. The first part identifies the fault but the second identifies the nature of the fault.
ie, Pxxx says the fault lies with the frobnozzle, but the second part (-4D) identifies is power supply is shorted to ground. It could also be open, have a correlation error, out of range error or a plausibility error. There's a plethora of possibilities and they all mean something different.
Without the second part of the code, you're only half way there.
Once you have the complete code, put it into Google with a bit of refinement, such as "Discovery 3 P2290-0D" and see what comes up. More than half the time it actually brings up a pdf that's part of the workshop manual and that lists precisely what the code means and the list of possible causes. That saves people on the forum from having to do that work for you and significantly increases the likelihood of getting a prompt and *experienced* response.
tldr; Get the whole code including the suffix, then put it into google.
Firstly, when you read a fault code, it comes in 2 parts separated by a hyphen. Pxxx-4D for example. The first part identifies the fault but the second identifies the nature of the fault.
ie, Pxxx says the fault lies with the frobnozzle, but the second part (-4D) identifies is power supply is shorted to ground. It could also be open, have a correlation error, out of range error or a plausibility error. There's a plethora of possibilities and they all mean something different.
Without the second part of the code, you're only half way there.
Once you have the complete code, put it into Google with a bit of refinement, such as "Discovery 3 P2290-0D" and see what comes up. More than half the time it actually brings up a pdf that's part of the workshop manual and that lists precisely what the code means and the list of possible causes. That saves people on the forum from having to do that work for you and significantly increases the likelihood of getting a prompt and *experienced* response.
tldr; Get the whole code including the suffix, then put it into google.