Data Transmission Services

Service name	Description
ReadDataByIdentifier	The client requests the transmission of the current value of a record with access by recordDataIdentifier.
WriteDataByIdentifier	The client requests to write a record accessed by recordDataIdentifier.

6.1.   ReadDataByIdentifier service

6.1.1   Message description

• CPR_050The ReadDataByIdentifier service is used by the client to request data record values from a server. The data are identified by a recordDataIdentifier. It is the VU manufacturer's responsibility that the server conditions are met when performing this service.

6.1.2   Message format

- CPR_051The message formats for the ReadDataByIdentifier primitives are detailed in the following tables.

Table 25

ReadDataByIdentifier Request Message

Byte #	Parameter Name	Hex Value	Mnemonic
#1	Format byte — physical addressing	80	FMT
#2	Target address byte	EE	TGT
#3	Source address byte	tt	SRC
#4	Additional length byte	03	LEN
#5	ReadDataByIdentifier Request Service Id	22	RDBI
#6 to #7	recordDataIdentifier = [a value fromTable 28]	xxxx	RDI_…
#8	Checksum	00-FF	CS

Table 26

ReadDataByIdentifier Positive Response Message

Byte #	Parameter Name	Parameter Name	Hex Value	Mnemonic
#1	Format byte — physical addressing	Format byte — physical addressing	80	FMT
#2	Target address byte	Target address byte	tt	TGT
#3	Source address byte	Source address byte	EE	SRC
#4	Additional length byte	Additional length byte	m+3	LEN
#5	ReadDataByIdentifier Positive Response Service Id	ReadDataByIdentifier Positive Response Service Id	62	RDBIPR
#6 and #7	recordDataIdentifier = [the same value as bytes #6 and #7 Table 25]	recordDataIdentifier = [the same value as bytes #6 and #7 Table 25]	xxxx	RDI_...
#8 to #m + 7	dataRecord[] =	[data#1	xx	DREC_DATA1
#8 to #m + 7	dataRecord[] =	:	:	:
#8 to #m + 7	dataRecord[] =	data#m]	xx	DREC_DATAm
#m + 8	Checksum	Checksum	00-FF	CS

Table 27

ReadDataByIdentifier Negative Response Message

| Byte # | Parameter Name | Parameter Name | Hex Value | Mnemonic |

| --- | --- | --- | --- | --- | | #1 | Format byte — physical addressing | Format byte — physical addressing | 80 | FMT | | #2 | Target address byte | Target address byte | tt | TGT | | #3 | Source address byte | Source address byte | EE | SRC | | #4 | Additional length byte | Additional length byte | 03 | LEN | | #5 | NegativeResponse Service Id | NegativeResponse Service Id | 7F | NR | | #6 | ReadDataByIdentifier Request Service Id | ReadDataByIdentifier Request Service Id | 22 | RDBI | | #7 | ResponseCode= | [requestOutOfRange | 31 | RC_ROOR | | #7 | ResponseCode= | incorrectMessageLength | 13 | RC_IML | | #7 | ResponseCode= | conditionsNotCorrect] | 22 | RC_CNC | | #8 | Checksum | Checksum | 00-FF | CS |

6.1.3   Parameter Definition

• CPR_052The parameter recordDataIdentifier (RDI_) in the ReadDataByIdentifier request message identifies a data record.

- CPR_053recordDataIdentifier values defined by this document are shown in the table below.

- The recordDataIdentifier table consists of five columns and multiple lines.

• — The 1^st column (Hex) includes the ‘Hex Value’ assigned to the recordDataIdentifier specified in the 3^rd column.

- — The 2^nd column (Data element) specifies the data element of Appendix 1 on which the recordDataIdentifier is based (transcoding is sometimes necessary).

- — The 3^rd column (Description) specifies the corresponding recordDataIdentifier name.

• — The 4^th column (Access rights) specifies the access rights to this recordDataIdentifier.

- — The 5^th column (Mnemonic) specifies the mnemonic of this recordDataIdentifier.

Table 28

Definition of recordDataIdentifier values

| Hex | Data element | recordDataIdentifier Name (see format in Section 8.2) | Access rights (Read/Write) | Mnemonic |

| --- | --- | --- | --- | --- | | F90B | CurrentDateTime | TimeDate | R/W | RDI_TD | | F912 | HighResOdometer | HighResolutionTotalVehicleDistance | R/W | RDI_HRTVD | | F918 | K-ConstantOfRecordingEquipment | Kfactor | R/W | RDI_KF | | F91C | L-TyreCircumference | LfactorTyreCircumference | R/W | RDI_LF | | F91D | W-VehicleCharacteristicConstant | WvehicleCharacteristicFactor | R/W | RDI_WVCF | | F921 | TyreSize | TyreSize | R/W | RDI_TS | | F922 | nextCalibrationDate | NextCalibrationDate | R/W | RDI_NCD | | F92C | SpeedAuthorised | SpeedAuthorised | R/W | RDI_SA | | F97D | vehicleRegistrationNation | RegisteringMemberState | R/W | RDI_RMS | | F97E | VehicleRegistrationNumber | VehicleRegistrationNumber | R/W | RDI_ VRN | | F190 | VehicleIdentificationNumber | VIN | R/W | RDI_ VIN | | F9D0 | SensorSerialNumber | MotionSensorSerialNumber | R | RDI_SSN | | F9D1 | RemoteCommunicationModuleSerialNumber | RemoteCommunicationFacilitySerialNumber | R | RDI_RCSN | | F9D2 | SensorGNSSSerialNumber | ExternalGNSSFacilitySerialNumber | R | RDI_GSSN | | F9D3 | SealDataVu | SmartTachographSealsSerialNumber | R/W | RDI_SDV | | F9D4 | VuSerialNumber | VuSerialNumber | R | RDI_VSN | | F9D5 | ByDefaultLoadType | ByDefaultLoadType | R/W | RDI_BDLT | | F9D6 | TachographCardsGen1Suppression | TachographCardsGen1Suppression | R/W | RDI_TCG1S | | F9D7 | VehiclePosition | VehiclePosition | R | RDI_VP | | F9D8 | LastCalibrationCountry | CalibrationCountry | R | RDI_CC |

• CPR_054The parameter dataRecord (DREC_) is used by the ReadDataByIdentifier positive response message to provide the data record value identified by the recordDataIdentifier to the client (tester). Data formats are specified in section 8. Additional user optional dataRecords including VU specific input, internal and output data may be implemented, but are not defined in this document.

6.2.   WriteDataByIdentifier service

6.2.1   Message description

• CPR_056The WriteDataByIdentifier service is used by the client to write data record values to a server. The data are identified by a recordDataIdentifier. It is the VU manufacturer's responsibility that the server conditions are met when performing this service. To update the parameters listed in Table 28 the VU must be in CALIBRATION mode.

6.2.2   Message format

- CPR_057The message formats for the WriteDataByIdentifier primitives are detailed in the following tables.

Table 29

WriteDataByIdentifier Request Message

Byte #	Parameter Name	Parameter Name	Hex Value	Mnemonic
#1	Format byte — physical addressing	Format byte — physical addressing	80	FMT
#2	Target address byte	Target address byte	EE	TGT
#3	Source address byte	Source address byte	tt	SRC
#4	Additional length byte	Additional length byte	m + 3	LEN
#5	WriteDataByIdentifier Request Service Id	WriteDataByIdentifier Request Service Id	2E	WDBI
#6 to #7	recordDataIdentifier = [a value from Table 28]	recordDataIdentifier = [a value from Table 28]	xxxx	RDI_…
#8 to m + 7	dataRecord[] =	[data#1	xx	DREC_DATA1
#8 to m + 7	dataRecord[] =	:	:	:
#8 to m + 7	dataRecord[] =	data#m]	xx	DREC_DATAm
#m + 8	Checksum	Checksum	00-FF	CS

