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) (c. 799)

Please note that the date you requested in the address for this web page is not an actual date upon which a change occurred to this item of legislation. You are being shown the legislation from , which is the first date before then upon which a change was made.

ANNEX I C U.K. Requirements for construction, testing, installation, and inspection

Appendix 2

TACHOGRAPH CARDS SPECIFICATION U.K.

4. TACHOGRAPH CARDS STRUCTURE U.K.

This paragraph specifies the file structures of the Tachograph cards for storage of accessible data.

It does not specify card manufacturer dependent internal structures, such as e.g. file headers, nor storage and handling of data elements needed for internal use only such as ,, or.

TCS_140 A generation 2 tachograph card shall host the Master File MF and a generation 1 and a generation 2 tachograph application of the same type (e.g. driver card applications). U.K.

TCS_141 A tachograph card shall support at least the minimum number of records specified for the corresponding applications and shall not support more records than the maximum number of records specified for the corresponding applications. U.K.

The maximum and minimum numbers of records are specified in this chapter for the different applications.

For the security conditions used in the access rules throughout this chapter please refer to chapter 3.3. In general the access mode ‘read’ denotes the READ BINARY command with even and if supported odd INS byte with the exception of the EF Sensor_Installation_Data on the workshop card, see TCS_156 and TCS_160. The access mode ‘update’ denotes the Update Binary command with even and if supported odd INS byte and the access mode ‘select’ the SELECT command.

4.1. Master File MF U.K.

TCS_142 After its personalisation, the master file MF shall have the following permanent file structure and file access rules: U.K.

Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary. U.K.

The following abbreviation for the security condition is used in this table:

SC1

ALW OR SM-MAC-G2

TCS_143 All EF structures shall be transparent. U.K.

TCS_144 The Master File MF shall have the following data structure: U.K.

TCS_145 The elementary file EF DIR shall contain the following application related data objects: ‘61 08 4F 06 FF 54 41 43 48 4F 61 08 4F 06 FF 53 4D 52 44 54’ U.K.

TCS_146 The elementary file EF ATR/INFO shall be present if the tachograph card indicates in its ATR that it supports extended length fields. In this case the EF ATR/INFO shall contain the extended length information data object (DO‘7F66’) as specified in ISO/IEC 7816-4:2013 clause 12.7.1. U.K.

TCS_147 The elementary file EF Extended_Length shall be present if the tachograph card indicates in its ATR that it supports extended length fields. In this case the EF shall contain the following data object: ‘02 01 xx’ where the value ‘xx’ indicates whether extended length fields are supported for the T = 1 and / or T = 0 protocol. U.K.

The value ‘01’ indicates extended length field support for the T = 1 protocol.

The value ‘10’ indicates extended length field support for the T = 0 protocol.

The value ‘11’ indicates extended length field support for the T = 1 and the T = 0 protocol.

4.2. Driver card applications U.K.

4.2.1 Driver card application generation 1 U.K.

TCS_148 After its personalisation, the driver card application generation 1 shall have the following permanent file structure and file access rules: U.K.

The following abbreviations for the security conditions are used in this table:

SC1

ALW OR SM-MAC-G2

SC2

ALW OR SM-MAC-G1 OR SM-MAC-G2

SC3

SM-MAC-G1 OR SM-MAC-G2

TCS_149 All EF structures shall be transparent. U.K.

TCS_150 The driver card application generation 1 shall have the following data structure: U.K.

TCS_151 The following values, used to provide sizes in the table above, are the minimum and maximum record number values the driver card data structure must use for a generation 1 application: U.K.

4.2.2 Driver card application generation 2 U.K.

TCS_152 After its personalisation, the driver card application generation 2 shall have the following permanent file structure and file access rules. U.K.

Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary. U.K.

The following abbreviation for the security condition is used in this table:

SC1

ALW OR SM-MAC-G2

TCS_153 All EF structures shall be transparent. U.K.

TCS_154 The driver card application generation 2 shall have the following data structure: U.K.

TCS_155 The following values, used to provide sizes in the table above, are the minimum and maximum record number values the driver card data structure must use for a generation 2 application: U.K.

4.3. Workshop card applications U.K.

4.3.1 Workshop card application generation 1 U.K.

TCS_156 After its personalisation, the workshop card application generation 1 shall have the following permanent file structure and file access rules: U.K.

The following abbreviations for the security conditions are used in this table:

SC1

ALW OR SM-MAC-G2

SC2

