Heating ThermalStorage tank in E+

asked 2017-09-20 18:29:24 -0500

updated 2017-10-02 09:45:41 -0500

I'm trying to model a use case where we'd want to store excess heat in a 4-pipe water to water central heat pump configuration (if cooling load > heating load, there's extra heat that can be used to charge said tank) as well as charging the tank at night.

The ThermalStorage:ChilledWater:Mixed and ThermalStorage:ChilledWater:Stratified both have a nice feature: they have a Use/Source side availability schedule (eg: here).

I'd like to use something similar but for heating. How can I do that?

  • Can I use the ThermalStorage:ChilledWater:XX objects as a heating storage tank ? The name would imply no, but I've seen stranger things.
  • Any other good way/workaround to achieve a similar behavior?

As far as workaround, I was thinking there was perhaps a way of using a HeatExchanger:FluidToFluid (control type as HeatingSetpointModulated for eg) placed on the demand side of the primary plant loop (the one with the heating side of the heat pump), and connected to a secondary plant loop, on which it'd be on the supply side.

The secondary plant loop would have a WaterHeater:Mixed (serving as a storage tank) on the demand side and would be controlled by an availability manager that would turn off the secondary plant loop when charging is not desired. The storage tank would also be on the supply side of the primary plant loop (in parallel or in series, not sure).

It sure is convoluted, and it may not work, not sure if the AvailabilityManager would be enough (would that ensure the primary plant loop sees no heating demand from the HX?). This workaround, if it works, would have the advantage of allowing for a greater variety of controls aside from just Scheduled (though a Schedule can be easily actuated via EMS that being said...)

edit retag flag offensive close merge delete

Comments

I have bumped into this same problem wanting to implement a hot water TES but have been frustrated by the lack of the "Use/Source Side Availability Schedule" as you mention. Did you manage to get the workaround you wanted?

akat022 gravatar image akat022  ( 2017-12-22 09:02:21 -0500 )edit