greenmonster wrote on 01/26/11 at 23:03:12:I don`t quite get this, do you mean that f e editing breaks in f e Wordpad will ruin the map?
But of course! If you change the breakpoints only, the map will not match its intended breakpoints.
Let's say you have this part of the map (and that these values are very good):
RPM ... 4000 5000 6000 7000 ...
InjDur14 ... 10000 11000 12000 13000 ...
Now, say you decide you can ditch the 6000 column because it will interpolate just fine, but would benefit from a new one at 4500 because you happen to know things vary more at that range. If you just edit the breakpoints in WordPad:
RPM ... 4000 4500 5000 7000 ...
InjDur14 ... 10000 11000 12000 13000 ... <-- unchanged
You end up with a pw of 12000 instead of 11000 at 5000 rpm, and 12500 (runtime interpolated) instead of 12000 at 6000 rpm. If the map was good before, it is ruined.
When you use ECUController, it will transpose the affected portions of the map, so the net result at any given rpm and throttle is unchanged - but hopefully with a better foundation for future tweaks:
RPM ... 4000 4500 5000 7000 ...
InjDur14 ... 10000 10500 11000 13000 ... <-- transposed
The pulsewidth at 5000 rpm is unchanged, as is the (runtime interpolated) pw for 6000 rpm. For the new column of 4500 rpm, a new value is interpolated from the surrounding cells. At this point, the map should virtually perform the same as the original. But future tweaks or AutoTune could later tune this newly inserted value to, say, 10700 while the original map would always use 10500 from runtime interpolation between cells.