masoudnajafi

@KarlWernersson : The value MaximumCommunicationStep is usually variable and may varies as a function of the FMU inputs. So this value cannot be retrieved after DoStep. It should be retrieved...

[Maximum Communication Step Size.docx](https://github.com/modelica/fmi-standard/files/3206205/Maximum.Communication.Step.Size.docx)

Following the discussion in the Renningen Design meeting, what should I do next for this ticket? Could I add the API to the header files?

I updated the proposal (proposal_nextmaxcommstep_rev3.docx). Please let me know what should I do next? Thanks Masoud [proposal_nextmaxcommstep_rev3.docx](https://github.com/modelica/fmi-standard/files/3944182/proposal_nextmaxcommstep_rev3.docx)

FCP_019_Maximum_Communication_Step_Size was created.

Yes, I made it smaller and much easier to implement from importer's point of view. As far as I know, it should be possible to implement in 3.1.

If You handle constraints and do not throw them away and ensure that you do not have drift, you need not use this API. But In some cases there are...

@TorstenBlochwitz The change in Event-mode can already be done in FMI-2. But that slows down the simulation a lot. Furthermore, for the constraint correction purpose, the change in continuous-time states,...

I have no objection with adding this bullet to the FMI-3.0, but I would like to highlight that this is not the intention of this issue. As I explained above,...

The main motivation behind this proposal is to avoid state-event detection conflict between the solver and the FMU. As a very simple example, suppose that an event-indicator (with previous positive...