Honeywell Experion C300 - C300 Redundancy-Related Notifications

C300 Redundancy-related notifications
Become Primary command – BECMPRICMD
R301.1 Experion C300 Controller User's Guide 201
11/06 Honeywell
Table 14 Redundancy-Related Notifications
Notification Description RDNSYNCSTATE
Backup State The secondary generates the Backup State Change Event
as part of event regeneration. A transition to the Backup
State only occurs as part of startup or a redundancy role
change. In both of these cases, any previously existing
notification connection is broken, a new notification
connection is reformed, and event regeneration is
commanded.
Not Synchronized The primary and secondary are configured for redundancy
but the redundant pair is not synchronized or not in standby.
The primary is configured for redundancy via C300 block
load of the MODISREDUN parameter. A secondary can
only be in the secondary role if, retention startup
remembered that it was previously configured redundant,
and the C300 is configured with the even Device Index.
The “Not Synchronized” alarm returns to normal upon
configuring the primary at the odd Device Index as non-
redundant or upon entering the Synchronized or Standby
state.
Redun Incompatible
Partner
Both the primary and secondary controllers generate this
notification upon determining that their partner module is not
compatible for attempting initial-sync.
INCOMPATIBLE
Redun No Partner Both the primary and secondary controllers generate this
notification when the partner is not present.
Note that the primary controller only generates this
notification when it is either explicitly or implicitly configured
for redundant behavior. Explicit redundancy configuration
occurs when the C300 block is loaded with MODISREDUN
set ON, and implicit redundancy configuration occurs in the
absence of any configuration, (C300 in the NODB state).
NOPARTNER
Redun Non-
Redundant
Only the controller explicitly configured non-redundant
generates this notification when the partner is not present.
NOPARTNER
Redun Partner
Visible on FTE
Both the primary and secondary controllers generate this
notification upon detecting a compatible partner visible
across FTE.
Note that partner compatibility checks across FTE are
triggered by the Alternate Synchronization command.
PARTNERVISBL
Redun Partner
Visible on Redun
Link
Both the primary and secondary controllers generate this
notification upon detecting a compatible partner visible
across the redundancy private-path.
PARTNERVISBL