/
Tachograph debug procedure

Tachograph debug procedure

If you have difficulties with downloading DDD files, you should follow these steps, to debug the system and find the issue.

  1. Make sure that the connection between FM-500 device and digital tachograph is correct. Check the statuses of the tachograph in real time (driver ID, odometer, slot activity. If you are getting accurate values, means device is reading the data from tachograph

2. If statuses are not present, send SMS command “bestpassword D vin” to the device. If you receive an answer with vehicle identification number, means connection is correct. If you get response “vin=”, need to re-check connection.

3. Check application status.

  • Check the status of the reader, card and application in debug tab

  • Check did your preferred IMEI connect to the application (you can filter IMEI in the logs tab)

4. Monitor system events in the monitoring platform.

By following the events you can find in which step, DDD file reading procedure was interrupted (CAN communication; VIN check; Authorization)

You can find event list here: Device events.

All events starting with code 104 are related to digital tachograph (f.e. 104-29 CAN start communication success).