i want to clear my ses light, and see what it comes back on for(switched sims from one side to the other, now have no activity code for both) can i just unhook the battery, or do i have to unplug the pcm.

 

unhook battery and hang out for about 15minutes or you can walk back out to the garage in a half hour. It will reset. What are the codes you throwing? No activity to the rear 02's? Shed a lil more light...

 

yes heres the story, a few weeks ago, my ses light came on, i went to check the code, no activity bank 1 sensor 2. finialy got to swapin it out for the passenger side to see if the code would follow. went back to autozone to check the code, and it said no activity for both. its never ending, wish i had left the car stock. im at my end of my ropes, i have no money to fix the car, and everytime i think i start to get ahead, something else gets ****ed up.

 

You can clear the codes from the PCM simply by pulling the "PCM BAT" fuse for 30 seconds.... not need for any longer period of time. But if the problem is still there, the codes and the SES light will come back on. If the SES light is on, the problem is "active" and needs to be fixed to get rid of the light.

Is it possible a wiring problem burned out the first sim, and when you swapped them side to side you burned out the other one? A simple wiring problem would explain it.

 

its just one sim, i guess cause i switched them with out clearing the original code(no activity bank 1, sensor2) that code was read when i pulled them the last time. i just went to autozone, pulled the code, and only got 2 codes for the bank 2 sensor 2. cleared them and then drove till it came back on, same thing. so its in the sensor that was originaly on the drivers side.

 

Well, what are the code numbers?

 

p0160

 

You're on the right track with the O2 sensor. Specifically, that's the code for the passenger side after cat O2 sensor. I think Fred is on the right track, as wiring or a connector problem is most likely the cause.

 

nope its a bad o2 sim, it was originaly on the driver side, and throw a code, swaped it to the other side to make sure.

 

Here's the code definitions: http://www.troublecodes.net/OBD2/Pcodes.shtml

 

Problem is he's got two threads running on the same "sim" problem. In this one he claims he got codes for no activity on BOTH sides. In the other thread, he updates people and explains that he forgot to clear the codes before he switched the sensors, or he got two codes for the same sensor on ONE side, or some such.

That's the problems with scattergunning multiple posts on the same problem on multiple forums. Apparently he thinks we're stupid because we didn't know it was only a problem with one sensor, which we clearly would have known by reading his other thread on another forum.....

Next time I'll avoid his posts, because clearly we are both wasting out time trying to help him in this thread, when the problem was already solved in the other thread......

 

I didn't see the other thread.