This includes the formal description and documentation of ECU software, the description of change requests, and blocksets for model-based software engineering. This includes APIs for programmatic access to sensor and actuator devices, The process of recording data from internal ECU memory and external sensors. Measurement and The process of ECU parameter tuning. Tests with ECU hardware and software in the loop are carried out. ECU internal variables and external sensor data is recorded and analyzed. The values of internal ECU parameters are determined as a result of this process.
|Published (Last):||5 January 2015|
|PDF File Size:||13.28 Mb|
|ePub File Size:||6.67 Mb|
|Price:||Free* [*Free Regsitration Required]|
History[ edit ] During the economic crisis at the end of the s and beginning of the s, the automotive industry was under high pressure to cut costs and to optimize their internal processes. One area identified for cost savings was the measurement and testing area for vehicle development. The equipment used there had been mostly purpose-built solutions, with widely incompatible interfaces and data formats , which severely impeded interconnectivity and exchange of data.
Unlike earlier standardization efforts, where standards were created by OEMs and unilaterally imposed on suppliers, ASAM had the goal right from the beginning to include suppliers in the standard development process as equal partners. This measure brought in their technological know-how and ensured that the standards are feasible and result in cost-effective products.
Since the number and importance of the standards grew steadily, ASAM e. First chairman came from DaimlerChrysler. First business manager was sent by BMW. Event hosted by GM in Detroit. BoD decision to freeze all standards at their current version for 18 month to help tool vendors to develop ASAM-compliant tools.
Non-members have to purchase standards to contribute to the costs of their development. Honda becomes first OEM member from Japan. The standard is proposed for transfer to ISO as part 4 of the standard. They mostly originate from the automotive industry , although ASAM does not limit the membership to this industry. The member companies can be broadly categorized into three major groups: End Users: OEMs and their suppliers, mostly applying tools and processes compliant to ASAM standards ASAM System Providers: tool vendors and service providers, implementing ASAM standards in tools or via engineering services Educational: universities and research institutions Members pay an annual fee, which is dependent on the number of their employees.
They gain free access to all ASAM standards and checker tools, and can use them for the development of tools or for providing engineering services. Furthermore, the membership allows to propose changes to existing standards or the development of new standards and to participate in their development. Typically, large companies such as OEMs and Tier-1s have a strong interest in standards, as they are used to displace proprietary or home-grown systems and make them more independent from specific tool vendors or costly, internal tool departments.
ASAM standards are an insurance for OEMs and Tier-1s that their investment in testing and development equipment is stable and can be reused for the long term. The standards allow them to sell products to a wide group of End Users without having to implement major product customizations. This minimizes development costs and maximizes profits. Those companies, who actively participate in the development of the standards, have an additional "first-to-market" advantage.
Nearly two-thirds of the ASAM members belong to this group. As a consequence, ASAM-compliant tools and engineering services are widely available.
According to an expert opinion, there are about products worldwide available just in the area of MCD-systems. ASAM is set up as an incorporated association. The structure allows the integration of new members in the existing organization. Each company has voting rights in proportion to their annual membership fee. The delegates elect the Board of Directors and the Technical Steering Committee for alternating two year terms. They furthermore accept the annual financial report, approve changes of the statutes and vote on any further decisions of strategic importance.
The Board of Directors BoD has operational control of the association, but is bound to the decisions of the membership meeting. The BoD consist of up to five members. The Board represents ASAM on all legal and public matters, is responsible for the finances of the association, decides on the admission or expulsion of members, sets guidelines for the other committees and the head office, develops a long-term strategy for the association and monitors its execution.
The committee consist of a maximum of 10 delegates from the ASAM community. The committee evaluates technical proposals, monitors the progress of ongoing projects, and reviews and releases new or revised standards. Those groups may be closed, which means that only those companies send members to the Project Group, who proposed the standard.
An open Project Group may also allow or invite further participants. Project Groups may work on the development of future versions of a standard FVD Projects , or they carry out maintenance tasks on a standard such as minor revisions or bug fixing Maintenance Projects.
Standards Creation Process[ edit ] Life cycle of an ASAM standard Members of the association initiate the development of new standards, or the extension or correction of existing standards. The process is started via an "Issue Proposal" to ASAM, which describes the desired goals, use-cases, technical content, estimated resources and a project plan. The proposal is publicized to all members for feedback. After a minimum of 6 weeks of discussion, the proposal and member feedback is presented to the TSC for evaluation and decision.
In case resources are secured and the proposal is accepted by the TSC, then the proposed project can be kicked off. A project can only start, if at least three member companies participate in the project group. ASAM provides the work infrastructure for the project team, i. The ASAM office assigns a maintenance project manager for maintenance projects, who controls and carries out the operative work for the project group.
Otherwise, the project team sets up its inner structure and working processes according to its own needs. Throughout the project term, the project members work on the standard through regular meetings, phone conferences or individual off-line work. Once the project team members determine that the standard is ready for release, they submit the deliverables for review to the TSC.
Deliverables may include documents, schemas, reference code and example files. The project leader presents the release at the TSC meeting. The ASAM office publicizes the release and makes the standard available for download for its members. They focus on the definition of communication interfaces between devices in the measurement, calibration, diagnostics and testing area. The standards cover processes and tool-chains in these areas and have the goal to reduce the development, integration and maintenance efforts for them.
ASAM standards cover specific use-cases and are developed according to the following guiding principles: Independence from Hardware and Operating System Use of object-oriented models Definition of semantics and syntax Independence from the physical storage of data Consequently, they are vendor- and technology-independent, which keeps system components of different origin interchangeable and decouples them from the continuous advances of IT platforms.
This secures investments in tools and processes for the long-term. ASAM uses common description methods for the technology definitions in the standards: Format description: defines syntax and semantics of a file format for the purpose of data exchange. API : defines the interface and functional behavior of executable routines for the purpose of calling service routines or exchanging data between computer programs.
Protocol definition: defines syntax, semantics and synchronization of the communication via a bus for the purpose of establishing a communication link between computer systems.
Technology reference: specifies a technology-dependent interpretation of the technology-independent parts of the standard, typically via mapping rules or program code. Application area companion: defines an extension of a base standard for a specific application area or a specific type of device.
Transport layer specification: defines how a generic protocol definition is to be interpreted using a concrete physical layer. ASAM has subdivided the standards into three groups, which are briefly described in the following tables:.
ASAP2 Tool-Set – Editing A2L Description Files Extensively and Easily
History[ edit ] During the economic crisis at the end of the s and beginning of the s, the automotive industry was under high pressure to cut costs and to optimize their internal processes. One area identified for cost savings was the measurement and testing area for vehicle development. The equipment used there had been mostly purpose-built solutions, with widely incompatible interfaces and data formats , which severely impeded interconnectivity and exchange of data. Unlike earlier standardization efforts, where standards were created by OEMs and unilaterally imposed on suppliers, ASAM had the goal right from the beginning to include suppliers in the standard development process as equal partners. This measure brought in their technological know-how and ensured that the standards are feasible and result in cost-effective products. Since the number and importance of the standards grew steadily, ASAM e. First chairman came from DaimlerChrysler.
ASAP2 STANDARD PDF
Measurement , The process of ECU parameter tuning. Tests with ECU hardware and software in the loop are carried out. ECU internal variables and external sensor data is recorded and analyzed. The values of internal ECU parameters are determined as a result of this process. This inclusion was a deliberate decision to keep all information to describe and access ECU data in one location.