[J x K]

Hey I need some help...

I can't seem to find the right 02 voltage for my car & catless downpipes. (My car is a full off-road race car of course ) I've tried and tested multiple 02 voltages.

Here's the run down, I received my procede pre-programmed with a default 02 modifier setting of 40%. However, later that night I turned it down to 25% after about 50 miles of the install of the procede because I assumed it needed to be lower. It was fine til about 150 miles later, and it then threw a code for the downpipes. Since then, I've been trying all kinds of different random 02 sim voltages, not in any particular order, ranging from 40%, 39%, 38%, 37%... all the way down to 15%.... I'm still going to try different ones, right after I type this... anyone care to help? I'm gonna try 29% through 26%, havent tested those yet...


For reference, my car has AR Design catless downpipes, and 05/09 build date; not sure what software, I assume around 32.xx.

Thanks so much,

J

[J x K]

Update:
I tried 29%-26%. no succes.

However I'm trying something new, I reput the 02 modifier at 100%, let it throw the downpipe code and started to adjust it accordingly. I tried 80%, 60%, and now I'm at 45%. The 45% seems to be working, since it has been 17 miles with no codes vs all the other %'s the codes would throw within 6 miles...

Will update accordingly... Anyone have any input?

[RigorMortis]

I have the same problem, tried almost every value, no success...

[J x K]

Hmmm, 52 miles on 45%.. let's see how she holds

[XPO186]

I suggest starting again at 50% and just drive the car for awhile. Check any invisible fault codes through the procede every few days and if you happen to get a code, drop the O2 modifier by 5% and start again. Be patient, because it may take some time and miles for the codes to come on.

This is the process I used to find the right setting for my car and after every time I changed the setting, it took at least 180-200 miles before the codes came back, so be patient.

[cn555ic]

Originally Posted by XPO186

I suggest starting again at 50% and just drive the car for awhile. Check any invisible fault codes through the procede every few days and if you happen to get a code, drop the O2 modifier by 5% and start again. Be patient, because it may take some time and miles for the codes to come on.

This is the process I used to find the right setting for my car and after every time I changed the setting, it took at least 180-200 miles before the codes came back, so be patient.

When you guys get these codes, does the SES light come on?

[J x K]

Yes, the ses light will come on once the test conditions are completed for the codes, which is usually the 2nd time after you drive your car after the code was thrown.

I see the codes via bt scanner before the test conditions even become complete... I delete the codes before the ses light comes on, and try different %'s.

Update:
I re-started from 100%. Code was thrown. Then tried 80%, 60%, 45%, 40%, in that order. Codes were thrown, now I'm trying 35%. I'm going to keep going down in 5% increments and see if I can nail it..

Anyone have better suggestions?

[Ferre86]

same tired all % , then back to 11-2 beta map with default settings , it works great for me no limp yet for long time.

[cn555ic]

Originally Posted by J x K

Yes, the ses light will come on once the test conditions are completed for the codes, which is usually the 2nd time after you drive your car after the code was thrown.

I see the codes via bt scanner before the test conditions even become complete... I delete the codes before the ses light comes on, and try different %'s.

Update:
I re-started from 100%. Code was thrown. Then tried 80%, 60%, 45%, 40%, in that order. Codes were thrown, now I'm trying 35%. I'm going to keep going down in 5% increments and see if I can nail it..

Anyone have better suggestions?

Wow its apparent that different programs makes the sensitivity more or less depending on the program version...What program is your car running?

[J x K]

Not sure, I'm pretty sure its 81 and 32.xx software.. Car is 05/09 build.

Wonder what shiv has to say about this? o.o

[J x K]

I'm on 11-2 default stage 3 map too

[OpenFlash]

I think you have been going about it a bit wrong. It's unlikely that you will be able to test more than a couple settings per day given the time it takes to trigger a catalyst conversion code.

Start off with 40% again. Drive it until you throw the cat conversion codes. If you throw them, clear the codes, drop the value by 5% and test again. And so on.

HOWEVER, if the value is too low, you will throw fuel mixture codes. If that is the case, you have to raise the value and find the "sweet spot" where no faults occur (cat conversion or fuel mixture). This is where you want to keep your o2 setting.

It is likely that during your series of setting reductions, you simply went from throwing cat conversion codes to fuel mixture codes. The right setting is there. You just need to take a little time to find it. That means checking/confirming the kind of code and making small changes.

Shiv

[Jeller]

I noticed it took about 25 +/- a couple miles worth of driving between throwing cat codes.

[OpenFlash]

Originally Posted by Jeller

I noticed it took about 25 +/- a couple miles worth of driving between throwing cat codes.

Exactly. Which is why unless you are going on a long road trip, it's hard to test more than a few settings day. If you are getting codes much quicker than that, then it's likely that your o2 sim is too strong which is triggering fuel mixture or o2 response codes.

Shiv

[J x K]

Originally Posted by shiv@vishnu

I think you have been going about it a bit wrong. It's unlikely that you will be able to test more than a couple settings per day given the time it takes to trigger a catalyst conversion code.

Start off with 40% again. Drive it until you throw the cat conversion codes. If you throw them, clear the codes, drop the value by 5% and test again. And so on.

HOWEVER, if the value is too low, you will throw fuel mixture codes. If that is the case, you have to raise the value and find the "sweet spot" where no faults occur (cat conversion or fuel mixture). This is where you want to keep your o2 setting.

It is likely that during your series of setting reductions, you simply went from throwing cat conversion codes to fuel mixture codes. The right setting is there. You just need to take a little time to find it. That means checking/confirming the kind of code and making small changes.

Shiv

Shiv, I started over & tested and went in this particular order..
100% > 80% > 60% > 45% > 40% > and I'm currently testing 35%.

After re-adjusting the 02 modifier settings, sometimes it takes as little as 6 miles for the codes to be thrown (Invisible codes shown through BT cable being tested bye DME still, not shown as SES on dash yet). I keep getting the 2c32 / 2c6a codes... Sometimes one or the other, sometimes both. Interesting to note - I tried 02 voltage at 15% and a code was thrown after only 1 mile, so I'm guessing that was too low.

The thought of a damaged 02 sensor came into mind, however it took 150+ miles or so for the codes to start appearing after I installed the procede..