Describe the translation issue or enhancement:
Update translator to support a simple combined SHW/space heating system for
primarily residential applications. The enhancement described here is for
systems with no heat exhanger between the SHW and space heating loops. Rather,
potable water is circulated through the space heating elements.
The attached CBECC-Com cibd/SDD XML models illustrate the SDD structure for a
combined SHW/space heating system that serves the SHW loads and baseboards in
two zones. the CBECC-Com GUI, and how it is intended to be translated to OS.
A few notes:
- Currently the translator automatically specifies the the
PlantLoop:CommonPipeSimulation to 'CommonPipe' if there is a SecondarySupply
FluidSeg and child pump, and the Secondary pump is translated to be on the
inlet to the demand side of the PlantLoop. These translator rules should not be
used for FluidSys:Type = ServiceHotWater, as the branch pumps will not operate
correctly. To facilitate control of the commone pipe configruation, a new SDD
property, FluidSys:CommonPipeSim has been added, with enums 'None',
'CommonPipe', and 'TwoWayCommonPipe'. In the attached example SDD XML file,
this property is specified as 'None'. The translator shoud respect this new
property, and if not specified in SDD, use the current translator rule to set
this. The other exception for FluidSys:Type = ServiceHotWater systems is
SecondarySupply child pumps should be translated as branch pumps on the demand
side, upstream of the coils that reference the SecondarySupply segment. This
is shown in the attached diagram of the OS system.
- For these systems, the user should be setting the FluidSys:DsgnSupWtrTemp and
FluidSys:DsgnSupWtrDelT to reflect the space heating applications. This will
help ensure sizing of loop and coil flows rates will be based on the correct
delta T.
- The new properties Spc:HotWtrSupTemp can be used Spc:HotWtrSupTempSchRef to
specify the temperature that is delivered to the space for SHW use. If the SHW
loop supply water temperature setpoint (FluidSys:FixedSupTemp) is different
than the Spc:HotWtrSup* temperature, mixing of cold water with the hot is
assumed to achieve the target temperature for the flow specified for the space.
Kyle, I think the attached SDD XML example has all you need to update the
translator.
STILL TO RESOLVE:
1) Roger/Noah: Reporting of energy from the combined system will be reported to
the 'WaterHeating' end-use. I assume this is OK?
2) Noah/Kyle: I see potential for conflict between WtrHtr:WtrHtrTempSetptSchRef
and FluidSys:FixedSupTemp, do we need both?
3) Noah: There are two SDD simulation properties, Spc:HotWtrHtgTot and
Spc:HotWtrHtgRtSim. What is the difference?
4) Roger/Noah: At this point, I've basically only added the properties needed
to represent this system. I believe this scope was originally on NORESCO's
plate. Do you guys understand this enough to finish the rules and testing?
Original issue reported on code.google.com by da...@360-analytics.com on 11 Mar 2015 at 11:28
Original issue reported on code.google.com by
da...@360-analytics.comon 11 Mar 2015 at 11:28Attachments: