CB FALCON
63 750-265
FAULT HANDLING
Lockouts and Alerts
The Falcon implements two kinds of faults: lockouts and alerts.
A list of fault codes with possible troubleshooting tips is
provided in Table 50 on page 105.
A list of alerts is provided in Table 51 on page 113.
LOCKOUT
• A lockout causes the boiler control to shutdown and
requires manual or remote reset to clear the lockout.
• Always causes alarm contacts to close.
• Logged in lockout history.
ALERT
• Every other kind of problem that isn't a lockout is an alert.
Examples include boiler control abnormal holds, LL master
problems, faults from non-safety functions, etc.
• Alerts never require manual intervention to reset them; that
is, if the alert clears up, then normal operation will continue.
An alert is not a condition, it is an event. The cause of the
alert may be a condition, e.g. something that is causing an
abnormal hold, but the alert itself in this case is a
momentary event generated upon entry to that condition.
• Whether the alarm contact closes or not is programmable
for each alert by the OEM.
• Alerts are logged in a 15-item volatile alert history sorted in
chronological order. Only one instance of each alert code
occurs in the history, corresponding to the most recent
occurrence of that alert.
Alarms for Alerts
The Alarm Parameter Control Block (see the section above)
determines which alerts will cause an alarm (by closing the
alarm contacts) and which will be reported silently.
Thus an alarm might be on because of a lockout or an alert. If
the cause is a lockout then the alarm contacts remain close
until the lockout is cleared. However, for alarms due to alerts
(which may recur) the alarm may be silenced for a period of
time (0–600 minutes) by specifying it in the Alarm Silence Time
parameter.
To Next Page
Loading...
Need help?
General
