[xr4x4ti]

I am starting to turn up the wick on my car and I am finally running into some of the limitations of the A9L. First, I am exceeding the 2400Kg/hr flow rate that it will measure and I want to run up to 20 psi boost, so of course I am going way past the 200% load limit.

Ok, no big deal, I just perform the scaling steps outlined on Decipha's excellent write up http://info.efidynotuning.com/scaling.htm.

But, what bugs me about that is then output of the data logs is really no longer correct and most annoying to me is the load columns in the fuel and spark tables is now really not the real load and you must keep track of that in your head.

This got me thinking, the DEF files have conversion factors in place for each variable to convert them from the actual number in the tune to what to the more practical number that is displayed on the screen. I thought, there is no reason that these numbers couldn't be manipulated such that what is displayed on screen or in the datalogs is still the correct value and not the scaled value. I started playing around with the latest rev 98 of the GUFB. xls file to see if this would work and I instantly hit a wall. There seems to be something hard coded into BE that will not let you set a value of load that is greater then 200 for FN071 no matter what the limit is in the DEF file. I figured I would ask the experts before going any further.

In my dream world I could see creating two new "Z" scalers or hacks that would be written to an empty spot in the tune. One would represent Airflow scaling factor and the other would represent the load scaler. This would by default be 1, but if increased to say 2, would change the appropriate factors in the tune to keep the EEC happy, but the values in BE and in the datalogs would still be correct since all of the math would be done in the background. The load scaler would then also allow loads greater then 200 to be displayed on the tables. Say the factor was 2, then the max load allowed would be 400.

Thoughts and Ideas?

[decipha]

I thought about the same exact thing myself, it would require the program to be reworked to do it other than that it wouldn't be an issue

[xr4x4ti]

Ok, I figured out what was giving me troubles with BE (with Clint's help). BE is NOT going to be an obstacle to do this idea on a one-off basis, which is what I am going to try and do and see what happens. What I mean by a one-off basis is that I will put in a couple of cells in a custom DEF file that are my scaling factors and then reference them in all of the appropriate cells to make the load,MAF, injector slopes, etc all read the correct numbers. These scaling factors will not be stored in the BIN. The problem with this is that if you reed an old BIN file things will look a bit funny.

More details to follow.

[decipha]

well yea, in order for it to be done any not look goofy the software would have to be able to recognize it

you simply take a section of null filler and use it as a VID block, thats what i do on all my fox tunes so I can look in the binary to see the exact setup the tune was written for, makes it much easier for me than having to dig up vehicle info sheets and what not