Study on the inclusion of ecall in the periodic roadworthiness testing of motor vehicles WP3 Definition of test scenarios MOVE/C2/2017/282

Size: px

Start display at page:

Download "Study on the inclusion of ecall in the periodic roadworthiness testing of motor vehicles WP3 Definition of test scenarios MOVE/C2/2017/282"

Cassandra Williams
5 years ago
Views:

1 Study on the inclusion of ecall in the periodic roadworthiness testing of motor vehicles WP3 Definition of test scenarios MOVE/C2/2017/282 Dietmar Bönninger, Central agency for PTI Brussels, June 8th 2018

2 ecall: TOP 1 TOP 2 TOP 3 TOP 4 Defects of the system and their causes Components and their defects 2.1 Overview components 2.2 Defect rate components Definition of test scenarios 3.1 State of the technical discussion 3.2 Test steps 3.3 Self-test 3.4 Detection of defects Summary 2

3 1 Defects of the system and their causes

4 ecall Reasons for defects external damage of components e.g. broken antenna degradation of components e.g. porous surround of speakers incorrect maintenance e.g. installation of an invalid speaker system manipulation e.g. usage of a GPS / GSM jammer, manipulation of the warning and checking device, encoding of ecall 4

5 2 Components and their defects

6 2.1 Overview components

7 Overview components Components and their defects (e.g.) GNSS receiver hardware defect in the GNSS receiver unit manipulation by shielding 7

8 Overview components Components and their defects (e.g.) GNSS antenna damage/broken antenna improper maintenance manipulation by shielding real location differs from the indicated location 8

9 Overview components Components and their defects (e.g.) Network access device (including SIM) insufficient transmitter and/or receiver performance internal hardware error SIM card defective/invalid/blocked 9

10 Overview components Components and their defects (e.g.) Mobile network antenna damage/defect in the antenna improper maintenance manipulation by shielding reception power affected by a mechanical defect no available GSM-signal 10

11 Overview components Components and their defects (e.g.) Electronic control unit manipulation/deactivation by coding Internal failure replacement with not permitted device v. 4.8 v

12 Overview components Components and their defects (e.g.) Microphone damage degradation due to hear or humidity interference with regard to directionality improper shielding of the wires (EMC) wrong orientation of the microphone directional characteristic of microphone and installation location not optimal anymore 12

13 Overview components Components and their defects (e.g.) Loudspeaker / emergency speaker damage/defect degradation of the membrane interference with regard to transmission unauthorised repair/replacement 13

14 Overview components Components and their defects (e.g.) Manual pushbutton Pushbutton mechanically defective or stuck 14

15 Overview components Components and their defects (e.g.) Battery & electrical power supply line disconnection short circuit to positive, to earth state of battery charge low battery capacity low 15

16 Overview components Components and their defects (e.g.) Warning & indicator device faulty bulb/lcd display malfunction of the control device 16

17 Overview components Components and their defects (e.g.) Crash detection system Excluded from the study other system in 2014/45/EU 17

18 2.2 Defect rate components

19 Defect rate components Overview Components GNSS receiver 0,25 % GNSS antenna 0,50 % Network access device (NAD) 0,50 % NAD antenna 0,50 % Electronic control unit 1,50 % Microphone 1,25 % Loudspeaker / Emergency speaker 1,00 % Manual pushbutton 0,25 % Battery & electrical power supply 0,25 % Warning and indicator device 0,25 % 19

20 3 Definition of test scenarios

21 3.1 State of the technical discussion

22 Test sceranios State of the technical discussion COM 2013/316 Proposal concerning type - approval requirements for the deployment of the ecall in - vehicle TRL/EC Report - Technical requirements and test procedures for the type approval + Regulation (EU) 2015/ Study on the inclusion of ecall in the periodic roadworthiness testing of motor vehicles EeIP TF PTI Final Report "Study on the Periodic Technical Inspection requirements for ecall equipped vehicles" 7th Meeting EeIP TF PTI - Two preferred scenarios (OBD & Test-Call via long dialing number) Delegated Regulation (EU) 2017/79 22

