Dear CarMaker Team,
I am running into an issue using an FMU plug-in for the HV Battery model class together with CarMaker for Simulink, and would appreciate your guidance.
I have developed a HV battery model in Simulink and exported it as a Co-Simulation FMU (solver ode1, fixed step 0.001 s, “Treat each discrete rate as a separate task” unchecked). The FMU is registered as a plug-in for the HV Battery model class in my vehicle dataset. Hardware implementation is Intel x86-64 (Windows 64) for both the FMU and the CarMaker for Simulink interface.
In standalone CarMaker the FMU runs correctly and produces the expected dynamic response. Under CarMaker for Simulink co-simulation, however, the FMU’s outputs flatline: the current input arriving at the FMU sits at zero, no voltage is produced, and no power flows. The model integrates (SoC and energy outputs drift consistently with zero current), but the electrical path is dead.
Exporting the FMU from either the src or src_cm4sl project directory makes no difference to the CM4SL behavior. The Modelclass-specific Parameters set via the FMU plug-in dialog do not appear to reach the FMU at runtime. The Cfg* inputs arriving at the FMU (Capacity, Voltage, SOC_init, etc.) remain at the CarMaker defaults (10 Ah, 12 V, 70%) rather than the values I have configured. I observed the same behavior with a simpler test FMU plugged into the LV Battery model slot, which suggests a general disconnect between the Modelclass-specific Parameters mechanism and the FMU plug-in under CM4SL.
Is there a known issue or recommended workflow for using FMU plug-in battery models together with CarMaker for Simulink? In particular, is there a way to ensure (a) the powertrain current request reaches the FMU, and (b) Modelclass-specific Parameters are correctly passed to the FMU under co-simulation? I would be grateful for any guidance to help resolve this integration issue.
Best regards,
Sara