Always good to have a known good O2 sensor.
if you want some confidence on whether the O2 is a contributor check whether problem only occurs in open loop goes away in closed loop. If problem is occurring in open loop only it’s not likely caused by O2 sensor.
The O2 is only used for afm after getting into closed loop.
Of course, you could have a bad O2 and never being able to get into closed loop. Old engines often have more than one problem which are not noticed until chasing a more obvious problem. I just mean that a bad O2 is not going to cause a idle hunting up and down if never getting into closed loop.
Adding to the “it’s worth investing in data logging capability”. You can check if the O2 is working by watching the output as the PCM changes the afm target. The PCM moves the afm up and down and expects to see a response in the O2. If it doesn’t reach expected values, too slow to respond, & some other stuff it will drop out of closed loop. I had a “lazy“ O2 sensor once which was dropping me out of closed loop during hot idle and causing me to failing emissions. It would get into closed loop on cold start fine, stay in closed loop driving but drop out on hot idle which is part of the emission test.
That said, getting going on data logging takes some time and effort. Worth it if you are planning to keep the truck for a long time. Probably too much time when in middle of problem now but something to think about for the future.
for now, I’d narrow done whether the problem is in open or closed loop or both before messing with O2. They aren’t that expensive but sometimes hard to remove. Easier to use a paper clip to decide if it’s a candidate first.
EDIT: Reply collision alert with @Sabinoerc above. But it sounds like we're on the
same page, so I'll leave the following reply in place.
Hello
@cc333,
Sometimes while you are troubleshooting a difficult issue, you end up learning on the
fly, and oftentimes this new knowledge would have been really helpful back at the beginning.
For what it's worth, Sabinoerc is giving you solid advice, as seen above.
In order to help the remote troubleshooters reading this thread, I just want to make
sure that we all understand/share the definitions for the following terms:
*
OPEN LOOP: Whenever the signals aren't available from the O2 sensors, the computer
will rely upon the (analog) signals from the remaining sensors in order to properly index
into the fueling and spark advance tables, allowing you to immediately drive a cold vehicle
smoothly and with the minimum emissions possible.
On a healthy GMT400, every time you drive the vehicle from a cold start, you *will* be in
Open Loop mode until the coolant temperature rises above a preset threshold and the O2
sensors start switching up & down around the ideal chemically-correct Air/Fuel ratio.
(Stoichiometric)
If your vehicle then switches successfully into Closed Loop mode at that time, then
the way your truck drives will be determined to a large degree upon how responsive/
how accurately/how poorly the O2 sensors measure the amount of oxygen in the exhaust
after the engine has attempted to burn the combustible mixture in each individual cylinder firing.
*
CLOSED LOOP: Once the O2 sensors have been warmed up enough (by the hot exhaust
stream only on the old single-wire sensors, warmed up much faster by the internal
heater circuit on the newer 3-wire O2 sensors) ...the base fueling & timing values in
the computer tables are fine-tuned in realtime by the feedback of your Oxygen sensors.
IF you are getting fast/accurate/reliable feedback from your O2 sensors, the way your
engine drives will be
improved.
On the other hand, it is quite possible for a mechanically sound engine + a correctly
operating computer to run just fine by themselves (Open Loop) ...but once the
engine heats up and the
aged out of spec/outright bad oxygen sensors are switched in,
*now* the engine starts running rough/lethargic/stanky/etc.
****
Given the above, it can be extremely helpful if the troubleshooter of one of our
GMT400 vehicles can determine whether or not the engine bay is operating
in either Open Loop vs Closed Loop operation. And 29+ years ago on the
OBD1 computers, the engineers added in this slick feature to let the mechanics
who understand all of the above (normally the Regional Reps/support-level Field
troubleshooters supporting the GM dealerships) to be able to access this diagnostic
hint with nothing more than a neat little shorting plug. (Or jumper wire, or even
paper clip for the roadside MacGyver types :0)
NOTE: In the perfect world, GM would have placed a tiny pushbutton somewhere in
the cab where I could watch the flashing SES light any time I wanted. But they
decided against that, and I actually understand why. Instead, they made these 2
pins on the ALDL plug perform *2* separate functions:
1) KOEO mode: Key On Engine Off, jumper 2 pins together and retrieve any stored
error codes. (And if there are no codes, we see a Flashing 12 repeated 3 times so
that the mechanic doesn't have to wonder if the 'error remembering/reporting
circuit' is working as advertised or broken.
2) Engine running mode: IF you wait until the engine starts to jumper these 2 pins,
*now* you will get 2 different flashing speeds:
*
FAST (2.5 times per second) flashing.
Attention!
Attention! You are in Open Loop mode,
does this make sense at your current coolant temperature and time since engine start?
*
SLOW (Once per second) flashing. You are in closed loop mode. If the engine is responsive/running
like new, you are good to go. On the other hand, IF your engine was running fine in
Open Loop, and then went bad shortly after the system went Closed Loop, then
this makes a big difference in our troubleshooting approach. (!)
****
Good feedback loops can help (within limits) to tune around fuel & ignition components that
are aging/starting to drift away from their original calibrations. Relying upon a error-correcting
feedback loop like this allows our engines to run 10s of thousands of miles with clean emissions
and like-new driveability, instead of running purely Open Loop a few thousand miles before the next
widget ages just a little out of specification, goofs up the driving experience, and the car owner
ends up back in the repair shop waiting room. (!)
But given this same authority, a Bad feedback loop can take a good engine/good computer combo and
make it run poorly.
*This* is why it would help us a lot with remotely troubleshooting your truck if you can
report this Open Loop / Closed Loop status to us.
OK, so I'm running the truck with the two pins shorted for open loop I think, and Service Engine Soon is flashing quickly. Is that normal?
c
Hopefully the above clarifies how the 'post engine running' shorting of these
2 ALDL pins gives you some additional insight into what mode of operation
that your computer is in. And why this was referred to as "Field Service" mode.
So if you could go back to
reply #9, reread that page out of the service manual,
and then monitor your truck and let us know when it is running well vs running poorly
(and if this change occurs when the computer switches from OPEN to CLOSED loop,
then we can use this info to refine our recommendations, and hopefully get this
sorted out with the lowest number of repair parts possible.
NOTE: If you figure out how to use this to your advantage, then you will be
troubleshooting at the old "Regional Rep" level. And of course, all of the above
is just a peek under the covers -- if you really want to set yourself up for full
Situational Awareness, at some point down the road you will want to invest in
some gear that will allow you to see ALL of the realtime data streams.
I tried to keep this explanation as straightforward as possible. But if I missed
the mark and you now have additional questions, please don't hesitate to post
them here.
Best of luck getting your GMT400 vehicle running as right as rain.
Cheers --