Introduction
Software-in-the-loop (SIL) testing has become the default approach for validating ECU functionality before physical hardware is available. But underneath this shift lies a growing problem: virtual ECUs (V-ECUs) are deeply tied to proprietary OEM formats, tool chains, and bus simulation solutions. Every new OEM customer means new adapters, new integration cycles, and new costs — for both sides.
The FMI-LS-BUS standard changes that equation. Built as a layered extension of the established FMI 3.0 standard, and co-developed by dSPACE alongside industry partners including Bosch, ETAS, AVL, and Synopsys, it introduces a common, tool-agnostic interface for bus communication in virtual environments — covering CAN, FlexRay, LIN, and Automotive Ethernet. This whitepaper explains what FMI-LS-BUS is, why it matters, and what it means for OEM-supplier collaboration today.
You Will Learn
- Why current SIL workflows create structural inefficiencies for both OEMs and suppliers
- How heterogeneous tool chains and proprietary bus simulation lock-in drive up integration costs
- What the FMI-LS-BUS standard is and how it extends FMI 3.0 for bus communication
- The three system compositions FMI-LS-BUS supports and when each applies
- How High-Cut and Low-Cut abstraction levels serve different development phases
- Why the same FMU works across all three compositions without modification
- The concrete competitive and economic benefits FMI-LS-BUS delivers specifically for suppliers
- How IP protection and OEM transparency can coexist under the standard
- Where the standard stands today in its development roadmap
- How dSPACE SystemDesk and VEOS integrate FMI-LS-BUS into a complete SIL tool chain
Strategic Insight: Standardization Is the New Supplier Competitive Advantage
The Proprietary Trap Is a Real Business Risk
Today, suppliers routinely maintain multiple adapter stacks just to deliver compatible V-ECUs to different OEMs. Every proprietary format difference, every OEM-specific bus simulation API, and every undocumented extension translates directly into integration overhead, delayed approvals, and narrowing margins. The problem is not technical complexity alone — it is the absence of a shared contract between parties.
One Interface, Multiple OEMs — Without Rebuilding Everything
FMI-LS-BUS defines the interface semantics between FMUs and simulators: what variables exist, how they are clocked, and what they mean. This creates a stable, executable specification that suppliers can deliver once and validate across multiple OEM environments. The same standardized FMU runs across direct connections, dedicated bus simulation FMUs, and importer-embedded bus simulation — without any modification to the FMU itself.
Shift Left, Reduce Risk, Accelerate Acceptance
With High-Cut abstraction, suppliers can deliver testable architecture and function models early — before AUTOSAR stacks or full COM implementations are complete. Errors in interface design and data dependencies surface at the MIL/SIL stage rather than in expensive HIL campaigns. With Low-Cut abstraction, realistic protocol-level behavior, fault injection, and latency analysis become reproducible and auditable. Together, these two abstraction modes compress the validation lifecycle across all development phases.
Reuse, Variant Management, and Stronger Market Position
FMUs built on FMI-LS-BUS are containerized, versionable units that can be reused across vehicle programs, platforms, and OEM relationships. Suppliers who build proven reference FMUs under this standard gain the ability to offer them as high-quality, documented modules — reducing per-variant cost and strengthening their position in multi-customer development environments.
Governance and Challenges
The transition to standardized V-ECU exchange is not without friction. Organizations must align internally on new tooling, interface documentation practices, and test envelope governance. IP protection remains a sensitive area — defining the right level of transparency for black-box FMUs requires clear agreements between OEM and supplier teams. CI/CT integration demands upfront investment in test automation infrastructure. Teams accustomed to proprietary workflows will need time and change management to adopt the new model.
Implementation and Strategy
Adopting FMI-LS-BUS begins with identifying where proprietary V-ECU adapter chains create the most friction across your current OEM programs. From there, the path moves toward generating FMI-LS-BUS-compatible FMUs using tools such as dSPACE SystemDesk, validating them within SIL simulators like VEOS, and establishing CI/CT pipelines that treat FMUs as executable contracts. Engaging with the open development community on GitHub and the Modelica Implementers’ Guide accelerates the learning curve significantly.
Who Should Read This
This whitepaper is essential reading for ECU software engineers and system architects working on virtual validation, SIL/HIL test engineers managing OEM integration workflows, tool chain leads evaluating standardization strategy, and supplier-side technical program managers who deal with multi-OEM delivery challenges. It is equally relevant for OEM simulation engineers seeking to reduce V-ECU onboarding friction.
Download FMI-LS-BUS Standard: Making V-ECUs OEM-independent from dSPACE to understand exactly how this layered standard reshapes the economics of virtual ECU development and what it takes to implement it in your SIL tool chain today.
