Opened 6 years ago

Last modified 3 years ago

#5311 new defect

Bad behavior of FMUs exported from OM when stopTimeDefined is set to fmi2True

Reported by: jean-philippe.tavella@… Owned by: Lennart Ochel
Priority: normal Milestone:
Component: FMI Version: v1.13.0
Keywords: Cc: jose.evora@…

Description

Dear All,

I try to use FMUs exported from OM as FMU for co-simulation (FMI 2.0).
My Master code is DACCOSIM NG (https://bitbucket.org/simulage/daccosim) and this code usually invoke the primitive fmi2SteupExperiment() with the parameter stopTimeDefined set to fmi2True.
In this case, when getting the values of the variables along time, I only get constant values.
This bug can be avoided by not defining the "stopTime" but we would prefer the bug to be corrected in OM exporter.

Best.

Change History (5)

comment:1 by Francesco Casella, 6 years ago

Milestone: Future1.14.0

comment:2 by Francesco Casella, 5 years ago

Milestone: 1.14.01.16.0

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0

comment:3 by Francesco Casella, 4 years ago

Milestone: 1.16.01.17.0

Retargeted to 1.17.0 after 1.16.0 release

comment:4 by Francesco Casella, 4 years ago

Milestone: 1.17.01.18.0

Retargeted to 1.18.0 because of 1.17.0 timed release.

comment:5 by Francesco Casella, 3 years ago

Milestone: 1.18.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.