Search Results

In-vehicle network communication is evolving faster speeds and higher performance capabilities, connecting the information possessed by ECU and sensors with the in-vehicle electronic systems which are continuing to develop. With the evolution of the complicated networks, it is becoming difficult to develop them without many verification of actual machine. On the other hand, as for the verification means required at the logic level or physical level for a network verification through ECU design, virtual verification in the whole vehicle is difficult due to speed increases and the sheer size of the system. Therefore, it is only applicable for systems which are limited to a domain or an area, and flexible and timely utilization would be difficult due to the changes in specifications.

Along with the evolution of vehicle electronic systems from independent control in each domain system to the integration control of the whole vehicle system, ECU systems have become increasingly complicated and large-scale. This has made it extremely difficult to develop the entire system coherently and efficiently from the functional level down to implementation level. On the other hand, the development methodology focusing on single ECU system used today has been facing an additional challenge because of increasingly strict requirements for safety design based on multi-ECU systems. To address these challenges, we have been working on developing virtual development of Engine ECU by modeling technology. In order to achieve optimum electronic systems, it is necessary to build many real devices and evaluate the performance of systems. However, it is also becoming necessary to build virtual devices because of the increasingly complicated and large-scale systems.

As automotive electronic systems aiming for a safe and secure automobile society continue to develop, the control specifications of the ECU are becoming increasingly complex. When attempting to validate control specifications that cooperatively control different control specifications, control specification developers must consider various validation viewpoints. They narrow down the validation viewpoints based on rules from past experience, describe timing charts, and validate the specifications. However, due to complicated specifications, empirical rules do not pass, and specification mismatches are often found after actual systems completion. On the other hand, a block diagram simulator is a tool to verify control specifications. Since these tools are aimed at modeling and verifying the system design, it is efficient to describe how to implement the system. However, first it is necessary to verify the consistency between the model and the specifications.