‘3.6.4

Entry of load/unload operation’;

‘3.9.18

‘GNSS anomaly’ event’;

‘3.12.17

Border crossings

3.12.18

Load/unload operations

3.12.19

Digital map’;

‘3.20

Data exchanges with additional external devices’;

‘3.27

Monitoring border crossings

3.28

Software update’;

‘4.5.3.2.1.1

Additional application identification (not accessed by version 1 of second generation vehicle units)’;

‘4.5.3.2.17

Authentication status for positions related to places where daily work periods start and/or end (not accessed by version 1 of second generation vehicle units)

4.5.3.2.18

Authentication status for positions where three hours accumulated driving time are reached (not accessed by version 1 of second generation vehicle units)

4.5.3.2.19

Border crossings (not accessed by version 1 of second generation vehicle units)

4.5.3.2.20

Load/unload operations (not accessed by version 1 of second generation vehicle units)

4.5.3.2.21

Load type entries (not accessed by version 1 of second generation vehicle units)

4.5.3.2.22

VU configurations (not accessed by version 1 of second generation vehicle units)’;

‘4.5.4.2.1.1

Additional application identification (not accessed by version 1 of second generation vehicle units)’;

‘4.5.4.2.16

Authentication status for positions related to places where daily work periods start and/or end (not accessed by version 1 of second generation vehicle units)

4.5.4.2.17

Authentication status for positions where three hours accumulated driving are reached (not accessed by version 1 of second generation vehicle units)

4.5.4.2.18

Border crossings (not accessed by version 1 of second generation vehicle units)

4.5.4.2.19

Load/unload operations (not accessed by version 1 of second generation vehicle units)

4.5.4.2.20

Load type entries (not accessed by version 1 of second generation vehicle units)

4.5.4.2.21

Calibration Additional Data (not accessed by version 1 of second generation vehicle units)

4.5.4.2.22

VU configurations (not accessed by version 1 of second generation vehicle units)’;

‘4.5.5.2.1.1

Additional application identification (not accessed by version 1 of second generation vehicle units)’;

‘4.5.5.2.6

VU configurations (not accessed by version 1 of second generation vehicle units)’;

‘4.5.6.2.1.1

Additional application identification (not accessed by version 1 of second generation vehicle units)’;

‘4.5.6.2.6

VU configurations (not accessed by version 1 of second generation vehicle units)’;

‘(f)

‘calibration of a smart tachograph’ means:

updating or confirming vehicle parameters to be held in the data memory. Vehicle parameters include vehicle identification (VIN, VRN and registering Member State) and vehicle characteristics (w, k, l, tyre size, speed-limiting device setting (if applicable), current UTC time, current odometer value, by-default load type); during the calibration of a recording equipment, the types and identifiers of all type-approval relevant seals in place shall also be stored in the data memory;

any update or confirmation of UTC time only, shall be considered as a time adjustment and not as a calibration, provided it does not contradict requirement 409 set out in point 6.4.

calibrating a recording equipment requires the use of a workshop card;’;

‘(g)

‘card number’ means:

a 16-alpha-numerical characters number that uniquely identifies a tachograph card within a Member State. The card number includes an identification, which consists in a driver identification, or in a card owner identification together with a card consecutive index, a card replacement index and a card renewal index;

a card is therefore uniquely identified by the code of the issuing Member State and the card number;’;

‘(i)

‘card renewal index’ means:

the 16th alpha-numerical character of a card number which is incremented each time a tachograph card corresponding to a given identification, i.e. driver identification or owner identification together with consecutive index, is renewed;

(j)

‘card replacement index’ means:

the 15th alpha-numerical character of a card number which is incremented each time a tachograph card corresponding to a given identification, i.e. driver identification or owner identification together with consecutive index, is replaced;’;

‘(ee)

‘non-valid card’ means:

a card detected as faulty, or which authentication failed, or whose start of validity date is not yet reached, or which expiry date has passed;

a card is also considered as non-valid by the vehicle unit:

‘(ll)

‘remote communication facility’, ‘remote communication module’ or ‘remote early detection facility’ means:

the equipment of the vehicle unit which is used to perform targeted roadside checks;’;

‘(nn)

‘card renewal’ means:

issue of a new tachograph card when an existing card reaches its expiry date, or is malfunctioning and has been returned to the issuing authority;’;

‘(pp)

‘card replacement’ means:

issue of a new tachograph card in replacement of an existing card, which has been declared as lost, stolen or malfunctioning and has not been returned to the issuing authority;’;

‘(tt)

‘time adjustment’ means:

an adjustment of current time; this adjustment can be automatic, using the time provided by the GNSS receiver as a reference, or performed in calibration mode;’;

‘-

installed and used only in M1 and N1 type vehicles, as defined in Article 4 of Regulation (EU) 2018/858 of the European Parliament and of the Council (1),’;

‘(aaa)

reserved for future use;’;

‘(ccc)

‘introduction date’ means:

the date set out in Regulation (EU) No 165/2014 as from which vehicles registered for the first time shall be fitted with a tachograph in accordance with this Regulation.’;

‘(5)

The vehicle unit shall include an ITS interface, which is specified in Appendix 13.

The recording equipment may be connected to other facilities through additional interfaces and/or through the ITS interface.’;

‘-

drivers manual entries:

‘—

monitoring border crossings,

—

software update.’;

‘-

The downloading function is not accessible in the operational mode, except:

(i)

the second indent is replaced by the following:

(ii)

the fourth indent is replaced by the following:

‘(16)

Upon card insertion (or remote card authentication) the recording equipment shall detect whether the card is a valid tachograph card in accordance with definition (ee) in section 1, and in such a case identify the card type and the card generation.

For checking if a card has already been inserted, the recording equipment shall use the tachograph card data stored in its data memory, as set out in requirement 133.’;

‘(20)

The withdrawal of tachograph cards may function only when the vehicle is stopped and after the relevant data have been stored on the cards. The withdrawal of the card shall require positive action by the user.’;

‘(26)

To detect manipulation of motion data, information from the motion sensor shall be corroborated by vehicle motion information derived from the GNSS receiver and by other source(s) independent from the motion sensor. At least another independent vehicle motion source shall be inside the VU without the need of an external interface.

(27)

This function shall measure the position of the vehicle in order to allow for the recording of:

‘(33)

To ensure a maximum tolerance on speed displayed of ± 6 km/h in use, and taking into account:

the recording equipment shall, for speeds between 20 and 180 km/h, and for characteristic coefficients of the vehicle between 2 400 and 25 000 imp/km, measure the speed with a tolerance of ± 1 km/h (at constant speed).

Note: The resolution of data storage brings an additional tolerance of ± 0,5 km/h to speed stored by the recording equipment.’;

‘(37)

The absolute position shall be measured in geographical coordinates of latitude and longitude in degrees and minutes with a resolution of 1/10 of a minute.’;

‘(41)

Time drift shall be ± 1 second per day or less, in temperature conditions in accordance with requirement 213, in the absence of any time adjustment.’;

‘(41a)

Time accuracy when time is adjusted by workshops in accordance with requirement 212 shall be 3 seconds or better.

(41b)

The vehicle unit shall include a drift counter, which computes the maximal time drift since the last time adjustment in accordance with point 3.23. The maximal time drift shall be defined by the vehicle unit manufacturer and shall not exceed 1 second per day, as set out in requirement 41.

(41c)

The drift counter shall be reset to 1 second after each time adjustment of the recording equipment in accordance with point 3.23. This includes:

(i)

paragraphs (57) to (59) are replaced by the following:

(ii)

the following subparagraph is added in paragraph (60):

‘The recording equipment shall display the current place of the vehicle on the basis of the GNSS information, and of stored digital map(s) in accordance with point 3.12.19 and shall request the driver to confirm or to manually rectify the place.’;

‘(61)

Upon driver (or workshop) card insertion, and only at this time, the recording equipment shall allow manual entries of activities. Manual entries of activities shall be performed using local time and date values of the time zone (UTC offset) currently set for the vehicle unit.

At driver or workshop card insertion the cardholder shall be reminded of:

At the first insertion of a given driver card or workshop card currently unknown to the vehicle unit, the cardholder shall be invited to express his consent for tachograph related personal data output through the ITS interface. For checking if a card has already been inserted, the recording equipment shall use the tachograph card data stored in its data memory, as set out in requirement 133.

At any moment, the driver (resp. workshop) consent can be enabled or disabled through commands in the menu, provided the driver (resp. workshop) card is inserted.

It shall be possible to input activities with the following restrictions:

It shall be possible to make manual entries, if required, at the first insertion of a previously unused driver (or workshop) card.

The procedure for manual entries of activities shall include as many consecutive steps as necessary to set a type, a start time and an end time for each activity. For any part of the time period between last card withdrawal and current card insertion, the cardholder shall have the option not to declare any activity.

During the manual entries associated with card insertion and if applicable, the card holder shall have the opportunity to input:

For the place where the current daily work period begins entered at the current card insertion, the recording equipment shall display the current place of the vehicle on the basis of the GNSS information, and of stored digital map(s) in accordance with point 3.12.19, and shall request the driver to confirm or to manually rectify the place.

If the card holder does not enter any place where the work period begins or ended, during the manual entries associated with card insertion, this shall be considered as a declaration that his work period has not changed since the last card withdrawal. The next entry of a place where a previous daily work period ends shall then overwrite the temporary entry made at the last card withdrawal.

If a place is entered, it shall be recorded in the relevant tachograph card.

Manual entries shall be interrupted if:

Additional interruptions are allowed, e.g. a timeout after a certain period of user inactivity. If manual entries are interrupted, the recording equipment shall validate any complete place and activity entries (having either unambiguous place and time, or activity type, begin time and end time) already made.

