Check engine & Air bag lights ON

[LookAtThatSHO]

My check engine light has been on for nearly 30,000 miles. I believe it's on because of when I did my y-pipe upgrade, my buddy took one of the O2 sensors out and left it hanging by the exhaust and it melted some of the plastic on the sensor, so when we re-installed the check engine light came on. The sensors have since been changed and new ones installed after the upgrade, but the Check Engine light has remained on ever since. Hooking the CPU up to a reader shows me that it's complaining about the O2 sensors, but I know they aren't the culprit. My question is, does the CPU need to be refreshed in order for the light to finally go out?

Also, My air bag light has been blinking for over 50,000 miles now. Yes, my instrument cluster has looked like it's been Christmas for a long time now. I plan on fixing the problem on why it has been blinking here shortly. My question is, after fixing the problem, does the CPU also need refreshing before it will stop blinking or should it go out on its own if everything checks out?

Thanks,
Mike

 

[95IVSHO]

No the cpu does not need refreshing, if you replaced the o2 sensors because the scanner told you to do so, you should of done some testing. what kind of scanner did you use, hopefully not one of those parts store type scanners. you may have a bad wire, frayed, shorted out somewhere. clean and check your connections, see if you can find a shop or somebody with a oscilliscope or very good DMM with a low amp clamp and check the readings on the wires. you will be able to check the amps and watch the graphs and see if the o2 heaters are working. do some testing and get back with us. as for the air bags, youll need a factory scanner or mastertech or snapon to get the codes for that.

and your christmas instrument cluster will start dying off as you fix the problems, no need to refresh the cpu

 

[LookAtThatSHO]

Thanks for the reply. I originally changed the o2 sensors because they came with my new SS y-pipe with only a few 1000 miles on them. I thoguht my old ones were original anyways, and my SHO had about 130,*** miles on them at the time.

SO, this isn't good news to me that the computer will fix itself. As I mentioned above, I thought the o2s that came with my new y-pipe were practically new and worked flawlessly; now I have another problem. The scanner that was used to determine that the o2s were the culprit was one from a local garage, so I know it's valid as it's used all the time by the mechanics there. I'm sure one of them should have a DMM or another gadget we can use to measure the amps. I will definitely get back to everyone here and let them know what the true culprit was.

For the airbags, I've already got it narrowed down to either a 1) faulty diagnostic module (the one located behind the glove box) or 2) wiring harness going to the front/primary crash sensor (located under the radiator cover). Both are in transit and should arrive by next Tuesday (thanks to another member here on the forum).

I'll have the SHO in the shop sometime next week to get this all figured out. Can't wait to get these lights out!

Thanks,
Mike

 

[luigisho]

Clear the computer of codes by disconnecting the battery for a while. That should clear any stored codes and then see what comes back.