Commission Implementing Regulation (EU) 2016/799 of 18 March 2016 implementing Regulation (EU) No 165/2014 of the European Parliament and of the Council laying down the requirements for the construction, testing, installation, operation and repair of tachographs and their components (Text with EEA relevance)

Driving without an appropriate card	Driving without an appropriate card	Driver slot	Driver slot	Driver slot	Driver slot	Driver slot
Driving without an appropriate card	Driving without an appropriate card	No (or non-valid) card	Driver card	Control card	Workshop card	Company card
Co-driver slot	No (or non-valid) card	X		X		X
Co-driver slot	Driver card	X		X	X	X
Co-driver slot	Control card	X	X	X	X	X
Co-driver slot	Workshop card	X	X	X		X
Co-driver slot	Company card	X	X	X	X	X

3.9.5   ‘Card insertion while driving’ event

• (76)This event shall be triggered when a tachograph card is inserted in any slot, while driver activity is DRIVING.

3.9.6   ‘Last card session not correctly closed’ event

• (77)This event shall be triggered when at card insertion the recording equipment detects that, despite the provisions laid down in paragraph 3.1., the previous card session has not been correctly closed (the card has been withdrawn before all relevant data have been stored on the card). This event shall be triggered by driver and workshop cards only.

3.9.7   ‘Over speeding’ event

• (78)This event shall be triggered for each over speeding.

3.9.8   ‘Power supply interruption’ event

• (79)This event shall be triggered, while not in calibration or control mode, in case of any interruption exceeding 200 milliseconds of the power supply of the motion sensor and/or of the vehicle unit. The interruption threshold shall be defined by the manufacturer. The drop in power supply due to the starting of the engine of the vehicle shall not trigger this event.

3.9.9   ‘Communication error with the remote communication facility’ event

• (80)This event shall be triggered, while not in calibration mode, when the remote communication facility does not acknowledge the successful reception of remote communication data sent from the vehicle unit for more than three attempts.

3.9.10   ‘Absence of position information from GNSS receiver’ event

• (81)This event shall be triggered, while not in calibration mode, in case of absence of position information originating from the GNSS receiver (whether internal or external) for more than three hours of accumulated driving time.

3.9.11   ‘Communication error with the external GNSS facility’ event

• (82)This event shall be triggered, while not in calibration mode, in case of interruption of the communication between the external GNSS facility and the vehicle unit for more than 20 continuous minutes, when the vehicle is moving.

3.9.12   ‘Motion data error’ event

• (83)This event shall be triggered, while not in calibration mode, in case of interruption of the normal data flow between the motion sensor and the vehicle unit and/or in case of data integrity or data authentication error during data exchange between the motion sensor and the vehicle unit. This event shall also be triggered, while not in calibration mode, in case the speed calculated from the motion sensor pulses increases from 0 to more than 40 km/h within 1 second, and then stays above 40km/h during at least 3 seconds.

3.9.13   ‘Vehicle motion conflict’ event

• (84)This event shall be triggered, as specified in Appendix 12, while not in calibration mode, in case motion information calculated from the motion sensor is contradicted by motion information calculated from the internal GNSS receiver or from the external GNSS facility or by other independent source(s) in accordance with requirement 26. This event shall not be triggered during a ferry/train crossing.

3.9.14   ‘Security breach attempt’ event

• (85)This event shall be triggered for any other event affecting the security of the motion sensor and/or of the vehicle unit and/or the external GNSS facility as required in Appendix 10, while not in calibration mode.

3.9.15   ‘Time conflict’ event

• (86)This event shall be triggered, while not in calibration mode, when the VU detects a discrepancy between the time of the vehicle unit’s time measurement function and the time originating from the authenticated positions transmitted by the GNSS receiver or the external GNSS facility. A ‘time discrepancy’ is detected if the time difference exceeds ±3 seconds corresponding to the time accuracy set out in requirement 41a, the latter increased by the maximal time drift per day. This event shall be recorded together with the internal clock value of the recording equipment. The VU shall perform the check for triggering the ‘time conflict’ event right before the VU automatically re-adjusts the VU internal clock, in accordance with requirement 211.

3.9.16   ‘Card’ fault

• (87)This fault shall be triggered when a tachograph card failure occurs during operation.

3.9.17   ‘Recording equipment’ fault

• (88)This fault shall be triggered for any of these failures, while not in calibration mode:

• — VU internal fault

• — Printer fault

• — Display fault

• — Downloading fault

• — Sensor fault

• — GNSS receiver or external GNSS facility fault

• — Remote Communication facility fault

• — ITS interface fault.

3.9.18   ‘GNSS anomaly’ event

• (88a)This event shall be triggered, while not in calibration mode, when the GNSS receiver detects an attack, or when authentication of navigation messages has failed, as specified in Appendix 12. After a GNSS anomaly event has been triggered, the VU shall not generate other GNSS anomaly events for the next 10 minutes.

3.10   Built-in and self-tests

• (89) The recording equipment shall detect faults through self-tests and built-in-tests, according to the following table:

Sub-assembly to test	Self-test	Built-in-test
Software		Integrity
Data memory	Access	Access, data integrity
Card interface devices	Access	Access
Keyboard		Manual check
Printer	(up to manufacturer)	Printout
Display		Visual check
Downloading (performed only during downloading)	Proper operation
Sensor	Proper operation	Proper operation
Remote communication facility	Proper operation	Proper operation
GNSS facility	Proper operation	Proper operation
ITS interface	Proper operation

3.11   Reading from data memory

• (90)The recording equipment shall be able to read any data stored in its data memory.

3.12   Recording and storing in the data memory

For the purpose of this point,

• — ‘365 days’ is defined as 365 calendar days of average drivers activity in a vehicle. The average activity per day in a vehicle is defined as at least 6 drivers or co-drivers, 6 card insertion withdrawal cycles, and 256 activity changes. ‘365 days’ therefore include at least 2 190 drivers or co-drivers, 2 190 card insertion withdrawal cycles, and 93 440 activity changes,

• — the average number of place entries per day is defined as at least 6 entries where the daily work period begins and 6 entries where the daily work period ends, so that ‘365 days’ include at least 4 380 place entries,

• — the average number of positions per day when the accumulated driving time reaches a multiple of three hours is defined as at least 6 positions, so that ‘365 days’ include at least 2 190 such positions,

• — the average number of border crossings per day is defined as at least 20 crossings, so that ‘365 days’ include at least 7 300 border crossings,

• — the average number of load/unload operations per day is defined as at least 25 operations (irrespective of the type), so that ‘365 days’ include at least 9 125 load/unload operations,

• — times are recorded with a resolution of one minute, unless otherwise specified,

• — odometer values are recorded with a resolution of one kilometre,

• — speeds are recorded with a resolution of 1 km/h,

