Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Join international automotive experts from leading OEMs and suppliers as well as MathWorks industry experts and partners at the
free two-day MathWorks Automotive Conference, which this year focuses on e-mobility.
This simple buzzword covers many different challenges that automotive engineers face due to the industrys multidisciplinary domain:
Hybrid-electrical powertrain applications, emission reduction, and battery control systems are only a few examples. The "e" in "e-mobility"
means not only electric but overall enhanced or energy-efficient mobility. And with all the assistance functions that make mobility safer and
more convenient, it's also engaging mobility.
Conference sessions demonstrate e-mobility solutions based on MathWorks products, and presenters and attendees can exchange ideas
and discuss successful implementations of technical computing and Model-Based Design using MATLAB and Simulink.
Abstracts
Driving Innovation Addressing Megatrends in Automotive
John Stewart, Vice President, MathWorks EMEA
Technology and innovation, environment and legislation, economy and competition, and society and customers are four areas of
megatrends in the automotive industry. To successfully embrace these trends and meet the challenges facing the industry, automotive
OEMs and suppliers worldwide are modifying their development processes. Under the impetus of green initiatives, many projects, such as
the electrification of powertrains, are evolving their core processes to adopt Model-Based Design throughout their development life cycle. In
this talk, John Stewart discusses how early verification is a key approach within Model-Based Design that enables users and organizations
to be well prepared to follow and benefit from industry megatrends.
Applying Model-Based Design to an On-Board Driver Support System for Economic Driving
Jonny Andersson, Scania, Sweden
Scania Driver Support is an on-board support system developed for heavy-duty trucks that went into production in the fall of 2009. It is
designed to detect and analyze driving situations while driving. It identifies scenarios in which the drivers actions are especially important
for the driving economy, and it gives advice on how to act just after a situation has been evaluated. Rating the drivers behavior is also a
part of the method to create a positive influence on the driving style. Each situation is awarded up to five stars, and an average score also
shows the overall progress.
Four categories define the criteria with which the driver is evaluated:
1.
Hill driving Encourages the driver to adapt the speed to the terrain for better fuel economy.
2.
Brake use Rewards smooth braking and encourages the use of auxiliary brakes for nonurgent braking.
3.
Anticipation Focuses on the interplay between acceleration and braking and encourages a defensive driving style.
4.
Choice of gears Gives advice on using the correct gears for fuel economy and performance.
This presentation focuses on the development process for the on-board Scania Driver Support system.
Combustion Engine Starter Simulation in Real Time on Hybrid Powertrain Test Beds
Dr. Martin Schmidt, AVL List GmbH, Austria
In the development process for hybrid powertrains, a lot of time and money can be saved by using simulation models instead of real vehicle
components. The same model can be used to test basic functionalities in the lab and the behavior and impact to the unit under test on real
components on engine or powertrain test beds.
MATLAB and Simulink enable such simulation models to be designed efficiently and support the code generation to a real-time target
system.
This session presents engine starter simulation in hybrid powertrains. A starter simulation model has been developed with MATLAB and
Simulink to test the start behavior of the hybrid engine.
In the model development process, AVL ARTE.Lab is used. Based on MATLAB, Simulink, and Real-Time Workshop, AVL ARTE.Lab
generates the real-time application. This real-time application is executed on the AVL test bed automation and control system. A generic
Model Parameter Editor (MPE) allowing the smooth management of the model parameters at run time is provided. This is achieved by
modifying MAT-files created in conjunction with the simulation model. In this way, parameter variations of the starter simulation model can
be easily applied. A parameter updater has been created with MATLAB Compiler for automated parameter migration and preprocessing;
updates of the starter simulation model are automatically considered in the parameters.
The results show the realistic start behavior by using the starter simulation model on a hybrid powertrain test bed. By using MATLAB and
Simulink, different starter simulation models can be quickly exchanged, which leads to a shorter time to market.
Renaults Model-Based Design Powertrain Control Development Process: From Initial Requirements to Auto-Coded Blocks
Pedro Moreno Lahore, Renault, France
This session describes Renaults powertrain software process, which is based on Renault EMS 2010 modular software, rules, and tools that
are applied in a MATLAB and Simulink based simulation and software integration platform that helps users throughout development, from
the first evaluation of the requirement to the HIL validation of the strategy. This platform helps the different teams with:
Strategy requirement definition
Strategy design and validation
Strategy tuning
Physical model development for offline strategy performance evaluation
Software integration
The goal is to share and enrich future software-integrated control strategies, physical models, and clients stimuli throughout the
development process in order to increase reliability and quality, thereby decreasing development time.
Developing Vehicle Models with MathWorks Physical Modeling Solutions and dSPACE Automotive Simulation Models
Tino Schulze, dSPACE, Germany
Steve Miller, MathWorks, Germany
When it comes to modeling and simulation, automotive engineers want it all. They want models of the vehicle, the components, and the
environment. Engineers designing electric vehicles need to combine electrical, mechanical, and other domains in a single model. They want
models that run in desktop simulation and in real time. And, no matter how complete the model provided by the software vendor is, they
need the ability to customize it further. To meet all of these requirements, the best option can be the combination of two compatible
solutions. The ability to create custom models of vehicles and vehicle components delivered by MathWorks physical modeling solutions
combined with Automotive Simulation Models (ASM) from dSPACE enables engineers to create the exact model required for all tasks for
Model-Based Design. This session covers the advantages of each environment and how they complement each other.
Verification by Simulation Within the Model-Based Development Process at Continental Automotive Groups Engine Systems Business
Unit
Dr. Marco Kunze, Continental Automotive GmbH, Germany
The integrated development environment System Design Automation (SDA) at Continental Automotive Groups Engine Systems business
unit supports model-based function development (MBD) in the field of increasingly complex electronic control unit (ECU) structures and
supports developers throughout the function development process. Model-based testing and test engineering have taken a larger and larger
role, especially in the context of safety-relevant software and ISO 26262.
Based on PC simulation, models can be verified in an early step in addition to pure formal verification and before using further enhanced
and hardware-based methods like rapid prototyping. An important point at this time in development is the traceability from requirement to
the solution and its test and vice versa. The central topic for function and software engineers who are fulfilling all these tasks is to get
guidance through the huge amount of functionalities offered in the commercial standard tools.
The Engine Systems business unit therefore integrated into the SDA environment an MBD test suite, which is based on MATLAB, Simulink,
and Stateflow. The central part of the test suite is represented by the simulation manager. This central graphical user interface has been
extended in-house and covers the generation of new test cases, the reuse of existing test cases, and test case execution.
This session explains the function of the MBD test suite as an XML-based test plan, specification, and report and shows how the modelbased function development is supported by the simulation manager. It presents how the simulation manager makes full use of SDAs
closed workflow from the golden model representing the physical algorithm down to the generated code. All testing and validation tasks
can be done based on PC simulation or by the means of different rapid prototyping methods and are seamlessly integrated in the
development process. In addition, the generation of test vectors out of the golden model leads to test vector objects, which can be efficiently
reused by downstream steps of the development process.
Using the simulation manager and the MBD test suite optimizes the efficiency of the daily tasks of the function development process in the
Engine Systems business unit at Continental Automotive Group by giving a direct relationship between requirement engineering, test
planning and specification, and test implementation, either based on Simulink or based on measurements and test execution and report.
This results in a very high quality of modeled functionality. This integration makes it possible to further optimize the execution of the
downstream activities in the verification cycle, such as production code generation, integration, and documentation.
Production Code Generation Time Machine: A Guided Journey from Rapid Control Prototyping to E-Mobility
Tom Erkkinen, MathWorks, United States
Code generation experts and novices alike should enjoy this trip back in time, which begins with the roots of Model-Based Design and ends
with its latest capabilities. Topics discussed include large-scale modeling, fixed-point design, code optimization, software integration, and
code verification. Emerging automotive trends involving certification and standards support are also covered.
Automatic Code Generation of AUTOSAR Software Components for Mass Production Application of Engine Management Systems:
Process and Benefits
One System, Dozens of Devices and Controllers, Thousands of Parameters Parallel Computing as an Enabler for System-Level
Optimization
Loren Dean, MathWorks, United States
Designing e-mobility systems means multiple devices, batteries, complex machines, multifaceted controllers, and thousands of parameters.
And only some combinations will provide the energy efficiency and the dynamic that the vehicles customers want.
So engineers need to develop and especially optimize on the system level, meaning hundreds and thousands of simulation and calculation
runs. Parallel computing offers a way to realistically unleash this optimization potential while keeping tight schedules. The increased
availability of multicore machines and clusters offers the potential to perform analyses on or from the engineers computer. The term
stochastic methods should no longer be an excuse for insufficient coverage of the search space. This session shows how parallel
computing can be applied with MATLAB and Simulink to enable engineers to solve large problems more quickly and efficiently using
multicore computers, clusters, and beyond.
Best Practice for Software Quality Defining and Measuring Software Quality Objectives for Source Code
Philippe Spozio, Renault SA, France
Thierry Cambois, PSA Peugeot Citron, France
When verifying and validating code, automotive manufacturers and their suppliers often share the objective of producing safe code with the
right timing and cost. However, they have different ways of meeting this objective. The supplier may ensure quality through verification and
validation in the development process; the manufacturer may check quality through verification and validation in the final product. Without a
common approach on both sides, measuring the real quality of the end code can be a very complicated task.
In order to share their experience in using software verification tools such as Polyspace code verifiers, automotive manufacturers Renault
SA and PSA Peugeot Citron, automotive suppliers Valeo and Delphi Diesel Systems Power Train, and MathWorks decided in 2007 to
create a working group. This working group focused on defining software quality objectives for source code and a common approach to
implement and measure them. This session presents their results.
Incremental Quality Objectives have been defined along the software life-cycle process, from the first code version to the ultimate code
delivery. Along that path, we describe verification milestones, such as the absence of coding rules violations or the absence of run-time
errors, and propose to associate different quality levels with different modules and different deliveries. The quality therefore relies on a
modular verification approach based on a typical development process.
The final result is a tool-independent document that can be used as a step in a better formalization of relationships between car
manufacturers and suppliers with regards to software quality objectives. As a consequence of this work, Renault and PSA integrated the
document in their software requirement plan. Additionally, the document proposes a pragmatic way of using verification tools such as
Polyspace code verifiers for the purpose of detecting coding rules violations or proving absence of run-time errors.
Verification and Validation in a Collaborative, Layered Design Environment for Embedded Software-Intensive Systems
Raymond Tinsel, DAF Trucks, Netherlands
Co Melissant, MonkeyProof Solutions BV, Netherlands
Confidence in correctness and fit-for-purpose of models of both the system-under-design and its environment are key to the success of any
model-based approach to systems engineering. With the growing need for complex safety-critical systems in automotive, bidirectional
traceability between implementation and tests, and related requirement(s) or change requests, is of growing importance, as is the ability to
perform regression testing.
This session demonstrates a lean but scalable, engineer-friendly (single environment, easy navigation) and management-friendly
(automated data integrity checking and reporting, role-based permissions) approach to get to a fully verified and validated model-based
system design. We take a close look at a pragmatic and manageable, layered, top-down Model-Based Design and engineering process as
well as the tool suite and configuration that support and control it.
The process and tool suite are MATLAB-, Simulink-, and code generationcentric and build on top of the available verification and validation
capabilities of these tools. Database functionality is used to establish and maintain a central truth and to control permissions as required in a
collaborative environment. Version control and audit trails are applied throughout the process. A controlled environment is created without
loss of flexibility required in innovation.
The presented combination of process and tool suite has been successfully tailored and implemented in production environments in joint
efforts between MonkeyProof Solutions BV and its automotive OEM and tier-1 customers. The level of adoption of the approach is flexible,
ranging from creating executable specs for a supplier to in-house production code generation. The discussed approach is usually
implemented in stages to enable a smooth transition and to minimize risk.
Vehicle model
Driver model
The plant can be used to validate new functionality before running the algorithm on the actual engine, and since the controller used in
simulation is identical when running in the test cell or in demonstrator vehicle, most of the bugs in the new algorithm are captured at offline
simulation.
The Raptor environment is used for production algorithm development as well as rapid prototyping and advanced algorithm development;
the model-in-the-loop environment combined with the complete controller is particularly well-suited as a plant model for developing the
algorithm offline and can be validated on an actual engine, using the dSPACE hardware before the production controller is available.
Agenda
Tuesday, 22 June
Time
Session Title
10:0011:00
Registration
11:0011:30
11:3012:00
12:0012:30
12:3014:00
14:0014:30
14:3015:00
15:0015:30
15:3016:15
16:1516:45
16:4517:15
17:1517:45
17:4518:15
18:1519:00
19:00
Wrap-Up
Networking Reception with Buffet Dinner
Wednesday, 23 June
Time
Session Title
09:0009:30
09:3010:00
10:0010:30
10:3011:00
11:0011:30
11:3012:00
12:0012:30
12:3013:00
13:0014:30
14:3015:00
15:0015:30
15:3016:00