Cannot set discrete inputs for Co-Simulation FMU

[anatoly.trosinenko@…]

When building CS FMU version 2, I cannot set Integer and Boolean inputs between steps. FMU Checker cannot pass input csv to the model too.

How to reproduce

1. Set up the following FMU generation parameters
   • Version: 2.0
   • Type: Co-Simulation
2. Build the following test model to FMU:

   model DiscreteInput
     input Integer int;
   end DiscreteInput;
   

3. Pass the following input to this FMU using FMU Checker ver. 2.0.3

   "time","int"
   0.0,0
   0.1,1
   0.2,2
   

   fmuCheck.linux64 -l 6 -i input.csv DiscreteInput.fmu
   

What is expected

The FMU passes validation.

What really happens

An error occurres when setting Integer inputs:

[FMU][logStatusError][FMU status:Error] fmi2SetInteger: Illegal call sequence. fmi2SetInteger is not allowed in Continuous-Time Mode state.

See the log attached for details.

[anatoly.trosinenko@…]

Error log

[Adrian Pop]

Lennart, can you have a look at this?

[Lennart Ochel]

Does that mean fmi2SetInteger is allowed to be called in continuous-time mode?

[Adrian Pop]

Yes, in between fmi2DoStep. See:
​https://svn.modelica.org/fmi/branches/public/specifications/v2.0/FMI_for_ModelExchange_and_CoSimulation_v2.0.pdf
Figure 11, for inputs and tunable parameters.

[Lennart Ochel]

I've just pushed a workaround. Please verify (e.g. using tomorrows nightly build) if it actually helps.

[anatoly.trosinenko@…]

I will check it slightly later, but as far as I remember, it was failing not only for Integers, but also for Booleans and Strings

[mirko.dangelo@…]

I checked. It works now for Integers but it fails for Booleans and Strings.

[Lennart Ochel]

We can do the same workaround for those types as well until we have a proper implementation of the call sequence logics for CS and ME.

[mirko.dangelo@…]

It would be perfect since I'm also using Booleans and Strings.

[Lennart Ochel]

It should work now: ​OMCompiler#1674