Auto >> AutoSPT >  >> Auto Repair

How do you reset the check engine light on a 1996 GMC Jimmy?

You can't just "reset" the check engine light (CEL) on a 1996 GMC Jimmy (or any OBD-II compliant vehicle) without addressing the underlying problem. The light is there to tell you something is wrong. Simply clearing the code without fixing the issue will just make the light come back on.

However, if you've *already* fixed the problem that caused the CEL, you can clear the code using one of these methods:

* Disconnect the battery: This is the simplest method. Disconnect the negative (-) terminal of the battery for about 10-15 minutes. This will reset the computer's memory, including the trouble codes stored for the CEL. Reconnect the battery, and start the vehicle. The light may take a few driving cycles to turn off completely if the problem is truly resolved.

* OBD-II Scanner: This is the preferred method. An OBD-II scanner (available relatively cheaply at auto parts stores) can read the diagnostic trouble codes (DTCs) that triggered the CEL. This allows you to understand the problem and verify that it's been fixed. Most scanners also have the ability to clear the codes. This method is significantly better because it provides useful information about the problem.

Important Considerations:

* The problem must be fixed: Ignoring the check engine light and simply resetting it without fixing the root cause can lead to further damage to your vehicle and potentially dangerous driving conditions.

* State Inspections: In some states, a check engine light can fail an emissions inspection, even if it's been reset.

* Intermittent Problems: Sometimes, the problem is intermittent. Even after clearing the code, the light might return if the problem isn't consistently replicated.

In short, find out *why* the check engine light is on before you reset it. Use an OBD-II scanner to diagnose the problem; it's the best way to ensure your Jimmy is running safely and efficiently. Disconnecting the battery is a last resort, only to be used after confirming the issue is solved.