garygid
Well-known member
Since you have a working Pascal program to receive your
logging data, and write the data to a log file...
Is your Log file format already compatible with the
One-CAN Log files that CAN-Do writes and reads?
If compatible, your program can capture the Log,
and your users could still use CAN-Do to examine
their Logs, and share the files with others.
These are binary, fixed length records of 12 bytes,
two time-stamp (second and millisecond) bytes,
then the two LL NH MsgID bytes, and 8 data bytes.
I do insert a Date-Time Pseudo Message just before
the first message in each minute. The LL NH are FF FF,
and the first 4 data bytes are seconds past 1970 (or
some such) and the next 3 are zero (for microseconds)
and the last byte is FF to indicate that there are no
microseconds.
The file extensions are ".evc" for EV-CAN, ".can" for the
CAR-CAN data, and ".avc" for the AV-CAN data.
The two time-stamp bytes are seconds * 1024 + milliseconds.
The sec are 0 through 59, and ms are 0 through 999.
logging data, and write the data to a log file...
Is your Log file format already compatible with the
One-CAN Log files that CAN-Do writes and reads?
If compatible, your program can capture the Log,
and your users could still use CAN-Do to examine
their Logs, and share the files with others.
These are binary, fixed length records of 12 bytes,
two time-stamp (second and millisecond) bytes,
then the two LL NH MsgID bytes, and 8 data bytes.
I do insert a Date-Time Pseudo Message just before
the first message in each minute. The LL NH are FF FF,
and the first 4 data bytes are seconds past 1970 (or
some such) and the next 3 are zero (for microseconds)
and the last byte is FF to indicate that there are no
microseconds.
The file extensions are ".evc" for EV-CAN, ".can" for the
CAR-CAN data, and ".avc" for the AV-CAN data.
The two time-stamp bytes are seconds * 1024 + milliseconds.
The sec are 0 through 59, and ms are 0 through 999.