Virtual validation is reshaping how the automotive and aerospace industries develop and test electronic control units. As software complexity grows and development timelines tighten, the industry is under increasing pressure to shift testing earlier in the process, long before physical hardware is ready. Software-in-the-loop (SIL) testing has emerged as the go-to method for validating ECU functionality in a virtual environment, giving both OEMs and suppliers the ability to catch issues faster and at lower cost.
The problem is that today’s SIL ecosystem is deeply fragmented. Suppliers are forced to maintain multiple proprietary adapter chains, adopt OEM-specific tool chains, and navigate incompatible V-ECU formats, all just to deliver a virtual component that works in one customer’s simulation environment. The result is wasted engineering effort, integration friction, and collaboration bottlenecks that slow down entire programs.
A standardized solution has been missing for too long. The FMI Layered Standard for Network Communication, known as FMI-LS-BUS, directly addresses this gap. Built on top of the well-established FMI 3.0 standard and developed with contributions from dSPACE, Bosch, ETAS, AVL, Synopsys, and others, it enables bus simulations with Functional Mock-up Units (FMUs) in a tool-agnostic, reproducible way.
This whitepaper from dSPACE explains what FMI-LS-BUS is, how it works, and why it represents a structural shift in how OEMs and suppliers exchange and validate virtual ECUs.
You will learn:
- Why fragmented SIL tool chains are costing OEMs and suppliers significant time and money
- How FMI-LS-BUS standardizes bus communication simulation across CAN, FlexRay, LIN, and Ethernet
- Where the High-Cut and Low-Cut abstraction levels apply in the development cycle
- How suppliers can deliver OEM-independent V-ECU FMUs without adopting proprietary tool chains
- Why standardized FMUs act as executable contracts between OEMs and suppliers
- How FMI-LS-BUS supports continuous integration and automated regression testing
- What the current development roadmap looks like and which bus systems are already supported
- How dSPACE SystemDesk and VEOS integrate FMI-LS-BUS into a complete SIL tool chain
- Which system compositions the standard supports and when to use each
- How reusable FMUs reduce variant management costs across multiple OEM programs
Strategic Insight: Standardization Is the Real Competitive Advantage in Virtual Validation
The automotive development landscape is moving fast toward model-based, software-defined vehicles. SIL testing has become central to this shift, but the absence of a common standard for virtual ECU exchange has created a hidden tax on every OEM-supplier relationship. Engineers spend time on integration workarounds instead of engineering value. Programs slow down not because of technical limitations, but because of interface friction.
FMI-LS-BUS changes the equation. By defining how FMUs communicate over simulated bus networks, it creates a shared technical foundation that both sides of the supply chain can build on.
1. The SIL Integration Problem Is Bigger Than It Looks
Today’s SIL workflows require suppliers to either adopt the OEM’s entire tool chain or build and maintain extensive adapter solutions for each customer. When formats differ or proprietary extensions create incompatibilities, the resulting integration problems are costly and time-consuming to resolve. Multiply this across multiple OEM programs, and the overhead becomes a serious drag on development velocity and profitability.
2. One Standard, Three System Compositions
FMI-LS-BUS supports three distinct system compositions, from simple direct two-FMU connections to fully featured bus simulation via a dedicated bus simulation FMU or a simulator with integrated bus logic. What makes this powerful is that the same standardized FMU works across all three compositions without any changes to the FMU itself. This gives both tool vendors and end users the flexibility to match simulation fidelity to the development phase.
3. High-Cut and Low-Cut: Right Tool for the Right Phase
The standard introduces two abstraction levels that map directly to where a project is in its lifecycle. High-Cut models communication at the signal level and is ideal for early architecture and function validation, without needing a full COM stack implementation. Low-Cut operates at the message level, supporting realistic timing, arbitration, fault injection, and full AUTOSAR COM stack testing. Together, they cover the entire development arc from concept to validation.
4. Reusability and Variant Management at Scale
Because FMUs are containerized, versionable artifacts built on an open standard, they can be reused across vehicle lines, projects, and OEM customers. Suppliers who invest in FMI-LS-BUS-compliant FMUs build a reusable library of verified components that reduces marginal costs per variant and shortens change cycle times.
5. CI/CT Automation Becomes Realistic
One of the most significant but underappreciated benefits of FMI-LS-BUS is what it unlocks for automation. With clearly defined interface semantics and a bus-agnostic standard, nightly regression tests, bus conformance checks, latency measurements, and robustness tests can all be automated in CI/CT pipelines regardless of whether the OEM uses an in-house simulation environment or a third-party SIL platform.
Addressing the Challenges of Implementation
Moving to a standardized virtual validation approach requires more than technology. Organizations need to align internally on how V-ECU deliverables are defined, versioned, and governed. Teams accustomed to proprietary workflows will need to adapt processes and tooling. The standard itself is still maturing, with FlexRay support in beta and Ethernet in alpha as of the current release. Keeping pace with the development roadmap and participating in the broader FMI community will be important for early adopters who want to influence how the standard evolves.
How to Get Started
Organizations looking to adopt FMI-LS-BUS should start by auditing their current V-ECU exchange processes to identify where proprietary dependencies create the most friction. From there, assess tool chain readiness, particularly whether your SIL simulator already supports FMI 3.0. dSPACE’s SystemDesk and VEOS already support key parts of the standard, providing a practical entry point for teams working within the dSPACE ecosystem. Piloting with a single OEM relationship and a defined bus type, such as CAN, is a low-risk way to build internal confidence before scaling across programs.
Who Should Read This V-ECU Standardization Whitepaper?
This whitepaper is designed for engineering and product strategy leaders across the automotive and embedded systems space:
- ECU software engineers and SIL test architects
- V-ECU platform owners at Tier 1 and Tier 2 suppliers
- Simulation and virtual validation teams at OEMs
- Tool chain and systems integration engineers
- R&D and technology strategy leaders in automotive and aerospace
It is especially valuable for organizations managing V-ECU exchanges across multiple OEM programs and looking to reduce integration overhead while improving test coverage and delivery predictability.
Download FMI-LS-BUS Standard: Making V-ECUs OEM-Independent from dSPACE to understand how a single open standard can eliminate proprietary integration overhead, enable OEM-independent virtual ECU delivery, and accelerate SIL validation from early architecture design through to series production.
