those with frequent o2/heater codes
those with frequent o2/heater codes Just wanted to inform people of this:
For a very long while i have always been getting slow switching and heater performance codes for both o2 sensors(front) and they are both relativly new. Well i noticed they mainly are thrown when in traffic and i am at lower rpms for a while.
Welllll i got a newer 5 wire maf(screened) to replace my descreened stocker...
After some programing, not only do i get the throttle response back off idle, i havnt thrown a code for an o2 since. And this was 2 months ago on a dailly driver....
Soooo moral of the story is if your having o2 codes, a descreened maf may be the culprit.... im guessing cause the inaccurate readings with low airflow causing the afr to go rich and make exhaust temps colder.
For a very long while i have always been getting slow switching and heater performance codes for both o2 sensors(front) and they are both relativly new. Well i noticed they mainly are thrown when in traffic and i am at lower rpms for a while.
Welllll i got a newer 5 wire maf(screened) to replace my descreened stocker...
After some programing, not only do i get the throttle response back off idle, i havnt thrown a code for an o2 since. And this was 2 months ago on a dailly driver....
Soooo moral of the story is if your having o2 codes, a descreened maf may be the culprit.... im guessing cause the inaccurate readings with low airflow causing the afr to go rich and make exhaust temps colder.
Last edited by tc3; Oct 10, 2007 at 06:33 AM.
yea something like that, if you search around there should be a company that makes the new model(5 wire) maf compatable with the ls1 tune so you dont have to waist money on updating your maf with efilive or hptuners or w/e
P0155 is a heater performace code. It is an emessions related and will always take 2 consecutive trips to trigger the s.e.s light. If conditions meet for it to trip once it will throw a code but not s.e.s light...
