Keep the existing firmware project
Build the VECU from an existing CMake project instead of maintaining a separate simulation project structure.
Back to / Development Tools
Virtual ECU and SIL Simulation Tool
KITE VECU
Released Version 0.18.0
KITE VECU combines firmware builds, virtual ECU execution, multi-ECU signal exchange, and live observation in one SIL workspace, shortening the path from source code to repeatable simulation.
KITE VECU engineering workspace
Overview
From firmware projects to virtual ECU execution
KITE VECU creates or opens a simulation workspace, builds a VECU DLL from an existing CMake project, and can also load a prebuilt DLL or import an FMU. Engineers then configure Systems / ECU, Variables, ECU Signal Wiring, the Data Exchange Pool, CAN, and peripheral interfaces to run SIL scenarios, observe signals, and compare module behavior from one workspace.
ID · ki-vecu
Cross-ECU Data Exchange Pool and signal mapping
KITE VECU
Multiple model entry paths
Choose source project, prebuilt DLL, or FMU based on the available artifact, and export an FMU from the workspace.
Repeatable SIL scenarios
Standardize test operation with Start, Pause, Stop, Step, Restart, and scenario management.
Observable data flow
Keep ECU signals, shared data, peripheral interfaces, plots, and dashboards in the same execution context.
Live visualization of execution results
Place simulation signals in gauges, labels, progress bars, tables, plotters, and custom dashboards so test state and trends stay visible.
Screen 01 / 01
Dashboard, live signals, and trend plots
Compose a test dashboard from gauges, progress bars, signal tables, and plotters to review VECU state and signal changes in one place.
Product Highlights
The engineering workspace covers workspace creation, CMake / Ninja build output, VECU DLL loading, FMU import, and FMU export.
The execution toolbar provides Start, Pause, Stop, Step, Restart, Build, Rebuild, and Reload DLL actions.
The workspace includes Variables, Systems / ECU, ECU Signal Wiring, the Data Exchange Pool, Pool Monitor, CAN Bus, Module Diff, and CAN Fault Injection.
Core Capabilities
Workspace and build
Create or open a workspace, select a CMake project, set the build directory and VECU output, then inspect build status in the output panel.
DLL / FMU and SIL control
Attach a prebuilt DLL, import or export an FMU, and control the virtual ECU with Start, Pause, Stop, Step, and Restart.
Variables and Module Diff
Search, observe, and change variables while comparing variable and behavior differences between modules or versions.
ECU Signal Wiring
Create input/output connections across Systems / ECU so multiple VECUs share an inspectable signal topology.
Data exchange and peripherals
Configure pools, spaces, read/write mappings, DBC, and CAN, LIN, Ethernet, SPI, I2C, FLS, EEP, DIO, ADC, PWM, ICU, and OCU interfaces.
Dashboard and fault injection
Use gauges, tables, plotters, control widgets, and CAN Fault Injection to build an interactive validation view.
KITE VECU workflow
Load engineering artifacts, configure multi-ECU data exchange, run SIL scenarios, and review observations within the same workspace.
1
1. Create or open a workspace
Select an existing CMake firmware project, a prebuilt VECU DLL, or import an FMU.
2
2. Build and load the VECU
Set the build directory and output, run Build / Rebuild, confirm the DLL is loaded, then reload or export an FMU when needed.
3
3. Configure ECUs and scenarios
Create Systems / ECU, signal wiring, the Data Exchange Pool, CAN / peripheral mappings, and repeatable test scenarios.
4
4. Run, observe, and compare
Start or step through SIL execution and inspect results with Variables, Dashboard, Plotter, Pool Monitor, Module Diff, and fault injection.
Engineering tasks it fits
Designed for development and validation teams that need to verify ECU software, control logic, cross-ECU data exchange, and test scenarios before vehicle or hardware testing.
Early ECU software integration
Build and run firmware before target hardware is available to inspect initialization, variables, and control flow.
Multi-ECU co-simulation
Connect multiple VECUs through Signal Wiring and the Data Exchange Pool to inspect cross-module data flow.
Control-logic regression
Use reusable scenarios, step execution, and dashboards to standardize test operation and observation.
FMU model integration
Bring an existing FMU into the workspace or export VECU work as an FMU for another simulation environment.
Communication and peripheral fault analysis
Configure CAN, DBC, and peripheral mappings, then use Pool Monitor, Module Diff, and CAN Fault Injection to locate behavior differences.
Supported Formats & Standards
CMake firmware project CMake / Ninja build VECU DLL FMI / FMU import and export SIL CAN / CAN FD DBC LIN / Ethernet SPI / I2C FLS / EEP DIO / ADC / PWM / ICU / OCU KITE .kpkg plugins