Adding load columns and RPM rows to maps
On the IX I'd completely delete the high octane 2,3 low octane 2,3 stuff from the ROM if it wasnt already. I cant remember if the lookup was just changed or it was removed
The 9694xxxx is the one that ran out of room, yes?
The 9694xxxx is the one that ran out of room, yes?
Aaron is correct about the only rom that has ran out of room. 96940011 was my orig. rom.
Last edited by laramie_05MR; Oct 1, 2009 at 12:04 PM.
That will work better based on what I am looking at right now on my lappy. Especially for SD cars that need resolution vs Kpa. The additional 5 rpm slots will allow good control all the way around and should run out to 10k pretty easy.
I will post up a pic when I get to work...
Really the hardest bit in all this is taking the existing maps and smoothing them across the new rpm/load points..
I am tempted to leave the maps blank and let u guys do that
Really the hardest bit in all this is taking the existing maps and smoothing them across the new rpm/load points..
I am tempted to leave the maps blank and let u guys do that
couldn't the low octane map be destroyed? I mean with all the other fault fallbacks if you can't keep your foot out of it and end up in low octane map you deserve to be punished.
Absolutely agreed on the notion of completely removing the concept of "octane" from the ECU; it's an important component of a street car configuration, as you'll find out the first time you get a bad tank of gas. (I'd argue it's about as silly as getting rid of fuel trims, but there's some full-time open-loop guys who'd take issue with me.
)
But I have to wonder if we couldn't do something algorithmic rather than entire dedicated maps for the low-octane configuration. I'm thinking something like a transformation of the octane calculation into an AFR and timing modifier, that decreases timing/increases AFR up to some adjustment maximum (ie. when applying the adjustment value, never exceed X AFR, never go lower than Y degrees of timing). Think an "octane" trim, much like fuel trims, that is applied to the high-octane values in place of referencing a low-octane map. As the octane value reduces, the adjustment becomes more dramatic (perhaps in a configurable, linear, manner)?
The main advantage I could see here would be that it takes the low-octane tuning out of the picture, since most people don't seem to ever touch those maps (and in some cases, they probably should; I've seen rescaled timing and fuel axes, with stock low-octane map contents, either through laziness or incompetence).
Anyway, just thinking out loud.
)But I have to wonder if we couldn't do something algorithmic rather than entire dedicated maps for the low-octane configuration. I'm thinking something like a transformation of the octane calculation into an AFR and timing modifier, that decreases timing/increases AFR up to some adjustment maximum (ie. when applying the adjustment value, never exceed X AFR, never go lower than Y degrees of timing). Think an "octane" trim, much like fuel trims, that is applied to the high-octane values in place of referencing a low-octane map. As the octane value reduces, the adjustment becomes more dramatic (perhaps in a configurable, linear, manner)?
The main advantage I could see here would be that it takes the low-octane tuning out of the picture, since most people don't seem to ever touch those maps (and in some cases, they probably should; I've seen rescaled timing and fuel axes, with stock low-octane map contents, either through laziness or incompetence).
Anyway, just thinking out loud.
For tephra donations:
http://dsm-ezine.com/tephra_donation.html
http://dsm-ezine.com/tephra_donation.html







