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

8. DATARECORDS FORMATS U.K.

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. U.K.

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). U.K.

8.1. Transmitted parameter ranges U.K.

CPR_069 Table 38 defines the ranges used to determine the validity of a transmitted parameter. U.K.

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. U.K.

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. U.K.

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. U.K.

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. U.K.

8.2. dataRecords formats U.K.

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: U.K.

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

CPR_075 Table 40 details the formats of the different bytes of the TimeDate parameter: U.K.

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,75 s
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. U.K.

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: U.K.

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 byte ‘Year’ parameter: U.K.

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: U.K.

Table 42
Detailed format of VehicleRegistrationNumber (recordDataIdentifier value # F97E)
Byte	Parameter definition	Resolution	Operating range
1	Code Page (as defined in Appendix 1)	ASCII	01 to 0A
2 - 14	Vehicle Registration Number (as defined in Appendix 1)	ASCII	ASCII