Christian Bertsch
Christian Bertsch
(from a discussion with Pierre) We should better explain, under which conditions and for which use cases to use SE (e.g. realtime conditions on a HiL system with mutliple vECUs...
It would be nice to get sim-vicus listed on https://fmi-standard.org/tools/ Even better would be participation in the FMI Cross-Check https://github.com/modelica/fmi-cross-check
see https://github.com/modelica/fmi-standard.org/blob/main/CONTRIBUTING.md#updating-the-tools-list For the examplesURL you are encouraged to provide a link to a webpage or repo where you document how you tested your tool w.r.t to FMI support. So...
(moved from https://trac.fmi-standard.org/ticket/398; reported by Lausdahl) The FMU Checker seems to be missing the semantics checks from the standard and thus not reporting any error for modelDescription.xml which contain obvious...
(moved from https://trac.fmi-standard.org/ticket/389; reported by: lausdahl) The FMUChecker does not check if the FMU respects the FMI standard concerning the fmuResourceLocation URI for the instantiate call. The check must check...
I would like to encourage you get listed on the FMI tools page https://fmi-standard.org/tools/, see https://github.com/modelica/fmi-standard.org/blob/main/CONTRIBUTING.md#updating-the-tools-list.
see "problem 1" in https://github.com/modelica/FMI-Tools-Forum/issues/3#issuecomment-2072321649
providing a matching rule is mandatory, see There might be use cases where one does not want one of the predefined matching rules to be applied, see https://github.com/modelica/fmi-ls-struct/issues/8
Discussion came up in https://github.com/modelica/fmi-ls-struct/issues/6
Currently it points to FMI 2.0.3 and FMI 3.01 is missing: 