I just copied and pasted a couple of fuel and timing maps from ECUFlash into MS Excel to compare them, and when I tried to conditional format the cells I realised that some of the numbers in the fuel maps run to 4 decimals, even after they've been adjusted in ECUFlash.

Has anyone else noticed this, and does anyone know the significance?

The timing maps are all whole numbers (no decimals), in case anyone is interested.

 

If you have a look at the scalings for AFR, you'll see that ECUflash only displays to one decimal place. The formula to change from the hex word in the ROM to something approximation an AFR for display in ECUflash will often give those sort of results. If you format the cells in Excel to show only one decimal place then you'll see the same thing as ECUflash.

MB

 

I realised about the display in ECUFlash being rounded, but just thought it was strange that ECUFlash would only allow you to change AFR values in .1 of an AFR increments when presumably if you imported your fuel tables from Excel you could tune in .0001 of an AFR.

Surely that kind of accuracy, or at least being able to tune in hundredths of an AFR (rather than going mad and tuning in ten thousandths), would be useful in some applications?

 

Approx seven hundredths on a full load mixture is the real limit (look at the forumla to see why). Ecuflash is taking 3 real steps for every 2 incs/decs at 11.5:1 AFR. You can type manually though.

I can guarantee that it will not stop your Evo running any race it was going to win otherwise.

Too many decimal places on the display encourages mistakes.

If you display the fuel map in hex you can work that way if you prefer.