DTC's Showing up on Instrument Cluster
DTC's Showing up on Instrument Cluster
Does anyone know what the following codes signify? I drove about 50 Highway miles today, exited and got gas and then my Service Engine Soon light came on. Gas cap is tight, but the truck is showing the following codes:
DTC D262
DTC 9202
DTC 5284
Any help would be appreciated. I purchased the extended warranty, but am not sure if what these codes relate to would be covered.
Thanks In Advance, MISTERP
DTC D262
DTC 9202
DTC 5284
Any help would be appreciated. I purchased the extended warranty, but am not sure if what these codes relate to would be covered.
Thanks In Advance, MISTERP
These are not directly the engine faults but a reflection of 'some' engine faults as well as other areas of the trucks operation.
Have the engine scanned to pick up all the fault codes.
DTC 262 is missing SCP message.
DTC 9202 is fuel sender open.
DTC 5284 is oil pressure switch failure.
I'm sure the engine codes will say the same but you have to service by the engine codes, then the dash messages should clear unless there is something else.
You can't always go by this but sometimes is happens to be the same or quite close.
Example is a cylinder miss won't show on a dash readout code.
Have the engine scanned to pick up all the fault codes.
DTC 262 is missing SCP message.
DTC 9202 is fuel sender open.
DTC 5284 is oil pressure switch failure.
I'm sure the engine codes will say the same but you have to service by the engine codes, then the dash messages should clear unless there is something else.
You can't always go by this but sometimes is happens to be the same or quite close.
Example is a cylinder miss won't show on a dash readout code.
Bluegrass,
Where is a table to the odometer codes that correlate to OBD-II codes (if one exists) available?
In any event, the original poster needs to have the OBD-II codes pulled.
Steve
Where is a table to the odometer codes that correlate to OBD-II codes (if one exists) available?
In any event, the original poster needs to have the OBD-II codes pulled.
Steve
Now, if I tell you, everybody will know!
Check MustangWorld, how to section, on HEC Cluster dgn.
This only corralates to a limited number of engine functions that has to do with dash display.
The dash has it's own micro processor and has the benifit of some inputs to it from the engine control system.
Once you get there, you will see what it monitors and can tell you.
The bAtt subsection has left out a range of values between 124 and 215, that equates to the normal operating voltage range. If you test your's, you should find a value around 130 +/-.
Enjoy.
Check MustangWorld, how to section, on HEC Cluster dgn.
This only corralates to a limited number of engine functions that has to do with dash display.
The dash has it's own micro processor and has the benifit of some inputs to it from the engine control system.
Once you get there, you will see what it monitors and can tell you.
The bAtt subsection has left out a range of values between 124 and 215, that equates to the normal operating voltage range. If you test your's, you should find a value around 130 +/-.
Enjoy.
Well, found the HEC Dealer test mode right under my nose.
It is contained on the service CD!
On my 2000 CD:
Group 4 Electrical
Section 413-01 Instrument Cluster
Diagnosis and Testing
The supplied table also gives a limited number of corresponding OBD-II codes that relate to functions monitored by the cluster.
Thanks for the heads-up and the nudge in the right direction.
Steve
It is contained on the service CD!
On my 2000 CD:
Group 4 Electrical
Section 413-01 Instrument Cluster
Diagnosis and Testing
The supplied table also gives a limited number of corresponding OBD-II codes that relate to functions monitored by the cluster.
Thanks for the heads-up and the nudge in the right direction.
Steve
Well, I took it in yesterday and it turned out to be a faulty thermostat... I was wondering why it seemed like it was taking forever for the damn truck to start blowing heat! It's too cold and crappy out up here in Chicago to try to figure out anything under the hood right now. Thank goodness for extended warranty.
Ken
Ken
(Much) more info ;-))
Hi.
From Dan, over at 'StangNet;
----------------------------------------
"DanM01-08-04, 08:45 PM
Eegads, the misinformation here is BRUTAL!
Okay, to start, here's how Diagnostic codes work. And frankly I cannot BELIEVE the Ford tech didn't know this. He should be fired.
Codes do start with a letter. Like P0xxx, P1xxx, P2xxx, P3xxx. Those are all POWERTRAIN codes, 400 of them (hence the P). They refer to powertrain (engine, tranny) functions as well as emissions systems. Then you have C0xxx-C3xxx These are CHASSIS codes. Then you have BODY codes, B0xxx-B3xxx, and COMMUNICATION codes, U0xxx-U3xxx. That's 1600 codes.
Now, in a computer, you need to represent these codes as 16-bit numbers. There is no P or U in a computer, we use hexadecimal, so with a bit of manululation you get:
P0xxx = 0xxx
P1xxx = 1xxx
P2xxx = 2xxx
P3xxx = 3xxx
C0xxx = 4xxx
...
C3xxx = 7xxx
B0xxx = 8xxx
... (remember hex digits, 0-9,A,B,C,D,E,F)
B3xxx = Bxxx
U0xxx = Cxxx
...
U3xxx = Fxxx
Soooo, in short, 5284 = C1284. Your Ford tech should have known that. GM uses the exact same code structure, I know that for a fact, and I'd bet Chrysler does too.
As to the code itself, it's not an emissions code**, it's an Oil Pressure Switch code, just like the description says. And it's not an uncommon one - SEVERAL 99+s show this code ON THE CLUSTER occasionally, it's nothing to worry about. There's probably a slight blip in the oil pressure signal from the sensor, and the cluster picks up on it and sets the DTC.
It's correct that the cluster codes have nothing to do with codes that may or may not be in the EEC (they're the same codes numerically and mean the same, but a code set in the cluster does not mean the code is set in the EEC as well, and visa versa). The cluster sees the oil pressure signal from the sensor just the same as the EEC does. The fact that the CLUSTER has set that code while the EEC hasn't (if the EEC had set it too, you'd have a SES) just means that the cluster is more picky (probably TOO picky) about that particular diagnostic routine than the EEC is.
Ford, I'm sure, knows about this issue, but since it's a diagnostic issue, and not a problem with the switch itself, and since only the CLUSTER usually detects it, and no SES is usually set, there's really no reason to do anything about it.
Particularly when Ford's own mechanics don't seem to know how to read codes properly. :shrug:
Edit: Just saw that you ARE getting a SES. If your gauge is still reading okay pressure, and the car runs fine, then it's more than likely it's the same 'blip', just bad enough that the EEC is setting the code in addition to the cluster. I'd bet if you cleared it, it'd go away. If it keeps coming back, I might check the oil pressure sensor connector and terminals, or maybe replace the sensor. Either way, your engine is OKAY. It's just that top-notch Ford quality coming through.
**Note DTCs certainly CAN have to do with emissions. Several of the Powertrain codes are devoted to emissions systems such as EGR, catalyst operation, and fuel tank/canister systems. If the EEC detects an issue that would seriously affect emissions (like an EGR problem), it will set the appropriate code just as if it were a performance issue. Caveat being that usually emissions diagnostics are much 'softer', i.e. they are more loosely calibrated and generally take longer periods to set.
-----------------------
Not sure how a faulty t'stat could have set ANY of the cluster codes you mentioned. What code was set in the PCM, that led the mech to diagnose a faulty t'stat?
cheers
From Dan, over at 'StangNet;
----------------------------------------
"DanM01-08-04, 08:45 PM
Eegads, the misinformation here is BRUTAL!
Okay, to start, here's how Diagnostic codes work. And frankly I cannot BELIEVE the Ford tech didn't know this. He should be fired.
Codes do start with a letter. Like P0xxx, P1xxx, P2xxx, P3xxx. Those are all POWERTRAIN codes, 400 of them (hence the P). They refer to powertrain (engine, tranny) functions as well as emissions systems. Then you have C0xxx-C3xxx These are CHASSIS codes. Then you have BODY codes, B0xxx-B3xxx, and COMMUNICATION codes, U0xxx-U3xxx. That's 1600 codes.
Now, in a computer, you need to represent these codes as 16-bit numbers. There is no P or U in a computer, we use hexadecimal, so with a bit of manululation you get:
P0xxx = 0xxx
P1xxx = 1xxx
P2xxx = 2xxx
P3xxx = 3xxx
C0xxx = 4xxx
...
C3xxx = 7xxx
B0xxx = 8xxx
... (remember hex digits, 0-9,A,B,C,D,E,F)
B3xxx = Bxxx
U0xxx = Cxxx
...
U3xxx = Fxxx
Soooo, in short, 5284 = C1284. Your Ford tech should have known that. GM uses the exact same code structure, I know that for a fact, and I'd bet Chrysler does too.
As to the code itself, it's not an emissions code**, it's an Oil Pressure Switch code, just like the description says. And it's not an uncommon one - SEVERAL 99+s show this code ON THE CLUSTER occasionally, it's nothing to worry about. There's probably a slight blip in the oil pressure signal from the sensor, and the cluster picks up on it and sets the DTC.
It's correct that the cluster codes have nothing to do with codes that may or may not be in the EEC (they're the same codes numerically and mean the same, but a code set in the cluster does not mean the code is set in the EEC as well, and visa versa). The cluster sees the oil pressure signal from the sensor just the same as the EEC does. The fact that the CLUSTER has set that code while the EEC hasn't (if the EEC had set it too, you'd have a SES) just means that the cluster is more picky (probably TOO picky) about that particular diagnostic routine than the EEC is.
Ford, I'm sure, knows about this issue, but since it's a diagnostic issue, and not a problem with the switch itself, and since only the CLUSTER usually detects it, and no SES is usually set, there's really no reason to do anything about it.
Particularly when Ford's own mechanics don't seem to know how to read codes properly. :shrug:
Edit: Just saw that you ARE getting a SES. If your gauge is still reading okay pressure, and the car runs fine, then it's more than likely it's the same 'blip', just bad enough that the EEC is setting the code in addition to the cluster. I'd bet if you cleared it, it'd go away. If it keeps coming back, I might check the oil pressure sensor connector and terminals, or maybe replace the sensor. Either way, your engine is OKAY. It's just that top-notch Ford quality coming through.