If a second driver or workshop card is inserted while manual entries of activities are in progress for a previously inserted card, the manual entries for this previous card shall be allowed to be completed before manual entries start for the second card.

The cardholder shall have the option to insert manual entries according to the following minimum procedure:

The procedure shall end when the end time of a manually entered activity equals the card insertion time.

The recording equipment shall allow drivers and workshops to alternately upload manual entries that need to be entered during the procedure through the ITS interface specified in Appendix 13 and, optionally, through other interfaces.

The recording equipment shall allow the card holder to modify any activity manually entered, until validation by selection of a specific command. Thereafter, any such modification shall be forbidden.’;

‘(62)

The recording equipment shall allow the driver to enter, in real time, the following two specific conditions:

A ‘FERRY / TRAIN CROSSING’ shall not occur if an ‘OUT OF SCOPE’ condition is opened. If an ‘OUT OF SCOPE’ condition is opened, the recording equipment shall not allow users to enter a ‘FERRY / TRAIN CROSSING’ begin flag.

An opened ‘OUT OF SCOPE’ condition must be automatically closed, by the recording equipment, if a driver card is inserted or withdrawn.

An opened ‘OUT OF SCOPE’ condition shall inhibit the following events and warnings:

The driver shall enter the FERRY / TRAIN CROSSING begin flag immediately after selecting BREAK/REST on the ferry or train.

An opened FERRY / TRAIN CROSSING must be ended by the recording equipment when any of the following options occurs:

If more than one specific conditions entry of the same type is done within one calendar minute, only the last one shall be kept recorded.’;

‘3.6.4

Entry of load/unload operation

‘(83)

This event shall be triggered, while not in calibration mode, in case of interruption of the normal data flow between the motion sensor and the vehicle unit and/or in case of data integrity or data authentication error during data exchange between the motion sensor and the vehicle unit. This event shall also be triggered, while not in calibration mode, in case the speed calculated from the motion sensor pulses increases from 0 to more than 40 km/h within 1 second, and then stays above 40km/h during at least 3 seconds.’;

‘(84)

This event shall be triggered, as specified in Appendix 12, while not in calibration mode, in case motion information calculated from the motion sensor is contradicted by motion information calculated from the internal GNSS receiver or from the external GNSS facility or by other independent source(s) in accordance with requirement 26. This event shall not be triggered during a ferry/train crossing.’;

‘(86)

This event shall be triggered, while not in calibration mode, when the VU detects a discrepancy between the time of the vehicle unit’s time measurement function and the time originating from the authenticated positions transmitted by the GNSS receiver or the external GNSS facility. A ‘time discrepancy’ is detected if the time difference exceeds ±3 seconds corresponding to the time accuracy set out in requirement 41a, the latter increased by the maximal time drift per day. This event shall be recorded together with the internal clock value of the recording equipment. The VU shall perform the check for triggering the ‘time conflict’ event right before the VU automatically re-adjusts the VU internal clock, in accordance with requirement 211.’;

‘-

ITS interface fault.’;

‘3.9.18

‘GNSS anomaly’ event

—

‘365 days’ is defined as 365 calendar days of average drivers’ activity in a vehicle. The average activity per day in a vehicle is defined as at least 6 drivers or co-drivers, 6 card insertion withdrawal cycles, and 256 activity changes. ‘365 days’ therefore include at least 2 190 drivers or co-drivers, 2 190 card insertion withdrawal cycles, and 93 440 activity changes,

—

the average number of place entries per day is defined as at least 6 entries where the daily work period begins and 6 entries where the daily work period ends, so that ‘365 days’ include at least 4 380 place entries,

—

the average number of positions per day when the accumulated driving time reaches a multiple of three hours is defined as at least 6 positions, so that ‘365 days’ include at least 2 190 such positions,

—

the average number of border crossings per day is defined as at least 20 crossings, so that ‘365 days’ include at least 7 300 border crossings,

—

the average number of load/unload operations per day is defined as at least 25 operations (irrespective of the type), so that ‘365 days’ include at least 9 125 load/unload operations,

—

times are recorded with a resolution of one minute, unless otherwise specified,

—

odometer values are recorded with a resolution of one kilometre,

—

speeds are recorded with a resolution of 1 km/h,

—

positions (latitudes and longitudes) are recorded in degrees and minutes, with a resolution of 1/10 of minute, with the associated GNSS accuracy and acquisition time, and with a flag indicating whether the position has been authenticated.’;

(i)

in paragraph (93), the following indent is added:

(ii)

paragraph (94) is replaced by the following:

‘(97)

The vehicle unit shall be able to record and store in its data memory the following data related to the 20 most recent successful pairings of motion sensors (if several pairings happen within one calendar day, only the first and the last one of the day shall be stored):’;

‘(100)

The vehicle unit shall be able to record and store in its data memory the following data related to the 20 most recent successful couplings of external GNSS facilities (if several couplings happen within one calendar day, only the first and the last one of the day shall be stored).’;

(i)

paragraph (110) is amended as follows:

(ii)

the following paragraph (110a) is inserted:

(i)

the fifth row is replaced by the following:

(ii)

the following row is added:

‘-

the serial numbers of the motion sensor, the external GNSS facility (if any), and the external remote communication facility (if any),

-

the by-default load type associated to the vehicle (load of either goods or passengers),

-

the country in which the calibration has been performed, and the date time when the position used to determine this country was provided by the GNSS receiver.’;

(133a)

The recording equipment shall record and store in its data memory the following information about border crossings:

(133b)

Together with countries and position, the recording equipment shall record and store in its data memory:

(133c)

The data memory shall be able to hold border crossings for at least 365 days.

(133d)

When storage capacity is exhausted, new data shall replace oldest data.

(133e)

The recording equipment shall record and store in its data memory the following information about load and unload operations of the vehicle:

(133f)

When the position of the vehicle is not available from the GNSS receiver at the time of the load/unload operation, the recording equipment shall use the latest available position, and the related date and time.

(133g)

Together with the type of operation and position, the recording equipment shall record and store in its data memory:

(133h)

The data memory shall be able to store load/unload operations for at least 365 calendar days.

(133i)

When storage capacity is exhausted, new data shall replace oldest data.

(133j)

For the purpose of recording the position of the vehicle when the border of a country is crossed, the recording equipment shall store in its data memory a digital map.

(133k)

Allowed digital maps for supporting the border crossing monitoring function of the recording equipment shall be made available by the European Commission for download from a dedicated secured website, under various formats.

(133l)

For each of these maps, a version identifier and a hash value shall be available on the website.

(133m)

The maps shall feature:

(133n)

Tachograph manufacturers shall select a map from the website and download it securely.

(133o)

Tachograph manufacturers shall only use a downloaded map from the website after having verified its integrity using the hash value of the map.

(133p)

The selected map shall be imported in the recording equipment by its manufacturer, under an appropriate format, but the semantic of the imported map shall remain unchanged.

(133q)

The manufacturer shall also store the version identifier of the map used in the recording equipment.

(133r)

It shall be possible to update or replace the stored digital map by a new one made available by the European Commission.

(133s)

Digital map updates shall be made using the software update mechanisms set up by the manufacturer, in application of requirements 226d and 226e, so that the recording equipment can verify the authenticity and integrity of a new imported map, before storing it and replacing the previous one.

(133t)

Tachograph manufacturers may add additional information to the basic map referred to in requirement (133m), for purposes other than recording border crossings, such as the borders of the EU regions, provided that the semantic of the basic map is not changed.’;

‘-

to compute the driver's continuous driving time, cumulative break time and accumulated driving times for the previous and the current week,’;

‘(135a)

The structure in the ‘TACHO_G2’ application depends on the version. Version 2 cards contain additional Elementary Files to the ones of version 1 cards, in particular:

The vehicle unit shall ignore any authentication status found in EF Places_Authentication or EF GNSS_Places_Authentication, when no vehicle position with the same timestamp is found in EF Places or EF GNSS_Places.

The vehicle unit shall ignore the elementary file EF VU_Configuration in all cards insofar as no specific rules have been provided with respect to the use of such elementary file. Those rules shall be set out through an amendment of Annex IC, which shall include the modification or deletion of this paragraph.’;

(i)

paragraph (140) is replaced by the following:

(ii)

paragraph (143) is replaced by the following:

(i)

in paragraph (144), the following sub-paragraph is added:

‘The structure in the ‘TACHO_G2’ application depends on the version. Version 2 cards contain additional Elementary Files to the ones of version 1 cards.’;

(ii)

the following paragraphs (147a) and (147b) are inserted:

(iii)

the following paragraph (150a) is added:

‘-

the content of any of the printouts listed in requirement 169 under the same formats as the printouts themselves,’;

‘-

the accumulated driving time of the driver for the previous and the current week,

-

the accumulated driving time of the co-driver for the previous and the current week,’;

‘-

the accumulated driving time of the driver for the current week,

-

the accumulated driving time of the co-driver for the current daily work period,

-

the accumulated driving time of the driver for the current daily work period.’;

‘(193)

In addition and as an optional feature, the recording equipment may, in any mode of operation, download data through any other interface to a company authenticated through this channel. In such a case, company mode data access rights shall apply to this download.’;

‘(196a)

A transport undertaking which uses vehicles that are fitted with recording equipment complying with this Annex and fall within the scope of Regulation (EC) No 561/2006, shall ensure that all data are downloaded from the vehicle unit and driver cards.

The maximum period within which the relevant data are downloaded shall not exceed:

(196b)

Transport undertakings shall keep the data downloaded from the vehicle unit and driver cards for at least twelve months following recording.’;

