www.kpit.

com

Diagnostic in Adaptive AUTOSAR

HPC Diagnostics

05th June 2019 Höhenkirchen, Germany

Dipl. Informatiker
Bernhard.Wagner@kpit.com, MBA

1 6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
 Short flyover
over
Adaptive Autosar
Once you're in the forest, all the trees look pretty much alike

2 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
What is the market driver for adaptive AUTOSAR
Game changer for AUTOSAR –
selected main drivers
Classic Adaptive
• Highly automated driving
• Car-2-X applications
• Internet of Things and cloud Based on OSEK an „C“
Based on POSIX PSE51 System
and C++ 14
services
• Increasing of data rates Execution of code directly from Applicication is loaded from
ROM persitent memory into RAM
• Electric Powertrain
Same address space for all Each applications has it own (virtual)
application (MPU for safety support) address space (MMU support)

Optimize for signal-based

Service-oriented communication
communication
What is the main impact of
Fixed task configuration and Support of multiple (dynamic)
adaptive Autosar for diagnostic? configuration scheduling strategies

Specification Specifaction and code

Static serialisation of PDUs Dynamic serialisation

Source: https://www.autosar.org/fileadmin/HOW_TO_JOIN/AUTOSAR_Introduction.pdf

3 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
AUTOSAR is constantly growing

Number of Partners Number of Products on the market

4 15 May 2019 © KPIT Technologies Limited All WG-Meeting 2019

Working Group Organization
Project Leader Team

Cross-standard Working Groups (FO, CP, AP)

WG-A WG-MT WG-SEC WG-SAF

Architecture Team Methodology and Templates Automotive Security Functional Safety

WG-AIF WG-IVC WG-V2X WG-DIA WG-RES WG-UCM

Application Interfaces In-Vehicle COM Vehicle to X Diagnostics Resources Update & Conf. Management

WG-TSY
Time Synchronization Autosar Diagnostics
Classic Platform Working Groups (CP) Adaptive Platform Working Groups (AP)

WG-CP-RTE WG-CP-MCBD WG-CP-VAL WG-AP-EMO WG-AP-DI WG-AP-ST

Runtime Environment Multicore BSW Distr. Validation Execution Man. & OS Demonstrator Integration System Tests

WG-CP-MCL WG-CP-LIB WG-AP-PER WG-AP-CCT WG-AP-CLD

MCAL and NVRAM Libraries Persistency Core Coding Team Cloud Services

Legend: Lead Working Group

Working Group

5 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
Release Plan
Oct 2018 Mar 2019 Nov 2019 Nov 2020
First Sync Release Stabilization Release Sync Release Sync Release

Classic R4.4.0 R19-11 R20-11

Platform
✓
R1.5.0 R1.5.1 R19-11 R20-11
Foundation
✓ ✓

Adaptive R18-10 R19-03 R19-11 R20-11

Platform
✓ ✓

Process Harmonization

Q4/18 Q1/19 Q2/19 Q3/19 Q4/19 Q1/20 Q2/20 Q3/20 Q4/20 Q1/21
✓ released planned, content under evaluation

▪ Continue yearly sync release in November

▪ Additional stabilization releases possible
6 15 May 2019 © KPIT Technologies Limited All WG-Meeting 2019
Planned concepts in the next two years

• 27 Concepts are Classic Platform Adaptive P. & Classic P. Adaptive Platform

May (9 concepts) (7 concepts) (11 concepts)
planned for R19-11
and R20-11 Jun Jul Aug Sep Oct Nov

• Current status Ethernet Wake-up on Security Extensions

Socket API
Setup
Data Line Harmonized
MS0 VNSM IPSec Protocol V2X Support

HPC
MS1 BSW Distribution DoIP Extension Adaptive MCD
MS2 none
Signal Service
Firmware over the Air Integration of IAM
MS3 none Translation
Meta data for
MS4 none VFB++ Crypto API
application
HealthMonitoring Unified Timing and Recovery action via
• Concepts scheduled Harmonization CP Tracing approach application
for R20-11 are NV Data Handling Mode dependent
RS Safety
Enhancements configuration
marked with blue font
10-Base-T1S PHM Daisy Chaining

Variant Handling 15 May 2019 7 UCM Master HPC

Service versioning
Potential relevant ara::com
for Diagnostics AD Sensor Interfaces

7 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
What is Adaptive AUTOSAR?

▪ Future-proof basis for automotive ECUs

▪ Key advantage: to develop ECU
applications independently of one
another
▪ Standardization of the runtime for
Adaptive Applications (ARA)
-> main focus on functional cluster for
(virtual) machines
▪ Standardization by AUTOSAR
Consortium (almost every OEM)

8 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
 D-Server
in Adaptive Autosar

9 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
Service-Oriented Communication (SoC)

▪ The AUTOSAR Adaptive

