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)

In forceVersion 2016-03-18from 2016-03-02

Grade B

mapped from publisher markup. A grade says how a document's structure was obtained, not how reliable the law is.

Ask Gelex about this law

Address https://gelex.eu/eli/EU/regulation/2016/799@2016-03-18/en

Contents

Preamble
1. Article 1 Subject matter and scope
2. Article 2 Definitions
3. Article 3 Location-based services
4. Article 4 Procedure for type-approval of a tachograph and tachograph components
5. Article 5 Modifications to type-approvals
6. Article 6 Entry into force
ANNEX
ANNEX I C
Requirements for construction, testing, installation, and inspection INTRODUCTION
1.
2.
2.1(1)(2)(3)(4)(5)(6)(7)
2.3(9)(10)(11)(12)(13)
3.
3.1(15)(16)(17)(18)(19)(20)
3.2(21)(22)(23)(24)(25)(26)(27)
3.2.1(28)(29)(30)(31)
3.2.2(32)(33)(34)(35)
3.2.3(36)(37)
3.3(38)(39)(40)(41)(42)(43)
3.4(44)(45)(46)(47)(48)(49)(50)(51)(52)(53)
3.6
3.6.1(56)(57)(58)(59)(60)
3.7(63)(64)(65)(66)(67)(68)
3.9(71)
3.12(91)(92)
3.12.1
3.12.1.1(93)(94)
3.12.1.2(95)(96)(97)
3.12.1.3(98)(99)(100)
3.12.3(102)(103)(104)
3.12.4(105)(106)(107)
3.12.5(108)(109)(110)(111)(112)
3.12.6(113)(114)(115)
3.12.8(117)
3.12.10(119)(120)(121)(122)(123)
3.12.11(124)(125)
3.12.12(126)(127)
3.12.15(130)(131)
3.12.16(132)(133)
3.13(134)(135)
3.14
3.14.1(136)(137)(138)(139)(140)(141)(142)(143)
3.14.2(144)(145)(146)(147)(148)(149)(150)
3.15(151)(152)(153)(154)(155)(156)(157)(158)(159)
3.15.1(160)(161)(162)(163)(164)
3.15.4(167)(168)
3.16(169)(170)(171)(172)(173)(174)(175)(176)(177)(178)(179)(180)(181)
3.17(182)(183)(184)(185)(186)(187)(188)(189)(190)(191)
3.18(192)(193)(194)(195)(196)
3.19(197)(198)(199)
3.20(200)(201)
3.21(202)(203)(204)(205)(206)
3.22(207)(208)(209)
3.23(210)(211)(212)
3.24(213)(214)(215)(216)(217)(218)
3.25(219)(220)(221)(222)(223)
3.26(224)(225)(226)
4.
4.1(227)(228)(229)(230)(231)(232)(233)(234)(235)(236)(237)
4.2(238)(239)
4.4(241)(242)(243)(244)
4.5(245)(246)(247)
4.5.2(248)
4.5.3
4.5.3.1
4.5.3.1.1(253)
4.5.3.1.2(254)
4.5.3.1.3(255)
4.5.3.1.4(256)
4.5.3.1.5(257)(258)
4.5.3.1.6(259)
4.5.3.1.7(260)(261)(262)
4.5.3.1.8(263)(264)(265)
4.5.3.1.9(266)(267)(268)
4.5.3.1.10(269)(270)
4.5.3.1.11(271)(272)
4.5.3.1.12(273)
4.5.3.1.13(274)(275)
4.5.3.1.14(276)(277)
4.5.3.2
4.5.3.2.1(278)
4.5.3.2.2(279)
4.5.3.2.3(280)
4.5.3.2.4(281)
4.5.3.2.5(282)(283)
4.5.3.2.6(284)
4.5.3.2.7(285)(286)(287)
4.5.3.2.8(288)(289)(290)
4.5.3.2.9(291)(292)(293)
4.5.3.2.10(294)(295)
4.5.3.2.11(296)(297)
4.5.3.2.12(298)
4.5.3.2.13(299)(300)
4.5.3.2.14(301)(302)
4.5.3.2.15(303)(304)
4.5.3.2.16(305)(306)
4.5.4
4.5.4.1
4.5.4.1.1(307)
4.5.4.1.2(308)(309)
4.5.4.1.3(310)
4.5.4.1.4(311)
4.5.4.1.5(312)
4.5.4.1.6(313)(314)(315)(316)(317)
4.5.4.1.7(318)(319)
4.5.4.1.8(320)(321)
4.5.4.1.9(322)(323)
4.5.4.1.10(324)(325)
4.5.4.1.11(326)
4.5.4.1.12(327)
4.5.4.1.13(328)(329)
4.5.4.2
4.5.4.2.1(330)
4.5.4.2.2(331)(332)
4.5.4.2.3(333)
4.5.4.2.4(334)
4.5.4.2.5(335)
4.5.4.2.6(336)(337)(338)(339)(340)
4.5.4.2.7(341)(342)
4.5.4.2.8(343)(344)
4.5.4.2.9(345)(346)
4.5.4.2.10(347)(348)
4.5.4.2.11(349)
4.5.4.2.12(350)
4.5.4.2.13(351)(352)
4.5.4.2.14(353)(354)
4.5.4.2.15(355)(356)
4.5.5
4.5.5.1
4.5.5.1.1(357)
4.5.5.1.2(358)
4.5.5.1.3(359)
4.5.5.1.4(360)
4.5.5.1.5(361)(362)
4.5.5.2
4.5.5.2.1(363)
4.5.5.2.2(364)
4.5.5.2.3(365)
4.5.5.2.4(366)
4.5.5.2.5(367)(368)
4.5.6
4.5.6.1
4.5.6.1.1(369)
4.5.6.1.2(370)
4.5.6.1.3(371)
4.5.6.1.4(372)
4.5.6.1.5(373)(374)
4.5.6.2
4.5.6.2.1(375)
4.5.6.2.2(376)
4.5.6.2.3(377)
4.5.6.2.4(378)
4.5.6.2.5(379)(380)
5.
5.1(381)(382)(383)(384)(385)(386)(387)(388)(389)(390)(391)(392)(393)(394)
5.2(395)(396)(397)
5.3(398)(399)(400)(401)(402)(403)(404)(405)(406)
6.
6.4(409)(410)(411)(412)(413)
6.4(409)(410)(411) a.
6.6(415)(416)
7.(417)(418)(419)(420)(421)(422)(423)(424)
8.
8.1(425)(426)(427)(428)(429)(430)
8.2(431)(432)(433)
8.3(434)(435)(436)(437)(438)(439)
8.4(440)(441)(442)(443)(444)(445)(446)(447)(448)(449)(450)
8.5(451)(452)(453)(454)
8.6(455)(456)(457)(458)(459)
Appendix 1 DATA DICTIONARY
1.
2.
2.1. Value assignment — Octet Aligned: scpaatttttttttttB (16 bits)
6.
6.1. VU Authentication protocol identifiers
Appendix 2 TACHOGRAPH CARDS SPECIFICATION
1.
2.TCS_01TCS_02
2.1.TCS_03TCS_04
2.3.TCS_06TCS_07
3.
3.2.TCS_10
3.2.1TCS_11TCS_12TCS_13TCS_14TCS_15TCS_16
3.2.2TCS_17TCS_18
3.2.3TCS_19TCS_20TCS_21
3.3.TCS_22TCS_23TCS_24TCS_25——TCS_26——TCS_27——TCS_28
3.4.————————TCS_29TCS_30
3.5.TCS_31TCS_32TCS_33 Notes: TCS_34
3.5.1
3.5.1.1TCS_35TCS_36TCS_37TCS_38
3.5.1.2TCS_39TCS_40TCS_41
3.5.2
3.5.2.1TCS_42TCS_43
3.5.2.1.1TCS_44TCS_45TCS_46TCS_47
3.5.2.2TCS_48TCS_49TCS_50
3.5.2.3TCS_51TCS_52TCS_53
3.5.2.3.1TCS_54TCS_55
3.5.3
3.5.3.1TCS_56TCS_57
3.5.3.1.1TCS_58TCS_59TCS_60
3.5.3.2TCS_61TCS_62TCS_63
3.5.3.3TCS_64TCS_65TCS_66
3.5.3.3.1TCS_67TCS_68
3.5.4TCS_69TCS_70TCS_71
3.5.5TCS_72TCS_73TCS_74TCS_75TCS_76TCS_77TCS_78
3.5.6TCS_79TCS_80
3.5.7
3.5.7.1TCS_81TCS_82TCS_83TCS_84TCS_85
3.5.7.2TCS_86TCS_87TCS_88TCS_89TCS_90
3.5.8TCS_91TCS_92TCS_93TCS_94TCS_95
3.5.9TCS_96TCS_97TCS_98TCS_99
3.5.10TCS_100TCS_101TCS_102
3.5.11
3.5.11.1TCS_103TCS_104TCS_105TCS_106TCS_107
3.5.11.2
3.5.11.2.1TCS_108TCS_109
3.5.11.2.2TCS_110TCS_111
3.5.11.2.3TCS_112TCS_113TCS_114
3.5.12TCS_115TCS_116TCS_117
3.5.13TCS_118TCS_119TCS_120TCS_121TCS_122TCS_123TCS_124TCS_125
3.5.14TCS_126TCS_127TCS_128TCS_129TCS_130TCS_131
3.5.15TCS_132TCS_133TCS_134
3.5.16TCS_135TCS_136TCS_137TCS_138TCS_139
4.TCS_140TCS_141
4.1.TCS_142TCS_143TCS_144TCS_145TCS_146TCS_147
4.2.
4.2.1TCS_148TCS_149TCS_150TCS_151
4.2.2TCS_152TCS_153TCS_154TCS_155
4.3.
4.3.1TCS_156TCS_157TCS_158TCS_159
4.3.2TCS_160TCS_161TCS_162TCS_163
4.4.
4.4.1TCS_164TCS_165TCS_166TCS_167
4.4.2TCS_168TCS_169TCS_170TCS_171
4.5.
4.5.1TCS_172TCS_173TCS_174TCS_175
4.5.2TCS_176TCS_177TCS_178TCS_179
Appendix 3
PICTOGRAMS PIC_001
Appendix 4 PRINTOUTS
3.
Appendix 5
DISPLAY DIS_001
Appendix 6 FRONT CONNECTOR FOR CALIBRATION AND DOWNLOAD
1.
2.INT_004INT_005INT_006
2.INT_004INT_005 Data byte organisation
3.INT_007INT_008INT_009
Appendix 7 DATA DOWNLOADING PROTOCOLS
1.
2.
2.2.
2.2.1DDP_002DDP_003DDP_004
2.2.2 Notes:
2.2.2.1DDP_005
2.2.2.2DDP_006
2.2.2.3DDP_007
2.2.2.4DDP_008
2.2.2.5DDP_052
2.2.2.6DDP_053
2.2.2.7DDP_009
2.2.2.8DDP_010
2.2.2.9DDP_011DDP_054
2.2.2.10DDP_012DDP055
2.2.2.11DDP_013
2.2.2.12DDP_014
2.2.2.13DDP_015
2.2.2.14DDP_016
2.2.2.15DDP_017
2.2.2.16DDP_018
2.2.4DDP_019
Figure 1 Message flow, timing
2.2.5
2.2.5.1DDP_020DDP_021
2.2.5.2
1.
Figure 2 VU error handling
2.
Figure 3 IDE error handling
2.2.6
2.2.6.1DDP_029 Data structure generation 1 Data structure generation 2
2.2.6.2DDP_030 Data structure generation 1 Data structure generation 2
2.2.6.3DDP_031 Data structure generation 1 Data structure generation 2
2.2.6.4DDP_032 Data structure generation 1 Data structure generation 2:
2.2.6.5DDP_033 Data structure generation 1 Data structure generation 2:
3.
3.3.DDP_035
3.4.
3.4.2DDP_041DDP_042DDP_043DDP_044DDP_045DDP_046
4.DDP_047DDP_048DDP_049DDP_050DDP_051
Appendix 8 CALIBRATION PROTOCOL
1.CPR_001CPR_002CPR_003
2. References:
3.
3.1.CPR_004 Table 1 Service Identifier value summary table
4. Table 2 CPR_005 Communication Services
4.1.CPR_006CPR_007CPR_008CPR_009CPR_010CPR_011CPR_012CPR_014CPR_016CPR_017 Table 3 Table 4 CPR_018 Table 5 Table 6 CPR_019 Timing values for fast initialisation Communication timing values StartCommunication Request Message StartCommunication Positive Response Message
4.2.
4.2.1CPR_020CPR_021CPR_022CPR_023
4.2.2CPR_024 Table 7 Table 8 Table 9 StopCommunication Request Message StopCommunication Positive Response Message StopCommunication Negative Response Message
4.3.
4.3.2CPR_079 Table 10 CPR_080 Table 11 CPR_081 Table 12 TesterPresent Request Message TesterPresent Positive Response Message TesterPresent Negative Response Message
5. Table 13 Management Services
5.1.
5.1.1CPR_025CPR_026CPR_027
5.1.2CPR_028 Table 14 Table 15 Table 16 StartDiagnosticSession Request Message StartDiagnosticSession Positive Response Message StartDiagnosticSession Negative Response Message
5.1.3CPR_029 Table 17 Definition of diagnosticSession Values
5.2.
5.2.1CPR_033CPR_034CPR_035CPR_036CPR_037CPR_038CPR_039
5.2.2CPR_040 Table 18 Table 19 Table 20 SecurityAccess Request- requestSeed Message SecurityAccess — requestSeed Positive Response Message SecurityAccess Negative Response Message
5.2.3CPR_041 Table 21 Table 22 Table 23 SecurityAccess Request — sendKey Message SecurityAccess — sendKey Positive Response Message SecurityAccess Negative Response Message
6. Table 24 Data Transmission Services
6.1.
6.1.2CPR_051 Table 25 Table 26 Table 27 ReadDataByIdentifier Request Message ReadDataByIdentifier Positive Response Message ReadDataByIdentifier Negative Response Message
6.1.3CPR_052CPR_053 Table 28 CPR_054 Definition of recordDataIdentifier values
6.2.
6.2.2CPR_057 Table 29 Table 30 Table 31 WriteDataByIdentifier Request Message WriteDataByIdentifier Positive Response Message WriteDataByIdentifier Negative Response Message
7. Table 32 Input/Output Control functional unit
7.1.
7.1.1CPR_058CPR_059CPR_060CPR_061
7.1.2CPR_062 Table 33 Table 34 Table 35 InputOutputControlByIdentifier Request Message InputOutputControlByIdentifier Positive Response Message InputOutputControlByIdentifier Negative Response Message
7.1.3CPR_064 Table 36 CPR_065 Table 37 Definition of inputOutputControlParameter values Definition of controlState values
7.1.3CPR_064 Table 36 Definition of inputOutputControlParameter values ReturnControlToECU
8.CPR_067CPR_068
8.1.CPR_069CPR_070CPR_071CPR_072 Table 38 CPR_073 dataRecords ranges
8.2.CPR_074 Table 39 CPR_075 Table 40 CPR_076 Table 41 CPR_078 Table 42 Format of dataRecords Detailed format of TimeDate (recordDataIdentifier value # F90B) Detailed format of NextCalibrationDate (recordDataIdentifier value # F922) Detailed format of VehicleRegistrationNumber (recordDataIdentifier value # F97E)
8.2.CPR_074 Table 39 CPR_075 Table 40 CPR_076 Table 41 Format of dataRecords Detailed format of TimeDate (recordDataIdentifier value # F90B) Detailed format of NextCalibrationDate (recordDataIdentifier value # F922)
Appendix 9 TYPE APPROVAL LIST OF MINIMUM REQUIRED TESTS
1.
2.
3. a)
4.
grp_33
5.

THE EUROPEAN COMMISSION,

Having regard to the Treaty on the Functioning of the European Union,

Having regard to Regulation (EU) No 165/2014 of the European Parliament and of the Council of 4 February 2014 on tachographs in road transport, and in particular Articles 11 and 12(7) thereof,

Whereas:

(1) Regulation (EU) No 165/2014 has introduced second-generation digital tachographs called smart tachographs, which include a connection to the global navigation satellite system (GNSS) facility, a remote early detection communication facility, and an interface with intelligent transport systems. The specifications for the technical requirements for the construction of smart tachographs should be set up.

(2) The remote early detection facility established by Article 9(4) of Regulation (EU) No 165/2014 should transmit to a roadside control officer the data of the digital tachograph and the information concerning the weights and weight per axles of the complete vehicle combination (tractor and trailers or semi-trailers), in accordance with Directive 96/53/EC of the European Parliament and of the Council. That should enable an effective and quick check of vehicles by the control authorities, with fewer electronic devices in the vehicle cab.

(3) In accordance with Directive 96/53/EC, the remote early detection facility should use the CEN DSRC standards referred to in that Directive, at the frequency band of 5795-5805 MHz. As that frequency band is used for electronic tolling as well, and in order to avoid interference between tolling and control applications, control officers should not use the remote early detection facility on a toll plaza.

(4) New security mechanisms for maintaining the level of security of the digital tachograph should be introduced with the smart tachograph to address current security vulnerabilities. One of such vulnerabilities is the absence of expiry dates of digital certificates. In order to comply with the best practices in security matters, it is recommended that the use of digital certificates without expiry dates should be avoided. The normal operation validity period of vehicle units should be 15 years, starting on the issuing date of the vehicle unit digital certificates. Vehicle units should be replaced after that validity period.

(5) The provision of secured and reliable positioning information is an essential element of the effective operation of smart tachographs. Therefore, it is appropriate to ensure their compatibility with the added value services provided by the Galileo programme as set out in Regulation (EU) No 1285/2013 of the European Parliament and of the Council in order to improve the security of the smart tachograph.

(6) In accordance with Articles 8(1), 9(1) and 10(1) and (2) of Regulation (EU) No 165/2014, the security mechanisms introduced by that Regulation should apply 36 months after the entry into force of the necessary implementing acts in order to allow the manufacturers to develop the new generation of smart tachographs, and receive their type-approval certificates from the competent authorities.

(7) In accordance with Regulation (EU) No 165/2014, vehicles registered for the first time in a Member State 36 months after the entry into force of this Commission Regulation, should be equipped with a smart tachograph compliant with the requirements of this Commission Regulation. In any case, all vehicles operating in a Member State other than their Member State of registration should be equipped with a compliant smart tachograph 15 years after the date of application of those requirements.

(8) Commission Regulation (EC) No 68/2009 allowed, during a transitional period expiring on 31 December 2013, the use of an adaptor to make possible the installation of tachographs in M1 and N1 type vehicles. Due to technical difficulties related to finding an alternative to the use of the adaptor, the experts of the automotive and tachograph industry, together with the Commission, concluded that no alternative solution to the adaptor was feasible without entailing high costs for industry, which would be disproportionate to the size of the market. Therefore, the use of the adaptor in M1 and N1 type vehicles should be allowed indefinitely.

(9) The measures provided for in this Regulation are in accordance with the opinion of the Committee referred to in Article 42(3) of Regulation (EU) No 165/2014,

HAS ADOPTED THIS REGULATION:

Article 1 Subject matter and scope

1. This Regulation lays down the provisions necessary for the uniform application of the following aspects regarding tachographs:

(a) recording of the position of the vehicle at certain points during the daily working period of the driver;

(b) remote early detection of possible manipulation or misuse of smart tachographs;

(d) the administrative and technical requirements for the type-approval procedures of tachographs, including the security mechanisms.

2. The construction, testing, installation, inspection, operation and repair of smart tachographs and their components, shall comply with the technical requirements set out in Annex 1C to this Regulation.

3. Tachographs other than smart tachographs shall continue, as regards construction, testing, installation, inspection, operation and repair, to comply with the requirements of either Annex 1 or Annex 1B to Council Regulation (EEC) No 3821/85, as applicable.

4. Pursuant to Article 10d of Directive 96/53/EC, the remote early detection facility shall also transmit the weight data provided by an internal on-board weighing system, for the purpose of early fraud detection.

Article 2 Definitions

For the purposes of this Regulation, the definitions laid down in Article 2 of Regulation (EU) No 165/2014 shall apply. In addition, the following definitions shall apply:

(1) digital tachograph or first generation tachograph means a digital tachograph other than a smart tachograph;

(2) external GNSS facility means a facility which contains the GNSS receiver when the vehicle unit is not a single unit, as well as other components needed to protect the communication of data about position to the rest of the vehicle unit;

(3) information folder means the complete folder, in electronic or paper form, containing all the information supplied by the manufacturer or its agent to the type-approval authority for the purpose of the type-approval of a tachograph or a component thereof, including the certificates referred to in Article 12(3) of Regulation (EU) No 165/2014, the performance of the tests defined in Annex 1C to this Regulation, as well as drawings, photographs, and other relevant documents;

(4) information package means the information folder, in electronic or paper form, accompanied by any other documents added by the type-approval authority to the information folder in the course of carrying out their functions including, at the end of the type-approval process, the EC type-approval certificate of the tachograph or a component thereof;

(5) index to the information package means the document listing the numbered contents of the information package identifying all the relevant parts of this package. The format of that document shall distinguish the successive steps in the EC type-approval process, including the dates of any revisions and updating of that package;

(6) remote early detection facility means the equipment of the vehicle unit which is used to perform targeted roadside checks;

(7) smart tachograph or second generation tachograph means a digital tachograph complying with Articles 8, 9 and 10 of Regulation (EU) No 165/2014 as well as with Annex 1C to this Regulation;

(8) tachograph component or component means any of the following elements: the vehicle unit, the motion sensor, the tachograph card, the record sheet, the external GNSS facility and the remote early detection facility;

(9) type-approval authority means the authority of a Member State competent to carry out the type-approval of the tachograph or of its components, the authorisation process, the issuing and, if appropriate, withdrawing of type-approval certificates, acting as the contact point for the type-approval authorities of other Member States and ensuring that the manufacturers meet their obligations relating to the conformity with the requirement of this Regulation.

Article 3 Location-based services

1. Manufacturers shall ensure that smart tachographs are compatible with the positioning services provided by the Galileo and the European Geostationary Navigation Overlay Service (EGNOS) systems.

2. In addition to the systems referred to in paragraph 1, manufacturers may also choose to ensure compatibility with other satellite navigation systems.

Article 4 Procedure for type-approval of a tachograph and tachograph components

1. A manufacturer or its agent shall submit an application for type-approval of a tachograph or any of its components, or group of components, to the type-approval authorities designated by each Member State. It shall consist of an information folder containing the information for each of the components concerned including, where applicable, the type-approval certificates of other components necessary to complete the tachograph, as well as any other relevant documents.

2. A Member State shall grant type-approval to any tachograph, component or group of components that conforms to the administrative and technical requirements referred to in Article 1(2) or (3), as applicable. In that case, the type-approval authority shall issue to the applicant a type-approval certificate that shall conform to the model laid down in Annex II to this Regulation.

3. The type-approval authority may request the manufacturer or its agent to supply any additional information.

4. The manufacturer or its agent shall make available to the type-approval authorities, as well as to the entities responsible for issuing the certificates referred to in Article 12(3) of Regulation (EU) No 165/2014, as many tachographs or tachograph components as are necessary to enable the type-approval procedure to be conducted satisfactorily.

5. Where the manufacturer or its agent seeks a type-approval of certain components or groups of components of a tachograph, he shall provide the type-approval authorities with the other components, already type-approved, as well as other parts necessary for the construction of the complete tachograph, in order for those authorities to conduct the necessary tests.

Article 5 Modifications to type-approvals

1. The manufacturer or its agent shall inform without delay the type-approval authorities that granted the original type-approval, about any modification in software or hardware of the tachograph or in the nature of the materials used for its manufacture which are recorded in the information package and shall submit an application for the modification of the type-approval.

2. The type-approval authorities may revise or extend an existing type-approval, or issue a new type-approval according to the nature and characteristics of the modifications. A revision shall be made where the type-approval authority considers that the modifications in software or hardware of the tachograph or in the nature of materials used for its manufacture are minor. In such cases, the type-approval authority shall issue the revised documents of the information package, indicating the nature of the modifications made and the date of their approval. An updated version of the information package in a consolidated form, accompanied by a detailed description of the modifications made, shall be sufficient to meet this requirement. An extension shall be made where the type-approval authority considers that the modifications in software or hardware of the tachograph or in the nature of materials used for its manufacture are substantial. In such cases, it may request that new tests be conducted and inform the manufacturer or its agent accordingly. If those tests prove satisfactory, the type-approval authority shall issue a revised type-approval certificate containing a number referring to the extension granted. The type-approval certificate shall mention the reason of the extension and its date of issue.

3. The index to the information package shall indicate the date of the most recent extension or revision of the type-approval, or the date of the most recent consolidation of the updated version of the type-approval.

4. A new type-approval shall be necessary when the requested modifications to the type-approved tachograph or its components would lead to the issuance of a new security or interoperability certificate.

Article 6 Entry into force

This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union. It shall apply from 2 March 2016. However, the Annexes shall apply from 2 March 2019 with the exception of Appendix 16 which shall apply from 2 March 2016.

This Regulation shall be binding in its entirety and directly applicable in all Member States. Done at Brussels, 18 March 2016. For the Commission The President Jean-Claude Juncker

ANNEX

ANNEX I C

Requirements for construction, testing, installation, and inspection INTRODUCTION

The first generation digital tachograph system has been deployed since 1 May 2006. It may be used until its end of life for domestic transportation. For international transportation, instead, 15 years after the entry into force of this Commission Regulation, all vehicles shall be equipped with a compliant second generation smart tachograph, introduced by this Regulation. This Annex contains second generation recording equipment and tachograph cards requirements. Starting from its introduction date, second generation recording equipment shall be installed in vehicles registered for the first time, and second generation tachograph cards shall be issued. In order to foster a smooth introduction of the second generation tachograph system: This will allow drivers to keep their unique driver card and use both systems with it. Second generation recording equipment shall however only be calibrated using second generation workshop cards. This Annex contains all requirements related to the interoperability between the first and the second generation tachograph system. Appendix 15 contains additional details about how the coexistence of the two systems shall be managed.

second generation tachograph cards shall be designed to be also used in first generation vehicle units,

replacement of valid first generation tachograph cards at the introduction date shall not be requested.

1. DEFINITIONS In this Annex:

1.

(a) activation means: the phase in which the tachograph becomes fully operational and implements all functions, including security functions, through the use of a workshop card;

(b) authentication means: a function intended to establish and verify a claimed identity;

(d) built-in test (BIT) means: tests run at request, triggered by the operator or by external equipment;

(e) calendar day means: a day ranging from 00:00 hours to 24:00 hours. All calendar days relate to UTC time (Universal Time Coordinated);

(f) calibration of a smart tachograph means: updating or confirming vehicle parameters to be held in the data memory. Vehicle parameters include vehicle identification (VIN, VRN and registering Member State) and vehicle characteristics (w, k, l, tyre size, speed-limiting device setting (if applicable), current UTC time, current odometer value); during the calibration of a recording equipment, the types and identifiers of all type-approval relevant seals in place shall also be stored in the data memory; any update or confirmation of UTC time only, shall be considered as a time adjustment and not as a calibration, provided it does not contradict Requirement 409; calibrating recording equipment requires the use of a workshop card;

(g) card number means: a 16-alphanumerical character number that uniquely identifies a tachograph card within a Member State. The card number includes a card consecutive index (if applicable), a card replacement index and a card renewal index; a card is therefore uniquely identified by the code of the issuing Member State and the card number;

(h) card consecutive index means: the 14th alphanumerical character of a card number that is used to differentiate the different cards issued to a company, a workshop or a control authority entitled to be issued several tachograph cards. The company, the workshop or the control authority is uniquely identified by the 13 first characters of the card number;

(i) card renewal index means: the 16th alphanumerical character of a card number which is incremented each time a tachograph card is renewed;

(j) card replacement index means: the 15th alpha-numerical character of a card number which is incremented each time a tachograph card is replaced;

(k) characteristic coefficient of the vehicle means: the numerical characteristic giving the value of the output signal emitted by the part of the vehicle linking it with the recording equipment (gearbox output shaft or axle) while the vehicle travels a distance of one kilometre under standard test conditions as defined under requirement 414. The characteristic coefficient is expressed in impulses per kilometre (w = … imp/km);

(l) company card means: a tachograph card issued by the authorities of a Member State to a transport undertaking needing to operate vehicles fitted with a tachograph, which identifies the transport undertaking and allows for the displaying, downloading and printing of the data, stored in the tachograph, which have been locked by that transport undertaking;

(m) constant of the recording equipment means: the numerical characteristic giving the value of the input signal required to show and record a distance travelled of one kilometre; this constant shall be expressed in impulses per kilometre (k = … imp/km);

(n) continuous driving time is computed within the recording equipment as: the continuous driving time is computed as the current accumulated driving times of a particular driver, since the end of his last AVAILABILITY or BREAK/REST or UNKNOWN period of 45 minutes or more (this period may have been split according to Regulation (EC) No 561/2006 of the European Parliament and of the Council). The computations involved take into account, as needed, past activities stored on the driver card. When the driver has not inserted his card, the computations involved are based on the data memory recordings related to the current period where no card was inserted and related to the relevant slot;

(o) control card means: a tachograph card issued by the authorities of a Member State to a national competent control authority which identifies the control body and, optionally, the control officer, and which allows access to the data stored in the data memory or in the driver cards and, optionally, in the workshop cards for reading, printing and/or downloading; It shall also give access to the roadside calibration checking function and to data on the remote early detection communication reader;

(p) cumulative break time is computed within the recording equipment as: the cumulative break from driving time is computed as the current accumulated AVAILABILITY or BREAK/REST or UNKNOWN times of 15 minutes or more of a particular driver, since the end of his last AVAILABILITY or BREAK/REST or UNKNOWN period of 45 minutes or more (this period may have been split according to Regulation (EC) No 561/2006). The computations involved take into account, as needed, past activities stored on the driver card. Unknown periods of negative duration (start of unknown period > end of unknown period) due to time overlaps between two different sets of recording equipment, are not taken into account for the computation. When the driver has not inserted his card, the computations involved are based on the data memory recordings related to the current period where no card was inserted and related to the relevant slot;

(q) data memory means: an electronic data storage device built into the recording equipment;

(r) digital signature means: data appended to, or a cryptographic transformation of, a block of data that allows the recipient of the block of data to prove the authenticity and integrity of the block of data;

(s) downloading means: the copying, together with the digital signature, of a part, or of a complete set, of data files recorded in the data memory of the vehicle unit or in the memory of a tachograph card, provided that this process does not alter or delete any stored data; manufacturers of smart tachograph vehicle units and manufacturers of equipment designed and intended to download data files shall take all reasonable steps to ensure that the downloading of such data can be performed with the minimum delay by transport undertakings or drivers; The downloading of the detailed speed file may not be necessary to establish compliance with Regulation (EC) No 561/2006, but may be used for other purposes such as accident investigation;

(t) driver card means: a tachograph card, issued by the authorities of a Member State to a particular driver, which identifies the driver and allows for the storage of driver activity data;

(u) effective circumference of the wheels means: the average of the distances travelled by each of the wheels moving the vehicle (driving wheels) in the course of one complete rotation. The measurement of these distances shall be made under standard test conditions as defined under requirement 414 and is expressed in the form l = … mm. Vehicle manufacturers may replace the measurement of these distances by a theoretical calculation which takes into account the distribution of the weight on the axles, vehicle unladen in normal running order. The methods for such theoretical calculation are subject to approval by a competent Member State authority and can take place only before tachograph activation;

(v) event means: an abnormal operation detected by the smart tachograph which may result from a fraud attempt;

(w) external GNSS facility means a facility which contains the GNSS receiver when the vehicle unit is not a single unit as well as other components needed to protect the communication of position data to the rest of the vehicle unit;

(x) fault means: abnormal operation detected by the smart tachograph which may come from an equipment malfunction or failure;

(y) GNSS receiver means: an electronic device that receives and digitally processes the signals from one or more Global Navigation Satellite System(s) (GNSS in English) in order to provide position, speed and time information;

(z) installation means: the mounting of a tachograph in a vehicle;

(aa) interoperability means: the capacity of systems and the underlying business processes to exchange data and to share information;

(bb) interface means: a facility between systems which provides the media through which they can connect and interact;

(cc) position means: geographical coordinates of the vehicle at a given time;

(dd) motion sensor means: a part of the tachograph, providing a signal representative of vehicle speed and/or distance travelled;

(ee) non-valid card means: a card detected as faulty, or which initial authentication failed, or whose start of validity date is not yet reached, or whose expiry date has passed;

(ff) open standard means: a standard set out in a standard specification document available freely or at a nominal charge which it is permissible to copy, distribute or use for no fee or for a nominal fee;

(gg) out of scope means: when the use of the recording equipment is not required, according to the provisions of Regulation (EC) No 561/2006;

(hh) over speeding means: exceeding the authorised speed of the vehicle, defined as any period of more than 60 seconds during which the vehicle's measured speed exceeds the limit for setting the speed limitation device laid down in Council Directive 92/6/EEC, as last amended;

(ii) periodic inspection means: a set of operations performed to check that the tachograph works properly, that its settings correspond to the vehicle parameters, and that no manipulation devices are attached to the tachograph;

(jj) printer means: component of the recording equipment which provides printouts of stored data;

(kk) remote early detection communication means: communication between the remote early detection communication facility and the remote early detection communication reader during targeted roadside checks with the aim of remotely detecting possible manipulation or misuse of recording equipment;

(ll) remote communication facility means: the equipment of the vehicle unit which is used to perform targeted roadside checks;

(mm) remote early detection communication reader means: the system used by control officers for targeted roadside checks.

(nn) renewal means: issue of a new tachograph card when an existing card reaches its expiry date, or is malfunctioning and has been returned to the issuing authority. Renewal always implies the certainty that two valid cards do not coexist;

(oo) repair means: any repair of a motion sensor or of a vehicle unit or of a cable that requires the disconnection of its power supply, or its disconnection from other tachograph components, or the opening of the motion sensor or vehicle unit;

(pp) card replacement means: issue of a tachograph card in replacement of an existing card, which has been declared lost, stolen or malfunctioning and has not been returned to the issuing authority. Replacement always implies a risk that two valid cards may coexist;

(qq) security certification means: process to certify, by a common criteria certification body, that the recording equipment (or component) or the tachograph card under investigation fulfils the security requirements defined in the relative protection profiles;

(rr) self test means: tests run cyclically and automatically by the recording equipment to detect faults;

(ss) time measurement means: a permanent digital record of the coordinated universal date and time (UTC);

(tt) time adjustment means: an automatic adjustment of current time at regular intervals and within a maximum tolerance of one minute, or an adjustment performed during calibration;

(uu) tyre size means: the designation of the dimensions of the tyres (external driving wheels) in accordance with Council Directive 92/23/EEC as last amended;

(vv) vehicle identification means: numbers identifying the vehicle: vehicle registration number (VRN) with indication of the registering Member State and vehicle identification number (VIN);

(ww) for computing sake in the recording equipment week means: the period between 00:00 hours UTC on Monday and 24:00 UTC on Sunday;

(xx) workshop card means: a tachograph card issued by the authorities of a Member State to designated staff of a tachograph manufacturer, a fitter, a vehicle manufacturer or a workshop, approved by that Member State, which identifies the cardholder and allows for the testing, calibration and activation of tachographs, and/or downloading from them;

(yy) adaptor means: a device, providing a signal permanently representative of vehicle speed and/or distance travelled, other than the one used for the independent movement detection, and which is: use of such an adaptor in those vehicles described above shall allow for the installation and correct use of a vehicle unit compliant with all the requirements of this Annex, for those vehicles, the smart tachograph includes cables, an adaptor, and a vehicle unit;

installed and used only in M1 and N1 type vehicles (as defined in Annex II to Directive 2007/46/EC of the European Parliament and of the Council, as last amended) put into service since 1 May 2006,

installed where it is not mechanically possible to install any other type of existing motion sensor which is otherwise compliant with the provisions of this Annex and its Appendixes 1 to 15,

installed between the vehicle unit and where the speed/distance impulses are generated by integrated sensors or alternative interfaces,

seen from a vehicle unit, the adaptor behaviour is the same as if a motion sensor, compliant with the provisions of this Annex and its Appendixes 1 to 16, was connected to the vehicle unit;

(zz) data integrity means: the accuracy and consistency of stored data, indicated by an absence of any alteration in data between two updates of a data record. Integrity implies that the data is an exact copy of the original version, e.g. that it has not been corrupted in the process of being written to, and read back from, a tachograph card or a dedicated equipment or during transmission via any communications channel;

(aaa) data privacy means: the overall technical measures taken to ensure the proper implementation of the principles laid down in Directive 95/46/EC of the European Parliament and of the Council as well as of those laid down in Directive 2002/58/EC of the European Parliament and of the Council;

(bbb) smart tachograph system means: the recording equipment, tachograph cards and the set of all directly or indirectly interacting equipment during their construction, installation, use, testing and control, such as cards, remote communication reader and any other equipment for data downloading, data analysis, calibration, generating, managing or introducing security elements, etc.;

(ccc) introduction date: 36 months after the entry into force of the detailed provisions referred to in Article 11 of Regulation (EU) No 165/2014 of the European Parliament and of the Council This is the date after which vehicles registered for the first time:

shall be fitted with a tachograph connected to a positioning service based on a satellite navigation system,

shall be able to communicate data for targeted roadside checks to competent control authorities while the vehicle is in motion,

and may be equipped with standardised interfaces allowing the data recorded or produced by tachographs to be used in operational mode, by an external device.

(ddd) protection profile means: a document used as part of certification process according Common Criteria, providing implementation independent specification of information assurance security requirements;

(eee) GNSS accuracy: in the context of recording the position from a Global Navigation Satellite System (GNSS) with tachographs, means the value of the horizontal dilution of precision (HDOP) calculated as the minimum of the HDOP values collected on the available GNSS systems.

2. GENERAL CHARACTERISTICS AND FUNCTIONS OF THE RECORDING EQUIPMENT

2. 2.1(1)(2)(3)(4)(5)(6)(7)

General characteristics The purpose of the recording equipment is to record, store, display, print, and output data related to driver activities. Any vehicle fitted with the recording equipment complying with the provisions of this Annex, must include a speed display and an odometer. These functions may be included within the recording equipment. The recording equipment includes cables, a motion sensor, and a vehicle unit. The interface between motion sensors and vehicle units shall comply with the requirements specified in Appendix 11. The vehicle unit shall be connected to global navigation satellite system(s), as specified in Appendix 12. The vehicle unit shall communicate with remote early detection communication readers, as specified in Appendix 14. The vehicle unit may include an ITS interface, which is specified in Appendix 13 The recording equipment may be connected to other facilities through additional interfaces and/or through the optional ITS interface. Any inclusion in or connection to the recording equipment of any function, device, or devices, approved or otherwise, shall not interfere with, or be capable of interfering with, the proper and secure operation of the recording equipment and the provisions of this Regulation. Recording equipment users identify themselves to the equipment via tachograph cards. The recording equipment provides selective access rights to data and functions according to user's type and/or identity. The recording equipment records and stores data in its data memory, in the remote communication facility and in tachograph cards. This is done in accordance with Directive 95/46/EC of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data, with Directive 2002/58/EC of 12 July 2002 concerning the processing of personal data and the protection of privacy in the electronic communications sector and in compliance with Article 7 of Regulation (EU) No. 165/2014.

2.2(8) Functions The recording equipment shall ensure the following functions:

monitoring cards insertions and withdrawals,

speed, distance and position measurement,

time measurement,

monitoring driver activities,

monitoring driving status,

drivers manual entries:

entry of places where daily work periods begin and/or end,

manual entry of driver activities,

entry of specific conditions,

company locks management,

monitoring control activities,

detection of events and/or faults,

built-in and self-tests,

reading from data memory,

recording and storing in data memory,

reading from tachograph cards,

recording and storing in tachograph cards,

displaying,

printing,

warning,

data downloading to external media,

remote communication for targeted roadside checks,

output data to additional facilities,

calibration,

roadside calibration check,

time adjustment.

2.3(9)(10)(11)(12)(13)

Modes of operation The recording equipment shall possess four modes of operation: The recording equipment shall switch to the following mode of operation according to the valid tachograph cards inserted into the card interface devices. In order to determine the mode of operation, the tachograph card generation is irrelevant, provided the inserted card is valid. A first generation workshop card shall always be considered as non-valid when it is inserted in a second generation VU. Mode of operation Driver slot No card Driver card Control card Workshop card Company card Co-driver slot No card Operational Operational Control Calibration Company Driver card Operational Operational Control Calibration Company Control card Control Control Control Operational Operational Workshop card Calibration Calibration Operational Calibration Operational Company card Company Company Operational Operational Company The recording equipment shall ignore non-valid cards inserted, except displaying, printing or downloading data held on an expired card which shall be possible. All functions listed in 2.2. shall work in any mode of operation with the following exceptions: The recording equipment can output any data to display, printer or external interfaces with the following exceptions:

operational mode,

control mode,

calibration mode,

company mode.

the calibration function is accessible in the calibration mode only,

the roadside calibration checking function is accessible in the control mode only,

the company locks management function is accessible in the company mode only,

the monitoring of control activities function is operational in the control mode only,

The downloading function is not accessible in the operational mode (except as provided for in requirement 193), and except downloading a driver card when no other card type is inserted into the VU.

in the operational mode, any personal identification (surname and first name(s)) not corresponding to a tachograph card inserted shall be blanked and any card number not corresponding to a tachograph card inserted shall be partially blanked (every odd character — from left to right — shall be blanked),

in the company mode, driver related data (requirements 102, 105 and 108) can be output only for periods where no lock exists or no other company holds a lock (as identified by the first 13 digits of the company card number),

when no card is inserted in the recording equipment, driver related data can be output only for the current and 8 previous calendar days,

personal data originating from the VU shall not be output through ITS interface of the VU unless the consent of the driver to whom the data relates is verified,

the vehicle units have a normal operations validity period of 15 years, starting with the vehicle unit certificates issuing date, but vehicle units can be used for additional 3 months, for data downloading only.

2.4(14) Security The system security aims at protecting the data memory in such a way as to prevent unauthorised access to and manipulation of the data and detecting any such attempts, protecting the integrity and authenticity of data exchanged between the motion sensor and the vehicle unit, protecting the integrity and authenticity of data exchanged between the recording equipment and the tachograph cards, protecting the integrity and authenticity of data exchanged between the recording equipment and the external GNSS facility, protecting the confidentiality, integrity and authenticity of data exchanged through the remote early detection communication for control purposes, and verifying the integrity and authenticity of data downloaded. In order to achieve the system security, the following components shall meet the security requirements specified in their Protection Profiles, as required in Appendix 10:

vehicle unit,

tachograph card,

motion sensor,

external GNSS facility (this Profile is only needed and applicable for the external GNSS variant).

3. CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR RECORDING EQUIPMENT

3. 3.1(15)(16)(17)(18)(19)(20)

Monitoring cards insertion and withdrawal The recording equipment shall monitor the card interface devices to detect card insertions and withdrawals. Upon card insertion the recording equipment shall detect whether the card inserted is a valid tachograph card and in such a case identify the card type and the card generation. If a card with the same card number and a higher renewal index has already been inserted in the recording equipment, the card shall be declared as non-valid. If a card with the same card number and renewal index but with a higher replacement index has already been inserted in the recording equipment, the card shall be declared as non-valid. First generation tachograph cards shall be considered as non-valid by the recording equipment, after the possibility of using first generation tachograph cards has been suppressed by a workshop, in compliance with Appendix 15 (req. MIG003). First generation workshop cards which are inserted in the second generation recording equipment shall be considered as non-valid. The recording equipment shall be so designed that the tachograph cards are locked in position on their proper insertion into the card interface devices. The release of tachograph cards may function only when the vehicle is stopped and after the relevant data have been stored on the cards. The release of the card shall require positive action by the user.

3.2(21)(22)(23)(24)(25)(26)(27)

Speed, position and distance measurement The motion sensor (possibly embedded in the adaptor) is the main source for speed and distance measurement. This function shall continuously measure and be able to provide the odometer value corresponding to the total distance travelled by the vehicle using the pulses provided by the motion sensor. This function shall continuously measure and be able to provide the speed of the vehicle using the pulses provided by the motion sensor. The speed measurement function shall also provide the information whether the vehicle is moving or stopped. The vehicle shall be considered as moving as soon as the function detects more than 1 imp/sec for at least 5 seconds from the motion sensor, otherwise the vehicle shall be considered as stopped. Devices displaying speed (speedometer) and total distance travelled (odometer) installed in any vehicle fitted with a recording equipment complying with the provisions of this Regulation, shall comply with the requirements relating to maximum tolerances (see 3.2.1 and 3.2.2) laid down in this Annex. To detect manipulation of motion data, information from the motion sensor shall be corroborated by vehicle motion information derived from the GNSS receiver and optionally by other source(s) independent from the motion sensor. This function shall measure the position of the vehicle in order to allow for the automatic recording of:

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

positions where the continuous driving time of the driver reaches a multiple of three hours;

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

3.2.1(28)(29)(30)(31)

Measurement of distance travelled The distance travelled may be measured either: The recording equipment shall measure distance from 0 to 9999999,9 km. Distance measured shall be within the following tolerances (distances of at least 1000 m.): Distance measured shall have a resolution better than or equal to 0,1 km.

so as to cumulate both forward and reverse movements, or

so as to include only forward movement.

± 1 % before installation,

± 2 % on installation and periodic inspection,

± 4 % in use.

3.2.2(32)(33)(34)(35)

Measurement of speed The recording equipment shall measure speed from 0 to 220 km/h. To ensure a maximum tolerance on speed displayed of ± 6 km/h in use, and taking into account: the recording equipment shall, for speeds between 20 and 180 km/h, and for characteristic coefficients of the vehicle between 4000 and 25000 imp/km, measure the speed with a tolerance of ± 1 km/h (at constant speed). Note: The resolution of data storage brings an additional tolerance of ± 0,5 km/h to speed stored by the recording equipment. The speed shall be measured correctly within the normal tolerances within 2 seconds of the end of a speed change when the speed has changed at a rate up to 2 m/s2. Speed measurement shall have a resolution better than or equal to 1 km/h.

a ± 2 km/h tolerance for input variations (tyre variations, …),

a ± 1 km/h tolerance in measurements made during installation or periodic inspections,

3.2.3(36)(37)

Measurement of position The recording equipment shall measure the absolute position of the vehicle using the GNSS receiver. The absolute position is measured in geographical coordinates of latitude and longitude in degrees and minutes with a resolution of 1/10 of a minute.

3.3(38)(39)(40)(41)(42)(43)

Time measurement The time measurement function shall measure permanently and digitally provide UTC date and time. UTC date and time shall be used for dating data inside the recording equipment (recordings, data exchange) and for all printouts specified in Appendix 4 Printouts. In order to visualise the local time, it shall be possible to change the offset of the time displayed, in half hour steps. No other offsets than negative or positive multiples of half hours shall be allowed; Time drift shall be within ± 2 seconds per day in type approval conditions, in the absence of any time adjustment. Time measured shall have a resolution better than or equal to 1 second. Time measurement shall not be affected by an external power supply cut-off of less than 12 months in type approval conditions.

3.4(44)(45)(46)(47)(48)(49)(50)(51)(52)(53)

Monitoring driver activities This function shall permanently and separately monitor the activities of one driver and one co-driver. Driver activity shall be DRIVING, WORK, AVAILABILITY or BREAK/REST. It shall be possible for the driver and/or the co-driver to manually select WORK, AVAILABILITY or BREAK/REST. When the vehicle is moving, DRIVING shall be selected automatically for the driver and AVAILABILITY shall be selected automatically for the co-driver. When the vehicle stops, WORK shall be selected automatically for the driver. The first change of activity to REST or AVAILABILITY arising within 120 seconds of the automatic change to WORK due to the vehicle stop shall be assumed to have happened at the time of vehicle stop (therefore possibly cancelling the change to WORK). This function shall output activity changes to the recording functions at a resolution of one minute. Given a calendar minute, if DRIVING is registered as the activity of both the immediately preceding and the immediately succeeding minute, the whole minute shall be regarded as DRIVING. Given a calendar minute that is not regarded as DRIVING according to requirement 051, the whole minute shall be regarded to be of the same type of activity as the longest continuous activity within the minute (or the latest of the equally long activities). This function shall also permanently monitor the continuous driving time and the cumulative break time of the driver.

3.5(54)(55) Monitoring driving status This function shall permanently and automatically monitor the driving status. The driving status CREW shall be selected when two valid driver cards are inserted in the equipment, the driving status SINGLE shall be selected in any other case.

3.6 Driver's entries

3.6 3.6.1(56)(57)(58)(59)(60)

Entry of places where daily work periods begin and/or end This function shall allow for the entry of places where, according to the driver and/or the co-driver, his daily work periods begin and/or end. Places are defined as the country and, in addition where applicable, the region, which are entered or confirmed manually. At the time of a driver card withdrawal, the recording equipment shall prompt the (co-)driver to enter a place where the daily work period ends. The driver shall then enter the current place of the vehicle, which shall be considered as a temporary entry. It shall be possible to input places where daily work periods begin and/or end through commands in the menus. If more than one such input is done within one calendar minute, only the last begin place input and the last end place input done within that time shall be kept recorded.

3.6.2(61) Manual entry of driver activities and driver consent for ITS interface Upon driver (or workshop) card insertion, and only at this time, the recording equipment shall allow manual entries of activities. Manual entries of activities shall be performed using local time and date values of the time zone (UTC offset) currently set for the vehicle unit. At driver or workshop card insertion the cardholder shall be reminded of: At the first insertion of a given driver card or workshop card currently unknown to the vehicle unit, the cardholder shall be invited to express his consent for tachograph related personal data output through the optional ITS interface. At any moment, the driver (resp. workshop) consent can be enabled or disabled through commands in the menu, provided the driver (resp. workshop) card is inserted. It shall be possible to input activities with the following restrictions: It shall be possible to make manual entries, if required, at the first insertion of a previously unused driver (or workshop) card. The procedure for manual entries of activities shall include as many consecutive steps as necessary to set a type, a start time and an end time for each activity. For any part of the time period between last card withdrawal and current card insertion, the cardholder shall have the option not to declare any activity. During the manual entries associated with card insertion and if applicable, the card holder shall have the opportunity to input: If the card holder doesn't enter any place where the work period begins or ended, during the manual entries associated with card insertion, this shall be considered as a declaration that his work period has not changed since the last card withdrawal. The next entry of a place where a previous daily work period ends shall then overwrite the temporary entry made at the last card withdrawal. If a place is entered, it shall be recorded in the relevant tachograph card. Manual entries shall be interrupted if: Additional interruptions are allowed, e.g. a timeout after a certain period of user inactivity. If manual entries are interrupted, the recording equipment shall validate any complete place and activity entries (having either unambiguous place and time, or activity type, begin time and end time) already made. If a second driver or workshop card is inserted while manual entries of activities are in progress for a previously inserted card, the manual entries for this previous card shall be allowed to be completed before manual entries start for the second card. The cardholder shall have the option to insert manual entries according to the following minimum procedure: The procedure shall end when the end time of a manually entered activity equals the card insertion time. The recording equipment may then optionally allow the card holder to modify any activity manually entered, until validation by selection of a specific command. Thereafter, any such modification shall be forbidden.

the date and time of his last card withdrawal;

optionally: the local time offset currently set for the vehicle unit.

Activity type shall be WORK, AVAILABILITY or BREAK/REST;

Start and end times for each activity shall be within the period of the last card withdrawal — current insertion only;

Activities shall not be allowed to overlap mutually in time.

a place where a previous daily work period ended, associated to the relevant time (thus overwriting the entry made at the last card withdrawal),

a place where the current daily work period begins, associated to the relevant time.

the card is withdrawn or,

the vehicle is moving and the card is in the driver slot.

Enter activities manually, in chronological order, for the period last card withdrawal — current insertion.

Begin time of the first activity shall be set to card withdrawal time. For each subsequent entry, the start time shall be preset to immediately follow the end time of the previous entry. Activity type and end time shall be selected for each activity.

3.6.3(62) Entry of specific conditions The recording equipment shall allow the driver to enter, in real time, the following two specific conditions: A FERRY / TRAIN CROSSING may not occur if an OUT OF SCOPE condition is opened. An opened OUT OF SCOPE condition must be automatically closed, by the recording equipment, if a driver card is inserted or withdrawn. An opened OUT OF SCOPE condition shall inhibit the following events and warnings: The FERRY / TRAIN CROSSING begin flag shall be set before shutting down the engine on the ferry/train. An opened FERRY / TRAIN CROSSING must end when any of following options occurs: An opened FERRY/TRAIN CROSSING shall end when it is no longer valid based on the rules stated in Regulation (EC) No. 561/2006.

OUT OF SCOPE (begin, end)

FERRY / TRAIN CROSSING (begin, end).

Driving without an appropriate card,

Warnings associated with continuous driving time.

The driver manually ends the FERRY/TRAIN CROSSING

The driver ejects his card

3.7(63)(64)(65)(66)(67)(68)

Company locks management This function shall allow the management of the locks placed by a company to restrict data access in company mode to itself. Company locks consist in a start date/time (lock-in) and an end date/time (lock-out) associated with the identification of the company as denoted by the company card number (at lock-in). Locks may be turned in or out in real time only. Locking-out shall only be possible for the company whose lock is in (as identified by the first 13 digits of the company card number), or, Locking-out shall be automatic if another company locks in. In the case where a company locks in and where the previous lock was for the same company, then it will be assumed that the previous lock has not been turned out and is still in.

3.8(69)(70) Monitoring control activities This function shall monitor DISPLAYING, PRINTING, VU and card DOWNLOADING, and ROADSIDE CALIBRATION check activities carried while in control mode. This function shall also monitor OVER SPEEDING CONTROL activities while in control mode. An over speeding control is deemed to have happened when, in control mode, the over speeding printout has been sent to the printer or to the display, or when events and faults data have been downloaded from the VU data memory.

3.9(71) Detection of events and/or faults This function shall detect the following events and/or faults:

3.9(71)

3.9.1(72) Insertion of a non-valid card event This event shall be triggered at the insertion of any non-valid card, at the insertion of a driver card already replaced and/or when an inserted valid card expires.

3.9.2(73) Card conflict event This event shall be triggered when any of the valid cards combination noted X in the following table arises: Card conflict Driver slot No card Driver card Control card Workshop card Company card Co-driver slot No card Driver card X Control card X X X Workshop card X X X X Company card X X X

3.9.3(74) Time overlap event This event shall be triggered when the date / time of last withdrawal of a driver card, as read from the card, is later than the current date / time of the recording equipment in which the card is inserted.

3.9.4(75) Driving without an appropriate card event This event shall be triggered for any valid tachograph cards combination noted X in the following table, when driver activity changes to DRIVING, or when there is a change of the mode of operation while driver activity is DRIVING: Driving without an appropriate card Driver slot No (or non-valid) card Driver card Control card Workshop card Company card Co-driver slot No (or non-valid) card X X X Driver card X X X X Control card X X X X X Workshop card X X X X Company card X X X X X

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

3.9.6(77) Last card session not correctly closed event 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(78) Over speeding event This event shall be triggered for each over speeding.

3.9.8(79) Power supply interruption event 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(80) Communication error with the remote communication facility event 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(81) Absence of position information from GNSS receiver event 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(82) Communication error with the external GNSS facility event 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(83) Motion data error event 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.

3.9.13(84) Vehicle motion conflict event This event shall be triggered, 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 and optionally by other independent sources, as specified in Appendix 12. This event shall not be triggered during a ferry/train crossing, an OUT OF SCOPE condition, or when the position information from the GNSS receiver is not available.

3.9.14(85) Security breach attempt event 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(86) Time conflict event This event shall be triggered, while not in calibration mode, when the VU detects a discrepancy of more than 1 minute between the time of the vehicle unit's time measurement function and the time originating from the GNSS receiver. This event is recorded together with the internal clock value of the vehicle unit and comes together with an automatic time adjustment. After a time conflict event has been triggered, the VU will not generate other time conflict events for the next 12 hours. This event shall not be triggered in cases no valid GNSS signal was detectable by the GNSS receiver within the last 30 days. However, when the position information from the GNSS receiver is available again, the automatic time adjustment shall be done.

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

3.9.17(88) Recording equipment fault 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

3.10(89) Built-in and self-tests The recording equipment shall self-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

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

3.12(91)(92) Recording and storing in the data memory For the purpose of this paragraph, 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. The recording equipment shall be able to record and store implicitly or explicitly in its data memory the following:

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 2190 (co-)drivers, 2190 card insertion withdrawal cycles, and 93440 activity changes,

the average number of positions per day is defined as at least 6 positions where the daily work period begins, 6 positions when the driver's continuous driving time reaches a multiple of three hours, and 6 positions where the daily work period ends, so that 365 days include at least 6570 positions,

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.

3.12(91)(92)

3.12.1 Equipment identification data

3.12.1 3.12.1.1(93)(94)

Vehicle unit identification data The recording equipment shall be able to store in its data memory the following vehicle unit identification data: Vehicle unit identification data are recorded and stored once and for all by the vehicle unit manufacturer, except the software related data and the approval number which may be changed in case of software upgrade and the ability to use first generation tachograph cards.

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,

3.12.1.2(95)(96)(97)

Motion sensor identification data The motion sensor shall be able to store in its memory the following identification data: Motion sensor identification data are recorded and stored once and for all in the motion sensor, by the motion sensor manufacturer. The vehicle unit shall be able to record and store in its data memory the following data related to the 20 most recent pairing 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:

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).