‘3.20

Data exchanges with additional external devices’;

‘(200)

The recording equipment shall also be equipped with an ITS interface in accordance with Appendix 13, allowing the data recorded or produced by either the tachograph or the tachograph cards to be used by an external facility.

In operational mode, the driver consent shall be needed for the transmission of personal data through the ITS interface. Nevertheless, the driver consent shall not apply to tachograph or card data accessed in control, company or calibration mode. The data and functional access rights for these modes are specified in requirements 12 and 13.

The following requirements shall apply to ITS data made available through that interface:

Additional vehicle unit interfaces may co-exist, provided they fully comply with the requirements of Appendix 13 in terms of driver consent. The recording equipment shall have the capacity to communicate the driver consent status to other platforms in the vehicle network and to external devices.

For personal data injected in the vehicle network, which are further processed outside the vehicle network, it shall not be the responsibility of the tachograph manufacturer to have that personal data process compliant with the applicable Union legislation regarding data protection.

The ITS interface shall also allow for data entry during the manual entry procedure in accordance with requirement 61, for both the driver and the co-driver.

The ITS interface may also be used to enter additional information, in real time, such as:

This information may also be entered through other interfaces.’;

‘(201)

The serial link interface as specified in Annex IB to Regulation (EEC) No 3821/85, as last amended, can continue to equip tachographs for back compatibility. The serial link is classified as a part of the vehicle network, in accordance with requirement 200.’;

(i)

the ninth indent is replaced by the following:

(ii)

the following indent is added:

‘(205)

Coupling the external GNSS facility to the VU shall consist, at least, in:

‘(211)

The time setting of the VU internal clock shall be automatically re-adjusted at variable time intervals. The next automatic time re-adjustment shall be triggered between 72h and 168h after the previous one, and after the VU can access to GNSS time through a valid authenticated position message in accordance with Appendix 12. Nevertheless, the time adjustment shall never be bigger than the accumulated maximal time drift per day, as calculated by the VU manufacturer in accordance with requirement 41b. If the difference between internal VU clock time and GNSS receiver time is bigger than the accumulated maximum time drift per day, then the time adjustment shall bring the VU internal clock as close as possible to the GNSS receiver time. The time setting may only be done if the time provided by the GNSS receiver is obtained using authenticated position messages as set out in Appendix 12. The time reference for the automatic time setting of the VU internal clock shall be the time provided in the authenticated position message.’;

‘(212)

The time adjustment function shall also allow for triggered adjustment of the current time, in calibration mode.

Workshops may adjust time:

(226a)

This function shall detect when the vehicle has crossed the border of a country, which country has been left and which country has been entered.

(226b)

The border crossing detection shall be based on the position measured by the recording equipment, and stored digital map in accordance with point 3.12.19.

(226c)

Border crossings related to the presence of the vehicle in a country for a shorter period than 120s shall not be recorded.

(226d)

The vehicle unit shall incorporate a function for the implementation of software updates whenever such updates do not involve the availability of additional hardware resources beyond the resources set out in requirement 226f, and the type-approval authorities give their authorisation to the software updates based on the existing type-approved vehicle unit, in accordance with Article 12(5) of Regulation (EU) No 165/2014.

(226e)

The software update function shall be designed for supporting the following functional features, whenever they are legally required:

(226f)

The vehicle unit shall provide free hardware resources of at least 35% for software and data needed for the implementation of requirement 226e and free hardware resources of at least 65% for the update of the digital map based on the hardware resources required for the NUTS 0 map version 2021.’;

‘(246)

Any additional data may be stored on tachograph cards, provided that the storage of those data complies with the applicable legislation regarding data protection.’;

(i)

the header is replaced by the following:

(ii)

the following point 4.5.3.2.1.1 is inserted after point 4.5.3.2.1:

(iii)

in point 4.5.3.2.7, paragraph (287) is replaced by the following:

(iv)

in point 4.5.3.2.8, paragraph (290) is replaced by the following:

(v)

in point 4.5.3.2.9, paragraph (292) is replaced by the following:

(vi)

in point 4.5.3.2.10, paragraph (295) is replaced by the following:

(vii)

in point 4.5.3.2.11, paragraph (297) is replaced by the following:

(viii)

in point 4.5.3.2.14, paragraph (302) is replaced by the following:

(ix)

in point 4.5.3.2.15, paragraph (304) is replaced by the following:

(x)

in point 4.5.3.2.16, paragraph (306) is replaced by the following:

(xi)

the following points 4.5.3.2.17 to 4.5.3.2.22 are added:

(i)

the header is replaced by the following:

(ii)

the following point 4.5.4.2.1.1 is inserted after point 4.5.4.2.1:

(iii)

in point 4.5.4.2.6, paragraph (338) is replaced by the following:

(iv)

in point 4.5.4.2.8, paragraph (344) is replaced by the following:

(v)

