Diagnostic in Adaptive AUTOSAR
- 1. www.kpit.com 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. Diagnostic in Adaptive AUTOSAR HPC Diagnostics
- 2. © KPIT Technologies Limited6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.2 Short flyover over Adaptive Autosar Once you're in the forest, all the trees look pretty much alike
- 3. © KPIT Technologies Limited What is the market driver for adaptive AUTOSAR Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.3 Game changer for AUTOSAR – selected main drivers • Highly automated driving • Car-2-X applications • Internet of Things and cloud services • Increasing of data rates • Electric Powertrain Source: https://www.autosar.org/fileadmin/HOW_TO_JOIN/AUTOSAR_Introduction.pdf What is the main impact of adaptive Autosar for diagnostic? 6/4/2019 Classic Based on OSEK an „C“ Execution of code directly from ROM Same address space for all application (MPU for safety support) Optimize for signal-based communication Fixed task configuration and configuration Specification Static serialisation of PDUs Adaptive Based on POSIX PSE51 System and C++ 14 Applicication is loaded from persitent memory into RAM Each applications has it own (virtual) address space (MMU support) Service-oriented communication Support of multiple (dynamic) scheduling strategies Specifaction and code Dynamic serialisation
- 4. © KPIT Technologies Limited AUTOSAR is constantly growing 15 May 2019 All WG-Meeting 20194 Number of Partners Number of Products on the market
- 5. © KPIT Technologies Limited Working Group Organization 6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.5 WG-AIF Application Interfaces WG-A Architecture Team WG-CP-RTE Runtime Environment WG-AP-DI Demonstrator Integration WG-AP-ST System Tests WG-CP-VAL Validation Cross-standard Working Groups (FO, CP, AP) Lead Working Group Working Group Legend: WG-AP-EMO Execution Man. & OS WG-RES Resources WG-DIA Diagnostics WG-IVC In-Vehicle COM Classic Platform Working Groups (CP) Adaptive Platform Working Groups (AP) WG-UCM Update & Conf. Management WG-V2X Vehicle to X WG-CP-MCL MCAL and NVRAM Project Leader Team WG-AP-PER Persistency WG-CP-LIB Libraries WG-CP-MCBD Multicore BSW Distr. WG-MT Methodology and Templates WG-SEC Automotive Security WG-SAF Functional Safety WG-AP-CCT Core Coding Team WG-AP-CLD Cloud Services WG-TSY Time Synchronization Autosar Diagnostics
- 6. © KPIT Technologies Limited Release Plan 15 May 2019 All WG-Meeting 20196 ✓ released planned, content under evaluation Q4/18 Q3/19Q1/19 Q2/19 Q4/19 R4.4.0Classic Platform Foundation R1.5.1 R19-11 R1.5.0 R19-11 Q3/20Q1/20 Q2/20 Q4/20 Q1/21 Adaptive Platform R19-03R18-10 R19-11 Oct 2018 First Sync Release Mar 2019 Stabilization Release Nov 2019 Sync Release R20-11 R20-11 R20-11 Nov 2020 Sync Release ✓ ✓ ✓ ✓ ✓ Process Harmonization ▪ Continue yearly sync release in November ▪ Additional stabilization releases possible
- 7. © KPIT Technologies Limited Planned concepts in the next two years 6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.7 May Jun Jul Aug Sep Oct Nov 7 Classic Platform (9 concepts) Ethernet Wake-up on Data Line VNSM BSW Distribution Firmware over the Air Meta data for application HealthMonitoring Harmonization CP NV Data Handling Enhancements 10-Base-T1S Variant Handling Adaptive P. & Classic P. (7 concepts) Security Extensions Harmonized IPSec Protocol DoIP Extension Signal Service Translation VFB++ Unified Timing and Tracing approach RS Safety Adaptive Platform (11 concepts) Socket API V2X Support Adaptive MCD Integration of IAM Crypto API Recovery action via application Mode dependent configuration PHM Daisy Chaining UCM Master Service versioning ara::com AD Sensor Interfaces • 27 Concepts are planned for R19-11 and R20-11 • Current status • Concepts scheduled for R20-11 are marked with blue font Setup MS0 MS1 MS2 none MS3 none MS4 none 15 May 2019 HPC Potential relevant for Diagnostics HPC
- 8. © KPIT Technologies Limited What is Adaptive AUTOSAR? 6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.8 ▪ 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)
- 9. © KPIT Technologies Limited6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.9 D-Server in Adaptive Autosar
- 10. © KPIT Technologies Limited Service-Oriented Communication (SoC) 6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.10 Source: https://www.autosar.org/fileadmin/user_upload/standards/adaptive/17-10/AUTOSAR_SWS_CommunicationManagement.pdf ▪ The AUTOSAR Adaptive architecture organizes the software as functional cluster These clusters offer common functionality as services to the applications ▪ In comparison to the AUTOSAR Classic Platform the Runtime Environment for the Adaptive Platform dynamically links services and clients during runtime Service provider Service request offer find calc t Service Registry
- 11. © KPIT Technologies Limited Diagnostics Management(DM) in Adaptive AUTOSAR 19/03 6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.11 ▪ 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 Ethernet OTX Sequences Business Logic MCD-3 D Server D-PDU API ODX-Data
- 12. © KPIT Technologies Limited DOIP Communication with each SoftwareCluster 6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.12 FL FR SWC#1 FL- App DCM #1 FR- App RL RR SWC#2 FL- App DCM #2 FR- App DOIP SoftwareCluster(SWC) have their own Diagnostic Adresses. OTX Sequences Business Logic MCD-3 D Server D-PDU API SWC#2 Diagnostic Tester SWC#1 ODX ODX FL FR SWC#1 FL- App DCM #1 FR- App RL RR SWC#2 FL- App DCM #2 FR- App DOIP OTX Sequences Business Logic MCD-3 D Server D-PDU API SWC#2 Diagnostic Tester SWC#1 ODX ODX SWC#3 Diag Tester SWC#1 OTX SWC#2 ODX External Tester using DOIP External and internal Tester using DOIP (planned for Nov 2019) Diagnostic AUTOSAR Tier 1 / OEM
- 13. © KPIT Technologies Limited6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.13 MC-Server
- 14. © KPIT Technologies Limited MC-Use Cases 6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.14 FL FR SWC#1 FL- App MC-Server #1 FR- App SomeIP iLinkRT over UDP MC 3rd-Party OEM RL RR SWC#2 FL- App MC-Server #2 FR- App <- Command Channel (CMD) -> Data data acquisition (DAQ) A2L-Editor A2L XIL Automation Applikation XIL to iLinkRt (provided by ASAM) XIL-Interface (C#)
- 15. © KPIT Technologies Limited6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.15 Possible Offboard work packages
- 16. © KPIT Technologies Limited Vehicle Information Table - > Physical Link (pre adaptive) 6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.16 ▪ 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
- 17. © KPIT Technologies Limited RR ADAS Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.17 FL FR RL HMI ECU #1 Dcm Dcm ECU #2 Dcm DCM ECU #3 Dcm Dcm CAM CAM CAM HMI ADAS CAM Service-Oriented Communication (SoC) Vehicle Info Spec. from ODX is now a vehicle specific registry. The physical vehicle link will no longer be defined at data definition time, instead it needs to be generated at runtime. 6/4/2019
- 18. © KPIT Technologies Limited Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.18 ECU #1 Dcm FL FR RL RR ADASHMI Some IP OTX Sequences Business Logic MCD-3 D Server D-PDU API Data for ECU-Code SoC: How this works 1) Advice 2) Offer 3) Subscribe 4) Handshake 5) Subscribe 6) Handshake ❶ I need CAM feedback from FL and RL ❷ ECU1 provides CAM feedback from FL ❷ ECU2 provides CAM feedback from RL ❸ Request CAM feedback from FL from ECU1 ❹ ECU1 sends CAM feedback from FL ❺ Request CAM feedback from RL from ECU2❻ ECU2 sends CAM feedback from RL ISO 13400-2 (DoIP) Dcm Service-Oriented Communication (SoC) - DiagnosticDEXT DEXT ECU #2 Dcm Dcm DEXT DEXT ECU #3 Dcm Dcm DEXT DEXT DEXT DEXT VIN LL DB ECU FL CAM #1#FL FR CAM #1#FR RL CAM #2#RL HMI HMI #2#HMI RR CAM #3#RR ADAS ADAS #3#ADAS DEXT VIT-Registry VIN Adresss selected with VIT-Registry 6/4/2019
- 19. © KPIT Technologies Limited6/4/2019 Distribution of this document prohibited. No portion to be reproduced without prior written permission from KPIT Technologies Ltd.19 Do we need two Standardization Organizations to take care of Onboard-Diagnostics?