Cluster Simulation with Integrated Workflow and Test Management Chandu Puliroju dspace Inc.
ADAS and Autonomous Driving Imagine an autonomous car on a crowded crossroads Test Drive Test Drive Test Drive Test Drive Test Drive Test Drive Test Drive Test Drive Test Drive Test Drive Test Drive Test Drive 3
Daily Problems Many tests Few HILs test case test case test case test case 4
Software-in-the-Loop Faster than real Same tooling time XIL-API XCP Experimentation test case test case COM Test Automation Faster than real time XIL-API XCP Experimentation COM Test Automation 5
Offline Platform What is VEOS? MS Windows-based Simulation (and integration) platform Simulates Virtual ECUs Simulates other models (e.g., Functional Mockup Units) No real time (faster, slower, pause) C code debugging possible and more yet another platform (plus extras)
VEOS A flexible and fast Simulation and Validation Platform PC-based simulation platform for virtual ECUs, plant and environment models Supports Simulink, C Code, C++ Code, AUTOSAR, and 3 rd party models using FMI standard Provides possibilities to co-simulate even with proprietary simulators (e.g. RTMaps, ADTF) Interfaces to standard calibration and test tools (XCP, XIL-API) Step-by-Step debug during run time. 7 FMI: Functional Mockup Interface
One tool-chain for SIL and HIL testing ISO 26262 ready. Prequalified for all ASILs SYNECT Data management ASM Open simulation models MotionDesk 3-D visualization ControlDesk Experiment environment AutomationDesk Testing and evaluation SIL HIL Early PC-based validation of ECU software and functions Early, PC-based validation of ECU software and functions Seamless reuse of data Real-time validation of components and system Seamless reuse of tools, models, tests, layouts, data, etc. in real ECU testing 8
SIL Environment Virtual ECUs (V-ECUs) Plant models NEW Use Case Test of new controller functions in realistic environment Early integration test Non- Benefit of using VEOS Reuse of models, test, layout throughout the whole development process Integration test with realistic V-ECUs PC Cluster Simulation Simulation environment: XIL API 9
Speedup of (selected) HIL tests with SIL Simulation XIL-API Experimentation XCP COM Test Automation 10
Too many Tests for SIL? 11
Manager Node Too many Tests for SIL? Scalability with Cluster Simulation VEOS Cluster 12
Example: Adaptive Cruise Control Test Drive
General Structure: Simulation Cluster Manager Node: Distributes test cases, handles measurement data Execution Node: Loads test case, executes SIL test, collects measurements Example: Maneuver: ACC with Cut-In Tool Automation (e.g., Python) Cluster Management (e.g., via SYNECT) Execution (e.g., via SYNECT Execute Agent *) Test Automation (e.g., Python) SIL Tool Chain (e.g., XIL, VEOS, ASM) VEOS Cluster Manager Node 14
Test Generation Cluster Setup Database Scenario A ACC Cut-In Data Management Variant 1 Variant 2 VEOS Cluster Manager Node Scenario Variant Scenario X Variant n Results 15
Result Analysis Test Generation Why Cluster? NEW A Simulation Cluster is open to integrate test generation methods leverages SIL tool chain in general (VEOS, XIL-API, ASM) by scaling up, SYNECT Test Management Generate Scenario A ACC Cut-In Scenario Scenario X Data Management Variant 1 Variant 2 Variant Variant n VEOS Cluster Manager Node Real Time Testing Results Manage Classify Scale/Adapt 16
17 CLUSTER SIMULATION DEMO
18 OPTIMIZING HIL TESTING TIME
Test case authoring using Test Manager Test Steps UI in Test Manager = Test Implementation Test Project = 1 AUD Sequence = 1 Framework 19
Test Automation (TA) Framework Test Cases Test Management Project Test Steps Manager SYNECT Project Navigator 20
Test Phases Test Steps Test Actions Step Properties Favorite Actions Variable Mappings 21
How to optimize HIL time? 100 Test Cases = 600 mins (10 Hours) of HIL Time!!! 400 mins of HIL Time is wasted! HIL Testing Sequential Testing Process Test Case - 1 2 mins Test case 1 Test case 2 Test case 3 Test case 4 EXECUTION Test case 5 1 Test Case = 6 mins 4 mins EVALUATION Test case 10 Test case 9 Test case 8 Test case 7 Test case 6... Test case 11 Test case... Test case 100 22
Optimizing HIL Testing Time 100 Test Cases = 200 mins (~3 Hours) of HIL Time Reduced from 7 Hours to 3 Hours = Saves ~58% of HIL Time Master SYNECT Data Manager Execution Iteration Test Case - 1 2 mins 2 mins HIL Time HIL PC Test case 1 Test case 2 Test case 3 Captured Data Results EXECUTION Test case 4....mat /.mf4 1.mat /.mf4 2 Passed Failed 4 mins EVALUATION Offline PC Post-Processing Offline PC Iteration Test case 1 Test case 2.mat /.mf4 3.mat /.mf4 4 Passed Passed...... Test case 3 Test case 4... 23
24 DEMO
Thank you for listening! 25
Important Information! 2017, dspace GmbH All rights reserved. Written permission is required for reproduction of all or parts of this publication. The source must be stated in any such reproduction. This publication and the contents hereof are subject to change without notice. Benchmark results are based on a specific application. Results are generally not transferable to other applications. Brand names or product names are trademarks or registered trademarks of their respective companies or organizations. 26