Trouble Codes

So I've been doing some modding to my GTP and I now have some reoccuring trouble codes.

After I installed the 2.5 downpipe I noticed I got trouble code P1133
"DTC P1133 HO2S Insufficient Switching Bank 1 Sensor 1"

I believe that is my manifold O2 sensor, right? Could this have happened due to the change of downpipe, or due to pure coincidence did my O2 sensor crap itself immediately after I changed the pipe? What's the best way to check the output of that O2 sensor, I have a Aeroforce Scan Gauge if I can do it remotely.


After I installed the PCM I got 2 codes,
"DTC P0650 Malfunction Indicator Lamp (MIL) Control Circuit"
I don't know if this could be because I have my ABS and TCS OFF lights removed from the dash and DIC? It never did that before and I've had those lights removed for a while (I mean physically taken out)

"DTC P1670 Driver 4"
I'm stumped with that one....PCM related?


I know someone locally with HP Tuners...which ones could/should I delete?

Thanks!

I found out how to check the MV on the gauge...they seem to be in order. I pulled the battery cable for a couple mins and drove it a bit...it's not back YET. I'll keep an eye on that one. As for the other two codes, I still have no idea, and I don't think the MIL has anything to do with my pulled bulbs now to think of it.

I swapped in the factory PCM, went for a drive and all the codes went away...I think Intense sent me a bad PCM...

We'll see about that O2 sensor I guess...maybe it's adapting to the downpipe? I guess I'll see if it trips the code again.

Based on the DTCs after installation it looks like the Intense PCM definitely has hardware issues. Thats why it is a good idea to keep the original PCM module as a backup.

02 sensors really don't need to adapt to anything. They either work or don't. If you are still getting the P1133 DTC or if its pop back up then best to replace it. The P1133 DTC means the 02 sensor is lazy. Insufficient lean to rich (L/R) or rich to lean (R/L) switching.

Thanks for the input.

I have a good price on a Delco o2 sensor, I might pick it up just in case. If it threw a code once, I feel it'll throw it again eventually, and for the price I was quoted it won't be a huge loss if I don't need it.

Yeah something's messed on the PCM, although it's strange that the functions of the code affected areas did not seem to be affected...the CEL still worked with the MIL code and I read Driver 4 controls A/C and fan controls, and everything worked....

I contacted Intense inquiring for an exchange...we'll see how quickly they get to it. Other than the codes the PCM worked ok and since I switched back to the stock PCM, everything feels so sloppy and granny-like...lol. Programming definately makes everything more crisp.

The problem with re-programmed PCMs from any of the vendors is you never know what you are going to get. Like a box of chocolates. :lol:

I really don't think they are thoroughly tested before the re-programming job. If you look at the condition of these PCM modules you get from Intense, DHP or ZZP some look really sad. All dented and scratched up. I've seen corrosion on them. The best results are obtained by sending in your original PCM to get burned otherwise you are stuck with what someone else sent in to include any inherent problems. The only real way to test ODM circuits is with a GM Tech 2 scan tool and technically should be done before re-programming a PCM module but I doubt the companies are doing that.

The P1670 DTC is related to an internal issue with the ODM modules (output driver) but very uncommon to get on modern odb-ii cars. Used to be real common with the odb-i. Those were the ole Quad Driver failures which is similar. ODM 4 is generated when the PCM has determined that the voltage or current in the feedback circuit may cause damage to the PCM. Each ODM circuit has an internal feedback circuit back to the PCM microprocessor. Just an internal PCM failure and nothing you can do about it other than getting a replacement PCM.