V1.0 | 2016-09-12

The Standard in Practice

AUTOSAR Diagnostic Extract

2

u Diagnostic Processes in Place

AUTOSAR DEXT Introduction

Possibilities with DEXT in Diagnostic Tools

Diagnostic Processes with DEXT in Practice and Beyond

Agenda

3

Diagnostic Requirements

Diagnostic Processes in Place

Diagnostics

OEM

TIER1

??

Others

Legislation

After Sales

Production

4

Different Diagnostic Requirement Workflows in Place

Diagnostic Processes in Place

?

?

?

u No common authoring format

u Various OEM specific exchange formats

u Different tooling

u As many workflows in place as there are OEMs and TIER1

u For diagnostic testers the ODX format is established as exchange format

We need a diagnostic exchange format

OEM driven

TIER1 driven

?

5

But ECUC is no exchange format

u ECUC is designed to be

u input for code generator

u extensible for vendor-specific extensions

u ECUC has incompatible changes between AUTOSAR versions

u Tooling cannot be adapted each time.

u In reality the used format is a mixture between many AUTOSAR versions

ECUC to Exchange Diagnostic Data

Diagnostic Processes in Place

ECUC

OEM

TIER1

6

Established Vector Diagnostic Workflow

Diagnostic Processes in Place

ECU Extract of System Description provided by OEM

Communication input files provided by OEM.

OEM specific pre-configuration files provided by Vector

Other AUTOSAR tools

.arxml DaVinci Developer

PREEvision

DaVinci Configurator Pro

Software Component Description Files

Contain software component information

Header and Code Files

u BSW module configuration

u RTE u SWC

.c

.h

Other AUTOSAR tools

ECU Configuration Description

Vector Tool

3rd Party tool

CANdelaStudio

Diagnostic Data File .cdd

.odx

.arxml .arxml .arxml

ECUC .arxml

.arxml .arxml .arxml

BASE-ECUC

.arxml

.arxml

DBC FIBEX LDF

7

Diagnostic Processes in Place

u AUTOSAR DEXT Introduction

Possibilities with DEXT in Diagnostic Tools

Diagnostic Processes with DEXT in Practice and Beyond

Agenda

8

u Diagnostic Services [76 pages]

u How to describe the configuration of the diagnostic services of AUTOSAR

u How to map diagnostic services to SWC or BSW ports

u Diagnostic Event Handling [45 pages]

u How to describe the diagnostic events, DTCs, extended data records, snapshot records

u How to map event related data and function calls to SWC or BSW ports

u Upstream Mapping [317 pages]

u How to derive ECUC from the DEXT content

What the Document Describes

AUTOSAR DEXT Introduction

u Use Cases [ 5 pages]

u What’s the goal: DCM and DEM configuration

u Conceptual Background [2 pages]

u Why not using ECUC?

u Common Meta Model Elements [33 pages]

u How to achieve “decentralized configuration”

9

u Diagnostic representation on network

u For diagnostics the DEXT is like system extract for communication

DEXT and System Extract

AUTOSAR DEXT Introduction

AUTOSAR

Network

ServiceInterface

u SYS-EX: PDU, Signal

u DEXT: SID, DID, RID, DTC

SYS-EX

DEXT

10

AUTOSAR DEXT

u Can be incomplete as all AUTOSAR .arxml files

u Allows to deliver fragments to the diagnostic tool chain

Valid Fragmented Contribution

AUTOSAR DEXT Introduction

ODX Comparison to ODX

u ODX schema requires complete files

.arxml .arxml

.arxml .arxml

.arxml

11

u New AUTOSAR Standard

u Detailed concept validations, prototypes in practice

u Risk of missing features

u “AUTOSAR-aware” OEMs

u Will enforce standard modification for new features

u Avoiding SDGs while standard is evolving

u OEM specific schema as intermediate solution (“OEM DEXT”)

u In upcoming release 4.3.0

u Integrated feedback from previous releases

u OBD, J1939, Fim

u Environmental Conditions

Stability of DEXT

AUTOSAR DEXT Introduction

12

Diagnostic Processes in Place

AUTOSAR DEXT Introduction

u Possibilities with DEXT in Diagnostic Tools

Diagnostic Processes with DEXT in Practice and Beyond

Agenda

13

Base ECUC Configuration without DEXT

Possibilities with DEXT in Diagnostic Tools

DaVinci

Configurator Pro

ECUC Configuration Description

.arxml

Code G

enera

tor

Fro

ntE

nd

Authoring

Proprietary File

Import data processors

Proprietary DataBase

u Missing standardized authoring format

u Exchange formats with different quality

u Dependency to individual tooling

u Manual adding of individual configurations

The OEM specific workflow creates an OEM specific diagnostic solution

Header and Code Files

uDCM and DEM uOEM specific

extensions

.c

OEM

.h

OEM

AUTOSAR

14

Base ECUC Configuration with DEXT

Possibilities with DEXT in Diagnostic Tools

AUTOSAR DEXT

Standardized exchange format

Code G

enera

tor

Fro

ntE

nd

Authoring AUTOSAR

DaVinci

Configurator Pro

ECUC Configuration Description

.arxml

DEXT OEM?

Header and Code Files

uDCM and DEM uOEM specific

extensions

.c

OEM?

.h

OEM?

15

Input Data Update

Possibilities with DEXT in Diagnostic Tools

u Updating input data is common in diagnostic processes

u Updating existing ECUC configurations is challenging

u DEXT format facilitates the update procedure

u Vector DaVinci Configurator Pro provides a smart update functionality, for DEXT and other input data

New Requirement

Development Integration

New Function

Legislation Update

Feature Increase

DEXT DaVinci

Configurator Pro

Header and Code Files

uDCM and DEM

ECUC Configuration Description

.arxml

.c

.h

16

ECUC

u Network representation

u Application Pre-Mapping

u OEM specific behavior

u 100% derived in best case

u Integrator completes project configuration

u DEXT modelling on higher SWC level

u More frontloading

u Less integrator responsibility

Reducing Integrator Responsibility

Possibilities with DEXT in Diagnostic Tools

Integrator

DEXT

17

Diagnostic Processes in Place

AUTOSAR DEXT Introduction

Possibilities with DEXT in Diagnostic Tools

u Diagnostic Processes with DEXT in Practice and Beyond

Agenda

18

DEXT as Connector to EE Development

Diagnostic Processes with DEXT in Practice and Beyond

refe

rences

PREEvision

CANdela Studio

System Design

Diagnostic Design

DEXT

SYS-EX

19 © 2016. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 | 2016-09-12

Author: Wigbert Knape Vector Germany

For more information about Vector and our products please visit www.vector.com