Troubleshooting the guarded peer-link, Gpl status information – Rockwell Automation T3831 ICS Regent Communications Package for Winterpret User Manual

Page 30

Advertising
background image

Communications Package for W

INTERPRET

(T3831)


3 0

Industrial Control Services

Troubleshooting the Guarded Peer-Link

GPL Status Information

After you use the Load, Connect and Start Network
commands of W

INTERPRET

to activate the GPL operations in

the Regent systems, each Regent performs diagnostics on the
GPL communications. Make sure that you follow the steps
outlined in the Loading, Connecting and Starting the
Guarded Peer-Link, starting on page 21. If you have correctly
configured and activated the Guarded Peer-Link, the
following GPL system variables will report the status of the
GPL communications.

GPLINTEMP

Always on if valid GPL input templates
are loaded.

GPLOUTTEMP

Always on if valid GPL output templates
are loaded.

GPLCONNECT

Always on if the GPL has been Connected.

GPLMSTRSCAN

Always on for a Regent with a Net Master
port in the GPL network is started.

GPLDATAxx

For every configured node xx (ranging
from 01 to 31) the associated GPLDATAxx
system variable should always be on if
valid fresh data is being received from at
least one leg of the GPL network. If this
bit ever turns off for a configured node,
then there is usually a problem associated
with that node (e.g. not connected).

The GPL system variables contain three types of GPL fault
status information.

First, a general fault bit named GPLFLTANYBUS will turn on
if any type of GPL fault has been detected. This bit should
always be monitored because it provides a general
annunciation of any type of GPL communications error.

Second, port fault bits named GPLPxFAULT (where x is 1
through 6 for the port number) will turn on to indicate which
GPL port is not operating correctly. By monitoring these bits,

Advertising