ODX Tech-Day, Seoul. Diagnostic processes using ODX V

Transcription

1 ODX Tech-Day, Seoul Diagnostic processes using ODX V

2 Agenda 1. Motivation 3 2. ODX in Diagnostic Processes 8 3. ODX based reprogramming / configuration Summary 24 2

3 Motivation Diagnostics the challenging issues Consistent data supply ECU Specification Tester Parameterization ECU Software configuration Harmonized Data Exchange with Supplier with other OEMs Different diagnostic data sources Requirement database Legacy systems Existing ECUs 3

4 Motivation Process Steps Consistent Diagnostic Consistent data base diagnostic Data XML data OEM Supplier ECU Software implementation 4

5 Motivation Level of detail quality of your data A diagnostic tester The response may contain 1-3 response parameters: > State Window 1, State Window 2 and State Window 3 (optional) A protocol validation tool The response contains exactly 2 response parameters: > State Window 1 and State Window 2 > Possible states are: Open=1, Closed=0 A code generator The response contains exactly 2 response parameters: > State Window 1 and State Window 2 > Possible states are: Open=1, Closed=0 (other values are invalid) > The window state is reported by returning the value of an internal variable Level of Detail increases 5

6 Motivation Different stages, different requirements Data is dynamic Data is static Development Manufacturing After Sales 6

7 Agenda 1. Motivation 3 2. ODX in Diagnostic Processes 8 3. ODX based reprogramming / configuration Summary 24 7

8 ODX in Diagnostic Processes Many Diagnostic use cases Focus: One source many drains Single source for diagnostic data supply CANdela based diagnostic specification Data exchange with suppliers Data exchange with internal process partners Diagnostic Requirements management (PREEvision/OEM specific database) Tester parameterization ODX for MCD-3D Tester Proprietary tester parameterization ECU Software Configuration using Autosar DIAG-EXT

9 ODX in Diagnostic Processes Many Diagnostic use cases Diagnostic Requirements Definition WindowPosition (readable DID) SYS-EX: System Extract of System Description for one ECU (Format: ARXML) DIAG-EX: Diagnostic ECU Extract (Format: ARXML) Common Database PREE vision CSV AUTOSAR System Design PREE vision WindowPosition (scaling, access via SWC port WindowPos ) SYS-EX Diagnostic Communication Design CANdela Studio WindowPosition (assigned to ID 0x602) SYS-EX SWC references DIAG-EX CDD ODX Legacy AUTOSAR SWC Design (Diagnostic Interfaces) AUTOSAR BSW Configuration (Dcm, Dem) Diagnostic Validation Diagnostic Tester Legacy Tester DaVinci Developer DaVinci Configurator PRO CANoe.DiVa MCD-3D <Legacy> 9

10 ODX in Diagnostic Processes ODX for some exchanges (European OEM) Focus: ODX at specific interfaces CANdela based diagnostic specification Data exchange with suppliers Data exchange with internal process partners ODX based ECU specifications from specific process partners Tester parameterization ODX for MCD-3D Tester ODX in the near future Support for automated code generation using CANdesc Different level of data quality. 10

11 KWPlp Template ODX in Diagnostic Processes ODX for some exchanges (European OEM) OEM 3D Tester odx KWP/UDS Template Supplier.cdd CANdelaStudio.cdd CANdelaStudio.doc.odx.cdd CANdesc SW generation KWPlp ECU ODX Editor.odx ODX Editor OEM 2 (Cooperation) Supplier 11

12 ODX in Diagnostic Processes Database ODX via CANdelaStudio (HKMC) Focus OEM specific diagnostic database for ODX Generation of ODX ODX based diagnostic exchange Data exchange with suppliers Data exchange with internal process partners Tester parameterization Main focus (!) ODX for MCD-3D Tester Supplier support ECU Code Generation Diagnostic Validation ODX data supply 12

13 ODX in Diagnostic Processes Database ODX via CANdelaStudio (HKMC) HKMC DB Supplier *.c/*.h Generated ODX Authoring Guideline Geny Code generation DiVa ODXEditor Checker Rules Validation CDD CANdelaStudio Diagnostic Data Updated ODX OEM ODX Checker ODX OEM AddOn ODX 13

14 ODX in Diagnostic Processes 100% pure ODX OEM specific storage of diagnostics (database) Support out of the box using ODXStudio ECU perspective. ODX exchange with ALL process partners. Elaborated ODX AGL. Well defined development process. 14

15 ODX in Diagnostic Processes 100% pure ODX OEM Supplier <Legacy> DB ODX-D ODX-C/CS ODX of Legacy (ECU container) Authoring Guideline ODXStudio ECU Perspective ODX-D ODX-E Expert Views ODX-C/CS ODX (ECU container) Checker Rules OEM ODX Checker ODX ODX-D* ODX-E ODX-C/CS ODX-F ODX (ECU container) ODXStudio ECU Perspective Flash Data Config Data Data flow Dependency Document Data Tool 15

16 ODX in Diagnostic Processes No ODX Well established/proven diagnostic process Proven diagnostic database to store/specify general data Own data driven Tester format MDX Unified Diagnostic Services (UDS) Mass Data (DIDs, I/Os, Routines, DTCs) Supplier support ECU Code Generation Diagnostic Validation 16

17 ODX in Diagnostic Processes No ODX 17 Source: Presentation of Peter Geffers at Vector Congress :

18 Agenda 1. Motivation 3 2. ODX in Diagnostic Processes 8 3. ODX based reprogramming / configuration Summary 24 18

19 ODX based reprogramming / configuration ECU (re)programming Update ECU software using diagnostic communication Very OEM specific process! Flash bootloader Application verification (DIDs, CRC, ) Requirements: Ensure compatibility of software and ECU/vehicle configuration Collect application/bootloader related data Software and hardware version, Authorization, compliance to process definition Avoid future problems in production/service Efficient management of many different hardware-/software combinations Scope: Typically one ECU 19

20 ODX based reprogramming / configuration (Re)programming related data Supplier an OEM Development ODX Authoring Guideline Development Production Flash Tool ODX-F Flash Tool ODXStudio odx-f odx-f ODXStudio odx vehicle container Flash Tool vflash vflash Service Data flow Dependency Document Data Tool 20

21 ODX based reprogramming / configuration Variant coding Adjust ECU to vehicle specific environment Region, optional functions, characteristic curves Executed during vehicle production or in workshop after replacing an ECU Very OEM specific process Production process Repair instructions Motivation: Shipment of different vehicles having same hardware Avoid future problems in production/service Scope: Vehicle 21

22 ODX based reprogramming / configuration Variant coding related data an OEM ODX Authoring Guideline Development Production Config Tool odx-e ODXStudio odx vehicle container Config Tool Service Data flow Dependency Document Data Tool 22

23 Agenda 1. Motivation 3 2. ODX in Diagnostic Processes 8 3. ODX based reprogramming / configuration Summary 24 23

24 Summary Dynamic generation / static consumption Data is dynamic Data is static Development Manufacturing After Sales Author Generate Consume 24

25 Summary Many use cases benefit from high quality diagnostic data Code generation Diagnostic validation Generation instead of native editing of ODX! ODX is only one aspect of many topics! Legacy systems Taking over ECUs Diagnostic process muss support all aspects of the development 25

26 Your questions are welcome! Author: Hummel, Markus Vector Germany