Difference between revisions of "Buffer Store Control"
| Line 27: | Line 27: | ||
This application starts with a definition of the system to be controlled. This is done through a schematic design that in turn leads to control points, logic, and a parts list. | This application starts with a definition of the system to be controlled. This is done through a schematic design that in turn leads to control points, logic, and a parts list. | ||
The following schematic was generated using | We arrive at the definition through a series of questions and automated calculations, using a standardised dictionary to record answers. All open controls on this wiki follow the same open controls dictionary, so data collected can feed directly into software. | ||
We are in the process of refining Q&A modules to suit different applications, however the 'Designer' for heat networks (the Q&A module) covers buffer store and heat source selection in detail and ready to use. The following schematic was generated using this open-source [http://heatweb.co.uk/w/index.php?title=Heat_Network_Designer Heat Network Designer software]. | |||
[[File:Hnbrschem1.svg]] | |||
* [https://hw7.ddns.net/ui/hndesign?jsonQ=hndesign&loadSchedule=%5B%7B%22propertyType%22%3A%22Flat%22%2C%22bedrooms%22%3A2%2C%22occupants%22%3A%223%22%2C%22kwCH%22%3A%224%22%2C%22qty%22%3A%22147%22%7D%2C%7B%22propertyType%22%3A%22Office%22%2C%22bedrooms%22%3A0%2C%22occupants%22%3A2%2C%22kwCH%22%3A%228%22%2C%22qty%22%3A1%7D%2C%7B%22propertyType%22%3A%22Entrance%22%2C%22bedrooms%22%3A%220%22%2C%22occupants%22%3A%221%22%2C%22kwCH%22%3A%227%22%2C%22qty%22%3A%221%22%7D%5D&nBuildings=1&tPeak=65&tPriRtnDHW=19&profileDHW=EST&typeEmitter=underfloor&connectionCH=indirect&tXPeak=-5&tPriRtnCH=35&divCH=70&baseTemp=16°DaysAvg=1749.5%2C1884.5%2C2023.9%2C2167.9%2C2316.2%2C2467.9%2C2623.5%2C2782.4%2C2944.3%2C3108.6%2C3275.4%2C3444.9%2C3615.7°Days=1850&goBoilers=true&goASHP=true&goHN=true&goWSHP=false&goReclaim=false&goCHP=false&goSolar=false&boilerFuel=gas&boilerEmissions=0.216&listBSizes=30%2C50%2C75%2C100%2C250%2C500%2C750%2C1000&selectBoilers=4%20x%20250&tariffHP=flat&elecEmissions=0.233&elecEmissions=0.233&fridgeASHP=R744&listASHPSizes=30&selectASHP=6%20x%2030&vBuffer=2000&maxVelocityFlow=2&minVelocity=0.5&goSave=false https://hw7.ddns.net/ui/hndesign - bivalent system] | * [https://hw7.ddns.net/ui/hndesign?jsonQ=hndesign&loadSchedule=%5B%7B%22propertyType%22%3A%22Flat%22%2C%22bedrooms%22%3A2%2C%22occupants%22%3A%223%22%2C%22kwCH%22%3A%224%22%2C%22qty%22%3A%22147%22%7D%2C%7B%22propertyType%22%3A%22Office%22%2C%22bedrooms%22%3A0%2C%22occupants%22%3A2%2C%22kwCH%22%3A%228%22%2C%22qty%22%3A1%7D%2C%7B%22propertyType%22%3A%22Entrance%22%2C%22bedrooms%22%3A%220%22%2C%22occupants%22%3A%221%22%2C%22kwCH%22%3A%227%22%2C%22qty%22%3A%221%22%7D%5D&nBuildings=1&tPeak=65&tPriRtnDHW=19&profileDHW=EST&typeEmitter=underfloor&connectionCH=indirect&tXPeak=-5&tPriRtnCH=35&divCH=70&baseTemp=16°DaysAvg=1749.5%2C1884.5%2C2023.9%2C2167.9%2C2316.2%2C2467.9%2C2623.5%2C2782.4%2C2944.3%2C3108.6%2C3275.4%2C3444.9%2C3615.7°Days=1850&goBoilers=true&goASHP=true&goHN=true&goWSHP=false&goReclaim=false&goCHP=false&goSolar=false&boilerFuel=gas&boilerEmissions=0.216&listBSizes=30%2C50%2C75%2C100%2C250%2C500%2C750%2C1000&selectBoilers=4%20x%20250&tariffHP=flat&elecEmissions=0.233&elecEmissions=0.233&fridgeASHP=R744&listASHPSizes=30&selectASHP=6%20x%2030&vBuffer=2000&maxVelocityFlow=2&minVelocity=0.5&goSave=false https://hw7.ddns.net/ui/hndesign - bivalent system] | ||
* [https://hw7.ddns.net/ui/hndesign https://hw7.ddns.net/ui/hndesign - start new design] | * [https://hw7.ddns.net/ui/hndesign https://hw7.ddns.net/ui/hndesign - start new design] | ||
[[Category:Applications]] | [[Category:Applications]] | ||
Revision as of 13:56, 24 May 2022
The new Heat Network Guidance from CIBSE, along with CP1, have been clear about the correct way that buffer stores should be implemented in systems.
The methods laid out in guidance require boilers and heat sources to be sequenced from storage, rather than temperature error , and they must also have loading valves. These functions can prove a challenge to the best BMS installers, so the use of a standardised open-source controls library and hardware interface makes a great deal of sense, allowing the finer detail to improve (evolve) over time, rather than trying to reinvent the wheel on every installation based on an individual's understanding of both guidance and BMS software.
This controller function is suitable for domestic and commercial storage systems. It can be used stand-alone, in groups, or as an interface for BMS systems.
Functionality
- Heat sources are assigned an order, representing the preferred order in which they fire, with 1 being the lead.
- Uncontrolled heat sources, such as solar thermal, has an order of 0. Heat will be taken if available and safety controls allow.
- Heat sources with the same order will be run in duty/standby and rotated, pulling in the next in order as required.
- Heat sources are fired up according to store depletion, both on volume remaining and rate of depletion.
- Heat sources may be exercised after a period of inactivity, regardless of order.
- Modulation will be applied to heat sources where possible to match loads and minimise cycling.
- Low load buffering mode to minimise cycling.
- Timing functions can be applied.
- Includes functions for override of non-critical loads, such as central heating, when store close to empty.
- Includes functions for activation of heat dump circuits for solar thermal and biomass.
- Includes functions for boiler loading valve and pump control (with DP switch or sensor).
- Includes functions for network tempering valve control.
- BMS integration via Modbus RTU or IP.
- Includes functions for M-Bus/Modbus heat meter reading.
- Includes alarm functions for low/high temperature, low/high pressure, low storage, failure of heat sources.
- Makes possible the implementation of storage management and sequencing based on volatile fuel prices using predicted loads
Hydraulic Design
This application starts with a definition of the system to be controlled. This is done through a schematic design that in turn leads to control points, logic, and a parts list.
We arrive at the definition through a series of questions and automated calculations, using a standardised dictionary to record answers. All open controls on this wiki follow the same open controls dictionary, so data collected can feed directly into software.
We are in the process of refining Q&A modules to suit different applications, however the 'Designer' for heat networks (the Q&A module) covers buffer store and heat source selection in detail and ready to use. The following schematic was generated using this open-source Heat Network Designer software.
