My stock KFMIRL map tops at around 180%, which means the maximum possible boost is around 1.1bar.
In order to raise the boost higher I have to increase the higher end of KFMIRL table.

While the original KFMIOP axis goes up to 160%, what happens if KFMIRL requests higher load than 160%?
I have already rescaled and recalculated both the KFMIOP axis and data to match the new KFMIRL.
Since KFZWOP(/2) share the x-axis with KFMIOP its values need to be scaled too.

However there are several other axises indicating load % (e.g in KFZW/2, KFKHFM, KFLF, KFLBTS, etc) with percentages varying from 150% to 185%. How are the different load axises connected and what happens if some maps are rescaled / calculated while the other maps are left alone?

Thanks
 

I´ve seen some "pro-tuned" files which have KFMIRL raised, yet the KFMIOP load axis left alone (as well as the other load indicating axises). The KFMIOP table values (axis from KFMIRL and ultimately from KFPED?) are recalculated correctly thou. The boost is also at the levels it should be.

Is it possible that the ECU extrapolates the new values when the upper limit of some load axis is exceeded, or simply use the last known value pointed by the highest available load percent in the specific map. E.G if KFMIRL requests 191% at 100% (PED), LDRXN has limited the load to 180%, and the KFZW load axis goes only up to 150%. Then the ignition angle would be set to value pointed by KFZW map @ 150% (Y) and the RPM (X)?

Since the KFMIOP should be limiting the load I recon the ECU indeed does extrapolate.

I checked some BAM/BFV maps and they have all of the load axises set higher than the maximum load allowed by LDRXN.
So maybe I´ll just borrow the axises from a higher end model files and recalculate the table values.

I remember that my "pro" tuner did something like raising kfmirl and kfmiop and kfzwop... and also set lamfa > 1 very funny tune it was... although it worked but I suspect that load model was miscalculating torque..

Excellent summary. Thanks.

BTW i have spreadsheets of a few of the various map packs floating around that are ripe for datamining....

http://nyet.org/cars/files/

check out  the csvs...

they're missing axis locations, but I can add them easily.

Yup. This is why starting with the k-box is probably a good idea...

The two biggest limitations are load (which is solved in the kbox) and MAP (which can't be solved w/o rewriting the code, or underscaling a larger MAP)