[ehoffman]

Today I just updated to the latest JB4 firmware. Went for a drive and a few times over about 4k rpm the JB4 kicked down from Map 5 to 4. The app says the Safety reason was that the AFR was lean, and then threw some codes:
2C7F
2C7E
2C2B.

These all seem to be Lamda related...
I'm running FBO on an E92 335i with catless DPs.

I have logs around when this occurred, but wasn't actually logging when the Map bumped down to 4.
I'm afraid to go to Map 5 again and try to 'catch' the issue in a log because I'm not sure what the issue is...

Thoughts?

[RSL]

They change stuff all the time on firmware updates and if something changed in the car pre/post flash, you need to start digging for what it was.

1) Check the release notes for the firmware see what changed.
2) Make sure the interface you're using works with the firmware you've updated to. Generally best to always make sure you have the latest interface whenever you update to the latest firmware.
3) Check *all* the interface settings after any interface/firmware update.
4) If you use JB4 mobile too, always confirm your dash menu options haven't changed after the app updates, particularly menu 4. I've seen it move to 4/4 and stay there after app updates. Always make sure you're using the latest JB4 app with the latest firmware too, just like the interface.

[ehoffman]

Originally Posted by RSL

They change stuff all the time on firmware updates and if something changed in the car pre/post flash, you need to start digging for what it was.

1) Check the release notes for the firmware see what changed.
2) Make sure the interface you're using works with the firmware you've updated to. Generally best to always make sure you have the latest interface whenever you update to the latest firmware.
3) Check *all* the interface settings after any interface/firmware update.
4) If you use JB4 mobile too, always confirm your dash menu options haven't changed after the app updates, particularly menu 4. I've seen it move to 4/4 and stay there after app updates. Always make sure you're using the latest JB4 app with the latest firmware too, just like the interface.

Thanks for the info. I do have the latest jb4 iOS app with the Rev3 Bluetooth kit. I was 2-3 firmware updates behind, so not sure if it's a complete coincidence, or maybe the new firmware just takes time to see my setup? I'll try clearing the codes and see if they pop up again. Didn't see the auto clearing setting in the app, but either way not sure I want to do that if it actually indicates an issue.
The codes seem to be related to fuel ratio or O2 sensors, so perhaps related to the AFR lean safety map downgrade

Additionally, I'm not sure what AFR represents 'lean', but appears to range from 14 - 20

[RSL]

I suppose it's possible there were O2 failures at the same time, but seems like one heck of a coincidence. Firmware will not take time to learn anything. I'm not sure what all has changed recently, but I know they are making changes to get CARB approval in on it and at least one of the changes was to remove some auto-clear codes/functionality on US cars. It's possible you've had codes and no light, but kicking to map 4 would indicate there's an actual issue either with setting/tune or hardware wise.

IIRC, lean safety is higher than 14:1 for more than 1 second, but not clear on the RPM/boost range it's active in. You might start by clearing codes and resetting lambda/AFR adaptations, then do a short test on map 0 or map 1. I'd definitely go through all the settings in JB4 app and the interface manually either way.

You might post on Terry's site in the help/log section if you haven't already, definitely more geared towards JB4 than here.

[ehoffman]

Originally Posted by RSL

I suppose it's possible there were O2 failures at the same time, but seems like one heck of a coincidence. Firmware will not take time to learn anything. I'm not sure what all has changed recently, but I know they are making changes to get CARB approval in on it and at least one of the changes was to remove some auto-clear codes/functionality on US cars. It's possible you've had codes and no light, but kicking to map 4 would indicate there's an actual issue either with setting/tune or hardware wise.

IIRC, lean safety is higher than 14:1 for more than 1 second, but not clear on the RPM/boost range it's active in. You might start by clearing codes and resetting lambda/AFR adaptations, then do a short test on map 0 or map 1. I'd definitely go through all the settings in JB4 app and the interface manually either way.

You might post on Terry's site in the help/log section if you haven't already, definitely more geared towards JB4 than here.

I've posted on N54Tech as well...cleared the codes and did a clean log that captured the bump down to Map4.

Based on the research I've done I think I need to reset the O2 and Lamda adaptations...can I not do that in the app? Don't see anything that obviously indicates how to do that

[RSL]

Originally Posted by ehoffman

I've posted on N54Tech as well...cleared the codes and did a clean log that captured the bump down to Map4.

Based on the research I've done I think I need to reset the O2 and Lamda adaptations...can I not do that in the app? Don't see anything that obviously indicates how to do that

I think there's a dash menu that does it, otherwise, INPA or MHD will. I really don't remember if the app has resets or not.

[BMWhoarder]

i had the same issue after updating. Bank 2 AFR was way off bank1 (lean). Menu 1-7 corrected this

[mike@x-ph.com]

I would check with BMS direct regarding this issue

[V8bait]

I've had some issues recently with the new virtual ethanol firmware, it's like the cars are running at lower reported load or something. Causes afr, timing, shifting oddities on a few cars. Haven't looked into the reason yet, the two or three cars I saw it with just went back to previous firmware.

[ehoffman]

Originally Posted by mike@x-ph.com

I would check with BMS direct regarding this issue

I did talk to Terry...turns out I loaded the newest firmware on a G4 chip (just purchased my second 335i) and it's not compatible. I'm curious why it even allowed me to load the firmware at all, but I've since ordered the G5 upgrade chip