• — positions (latitudes and longitudes) are recorded in degrees and minutes, with a resolution of 1/10 of minute, with the associated GNSS accuracy and acquisition time, and with a flag indicating whether the position has been authenticated.’.

• (91)Data stored into the data memory shall not be affected by an external power supply cut-off of less than twelve months in type approval conditions. In addition, data stored in the external remote communication facility, as defined in Appendix 14, shall not be affected by power-supply cut-off of less than 28 days.

• (92)The recording equipment shall be able to record and store implicitly or explicitly in its data memory the following:

3.12.1   Equipment identification data

3.12.1.1   Vehicle unit identification data

• (93)The recording equipment shall be able to store in its data memory the following vehicle unit identification data:

• — name of the manufacturer,

• — address of the manufacturer,

• — part number,

• — serial number,

• — VU generation,

• — ability to use first generation tachograph cards,

• — software version number,

• — software version installation date,

• — year of equipment manufacture,

• — approval number,

• — digital map version identifier (requirement 133l).

• (94)Vehicle unit identification data are recorded and stored once and for all by the vehicle unit manufacturer, except data which may be changed in case of software update in accordance with this Regulation, and the ability to use first generation tachograph cards.

3.12.1.2   Motion sensor identification data

• (95)The motion sensor shall be able to store in its memory the following identification data:

• — name of the manufacturer,

• — serial number,

• — approval number,

• — embedded security component identifier (e.g. internal chip/processor part number),

• — operating system identifier (e.g. software version number).

• (96)Motion sensor identification data are recorded and stored once and for all in the motion sensor, by the motion sensor manufacturer.

• (97)The vehicle unit shall be able to record and store in its data memory the following data related to the 20 most recent successful pairings of motion sensors (if several pairings happen within one calendar day, only the first and the last one of the day shall be stored):

• The following data shall be recorded for each of these pairings:

• — motion sensor identification data: — serial number — approval number

• — motion sensor pairing data: — pairing date.

3.12.1.3   Global Navigation Satellite Systems identification data

• (98)The external GNSS facility shall be able to store in its memory the following identification data:

• — name of the manufacturer,

• — serial number,

• — approval number,

• — embedded security component identifier (e.g. internal chip/processor part number),

• — operating system identifier (e.g. software version number).

• (99)The identification data are recorded and stored once and for all in the external GNSS facility, by the external GNSS facility manufacturer.

• (100)The vehicle unit shall be able to record and store in its data memory the following data related to the 20 most recent successful couplings of external GNSS facilities (if several couplings happen within one calendar day, only the first and the last one of the day shall be stored).

• The following data shall be recorded for each of these couplings:

• — external GNSS facility identification data: — serial number, — approval number,

• — external GNSS facility coupling data: — coupling date

3.12.2   Keys and certificates

• (101)The recording equipment shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A and part B.

3.12.3   Driver or workshop card insertion and withdrawal data

• (102)For each insertion and withdrawal cycle of a driver or workshop card in the equipment, the recording equipment shall record and store in its data memory:

• — the card holder's surname and first name(s) as stored in the card,

• — the card's number, issuing Member State and expiry date as stored in the card,

• — the card generation,

• — the insertion date and time,

• — the vehicle odometer value at card insertion,

• — the slot in which the card is inserted,

• — the withdrawal date and time,

• — the vehicle odometer value at card withdrawal,

• — the following information about the previous vehicle used by the driver, as stored in the card: — VRN and registering Member State, — VU generation (when available), — card withdrawal date and time,

• — a flag indicating whether, at card insertion, the card holder has manually entered activities or not.

• (103)The data memory shall be able to hold these data for at least 365 days.

• (104)When storage capacity is exhausted, new data shall replace oldest data.

3.12.4   Driver activity data

• (105)The recording equipment shall record and store in its data memory whenever there is a change of activity for the driver and/or the co-driver, and/or whenever there is a change of driving status, and/or whenever there is an insertion or withdrawal of a driver or workshop card:

• — the driving status (CREW, SINGLE),

• — the slot (DRIVER, CO-DRIVER),

• — the card status in the relevant slot (INSERTED, NOT INSERTED),

• — the activity (DRIVING, AVAILABILITY, WORK, BREAK/REST),

• — the date and time of the change.

• INSERTED means that a valid driver or workshop card is inserted in the slot. NOT INSERTED means the opposite i.e. no valid driver or workshop card is inserted in the slot (e.g. a company card is inserted or no card is inserted)

• Activity data manually entered by a driver are not recorded in the data memory.

• (106)The data memory shall be able to hold driver activity data for at least 365 days.

• (107)When storage capacity is exhausted, new data shall replace oldest data.

3.12.5   Places and positions where daily work periods begin, end and/or where 3 hours accumulated driving time is reached

• (108)The recording equipment shall record and store in its data memory:

• — places and positions where the driver and/or co-driver begins his daily work period;

• — positions where the accumulated driving time reaches a multiple of three hours;

• — places and positions where the driver and/or the co-driver ends his daily work period.

• (109)When the position of the vehicle is not available from the GNSS receiver at these times, the recording equipment shall use the latest available position, and the related date and time.

• (110)Together with each place or position, the recording equipment shall record and store in its data memory:

• — the driver and/or co-driver card number and card issuing Member State,

• — the card generation,

• — the date and time of the entry,

• — the type of entry (begin, end or 3 hours accumulated driving time),

• — the related GNSS accuracy, date and time if applicable;

• — the vehicle odometer value,

• — a flag indicating whether the position has been authenticated.

• (110a)For places where the daily work period begins or ends entered during the manual entry procedure at card insertion in accordance with requirement 61, the current odometer value and position of the vehicle shall be stored.

• (111)The data memory shall be able to hold places and positions where daily work periods begin, end and/or where 3 hours accumulated driving time is reached for at least 365 days.

• (112)When storage capacity is exhausted, new data shall replace oldest data.

3.12.6   Odometer data

• (113)The recording equipment shall record in its data memory the vehicle odometer value and the corresponding date at midnight every calendar day.

• (114)The data memory shall be able to store midnight odometer values for at least 365 calendar days.

• (115)When storage capacity is exhausted, new data shall replace oldest data.

3.12.7   Detailed speed data

• (116)The recording equipment shall record and store in its data memory the instantaneous speed of the vehicle and the corresponding date and time at every second of at least the last 24 hours that the vehicle has been moving.

3.12.8   Events data

For the purpose of this subparagraph, time shall be recorded with a resolution of 1 second.

• (117)The recording equipment shall record and store in its data memory the following data for each event detected according to the following storage rules:

