Maf options?

[coffeeandcigars]

Thanks again for shedding light!

No, the fuel table values are scaled Lambda values. Many maps have a Load axis (descriptor 0x40), with (values x 0.05) representing the theoretical injector time in milliseconds. For the fuel maps, the table values are a target Lambda * 128, or rather Lambda = Val / 128. AFR = (14.7*128)/Val if you prefer. So, a value of 128 represents no change to the Load value as it is a Lambda of 1.0, and the maps are all used as corrections to the Load value that is initially computed from sensor inputs. Just to be clear, the target Lambda values are not at all related to O2 sensor feedback or anything...they are the "target" of the manual correction that the tuner enters.

Thanks for clarifiying this! In the tunerpro xdf this was implemented for one map. But i discarded it as nonsense

Axis values are free to change. You can even change the length of the axis if you want, although if there is another map that starts at the next byte address after it then you would need to move ALL of the hex data after it and update all of the addresses in the map index. Alternatively (preferably) you could just move the map to a different address where there is a lot of free space (lots of 0xFF values) and update the map index for just that one. In my opinion the 1x16 WOT maps are fine, but some people have increased them to 1x20 and moved them to an address with lots of unused space. Do keep in mind that the larger the table gets, the slower the Motronic is able to read them since it has to traverse the length of the axis starting at the end. FYI at higher RPM, the Motronic cannot access the tables as fast as at lower RPMs since it has many fewer free instruction cycles, so keeping the WOT maps smaller is preferable.

Extending the axis datapoints is a bit to advanced for me ;)
I went with rearranging the existing 16 to suit the higher limiter and spaced the gaps evenly. I also thought that i wont need a datapooint at 800 rpm for a WOT map and shifted its beginning to 1000 rpm.
Heres how its working, V7 is what i have as my new base for now and v8+v9 were to see if this has limitations in fuel delivery (They were just scaled with a factor across):


V8 responded pretty much as expected, getting a bit richer after 6000
V9 showed that before 4000 and after 5700 its not responding linear to the amount added in the map
This is the fuel map for V9 (left: scaled to AFR; right: pure bin values):

I have not tried to flatten out the curve for V9 yet...so not shure if theres a limit or just scaling linear hasnt worked that well!

[coffeeandcigars]

Did another test to see if theres a limit in the areas it didn respond as expected and up top its at some limit:

When checking this (Fuel Injector Clinic calculator) it seems possible that with the current enrichtment the limit of the injector duty-cylce has been reached:

You changed injectors/fuel pressure for the stroker right?