motion sensor identification data:

serial number

approval number

motion sensor pairing data:

pairing date.

3.12.1.3(98)(99)(100)

Global Navigation Satellite Systems identification data The external GNSS facility shall be able to store in its memory the following identification data: The identification data are recorded and stored once and for all in the external GNSS facility, by the external GNSS facility manufacturer. The vehicle unit shall be able to record and store in its data memory the following data related to the 20 most recent 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:

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).

external GNSS facility identification data:

serial number,

approval number,

external GNSS facility coupling data:

coupling date

3.12.2(101) Keys and certificates 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(102)(103)(104)

Driver or workshop card insertion and withdrawal data 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 data memory shall be able to hold these data for at least 365 days. When storage capacity is exhausted, new data shall replace oldest data.

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.

3.12.4(105)(106)(107)

Driver activity data 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: 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. The data memory shall be able to hold driver activity data for at least 365 days. When storage capacity is exhausted, new data shall replace oldest data.

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.

3.12.5(108)(109)(110)(111)(112)

Places and positions where daily work periods begin, end, and/or where 3 hours' continuous driving time is reached The recording equipment shall record and store in its data memory: 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. Together with each place or position, the recording equipment shall record and store in its data memory: The data memory shall be able to hold places and positions where daily work periods begin, end and/or where 3 hours continuous driving time is reached for at least 365 days. When storage capacity is exhausted, new data shall replace oldest data.

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

