question on custom os 0202005

On the stock F-body spark multiplier map you can see it will work fine above 1,600 RPM, there is no need to set the entire map to 1.0, you only need to do this in an area you want the timing pulled and if the cell is currently 0.
I suppose most people will just test it at idle, which of course won't work on that map.

Quote:

---

Originally Posted by GAMEOVER

Thanks Joe....I got another question(nothing to do with nitrous) if I want COS5 to pull timing or act like a stock High Octane & Low Octane tables(in case of bad petro) do I set A0001 to 50% and A0002 to 50%? Or?

---

The COS slides between HO and LO tables just like a stock OS (even when MAF is failed)... set A0000 to Disable and A0002 to 100%.

I thought you had to set it at 50% so it will blend between hi and low.
Joe quik question.I'm doing a c6z06 ls7 in a gto and has long tubes.having a hard time getting o2s hot at idle.I changed the switch rate.can I tell the heaters to be on all the time.I think I read somewhere someone did this and it worked good.I've turned on the heaters all the time and it really helped the o2 from making such big swings while switching.

Quote:

---

Originally Posted by AllOutPerformance

I thought you had to set it at 50% so it will blend between hi and low.
Joe quik question.I'm doing a c6z06 ls7 in a gto and has long tubes.having a hard time getting o2s hot at idle.I changed the switch rate.can I tell the heaters to be on all the time.I think I read somewhere someone did this and it worked good.I've turned on the heaters all the time and it really helped the o2 from making such big swings while switching.

---

A0002 set to 100% will force the pcm to use the high octane table as the default until knock is detected. If knock is present it will still learn down (watch the ASPARK pid).
Setting to 50% will have a blended value between the HIGH/LOW table as the default. Not sure if it will learn up as I always set to 100%

Thanks Joecar, Ross & 5.7ute...I just realized that I've been doing the COS5 wrong for the past 6 months or so... I'm glad I followed this thread...:D