suggested advanced logging semantics
Posted: Wed Jan 12, 2011 11:05 pm
For a custom loggable solution that is tuning software agnostic. (doesn't require the tuning software to have (much) special knowledge, especially prior to connecting to the ECU to work)
Provide the following API calls:
Request list of loggable var ID's.
call should provide back a list of how many variables there and, and unique ID's for each
VarID details:
call should provide the following information:
size (8/16/32 bit signed/unsigned), name (limited to X chars, or padded to X chars), "help info" i.e. something ti display in the gui. (required so the tuning software is essentially agnostic).
Additional details may be needed, conversion factors, expected limits, etc, but since this info is all static anyways it's not a big deal and can be stuffed into a header/static struct someplace.
In MtX I can create a menu allowing the user to pick and choose the variables he wants. (ordered appropriately). and then a command to send a that list to the firmware
with would have the following params, number of variables + list of ID's
When a custom datalog is requested, the firmware spits back the requested list in the order specified.
Requires 3 API calls,
- get list of loggable ID's
- Get loggable-ID details
- Set custom datalog stream
Provide the following API calls:
Request list of loggable var ID's.
call should provide back a list of how many variables there and, and unique ID's for each
VarID details:
call should provide the following information:
size (8/16/32 bit signed/unsigned), name (limited to X chars, or padded to X chars), "help info" i.e. something ti display in the gui. (required so the tuning software is essentially agnostic).
Additional details may be needed, conversion factors, expected limits, etc, but since this info is all static anyways it's not a big deal and can be stuffed into a header/static struct someplace.
In MtX I can create a menu allowing the user to pick and choose the variables he wants. (ordered appropriately). and then a command to send a that list to the firmware
with would have the following params, number of variables + list of ID's
When a custom datalog is requested, the firmware spits back the requested list in the order specified.
Requires 3 API calls,
- get list of loggable ID's
- Get loggable-ID details
- Set custom datalog stream