LegalizeCommission 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)
| Image omitted; see official source | General events, No further details, Insertion of a non valid card, Card conflict, Time overlap, Driving without an appropriate card, Card insertion while driving, Last card session not correctly closed, Over speeding, Power supply interruption, Motion data error, Vehicle Motion Conflict, Time conflict (GNSS versus VU internal clock), Communication error with the remote communication facility, Absence of position information from GNSS receiver, Communication error with the external GNSS facility, RFU, |
| Image omitted; see official source | Vehicle unit related security breach attempt events, No further details, Motion sensor authentication failure, Tachograph card authentication failure, Unauthorised change of motion sensor, Card data input integrity error Stored user data integrity error, Internal data transfer error, Unauthorised case opening, Hardware sabotage, Tamper detection of GNSS, External GNSS facility authentication failure, External GNSS facility certificate expired, RFU, |
| Image omitted; see official source | Sensor related security breach attempt events, No further details, Authentication failure, Stored data integrity error, Internal data transfer error, Unauthorised case opening, Hardware sabotage, RFU, |
| Image omitted; see official source | Recording equipment faults, No further details, VU internal fault, Printer fault, Display fault, Downloading fault, Sensor fault, Internal GNSS receiver, External GNSS facility, Remote communication facility, ITS interface, RFU, |
| Image omitted; see official source | Card faults, No further details, RFU, |
| Image omitted; see official source | RFU, |
| Image omitted; see official source | Manufacturer specific. |
Generation 2, version 2:
- ‘0x’H General events,
- ‘00’H No further details,
- ‘01’H Insertion of a non valid card,
- ‘02’H Card conflict,
- ‘03’H Time overlap,
- ‘04’H Driving without an appropriate card,
- ‘05’H Card insertion while driving,
- ‘06’H Last card session not correctly closed,
- ‘07’H Over speeding,
- ‘08’H Power supply interruption,
- ‘09’H Motion data error,
- ‘0A’H Vehicle Motion Conflict,
- ‘0B’H Time conflict (GNSS versus VU internal clock),
- ‘0C’H Communication error with the remote communication facility,
- ‘0D’H Absence of position information from GNSS receiver,
- ‘0E’H Communication error with the external GNSS facility,
- ‘0F’H GNSS anomaly,
- ‘1x’H Vehicle unit related security breach attempt events,
- ‘10’H No further details,
- ‘11’H Motion sensor authentication failure,
- ‘12’H Tachograph card authentication failure,
- ‘13’H Unauthorised change of motion sensor,
- ‘14’H Card data input integrity error,
- ‘15’H Stored user data integrity error,
- ‘16’H Internal data transfer error,
- ‘17’H Unauthorised case opening,
- ‘18’H Hardware sabotage,
- ‘19’H Tamper detection of GNSS,
- ‘1A’H External GNSS facility authentication failure,
- ‘1B’H External GNSS facility certificate expired,
- ‘1C’H Inconsistency between motion data and stored driver activity data,
- ‘1D’H to ‘1F’H RFU,
- ‘2x’H Sensor related security breach attempt events,
- ‘20’H No further details,
- ‘21’H Authentication failure,
- ‘22’H Stored data integrity error,
- ‘23’H Internal data transfer error,
- ‘24’H Unauthorised case opening,
- ‘25’H Hardware sabotage,
- ‘26’H to ‘2F’H RFU,
- ‘3x’H Recording equipment faults,
- ‘30’H No further details,
- ‘31’H VU internal fault,
- ‘32’H Printer fault,
- ‘33’H Display fault,
- ‘34’H Downloading fault,
- ‘35’H Sensor fault,
- ‘36’H Internal GNSS receiver,
- ‘37’H External GNSS facility,
- ‘38’H Remote communication facility,
- ‘39’H ITS interface,
- ‘3A’H Internal Sensor Fault,
- ‘3B’H to ‘3F’H RFU,
- ‘4x’H Card faults,
- ‘40’H No further details,
- ‘41’H to ‘4F’H RFU,
- ‘50’H to ‘7F’H RFU,
- ‘80’H to ‘FF’H Manufacturer specific.
2.71. ExtendedSealIdentifier
Generation 2:
The extended seal identifier uniquely identifies a seal (Annex IC requirement 401).
Image omitted; see official source
manufacturerCode is a code of the manufacturer of the seal. Value assignment: see database registration to be managed by the European Commission (see https://dtc.jrc.ec.europa.eu).
sealIdentifier is an identifier for the seal which is unique for the manufacturer. Value assignment: alpha-numeric number, unique in the manufacturer domain according to [ISO8859-1].
2.72. ExtendedSerialNumber
Unique identification of an equipment. It can also be used as an equipment Public Key Identifier.
Generation 1:
Image omitted; see official source
serialNumber is a serial number for the equipment, unique for the manufacturer, the equipment's type and the month and year below.
monthYear is the identification of the month and the year of manufacturing (or of serial number assignment).
Value assignment: BCD coding of Month (two digits) and Year (two last digits).
type is an identifier of the type of equipment.
Value assignment: manufacturer specific, with ‘FFh’ reserved value.
manufacturerCode: is the numerical code identifying a manufacturer of type approved equipment.
Generation 2:
Image omitted; see official source
serialNumber see Generation 1
monthYear see Generation 1
type indicates the type of equipment
manufacturerCode: see Generation 1.
2.73. FullCardNumber
Code fully identifying a tachograph card.
Image omitted; see official source
cardType is the type of the tachograph card.
cardIssuingMemberState is the code of the Member State having issued the card.
cardNumber is the card number.
2.74. FullCardNumberAndGeneration
Generation 2:
Code fully identifying a tachograph card and its generation.
Image omitted; see official source
fullcardNumber identifies the tachograph card.
generation indicates the generation of the tachograph card used.
2.75. Generation
Generation 2:
Indicates the generation of tachograph used.
Image omitted; see official source
Value assignment:
- ‘00’H RFU
- ‘01’H Generation 1
- ‘02’H Generation 2
- ‘03’H .. ‘FF’H RFU
2.76. GeoCoordinates
Generation 2:
The 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. Longitude and latitude of an unknown position shall be represented as Hex ‘7FFFFF’ (Decimal 8388607).
Image omitted; see official source
latitude is encoded as a multiple (factor 10) of the ±DDMM.M representation.
longitude is encoded as a multiple (factor 10) of the ±DDDMM.M representation.
2.77. GNSSAccuracy
Generation 2:
The 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.
Image omitted; see official source
2.78. GNSSAccumulatedDriving
Generation 2:
Information, 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).
Image omitted; see official source
gnssADPointerNewestRecord is the index of the last updated GNSS accumulated driving record.
Value 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.
gnssAccumulatedDrivingRecords 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.
2.79. GNSSAccumulatedDrivingRecord
Generation 2:
Information, 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)
Image omitted; see official source
timeStamp is the date and time when the accumulated driving time reaches a multiple of three hours.
gnssPlaceRecord contains information related to the position of the vehicle.
vehicleOdometerValue is the odometer value when the accumulated driving time reaches a multiple of three hours.
2.79a. GNSSAuthAccumulatedDriving
Generation 2, version 2:
Information, stored in a driver or workshop card, providing the authentication status of GNSS positions of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirements 306d and 356d).
Image omitted; see official source
gnssAuthADPointerNewestRecord is the index of the last updated GNSS position authentication status record.
Value assignment is the number corresponding to the numerator of the GNSS position authentication status record, beginning with '0' for the first occurrence of the GNSS position authentication status record in the structure.
gnssAuthStatusADRecords is the set of records containing the date and time the accumulated driving reaches a multiple of three hours and the authentication status of the GNSS position.
2.79b. GNSSAuthStatusADRecord
Generation 2, version 2:
Information, stored in a driver or workshop card, providing the authentication status of a GNSS position of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirements 306c and 356c). Other information related to the GNSS position itself is stored in another record (see 2.79 GNSSAccumulatedDrivingRecord).
Image omitted; see official source
timeStamp is the date and time when the accumulated driving time reaches a multiple of three hours (which is the same date and time as in the corresponding GNSSAccumulatedDrivingRecord).
authenticationStatus is the authentication status of the GNSS position when the accumulated driving time reaches a multiple of three hours.
2.79c. GNSSPlaceAuthRecord
Generation 2, version 2:
Information related to the GNSS position of the vehicle (Annex IC requirements 108, 109, 110, 296, 306a, 306c, 306e, 306g, 356a, 356c, 356e and 356g).
Image omitted; see official source
timeStamp is the date and time when the GNSS position of the vehicle was determined.
gnssAccuracy is the accuracy of the GNSS position data.
geoCoordinates is the recorded location using GNSS.
authenticationStatus is the authentication status of the GNSS position when it was determined.
2.80. GNSSPlaceRecord
Generation 2:
Information related to the GNSS position of the vehicle (Annex 1C requirements 108, 109, 110, 296, 305, 347, and 353).
Image omitted; see official source
timeStamp is the date and time when the GNSS position of the vehicle was determined.
gnssAccuracy is the accuracy of the GNSS position data.
geoCoordinates is the recorded location using GNSS.
2.81. HighResOdometer
Odometer value of the vehicle: Accumulated distance travelled by the vehicle during its operation.
Image omitted; see official source
Value assignment: Unsigned binary. Value in 1/200 km in the operating range 0 to 21 055 406 km.
2.82. HighResTripDistance
A distance travelled during all or part of a journey.
Image omitted; see official source
Value assignment: Unsigned binary. Value in 1/200 km in the operating range 0 to 21 055 406 km.
2.83. HolderName
The surname and first name(s) of a card holder.
Image omitted; see official source
holderSurname is the surname (family name) of the holder. This surname does not include titles.
Value assignment: When a card is not personal, holderSurname contains the same information as companyName or workshopName or controlBodyName.
holderFirstNames is the first name(s) and initials of the holder.
2.84. Reserved for future use
Generation 2:
Information 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.
Image omitted; see official source
2.85. K-ConstantOfRecordingEquipment
Constant of the recording equipment (definition m)).
Image omitted; see official source
Value assignment: Pulses per kilometer in the operating range 0 to 64 255 pulses/km.
2.86. KeyIdentifier
A unique identifier of a Public Key used to reference and select the key. It also identifies the holder of the key.
Image omitted; see official source
The first choice is suitable to reference the public key of a Vehicle Unit, of a tachograph card or of an external GNSS facility.
The 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).
The third choice is suitable to reference the public key of a Member State.
2.87. KMWCKey
Generation 2:
AES key and its associated key version used for VU — Motion Sensor pairing. For details see Appendix 11.
Image omitted; see official source
kMWCKey is the length of the AES key concatenated with the key which is used for VU — Motion Sensor pairing.
keyVersion denotes the key version of the AES key.
2.88. Language
Code identifying a language.
Image omitted; see official source
Value assignment: Two-letter lower-case coding according to ISO 639.
2.89. LastCardDownload
Date 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.
Image omitted; see official source
Value assignment: not further specified.
2.89a. LengthOfFollowingData
Generation 2, version 2:
Length indicator for extensible records.
Image omitted; see official source
Value assignment: See Appendix 2.
2.90. LinkCertificate
Generation 2:
The link certificate between European Root CA key pairs.
Image omitted; see official source
2.90a. LoadType
Generation 2, version 2:
Code identifying a load type entered.
Image omitted; see official source
Value assignment:
- ‘00’H Undefined load type,
- ‘01’H Goods,
- ‘02’H Passengers,
- ‘03’H .. ‘FF’H RFU.
2.91. L-TyreCircumference
Effective circumference of the wheel tyres (definition u)).
Image omitted; see official source
Value assignment: Unsigned binary, value in 1/8 mm in the operating range 0 to 8 031 mm.
2.92. MAC
Generation 2:
A cryptographic check sum of 8, 12 or 16 bytes length corresponding to the cipher suites specified in Appendix 11.
Image omitted; see official source
2.93. ManualInputFlag
Code identifying whether a cardholder has manually entered driver activities at card insertion or not (Annex 1B requirement 081 and Annex 1C requirement 102).
Image omitted; see official source
Value assignment: not further specified.
2.94. ManufacturerCode
Code identifying a manufacturer of type approved equipment.
Image omitted; see official source
The laboratory competent for interoperability tests maintains and publishes the list of manufacturer codes on its web site (Annex 1C requirement 454).
ManufacturerCodes are provisionally assigned to developers of tachograph equipment on application to the laboratory competent for interoperability tests.
2.95. ManufacturerSpecificEventFaultData
Generation 2:
Manufacturer specific error codes simplify the error analysis and maintenance of vehicle units.
Image omitted; see official source
manufacturerCode identifies the manufacturer of the Vehicle Unit.
manufacturerSpecificErrorCode is an error code specific to the manufacturer.
2.96. MemberStateCertificate
The certificate of the public key of a member state issued by the European certification authority.
Image omitted; see official source
2.97. MemberStateCertificateRecordArray
Generation 2:
The member state certificate plus metadata as used in the download protocol.
Image omitted; see official source
recordType denotes the type of the record (MemberStateCertificate). Value Assignment: See RecordType
recordSize is the size of the MemberStateCertificate in bytes.
noOfRecords is the number of records in the set records. The value shall be set to 1 as the certficates may have different lengths.
records is the set of member state certificates.
2.98. MemberStatePublicKey
Generation 1:
The public key of a Member State.
Image omitted; see official source
2.99. Name
A name.
Image omitted; see official source
codePage specifies a character set defined in Chapter 4,
name is a name encoded using the specified character set.
2.100. NationAlpha
Alphabetic 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).
Image omitted; see official source
The 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.
2.101. NationNumeric
Numerical reference to a country.
Image omitted; see official source
Value assignment: see data type 2.100 (NationAlpha).
Any 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.
2.101a. NoOfBorderCrossingRecords
Generation 2, version 2:
Number of border crossing records a driver or workshop card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.102. NoOfCalibrationRecords
Number of calibration records, a workshop card can store.
Generation 1:
Image omitted; see official source
Value assignment: see Appendix 2.
Generation 2:
Image omitted; see official source
Value assignment: see Appendix 2.
2.103. NoOfCalibrationsSinceDownload
Counter indicating the number of calibrations performed with a workshop card since its last download (Annex 1C requirement 317 and 340).
Image omitted; see official source
Value assignment: Not specified further.
2.104. NoOfCardPlaceRecords
Number of place records a driver or workshop card can store.
Generation 1:
Image omitted; see official source
Value assignment: see Appendix 2.
Generation 2:
Image omitted; see official source
Value assignment: see Appendix 2.
2.105. NoOfCardVehicleRecords
Number of vehicles used records a driver or workshop card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.106. NoOfCardVehicleUnitRecords
Generation 2:
Number of vehicle units used records a driver or workshop card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.107. NoOfCompanyActivityRecords
Number of company activity records, a company card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.108. NoOfControlActivityRecords
Number of control activity records, a control card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.109. NoOfEventsPerType
Number of events per type of event a card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.110. NoOfFaultsPerType
Number of faults per type of fault a card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.111. NoOfGNSSADRecords
Generation 2:
Number of GNSS accumulated driving records a card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.111a. NoOfLoadUnloadRecords
Generation 2, version 2:
Number of load/unload records a card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.112. NoOfSpecificConditionRecords
Generation 2:
Number of specific condition records a card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.112a. NoOfLoadTypeEntryRecords
Generation 2, version 2:
Number of load type entry records a driver or workshop card can store.
Image omitted; see official source
Value assignment: see Appendix 2.
2.113. OdometerShort
Odometer value of the vehicle in a short form.
Image omitted; see official source
Value assignment: Unsigned binary. Value in km in the operating range 0 to 9 999 999 km.
2.114. OdometerValueMidnight
The vehicle's odometer value at midnight on a given day (Annex 1B requirement 090 and Annex 1C requirement 113).
Image omitted; see official source
Value assignment: not further specified.
2.114a. OperationType
Generation 2, version 2:
Code identifying a type of operation entered.
Image omitted; see official source
Value assignment:
- ‘00’H RFU,
- ‘01’H Load operation,
- ‘02’H Unload operation,
- ‘03’H Simultaneous load/unload operation,
- ‘04’H .. ‘FF’H RFU.
2.115. OdometerValueMidnightRecordArray
Generation 2:
The OdometerValueMidnight plus metadata used in the download protocol.
Image omitted; see official source
recordType denotes the type of the record (OdometerValueMidnight). Value Assignment: See RecordType
recordSize is the size of the OdometerValueMidnight in bytes.
noOfRecords is the number of records in the set records.
records is the set of OdometerValueMidnight records.
2.116. OverspeedNumber
Number of over speeding events since the last over speeding control.
Image omitted; see official source
Value 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.
2.116a. PlaceAuthRecord
Information related to a place where a daily work period begins or ends (Annex IC requirements 108, 271, 296, 324 and 347).
Generation 2, version 2:
Image omitted; see official source
entryTime is a date and time related to the entry.
entryTypeDailyWorkPeriod is the type of entry.
dailyWorkPeriodCountry is the country entered.
dailyWorkPeriodRegion is the region entered.
vehicleOdometerValue is the odometer value at the time of place entry.
entryGNSSPlaceAuthRecord is the recorded location, GNSS authentication status and time.
2.116b. PlaceAuthStatusRecord
Generation 2, version 2:
Information, stored in a driver or workshop card, providing the authentication status of a place where a daily work period begins or ends (Annex IC requirements 306a and 356a). Other information related to the place itself is stored in another record (see 2.117 PlaceRecord).
Image omitted; see official source
entryTime is a date and time related to the entry (which is the same date and time as in the corresponding PlaceRecord).
authenticationStatus is the authentication status of the recorded GNSS position.
2.117. PlaceRecord
Information related to a place where a daily work period begins or ends (Annex 1C requirements 108, 271, 296, 324, and 347).
Generation 1:
Image omitted; see official source
entryTime is a date and time related to the entry.
entryTypeDailyWorkPeriod is the type of entry.
dailyWorkPeriodCountry is the country entered.
dailyWorkPeriodRegion is the region entered.
vehicleOdometerValue is the odometer value at the time of place entry.
Generation 2:
Image omitted; see official source
In addition to Generation 1 the following component is used:
entryGNSSPlaceRecord is the recorded location and time.
2.117a. PositionAuthenticationStatus
Generation 2, version 2:
Image omitted; see official source
Value assignment (see Appendix 12):
- ‘00’H Not Authenticated (see Appendix 12, requirement GNS_39),
- ‘01’H Authenticated (see Appendix 12, requirement GNS_39),
- ‘02’H .. ‘FF’H RFU.
2.118. PreviousVehicleInfo
Information 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).
Generation 1:
Image omitted; see official source
vehicleRegistrationIdentification is the VRN and the registering Member State of the vehicle.
cardWithdrawalTime is the card withdrawal date and time.
Generation 2:
Image omitted; see official source
In addition to generation 1 the following data element is used:
vuGeneration identifies the generation of the vehicle unit.
2.119. PublicKey
Generation 1:
A public RSA key.
Image omitted; see official source
rsaKeyModulus is the Modulus of the key pair.
rsaKeyPublicExponent is the public exponent of the key pair.
2.120. RecordType
Generation 2:
Reference to a record type. This data type is used in RecordArrays.
Image omitted; see official source
Value assignment:
| Image omitted; see official source | ActivityChangeInfo, CardSlotsStatus, CurrentDateTime, MemberStateCertificate, OdometerValueMidnight, DateOfDayDownloaded, SensorPaired, Signature, SpecificConditionRecord, VehicleIdentificationNumber, VehicleRegistrationNumber, VuCalibrationRecord, VuCardIWRecord, VuCardRecord, VuCertificate, VuCompanyLocksRecord, VuControlActivityRecord, VuDetailedSpeedBlock, VuDownloadablePeriod, VuDownloadActivityData, VuEventRecord, VuGNSSADRecord, VuITSConsentRecord, VuFaultRecord, VuIdentification, VuOverSpeedingControlData, VuOverSpeedingEventRecord, VuPlaceDailyWorkPeriodRecord, VuTimeAdjustmentGNSSRecord, VuTimeAdjustmentRecord, VuPowerSupplyInterruptionRecord, SensorPairedRecord, SensorExternalGNSSCoupledRecord, VuBorderCrossingRecord, VuLoadUnloadRecord, VehicleRegistrationIdentification, RFU, Manufacturer specific. |
2.121. RegionAlpha
Alphabetic reference to a region within a specified country.
Image omitted; see official source
Generation 1:
Value assignment:
Image omitted; see official source
Generation 2:
The RegionAlpha codes shall be held on a list maintained on the website of the laboratory appointed to carry out interoperability testing.
2.122. RegionNumeric
Numerical reference to a region within a specified country.
Image omitted; see official source
Generation 1:
Value assignment:
Image omitted; see official source
Generation 2:
The RegionNumeric codes shall be held on a list maintained on the website of the laboratory appointed to carry out interoperability testing.
2.123. RemoteCommunicationModuleSerialNumber
Generation 2:
Serial number of the Remote Communication Module.
Image omitted; see official source
2.124. RSAKeyModulus
Generation 1:
The modulus of a RSA key pair.
Image omitted; see official source
Value assignment: Unspecified.
2.125. RSAKeyPrivateExponent
Generation 1:
The private exponent of a RSA key pair.
Image omitted; see official source
Value assignment: Unspecified.
2.126. RSAKeyPublicExponent
Generation1:
The public exponent of a RSA key pair.
Image omitted; see official source
Value assignment: Unspecified.
2.127. RtmData
Generation2:
For the definition of this data type see Appendix 14.
2.128. SealDataCard
Generation 2:
This 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.
Image omitted; see official source
noOfSealRecords is the number of records in sealRecords.
sealRecords is a set of seal records.
2.129. SealDataVu
Generation 2:
This 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.
Image omitted; see official source
sealRecords 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.
2.130. SealRecord
Generation 2:
This data type stores information about a seal that is attached to a component. This data type is related to Annex 1C requirement 337.
Image omitted; see official source
equipmentType identifies the type of equipment the seal is attached to.
extendedSealIdentifier is the identifier of the seal attached to the equipment.
2.131. SensorApprovalNumber
Type approval number of the sensor.
Generation 1:
Image omitted; see official source
Value assignment: Unspecified.
Generation 2:
Image omitted; see official source
Value assignment:
The 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.
2.132. SensorExternalGNSSApprovalNumber
Generation 2:
Type approval number of the external GNSS facility.
Image omitted; see official source
Value assignment:
The 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.
2.133. SensorExternalGNSSCoupledRecord
Generation 2:
Information, stored in a vehicle unit, related to the identification of the external GNSS facility coupled with the vehicle unit (Annex 1C requirement 100).
Image omitted; see official source
sensorSerialNumber is the serial number of the external GNSS facility coupled with the vehicle unit.
sensorApprovalNumber is the approval number of this external GNSS facility.
sensorCouplingDate is a date of coupling of this external GNSS facility with the vehicle unit.
2.134. SensorExternalGNSSIdentification
Generation 2:
Information related to the identification of the external GNSS facility (Annex 1C requirement 98).
Image omitted; see official source
sensorSerialNumber is the extended serial number of the external GNSS facility.
sensorApprovalNumber is the approval number of the external GNSS facility.
sensorSCIdentifier is the identifier of the security component of the external GNSS facility.
sensorOSIdentifier is the identifier of the operating system of the external GNSS facility.
2.135. SensorExternalGNSSInstallation
Generation 2:
Information, stored in an external GNSS facility, related to the installation of the external GNSS sensor (Annex 1C requirement 123).
Image omitted; see official source
sensorCouplingDateFirst is the date of the first coupling of external GNSS facility with a vehicle unit.
firstVuApprovalNumber is the approval number of the first vehicle unit coupled with the external GNSS facility.
firstVuSerialNumber is the serial number of the first vehicle unit paired with the external GNSS facility.
sensorCouplingDateCurrent is the date of the current coupling of external GNSS facility with a vehicle unit.
currentVuApprovalNumber is the approval number of the vehicle unit currently coupled with the external GNSS facility.
currentVUSerialNumber is the serial number of the vehicle unit currently coupled with the external GNSS facility.
2.136. SensorExternalGNSSOSIdentifier
Generation 2:
Identifier of the operating system of the external GNSS facility.
Image omitted; see official source
Value assignment: manufacturer specific.
2.137. SensorExternalGNSSSCIdentifier
Generation 2:
This type is used e.g. to identify the cryptographic module of the external GNSS facility.
Identifier of the security component of the external GNSS facility.
Image omitted; see official source
Value assignment: component manufacturer specific.
2.138. SensorGNSSCouplingDate
Generation 2:
Date of a coupling of the external GNSS facility with a vehicle unit.
Image omitted; see official source
Value assignment: Unspecified.
2.139. SensorGNSSSerialNumber
Generation 2:
This 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.
Serial number of the GNSS receiver.
Image omitted; see official source
2.140. SensorIdentification
Information, stored in a motion sensor, related to the identification of the motion sensor (Annex 1B requirement 077 and Annex 1C requirement 95).
Image omitted; see official source
sensorSerialNumber is the extended serial number of the motion sensor (includes part number and manufacturer code).
sensorApprovalNumber is the approval number of the motion sensor.
sensorSCIdentifier is the identifier of the security component of the motion sensor.
sensorOSIdentifier is the identifier of the operating system of the motion sensor.
2.141. SensorInstallation
Information, stored in a motion sensor, related to the installation of the motion sensor (Annex 1B requirement 099 and Annex 1C requirement 122).
Image omitted; see official source
sensorPairingDateFirst is the date of the first pairing of the motion sensor with a vehicle unit.
firstVuApprovalNumber is the approval number of the first vehicle unit paired with the motion sensor.
firstVuSerialNumber is the serial number of the first vehicle unit paired with the motion sensor.
sensorPairingDateCurrent is the date of the current pairing of the motion sensor with the vehicle unit.
currentVuApprovalNumber is the approval number of the vehicle unit currently paired with the motion sensor.
currentVUSerialNumber is the serial number of the vehicle unit currently paired with the motion sensor.
2.142. SensorInstallationSecData
Information, stored in a workshop card, related to the security data needed for pairing motion sensors to vehicle units (Annex 1C requirement 308 and 331).
Generation 1:
Image omitted; see official source
Value assignment: in accordance with ISO 16844-3.
Generation 2:
As described in Appendix 11 a workshop card shall store up to three keys for VU Motion Sensor pairing. These keys have different key versions.
Image omitted; see official source
2.143. SensorOSIdentifier
Identifier of the operating system of the motion sensor.
Image omitted; see official source
Value assignment: manufacturer specific.
2.144. SensorPaired
Generation 1:
Information, stored in a vehicle unit, related to the identification of the motion sensor paired with the vehicle unit (Annex 1B requirement 079).
Image omitted; see official source
sensorSerialNumber is the serial number of the motion sensor currently paired with the vehicle unit.
sensorApprovalNumber is the approval number of the motion sensor currently paired with the vehicle unit.
sensorPairingDateFirst is the date of the first pairing with a vehicle unit of the motion sensor currently paired with the vehicle unit.
2.145. SensorPairedRecord
Generation 2:
Information, stored in a vehicle unit, related to the identification of a motion sensor paired with the vehicle unit (Annex 1C requirement 97).
Image omitted; see official source
sensorSerialNumber is the serial number of a motion sensor paired with the vehicle unit.
sensorApprovalNumber is the approval number of this motion sensor.
sensorPairingDate is a date of pairing of this motion sensor with the vehicle unit.
2.146. SensorPairingDate
Date of a pairing of the motion sensor with a vehicle unit.
Image omitted; see official source
Value assignment: Unspecified.
2.147. SensorSCIdentifier
Identifier of the security component of the motion sensor.
Image omitted; see official source
Value assignment: component manufacturer specific.
2.148. SensorSerialNumber
Serial number of the motion sensor.
Image omitted; see official source
2.149. Signature
A digital signature.
Generation 1:
Image omitted; see official source
Value assignment: in accordance with Appendix 11 Common security mechanisms.
Generation 2:
Image omitted; see official source
Value assignment: in accordance with Appendix 11 Common security mechanisms.
2.150. SignatureRecordArray
Generation 2:
A set of signatures plus metadata used in the download protocol.
Image omitted; see official source
recordType denotes the type of the record (Signature). Value Assignment: See RecordType
recordSize is the size of the Signature in bytes.
noOfRecords is the number of records in the set records. The value shall be set to 1 as the signatures may have different lengths.
records is the set of signatures.
2.151. SimilarEventsNumber
The number of similar events for one given day (Annex 1B requirement 094 and Annex 1C requirement 117).
Image omitted; see official source
Value 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.
2.152. SpecificConditionRecord
Information, 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).
Image omitted; see official source
entryTime is the date and time of the entry.
specificConditionType is the code identifying the specific condition.
2.153. SpecificConditions
Information, 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).
Generation 2:
Image omitted; see official source
conditionPointerNewestRecord is the index of the last updated specific condition record.
Value 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.
specificConditionRecords is the set of records containing information on the specific conditions recorded.
2.154. SpecificConditionType
Code identifying a specific condition (Annex 1B requirements 050b, 105a, 212a and 230a and Annex 1C requirements 62).
Image omitted; see official source
Generation 1:
Value assignment:
- ‘00’H RFU
- ‘01’H Out of scope — Begin
- ‘02’H Out of scope — End
- ‘03’H Ferry / Train crossing
- ‘04’H .. ‘FF’H RFU
Generation 2:
Value assignment:
- ‘00’H RFU
- ‘01’H Out of scope — Begin
- ‘02’H Out of scope — End
- ‘03’H Ferry / Train crossing — Begin
- ‘04’H Ferry / Train crossing — End
- ‘05’H .. ‘FF’H RFU
2.155. Speed
Speed of the vehicle (km/h).
Image omitted; see official source
Value assignment: kilometers per hour in the operational range 0 to 220 km/h.
2.156. SpeedAuthorised
Maximum authorised Speed of the vehicle (definition hh)).
Image omitted; see official source
2.157. SpeedAverage
Average speed in a previously defined duration (km/h).
Image omitted; see official source
2.158. SpeedMax
Maximum speed measured in a previously defined duration.
Image omitted; see official source
2.158a. TachographCardsGen1Suppression
Generation 2, version 2:
Ability of a second generation VU to use first generation of driver, control and company cards (see Appendix 15, MIG_002).
Image omitted; see official source
Value assignment:
- ‘0000’H The VU is able to use the generation 1 of tachograph cards (default value),
- ‘A5E3’H The VU is not able to use the tachograph cards generation 1,
All other values Not used.
2.159. TachographPayload
Generation 2:
For the definition of this data type see Appendix 14.
2.160. Reserved for future use
2.161. TDesSessionKey
Generation 1:
A triple DES session key.
Image omitted; see official source
Value assignment: not further specified.
2.162. TimeReal
Code 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.
Image omitted; see official source
Value assignment – Octet aligned: Number of seconds since midnight 1 January 1970 UTC.
The max. possible date/time is in the year 2106.
2.163. TyreSize
Designation of tyre dimensions.
Image omitted; see official source
Value assignment: in accordance with Directive 92/23 (EEC) 31/03/92 O.J. L129 p.95.
2.164. VehicleIdentificationNumber
Vehicle Identification Number (VIN) referring to the vehicle as a whole, normally chassis serial number or frame number.
Image omitted; see official source
Value assignment: As defined in ISO 3779.
2.165. VehicleIdentificationNumberRecordArray
Generation 2:
The Vehicle Idenification Number plus metadata as used in the download protocol.
Image omitted; see official source
recordType denotes the type of the record (VehicleIdentificationNumber). Value Assignment: See RecordType
recordSize is the size of the VehicleIdentificationNumber in bytes.
noOfRecords is the number of records in the set records.
records is the set of vehicle identification numbers.
2.166. VehicleRegistrationIdentification
Identification of a vehicle, unique for Europe (VRN and Member State).
Image omitted; see official source
vehicleRegistrationNation is the nation where the vehicle is registered.
vehicleRegistrationNumber is the registration number of the vehicle (VRN).
2.166a. VehicleRegistrationIdentificationRecordArray
Generation 2, version 2:
The Vehicle Registration Identification plus metadata as used in the download protocol.
Image omitted; see official source
recordType denotes the type of the record (VehicleRegistrationIdentification). Value assignment: see RecordType.
recordSize is the size of the VehicleRegistrationIdentification in bytes.
noOfRecords is the number of records in the set records.
records is the set of vehicle registration identification.
2.167. VehicleRegistrationNumber
Registration number of the vehicle (VRN). The registration number is assigned by the vehicle licensing authority.
Image omitted; see official source
codePage specifies a character set defined in Chapter 4,
vehicleRegNumber is a VRN encoded using the specified character set.
Value assignment: Country specific.
2.168. VehicleRegistrationNumberRecordArray
Generation 2, version 1:
The Vehicle Registration Number plus metadata as used in the download protocol.
Image omitted; see official source
recordType denotes the type of the record (VehicleRegistrationNumber). Value Assignment: See RecordType
recordSize is the size of the VehicleRegistrationNumber in bytes.
noOfRecords is the number of records in the set records.
records is the set of vehicle registration numbers.
2.169. VuAbility
Generation 2:
Information stored in a VU on the ability of the VU to use generation 1 tachograph cards or not (Annex 1C requirement 121).
Image omitted; see official source
Value assignment — Octet Aligned: ‘xxxxxxxa’B (8 bits)
For the ability to support of generation 1:
- ‘a’B Ability to support generation 1 tachograph cards:
‘0’ B Generation 1 is supported,
‘1’B Generation1 is not supported,
- ‘xxxxxxx’B RFU
2.170. VuActivityDailyData
Generation 1:
Information, 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.
Image omitted; see official source
noOfActivityChanges is the number of ActivityChangeInfo words in the activityChangeInfos set.
activityChangeInfos 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.
2.171. VuActivityDailyRecordArray
Generation 2:
Information, 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.
Image omitted; see official source
recordType denotes the type of the record (ActivityChangeInfo). Value Assignment: See RecordType
recordSize is the size of the ActivityChangeInfo in bytes.
noOfRecords is the number of records in the set records.
records 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.
2.172. VuApprovalNumber
Type approval number of the vehicle unit.
Generation 1:
Image omitted; see official source
Value assignment: Unspecified.
Generation 2:
Image omitted; see official source
Value assignment:
The 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.
2.173. VuCalibrationData
Generation 1:
Information, stored in a vehicle unit, related to the calibrations of the recording equipment (Annex 1B requirement 098).
Image omitted; see official source
noOfVuCalibrationRecords is the number of records contained in the vuCalibrationRecords set.
vuCalibrationRecords is the set of calibration records.
2.174. VuCalibrationRecord
Information, stored in a vehicle unit, related a calibration of the recording equipment (Annex 1B requirement 098 and Annex 1C requirement 119 and 120).
Generation 1:
Image omitted; see official source
calibrationPurpose is the purpose of the calibration.
workshopName, workshopAddress are the workshop name and address.
workshopCardNumber identifies the workshop card used during the calibration.
workshopCardExpiryDate is the card expiry date.
vehicleIdentificationNumber is the VIN.
vehicleRegistrationIdentification contains the VRN and registering Member State.
wVehicleCharacteristicConstant is the characteristic coefficient of the vehicle.
kConstantOfRecordingEquipment is the constant of the recording equipment.
lTyreCircumference is the effective circumference of the wheel tyres.
tyreSize is the designation of the dimension of the tyres mounted on the vehicle
authorisedSpeed is the authorised speed of the vehicle.
oldOdometerValue, newOdometerValue are the old and new values of the odometer.
oldTimeValue, newTimeValue are the old and new values of date and time.
nextCalibrationDate is the date of the next calibration of the type specified in CalibrationPurpose to be carried out by the authorised inspection authority.
Generation 2, version 1:
Image omitted; see official source
In addition to generation 1 the following data element is used:
sealDataVu gives information about the seals that are attached to different components of the vehicle.
Generation 2, version 2:
Image omitted; see official source
In addition to generation 1 the following data element is used:
sensorSerialNumber is the serial number of the motion sensor paired with the vehicle unit at the end of the calibration,
sensorGNSSSerialNumber is the serial number of the external GNSS facility coupled with the vehicle unit at the end of the calibration (if any),
rcmSerialNumber is the serial number of the remote communication facility coupled with the vehicle unit at the end of the calibration (if any),
sealDataVu gives information about the seals that are attached to different components of the vehicle.
byDefaultLoadType is the by-default load type of the vehicle (only present in version 2).
calibrationCountry is the country in which the calibration has been performed.
calibrationCountryTimestamp is the date and time when the position used to determine the country in which the calibration has been performed was provided by the GNSS receiver.
2.175. VuCalibrationRecordArray
Generation 2:
Information, stored in a vehicle unit, related to the calibrations of the recording equipment (Annex 1C requirement 119 and 120).
Image omitted; see official source
recordType denotes the type of the record (VuCalibrationRecord). Value Assignment: See RecordType
recordSize is the size of the VuCalibrationRecord in bytes.
noOfRecords is the number of records in the set records.
records is the set of calibration records.
2.176. VuCardIWData
Generation 1:
Information, 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).
Image omitted; see official source
noOfIWRecords is the number of records in the set vuCardIWRecords.
vuCardIWRecords is a set of records related to card insertion withdrawal cycles.
2.177. VuCardIWRecord
Information, 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).
Generation 1:
Image omitted; see official source
cardHolderName is the driver or workshop card holder's surname and first names as stored in the card.
fullCardNumber is the type of card, its issuing Member State and its card number as stored in the card.
cardExpiryDate is the card's expiry date as stored in the card.
cardInsertionTime is the insertion date and time.
vehicleOdometerValueAtInsertion is the vehicle odometer value at card insertion.
cardSlotNumber is the slot in which the card is inserted.
cardWithdrawalTime is the withdrawal date and time.
vehicleOdometerValueAtWithdrawal is the vehicle odometer value at card withdrawal.
previousVehicleInfo contains information about the previous vehicle used by the driver, as stored in the card.
manualInputFlag is a flag identifying if the cardholder has manually entered driver activities at card insertion.
Generation 2:
Image omitted; see official source
Instead of fullCardNumber the generation 2 data structure makes use of the following data element.
fullCardNumberAndGeneration is the type of card, its issuing Member State, its card number and generation as stored in the card.
2.178. VuCardIWRecordArray
Generation 2:
Information, 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).
Image omitted; see official source
recordType denotes the type of the record (VuCardIWRecord). Value Assignment: See RecordType
recordSize is the size of the VuCardIWRecord in bytes.
noOfRecords is the number of records in the set records.
records is a set of records related to card insertion withdrawal cycles.
2.179. VuCardRecord
Generation 2:
Information, stored in a vehicle unit, about a tachograph card used (Annex IC requirement 132).
Image omitted; see official source
cardNumberAndGenerationInformation is the full card number and generation of the card used (data type 2.74).
cardExtendedSerialNumber as read from the file EF_ICC under the MF of the card.
cardStructureVersion as read from the file EF_Application_Identification under the DF_Tachograph_G2.
cardNumber as read from the file EF_Identification under the DF_Tachograph_G2.
2.180. VuCardRecordArray
Generation 2:
Information 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).
Image omitted; see official source
recordType denotes the type of the record (VuCardRecord). Value Assignment: See RecordType
recordSize is the size of the VuCardRecord in bytes.
noOfRecords is the number of records in the set records.
records is a set of records related to the tachograph cards used with the VU.
2.181. VuCertificate
Certificate of the public key of a vehicle unit.
Image omitted; see official source
2.182. VuCertificateRecordArray
Generation 2:
The VU certificate plus metadata as used in the download protocol.
Image omitted; see official source
recordType denotes the type of the record (VuCertificate). Value Assignment: See RecordType
recordSize is the size of the VuCertificate in bytes.
noOfRecords is the number of records in the set records. The value shall be set to 1 as the certificates may have different lengths.
records is a set of VU certificates.
2.183. VuCompanyLocksData
Generation 1:
Information, stored in a vehicle unit, related to company locks (Annex 1B requirement 104).
Image omitted; see official source
noOfLocks is the number of locks listed in vuCompanyLocksRecords.
vuCompanyLocksRecords is the set of company locks records.
2.184. VuCompanyLocksRecord
Information, stored in a vehicle unit, related to one company lock (Annex 1B requirement 104 and Annex 1C requirement 128).
Generation 1:
Image omitted; see official source
lockInTime, lockOutTime are the date and time of lock-in and lock-out.
companyName, companyAddress are the company name and address related with the lock-in.
companyCardNumber identifies the card used at lock-in.
Generation 2:
Image omitted; see official source
Instead of companyCardNumber the generation 2 data structure makes use of the following data element.
companyCardNumberAndGeneration identifies the card including its generation used at lock-in.
2.185. VuCompanyLocksRecordArray
Generation 2:
Information, stored in a vehicle unit, related to company locks (Annex 1C requirement 128).
Image omitted; see official source
recordType denotes the type of the record (VuCompanyLocksRecord). Value Assignment: See RecordType
recordSize is the size of the VuCompanyLocksRecord in bytes.
noOfRecords is the number of records in the set records. Value 0..255.
records is the set of company locks records.
2.185a. VuConfigurationLengthRange
Generation 2, version 2:
Number of bytes in a tachograph card, available to store VU configurations.
Image omitted; see official source
Value assignment: see Appendix 2.
2.186. VuControlActivityData
Generation 1:
Information, stored in a vehicle unit, related to controls performed using this VU (Annex 1B requirement 102).
Image omitted; see official source
noOfControls is the number of controls listed in vuControlActivityRecords.
vuControlActivityRecords is the set of control activity records.
2.187. VuControlActivityRecord
Information, stored in a vehicle unit, related to a control performed using this VU (Annex 1B requirement 102 and Annex 1C requirement 126).
Generation 1:
Image omitted; see official source
controlType is the type of the control.
controlTime is the date and time of the control.
controlCardNumber identifies the control card used for the control.
downloadPeriodBeginTime is the begin time of the downloaded period, in case of downloading.
downloadPeriodEndTime is the end time of the downloaded period, in case of downloading.
Generation 2:
Image omitted; see official source
Instead of controlCardNumber the generation 2 data structure makes use of the following data element.
controlCardNumberAndGeneration identifies the control card including its generation used for the control.
2.188. VuControlActivityRecordArray
Generation 2:
Information, stored in a vehicle unit, related to controls performed using this VU (Annex 1C requirement 126).
Image omitted; see official source
recordType denotes the type of the record (VuControlActivityRecord). Value Assignment: See RecordType
recordSize is the size of the VuControlActivityRecord in bytes.
noOfRecords is the number of records in the set records.
records is the set of VU control activity records.
2.189. VuDataBlockCounter
Counter, stored in a card, identifying sequentially the insertion withdrawal cycles of the card in vehicle units.
Image omitted; see official source
Value assignment: Consecutive Number with max, value 9 999, starting again with 0.
2.190. VuDetailedSpeedBlock
Information, 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).
Image omitted; see official source
speedBlockBeginDate is the date and time of the first speed value within the block.
speedsPerSecond is the chronological sequence of measured speeds every seconds for the minute starting at speedBlockBeginDate (included).
2.191. VuDetailedSpeedBlockRecordArray
Generation 2:
Information, stored in a vehicle unit, related to the detailed speed of the vehicle.
Image omitted; see official source
recordType denotes the type of the record (VuDetailedSpeedBlock). Value Assignment: See RecordType
recordSize is the size of the VuDetailedSpeedBlock in bytes.
noOfRecords is the number of records in the set records.
records is the set of detailed speed blocks.
2.192. VuDetailedSpeedData
Generation 1:
Information, stored in a vehicle unit, related to the detailed speed of the vehicle.
Image omitted; see official source
noOfSpeedBlocks is the number of speed blocks in the vuDetailedSpeedBlocks set.
vuDetailedSpeedBlocks is the set of detailed speed blocks.
2.192a. VuDigitalMapVersion
Generation 2, version 2:
Version of the digital map stored in the vehicle unit (Annex IC requirement 133j).
Image omitted; see official source
Value assignment: as specified on the dedicated secured website made available by the European Commission (Annex IC requirement 133k).
2.193. VuDownloadablePeriod
Reading this document does not replace reading the official text published in the Official Journal of the European Union. We assume no responsibility for any inaccuracies arising from the conversion of the original to this format.
This text is published under EUR-Lex's own terms of reuse, not a Legalize or public-domain licence.
EUR-Lex
Creative Commons Attribution 4.0 International (CC BY 4.0)
© European Union, https://eur-lex.europa.eu — Source: EUR-Lex (Publications Office of the European Union). Reused under the Creative Commons Attribution 4.0 International (CC BY 4.0) licence. Only EU legislation published in the printed Official Journal of the European Union is deemed authentic; consolidated texts are reproduced here for documentation purposes and have been reformatted to Markdown.