in point 4.5.4.2.9, paragraph (346) is replaced by the following:

(vi)

point 4.5.4.2.10 is replaced by the following:

(vii)

in point 4.5.4.2.13, paragraph (352) is replaced by the following:

(viii)

in point 4.5.4.2.14, paragraph (354) is replaced by the following:

(ix)

in point 4.5.4.2.15, paragraph (356) is replaced by the following:

(x)

the following points 4.5.4.2.16 to 4.5.4.2.22 are added:

(i)

in point 4.5.5.1.5 the second indent is replaced by the following:

(ii)

the following point 4.5.5.2.1.1 is inserted after point 4.5.5.2.1:

(iii)

the following point is inserted after point 4.5.5.2.5:

(i)

the following point is inserted after point 4.5.6.2.1:

(ii)

the following point 4.5.6.2.6 is added:

(i)

paragraph (383) is replaced by the following:

(ii)

paragraph (392) is replaced by the following:

(i)

the first subparagraph in paragraph (395) is replaced by the following:

‘After the recording equipment has been checked on installation, an installation plaque, engraved or printed in a permanent way, which is clearly visible and easily accessible shall be affixed onto the recording equipment. In cases where this is not possible, the plaque shall be affixed to the vehicle's ‘B’ pillar so that it is clearly visible. For vehicles that do not have a ‘B’ pillar, the installation plaque should be affixed in the area of the door of the vehicle and be clearly visible in all cases.’;

(ii)

paragraph (396) is amended as follows:

‘(409)

Periodic inspections of the equipment fitted to the vehicles shall take place after any repair of the equipment, or after any alteration of the characteristic coefficient of the vehicle or of the effective circumference of the tyres, or after equipment UTC time is wrong by more than 5 minutes, or when the VRN has changed, and at least once within two years (24 months) of the last inspection.’;

‘-

that the version identifier of the stored digital map is the most recent one.’;

‘(410a)

In case of detection of a manipulation by the competent national authorities, the vehicle may be sent to an authorised workshop for a recalibration of the recording equipment.’;

‘(429)

Procedures to update in-situ recording equipment software shall be approved by the authority which granted type approval for the recording equipment. Software update must not alter nor delete any driver activity data stored in the recording equipment. Software may be updated only under the responsibility of the equipment manufacturer.

(430)

Type approval of software modifications aimed to update a previously type approved recording equipment may not be refused if such modifications only apply to functions not specified in this Annex. Software update of a recording equipment may exclude the introduction of new character sets, if not technically feasible.’;

(i)

paragraph (443) is replaced by the following:

(ii)

paragraph (447) is replaced by the following:

(i)

the following points 2.11a and 2.11b are inserted:

(ii)

the following points 2.24a, 2.24b, 2.24c and 2.24d are inserted:

(iii)

the following point 2.26a is inserted:

(iv)

the following point 2.48a is inserted:

(v)

the following point 2.50a is inserted:

(vi)

the following point 2.60a is inserted:

(vii)

the following point 2.61a is inserted:

(viii)

the following points 2.79a, 2.79b and 2.79c are inserted:

(ix)

point 2.84 is replaced by the following:

(x)

the following point 2.89a is inserted:

(xi)

the following point 2.90a is inserted:

(xii)

the following point 2.101a is inserted:

(xiii)

the following point 2.111a is inserted:

(xiv)

the following point 2.112a is inserted:

(xv)

the following point 2.114a is inserted:

(xvi)

the following points 2.116a and 2.116b are inserted:

(xvii)

the following point 2.117a is inserted:

(xviii)

the following point 2.158a is inserted:

(xix)

the following point 2.166a is inserted:

(xx)

the following point 2.185a is inserted:

(xxi)

the following point 2.192a is inserted:

(xxii)

the following points 2.203a and 2.203b are inserted:

(xxiii)

the following point 2.204a is inserted:

(xxiv)

the following points 2.208a and 2.208b are inserted:

(xxv)

the following point 2.222a is inserted:

(xxvi)

the following points 2.234a, 2.234b and 2.234c are inserted:

—

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

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

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

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

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

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

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

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

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

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

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.60a.

DownloadInterfaceVersion

Generation 2, version 2:

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

Value assignment: ‘aabb’H:

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

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

DSRCSecurityData

Generation 2:

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

(i)

the header corresponding to Generation 2 is replaced by the following:

‘Generation 2, version 1:’;

(ii)

the following text is added:

‘2.71.

ExtendedSealIdentifier

Generation 2:

The extended seal identifier uniquely identifies a seal (Annex IC requirement 401).

manufacturerCode is a code of the manufacturer of the seal. Value assignment: see database registration to be managed by the European Commission (see https://dtc.jrc.ec.europa.eu).

sealIdentifier is an identifier for the seal which is unique for the manufacturer. Value assignment: alpha-numeric number, unique in the manufacturer domain according to [ISO8859-1].’;

‘2.79a.

GNSSAuthAccumulatedDriving

Generation 2, version 2:

Information, stored in a driver or workshop card, providing the authentication status of GNSS positions of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirements 306d and 356d).

