Commission Delegated Regulation (EU) 2017/79 of 12 September 2016 establishing de... (32017R0079)
INHALT
Commission Delegated Regulation (EU) 2017/79 of 12 September 2016 establishing detailed technical requirements and test procedures for the EC type-approval of motor vehicles with respect to their 112-based eCall in-vehicles systems, of 112-based eCall in-vehicle separate technical units and components and supplementing and amending Regulation (EU) 2015/758 of the European Parliament and of the Council with regard to the exemptions and applicable standards (Text with EEA relevance. )
- COMMISSION DELEGATED REGULATION (EU) 2017/79
- of 12 September 2016
- establishing detailed technical requirements and test procedures for the EC type-approval of motor vehicles with respect to their 112-based eCall in-vehicles systems, of 112-based eCall in-vehicle separate technical units and components and supplementing and amending Regulation (EU) 2015/758 of the European Parliament and of the Council with regard to the exemptions and applicable standards
- (Text with EEA relevance)
- Article 1
- Subject matter
- Article 2
- Classes of vehicles exempted from the requirement to be equipped with a 112-based eCall in-vehicle system
- Article 3
- Multi-stage approval of special purpose vehicles
- Article 4
- Definitions
- Article 5
- Requirements and test procedures for EC type-approval of motor vehicles with regard to the installation of 112-based eCall in-vehicle systems
- Article 6
- Requirements and test procedures for EC type-approval of 112-based eCall in-vehicle system components
- Article 7
- Requirements and test procedures for EC type-approval of 112-based eCall in-vehicle STUs
- Article 8
- Obligations of the Member States
- Article 9
- Amendments to Regulation (EU) 2015/758
- Article 10
- Entry into force and application
- TABLE OF CONTENTS
- ANNEX I
- Technical requirements and procedures for testing the resistance of eCall in-vehicle systems to severe crashes (high-severity deceleration test)
- 1. Requirements
- 1.1. Performance requirements
- 2. Test procedure
- 2.1. Purpose of the high-severity deceleration test procedure
- 2.3. Deceleration/acceleration procedure
- 2.3.7. Description of the test pulse
- Figure
- Minimum and maximum curve of the test pulse (pulse corridor)
- 2.4. Verification procedure
- 2.5. Positioning test procedure
- 2.6. Antenna test procedure
- 2.7. Connection procedures
- 2.7.1. Simulated Mobile Network Procedure
- 2.7.2. Public Mobile Network Procedure
- 2.7.3. Wired Transmission Procedure
- 2.8. Verification procedures for components
- 2.8.2. Control module including its connectors and wire harness as described in point 2.2.4 of this Annex.
- 2.8.3. Mobile network antenna including its connectors and wire harness as described in point 2.2.4 of this Annex
- 2.8.4. Power supply (if not part of the control module) including its connectors and wire harness as described in point 2.2.4 of this Annex
- ANNEX II
- Full-scale impact test assessment
- 1. Requirements
- 1.1. Performance requirements
- 2. Test procedure
- 2.1. Purpose of the full-scale impact test procedure
- 2.3. Impact test procedure
- 2.4. Verification procedure
- 2.5. Positioning test procedure
- 2.6. Antenna test procedure
- 2.7. Connection procedures
- ANNEX III
- Crash resistance of audio equipment
- 1. Requirements
- 1.1. Performance requirements
- 2. Test procedure
- 2.1. Purpose of the audio equipment crash resistance test procedure
- 2.3. Overview of test procedure
- 2.4. Arrangement of testers
- 2.5. Test setup
- 2.6. Test call
- 2.6.2. Exchange of test messages
- 2.6.2.1. Receive direction
- 2.6.2.2. Send direction
- 2.7. Connection procedures
- Appendix
- Test sentences
- 3. Test sentence pairs
- 3.1. Dutch
- 3.2. English
- 3.3. Finnish
- 3.4. French
- 3.5. German
- 3.6. Italian
- 3.7. Polish
- 3.8. Spanish
- ANNEX IV
- Co-existence of third party services (TPS) with the 112-based eCall in-vehicle systems
- 1. Requirements
- 1.2. Performance requirements
- 1.3. Documentation requirements
- 2. Test procedure
- 2.1. Purpose of the TPS co-existence test procedure
- 2.5. Connection procedures
- ANNEX V
- Automatic triggering mechanism
- 1. Requirements
- 1.2. Documentation requirements
- ANNEX VI
- Technical requirements for compatibility of eCall in-vehicle systems with the positioning services provided by the Galileo and the EGNOS systems
- 1. Requirements
- 1.1. Compatibility requirements
- 1.2. Performance requirements
- 2. Test methods
- 2.1. Test conditions
- Figure 1
- Open sky definition
- 2.2. Test procedures
- 2.2.1. NMEA-0183 messages output test.
- Figure 2
- Diagram of test stand
- 2.2.2. Assessment of positioning accuracy in autonomous static mode.
- 2.2.3. Assessment of positioning accuracy in autonomous dynamic mode.
- 2.2.4. Movement in shadow areas, areas of intermittent reception of navigation signals and urban canyons.
- Figure 3
- Urban canyon definition
- 2.2.5. Cold start time to first fix test.
- 2.2.6. Test of re-acquisition time of tracking signals after block out of 60 seconds.
- 2.2.7. Test of GNSS receiver sensitivity in cold start mode, tracking mode, and re-acquisition scenario.
- Figure 4
- Diagram of path calibration
- Figure 5
- Arrangement for evaluation of GNSS module sensitivity
- ANNEX VII
- In-vehicle system self-test
- 1. Requirements
- 1.2. Performance requirements
- 1.3. Documentation requirements
- 2. Test procedure
- 2.1. Self-test function verification test
- 3. Modification of type of 112-based eCall in-vehicle system or STU
- ANNEX VIII
- Technical requirements and test procedures related to privacy and data protection
- PART I
- Procedure for verifying the lack of traceability of an eCall in-vehicle system or STU
- 1. Purpose
- 2. Requirements
- 3. Test procedure
- 4. Assessment
- PART II
- Procedure for verifying the length of time an eCall log file is stored by the eCall in-vehicle system or STU
- 1. Purpose
- 2. Requirements
- 3. Test conditions
- 4. Test Method
- 5. Assessment
- PART III
- Procedure for verifying the automatic and continuous removal of data in the internal memory of an eCall in-vehicle system or STU
- 1. Purpose
- 2. Requirements
- 3. Test conditions
- 4. Test Method
- 5. Assessment
- PART IV
- Procedure for verifying the non- exchange of personal data between an eCall in-vehicle system or STU and third party services systems
- 1. Purpose
- 2. Requirements
- 2.2. Performance requirements
- 3. Test procedure
- 3.4. Connection procedures
- ANNEX IX
- Classes of vehicles referred to in Article 2
Feedback