Description:
Detailed information about Ruptela tachograph solution can be found here:
Tachograph Solution
Information to activate tacho support from LCM can be found here:
Installation / configuration workflow summary:
Tacho status 0 troubleshooting steps:
Refer to the manuals bellow to check tacho compatibility:
1.1. If tacho is not compatible, inform client, that tacho does not support remote DDD download.
1.2. If tacho is compatible, proceed further with this document.
Make sure, that HCV is updated with latest FW:
2.1. Test tachograph communication by sending tacho SMS command and tachostatus SMS command for HCV5 and Tco4 HCV (FW 03.64.19 and higher) (Note: Ignition must be ON). If tacho status is 0, proceed further with this document.
Find out how HCV is connected to tachograph (Via FMS / Via C connector directly / Via front K-Line interface).
3.1. Connection via FMS:
3.1.1. Find out which CAN interface was used from HCV side (CAN1 or CAN2).
3.1.2. Check device configuration to make sure it is correct. Example of configuration via CAN2 interface:
3.1.3. Test tachograph communication by sending tacho SMS command (Note: ignition must be ON).
3.1.4. If tacho status is still 0, try different baud rate in configuration (FMS 250/500):
3.1.5. Test tachograph communication by sending tacho SMS command (Note: Ignition must be ON).
3.1.6. If tacho status is still 0, most likely default telematics system is used. In such case, advice to refer to the truck dealer for the option to free tachograph port C and prepare the tachograph.
3.2. Connection via C connector:
3.2.1. Find out which CAN interface was used from HCV side (CAN1 or CAN2).
3.2.2. Check device configuration to make sure it is correct. Example of configuration via CAN1 interface:
3.2.3. Test tachograph communication by sending tacho SMS command (Note: Ignition must be ON).
3.2.4. If tacho status is still 0, try different baud rate in configuration (Tacho read 250/500):
3.2.5. Test tachograph communication by sending tacho SMS command (Note: Ignition must be ON).
3.2.6. If tacho status is still 0, pass ticket to Tier 2.
3.3. Connection via front K-Line interface:
3.3.1. Check device configuration and make sure Tacho read is enabled on K-Line:
3.3.2. Confirm with client if front interface was activated using the VDO unlock card (an example of the card is show below).
Before activation, all tachograph sockets must be free and not occupied by any driver, company, etc. card!
For the VDO unlock card please refer to your local VDO representative.
3.3.3. Test tachograph communication by sending tacho SMS command (Note: ignition must be ON).
3.3.4. If tacho status is still 0, pass ticket to Tier 2.