AUTOSAR Diagnostic Extract

Transcription

1 AUTOSAR Diagnostic Extract The Standard in Practice V

2 Agenda Diagnostic Processes in Place AUTOSAR DEXT Introdction Possibilities with DEXT in Diagnostic Tools Diagnostic Processes with DEXT in Practice and Beyond 2

3 Diagnostic Processes in Place Diagnostic Reqirements Prodction OEM After Sales Diagnostics Legislation?? Others TIER1 3

4 Diagnostic Processes in Place Different Diagnostic Reqirement Workflows in Place???? No common athoring format Varios OEM specific exchange formats Different tooling As many workflows in place as there are OEMs and TIER1 For diagnostic testers the ODX format is established as exchange format We need a diagnostic exchange format OEM driven TIER1 driven 4

5 Diagnostic Processes in Place ECUC to Exchange Diagnostic Data Bt ECUC is no exchange format ECUC is designed to be inpt for code generator extensible for vendor-specific extensions OEM ECUC has incompatible changes between AUTOSAR versions Tooling cannot be adapted each time. TIER1 In reality the sed format is a mixtre between many AUTOSAR versions ECUC 5

6 Diagnostic Processes in Place Established Vector Diagnostic Workflow PREEvision Other AUTOSAR tools.arxml ECU Extract of System Description provided by OEM DaVinci Developer DBC FIBEX LDF.arxml.arxml Commnication inpt files provided by OEM. OEM specific preconfigration files provided by Vector.arxml.arxml.arxml Software Component Description Files Contain software component information.c Header and Code Files.arxml ECUC BASE-ECUC.arxml DaVinci Configrator Pro.h BSW modle configration RTE SWC CANdelaStdio.arxml ECU Configration Description Other AUTOSAR tools.cdd.odx Diagnostic Data File Vector Tool 3rd Party tool 6

7 Agenda Diagnostic Processes in Place AUTOSAR DEXT Introdction Possibilities with DEXT in Diagnostic Tools Diagnostic Processes with DEXT in Practice and Beyond 7

8 AUTOSAR DEXT Introdction What the Docment Describes Use Cases [ 5 pages] Diagnostic Services [76 pages] How to describe the configration of the diagnostic services of AUTOSAR How to map diagnostic services to SWC or BSW ports Diagnostic Event Handling [45 pages] How to describe the diagnostic events, DTCs, extended data records, snapshot records How to map event related data and fnction calls to SWC or BSW ports Upstream Mapping [317 pages] What s the goal: DCM and DEM configration Conceptal Backgrond [2 pages] Why not sing ECUC? Common Meta Model Elements [33 pages] How to achieve decentralized configration How to derive ECUC from the DEXT content 8

9 AUTOSAR DEXT Introdction DEXT and System Extract Diagnostic representation on network For diagnostics the DEXT is like system extract for commnication SYS- EX ServiceInterface AUTOSAR DEXT Network SYS-EX: PDU, Signal DEXT: SID, DID, RID, DTC 9

10 AUTOSAR DEXT Introdction Valid Fragmented Contribtion AUTOSAR DEXT Can be incomplete as all AUTOSAR.arxml files Allows to deliver fragments to the diagnostic tool chain.arxml.arxml.arxml.arxml.arxml Comparison to ODX ODX schema reqires complete files ODX 10

11 AUTOSAR DEXT Introdction Stability of DEXT New AUTOSAR Standard Detailed concept validations, prototypes in practice Risk of missing featres AUTOSAR-aware OEMs Will enforce standard modification for new featres Avoiding SDGs while standard is evolving OEM specific schema as intermediate soltion ( OEM DEXT ) In pcoming release Integrated feedback from previos releases OBD, J1939, Fim Environmental Conditions 11

12 Agenda Diagnostic Processes in Place AUTOSAR DEXT Introdction Possibilities with DEXT in Diagnostic Tools Diagnostic Processes with DEXT in Practice and Beyond 12

13 Code Generator FrontEnd Possibilities with DEXT in Diagnostic Tools Base ECUC Configration withot DEXT Athoring AUTOSAR Proprietary File Import data processors DaVinci Configrator Pro.c OEM.h OEM Header and Code Files DCM and DEM OEM specific extensions Proprietary DataBase.arxml ECUC Configration Description Missing standardized athoring format Exchange formats with different qality Dependency to individal tooling Manal adding of individal configrations The OEM specific workflow creates an OEM specific diagnostic soltion 13

14 Code Generator FrontEnd Possibilities with DEXT in Diagnostic Tools Base ECUC Configration with DEXT Athoring AUTOSAR DEXT OEM? AUTOSAR DEXT DaVinci Configrator Pro.c OEM?.h OEM? Header and Code Files DCM and DEM OEM specific extensions.arxml ECUC Configration Description Standardized exchange format 14

15 Possibilities with DEXT in Diagnostic Tools Inpt Data Update Featre Increase New Reqirement Legislation Update DEXT Development Integration DaVinci Configrator Pro.c.h Header and Code Files DCM and DEM New Fnction.arxml ECUC Configration Description Updating inpt data is common in diagnostic processes Updating existing ECUC configrations is challenging DEXT format facilitates the pdate procedre Vector DaVinci Configrator Pro provides a smart pdate fnctionality, for DEXT and other inpt data 15

16 Possibilities with DEXT in Diagnostic Tools Redcing Integrator Responsibility DEXT modelling on higher SWC level More frontloading Less integrator responsibility Network representation Application Pre-Mapping OEM specific behavior DEXT 100% derived in best case Integrator completes project configration ECUC Integrator 16

17 Agenda Diagnostic Processes in Place AUTOSAR DEXT Introdction Possibilities with DEXT in Diagnostic Tools Diagnostic Processes with DEXT in Practice and Beyond 17

18 references Diagnostic Processes with DEXT in Practice and Beyond DEXT as Connector to EE Development CANdela Stdio DEXT Diagnostic Design PREEvision SYS- EX System Design 18

19 For more information abot Vector and or prodcts please visit Athor: Wigbert Knape Vector Germany Vector Informatik GmbH. All rights reserved. Any distribtion or copying is sbject to prior written approval by Vector. V