23 3.2 Test steps

24 Test scenarios Test steps Inspection criteria: 1 2 Inspection method: F fitment V visual C FP condition function/performance E electronic (using the electronic interface) 24

25 Test scenarios Test steps Fitment Visual 1 Inspection criteria: 2 Inspection method: F fitment V visual C FP condition function/performance E electronic (using the electronic interface) 25

26 Test steps F1/V System identification the identification of the ecall system by visual means for example, the existence of an ecall pushbutton Fitment Visual 1. Visual identification of components 26

27 Test steps F1/E System identification Fitment Electronic the identification of the ecall system via the electronic vehicle interface system equipped yes/no 2. ECU request of the fitment 1. START 3. ECU response of the fitment 4. Evaluation of response 27

28 Test steps F2/E Configuration testing Fitment Electronic configuration testing of the ecall electronic control via the electronic vehicle interface testing the software version and configuration (integrity) compared with the respective reference data 2. ECU request of the configuration 1. START 3. ECU response of the configuration 4. Comparison Nominative/Actualconfiguration 28

29 Test steps C1/V Condition testing Condition Visual based on visual components the condition is tested by means of a visual inspection of the accessible and visible components e.g. external antenna, pushbutton, emergency speaker, microphone 1. Visual system condition check 30

30 Test steps C2/V Condition testing Condition Visual based on warning control units the condition is tested by means of the visual inspection of the display of the warning and control units Displayed information is compared with the manufacturer s specifications 1. Visual check of Indicator lamp status 31

31 Test steps C2/E Condition testing Condition Electronic based on warning and control units condition of the ecall system based on warning and control units by electronic means is performed via the electronic vehicle interface (status: ok/nok) 2. Indicator lamp status request 1. START 3. Indicator lamp status response 4. Evaluation of response 2015 CITA Conference, 14-16th April 2015, Dubai, UAE Page 33 32

32 Test steps ecall PTI Condition test C3/E Condition testing Condition Electronic Electronic Condition inspection: based on stored trouble codes (DTC s) Electronic request of the trouble codes in the ECU condition of the ecall system based on stored trouble F-06 Mikrofon codes 1: Kurzschluss (DTCs) nach Masseby electronic means failure of the specific component can be displayed No. # Defect Description F-01 GPS-Antenne: Kurzschluss nach Masse F-02 GSM-Antenne: Unterbrechung F-03 GSM-Backup-Antenne: Kurzschluss nach Plus F-04 Interner Steuergerätefehler F-05 Kein Zugriff auf interne SIM-Karte F-07 Notruf-Lautsprecher: Kurzschluss nach Plus F-08 Notruf-Lautsprecher: Unterbrechung F-09 Notruf-Taster: Unterbrechung 2. Request of trouble codes 1. START 3. Response of trouble codes 4. Evaluation of response 2015 CITA Conference, 14-16th April 2015, Dubai, UAE Page 41 33

33 Test steps ecall PTI Function test FP1/E Checking the min. set of data Function / Performance Electronic MSD is requested from the ecall electronic control unit Electronic function testing: Read out the Minimum Set of Data entries of the MSD andare the check compared availabilitywith of mobile the vehicle data networks the stated vehicle position is matched to the current location 2. Request of MSD 1. START 3. Response of MSD 4. Plausibility check of MSD 2015 CITA Conference, 14-16th April 2015, Dubai, UAE Page 43 35

Test steps FP2/E Testing the voice functionality Function testing of audio components: Function / Performance testing Activation the microphone of the Voice and Prompt emergency Mode speaker by

34 Test steps FP2/E Testing the voice functionality Function testing of audio components: Function / Performance testing Activation the microphone of the Voice and Prompt emergency Mode speaker by Time-delayed echo test for subjective voice echo-test or evaluation triggering the loudspeakers and reading the signal level of the microphone Electronic approx. 2 sec CITA Conference, 14-16th April 2015, Dubai, UAE Page 3837

