Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question
1

Issues with multiple FunctionalMockupUnitImport:To:Variables for same FMU.

asked 2018-11-09 16:09:35 -0500

Stuart Dols gravatar image

updated 2018-11-09 16:21:33 -0500

I'm receiving the following errors when trying to perform co-simulation having more than one ExternalInterface:FunctionalMockupUnitImport:To:Variable for the same FMU in EP version 9.0.1.

 ** Severe  ** GetRuntimeLanguageUserInput: ExternalInterface:FunctionalMockupUnitImport:To:Variable, invalid entry.  
 **   ~~~   ** Invalid FMU File Name=ContamFMU.fmu  
 **   ~~~   ** Name conflicts with an existing global variable name  
 ** Severe  ** GetRuntimeLanguageUserInput: ExternalInterface:FunctionalMockupUnitImport:To:Variable, invalid entry.  
 **   ~~~   ** Invalid FMU Instance Name=ContamFMU  
 **   ~~~   ** Name conflicts with an existing global variable name  
 **  Fatal  ** Errors found in getting EMS Runtime Language input. Preceding condition causes termination.

It works fine in EP version 8.3 when I also include the variables as EMS:GlobalVariables.
Using only one variable works in 9.0. However, I must remove the EMS:GlobalVariables (I think EP 8.6+ automatically creates the globals from the EI:FMUI:To:Variable declarations).

 ExternalInterface:FunctionalMockupUnitImport:To:Variable,
   CX_IN_C_TV,              !- Name  
   ContamFMU.fmu,           !- FMU File Name  
   ContamFMU,               !- FMU Instance Name  
   CTRL_O_CtrlOut_C,        !- FMU Variable Name  
   0;                       !- Initial Value

 ExternalInterface:FunctionalMockupUnitImport:To:Variable,
   CX_IN_B_TV,              !- Name  
   ContamFMU.fmu,           !- FMU File Name  
   ContamFMU,               !- FMU Instance Name  
   CTRL_O_CtrlOut_B,        !- FMU Variable Name  
   0;                       !- Initial Value

Is this a bug, or am I missing something?
I can provide a fairly simple set of co-simulation input files if necessary.

- Stuart

edit retag flag offensive close merge delete

Comments

The function GetRuntimeLanguageUserInput() in RuntimeLanguageProcessor.cc is creating an ErlVariable for each alpha field of each ExternalInterface:FunctionalMockupUnitImport:To:Variable.

Therefore, the second ContamFMU.fmu filename conflicts with the first yielding the reported error.

This appears to be a bug.
I think EnergyPlus should allow more than one variable from a given FMU.

Stuart Dols gravatar imageStuart Dols ( 2018-11-15 12:57:19 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted
2

answered 2018-11-16 12:22:00 -0500

Thierry Nouidui gravatar image

This is a bug. A ticket has been opened to investigate the root cause of the problem https://github.com/NREL/EnergyPlus/is...

edit flag offensive delete link more
1

answered 2018-12-12 07:59:12 -0500

Stuart Dols gravatar image

In order to get around this issue one can use ExternalInterface:FunctionalMockupUnitImport:To:Schedule instead of ExternalInterface:FunctionalMockupUnitImport:To:Variable. EnergyPlus does allow multiple instances of the Schedule object.

edit flag offensive delete link more

Comments

@stuart-dols Could you checkout the branch below, compile and see whether it fixes the problem?

https://github.com/NREL/EnergyPlus/tr...

Thierry Nouidui gravatar imageThierry Nouidui ( 2019-02-23 13:24:07 -0500 )edit

Please tell me how to transition my test IDF to be compatible with this version.

Stuart Dols gravatar imageStuart Dols ( 2019-02-25 14:32:16 -0500 )edit

I have downloaded the pre-release version of E+ 9.1 to transition your file but got some errors because of the HVAC system. I could hence not test the file. Could you simplify the IDF to only include the envelope and the external interface objects to see whether the problem persists. I did a mini example on my side with the compiled version of the code which is on the branch I have sent you earlier and it worked. For the transition errors, I suggest to check with @MJWitte

Thierry Nouidui gravatar imageThierry Nouidui ( 2019-03-03 01:59:47 -0500 )edit

@Thierry Nouidui There was a bug in the v9.0-9.1 transition packaged in the v9.1 idd freeze release. If you pull current develop and build transition, it should work. Or e-mail me separately and I can get it to you.

MJWitte gravatar imageMJWitte ( 2019-03-05 16:02:05 -0500 )edit

@MJWitte: Thanks. @stuart-dols: Please check with @MJWitte if he can transition your file for you or try a mini version of your IDF which doesn't have an HVAC in the loop.

Thierry Nouidui gravatar imageThierry Nouidui ( 2019-03-07 10:44:41 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

 



Question Tools

1 follower

Stats

Asked: 2018-11-09 16:09:35 -0500

Seen: 111 times

Last updated: Dec 12 '18