What is converted and what is not
Tacho Converter does not carry everything in a .ddd file into the PDF. This page
says exactly what goes in and what stays out, because knowing in advance that a section you need
is missing is worth more than finding out afterwards.
Driver card
| Data in the file | In the PDF | Section |
|---|---|---|
| Card and holder identification | ✅ | Header |
| Driving licence | ✅ | Header |
| Daily activities | ✅ | Daily activities + Timeline |
| Vehicles used | ✅ | Vehicles used |
| Start and end places of shifts | ✅ | Places / Routes |
| Events | ✅ | Events / Violations |
| Faults | ✅ | Events / Violations |
| Special conditions (ferry, train, out of scope) | ✅ | Special conditions |
| Border crossings | ✅ | Border crossings |
| Loading and unloading operations | ❌ | — |
| Load type | ❌ | — |
The last two rows deserve a note: that data is read from the file — the converter recognises and interprets it — but there is currently no PDF section that prints it. It belongs to second generation version 2, so it is present only on the newest cards. If you need it, it is one of the quickest additions to make: the reading work is already done.
Vehicle unit
| Data in the file | In the PDF | Section |
|---|---|---|
| Vehicle overview (plate, VIN, country) | ✅ | Header |
| Downloadable period | ✅ | Header |
| Tachograph identification (manufacturer, serial number) | ✅ | Header |
| Daily activities | ✅ | Daily activities + Timeline |
| Card insertions and withdrawals | ✅ | Drivers / Sessions |
| Events and faults | ✅ | Events |
| Overspeeding and control data | ✅ | Overspeed control |
| Calibrations | ✅ | Calibrations |
| Time adjustments | ❌ | — |
| Detailed speed | ❌ | — |
Time adjustments are read as well, but not printed. Detailed speed is a case of its own: the vehicle unit records speed second by second over the last twenty-four hours of driving, and it is by far the bulkiest part of a download. Putting it in a PDF would mean hundreds of pages of numbers, unreadable by a human. It matters in forensic work, and that work is done on the original file, not on a printout.
Company card
| Data in the file | In the PDF | Section |
|---|---|---|
| Card identification | ✅ | Header |
| Company activity (downloads, locks, unlocks) | ✅ | Company activity |
Company card conversion is experimental. It works on the files we have been able to test, but the sample is small: if you convert one, your feedback is worth more than any test we can run ourselves.
What is not processed at all
-
Digital signatures — the file carries them, but the converter does not verify
them. The PDF it produces is a reading aid, not a document of evidentiary value:
for a roadside check or a dispute, the original
.dddwith its signatures intact is what counts. - Workshop cards and control cards — they have a structure of their own and are not handled. Upload one and the conversion stops with an error naming the unsupported card type.
Why conversion is partial
It is not cost-cutting: it is the order in which the tool was built. The sections that serve the most people came first — activities, times, vehicles, events — and the rest is being added as people ask for it.
If you need something that is left out today, tell us: that is how we decide what comes next. Requests from people actually using the tool count for more than any feature list dreamed up at a desk.
This page describes how Tacho Converter works. For legal obligations, refer to the official texts.