35 Test steps FP2/E Testing the voice functionality Function / Performance Electronic 38

36 Test steps FP3/E Testing the MCC Function / Performance Electronic Testing the mobile communication components reading out the availability of PLMNs via electronic vehicle interface periodic background scan for PLMNs required in [EN 16062]* no registration on a mobile communications network 2. NAD request of mobile networks 1. START 3. NAD response of mobile networks 4. Evaluation of response 2015 CITA Conference, 14-16th April 2015, Dubai, UAE Page 34 39

37 Test steps FP4/E Triggering a remote test call (1) Function / Performance Electronic test-mode via the scan tool switch to long-dialing service number test call and MSD is transmitted via a mobile connection to a server (PSAP simulation). received data are compared with the existing data from the vehicle and the location of the test audio check via test-message Anruf von IVS mit Langwahlnummer an Server 1 Einleitung und Zielstellung 2. Start/ quit test mode 1. START/ quit testing 2 Motivation 6. Retrieval and evaluation of test results (MSD and audio test) 3 Variantenbetrachtung 3. Establish call by ECU; submit MSD to server 4 Fazit/Ausblick 4. Send audio test message to ECU resp. speaker 5. Record audio test message via microphone and send back to server PSAP-Simulation 41

38 3.3 Development

39 Development test scenarios Scenario 0 Without-Case The Without-Case describes the situation whereby the ecall system is not tested within the scope of PTI. This means that defects in the system components cannot be detected. It thus becomes clear that the Without-Case would result in continuous degradation of the ecall system. 43

40 Development test scenarios Scenario 1 Testing via warning and indicator lamp Code Test step Method Time [s] F1/V System identification visual 2 F1/E System identification electronic 2 F2/E Configuration testing electronic 0 C1/V Condition testing on the basis of visual components visual 4 C2/V Condition testing on the basis of warning & control units visual 3 C2/E Condition testing on the basis of warning and control units electronic 0 C3/E Condition testing on the basis of stored trouble codes electronic 1,4 FP1/E Checking the minimum set of data electronic 1,4 FP2/E Testing the voice quality electronic 4,7 FP3/E Testing the mobile communications components electronic 0 FP4/E Execution of a remote test call electronic 55,7 sum 9 44

41 Development test scenarios Scenario 2 Testing via electronic vehicle interface level 2 Code Test step Method Execution time [s] F1/V System identification visual 2 F1/E System identification electronic 2 F2/E Configuration testing electronic 0 C1/V Condition testing on the basis of visual components visual 4 C2/V Condition testing on the basis of warning & control units visual 0 C2/E Condition testing on the basis of warning and control units electronic 0 C3/E Condition testing on the basis of stored trouble codes electronic 1,4 FP1/E Checking the minimum set of data electronic 1,4 FP2/E Testing the voice quality electronic 4,7 FP3/E Testing the mobile communications components electronic 0 FP4/E Execution of a remote test call electronic 55,7 sum 7,4 45

42 Development test scenarios Scenario 3 Testing via electronic vehicle interface level 3 Code Test step Method Execution time [s] F1/V System identification visual 2 F1/E System identification electronic 2 F2/E Configuration testing electronic 0 C1/V Condition testing on the basis of visual components visual 4 C2/V Condition testing on the basis of warning & control units visual 3 C2/E Condition testing on the basis of warning and control units electronic 0 C3/E Condition testing on the basis of stored trouble codes electronic 1,4 FP1/E Checking the minimum set of data electronic 1,4 FP2/E Testing the voice quality electronic 4,7 FP3/E Testing the mobile communications components electronic 0 FP4/E Execution of a remote test call electronic 55,7 sum 13,5 46

