In CAN scan mode, all CAN messages are logged (except remote frames and error frames, and assuming the SICOLOG is fast enough). However, CAN signals of a scanned CAN are not updated (and thus input CAN signals always yield 0, and output CAN signals are never output). It is possible to also make a standard recording at the same time. Then, saving the measurement with TEMES will only store the samples and ignore the CAN samples, and TSD.EXE must first be called at the command line in order to extract the recorded CAN samples. E. g. with
C:\>TSD s m:
(or with
C:\>TSD s m: filename.log
to also redirect the output to file filename.log)
which yields
2018-09-02 10:31:54
2018-09-02 10:31:56.953910 1 7df 3 1b 1c 1d
2018-09-02 10:31:57.463868 1 7df 3 1b 1c 1d
2018-09-02 10:31:57.983868 1 7df 3 1b 1c 1d
2018-09-02 10:31:58.503928 1 18db33f1 2 2a 2b
2018-09-02 10:31:59.023906 1 18db33f1 2 2a 2b
2018-09-02 10:31:59.543906 1 18db33f1 2 2a 2b
00000000011111111112222222222333333333344444444445555
12345678901234567890123456789012345678901234567890123
Column 1-10: Date
Column 12-26: Time (start marker or sync time without fraction)
Column 28: CAN number (1-4)
Column 30: 'F' if message is a CAN FD message
Column 31: 'B' if message uses bit rate switching
Column 32: 'R' is reserved for remote frames
Column 34-41: Message identifier (hex)
Column 43-44: Message size (decimal)
Column 46- : Message data (hex)
The timestamps have an accuracy of about 1 s (because they are derived from the real time clock), and only the relative timestamps (= the differences of absolute timestamps) are exact (for the corresponding CAN number) within a contiguous section which is delimited by start markers.
Following warning or error lines can appear:
W: Missing measurement data (USB stick access too slow)!
W: Missing messages for CAN #1!
W: Missing messages for CAN #2!
W: Missing messages for CAN #3!
W: Missing messages for CAN #4!
E: Unknown data = stream data (hex)
E: Wrong data = stream data (hex)
And one warning line which can mostly be ignored for the CAN samples:
W: Missing measurement data (CPU too slow)!
However, the timestamp might be out of synchronization when the cycle processing was delayed by at least 30 ms (for CAN1 or CAN2) or 35 minutes (for CAN3 or CAN4), or when a start marker happens to be in the missing measurement data. Also, there is a blind spot after missing messages for a CAN that further missing messages will be ignored for the next following 4 CAN messages (for CAN1 or CAN2) or for the next following 26 CAN messages (for CAN3 or CAN4).
The ASCII file filename.log can be converted to a TEMES measurement filename.tms with the command line program LOG2TMS.EXE, e. g. with
C:\>LOG2TMS -1 library filename
which creates signals for all defined CAN signals of the library library.can with the adjustable default sample rate of 10 ms and only the samples of CAN number 1.
Please see also CAN Scan Mode (Definition).
Minimum required version: TSD.EXE V1.09