To adeptly replicate Electronic Control Unit (ECU) behavior, you need a powerful tool for automotive development and testing. A recommended methodology for virtualizing ECUs in vehicles relies on a systematic process, emphasizing the benefits of early testing through adherence to the four layers of the Classic AUTomotive Open System ARchitecture (AUTOSAR) architecture, spanning from application to microcontroller abstraction. This white paper outlines crucial steps, including application modeling and virtual ECU (vECU) simulation using NI VeriStand and Synopsys’ Silver software.
Most ECUs adhere to a well-defined architecture (See Figure 1) established by AUTOSAR, which is a standardized software architecture developed collaboratively by automotive manufacturers, suppliers, and other stakeholders. It provides a common platform for the development, integration, and management of software in modern vehicles. AUTOSAR aims to address the increasing complexity of automotive electronic systems by defining a standardized framework for software architecture, application interfaces, and communication protocols.
This open and standardized approach allows different automotive software components from various suppliers to work seamlessly together, fostering interoperability and scalability. AUTOSAR promotes reusability of software modules, making it easier for automotive companies to develop and maintain software across different vehicle models and electronic control units. This results in more efficient development processes, shortened time to market, and improved overall system reliability in the automotive industry.
Figure 1: AUTOSAR ECU Layered Architecture
As depicted in Figure 1, the AUTOSAR architecture consists of four layers endowing an ECU with capabilities. Leveraging this architecture in ECU simulation facilitates the early validation of features, eliminating the necessity to wait for the physical ECU, thus expediting the testing process.
To gain a better understanding of the purpose behind each layer, let’s delve into the ultimate tasks of each one of the four layers of the AUTOSAR Classic platform architecture.
In a more detailed exploration of these layers, it becomes evident that the application layer plays a pivotal role by encapsulating the core functionality of the ECU. Leveraging the code within this layer, we can accurately simulate our vECU.
To achieve accurate simulation of a vECU, a structured approach is essential (see Figure 2). Therefore, carrying out the following key steps, we can achieve our objective.
* ISOLAR-A and ISOLAR-B refer to software tools by ETAS for developing embedded software in automotive ECUs. They aid in creating AUTOSAR-compliant software, standardizing architectures for improved scalability and interoperability. For the latest details, consult ETAS official documentation or contact them directly.
The visual representation below summarizes the recommended process for ECU virtualization. To guide you through each step, we have highlighted NI’s recommended tools in bold. Additionally, each step lists other widely used tools that can be considered for the respective processes. This structured approach aims to enhance clarity and assist in making informed decisions when implementing ECU virtualization.
Figure 2: Virtual Validation Process
Therefore, by following these well-defined steps, we can effectively and efficiently simulate any vehicle ECU behavior, offering a powerful tool for automotive development and testing, saving time, and shifting left in the testing process.