Download now - ASAM

More documents

Recommendations

Info

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
DESCRIPTIOn ASAM AE CC (Container Catalog) is a generic approach for exchange of engineering data and its configuration It describes the meta data of a set of objects (e g files) in an exchange container which is exchanged between repositories or tools An important use case is the full fledged as well as the incremental data exchange between partners with different repositories A typical container comprises of: • Engineering objects such as source codes, documentation, compiled objects etc • Meta information about the exchanged object such as creator, name, description, version info, engineering domain, configuration and storage area FSX is based on XML and can be accessed, edited and transformed by standard XML software like transformation tools (e g XSLT), XML editors CC has the following main features: • Description of the repository structure • Description of meta data of the engineering objects • Flexible extension possibilities • Revision information and change histories DESCRIPTIOn ASAM AE CDF (CDFX-file) is a description format for data exchange of ECU parameter values Additionally ASAM AE CDF defines maturity levels for the parameter values While the complete ECU calibration process the calibrated data is exchanged in CDFX-files between different calibrators, ECUs and projects Additionally to the values of the different parameters the maturity levels of the values are exchanged too The ECU calibrator / tester uses a measurement and calibration tool to optimize the parameter values and give the values a maturity level For further processing or data transfer the tools support the CDFX-file format to store of the parameter values and its maturity levels 02 section • Linking support • Support for conditional document configurations (conditional compilation) • Support for content view filtering STAnDARD COnTACT CC@asam net CuRREnT STAnDARD vERSIOn ASAM AE CC V3 0 0 ACTIvE PROjECT TEAM MEMBERS Robert Bosch GmbH, Continental Automotive GmbH, MAN AG, XI-Works CuRREnT ACTIvITIES No current activities ASAM AE CC In ThE MARKET Used in several bilateral software projects as exchange container description A derivate of Container Catalog is also used as PDX in ODX Tools Also used as „document configuration“ file to control of the publishing process of functional documentation QuALITy ASSuRAnCE Verification by several different and independent in-house implementation of the participants ASAM AE CDF completes ASAM MCD-2 MC ASAM MCD-2 MC defines the parameters and the interfaces to access it in the ECU ASAM AE CDF defines how to store and transfer the data outside the ECU CuRREnT STAnDARD vERSIOn ASAM AE CDF V2 0 0 STAnDARD COnTACT Thilo Wenzel, ETAS GmbH, CDF@asam net ACTIvE PROjECT TEAM MEMBERS Robert Bosch GmbH, Continental Automotive GmbH, ETAS GmbH, Vector Informatik GmbH, XI-Works CuRREnT ACTIvITIES No current activities STAnDARD REPORT fROM ASAM AE CC STAnDARD REPORT fROM ASAM AE CDf 13
Page 1 and 2: association for standardisation of
Page 3 and 4: table of contents Solutions Guide 2
Page 5 and 6: DEAR READER, In the 2009 issue of o
Page 7 and 8: The vision of ASAM is that standard
Page 9 and 10: The ASAM organization was created w
Page 11 and 12: at the same time The use case is XC
Page 13: STAnDARD COnTACT Thilo Wenzel, ETAS
Page 17 and 18: DESCRIPTIOn ASAM AE ISSUE is an exc
Page 19 and 20: ASAM CAT STAnDARDS DESCRIPTIOn When
Page 21 and 22: tems Device Information Text is act
Page 23 and 24: • Extension of maximum file size
Page 25 and 26: Standard Market Name ASAM AE CC Con
Page 27 and 28: ASAM COMMOn Standard Market Name 03
Page 29 and 30: • The Bus Navigator displays a we
Page 31 and 32: ferred via the ETK interface and fo
Page 33 and 34: import/export facilities and made a
Page 35 and 36: (IFW) of Leibniz University in Hann
Page 37 and 38: implements the ASAM ODS security mo
Page 39 and 40: in parallel to the MDM-FASIS in the
Page 41 and 42: BuSineSS BenefitS Due to the powerf
Page 43 and 44: BuSineSS BenefitS Through the share
Page 45 and 46: ing to the defined companion and th
Page 47 and 48: the specific project surrounding co
Page 49 and 50: SuCCeSS Strategy Visu-IT! developed
Page 51 and 52: Checkers are available for: ASAM MC
Page 53 and 54: 05 section 51
Page 55 and 56: fAMOS Product Type/Service: Signal
Page 57 and 58: aquintos GmbH COMPANy dESCRIPTION a
Page 59 and 60: ASAM RELATEd PROduCTS ANd SERVICES
Page 61 and 62: Das virtuelle Fahrzeug Forschungsge
Page 63 and 64: AutomationDesk Product Type/Service
Page 65 and 66:
The physical ECUs of a RBS (remaini
Page 67 and 68:
EtherCAn Product Type/Service: Ethe
Page 69 and 70:
CONTACT Name: Ms Ramona Theil Email
Page 71 and 72:
and Communication Technologies (ASC
Page 73 and 74:
Functionalities: Transferring parti
Page 75 and 76:
imc Meßsysteme GmbH COMPANy dESCRI
Page 77 and 78:
plication and hardware Supported AS
Page 79 and 80:
Kristl, Seibt & Co GmbH COMPANy dES
Page 81 and 82:
Dipl. Ing. Bernd Wenzel, Managing D
Page 83 and 84:
PROvEtech:TA Product Type/Service:
Page 85 and 86:
MKS GmbH BRIEF dESCRIPTION MKS, the
Page 87 and 88:
Peak Solution GmbH COMPANy dESCRIPT
Page 89 and 90:
05 section 87
Page 91 and 92:
ReliaTec GmbH COMPANy dESCRIPTION T
Page 93 and 94:
sasLib Product Type/Service: Samtec
Page 95 and 96:
05 section 93
Page 97 and 98:
05 section Diagnostic Quality - ODX
Page 99 and 100:
Sontheim Industrie Elektronik GmbH
Page 101 and 102:
analysis capabilities of FIBEXplore
Page 103 and 104:
05 section TU Dresden, IAD - Instit
Page 105 and 106:
Development ECU ECU ECU Process Dis
Page 107 and 108:
ASAP2Toolkit Product Type/Service:
Page 109 and 110:
05 section Innovation you can depen
Page 111 and 112:
iASYS Technologies Pvt , Ltd 72 In2
Page 113 and 114:
06 Request form for ASAM Membership
Page 115 and 116:
A BASE STAnDARD defines syntax, abs
Page 117 and 118:
CR is short for Change Request DCD
Page 119:
consist of both protocol control in
Page 122:
System Architecture System Architec
show all

Download now - ASAM

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?