Skip to main content

Remote tachograph download does not work – what to check

What to check when a remote tachograph download fails: tachostatus responses, Pending, authorization, communication and validation errors, Tacho App setup.

Applies to: remote tachograph download with HCV5, HCV5 Lite and Tco4 HCV devices. Tco4 HCV devices do not support Gen2v2 tachographs (e.g. VDO DTCO 4.1, Stoneridge SE5000-8.1) – with these tachographs the device must be replaced with an HCV5 or HCV5 Lite.

1. Before you start

  • The vehicle ignition must be ON and a valid company card must be connected during the download.

  • Make sure the device runs the latest firmware, extender firmware and configuration (re-save the configuration file with the latest Advanced Configurator and upload it again). If you use TrustTrack, also use the latest Tacho App version. All files are available on the Downloads page.

  • A firmware update queued for the device waits until an ongoing tachograph download is finished.

2. Check the tachograph status

With the ignition ON, send the SMS command <password> tachostatus. For 5th generation devices, also send <password> info tachoecuhw;tachoecuhwver;tachoecusw;tachoecuswver;tachoregstate. For Tco4 HCV devices this command is not available – take the tachograph model from the technical printout, service documents or a sticker photo. Then follow the section that matches the tachostatus response.

Tacho status 0 – the device does not detect the tachograph

  1. Check the connection. Supported connections are FMS, Port C or the front interface (VDO only). Port A is not supported. See the connection diagrams.

  2. Check that the matching interface (FMS, Tacho read or K-Line) is enabled in the configuration.

  3. If you use the FMS or Tacho read connection, try swapping CAN1 and CAN2.

  4. If you use Port C (Tacho read), try switching the baud rate between 250 and 500, and check that the resistance between C5 and C7 is 60 ohms.

  5. Check for third-party devices connected to the tachograph or FMS interface (e.g. other trackers or manufacturer fleet units). Remove them if possible.

Tacho status 0, Error (10 12)

DDD file download is not enabled on tachograph Port A (used with the FMS connection). Ask an authorised tachograph workshop to enable it.

Tacho status 0, Error (10 22)

DDD file download is not enabled on tachograph Port C. Ask an authorised tachograph workshop to enable it.

Tacho status 2

The device detects the tachograph, but the required settings are missing. Check that the FMS, Tacho read or K-Line interface is enabled and that these IOs are enabled in the configuration: TCO first driver ID, TCO second driver ID, TCO first driver status, TCO second driver status.

Tacho status 1 – the tachograph is detected

The connection works. Continue with section 3 depending on the download error.

3. Download errors

Download stays "Pending" or does not start

  • The device must connect to the server via IP1. IP2 is used only for sending records, not for tachograph downloads.

  • The ignition source must be DIN4 or Custom ignition, with all related IOs enabled in the configuration and working.

  • TrustTrack: if a company card is specified in the vehicle details, check that the card name matches the card in the Tacho App. If needed, select the correct card.

  • TrustTrack: delete all pending tachograph downloads, wait at least 2–3 hours and start a new download.

"Authorization error"

  • Check that the company card is valid (not expired).

  • Use the same company card that was used to lock the tachograph to the company.

  • VDO tachographs with software version 4072: a download attempt with an expired company card can permanently disable remote download, even after a valid card is used. If the company card was replaced around the time the problem started, update the tachograph software to version 4075 or higher at an authorised workshop.

"Device communication error"

  • Check that a supported connection is used (FMS, Port C or front interface for VDO). If Port A is used, change the connection.

  • For Port C, check that the resistance between C5 and C7 is 60 ohms.

  • Check for third-party devices on the tachograph or FMS interface.

  • Stoneridge tachographs with a DSRC module on Port C: when the vehicle starts moving, the DSRC module communicates with the tachograph via Port C, and remote download is not possible at the same time. Download only when the vehicle is stopped, or use the FMS connection if it is available.

"Validation error" or file without technical data

The downloaded file has an invalid signature in one of its data blocks. Ask the vehicle owner to take a manual tachograph download for the same period (a full file with all data), or have it done at an authorised tachograph workshop, and send it to support.

  • If the manual file has the same invalid signature, the issue is in the tachograph – ask the authorised workshop to check it.

  • If the manual file is correct, send it to support as evidence for further investigation.

"Unknown error" or download stuck during authentication

Contact support (see section 6).

4. Tacho App (TrustTrack)

  • The client is added in the "Clients" tab (use the client's web user details).

  • The company card is visible in the "Cards" tab and has a name ("no label" means no name is assigned – double-click the card, enter a name and press Enter).

  • The card is assigned to the client in the "Assignments" tab. A green check mark is shown in the bottom-right corner of the app.

  • Only Omnikey 3021 card readers and Lisle card racks are supported. Make sure the reader drivers are installed.

  • Use the Tacho App on a dedicated computer. Close other tachograph or card reader applications, as they conflict with the Tacho App.

  • If the card is not visible, restart the Tacho App (right-click the tray icon → Exit, then start it again) and check that the card is inserted with the chip facing up.

See also the Tachograph desktop app user manual.

5. Time analysis is empty

Driving and resting times are calculated from tachograph data received via the K-Line interface and from .DDD driver card files. The Time analysis panel is shown only for vehicles that have this tachograph data.

6. Contact support

Include:

  • IMEI and the responses to tachostatus and the info command (section 2)

  • tachograph model and software version (from the technical printout, service documents or a sticker photo)

  • connection type (FMS, Port C, front interface)

  • whether this is a new installation or downloads worked before

  • any recent firmware or configuration changes, or a tachograph replacement (e.g. from Gen1 to Gen2)

  • the exact error and the time of the failed download

Related Articles
Did this answer your question?