ANNEX IISupplementary provisions
ANNEX II Annex II to Delegated Regulation (EU) 2017/79 is amended as follows: (1) point 1.1.6. is replaced by the following: ‘1.1.6. Position determination: The eCall system shall be able to determine accurately the up-to-date vehicle location, including two recent vehicle locations before the generation of the data for the MSD.’; (2) in point 2.3.3., point (c) is replaced by the following: ‘(c) one of the connection procedures defined in point 2.7 of Annex I, as agreed between the technical service and the manufacturer, will be applied for any test eCall;’; (3) point 2.4 is replaced by the following: ‘2.4. Power-Supply Test procedure The test procedure described in points 2.4.1 to 2.4.6. shall apply where Annex X is applicable and any of the following conditions is met: (a) the eCall STU was not subject of the test laid down in Annex X, (b) the eCall STU was subject of the test laid down in Annex X but the back-up power supply in the vehicle is shared with other devices. 2.4.1. If the automatic eCall was terminated, trigger a manual test eCall. 2.4.2. Read out any text for at least 5 minutes at the PSAP test point. Alternatively, the test method referred to in point 2.6.2. of Annex III can be performed at this step if the duration of 5 minutes is not exceeded. 2.4.3. Clear down the eCall using the appropriate PSAP test point command (e.g. hang up). 2.4.4. Wait for 56 minutes after the call was ended. 2.4.5. Initiate a call from the PSAP test point to the eCall in-vehicle system. 2.4.6. If the call is automatically accepted, read out any text for at least 5 minutes at the PSAP test point, otherwise the test is finished.’; (4) point 2.7. is deleted; (5) point 3 is added: ‘3. Verification procedure 3.1. Verification of the Minimum Set of Data (MSD) 3.1.1. Verify each of the following items in at least one of the test eCalls: (a) Verify that an eCall was triggered automatically by the full-scale impact event. This shall be verified by a record of the PSAP test point showing that it received an eCall following the impact event and that the MSD control indicator was set to ‘automatically initiated eCall’. (b) Verify that the eCall status indicator indicated an eCall sequence following the automatic or manual trigger. This shall be verified by a record showing that an indication sequence was performed on all sensory channels specified in the manufacturer’s documentation (visual and/or audible). (c) Verify that an MSD was received by the PSAP test point. This shall be verified by a record of the PSAP test point showing that an MSD emitted from the vehicle following the automatic trigger was received and successfully decoded. (d) Verify that the MSD contained accurate vehicle-specific data. This shall be verified by a record of the dedicated PSAP test point showing that the information transmitted in the fields regarding vehicle type, vehicle identification number (VIN) and vehicle propulsion storage type does not deviate from the information specified in the type-approval application. (e) Verify that the MSD contained an accurate, up-to-date location. This shall be verified in accordance with the Positioning Test Procedure as defined in point 2.5 of Annex I by a test record showing that the deviation between IVS location and true location, d_IVS, is less than 150 metres and the confidence bit transmitted to the PSAP test point indicates ‘position can be trusted’. If no GNSS signals are available at the impact test location, the vehicle can be moved to an appropriate location before performing the test eCall. (f) Verify that the MSD contained the two recent locations before the generation of the data for the MSD. This shall be verified by a record of the PSAP test point showing that it received the ‘recentVehicleLocationN1’ and ‘recentVehicleLocationN2’. (g) Verify that the MSD contained an up-to-date timestamp. This shall be verified by a test record showing that the timestamp contained in the MSD received by the PSAP test point does not deviate from the exact recorded time of the trigger activation by more than 60 seconds. 3.2. If the automatic test eCall could not be performed successfully due to vehicle-external factors, it shall be permissible to verify the automatic trigger following the impact via the internal record transaction function of the in-vehicle system. This register shall be capable to store received trigger signals in non-volatile memory. The test engineer shall have access to the data stored in the in-vehicle system and shall verify that no record of automatic trigger signal is stored before the impact event and that a record of an automatic trigger signal is stored after the impact event. 3.3. If the test eCall was performed with the vehicle connected to an off-vehicle power supply (in cases where the impact test was carried out with the standard vehicle power supply not installed), verify that the on-board electrical system feeding the eCall in-vehicle system remained intact. This shall be verified by a record of a test engineer confirming a successful check of the integrity of the on-board electrical system including the dummy in-vehicle power source (visual inspection for mechanical damage to either the power source’s mounting bracket or its structure) and the connections via its terminals. 3.4. Verification of Power-Supply test 3.4.1. The requirement is determined to have been passed if the eCall in-vehicle system is capable to communicate for the required period, as specified in point 2 of Annex X. Otherwise, the test is determined to have been failed.’.