What this guide covers
Setting up remote DDD download — the D8 protocol — on a vehicle running Telematics Pro, including the company-card upload to the platform and the first scheduled overnight download cycle.
Prerequisites
- Telematics Pro installed and reporting CAN-bus data (see the install guide first)
- A valid company tachograph card issued by your national authority (ITD in Poland, KBA in Germany)
- Admin access to the FrameLogic platform
Step 1 — Upload the company card
In the platform: Compliance → Cards → Add company card. The card must be inserted in the reader on the admin workstation. The platform stores the card credentials encrypted; the physical card stays with the compliance officer.
Step 2 — Configure the download schedule
Per vehicle: Compliance → Vehicles → [vehicle] → DDD schedule.
- Driver-card data: every 7 days (national maximum is 28; we recommend 7 to keep the working window tight)
- Vehicle-unit data: every 28 days (national maximum is 90)
The cycle is staggered automatically across the fleet to avoid burst network load.
Step 3 — First run
Trigger a manual download for one vehicle: DDD schedule → Run now. The unit communicates with the tachograph over CAN; the file is fetched, signed, and uploaded to the platform archive. Expect this to complete within 90 seconds for driver-card data, longer for vehicle-unit data.
Step 4 — Archive and audit
Downloaded DDD files appear in Compliance → Archive. Each file is hash-signed at the device and again on the server, with a timestamped audit log accepted by GITD (Poland) and BAG (Germany) inspections.
You can export the archive on request — for instance for a labour-law inspection or insurance review — directly from the archive screen.
Troubleshooting
- Card not recognised: verify the company card is set as the default admin card and not blocked.
- Vehicle returns no driver data: confirm the driver inserted their card; D8 only fetches what’s been recorded.
- Cross-border failures: the unit prefers the home-country SIM in steady-state, but DDD downloads should still complete on the secondary SIM if the primary times out. Check Compliance → DDD logs for the carrier used.