I continue running one of the example files: AirflowWindowsAndBetweenGlassShades.idf. The simulation produces results only for the two design days specified in the IDF file because the file has no _SimulationControl_ object.
Now, I am trying to turn off the HVAC and do a simulation with no HVAC. I did the following to achieve this aim:
I added a new Schedule to the example file and called it AlwaysOff:
Schedule:Constant,
AlwaysOff,
Control Type,
0;
I then used this schedule as the Availability Schedule name for all HVAC equipment. There is only one type of HVAC used in this example file and it is ZoneHVAC:IdealLoadsAirSystem. There are one of these for each of the three zones. In the example file their availability schedule names (the second lines of each ZoneHVAC:IdealLoadsAirSystem record) were left blank, which implied that they were always available. I changed that to my new AlwaysOff. Here are the first three lines of the modified IdealLoadsAirSystem records. The other lines remain as they are:
ZoneHVAC:IdealLoadsAirSystem,
Zone1Air, !- Name
AlwaysOff, !- Availability Schedule Name
I then ran the simulation as I did before. To my surprise and disappointment, the results were exactly the same as they were with the original file. The HVAC systems were called in during the design day simulations and they kept the temperatures in the set range.
I understand that I have conflicting information in the IDF file. I specify temperature set points for heating and cooling systems but set the availability of these heating and cooling systems to zero. I assumed that when a system were unavailable, its set points would be irrelevant.
Can anyone comment on why the unavailable HVAC systems are still called in to the job and why they work as if they were available?