Table 30

WriteDataByIdentifier Positive Response Message

Byte #	Parameter Name	Hex Value	Mnemonic
#1	Format byte — physical addressing	80	FMT
#2	Target address byte	tt	TGT
#3	Source address byte	EE	SRC
#4	Additional length byte	03	LEN
#5	WriteDataByIdentifier Positive Response Service Id	6E	WDBIPR
#6 to #7	recordDataIdentifier = [the same value as bytes #6 and #7 Table 29]	xxxx	RDI_…
#8	Checksum	00-FF	CS

Table 31

WriteDataByIdentifier Negative Response Message

Byte #	Parameter Name	Parameter Name	Hex Value	Mnemonic
#1	Format byte — physical addressing	Format byte — physical addressing	80	FMT
#2	Target address byte	Target address byte	tt	TGT
#3	Source address byte	Source address byte	EE	SRC
#4	Additional length byte	Additional length byte	03	LEN
#5	NegativeResponse Service Id	NegativeResponse Service Id	7F	NR
#6	WriteDataByIdentifier Request Service Id	WriteDataByIdentifier Request Service Id	2E	WDBI
#7	ResponseCode=	[requestOutOfRange	31	RC_ROOR
#7	ResponseCode=	incorrectMessageLength	13	RC_IML
#7	ResponseCode=	conditionsNotCorrect]	22	RC_CNC
#8	Checksum	Checksum	00-FF	CS

6.2.3   Parameter definition

The parameter recordDataIdentifier (RDI_) is defined in Table 28.

The parameter dataRecord (DREC_) is used by the WriteDataByIdentifier request message to provide the data record values identified by the recordDataIdentifier to the server (VU). Data formats are specified in section 8.

7. CONTROL OF TEST PULSES — INPUT/OUTPUT CONTROL FUNCTIONAL UNIT

The services available are detailed in the following table:

Table 32

Input/Output Control functional unit

Service name	Description
InputOutputControlByIdentifier	The client requests the control of an input/output specific to the server.

7.1.   InputOutputControlByIdentifier service

7.1.1   Message description

There is a connection via the front connector which allows test pulses to be controlled or monitored using a suitable tester.

• CPR_058This calibration I/O signal line can be configured by K-line command using the InputOutputControlByIdentifier service to select the required input or output function for the line. The available states of the line are:

- — disabled,

- — speedSignalInput, where the calibration I/O signal line is used to input a speed signal (test signal) replacing the motion sensor speed signal, this function is not available in CONTROL mode,

• — realTimeSpeedSignalOutputSensor, where the calibration I/O signal line is used to output the speed signal of the motion sensor,

- — RTCOutput, where the calibration I/O signal line is used to output the UTC clock signal, this function is not available in CONTROL mode.

• CPR_059The vehicle unit must have entered an adjustment session and must be in CALIBRATION or CONTROL mode to configure the state of the line. When the VU is in CALIBRATION mode, the four states of the line can be selected (disabled, speedSignalInput, realTimeSpeedSignalOutputSensor, RTCOutput). When the VU is in CONTROL mode, only two states of the lines can be selected (disabled, realTimeSpeedOutputSensor). On exit of the adjustment session or of the CALIBRATION or CONTROL mode the vehicle unit must ensure the calibration I/O signal line is returned to the ‘disabled’ (default) state.

- CPR_060If speed pulses are received at the real time speed signal input line of the VU while the calibration I/O signal line is set to input then the calibration I/O signal line shall be set to output or returned to the disabled state.

- CPR_061The sequence shall be:

• — Establish communications by StartCommunication Service

• — Enter an adjustment session by StartDiagnosticSession Service and be in CALIBRATION or CONTROL mode of operation (the order of these two operation is not important).

- — Change the state of the output by InputOutputControlByIdentifier Service.

7.1.2   Message format

• CPR_062The message formats for the InputOutputControlByIdentifier primitives are detailed in the following tables.

Table 33

InputOutputControlByIdentifier Request Message

Byte #	Parameter Name	Hex Value	Mnemonic
#1	Format byte — physical addressing	80	FMT
#2	Target address byte	EE	TGT
#3	Source address byte	tt	SRC
#4	Additional length byte	xx	LEN
#5	InputOutputControlByIdentifier Request Sid	2F	IOCBI
#6 and #7	InputOutputIdentifier = [CalibrationInputOutput]	F960	IOI_CIO
#8 or #8 to #9	ControlOptionRecord = [		COR_…
#8 or #8 to #9	inputOutputControlParameter — one value from Table 36	xx	IOCP_…
#8 or #8 to #9	controlState — one value from Table 37 (see note below)]	xx	CS_…
#9 or #10	Checksum	00-FF	CS

Note: The controlState parameter is present only in some cases (see 7.1.3).

Table 34

InputOutputControlByIdentifier Positive Response Message

Byte #	Parameter Name	Hex Value	Mnemonic
#1	Format byte — physical addressing	80	FMT
#2	Target address byte	tt	TGT
#3	Source address byte	EE	SRC
#4	Additional length byte	xx	LEN
#5	inputOutputControlByIdentifier Positive Response SId	6F	IOCBIPR
#6 and #7	inputOutputIdentifier = [CalibrationInputOutput]	F960	IOI_CIO
#8 or #8 to #9	controlStatusRecord = [		CSR_
#8 or #8 to #9	inputOutputControlParameter (same value as byte #8 Table 33)	xx	IOCP_…
#8 or #8 to #9	controlState (same value as byte #9 Table 33)] (if applicable)	xx	CS_…
#9 or #10	Checksum	00-FF	CS

Table 35

InputOutputControlByIdentifier Negative Response Message

Byte #	Parameter Name	Hex Value	Mnemonic
#1	Format byte — physical addressing	80	FMT
#2	Target address byte	tt	TGT
#3	Source address byte	EE	SRC
#4	Additional length byte	03	LEN
#5	negativeResponse Service Id	7F	NR
#6	inputOutputControlByIdentifier Request SId	2F	IOCBI
#7	responseCode=[
#7	incorrectMessageLength	13	RC_IML
#7	conditionsNotCorrect	22	RC_CNC
#7	requestOutOfRange	31	RC_ROOR
#7	deviceControlLimitsExceeded]	7A	RC_DCLE
#8	Checksum	00-FF	CS

7.1.3   Parameter definition

- CPR_064The parameter inputOutputControlParameter (IOCP_) is defined in the following table.

Table 36

Definition of inputOutputControlParameter values

| Hex | Description | Mnemonic |

| --- | --- | --- | | 00 | ReturnControlToECU This value shall indicate to the server (VU) that the tester does no longer have control about the calibration I/O signal line. | RCTECU | | 01 | ResetToDefault This value shall indicate to the server (VU) that it is requested to reset the calibration I/O signal line to its default state. | RTD | | 03 | ShortTermAdjustment This value shall indicate to the server (VU) that it is requested to adjust the calibration I/O signal line to the value included in the controlState parameter. | STA |

- CPR_065The parameter controlState is present only when the inputOutputControlParameter is set to ShortTermAdjustment and is defined in the following table:

Table 37

Definition of controlState values

Mode	Hex Value	Description
Disable	00	I/O line is disabled (default state)
Enable	01	Enable calibration I/O line as speedSignalInput
Enable	02	Enable calibration I/O line as realTimeSpeedSignalOutputSensor
Enable	03	Enable calibration I/O line as RTCOutput

