Revision history [back]

Hi, We are currently testing FMU integration in several environments (dymola, daccosim and fmpy).
FMU 2.0 don't run on daccosim and fmpy while it don't reach error on dymola. So we check the fmu with the tool FMUChecker which report the following error : "The StopTimeDefined parameter is set to 0. This is not valid. EnergyPlus FMU requires a stop time and will use the stop time 0.000000 which is provided" We generate the same energyplus model using FMU 1.0 standard and successfully check it with FMUChecker

So it seem that Energyplus translation on FMU 2.0 don't exactly respect the FMI standard

Do you have already experienced this error ?

M&A

Hi, We are currently testing FMU integration in several environments (dymola, daccosim and fmpy).
FMU 2.0 don't run on daccosim and fmpy while it don't reach error on dymola. So we check the fmu with the tool FMUChecker which report the following error : "The StopTimeDefined parameter is set to 0. This is not valid. EnergyPlus FMU requires a stop time and will use the stop time 0.000000 which is provided" We generate the same energyplus model using FMU 1.0 standard and successfully check it with FMUChecker

So it seem that Energyplus translation on FMU 2.0 don't exactly respect the FMI standard

Do you have already experienced this error ?

M&A

Hi, We are currently testing FMU integration in several environments (dymola, daccosim and fmpy).
FMU 2.0 don't run on daccosim and fmpy while it don't reach error on dymola. So we check the fmu with the tool FMUChecker which report the following error : "The StopTimeDefined parameter is set to 0. This is not valid. EnergyPlus FMU requires a stop time and will use the stop time 0.000000 which is provided" We generate the same energyplus model using FMU 1.0 standard and successfully check it with FMUChecker

So it seem that Energyplus translation on FMU 2.0 don't exactly respect the FMI standard

Do you have already experienced this error ?

M&A