Service Service Service
provider
architecture organizes the
Registry request
software as functional cluster
offer These clusters offer common
functionality as services to the
find applications
▪ In comparison to the AUTOSAR
Classic Platform the Runtime

t
calc
Environment for the Adaptive
Platform dynamically links
services and clients during
runtime

Source: https://www.autosar.org/fileadmin/user_upload/standards/adaptive/17-10/AUTOSAR_SWS_CommunicationManagement.pdf

10 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
Diagnostics Management(DM) in Adaptive AUTOSAR 19/03
▪ The Adaptive AUTOSAR platform can be
extended with new software packages without
re-flashing the entire ECU
▪ The individual software packages are described
by Software Cluster
▪ To support the current approach of diagnostic
management (like software updates), each
SoftwareCluster has its own Diagnostic Address
▪ Diagnostic Management is intended to support
an own diagnostic server instance per installed
Software Cluster
▪ The Diagnostic Management uses its own
serializer ARA::DIA, similar to ARA::COM
This serializer and the DM parts can be generated Business Logic

MCD-3 D Server OTX Sequences

Ethernet D-PDU API
ODX-Data

11 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
DOIP Communication with each SoftwareCluster
External Tester using DOIP
SoftwareCluster(SWC) have their
Diagnostic Tester FL FR RL RR own Diagnostic Adresses.
Business OTX
Logic Sequences
FL- DCM FR- FL- DCM FR-
MCD-3 D
App #1 App App #2 App
Server
ODX

ODX

D-PDU API SWC#1 SWC#2

SWC#2 SWC#1
DOIP

External and internal Tester using DOIP (planned for Nov 2019)
Diagnostic Tester FL FR RL RR
Business OTX
Logic Sequences FL- DCM FR- FL- DCM FR- Diag Diagnostic
MCD-3 D
App #1 App

ODX

OTX
Server App #2 App Tester
ODX

ODX

D-PDU API SWC#1 SWC#2 SWC#2 SWC#3 SWC#1 AUTOSAR

SWC#2 SWC#1

DOIP
Tier 1 / OEM

12 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
 MC-Server

13 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
MC-Use Cases
A2L-Editor
A2L
MC

3rd-Party

OEM XIL
Automation
FL FR RL RR Applikation

XIL-Interface (C#)

FL- MC-Server FR- FL- MC-Server FR- XIL to iLinkRt

App #1 App App #2 App (provided by ASAM)

SWC#1 SWC#2

SomeIP
-> Data data acquisition (DAQ)
iLinkRT
<- Command Channel (CMD)
over UDP

14 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
 Possible Offboard work packages

15 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
Vehicle Information Table - > Physical Link (pre adaptive)
▪ The Vehicle Info-Spec includes the
static routing information for a given
vehicle and the physical links
▪ A physical link is a Physical Vehicle
Link connected to a Physical Interface
Link, so it is the connection from the
interface of the Diagnostic system to
the ECU in the vehicle

No Physical Link
exists in Adaptive
AUTOSAR

16 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
Service-Oriented Communication (SoC)
FL Vehicle Info Spec. from ODX is
Dcm
now a vehicle specific registry. CAM
ECU #1 FR The physical vehicle link will no
Dcm longer be defined at data
definition time, instead it needs CAM
to be generated at runtime.
RL
Dcm HMI
ECU #2
DCM
HMI
ADAS

RR
Dcm CAM
ECU #3 ADAS
Dcm
CAM

17 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
Service-Oriented Communication (SoC) - Diagnostic

Business Logic

FL FR RL HMI RR ADAS MCD-3 D Server OTX Sequences

Data for
D-PDU API LL DB ECU ECU-Code
FL CAM #1#FL

DEXT
Dcm Dcm Dcm Dcm Dcm Dcm
VIN FR CAM #1#FR
RL CAM #2#RL

ECU #1 ECU #2 ECU #3 VIT-Registry

DEXT
HMI HMI #2#HMI
RR CAM #3#RR
DEXT

DEXT
DEXT

DEXT
DEXT

DEXT

DEXT
ADAS ADAS #3#ADAS

Some IP VIN

Adresss selected with VIT-Registry ISO 13400-2 (DoIP)

SoC: How this works
❶ I need CAM feedback from FL and RL 1) Advice
❷ ECU1 provides CAM feedback from FL 2) Offer
3) Subscribe
❷ ECU2 provides CAM feedback from RL
4) Handshake
❸ Request CAM feedback from FL from ECU1 5) Subscribe
❹ ECU1 sends CAM feedback from FL
6) Handshake
❻ ECU2 sends CAM feedback from RL ❺ Request CAM feedback from RL from ECU2

18 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.
 Do we need two Standardization
Organizations to take care of
Onboard-Diagnostics?

19 6/4/2019 © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.