b - ASAM

More documents

Recommendations

Info

12 reports from the workgroups activity report from ASAM AE CC (Container Catalog) Description 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 • Linking support • Support for conditional document configurations (conditional compilation) • Support for content view filtering Standard and current version ASAM AE Container Catalog V3.0 Active workgroup members and speaker Bosch, MAN, Siemens VDO, XI-Works Speaker: Herbert Klein (XI-Works) Current activities Maintenance for V3.0 Solutions Guide 2007 SECTION TWO ASAM AE CC in the market Used in several bilateral software projects. A derivate of Container Catalog is also used as PDX in ODX Tools. Quality assurance Verification by several different and independent in house implementation of the participants. activity report from ASAM AE MDX (Meta Data Exchange Format) Description The increasing functionality in automotive systems requires distributed software development processes between car manufacturers and control unit suppliers, e.g. for powertrain control systems. This distributed development process needs a safe and reliable software integration scenario based on standardized exchange formats. From the automotive community’s perspective, a software integration flow is preferable where the functions creating OEMspecific added value do not have to be exposed to the project partners, and where integration for rapid design-space exploration is possible. This can be achieved in a scenario where automotive software functions are exchanged and integrated using object codes and MDX describes the needed interfaces of the functional blocks in the control unit software previously agreed on among the development partners. However MDX describes a multi-purpose format for data specifications of ECU (Electronic Control Unit) software which allows the exchange of data between vendor independent calibration, simulation, documentation, spreadsheet and data acquisition tools. MDX contains the following definitions: • Variables and Parameters • Base Types / Units / Data Constraints / System Constants • Classes • Computation Methods • Services MDX can describe all data constructions (measurements and characteristics) defined in the ASAM MCD-2MC V1.5.1 (excepting CUBOID) and additional things like structures.
eports from the workgroups activity report from ASAM AE MDX (con’t) Standard and current version ASAM AE MDX V1.0 Active workgroup members and speaker Bosch, MAN, XI-Works, Volkswagen AG Speaker: Herbert Klein (XI-Works) Current activities Maintenance for V1.0 Solutions Guide 2007 SECTION TWO ASAM AE MDX in the market Used in several bilateral software development projects as exchange format. Used, e.g. in XML Tools for Software functional data documentation tool. For details pleases see section of companies. Quality assurance Verification by several different and independent implementations of the participants. activity report from ASAM AE CDF (Calibration Data Format) Description The CDF V2.0 format describes a way how to exchange calibration data between different projects, project team members, suppliers and other involved parties. It allows to exchange data between vendor independent calibration, simulation, documentation, spreadsheet and data acquisition tools. All data are stored as physical values described in common data types of the automotive area. Especially supports CDF V2.0, all data constructions defined in the ASAM MCD-2MC V1.5.1 (excepting CUBOID) and is compatible to ASAM MDX V1.0 standard. Additionally, CDF V2.0 supports Quality Meta Data and Process Meta Data to describe not only the values of a calibration, but also its states in the development process. This allows to document and transfer quality decisions made at calibration time. CDF V2.0 is based on the earlier PaCo format created by the MSR group. As ASAM e. V. integrated the MSR standards in its own portfolio it was necessary to combine it with the existing ASAM CDF V1.0 standard. The result is the CDF V2.0 standard. The integration of CDF V2.0 into products is easy. The XML based format can be parsed by standard plug-ins. A reference and a user’s guide with detailed description and interpretation hints and example files covering all types of data objects are included in the standard. • Worldwide use possible as all data types used by the different automotive companies are covered • Quality Meta Data transfer with standardized values • Supported by the main measurement and calibration tools • Standardized and maintained by ASAM • Free of license fees • Easy XML based format 13
Page 3 and 4: table of contents SECTION ONE Forew
Page 5 and 6: association for the standardisation
Page 7 and 8: Solutions Guide 2007 SECTION ONE as
Page 9 and 10: eports from the workgroups activity
Page 13: eports from the workgroups activity
Page 23 and 24: ASAM standards portfolio 2007 i ASA
Page 25 and 26: quality & productivity improvements
Page 27 and 28: ODX-BEST2-Converter supporting migr
Page 29 and 30: measuring and analysis of vibration
Page 31 and 32: ILM (information lifecycle manageme
Page 33 and 34: supplier independent configuration
Page 35 and 36: PUMA open testbed automation system
Page 37 and 38: ASAM GDI Filling i Summary Challeng
Page 39 and 40: ASAM GDI Filling vi Solutions Guide
Page 41 and 42: managing vehicle test data with ASA
Page 43 and 44: Solutions Guide 2007 platform indep
Page 45 and 46: Solutions Guide 2007 ASAM ODS matur
Page 47 and 48: directory of members & ASAM related
Page 49 and 50: AFT Atlas Fahrzeugtechnik GmbH Gewe
Page 51 and 52: ASAM related products and services:
Page 53 and 54: executes them in Real time on the t
Page 55 and 56: Solutions Guide 2007 SECTION FIVE d
Page 57 and 58: Solutions Guide 2007 SECTION FIVE d
Page 59 and 60: HighQSoft GmbH Findingstrasse 17 86
Page 61 and 62: Email: Ralf.Winkelmann@imc-berlin.d
Page 63 and 64: Solutions Guide 2007 have been invo
Page 65 and 66:
Kayser-Threde GmbH Perchtinger Stra
Page 67 and 68:
M&K GmbH Annaberger Str. 240 09125
Page 69 and 70:
SECTION FIVE electronics testing in
Page 71 and 72:
Solutions Guide 2007 SECTION FIVE d
Page 74 and 75:
72 RA Consulting GmbH Zeiloch 6a 76
Page 76:
74 Company description: Re-Sol supp
Page 80 and 81:
78 SMART Electronic Development Gmb
Page 82 and 83:
Sontheim Industrie Elektronik GmbH
Page 85:
ASAM related products and services:
Page 88 and 89:
SECTION FIVE Supported ASAM Standar
Page 91 and 92:
Solutions Guide 2007 SECTION FIVE d
Page 93 and 94:
a member reference by keyword index
Page 95 and 96:
member reference by keyword index d
Page 97 and 98:
member reference by keyword index e
Page 99 and 100:
member reference by keyword index l
Page 101 and 102:
member reference by keyword index t
Page 103 and 104:
member reference by standard index
Page 105 and 106:
glossary of key terms the standards
Page 107 and 108:
glossary of key terms d engineering
Page 109 and 110:
glossary of key terms p Object A co
show all

b - ASAM

Create successful ePaper yourself

Delete template?

Save as template?