Download now - ASAM

STAnDARD
REPORT fROM
ASAM AE hIL
12
standard reports
Solutions Guide 2011
DESCRIPTIOn
A typical Hardware-in-the-Loop (HIL) simulator
today has not only to provide interfaces for
the real-time simulator itself Also a wide range
of external functionalities needs to be remotecontrolled
In general a standardized API has
to be developed for all of these functionalities
listed below:
Model Access, i e the capability to write, read
and measure simulator internal variables,
ECU Access, i e the capability to write, read
and measure ECU internal variables, Stimulator
functionality, i e the option to describe
and evaluate real-time capable stimulation
sequences, DIAG Access, i e , the feature set
to remote-control 3rd party ECU diagnostic
tools, e g to use failure memory management
options, FIU Access, the capability to control
electrical failure injection systems, to be used for
short circuits, set to battery voltage or ground
potential, open connection, etc for ECU pins,
Network Access, i e the option to read and
write signal values on the automotive network
systems, such as CAN, LIN, FlexRay in a symbolic
form, A Test Framework which serves as a
central infrastructure to handle all variables related
to their specific formats (ASAM MCD-2
MC, ASAM MCD-2 D (ODX), ASAM MCD-2
(Fibex, DBC)) This framework also provides
the means for the parameterization of the test
bench itself
A description and modelling method should be
used, which was also applied successfully in the
ASAM MCD-3 project:
The modelling of the generic, technology independent
functionalities in UML (Enterprise Architect)
and automated generation of related
interface references for the most important
interface technologies
The most important interface technologies for
this application area are NET (as C# interfaces),
the Open Source script language Python
and Java At least for these four technologies,
interface references are provided They are
generated by means of a tool which automates
Enterprise Architect If there is the need for additional
interface references they can be added
without any influence on the generic model or
already existing references
With regard to list Model Access and ECU Ac-
cess, it needs to be mentioned that an almost
identical API modelling is to be aimed for Furthermore,
the reuse of model parts of ASAM
MCD-3 is intended
But in general it needs also to be emphasized,
that ASAM MCD-3 MC and ASAM MCD-3
D cannot be applied directly for the HIL use
cases because of their complexity and abstract
definition Therefore, there is the need for
Hardware-in-the-Loop and ECU test oriented
convenience layers
CuRREnT STAnDARD vERSIOn
ASAM HIL API V1 0 1
STAnDARD COnTACT
Dr Jobst Richert, dSPACE GmbH
HIL_API@asam net
ACTIvE PROjECT TEAM MEMBERS
The project team consists of the following
companies:
End Users: Audi AG / Volkswagen AG, BMW
AG, Robert Bosch GmbH, Continental Automotive
GmbH (Core Group)
Furthermore this project is supported by HIS
(German: Herstellerinitiative Software, a coordination
group among the German OEMs)
Test System / Tool Suppliers / Others: Berner
& Mattner Systemtechnik GmbH, dSPACE
GmbH, ETAS GmbH, M&K GmbH, National
Instruments, TraceTronic GmbH, Vector Informatik
GmbH
CuRREnT ACTIvITIES
Finalization of maintenance version 1 0 1 until
end of 2010 The next major version 2 0 project
will start early in 2011
ASAM AE hIL In ThE MARKET
ASAM HIL API 1 0 is available in several HIL
supplier implementations First system integrations
based on this new standards also already
exist
QuALITy ASSuRAnCE
Dependent on the availability of product implementations
running in parallel, cross tests
are pre-planned