ALW OR SM-MAC-G1 OR SM-MAC-G2

SC3

SM-MAC-G1 OR SM-MAC-G2

[F1 SC4

For the READ BINARY command with even INS byte:

• (SM-C-MAC-G1 AND SM-R-ENC-MAC-G1) OR

• (SM-C-MAC-G2 AND SM-R-ENC-MAC-G2)

• For the READ BINARY command with odd INS byte (if supported): NEV]

Textual Amendments

F1 Substituted by Commission Implementing Regulation (EU) 2018/502 of 28 February 2018 amending Implementing Regulation (EU) 2016/799 laying down the requirements for the construction, testing, installation, operation and repair of tachographs and their components (Text with EEA relevance).

TCS_157 All EF structures shall be transparent. U.K.

TCS_158 The workshop card application generation 1 shall have the following data structure: U.K.

TCS_159 The following values, used to provide sizes in the table above, are the minimum and maximum record number values the workshop card data structure must use for a generation 1 application: U.K.

4.3.2 Workshop card application generation 2 U.K.

TCS_160 After its personalisation, the workshop card application generation 2 shall have the following permanent file structure and file access rules. U.K.

Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary. U.K.

The following abbreviations for the security conditions are used in this table:

SC1

ALW OR SM-MAC-G2

SC5

For the Read Binary command with even INS byte: SM-C-MAC-G2 AND SM-R-ENC-MAC-G2

For the Read Binary command with odd INS byte (if supported): NEV

TCS_161 All EFs structures shall be transparent. U.K.

TCS_162 The workshop card application generation 2 shall have the following data structure: U.K.

TCS_163 The following values, used to provide sizes in the table above, are the minimum and maximum record number values the workshop card data structure must use for a generation 2 application: U.K.

4.4. Control card applications U.K.

4.4.1 Control Card application generation 1 U.K.

TCS_164 After its personalisation, the control card application generation 1 shall have the following permanent file structure and file access rules: U.K.

The following abbreviations for the security conditions are used in this table:

SC1

ALW OR SM-MAC-G2

SC2

ALW OR SM-MAC-G1 OR SM-MAC-G2

SC3

SM-MAC-G1 OR SM-MAC-G2

SC6

EXT-AUT-G1 OR SM-MAC-G1 OR SM-MAC-G2

TCS_165 All EF structures shall be transparent. U.K.

TCS_166 The control card application generation 1 shall have the following data structure: U.K.

TCS_167 The following values, used to provide sizes in the table above, are the minimum and maximum record number values the control card data structure must use for a generation 1 application: U.K.

4.4.2 Control card application generation 2 U.K.

TCS_168 After its personalisation, the control card application generation 2 shall have the following permanent file structure and file access rules. U.K.

Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary. U.K.

The following abbreviation for the security condition is used in this table:

SC1

ALW OR SM-MAC-G2

TCS_169 All EF structures shall be transparent. U.K.

TCS_170 The control card application generation2 shall have the following data structure: U.K.

TCS_171 The following values, used to provide sizes in the table above, are the minimum and maximum record number values the control card data structure must use for a generation 2 application: U.K.

4.5. Company card applications U.K.

4.5.1 Company card application generation 1 U.K.

TCS_172 After its personalisation, the company card application generation 1 shall have the following permanent file structure and file access rules: U.K.

The following abbreviations for the security conditions are used in this table:

SC1

ALW OR SM-MAC-G2

SC2

ALW OR SM-MAC-G1 OR SM-MAC-G2

SC3

SM-MAC-G1 OR SM-MAC-G2

SC6

EXT-AUT-G1 OR SM-MAC-G1 OR SM-MAC-G2

TCS_173 All EF structures shall be transparent. U.K.

TCS_174 The company card application generation 1 shall have the following data structure: U.K.

TCS_175 The following values, used to provide sizes in the table above, are the minimum and maximum record number values the company card data structure must use for a generation 1 application: U.K.

4.5.2 Company card application generation 2 U.K.

TCS_176 After its personalisation, the company card application generation 2 shall have the following permanent file structure and file access rules. U.K.

Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary. U.K.

The following abbreviation for the security condition is used in this table:

SC1

ALW OR SM-MAC-G2

TCS_177 All EF structures shall be transparent. U.K.

TCS_178 The company card application generation 2 shall have the following data structure: U.K.

TCS_179 The following values, used to provide sizes in the table above, are the minimum and maximum record number values the company card data structure must use for a generation 2 application: U.K.