• 8.1. Message description CPR_065a The service RoutineControl (TimeAdjustment) provides the ability to trigger an alignment of the VU clock to the time provided by the GNSS receiver. For the service RoutineControl (TimeAdjustment) execution the VU must be in CALIBRATION mode. Precondition: it is ensured that the VU is able to receive authenticated position messages from the GNSS receiver. As long the time adjustment is ongoing, the VU shall respond to the request RoutineControl, subfunction requestRoutineResults, with routineInfo = 0x78. Note: the time adjustment may take some time. The diagnostic tester shall request the time adjustment status by using the sub-function requestRoutineResults.

• 8.2. Message format CPR_065b The message formats for the service RoutineControl (TimeAdjustment) and its primitives are detailed in the following tables. Table 37a RoutineControl, routine (TimeAdjustment) Request Message, subfunction startRoutine Byte # Parameter Name Hex Value Mnemonic

1

Format byte - physical addressing 80 FMT

2

Target address byte EE TGT

3

Source address byte tt SRC

4

Additional length byte xx LEN #5 RoutineControl Request Sid 31 RC

6

routineControlType = [startRoutine] 01 RCTP_STR

7 and #8

routineIdentifier = [TimeAdjustment] 0100 RI_TA

9

Checksum 00-FF CS Table 37b RoutineControl, routine (TimeAdjustment), subfunction startRoutine, Positive Response Message Byte # Parameter Name Hex Value Mnemonic

1

Format byte – physical addressing 80 FMT

2

Target address byte tt TGT

3

Source address byte EE SRC

4

Additional length byte xx LEN #5 RoutineControl Positive Response Sid 71 RCPR

6

routineControlType = [startRoutine] 01 RCTP_STR

7 and #8

routineIdentifier= [TimeAdjustment] 0100 RI_TA

9

Checksum 00-FF CS Table 37c RoutineControl, routine (TimeAdjustment) Request Message, subfunction requestRoutineResults Byte # Parameter Name Hex Value Mnemonic

1

Format byte - physical addressing 80 FMT

2

Target address byte EE TGT

3

Source address byte tt SRC

4

Additional length byte xx LEN #5 RoutineControl Request Sid 31 RC

6

routineControlType = [requestRoutineResults] 03 RCTP_RRR

7 and #8

routineIdentifier= [TimeAdjustment] 0100 RI_TA

9

Checksum 00-FF CS Table 37d RoutineControl, routine (TimeAdjustment), subfunction requestRoutineResults, Positive Response Message Byte # Parameter Name Hex Value Mnemonic

1

Format byte – physical addressing 80 FMT

2

Target address byte tt TGT

3

Source address byte EE SRC

4

Additional length byte xx LEN #5 RoutineControl Positive Response Sid 71 RCPR

6

routineControlType = [requestRoutineResults] 03 RCTP_RRR

7 and #8

routineIdentifier= [TimeAdjustment] 0100 RI_TA

9

routineInfo (see Table 37f) XX RINF_TA

10

routineStatusRecord[] = routineStatus#1 (see Table 37g) XX RS_TA

11

Checksum 00-FF CS Table 37e RoutineControl, routine (TimeAdjustment) Negative Response Message Byte # Parameter Name Hex Value Mnemonic

1

Format byte – physical addressing 80 FMT

2

Target address byte tt TGT

3

Source address byte EE SRC

4

Additional length byte 03 LEN #5 negativeResponse Service Id 7F NR

6

inputOutputControlByIdentifier Request SId 31 RC

7

responseCode=[ sub-functionNotSupported incorrectMessageLengthOrInvalidFormat conditionsNotCorrect requestOutOfRange ] 12 13 22 31 SFNS IMLOIF CNC ROOR

8

Checksum 00-FF CS Table 37f RoutineControl, routine (TimeAdjustment), routineInfo routineInfo Hex Value Description NormalExitWithResultAvailable 61 The routine was executed completely; additional routine results available. RoutineExecutionOngoing 78 The requested routine is still executed. Table 37g RoutineControl, routine (TimeAdjustment), routineStatus Hex Value Test result Description 01 positive The time adjustment successfully finished. 02..0F

RFU 10 negative No GNSS signal reception. 11..7F

RFU 80..FF

Manufacturer specific

This section details:

• — general rules that shall be applied to ranges of parameters transmitted by the vehicle unit to the tester,

• — formats that shall be used for data transferred via the Data Transmission Services described in section 6.

• CPR_067 All parameters identified shall be supported by the VU.

• CPR_068 Data transmitted by the VU to the tester in response to a request message shall be of the measured type (i.e. current value of the requested parameter as measured or observed by the VU).

• 9.1. Transmitted parameter ranges CPR_069 Table 38 defines the ranges used to determine the validity of a transmitted parameter. CPR_070 The values in the range ‘error indicator’ provide a means for the vehicle unit to immediately indicate that valid parametric data is not currently available due to some type of error in the tachograph. CPR_071 The values in the range ‘not available’ provide a means for the vehicle unit to transmit a message which contains a parameter that is not available or not supported in that module. The values in the range ‘not requested’ provide a means for a device to transmit a command message and identify those parameters where no response is expected from the receiving device. CPR_072 If a component failure prevents the transmission of valid data for a parameter, the error indicator as described in Table 38 should be used in place of that parameter’s data. However, if the measured or calculated data has yielded a value that is valid yet exceeds the defined parameter range, the error indicator should not be used. The data should be transmitted using the appropriate minimum or maximum parameter value.

Table 38 dataRecords ranges Range Name 1 byte (Hex value) 2 bytes (Hex value) 4 bytes (Hex Value) ASCII Valid signal 00 to FA 0000 to FAFF 00000000 to FAFFFFFF 1 to 254 Parameter specific indicator FB FB00 to FBFF FB000000 to FBFFFFFF none Reserved range for future indicator bits FC to FD FC00 to FDFF FC000000 to FDFFFFFF none Error indicator FE FE00 to FEFF FE000000 to FEFFFFFF 0 Not available or not requested FF FF00 to FFFF FF000000 to FFFFFFFF FF CPR_073 For parameters coded in ASCII, the ASCII character ‘*’ is reserved as a delimiter.

• 9.2. dataRecords formats Table 39 to Table 42 below detail the formats that shall be used via the ReadDataByIdentifier and WriteDataByIdentifier Services. CPR_074 Table 39 provides the length, resolution and operating range for each parameter identified by its recordDataIdentifier:

Table 39 Format of dataRecords Parameter Name Data length (bytes) Resolution Operating range TimeDate 8 See details in Table 40 HighResolutionTotalVehicleDistance 4 5 m/bit gain, 0 m offset 0 to +21 055 406 km Kfactor 2 0.001 pulse/m /bit gain, 0 offset 0 to 64.255 pulse/m LfactorTyreCircumference 2 0.125 10^-3 m /bit gain, 0 offset 0 to 8.031 m WvehicleCharacteristicFactor 2 0.001 pulse/m /bit gain, 0 offset 0 to 64.255 pulse/m TyreSize 15 ASCII ASCII NextCalibrationDate 3 See details in Table 41 SpeedAuthorised 2 1/256 km/h/bit gain, 0 offset 0 to 250.996 km/h RegisteringMemberState 3 ASCII ASCII VehicleRegistrationNumber 14 See details in Table 42 VIN 17 ASCII ASCII SealDataVu 55 See details in Table 43 ByDefaultLoadType 1 See details in Table 44 VuSerialNumber 8 See details in Table 45 SensorSerialNumber 8 See details in Table 45 SensorGNSSSerialNumber 8 See details in Table 45 RemoteCommunicationModuleSerialNumber 8 See details in Table 45 TachographCardsGen1Suppression 2 See details in Table 46 VehiclePosition 14 See details in Table 47 CalibrationCountry 3 ASCII NationAlpha as defined in Appendix 1 CPR_075 Table 40 details the formats of the different bytes of the TimeDate parameter:

