Hi all!,
I'm having trouble performing the PRM sizing runs in the IES V2017 for the baseline and proposed buildings.
After performing "Room Load Calculations" (no problems here), the software tells me that there are "Zoning issue detected: Unassigned zones present. Assign model zones to these zone components manually or run "Check for unset components..." from the ApacheHVAC menu".
However, when I go to the Apache HVAC menu and performe "Check for unset components", the software tells me "HVAC Zoning consistency check OK. No discrepancies found". ... Which seem inconsistent with its previous statement.
Additionally, the excel files in "Loads Data" case are not there (the software doesn´t create them).
The problem repeats itself for the "System Loads Calculation".
However, when I try to do all this "manually" (running the room and aquipment sizing on ApacheHVAC), no problems appear.
Can anyone please help me out?
Thank you all in advance!
PRM Sizing Runs
Re: PRM Sizing Runs
Hi Luisandrade - I'm sorry I can't help you, but I can chime in that I'm having a very similar (if not the exact same) issue as you've described.
I'm using the ASHRAE 90.1 App. G - PRM 2007 Navigator in IES VE 2017, and whenever I open my Baseline.asp ApacheHVAC file, I get the same "Zoning issue detected error". When I run the Zoning Checks/Updates, I also get the same "HVAC Zoning consistency check OK." (The item in the ApachHVAC dropdown menu to "Check All Unset Spaces..." is greyed out.)
When I use the Navigator for Room Load Calculations -> Run in Parallel, the load calcs for the Proposed system complete just fine, however all of the Baseline rotations list "Failed" in the Status column of the Tasks window, and the overall PRM Room Load Calculations lists "Predecessor Failed" as the Status. However, when I open Apache and run the ASHRAE Loads for just the Baseline.asp file, the calculations complete, but I again get the "Zoning issue detected error" when the loads are opened in VistaPro.
I have no idea if these errors or related, but wanted to share my similar experience in case it helps someone figure out what's going on.
Cheers!
I'm using the ASHRAE 90.1 App. G - PRM 2007 Navigator in IES VE 2017, and whenever I open my Baseline.asp ApacheHVAC file, I get the same "Zoning issue detected error". When I run the Zoning Checks/Updates, I also get the same "HVAC Zoning consistency check OK." (The item in the ApachHVAC dropdown menu to "Check All Unset Spaces..." is greyed out.)
When I use the Navigator for Room Load Calculations -> Run in Parallel, the load calcs for the Proposed system complete just fine, however all of the Baseline rotations list "Failed" in the Status column of the Tasks window, and the overall PRM Room Load Calculations lists "Predecessor Failed" as the Status. However, when I open Apache and run the ASHRAE Loads for just the Baseline.asp file, the calculations complete, but I again get the "Zoning issue detected error" when the loads are opened in VistaPro.
I have no idea if these errors or related, but wanted to share my similar experience in case it helps someone figure out what's going on.
Cheers!
Re: PRM Sizing Runs
A quick update on my Room Load Calculation issue, as it appears it us unrelated to the "Zoning issues detected" problem.
By turning on the Errors/Warnings/Messages boxes in the Tasks window, I was alerted there was a problem with an unused "New Weekly Profile" that was causing an error when running the Baseline load calcs. By going to the Profiles Database manager I was able to find and delete this rogue profile and resolve the issue.
I'm still getting the "Zoning issues detected" alert whenever I open the Baseline.asp file. =\
By turning on the Errors/Warnings/Messages boxes in the Tasks window, I was alerted there was a problem with an unused "New Weekly Profile" that was causing an error when running the Baseline load calcs. By going to the Profiles Database manager I was able to find and delete this rogue profile and resolve the issue.
I'm still getting the "Zoning issues detected" alert whenever I open the Baseline.asp file. =\