positions where the continuous driving time of the driver reaches a multiple of three hours;

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

the (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 continuous driving time),

the related GNSS accuracy, date and time if applicable;

the vehicle odometer value.

3.12.6(113)(114)(115)

Odometer data The recording equipment shall record in its data memory the vehicle odometer value and the corresponding date at midnight every calendar day. The data memory shall be able to store midnight odometer values for at least 365 calendar days. When storage capacity is exhausted, new data shall replace oldest data.

3.12.7(116) Detailed speed data 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 driven.

3.12.8(117) Events data For the purpose of this subparagraph, time shall be recorded with a resolution of 1 second. 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 Card conflict Driving without an appropriate card Card insertion while driving Last card session not correctly closed Over speeding (1) Power supply interruption (2) Communication error with the remote communication facility Absence of position information from GNSS receiver Motion data error Vehicle motion conflict Security breach attempt Time conflict

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

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.

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.

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

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,

VRN, Member State of registration and VU generation.

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.

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.

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.

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.

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.

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.

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.

the longest event for each of the 10 last days of occurrence,

the 5 longest 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.

3.12.8(117)

(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(118) Faults data For the purpose of this subparagraph, time shall be recorded with a resolution of 1 second. 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 Recording equipment faults

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.

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(119)(120)(121)(122)(123)

Calibration data The recording equipment shall record and store in its data memory data relevant to: The following data shall be recorded for each of these calibrations: 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). The motion sensor shall record and store in its memory the following motion sensor installation data: The external GNSS facility shall record and store in its memory the following external GNSS facility installation data:

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).

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.

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).

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(124)(125)

Time adjustment data 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 following data shall be recorded for each of these time adjustments:

the most recent time adjustment,

the 5 largest 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(126)(127)

Control activity data The recording equipment shall record and store in its data memory the following data relevant to the 20 most recent control activities: In case of downloading, the dates of the oldest and of the most recent days downloaded shall also be recorded.

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).

3.12.13(128) Company locks data The recording equipment shall record and store in its data memory the following data relevant to the 255 most recent company locks: Data previously locked by a lock removed from memory due to the limit above, shall be treated as not locked.

lock-in date and time,

lock-out date and time,

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

company name and address.

3.12.14(129) Download activity data 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(130)(131)

Specific conditions data The recording equipment shall record in its data memory the following data relevant to specific conditions: 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.

date and time of the entry,

type of specific condition.

3.12.16(132)(133)

Tachograph card data 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 recording equipment shall be able to store at least 88 such records.

the tachograph card number and its serial number,

the manufacturer of the tachograph card,

the tachograph card type,

the tachograph card version.

3.13(134)(135)

Reading from tachograph cards The recording equipment shall be able to read from first and second generation tachograph cards, where applicable, the necessary data: This requirement only applies to first generation tachograph cards if their use has not been suppressed by a workshop. 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.

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 cumulated 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.

3.14 Recording and storing on tachograph cards