Table 40 Detailed format of TimeDate (recordDataIdentifier value # F90B) Byte Parameter definition Resolution Operating range 1 Seconds 0.25 s/bit gain, 0 s offset 0 to 59.75s 2 Minutes 1 min/bit gain, 0 min offset 0 to 59 min 3 Hours 1 h/bit gain, 0 h offset 0 to 23 h 4 Month 1 month/bit gain, 0 month offset 1 to 12 month 5 Day 0.25 day/bit gain, 0 day offset (see NOTE below Table 41) 0.25 to 31.75 day 6 Year 1 year/bit gain, +1985 year offset (see NOTE below Table 41) 1985 to 2235 year 7 Local Minute Offset 1 min/bit gain, -125 min offset -59 to +59 min 8 Local Hour Offset 1 h/bit gain, -125 h offset - 23 to +23 h CPR_076 Table 41 details the formats of the different bytes of the NextCalibrationDate parameter:

Table 41 Detailed format of NextCalibrationDate (recordDataIdentifier value # F922) Byte Parameter definition Resolution Operating range 1 Month 1 month/bit gain, 0 month offset 1 to 12 month 2 Day 0.25 day/bit gain, 0 day offset (see NOTE below) 0.25 to 31.75 day 3 Year 1 year/bit gain, +1985 year offset (see NOTE below) 1985 to 2235 year NOTE concerning the use of the ‘Day’ parameter: 1) A value of 0 for the date is null. The values 1, 2, 3, and 4 are used to identify the first day of the month; 5, 6, 7, and 8 identify the second day of the month; etc. 2) This parameter does not influence or change the hours parameter above. NOTE concerning the use of the ‘Year’ parameter: A value of 0 for the year identifies the year 1985; a value of 1 identifies 1986; etc. CPR_078 Table 42 details the formats of the different bytes of the VehicleRegistrationNumber parameter:

Table 42 Detailed format of VehicleRegistrationNumber (recordDataIdentifier value # F97E) Byte Parameter definition Resolution Operating range 1 Code Page (as defined in Appendix 1) not applicable VehicleRegistrationNumber 2 – 14 Vehicle Registration Number (as defined in Appendix 1) not applicable VehicleRegistrationNumber CPR_090 Table 43 details the formats of the different bytes of the SealDataVu parameter:

Table 43 Detailed format of SealDataVu (recordDataIdentifier value # F9D3) Byte Parameter definition Resolution Operating range 1 – 11 sealRecord1. Format SealRecord as defined in Appendix 1. not applicable SealRecord 12 - 22 sealRecord2. Format SealRecord as defined in Appendix 1. not applicable SealRecord 23 – 33 sealRecord3. Format SealRecord as defined in Appendix 1. not applicable SealRecord 34 – 44 sealRecord4. Format SealRecord as defined in Appendix 1. not applicable SealRecord 45 – 55 sealRecord5. Format SealRecord as defined in Appendix 1. not applicable SealRecord NOTE: If there are less than 5 seals available the value of the EquipmentType in all unused sealRecords shall be set to 15, i.e. unused. CPR_091 Table 44 details the formats of the different bytes of the ByDefaultLoadType parameter:

Table 44 Detailed format of ByDefaultLoadType (recordDataIdentifier value # F9D5) Byte Parameter definition Resolution Operating range 1 loadType '00'H: Undefined load type '01'H: Goods '02'H: Passengers not applicable '00'H to '02'H CPR_092 Table 45 details the formats of the different bytes of the VuSerialNumber, SensorSerialNumber, SensorGNSSSerialNumber and RemoteCommunicationModuleSerialNumber parameters:

Table 45 Detailed format of VuSerialNumber, SensorSerialNumber, SensorGNSSSerialNumber and RemoteCommunicationModuleSerialNumber (recordDataIdentifier values # F9D4, F9D0, F9D2, F9D1) Byte Parameter definition Resolution Operating range 1 VuSerialNumber, SensorSerialNumber, SensorGNSSSerialNumber and RemoteCommunicationModuleSerialNumber: format ExtendedSerialNumber as defined in Appendix 1. not applicable ExtendedSerialNumber CPR_093 Table 46 details the formats of the different bytes of the TachographCardsGen1Suppression parameter:

Table 46 Detailed format of TachographCardsGen1Suppression (recordDataIdentifier value # F9D6) Byte Parameter definition Resolution Operating range 1-2 TachographCardsGen1Suppression. Format TachographCardsGen1Suppression as defined in Appendix 1. not applicable '0000'H, 'A5E3'H CPR_094 Table 47 details the formats of the different bytes of the VehiclePosition parameter.

Table 47 Detailed format of VehiclePosition (recordDataIdentifier value # F9D7) Byte Parameter definition Resolution Operating range 1 - 4 Time stamp of the vehicle position was determined. Not applicable TimeReal 5 GNSS accuracy Not applicable GNSSAccuracy 6 - 11 Vehicle position Not applicable GeoCoordinates 12 Authentication status Not applicable PositionAuthenticationStatus 13 Current country Not applicable NationNumeric 14 Current region Not applicable RegionNumeric Note: after vehicle position update, the update of current country and region may be delayed.

Appendix 9

TYPE APPROVAL LIST OF MINIMUM REQUIRED TESTS

TABLE OF CONTENT	TABLE OF CONTENT
1.	INTRODUCTION
2.	VEHICLE UNIT FUNCTIONAL TESTS
3.	MOTION SENSOR FUNCTIONAL TESTS
4.	TACHOGRAPH CARDS FUNCTIONAL TESTS
5.	EXTERNAL GNSS FACILITY TESTS
6.	EXTERNAL REMOTE COMMUNICATION FACILITY TESTS
7.	PAPER FUNCTIONAL TESTS
8.	INTEROPERABILITY TESTS
9.	OSNMA TESTS

1.1.   Type approval

The EC type approval for a recording equipment (or component) or a tachograph card is based on:

• — a security certification, based on Common Criteria specifications, against a security target fully compliant with Appendix 10 to this Annex,

• — a functional certification performed by a Member State authority certifying that the item tested fulfils the requirements of this Annex in terms of functions performed, measurement accuracy and environmental characteristics,

• — an interoperability certification performed by the competent body certifying that the recording equipment (or tachograph card) is fully interoperable with the necessary tachograph card (or recording equipment) models (see Chapter 8 of this Annex).

This Appendix specifies which tests, as a minimum, must be performed by a Member State authority during the functional tests, and which tests, as a minimum, must be performed by the competent body during the interoperability tests. Procedures to follow to carry out the tests or the type of tests are not specified further.

The security certification aspects are not covered by this Appendix. If some tests requested for type approval are performed during the security evaluation and certification process, then these tests do not need to be performed again. In this case, only the results of these security tests may be inspected. For information, the requirements expected to be tested (or closely related to tests expected to be performed) during the security certification, are marked with a ‘*’ in this Appendix.

The numbered requirements refer to the Annex corpus, while the other requirements refer to the other appendixes (e.g. PIC_001 refers to requirement PIC_001 of Appendix 3 Pictograms).

This Appendix considers separately the type approval of the motion sensor, of the vehicle unit, and of the external GNSS facility as components of the recording equipment. Each component will get its own type approval certificate in which the other compatible components will be indicated. The functional test of the motion sensor (or external GNSS facility) is done together with the vehicle unit and vice versa.

Interoperability between every model of motion sensor (resp. external GNSS facility) and every model of vehicle unit is not required. In that case the type approval for a motion sensor (resp. external GNSS facility) can be granted only in combination with the type approval of the relevant vehicle unit and vice versa.

The Member States authority in charge of the functional tests of a vehicle unit or an external GNSS facility must make sure that the embedded GNSS receiver has successfully passed the OSNMA tests specified in this Appendix. These tests are considered to be a part of the functional tests of the vehicle unit or the external GNSS facility.

1.2.   References

The following references are used in this Appendix:

IEC 60068-2-1:Environmental testing — Part 2-1: Tests — Test A: Cold

IEC 60068-2-2:Basic environmental testing procedures; part 2: tests; tests B: dry heat (sinusoidal).

IEC 60068-2-6:Environmental testing — Part 2: Tests — Test Fc: Vibration

IEC 60068-2-14:Environmental testing; Part 2-14: Tests; Test N: Change of temperature

IEC 60068-2-27:Environmental testing. Part 2: Tests. Test Ea and guidance: Shock

IEC 60068-2-30:Environmental testing — Part 2-30: Tests — Test Db: Damp heat, cyclic (12 h + 12 h cycle)

IEC 60068-2-64:Environmental testing — Part 2-64: Tests — Test Fh: Vibration, broadband random and guidance

IEC 60068-2-78Environmental testing — Part 2-78: Tests — Test Cab: Damp heat, steady state

ISO 16750-3 —Mechanical loads (2012-12)

ISO 16750-4 —Climatic loads(2010-04).

ISO 20653:Road vehicles — Degree of protection (IP code) — Protection of electrical equipment against foreign objects, water and access

ISO 10605:2008 + Technical Corrigendum:2010 + AMD1:2014Road vehicles — Test methods for electrical disturbances from electrostatic discharge

ISO 7637-1:2002 + AMD1: 2008Road vehicles — Electrical disturbances from conduction and coupling — Part 1: Definitions and general considerations.

ISO 7637-2Road vehicles — Electrical disturbances from conduction and coupling — Part 2: Electrical transient conduction along supply lines only.

ISO 7637-3Road vehicles — Electrical disturbances from conduction and coupling — Part 3: Electrical transient transmission by capacitive and inductive coupling via lines other than supply lines.

ISO/IEC 7816-1Identification cards — Integrated circuit(s) cards with contacts — Part 1: Physical characteristics..

ISO/IEC 7816-2Information technology — Identification cards — Integrated circuit(s) cards with contacts — Part 2: Dimensions and location of the contacts.

ISO/IEC 7816-3Information technology — Identification cards — Integrated circuit(s) cards with contacts — Part 3: Electronic signals and transmission protocol.

ISO/IEC 10373-1:2006 + AMD1:2012Identification cards — Test methods — Part 1: General characteristics

ISO/IEC 10373-3:2010 + Technical Corrigendum:2013Identification cards — Test methods — Part 3: Integrated circuit cards with contacts and related interface devices

ISO 16844-3:2004, Cor 1:2006Road vehicles — Tachograph systems — Part 3: Motion sensor interface (with vehicle units).

ISO 16844-4Road vehicles — Tachograph systems — Part 4: CAN interface

ISO 16844-6Road vehicles — Tachograph systems — Part 6: Diagnostics

ISO 16844-7Road vehicles — Tachograph systems — Part 7: Parameters

ISO 534Paper and board — Determination of thickness, density and specific volume

RGODPJRC Technical Report - Receiver guidelines for OSNMA data processing

UN ECE R10Uniform provisions concerning the approval of vehicles with regard to electromagnetic compatibility (United Nation Economic Commission for Europe)

| No | Test | Description | Related requirements |

| --- | --- | --- | --- | | 1. | Administrative examination | Administrative examination | Administrative examination | | 1.1 | Documentation | Correctness of documentation | | | 1.2 | Manufacturer test results | Results of manufacturer test performed during integration. Paper demonstrations. | 88, 89,91 | | 2. | Visual inspection | Visual inspection | Visual inspection | | 2,1 | Compliance with documentation | Compliance with documentation | | | 2.2 | Identification / markings | Identification / markings | 224 to 226 | | 2.3 | Materials | Materials | 219 to 223 | | 2.4 | Sealing | Sealing | 398, 401 to 405 | | 2.5 | External interfaces | External interfaces | | | 3. | Functional tests | Functional tests | Functional tests | | | | | | | 3.1 | Functions provided | Functions provided | 02, 03, 04, 05, 07, 382, | | 3.2 | Modes of operation | Modes of operation | 09 to 11, 134, 135 | | 3.3 | Functions and data access rights | Functions and data access rights | 12, 13, 382, 383, 386 to 389 | | 3.4 | Monitoring cards insertion and withdrawal | Monitoring cards insertion and withdrawal | 15, 16, 17, 18, 19, 20, 134 | | 3.5 | Speed, position and distance measurement | Speed, position and distance measurement | 21 to 37 | | 3.6 | Time measurement (test performed at 20°C) | Time measurement (test performed at 20°C) | 38 to 43 | | 3.7 | Monitoring driver activities | Monitoring driver activities | 44 to 53, 134 | | 3.8 | Monitoring driving status | Monitoring driving status | 54, 55, 134 | | 3.9 | Driver’s entries | Driver’s entries | 56 to 62c | | 3.10 | Company locks management | Company locks management | 63 to 68 | | 3.11 | Monitoring control activities | Monitoring control activities | 69, 70 | | 3.12 | Detection of events and/or faults | Detection of events and/or faults | 71 to 88a, 134 | | 3.13 | Equipment identification data | Equipment identification data | 93, 94, 97, 100 | | 3.14 | Driver or workshop card insertion and withdrawal data | Driver or workshop card insertion and withdrawal data | 102 to 104 | | 3.15 | Driver activity data | Driver activity data | 105 to 107 | | 3.16 | Places and positions data | Places and positions data | 108 to 112 | | 3.17 | Odometer data | Odometer data | 113 to 115 | | 3.18 | Detailed speed data | Detailed speed data | 116 | | 3.19 | Events data | Events data | 117 | | 3.20 | Faults data | Faults data | 118 | | 3.21 | Calibration data | Calibration data | 119 to 121 | | 3.22 | Time adjustment data | Time adjustment data | 124, 125 | | 3.23 | Control activity data | Control activity data | 126, 127 | | 3.24 | Company locks data | Company locks data | 128 | | 3.25 | Download activity data | Download activity data | 129 | | 3.26 | Specific conditions data | Specific conditions data | 130, 131 | | 3.27 | Tachograph cards data | Tachograph cards data | 132, 133 | | 3.28 | Border crossings | Border crossings | 133a to 133d | | 3.29 | Load/unload operation | Load/unload operation | 133e to 133i | | 3.30 | Digital map | Digital map | 133j to 133t | | 3.31 | Recording and storing on tachographs cards | Recording and storing on tachographs cards | 136, 137, 138, 139, 141, 142, 143 144, 145, 146, 147, 147a, 147b, 148, 149, 150, 150a | | 3.32 | Displaying | Displaying | 90, 134, 151 to 168, PIC_001, DIS_001 | | 3.33 | Printing | Printing | 90, 134, 169 to 181, PIC_001, PRT_001 to PRT_014 | | 3.34 | Warning | Warning | 134, 182 to 191, PIC_001 | | 3.35 | Data downloading to external media | Data downloading to external media | 90, 134, 192 to 196 | | 3.36 | Remote communication for targeted roadside checks | Remote communication for targeted roadside checks | 197 to 199 | | 3.37 | Data exchanges with additional external devices | Data exchanges with additional external devices | 200, 201 | | 3.38 | Calibration | Calibration | 202 to 206, 383, 384, 386 to 391 | | 3.39 | Roadside calibration checking | Roadside calibration checking | 207 to 209 | | 3.40 | Time adjustment | Time adjustment | 210 to 212 | | 3.41 | Monitoring border crossings | Monitoring border crossings | 226a to 226c | | 3.42 | Software update | Software update | 226d to 226f | | 3.43 | Non-interference of additional functions | Non-interference of additional functions | 06, 425 | | 3.44 | Motion sensor interface | Motion sensor interface | 02, 122 | | 3.45 | External GNSS facility | External GNSS facility | 03, 123 | | 3.46 | Verify that the VU detects, records and stores the event(s) and/or fault(s) defined by the VU manufacturer when a paired motion sensor reacts to magnetic fields disturbing vehicle motion detection. | Verify that the VU detects, records and stores the event(s) and/or fault(s) defined by the VU manufacturer when a paired motion sensor reacts to magnetic fields disturbing vehicle motion detection. | 217 | | 3.47 | Cypher suite and standardized domain parameters | Cypher suite and standardized domain parameters | CSM_48, CSM_50 | | | | | | | 4. | Environmental tests | Environmental tests | Environmental tests | | 4.1 | Temperature | Verify functionality through: Test according to ISO 16750-4, Chapter 5.1.1.2: Low temperature operation test (72 h @ – 20 °C) This test refers to IEC 60068-2-1: Environmental testing - Part 2-1: Tests - Test A: Cold Test according to ISO 16750-4: Chapter 5.1.2.2: High temperature operation test (72 h at 70 °C) This test refers to IEC 60068-2-2: Basic environmental testing procedures; part 2: tests; tests B: dry heat Test according to ISO 16750-4: Chapter 5.3.2: Rapid change of temperature with specified transition duration (– 20 °C/70 °C, 20 cycles, dwell time 2h at each temperature) A reduced set of tests (among those defined in section 3 of this table) can be carried out at the lower temperature, the higher temperature and during the temperature cycles | 213 | | 4.2 | Humidity | Verify that the vehicle unit can withstand a cyclic damp (heat test) through IEC 60068-2-30, test Db, six 24 hours cycles, each temperature varying from +25 °C to + 55 °C and a relative humidity of 97 % at + 25 °C and equal to 93 % at +55 °C | 214 | | 4.3 | Mechanical | 1. Sinusoidal vibrations. verify that the vehicle unit can withstand sinusoidal vibrations with the following characteristics: constant displacement between 5 and 11 Hz: 10mm peak constant acceleration between 11 and 300 Hz: 5g This requirement is verified through IEC 60068-2-6, test Fc, with a minimum test duration of 3 × 12 hours (12 hours per axis) ISO 16750-3 does not require a sinusoidal vibration test for devices located in the decoupled vehicle cab. 2. Random vibrations: Test according to ISO 16750-3: Chapter 4.1.2.8: Test VIII: Commercial vehicle, decoupled vehicle cab Random vibration test, 10…2000 Hz, RMS vertical 21,3 m/s², RMS longitudinal 11,8 m/s², RMS lateral 13,1 m/s², 3 axes, 32 h per axis, including temperature cycle – 20…70 °C. This test refers to IEC 60068-2-64: Environmental testing - Part 2-64: Tests - Test Fh: Vibration, broadband random and guidance 3. Shocks: mechanical shock with 3 g half sinus according ISO 16750. The tests described above are performed on different samples of the equipment type being tested. | 219 | | 4.4 | Protection against water and foreign bodies | Test according to ISO 20653: Road vehicles – Degree of protection (IP code) – Protection of electrical equipment against foreign objects, water and access (No change in parameters); Minimum value IP 40 | 220, 221 | | 4.5 | Over-voltage protection | Verify that the vehicle unit can withstand a power supply of: 24 V versions: 34V at + 40 °C 1 hour 12V versions: 17V at + 40 °C 1 hour (ISO 16750-2) | 216 | | 4.6 | Reverse polarity protection | Verify that the vehicle unit can withstand an inversion of its power supply (ISO 16750-2) | 216 | | 4.7 | Short-circuit protection | Verify that input output signals are protected against short circuits to power supply and ground (ISO 16750-2) | 216 | | 5. | EMC tests | EMC tests | EMC tests | | 5.1 | Radiated emissions and susceptibility | Compliance with Regulation ECE R10 | 218 | | 5.2 | Electrostatic discharge | Compliance with ISO 10605:2008 + Technical Corrigendum:2010 + AMD1:2014: +/– 4 kV for contact and +/– 8 kV for air discharge | 218 | | 5.3 | Conducted transient susceptibility on power supply | For 24V versions: compliance with ISO 7637-2 + ECE Regulation No. 10 Rev. 3: pulse 1a: Vs=450V Ri=50 ohms pulse 2a: Vs=+37V Ri=2 ohms pulse 2b: Vs=+20V Ri=0,05 ohms pulse 3a: Vs=– 150V Ri=50 ohms pulse 3b: Vs=+150V Ri=50 ohms pulse 4: Vs=– 16V Va=– 12V t6=100ms pulse 5: Vs=+120V Ri=2,2 ohms td=250ms For 12V versions: compliance with ISO 7637– 1 + ECE Regulation No. 10 Rev. 3: pulse 1: Vs=– 75V Ri=10 ohms pulse 2a: Vs=+37V Ri=2 ohms pulse 2b: Vs=+10V Ri=0,05 ohms pulse 3a: Vs=– 112V Ri=50 ohms pulse 3b: Vs=+75V Ri=50 ohms pulse 4: Vs=– 6V Va=– 5V t6=15ms pulse 5: Vs=+65V Ri=3ohms td=100ms Pulse 5 shall be tested only for vehicle units designed to be installed in vehicles for which no external common protection against load dump is implemented For load dump proposal, refer to ISO 16750-2, 4th edition, chapter 4.6.4. | 218 |

3. MOTION SENSOR FUNCTIONAL TESTS

No	Test	Description	Related requirements
1.	Administrative examination	Administrative examination	Administrative examination
1.1	Documentation	Correctness of documentation
2.	Visual inspection	Visual inspection	Visual inspection
2.1.	Compliance with documentation	Compliance with documentation
2.2.	Identification/markings	Identification/markings	225, 226,
2.3	Materials	Materials	219 to 223
2.4.	Sealing	Sealing	398, 401 to 405
3.	Functional tests	Functional tests	Functional tests
3.1	Sensor identification data	Sensor identification data	95 to 97*
3.2	Motion sensor — vehicle unit pairing	Motion sensor — vehicle unit pairing	122*, 204
3.3	Motion detection Motion measurement accuracy	Motion detection Motion measurement accuracy	30 to 35
3.4	Vehicle unit interface	Vehicle unit interface	02
3.5	Check that the motion sensor is immune to constant magnetic field. Alternatively, verify that the motion sensor reacts to constant magnetic fields disturbing vehicle motion detection so that a connected VU can detect, record and store sensor faults	Check that the motion sensor is immune to constant magnetic field. Alternatively, verify that the motion sensor reacts to constant magnetic fields disturbing vehicle motion detection so that a connected VU can detect, record and store sensor faults	217
4.	Environmental tests	Environmental tests	Environmental tests
4.1	Operating temperature	Verify functionality (as defined in test No 3.3) in temperature range [– 40°C; + 135°C] through: IEC 60068-2-1 test Ad, with a test duration of 96 hours at the lowest temperature Tomin, IEC 60068-2-2 test Bd, with a test duration of 96 hours at the highest temperature Tomax Test according to ISO 16750-4: Chapter 5.1.1.2: Low temperature operation test (24 h @ – 40 °C) This test refers to IEC 60068-2-1: Environmental testing — Part 2-1: Tests — Test A: Cold IEC 68-2-2 test Bd, with a test duration of 96 hours at the lowest temperature of – 40°C. Test according to ISO 16750-4: Chapter 5.1.2.2: High temperature operation test (96 h @ 135 °C) This test refers to IEC 60068-2-2: Basic environmental testing procedures; part 2: tests; tests B: dry heat	213
4.2	Temperature cycles	Test according to ISO 16750-4: Chapter 5.3.2: Rapid change of temperature with specified transition duration (– 40°C/135 °C, 20 cycles, dwell time 30 min at each temperature) IEC 60068-2-14: Environmental testing; Part 2-14: Tests; Test N: Change of temperature	213
4.3	Humidity cycles	Verify functionality (as defined in test No. 3.3) through IEC 60068-2-30, test Db, six 24 hours cycles, each temperature varying from + 25°C to + 55°C and a relative humidity of 97 % at + 25°C and equal to 93 % at + 55°C	214
4.4	Vibration	ISO 16750-3: Chapter 4.1.2.6: Test VI: Commercial vehicle, engine, gearbox Mixed mode vibration test including a) Sinusoidal vibration test, 20…520 Hz, 11,4 … 120 m/s2, <= 0,5 oct/min b) Random vibration test, 10…2 000  Hz, RMS 177 m/s2 94 h per axis, including temperature cycle – 20…70°C) This test refers to IEC 60068-2-80: Environmental testing — Part 2-80: Tests — Test Fi: Vibration — Mixed mode	219
4.5	Mechanical shock	ISO 16750-3: Chapter 4.2.3: Test VI: Test for devices in or on the gearbox half-sinusoidal shock, acceleration to be agreed in the range 3 000 …15 000  m/s2, pulse duration to be agreed, however < 1 ms, number of shocks: to be agreed This test refers to IEC 60068-2-27: Environmental testing. Part 2: Tests. Test Ea and guidance: Shock	219
4.6	Protection against water and foreign bodies	Test according to ISO 20653: Road vehicles — Degree of protection (IP code) — Protection of electrical equipment against foreign objects, water and access (Target value IP 64)	220, 221
4.7	Reverse polarity protection	Verify that the motion sensor can withstand an inversion of its power supply	216
4.8	Short circuit protection	Verify that input output signals are protected against short circuits to power supply and ground	216
5.	EMC	EMC	EMC
5.1	radiated emissions and susceptibility	Verify compliance with Regulation ECE R10	218
5.2	Electrostatic discharge	Compliance with ISO 10605:2008 + Technical Corrigendum:2010 + AMD1:2014: +/– 4kV for contact and +/– 8kV for air discharge	218
5.3	Conducted transient susceptibility on data lines)	For 24V versions: compliance with ISO 7637-2 + ECE Regulation No. 10 Rev. 3: pulse 1a: Vs = – 450 V Ri = 50 ohms pulse 2a: Vs = + 37 V Ri = 2 ohms pulse 2b: Vs = + 20 V Ri = 0,05 ohms pulse 3a: Vs = – 150 V Ri = 50 ohms pulse 3b: Vs = + 150 V Ri = 50 ohms pulse 4: Vs= – 16 V Va = – 12 V t6 = 100ms pulse 5: Vs = + 120 V Ri = 2,2 ohms td = 250ms For 12V versions: compliance with ISO 7637-1 + ECE Regulation No. 10 Rev. 3: pulse 1: Vs = – 75 V Ri = 10 ohms pulse 2a: Vs = + 37 V Ri = 2 ohms pulse 2b: Vs = + 10 V Ri = 0,05 ohms pulse 3a: Vs = – 112 V Ri = 50 ohms pulse 3b: Vs = + 75 V Ri = 50 ohms pulse 4: Vs= – 6 V Va=-5 V t6 = 15 ms pulse 5: Vs = + 65 V Ri = 3 ohms td = 100 ms Pulse 5 shall be tested only for vehicle units designed to be installed in vehicles for which no external common protection against load dump is implemented For load dump proposal, refer to ISO 16750-2, 4th edition, chapter 4.6.4	218

Tests according to this Section 4,

no. 5 ‘Protocol tests’,

no. 6 ‘Card structure’ and

no. 7 ‘Functional tests’

can be performed by the evaluator or certifier during the Common Criteria (CC) security certification process for the chip module.

Tests number 2.3 and 4.2 are the same. These are the mechanical tests of the combination card body and chip module. If one of these components (card body, chip module) is changed, then these tests are necessary.

No	Test	Description	Related requirements
1.	Administrative examination	Administrative examination	Administrative examination
1.1	Documentation	Correctness of documentation
2	Card Body	Card Body	Card Body
2.1	Printed Design	Make sure that all features for protection and visible data are correctly printed on the card and compliant. [Designator] Annex 1C, chapter 4.1 ‘Visible data’, 227) The front page shall contain: the words ‘Driver card’ or ‘Control card’ or ‘Workshop card’ or ‘Company card’ printed in capital letters in the official language or languages of the Member State issuing the card, according to the type of the card. [Member State name] Annex 1C, chapter 4.1 ‘Visible data’, 228) The front page shall contain: the name of the Member State issuing the card (optional). [Sign] Annex 1C, chapter 4.1 ‘Visible data’, 229) The front page shall contain: the distinguishing sign of the Member State issuing the card, printed in negative in a blue rectangle and encircled by 12 yellow stars. [Enumeration] Annex 1C, chapter 4.1 ‘Visible data’, 232) The reverse page shall contain: an explanation of the numbered items which appear on the front page of the card. [Colour] Annex 1C, chapter 4.1 ‘Visible data’, 234) Tachograph cards shall be printed with the following background predominant colours: — driver card: white, — workshop card: red, — control card: blue, — company card: yellow. [Security] Annex 1C, chapter 4.1 ‘Visible data’, 235) Tachograph cards shall bear at least the following features for protection of the card body against counterfeiting and tampering: — a security design background with fine guilloche patterns and rainbow printing, — at least one two-coloured microprint line. [Markings] Annex 1C, chapter 4.1 ‘Visible data’, 236) Member States may add colours or markings, such as national symbols and security features. [Approval mark] Tachograph cards shall contain an approval mark. The approval mark shall be made up of: — a rectangle, within which shall be placed the letter ‘e’ followed by a distinguishing number or letter for the country which has issued the approval, — an approval number corresponding to the number of the approval certificate for a tachograph card, placed at any point within the immediate proximity of this rectangle.	227 to 229, 232, 234 to 236
2.2	Mechanical Tests	[Card size] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [5] Dimension of card, [5.1] Card size, [5.1.1] Card dimensions and tolererances, card type ID-1 Unused card [Card edges] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [5] Dimension of card, [5.1] Card size, [5.1.2] Card edges [Card construction] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [6] Card construction [Card materials] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [7] Card materials [Bending stiffness] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.1] Bending stiffness [Toxicity] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.3] Toxicity [Resistance to chemicals] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.4] Resistance to chemicals [Card stability] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.5] Card dimensional stability and warpage with temperature and humidity [Light] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.6] Light [Durability] Annex 1C, chapter 4.4 ‘Environmental and electrical specifications’, 241) Tachograph cards shall be capable of operating correctly for a five-year period if used within the environmental and electrical specifications. [Peel strength] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.8] Peel strength [Adhesion or blocking] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.9] Adhesion or blocking [Warpage] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.11] Overall card warpage [Resistance to heat] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.12] Resistance to heat [Surface distortions] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.13] Surface distortions [Contamination] Tachograph cards must conform to standard ISO/IEC 7810, Identification cards — Physical characteristics, [8] Card characteristics, [8.14] Contamination and interaction of card components	240, 243 ISO/IEC 7810
2.3	Mechanical tests with chip module embedded	[Bending] Tachograph cards must conform to standard ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits [9.2] Dynamic bending stress Total number of bending cycles: 4 000 . [Torsion] Tachograph cards must conform to standard ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits [9.3] Dynamic torsional stress Total number of torsion cycles: 4 000 .	ISO/IEC 7810
3	Module	Module	Module
3.1	Module	Module is the chip encapsulation and the contact plate. [Surface profile] Tachograph cards must conform to standard ISO/IEC 7816-1:2011, Identification cards — Integrated circuit cards — Part 1: Cards with contacts — Physical characteristics [4.2] Surface profile of contacts [Mechanical strength] Tachograph cards must conform to standard ISO/IEC 7816-1:2011, Identification cards — Integrated circuit cards — Part 1: Cards with contacts — Physical characteristics [4.3] Mechanical strength (of a card and contacts) [Electrical resistance] Tachograph cards must conform to standard ISO/IEC 7816-1:2011, Identification cards — Integrated circuit cards — Part 1: Cards with contacts — Physical characteristics [4.4] Electrical resistance (of contacts) [Dimension] Tachograph cards must conform to standard ISO/IEC 7816-2:2007, Identification cards — Integrated circuit cards — Part 2: Cards with contacts — Dimension and location of the contacts [3] Dimension of the contacts [Location] Tachograph cards must conform to standard ISO/IEC 7816-2:2007, Identification cards — Integrated circuit cards — Part 2: Cards with contacts — Dimension and location of the contacts [4] Number and location of the contacts In case of modules with six contacts, contact ‘C4’ and ‘C8’ are not part of this test requirement.	ISO/IEC 7816
4	Chip	Chip	Chip
4.1	Chip	[Operating temperature] The Tachograph card chip shall operate in an ambient temperature range between – 25 °C and + 85 °C. [Temperature and humidity] Annex 1C, chapter 4.4 ‘Environmental and electrical specifications’, 241) Tachograph cards shall be capable of operating correctly in all the climatic conditions normally encountered in Community territory and at least in the temperature range – 25°C to + 70°C with occasional peaks of up to + 85°C, ‘occasional’ meaning not more than 4 hours each time and not over 100 times during the life time of the card. The Tachograph cards are exposed in consecutive steps to the following temperatures and humidities for the given time. After each step the Tachograph cards are tested for electrical functionality. 1. Temperature of – 20 °C for 2 h. 2. Temperature of +/– 0 °C for 2 h. 3. Temperature of + 20 °C, 50 % RH, for 2 h. 4. Temperature of + 50 °C, 50 % RH, for 2 h. 5. Temperature of + 70 °C, 50 % RH, for 2 h. The temperature is increased intermittently to + 85 °C, 50 % RH, for 60 min. 6. Temperature of + 70 °C, 85 % RH, for 2 h. The temperature is increased intermittently to + 85 °C, 85 % RH, for 30 min. [Humidity] Annex 1C, chapter 4.4 ‘Environmental and electrical specifications’, 242) Tachograph cards shall be capable of operating correctly in the humidity range 10 % to 90 %. [Electromagnetic compatibility — EMC] Annex 1C, chapter 4.4 ‘Environmental and electrical specifications’ 244) During operation, Tachograph cards shall conform to ECE R10 related to electromagnetic compatibility. [Static electricity] Annex 1C, chapter 4.4 ‘Environmental and electrical specifications’, 244) During operation, Tachograph cards shall be protected against electrostatic discharges. Tachograph cards must conform to standard ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits [9.4] Static electricity [9.4.1] Contact IC cards Test voltage: 4 000  V. [X-rays] Tachograph cards must conform to standard ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits [9.1] X-rays [Ultraviolet light] ISO/IEC 10373-1:2006, Identification cards — Test methods — Part 1: General characteristics [5.11] Ultraviolet light [3-wheel] Tachograph cards must conform to standard ISO/IEC 10373-1:2006/Amd. 1:2012, Identification cards — Test methods — Part 1: General characteristics, Amendment 1 [5.22] ICC — Mechanical strength: 3 wheel test for ICCs with contacts [Wrapping] Tachograph cards must conform to standard MasterCard CQM V2.03:2013 [11.1.3] R-L3-14-8: Wrapping Test Robustness [13.2.1.32] TM-422: Mechanical Reliability: Wrapping Test	241 to 244 ECE R10 ISO/IEC 7810 ISO/IEC 10373
4.2	Mechanical tests chip module embedded in the card body-> same as 2.3	[Bending] Tachograph cards must conform to standard ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits [9.2] Dynamic bending stress Total number of bending cycles: 4 000 . [Torsion] Tachograph cards must conform to standard ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits [9.3] Dynamic torsional stress Total number of torsion cycles: 4 000 .	ISO/IEC 7810
5	Protocol tests	Protocol tests	Protocol tests
5.1	ATR	Check that the ATR is compliant	ISO/IEC 7816-3 TCS_14, TCS_17, TCS_18
5.2	T=0	Check that T=0 protocol is compliant	ISO/IEC 7816-3 TCS_11, TCS_12, TCS_13, TCS_15
5.3	PTS	Check that the PTS command is compliant by setting T=1 from T=0.	ISO/IEC 7816-3 TCS_12, TCS_19, TCS_20, TCS_21
5.4	T=1	Check that T=1 protocol is compliant	ISO/IEC 7816-3 TCS_11, TCS_13, TCS_16
6	Card structure	Card structure	Card structure
6.1		Test that the file structure of the card is compliant by checking the presence of the mandatory files in the card and their access conditions	TCS_22 to TCS_28 TCS_140 to TCS_179
7	Functional tests	Functional tests	Functional tests
7.1	Normal processing	Test at least once each allowed usage of each command (ex: test the UPDATE BINARY command with CLA = ‘00’, CLA = ‘0C’ and with different P1,P2 and Lc parameters) Check that the operations have actually been performed in the card (ex: by reading the file the command has been performed on)	TCS_29 to TCS_139
7.2	Error messages	Test at least once each error message (as specified in Appendix 2) for each command Test at least once every generic error (except ‘6400’ integrity errors checked during security certification)	TCS_29 to TCS_139
7.3	Cypher suite and standardized domain parameters	Cypher suite and standardized domain parameters	CSM_48, CSM_50
8	Personalisation	Personalisation	Personalisation
8.1	Optical personalisation	Annex 1C, chapter 4.1 ‘Visible data’, 230) The front page shall contain: information specific to the card issued. Annex 1C, chapter 4.1 ‘Visible data’, 231) The front page shall contain: dates using a ‘dd/mm/yyyy’ or ‘dd.mm.yyyy’ format (day, month, year). Annex 1C, chapter 4.1 ‘Visible data’, 235) Tachograph cards shall bear at least the following features for protection of the card body against counterfeiting and tampering: — in the area of the photograph, the security design background and the photograph shall overlap.	230, 231, 235