Event	Storage rules	Data to be recorded per event
Insertion of a non-valid card	— the 10 most recent events.	— date and time of event, — card(s) type, number, issuing Member State and generation of the card creating the event. — number of similar events that day
Card conflict	— the 10 most recent events.	— date and time of beginning of event, — date and time of end of event, — card(s) type, number, issuing Member State and generation of the two cards creating the conflict.
Driving without an appropriate card	— the longest event for each of the 10 last days of occurrence, — the 5 longest events over the last 365 days.	— date and time of beginning of event, — date and time of end of event, — card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event, — number of similar events that day.
Card insertion while driving	— the last event for each of the 10 last days of occurrence,	— date and time of the event, — card(s) type, number, issuing Member State and generation, — number of similar events that day
Last card session not correctly closed	— the 10 most recent events.	— date and time of card insertion, — card(s) type, number, issuing Member State and generation, — last session data as read from the card: — date and time of card insertion.
Over speeding (1)	— the most serious event for each of the 10 last days of occurrence (i.e. the one with the highest average speed), — the 5 most serious events over the last 365 days. — the first event having occurred after the last calibration	— date and time of beginning of event, — date and time of end of event, — maximum speed measured during the event, — arithmetic average speed measured during the event, — card type, number, issuing Member State and generation of the driver card (if applicable), — number of similar events that day.
Power supply interruption (2)	— the longest event for each of the 10 last days of occurrence, — the 5 longest events over the last 365 days.	— date and time of beginning of event, — date and time of end of event, — card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event, — number of similar events that day.
Communication error with the remote communication facility	— the longest event for each of the 10 last days of occurrence, — the 5 longest events over the last 365 days.	— date and time of beginning of event, — date and time of end of event, — card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event, — number of similar events that day.
Absence of position information from GNSS receiver	— the longest event for each of the 10 last days of occurrence, — the 5 longest events over the last 365 days.	— date and time of beginning of event, — date and time of end of event, — card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event, — number of similar events that day.
Communication error with the external GNSS facility	— the longest event for each of the 10 last days of occurrence, — the 5 longest events over the last 365 days.	— date and time of beginning of event, — date and time of end of event, — card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event, — number of similar events that day.
Motion data error	— the longest event for each of the 10 last days of occurrence, — the 5 longest events over the last 365 days.	— date and time of beginning of event, — date and time of end of event, — card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event, — number of similar events that day.
Vehicle motion conflict	— the longest event for each of the 10 last days of occurrence, — the 5 longest events over the last 365 days.	— date and time of beginning of event, — date and time of end of event, — card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event, — number of similar events that day.
Security breach attempt	— the 10 most recent events per type of event.	— date and time of beginning of event, — date and time of end of event (if relevant), — card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event, — type of event.
Time conflict	— the most serious event for each of the 10 last days of occurrence (i.e. the ones with the greatest difference between recording equipment date and time, and GNSS date and time). — the 5 most serious events over the last 365 days.	— recording equipment date and time — GNSS date and time, — card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event, — number of similar events that day.
GNSS anomaly	— the longest events for each of the 10 last days of occurrence, — the 5 longest events over the last 365 days.	— date and time of beginning of event, — date and time of end of event, — card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event, — number of similar events that day.

• (1) The recording equipment shall also record and store in its data memory:
• — the date and time of the last OVER SPEEDING CONTROL,
• — the date and time of the first over speeding following this OVER SPEEDING CONTROL,
• — the number of over speeding events since the last OVER SPEEDING CONTROL.

• (2) These data may be recorded at power supply reconnection only, times may be known with an accuracy to the minute.

3.12.9   Faults data

For the purpose of this subparagraph, time shall be recorded with a resolution of 1 second.

• (118)The recording equipment shall attempt to record and store in its data memory the following data for each fault detected according to the following storage rules:

Fault	Storage rules	Data to be recorded per fault
Card fault	— the 10 most recent driver card faults.	— date and time of beginning of fault, — date and time of end of fault, — card(s) type, number, issuing Member State and generation.
Recording equipment faults	— the 10 most recent faults for each type of fault, — the first fault after the last calibration.	— date and time of beginning of fault, — date and time of end of fault, — type of fault, — card(s) type, number and issuing Member State and generation of any card inserted at beginning and/or end of the fault.

3.12.10   Calibration data

• (119)The recording equipment shall record and store in its data memory data relevant to:

• — known calibration parameters at the moment of activation,

• — its very first calibration following its activation,

• — its first calibration in the current vehicle (as identified by its VIN),

• — the 20 most recent calibrations (if several calibrations happen within one calendar day, only the first and the last one of the day shall be stored).

• (120)The following data shall be recorded for each of these calibrations:

• — purpose of calibration (activation, first installation, installation, periodic inspection),

• — workshop name and address,

• — workshop card number, card issuing Member State and card expiry date,

• — vehicle identification,

• — parameters updated or confirmed: w, k, l, tyre size, speed limiting device setting, odometer (old and new values), date and time (old and new values),

• — the types and identifiers of all the seals in place,

• — the serial numbers of the motion sensor, the external GNSS facility (if any), and the external remote communication facility (if any),

• — the by-default load type associated to the vehicle (load of either goods or passengers),

• — the country in which the calibration has been performed, and the date time when the position used to determine this country was provided by the GNSS receiver.

• (121)In addition, the recording equipment shall record and store in its data memory its ability to use first generation tachograph cards (still activated or not).

• (122)The motion sensor shall record and store in its memory the following motion sensor installation data:

• — first pairing with a VU (date, time, VU approval number, VU serial number),

• — last pairing with a VU (date, time, VU approval number, VU serial number).

• (123)The external GNSS facility shall record and store in its memory the following external GNSS facility installation data:

• — first coupling with a VU (date, time, VU approval number, VU serial number),

• — last coupling with a VU (date, time, VU approval number, VU serial number).

3.12.11   Time adjustment data

• (124)The recording equipment shall record and store in its data memory data relevant to time adjustments performed in calibration mode outside the frame of a regular calibration (def. f)):

• — the most recent time adjustment,

• — the 5 largest time adjustments.

• (125)The following data shall be recorded for each of these time adjustments:

• — date and time, old value,

• — date and time, new value,

• — workshop name and address,

• — workshop card number, card issuing Member State, card generation and card expiry date.

3.12.12   Control activity data

• (126)The recording equipment shall record and store in its data memory the following data relevant to the 20 most recent control activities:

• — date and time of the control,

• — control card number, card issuing Member State and card generation,

• — type of the control (displaying and/or printing and/or VU downloading and/or card downloading and/or roadside calibration checking).

• (127)In case of downloading, the dates of the oldest and of the most recent days downloaded shall also be recorded.

3.12.13   Company locks data

• (128)The recording equipment shall record and store in its data memory the following data relevant to the 255 most recent company locks:

• — lock-in date and time,

• — lock-out date and time,

• — company card number, card issuing Member State and card generation,

• — company name and address.

