ok, i had my codes read

[katt68]

ok,i have been getting my check engine light coming on agfter driving about 10 kms. i had the code pullked on friday and the only one my 92 ex is giving is for the oxygen sensor, the truck is running rich. i changed the o2 sensor back in november( i have had this problem since about then. i do not understand why it would say it is the o2 sensor since there is a new one there. the mechanic said it seems to be getting no signal at all. the truck also, sort of bogs out when giving slight amouyt of gas upon acceleration. what can i do to check and get things working for sure.

 

[Texplorer]

Did you change all the O2 sensors or just one?

 

[slag]

Correct me if I am wrong, but I believe the 91 and 92 at least only have one o2 sensor that is right after the Y but still on the y pipe.

 

[Texplorer]

I didnt even look at the year, I have no idea how many the 91-94 have. I know I have like 4. Sorry.

 

[MrShorty]

A '92 only has one O2 sensor.
Which O2 sensor code is your mechanic getting? Lean or rich?
There's a lot more to an O2 sensor code (or any other code for that matter) than declaring the O2 sensor to be faulty. The computer really can't see past the end of its proverbial nose. When the computer generates a code, all it knows is that, at the point where it measures the voltage (somewhere in it's innards), it sees something out of bounds. It can't distinguish between a fault that's a result of a bad sensor or bad wiring or bad computer internals. It also can't tell if a bad O2 sensor reading is from bad fuel delivery. (Refer to a post by Glacier991 titled "check engine light myths" or something like that)
What has your mechanic done, besides pull the codes? Oxygen sensor codes can be some of the more difficult to diagnose, because there are so many possible causes. Checked the wiring? Fuel pressure? Has he been through the circuit pinpoint test for the code he's getting?

 

[Opera House]

If this one reads rich, maybe the first one did too. Sounds like what qualifies as a mechanic is just someone with some tools and willing to get dirty. Without the actual code number we can only guess what you have told us is what is happening with the engine. At this age, I would be pulling the vacuum line and looking for the presence of gas from leaking fuel pressure regulator. It's not the sensors fault if it is telling you there is more gas and less air than it expects.

Didn't Shakespeare say.........
The fault dear Brutus, is not in our sensors
But in ourselves.

 

[Positive Vibes]

We need exact codes and more info. What has the mechanic or you replaced besides the O2 sensor? Cleaned the MAF? Change the FPCR? Vacuum lines?

 

[katt68]

ok, here is what i know

alright, it is a code 117...o2 sensor rich. we noticed on his computer that the voltage was not changing at all with revving the truck or anything on the koeo tests.
i have cleaned the maf, adjusted the tps to .96 volts,checked the iac and cleaned,new o2 sensor.
i am not getting a rich black sooty exhaust or anything. gas mileage is bad for sure but did get a bit better with the tps being adjusted to .96 volts. please help !

 

[MrShorty]

Code 117? According to my lists, that's ECT sensor voltage too low, causing to computer to read the temperature too high.
Did you mean 171?

 

[katt68]

maybe

you could be right,171 was the code.

 

[metstalker]

94 oxygen sensor

my 94 only has one oxygen sensor

 

[TheRookie]

KOEO is Key on engine Off. I assume you mean KOER

 

[MrShorty]

Out of curiosity, any code from the KOER test? 171 is a continuous memory code. If the KOER test gave 111, then the fault is intermittent enough to only show up while driving.
Other than that, I return to the same questions I asked earlier: Are the fuel pressure tests normal? Wiring from the O2 sensor to the computer intact? Any exhaust leaks? The circuit test is quite involved, has there been any attempt to review it for possible causes?

 

[katt68]

fuel pressure test?

how do i do a fuel pressure test?

 

[MrShorty]

Get a fuel pressure gauge (any self-respecting parts store will have one). Attach it to the Schrader valve (looks like a tire stem) on the fuel rail. A good manual will have a detailed protocol to follow, but basically it goes like this.
KOEO -- run fuel pump (use test lead on self-test connector) and note pressure. Should be 35-45 psig. Turn fuel pump off, pressure should stay within a few psig for several minutes.
KOER -- With vacuum line to FPR disengage, shouldn't change. If vaccum line is left hooked up to FPR, should drop 5 to 10 psig.
Visually check vacuum line to FPR. Should not be any fuel in it.

 

[Blake D]

Please help with codes

Here are my codes
These are with engine off.
565
and after long seperator pause it is 332

can anyone tell me what these are and direct me on how to fix?

Thanks
Blake

 

[Blake D]

can anybody help me out with these codes?

 

[Maniak]

Blake,
Accroding do what I found....

Code 565 is Canister Purge 1 solenoid/circuit failure
Code 332 is EGR did not open/respond during test or did not open intermittantly...

I'd start looking for broken vacuum lines and possible wire issues (stripped/burned wires)..

I'm some other people with have more ideas..

~Mark

 

[MrShorty]

First thing I would suggest is get yourself access to a manual. I have found Chiltons/Haynes to be mostly inadequate for this computer diagnostics. They may have the procedure to pull codes, but they don't tell you what to do with the codes once you get them. Best resource I've found is Mitchell manuals at the library (too cheap to date to buy the emissions manual, though it is available and not overly expensive from the right source). Then you have code lists and most of the information you'll need to diagnose these things.
That said:
KOEO hard fault 565=cannister purge solenoid circuit failure. Not a common code, and not a lot that triggers it. Basically there's either an open or a short to ground in the cannister purge solenoid circuit. Get a wiring diagram and inspect the circuit.
From your description, that long separator pause (should have been a voltage pulse to separate, too), separates the KOEO codes from the continuous memory codes. When diagnosing these systems, you want to start with the KOEO hard faults and resolve them until you get a pass (111) code for the KOEO codes. Then move to the KOER test (you don't mention any codes for this test). Only after getting a pass code for the KOER test do you want to move on to the continuous memory codes. That said: 332 indicates a fault in the EGR system. Would want to go through the circuit pinpoint tests before replacing anything (many people make the mistake of replacing the EGR valve when the fault really lies in the EGR position sensor).

 

[Blake D]

Is this something I can do myself or is it better left to a mechanic?
What problems will I have if I do nothing?