You can see what’s implemented on the specific websites for each base map:
Edit:
The website is not yet fully updated (it will be updated when the non-beta version is released).
You can also check the base map description in the client software with the base map loader tool.
Hi there, I updated to this firmware from version 222 and the car took ages to start and the short term fuel trim was disabled due to “Blocked: No Lambda Assignment (-17)”. As soon as I went back to firmware 222, no short term trim issues and the engine fired up instantly.
Any idea what might be causing this? Have project files and logs if needed.
Lambda Assignment is needed so the ECU knows what cyclinders the O2 is used for. Open the ‘old’ file and look at the report for the upgrade. It will tell you what issues you’ll have from the upgrade.
Weird Iqnition overrun issue. Anyone can help what can cause this?
last burnout, overrun cause iqnition angle to 0. Why?
UPDATE
Overrun is disabled, but somehow when we have first time antilag on, overrun state go from 0 to 1, when we disable antilag using button, overrun state go to 2 and be there what ever we do with throttle. Again antilag make state 4 and release state to 1 until antilag disabled make it 2 and keep overrun on.
I see where overrun is active but could this be a case where you previously had activated overrun and then unchecked enable and forgot to make permanent? The base overrun angle is -5 but your only dropping to 0. Try setting the cut type to fuel and ign and see if it remains active after disabling it.
@123cdi we will analyse the problem and get back to you.
@FrogJam_Motorsport Have you identify the problem? Does the new version delete the assignment? Please provide the project from 222 version so we could look at it. Post it here or in PM.