43 Development test scenarios Scenario 4 Testing via call level 3 Code Test step Method Execution time [s] F1/V System identification visual 2 F1/E System identification electronic 2 F2/E Configuration testing electronic 0 C1/V Condition testing on the basis of visual components visual 4 C2/V Condition testing on the basis of warning & control units visual 3 C2/E Condition testing on the basis of warning and control units electronic 0 C3/E Condition testing on the basis of stored trouble codes electronic 1,4 FP1/E Checking the minimum set of data electronic 1,4 FP2/E Testing the voice quality electronic 4,7 FP3/E Testing the mobile communications components electronic 0 FP4/E Execution of a remote test call electronic 55,7 sum 64,5 47

44 3.4 Self-test limitations

) not all possible failures of components are detectable with reasonable effort list of potential failures,

45 Self-test self-test function of ecall system can cover a variety of electrical failures (audio components not required!) not all possible failures of components are detectable with reasonable effort list of potential failures, which are not feasible to cover TRL report it is assumeable that the entire self-test can be simply deactivated using a generic scan tool reasons are, for example, the need of the vehicle owner for privacy 49

46 Self-test limitations (TRL-report) ecall components Self-test limitations (failure modes) GNSS receiver 1 GNSS antenna 2 Reduced performance/failure due to unintended manipulation (e.g. non-approved replacement part, installation faults) or mechanical degradation (e.g. corrosion of contacts) Failure due to deliberate manipulation (shielding of antenna or jamming of signals), e.g. based on concerns the vehicle could be tracked Network access device (NAD) 3 SIM invalid NAD antenna 4 Reduced performance/failure due to unintended manipulation (e.g. non-approved replacement part, installation faults) or mechanical degradation (e.g. corrosion of contacts) Failure due to deliberate manipulation (shielding of antenna or jamming of signals), e.g. based on concerns the vehicle could be tracked Electronic control unit 5 Microphone 6 Reduced performance/failure due to degradation (e.g. soiling, ageing, mechanical defects) Battery & electrical power supply Reduced performance/failure due to manipulation (e.g. non-approved replacement part, installation faults, covered by retrofit elements) Loudspeaker/ Emergency speaker 7 Reduced performance/failure due to degradation (e.g. soiling, ageing, mechanical defects) Reduced performance/failure due to manipulation (e.g. non-approved replacement part, installation faults, covered by retrofit elements) Manual pushbutton 8 Mechanical failure (e.g. button stuck) Connection failure, short circuit Battery & electrical power supply 9 Reduced state of capacity Warning and indicator device 10 Connection failure, short circuit Failure due to deliberate manipulation LED failure 50

50 3.5 Detection of defects

51 Detection of defects Detection rate Scenario ecall Components Without- Case Testing via warning and indicator lamp Testing via el. vehicle interface Level 2 Testing via el. vehicle interface Level 3 Testing via call GNSS receiver 1 o GNSS antenna 2 o Network access device (NAD) 3 o NAD antenna 4 o Electronic control unit 5 o Microphone 6 o Loudspeaker/ Emergency speaker 7 o Manual pushbutton 8 o Battery & electrical power supply 9 o Warning and indicator device 10 o 55

52 4 Summary

53 Summary defect rate of the components have been evaluated. Reasons: degradation / damage manipulation wrong maintanance different test scenarios have been analyzed to check the: fitment condition function self-test is limited and tell-tale not specified cost-benefit-analyses still to be done 57

org Dietmar Bönninger Department for development and policy

54 Central agency for PTI Fahrzeugsystemdaten GmbH Wintergartenstraße Dresden / Germany fsd.zentrale-stelle.org Dietmar Bönninger Department for development and policy issues phone mobile dietmar.boenninger@fsd-web.de 58

55 Backup microphone 59

56 Backup speakers 60

57 Backup self test 61

AECS REGULATION POST-CRASH CHECK WITH HMI METHOD

AECS REGULATION POST-CRASH CHECK WITH HMI METHOD 01 Context Context Homologation time to be consider for one new function Part I AECD (~4 weeks) Part II AECD installation (~2 days or more) OEM aim to build