FB_HVACBasicSequenceCtrl
Application
Unlike the sequence controllers FB_HVACPIDCooling, FB_HVACDehumidify, FB_HVACEnergyRecovery, FB_HVACPIDHumidify, FB_HVACPIDMixedAir, FB_HVACPIDPreHeating and FB_HVACPIDReHeating, the function block FB_HVACBasicSequenceCtrl has no special system-specific extensions or application. It is more general. The control direction of the controller is not automatically determined depending on the room air and outside air as is the case with the function blocks for heat recovery or the mixed air chamber.
A sequence of static heating and cooling ceiling can be implemented in the field of room automation with this function block.
VAR_INPUT
eDataSecurityType : E_HVACDataSecurityType;
bSetDefault : BOOL;
bEnable : BOOL;
iNumberOfSequences : INT;
iMyNumberInSequence: INT;
rW : REAL;
rX : REAL;
tTaskCycleTime : TIME;
tCtrlCycleTime : TIME;
eCtrlMode : E_HVACCtrlMode;
rYManual : REAL;
rInitialValue : REAL;
bResetController : BOOL;
bReset : BOOL;
eDataSecurityType:if eDataSecurityType:= eHVACDataSecurityType_Persistent, the persistent VAR_IN_OUT variables of the function block are stored in the flash of the computer if a value changes. For this to work, the function block FB_HVACPersistentDataHandling must be instanced once in the main program, which is called cyclically. Otherwise the instanced FB is not released internally.
A change of value can be initiated by the building management system, a local operating device or via a write access from TwinCAT. When the computer is restarted, the saved data are automatically read back from the flash into the RAM.
Application example: Example_PERSISTENT.zip
If eDataSecurityType:= eHVACDataSecurityType_Idle the persistently declared variables are not saved in a fail-safe manner.
Notice | |
A cyclically changing variable must never be linked with the IN_OUT variable of a function block, if eDataSecurityType:= eHVACDataSecurityType_Persistent. It would lead to early wear of the flash memory. |
bSetDefault: If the variable is TRUE, the default values of the VAR_IN_OUT variables are adopted.
bEnable: input variable for enabling the controller. The controller is active if bEnable = TRUE.
iNumberOfSequences: number of sequence controllers in the system.
iMyNumberInSequence: own number in the controller in the sequence.
rW: the setpoint is transferred to the controller with the variable rW.
rX: actual value of the control loop.
tTaskCycleTime: cycle time with which the function block is called. If the function block is called in every cycle this corresponds to the task cycle time of the calling task.
tCtrlCycleTime: cycle time with which the control loop is processed. This must be greater than or equal to the TaskCycleTime. The function block uses this input value to calculate internally whether the state and the output values have to be updated in the current cycle.
eCtrlMode: the operation mode is selected via this enum.
rYManual: manual value.
rInitialValue: the restart behavior of the controller is influenced by rInitialValue.
bResetController: a positive edge on the input bResetController resets the PID controller.
bReset: acknowledge input in the event of a fault.
VAR_OUTPUT
rY : REAL;
rXW : REAL;
bMaxLimit : BOOL;
bMinLimit : BOOL;
bActive : BOOL;
bARWactive : BOOL;
eState : E_HVACState;
bError : BOOL;
eErrorCode : E_HVACErrorCodes;
bInvalidParameter: BOOL;
rY: control signal output of the PID controller.
rXW: control deviation
bMaxLimit: the output bMaxLimit is TRUE, if the output rY has reached the value rYMax.
bMinLimit: the output bMinLimit is TRUE, if the output rY has reached the value rYMin.
bActive: bActive is TRUE, if the controller is active and enabled.
bARWactive: bARWactiveis TRUE, if the integral component of the controller has reached the lower or upper control value limit.
eState: state of the controller. See E_HVACState.
bError: this output indicates with a TRUE that there is an error.
eErrorCode: contains the command-specific error code. See E_HVACErrorCodes.
bInvalidParameter: TRUE if an error occurs during the plausibility check. The message must be acknowledged with bReset.
VAR_IN_OUT
rDeadRange : REAL;
bDirection : BOOL;
rKp : REAL;
tTi : TIME;
tTv : TIME;
tTd : TIME;
rDeadBand : REAL;
rYMin : REAL;
rYMax : REAL;
iCurrentSequence: INT;
rDeadRange: in order to avoid unnecessary driving and hence premature wear of the valves or damper drives, a dead range (0..32767) can be set for the controller output signal rY. This means that a control signal change is only active if the change of value is greater than the dead range. A constant change of the control signal rY is converted to a pulsating drive of the actuator if a dead range is specified. The larger the dead range the larger the pauses and the control signal jumps will be. The variable is saved persistently. Preset to 0.
bDirection: the control direction of the controller can be changed with the parameter bDirection. If bDirection is TRUE, the direct control direction for cooling operation of the controller is active.
If bDirection is FALSE, the indirect control direction of the controller is activated for heating operation.
The variable is saved persistently. Preset to FALSE.
rKp: proportional factor gain. The variable is saved persistently. Preset to 1.
tTi: integral action time. The I-part corrects the residual control deviation following correction of the P-part. The smaller the tTi time is set, the faster the controller corrects. The control loop becomes unstable if the time is too short. Larger tTi-times must be entered in order to reduce the integration component. The integral action time should be selected to be longer than the stroke time of the valve or damper drive. The variable is saved persistently. Preset to 30 s.
tTv: rate time. The larger tTv is, the stronger the controller corrects. The control loop becomes unstable if the time is too long. Often in normal building automation applications only a PI controller is used. In this case zero must be entered for tTv. The variable is saved persistently. Preset to 0 s.
tTd : damping time. The variable is saved persistently. Preset to 0 s.
rDeadBand: if the control value is at the lower or upper limit of a controller and the actual value of the controlled system oscillates around the setpoint with a small amplitude, frequent switching back and forth between two sequence controllers can be damped by an additional parameter for the switchover. To this end, the difference between the actual values and the setpoints of the controlled system is integrated after the sequence controller has reached its lower or upper limit. Switching to the next sequence only takes place if the sum of this integration is greater than the value of rDeadband (see sample). The variable is saved persistently. Preset to 0.
rYMin: lower limit of the working range of the controller. The variable is saved persistently. Preset to 0.
rYMax: upper limit of the working range of the controller. The variable is saved persistently. Preset to 100.
iCurrentSequence: currently active controller in the sequence.