COR User Guide
Page 27
Two examples of when Fallback might "kick in":
❖
If the AquaBus cable between an AquaBus module and the rest of the APEX
system gets disconnected
❖
If the controller fails
The Fallback command requires one of four parameters: ON, OFF, a profile name, or a
numeric value, which is the desired percentage of the COR maximum speed/intensity if
Fallback kicks in.
Examples:
•
Fallback ON
•
Fallback OFF
•
Fallback COR-Slow
•
Fallback 75
Experienced APEX users may recognize that the Fallback % syntax as new; it was
introduced in the same new firmware which contains COR support. Note that in the
example above, the % symbol is not used, and should not be specified in the
programming; just use the number.
Fallback 100
has the same effect as
Fallback ON
;
Fallback 0
has the same effect as
Fallback OFF
.
Neptune Systems recommends the use of either the
Fallback ON
or
Fallback
%
option for
the COR when used as a return pump. Other, less-common, cases may be better suited
by use of
Fallback OFF
or
Fallback %
with a reduced pump speed specified. Typically, if
the COR has been calibrated,
Fallback ON
or
Fallback 100
are the best choices. The use
of
Fallback
profile-name
is not recommended with the COR; generally, if a state other
than ON or OFF is desired,
Fallback %
is preferred, as it is easier and simpler than using
a profile.
Fallback of a COR driver will occur approximately 100 seconds after the COR driver
detects a loss of communications. At that moment, the COR driver logo LED will begin to
flash orange and the pump will be operating at the state or speed specified. If
communications with the APEX are restored, then the COR will resume operating with its
normal programming. If the COR is in Fallback mode and either COR button is pressed,
the COR will change from Fallback mode into Standalone Mode and the COR driver logo
LED will change from flashing to being lit solid orange. The buttons may then be used to
manually adjust pump speed.
