Matthias Blesken

> Regarding: https://modelica.github.io/fmi-guides/main/fmi-profiles/#_basic_hil_sensor_hil_profile > > I propose to move "Scheduled Execution Interface" from required to optional. Agreed. Let's do it. > > "New Integer Types" have to be supported anyway,...

**Why is there a separate "Sensor Profile"?** It could be confusing. For example "OSI-encoded sensor data via binary variables" is an important use case on HIL simulators, too. (Of course...

> "New Integer Types" have to be supported anyway, we can remove this. (#44)

**Why limit it to "SIL"? What's the difference for "HIL ECU profile"?**

Actually if this is about " .. integration of multi-ECU networks" bus access should be supported (**i.e. the ls-bus**). And a ECU sw developer would most likely expect that he/she...

Without having read the discussion before I suggest that once https://github.com/modelica/fmi-standard/pull/1546 is done and hopefully lead to a much clearer explanation of SE in the standard itself the need and...

> Move to optional: > > * resizable Inputs/Outputs : For most tools, changing the IO during runtime is impossible and we are calling this "Basic" which is, in my...

**Why "Binary FMUs for Desktop Platforms" and "... intended mainly for desktop simulation uses"?** (typo by the way) - This is a very basic profile in general. It could be...

> @MBlesken : can you close this issue? @andreas-junghanns Hm, I don't think that @pmai and I have the same opinion on that section (> That is already what that...

> Proposal from design meeting 2022-06-27: > * Remove String I/O (-> binary I/O is likely enough) Good.