Codes set while drive belt is off

[ree]

I'm looking into a belt/pully issue. Will codes that are set when the engine is operated while the drive belt is off clear themselves? Or will I need a programmer to clear them?

[f5fstop]

All codes, except for a few SIR (airbag) codes will eventually clear after X-number of ignition run cycles. (Ignition run cycle is from a cold start to a specific engine temperature, and back down to a cold start value). Without looking up the H2, I will guess that any codes (other than SIR) will clear within at least 100 ignition cycles without the condition happening again.
The airbag codes that keep the light on and active codes set are usually quite obvious, the air bag has gone off, or the bag has not gone off and you have been in a serious wreck that triggered the system to near deploy mode.

Probably what you will set is 0562 (low system voltage), 0622 duty cycle PWM out of range, 1637 regulator detects a problem in control circuit, these type of codes should clear in 40-50 ign cycles. You may also cause some HVAC codes (not sure), and some of these codes can stay around for up to 100 ign cycles (don't ask me why the HVAC codes can hang around for such a long time).

Again, other than SIR, I can't think of any that will hang around forever. However, I cannot check the system right now, and I'm taking this from memory.

[drmiles]

Put a piece of black tape over the display. Fixed!!

Go to the dealer and tell him to clear the codes, wash the car and get you some coffee.

Either way works well...

[ree]

I would except the dealer's 120 miles away.

I want to get a programmer to toy with my shift points and change the speedo when I upgrade to 37s so maybe now's the time to go shopping over at trailduty.

[ree]

Originally Posted by f5fstop

All codes, except for a few SIR (airbag) codes will eventually clear after X-number of ignition run cycles. (Ignition run cycle is from a cold start to a specific engine temperature, and back down to a cold start value). Without looking up the H2, I will guess that any codes (other than SIR) will clear within at least 100 ignition cycles without the condition happening again.
The airbag codes that keep the light on and active codes set are usually quite obvious, the air bag has gone off, or the bag has not gone off and you have been in a serious wreck that triggered the system to near deploy mode.

Probably what you will set is 0562 (low system voltage), 0622 duty cycle PWM out of range, 1637 regulator detects a problem in control circuit, these type of codes should clear in 40-50 ign cycles. You may also cause some HVAC codes (not sure), and some of these codes can stay around for up to 100 ign cycles (don't ask me why the HVAC codes can hang around for such a long time).

Again, other than SIR, I can't think of any that will hang around forever. However, I cannot check the system right now, and I'm taking this from memory.

Thanks. That's enough to convince me to just get the programmer I've wanted to get anyhow. I don't want to have the check engine light on and wonder if it's because of what I did or because of a real issue.

[PARAGON]

Originally Posted by ree

Thanks. That's enough to convince me to just get the programmer I've wanted to get anyhow. I don't want to have the check engine light on and wonder if it's because of what I did or because of a real issue.

dude, it's cool to have anyway.

Twice now I've had a situation where my truck kept throwing codes and would go into reduced power. Read the code and it was some BS and then was some BS code the next time, it wasn't making sense but I could clear the code and get moving again....... for a little while until it would throw the code.

One was a voltage issue and the other was a loose connection at the throttle position sensor. Both times I was wheeling and at times where I had to do something but couldn't go anywhere because the RPMs would only get up to about 1000 or so. The programmer saved me those days.

[f5fstop]

Originally Posted by ree

Thanks. That's enough to convince me to just get the programmer I've wanted to get anyhow. I don't want to have the check engine light on and wonder if it's because of what I did or because of a real issue.

Programmer's cool, but check engine light should not show for history codes, once the active code is set and the problem is corrected (e.g., generator sets a code, but with the belt back on, problem is corrected so code goes to history status).

[PARAGON]

Originally Posted by f5fstop

Programmer's cool, but check engine light should not show for history codes, once the active code is set and the problem is corrected (e.g., generator sets a code, but with the belt back on, problem is corrected so code goes to history status).

I don't think that's the case for all codes that get set. I ran across a couple that would not turn the light off unless there were 3 ignition cycles.

Action Taken When the DTC Sets - Type A
The control module illuminates the malfunction indicator lamp (MIL) when the diagnostic runs and fails.
Action Taken When the DTC Sets - Type B
The control module illuminates the MIL on the second consecutive ignition cycle that the diagnostic runs and fails.

• Conditions for Clearing the MIL/DTC - Type A or Type B
• The control module turns OFF the MIL after 3 consecutive ignition cycles that the diagnostic runs and does not fail.
• A current DTC Last Test Failed clears when the diagnostic runs and passes.
• Use a scan tool in order to clear the MIL and the DTC.

[ree]

Originally Posted by f5fstop

Programmer's cool, but check engine light should not show for history codes, once the active code is set and the problem is corrected (e.g., generator sets a code, but with the belt back on, problem is corrected so code goes to history status).

So why do the service manuals tell techs to clear codes after procedures? Just to clear history so that if another tech sees the truck 10 miles from now they don't get confused?

Nice try talking me out of getting a programmer. Im gonna do.