Steps:
Open the log file via Notepad++ it will help filter out needed data. After the file is already open via Notepad++ press ctrl+f and add the following filters:
TACHO - Check TACHO status
Search for "TDSM:"
Search for "Tacho sts:"
[TDSM]->Tacho sts 0
[TDSM]->Tacho sts 1
[TDSM]->Tacho sts 2
TACHO - Check if the server is requesting the correct information from the Tachograph
Search for "ATR->"
[TACHO.API] ATR->wtr=0x39, st=1627560734, end=1635509534
What To Read => wtr=0x39
0x39 in HEX represents 00111001 in BINARY, reading from right to left, the:
- 1st bit as 1 is asking to retrieve the Tachograph data
- 2nd bit as 0 is NOT asking to retrieve the Driver Card data in Slot 1
- 3rd bit as 0 is NOT asking to retrieve the Driver Card data in Slot 1
- 4th bit as 1 is asking to retrieve Events and faults from the tachograph.
- 5th bit as 1 is asking to retrieve Detailed speed from the tachograph.
- 6th bit as 1 is asking to retrieve Technical data from the tachograph. - 7th bit - unknwon- 8th bit - unknwon
Start Time (FROM) => st=1627560734
1627560734 = 2021-07-29T12:12:14
End TIme (TO) => end=1635509534
1635509534 = 2021-10-29T12:12:14
To convert from HEX to BIN use: https://www.asciitohex.com/
To convert timestamp use: https://www.epochconverter.com/
TACHO - Check Negative Response Error Code
Search for "TACHO"
More specific also "err_Resp"
When something fails in the communication between the device and the tachograph, an error code is generated.
Example (error code is bolded):
[TACHO.API] rxerr_RspTransfrData-> 0x7F 0x36 0x22
[TACHO.API] rxerr_RespDiagSession-> 0x7F 0x10 0x22 (st=0 l=003)
[TACHO.API] err_resp_obj-> 0x7F 0x22 0x22 (st=0 l=003)
Information on the meaning of each code can be found in Confluence: