{
  "url": "https://openlegislation.uk/eu-regulation-2016-799/annex-1/appendix-1",
  "json_url": "https://openlegislation.uk/eu-regulation-2016-799/annex-1/appendix-1.json",
  "legislation": "eur/2016/799",
  "legislation_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)",
  "legislation_url": "https://openlegislation.uk/eu-regulation-2016-799",
  "path": "annex/1/appendix/1",
  "kind": "appendix",
  "number": "1",
  "heading": null,
  "text": "DATA DICTIONARY\n1.\nINTRODUCTION\nThis appendix specifies data formats, data elements, and data structures for use within the recording equipment and tachograph cards.\n1.1.\nApproach for definitions of data types\nThis appendix uses Abstract Syntax Notation One (ASN.1) to define data types. This enables simple and structured data to be defined without implying any specific transfer syntax (encoding rules) which will be application and environment dependent.\nASN.1 type naming conventions are done in accordance with ISO/IEC 8824-1. This implies that:\nwhere possible, the meaning of the data type is implied through the names being selected,\nwhere a data type is a composition of other data types, the data type name is still a single sequence of alphabetical characters commencing with a capital letter, however capitals are used within the name to impart the corresponding meaning,\nin general, the data types names are related to the name of the data types from which they are constructed, the equipment in which data is stored and the function related to the data.\nIf an ASN.1 type is already defined as part of another standard and if it is relevant for usage in the recording equipment, then this ASN.1 type will be defined in this appendix.\nTo enable several types of encoding rules, some ASN.1 types in this appendix are constrained by value range identifiers. The value range identifiers are defined in paragraph 3 and Appendix 2.\n1.2.\nReferences\nThe following references are used in this Appendix:\nISO 639Code for the representation of names of languages. First Edition: 1988.\nISO 3166Codes for the representation of names of countries and their subdivisions — Part 1: Country codes, 2013\nISO 3779Road vehicles — Vehicle identification number (VIN) — Content and structure. 2009\nISO/IEC 7816-5Identification cards — Integrated circuit cards — Part 5: Registration of application providers.\nSecond edition: 2004.\nISO/IEC 7816-6Identification cards — Integrated circuit cards — Part 6: Interindustry data elements for interchange, 2004 + Technical Corrigendum 1: 2006\nISO/IEC 8824-1Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic notation. 2008 + Technical Corrigendum 1: 2012 and Technical Corrigendum 2: 2014.\nISO/IEC 8825-2Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules (PER). 2008.\nISO/IEC 8859-1Information technology — 8 bit single-byte coded graphic character sets — Part 1: Latin alphabet No.1. First edition: 1998.\nISO/IEC 8859-7Information technology — 8 bit single-byte coded graphic character sets — Part 7: Latin/Greek alphabet. 2003.\nISO 16844-3Road vehicles — Tachograph systems — Motion Sensor Interface. 2004 + Technical Corrigendum 1: 2006..\nTR-03110-3BSI / ANSSI Technical Guideline TR-03110-3, Advanced Security Mechanisms for Machine Readable Travel Documents and eIDAS Token — Part 3 Common Specifications, version 2.20, 3. February 2015\n2.\nDATA TYPE DEFINITIONS\nFor any of the following data types, the default value for an ‘unknown’ or a ‘not applicable’ content will consist in filling the data element with ‘FF’ bytes.\nAll data types are used for Generation 1 and Generation 2 applications unless otherwise specified.\nFor card data types used for Generation 1 and Generation 2 applications, the size specified in this Appendix is the one for Generation 2 application. The size for Generation 1 application is supposed to be already known by the reader. The Annex IC requirement numbers related to such data types cover both Generation 1 and Generation 2 applications.\n2.1.\nActivityChangeInfo\nThis data type enables to code, within a two bytes word, a slot status at 00:00 and/or a driver status at 00:00 and/or changes of activity and/or changes of driving status and/or changes of card status for a driver or a co-driver. This data type is related to Annex 1C requirements 105, 266, 291, 320, 321, 343, and 344.\nValue assignment — Octet Aligned: ‘scpaattttttttttt’B (16 bits)\nFor Data Memory recordings (or slot status):\n‘s’BSlot:\n‘0’B: DRIVER,\n‘1’B: CO-DRIVER,\n‘c’BDriving status:\n‘0’B: SINGLE,\n‘1’B: CREW,\n‘p’BDriver (or workshop) card status in the relevant slot:\n‘0’B: INSERTED, a card is inserted,\n‘1’B: NOT INSERTED, no card is inserted (or a card is withdrawn),\n‘aa’BActivity:\n‘00’B: BREAK/REST,\n‘01’B: AVAILABILITY,\n‘10’B: WORK,\n‘11’B: DRIVING,\n‘ttttttttttt’BTime of the change: Number of minutes since 00h00 on the given day.\nFor Driver (or Workshop) card recordings (and driver status):\n‘s’BSlot (not relevant when ‘p’=1 except note below):\n‘0’B: DRIVER,\n‘1’B: CO-DRIVER,\n‘c’BDriving status (case ‘p’=0) or\nFollowing activity status (case ‘p’=1):\n‘0’B: SINGLE,\n‘0’B: UNKNOWN\n‘1’B: CREW,\n‘1’B: KNOWN (=manually entered)\n‘p’BCard status:\n‘0’B: INSERTED, the card is inserted in a recording equipment,\n‘1’B: NOT INSERTED, the card is not inserted (or the card is withdrawn),\n‘aa’BActivity (not relevant when ‘p’=1 and ‘c’=0 except note below):\n‘00’B: BREAK/REST,\n‘01’B: AVAILABILITY,\n‘10’B: WORK,\n‘11’B: DRIVING,\n‘ttttttttttt’BTime of the change: Number of minutes since 00h00 on the given day.\nNote for the case ‘card withdrawal’:\nWhen the card is withdrawn:\n‘s’ is relevant and indicates the slot from which the card is withdrawn,\n‘c’ must be set to 0,\n‘p’ must be set to 1,\n‘aa’ must code the current activity selected at that time,\nAs a result of a manual entry, the bits ‘c’ and ‘aa’ of the word (stored in a card) may be overwritten later to reflect the entry.\n2.2.\nAddress\nAn address.\ncodePage specifies a character set defined in Chapter 4,\naddress is an address encoded using the specified character set.\n2.3.\nAESKey\nGeneration 2:\nAn AES key with a length of 128, 192 or 256 bits.\nValue assignment: not further specified.\n2.4.\nAES128Key\nGeneration 2:\nAn AES128 key.\nlength denotes the length of the AES128 key in octets.\naes128Key is an AES key with a length of 128 bits.\nValue assignment:\nThe length shall have the value 16.\n2.5.\nAES192Key\nGeneration 2:\nAn AES192 key.\nlength denotes the length of the AES192 key in octets.\naes192Key is an AES key with a length of 192 bits.\nValue assignment:\nThe length shall have the value 24.\n2.6.\nAES256Key\nGeneration 2:\nAn AES256 key.\nlength denotes the length of the AES256 key in octets.\naes256Key is an AES key with a length of 256 bits.\nValue assignment:\nThe length shall have the value 32.\n2.7.\nBCDString\nBCDString is applied for Binary Code Decimal (BCD) representation. This data type is used to represent one decimal digit in one semi octet (4 bits). BCDString is based on the ISO/IEC 8824-1 ‘CharacterStringType’.\nBCDString uses an ‘hstring’ notation. The leftmost hexadecimal digit shall be the most significant semi octet of the first octet. To produce a multiple of octets, zero trailing semi octets shall be inserted, as needed, from the leftmost semi octet position in the first octet.\nPermitted digits are: 0, 1, .. 9.\n2.8.\nCalibrationPurpose\nCode explaining why a set of calibration parameters was recorded. This data type is related to Annex 1B requirements 097 and 098 and Annex 1C requirements 119.\nValue assignment:\nGeneration 1:\n‘00’Hreserved value,\n‘01’Hactivation: recording of calibration parameters known, at the moment of the VU activation,\n‘02’Hfirst installation: first calibration of the VU after its activation,\n‘03’Hinstallation: first calibration of the VU in the current vehicle,\n‘04’Hperiodic inspection.\nGeneration 2:\nIn addition to generation 1 the following values are used:\n‘05’Hentry of VRN by company,\n‘06’Htime adjustment without calibration,\n‘07’H to ‘7F’HRFU,\n‘80’H to ‘FF’HManufacturer specific.\n2.9.\nCardActivityDailyRecord\nInformation, stored in a card, related to the driver activities for a particular calendar day. This data type is related to Annex 1C requirements 266, 291, 320 and 343.\nactivityPreviousRecordLength is the total length in bytes of the previous daily record. The maximum value is given by the length of the OCTET STRING containing these records (see CardActivityLengthRange Appendix 2 paragraph 4). When this record is the oldest daily record, the value of activityPreviousRecordLength must be set to 0.\nactivityRecordLength is the total length in bytes of this record. The maximum value is given by the length of the OCTET STRING containing these records.\nactivityRecordDate is the date of the record.\nactivityDailyPresenceCounter is the daily presence counter for the card this day.\nactivityDayDistance is the total distance travelled this day.\nactivityChangeInfo is the set of ActivityChangeInfo data for the driver this day. It may contain at maximum 1440 values (one activity change per minute). This set always includes the activityChangeInfo coding the driver status at 00:00.\n2.10.\nCardActivityLengthRange\nNumber of bytes in a driver or a workshop card, available to store driver activity records.\nValue assignment: see Appendix 2.\n2.11.\nCardApprovalNumber\nType approval number of the card.\nValue assignment:\nThe approval number shall be provided as published on the corresponding European Commission web site, i.e. for example including hyphens if any. The approval number shall be left-aligned.\n2.12.\nCardCertificate\nGeneration 1:\nCertificate of the public key of a card.\n2.13.\nCardChipIdentification\nInformation, stored in a card, related to the identification of the card's Integrated Circuit (IC) (Annex 1C requirement 249). The icSerialNumber together with the icManufacturingReferences identifies the card chip uniquely. The icSerialNumber alone does not uniquely identify the card chip.\nicSerialNumber is the IC serial number.\nicManufacturingReferences is the IC manufacturer specific identifier.\n2.14.\nCardConsecutiveIndex\nA card consecutive index (definition h)).\nValue assignment: (see Annex 1C chapter 7)\nOrder for increase: ‘0, …, 9, A, …, Z, a, …, z’\n2.15.\nCardControlActivityDataRecord\nInformation, stored in a driver or workshop card, related to the last control the driver has been subject to (Annex 1C requirements 274, 299, 327, and 350).\ncontrolType is the type of the control.\ncontrolTime is the date and time of the control.\ncontrolCardNumber is the FullCardNumber of the control officer having performed the control.\ncontrolVehicleRegistration is the VRN and registering Member State of the vehicle in which the control happened.\ncontrolDownloadPeriodBegin and controlDownloadPeriodEnd is the period downloaded, in case of downloading.\n2.16.\nCardCurrentUse\nInformation about the actual usage of the card (Annex 1C requirement 273, 298, 326, and 349).\nsessionOpenTime is the time when the card is inserted for the current usage. This element is set to zero at card removal.\nsessionOpenVehicle is the identification of the currently used vehicle, set at card insertion. This element is set to zero at card removal.\n2.17.\nCardDriverActivity\nInformation, stored in a driver or a workshop card, related to the activities of the driver (Annex 1C requirements 267, 268, 292, 293, 321 and 344).\nactivityPointerOldestDayRecord is the specification of the begin of the storage place (number of bytes from the beginning of the string) of the oldest complete day record in the activityDailyRecords string. The maximum value is given by the length of the string.\nactivityPointerNewestRecord is the specification of the begin of the storage place (number of bytes from the beginning of the string) of the most recent day record in the activityDailyRecords string. The maximum value is given by the length of the string.\nactivityDailyRecords is the space available to store the driver activity data (data structure: CardActivityDailyRecord) for each calendar day where the card has been used.\nValue assignment: this octet string is cyclically filled with records of CardActivityDailyRecord. At the first use storing is started at the first byte of the string. All new records are appended at the end of the previous one. When the string is full, storing continues at the first byte of the string independently of a break being inside a data element. Before placing new activity data in the string (enlarging current activityDailyRecord, or placing a new activityDailyRecord) that replaces older activity data, activityPointerOldestDayRecord must be updated to reflect the new location of the oldest complete day record, and activityPreviousRecordLength of this (new) oldest complete day record must be reset to 0.\n2.18.\nCardDrivingLicenceInformation\nInformation, stored in a driver card, related to the card holder driver licence data (Annex 1C requirement 259 and 284).\ndrivingLicenceIssuingAuthority is the authority responsible for issuing the driving licence.\ndrivingLicenceIssuingNation is the nationality of the authority that issued the driving licence.\ndrivingLicenceNumber is the number of the driving licence.\n2.19.\nCardEventData\nGeneration 1:\nInformation, stored in a driver or workshop card, related to the events associated with the card holder (Annex IC requirements 260 and 318).\nCardEventData is a sequence, ordered by ascending value of EventFaultType, of cardEventRecords (except security breach attempts related records which are gathered in the last set of the sequence).\ncardEventRecords is a set of event records of a given event type (or category for security breach attempts events).\nGeneration 2:\nInformation, stored in a driver or workshop card, related to the events associated with the card holder (Annex IC requirements 285 and 341).\nCardEventData is a sequence, ordered by ascending value of EventFaultType, of cardEventRecords (except security breach attempts related records which are gathered in the last set of the sequence).\ncardEventRecords is a set of event records of a given event type (or category for security breach attempts events).\n2.20.\nCardEventRecord\nInformation, stored in a driver or a workshop card, related to an event associated to the card holder (Annex 1C requirements 261, 286, 318 and 341).\neventType is the type of the event.\neventBeginTime is the date and time of beginning of event.\neventEndTime is the date and time of end of event.\neventVehicleRegistration is the VRN and registering Member State of vehicle in which the event happened.\n2.21.\nCardFaultData\nInformation, stored in a driver or a workshop card, related to the faults associated to the card holder (Annex 1C requirements 263, 288, 318, and 341).\nCardFaultData is a sequence of Recording Equipment faults set of records followed by card faults set of records.\ncardFaultRecords is a set of fault records of a given fault category (Recording Equipment or card).\n2.22.\nCardFaultRecord\nInformation, stored in a driver or a workshop card, related to a fault associated to the card holder (Annex 1C requirement 264, 289, 318, and 341).\nfaultType is the type of the fault.\nfaultBeginTime is the date and time of beginning of fault.\nfaultEndTime is the date and time of end of fault.\nfaultVehicleRegistration is the VRN and registering Member State of vehicle in which the fault happened.\n2.23.\nCardIccIdentification\nInformation, stored in a card, related to the identification of the integrated circuit (IC) card (Annex 1C requirement 248).\nclockStop is the Clockstop mode as defined in appendix 2.\ncardExtendedSerialNumber is the IC card unique serial number as further specified by the ExtendedSerialNumber data type.\ncardApprovalNumber is the type approval number of the card.\ncardPersonaliserID is the card personaliser ID encoded as ManufacturerCode.\nembedderIcAssemblerId provides information about the embedder/IC assembler.\nicIdentifier is the Identifier of the IC on the card and its IC manufacturer as defined in ISO/IEC 7816-6.\n2.24.\nCardIdentification\nInformation, stored in a card, related to the identification of the card (Annex 1C requirements 255, 280, 310, 333, 359, 365, 371, and 377).\ncardIssuingMemberState is the code of the Member State issuing the card.\ncardNumber is the card number of the card.\ncardIssuingAuthorityName is the name of the authority having issued the Card.\ncardIssueDate is the issue date of the Card to the current holder.\ncardValidityBegin is the first date of validity of the card.\ncardExpiryDate is the date when the validity of the card ends.\n2.25.\nCardMACertificate\nGeneration 2:\nCertificate of the card public key for mutual authentication with a VU. The structure of this certificate is specified in Appendix 11.\n2.26.\nCardNumber\nA card number as defined by definition g).\ndriverIdentification is the unique identification of a driver in a Member State.\nownerIdentification is the unique identification of a company or a workshop or a control body within a member state.\ncardConsecutiveIndex is the card consecutive index.\ncardReplacementIndex is the card replacement index.\ncardRenewalIndex is the card renewal index.\nThe first sequence of the choice is suitable to code a driver card number, the second sequence of the choice is suitable to code workshop, control, and company card numbers.\n2.27.\nCardPlaceDailyWorkPeriod\nInformation, stored in a driver or a workshop card, related to the places where daily work periods begin and/or end (Annex 1C requirements 272, 297, 325, and 348).\nplacePointerNewestRecord is the index of the last updated place record.\nValue assignment: Number corresponding to the numerator of the place record, beginning with ‘0’ for the first occurrence of the place records in the structure.\nplaceRecords is the set of records containing the information related to the places entered.\n2.28.\nCardPrivateKey\nGeneration 1:\nThe private key of a card.\n2.29.\nCardPublicKey\nThe public key of a card.\n2.30.\nCardRenewalIndex\nA card renewal index (definition i)).\nValue assignment : (see this Annex chapter 7).\n‘0’First issue.\nOrder for increase: ‘0, …, 9, A, …, Z’\n2.31.\nCardReplacementIndex\nA card replacement index (definition j)).\nValue assignment: (see this Annex chapter VII).\n‘0’Original card.\nOrder for increase: ‘0, …, 9, A, …, Z’\n2.32.\nCardSignCertificate\nGeneration 2:\nCertificate of the card public key for signature. The structure of this certificate is specified in Appendix 11.\n2.33.\nCardSlotNumber\nCode to distinguish between the two slots of a Vehicle Unit.\nValue assignment: not further specified.\n2.34.\nCardSlotsStatus\nCode indicating the type of cards inserted in the two slots of the vehicle unit.\nValue assignment — Octet Aligned: ‘ccccdddd’B\n‘cccc’BIdentification of the type of card inserted in the co-driver slot,\n‘dddd’BIdentification of the type of card inserted in the driver slot,\nwith the following identification codes:\n‘0000’Bno card is inserted,\n‘0001’Ba driver card is inserted,\n‘0010’Ba workshop card is inserted,\n‘0011’Ba control card is inserted,\n‘0100’Ba company card is inserted.\n2.35.\nCardSlotsStatusRecordArray\nGeneration 2:\nThe CardSlotsStatus plus metadata as used in the download protocol.\nrecordType denotes the type of the record (CardSlotsStatus). Value Assignment: See RecordType\nrecordSize is the size of the CardSlotsStatus in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of CardSlotsStatus records.\n2.36.\nCardStructureVersion\nCode indicating the version of the implemented structure in a tachograph card.\nValue assignment: ‘aabb’H:\n‘aa’HIndex for changes of the structure.\n‘00’H for Generation 1 applications\n‘01’H for Generation 2 applications\n‘bb’HIndex for changes concerning the use of the data elements defined for the structure given by the high byte.\n‘00’H for this version of Generation 1 applications\n‘00’H for this version of Generation 2 applications\n2.37.\nCardVehicleRecord\nInformation, stored in a driver or workshop card, related to a period of use of a vehicle during a calendar day (Annex 1C requirements 269, 294, 322, and 345).\nGeneration 1:\nvehicleOdometerBegin is the vehicle odometer value at the beginning of the period of use of the vehicle.\nvehicleOdometerEnd is the vehicle odometer value at the end of the period of use of the vehicle.\nvehicleFirstUse is the date and time of the beginning of the period of use of the vehicle.\nvehicleLastUse is the date and time of the end of the period of use of the vehicle.\nvehicleRegistration is the VRN and the registering Member State of the vehicle.\nvuDataBlockCounter is the value of the VuDataBlockCounter at last extraction of the period of use of the vehicle.\nGeneration 2:\nIn addition to generation 1 the following data element is used:\nVehicleIdentificationNumber is the vehicle identification number referring to the vehicle as a whole.\n2.38.\nCardVehiclesUsed\nInformation, stored in a driver or workshop card, related to the vehicles used by the card holder (Annex 1C requirements 270, 295, 323, and 346).\nvehiclePointerNewestRecord is the index of the last updated vehicle record.\nValue assignment: Number corresponding to the numerator of the vehicle record, beginning with ‘0’ for the first occurrence of the vehicle records in the structure.\ncardVehicleRecords is the set of records containing information on vehicles used.\n2.39.\nCardVehicleUnitRecord\nGeneration 2:\nInformation, stored in a driver or workshop card, related to a vehicle unit that was used (Annex 1C requirement 303 and 351).\ntimeStamp is the beginning of the period of use of the vehicle unit (i.e. first card insertion in the vehicle unit for the period).\nmanufacturerCode identifies the manufacturer of the Vehicle Unit.\ndeviceID identifies the Vehicle Unit type of a manufacturer. The value is manufacturer specific.\nvuSoftwareVersion is the software version number of the Vehicle Unit.\n2.40.\nCardVehicleUnitsUsed\nGeneration 2:\nInformation, stored in a driver or workshop card, related to the vehicle units used by the card holder (Annex 1C requirement 306 and 352).\nvehicleUnitPointerNewestRecord is the index of the last updated vehicle unit record.\nValue assignment: Number corresponding to the numerator of the vehicle unit record, beginning with ‘0’ for the first occurrence of the vehicle unit records in the structure.\ncardVehicleUnitRecords is the set of records containing information on vehicle units used.\n2.41.\nCertificate\nThe certificate of a public key issued by a Certification Authority.\nGeneration 1:\nValue assignment: digital signature with partial recovery of a CertificateContent according to Appendix 11 common security mechanisms: Signature (128 bytes) || Public Key remainder (58 bytes) || Certification Authority Reference (8 bytes).\nGeneration 2:\nValue assignment: See Appendix 11\n2.42.\nCertificateContent\nGeneration 1:\nThe (clear) content of the certificate of a public key according to Appendix 11 common security mechanisms.\ncertificateProfileIdentifier is the version of the corresponding certificate.\nValue assignment: ‘01h’ for this version.\ncertificationAuthorityReference identifies the Certification Authority issuing the certificate. It also references the Public Key of this Certification Authority.\ncertificateHolderAuthorisation identifies the rights of the certificate holder.\ncertificateEndOfValidity is the date when the certificate expires administratively.\ncertificateHolderReference identifies the certificate holder. It also references his Public Key.\npublicKey is the public key that is certified by this certificate.\n2.43.\nCertificateHolderAuthorisation\nIdentification of the rights of a certificate holder.\nGeneration 1:\ntachographApplicationID is the application identifier for the tachograph application.\nValue assignment: ‘FFh’‘54h’‘41h’‘43h’‘48h’‘4Fh’. This AID is a proprietary non registered application identifier in accordance with ISO/IEC 7816-5.\nequipmentType is the identification of the type of equipment to which the certificate is intended.\nValue assignment: in accordance with EquipmentType data type. 0 if certificate is the one of a Member State.\nGeneration 2:\ntachographApplicationID denotes the 6 most significant bytes of the generation 2 tachograph card application identifier (AID). The AID for the tachograph card application is specified in chapter 6.2.\nValue assignment:‘FF 53 4D 52 44 54’.\nequipmentType is the identification of the type of equipment as specified for generation 2 to which the certificate is intended.\nValue assignment: in accordance with EquipmentType data type.\n2.44.\nCertificateRequestID\nUnique identification of a certificate request. It can also be used as a Vehicle Unit Public Key Identifier if the serial number of the vehicle Unit to which the key is intended is not known at certificate generation time.\nrequestSerialNumber is a serial number for the certificate request, unique for the manufacturer and the month below.\nrequestMonthYear is the identification of the month and the year of the certificate request.\nValue assignment: BCD coding of Month (two digits) and Year (two last digits).\ncrIdentifier: is an identifier to distinguish a certificate request from an extended serial number.\nValue assignment: ‘FFh’.\nmanufacturerCode: is the numerical code of the manufacturer requesting the certificate.\n2.45.\nCertificationAuthorityKID\nIdentifier of the Public Key of a Certification Authority (a Member State or the European Certification Authority).\nnationNumeric is the numerical nation code of the Certification Authority.\nnationAlpha is the alphanumerical nation code of the Certification Authority.\nkeySerialNumber is a serial number to distinguish the different keys of the Certification Authority in the case keys are changed.\nadditionalInfo is a two byte field for additional coding (Certification Authority specific).\ncaIdentifier is an identifier to distinguish a Certification Authority Key Identifier from other Key Identifiers.\nValue assignment: ‘01h’.\n2.46.\nCompanyActivityData\nInformation, stored in a company card, related to activities performed with the card (Annex 1C requirement 373 and 379).\ncompanyPointerNewestRecord is the index of the last updated companyActivityRecord.\nValue assignment: Number corresponding to the numerator of the company activity record, beginning with ‘0’ for the first occurrence of the company activity record in the structure.\ncompanyActivityRecords is the set of all company activity records.\ncompanyActivityRecord is the sequence of information related to one company activity.\ncompanyActivityType is the type of the company activity.\ncompanyActivityTime is the date and time of the company activity.\ncardNumberInformation is the card number and the card issuing Member State of the card downloaded, if any.\nvehicleRegistrationInformation is the VRN and registering Member State of the vehicle downloaded or locked in or out.\ndownloadPeriodBegin and downloadPeriodEnd is the period downloaded from the VU, if any.\n2.47.\nCompanyActivityType\nCode indicating an activity carried out by a company using its company card.\n2.48.\nCompanyCardApplicationIdentification\nInformation, stored in a company card related to the identification of the application of the card (Annex 1C requirement 369 and 375).\ntypeOfTachographCardId is specifying the implemented type of card.\ncardStructureVersion is specifying the the version of the structure that is implemented in the card.\nnoOfCompanyActivityRecords is the number of company activity records the card can store.\n2.49.\nCompanyCardHolderIdentification\nInformation, stored in a company card, related to the cardholder identification (Annex 1C requirement 372 and 378).\ncompanyName is the name of the holder company.\ncompanyAddress is the address of the holder company.\ncardHolderPreferredLanguage is the preferred language of the card holder.\n2.50.\nControlCardApplicationIdentification\nInformation, stored in a control card related to the identification of the application of the card (Annex 1C requirement 357 and 363).\ntypeOfTachographCardId is specifying the implemented type of card.\ncardStructureVersion is specifying the version of the structure that is implemented in the card.\nnoOfControlActivityRecords is the number of control activity records the card can store.\n2.51.\nControlCardControlActivityData\nInformation, stored in a control card, related to control activity performed with the card (Annex 1C requirement 361 and 367).\ncontrolPointerNewestRecord is the index of the last updated control activity record.\nValue assignment: Number corresponding to the numerator of the control activity record, beginning with ‘0’ for the first occurrence of the control activity record in the structure.\ncontrolActivityRecords is the set of all control activity records.\ncontrolActivityRecord is the sequence of information related to one control.\ncontrolType is the type of the control.\ncontrolTime is the date and time of the control.\ncontrolledCardNumber is the card number and the card issuing Member State of the card controlled.\ncontrolledVehicleRegistration is the VRN and registering Member State of the vehicle in which the control happened.\ncontrolDownloadPeriodBegin and controlDownloadPeriodEnd is the period eventually downloaded.\n2.52.\nControlCardHolderIdentification\nInformation, stored in a control card, related to the identification of the cardholder (Annex 1C requirement 360 and 366).\ncontrolBodyName is the name of the control body of the card holder.\ncontrolBodyAddress is the address of the control body of the card holder.\ncardHolderName is the name and first name(s) of the holder of the Control Card.\ncardHolderPreferredLanguage is the preferred language of the card holder.\n2.53.\nControlType\nCode indicating the activities carried out during a control. This data type is related to Annex 1C requirements 126, 274, 299, 327, and 350.\nGeneration 1:\nValue assignment — Octet aligned: ‘cvpdxxxx’B (8 bits)\n‘c’Bcard downloading:\n‘0’B: card not downloaded during this control activity,\n‘1’B: card downloaded during this control activity\n‘v’BVU downloading:\n‘0’B: VU not downloaded during this control activity,\n‘1’B: VU downloaded during this control activity\n‘p’Bprinting:\n‘0’B: no printing done during this control activity,\n‘1’B: printing done during this control activity\n‘d’Bdisplay:\n‘0’B: no display used during this control activity,\n‘1’B: display used during this control activity\n‘xxxx’BNot used.\nGeneration 2:\nValue assignment — Octet aligned: ‘cvpdexxx’B (8 bits)\n‘c’Bcard downloading:\n‘0’B: card not downloaded during this control activity,\n‘1’B: card downloaded during this control activity\n‘v’BVU downloading:\n‘0’B: VU not downloaded during this control activity,\n‘1’B: VU downloaded during this control activity\n‘p’Bprinting:\n‘0’B: no printing done during this control activity,\n‘1’B: printing done during this control activity\n‘d’Bdisplay:\n‘0’B: no display used during this control activity,\n‘1’B: display used during this control activity\n‘e’Broadside calibration checking:\n‘0’B: calibration parameters not checked during this control activity,\n‘1’B: calibration parameters checked during this control activity\n‘xxx’BRFU.\n2.54.\nCurrentDateTime\nThe current date and time of the recording equipment.\nValue assignment: not further specified.\n2.55.\nCurrentDateTimeRecordArray\nGeneration 2:\nThe current date and time plus metadata as used in the download protocol.\nrecordType denotes the type of the record (CurrentDateTime). Value Assignment: See RecordType\nrecordSize is the size of the CurrentDateTime in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of current date and time records.\n2.56.\nDailyPresenceCounter\nCounter, stored in a driver or workshop card, increased by one for each calendar day the card has been inserted in a VU. This data type is related to Annex 1C requirements 266, 299, 320, and 343.\nValue assignment: Consecutive Number with maximum value = 9 999, starting again with 0. At the time of first issuing of the card the number is set to 0.\n2.57.\nDatef\nDate expressed in a readily printable numeric format.\nValue assignment:\nyyyyYear\nmmMonth\nddDay\n‘00000000’Hdenotes explicitly no date.\n2.58.\nDateOfDayDownloaded\nGeneration 2:\nThe date and time of the download.\nValue assignment: not further specified.\n2.59.\nDateOfDayDownloadedRecordArray\nGeneration 2:\nThe date and time of the download plus metadata as used in the download protocol.\nrecordType denotes the type of the record (DateOfDayDownloaded). Value Assignment: See RecordType\nrecordSize is the size of the CurrentDateTime in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of date and time of the download records.\n2.60.\nDistance\nA distance travelled (result of the calculation of the difference between two vehicle's odometer values in kilometers).\nValue assignment: Unsigned binary. Value in km in the operational range 0 to 9 999 km.\n2.61.\nDriverCardApplicationIdentification\nInformation, stored in a driver card related to the identification of the application of the card (Annex 1C requirement 253 and 278).\nGeneration 1:\ntypeOfTachographCardId is specifying the implemented type of card.\ncardStructureVersion is specifying the the version of the structure that is implemented in the card.\nnoOfEventsPerType is the number of events per type of event the card can record.\nnoOfFaultsPerType is the number of faults per type of fault the card can record.\nactivityStructureLength indicates the number of bytes available for storing activity records.\nnoOfCardVehicleRecords is the number of vehicle records the card can contain.\nnoOfCardPlaceRecords is the number of places the card can record.\nGeneration 2:\nIn addition to generation 1 the following data elements are used:\nnoOfGNSSADRecords is the number of GNSS accumulated driving records the card can store.\nnoOfSpecificConditionRecords is the number of specific condition records the card can store.\nnoOfCardVehicleUnitRecords is the number of vehicle units used records the card can store.\n2.62.\nDriverCardHolderIdentification\nInformation, stored in a driver card, related to the identification of the cardholder (Annex 1C requirement 256 and 281).\ncardHolderName is the name and first name(s) of the holder of the Driver Card.\ncardHolderBirthDate is the date of birth of the holder of the Driver Card.\ncardHolderPreferredLanguage is the preferred language of the card holder.\n2.63.\nReserved for future use\n2.64.\nEGFCertificate\nGeneration 2:\nCertificate of the external GNSS facility public key for mutual authentication with a VU. The structure of this certificate is specified in Appendix 11.\n2.65.\nEmbedderIcAssemblerId\nProvides information about the IC embedder.\ncountryCode is the 2 letter country code of the module embedder according to ISO 3166.\nmoduleEmbedder identifies the module embedder.\nmanufacturerInformation for manufacturer internal usage.\n2.66.\nEntryTypeDailyWorkPeriod\nCode to distinguish between begin and end for an entry of a daily work period place and condition of the entry.\nGeneration 1\nValue assignment: according to ISO/IEC8824-1.\nGeneration 2\nValue assignment: according to ISO/IEC8824-1.\n2.67.\nEquipmentType\nCode to distinguish different types of equipment for the tachograph application.\nGeneration 1:\nValue assignment: According to ISO/IEC8824-1.\nValue 0 is reserved for the purpose of designating a Member State or Europe in the CHA field of certificates.\nGeneration 2:\nThe same values as in generation 1 are used with the following additions:\nNote 1:\nThe generation 2 values for the Plaque, Adapter and the External GNSS connection as well as the generation 1 values for the Vehicle Unit and Motion Sensor may be used in SealRecord, i.e. if applicable.\nNote 2:\nIn the CardHolderAuthorisation (CHA) field of a generation 2 certificate, the values (1), (2), and (6) are to be interpreted as indicating a certificate for Mutual Authentication for the respective equipment type. For indicating the respective certificate for creating a digital signature, the values (17), (18) or (19) must be used.\n2.68.\nEuropeanPublicKey\nGeneration 1:\nThe European public key.\n2.69.\nEventFaultRecordPurpose\nCode explaining why an event or a fault has been recorded.\nValue assignment:\none of the 10 most recent (or last) events or faults\nthe longest event for one of the last 10 days of occurrence\none of the 5 longest events over the last 365 days\nthe last event for one of the last 10 days of occurrence\nthe most serious event for one of the last 10 days of occurrence\none of the 5 most serious events over the last 365 days\nthe first event or fault having occurred after the last calibration\nan active/on-going event or fault\nRFU\nmanufacturer specific\n2.70.\nEventFaultType\nCode qualifying an event or a fault.\nValue assignment:\nGeneration 1:\nGeneral events,\nNo further details,\nInsertion of a non valid card,\nCard conflict,\nTime overlap,\nDriving without an appropriate card,\nCard insertion while driving,\nLast card session not correctly closed,\nOver speeding,\nPower supply interruption,\nMotion data error,\nVehicle Motion Conflict,\nRFU,\nVehicle unit related security breach attempt events,\nNo further details,\nMotion sensor authentication failure,\nTachograph card authentication failure,\nUnauthorised change of motion sensor,\nCard data input integrity error\nStored user data integrity error,\nInternal data transfer error,\nUnauthorised case opening,\nHardware sabotage,\nRFU,\nSensor related security breach attempt events,\nNo further details,\nAuthentication failure,\nStored data integrity error,\nInternal data transfer error,\nUnauthorised case opening,\nHardware sabotage,\nRFU,\nRecording equipment faults,\nNo further details,\nVU internal fault,\nPrinter fault,\nDisplay fault,\nDownloading fault,\nSensor fault,\nRFU,\nCard faults,\nNo further details,\nRFU,\nRFU,\nManufacturer specific.\nGeneration 2:\nGeneral events,\nNo further details,\nInsertion of a non valid card,\nCard conflict,\nTime overlap,\nDriving without an appropriate card,\nCard insertion while driving,\nLast card session not correctly closed,\nOver speeding,\nPower supply interruption,\nMotion data error,\nVehicle Motion Conflict,\nTime conflict (GNSS versus VU internal clock),\nCommunication error with the remote communication facility,\nAbsence of position information from GNSS receiver,\nCommunication error with the external GNSS facility,\nRFU,\nVehicle unit related security breach attempt events,\nNo further details,\nMotion sensor authentication failure,\nTachograph card authentication failure,\nUnauthorised change of motion sensor,\nCard data input integrity error\nStored user data integrity error,\nInternal data transfer error,\nUnauthorised case opening,\nHardware sabotage,\nTamper detection of GNSS,\nExternal GNSS facility authentication failure,\nExternal GNSS facility certificate expired,\nRFU,\nSensor related security breach attempt events,\nNo further details,\nAuthentication failure,\nStored data integrity error,\nInternal data transfer error,\nUnauthorised case opening,\nHardware sabotage,\nRFU,\nRecording equipment faults,\nNo further details,\nVU internal fault,\nPrinter fault,\nDisplay fault,\nDownloading fault,\nSensor fault,\nInternal GNSS receiver,\nExternal GNSS facility,\nRemote communication facility,\nITS interface,\nRFU,\nCard faults,\nNo further details,\nRFU,\nRFU,\nManufacturer specific.\n2.71.\nExtendedSealIdentifier\nGeneration 2:\nThe extended seal identifier uniquely identifies a seal (Annex IC requirement 401).\nmanufacturerCode is a code of the manufacturer of the seal.\nsealIdentifier is an identifier for the seal which is unique for the manufacturer.\n2.72.\nExtendedSerialNumber\nUnique identification of an equipment. It can also be used as an equipment Public Key Identifier.\nGeneration 1:\nserialNumber is a serial number for the equipment, unique for the manufacturer, the equipment's type and the month and year below.\nmonthYear is the identification of the month and the year of manufacturing (or of serial number assignment).\nValue assignment: BCD coding of Month (two digits) and Year (two last digits).\ntype is an identifier of the type of equipment.\nValue assignment: manufacturer specific, with ‘FFh’ reserved value.\nmanufacturerCode: is the numerical code identifying a manufacturer of type approved equipment.\nGeneration 2:\nserialNumber see Generation 1\nmonthYear see Generation 1\ntype indicates the type of equipment\nmanufacturerCode: see Generation 1.\n2.73.\nFullCardNumber\nCode fully identifying a tachograph card.\ncardType is the type of the tachograph card.\ncardIssuingMemberState is the code of the Member State having issued the card.\ncardNumber is the card number.\n2.74.\nFullCardNumberAndGeneration\nGeneration 2:\nCode fully identifying a tachograph card and its generation.\nfullcardNumber identifies the tachograph card.\ngeneration indicates the generation of the tachograph card used.\n2.75.\nGeneration\nGeneration 2:\nIndicates the generation of tachograph used.\nValue assignment:\n‘00’HRFU\n‘01’HGeneration 1\n‘02’HGeneration 2\n‘03’H .. ‘FF’HRFU\n2.76.\nGeoCoordinates\nGeneration 2:\nThe geo-coordinates are encoded as integers. These integers are multiples of the ±DDMM.M encoding for the latitude and ±DDDMM.M for the longitude. Here ±DD respectively ±DDD denotes the degrees and MM.M the minutes.\nlatitude is encoded as a multiple (factor 10) of the ±DDMM.M representation.\nlongitude is encoded as a multiple (factor 10) of the ±DDDMM.M representation.\n2.77.\nGNSSAccuracy\nGeneration 2:\nThe accuracy of the GNSS position data (definition eee)). This accuracy is encoded as integer and is a multiple (factor 10) of the X.Y value provided by the GSA NMEA sentence.\n2.78.\nGNSSAccumulatedDriving\nGeneration 2:\nInformation, stored in a driver or workshop card, related to the GNSS position of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirement 306 and 354).\ngnssADPointerNewestRecord is the index of the last updated GNSS accumulated driving record.\nValue assignment is the number corresponding to the numerator of the GNSS accumulated driving record, beginning with '0' for the first occurrence of the GNSS accumulated driving record in the structure.\ngnssAccumulatedDrivingRecords is the set of records containing the date and time the accumulated driving reaches a multiple of three hours and information on the position of the vehicle.\n2.79.\nGNSSAccumulatedDrivingRecord\nGeneration 2:\nInformation, stored in a driver or workshop card, related to the GNSS position of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirement 305 and 353)\ntimeStamp is the date and time when the accumulated driving time reaches a multiple of three hours.\ngnssPlaceRecord contains information related to the position of the vehicle.\nvehicleOdometerValue is the odometer value when the accumulated driving time reaches a multiple of three hours.\n2.80.\nGNSSPlaceRecord\nGeneration 2:\nInformation related to the GNSS position of the vehicle (Annex 1C requirements 108, 109, 110, 296, 305, 347, and 353).\ntimeStamp is the date and time when the GNSS position of the vehicle was determined.\ngnssAccuracy is the accuracy of the GNSS position data.\ngeoCoordinates is the recorded location using GNSS.\n2.81.\nHighResOdometer\nOdometer value of the vehicle: Accumulated distance travelled by the vehicle during its operation.\nValue assignment: Unsigned binary. Value in 1/200 km in the operating range 0 to 21 055 406 km.\n2.82.\nHighResTripDistance\nA distance travelled during all or part of a journey.\nValue assignment: Unsigned binary. Value in 1/200 km in the operating range 0 to 21 055 406 km.\n2.83.\nHolderName\nThe surname and first name(s) of a card holder.\nholderSurname is the surname (family name) of the holder. This surname does not include titles.\nValue assignment: When a card is not personal, holderSurname contains the same information as companyName or workshopName or controlBodyName.\nholderFirstNames is the first name(s) and initials of the holder.\n2.84.\nInternalGNSSReceiver\nGeneration 2:\nInformation if the GNSS receiver is internal or external to the vehicle unit. True means that the GNSS receiver is internal to the VU. False means that the GNSS receiver is external.\n2.85.\nK-ConstantOfRecordingEquipment\nConstant of the recording equipment (definition m)).\nValue assignment: Pulses per kilometer in the operating range 0 to 64 255 pulses/km.\n2.86.\nKeyIdentifier\nA unique identifier of a Public Key used to reference and select the key. It also identifies the holder of the key.\nThe first choice is suitable to reference the public key of a Vehicle Unit, of a tachograph card or of an external GNSS facility.\nThe second choice is suitable to reference the public key of a Vehicle Unit (in cases where the serial number of the Vehicle Unit cannot be known at certificate generation time).\nThe third choice is suitable to reference the public key of a Member State.\n2.87.\nKMWCKey\nGeneration 2:\nAES key and its associated key version used for VU — Motion Sensor pairing. For details see Appendix 11.\nkMWCKey is the length of the AES key concatenated with the key which is used for VU — Motion Sensor pairing.\nkeyVersion denotes the key version of the AES key.\n2.88.\nLanguage\nCode identifying a language.\nValue assignment: Two-letter lower-case coding according to ISO 639.\n2.89.\nLastCardDownload\nDate and time, stored on a driver card, of last card download (for other purposes than control) Annex 1C requirement 257 and 282. This date is updateable by a VU or any card reader.\nValue assignment: not further specified.\n2.90.\nLinkCertificate\nGeneration 2:\nThe link certificate between European Root CA key pairs.\n2.91.\nL-TyreCircumference\nEffective circumference of the wheel tyres (definition u)).\nValue assignment: Unsigned binary, value in 1/8 mm in the operating range 0 to 8 031 mm.\n2.92.\nMAC\nGeneration 2:\nA cryptographic check sum of 8, 12 or 16 bytes length corresponding to the cipher suites specified in Appendix 11.\n2.93.\nManualInputFlag\nCode identifying whether a cardholder has manually entered driver activities at card insertion or not (Annex 1B requirement 081 and Annex 1C requirement 102).\nValue assignment: not further specified.\n2.94.\nManufacturerCode\nCode identifying a manufacturer of type approved equipment.\nThe laboratory competent for interoperability tests maintains and publishes the list of manufacturer codes on its web site (Annex 1C requirement 454).\nManufacturerCodes are provisionally assigned to developers of tachograph equipment on application to the laboratory competent for interoperability tests.\n2.95.\nManufacturerSpecificEventFaultData\nGeneration 2:\nManufacturer specific error codes simplify the error analysis and maintenance of vehicle units.\nmanufacturerCode identifies the manufacturer of the Vehicle Unit.\nmanufacturerSpecificErrorCode is an error code specific to the manufacturer.\n2.96.\nMemberStateCertificate\nThe certificate of the public key of a member state issued by the European certification authority.\n2.97.\nMemberStateCertificateRecordArray\nGeneration 2:\nThe member state certificate plus metadata as used in the download protocol.\nrecordType denotes the type of the record (MemberStateCertificate). Value Assignment: See RecordType\nrecordSize is the size of the MemberStateCertificate in bytes.\nnoOfRecords is the number of records in the set records. The value shall be set to 1 as the certficates may have different lengths.\nrecords is the set of member state certificates.\n2.98.\nMemberStatePublicKey\nGeneration 1:\nThe public key of a Member State.\n2.99.\nName\nA name.\ncodePage specifies a character set defined in Chapter 4,\nname is a name encoded using the specified character set.\n2.100.\nNationAlpha\nAlphabetic reference to a country shall be in accordance with the distinguishing signs used on vehicles in international traffic (United Nations Vienna Convention on Road Traffic, 1968).\nThe Nation Alpha and Numeric codes shall be held on a list maintained on the website of the laboratory appointed to carry out interoperability testing, as set out in Annex 1C requirement 440.\n2.101.\nNationNumeric\nNumerical reference to a country.\nValue assignment: see data type 2.100 (NationAlpha).\nAny amendment or updating of the Nation Alpha or Numeric specification described in the above paragraph shall only be made out after the appointed laboratory has obtained the views of type approved digital and smart tachograph vehicle unit manufacturers.\n2.102.\nNoOfCalibrationRecords\nNumber of calibration records, a workshop card can store.\nGeneration 1:\nValue assignment: see Appendix 2.\nGeneration 2:\nValue assignment: see Appendix 2.\n2.103.\nNoOfCalibrationsSinceDownload\nCounter indicating the number of calibrations performed with a workshop card since its last download (Annex 1C requirement 317 and 340).\nValue assignment: Not specified further.\n2.104.\nNoOfCardPlaceRecords\nNumber of place records a driver or workshop card can store.\nGeneration 1:\nValue assignment: see Appendix 2.\nGeneration 2:\nValue assignment: see Appendix 2.\n2.105.\nNoOfCardVehicleRecords\nNumber of vehicles used records a driver or workshop card can store.\nValue assignment: see Appendix 2.\n2.106.\nNoOfCardVehicleUnitRecords\nGeneration 2:\nNumber of vehicle units used records a driver or workshop card can store.\nValue assignment: see Appendix 2.\n2.107.\nNoOfCompanyActivityRecords\nNumber of company activity records, a company card can store.\nValue assignment: see Appendix 2.\n2.108.\nNoOfControlActivityRecords\nNumber of control activity records, a control card can store.\nValue assignment: see Appendix 2.\n2.109.\nNoOfEventsPerType\nNumber of events per type of event a card can store.\nValue assignment: see Appendix 2.\n2.110.\nNoOfFaultsPerType\nNumber of faults per type of fault a card can store.\nValue assignment: see Appendix 2.\n2.111.\nNoOfGNSSADRecords\nGeneration 2:\nNumber of GNSS accumulated driving records a card can store.\nValue assignment: see Appendix 2.\n2.112.\nNoOfSpecificConditionRecords\nGeneration 2:\nNumber of specific condition records a card can store.\nValue assignment: see Appendix 2.\n2.113.\nOdometerShort\nOdometer value of the vehicle in a short form.\nValue assignment: Unsigned binary. Value in km in the operating range 0 to 9 999 999 km.\n2.114.\nOdometerValueMidnight\nThe vehicle's odometer value at midnight on a given day (Annex 1B requirement 090 and Annex 1C requirement 113).\nValue assignment: not further specified.\n2.115.\nOdometerValueMidnightRecordArray\nGeneration 2:\nThe OdometerValueMidnight plus metadata used in the download protocol.\nrecordType denotes the type of the record (OdometerValueMidnight). Value Assignment: See RecordType\nrecordSize is the size of the OdometerValueMidnight in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of OdometerValueMidnight records.\n2.116.\nOverspeedNumber\nNumber of over speeding events since the last over speeding control.\nValue assignment: 0 means that no over speeding event has occurred since the last over speeding control, 1 means that one over speeding event has occurred since the last over speeding control …255 means that 255 or more over speeding events have occurred since the last over speeding control.\n2.117.\nPlaceRecord\nInformation related to a place where a daily work period begins or ends (Annex 1C requirements 108, 271, 296, 324, and 347).\nGeneration 1:\nentryTime is a date and time related to the entry.\nentryTypeDailyWorkPeriod is the type of entry.\ndailyWorkPeriodCountry is the country entered.\ndailyWorkPeriodRegion is the region entered.\nvehicleOdometerValue is the odometer value at the time of place entry.\nGeneration 2:\nIn addition to Generation 1 the following component is used:\nentryGNSSPlaceRecord is the recorded location and time.\n2.118.\nPreviousVehicleInfo\nInformation related to the vehicle previously used by a driver when inserting his card in a vehicle unit (Annex 1B requirement 081 and Annex 1C requirement 102).\nGeneration 1:\nvehicleRegistrationIdentification is the VRN and the registering Member State of the vehicle.\ncardWithdrawalTime is the card withdrawal date and time.\nGeneration 2:\nIn addition to generation 1 the following data element is used:\nvuGeneration identifies the generation of the vehicle unit.\n2.119.\nPublicKey\nGeneration 1:\nA public RSA key.\nrsaKeyModulus is the Modulus of the key pair.\nrsaKeyPublicExponent is the public exponent of the key pair.\n2.120.\nRecordType\nGeneration 2:\nReference to a record type. This data type is used in RecordArrays.\nValue assignment:\nActivityChangeInfo,\nCardSlotsStatus,\nCurrentDateTime,\nMemberStateCertificate,\nOdometerValueMidnight,\nDateOfDayDownloaded,\nSensorPaired,\nSignature,\nSpecificConditionRecord,\nVehicleIdentificationNumber,\nVehicleRegistrationNumber,\nVuCalibrationRecord,\nVuCardIWRecord,\nVuCardRecord,\nVuCertificate,\nVuCompanyLocksRecord,\nVuControlActivityRecord,\nVuDetailedSpeedBlock,\nVuDownloadablePeriod,\nVuDownloadActivityData,\nVuEventRecord,\nVuGNSSADRecord,\nVuITSConsentRecord,\nVuFaultRecord,\nVuIdentification,\nVuOverSpeedingControlData,\nVuOverSpeedingEventRecord,\nVuPlaceDailyWorkPeriodRecord,\nVuTimeAdjustmentGNSSRecord,\nVuTimeAdjustmentRecord,\nVuPowerSupplyInterruptionRecord,\nSensorPairedRecord,\nSensorExternalGNSSCoupledRecord,\nRFU,\nManufacturer specific.\n2.121.\nRegionAlpha\nAlphabetic reference to a region within a specified country.\nGeneration 1:\nValue assignment:\nGeneration 2:\nThe RegionAlpha codes shall be held on a list maintained on the website of the laboratory appointed to carry out interoperability testing.\n2.122.\nRegionNumeric\nNumerical reference to a region within a specified country.\nGeneration 1:\nValue assignment:\nGeneration 2:\nThe RegionNumeric codes shall be held on a list maintained on the website of the laboratory appointed to carry out interoperability testing.\n2.123.\nRemoteCommunicationModuleSerialNumber\nGeneration 2:\nSerial number of the Remote Communication Module.\n2.124.\nRSAKeyModulus\nGeneration 1:\nThe modulus of a RSA key pair.\nValue assignment: Unspecified.\n2.125.\nRSAKeyPrivateExponent\nGeneration 1:\nThe private exponent of a RSA key pair.\nValue assignment: Unspecified.\n2.126.\nRSAKeyPublicExponent\nGeneration1:\nThe public exponent of a RSA key pair.\nValue assignment: Unspecified.\n2.127.\nRtmData\nGeneration2:\nFor the definition of this data type see Appendix 14.\n2.128.\nSealDataCard\nGeneration 2:\nThis data type stores information about the seals that are attached to the different components of a vehicle and is intended for storage on a card. This data type is related to Annex 1C requirement 337.\nnoOfSealRecords is the number of records in sealRecords.\nsealRecords is a set of seal records.\n2.129.\nSealDataVu\nGeneration 2:\nThis data type stores information about the seals that are attached to the different components of a vehicle and is intended for storage in a Vehicle Unit.\nsealRecords is a set of seal records. If there are less than 5 seals available the value of the EquipmentType in all unused sealRecords shall be set to 16, i.e. unused.\n2.130.\nSealRecord\nGeneration 2:\nThis data type stores information about a seal that is attached to a component. This data type is related to Annex 1C requirement 337.\nequipmentType identifies the type of equipment the seal is attached to.\nextendedSealIdentifier is the identifier of the seal attached to the equipment.\n2.131.\nSensorApprovalNumber\nType approval number of the sensor.\nGeneration 1:\nValue assignment: Unspecified.\nGeneration 2:\nValue assignment:\nThe approval number shall be provided as published on the corresponding European Commission web site, i.e. for example including hyphens if any. The approval number shall be left-aligned.\n2.132.\nSensorExternalGNSSApprovalNumber\nGeneration 2:\nType approval number of the external GNSS facility.\nValue assignment:\nThe approval number shall be provided as published on the corresponding European Commission web site, i.e. for example including hyphens if any. The approval number shall be left-aligned.\n2.133.\nSensorExternalGNSSCoupledRecord\nGeneration 2:\nInformation, stored in a vehicle unit, related to the identification of the external GNSS facility coupled with the vehicle unit (Annex 1C requirement 100).\nsensorSerialNumber is the serial number of the external GNSS facility coupled with the vehicle unit.\nsensorApprovalNumber is the approval number of this external GNSS facility.\nsensorCouplingDate is a date of coupling of this external GNSS facility with the vehicle unit.\n2.134.\nSensorExternalGNSSIdentification\nGeneration 2:\nInformation related to the identification of the external GNSS facility (Annex 1C requirement 98).\nsensorSerialNumber is the extended serial number of the external GNSS facility.\nsensorApprovalNumber is the approval number of the external GNSS facility.\nsensorSCIdentifier is the identifier of the security component of the external GNSS facility.\nsensorOSIdentifier is the identifier of the operating system of the external GNSS facility.\n2.135.\nSensorExternalGNSSInstallation\nGeneration 2:\nInformation, stored in an external GNSS facility, related to the installation of the external GNSS sensor (Annex 1C requirement 123).\nsensorCouplingDateFirst is the date of the first coupling of external GNSS facility with a vehicle unit.\nfirstVuApprovalNumber is the approval number of the first vehicle unit coupled with the external GNSS facility.\nfirstVuSerialNumber is the serial number of the first vehicle unit paired with the external GNSS facility.\nsensorCouplingDateCurrent is the date of the current coupling of external GNSS facility with a vehicle unit.\ncurrentVuApprovalNumber is the approval number of the vehicle unit currently coupled with the external GNSS facility.\ncurrentVUSerialNumber is the serial number of the vehicle unit currently coupled with the external GNSS facility.\n2.136.\nSensorExternalGNSSOSIdentifier\nGeneration 2:\nIdentifier of the operating system of the external GNSS facility.\nValue assignment: manufacturer specific.\n2.137.\nSensorExternalGNSSSCIdentifier\nGeneration 2:\nThis type is used e.g. to identify the cryptographic module of the external GNSS facility.\nIdentifier of the security component of the external GNSS facility.\nValue assignment: component manufacturer specific.\n2.138.\nSensorGNSSCouplingDate\nGeneration 2:\nDate of a coupling of the external GNSS facility with a vehicle unit.\nValue assignment: Unspecified.\n2.139.\nSensorGNSSSerialNumber\nGeneration 2:\nThis type is used to store the serial number of the GNSS receiver both when it is inside the VU and when it is outside the VU.\nSerial number of the GNSS receiver.\n2.140.\nSensorIdentification\nInformation, stored in a motion sensor, related to the identification of the motion sensor (Annex 1B requirement 077 and Annex 1C requirement 95).\nsensorSerialNumber is the extended serial number of the motion sensor (includes part number and manufacturer code).\nsensorApprovalNumber is the approval number of the motion sensor.\nsensorSCIdentifier is the identifier of the security component of the motion sensor.\nsensorOSIdentifier is the identifier of the operating system of the motion sensor.\n2.141.\nSensorInstallation\nInformation, stored in a motion sensor, related to the installation of the motion sensor (Annex 1B requirement 099 and Annex 1C requirement 122).\nsensorPairingDateFirst is the date of the first pairing of the motion sensor with a vehicle unit.\nfirstVuApprovalNumber is the approval number of the first vehicle unit paired with the motion sensor.\nfirstVuSerialNumber is the serial number of the first vehicle unit paired with the motion sensor.\nsensorPairingDateCurrent is the date of the current pairing of the motion sensor with the vehicle unit.\ncurrentVuApprovalNumber is the approval number of the vehicle unit currently paired with the motion sensor.\ncurrentVUSerialNumber is the serial number of the vehicle unit currently paired with the motion sensor.\n2.142.\nSensorInstallationSecData\nInformation, stored in a workshop card, related to the security data needed for pairing motion sensors to vehicle units (Annex 1C requirement 308 and 331).\nGeneration 1:\nValue assignment: in accordance with ISO 16844-3.\nGeneration 2:\nAs described in Appendix 11 a workshop card shall store up to three keys for VU Motion Sensor pairing. These keys have different key versions.\n2.143.\nSensorOSIdentifier\nIdentifier of the operating system of the motion sensor.\nValue assignment: manufacturer specific.\n2.144.\nSensorPaired\nGeneration 1:\nInformation, stored in a vehicle unit, related to the identification of the motion sensor paired with the vehicle unit (Annex 1B requirement 079).\nsensorSerialNumber is the serial number of the motion sensor currently paired with the vehicle unit.\nsensorApprovalNumber is the approval number of the motion sensor currently paired with the vehicle unit.\nsensorPairingDateFirst is the date of the first pairing with a vehicle unit of the motion sensor currently paired with the vehicle unit.\n2.145.\nSensorPairedRecord\nGeneration 2:\nInformation, stored in a vehicle unit, related to the identification of a motion sensor paired with the vehicle unit (Annex 1C requirement 97).\nsensorSerialNumber is the serial number of a motion sensor paired with the vehicle unit.\nsensorApprovalNumber is the approval number of this motion sensor.\nsensorPairingDate is a date of pairing of this motion sensor with the vehicle unit.\n2.146.\nSensorPairingDate\nDate of a pairing of the motion sensor with a vehicle unit.\nValue assignment: Unspecified.\n2.147.\nSensorSCIdentifier\nIdentifier of the security component of the motion sensor.\nValue assignment: component manufacturer specific.\n2.148.\nSensorSerialNumber\nSerial number of the motion sensor.\n2.149.\nSignature\nA digital signature.\nGeneration 1:\nValue assignment: in accordance with Appendix 11 Common security mechanisms.\nGeneration 2:\nValue assignment: in accordance with Appendix 11 Common security mechanisms.\n2.150.\nSignatureRecordArray\nGeneration 2:\nA set of signatures plus metadata used in the download protocol.\nrecordType denotes the type of the record (Signature). Value Assignment: See RecordType\nrecordSize is the size of the Signature in bytes.\nnoOfRecords is the number of records in the set records. The value shall be set to 1 as the signatures may have different lengths.\nrecords is the set of signatures.\n2.151.\nSimilarEventsNumber\nThe number of similar events for one given day (Annex 1B requirement 094 and Annex 1C requirement 117).\nValue assignment: 0 is not used, 1 means that only one event of that type has occurred and has been stored on that day, 2 means that 2 events of that type has occurred on that day (one only has been stored), …255 means that 255 or more events of that type have occurred on that day.\n2.152.\nSpecificConditionRecord\nInformation, stored in a driver card, a workshop card or a vehicle unit, related to a specific condition (requirements Annex 1C 130, 276, 301, 328, and 355).\nentryTime is the date and time of the entry.\nspecificConditionType is the code identifying the specific condition.\n2.153.\nSpecificConditions\nInformation, stored in a driver card, a workshop card or a vehicle unit, related to a specific condition (Annex 1C requirement 131, 277, 302, 329, and 356).\nGeneration 2:\nconditionPointerNewestRecord is the index of the last updated specific condition record.\nValue assignment: Number corresponding to the numerator of the specific condition record, beginning with ‘0’ for the first occurrence of the specific condition record in the structure.\nspecificConditionRecords is the set of records containing information on the specific conditions recorded.\n2.154.\nSpecificConditionType\nCode identifying a specific condition (Annex 1B requirements 050b, 105a, 212a and 230a and Annex 1C requirements 62).\nGeneration 1:\nValue assignment:\n‘00’HRFU\n‘01’HOut of scope — Begin\n‘02’HOut of scope — End\n‘03’HFerry / Train crossing\n‘04’H .. ‘FF’HRFU\nGeneration 2:\nValue assignment:\n‘00’HRFU\n‘01’HOut of scope — Begin\n‘02’HOut of scope — End\n‘03’HFerry / Train crossing — Begin\n‘04’HFerry / Train crossing — End\n‘05’H .. ‘FF’HRFU\n2.155.\nSpeed\nSpeed of the vehicle (km/h).\nValue assignment: kilometers per hour in the operational range 0 to 220 km/h.\n2.156.\nSpeedAuthorised\nMaximum authorised Speed of the vehicle (definition hh)).\n2.157.\nSpeedAverage\nAverage speed in a previously defined duration (km/h).\n2.158.\nSpeedMax\nMaximum speed measured in a previously defined duration.\n2.159.\nTachographPayload\nGeneration 2:\nFor the definition of this data type see Appendix 14.\n2.160.\nReserved for future use\n2.161.\nTDesSessionKey\nGeneration 1:\nA triple DES session key.\nValue assignment: not further specified.\n2.162.\nTimeReal\nCode for a combined date and time field, where the date and time are expressed as seconds past 00h.00m.00s. on 1 January 1970 UTC.\nValue assignment – Octet aligned : Number of seconds since midnight 1 January 1970 UTC.\nThe max. possible date/time is in the year 2106.\n2.163.\nTyreSize\nDesignation of tyre dimensions.\nValue assignment: in accordance with Directive 92/23 (EEC) 31/03/92 O.J. L129 p.95.\n2.164.\nVehicleIdentificationNumber\nVehicle Identification Number (VIN) referring to the vehicle as a whole, normally chassis serial number or frame number.\nValue assignment: As defined in ISO 3779.\n2.165.\nVehicleIdentificationNumberRecordArray\nGeneration 2:\nThe Vehicle Idenification Number plus metadata as used in the download protocol.\nrecordType denotes the type of the record (VehicleIdentificationNumber). Value Assignment: See RecordType\nrecordSize is the size of the VehicleIdentificationNumber in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of vehicle identification numbers.\n2.166.\nVehicleRegistrationIdentification\nIdentification of a vehicle, unique for Europe (VRN and Member State).\nvehicleRegistrationNation is the nation where the vehicle is registered.\nvehicleRegistrationNumber is the registration number of the vehicle (VRN).\n2.167.\nVehicleRegistrationNumber\nRegistration number of the vehicle (VRN). The registration number is assigned by the vehicle licensing authority.\ncodePage specifies a character set defined in Chapter 4,\nvehicleRegNumber is a VRN encoded using the specified character set.\nValue assignment: Country specific.\n2.168.\nVehicleRegistrationNumberRecordArray\nGeneration 2:\nThe Vehicle Registration Number plus metadata as used in the download protocol.\nrecordType denotes the type of the record (VehicleRegistrationNumber). Value Assignment: See RecordType\nrecordSize is the size of the VehicleRegistrationNumber in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of vehicle registration numbers.\n2.169.\nVuAbility\nGeneration 2:\nInformation stored in a VU on the ability of the VU to use generation 1 tachograph cards or not (Annex 1C requirement 121).\nValue assignment — Octet Aligned:‘xxxxxxxa’B (8 bits)\nFor the ability to support of generation 1:\n‘a’BAbility to support generation 1 tachograph cards:\n‘0’ B Generation 1 is supported,\n‘1’B Generation1 is not supported,\n‘xxxxxxx’BRFU\n2.170.\nVuActivityDailyData\nGeneration 1:\nInformation, stored in a VU, related to changes of activity and/or changes of driving status and/or changes of card status for a given calendar day (Annex 1B requirement 084 and Annex 1C requirement 105, 106, 107) and to slots status at 00:00 that day.\nnoOfActivityChanges is the number of ActivityChangeInfo words in the activityChangeInfos set.\nactivityChangeInfos is the set of ActivityChangeInfo words stored in the VU for the day. It always includes two ActivityChangeInfo words giving the status of the two slots at 00:00 that day.\n2.171.\nVuActivityDailyRecordArray\nGeneration 2:\nInformation, stored in a VU, related to changes of activity and/or changes of driving status and/or changes of card status for a given calendar day (Annex 1C requirement 105, 106, 107) and to slots status at 00:00 that day.\nrecordType denotes the type of the record (ActivityChangeInfo). Value Assignment: See RecordType\nrecordSize is the size of the ActivityChangeInfo in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of ActivityChangeInfo words stored in the VU for the day. It always includes two ActivityChangeInfo words giving the status of the two slots at 00:00 that day.\n2.172.\nVuApprovalNumber\nType approval number of the vehicle unit.\nGeneration 1:\nValue assignment: Unspecified.\nGeneration 2:\nValue assignment:\nThe approval number shall be provided as published on the corresponding European Commission web site, i.e. for example including hyphens if any. The approval number shall be left-aligned.\n2.173.\nVuCalibrationData\nGeneration 1:\nInformation, stored in a vehicle unit, related to the calibrations of the recording equipment (Annex 1B requirement 098).\nnoOfVuCalibrationRecords is the number of records contained in the vuCalibrationRecords set.\nvuCalibrationRecords is the set of calibration records.\n2.174.\nVuCalibrationRecord\nInformation, stored in a vehicle unit, related a calibration of the recording equipment (Annex 1B requirement 098 and Annex 1C requirement 119 and 120).\nGeneration 1:\ncalibrationPurpose is the purpose of the calibration.\nworkshopName, workshopAddress are the workshop name and address.\nworkshopCardNumber identifies the workshop card used during the calibration.\nworkshopCardExpiryDate is the card expiry date.\nvehicleIdentificationNumber is the VIN.\nvehicleRegistrationIdentification contains the VRN and registering Member State.\nwVehicleCharacteristicConstant is the characteristic coefficient of the vehicle.\nkConstantOfRecordingEquipment is the constant of the recording equipment.\nlTyreCircumference is the effective circumference of the wheel tyres.\ntyreSize is the designation of the dimension of the tyres mounted on the vehicle\nauthorisedSpeed is the authorised speed of the vehicle.\noldOdometerValue, newOdometerValue are the old and new values of the odometer.\noldTimeValue, newTimeValue are the old and new values of date and time.\nnextCalibrationDate is the date of the next calibration of the type specified in CalibrationPurpose to be carried out by the authorised inspection authority.\nGeneration 2:\nIn addition to generation 1 the following data element is used:\nsealDataVu gives information about the seals that are attached to different components of the vehicle.\n2.175.\nVuCalibrationRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to the calibrations of the recording equipment (Annex 1C requirement 119 and 120).\nrecordType denotes the type of the record (VuCalibrationRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuCalibrationRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of calibration records.\n2.176.\nVuCardIWData\nGeneration 1:\nInformation, stored in a vehicle unit, related to insertion and withdrawal cycles of driver cards or of workshop cards in the vehicle unit (Annex 1B requirement 081 and Annex 1C requirement 103).\nnoOfIWRecords is the number of records in the set vuCardIWRecords.\nvuCardIWRecords is a set of records related to card insertion withdrawal cycles.\n2.177.\nVuCardIWRecord\nInformation, stored in a vehicle unit, related to an insertion and withdrawal cycle of a driver card or of a workshop card in the vehicle unit (Annex 1B requirement 081 and Annex 1C requirement 102).\nGeneration 1:\ncardHolderName is the driver or workshop card holder's surname and first names as stored in the card.\nfullCardNumber is the type of card, its issuing Member State and its card number as stored in the card.\ncardExpiryDate is the card's expiry date as stored in the card.\ncardInsertionTime is the insertion date and time.\nvehicleOdometerValueAtInsertion is the vehicle odometer value at card insertion.\ncardSlotNumber is the slot in which the card is inserted.\ncardWithdrawalTime is the withdrawal date and time.\nvehicleOdometerValueAtWithdrawal is the vehicle odometer value at card withdrawal.\npreviousVehicleInfo contains information about the previous vehicle used by the driver, as stored in the card.\nmanualInputFlag is a flag identifying if the cardholder has manually entered driver activities at card insertion.\nGeneration 2:\nInstead of fullCardNumber the generation 2 data structure makes use of the following data element.\nfullCardNumberAndGeneration is the type of card, its issuing Member State, its card number and generation as stored in the card.\n2.178.\nVuCardIWRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to insertion and withdrawal cycles of driver cards or of workshop cards in the vehicle unit (Annex 1C requirement 103).\nrecordType denotes the type of the record (VuCardIWRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuCardIWRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of records related to card insertion withdrawal cycles.\n2.179.\nVuCardRecord\nGeneration 2:\nInformation, stored in a vehicle unit, about a tachograph card used (Annex IC requirement 132).\ncardNumberAndGenerationInformation is the full card number and generation of the card used (data type 2.74).\ncardExtendedSerialNumber as read from the file EF_ICC under the MF of the card.\ncardStructureVersion as read from the file EF_Application_Identification under the DF_Tachograph_G2.\ncardNumber as read from the file EF_Identification under the DF_Tachograph_G2.\n2.180.\nVuCardRecordArray\nGeneration 2:\nInformation stored in a vehicle unit about the tachograph cards used with this VU. This information is intended for the analysis of VU — card problems (Annex 1C requirement 132).\nrecordType denotes the type of the record (VuCardRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuCardRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of records related to the tachograph cards used with the VU.\n2.181.\nVuCertificate\nCertificate of the public key of a vehicle unit.\n2.182.\nVuCertificateRecordArray\nGeneration 2:\nThe VU certificate plus metadata as used in the download protocol.\nrecordType denotes the type of the record (VuCertificate). Value Assignment: See RecordType\nrecordSize is the size of the VuCertificate in bytes.\nnoOfRecords is the number of records in the set records. The value shall be set to 1 as the certificates may have different lengths.\nrecords is a set of VU certificates.\n2.183.\nVuCompanyLocksData\nGeneration 1:\nInformation, stored in a vehicle unit, related to company locks (Annex 1B requirement 104).\nnoOfLocks is the number of locks listed in vuCompanyLocksRecords.\nvuCompanyLocksRecords is the set of company locks records.\n2.184.\nVuCompanyLocksRecord\nInformation, stored in a vehicle unit, related to one company lock (Annex 1B requirement 104 and Annex 1C requirement 128).\nGeneration 1:\nlockInTime, lockOutTime are the date and time of lock-in and lock-out.\ncompanyName, companyAddress are the company name and address related with the lock-in.\ncompanyCardNumber identifies the card used at lock-in.\nGeneration 2:\nInstead of companyCardNumber the generation 2 data structure makes use of the following data element.\ncompanyCardNumberAndGeneration identifies the card including its generation used at lock-in.\n2.185.\nVuCompanyLocksRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to company locks (Annex 1C requirement 128).\nrecordType denotes the type of the record (VuCompanyLocksRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuCompanyLocksRecord in bytes.\nnoOfRecords is the number of records in the set records. Value 0..255.\nrecords is the set of company locks records.\n2.186.\nVuControlActivityData\nGeneration 1:\nInformation, stored in a vehicle unit, related to controls performed using this VU (Annex 1B requirement 102).\nnoOfControls is the number of controls listed in vuControlActivityRecords.\nvuControlActivityRecords is the set of control activity records.\n2.187.\nVuControlActivityRecord\nInformation, stored in a vehicle unit, related to a control performed using this VU (Annex 1B requirement 102 and Annex 1C requirement 126).\nGeneration 1:\ncontrolType is the type of the control.\ncontrolTime is the date and time of the control.\ncontrolCardNumber identifies the control card used for the control.\ndownloadPeriodBeginTime is the begin time of the downloaded period, in case of downloading.\ndownloadPeriodEndTime is the end time of the downloaded period, in case of downloading.\nGeneration 2:\nInstead of controlCardNumber the generation 2 data structure makes use of the following data element.\ncontrolCardNumberAndGeneration identifies the control card including its generation used for the control.\n2.188.\nVuControlActivityRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to controls performed using this VU (Annex 1C requirement 126).\nrecordType denotes the type of the record (VuControlActivityRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuControlActivityRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of VU control activity records.\n2.189.\nVuDataBlockCounter\nCounter, stored in a card, identifying sequentially the insertion withdrawal cycles of the card in vehicle units.\nValue assignment: Consecutive Number with max, value 9 999, starting again with 0.\n2.190.\nVuDetailedSpeedBlock\nInformation, stored in a vehicle unit, related to the vehicle's detailed speed for a minute during which the vehicle has been moving (Annnex 1B requirement 093 and Annex 1C requirement 116).\nspeedBlockBeginDate is the date and time of the first speed value within the block.\nspeedsPerSecond is the chronological sequence of measured speeds every seconds for the minute starting at speedBlockBeginDate (included).\n2.191.\nVuDetailedSpeedBlockRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to the detailed speed of the vehicle.\nrecordType denotes the type of the record (VuDetailedSpeedBlock). Value Assignment: See RecordType\nrecordSize is the size of the VuDetailedSpeedBlock in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of detailed speed blocks.\n2.192.\nVuDetailedSpeedData\nGeneration 1:\nInformation, stored in a vehicle unit, related to the detailed speed of the vehicle.\nnoOfSpeedBlocks is the number of speed blocks in the vuDetailedSpeedBlocks set.\nvuDetailedSpeedBlocks is the set of detailed speed blocks.\n2.193.\nVuDownloadablePeriod\nOldest and latest dates for which a vehicle unit holds data related to drivers activities (Annex 1B requirements 081, 084 or 087 and Annex 1C requirements 102, 105, 108).\nminDownloadableTime is the oldest card insertion or activity change or place entry date and time stored in the VU.\nmaxDownloadableTime is the latest card withdrawal or activity change or place entry date and time stored in the VU.\n2.194.\nVuDownloadablePeriodRecordArray\nGeneration 2:\nThe VUDownloadablePeriod plus metadata used in the download protocol.\nrecordType denotes the type of the record (VuDownloadablePeriod). Value Assignment: See RecordType\nrecordSize is the size of the VuDownloadablePeriod in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of VuDownloadablePeriod records.\n2.195.\nVuDownloadActivityData\nInformation, stored in a vehicle unit, related to its last download (Annex 1B requirement 105 and Annex 1C requirement 129).\nGeneration 1:\ndownloadingTime is the date and time of downloading.\nfullCardNumber identifies the card used to authorise the download.\ncompanyOrWorkshopName is the company or workshop name.\nGeneration 2:\nInstead of fullCardNumber the generation 2 data structure makes use of the following data element.\nfullCardNumberAndGeneration identifies the card including its generation used to authorise the download.\n2.196.\nVuDownloadActivityDataRecordArray\nGeneration 2:\nInformation related to the last VU download (Annex 1C requirement 129).\nrecordType denotes the type of the record (VuDownloadActivityData). Value Assignment: See RecordType\nrecordSize is the size of the VuDownloadActivityData in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of download activity data records.\n2.197.\nVuEventData\nGeneration 1:\nInformation, stored in a vehicle unit, related to events (Annex 1B requirement 094 except over speeding event).\nnoOfVuEvents is the number of events listed in the vuEventRecords set.\nvuEventRecords is a set of events records.\n2.198.\nVuEventRecord\nInformation, stored in a vehicle unit, related to an event (Annex 1B requirement 094 and Annex 1C requirement 117 except over speeding event).\nGeneration 1:\neventType is the type of the event.\neventRecordPurpose is the purpose for which this event has been recorded.\neventBeginTime is the date and time of beginning of event.\neventEndTime is the date and time of end of event.\ncardNumberDriverSlotBegin identifies the card inserted in the driver slot at the beginning of the event.\ncardNumberCodriverSlotBegin identifies the card inserted in the co-driver slot at the beginning of the event.\ncardNumberDriverSlotEnd identifies the card inserted in the driver slot at the end of the event.\ncardNumberCodriverSlotEnd identifies the card inserted in the co-driver slot at the end of the event.\nsimilarEventsNumber is the number of similar events that day.\nThis sequence can be used for all events other than over speeding events.\nGeneration 2:\nIn addition to generation 1 the following data elements are used:\nmanufacturerSpecificEventFaultData contains additional, manufacturer specific information about the event.\nInstead of cardNumberDriverSlotBegin, cardNumberCodriverSlotBegin, cardNumberDriverSlotEnd, and cardNumberCodriverSlotEnd the generation 2 data structure makes use of the following data elements:\ncardNumberAndGenDriverSlotBegin identifies the card including its generation which is inserted in the driver slot at the beginning of the event.\ncardNumberAndGenCodriverSlotBegin identifies the card including its generation which is inserted in the co-driver slot at the beginning of the event.\ncardNumberAndGenDriverSlotEnd identifies the card including its generation which is inserted in the driver slot at the end of the event.\ncardNumberAndGenCodriverSlotEnd identifies the card including its generation which is inserted in the co-driver slot at the end of the event.\nIf the event is a time conflict the eventBeginTime and eventEndTime are to be interpreted as follows:\neventBeginTime is the recording equipment date and time.\neventEndTime is the GNSS date and time.\n2.199.\nVuEventRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to events (Annex 1C requirement 117 except over speeding event).\nrecordType denotes the type of the record (VuEventRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuEventRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of events records.\n2.200.\nVuFaultData\nGeneration 1:\nInformation, stored in a vehicle unit, related to faults (Annex 1B requirement 096).\nnoOfVuFaults is the number of faults listed in the vuFaultRecords set.\nvuFaultRecords is a set of faults records.\n2.201.\nVuFaultRecord\nInformation, stored in a vehicle unit, related to a fault (Annex 1B requirement 096 and Annex 1C requirement 118).\nGeneration 1:\nfaultType is the type of recording equipment fault.\nfaultRecordPurpose is the purpose for which this fault has been recorded.\nfaultBeginTime is the date and time of beginning of fault.\nfaultEndTime is the date and time of end of fault.\ncardNumberDriverSlotBegin identifies the card inserted in the driver slot at the beginning of the fault.\ncardNumberCodriverSlotBegin identifies the card inserted in the co-driver slot at the beginning of the fault.\ncardNumberDriverSlotEnd identifies the card inserted in the driver slot at the end of the fault.\ncardNumberCodriverSlotEnd identifies the card inserted in the co-driver slot at the end of the fault.\nGeneration 2:\nIn addition to generation 1 the following data element is used:\nmanufacturerSpecificEventFaultData contains additional, manufacturer specific information about the fault.\nInstead of cardNumberDriverSlotBegin, cardNumberCodriverSlotBegin, cardNumberDriverSlotEnd, and cardNumberCodriverSlotEnd the generation 2 data structure makes use of the following data elements:\ncardNumberAndGenDriverSlotBegin identifies the card including its generation which is inserted in the driver slot at the beginning of the fault.\ncardNumberAndGenCodriverSlotBegin identifies the card including its generation which is inserted in the co-driver slot at the beginning of the fault.\ncardNumberAndGenDriverSlotEnd identifies the card including its generation which is inserted in the driver slot at the end of the fault.\ncardNumberAndGenCodriverSlotEnd identifies the card including its generation which is inserted in the co-driver slot at the end of the fault.\n2.202.\nVuFaultRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to faults (Annex 1C requirement 118).\nrecordType denotes the type of the record (VuFaultRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuFaultRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of faults records.\n2.203.\nVuGNSSADRecord\nGeneration 2:\nInformation, stored in a vehicle unit, related to the GNSS position of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirement 108, 110).\ntimeStamp is the date and time when the accumulated driving time reaches a multiple of three hours.\ncardNumberAndGenDriverSlot identifies the card including its generation which is inserted in the driver slot.\ncardNumberAndGenCodriverSlot identifies the card including its generation which is inserted in the co-driver slot.\ngnssPlaceRecord contains information related to the position of the vehicle.\nvehicleOdometerValue is the odometer value when the accumulated driving time reaches a multiple of three hours.\n2.204.\nVuGNSSADRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to the GNSS position of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirement 108 and 110).\nrecordType denotes the type of the record (VuGNSSADRecord).\nValue Assignment : See RecordType.\nrecordSize is the size of the VuGNSSADRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of GNSS accumulated driving records.\n2.205.\nVuIdentification\nInformation, stored in a vehicle unit, related to the identification of the vehicle unit (Annex 1B requirement 075 and Annex 1C requirement 93 and 121).\nGeneration 1:\nvuManufacturerName is the name of the manufacturer of the vehicle unit.\nvuManufacturerAddress is the address of the manufacturer of the vehicle unit.\nvuPartNumber is the part number of the vehicle unit.\nvuSerialNumber is the serial number of the vehicle unit.\nvuSoftwareIdentification identifies the software implemented in the vehicle unit.\nvuManufacturingDate is the manufacturing date of the vehicle unit.\nvuApprovalNumber is the type approval number of the vehicle unit.\nGeneration 2:\nIn addition to generation 1 the following data element are used:\nvuGeneration identifies the generation of the vehicle unit.\nvuAbility provides information whether the VU supports generation 1 tachograph cards or not.\n2.206.\nVuIdentificationRecordArray\nGeneration 2:\nThe VuIdentification plus metadata used in the download protocol.\nrecordType denotes the type of the record (VuIdentification). Value Assignment: See RecordType\nrecordSize is the size of the VuIdentification in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of VuIdentification records.\n2.207.\nVuITSConsentRecord\nGeneration 2:\nInformation stored in a vehicle unit, related to the consent of a driver to use Intelligent Transport Systems.\ncardNumberAndGen identifies the card including its generation. This must be a driver card or a workshop card.\nconsent is a flag which indicates whether the driver has given his consent on the usage of Intelligent Transport Systems with this vehicle / vehicle unit.\nValue assignment:\nTRUEindicates the driver's consent to use Intelligent Transport Systems\nFALSEindicates the driver's denial to use Intelligent Transport Systems\n2.208.\nVuITSConsentRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to drivers' consent on the usage of Intelligent Transport Systems (Annex 1C requirement 200).\nrecordType denotes the type of the record (VuITSConsentRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuITSConsentRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is the set of ITS consent records.\n2.209.\nVuManufacturerAddress\nAddress of the manufacturer of the vehicle unit.\nValue assignment: Unspecified.\n2.210.\nVuManufacturerName\nName of the manufacturer of the vehicle unit.\nValue assignment: Unspecified.\n2.211.\nVuManufacturingDate\nDate of manufacture of the vehicle unit.\nValue assignment: Unspecified.\n2.212.\nVuOverSpeedingControlData\nInformation, stored in a vehicle unit, related to over speeding events since the last over speeding control (Annex 1B requirement 095 and Annex 1C requirement 117).\nlastOverspeedControlTime is the date and time of the last over speeding control.\nfirstOverspeedSince is the date and time of the first over speeding following this over speeding control.\nnumberOfOverspeedSince is the number of over speeding events since the last over speeding control.\n2.213.\nVuOverSpeedingControlDataRecordArray\nGeneration 2:\nThe VuOverSpeedingControlData plus metadata used in the download protocol.\nrecordType denotes the type of the record (VuOverSpeedingControlData). Value Assignment: See RecordType\nrecordSize is the size of the VuOverSpeedingControlData in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of over speeding control data records.\n2.214.\nVuOverSpeedingEventData\nGeneration 1:\nInformation, stored in a vehicle unit, related to over speeding events (Annex 1B requirement 094).\nnoOfVuOverSpeedingEvents is the number of events listed in the vuOverSpeedingEventRecords set.\nvuOverSpeedingEventRecords is a set of over speeding events records.\n2.215.\nVuOverSpeedingEventRecord\nGeneration 1:\nInformation, stored in a vehicle unit, related to over speeding events (Annex 1B requirement 094 and Annex 1C requirement 117).\neventType is the type of the event.\neventRecordPurpose is the purpose for which this event has been recorded.\neventBeginTime is the date and time of beginning of event.\neventEndTime is the date and time of end of event.\nmaxSpeedValue is the maximum speed measured during the event.\naverageSpeedValue is the arithmetic average speed measured during the event.\ncardNumberDriverSlotBegin identifies the card inserted in the driver slot at the beginning of the event.\nsimilarEventsNumber is the number of similar events that day.\nGeneration 2:\nInformation, stored in a vehicle unit, related to over speeding events (Annex 1B requirement 094 and Annex 1C requirement 117).\nInstead of cardNumberDriverSlotBegin, the generation 2 data structure makes use of the following data element:\ncardNumberAndGenDriverSlotBegin identifies the card including its generation which is inserted in the driver slot at the beginning of the event.\n2.216.\nVuOverSpeedingEventRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to over speeding events (Annex 1C requirement 117).\nrecordType denotes the type of the record (VuOverSpeedingEventRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuOverSpeedingEventRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of over speeding events records.\n2.217.\nVuPartNumber\nPart number of the vehicle unit.\nValue assignment: VU manufacturer specific.\n2.218.\nVuPlaceDailyWorkPeriodData\nGeneration 1:\nInformation, stored in a vehicle unit, related to places where drivers begin or end a daily work period (Annex 1B requirement 087 and Annex 1C requirement 108 and 110).\nnoOfPlaceRecords is the number of records listed in the vuPlaceDailyWorkPeriodRecords set.\nvuPlaceDailyWorkPeriodRecords is a set of place related records.\n2.219.\nVuPlaceDailyWorkPeriodRecord\nGeneration 1:\nInformation, stored in a vehicle unit, related to a place where a driver begins or ends a daily work period (Annex 1B requirement 087 and Annex 1C requirement 108 and 110).\nfullCardNumber is the driver's card type, card issuing Member State and card number.\nplaceRecord contains the information related to the place entered.\nGeneration 2:\nInformation, stored in a vehicle unit, related to a place where a driver begins or ends a daily work period (Annex 1B requirement 087 and Annex 1C requirement 108 and 110).\nInstead of fullCardNumber, the generation 2 data structure makes use of the following data element:\nfullCardNumberAndGeneration is the type of card, its issuing Member State, its card number and generation as stored in the card.\n2.220.\nVuPlaceDailyWorkPeriodRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to places where drivers begin or end a daily work period (Annex 1C requirement 108 and 110).\nrecordType denotes the type of the record (VuPlaceDailyWorkPeriodRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuPlaceDailyWorkPeriodRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of place related records.\n2.221.\nVuPrivateKey\nGeneration 1:\nThe private key of a vehicle unit.\n2.222.\nVuPublicKey\nGeneration 1:\nThe public key of a vehicle unit.\n2.223.\nVuSerialNumber\nSerial number of the vehicle unit (Annex 1B requirement 075 and Annex 1C requirement 93).\n2.224.\nVuSoftInstallationDate\nDate of installation of the vehicle unit software version.\nValue assignment: Unspecified.\n2.225.\nVuSoftwareIdentification\nInformation, stored in a vehicle unit, related to the software installed.\nvuSoftwareVersion is the software version number of the Vehicle Unit.\nvuSoftInstallationDate is the software version installation date.\n2.226.\nVuSoftwareVersion\nSoftware version number of the vehicle unit.\nValue assignment: Unspecified.\n2.227.\nVuSpecificConditionData\nGeneration 1:\nInformation, stored in a vehicle unit, related to specific conditions.\nnoOfSpecificConditionRecords is the number of records listed in the specificConditionRecords set.\nspecificConditionRecords is a set of specific conditions related records.\n2.228.\nVuSpecificConditionRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to specific conditions (Annex 1C requirement 130).\nrecordType denotes the type of the record (SpecificConditionRecord). Value Assignment: See RecordType\nrecordSize is the size of the SpecificConditionRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of specific conditions related records.\n2.229.\nVuTimeAdjustmentData\nGeneration 1:\nInformation, stored in a vehicle unit, related to time adjustments performed outside the frame of a regular calibration (Annex 1B requirement 101).\nnoOfVuTimeAdjRecords is the number of records in vuTimeAdjustmentRecords.\nvuTimeAdjustmentRecords is a set of time adjustment records.\n2.230.\nReserved for future use\n2.231.\nReserved for future use\n2.232.\nVuTimeAdjustmentRecord\nInformation, stored in a vehicle unit, related a time adjustment performed outside the frame of a regular calibration (Annex 1B requirement 101 and Annex 1C requirement 124 and 125).\nGeneration 1:\noldTimeValue, newTimeValue are the old and new values of date and time.\nworkshopName, workshopAddress are the workshop name and address.\nworkshopCardNumber identifies the workshop card used to perform the time adjustment.\nGeneration 2:\nInstead of workshopCardNumber the generation 2 data structure makes use of the following data element.\nworkshopCardNumberAndGeneration identifies the workshop card including its generation used to perform the time adjustment.\n2.233.\nVuTimeAdjustmentRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to time adjustments performed outside the frame of a regular calibration (Annex 1C requirement 124 and 125).\nrecordType denotes the type of the record (VuTimeAdjustmentRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuTimeAdjustmentRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of time adjustment records.\n2.234.\nWorkshopCardApplicationIdentification\nInformation, stored in a workshop card related to the identification of the application of the card (Annex 1C requirement 307 and 330).\nGeneration 1:\ntypeOfTachographCardId is specifying the implemented type of card.\ncardStructureVersion is specifying the the version of the structure that is implemented in the card.\nnoOfEventsPerType is the number of events per type of event the card can record.\nnoOfFaultsPerType is the number of faults per type of fault the card can record.\nactivityStructureLength indicates the number of bytes available for storing activity records.\nnoOfCardVehicleRecords is the number of vehicle records the card can contain.\nnoOfCardPlaceRecords is the number of places the card can record.\nnoOfCalibrationRecords is the number of calibration records the card can store.\nGeneration 2:\nIn addition to generation 1 the following data elements are used:\nnoOfGNSSADRecords is the number of GNSS accumulated driving records the card can store.\nnoOfSpecificConditionRecords is the number of specific condition records the card can store.\nnoOfCardVehicleUnitRecords is the number of vehicle units used records the card can store.\n2.235.\nWorkshopCardCalibrationData\nInformation, stored in a workshop card, related to workshop activity performed with the card (Annex 1C requirements 314, 316, 337, and 339).\ncalibrationTotalNumber is the total number of calibrations performed with the card.\ncalibrationPointerNewestRecord is the index of the last updated calibration record.\nValue assignment: Number corresponding to the numerator of the calibration record, beginning with ‘0’ for the first occurrence of the calibration records in the structure.\ncalibrationRecords is the set of records containing calibration and/or time adjustment information.\n2.236.\nWorkshopCardCalibrationRecord\nInformation, stored in a workshop card, related to a calibration performed with the card (Annex 1C requirement 314 and 337).\nGeneration 1:\ncalibrationPurpose is the purpose of the calibration.\nvehicleIdentificationNumber is the VIN.\nvehicleRegistration contains the VRN and registering Member State.\nwVehicleCharacteristicConstant is the characteristic coefficient of the vehicle.\nkConstantOfRecordingEquipment is the constant of the recording equipment.\nlTyreCircumference is the effective circumference of the wheel tyres.\ntyreSize is the designation of the dimensions of the tyres mounted on the vehicle.\nauthorisedSpeed is the maximum authorised speed of the vehicle.\noldOdometerValue, newOdometerValue are the old and new values of the odometer.\noldTimeValue, newTimeValue are the old and new values of date and time.\nnextCalibrationDate is the date of the next calibration of the type specified in CalibrationPurpose to be carried out by the authorised inspection authority.\nvuPartNumber, vuSerialNumber and sensorSerialNumber are the data elements for recording equipment identification.\nGeneration 2:\nIn addition to generation 1 the following data elements are used:\nsensorGNSSSerialNumber which identifies an external GNSS facility.\nrcmSerialNumber which identifies a Remote Communication Module.\nsealDataCard gives information about the seals that are attached to different components of the vehicle.\n2.237.\nWorkshopCardHolderIdentification\nInformation, stored in a workshop card, related to the identification of the cardholder (Annex 1C requirement 311 and 334).\nworkshopName is name of the workshop of the card holder.\nworkshopAddress is the address of the workshop of the card holder.\ncardHolderName is the name and first name(s) of the holder (e.g. the name of the mechanic).\ncardHolderPreferredLanguage is the preferred language of the card holder.\n2.238.\nWorkshopCardPIN\nPersonal identification number of the Workshop Card (Annex 1C requirement 309 and 332).\nValue assignment: The PIN known to the cardholder, right padded with ‘FF’ bytes up to 8 bytes.\n2.239.\nW-VehicleCharacteristicConstant\nCharacteristic coefficient of the vehicle (definition k)).\nValue assignment: Impulses per kilometer in the operating range 0 to 64 255 pulses/km.\n2.240.\nVuPowerSupplyInterruptionRecord\nGeneration 2:\nInformation, stored in a vehicle unit, related to Power Supply Interruption events (Annex 1C requirement 117).\neventType is the type of the event.\neventRecordPurpose is the purpose for which this event has been recorded.\neventBeginTime is the date and time of beginning of event.\neventEndTime is the date and time of end of event.\ncardNumberAndGenDriverSlotBegin identifies the card including its generation inserted in the driver slot at the beginning of the event.\ncardNumberAndGenDriverSlotEnd identifies the card including its generation inserted in the driver slot at the end of the event.\ncardNumberAndGenCodriverSlotBegin identifies the card including its generation inserted in the co-driver slot at the beginning of the event.\ncardNumberAndGenCodriverSlotEnd identifies the card including its generation inserted in the co-driver slot at the end of the event.\nsimilarEventsNumber is the number of similar events that day.\n2.241.\nVuPowerSupplyInterruptionRecordArray\nGeneration 2:\nInformation, stored in a vehicle unit, related to Power Supply Interruption events (Annex 1C requirement 117).\nrecordType denotes the type of the record (VuPowerSupplyInterruptionRecord). Value Assignment: See RecordType\nrecordSize is the size of the VuPowerSupplyInterruptionRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of power supply interruption events records.\n2.242.\nVuSensorExternalGNSSCoupledRecordArray\nGeneration 2:\nA set of SensorExternalGNSSCoupledRecord plus metadata used in the download protocol.\nrecordType denotes the type of the record (SensorExternalGNSSCoupledRecord). Value Assignment: See RecordType\nrecordSize is the size of the SensorExternalGNSSCoupledRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of Sensor External GNSS Coupled records.\n2.243.\nVuSensorPairedRecordArray\nGeneration 2:\nA set of SensorPairedRecord plus metadata used in the download protocol.\nrecordType denotes the type of the record (SensorPairedRecord). Value Assignment: See RecordType\nrecordSize is the size of the SensorPairedRecord in bytes.\nnoOfRecords is the number of records in the set records.\nrecords is a set of sensor paired records.\n3.\nVALUE AND SIZE RANGE DEFINITIONS\nDefinition of variable values used for definitions in paragraph 2.\n4.\nCHARACTER SETS\nIA5Strings use the ASCII characters as defined by ISO/IEC 8824-1. For readability and for easy referencing the value assignment is given below. The ISO/IEC 8824-1 supersedes this informative note in case of discrepancy.\nOther character strings (Address, Name, VehicleRegistrationNumber) use, in addition, characters from the decimal character code range 161 — 255 of the following 8-bit, standard character sets, specified by the Code Page number:Standard Character Set\nCode Page(Decimal)\nISO/IEC 8859-1 Latin-1 Western European\n1\nISO/IEC 8859-2 Latin-2 Central European\n2\nISO/IEC 8859-3 Latin-3 South European\n3\nISO/IEC 8859-5 Latin / Cyrillic\n5\nISO/IEC 8859-7 Latin / Greek\n7\nISO/IEC 8859-9 Latin-5 Turkish\n9\nISO/IEC 8859-13 Latin-7 Baltic Rim\n13\nISO/IEC 8859-15 Latin-9\n15\nISO/IEC 8859-16 Latin-10 South Eastern European\n16\nKOI8-R Latin / Cyrillic\n80\nKOI8-U Latin / Cyrillic\n85\n5.\nENCODING\nWhen encoded with ASN.1 encoding rules, all data types defined shall be encoded according to ISO/IEC 8825-2, aligned variant.\n6.\nOBJECT IDENTIFIERS UND APPLICATION IDENTIFIERS\n6.1.\nObject Identifiers\nThe Object Identifiers (OIDs) listed in this chapter are only relevant for generation 2. These OIDs are specified in TR-03110-3 and repeated here for the sake of completeness. These OIDs are contained in the subtree of bsi-de:\nVU Authentication protocol identifiers\nExample: Suppose VU Authentication is to be done with SHA-384, then the object identifier to use is (in ASN.1 notation) . The value of this object identifier in dot notation is .\nDot notation\nByte notation\n‘04 00 7F 00 07 02 02 02 02 03’\n‘04 00 7F 00 07 02 02 02 02 04’\n‘04 00 7F 00 07 02 02 02 02 05’\nChip Authentication protocol identifiers\nExample: Suppose Chip Authentication is to be done by using the ECDH algorithm, resulting in an AES session key length of 128 bits. This session key will subsequently be used in the CBC mode of operation to ensure data confidentiality and with the CMAC algorithm to ensure data authenticity. Therefore, the object identifier to use is (in ASN.1 notation) . The value of this object identifier in dot notation is .\nDot notation\nByte notation\n‘04 00 7F 00 07 02 02 03 02 02’\n‘04 00 7F 00 07 02 02 03 02 03’\n‘04 00 7F 00 07 02 02 03 02 04’\n6.2.\nApplication Identifiers\nGeneration 2:\nThe Application Identifier (AID) for the External GNSS Facility (Generation 2) is given by ‘FF 44 54 45 47 4D’. This is a proprietary AID according to ISO/IEC 7816-4.\nNote: The last 5 bytes encode DTEGM for smart Tachograph External GNSS Facility.\nThe Application Identifier for the generation 2 tachograph card application is given by ‘FF 53 4D 52 44 54’. This is a proprietary AID according to ISO/IEC 7816-4.",
  "extent": "E+W+S+N.I.",
  "status": null,
  "version": "current",
  "annotations": [
    {
      "type": "F",
      "label": "F1",
      "text": "Inserted 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)."
    },
    {
      "type": "F",
      "label": "F2",
      "text": "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)."
    }
  ],
  "outstanding_effects": [],
  "provenance": {
    "source": "legislation.gov.uk",
    "source_url": "https://www.legislation.gov.uk/eur/2016/799/annex/1/appendix/1",
    "retrieved_at": "2026-11-01T14:45:49.686558+00:00"
  },
  "licence": "Open Government Licence v3.0",
  "licence_url": "https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
  "attribution": "Contains public sector information licensed under the Open Government Licence v3.0. Source: legislation.gov.uk, The National Archives."
}