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)

• (458)If at the end of this period, interoperability problems still remain, the laboratory in charge of interoperability tests, with the collaboration of the manufacturers concerned and with the type approval authorities who delivered the corresponding functional certificates shall find out the causes of the interoperability faults and establish which modifications should be made by each of the manufacturers concerned. The search for technical solutions shall last for a maximum of two months, after which, if no common solution is found, the Commission, after having consulted the laboratory in charge of interoperability tests, shall decide which equipment(s) and cards get a definitive interoperability certificate and state the reasons why.

• (459)Any request for interoperability tests, registered by the laboratory between the end of the four month period after the first provisional interoperability certificate has been delivered and the date of the decision by the Commission referred to in requirement 455, shall be postponed until the initial interoperability problems have been solved. Those requests are then processed in the chronological order of their registration.

Appendix 1

DATA DICTIONARY

TABLE OF CONTENT	TABLE OF CONTENT
1.	INTRODUCTION
1.1.	Approach for definitions of data types
1.2.	References
2.	DATA TYPE DEFINITIONS
2.1.	ActivityChangeInfo
2.2.	Address
2.3.	AESKey
2.4.	AES128Key
2.5.	AES192Key
2.6.	AES256Key
2.7.	BCDString
2.8.	CalibrationPurpose
2.9.	CardActivityDailyRecord
2.10.	CardActivityLengthRange
2.11.	CardApprovalNumber
2.11a.	CardBorderCrossing
2.11b.	CardBorderCrossingRecord
2.12.	CardCertificate
2.13.	CardChipIdentification
2.14.	CardConsecutiveIndex
2.15.	CardControlActivityDataRecord
2.16.	CardCurrentUse
2.17.	CardDriverActivity
2.18.	CardDrivingLicenceInformation
2.19.	CardEventData
2.20.	CardEventRecord
2.21.	CardFaultData
2.22.	CardFaultRecord
2.23.	CardIccIdentification
2.24.	CardIdentification
2.24a.	CardLoadTypeEntries
2.24b.	CardLoadTypeEntryRecord
2.24c.	CardLoadUnloadOperations
2.24d.	CardLoadUnloadRecord
2.25.	CardMACertificate
2.26.	CardNumber
2.26a.	CardPlaceAuthDailyWorkPeriod
2.27.	CardPlaceDailyWorkPeriod
2.28.	CardPrivateKey
2.29.	CardPublicKey
2.30.	CardRenewalIndex
2.31.	CardReplacementIndex
2.32.	CardSignCertificate
2.33.	CardSlotNumber
2.34.	CardSlotsStatus
2.35.	CardSlotsStatusRecordArray
2.36.	CardStructureVersion
2.37.	CardVehicleRecord
2.38.	CardVehiclesUsed
2.39.	CardVehicleUnitRecord
2.40.	CardVehicleUnitsUsed
2.41.	Certificate
2.42.	CertificateContent
2.43.	CertificateHolderAuthorisation
2.44.	CertificateRequestID
2.45.	CertificationAuthorityKID
2.46.	CompanyActivityData
2.47.	CompanyActivityType
2.48.	CompanyCardApplicationIdentification
2.48a.	CompanyCardApplicationIdentificationV2
2.49.	CompanyCardHolderIdentification
2.50.	ControlCardApplicationIdentification
2.50a.	ControlCardApplicationIdentificationV2
2.51.	ControlCardControlActivityData
2.52.	ControlCardHolderIdentification
2.53.	ControlType
2.54.	CurrentDateTime
2.55.	CurrentDateTimeRecordArray
2.56.	DailyPresenceCounter
2.57.	Datef
2.58.	DateOfDayDownloaded
2.59.	DateOfDayDownloadedRecordArray
2.60.	Distance
2.60a.	DownloadInterfaceVersion
2.61.	DriverCardApplicationIdentification
2.61a.	DriverCardApplicationIdentificationV2
2.62.	DriverCardHolderIdentification
2.63.	Reserved for future use
2.64.	EGFCertificate
2.65.	EmbedderIcAssemblerId
2.66.	EntryTypeDailyWorkPeriod
2.67.	EquipmentType
2.68.	EuropeanPublicKey
2.69.	EventFaultRecordPurpose
2.70.	EventFaultType
2.71.	ExtendedSealIdentifier
2.72.	ExtendedSerialNumber
2.73.	FullCardNumber
2.74.	FullCardNumberAndGeneration
2.75.	Generation
2.76.	GeoCoordinates
2.77.	GNSSAccuracy
2.78.	GNSSAccumulatedDriving
2.79.	GNSSAccumulatedDrivingRecord
2.79a.	GNSSAuthAccumulatedDriving
2.79b.	GNSSAuthStatusADRecord
2.79c.	GNSSPlaceAuthRecord
2.80.	GNSSPlaceRecord
2.81.	HighResOdometer
2.82.	HighResTripDistance
2.83.	HolderName
2.84.	Reserved for future use
2.85.	K-ConstantOfRecordingEquipment
2.86.	KeyIdentifier
2.87.	KMWCKey
2.88.	Language
2.89.	LastCardDownload
2.89a.	LengthOfFollowingData
2.90.	LinkCertificate
2.90a.	LoadType
2.91.	L-TyreCircumference
2.92.	MAC
2.93.	ManualInputFlag
2.94.	ManufacturerCode
2.95.	ManufacturerSpecificEventFaultData
2.96.	MemberStateCertificate
2.97.	MemberStateCertificateRecordArray
2.98.	MemberStatePublicKey
2.99.	Name
2.100.	NationAlpha
2.101.	NationNumeric
2.101a.	NoOfBorderCrossingRecords
2.102.	NoOfCalibrationRecords
2.103.	NoOfCalibrationsSinceDownload
2.104.	NoOfCardPlaceRecords
2.105.	NoOfCardVehicleRecords
2.106.	NoOfCardVehicleUnitRecords
2.107.	NoOfCompanyActivityRecords
2.108.	NoOfControlActivityRecords
2.109.	NoOfEventsPerType
2.110.	NoOfFaultsPerType
2.111.	NoOfGNSSADRecords
2.111a.	NoOfLoadUnloadRecords
2.112.	NoOfSpecificConditionRecords
2.112a.	NoOfLoadTypeEntryRecords
2.113.	OdometerShort
2.114.	OdometerValueMidnight
2.114a.	OperationType
2.115.	OdometerValueMidnightRecordArray
2.116.	OverspeedNumber
2.116a.	PlaceAuthRecord
2.116b.	PlaceAuthStatusRecord
2.117.	PlaceRecord
2.117a.	PositionAuthenticationStatus
2.118.	PreviousVehicleInfo
2.119.	PublicKey
2.120.	RecordType
2.121.	RegionAlpha
2.122.	RegionNumeric
2.123.	RemoteCommunicationModuleSerialNumber
2.124.	RSAKeyModulus
2.125.	RSAKeyPrivateExponent
2.126.	RSAKeyPublicExponent
2.127.	RtmData
2.128.	SealDataCard
2.129.	SealDataVu
2.130.	SealRecord
2.131.	SensorApprovalNumber
2.132.	SensorExternalGNSSApprovalNumber
2.133.	SensorExternalGNSSCoupledRecord
2.134.	SensorExternalGNSSIdentification
2.135.	SensorExternalGNSSInstallation
2.136.	SensorExternalGNSSOSIdentifier
2.137.	SensorExternalGNSSSCIdentifier
2.138.	SensorGNSSCouplingDate
2.139.	SensorGNSSSerialNumber
2.140.	SensorIdentification
2.141.	SensorInstallation
2.142.	SensorInstallationSecData
2.143.	SensorOSIdentifier
2.144.	SensorPaired
2.145.	SensorPairedRecord
2.146.	SensorPairingDate
2.147.	SensorSCIdentifier
2.148.	SensorSerialNumber
2.149.	Signature
2.150.	SignatureRecordArray
2.151.	SimilarEventsNumber
2.152.	SpecificConditionRecord
2.153.	SpecificConditions
2.154.	SpecificConditionType
2.155.	Speed
2.156.	SpeedAuthorised
2.157.	SpeedAverage
2.158.	SpeedMax
2.158a.	TachographCardsGen1Suppression
2.159.	TachographPayload
2.160.	Reserved for future use
2.161.	TDesSessionKey
2.162.	TimeReal
2.163.	TyreSize
2.164.	VehicleIdentificationNumber
2.165.	VehicleIdentificationNumberRecordArray
2.166.	VehicleRegistrationIdentification
2.166a.	VehicleRegistrationIdentificationRecordArray
2.167.	VehicleRegistrationNumber
2.168.	VehicleRegistrationNumberRecordArray
2.169.	VuAbility
2.170.	VuActivityDailyData
2.171.	VuActivityDailyRecordArray
2.172.	VuApprovalNumber
2.173.	VuCalibrationData
2.174.	VuCalibrationRecord
2.175.	VuCalibrationRecordArray
2.176.	VuCardIWData
2.177.	VuCardIWRecord
2.178.	VuCardIWRecordArray
2.179.	VuCardRecord
2.180.	VuCardRecordArray
2.181.	VuCertificate
2.182.	VuCertificateRecordArray
2.183.	VuCompanyLocksData
2.184.	VuCompanyLocksRecord
2.185.	VuCompanyLocksRecordArray
2.185a.	VuConfigurationLengthRange
2.186.	VuControlActivityData
2.187.	VuControlActivityRecord
2.188.	VuControlActivityRecordArray
2.189.	VuDataBlockCounter
2.190.	VuDetailedSpeedBlock
2.191.	VuDetailedSpeedBlockRecordArray
2.192.	VuDetailedSpeedData
2.192a.	VuDigitalMapVersion
2.193.	VuDownloadablePeriod
2.194.	VuDownloadablePeriodRecordArray
2.195.	VuDownloadActivityData
2.196.	VuDownloadActivityDataRecordArray
2.197.	VuEventData
2.198.	VuEventRecord
2.199.	VuEventRecordArray
2.200.	VuFaultData
2.201.	VuFaultRecord
2.202.	VuFaultRecordArray
2.203.	VuGNSSADRecord
2.203a.	VuBorderCrossingRecord
2.203b.	VuBorderCrossingRecordArray
2.204.	VuGNSSADRecordArray
2.204a.	VuGnssMaximalTimeDifference
2.205.	VuIdentification
2.206.	VuIdentificationRecordArray
2.207.	VuITSConsentRecord
2.208.	VuITSConsentRecordArray
2.208a.	VuLoadUnloadRecord
2.208b.	VuLoadUnloadRecordArray
2.209.	VuManufacturerAddress
2.210.	VuManufacturerName
2.211.	VuManufacturingDate
2.212.	VuOverSpeedingControlData
2.213.	VuOverSpeedingControlDataRecordArray
2.214.	VuOverSpeedingEventData
2.215.	VuOverSpeedingEventRecord
2.216.	VuOverSpeedingEventRecordArray
2.217.	VuPartNumber
2.218.	VuPlaceDailyWorkPeriodData
2.219.	VuPlaceDailyWorkPeriodRecord
2.220.	VuPlaceDailyWorkPeriodRecordArray
2.221.	VuPrivateKey
2.222.	VuPublicKey
2.222a.	VuRtcTime
2.223.	VuSerialNumber
2.224.	VuSoftInstallationDate
2.225.	VuSoftwareIdentification
2.226.	VuSoftwareVersion
2.227.	VuSpecificConditionData
2.228.	VuSpecificConditionRecordArray
2.229.	VuTimeAdjustmentData
2.230.	Reserved for future use
2.231.	Reserved for future use
2.232.	VuTimeAdjustmentRecord
2.233.	VuTimeAdjustmentRecordArray
2.234.	WorkshopCardApplicationIdentification
2.234a.	WorkshopCardApplicationIdentificationV2
2.234b.	WorkshopCardCalibrationAddData
2.234c.	WorkshopCardCalibrationAddDataRecord
2.235.	WorkshopCardCalibrationData
2.236.	WorkshopCardCalibrationRecord
2.237.	WorkshopCardHolderIdentification
2.238.	WorkshopCardPIN
2.239.	W-VehicleCharacteristicConstant
2.240.	VuPowerSupplyInterruptionRecord
2.241.	VuPowerSupplyInterruptionRecordArray
2.242.	VuSensorExternalGNSSCoupledRecordArray
2.243.	VuSensorPairedRecordArray
3.	VALUE AND SIZE RANGE DEFINITIONS
4.	CHARACTER SETS
5.	ENCODING
6.	OBJECT IDENTIFIERS UND APPLICATION IDENTIFIERS
6.1.	Object Identifiers
6.2.	Application Identifiers

1. INTRODUCTION

This appendix specifies data formats, data elements, and data structures for use within the recording equipment and tachograph cards.

1.1.   Approach for definitions of data types

This 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.

ASN.1 type naming conventions are done in accordance with ISO/IEC 8824-1. This implies that:

• — where possible, the meaning of the data type is implied through the names being selected,

• — where 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,

• — in 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.

If 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.

To 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.

1.2.   References

The following references are used in this Appendix:

• ISO 639 Code for the representation of names of languages. First Edition: 1988.

• ISO 3166 Codes for the representation of names of countries and their subdivisions — Part 1: Country codes, 2013

• ISO 3779 Road vehicles — Vehicle identification number (VIN) — Content and structure. 2009

• ISO/IEC 7816-5 Identification cards — Integrated circuit cards — Part 5: Registration of application providers.

Second edition: 2004.

• ISO/IEC 7816-6 Identification cards — Integrated circuit cards — Part 6: Interindustry data elements for interchange, 2004 + Technical Corrigendum 1: 2006

• ISO/IEC 8824-1 Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic notation. 2008 + Technical Corrigendum 1: 2012 and Technical Corrigendum 2: 2014.

• ISO/IEC 8825-2 Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules (PER). 2008.

• ISO/IEC 8859-1 Information technology — 8 bit single-byte coded graphic character sets — Part 1: Latin alphabet No.1. First edition: 1998.