3.14 3.14.1(136)(137)(138)(139)(140)(141)(142)(143)

Recording and storing in first generation tachograph cards 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. The recording equipment shall set the card session data in the driver or workshop card right after the card insertion. 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. 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. All events not defined for the first generation recording equipment, shall not be stored on the driver and workshop cards. Tachograph cards data update shall be such that, when needed and taking into account card actual storage capacity, most recent data replace oldest data. 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. Before releasing a driver card and after all relevant data have been stored on the card, the recording equipment shall reset the card session data.

3.14.2(144)(145)(146)(147)(148)(149)(150)

Recording and storing in second generation tachograph cards 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 recording equipment shall set the card session data in the driver or workshop card right after the card insertion. 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. 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. Tachograph cards data update shall be such that, when needed and taking into account card actual storage capacity, most recent data replace oldest data. 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. 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.

3.15(151)(152)(153)(154)(155)(156)(157)(158)(159)

Displaying The display shall include at least 20 characters. The minimum character size shall be 5 mm high and 3.5 mm wide. 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). The display shall be provided with adequate non-dazzling lighting. Indications shall be visible from outside the recording equipment. The recording equipment shall be able to display: Additional information may be displayed by the recording equipment, provided that it is clearly distinguishable from information required above. 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. The display shall always be ON when the vehicle is moving. 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.

default data,

data related to warnings,

data related to menu access,

other data requested by a user.

3.15.1(160)(161)(162)(163)(164)

Default display When no other information needs to be displayed, the recording equipment shall display, by default, the following: 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. 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. The recording equipment shall briefly display the card holder name at card insertion. 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).

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.

3.15.2(165) Warning display 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(166) Menu access The recording equipment shall provide necessary commands through an appropriate menu structure.

3.15.4(167)(168)

Other displays It shall be possible to display selectively on request: optional: 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.

the UTC date and time, and local time offset,

the content of any of the six printouts 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 cumulated driving time of the driver for the previous and the current week,

the cumulated driving time of the co-driver for the previous and the current week,

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

the cumulated driving time of the driver for current week,

the cumulated driving time of the co-driver for the current daily work period,

the cumulated driving time of the driver for the current daily work period.

3.16(169)(170)(171)(172)(173)(174)(175)(176)(177)(178)(179)(180)(181)

Printing 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: 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. 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. In order to produce the driver activities from card daily printout or the events and faults from card printout, the recording equipment shall: The printer shall be able to print 24 characters per line. The minimum character size shall be 2.1 mm high and 1.5 mm wide. The printer shall support the characters specified in Appendix 1 Chapter 4 Character sets. Printers shall be so designed as to produce these printouts with a degree of definition likely to avoid any ambiguity when they are read. Printouts shall retain their dimensions and recordings under normal conditions of humidity (10-90 %) and temperature. 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. 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. Printouts shall conform at least to the test specifications defined in Appendix 9. It shall also be possible to add hand-written notes, such as the driver's signature, to these documents. 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.

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)

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.

