Converting Datalogged load to Scaled Load (Tp)

[J30_VG33ET]

If you'd like to convert the load logged in the CSV file by NIStune to the scale on the tables, divide by 256.

Example:
14325 / 256 = Tp of 56

[Matt]

the big guage will show this inside [] square backets but i will add it to the other displays also so it makes more sense

[J30_VG33ET]

I noticed that you added this to the log file. Could this be a separate column so the data can be sorted (easily)? It's kinda a pain to manually strip the [] from the Tp values.

Maybe call it TP (MSB), like MAF (LHS).

[UNISA JECS]

I noticed that you added this to the log file. Could this be a separate column so the data can be sorted (easily)? It's kinda a pain to manually strip the [] from the Tp values.

Maybe call it TP (MSB), like MAF (LHS).

I actually had the same question for sorting purposes only.

[Matt]

it could be added as a separate consult register instead, which may be better

[JasonKemmerer]

Since we're on the topic of calculating TP, what is the equation to do this?
I tried the equation on the Nistune Mapping Guide:
Theoretical Pulse width (TP) = MAF Lookup * Injector multiplier

So for example we get a value for MAF Lookup or VQ of 14372 (3.2v for a Z32 MAF). Multiplied by 288 (again Z32 370cc INJ). We get 4139136! So even if we divide it by 256 the # is still ridiculously high.

The other equation I have that seems to work but not sure its 100% is this:
TP=(VQ*K Value/CAS Value)/ # of cylinders.
Where CAS=RPM/50x256

any thoughts?

[Matt]

the first is just a generalisation in how things

the second is more accurate description. the true description is dependent on ECU type and is described in the appropriate patent description for the specific ECU model in question

For example the zemulator used a theoretical forumula derived from MAF voltage to work out its trace but that doesnt work the same for all types of ECUs due to variation in formula