Here is the update package for 2.8 Ironbug_UpdatePkgForOps2.8_v0.0.12.2.zip (743.3 KB)
I think I may have found a bug… when I try to specify the Glychol Concentration, the condenser water loop throws an error. Running it through a number container first does not help.
Also, is there a way to create a fluid cooler? I only see cooling towers.
@Elliot_Glassman
It seems the ObjParams components failed to guard the input type for Glychol Concentration.
In this case, openstudio is expecting the integer for the input value.
I will look into the code and try to fix it. but for now you can pass the value via “Integer”
Evaporative fluid cooler is not added yet, but if you could provide an example with a basic settings, that’d be great, and I can add it over the weekend.
-Mingbo
Yeah the only problem is when I pass 0.4 as an integer, I get 0!
What can I provide you as an example? I am basically trying to change this Unitary system to have a fluid cooler not a cooling tower. Let me know what is most helpful to put together for you.
Hi @Elliot_Glassman, I have added an integer type in objParam component, all values will be automatically converted to integer when it is needed.
I have added fluid cooler in following update package.
Ironbug_v0.0.12(20190623update).zip (264.1 KB)
Please let me know if it works.
Thanks
-Mingbo
Hi Mingbo,
Thanks for the amazing update.
Is it possible that something in the plant loop branches may have broken in this update? For some reason all my plant loop components are only showing one branch now despite multiple inputs, and the OS file is missing the other branches (needless to say, the simulations won’t run)
You are right, I updated the plantBranches component last week as well, and I did break the old component.
But here is a fixed update, please let me know if this works.
Ironbug_v0.0.12(20190624update).zip (260.7 KB)
Thanks, Mingbo.
Despite specifying “EthyleneGlycol” in the fluid input, it is still showing water as the fluid in Open Studio file produced. Also, I am trying to specify a 40% concentration, and putting in 0.4 changes it to 0 because of the integer issue.
That’s strange, I just tried again, it exports both value correctly. (I think the concentration value takes %, so 40 works, instead of 0.4)
Yeah when I attach the DWLoop output to a panel I see the Glycol, but in Open Studio and the IDF it says water… not sure why its not translating.
Also in the IDF file I am trying to replicate, it is specified as 0.40, and the following documentation on Big Ladder seems to indicate its a decimal too:
Let me know your thoughts
Could you give me a test gh file that doesn’t export osm file correctly with fluid type?
For the concentration value, I am not sure if it is a bug from openstudio or it is just how it sets. The only way to find out is build a simple model and try to run it with these settings. You can also check the idf file after the test run.
I messaged you the file, let me know if you did not get it.
I don’t know if this is an Ironbug issue of more OS/E+ thing, or if it’s related to the fluid issue at all, but every time I substitute my two speed cooling tower (which works) for the two speed fluid cooler the simulation fails. Please let me know if you spot anything in the file I sent you.
Hi @Elliot_Glassman,
I did a several tests with your file.
The first error I ran into is related to the Humidity setpoint manager. I think this related to humidify schedule in the zone, and also the location where you placed the in the airloop. Since this is not your main problem, so I removed all humidity controls (Humidifier and its set point manager) to recreate the fluid cooler’s issue.
Then, I got an error that says the “Heat pump loop” is too hot. I suspect this is somewhat related to your loop controls. Since the dummy boiler is not suppose to run at all, and setpoint managers after fluid cooler and boiler are the same as supply outlet setpoint manger, I removed them in branches.
With these adjustments, it runs now.
I attach the osm here if you want to take a look, and test at your end.unnamed.osm (155.2 KB)
So, with all these tests, at least we can rule out that the error is related to fluid cooler itself.
I’d suggest you to test the system with a small simple box model first, which helps to isolate issues and easier to solve. I’d also suggest you check the “.err” file in the study folder, this will provide some clues which part of model fails.
Please let me know if this still doesn’t fix your problem.
-Mingbo
Thanks, Mingbo.
This definitely solved the issue. I also fixed the humidifier control.
The fluid issue still remains; despite me specifying the glychol, it has water as the medium. One thing I noticed is that I am actually trying to do a non-evaporative fluid cooler, which is in Open Studio but I guess is not in Ironbug yet. I do not know if this is a factor.
@Elliot_Glassman The reason that you cannot set its fluid type to Glycol is because there is a HotWaterBoiler in this loop’s supply side. I can set it successfully after I removed boiler from this loop.
I have added the non-evaporative fluid cooler in this update zip file. Please let me know if this works.
Ironbug_v0.0.12_20190707updates.zip (279.9 KB)
Hi Mingbo,
Thanks again for the quick response and update. Two questions:
- I get this error when I open up Grasshopper:
Does not seem to affect anything I have in my model however.
- This seems kind of weird, but is it possible that there is a value hard coded for the design flow rate? I left it blank so it would autosize, but the simulation keeps having a fatal error and the IDF error file implies an inputted design flow rate of 1.388000E-003 m3/s. When I input a higher value, it runs.
Hi @Elliot_Glassman,
- This version of Ironbug works with all versions (2.5, 2.8 or newer) of OpenStudio, but some updates are only available in OS2.8 or newer. These unfriendly exception messages will be removed in the next update.
- The design flow rate in which component?
Ah, I look forward to testing out 2.8 when I get through this exercise in 2.5!
The design flow rate in the fluid cooler. The error I get:
************* Beginning Plant Sizing Calculations
** Severe ** SizeFluidCooler: The combination of design input values did not allow the calculation of a
** ~~~ ** reasonable UA value. Review and revise design input values as appropriate. Specifying hard
** ~~~ ** sizes for some “autosizable” fields while autosizing other “autosizable” fields may be
** ~~~ ** contributing to this problem.
** ~~~ ** This model iterates on UA to find the heat transfer required to provide the design outlet
** ~~~ ** water temperature. Initially, the outlet water temperatures at high and low UA values are
** ~~~ ** calculated. The Design Exit Water Temperature should be between the outlet water
** ~~~ ** temperatures calculated at high and low UA values. If the Design Exit Water Temperature is
** ~~~ ** out of this range, the solution will not converge and UA will not be calculated.
** ~~~ ** The possible solutions could be to manually input adjusted water and/or air flow rates based
** ~~~ ** on the autosized values shown below or to adjust design fluid cooler air inlet dry-bulb temperature.
** ~~~ ** Plant:Sizing object inputs also influence these results (e.g. DeltaT and ExitTemp).
** ~~~ ** Inputs to the fluid cooler object:
** ~~~ ** Design Fluid Cooler Load [W] = 582060.00
** ~~~ ** Design Fluid Cooler Water Volume Flow Rate [m3/s] = 1.388000E-003
** ~~~ ** Design Fluid Cooler Air Volume Flow Rate [m3/s] = 139666.47
** ~~~ ** Design Fluid Cooler Air Inlet Dry-bulb Temp [C] = 35.00
** ~~~ ** Inputs to the plant sizing object:
** ~~~ ** Design Exit Water Temp [C] = 39.00
** ~~~ ** Loop Design Temperature Difference [C] = 11.00
** ~~~ ** Design Fluid Cooler Water Inlet Temp [C] = 51.67
** ~~~ ** Calculated water outlet temp at low UA [C] (UA = 58.21 W/K) = 51.50
** ~~~ ** Calculated water outlet temp at high UA [C] (UA = 582060.00 W/K) = 35.00
All the numbers are things I have input except for the Design Fluid Cooler Water Volume Flow Rate
@Elliot_Glassman , thanks for these details.
I wouldn’t be surprised that this is a bug from OpenStudio, as they had a similar issue before in CentralHeatPump.
I will do a quick test, and report it to OpenStudio team if needed.