• Data previously locked by a lock removed from memory due to the limit above, shall be treated as not locked.

3.12.14   Download activity data

• (129)The recording equipment shall record and store in its data memory the following data relevant to the last data memory downloading to external media while in company or in calibration mode:

• — date and time of downloading,

• — company or workshop card number, card issuing Member State and card generation,

• — company or workshop name.

3.12.15   Specific conditions data

• (130)The recording equipment shall record in its data memory the following data relevant to specific conditions:

• — date and time of the entry,

• — type of specific condition.

• (131)The data memory shall be able to hold specific conditions data for at least 365 days (with the assumption that on average, 1 condition is opened and closed per day). When storage capacity is exhausted, new data shall replace oldest data.

3.12.16   Tachograph card data

• (132)The recording equipment shall be able to store the following data related to the different tachograph cards in which had been used in the VU:

• — the tachograph card number and its serial number,

• — the manufacturer of the tachograph card,

• — the tachograph card type,

• — the tachograph card version.

• (133)The recording equipment shall be able to store at least 88 such records.

3.12.17   Border crossings

• (133a) The recording equipment shall record and store in its data memory the following information about border crossings:
• — the country that the vehicle is leaving,
• — the country that the vehicle is entering,
• — the position where the vehicle has crossed the border.

• (133b) Together with countries and position, the recording equipment shall record and store in its data memory:
• — the driver and/or co-driver card number and card issuing Member State,
• — the card generation,
• — the related GNSS accuracy, date and time,
• — a flag indicating whether the position has been authenticated
• — the vehicle odometer value at the time of border crossing detection.

• (133c) The data memory shall be able to hold border crossings for at least 365 days.

• (133d) When storage capacity is exhausted, new data shall replace oldest data.

3.12.18   Load/unload operations

• (133e) The recording equipment shall record and store in its data memory the following information about load and unload operations of the vehicle:
• — the type of operation (load, unload or simultaneous load/unload),
• — the position where the load/unload operation has occurred.

• (133f) When the position of the vehicle is not available from the GNSS receiver at the time of the load/unload operation, the recording equipment shall use the latest available position, and the related date and time.

• (133g) Together with the type of operation and position, the recording equipment shall record and store in its data memory:
• — the driver and/or co-driver card number and card issuing Member State,
• — the card generation,
• — the date and time of the load/unload operation,
• — the related GNSS accuracy, date and time if applicable,
• — a flag indicating whether the position has been authenticated,
• — the vehicle odometer value.

• (133h) The data memory shall be able to store load/unload operations for at least 365 calendar days.

• (133i) When storage capacity is exhausted, new data shall replace oldest data.

3.12.19   Digital map

• (133j) For the purpose of recording the position of the vehicle when the border of a country is crossed, the recording equipment shall store in its data memory a digital map.

• (133k) Allowed digital maps for supporting the border crossing monitoring function of the recording equipment shall be made available by the European Commission for download from a dedicated secured website, under various formats.

• (133l) For each of these maps, a version identifier and a hash value shall be available on the website.

• (133m) The maps shall feature:
• — a level of definition corresponding to NUTS level 0, according to the Nomenclature of Territorial Units for Statistics,
• — a scale of 1:1 million.

• (133n) Tachograph manufacturers shall select a map from the website and download it securely.

• (133o) Tachograph manufacturers shall only use a downloaded map from the website after having verified its integrity using the hash value of the map.

• (133p) The selected map shall be imported in the recording equipment by its manufacturer, under an appropriate format, but the semantic of the imported map shall remain unchanged.

• (133q) The manufacturer shall also store the version identifier of the map used in the recording equipment.

• (133r) It shall be possible to update or replace the stored digital map by a new one made available by the European Commission.

• (133s) Digital map updates shall be made using the software update mechanisms set up by the manufacturer, in application of requirements 226d and 226e, so that the recording equipment can verify the authenticity and integrity of a new imported map, before storing it and replacing the previous one.

• (133t) Tachograph manufacturers may add additional information to the basic map referred to in requirement (133m), for purposes other than recording border crossings, such as the borders of the EU regions, provided that the semantic of the basic map is not changed.

3.13   Reading from tachograph cards

• (134)The recording equipment shall be able to read from first and second generation tachograph cards, where applicable, the necessary data:

• — to identify the card type, the card holder, the previously used vehicle, the date and time of the last card withdrawal and the activity selected at that time,

• — to check that last card session was correctly closed,

• — to compute the driver's continuous driving time, cumulative break time and accumulated driving times for the previous and the current week,

• — to print requested printouts related to data recorded on a driver card,

• — to download a driver card to external media.

• This requirement only applies to first generation tachograph cards if their use has not been suppressed by a workshop.

• (135)In case of a reading error, the recording equipment shall try again, three times maximum, the same read command, and then if still unsuccessful, declare the card faulty and non-valid.

• (135a)The structure in the ‘TACHO_G2’ application depends on the version. Version 2 cards contain additional Elementary Files to the ones of version 1 cards, in particular:

• — in driver and workshop cards: — EF Places_Authentication shall contain the authentication status of the vehicle positions stored in EF Places. A timestamp shall be stored with each authentication status, which shall be exactly the same as the date and time of the entry stored with the corresponding position in EF Places. — EF GNSS_Places_Authentication shall contain the authentication status of the vehicle positions stored in EF GNSS_Places. A timestamp shall be stored with each authentication status, which shall be exactly the same as the date and time of the entry stored with the corresponding position in EF Places. — EF Border_Crossings, EF Load_Unload_Operations and EF Load_Type_Entries shall contain data related to border crossings, load/unload operations and load types.

• — in workshop cards: — EF Calibration_Add_Data shall contain additional calibration data to the ones stored in EF Calibration. The old date and time value and the vehicle identification number shall be stored with each additional calibration data record, which shall be exactly the same as the old date and time value and the vehicle identification number stored with the corresponding calibration data in EF Calibration.

• — in all tachograph cards: — EF VU_Configuration shall contain the cardholder tachograph specific settings.

• The vehicle unit shall ignore any authentication status found in EF Places_Authentication or EF GNSS_Places_Authentication, when no vehicle position with the same timestamp is found in EF Places or EF GNSS_Places.

• The vehicle unit shall ignore the elementary file EF VU_Configuration in all cards insofar as no specific rules have been provided with respect to the use of such elementary file. Those rules shall be set out through an amendment of Annex IC, which shall include the modification or deletion of this paragraph.

3.14   Recording and storing on tachograph cards

3.14.1   Recording and storing in first generation tachograph cards

• (136)Provided first generation tachograph cards use has not been suppressed by a workshop, the recording equipment shall record and store data exactly in the same way as a first generation recording equipment would do.

• (137)The recording equipment shall set the ‘card session data’ in the driver or workshop card right after the card insertion.

