When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
TerminatorX has the afr=9.55 for 20 seconds issue. Can I force openloop for 20 secs?
Running the terminatorx on my LS and it runs great expect I have the common issue where the AFR reads 9.55 for the first 20 or so seconds of startup and the ECU start tries to correct the false 9.55 reading resulting in a struggle to stay idling until about 20 seconds pass and the o2 sensor starts reading proper.
I'm gonna order a new official Holley o2 sensor on payday but until then, I would like to use an advanced table or something to force open loop mode for the first 20 seconds after startup. I tried making one but it didn't work. Checked the "disable CL while active" box, set it to activate when "time" was above 2 seconds and deactivate when time was above 20 seconds but when I try it nothing changes. It still goes closed loop after 5 seconds. I must be doing the advanced table wrong because I've seen posts here where people have done it.
This what I was doing when I had several terminators come through with O2 heater issues. I had any lately with the issue. You may have to adjust the seconds for you application but you get the idea. For this to work properly your fuel table startup fueling must be dialed in correctly.
Awesome, thanks, I'll give this a try! Question though, does this stay active permanently or does it shut off after 30 seconds at the end of the x axis?
It will stay active for as long as you tell it to... but the way he showed it will stay active for 30 seconds after 400rpm (each start) tapering off at the end to gradually introduce any corrections that may be needed. The reason for the after 400 rpm is so if you sit with key on for 20 secs before you start it will only be active for 10 more seconds and still be in your window of error
I don't know how but I've never run into this issue before on the Term X. I'm wondering if this is an older firmware issue or if it still exists in the latest versions?
I don't know how but I've never run into this issue before on the Term X. I'm wondering if this is an older firmware issue or if it still exists in the latest versions?
Some of the older ones have O2 heater circuit issues, not related to firmware.