AUTOSAR Diagnostic Extract

Transcription

1 AUTOSAR Diagnostic Extract The Standard in Practice V

2 Agenda Diagnostic Processes in Place AUTOSAR DEXT Introdction Designed for ECU development Enhancement of E/E Workflow Conclsion 2

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

4 Diagnostic Processes in Place Standardized Diagnostic Formats Prodction OEM After Sales ODX-D Diagnostics?? Others TIER1 4

5 Diagnostic Processes in Place Necessary inpt for ECU development OEM standards General common details mostly covered by AUTOSAR ODX-D Service instances, DTCs,.. TIER1 Project specification Frther details mostly non-formal 5

6 Agenda Diagnostic Processes in Place AUTOSAR DEXT Introdction Designed for ECU development Enhancement of E/E Workflow Conclsion 6

7 AUTOSAR DEXT Introdction DEXT - AUTOSAR exchange format for diagnostics Transfer of diagnostic demands of the OEM-specific configration process to their tier-1 sppliers Covers AUTOSAR capabilities Covers different diagnostic protocols UDS OBD / WWH-OBD SAE J1939 Covers FIM (Fnction Inhibition) aspects Very stable since introdction with AUTOSAR Release 4.2 7

8 AUTOSAR DEXT Introdction Overview: Diagnostic Extract Template Diagnostic Contribtion Set (central entry point) Diagnostic Services Diagnostic services and service instances Definition of access permission Falt Memory Definition of events (monitor) DTCs ExtendedData Records, Snapshot Records Event mappings (to DTC, operation cycle, 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 Agenda Diagnostic Processes in Place AUTOSAR DEXT Introdction Designed for ECU development Enhancement of E/E Workflow Conclsion 10

11 Designed for ECU development Falt memory Monitor -> DTC mapping Deboncing conditions Aging threshold Operation Cycles Snapshot-/ExtendedData storage conditions Enable-/Storage conditions Indicator 11

12 Designed for ECU development Diagnostic Service details EcReset Response-Pending before reset Response after boot Shtdown time of EnableRapidPowerShtdown Secrity Access AttemptConter Timings ReadDataByPeriodicIdentifier Transmission rate vale (slow medim fast) Maximm schedlable DIDs DynDID Max nmber of DIDs in DDDIDs 12

13 Designed for ECU development Environmental conditions checks Formalized condition which is evalated dring rntime by looking at "environmental states Similar to Session-Secrity check Nested boolean expression Can be added to any diagnostic object Atomatic test generation with CANoe.Diva possible 13

14 Designed for ECU development Decentralized development (work split) Can be incomplete as all AUTOSAR.arxml files Allows to deliver fragments to the diagnostic tool chain Fix defined DIDs inclding scaling SWC OEM A Tier 1 Creating proxies to adapt internal representations DIDs demands only withot scaling OEM B Tier 1 Creating proxies to adapt internal representations 14

15 Agenda Diagnostic Processes in Place AUTOSAR DEXT Introdction Designed for ECU development Enhancement of E/E Workflow Conclsion 15

16 Enhancement of E/E Workflow AUTOSAR Workflow SW fnctionality of the vehicle is defined as a system of SWCs... SWC1 Virtal Fnction Bs VFB SWC2 SWC3 ECU1 SWC1 SWC2 ECU2 SWC3 and mapped to ECUs Software Component Description* System Description* An extract is created for each ECU... ECU1 SWC1 SWC2 The ECU is configred in detail SWC1 SWC2 Basic Software (BSW) RTE 16 Extract of System Description* ECU Configration Description (ECUC)* *

17 Enhancement of E/E Workflow Diagnostic Service Software Mapping Using DEXT Diagnostic Service Software Mapping to connect with ports SWC RTE Dcm_SWC 17

18 Enhancement of E/E Workflow Model-based development workflow (example) OEM is able to pre-define port mappings Which port delivers the VIN for DID F190 Atomatic configration of Basic-Software possible More accracy and less effort on integration (Tier1) SWC OEM Tier 1 18

19 Enhancement of E/E Workflow Diagnostic Workflow Diagnostic Reqirements Definition Reqired: Readable DID WindowPos PREE vision AUTOSAR System Design SWC port WindowPos with service needs and scaling Mapping CSV Reqirements Import Diagnostic Specification SWC Sync CANdela Stdio DID WindowPos assigned to ID 0x602, accessible only in extended session, visible for development SYS-EX SWC references DIAG-EX CDD ODX AUTOSAR SWC Design (Diagnostic Interfaces) AUTOSAR BSW Configration (Dcm, Dem) Diagnostic Validation Diagnostic Tester Parametrization DaVinci Developer or PREEvision DaVinci Configrator PRO CANoe.DiVa Indigo 19 SYS-EX: System Extract of System Description for one ECU (Format: ARXML) DIAG-EX: Diagnostic ECU Extract (Format: ARXML)

20 Agenda Diagnostic Processes in Place AUTOSAR DEXT Introdction Designed for ECU development Enhancement of E/E Workflow Conclsion 20

21 Conclsion Conclsion DEXT completes diagnostic workflows DEXT focses on ECU development DEXT is limited to capabilities of AUTOSAR For more information: Contact yor local sales agent for > Evalation Bndle, Prototype, Training 21

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