• ISO/IEC 8859-7 Information technology — 8 bit single-byte coded graphic character sets — Part 7: Latin/Greek alphabet. 2003.

• ISO 16844-3 Road vehicles — Tachograph systems — Motion Sensor Interface. 2004 + Technical Corrigendum 1: 2006..

• TR-03110-3 BSI / 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

2. DATA TYPE DEFINITIONS

For 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 Hex ‘FF’ bytes, unless otherwise specified.

All data types are used for Generation 1 and Generation 2 applications unless otherwise specified. Data types only used for Generation 2, version 2 applications are indicated.

For 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.

Card data types not defined for Generation 1 cards are not stored in Generation 1 application of Generation 2 cards. In particular:

• — Type approval numbers stored in Generation 1 application of Generation 2 cards are truncated to the 8 first characters where needed,

• — Only the ‘FERRY / TRAIN CROSSING begin’ of a ‘FERRY / TRAIN CROSSING’ specific condition is stored in Generation 1 application of Generation 2 cards.

2.1.   ActivityChangeInfo

This 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.

Image omitted; see official source

Value assignment — Octet Aligned: ‘scpaattttttttttt’B (16 bits)

For Data Memory recordings (or slot status):

• ‘s’B Slot:

‘0’B: DRIVER,

‘1’B: CO-DRIVER,

• ‘c’B Driving status:

‘0’B: SINGLE,

‘1’B: CREW,

• ‘p’B Driver (or workshop) card status in the relevant slot:

‘0’B: INSERTED, a card is inserted,

‘1’B: NOT INSERTED, no card is inserted (or a card is withdrawn),

• ‘aa’B Activity:

‘00’B: BREAK/REST,

‘01’B: AVAILABILITY,

‘10’B: WORK,

‘11’B: DRIVING,

• ‘ttttttttttt’B Time of the change: Number of minutes since 00h00 on the given day.

For Driver (or Workshop) card recordings (and driver status):

• ‘s’B Slot (not relevant when ‘p’=1 except note below):

‘0’B: DRIVER,

‘1’B: CO-DRIVER,

• ‘c’B Driving status (case ‘p’=0) or

Following activity status (case ‘p’=1):

‘0’B: SINGLE,

‘0’B: UNKNOWN

‘1’B: CREW,

‘1’B: KNOWN (=manually entered)

• ‘p’B Card status:

‘0’B: INSERTED, the card is inserted in a recording equipment,

‘1’B: NOT INSERTED, the card is not inserted (or the card is withdrawn),

• ‘aa’B Activity (not relevant when ‘p’=1 and ‘c’=0 except note below):

‘00’B: BREAK/REST,

‘01’B: AVAILABILITY,

‘10’B: WORK,

‘11’B: DRIVING,

• ‘ttttttttttt’B Time of the change: Number of minutes since 00h00 on the given day.

Note for the case ‘card withdrawal’:

When the card is withdrawn:

• — ‘s’ is relevant and indicates the slot from which the card is withdrawn,

• — ‘c’ must be set to 0,

• — ‘p’ must be set to 1,

• — ‘aa’ must code the current activity selected at that time,

As 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.

2.2.   Address

An address.

Image omitted; see official source

codePage specifies a character set defined in Chapter 4,

address is an address encoded using the specified character set.

2.3.   AESKey

Generation 2:

An AES key with a length of 128, 192 or 256 bits.

Image omitted; see official source

Value assignment: not further specified.

2.4.   AES128Key

Generation 2:

An AES128 key.

Image omitted; see official source

length denotes the length of the AES128 key in octets.

aes128Key is an AES key with a length of 128 bits.

Value assignment:

The length shall have the value 16.

2.5.   AES192Key

Generation 2:

An AES192 key.

