[HCr22] Heating circuit, precontrol

Components and functions of the plant example:

Plant example HCr22 is a heating circuit for precontrol. HCr22 can be used as a simplified heating circuit for radiators (with a linear heating curve, a setback defined by a scheduler and without room sensor).

Outside temperature

The outside temperature [TOa] is used unfiltered and filtered. Two different attenuated signals result from the filtering.

Function heating limit

Both filtered outside temperatures are considered.

The plant is enabled for automatic mode, e.g. by the scheduler, if both filtered outside temperatures are below the value from [HtgLm]. The plant is not enabled for automatic mode if one of the two values exceeds the value from [HtgLm].

BACnet objects

Gather heat requests

The heat request can be gathered from different consumers. Binary demand messages and analog demand setpoints can be collected.

The program receives an input block of type R_B that can be linked to a binary demand message via BACnet and an input block of type R_A for an analog demand setpoint.
[R_B] Read binary
[R_A] Read analog

Additional demand signals can be connected in parallel: Binary to an OR and analog to a MAX block.

Flow temperature control

The setpoint for flow temperature is the maximum from the setpoints from heat requests (SpHReqX) and the flow setpoint calculated using a linear heating curve.

Key

BACnet objects

The scheduler [MSchedule] specifies a certain operating mode and can also specify operation at a reduced flow temperature setpoint (Off, On, Reduced).

During operation at a reduced flow temperature setpoint, the value from [SpRdc] is subtracted from the setpoint as calculated by the heating curve.

BACnet objects

If plant power must be reduced, e.g. during charging of the hot water storage tank, connect input [YCtrMax] of the temperature controller to a limitation signal, e.g. via BACnet.

Plant operating modes:

• Off (1)
• On (2)

The operating modes are reported on [MCalcVal] object 'Present operating mode'.

At the same time, the reason for the present operating mode is reported to another [MCalcVal] object:

• Exception (1)
• Operating mode switch (2), resulting from an active (not equal to Auto) operating mode switch
• Manual operating mode selection (3), resulting from an active (not equal to Auto) manual operating mode selection
• Heating limit (4)
• Heat request (5)
• Scheduler (6), resulting from an active scheduler

There is a normal mode and local exception mode.

Normal operation

Sources for normal mode:

• [MI] Operating mode switch
• [MCnfVal] Manual operating mode selection
• Heating limit
• Heat request
• [MSchedule] Scheduler

In normal mode, components are simultaneously switched on and off as per the operating mode.

Exception mode

Sources for exception mode:

• Pump fault
• Overtemperature detector

In exception mode, all outputs are switched off directly at priority 5 (the mixing valve is switched to bypass) and the present operating mode is set to 'Off'.

Local exception mode (special case for overtemperature detector)

The pump remains on, for example, for 10 minutes if the overtemperature detector is triggered. The pump is then switched off. The outputs [AO] valve position and [BO] pump command are switched at priority 4.

The overrun described above may need to be adapted in the program depending on the application and installation. For example, it may have to be set to 0 for floor heating.

Start-up control (nested chart SttUpAlmHdl)

The following functionality is available for an automatic startup of the plant, e.g. after a loss of power and return of power:

1. Fixed switch-on delay (can be set on input pin [DlySttUp])
2. The plant remains off to ensure communications are reliable and cross-check references are triggered. 'Exception' is reported as the reason for the present operating mode.
2. Automatic acknowledge (2x) of possible pending alarms during a fixed switch-on delay.
3. Additional adjustable delay for staged plant ramp-up (can be set on input pin [DlyOn])

Alarm handling (nested chart SttUpAlmHdl)

The state of events on the plant is acquired by BACnet object 'Plant state'. The state is mapped on function block CMN_EVT.
[CMN_EVT] Common event

The following functions are available:

1. Automatic acknowledge (2x) after startup
2. Alarm acknowledgement with a value object
3. Alarm indication:
   - For pending alarms On
   - For unprocessed alarms flashing
4. Ability to connect the acknowledge button [BI]
5. Ability to connect to an alarm indication [BO], e.g. an alarm lamp through an output block [BO]
6. Ability to connect to other alarm handling functions on other plants, e.g. acknowledge button and alarm indication for multiple plants in the same control cabinet

Startup function and alarm handling for flat plants