• (138)The recording equipment shall update data stored on valid driver, workshop, company and/or control cards with all necessary data relevant to the period while the card is inserted and relevant to the card holder. Data stored on these cards are specified in Chapter 4.

• (139)The recording equipment shall update driver activity and places data (as specified in 4.5.3.1.9 and 4.5.3.1.11), stored on valid driver and/or workshop cards, with activity and places data manually entered by the cardholder.

• (140)All events and faults not defined for the first generation recording equipment shall not be stored on the first generation driver and workshop cards.

• (141)Tachograph cards data update shall be such that, when needed and taking into account card actual storage capacity, most recent data replace oldest data.

• (142)In the case of a writing error, the recording equipment shall try again, three times maximum, the same write command and then if still unsuccessful, declare the card faulty and non-valid.

• (143)Before releasing a driver or workshop card and after all relevant data have been stored on the card, the recording equipment shall reset the ‘card session data’.

3.14.2   Recording and storing in second generation tachograph cards

• (144)Second generation tachograph cards shall contain 2 different card applications, the first of which shall be exactly the same as the TACHO application of first generation tachograph cards, and the second the ‘TACHO_G2’ application, as specified in Chapter 4 and Appendix 2.

• The structure in the ‘TACHO_G2’ application depends on the version. Version 2 cards contain additional Elementary Files to the ones of version 1 cards.

• (145)The recording equipment shall set the ‘card session data’ in the driver or workshop card right after the card insertion.

• (146)The recording equipment shall update data stored on the 2 card applications of valid driver, workshop, company and/or control cards with all necessary data relevant to the period while the card is inserted and relevant to the card holder. Data stored on these cards are specified in Chapter 4.

• (147)The recording equipment shall update driver activity places and positions data (as specified in 4.5.3.1.9, 4.5.3.1.11, 4.5.3.2.9 and 4.5.3.2.11), stored on valid driver and/or workshop cards, with activity and places data manually entered by the cardholder.

• (147a)On insertion of a driver or workshop card, the recording equipment shall store on the card the by-default load type of the vehicle.

• (147b)On insertion of a driver or workshop card, and after the manual entry procedure, the recording equipment shall check the last place where the daily work period begins or ends stored on the card. This place may be temporary, as specified in requirement 59. If this place is in a different country from the current one in which the vehicle is located, the recording equipment shall store on the card a border crossing record, with:

• — the country that the driver left: not available,

• — the country that the driver is entering: the current country in which the vehicle is located,

• — the date and time when the driver has crossed the border: the card insertion time,

• — the position of the driver when the border has been crossed: not available,

• — the vehicle odometer value: not available.

• (148)Tachograph cards data update shall be such that, when needed and taking into account card actual storage capacity, most recent data replace oldest data.

• (149)In the case of a writing error, the recording equipment shall try again, three times maximum, the same write command and then if still unsuccessful, declare the card faulty and non-valid.

• (150)Before releasing a driver card and after all relevant data have been stored on the 2 card applications of the card, the recording equipment shall reset the ‘card session data’.

• (150a)The vehicle unit shall ignore the elementary file EF VU_Configuration in all cards insofar as no specific rules have been provided with respect to the use of such elementary file. Those rules shall be set out through an amendment of Annex IC, which shall include the modification or deletion of this paragraph.

3.15   Displaying

• (151)The display shall include at least 20 characters.

• (152)The minimum character size shall be 5 mm high and 3.5 mm wide.

• (153)The display shall support the characters specified in Appendix 1 Chapter 4 ‘Character sets’. The display may use simplified glyphs (e.g. accented characters may be displayed without accent, or lower case letters may be shown as upper case letters).

• (154)The display shall be provided with adequate non-dazzling lighting.

• (155)Indications shall be visible from outside the recording equipment.

• (156)The recording equipment shall be able to display:

• — default data,

• — data related to warnings,

• — data related to menu access,

• — other data requested by a user.

• Additional information may be displayed by the recording equipment, provided that it is clearly distinguishable from information required above.

• (157)The display of the recording equipment shall use the pictograms or pictograms combinations listed in Appendix 3. Additional pictograms or pictograms combinations may also be provided by the display, if clearly distinguishable from the aforementioned pictograms or pictograms combinations.

• (158)The display shall always be ON when the vehicle is moving.

• (159)The recording equipment may include a manual or automatic feature to turn the display OFF when the vehicle is not moving.

• Displaying format is specified in Appendix 5.

3.15.1   Default display

• (160)When no other information needs to be displayed, the recording equipment shall display, by default, the following:

• — the local time (as a result of UTC time + offset as set by the driver),

• — the mode of operation,

• — the current activity of the driver and the current activity of the co-driver,

• — information related to the driver:

• — if his current activity is DRIVING, his current continuous driving time and his current cumulative break time,

• — if his current activity is not DRIVING, the current duration of this activity (since it was selected) and his current cumulative break time.

• (161)Display of data related to each driver shall be clear, plain and unambiguous. In the case where the information related to the driver and the co-driver cannot be displayed at the same time, the recording equipment shall display by default the information related to the driver and shall allow the user to display the information related to the co-driver.

• (162)In the case where the display width does not allow displaying by default the mode of operation, the recording equipment shall briefly display the new mode of operation when it changes.

• (163)The recording equipment shall briefly display the card holder name at card insertion.

