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.

It has to be close to target AFR.

Are you sure:
a) you are in closed loop
b) the closed loop PD settings aren't changed ( to really slow for example)

don't you read knock? If 25.5 is a correct reading you are running realllllly lean.

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.

Yes it does show the real AFR.
Strange to here the live gauges is reading something else????

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.

You have watertemp?
If you do I dont have a clue. What you wroth is possibly the best option to go back in firmware.

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 checked mine while playing with the transient throttle settings. Cold start mine read 25.5 and ~10minutes later of idling it read 14.4.

According to the manual"

"The target AFR. If the ECU is currently in open loop mode (due to a
setting or a condition), this will not give a reading."

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.