- Latest available (Revised)
- Original (As adopted by EU)
Commission Implementing Regulation (EU) 2016/799Show full title
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)
You are here:
What Version
More Resources
Revised version PDFs
- Revised 26/02/202011.25 MB
- Revised 17/04/201810.62 MB
- Revised 26/05/20169.89 MB
Legislation originating from the EU
When the UK left the EU, legislation.gov.uk published EU legislation that had been published by the EU up to IP completion day (31 December 2020 11.00 p.m.). On legislation.gov.uk, these items of legislation are kept up-to-date with any amendments made by the UK since then.
This item of legislation originated from the EU
Legislation.gov.uk publishes the UK version. EUR-Lex publishes the EU version. The EU Exit Web Archive holds a snapshot of EUR-Lex’s version from IP completion day (31 December 2020 11.00 p.m.).
Status:
This is the original version as it was originally adopted in the EU.
This legislation may since have been updated - see the latest available (revised) version
4.TACHOGRAPH CARDS STRUCTURE
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
TCS_140A 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).
TCS_141A 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.
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
TCS_142After its personalisation, the master file MF shall have the following permanent file structure and file access rules:
Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.
The following abbreviation for the security condition is used in this table:
SC1
ALW OR SM-MAC-G2
TCS_143All EF structures shall be transparent.
TCS_144The Master File MF shall have the following data structure:
TCS_145The 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’
TCS_146The 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.
TCS_147The 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.
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
4.2.1 Driver card application generation 1
TCS_148After its personalisation, the driver card application generation 1 shall have the following permanent file structure and file access rules:
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_149All EF structures shall be transparent.
TCS_150The driver card application generation 1 shall have the following data structure:
TCS_151The 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:
4.2.2 Driver card application generation 2
TCS_152After its personalisation, the driver card application generation 2 shall have the following permanent file structure and file access rules.
Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.
The following abbreviation for the security condition is used in this table:
SC1
ALW OR SM-MAC-G2
TCS_153All EF structures shall be transparent.
TCS_154The driver card application generation 2 shall have the following data structure:
TCS_155The 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:
4.3. Workshop card applications
4.3.1 Workshop card application generation 1
TCS_156After its personalisation, the workshop card application generation 1 shall have the following permanent file structure and file access rules:
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
SC4
For the READ BINARYcommand with even INS byte:
(PLAIN-C AND SM-R-ENC-G1) OR (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
TCS_157All EF structures shall be transparent.
TCS_158The workshop card application generation 1 shall have the following data structure:
TCS_159The 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:
4.3.2 Workshop card application generation 2
TCS_160After its personalisation, the workshop card application generation 2 shall have the following permanent file structure and file access rules.
Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.
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_161All EFs structures shall be transparent.
TCS_162The workshop card application generation 2 shall have the following data structure:
TCS_163The 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:
4.4. Control card applications
4.4.1 Control Card application generation 1
TCS_164After its personalisation, the control card application generation 1 shall have the following permanent file structure and file access rules:
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_165All EF structures shall be transparent.
TCS_166The control card application generation 1 shall have the following data structure:
TCS_167The 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:
4.4.2 Control card application generation 2
TCS_168After its personalisation, the control card application generation 2 shall have the following permanent file structure and file access rules.
Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.
The following abbreviation for the security condition is used in this table:
SC1
ALW OR SM-MAC-G2
TCS_169All EF structures shall be transparent.
TCS_170The control card application generation2 shall have the following data structure:
TCS_171The 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:
4.5. Company card applications
4.5.1 Company card application generation 1
TCS_172After its personalisation, the company card application generation 1 shall have the following permanent file structure and file access rules:
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_173All EF structures shall be transparent.
TCS_174The company card application generation 1 shall have the following data structure:
TCS_175The 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:
4.5.2 Company card application generation 2
TCS_176After its personalisation, the company card application generation 2 shall have the following permanent file structure and file access rules.
Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.
The following abbreviation for the security condition is used in this table:
SC1
ALW OR SM-MAC-G2
TCS_177All EF structures shall be transparent.
TCS_178The company card application generation 2 shall have the following data structure:
TCS_179The 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:
Options/Help
Print Options
PrintThe Whole Regulation
PrintThe Whole Annex
PrintThis Division only
You have chosen to open the Whole Regulation
The Whole Regulation you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.
Would you like to continue?
You have chosen to open Schedules only
The Schedules you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.
Would you like to continue?
Legislation is available in different versions:
Latest Available (revised):The latest available updated version of the legislation incorporating changes made by subsequent legislation and applied by our editorial team. Changes we have not yet applied to the text, can be found in the ‘Changes to Legislation’ area.
Original (As adopted by EU): The original version of the legislation as it stood when it was first adopted in the EU. No changes have been applied to the text.
Opening Options
Different options to open legislation in order to view more content on screen at once
More Resources
Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:
- the original print PDF of the as adopted version that was used for the EU Official Journal
- lists of changes made by and/or affecting this legislation item
- all formats of all associated documents
- correction slips
- links to related legislation and further information resources
More Resources
Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:
- the original print PDF of the as adopted version that was used for the print copy
- correction slips
Click 'View More' or select 'More Resources' tab for additional information including:
- lists of changes made by and/or affecting this legislation item
- confers power and blanket amendment details
- all formats of all associated documents
- links to related legislation and further information resources
All content is available under the Open Government Licence v3.0 except where otherwise stated. This site additionally contains content derived from EUR-Lex, reused under the terms of the Commission Decision 2011/833/EU on the reuse of documents from the EU institutions. For more information see the EUR-Lex public statement on re-use.