Revision history [back]

Here are 5 possible causes of Controller:MechanicalVentilation errors that I've run across:

1. The model is missing design days. You can check the text "Number of Design Days:" field on the Weather File & Design Days tab. The design days get imported into the .osm when you browse for and select a file, so don't worry if the file path is empty after you reopen the file as long as the "Number of Design Days:" is more than 0.
2. The model has an Airloop with no OA intake system, but one or more of the zones connected to this Airloop has a DesignSpecificationOutdoorAir object.
3. The model has an Airloop with an OA intake system, but none of the zones connected to the Airloop have a DesignSpecificationOutdoorAir object.
4. The Airloop is connected to a zone that contains no spaces, and therefore has no DesignSpecificationOutdoorAir object.
5. The model has an Airloop with no zones attached.

Here are 5 possible causes of Controller:MechanicalVentilation errors that I've run across:

1. The model is missing design days. You can check the text "Number of Design Days:" field on the Weather File & Design Days tab. The design days get imported into the .osm when you browse for and select a file, so don't worry if the file path is empty after you reopen the file as long as the "Number of Design Days:" is more than 0.
2. The model has an Airloop with no OA intake system, but one or more of the zones connected to this Airloop has a DesignSpecificationOutdoorAir object.
3. The model has an Airloop with an OA intake system, but none of the zones connected to the Airloop have a DesignSpecificationOutdoorAir object.
4. The Airloop is connected to a zone that contains no spaces, and therefore has no DesignSpecificationOutdoorAir object.
5. The model has an Airloop with no zones attached.