gnssAuthADPointerNewestRecord is the index of the last updated GNSS position authentication status record.

Value assignment is the number corresponding to the numerator of the GNSS position authentication status record, beginning with '0' for the first occurrence of the GNSS position authentication status record in the structure.

gnssAuthStatusADRecords is the set of records containing the date and time the accumulated driving reaches a multiple of three hours and the authentication status of the GNSS position.

2.79b.

GNSSAuthStatusADRecord

Generation 2, version 2:

Information, stored in a driver or workshop card, providing the authentication status of a GNSS position of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirements 306c and 356c). Other information related to the GNSS position itself is stored in another record (see 2.79 GNSSAccumulatedDrivingRecord).

timeStamp is the date and time when the accumulated driving time reaches a multiple of three hours (which is the same date and time as in the corresponding GNSSAccumulatedDrivingRecord).

authenticationStatus is the authentication status of the GNSS position when the accumulated driving time reaches a multiple of three hours.

2.79c.

GNSSPlaceAuthRecord

Generation 2, version 2:

Information related to the GNSS position of the vehicle (Annex IC requirements 108, 109, 110, 296, 306a, 306c, 306e, 306g, 356a, 356c, 356e and 356g).

timeStamp is the date and time when the GNSS position of the vehicle was determined.

gnssAccuracy is the accuracy of the GNSS position data.

geoCoordinates is the recorded location using GNSS.

authenticationStatus is the authentication status of the GNSS position when it was determined.’;

‘2.84.

Reserved for future use’;

‘2.89a.

LengthOfFollowingData

Generation 2, version 2:

Length indicator for extensible records.

Value assignment: See Appendix 2.’;

‘2.90a.

LoadType

Generation 2, version 2:

Code identifying a load type entered.

Value assignment:

‘2.101a.

NoOfBorderCrossingRecords

Generation 2, version 2:

Number of border crossing records a driver or workshop card can store.

Value assignment: see Appendix 2.’;

‘2.111a.

NoOfLoadUnloadRecords

Generation 2, version 2:

Number of load/unload records a card can store.

Value assignment: see Appendix 2.’;

‘2.112a.

NoOfLoadTypeEntryRecords

Generation 2, version 2:

Number of load type entry records a driver or workshop card can store.

Value assignment: see Appendix 2.’;

‘2.114a.

OperationType

Generation 2, version 2:

Code identifying a type of operation entered.

Value assignment:

‘2.116a.

PlaceAuthRecord

Information related to a place where a daily work period begins or ends (Annex IC requirements 108, 271, 296, 324 and 347).

Generation 2, version 2:

entryTime is a date and time related to the entry.

entryTypeDailyWorkPeriod is the type of entry.

dailyWorkPeriodCountry is the country entered.

dailyWorkPeriodRegion is the region entered.

vehicleOdometerValue is the odometer value at the time of place entry.

entryGNSSPlaceAuthRecord is the recorded location, GNSS authentication status and time.

2.116b.

PlaceAuthStatusRecord

Generation 2, version 2:

Information, stored in a driver or workshop card, providing the authentication status of a place where a daily work period begins or ends (Annex IC requirements 306a and 356a). Other information related to the place itself is stored in another record (see 2.117 PlaceRecord).

entryTime is a date and time related to the entry (which is the same date and time as in the corresponding PlaceRecord).

authenticationStatus is the authentication status of the recorded GNSS position.’;

‘2.117a.

PositionAuthenticationStatus

Generation 2, version 2:

Value assignment (see Appendix 12):

‘‘22’H

VuBorderCrossingRecord,

‘23’H

VuLoadUnloadRecord,

‘24’H

VehicleRegistrationIdentification,

‘25’H to ‘7F’H

RFU.’;

‘2.158a.

TachographCardsGen1Suppression

Generation 2, version 2:

Ability of a second generation VU to use first generation of driver, control and company cards (see Appendix 15, MIG_002).

‘2.166a.

VehicleRegistrationIdentificationRecordArray

Generation 2, version 2:

The Vehicle Registration Identification plus metadata as used in the download protocol.

recordType denotes the type of the record (VehicleRegistrationIdentification). Value assignment: see RecordType.

recordSize is the size of the VehicleRegistrationIdentification in bytes.

noOfRecords is the number of records in the set records.

records is the set of vehicle registration identification.’;

(i)

the header for Generation 2 is replaced by the following:

‘Generation 2, version 1:’;

(ii)

the following text is added:

‘Generation 2, version 2:

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

sensorSerialNumber is the serial number of the motion sensor paired with the vehicle unit at the end of the calibration,

sensorGNSSSerialNumber is the serial number of the external GNSS facility coupled with the vehicle unit at the end of the calibration (if any),

rcmSerialNumber is the serial number of the remote communication facility coupled with the vehicle unit at the end of the calibration (if any),

sealDataVu gives information about the seals that are attached to different components of the vehicle.

byDefaultLoadType is the by-default load type of the vehicle (only present in version 2).

calibrationCountry is the country in which the calibration has been performed.

calibrationCountryTimestamp is the date and time when the position used to determine the country in which the calibration has been performed was provided by the GNSS receiver.’;

‘2.185a.

VuConfigurationLengthRange

Generation 2, version 2:

Number of bytes in a tachograph card, available to store VU configurations.

Value assignment: see Appendix 2.’;

‘2.192a.

VuDigitalMapVersion

Generation 2, version 2:

Version of the digital map stored in the vehicle unit (Annex IC requirement 133j).

Value assignment: as specified on the dedicated secured website made available by the European Commission (Annex IC requirement 133k).’;

(i)

the header corresponding to Generation 2 is replaced by the following:

‘Generation 2, version 1:’;

(ii)

the following text is added:

‘Generation 2, version 2:

Information, stored in a vehicle unit, related to the GNSS position of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirement 108, 110).

In Generation 2 version 2, instead of gnssPlaceRecord, the gnssPlaceAuthRecord is used, which contains the GNSS authentication status in addition.’;

‘2.203a.

VuBorderCrossingRecord

Generation 2, version 2:

Information, stored in a vehicle unit, related to border crossings of the vehicle when the latter has crossed the border of a country (Annex IC requirement 133a and 133b).

cardNumberAndGenDriverSlot identifies the card including its generation which is inserted in the driver slot.

cardNumberAndGenCodriverSlot identifies the card including its generation which is inserted in the co-driver slot.

countryLeft is the country which was left by the vehicle, based on the last available position before the border crossing has been detected. ‘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. ‘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 border crossing was detected, 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.

2.203b.

VuBorderCrossingRecordArray

Generation 2, version 2:

Information, stored in a vehicle unit, related to border crossings of the vehicle (Annex IC requirement 133c).

recordType denotes the type of the record (VuBorderCrossingRecord). Value assignment: see RecordType.

recordSize is the size of the VuBorderCrossingRecord in bytes.

noOfRecords is the number of records in the set records.

records is a set of border crossing records.’;

‘2.204a.

VuGnssMaximalTimeDifference

Generation 2, version 2:

The maximal difference between true time and the VU Real Time Clock time, based on the maximal time drift specified in Annex IC requirement 041, transmitted by the vehicle unit to an external GNSS Facility, see Appendix 12 requirement GNS_3g.

’;

‘2.208a.

VuLoadUnloadRecord

Generation 2, version 2:

Information, stored in the vehicle unit, related to a load/unload operation entered (Annex IC requirements 133e, 133f and 133g).

timeStamp is the date and time when the load/unload operation was entered.

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

cardNumberAndGenDriverSlot identifies the card including its generation which is inserted in the driver slot.

cardNumberAndGenCodriverSlot identifies the card including its generation which is inserted in the co-driver slot.

gnssPlaceAuthRecord contains information related to the position of the vehicle, and its authentication status.

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

2.208b.

VuLoadUnloadRecordArray

Generation 2, version 2:

Information, stored in a vehicle unit, related to a load/unload operation vehicle entered (Annex IC requirement 133h).

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

recordSize is the size of the VuLoadUnloadRecord in bytes.

noOfRecords is the number of records in the set records.

records is a set of load/unload operation records.’;

(i)

the header for Generation 2 is replaced by the following:

‘Generation 2, version 1:’;

(ii)

the following text is added:

‘Generation 2, version 2:

Information, stored in a vehicle unit, related to a place where a driver begins or ends a daily work period (Annex 1B requirement 087 and Annex 1C requirement 108 and 110).

Instead of placeRecord, the generation 2 version 2 data structure makes use of the following data element:

placeAuthRecord contains the information related to the place entered, the recorded position, GNSS authentication status and position determination time.’;

‘2.222a.

VuRtcTime

Generation 2, version 2:

The time of the VU RTC clock, transmitted by the VU to an External GNSS Facility, see Appendix 12 requirement GNS_3f.

’;

‘2.234a.

WorkshopCardApplicationIdentificationV2

Generation 2, version 2:

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

lengthOfFollowingData is the number of bytes following in the record.

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

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

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

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

2.234b.

WorkshopCardCalibrationAddData

Generation 2, version 2:

Information, stored in a workshop card, related to the additional data (i.e. by-default load type) entered during a calibration (Annex IC requirement 356l).

calibrationPointerNewestRecord is the index of the last updated calibration additional data record.

Value assignment is the number corresponding to the numerator of the calibration additional data record, beginning with '0' for the first occurrence of the calibration additional data record in the structure.

workshopCardCalibrationAddDataRecords is the set of records containing the old date and time value, the vehicle identification value and the by-default load type of the vehicle.