Target AFR (resolved: 1.0OV firmware bug)
#1
Junior Member
Thread Starter
iTrader: (3)
Join Date: Aug 2005
Location: Gig Harbor, WA
Posts: 488
Total Cats: 3
Target AFR (resolved: 1.0OV firmware bug)
Could someone check the F11 screen and see if the target AFR is what you would expect? Mine is stuck at 25.5 and I thought it used to actually reflect the real target.
Last edited by TurboRoach; 06-08-2009 at 04:49 PM. Reason: resolved
#3
Junior Member
Thread Starter
iTrader: (3)
Join Date: Aug 2005
Location: Gig Harbor, WA
Posts: 488
Total Cats: 3
It doesn't seem to be going into closed loop. On the live gauge screen it reads the correct AFR. I checked all of the conditions for closed loop and they are all met, but it is still not going into it. It is doing closed loop idle but not fuel for some reason.
The only changes I've made since Friday when the car was running fine was to swap injectors.
None of my targets are actually 25.5. I just wanted to know if the F11 screen showed the real target AFR.
The only changes I've made since Friday when the car was running fine was to swap injectors.
None of my targets are actually 25.5. I just wanted to know if the F11 screen showed the real target AFR.
#5
Junior Member
Thread Starter
iTrader: (3)
Join Date: Aug 2005
Location: Gig Harbor, WA
Posts: 488
Total Cats: 3
The live gauge shows:
14.5 (open)
if it goes closed loop the open will switch to the target AFR, which for some reason mine won't do. I'm going to try rolling back the firmware and see what happens.
14.5 (open)
if it goes closed loop the open will switch to the target AFR, which for some reason mine won't do. I'm going to try rolling back the firmware and see what happens.
#7
Junior Member
Thread Starter
iTrader: (3)
Join Date: Aug 2005
Location: Gig Harbor, WA
Posts: 488
Total Cats: 3
I tried going back to version 1.0OB and things started to work correctly.
I then went to 1.0OV again, and things work as long as I don't use the Analog AEM UEGO sensor option, which is the only reason to run 1.0OV.
So, it looks like there is a bug in the firmware when using the AEM sensor I have. There is also that file name bug in the WARI software that showed up about the same time....
I then went to 1.0OV again, and things work as long as I don't use the Analog AEM UEGO sensor option, which is the only reason to run 1.0OV.
So, it looks like there is a bug in the firmware when using the AEM sensor I have. There is also that file name bug in the WARI software that showed up about the same time....
#9
Junior Member
Thread Starter
iTrader: (3)
Join Date: Aug 2005
Location: Gig Harbor, WA
Posts: 488
Total Cats: 3
Cool, that explains the 25.5 AFR target.
I still think there is a bug in the code. If I use the analog UEGO 0-5V it will go into closed loop, if whilst in closed loop, I switch to AEM UEGO 0-5V it will no longer go into closed loop. I waited a long time and checked all the conditions for closed loop and it still wasn't doing it. Switched back to UEGO 0-5V and it instantly went into closed loop. I was using the same physical sensor in both cases, just switching between analog options.
I still think there is a bug in the code. If I use the analog UEGO 0-5V it will go into closed loop, if whilst in closed loop, I switch to AEM UEGO 0-5V it will no longer go into closed loop. I waited a long time and checked all the conditions for closed loop and it still wasn't doing it. Switched back to UEGO 0-5V and it instantly went into closed loop. I was using the same physical sensor in both cases, just switching between analog options.
Thread
Thread Starter
Forum
Replies
Last Post
Motorsport-Electronics
ECUs and Tuning
0
09-05-2015 08:02 AM