Commission Implementing Regulation (EU) 2016/799Show full title

6. DATA TRANSMISSION SERVICES

The services available are detailed in the following table:

Table 24

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_050 The 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_051 The 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		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		m+3	LEN
#5	ReadDataByIdentifier Positive Response Service Id		62	RDBIPR
#6 and #7	recordDataIdentifier = [the same value as bytes #6 and #7 Table 25]		xxxx	RDI_...
#8 to #m + 7	dataRecord[] =	[data#1	xx	DREC_DATA1
		:	:	:
		data#m]	xx	DREC_DATAm
#m + 8	Checksum		00-FF	CS

Table 27

ReadDataByIdentifier 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	ReadDataByIdentifier Request Service Id		22	RDBI
#7	ResponseCode=	[requestOutOfRange	31	RC_ROOR
		incorrectMessageLength	13	RC_IML
		conditionsNotCorrect]	22	RC_CNC
#8	Checksum		00-FF	CS

6.1.3 Parameter Definition

CPR_052 The parameter recordDataIdentifier (RDI_) in the ReadDataByIdentifier request message identifies a data record.

CPR_053 recordDataIdentifier values defined by this document are shown in the table below.

The recordDataIdentifier table consists of four columns and multiple lines.

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

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

• The 3rd column (Description) specifies the corresponding recordDataIdentifier name.

• The 4th 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)	Mnemonic
F90B		TimeDate	RDI_TD
F912		HighResolutionTotalVehicleDistance	RDI_HRTVD
F918		Kfactor	RDI_KF
F91C		LfactorTyreCircumference	RDI_LF
F91D		WvehicleCharacteristicFactor	RDI_WVCF
F921		TyreSize	RDI_TS
F922		NextCalibrationDate	RDI_NCD
F92C		SpeedAuthorised	RDI_SA
F97D		RegisteringMemberState	RDI_RMS
F97E		VehicleRegistrationNumber	RDI_ VRN
F190		VIN	RDI_ VIN

CPR_054 The 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_056 The 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_057 The message formats for the WriteDataByIdentifier primitives are detailed in the following tables.

Table 29
WriteDataByIdentifier 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		m + 3	LEN
#5	WriteDataByIdentifier Request Service Id		2E	WDBI
#6 to #7	recordDataIdentifier = [a value from Table 28]		xxxx	RDI_…
#8 to m + 7	dataRecord[] =	[data#1	xx	DREC_DATA1
		:	:	:
		data#m]	xx	DREC_DATAm
#m + 8	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		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	WriteDataByIdentifier Request Service Id		2E	WDBI
#7	ResponseCode=	[requestOutOfRange	31	RC_ROOR
		incorrectMessageLength	13	RC_IML
		conditionsNotCorrect]	22	RC_CNC
#8	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.