**Note DTCs certainly CAN have to do with emissions. Several of the Powertrain codes are devoted to emissions systems such as EGR, catalyst operation, and fuel tank/canister systems. If the EEC detects an issue that would seriously affect emissions (like an EGR problem), it will set the appropriate code just as if it were a performance issue. Caveat being that usually emissions diagnostics are much 'softer', i.e. they are more loosely calibrated and generally take longer periods to set.
-----------------------
Not sure how a faulty t'stat could have set ANY of the cluster codes you mentioned. What code was set in the PCM, that led the mech to diagnose a faulty t'stat?
cheers
Last edited by MGDfan; Mar 18, 2005 at 07:11 AM.
Trending Topics
I never actually code scanned the truck, I just saw what I originally posted above. Is it possible that the oil pressure code got stored when I dump my oil and then start the truck and it takes a couple seconds to build pressure? I drove the truck today, and it smells like it is leaking coolant, and has smelled like this for about 5 months. I asked the dealer to check it yesterday and they claim that they pressure tested the system. I don't see any coolant leaking though.
Just a thought, but it might be the heater core leaking?? not sure, but I think there is a valve that might close in the heater lines, that would not allow the core to be in the circuit during the pressure test?
I'm sure someone will correct me if my thinking is wacko..
Matt
I'm sure someone will correct me if my thinking is wacko..
Matt



