DOCSLIB.ORG

PC-Based Validation of ECU Software

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
PC-Based Validation of ECU Software PC-Based Validation of ECU Software Sean Wyatt - ETAS, Inc. Embedded System Workshop Venue: Oakland University School of Engineering and Computer Science, Rochester, MI Date: October 13, 2012 What you will learn Motivation for PC-Based Development How to create MiL and SiL platforms using ETAS INTECRIO software; How to calibrate C-code using production tools like ETAS INCA; How to improve productivity, reduce cost by leveraging the PC platform; 2 Agenda Why PC-based Development Definitions What is INTECRIO? Model-in-the-loop with INTECRIO Software-in-the-loop with INTECRIO Other ETAS Solutions Summary 3 Agenda Why PC-based Development Definitions What is INTECRIO? Model-in-the-loop with INTECRIO Software-in-the-loop with INTECRIO Other ETAS Solutions Summary 4 Why PC-Based Development? Engine Management Transmission Management Effort Vehicle Motion Management Battery Number of calibrations Management Brake Consumption and Management emission requirements Increased inter domain connectivity SW- SW- SW- Component 1 Component 2 Component 3 AUTOSAR AUTOSAR AUTOSAR Interface Interface … Interface AUTOSAR-RTE Basic Software Module (BSM) Microcontroller Abstraction 100% ECU Hardware 25000 4000 9000 12000 16000 0% New layered standard 1997 2002 2004 2007 2010 New functions and architecture variants Engine control complexity 5 Why PC-Based Development? Simulation Benches Vehicles Today – 70% 2015 – 40% 2015 – 40% Effort Today – 25% 2015 – 20% Today – 5% 6 Why PC-Based Development? “Road to lab to math is basically the idea that you want to be as advanced on the evolutionary scale of engineering as possible. Math is the next logical step in the process over testing on the road and in the lab. Math is much more cost effective because you don’t have to build preproduction vehicles and then waste them. We’ve got to get out in front of the technology so it doesn’t leave us behind. We have to live and breathe math. When we do that, we can pass the savings on to the consumer.” - A senior auto executive Summary: Development hardware (ECUs, vehicles etc.) is expensive and PCs are more powerful and inexpensive than ever. Why PC-Based Development? Automotive industry is already leveraging PC- based development for a range of activities, e.g.: – software functional testing and V&V – legacy c-code simulation on the PC – target-like timing analysis (RTOS) – calibration development – system development using plant models – complete ECU hardware emulation But more can be done. Several studies.. 9 Agenda Why PC-based Validation Definitions What is INTECRIO? Model-in-the-loop with INTECRIO Software-in-the-loop with INTECRIO Other ETAS Solutions Summary 10 Definitions Our Definition: A virtual ECU development environment is characterized by the absence of physical hardware, i.e. PC-based representation of all components, with or without real-time execution 11 Evolution of Virtualization ECU Application Models, Software Driver, Vehicle and Environment Models 4 Virtual Environment 3 Real ECU Real Vehicle 2 1 Real Environment 12 What’s included for today? Included: ECU algorithm models or embedded code ECU real-time operating system (RTOS) and other basic software components Physical systems (e.g. engine, transmission, body, chassis, driver, environment models) Not included: Virtualization of the ECU hardware (e.g. microcontroller, peripherals) Virtualization of the physical buses (e.g. CAN, FlexRay) 13 Steps to Create a Virtual Environment Physical Models or ECU Algorithm ECU Embedded stimuli Models Code The main ingredients Integration and Build Environment Execution Platform Instrumentation The glue and tools necessary Verification and Calibration and Automatic Testing Validation Measurement The development tasks you are interested in 14 Model-in-the-Loop (MiL) Simulation • Defined as the ECU algorithm model “in-the-loop” with the plant models – May be run within the modeling environment, or Physical Models or ECU Algorithm stimuli Models IntegrationConnect models and Build in Simulink Environment RunExecution in Simulink Platform under Windows 15 Model-in-the-Loop (MiL) Simulation • Defined as the ECU algorithm model “in-the-loop” with the plant models – May be run within the modeling environment, or – Run as an executable under Windows - from model-generated code Physical Models or ECU Algorithm stimuli Models code gen code gen Integrate model-code and compile RunExecution executable Platform under Windows 16 Software-in-the-Loop (SiL) Simulation • Defined as the ECU embedded software “in-the-loop” with the plant models – May be run within the modeling environment, or Physical Models or ECU Embedded stimuli C-Code S-functions Connect models and S-functions Integration and Build Environment (containing code DLLs) in Simulink RunExecution in Simulink Platform under Windows 17 Software-in-the-Loop (SiL) Simulation • Defined as the ECU embedded software “in-the-loop” with the plant models – May be run within the modeling environment, or – Run as an executable under Windows Physical Models or ECU Algorithm ECU Embedded stimuli Models C-Code code gen code gen Integrate model-code with ECU code Integration and Build Environment and compile RunExecution inexecutable Simulink Platform under Windows 18 Agenda Why PC-based Validation Definitions What is INTECRIO? Model-in-the-loop with INTECRIO Software-in-the-loop with INTECRIO Other ETAS Solutions Summary 19 Virtual Setup for ECU Development Environment (Road, Wind, etc.) Vehicle Driver Subsystem Subsystem Subsystem (e.g. Engine) (e.g. Transmission) (e.g. Chassis) Set-Point (Sensor) Sensor Actuator Sensor Actuator Sensor Actuator Vehicle Network (e.g. CAN) 20 Virtual Setup for ECU Development Environment (Road, Wind, etc.) Vehicle Driver Subsystem Subsystem Subsystem (e.g. Engine) (e.g. Transmission) (e.g. Chassis) Set-Point (Sensor) Virtual Sensor/Actuator Signal Bus Vehicle Network (e.g. CAN) 21 Virtual Setup for ECU Development Environment (Road, Wind, etc.) Driver Vehicle Subsystem Models (e.g. Engine, Transmission, Chassis) Set-Point (Sensor) Virtual Sensor/Actuator Signal Bus Vehicle Network (e.g. CAN) 22 Virtual Setup for ECU Development Environment (Road, Wind, etc.) Driver Vehicle Subsystem Models (e.g. Engine, Transmission, Chassis) Set-Point (Sensor) Virtual Sensor/Actuator and Network Signal Bus m2 m4 m6 m1 m3 m5 m7 function1 function 2 function 3 23 What is INTECRIO? Virtual Sensor/Actuator and Network Signal Bus 26 What is INTECRIO? Plant Models Application Software Driver,Vehicle,Environment Design and Specification Simulink ASCET Simulink C-code obj, lib, dll code gen code gen INTECRIO RTA-OSEK for PC Target HEX and A2L files 27 Key Takeaways PC-based development of ECU software is becoming more widespread due to cost and performance advantages INTECRIO is a versatile platform for PC- based verification and validation (e.g. in MiL and SiL phases) 28 Agenda Why PC-based Validation Definitions What is INTECRIO? Model-in-the-loop with INTECRIO Software-in-the-loop with INTECRIO Other ETAS Solutions Summary 29 INTECRIO for MiL Simulink Simulink R2007a R2011a Embedded Coder Simulink Coder Hex and A2L Virtual Prototyping 30 INTECRIO for MiL 31 INTECRIO for MiL: Demo Setup • Goal: Simulate a Simulink-based plant (throttle) + Simulink throttle controller specification. THR_Cor Actual Position Desired Position Simulink Algorithm Throttle Plant Model 32 Agenda Why PC-based Validation Definitions What is INTECRIO? Model-in-the-loop with INTECRIO Software-in-the-loop with INTECRIO Other ETAS Solutions Summary 33 INTECRIO for SiL – 2 steps Simulink Models Software Component INTECRIO HEX and A2L files 34 INTECRIO for SiL – Step 1 with INCODIO Measure C-code Create Interface Calibrate Schedule 35 INTECRIO for SiL 36 INTECRIO for MiL + SiL: Demo Setup • Goal: Verify that the C-code implementation of the Throttle Controller matches specification, reusing the stimulus and plant Simulink models. THR_Cor Actual Position Desired Position C-Code Algorithm Throttle Plant Model 37 Calibration of C-code with INCA 38 Key Takeaways MiL: INTECRIO integrates one or more Simulink models at the code level, adds scheduling information and compiles for PC target. SiL: INCODIO parses C-code and makes it visible to INTECRIO for integration with models or other C-code. INTECRIO adds scheduling information and compiles for PC target. Calibration: An industry standard tool like INCA can be used to pre-calibrate ECU software in the SiL environment 39 Agenda Why PC-based Validation Definitions What is INTECRIO? Model-in-the-loop with INTECRIO Software-in-the-loop with INTECRIO Other ETAS Solutions Summary 40 INCA with INCA-SIP Algorithm Engineer ® Simulink INCA Control & Plant Models Legacy C-code .dll INCA-SIP API XCP on Ethernet Windows 41 INCA with INCA-VLINK Calibration Engineer ® Simulink INCA Control & Plant Models Legacy C-code .dll INCA-EIP INCA-VLINK compile TCP/IP on Ethernet Windows 42 ISLOAR-EVE* (ETAS Virtual ECU) Authoring Virtual Instruments INCA Windows Ethernet *Product not yet released 43 Agenda Why PC-based Validation Definitions What is INTECRIO? Model-in-the-loop with INTECRIO Software-in-the-loop with INTECRIO Other ETAS Solutions Summary 44 Summary Virtual techniques can substantially lower the cost of verification and validation of ECU control models and software. Calibrators can use the same tools in the virtual environment as in the vehicle. Re-use of test cases, models and calibration data across the development cycle further optimizes cost and effort. AUTOSAR architecture further enables validation
Load more

Recommended publications
  • Measuring Everything
    Measuring Everything White Paper Measuring Everything Table of Contents 1 Really Measuring Everything..................................................................................................................................................... 3 1.1 Measurement Concept in CANape ........................................................................................................................................... 5 1.2 Recorder PC Hardware .............................................................................................................................................................. 6 2 Accessing Internal ECU Data .................................................................................................................................................... 6 2.1 Example: ECU ............................................................................................................................................................................. 9 2.2 Example: Transmission ECU...................................................................................................................................................... 9 3 Acquiring Sensor Data for Autonomous Driving ...................................................................................................................10 3.1 Acquiring Raw Data From Radar Sensors .............................................................................................................................10 3.1.1 Practical Example With More Than Two GByte/s ................................................................................................................11
    [Show full text]
  • Development of a Calibration Tool Using CCP and XCP on CAN Bus
    Development of a Calibration Tool using CCP and XCP on CAN Bus Master Thesis Submitted in Fulfilment of the Requirements for the Academic Degree M.Sc. Dept. of Computer Science Chair of Computer Engineering Submitted by: Satyesh Shivam Student ID: 386595 Date: 14.11.2016 Supervising tutor: Prof. Dr. W. Hardt External Supervisor: Dipl-Ing Billand Dirk (Bosch Engineering Gmbh) Abstract Testing of the Electronic Control Unit is a very important step before delivering the software to customer. Due to increasing complexity in the requirements and the timing constraints, it is needed that the testing should be proper and on time. To meet the timing constraints it is needed to automate the entire process of testing. Although the current testing tool support the automation process, it is very slow. In this thesis a new tool has been developed which will support calibration using CCP and XCP on CAN bus. Secondly, the tool will also provide the feature of automation, where user can write their own script to test the ECU. This will make the entire process of testing very fast. Finally both the solutions will be compared with respect to time for deducing the final conclusion. Keywords: CCP, XCP, ECU Testing, Calibration, Design Patterns Acknowledgements I would like to show my greatest appreciation to Prof.Dr.Wolfram Hardt for giving me an opportunity to do my thesis under his guidance. I am grateful to Mr. Dirk Billand for being my supervisor and providing constant support in developing my thesis from all the directions. I appreciate the feedback offered by Mr.
    [Show full text]
  • CPU, FPGA, and I/O Solutions for Real-Time Simulation and Testing
    CPU, FPGA, and I/O Solutions for Real-Time Simulation and Testing Sam Mirsky , Application Engineering, MathWorks Martin Stoller, CEO, Speedgoat 1 CPU, FPGA, and I/O Solutions for Real-Time Simulation and Testing 2 © 2017 The MathWorks, Inc. and Speedgoat GmbH Agenda ▪ Introduction to Real-Time Simulation and Testing (RTST) including Rapid Control Prototyping (RCP) and Hardware-in-the-loop(HIL) simulation ▪ MathWorks Model-Based Design workflow - from Desktop simulation to Real- Time execution ▪ Integration with other MathWorks products ▪ Speedgoat Hardware ▪ How MathWorks helps you to achieve your next RTST project 3 Why perform Real-Time Simulation and Testing? To - Test and investigate complex control design that is expensive to test on the field - Reduce time to market for your engineering products - Save costs by detecting errors early in your design process by validating your simulation model in real time with actual hardware and I/O 4 User Story: Gulfstream Aerospace, USA Hardware-in-the-Loop Simulation of Aircraft Engines Gulfstream Aerospace Corporation (GAC), located in Savannah GA, USA, produces high-end civilian business jets. MathWorks and Speedgoat are providing a complete Hardware-in-the-Loop solution to simulate two interconnected engines, tested against the full authority digital engine controller (FADEC). Gulfstream G650 business jet 5 User Story: AGCO, Germany/France/Finland Hardware-in-the-Loop Simulation of Tractors and Agricultural Machinery • Automated testing of controllers for tractors and other agricultural machinery
    [Show full text]
  • Czech Technical University in Prague Faculty of Mechanical Engineering Department of Automotive, Combustion Engine and Railway Engineering
    Czech Technical University in Prague Faculty of Mechanical Engineering Department of Automotive, Combustion Engine and Railway Engineering Master’s Thesis Title HIL simulation of driving cycles and its validation by Bc. Harshaan Singh Thesis supervisors: doc. Ing. Jiří Novák, Ph.D., Czech Technical University, Prague doc. Ing. Tomáš Haubert, Ph.D., Porsche Engineering Services, s.r.o., Prague I dedicate this thesis to my nephew (Kuwarveer Singh) and my two nieces (Mehr Kaur and Sohila Kaur) Acknowledgement Firstly, I would like to extend my gratitude to both my supervisors Dr. Jiri Novak at Czech Technical University, Prague and Dr. Tomas Haubert at Porsche Engineering Services for giving this opportunity to pursue my Master’s Thesis on this exciting problem space. I am extremely thankful to all my team members Mr. Martin Florian, Mr. Josef Nemet, Mr. Tomas Kamenca and Mr. Daniel Soares, of Electronics Integration Department for providing a good working atmosphere and assistance in day to day activities. I am fortunate to have spent my time at Porsche Engineering and gaining better understanding about Vehicle Diagnostics and Hardware-in-the-loop simulations. Last but not the least, I would like to thank my family and friends for their immense support and love. Abstract To establish early niche in the market, vehicles being produced these days are growing exponentially in terms of complexity (hardware and especially in software). Keeping pace with this advancement, verifying and validating design becomes crucial steps. Hardware-in-the-loop (HIL) tests is one of the well adopted simulation test in the industry to overcome this challenge.
    [Show full text]
  • INCA-VLINK V1.3 Getting Started Guide
    INCA-VLINK V1.3 Getting Started Copyright The data in this document may not be altered or amended without special noti- fication from ETAS GmbH. ETAS GmbH undertakes no further obligation in rela- tion to this document. The software described in it can only be used if the customer is in possession of a general license agreement or single license. Using and copying is only allowed in concurrence with the specifications stipulated in the contract. Under no circumstances may any part of this document be copied, reproduced, transmitted, stored in a retrieval system or translated into another language without the express written permission of ETAS GmbH. © Copyright 2014 ETAS GmbH, Stuttgart The names and designations used in this document are trademarks or brands belonging to the respective owners. The name INTECRIO is a registered trademark of ETAS GmbH. MATLAB and Simulink are registered trademarks of The MathWorks, Inc. Document AM019910 V1.3 R01 EN - 11.2014 2 ETAS Contents Contents 1 General Information . 5 1.1 Safety Advice . 5 1.1.1 Correct Use . 5 1.1.2 Labeling of Safety Instructions . 5 1.1.3 Demands on the Technical State of the Product. 5 1.2 System Information . 6 1.3 User Information . 6 1.3.1 What You Need to Know . 6 1.3.2 Structure of the Documentation . 7 1.3.3 INCA-VLINK: Online Help. 8 1.3.4 INCA-VLINK: Hardware Configurator Online Help . 8 1.3.5 Working with this Manual . 9 2 Installation . 10 2.1 Preparations . 10 2.1.1 Delivery Scope.
    [Show full text]
  • INCA V7.3 Getting Started
    INCA V7.3 Getting Started Copyright The data in this document may not be altered or amended without special noti- fication from ETAS GmbH. ETAS GmbH undertakes no further obligation in rela- tion to this document. The software described in it can only be used if the customer is in possession of a general license agreement or single license. Using and copying is only allowed in concurrence with the specifications stip- ulated in the contract. Under no circumstances may any part of this document be copied, reproduced, transmitted, stored in a retrieval system or translated into another language without the express written permission of ETAS GmbH. © Copyright 2020 ETAS GmbH, Stuttgart The names and designations used in this document are trademarks or brands belonging to the respective owners. INCA V7.3 - Getting Started R01 EN - 03.2020 INCA V7.3 - Getting Started 2 ETAS GmbH Content Content 1 Introduction 6 1.1 Intended Use 6 1.2 Target Group 6 1.3 Safety Information 7 1.4 Using this Manual 7 1.5 List of Abbreviations 8 2 INCA - Concept 10 2.1 General Description 10 2.1.1 System Overview 10 2.1.2 Open Interfaces 11 2.2 Calibration Basics 13 2.2.1 Standard Interfaces Based on the ASAM-MCD Model 14 2.2.2 Interfaces to the Control Unit- ASAM-MCD-1 15 2.2.3 Calibration with ETK (Parallel Control Unit Interface) 16 2.2.4 Calibration via the Serial Interface 18 2.2.5 Measurement and Calibration Hardware 21 2.3 INCA - Basics 22 2.3.1 Data Management Concept for Working Page and Reference Page 22 2.3.2 Project, Master Working , and Reference Datasets
    [Show full text]
  • INCA V7.2 New Functions
    INCA V7.2 New functions At a Glance Acquisition of tens of thousands of signals from the ECU at high cycle rates by means of the new FETK interface Connection to several FETK ECUs plus CAN, CAN FD, LIN, or FlexRay vehicle busses in parallel by new ES89x ECU and Bus Interface Modules Easy centrally controlled automated INCA installa- tions by using Windows® The flexible software tools in the ETAS The comprehensive measurements can be Installer INCA product family are designed for saved in compressed form in ASAM MDF electronic control unit (ECU) calibration V4.1 format without loss of quality, which Support of Windows® 10 and diagnostics and to record ECU meas- allows file sizes to be reduced by up to 60 urement data. As INCA was developed percent. For fast inputting of data, the further, new functions were provided measurement files can be indexed, and quarterly in the form of service packs from INCA V7.2 supports MDF-compliant index- version 7.1 on. All these functions are con- ing. In conjunction with the MDA meas- tained in INCA V7.2. In addition to the urement data analysis tool, a proprietary Microsoft Windows® 7, 8, and 8.1 opera- indexing system is also offered as an alter- ting systems, the new version native, one that allows very large meas- also supports Windows® 10. urement files to be input quickly into MDA. Recording large volumes of ECU data To facilitate the quick preparation of meas- Used in conjunction with the ETAS FETK-T urements with many variables, ETAS has interface for high-performance control speeded up the loading of extensive exper- units and the new ES891/ES892 interface iments and the opening of the variable se- modules, INCA V7.2 allows users to re- lection dialog.
    [Show full text]
  • Softing Automotive Product Catalog
    SOFTING AUTOMOTIVE Diagnostics | Measurement | Testing PRODUCTS & SOLUTIONS No. 6 LEGAL NOTICE 2 CONTACT Softing Automotive Electronics GmbH Richard­Reitzner­Allee 6, 85540 Haar – Germany Phone +49 89 45 656 ­420 Fax +49 89 45 656 ­499 E­mail [email protected] Internet www.automotive.softing.com Softing Engineering & Solutions GmbH Einhornstr. 10, 72138 Kirchentellinsfurt – Germany Phone +49 7121 9937 ­237 Fax +49 7121 9937 ­266 E­mail [email protected] Internet www.automotive.softing.com EXCLUSION OF LIABILITY The information provided in this catalog corresponds to the state of the art when going to press and is provided to the best of our knowledge. We will not accept any warranty claims arising from the information provided in this catalog, especially warranties for quality and durability pursuant to section 443 of the German Civil Code (Bürgerliches Gesetzbuch). We reserve the right to make improvements and additions to and to include new findings in this catalog with out giving advance notice. The actual products can deviate from the information provided in the cata­ log where technical modifications arising from product improvements make this necessary. The offer and/or the specifications in the order confirmation provided for a specific case by Softing Automotive Electronics GmbH and its affiliated com­ panies is binding in this respect. All the product names listed in the catalog are either registered or unregistered trademarks of the respective owners. Errors and omissions reserved. We provide this catalog to our customers and pro­ spective clients free of charge. Reprinting and reproducing this catalog and making it available electronically, even in the form of excerpts, is only permissible with our written consent.
    [Show full text]
  • User Guide Openecu Developer Platform Sim-API Release 3.1.0-FS R2021-1
    ® User Guide OpenECU Developer Platform Sim-API Release 3.1.0-FS r2021-1 Copyright © 2020 Pi Innovo Table of Contents Foreword .................................................................................................................. xii 1. Disclaimer .................................................................................................... xii 2. Health and Safety information ........................................................................ xii 1. Introduction ............................................................................................................ 1 1.1. Overview ..................................................................................................... 1 1.2. Included in your OpenECU kit ...................................................................... 2 1.2.1. Hardware ......................................................................................... 2 1.2.2. Software — C-API ............................................................................ 2 1.2.3. Software — Simulink API .................................................................. 2 1.2.4. Required Tools ................................................................................. 3 1.3. About MATLAB and Simulink ....................................................................... 3 1.4. Licensed Features ....................................................................................... 3 1.5. OpenECU requirements ..............................................................................
    [Show full text]
  • MANEUVER BASED VALIDATION of BMW Xdrive VARIANTS by USING VIRTUAL VEHICLE INTEGRATION and HIL TEST METHODS
    19.09.2012 Matthias Prebeck, Dr. Peter Rissling; BMW Group Michael Folie; IPG Automotive MANEUVER BASED VALIDATION OF BMW xDRIVE VARIANTS BY USING VIRTUAL VEHICLE INTEGRATION AND HIL TEST METHODS. IPG TECHNOLOGY CONFERENCE, SEPTEMBER 18 -19, KARLSRUHE. Freude am Fahren AGENDA. • Basics xDrive. • Testsystem. • Integration engine-model. • Maneuver based tests. • Testautomation. • Benefits and Outlook. MANEUVER BASED VALIDATION, 19.09.2012 Page 2 BASICS xDRIVE. ACTIVE 4X4-SYSTEM. DSC (Master): Computation target torque with respect to the driving sit. ECU: DSC Send-out target torque on communication bus. Com. Bus LMV (Actuator): Receive target torque and actuate clutch. ECU: LMV Securing torque accuracy over temperature and lifetime. Requirements xDrive: Maximum traction. BMW-typical driving characteristics. Reduced fuel consumption deficite. All advantages of a 4x4 car without the typical disadvantages. MANEUVER BASED VALIDATION, 19.09.2012 Page 3 BASICS xDRIVE. 4X4 FUNCTIONS IN LMV-ECU. Signal conditioning Bussignals: Bussignals: Target torque, Computation Actual torque, Guardmodel Wheel speeds, … of internal … variables Abrasion- Degradation Torque model (thermal impact) and fail-safe controller (oil, coating) logics Sensors, Terminals Diagnostics (Current, Ubat, GND) Control: current + mechanics MANEUVER BASED VALIDATION, 19.09.2012 Page 4 BASICS xDRIVE. LATEST MODELS WITH xDRIVE. 09/2009 06/2010 09/2010 07/2012 7-Series 5-Series GT 5-Series 3-Series 2009 2010 2011 2012 2013 09/2009 09/2010 09/2011 11/2012 X1 X3 6-Series 1-Series MANEUVER BASED VALIDATION, 19.09.2012 Page 5 TESTSYSTEM. HIL-PLATTFORM. Main Switch Power Supply 1 (Engine Start) Power Supply 2 Realtime Computer Patch Panel Plug-In TestBox 1 FlexRay DSC Plug-In TestBox 2 LMV CAN LMV-ECU + Actuator MANEUVER BASED VALIDATION, 19.09.2012 Page 6 TESTSYSTEM.
    [Show full text]
  • Increasing Efficiency in ECU Function Development for Battery Management Systems
    DEGREE PROJECT IN INFORMATION AND COMMUNICATION TECHNOLOGY, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2016 Increasing efficiency in ECU function development for Battery Management Systems SHIVARAM SINGH RAJPUT KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF INFORMATION AND COMMUNICATION TECHNOLOGY Increasing efficiency in ECU function development for Battery Management Systems Master of Science thesis in Embedded Systems (30 ECTS credits) at the school of Information and Communication Technology KTH Royal Institute of Technology Stockholm, Sweden October 2016 by, Shivaram Singh Rajput Supervisors: Christian Fleischer Advanced Battery Technology, NEVS Yuan Yao ESY ELEKTR. O INBYGGDA SYSTEM, KTH Examiner: Zhonghai Lu ESY ELEKTR. O INBYGGDA SYSTEM, KTH ABSTRACT In the context of automotive industries today, the focus of ECU function development is always on finding the best possible combinations of control algorithms and parameter. The complex algorithms with broad implementation range requires optimal calibration of ECU parameters to achieve the desired behaviour during the drive cycle of the vehicle. With the growing function complexity of automotive E/E Systems, the traditional approaches of designing the automotive embedded systems are not suitable. In order to overcome the challenge of complexity, many of the leading automotive companies have formed a partnership in order to develop and establish an open industry standard for automotive E/E architecture called AUTOSAR. In this thesis, toolchain for ECU function development following AUTOSAR standard and an efficient measurement and calibration mechanism using XCP on CAN will be investigated and implemented. Two toolchains will be proposed in this thesis, describing their usage in different stages of ECU function development and in calibration.
    [Show full text]