Service Engine Soon Light

[G-Mann]

Tried to start my car (cold) today and it would fire and sound like it wanted to start but did not. After about 5-6 times I pressed down on the gas pedal a bit, then hit the key and the car started but ran at a fast idle and ran very rough. Like it was missing. Ran the car for about 6 miles until the car got up to operating temperatures and everything smoothed out and the car ran fine. However the ( Service Engine Soon) light remained on. Stopped to see my Mechanic and he drove it and said that it seemed fine to him but recommended to hook it up to the diagnostics computer to find the code that triggered the light to remain on. The results were: PO-130 TPS sensor. He then checked the sensor and said the thing was good and that the throttle body looked very clean. Does anyone know that when I tried starting it while pressing down on the gas pedal was the culprit in having the thing run rough and triggering the light to come on?

[maxwedge]

I have po130 as an o2 sensor code?

[GVAR]

PO130 O2 Sensor Circuit Malfunction (Bank 1 Sensor 1) This is the O2 Sensor before the CAT. It is easy to change but you need a special socket. Mine went bad and I wound up replacing both O2 sensors within a month of eachother. Since I did change them my gas millage is awsome now. Hope that helps.

[Carwhiz]

Whoa, hold up here now....we can't tell what the code is unless we know the car. Codes are different from car to car. For example a PO133 may be an O2 code for a monte, but it may be an TPS code for a Granp Prix...I know from experience. By the discription of the problem, it sounds like the tps is out of wack. You can check the part by using an ohm meter. Your O2 sensors don't sound to be a problem because the sensors are in open loop during startup. O2 sensors do not begin "working" until the car is operating temperatures.

[maxwedge]

p0133 or p0130 is standard across the board for o2 sensor issues, just double checked on the MT2500 Snap On scanner trouble shooter function, for that car.. That code could have been there as a result of a seperate problem not the start up issue described.