3.17(182)(183)(184)(185)(186)(187)(188)(189)(190)(191)

Warnings The recording equipment shall warn the driver when detecting any event and/or fault. Warning of a power supply interruption event may be delayed until the power supply is reconnected. The recording equipment shall warn the driver 15 minutes before and at the time of exceeding the maximum allowed continuous driving time. Warnings shall be visual. Audible warnings may also be provided in addition to visual warnings. 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. Visual warnings may be built into the recording equipment and/or remote from the recording equipment. In the latter case it shall bear a T symbol. 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. 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. Additional warnings may be provided, as long as they do not confuse drivers in relation to previously defined ones.

3.18(192)(193)(194)(195)(196)

Data downloading to external media 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. In addition and as an optional feature, the recording equipment may, in any mode of operation, download data through any another means to a company authenticated through this channel. In such a case, company mode data access rights shall apply to this download. Downloading shall not alter or delete any stored data. The calibration/downloading connector electrical interface is specified in Appendix 6. Downloading protocols are specified in Appendix 7.

3.19(197)(198)(199)

Remote communication for targeted roadside checks 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. Data to be checked remotely shall be available to remote communication readers through wireless communication, as specified in Appendix 14. 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.

3.20(200)(201)

Output data to additional external devices The recording equipment may also be equipped with standardised interfaces allowing the data recorded or produced by tachograph to be used in operational or calibration mode, by an external facility. In Appendix 13, an optional ITS interface is specified and standardized. Other similar interfaces may co-exist, provided they fully comply with the requirements of Appendix 13 in term of minimum list of data, security and driver consent. The following requirements apply to ITS data made available through that interface: Other data may also be output in addition to the set of selected existing data, considered as the minimum list, provided they cannot be considered as personal data. The recording equipment shall notify other external facilities about the consent of the driver. When the ignition of the vehicle is ON, these data shall be permanently broadcasted. The serial link interface as specified in Annex 1B to Regulation (EEC) No. 3821/85, as last amended, can continue to equip tachographs for back compatibility. Anyhow, the driver consent is still required in case personal data are transmitted.

these data are a set of selected existing data from the tachograph data dictionary (Appendix 1),

a subset of these selected data are marked personal data,

the subset of personal data is only available if the verifiable consent of the driver, accepting his personal data can leave the vehicle network, is enabled,

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

the set and subset of data will be broadcasted via Bluetooth wireless protocol in the radius of the vehicle cab, with a refresh rate of 1 minute,

the pairing of the external device with the ITS interface will be protected by a dedicated and random PIN of at least 4 digits, recorded in and available through the display of each vehicle unit,

in any circumstances, the presence of the ITS interface cannot disturb or affect the correct functioning and the security of the vehicle unit.

3.21(202)(203)(204)(205)(206)

Calibration The calibration function shall allow: 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. Pairing the motion sensor to the VU shall consist, at least, in: Coupling the external GNSS facility to the VU shall consist, at least, in: The coupling shall be followed by the verification of the GNSS position information. 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.

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.

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.

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,

3.22(207)(208)(209)

Roadside calibration checking 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. This reading shall at least be possible on the vehicle unit display through commands in the menus. 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.

3.23(210)(211)(212)

Time adjustment 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. The time setting of the VU internal clock shall be automatically re-adjusted at intervals of 12 hours maximum. When this delay has expired and the GNSS signal is not available, the time setting shall be done as soon as the VU can access a valid time provided by GNSS receiver, according to the vehicle ignition conditions. The time reference for the automatic time setting of the VU internal clock shall be derived from the GNSS receiver. A time conflict event shall be triggered if the current time deviates more than one (1) minute from the time information provided by the GNSS receiver. The time adjustment function shall also allow for triggered adjustment of the current time, in calibration mode.

3.24(213)(214)(215)(216)(217)(218)

Performance characteristics 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. The tachograph shall be fully operational in the humidity range 10 % to 90 %. The seals used in the smart tachograph shall withstand the same conditions than those applicable to the tachograph components to which they are affixed. The recording equipment shall be protected against over-voltage, inversion of its power supply polarity, and short circuits. Motion sensors shall either: 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.

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.

3.25(219)(220)(221)(222)(223)

Materials 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. For normal conditions of use, all the internal parts of the equipment shall be protected against damp and dust. 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. The recording equipment shall conform to applicable technical specifications related to ergonomic design. The recording equipment shall be protected against accidental damage.

3.26(224)(225)(226)

Markings If the recording equipment displays the vehicle odometer value and speed, the following details shall appear on its display: 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. A descriptive plaque shall be affixed to each separate component of the recording equipment and shall show the following details: 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 equipment's part number.

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.

name and address of the equipment manufacturer,

manufacturer's part number and year of manufacture of the equipment,

equipment serial number,

approval mark for the equipment type.

4. CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR TACHOGRAPH CARDS

4. 4.1(227)(228)(229)(230)(231)(232)(233)(234)(235)(236)(237)

Visible data The front page shall contain: 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. the name of the Member State issuing the card (optional); 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 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 4.b card expiry date 4.c 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) 5. a Driving licence number (at the date of issue of the driver card) — — 5. b Card number 6. Photograph of the driver photograph of the controller (optional) photograph of the fitter (optional)- 7. 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 dates shall be written using a dd/mm/yyyy or dd.mm.yyyy format (day, month, year). The reverse page shall contain: an explanation of the numbered items which appear on the front page of the card; 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. Tachograph cards shall be printed with the following background predominant colours: — driver card white, — control card blue, — workshop card red, — company card yellow. Tachograph cards shall bear at least the following features for protection of the card body against counterfeiting and tampering: 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. Temporary cards referred to in Article 26.4 of Regulation (EU) No. 165/2014 shall comply with the provisions of this Annex.

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.

