You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Always On Schedule for the HVAC System needs to become more fail-safe.
Detailed Description
I wanted to declutter my list of schedules. After deleting all of them, the simulation could not run. The following is the error message I received:
[openstudio.model.ControllerMechanicalVentilation] Object of type 'OS:Controller:MechanicalVentilation' and named 'Controller Mechanical Ventilation 1' does not have an Availability Schedule attached.
I could not find a solution online. I had to compare my old and new models' lines of code to notice the missing element. Long story short, one of the Always On Schedule that I deleted was critical for my HVAC system to work.
Possible Implementation
Someone might find themselves in the same position as me. I have a couple of potential fail-safe features.
One option is to add a new Always On Schedule input box in OS:AirLoopHVAC. That way, the user can insert a new schedule in case one was deleted.
The other option is to hide the Always On Schedule from the Schedule>>Other Schedule list to prevent someone from deleting it. It can only be deleted with the HVAC System.
The text was updated successfully, but these errors were encountered:
Enhancement Request
The Always On Schedule for the HVAC System needs to become more fail-safe.
Detailed Description
I wanted to declutter my list of schedules. After deleting all of them, the simulation could not run. The following is the error message I received:
[openstudio.model.ControllerMechanicalVentilation] Object of type 'OS:Controller:MechanicalVentilation' and named 'Controller Mechanical Ventilation 1' does not have an Availability Schedule attached.
I could not find a solution online. I had to compare my old and new models' lines of code to notice the missing element. Long story short, one of the Always On Schedule that I deleted was critical for my HVAC system to work.
Possible Implementation
Someone might find themselves in the same position as me. I have a couple of potential fail-safe features.
One option is to add a new Always On Schedule input box in OS:AirLoopHVAC. That way, the user can insert a new schedule in case one was deleted.
The other option is to hide the Always On Schedule from the Schedule>>Other Schedule list to prevent someone from deleting it. It can only be deleted with the HVAC System.
The text was updated successfully, but these errors were encountered: