Load
http://users.wpi.edu/~ktarry/dsmtech/dsmromedit.html
oh yeah I take for granted that people know bits and bytes 
1byte = 8bits = 0->255 decimal
because load wants fractions of a decimal those 255 are broken into fractions. 5/8ths to be exact.
i.e each 1 decimal = 0.625 Load
Load = 0->159 3/8ths (159.375)
now we want to know a lot more LOAD than that. so we need 2 bytes.
2bytes = 16bits = 0->65536 at 5/8ths resolution, will give us LOAD as at 0->40960
which is plenty large enough for any Turbo vehicle
lol
Once I have released EvoScan 0.98 with easy Power graphing and Easy Alarms, I'll add a facility to patch Evo7/8 ROMS to output 2 byte LOAD.

1byte = 8bits = 0->255 decimal
because load wants fractions of a decimal those 255 are broken into fractions. 5/8ths to be exact.
i.e each 1 decimal = 0.625 Load
Load = 0->159 3/8ths (159.375)
now we want to know a lot more LOAD than that. so we need 2 bytes.
2bytes = 16bits = 0->65536 at 5/8ths resolution, will give us LOAD as at 0->40960
which is plenty large enough for any Turbo vehicle
lolOnce I have released EvoScan 0.98 with easy Power graphing and Easy Alarms, I'll add a facility to patch Evo7/8 ROMS to output 2 byte LOAD.
I'm still uncertain as to which parameters the ECU is reading and the calculation - I'll have to read the thread conversations between JCSBanks, Bez, and Malibu but the reading hurts like strenuous exercise.
I do see however calculated load follow the same shape (shape of line only) of plotted data as the actual IPW, just can't figure where the MAFhz falls in.
I need to research those read's to find if the logged IPW ms is a reading taken by ECU or just a commanded value sent out to the injectors. IPW corresponds to boost closely
Thread
Thread Starter
Forum
Replies
Last Post