• (164)When an ‘OUT OF SCOPE’ or FERRY/TRAIN condition is opened, then the default display must show using the relevant pictogram that the particular condition is opened (it is acceptable that the driver's current activity may not be shown at the same time).

3.15.2   Warning display

• (165)The recording equipment shall display warning information using primarily the pictograms of Appendix 3, completed where needed by additional numerically coded information. A literal description of the warning may also be added in the driver's preferred language.

3.15.3   Menu access

• (166)The recording equipment shall provide necessary commands through an appropriate menu structure.

3.15.4   Other displays

• (167)It shall be possible to display selectively on request:

• — the UTC date and time, and local time offset,

• — the content of any of the printouts listed in requirement 169 under the same formats as the printouts themselves,

• — the continuous driving time and cumulative break time of the driver,

• — the continuous driving time and cumulative break time of the co-driver,

• — the accumulated driving time of the driver for the previous and the current week,

• — the accumulated driving time of the co-driver for the previous and the current week,

• optional:

• — the current duration of co-driver activity (since it was selected),

• — the accumulated driving time of the driver for the current week,

• — the accumulated driving time of the co-driver for the current daily work period,

• — the accumulated driving time of the driver for the current daily work period.

• (168)Printout content display shall be sequential, line by line. If the display width is less than 24 characters the user shall be provided with the complete information through an appropriate mean (several lines, scrolling, …).

• Printout lines devoted to hand-written information may be omitted for display.

3.16   Printing

• (169)The recording equipment shall be able to print information from its data memory and/or from tachograph cards in accordance with the seven following printouts:

• — driver activities from card daily printout,

• — driver activities from Vehicle Unit daily printout,

• — events and faults from card printout,

• — events and faults from Vehicle Unit printout,

• — technical data printout,

• — over speeding printout.

• — tachograph card data history for a given VU (see chapter 3.12.16)

• The detailed format and content of these printouts are specified in Appendix 4.

• Additional data may be provided at the end of the printouts.

• Additional printouts may also be provided by the recording equipment, if clearly distinguishable from the seven aforementioned printouts.

• (170)The ‘driver activities from card daily printout’ and ‘Events and faults from card printout’ shall be available only when a driver card or a workshop card is inserted in the recording equipment. The recording equipment shall update data stored on the relevant card before starting printing.

• (171)In order to produce the ‘driver activities from card daily printout’ or the ‘events and faults from card printout’, the recording equipment shall:

• — either automatically select the driver card or the workshop card if one only of these cards is inserted,

• — or provide a command to select the source card or select the card in the driver slot if two of these cards are inserted in the recording equipment.

• (172)The printer shall be able to print 24 characters per line.

• (173)The minimum character size shall be 2.1 mm high and 1.5 mm wide.

• (174)The printer shall support the characters specified in Appendix 1 Chapter 4 ‘Character sets’.

• (175)Printers shall be so designed as to produce these printouts with a degree of definition likely to avoid any ambiguity when they are read.

• (176)Printouts shall retain their dimensions and recordings under normal conditions of humidity (10-90 %) and temperature.

• (177)The type approved paper used by the recording equipment shall bear the relevant type approval mark and an indication of the type(s) of recording equipment with which it may be used.

• (178)Printouts shall remain clearly legible and identifiable under normal conditions of storage, in terms of light intensity, humidity and temperature, for at least two years.

• (179)Printouts shall conform at least to the test specifications defined in Appendix 9.

• (180)It shall also be possible to add hand-written notes, such as the driver's signature, to these documents.

• (181)The recording equipment shall manage ‘paper out’ events while printing by, once paper has been re-loaded, restarting printing from printout beginning or by continuing printing and providing an unambiguous reference to previously printed part.

3.17   Warnings

• (182)The recording equipment shall warn the driver when detecting any event and/or fault.

• (183)Warning of a power supply interruption event may be delayed until the power supply is reconnected.

• (184)The recording equipment shall warn the driver 15 minutes before and at the time of exceeding the maximum allowed continuous driving time.

• (185)Warnings shall be visual. Audible warnings may also be provided in addition to visual warnings.

• (186)Visual warnings shall be clearly recognisable by the user, shall be situated in the driver's field of vision and shall be clearly legible both by day and by night.

• (187)Visual warnings may be built into the recording equipment and/or remote from the recording equipment.

• (188)In the latter case it shall bear a ‘T’ symbol.

• (189)Warnings shall have a duration of at least 30 seconds, unless acknowledged by the user by hitting one or more specific keys of the recording equipment. This first acknowledgement shall not erase warning cause display referred to in next paragraph.

• (190)Warning cause shall be displayed on the recording equipment and remain visible until acknowledged by the user using a specific key or command of the recording equipment.

• (191)Additional warnings may be provided, as long as they do not confuse drivers in relation to previously defined ones.

3.18   Data downloading to external media

• (192)The recording equipment shall be able to download on request data from its data memory or from a driver card to external storage media via the calibration/downloading connector. The recording equipment shall update data stored on the relevant card before starting downloading.

• (193)In addition and as an optional feature, the recording equipment may, in any mode of operation, download data through any other interface to a company authenticated through this channel. In such a case, company mode data access rights shall apply to this download.

• (194)Downloading shall not alter or delete any stored data.

• (195)The calibration/downloading connector electrical interface is specified in Appendix 6.

• (196)Downloading protocols are specified in Appendix 7.

• (196a)A transport undertaking which uses vehicles that are fitted with recording equipment complying with this Annex and fall within the scope of Regulation (EC) No 561/2006, shall ensure that all data are downloaded from the vehicle unit and driver cards.

• The maximum period within which the relevant data are downloaded shall not exceed:

• — 90 days for data from vehicle unit;

• — 28 days for data from the driver card.

• (196b)Transport undertakings shall keep the data downloaded from the vehicle unit and driver cards for at least twelve months following recording.

3.19   Remote communication for targeted roadside checks

• (197)When the ignition is on, the Vehicle Unit shall store every 60 seconds in the remote communication facility the most recent data necessary for the purpose of targeted roadside checks. Such data shall be encrypted and signed as specified in Appendix 11 and Appendix 14.

• (198)Data to be checked remotely shall be available to remote communication readers through wireless communication, as specified in Appendix 14.

• (199)Data necessary for the purpose of targeted roadside checks shall be related to:

• — the latest security breach attempt,

• — the longest power supply interruption,

• — sensor fault,

• — motion data error,

• — vehicle motion conflict,

• — driving without a valid card,

• — card insertion while driving,

• — time adjustment data,

• — calibration data including the dates of the two latest stored calibration records,

• — vehicle registration number,

• — speed recorded by the tachograph,

• — vehicle position,

• — an indication if the driver may currently infringe the driving times.

3.20   Data exchanges with additional external devices

• (200)The recording equipment shall also be equipped with an ITS interface in accordance with Appendix 13, allowing the data recorded or produced by either the tachograph or the tachograph cards to be used by an external facility.

• In operational mode, the driver consent shall be needed for the transmission of personal data through the ITS interface. Nevertheless, the driver consent shall not apply to tachograph or card data accessed in control, company or calibration mode. The data and functional access rights for these modes are specified in requirements 12 and 13.

• The following requirements shall apply to ITS data made available through that interface:

• — personal data shall only be available after the verifiable consent of the driver has been given, accepting that personal data can leave the vehicle network. A set of selected existing data that can be available via the ITS interface, and the classification of the data as personal or not personal are specified in Appendix 13. Additional data may also be output in addition to the set of data provided in Appendix 13. The VU manufacturer shall classify those data as ‘personal’ or ‘not personal’, being the driver consent applicable to those data classified as ‘personal’,

• — at any moment, the driver consent can be enabled or disabled through commands in the menu, provided the driver card is inserted,

• — in any circumstances, the presence of the ITS interface shall not disturb or affect the correct functioning and the security of the vehicle unit.

• Additional vehicle unit interfaces may co-exist, provided they fully comply with the requirements of Appendix 13 in terms of driver consent. The recording equipment shall have the capacity to communicate the driver consent status to other platforms in the vehicle network and to external devices.

• For personal data injected in the vehicle network, which are further processed outside the vehicle network, it shall not be the responsibility of the tachograph manufacturer to have that personal data process compliant with the applicable Union legislation regarding data protection.

• The ITS interface shall also allow for data entry during the manual entry procedure in accordance with requirement 61, for both the driver and the co-driver.

• The ITS interface may also be used to enter additional information, in real time, such as:

• — driver activity selection, in accordance with requirement 46,

• — places in accordance with requirement 56,

• — specific conditions, in accordance with requirement 62,

• — load/unload operations, in accordance with requirement 62a.

• This information may also be entered through other interfaces.

• (201)The serial link interface as specified in Annex IB to Regulation (EEC) No 3821/85, as last amended, can continue to equip tachographs for back compatibility. The serial link is classified as a part of the vehicle network, in accordance with requirement 200.

3.21   Calibration

• (202)The calibration function shall allow:

• — to automatically pair the motion sensor with the VU,

• — to automatically couple the external GNSS facility with the VU if applicable,

• — to digitally adapt the constant of the recording equipment (k) to the characteristic coefficient of the vehicle (w),

• — to adjust the current time within the validity period of the inserted workshop card,

• — to adjust the current odometer value,

• — to update motion sensor identification data stored in the data memory,

• — to update, if applicable, external GNSS facility identification data stored in the data memory,

• — to update the types and identifiers of all the seals in place,

• — to update or confirm other parameters known to the recording equipment: vehicle identification, w, l, tyre size and speed limiting device setting if applicable, and by-default load type,

• — to automatically store the country in which the calibration has been performed, and the date time when the position used to determine this country was provided by the GNSS receiver.

• (203)In addition, the calibration function shall allow to supress the use of first generation tachograph cards in the recording equipment, provided the conditions specified in Appendix 15 are met.

• (204)Pairing the motion sensor to the VU shall consist, at least, in:

• — updating motion sensor installation data held by the motion sensor (as needed),

• — copying from the motion sensor to the VU data memory the necessary motion sensor identification data.

• (205)Coupling the external GNSS facility to the VU shall consist, at least, in:

• — updating external GNSS facility installation data held by the external GNSS facility (as needed),

• — copying from the external GNSS facility to the VU data memory the necessary external GNSS facility identification data including the serial number of the external GNSS facility.

• (206)The calibration function shall be able to input necessary data through the calibration/downloading connector in accordance with the calibration protocol defined in Appendix 8. The calibration function may also input necessary data through other means.

3.22   Roadside calibration checking

• (207)The roadside calibration checking function shall allow reading the motion sensor serial number (possibly embedded in the adaptor) and the external GNSS facility serial number (when applicable), connected to the vehicle unit, at the time of the request.

• (208)This reading shall at least be possible on the vehicle unit display through commands in the menus.

• (209)The roadside calibration checking function shall also allow controlling the selection of the I/O mode of the calibration I/O signal line specified in Appendix 6, via the K-line interface. This shall be done through the ECUAdjustmentSession, as specified in Appendix 8, section 7 Control of Test Pulses — Input output control functional unit.

• When the I/O mode of the calibration I/O signal line is active according to this requirement, the ‘Driving without an appropriate card’ warning (requirement 75) shall not be triggered by the vehicle unit.

3.23   Time adjustment

• (210)The time adjustment function shall allow for automatically adjusting the current time. Two time sources are used in the recording equipment for time adjustment: 1) the internal VU clock, 2) the GNSS receiver.