Image omitted; see official source

length denotes the length of the AES192 key in octets.

aes192Key is an AES key with a length of 192 bits.

Value assignment:

The length shall have the value 24.

2.6.   AES256Key

Generation 2:

An AES256 key.

Image omitted; see official source

length denotes the length of the AES256 key in octets.

aes256Key is an AES key with a length of 256 bits.

Value assignment:

The length shall have the value 32.

2.7.   BCDString

BCDString 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’.

Image omitted; see official source

BCDString 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.

Permitted digits are: 0, 1, .. 9.

2.8.   CalibrationPurpose

Code 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.

Image omitted; see official source

Value assignment:

Generation 1:

• ‘00’H reserved value,

• ‘01’H activation: recording of calibration parameters known, at the moment of the VU activation,

• ‘02’H first installation: first calibration of the VU after its activation,

• ‘03’H installation: first calibration of the VU in the current vehicle,

• ‘04’H periodic inspection.

Generation 2:

In addition to generation 1 the following values are used:

• ‘05’H entry of VRN by company,

• ‘06’H time adjustment without calibration,

• ‘07’H to ‘7F’H RFU,

• ‘80’H to ‘FF’H Manufacturer specific.

2.9.   CardActivityDailyRecord

Information, 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.

Image omitted; see official source

activityPreviousRecordLength 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.

activityRecordLength is the total length in bytes of this record. The maximum value is given by the length of the OCTET STRING containing these records.

activityRecordDate is the date of the record.

activityDailyPresenceCounter is the daily presence counter for the card this day.

activityDayDistance is the total distance travelled this day.

activityChangeInfo 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.

2.10.   CardActivityLengthRange

Number of bytes in a driver or a workshop card, available to store driver activity records.

Image omitted; see official source

Value assignment: see Appendix 2.

2.11.   CardApprovalNumber

Type approval number of the card.

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.11a.   CardBorderCrossings

Generation 2, version 2:

Information, stored in a driver or workshop card, related to the border crossings of the vehicle when the latter has crossed the border of a country (Annex IC requirements 306f and 356f).

Image omitted; see official source

borderCrossingPointerNewestRecord is the index of the last updated card border crossing record.

Value assignment is the number corresponding to the numerator of the card border crossing record, beginning with ‘0’ for the first occurrence of the card border crossing record in the structure.

cardBorderCrossingRecords is the set of card border crossing records.

2.11b.   CardBorderCrossingRecord

Generation 2, version 2:

Information, stored in a driver or workshop card, related to the border crossings of the vehicle when the latter has crossed the border of a country (Annex IC requirements 147b, 306e and 356e).

Image omitted; see official source

countryLeft is the country which was left by the vehicle, or ‘no information available’ according to Annex IC requirement 147b. ‘Rest of the World’ (NationNumeric code ‘FF’H) shall be used when the vehicle unit is not able to determine the country where the vehicle is located (e.g. the current country is not part of the stored digital maps).

countryEntered is the country into which the vehicle has entered, or the country in which the vehicle is located at card insertion time. ‘Rest of the World’ (NationNumeric code ‘FF’H) shall be used when the vehicle unit is not able to determine the country where the vehicle is located (e.g. the current country is not part of the stored digital maps).

gnssPlaceAuthRecord contains information related to the position of the vehicle, when the vehicle unit has detected that the vehicle has crossed the border of a country, or ‘no information available’ according to requirement 147b of Annex IC, and its authentication status.

vehicleOdometerValue is the odometer value when the vehicle unit has detected that the vehicle has crossed the border of a country, or ‘no information available’ according to requirement 147b of Annex IC.

2.12.   CardCertificate

Generation 1:

Certificate of the public key of a card.

Image omitted; see official source

2.13.   CardChipIdentification

Information, 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.

Image omitted; see official source

icSerialNumber is the IC serial number.

icManufacturingReferences is the IC manufacturer specific identifier.

2.14.   CardConsecutiveIndex

A card consecutive index (definition h)).

Image omitted; see official source

Value assignment: (see Annex 1C chapter 7)

Order for increase: ‘0, …, 9, A, …, Z, a, …, z’

2.15.   CardControlActivityDataRecord

Information, 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).

Image omitted; see official source

controlType is the type of the control.

controlTime is the date and time of the control.

controlCardNumber is the FullCardNumber of the control officer having performed the control.

controlVehicleRegistration is the VRN and registering Member State of the vehicle in which the control happened.

controlDownloadPeriodBegin and controlDownloadPeriodEnd is the period downloaded, in case of downloading.

2.16.   CardCurrentUse

Information about the actual usage of the card (Annex 1C requirement 273, 298, 326, and 349).

Image omitted; see official source

sessionOpenTime is the time when the card is inserted for the current usage. This element is set to zero at card removal.

sessionOpenVehicle is the identification of the currently used vehicle, set at card insertion. This element is set to zero at card removal.

2.17.   CardDriverActivity

Information, 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).

Image omitted; see official source

activityPointerOldestDayRecord 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.

activityPointerNewestRecord 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.

activityDailyRecords is the space available to store the driver activity data (data structure: CardActivityDailyRecord) for each calendar day where the card has been used.

Value 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.

2.18.   CardDrivingLicenceInformation

Information, stored in a driver card, related to the card holder driver licence data (Annex 1C requirement 259 and 284).

Image omitted; see official source

drivingLicenceIssuingAuthority is the authority responsible for issuing the driving licence.

drivingLicenceIssuingNation is the nationality of the authority that issued the driving licence.

drivingLicenceNumber is the number of the driving licence.

2.19.   CardEventData

Generation 1:

Information, stored in a driver or workshop card, related to the events associated with the card holder (Annex IC requirements 260 and 318).

Image omitted; see official source

CardEventData 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).

cardEventRecords is a set of event records of a given event type (or category for security breach attempts events).

Generation 2:

Information, stored in a driver or workshop card, related to the events associated with the card holder (Annex IC requirements 285 and 341).

Image omitted; see official source

CardEventData 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).

cardEventRecords is a set of event records of a given event type (or category for security breach attempts events).

2.20.   CardEventRecord

Information, 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).

Image omitted; see official source

eventType is the type of the event.

eventBeginTime is the date and time of beginning of event.

eventEndTime is the date and time of end of event.

eventVehicleRegistration is the VRN and registering Member State of vehicle in which the event happened.

2.21.   CardFaultData

Information, 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).

Image omitted; see official source

CardFaultData is a sequence of Recording Equipment faults set of records followed by card faults set of records.

cardFaultRecords is a set of fault records of a given fault category (Recording Equipment or card).

2.22.   CardFaultRecord

Information, 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).

Image omitted; see official source

faultType is the type of the fault.

faultBeginTime is the date and time of beginning of fault.

faultEndTime is the date and time of end of fault.

faultVehicleRegistration is the VRN and registering Member State of vehicle in which the fault happened.

2.23.   CardIccIdentification

Information, stored in a card, related to the identification of the integrated circuit (IC) card (Annex 1C requirement 248).

Image omitted; see official source

clockStop is the Clockstop mode as defined in appendix 2.

cardExtendedSerialNumber is the IC card unique serial number as further specified by the ExtendedSerialNumber data type.

cardApprovalNumber is the type approval number of the card.

cardPersonaliserID is the card personaliser ID encoded as ManufacturerCode.

embedderIcAssemblerId provides information about the embedder/IC assembler.

icIdentifier is the Identifier of the IC on the card and its IC manufacturer as defined in ISO/IEC 7816-6.

2.24.   CardIdentification

Information, stored in a card, related to the identification of the card (Annex 1C requirements 255, 280, 310, 333, 359, 365, 371, and 377).

Image omitted; see official source

cardIssuingMemberState is the code of the Member State issuing the card.

cardNumber is the card number of the card.

cardIssuingAuthorityName is the name of the authority having issued the Card.

cardIssueDate is the issue date of the Card to the current holder.

cardValidityBegin is the first date of validity of the card.

cardExpiryDate is the date when the validity of the card ends.

2.24a.   CardLoadTypeEntries

Generation 2, version 2:

Information, stored in a driver or workshop card, related to the load type entries when the card is inserted in a vehicle unit (Annex IC requirements 306j and 356j).

Image omitted; see official source

loadTypeEntryPointerNewestRecord is the index of the last updated card load type entry record.

Value assignment: number corresponding to the numerator of the card load type entry record, beginning with '0' for the first occurrence of the card load type entry record in the structure.

cardLoadTypeEntryRecords is the set of records containing the date and time of the entry and the load type entered.

2.24b.   CardLoadTypeEntryRecord

Generation 2, version 2:

Information, stored in a driver or workshop card, related to the load type changes entered when the card is inserted in a vehicle unit (Annex IC requirements 306i and 356i).

Image omitted; see official source

timeStamp is the date and time when the load type was entered.

loadTypeEntered is the load type entered.

2.24c.   CardLoadUnloadOperations

Generation 2, version 2:

Information, stored in a driver or workshop card, related to load/unload operations of the vehicle (Annex IC requirements 306h and 356h).

Image omitted; see official source

loadUnloadPointerNewestRecord is the index of the last updated card load/unload record.

Value assignment: is the number corresponding to the numerator of the card load/unload record, beginning with '0' for the first occurrence of the card load/unload record in the structure.

cardLoadUnloadRecords is the set of records containing the indication of the type of operation performed (load, unload, or simultaneous load and unload), the date and time the load/unload operation has been entered, information about the position of the vehicle, and the vehicle odometer value.

2.24d.   CardLoadUnloadRecord

Generation 2, version 2:

Information, stored in a driver or workshop card, related to load/unload operations of the vehicle (Annex IC requirements 306g and 356g).

Image omitted; see official source

timeStamp is the date and time at the beginning of the load/unload operation.

operationType is the type of operation entered (load, unload, or simultaneous load/unload).

gnssPlaceAuthRecord contains information related to the position of the vehicle.

vehicleOdometerValue is the odometer value related to the beginning of the load/unload operation.

2.25.   CardMACertificate

Generation 2:

Certificate of the card public key for mutual authentication with a VU. The structure of this certificate is specified in Appendix 11.

Image omitted; see official source

2.26.   CardNumber

A card number as defined by definition g).

Image omitted; see official source

driverIdentification is the unique identification of a driver in a Member State.

ownerIdentification is the unique identification of a company or a workshop or a control body within a member state.

cardConsecutiveIndex is the card consecutive index.

cardReplacementIndex is the card replacement index.

cardRenewalIndex is the card renewal index.

The 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.

2.26a.   CardPlaceAuthDailyWorkPeriod

Generation 2, version 2:

Information, stored in a driver or a workshop card, providing the authentication status of places where daily work periods begin and/or end (Annex IC requirements 306b and 356b).

Image omitted; see official source

placeAuthPointerNewestRecord is the index of the last updated place authentication status record.

Value assignment: Number corresponding to the numerator of the place authentication status record, beginning with ‘0’ for the first occurrence of the place authentication status records in the structure.

placeAuthStatusRecords is the set of records containing the place authentication status of the places entered.

2.27.   CardPlaceDailyWorkPeriod

Information, 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).

Image omitted; see official source

placePointerNewestRecord is the index of the last updated place record.

Value assignment: Number corresponding to the numerator of the place record, beginning with ‘0’ for the first occurrence of the place records in the structure.

placeRecords is the set of records containing the information related to the places entered.

2.28.   CardPrivateKey

Generation 1:

The private key of a card.

Image omitted; see official source

2.29.   CardPublicKey

The public key of a card.

Image omitted; see official source

2.30.   CardRenewalIndex

A card renewal index (definition i)).

Image omitted; see official source

Value assignment: (see this Annex chapter 7).

• ‘0’ First issue.

Order for increase: ‘0, …, 9, A, …, Z’

2.31.   CardReplacementIndex

A card replacement index (definition j)).

Image omitted; see official source

Value assignment: (see this Annex chapter VII).

• ‘0’ Original card.

Order for increase: ‘0, …, 9, A, …, Z’

2.32.   CardSignCertificate

Generation 2:

Certificate of the card public key for signature. The structure of this certificate is specified in Appendix 11.

Image omitted; see official source

2.33.   CardSlotNumber

Code to distinguish between the two slots of a Vehicle Unit.

Image omitted; see official source

Value assignment: not further specified.

2.34.   CardSlotsStatus

Code indicating the type of cards inserted in the two slots of the vehicle unit.

Image omitted; see official source

Value assignment — Octet Aligned: ‘ccccdddd’B

• ‘cccc’B Identification of the type of card inserted in the co-driver slot,

• ‘dddd’B Identification of the type of card inserted in the driver slot,

with the following identification codes:

• ‘0000’B no card is inserted,

• ‘0001’B a driver card is inserted,

• ‘0010’B a workshop card is inserted,

• ‘0011’B a control card is inserted,

• ‘0100’B a company card is inserted.

2.35.   CardSlotsStatusRecordArray

Generation 2:

The CardSlotsStatus plus metadata as used in the download protocol.

Image omitted; see official source

recordType denotes the type of the record (CardSlotsStatus). Value Assignment: See RecordType

recordSize is the size of the CardSlotsStatus in bytes.

noOfRecords is the number of records in the set records.

records is the set of CardSlotsStatus records.

2.36.   CardStructureVersion

Code indicating the version of the implemented structure in a tachograph card.

Image omitted; see official source

Value assignment: ‘aabb’H:

• ‘aa’H Index for changes of the structure.

‘00’H for Generation 1 applications

‘01’H for Generation 2 applications

• ‘bb’H Index for changes concerning the use of the data elements defined for the structure given by the high byte.

‘00’H for Generation 1 applications

‘00’H for version 1 of Generation 2 applications

‘01’H for version 2 of Generation 2 applications.

2.37.   CardVehicleRecord

Information, 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).

Generation 1:

Image omitted; see official source

vehicleOdometerBegin is the vehicle odometer value at the beginning of the period of use of the vehicle.

vehicleOdometerEnd is the vehicle odometer value at the end of the period of use of the vehicle.

vehicleFirstUse is the date and time of the beginning of the period of use of the vehicle.

vehicleLastUse is the date and time of the end of the period of use of the vehicle.

vehicleRegistration is the VRN and the registering Member State of the vehicle.

vuDataBlockCounter is the value of the VuDataBlockCounter at last extraction of the period of use of the vehicle.

Generation 2:

Image omitted; see official source

In addition to generation 1 the following data element is used:

VehicleIdentificationNumber is the vehicle identification number referring to the vehicle as a whole.

2.38.   CardVehiclesUsed

Information, stored in a driver or workshop card, related to the vehicles used by the card holder (Annex 1C requirements 270, 295, 323, and 346).

Image omitted; see official source

vehiclePointerNewestRecord is the index of the last updated vehicle record.

Value assignment: Number corresponding to the numerator of the vehicle record, beginning with ‘0’ for the first occurrence of the vehicle records in the structure.

cardVehicleRecords is the set of records containing information on vehicles used.

2.39.   CardVehicleUnitRecord

Generation 2:

Information, stored in a driver or workshop card, related to a vehicle unit that was used (Annex 1C requirement 303 and 351).

Image omitted; see official source

timeStamp is the beginning of the period of use of the vehicle unit (i.e. first card insertion in the vehicle unit for the period).

manufacturerCode identifies the manufacturer of the Vehicle Unit.

deviceID identifies the Vehicle Unit type of a manufacturer. The value is manufacturer specific.

vuSoftwareVersion is the software version number of the Vehicle Unit.

2.40.   CardVehicleUnitsUsed

Generation 2:

Information, stored in a driver or workshop card, related to the vehicle units used by the card holder (Annex IC requirements 304 and 352).

Image omitted; see official source

vehicleUnitPointerNewestRecord is the index of the last updated vehicle unit record.

Value 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.

cardVehicleUnitRecords is the set of records containing information on vehicle units used.

2.41.   Certificate

The certificate of a public key issued by a Certification Authority.

Generation 1:

Image omitted; see official source

Value 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).

Generation 2:

Image omitted; see official source

Value assignment: See Appendix 11

2.42.   CertificateContent

Generation 1:

The (clear) content of the certificate of a public key according to Appendix 11 common security mechanisms.

Image omitted; see official source

certificateProfileIdentifier is the version of the corresponding certificate.

Value assignment: ‘01h’ for this version.

certificationAuthorityReference identifies the Certification Authority issuing the certificate. It also references the Public Key of this Certification Authority.

certificateHolderAuthorisation identifies the rights of the certificate holder.

certificateEndOfValidity is the date when the certificate expires administratively.

certificateHolderReference identifies the certificate holder. It also references his Public Key.

publicKey is the public key that is certified by this certificate.

2.43.   CertificateHolderAuthorisation

Identification of the rights of a certificate holder.

Image omitted; see official source

Generation 1:

tachographApplicationID is the application identifier for the tachograph application.

Value assignment: ‘FFh’ ‘54h’ ‘41h’ ‘43h’ ‘48h’ ‘4Fh’. This AID is a proprietary non registered application identifier in accordance with ISO/IEC 7816-5.

equipmentType is the identification of the type of equipment to which the certificate is intended.

Value assignment: in accordance with EquipmentType data type. 0 if certificate is the one of a Member State.

Generation 2:

tachographApplicationID 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.

Value assignment: ‘FF 53 4D 52 44 54’.

equipmentType is the identification of the type of equipment as specified for generation 2 to which the certificate is intended.

Value assignment: in accordance with EquipmentType data type.

2.44.   CertificateRequestID

Unique 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.

Image omitted; see official source

requestSerialNumber is a serial number for the certificate request, unique for the manufacturer and the month below.

requestMonthYear is the identification of the month and the year of the certificate request.

Value assignment: BCD coding of Month (two digits) and Year (two last digits).

crIdentifier: is an identifier to distinguish a certificate request from an extended serial number.

Value assignment: ‘FFh’.

manufacturerCode: is the numerical code of the manufacturer requesting the certificate.

2.45.   CertificationAuthorityKID

Identifier of the Public Key of a Certification Authority (a Member State or the European Certification Authority).

Image omitted; see official source

nationNumeric is the numerical nation code of the Certification Authority.

nationAlpha is the alphanumerical nation code of the Certification Authority.

keySerialNumber is a serial number to distinguish the different keys of the Certification Authority in the case keys are changed.

additionalInfo is a two byte field for additional coding (Certification Authority specific).

caIdentifier is an identifier to distinguish a Certification Authority Key Identifier from other Key Identifiers.

Value assignment: ‘01h’.

2.46.   CompanyActivityData

Information, stored in a company card, related to activities performed with the card (Annex 1C requirement 373 and 379).

Image omitted; see official source

companyPointerNewestRecord is the index of the last updated companyActivityRecord.

Value 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.

companyActivityRecords is the set of all company activity records.

companyActivityRecord is the sequence of information related to one company activity.

companyActivityType is the type of the company activity.

companyActivityTime is the date and time of the company activity.

cardNumberInformation is the card number and the card issuing Member State of the card downloaded, if any.

vehicleRegistrationInformation is the VRN and registering Member State of the vehicle downloaded or locked in or out.

downloadPeriodBegin and downloadPeriodEnd is the period downloaded from the VU, if any.

2.47.   CompanyActivityType

Code indicating an activity carried out by a company using its company card.

Image omitted; see official source

2.48.   CompanyCardApplicationIdentification

Information, stored in a company card related to the identification of the application of the card (Annex 1C requirement 369 and 375).

Image omitted; see official source

typeOfTachographCardId is specifying the implemented type of card.

cardStructureVersion is specifying the the version of the structure that is implemented in the card.

noOfCompanyActivityRecords is the number of company activity records the card can store.

2.48a.   CompanyCardApplicationIdentificationV2

Generation 2, version 2:

Information, stored in a company card related to the identification of the application of the card (Annex IC requirement 375a).

Image omitted; see official source

lengthOfFollowingData is the number of bytes following in the record.

vuConfigurationLengthRange is the number of bytes in a tachograph card, available to store VU configurations.

2.49.   CompanyCardHolderIdentification

Information, stored in a company card, related to the cardholder identification (Annex 1C requirement 372 and 378).

Image omitted; see official source

companyName is the name of the holder company.

companyAddress is the address of the holder company.

cardHolderPreferredLanguage is the preferred language of the card holder.

2.50.   ControlCardApplicationIdentification

Information, stored in a control card related to the identification of the application of the card (Annex 1C requirement 357 and 363).

Image omitted; see official source

typeOfTachographCardId is specifying the implemented type of card.

cardStructureVersion is specifying the version of the structure that is implemented in the card.

noOfControlActivityRecords is the number of control activity records the card can store.

2.50a.   ControlCardApplicationIdentificationV2

Generation 2, version 2:

Information, stored in a control card related to the identification of the application of the card (Annex IC requirement 363a).

Image omitted; see official source

lengthOfFollowingData is the number of bytes following in the record.

vuConfigurationLengthRange is the number of bytes in a tachograph card, available to store VU configurations.

2.51.   ControlCardControlActivityData

Information, stored in a control card, related to control activity performed with the card (Annex 1C requirement 361 and 367).

Image omitted; see official source

controlPointerNewestRecord is the index of the last updated control activity record.

Value 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.

controlActivityRecords is the set of all control activity records.

controlActivityRecord is the sequence of information related to one control.

controlType is the type of the control.

controlTime is the date and time of the control.

controlledCardNumber is the card number and the card issuing Member State of the card controlled.

controlledVehicleRegistration is the VRN and registering Member State of the vehicle in which the control happened.

controlDownloadPeriodBegin and controlDownloadPeriodEnd is the period eventually downloaded.

2.52.   ControlCardHolderIdentification

Information, stored in a control card, related to the identification of the cardholder (Annex 1C requirement 360 and 366).

Image omitted; see official source

controlBodyName is the name of the control body of the card holder.

controlBodyAddress is the address of the control body of the card holder.

cardHolderName is the name and first name(s) of the holder of the Control Card.

cardHolderPreferredLanguage is the preferred language of the card holder.

2.53.   ControlType

Code indicating the activities carried out during a control. This data type is related to Annex 1C requirements 126, 274, 299, 327, and 350.

Image omitted; see official source

Generation 1:

Value assignment — Octet aligned: ‘cvpdxxxx’B (8 bits)

• ‘c’B card downloading:

‘0’B: card not downloaded during this control activity,

‘1’B: card downloaded during this control activity

• ‘v’B VU downloading:

‘0’B: VU not downloaded during this control activity,

‘1’B: VU downloaded during this control activity

• ‘p’B printing:

‘0’B: no printing done during this control activity,

‘1’B: printing done during this control activity

• ‘d’B display:

‘0’B: no display used during this control activity,

‘1’B: display used during this control activity

• ‘xxxx’B Not used.

Generation 2:

Value assignment — Octet aligned: ‘cvpdexxx’B (8 bits)

• ‘c’B card downloading:

‘0’B: card not downloaded during this control activity,

‘1’B: card downloaded during this control activity

• ‘v’B VU downloading:

‘0’B: VU not downloaded during this control activity,

‘1’B: VU downloaded during this control activity

• ‘p’B printing:

‘0’B: no printing done during this control activity,

‘1’B: printing done during this control activity

• ‘d’B display:

‘0’B: no display used during this control activity,

‘1’B: display used during this control activity

• ‘e’B roadside calibration checking:

‘0’B: calibration parameters not checked during this control activity,

‘1’B: calibration parameters checked during this control activity

• ‘xxx’B RFU.

2.54.   CurrentDateTime

The current date and time of the recording equipment.

Image omitted; see official source

Value assignment: not further specified.

2.55.   CurrentDateTimeRecordArray

Generation 2:

The current date and time plus metadata as used in the download protocol.

Image omitted; see official source

recordType denotes the type of the record (CurrentDateTime). Value Assignment: See RecordType

recordSize is the size of the CurrentDateTime in bytes.

noOfRecords is the number of records in the set records.

records is a set of current date and time records.

2.56.   DailyPresenceCounter

Counter, 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.

Image omitted; see official source

Value 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.

2.57.   Datef

Date expressed in a readily printable numeric format.

Image omitted; see official source

Value assignment:

• yyyy Year

• mm Month

• dd Day

• ‘00000000’H denotes explicitly no date.

2.58.   DateOfDayDownloaded

Generation 2:

The date and time of the download.

Image omitted; see official source

Value assignment: not further specified.

2.59.   DateOfDayDownloadedRecordArray

Generation 2:

The date and time of the download plus metadata as used in the download protocol.

Image omitted; see official source

recordType denotes the type of the record (DateOfDayDownloaded). Value Assignment: See RecordType

recordSize is the size of the CurrentDateTime in bytes.

noOfRecords is the number of records in the set records.

records is the set of date and time of the download records.

2.60.   Distance

A distance travelled (result of the calculation of the difference between two vehicle's odometer values in kilometers).

Image omitted; see official source

Value assignment: Unsigned binary. Value in km in the operational range 0 to 9 999  km.

2.60a.   DownloadInterfaceVersion

Generation 2, version 2:

Code indicating the version of the download interface of a vehicle unit.

Image omitted; see official source

Value assignment: ‘aabb’H:

‘aa’H ‘00’H: not used,

‘01’H: Generation 2 vehicle unit,

‘bb’H ‘00’H: not used,

‘01’H: version 2 of Generation 2 vehicle unit.

2.61.   DriverCardApplicationIdentification

Information, stored in a driver card related to the identification of the application of the card (Annex 1C requirement 253 and 278).

Generation 1:

Image omitted; see official source

typeOfTachographCardId is specifying the implemented type of card.

cardStructureVersion is specifying the the version of the structure that is implemented in the card.

noOfEventsPerType is the number of events per type of event the card can record.

noOfFaultsPerType is the number of faults per type of fault the card can record.

activityStructureLength indicates the number of bytes available for storing activity records.

noOfCardVehicleRecords is the number of vehicle records the card can contain.

noOfCardPlaceRecords is the number of places the card can record.

Generation 2:

Image omitted; see official source

In addition to generation 1 the following data elements are used:

noOfGNSSADRecords is the number of GNSS accumulated driving records the card can store.

noOfSpecificConditionRecords is the number of specific condition records the card can store.

noOfCardVehicleUnitRecords is the number of vehicle units used records the card can store.

2.61a.   DriverCardApplicationIdentificationV2

Generation 2, version 2:

Information, stored in a driver card related to the identification of the application of the card (Annex IC requirement 278a).

Image omitted; see official source

lengthOfFollowingData is the number of bytes following in the record.

noOfBorderCrossingRecords is the number of border crossing records the driver card can store.

noOfLoadUnloadRecords is the number of load/unload records the driver card can store.

noOfLoadTypeEntryRecords is the number of load type entry records the driver card can store.

vuConfigurationLengthRange is the number of bytes in a tachograph card, available to store VU configurations.

2.62.   DriverCardHolderIdentification

Information, stored in a driver card, related to the identification of the cardholder (Annex 1C requirement 256 and 281).

Image omitted; see official source

cardHolderName is the name and first name(s) of the holder of the Driver Card.

cardHolderBirthDate is the date of birth of the holder of the Driver Card.

cardHolderPreferredLanguage is the preferred language of the card holder.

2.63.   DSRCSecurityData

Generation 2:

For the definition of this data type, see Appendix 11.

2.64.   EGFCertificate

Generation 2:

Certificate of the external GNSS facility public key for mutual authentication with a VU. The structure of this certificate is specified in Appendix 11.

Image omitted; see official source

2.65.   EmbedderIcAssemblerId

Provides information about the IC embedder.

Image omitted; see official source

countryCode is the 2 letter country code of the module embedder according to ISO 3166.

moduleEmbedder identifies the module embedder.

manufacturerInformation for manufacturer internal usage.

2.66.   EntryTypeDailyWorkPeriod

Code to distinguish between begin and end for an entry of a daily work period place and condition of the entry.

Generation 1

Image omitted; see official source

Value assignment: according to ISO/IEC8824-1.

Generation 2

Image omitted; see official source

Value assignment: according to ISO/IEC8824-1.

2.67.   EquipmentType

Code to distinguish different types of equipment for the tachograph application.

Image omitted; see official source

Generation 1:

Image omitted; see official source

Value assignment: According to ISO/IEC8824-1.

Value 0 is reserved for the purpose of designating a Member State or Europe in the CHA field of certificates.

Generation 2:

The same values as in generation 1 are used with the following additions:

Image omitted; see official source

• Note 1: The 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.

• Note 2: In 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.

2.68.   EuropeanPublicKey

Generation 1:

The European public key.

Image omitted; see official source

2.69.   EventFaultRecordPurpose

Code explaining why an event or a fault has been recorded.

Image omitted; see official source

Value assignment:

Image omitted; see official source

one of the 10 most recent (or last) events or faults the longest event for one of the last 10 days of occurrence one of the 5 longest events over the last 365 days the last event for one of the last 10 days of occurrence the most serious event for one of the last 10 days of occurrence one of the 5 most serious events over the last 365 days the first event or fault having occurred after the last calibration an active/on-going event or fault RFU manufacturer specific

2.70.   EventFaultType

Code qualifying an event or a fault.

Image omitted; see official source

Value assignment:

Generation 1:

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, 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, 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, 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 1: