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

Infloor Radiant Heat [closed]

asked 2015-12-09 12:33:44 -0600

Dustin gravatar image

updated 2017-05-08 18:35:38 -0600

Using OpenStudio.

I have some concerns regarding how I am going about modelling infloor radiant heat. I understand that I have to create an internal source construction. But how do you link the low temperature radiant variable flow equipment to those constructions?

I have another question regarding the low temperature variable flow equipment. When I add the equipment to my model there is a link to attach the item to loops. There is a link for heating and cooling. In my case the loop is only used for heating so can I just leave the cooling link blank and not attach it to any loop and it will still run. I'm thinking it won't like that and will fail running due to this error. Any advice or reference to other questions is greatly appreciated.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Dustin
close date 2016-07-04 11:16:21.097274

2 Answers

Sort by ยป oldest newest most voted

answered 2015-12-09 12:48:28 -0600

updated 2015-12-09 12:49:42 -0600

The relevant input field in the ZoneHVAC:LowTemperatureRadiant:VariableFlow zone equipment object that will link the system to the internal source construction surface is 'Radiant Surface Type'. The choice in that field will tell OpenStudio to create a ZoneHVAC:LowTemperatureRadiant:SurfaceGroup object on translation to idf that includes the surfaces in the zone of the selected type that have internal source constructions, and reference that object in the LowTemperatureRadiant object's !- Surface Name or Radiant Surface Group Name field.

Note: A while back I documented an issue with this translation that I'm not sure was addressed by the developers, so be aware. It shouldn't be an issue if you don't have any surfaces defined with internal source constructions in the space that you _don't_ want linked to the system.

You're correct that if you leave the loop connection blank, you will run into an error. As usual with these situations, you can link it to a cooling loop, but force cooling to never be activated by hard-sizing the 'Maximum Cold Water Flow' field to zero, or defining a Cooling Control Temperature Schedule such that cooling is never activated.

edit flag offensive delete link more


Ok thanks fro the information will definitely be put to use.

Dustin gravatar image Dustin  ( 2015-12-09 13:17:45 -0600 )edit

Where it says heating control temperature schedule name, is that the same type of schedule as the heating setpoint schedules that a building would have? If so could those be the same schedules?

Dustin gravatar image Dustin  ( 2015-12-09 13:22:08 -0600 )edit

It's the same type, but it is the sole source of control for the system (i.e. it doesn't care about the zone thermostat setpoint). See this and this.

Eric Ringold gravatar image Eric Ringold  ( 2015-12-09 13:33:34 -0600 )edit

answered 2015-12-10 06:08:32 -0600

Jean Marais gravatar image

in the idf you can leave certain fields blank. this should be readible in the idd file and the ioreference.

edit flag offensive delete link more


Question Tools

1 follower


Asked: 2015-12-09 12:33:44 -0600

Seen: 305 times

Last updated: Jan 27 '17