• (211)The time setting of the VU internal clock shall be automatically re-adjusted at variable time intervals. The next automatic time re-adjustment shall be triggered between 72h and 168h after the previous one, and after the VU can access to GNSS time through a valid authenticated position message in accordance with Appendix 12. Nevertheless, the time adjustment shall never be bigger than the accumulated maximal time drift per day, as calculated by the VU manufacturer in accordance with requirement 41b. If the difference between internal VU clock time and GNSS receiver time is bigger than the accumulated maximum time drift per day, then the time adjustment shall bring the VU internal clock as close as possible to the GNSS receiver time. The time setting may only be done if the time provided by the GNSS receiver is obtained using authenticated position messages as set out in Appendix 12. The time reference for the automatic time setting of the VU internal clock shall be the time provided in the authenticated position message.

• (212)The time adjustment function shall also allow for triggered adjustment of the current time, in calibration mode.

• Workshops may adjust time:

• — either by writing a time value in the VU, using the WriteDataByIdentifier service in accordance with section 6.2 of Appendix 8,

• — or by requesting an alignment of the VU clock to the time provided by the GNSS receiver. This may only be done if the time provided by the GNSS receiver is obtained using authenticated position messages. In this latter case, the RoutineControl service shall be used in accordance with section 8 of Appendix 8.

3.24   Performance characteristics

• (213)The Vehicle Unit shall be fully operational in the temperature range – 20 °C to 70 °C, the external GNSS facility in the temperature range – 20 °C to 70 °C, and the motion sensor in the temperature range – 40 °C to 135 °C. Data memory content shall be preserved at temperatures down to – 40 °C.

• (214)The tachograph shall be fully operational in the humidity range 10 % to 90 %.

• (215)The seals used in the smart tachograph shall withstand the same conditions than those applicable to the tachograph components to which they are affixed.

• (216)The recording equipment shall be protected against over-voltage, inversion of its power supply polarity, and short circuits.

• (217)Motion sensors shall either:

• — react to a magnetic field disturbing vehicle motion detection. In such circumstances, the vehicle unit will record and store a sensor fault (requirement 88) or,

• — have a sensing element that is protected from, or immune to, magnetic fields.

• (218)The recording equipment and the external GNSS facility shall conform to international regulation UN ECE R10 and shall be protected against electrostatic discharges and transients.

3.25   Materials

• (219)All the constituent parts of the recording equipment shall be made of materials of sufficient stability and mechanical strength and with stable electrical and magnetic characteristics.

• (220)For normal conditions of use, all the internal parts of the equipment shall be protected against damp and dust.

• (221)The Vehicle Unit and the external GNSS facility shall meet the protection grade IP 40 and the motion sensor shall meet the protection grade IP 64, as per standard IEC 60529:1989 including A1:1999 and A2:2013.

• (222)The recording equipment shall conform to applicable technical specifications related to ergonomic design.

• (223)The recording equipment shall be protected against accidental damage.

3.26   Markings

• (224)If the recording equipment displays the vehicle odometer value and speed, the following details shall appear on its display:

• — near the figure indicating the distance, the unit of measurement of distance, indicated by the abbreviation ‘km’,

• — near the figure showing the speed, the entry ‘km/h’.

• The recording equipment may also be switched to display the speed in miles per hour, in which case the unit of measurement of speed shall be shown by the abbreviation ‘mph’. The recording equipment may also be switched to display the distance in miles, in which case the unit of measurement of distance shall be shown by the abbreviation ‘mi’.

