17 750-265
WARNING
Explosion Hazard.
Improper configuration can cause fuel buildup and
explosion.
Improper user operation may result in property loss,
physical injury, or death.
The 833-3577 System Operator Interface used to
change Safety Configuration Parameters is to be done
only by experienced and/or licensed burner/boiler
operators and mechanics.
Programming Safety Parameters
Safety standards require a tool to be used to alter safety
parameters. For software-based parameters, this “tool” is a
password.
All safety parameters will require either the OEM or installer
password before they can be changed.
The password level assigned during the OEM Parameter PCB
process effectively controls the minimum password level of all
safety items.
The Falcon will require the Installer password for this item,
that is, if the parameter visibility control block indicates that no
password is required, the Installer password will be enforced.
The Falcon may be in one of two conditions, configured, and
unconfigured. It will run in the configured condition, whereas
the setup of safety data is required following the procedure
below before it will run when in the configured condition.
When unconfigured and idle, all safety loads are off and the
burner status is shown as “Safety data setup needed.”
To modify and confirm the safety data when the Falcon is in
the unconfigured condition requires the following steps: When
complete, the Falcon will transition to the configured condition.
The Falcon will not run while in the unconfigured state.
To begin, the Falcon needs to be powered in either Standby
or a Lockout condition. The user needs to provide a valid
password.
1. The user edits safety data in the enabled section. At any
time, if "exit" is chosen, the session is ended and the
Falcon remains in an unconfigured state. In this case
the burner control status indicates “Safety data setup
needed.”
2. When the edits are complete and the user accepts
(rather than exit) the parameters the display will show
“edits done.” This causes the Falcon to calculate the
modified section of safety data. However it is not yet
accepted and written into memory, nor does the Falcon
leave the unconfigured state; instead it contin-
ues with the confirmation process in the next step.
3. The Falcon provides a parameter state and expects
the user has either confirmed the data or rejected it. If
the user rejects the data then the process returns to
step 2 and when editing again is done the confirmation
process begins again. Once started, the confirmation
process is successful only if each safety data item has
been confirmed, in the order provided by the Falcon.
4. After all items are confirmed, the Falcon requests the
user to press and hold the Reset button on the device
for 3 seconds. The user must accomplish this within 30
seconds.
5. If the reset button is pressed and held for 3 seconds (an
optional equivalent: a Reset is entered on the local dis-
play) to confirm that the programmed device is physi-
cally the one that the operator intended to program then
the safety data and its confirmation is accepted and
burned into memory. When this is done, the Falcon is
in the configured condition, unless some other parame-
ter section also needs setup. If some other section
needs setup, the Falcon is again at step 1.
Functional Sub Systems
There are nine functional sub systems to the Falcon. They
are:
1. System Operational Settings (page 17)
2. General Configuration Settings (page 18)
3. Demand and Rate (page 19)
4. Rate Limits and Override (page 29)
5. Burner Control (page 52)
6. Modulation Output (page 40)
7. Pump Control (page 42)
8. Lead Lag (still to be defined)
9. Annunciation (page 48)
SYSTEM OPERATIONAL SETTINGS
System settings are those that enable or disable the Falcon
functions in general or that alter the behavior or availability of
multiple configurable items. See Table 7.
To Next Page
Loading...
Need help?
General
