VECU-BUILDER to generate virtual ECUs

The image shows the tree types of virtual ECU which can be generated with the VECU-BUILDER.

VECU-BUILDER generates virtual electronic control units (ECUs) as functional mock-up units (FMUs) for automotive microcontroller software verification and validation of software-in-the-loop (SIL) setups. With a standardized FMI 2.0/3.0 co-simulation interface, it seamlessly integrates into existing testing toolchains and facilitates collaboration with suppliers and partners.

Your benefits

Save development time and costs

By removing dependencies and integration of FMUs into existing infrastructures and CX toolchains.

Collaborate easily

With an approach that balances broad compatibility with standards-based system architecture.

Elevate your ECU development

Realize the full potential of a virtualized approach with ongoing support from a global team.

VECU-BUILDER from ETAS

The diagram illustrates the process of ECU virtualization, including steps for converting physical ECU software into a virtual ECU. Highlights include simulated microcontroller, peripherals, and communication standards such as XCP and FMI. — Steps for compiling automotive software into standalone virtual ECUs for independent execution.

Features

Types of microcontroller vECUs

The effective creation of virtual ECUs and systems typically involves incremental development. Each vECU type is defined by a gradual transition from simulation-specific code to the complete production code intended for the target ECU(s). Types 1 to 3 are executable on standard PC architecture, independent of actual ECU hardware. This approach significantly accelerates ECU development by enabling faster simulations and simplifying debugging.

Type 1

A type 1 vECU contains only the application software (ASW) and, optionally, the runtime environment (RTE). It communicates at signal level, allowing testing and validation of application software early in the development cycle while hardware is still in development. These vECUs are also used for rapid control prototyping.

Type 2

In addition to the application software and the runtime environment, a type 2 vECU contains simulation-specific basic software (BSW). Communication takes place at both signal and bus network levels. This enables the testing of a broader range of application software across multiple connected vECUs.

Type 3

A type 3 vECU contains all software components not tied to the microcontroller hardware. This includes application software, runtime environment, basic software from the series controller, and additional application-specific components, such as a hardware security module (HSM) or operating system.
Type 3 vECUs are used for software integration and network testing.

Virtual ECU for fuel cell development

The graphic shows the development of a virtual ECU

ETAS empowers OEMs and suppliers to realize significant time and cost reductions in development cycles while increasing overall efficiency. This is a result of extensive third-party compatibility and tailored virtualization solutions. VECU-BUILDER is the system of choice to create virtual ECUs in the automotive and commercial vehicle industry, emphasizing seamless integration and standardized protocols.

Virtual ECU for fuel cell development

An OEM aimed to transition from HiL testing to SiL to exponentially increase simulation speed and overall testing efficiency, while preserving existing test cases. The challenges involved integrating the existing architecture with a vECU, including in-house AUTOSAR BSW and current HiL testing parameters. ETAS used the third-party compatibility of VECU-BUILDER to successfully generate a virtual ECU that is compliant with automotive and proprietary requirements. Existing tooling and parameters were integrated into a custom type 3 vECU. The closed SiL testing model successfully generated results 6 to 8 times faster than the previous setup.

SiL for smartphone vehicle access system

SiL for Smartphone Vehicle Access System

Overall testing effectiveness can be constrained by high cost and time limitations due to a complex and unsuitable heterogenous HiL setup. Moreover, creating a virtual ECU can be complicated by data from various sources, including third-party AUTOSAR BSW and non-AUTOSAR components, as our current use case shows.

The industry-leading flexibility of VECU-BUILDER allowed the integration of all heterogeneous software into an FMU. Chosen as most flexible supplier for meeting the customer's requirements, ETAS delivered an incremental building and debugging SiL model that reduced turnaround times from weeks to days and significantly lowered development costs.

Discover the world of VECU-BUILDER

ETAS Downloads

ETAS Download Center provides abundant information on ETAS Products and Solutions, in the form of flyers, brochures, technical articles, or manuals. You will also find hotfixes and software updates.

Download Center