Interpreting log data

[david jenkins]

OK - managed to get out for a good blast this morning, with the laptop up and running. Collected a few logs and now I need to interpret the results. I'm running V3.0.0 with MAP.

Some of the data columns are obvious:

Timestamp: fair enough.
RPM: again, no problem
Load: that's the MAP readings
Advance: what MJ's telling the EDIS
RPM_Accel: no idea.
Load_Accel: no idea.
Mark interval: when I hit the space bar!

So the log gives me max & min MAP readings, which is very useful for setting up the MJ load table.

I have absolutely no idea on how to interpret RPM_Accel and Load_Accel - any clues, folks?

rgds,
David

[brentp]

For RPM it is RPM / sec- for load, it depends on your configuration. For MAP sensor it is KPA/sec, for TPS it is TPS%/sec.

There is no smoothing or averaging, so the values may often jump or spike. Smoothing is something I'm adding for the next version.

[david jenkins]

That helps me to understand WHAT they are, which is always useful!

Can I make use of that data when tuning/developing the ignition map? If so, how?

cheers,
David

[brentp]

Sure you can. You can import the data from different runs into a spreadsheet program, like Excel, and compare them against each other.

All other factors equal, modifications to your ignition map will affect how fast your accelerate (how much torque your engine produces in a given RPM band). This can be visualized using a chart view of the data values (typically RPM) over time. The faster you accelerate, (again, all other conditions being equal) the more torque you're producing.

Note the Accel data is in there somewhat redundantly- since you have multiple samples over time, the accel for RPM and load can be interpreted across time.

Hope this helps.