• (225)A descriptive plaque shall be affixed to each separate component of the recording equipment and shall show the following details:

• — name and address of the manufacturer,

• — manufacturer's part number and year of manufacture,

• — serial number,

• — type-approval mark.

• (226)When physical space is not sufficient to show all above mentioned details, the descriptive plaque shall show at least: the manufacturer's name or logo and the part number.

3.27   Monitoring border crossings

• (226a) This function shall detect when the vehicle has crossed the border of a country, which country has been left and which country has been entered.

• (226b) The border crossing detection shall be based on the position measured by the recording equipment, and stored digital map in accordance with point 3.12.19.

• (226c) Border crossings related to the presence of the vehicle in a country for a shorter period than 120s shall not be recorded.

3.28   Software update

• (226d) The vehicle unit shall incorporate a function for the implementation of software updates whenever such updates do not involve the availability of additional hardware resources beyond the resources set out in requirement 226f, and the type-approval authorities give their authorisation to the software updates based on the existing type-approved vehicle unit, in accordance with Article 12(5) of Regulation (EU) No 165/2014.

• (226e) The software update function shall be designed for supporting the following functional features, whenever they are legally required:
• — modification of the functions referred to in point 2.2, except the software update function itself,
• — the addition of new functions directly related to the enforcement of Union legislation on road transport,
• — modification of the modes of operation in point 2.3,
• — modification of the file structure such as the addition of new data or the increase of the file size,
• — deployment of software patches to address software as well as security defects or reported attacks on the functions of the recording equipment.

• (226f) The vehicle unit shall provide free hardware resources of at least 35% for software and data needed for the implementation of requirement 226e and free hardware resources of at least 65% for the update of the digital map based on the hardware resources required for the NUTS 0 map version 2021.

4. CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR TACHOGRAPH CARDS

4.1   Visible data

The front page shall contain:

• (227)the words ‘Driver card’ or ‘Control card’ or ‘Workshop card’ or ‘Company card’ printed in capital letters in the official language or languages of the Member State issuing the card, according to the type of the card.

• (228)the name of the Member State issuing the card (optional);

• (229)the distinguishing sign of the Member State issuing the card, printed in negative in a blue rectangle and encircled by 12 yellow stars. The distinguishing signs shall be as follows:

B BG CZ CY	Belgium Bulgaria Czech Republic Cyprus	LV L LT M	Latvia Luxembourg Lithuania Malta
DK	Denmark	NL	The Netherlands
D EST	Germany Estonia	A PL	Austria Poland
GR	Greece	P RO SK SLO	Portugal Romania Slovakia Slovenia
E	Spain	FIN	Finland
F HR H	France Croatia Hungary	S	Sweden
IRL	Ireland	UK	The United Kingdom
I	Italy

• (230)information specific to the card issued, numbered as follows:

	Driver card	Control Card	Company or Workshop card
1.	surname of the driver	control body name	company or workshop name
2.	first name(s) of the driver	surname of the controller (if applicable)	surname of card holder (if applicable)
3.	birth date of the driver	first name(s) of the controller (if applicable)	first name(s) of card holder (if applicable)
4.a	card start of validity date	card start of validity date	card start of validity date
4.b	card expiry date	card expiry date	card expiry date
4.c	the name of the issuing authority (may be printed on reverse page)	the name of the issuing authority (may be printed on reverse page)	the name of the issuing authority (may be printed on reverse page)
4.d	a different number from the one under heading 5, for administrative purposes (optional)	a different number from the one under heading 5, for administrative purposes (optional)	a different number from the one under heading 5, for administrative purposes (optional)
5. a	Driving licence number (at the date of issue of the driver card)	—	—
5. b	Card number	Card number	Card number
6.	Photograph of the driver	photograph of the controller (optional)	photograph of the fitter (optional)-
7.	Signature of the holder (optional)	Signature of the holder (optional)	Signature of the holder (optional)
8.	Normal place of residence, or postal address of the holder (optional).	Postal address of control body	postal address of company or workshop

• (231)dates shall be written using a ‘dd/mm/yyyy’ or ‘dd.mm.yyyy’ format (day, month, year).

The reverse page shall contain:

• (232)an explanation of the numbered items which appear on the front page of the card;

• (233)with the specific written agreement of the holder, information which is not related to the administration of the card may also be added, such addition will not alter in any way the use of the model as a tachograph card.

• (234)Tachograph cards shall be printed with the following background predominant colours:

• — driver card : white,

• — control card : blue,

• — workshop card : red,

• — company card : yellow.

• (235)Tachograph cards shall bear at least the following features for protection of the card body against counterfeiting and tampering:

• — a security design background with fine guilloche patterns and rainbow printing,

• — in the area of the photograph, the security design background and the photograph shall overlap,

• — at least one two-coloured microprint line.

• Image omitted; see official source

• (236)After consulting the Commission, Member States may add colours or markings, such as national symbols and security features, without prejudice to the other provisions of this Annex.

• (237)Temporary cards referred to in Article 26.4 of Regulation (EU) No. 165/2014 shall comply with the provisions of this Annex.

4.2   Security

The system security aims at protecting integrity and authenticity of data exchanged between the cards and the recording equipment, protecting the integrity and authenticity of data downloaded from the cards, allowing certain write operations onto the cards to recording equipment only, decrypting certain data, ruling out any possibility of falsification of data stored in the cards, preventing tampering and detecting any attempt of that kind.

• (238)In order to achieve the system security, the tachograph cards shall meet the security requirements defined in Appendixes 10 and 11.

• (239)Tachograph cards shall be readable by other equipment such as personal computers.

4.3   Standards

• (240)Tachograph cards shall comply with the following standards:

• — ISO/IEC 7810 Identification cards — Physical characteristics,

• — ISO/IEC 7816 Identification cards — Integrated circuit cards: — Part 1: Physical characteristics, — Part 2: Dimensions and position of the contacts (ISO/IEC 7816-2:2007), — Part 3: Electrical interface and transmission protocols (ISO/IEC 7816-3:2006), — Part 4: Organisation, security and commands for interchange (ISO/IEC 7816-4:2013 + Cor 1:2014), — Part 6: Interindustry data elements for interchange (ISO/IEC 7816-6:2004 + Cor 1:2006), — Part 8: Commands for security operations (ISO/IEC 7816-8:2004).

• — Tachograph cards shall be tested in accordance to ISO/IEC 10373-3:2010 Identification cards — Test methods — Part 3: Integrated circuit cards with contacts and related interface devices.

4.4   Environmental and electrical specifications

• (241)Tachograph cards shall be capable of operating correctly in all the climatic conditions normally encountered in Community territory and at least in the temperature range – 25 °C to + 70 °C with occasional peaks of up to + 85 °C, ‘occasional’ meaning not more than 4 hours each time and not over 100 times during the life time of the card.