AUTOSAR design skills for automotive applications
Automotive OEMs are developing electronic systems based on AUTOSAR to cope with the increasingly complex software in contemporary automobiles. AUTOSAR simplifies the development process and makes ECU software reusable. Since the launch of AUTOSAR in 2004, this innovative cutting-edge technology has been tested in many research projects; now, AUTOSAR has begun to enter the real realization stage through the production of ECU. AUTOSAR software represents the current technical level, and through continuous version updates to ensure continuous technological progress.
The automotive industry is facing a new era. More and more complex automobile functions make the development of automobile electronics more and more complicated. The customer's functional and personal requirements for the product, as well as the increase in non-functional requirements such as diagnostics, have further aggravated the complexity of the ECU development process. Cars, especially high-end luxury cars, have more than 1,000 software functions, several in-vehicle bus networks, and more than 70 ECUs. Due to the diversity of hardware platforms in the automotive electronics field, ECU software development relies heavily on hardware and system configuration. Each change of the relevant constraints will lead to re-programming or modification of the software.
In order to reduce the complexity of ECU software development, AUTOSAR development members provide a set of proven software architecture, which is used as the basis for developing reusable applications. AUTOSAR, an open system architecture standard, was jointly developed by automotive OEMs, component suppliers, and companies in the software, semiconductor, and electronics industries worldwide. AUTOSAR allows users to avoid increasing development costs due to the use of proprietary solutions.
AUTOSAR divides the electronic architecture into several layers and modules. While defining the interface, AUTOSAR also defines software components and hardware platform standards that are easy to exchange. The AUTOSAR development members not only provided specifications for basic software modules, but also provided methods for developing distributed system applications. This approach starts with model-based software and distributed system descriptions, and ends with automatic code generation and repeatable testing. This method simplifies the use of tool chains.
Three years after the introduction of AUTOSAR, AUTOSAR development members released version 2.1 in 2007. At this time, the development of AUTOSAR reached a stable stage. Several different development projects tested the usefulness of AUTOSAR. In the commercial field, the "AUTOSAR Evaluation System" has been completed. Now, AUTOSAR is ready to enter the product ECU.
In order to achieve the goal of AUTOSAR, that is, the separation between the application program and the basic module, automotive electronics is abstracted into several layers. The connection with the actual microcontroller, which is the physical foundation, is abstracted to the microcontroller abstraction layer for mapping the functions and peripheral interfaces of the microcontroller. The microcontroller abstraction layer defines the memory interface, I / O driver interface and communication connection interface, and can also simulate some functions that cannot be provided by the microcontroller. The second layer is the ECU Abstract Layer (ECU AbstracTIon Layer). This layer provides peripheral device drivers for the ECU based on the ECU related hardware. The third layer is the Services Layer. This layer provides various services, such as network services, memory management, network communications, and operating systems. The service layer is largely independent of the hardware system. The RTE of the fourth layer truly realizes the separation between the application program and the basic software. RTE is responsible for handling application integration and data exchange between applications and basic software modules. The existence of RTE is the basis for realizing application reuse. Because RTE pre-defines the relevant interfaces, developers can develop application software without knowing the hardware, and apply this software to any ECU that complies with AUTOSAR standards.
Virtual Function Bus (Virtual FuncTIonal Bus) forms the basis for the configuration of these layers. Through this virtual bus, all automotive electronic communication components can be abstracted while using predefined ports; for the virtual function bus, there is no difference between ECU internal communication and external bus communication. This difference will not be reflected until the system layout and the specific functions of the ECU are finalized. The software components themselves are not concerned about this distinction, so we can develop the software components independently. The software component is divided into several executable units, namely running entities. When a specified event occurs, a corresponding running entity will be triggered. Such an event may be a new sensor signal, or it may be a periodic timing. From the perspective of virtual function bus, the formal description of the electronic system finally defines the interface of related software components. Therefore, the development of application software can be independent of the specific ECU.
RTE enables access to I / O, memory, and other basic services. Using model-based descriptions, RTE can be customized for specific ECUs, which can adapt to different needs and save resources.
method
While defining the ECU software architecture, the AUTOSAR standard also defines the method of developing the AUTOSAR system. Compliance with the confirmed development process is an important prerequisite for developing software. The shortcomings in the requirements list will be discovered early in development. The reuse of software components simplifies the development process and makes the entire system more reliable. However, this approach also allows a certain degree of freedom: for example, users can decide whether to use a top-down or bottom-up development process.
The purpose of AUTOSAR is to provide general support for the software development process through tools. Mature tools are used for the structural realization of requirements and corresponding management, while establishing corresponding configurations.
The first step consists of formal descriptions of three main aspects: software (software components), ECU (ECU resources) and system constraints. Appropriate editing tools for creating complete system descriptions
The system configuration serves as the basis for the ECU configuration, and users can use the configuration tool to generate basic software components based on the ECU configuration. At the end of the development process, there are multiple generation tools that can be used to generate RTE and basic software. All design and configuration data in the development process are saved in a unified file format. To this end, AUTOSAR defines a file format based on XML. On the one hand, the unified file format ensures the universality of the development process; on the other hand, it simplifies the seamless integration between development tools.
transplant
The software architecture of AUTOSAR is not a single module, it contains a large number of standard modules with complete interface definitions. This makes it very easy to transplant AUTOSAR, even if it is transplanted between projects; in addition, you can use both standard AUTOSAR modules and proprietary software modules within a project.
In order to achieve such a transplantation work, we must first compare the existing software architecture with the AUTOSAR architecture. By analyzing overlapping functions and integration options, it is decided which modules can be retained and which modules should be replaced by standard software modules.
Therefore, it is a very wise choice to introduce a separation layer between the application and the basic software. One possible method is to prepare the application and AUTOSAR software components early in the migration process and integrate them through RTE. Under RTE, a dedicated modification layer is used to provide an interface to existing basic software, as shown in Figure 3.
If part of the existing basic software needs to be replaced by AUTOSAR basic software, then the focus is on using unified tools. Vector provides suitable tools that can be used to configure proprietary software modules. Non-AUTOSAR modules can be gradually replaced by AUTOSAR modules, thereby avoiding the risk of overthrowing the entire architecture or the huge workload of rewriting the modules.
prospect
The release of AUTOSAR 3.0 marks the further improvement of the AUTOSAR standard. The companies involved in the development of the standard promised to make continuous efforts to achieve the AUTOSAR goal. Various ideas currently introduced will be implemented in the future 4.0 version of AUTOSAR.
Tool suppliers have also put forward some ideas related to AUTOSAR. Vector's AUTOSAR development team is working on making AUTOSAR-based ECU development more convenient and easier. A typical example is a test tool for AUTOSAR application components running on a PC. This tool can also be used as a simulation environment for ECUs that conform to the AUTOSAR standard. This makes it easier to test the implementation code of AUTOSAR software components on a PC. Widely used standardized tools (such as Vector's CANoe) can be used for test implementation, visual testing, and generating test reports. Vector utilizes a full set of AUTOSAR basic software components and a common design and development tool chain to support the entire development process
Vector's AUTOSAR solution has been actually verified in several projects. At the same time, mature products that conform to AUTOSAR 2.0 and 2.1 have been verified (products that conform to AUTOSAR 3.0 will be available in the second quarter of 2008).
to sum up
AUTOSAR is becoming a reality. Many OEMs plan to use AUTOSAR in the next models. Vector provides a complete solution for AUTOSAR, including AUTOSAR software components and development tools. This not only supports the development of pure AUTOSAR systems, but also supports the gradual transplantation of existing systems to AUTOSAR.
Introduction
SCOTECH manufactures a full range of oil immersed power transformers including generator step up transformer, substation step down transformer, mobile Substation Transformer and other different types, our maximum capacity and voltage is up to 300MVA 330KV, with the advanced design and thorough quality management system, we had become one of the most reliable Power Transformer manufacturers in China. we do not compromise on the quality, we ensure that each one of our delivered units has passed the most strictly testing and that makes us confidently to provide the longest quality warranty to our customers. We export our power transformers to all major global markets.
Scope of supply
SCOTECH`s oil immersed power transformers Including generator step up transformer, substation step down transformer, Mobile Substation Transformer and other different types.
Voltage level: 132KV, 230KV, 330KV.
Rating level: up to 300MVA
Standards
SCOTECH`s oil immersed power transformers are designed and manufactured in accordance with all major international standards (IEC, ANSI, UL, CSA etc.)
Why SCOTECH
Long history- Focus on transformer manufacturing since 1934.
Technical support – 134 engineers stand by for you 24/7.
Manufacturing-advanced production and testing equipment, strict QA system.
Perfect service-The complete customer service package (from quotation to energization).
230Kv Power Transformer,230Kv Electrical Power Transformer,Power Transformer Up To 230Kv,230Kv Step Up Power Transformer
Jiangshan Scotech Electrical Co.,Ltd , https://www.scotech.com