Skip to main content
Tachograph troubleshooting - Log collection
Albert Basiul avatar
Written by Albert Basiul
Updated over 7 months ago

6. Collect the device log while ignition is ON and tacho download is in progress. See below:

Recommended order of actions:

6.1. Make sure the device has test FW version and Tacho status: 1.

Tacho test FW files can be recognized by "T0", "T1" and similar marking in the file name ( see examples below):

mceclip3.png

Note: Tacho test FW files CANNOT BE SHARED with client (you may upload it to the device yourself remotely OTA).

6.2. Make sure that all conditions for successful download are satisfied;

6.3. Send the following SMS to initiate Log reading:

password getlog 92.62.134.14,10103,1,60

Note: “password” should be replaced with SMS password set in the device configuration (or removed in case there is no password).

6.4. Wait for the response from the device:

getlog ok

6.5. Initiate new DDD download:

blobid2.jpg

6.6. Leave the device for 60 minutes OR until the download finishes.

Note: you can stop device log reading earlier (not waiting for 60 minutes) by sending SMS command (“password” should be replaced with SMS password):

password stoplog

6.7. Download the device log (.LOG file) from the server: http://support-objects-logs.sharedinfra.az2.ruptela.lt/

mceclip0.png

Note: you can search the page by IMEI pressing CTRL+F and inputting IMEI number.

6.9 When the device log is read, update the device back to a Standard FW after testing is complete.

7. The log file is necessary in order to pass the case to the 2nd line. How to interpret the log file for clues can be found here: Tachograph troubleshooting - Log interpretation

Did this answer your question?