4.2(238)(239)

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. In order to achieve the system security, the tachograph cards shall meet the security requirements defined in Appendixes 10 and 11. Tachograph cards shall be readable by other equipment such as personal computers.

4.3(240) Standards 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(241)(242)(243)(244)

Environmental and electrical specifications 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. Tachograph cards shall be capable of operating correctly in the humidity range 10 % to 90 %. Tachograph cards shall be capable of operating correctly for a five-year period if used within the environmental and electrical specifications. During operation, tachograph cards shall conform to ECE R10, related to electromagnetic compatibility, and shall be protected against electrostatic discharges.

4.5(245)(246)(247)

Data storage For the purpose of this paragraph, The tachograph cards functions, commands and logical structures, fulfilling data storage requirements are specified in Appendix 2. If not otherwise specified, data storage on tachograph cards shall be organized in such a way, that new data replaces stored oldest data in case the foreseen memory size for the particular records is exhausted. This paragraph specifies minimum storage capacity for the various application data files. Tachograph cards shall be able to indicate to the recording equipment the actual storage capacity of these data files. Any additional data that may be stored on tachograph cards, related to other applications possibly borne by the card, shall be stored in accordance with Directive 95/46/EC and with Directive 2002/58/EC and in compliance with Article 7 of Regulation (EU) No. 165/2014. Each Master File (MF) of any tachograph card shall contain up to five Elementary Files (EF) for card management, application and chip identifications, and two Dedicated Files (DF): The full details of the tachograph cards structure are specified in Appendix 2.

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.

DF Tachograph, which contains the application accessible to first generation vehicle units, which is also present in first generation tachograph cards,

DF Tachograph_G2, which contains the application only accessible to second generation vehicle units, which is only present in second generation tachograph cards.

4.5.1 Elementary files for identification and card management

4.5.2(248) IC card identification Tachograph cards shall be able to store the following smart card identification data:

clock stop,

card serial number (including manufacturing references),

card type approval number,

card personaliser identification (ID),

embedder ID,

IC identifier.

4.5.2(248)

4.5.2.1(249) Chip identification Tachograph cards shall be able to store the following Integrated Circuit (IC) identification data:

IC serial number,

IC manufacturing references.

4.5.2.2(250) DIR (only present in second generation tachograph cards) Tachograph cards shall be able to store the application identification data objects specified in Appendix 2.

4.5.2.3(251) ATR information (conditional, only present in second generation tachograph cards) Tachograph cards shall be able to store the following extended length information data object:

in the case the tachograph card supports extended length fields, the extended length information data object specified in Appendix 2.

4.5.2.4(252) Extended length information (conditional, only present in second generation tachograph cards) Tachograph cards shall be able to store the following extended length information data objects:

in the case the tachograph card supports extended length fields, the extended length information data objects specified in Appendix 2.

4.5.3 Driver card

4.5.3

4.5.3.1 Tachograph application (accessible to first and second generation vehicle units)

4.5.3.1 4.5.3.1.1(253)

Application identification The driver card shall be able to store the following application identification data:

tachograph application identification,

type of tachograph card identification.

4.5.3.1.2(254)

Key and certificates The driver card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A.

4.5.3.1.3(255)

Card identification The driver card shall be able to store the following card identification data:

card number,

issuing Member State, issuing authority name, issue date,

card beginning of validity date, card expiry date.

4.5.3.1.4(256)

Card holder identification The driver card shall be able to store the following card holder identification data:

surname of the holder,

first name(s) of the holder,

date of birth,

preferred language.

4.5.3.1.5(257)(258)

Card download The driver card shall be able to store the following data related to card download: The driver card shall be able to hold one such record.

date and time of last card download (for other purposes than control).

4.5.3.1.6(259)

Driving licence information The driver card shall be able to store the following driving licence data:

issuing Member State, issuing authority name,

driving licence number (at the date of the issue of the card).

4.5.3.1.7(260)(261)(262)

Events data For the purpose of this subparagraph, time shall be stored with a resolution of 1 second. The driver card shall be able to store data related to the following events detected by the recording equipment while the card was inserted: The driver card shall be able to store the following data for these events: Note: For the Time overlap event: Note: For the Last card session not correctly closed event: The driver card shall be able to store data for the six most recent events of each type (i.e. 36 events).

Time overlap (where this card is the cause of the event),

Card insertion while driving (where this card is the subject of the event),

Last card session not correctly closed (where this card is the subject of the event),

Power supply interruption,

Motion data error,

Security breach attempts.

Event code,

Date and time of beginning of the event (or of card insertion if the event was on-going at that time),

Date and time of end of the event (or of card withdrawal if the event was on-going at that time),

VRN and registering Member State of vehicle in which the event happened.

Date and time of beginning of the event shall correspond to the date and time of the card withdrawal from the previous vehicle,

Date and time of end of the event shall correspond to the date and time of card insertion in current vehicle,

Vehicle data shall correspond to the current vehicle raising the event.

date and time of beginning of event shall correspond to the card insertion date and time of the session not correctly closed,

date and time of end of event shall correspond to the card insertion date and time of the session during which the event was detected (current session),

Vehicle data shall correspond to the vehicle in which the session was not correctly closed.

4.5.3.1.8(263)(264)(265)

Faults data For the purpose of this subparagraph, time shall be recorded with a resolution of 1 second. The driver card shall be able to store data related to the following faults detected by the recording equipment while the card was inserted: The driver card shall be able to store the following data for these faults: The driver card shall be able to store data for the twelve most recent faults of each type (i.e. 24 faults).

Card fault (where this card is the subject of the event),

Recording equipment fault.

Fault code,

Date and time of beginning of the fault (or of card insertion if the fault was on-going at that time),

Date and time of end of the fault (or of card withdrawal if the fault was on-going at that time),

VRN and registering Member State of vehicle in which the fault happened.

4.5.3.1.9(266)(267)(268)

Driver activity data The driver card shall be able to store, for each calendar day where the card has been used or for which the driver has entered activities manually, the following data: The driver card memory shall be able to hold driver activity data for at least 28 days (the average activity of a driver is defined as 93 activity changes per day). The data listed under requirements 261, 264 and 266 shall be stored in a way allowing the retrieval of activities in the order of their occurrence, even in case of a time overlap situation.

the date,

a daily presence counter (increased by one for each of these calendar days),

the total distance travelled by the driver during this day,

a driver status at 00:00,

whenever the driver has changed of activity, and/or has changed of driving status, and/or has inserted or withdrawn his card:

the driving status (CREW, SINGLE),

the slot (DRIVER, CO-DRIVER),

the card status (INSERTED, NOT INSERTED),

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

the time of the change.

4.5.3.1.10(269)(270)

Vehicles used data The driver card shall be able to store, for each calendar day where the card has been used, and for each period of use of a given vehicle that day (a period of use includes all consecutive insertion / withdrawal cycle of the card in the vehicle, as seen from the card point of view), the following data: The driver card shall be able to store at least 84 such records.

date and time of first use of the vehicle (i.e. first card insertion for this period of use of the vehicle, or 00h00 if the period of use is on-going at that time),

vehicle odometer value at that time,

date and time of last use of the vehicle, (i.e. last card withdrawal for this period of use of the vehicle, or 23h59 if the period of use is on-going at that time),

vehicle odometer value at that time,

VRN and registering Member State of the vehicle.

4.5.3.1.11(271)(272)

Places where daily work periods start and/or end The driver card shall be able to store the following data related to places where daily work periods begin and/or end, entered by the driver: The driver card memory shall be able to hold at least 42 pairs of such records.

the date and time of the entry (or the date/time related to the entry if the entry is made during the manual entry procedure),

the type of entry (begin or end, condition of entry),

the country and region entered,

the vehicle odometer value.

4.5.3.1.12(273)

Card session data The driver card shall be able to store data related to the vehicle which opened its current session:

date and time the session was opened (i.e. card insertion) with a resolution of one second,

VRN and registering Member State.

4.5.3.1.13(274)(275)

Control activity data The driver card shall be able to store the following data related to control activities: Note: card downloading will only be recorded if performed through a recording equipment. The driver card shall be able to hold one such record.

date and time of the control,

control card number and card issuing Member State,

type of the control (displaying and/or printing and/or VU downloading and/or card downloading (see note)),

Period downloaded, in case of downloading,

VRN and registering Member State of the vehicle in which the control happened.

4.5.3.1.14(276)(277)

Specific conditions data The driver card shall be able to store the following data related to specific conditions entered while the card was inserted (whatever the slot): The driver card shall be able to store at least 56 such records.

Date and time of the entry,

Type of specific condition.

4.5.3.2 Tachograph generation 2 application (not accessible to first generation vehicle unit)

4.5.3.2 4.5.3.2.1(278)

Application identification The driver card shall be able to store the following application identification data:

tachograph application identification,

type of tachograph card identification.

4.5.3.2.2(279)

Keys and certificates The driver card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part B.

4.5.3.2.3(280)

Card identification The driver card shall be able to store the following card identification data:

card number,

issuing Member State, issuing authority name, issue date,

card beginning of validity date, card expiry date.

4.5.3.2.4(281)

Card holder identification The driver card shall be able to store the following card holder identification data:

surname of the holder,

first name(s) of the holder,

date of birth,

preferred language.

4.5.3.2.5(282)(283)

Card download The driver card shall be able to store the following data related to card download: The driver card shall be able to hold one such record.

date and time of last card download (for other purposes than control).

4.5.3.2.6(284)

Driving licence information The driver card shall be able to store the following driving licence data:

issuing Member State, issuing authority name,

driving licence number (at the date of the issue of the card).

4.5.3.2.7(285)(286)(287)

Time overlap (where this card is the cause of the event),

Card insertion while driving (where this card is the subject of the event),

Last card session not correctly closed (where this card is the subject of the event),

Power supply interruption,

Communication error with the remote communication facility,

Absence of position information from GNSS receiver event,

Communication error with the external GNSS facility

Motion data error,

Vehicle motion conflict,

Security breach attempts,

Time conflict.