Product specifications

SPlus Operations P13 Connectivity Guide PROCONTROL P13 OPC SERVER
66 2VAA001153C
Figure 3-50: Exchange of Acknowledge Information between Partner Nodes
How to define a Partner Node is described in 3.3.3.4.9 PARTNERNODE[X] Instruction.
3.8.2 Synchronization of Event Suppression
Via the partner node connection, the event suppression configuration is synchronized.
3.8.3 Propagation of Node-Specific Partner Events.
Certain event types are node-specific, i.e. can concern only the OPC server on one of the redundant nodes. These
node-specific events are
 Command tracking messages
 P13 system events.
To provide these event messages to a client connected to the partner node, these types of events are reported to
                  
behind the node.
Figure 3-51: Example of a Message received from PartnerNode CHIIT067
3.8.4 Bus Connection Controlled Redundancy Switch-Over
A pair of redundant PServers can cause an appropriate redundancy switch-over based on the state of their bus
connection states. The two redundant PServers cyclically read the number of active bus connections from its partner. If
a PServer recognizes its own number of active busses as less than that of its partner (i.e. its connection state is worse
than that of the partner), it sets itself to state OPC_STATUS_COMM_FAULT. This state can be used by the client (e.g.
800xA PPA) to do a switch-over to the better node. The PServer in OPC_STATUS_COMM_FAULT state sets itself to
running state when it recognizes its number of active bus connections as equal or bigger compared to that of the
partner.
To activate bus connection controlled redundancy switch-over, the extended partner node connection
(PARTNERNODEX, see 3.3.3.4.9 PARTNERNODE[X] Instruction.) must be used.
The following extract of an event log illustrates the messages caused by redundancy bus connection monitoring.
Figure 3-52: Redundancy Bus Connection Monitoring Messages
3.9 VPC Mode “Individual Command Signals”
3.9.1 Concept
           
object is used. Additionally a global release signal common to all control objects is necessary to enable the execution of
the command.
Specific handling is used for acknowledge of a control object. The individual acknowledge signal must be paired the
global acknowledge.
PServer Node01
PARTNERNODE,
Node02
PServer Node02
PARTNERNODE,
Node01
Acknowledge
Information