Rockwell Automation 1757-PROCESSLINX ProcessLinx OPC Server to Server Software User Manual - Manual (Page 49)

Publication 1757-UM002B-EN-P - January 2003
ProcessLinx Runtime Operation 4-5
Verifying OPC Tags In runtime, you can verify the status of all active OPC Items. Select Utility
⇒
Verify OPC Tags from the main menu to check all OPC Items. If an error is
found, a message is displayed in the Message pane. A successful verification
displays these messages:
MSG:: Verifying OPC Tags in Server A...
MSG:: OPC Tags Verified!
MSG:: Verifying OPC Tags in Server B...
MSG:: OPC Tags Verified
When you select the ‘Verify Tags...’ option from the Main Menu in runtime
mode, ProcessLinx verifies each Pipe. For each Pipe both Servers are checked
to see if there is a connection to them, if so then each Active Group of each
client is verified. If not then an error is logged.
Verifying a group means that for each tag in each group ProcessLinx checks
that the tag is active and that is has a connection to its corresponding item in
the Server. If it does not, then a message displays for that item in the Message
pane. A message also displays for each Inactive Group.
Ping The ping function verifies access to a remote node. To ping a remote node,
select Utility
⇒
Ping... from the main menu. In the Ping dialog box, enter the
host machine’s name or IP Address and click OK. The node’s status is
displayed in the Message pane. A successful Ping displays the message
“Ping>Host <localhost> is alive!” where localhost is the desired host machine’s
name. A failed Ping message also indicates that the host is unreachable or is
not responding due to a timeout or a network connection problem.
OPCShutdown In runtime, ProcessLinx supports the IOPCShutdown interface and the
Shutdown Request functionality from OPC Servers. If supported by the OPC
Server, when the Server needs to shutdown, it can use this interface to send a
shutdown request to ProcessLinx. ProcessLinx will then disconnect all items,
groups and interfaces connected with that Server and will wait the amount of
time specified by the 'Retry Wait Period' before attempting a connection to the
redundant node (if configured).
If redundancy is not defined then ProcessLinx will attempt to connect to the
original Server. The Server must be designed to not start up again (or deny
access) if it is truly 'shutdown'. ProcessLinx will enter an infinite retry loop
where it will continue to try reconnecting with that Server at the 'Retry Wait
Period' until connection is re-established.