How do I track HVAC nodes

asked 2016-05-23 21:46:02 -0500

buddy1187
201 ●1 ●3

updated 2017-04-16 14:47:42 -0500

__AmirRoth__

4436 ●5 ●17 http://bleedinggreenna...

Hello all,

I'm currently trying to trouble shoot my energy model after seeing I have 1000s of unmet cooling and heating hours along with poor humidity control and ACH ventilation minimums not being met in the thermal zones.

How do I go about tracking a node (such as setpoint manager) so that I can track a parameter within this node (i.e. supply air temperature coming out an AHU)? Is this a separate measure I have to write to get these values?

Thanks!

edit retag flag offensive close merge delete

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2016-05-26 23:53:54 -0500

TomB

1684 ●2 ●11

updated 2016-05-26 23:55:20 -0500

I think there are two parts to your question 1. How do I get the Node's handle? 2. How do I add variables to see behaviour at that node Eric has answered the second part

I'd be tempted to do this sort of troubleshooting in e+ because I find that quicker and more direct to add output variables and inspect csv results that way. On the other hand, I wouldn't do that in e+ if I had to repeat it, because the .idf gets clobbered when you save the .osm

You can get the node name from the HVAC page, like this image node name.JPG

edit flag offensive delete link

Comments

Thank you for your response Tom! Like you said, I am hesitant to do this troubleshooting in E+ since I cannot fix any errors in E+ and then re-import my idf file back into OS. I think Eric's solution is sufficient for my needs.

buddy1187 ( 2016-05-29 10:10:30 -0500 )edit

add a comment

answered 2016-05-24 09:17:09 -0500

ericringold

10527 ●31 ●8 https://www.nrel.gov/b...

Probably the simplest way is to use the 'Add Output Variable' BCL measure, entering the node name as the key value and one of the 'System Node ...' output variables from the .rdd file as the variable name. You can add multiple instances of that measure in the measure tab, to track what's going on across your loop.