- Y Diweddaraf sydd Ar Gael (Diwygiedig)
- Gwreiddiol (Fel y’i mabwysiadwyd gan yr UE)
Commission Implementing Regulation (EU) 2016/799Dangos y teitl llawn
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:
Pa Fersiwn
Nodweddion Uwch
- Dangos Graddfa Ddaearyddol(e.e. Lloegr, Cymru, Yr Alban aca Gogledd Iwerddon)
- Dangos Llinell Amser Newidiadau
Rhagor o Adnoddau
PDF o Fersiynau Diwygiedig
- ddiwygiedig 26/02/202011.25 MB
- ddiwygiedig 17/04/201810.62 MB
- ddiwygiedig 26/05/20169.89 MB
Mae hwn yn Rheoliad sy’n deillio o’r UE
Mae hon yn eitem o ddeddfwriaeth sy’n deillio o’r UE
Mae unrhyw newidiadau sydd wedi cael eu gwneud yn barod gan y tîm yn ymddangos yn y cynnwys a chyfeirir atynt gydag anodiadau.Ar ôl y diwrnod ymadael bydd tair fersiwn o’r ddeddfwriaeth yma i’w gwirio at ddibenion gwahanol. Y fersiwn legislation.gov.uk yw’r fersiwn sy’n weithredol yn y Deyrnas Unedig. Y Fersiwn UE sydd ar EUR-lex ar hyn o bryd yw’r fersiwn sy’n weithredol yn yr UE h.y. efallai y bydd arnoch angen y fersiwn hon os byddwch yn gweithredu busnes yn yr UE.
Y fersiwn yn yr archif ar y we yw’r fersiwn swyddogol o’r ddeddfwriaeth fel yr oedd ar y diwrnod ymadael cyn cael ei chyhoeddi ar legislation.gov.uk ac unrhyw newidiadau ac effeithiau a weithredwyd yn y Deyrnas Unedig wedyn. Mae’r archif ar y we hefyd yn cynnwys cyfraith achos a ffurfiau mewn ieithoedd eraill o EUR-Lex.
Changes over time for: Division 3.5.3
Changes to legislation:
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 to Legislation
Revised legislation carried on this site may not be fully up to date. Changes and effects are recorded by our editorial team in lists which can be found in the ‘Changes to Legislation’ area. Where those effects have yet to be applied to the text of the legislation by the editorial team they are also listed alongside the legislation in the affected provisions. Use the ‘more’ link to open the changes and effects relevant to the provision you are viewing.
Newidiadau ac effeithiau heb eu gweithredu eto ar yr eitem ddeddfwriaeth gyfan a’r darpariaethau cysylltiedig.
- Signature words omitted by S.I. 2019/453 reg. 110
- Annex 1C modified by S.I. 2023/739 reg. 3 Sch.
3.5.3 UPDATE BINARY U.K.
This command is compliant with ISO/IEC 7816-4, but has a restricted usage compared to the command defined in the norm.
The UPDATE BINARY command message initiates the update (erase + write) of the bits already present in an EF binary with the bits given in the command APDU.
3.5.3.1 Command with offset in P1-P2 U.K.
This command enables the IFD to write data into the EF currently selected, without the card verifying the integrity of data received.
Note: This command without secure messaging can only be used to update a file that supports the ALW security condition for the Update access mode.U.K.
TCS_56 Command Message U.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| CLA | 1 | ‘00h’ | |
| INS | 1 | ‘D6h’ | Update Binary |
| P1 | 1 | ‘XXh’ | Offset in bytes from the beginning of the file: Most Significant Byte |
| P2 | 1 | ‘XXh’ | Offset in bytes from the beginning of the file: Least Significant Byte |
| Lc | 1 | ‘NNh’ | Lc Length of data to Update. Number of bytes to be written. |
| #6-#(5+NN) | NN | ‘XX..XXh’ | Data to be written |
Note: bit 8 of P1 must be set to 0.U.K.
TCS_57 Response Message U.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| 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 written is not compatible with the size of the EF (Offset + Lc > EF size) the processing state returned is ‘6700’.
If 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 writing is unsuccessful, the processing state returned is ‘6581’.
3.5.3.1.1 Command with secure messaging (examples) U.K.
This command enables the IFD to write data into the EF currently selected, with the card verifying the integrity of data received. As no confidentiality is required, the data are not encrypted.
TCS_58 Command Message U.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| CLA | 1 | ‘0Ch’ | Secure Messaging asked |
| INS | 1 | ‘D6h’ | Update Binary |
| P1 | 1 | ‘XXh’ | Offset in bytes from the beginning of the file: Most Significant Byte |
| P2 | 1 | ‘XXh’ | Offset in bytes from the beginning of the file: Least Significant Byte |
| Lc | 1 | ‘XXh’ | Length of the secured data field |
| #6 | 1 | ‘81h’ | TPV: Tag for plain value data |
| #7 | L | ‘NNh’ or ‘81 NNh’ | LPV: length of transmitted data. L is 2 bytes if LPV > 127 bytes. |
| #(7+L)-#(6+L+NN) | NN | ‘XX..XXh’ | Plain Data value (Data to be written) |
| #(7+L+NN) | 1 | ‘8Eh’ | TCC: Tag for cryptographic checksum |
| #(8+L+NN) | 1 | ‘XXh’ | LCC: Length of following cryptographic checksum‘04h’ for Generation 1 secure messaging (see Appendix 11 Part A) ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B) |
| #(9+L+NN)-#(8+M+L+NN) | M | ‘XX..XXh’ | Cryptographic checksum |
| Le | 1 | ‘00h’ | As specified in ISO/IEC 7816-4 |
TCS_59 Response message if correct Secure Messaging input format U.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| #1 | 1 | ‘99h’ | TSW: Tag for Status Words (to be protected by CC) |
| #2 | 1 | ‘02h’ | LSW: length of returned Status Words |
| #3-#4 | 2 | ‘XXXXh’ | Processing Status of the unprotected response APDU |
| #5 | 1 | ‘8Eh’ | TCC: Tag for cryptographic checksum |
| #6 | 1 | ‘XXh’ | LCC: Length of following cryptographic checksum
|
| #7-#(6+L) | L | ‘XX..XXh’ | Cryptographic checksum |
| SW | 2 | ‘XXXXh’ | Status Words (SW1,SW2) |
The ‘regular’ processing states, described for the UPDATE BINARY command with no secure messaging (see §3.5.3.1), can be returned using the response message structure described above.
Additionally, some errors specifically related to secure messaging can happen. In that case, the processing state is simply returned, with no secure messaging structure involved:
TCS_60 Response Message if error in secure messaging U.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| SW | 2 | ‘XXXXh’ | Status Words (SW1,SW2) |
If no current session key is available, the processing state ‘6A88’ is returned.
If some expected data objects (as specified above) are missing in the secure messaging format, the processing state ‘6987’ is returned: this error happens if an expected tag is missing or if the command body is not properly constructed.
If some data objects are incorrect, the processing state returned is ‘6988’: this error happens if all the required tags are present but some lengths are different from the ones expected.
If the verification of the cryptographic checksum fails, the processing state returned is ‘6688’.
3.5.3.2 Command with short EF identifier U.K.
This command variant enables the IFD to select an EF by means of a short EF identifier and write data from this EF.
TCS_61A tachograph card shall support this command variant for all Elementary Files with a specified short EF identifier. These short EF identifiers are specified in chapter 4.U.K.
TCS_62 Command Message U.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| CLA | 1 | ‘00h’ | |
| INS | 1 | ‘D6h’ | Update Binary |
| P1 | 1 | ‘XXh’ | Bit 8 is set to 1 Bit 7 and 6 are set to 00 Bit 5 — 1 encode the short EF identifier of the corresponding EF |
| P2 | 1 | ‘XXh’ | Encodes an offset from 0 to 255 bytes in the EF referenced by P1 |
| Lc | 1 | ‘NNh’ | Lc Length of data to Update. Number of bytes to be written. |
| #6-#(5+NN) | NN | ‘XX..XXh’ | Data to be written |
TCS_63 Response Message U.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| SW | 2 | ‘XXXXh’ | Status Words (SW1,SW2) |
Note: The short EF identifiers used for the generation 2 tachograph application are specified in chapter 4.U.K.
If P1 encodes a short EF identifier and the command is successful, the identified EF becomes the currently selected EF (current EF).
If the command is successful, the card returns ‘9000’.
If the file corresponding with the short EF identifier is not found, the processing state returned is ‘6A82’.
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 written is not compatible with the size of the EF (Offset + Lc > EF size) the processing state returned is ‘6700’.
[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 writing is unsuccessful, the processing state returned is ‘6581’.
Textual Amendments
3.5.3.3 Command with odd instruction byte U.K.
This command variant enables the IFD to write data to an EF with 32 768 bytes or more.
TCS_64A tachograph card which supports EFs with 32 768 bytes or more shall support this command variant for these EFs. A tachograph card may or may not support this command variant for other EFs.U.K.
TCS_65 Command Message U.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| CLA | 1 | ‘00h’ | |
| INS | 1 | ‘D7h’ | Update Binary |
| P1 | 1 | ‘00h’ | Current EF |
| P2 | 1 | ‘00h’ | |
| Lc | 1 | ‘NNh’ | Lc Length of data in the command data field |
| #6-#(5+NN) | NN | ‘XX..XXh’ | Offset data object with tag ‘54h’ || Discretionary data object with tag ‘53h’ that encapsulates the data to be written |
The IFD shall encode the offset data object's and the discretionary data object's length with the minimum possible number of octets, i.e. using the length byte ‘01h’ the IFD shall encode an offset / length from 0 to 255 and using the length byte ‘02h’ an offset / length from ‘256’ up to ‘65 535’ bytes.
TCS_66 Response Message U.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| 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 written is not compatible with the size of the EF (Offset + Lc > EF size) the processing state returned is ‘6700’.
If 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 writing is unsuccessful, the processing state returned is ‘6581’.
3.5.3.3.1 Command with secure messaging (example) U.K.
The following example illustrates the usage of secure messaging if the security condition SM-MAC-G2 applies.
TCS_67Command messageU.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| CLA | 1 | ‘0Ch’ | Secure Messaging asked |
| INS | 1 | ‘D7h’ | Update 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 | L | ‘NNh’ or ‘81 NNh’ | LPV: length of transmitted data. L is 2 bytes if LPV > 127 bytes. |
| #(7+L)-#(6+L+NN) | NN | ‘XX..XXh’ | Plain Data encoded in BER-TLV, i.e. offset data object with tag ‘54h’ || Discretionary data object with tag ‘53h’ that encapsulates the data to be written |
| #(7+L+NN) | 1 | ‘8Eh’ | TCC: Tag for cryptographic checksum |
| #(8+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) |
| #(9+L+NN)-#(8+M+L+NN) | M | ‘XX..XXh’ | Cryptographic checksum |
| Le | 1 | ‘00h’ | As specified in ISO/IEC 7816-4 |
TCS_68Response message if the command is successfulU.K.
| Byte | Length | Value | Description |
|---|---|---|---|
| #1 | 1 | ‘99h’ | TSW: Tag for Status Words (to be protected by CC) |
| #2 | 1 | ‘02h’ | LSW: length of returned Status Words |
| #3-#4 | 2 | ‘XXXXh’ | Processing Status of the unprotected response APDU |
| #5 | 1 | ‘8Eh’ | TCC: Tag for cryptographic checksum |
| #6 | 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) |
| #7-#(6+L) | L | ‘XX..XXh’ | Cryptographic checksum |
| SW | 2 | ‘XXXXh’ | Status Words (SW1,SW2) |
Options/Help
Print Options
PrintThe Whole Regulation
PrintThe Whole Annex
PrintThe Whole Division
PrintThe Whole Division
PrintThe Whole Division
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
Y Rhestrau 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?
Mae deddfwriaeth ar gael mewn fersiynau gwahanol:
Y Diweddaraf sydd Ar Gael (diwygiedig):Y fersiwn ddiweddaraf sydd ar gael o’r ddeddfwriaeth yn cynnwys newidiadau a wnaed gan ddeddfwriaeth ddilynol ac wedi eu gweithredu gan ein tîm golygyddol. Gellir gweld y newidiadau nad ydym wedi eu gweithredu i’r testun eto yn yr ardal ‘Newidiadau i Ddeddfwriaeth’.
Gwreiddiol (Fel y’i mabwysiadwyd gan yr UE): Mae'r wreiddiol version of the legislation as it stood when it was first adopted in the EU. No changes have been applied to the text.
Gweler y wybodaeth ychwanegol ochr yn ochr â’r cynnwys
Rhychwant ddaearyddol: Indicates the geographical area that this provision applies to. For further information see ‘Frequently Asked Questions’.
Dangos Llinell Amser Newidiadau: 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.
Dewisiadau Agor
Dewisiadau gwahanol i agor deddfwriaeth er mwyn gweld rhagor o gynnwys ar y sgrin ar yr un pryd
Rhagor o Adnoddau
Gallwch wneud defnydd o ddogfennau atodol hanfodol a gwybodaeth ar gyfer yr eitem ddeddfwriaeth o’r tab hwn. Yn ddibynnol ar yr eitem ddeddfwriaeth sydd i’w gweld, gallai hyn gynnwys:
- y PDF print gwreiddiol y fel adopted version that was used for the EU Official Journal
- rhestr o newidiadau a wnaed gan a/neu yn effeithio ar yr eitem hon o ddeddfwriaeth
- pob fformat o’r holl ddogfennau cysylltiedig
- slipiau cywiro
- dolenni i ddeddfwriaeth gysylltiedig ac adnoddau gwybodaeth eraill
Llinell Amser Newidiadau
Mae’r llinell amser yma yn dangos y fersiynau gwahanol a gymerwyd o EUR-Lex yn ogystal ag unrhyw fersiynau dilynol a grëwyd ar ôl y diwrnod ymadael o ganlyniad i newidiadau a wnaed gan ddeddfwriaeth y Deyrnas Unedig.
Cymerir dyddiadau fersiynau’r UE o ddyddiadau’r dogfennau ar EUR-Lex ac efallai na fyddant yn cyfateb â’r adeg pan ddaeth y newidiadau i rym ar gyfer y ddogfen.
Ar gyfer unrhyw fersiynau a grëwyd ar ôl y diwrnod ymadael o ganlyniad i newidiadau a wnaed gan ddeddfwriaeth y Deyrnas Unedig, bydd y dyddiad yn cyd-fynd â’r dyddiad cynharaf y daeth y newid (e.e. ychwanegiad, diddymiad neu gyfnewidiad) a weithredwyd i rym. Am ragor o wybodaeth gweler ein canllaw i ddeddfwriaeth ddiwygiedig ar Ddeall Deddfwriaeth.
Rhagor o Adnoddau
Defnyddiwch y ddewislen hon i agor dogfennau hanfodol sy’n cyd-fynd â’r ddeddfwriaeth a gwybodaeth am yr eitem hon o ddeddfwriaeth. Gan ddibynnu ar yr eitem o ddeddfwriaeth sy’n cael ei gweld gall hyn gynnwys:
- y PDF print gwreiddiol y fel adopted fersiwn a ddefnyddiwyd am y copi print
- slipiau cywiro
liciwch ‘Gweld Mwy’ neu ddewis ‘Rhagor o Adnoddau’ am wybodaeth ychwanegol gan gynnwys
- rhestr o newidiadau a wnaed gan a/neu yn effeithio ar yr eitem hon o ddeddfwriaeth
- manylion rhoi grym a newid cyffredinol
- pob fformat o’r holl ddogfennau cysylltiedig
- dolenni i ddeddfwriaeth gysylltiedig ac adnoddau gwybodaeth eraill
Mae’r holl gynnwys ar gael dan Drwydded Llywodraeth Agored v3.0 ac eithrio ble nodir yn wahanol. Yn ychwanegol mae’r safle hwn â chynnwys sy’n deillio o EUR-Lex, a ailddefnyddiwyd dan delerau Penderfyniad y Comisiwn 2011/833/EU ar ailddefnyddio dogfennau o sefydliadau’r UE. Am ragor o wybodaeth gweler ddatganiad cyhoeddus Swyddfa Gyhoeddiadau’r UE ar ailddefnyddio.