- Latest available (Revised)
- Point in Time (31/01/2020)
- Original (As adopted by EU)
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)
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.
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.).
Point in time view as at 31/01/2020.
There are outstanding changes not yet made to Commission Implementing Regulation (EU) 2016/799. Any changes that have already been made to the legislation appear in the content and are referenced with annotations.
Changes and effects yet to be applied by the editorial team are only applicable when viewing the latest version or prospective version of legislation. They are therefore not accessible when viewing legislation as at a specific point in time. To view the ‘Changes to Legislation’ information for this provision return to the latest version view using the options provided in the ‘What Version’ box above.
This command variant enables the IFD to read data from an EF with 32 768 bytes or more.
Byte | Length | Value | Description |
---|---|---|---|
CLA | 1 | ‘00h’ | |
INS | 1 | ‘B1h’ | Read Binary |
P1 | 1 | ‘00h’ | Current EF |
P2 | 1 | ‘00h’ | |
Lc | 1 | ‘NNh’ | Lc Length of offset data object. |
#6-#(5+NN) | NN | ‘XX..XXh’ | Offset data object: Tag ‘54h’ Length ‘01h’ or ‘02h’ Value offset |
[F1Le | 1 | 'XXh' | As specified in ISO/IEC 7816-4] |
The IFD shall encode the offset data object's length with a minimum possible number of octets, i.e. using the length byte ‘01h’ the IFD shall encode an offset from 0 to 255 and using the length byte ‘02h’ an offset from ‘256’ up to ‘65 535’ bytes.
[F2In case of T = 0 the card assumes the value Le = ‘ 00h ’ if no secure messaging is applied.
Textual Amendments
In case of T = 1 the processing state returned is ‘ 6700 ’ if Le= ‘ 01h ’ .]
Byte | Length | Value | Description |
---|---|---|---|
#1-#L | L | ‘XX..XXh’ | Data read encapsulated in a discretionary data object with tag ‘53h’. |
SW | 2 | ‘XXXXh’ | Status Words (SW1,SW2) |
If the command is successful, the card returns ‘9000’.
If no EF is selected, the processing state returned is ‘6986’.
If the security conditions of the selected file are not satisfied, the command is interrupted with ‘6982’.
If the Offset is not compatible with the size of the EF (Offset > EF size), the processing state returned is ‘6B00’.
If the size of the data to be read is not compatible with the size of the EF (Offset + Le > EF size) the processing state returned is ‘6700’ or ‘6Cxx’ where ‘xx’ indicates the exact length.
[F1If an integrity error is detected within the file attributes, the card shall consider the file as corrupted and unrecoverable, the processing state returned is ‘ 6400 ’ or ‘ 6500 ’.]
If an integrity error is detected within the stored data, the card shall return the demanded data, and the processing state returned is ‘6281’.
The following example illustrates the usage of secure messaging if the security condition SM-MAC-G2 applies.
Byte | Length | Value | Description |
---|---|---|---|
CLA | 1 | ‘0Ch’ | Secure Messaging asked |
INS | 1 | ‘B1h’ | Read Binary |
P1 | 1 | ‘00h’ | Current EF |
P2 | 1 | ‘00h’ | |
Lc | 1 | ‘XXh’ | Length of the secured data field |
#6 | 1 | ‘B3h’ | Tag for plain value data encoded in BER-TLV |
#7 | 1 | ‘NNh’ | LPV: length of transmitted data |
#(8)-#(7+NN) | NN | ‘XX..XXh’ | Plain Data encoded in BER-TLV, i.e. the offset data object with tag ‘54’ |
#(8+NN) | 1 | ‘97h’ | TLE: Tag for expected length specification. |
#(9+NN) | 1 | ‘01h’ | LLE: Length of expected length |
#(10+NN) | 1 | ‘XXh’ | Expected length specification (original Le): Number of bytes to be read |
#(11+NN) | 1 | ‘8Eh’ | TCC: Tag for cryptographic checksum |
#(12+NN) | 1 | ‘XXh’ | LCC: Length of following cryptographic checksum ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B) |
#(13+NN)-#(12+M+NN) | M | ‘XX..XXh’ | Cryptographic checksum |
Le | 1 | ‘00h’ | As specified in ISO/IEC 7816-4 |
Byte | Length | Value | Description |
---|---|---|---|
#1 | 1 | ‘B3h’ | Plain Data encoded in BER-TLV |
#2 | L | ‘NNh’ or ‘81 NNh’ | LPV: length of returned data (=original Le). L is 2 bytes if LPV>127 bytes. |
#(2+L)-#(1+L+NN) | NN | ‘XX..XXh’ | Plain Data value encoded in BER-TLV, i.e. data read encapsulated in a discretionary data object with tag ‘53h’. |
#(2+L+NN) | 1 | ‘99h’ | Processing Status of the unprotected response APDU |
#(3+L+NN) | 1 | ‘02h’ | Length of Processing Status |
#(4+L+NN) — #(5+L+NN) | 2 | ‘XX XXh’ | Processing Status of the unprotected response APDU |
#(6+L+NN) | 1 | ‘8Eh’ | TCC: Tag for cryptographic checksum |
#(7+L+NN) | 1 | ‘XXh’ | LCC: Length of following cryptographic checksum ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B) |
#(8+L+NN)-#(7+M+L+NN) | M | ‘XX..XXh’ | Cryptographic checksum |
SW | 2 | ‘XXXXh’ | Status Words (SW1,SW2) |
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?
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?
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.
Point in Time: This becomes available after navigating to view revised legislation as it stood at a certain point in time via Advanced Features > Show Timeline of Changes or via a point in time advanced search.
Geographical Extent: Indicates the geographical area that this provision applies to. For further information see ‘Frequently Asked Questions’.
Show Timeline of Changes: See how this legislation has or could change over time. Turning this feature on will show extra navigation options to go to these specific points in time. Return to the latest available version by using the controls above in the What Version box.
Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:
This timeline shows the different versions taken from EUR-Lex before exit day and during the implementation period as well as any subsequent versions created after the implementation period as a result of changes made by UK legislation.
The dates for the EU versions are taken from the document dates on EUR-Lex and may not always coincide with when the changes came into force for the document.
For any versions created after the implementation period as a result of changes made by UK legislation the date will coincide with the earliest date on which the change (e.g an insertion, a repeal or a substitution) that was applied came into force. For further information see our guide to revised legislation on Understanding Legislation.
Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:
Click 'View More' or select 'More Resources' tab for additional information including: