Application

Sequence of Operation
PID Only (Mode 2)
25
Siemens Industry, Inc.
BACnet LCM-OAVS, App 2924
140-1304
2015-07-07
Venturi Air Valve Table Statement
V TABLE
PT
Description
Exhaust
Swap
121
Setting V TABLE PT to 121 instructs the controller to evaluate the values
in the inactive exhaust portion of the table using standard calibration
pass/fail logic. If they pass, they are exchanged with those in the active
exhaust portion of the table.
NOTE:
The factory default value for GEX VLV STAT is NOTCAL which indicates a failure of
the calibration or that calibration has not yet been done. The value is set whenever a
calibration or table transfer is performed as the last step of the calibration/table
transfer. GEX VLV STAT is never used for active control decisions.
NOTE:
The calibration table initially contains all zeros by default, that is, it contains no
calibration information. When the application detects all zeros, the application
operates, but runs with only PID control. If PID only control is satisfactory for a given
job, there is no need to populate the table. Should it be necessary, a populated table
can later be edited back to all zeroes to force PID only control.
PID Only (Mode 2)
NOTE:
The default P gain value is intended for PID operation in conjunction with the Venturi
table. The P gain and Venturi table work together to provide an appropriate response
to setpoint changes. When operating without the Venturi table in PID Only mode, the
application is slower to respond. Therefore, you should adjust the P gain as needed
when operating in PID Only mode to ensure acceptable performance.
The Venturi calibration table initially contains all zeros by default, that is, it contains no
calibration information. When the application detects a zero flow for the sixteenth entry
(the table entry with the highest flow), the application does operate, but runs with only
PID control. If PID only control is satisfactory for a given job, there is no need to
populate the Venturi tables.
Open Loop (Mode 3)
This application can operate in open loop mode. In open loop control, there is no
airflow sensor to provide an actual airflow measurement. Instead, operation is based
completely on the values in the Venturi table. For example, if the actuator’s setpoint is
600 cfm, the application will use the Venturi table to derive the voltage setting that
generates a flow of 600 cfm and then set the actuator to that voltage to generate the
desired flow. Assuming the table has accurate entries, the flow (if it were to be
measured) would be at setpoint.
Internally within the application, with open loop control, the flow is always assumed to
be at setpoint As a result there is virtually no difference between flow tracking and
setpoint tracking when the actuator being tracked is operating open loop.