EasyManua.ls Logo

Honeywell Experion C300 - Page 223

Honeywell Experion C300
270 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
C300 Redundancy-related notifications
OPM Status – RDNOPMSTATUS
R301.1 Experion C300 Controller User's Guide 207
11/06 Honeywell
Notification Description
RDNOPMSTATUS
Parameter
any loss-of-sync triggers this behavior, the most probable
loss-of-sync cause is the inability of the secondary controller
to interpret the peer dynamic data format. The secondary
controller block’s LASTOPMNAME parameter is blank in this
case. This notification represents abnormal OPM session
termination.
OPM Block Data
Failure
The one-time OPM initial-sync transfer of dynamic data that
occurs with control frozen contains two components: peer
dynamic data and block dynamic data, with the latter
typically being the larger of the two. A loss-of-sync
occurrence while transferring block dynamic data causes the
primary controller to generate this notification and to set the
RDNOPMSTATUS parameter to BlockDataFailure. This
notification represents abnormal OPM session termination.
Although any loss-of-sync triggers this behavior, the most
probable cause for loss-of-sync is either the inability of the
secondary controller to interpret the block dynamic data
format or the secondary controller has no destination block
to receive the dynamic data. The latter is possible in the
presence of a ghost block; a ghost block exists if the primary
controller has knowledge of a block that was not instantiated
in the secondary controller during OPM secondary
checkpoint restore.
The secondary controller block’s LASTOPMNAME
parameter indicates the name of the last block to be (on-
process) migrated. LASTOPMNAME is used to isolate the
name of the first CEE subordinate block that has detected a
dynamic state data error. In the special case of a ghost
block, LASTOPMNAME is either blank (because the ghost
block name no longer exists in the ERDB), or indicates the
name of a block that is not loaded to the controller (meaning
that the block only exists on the Control Builder project tree).
BlockDataFailure
OPM Session
Timeout
Control is frozen upon commencing the one-time OPM
initial-sync transfer of Dynamic Data. The redundancy
subsystem aborts controller OPM if control is frozen longer
than the maximum specified time, (i.e. 10 seconds for C200
and 20 seconds for C300). As a consequence, the
redundancy subsystem generates this notification and sets
the RDNOPMSTATUS parameter to SessionTimeout. This
notification represents abnormal OPM session termination.
SessionTimeout

Table of Contents

Related product manuals