problem with NightCycle Availability Manager, OpenStudio 1.4.0.0 and E+ v 8.1.0.009

asked 2014-12-15 03:25:11 -0500

Chienman
588 ●6

updated 2015-07-11 17:30:39 -0500

I've been trying to figure this out, and I just can't seem to get past it. I am probably missing something simple because it is late at night. Basically, I'm using the OpenStudio.dll (C# bindings) at the AirLoopHVAC level, I have used OpenStudio's call to nightCycleControlType(), setting the value to "CycleOnAny". The AvailabilityManagerAssignmentList is updated with a n AvailabiltyManager:NightCycle and the NightCycle manager looks like this:

AvailabilityManager:NightCycle, Packaged Rooftop VAV with Reheat NightCycle Manager, !- Name Always On Discrete, !- Applicability Schedule Name Always On Discrete, !- Fan Schedule Name CycleOnAny, !- Control Type 1, !- Thermostat Tolerance {deltaC} 3600;

But, even though there is no zone demand, the fans still run and my main AirLoopHVAC node still has flow. What am I missing or not setting? I thought all I had to do was set this up at the AvailabilityManager level, and everything below it would be overriddedn. Is it something weird, like the applicability schedule name and fan schedule name can't be the same?

edit retag flag offensive close merge delete

add a comment

Comments

@Chienman use the AirLoopHVAC.setAvailabilitySchedule method to set the HVAC availability schedule. This will be propagated down to the fan on translation to IDF.

aparker ( 2014-12-15 09:23:23 -0500 )edit

Andrew, interestingly I thought all I have to do is call the nightCycleControlType()...but my fan did not get a new schedule as a result. It wasn't obvious at the time that this is what I should have done. Now I have got it. thanks for the feedback.