aiLogistic opens the binary file of the driver card (Gen1 and Gen2) in its own reader, extracts who the holder is, what they did each day minute by minute, and what events the tachograph recorded — now in Spanish time.
A .ddd cannot be opened with a double click: it is a binary file from Annex I-B filled with blocks and a cyclic buffer. aiLogistic reads it internally and returns it in the form of a workday, not a dump.
When you drop the driver card file into aiLogistic, the backend does not save it and forgets it: it traverses it block by block as it is, a TLV structure from Regulation (EC) 3821/85 Annex I-B. From the card identification, it extracts the card number and its expiration date; from the holder block, the driver’s first name and last name, decoding the character set and cleaning up the padding that those fields carry.
The challenging part is the activities. The days come in a circular buffer of daily records, each with its list of activity changes encoded in two bytes: the minute of the day, whether the activity is rest, availability, other work, or driving, whether the card was inserted at that moment, and whether it was in double crew. aiLogistic starts from the pointer of the oldest record, makes a complete pass of the buffer, sorts the changes of each day, and converts them into a timeline of segments with absolute start and end times, carrying over the ongoing activity from one day to the next when the days are contiguous.
Everything is labeled in local Spanish time (Europe/Madrid), not in UTC. This is not an aesthetic detail: a driving period that starts at 23:50 UTC belongs to the next day in Spain, and if the file were read in UTC, the rests and workdays would be counted on the wrong day. Daylight saving time is handled by the timezone itself, so March and October do not misalign.
From the events block, the records that the tachograph recorded are read with their type, start, end, and vehicle registration: driving without the proper card, card insertion while driving, interruption of power supply, speeding, card conflicts, temporal overlap, movement data error. And what the reader does not understand, it does not break: each block declares its length, so those that have not yet been analyzed are skipped by their size and the rest of the file is read the same. That unique timeline is what later feeds the download deadlines, the violation report of 561/2006, and the periods of unknown activity.
Own reader, no black boxes
aiLogistic parses the binary in its backend (Gen1 and Gen2, and mixed files), without sending your .ddd to a third-party service to decipher it.
Minute by minute, no summaries
each activity change from the cyclic buffer is converted into a segment with real start and end, with the activity (driving, other work, availability, rest), the inserted card flag, and the double crew mark.
Spanish time from the first minute
timestamps are tagged in Europe/Madrid, so an activity at 23:50 UTC counts on the corresponding day here, and the time change doesn't shift a day.
It tells you who the file belongs to
card number, expiration, and holder's name come from the .ddd itself, so the app can match it with the driver you have registered instead of you guessing by the file name.
Tachograph events in plain text
driving without the proper card, power cuts, speeding, or card conflicts, each with its date, time, and the vehicle's license plate where it was recorded.
Tolerant of what it doesn't know
each block is skipped by the length it declares, so a file with new or uncommon structures is read the same way for what it does understand. And in cases that affect you — Gen2 format events, missing signature blocks, downloads without activity — the app flags it as a warning on the file record instead of keeping quiet.
Detects the bad file before you trust it
if it's truncated, if a block cuts off halfway, if the internal dates are impossible, or if what you've uploaded is actually a PDF or ZIP, the app rejects it with the reason and tells you what to do.
The original remains intact
parsing is read-only. The .ddd as it came from the download key is archived separately for legal retention, and the analysis can be repeated on it whenever you want.

Create your free account, register a driver, and upload their driver card file: in seconds you will have the holder, the days with data, and the daily journey hour by hour in Spanish time.