Which load columns would you recommend removing when wanting to add more?

 

On the IX EGR ign map, there is only advance from 30-60 load and from 1500-2500RPM.

Do you know if the 8's have the same map? as I dont see the EGR ign map on my ROM (im using the newest ecuflash)

Also do you know if the 8 also has the low coolant ign maps?

 

For an Evo 9:

fuel - The 20 and 30 load columns could easily be removed. The 70 could also be removed.

timing - If both the EGR ignition advance routine and the low coolant temp timing trim routine are both disabled, then the 10, 20, 30, and 40 load columns could be removed.

 

Are these tables defined for 90550001 in the latest ECU Flash? I am using an old version of ECU Flash. I rescaled loads on a converted car that uses a small turbo (max load columns now is 220) and ended up with big problems with cold driveability.

 

If we remove a table won't the value expressed remain the same? Like if I disable a periphery and then remove the table from my rom. It will have made the change I can just no longer see it. Would this work the same for fuel tables? Could a specific load or rpm be tuned and then the scaling changed to tune others, while the original remains just is not viewed?

 

Oooh, very good question...I like where your thinking is headed. I would think that is possible, except if I am interpreting the ecu correctly, that the scaling or area of memory that thes maps take up in the rom, are only defined by that size. So weather you scale it as an 80, then change it to 70, and adjust again, i think it will just shift that as the new scaling or reference point. I am not actually sure there is a full 0 to infinite array defined that will just keep going and addressing memory as needed if our cars could go there. I could be way off, but am wanting to be able to adjust those areas and actually have them be adjusted.

There is another thread about adding 5 rpm address and 10 load addresses or visa versa, something like that. So that is where i am gathering that you actually have to engineer a little code on this one that relocates data stored, and actually allows that object or process access to address the more memory it needs to hold the data...Tephra gives it more poetic justice in that thread.

EDIT: On the topic of scaling for the short term, I am missing the 10 and 30 load...? I have the load/rpm colums where the idle should be spaned equal so that the colums should scale the same? If I wanted to rescale them, is the answer in my explanation above? Or am I way off?

 

I'm having a little trouble deciphering your question...

A little trouble here.

When you rescale something you change the reference point that the ECU is using to interpolate. IE: if in a fuel table you have a 10 and 20 load column and change the 20 to a 50 the ECU will try to interpolate in that (10-50) range when you are between those load columns.

I'm almost curious what would happen if you tried to do something like 10 50 20 30 70... but not curious enough to try.

 

Sorry, I realize I wasn't clear. When I had help with my base map for my car, the stock scalings wer 10, 20, 30, rogressivly to 260 I believe. The guy that helped me with the base map scaled them so that I am now only seeing the 0, 20, 40, 50, 60 to 300.

I am having some off idle issues now that it is getting colder, and I was utilizing the comun knowledge that the car idles in the 30 load column. I can't see that column. I have the 20-40 load columns set at the same number, thinking that the two cells set equally would suggest that the invisible 30 load is set the same. If this is wrong, how do I rescale for better resolution so that I can tweek this off ifle searching?

I have the IDLE Timing table adjusted to specs. Since the loss of my roms, and the rebuild of the 94170015.xml over in the other thread, my low and mid fuel trims say drop approx -4.xxx. So I didnt want to rescale the maf since people suggest that this practice of maf smoothing or scaling is not the best. So from there, I am stuck with no view of the 30 load as maybe the alternate or best way to fix the idle searching or unstableness.

So how does one go about rescaling the to view the 10 and 30 load columns? Should I switch those to the 70, and 90 load for removing?

I didnt just want to rescale if it was looking or overlapping reference points in memory.

Sorry about the long read, and thanks for the help.

 

The rom only has a 19 by 19 grid to store the information in, like timing. You only get those 361 data points, and the ecu interpolates between them in a linear manner.

 

More of an exponential manner rather than linear, but i still agree with that this is all the ecu only has these data points to use.