This is a feature request related to a problem described below:
We are building Virtual ECU and Software-in-the-Loop (SiL) simulation environments that require standardized automotive network buses (CAN, LIN, Ethernet) and measurement/calibration interfaces. The FMI project defines these workflows under the FMI Layered Standards (FMI-LS) specifications (such as FMI-LS-BUS and FMI-LS-XCP).
Currently, fmu4cpp provides great support for standard FMI 3.0 Co-Simulation FMUs, but it lacks native capabilities to generate the necessary layered standard manifests and assets required to output fully compliant FMI-LS FMUs.
Hoping to have a solution like :
We would love to see fmu4cpp extend its FMI 3.0 export capabilities to natively support the packaging of FMI Layered Standards. Ideally, this would include:
- Manifest Support: C++ API builders/helpers to automatically generate and inject the required layered XML metadata files (e.g.,
fmiLsBus.xml or fmiLsXcp.xml) into the root of the FMU.
- Resource Packaging: Built-in utilities to target and bundle communication protocol description files (like
.dbc, .arxml, .ldf, or .a2l) directly into the FMU's resources/ folder.
- FMI 3.0 Variable Bindings: Clean code-generation abstractions to link network frames and physical signals to FMI 3.0 native Clocks, Terminals, and Binary variables for High-Cut and Low-Cut simulation abstractions.
Additional context
Adding this functionality would make fmu4cpp one of the premier open-source C++ frameworks, aligning it perfectly with the evolving FMI 3.0 ecosystem.
This is a feature request related to a problem described below:
We are building Virtual ECU and Software-in-the-Loop (SiL) simulation environments that require standardized automotive network buses (CAN, LIN, Ethernet) and measurement/calibration interfaces. The FMI project defines these workflows under the FMI Layered Standards (FMI-LS) specifications (such as FMI-LS-BUS and FMI-LS-XCP).
Currently,
fmu4cppprovides great support for standard FMI 3.0 Co-Simulation FMUs, but it lacks native capabilities to generate the necessary layered standard manifests and assets required to output fully compliant FMI-LS FMUs.Hoping to have a solution like :
We would love to see
fmu4cppextend its FMI 3.0 export capabilities to natively support the packaging of FMI Layered Standards. Ideally, this would include:fmiLsBus.xmlorfmiLsXcp.xml) into the root of the FMU..dbc,.arxml,.ldf, or.a2l) directly into the FMU'sresources/folder.Additional context
Adding this functionality would make
fmu4cppone of the premier open-source C++ frameworks, aligning it perfectly with the evolving FMI 3.0 ecosystem.