Identifying gpl variables – Rockwell Automation T3831 ICS Regent Communications Package for Winterpret User Manual
Page 13
Communications Package for
W
INTERPRET
(T3831)
P D - 6 0 4 1 M a r c h , 0 6
13
Table 3. Example of Serial Port Settings for Four Regents.
Port
#
Node
#
Port Type
Baud
Rate
Data
Format
Network
Leg
Regent
1
2
4
1
1
Net Master
Net Slave
19.2K
19.2K
8+1+Odd
8+1+Odd
1
2
Regent
2
2
4
2
2
Net Slave
Net Slave
19.2K
19.2K
8+1+Odd
8+1+Odd
1
2
Regent
3
4
6
3
3
Net Slave
Net Slave
19.2K
19.2K
8+1+Odd
8+1+Odd
1
2
Regent
4
3
5
4
4
Net Slave
Net Master
19.2K
19.2K
8+1+Odd
8+1+Odd
1
2
In this example, each Regent has a unique node number, and
both GPL ports for an individual Regent are assigned the
same node number. For each Regent, the two ports used for
GPL communications are ports on different communications
modules. This makes the network fault tolerant in case of a
communications module failure and subsequent module
removal and replacement. In the example, Regent 1 is the
Net Master for Leg 1 of the GPL network and Regent 4 is the
Net Master for Leg 2. All other GPL ports are configured as
Net Slaves. The Baud rate and data format are configured
the same for all GPL ports.
Identifying GPL variables
An example of variable definitions for four Regents is shown
in Table 4. The variables listed in each Regent’s column
would need to be defined in the I/O or shared variable
definitions for that Regent.
For each Regent, the variables are arranged in two rows to
illustrate whether the Regent will output the variables to the
GPL network (to one or more other Regents), or whether the
Regent will input the variables from the GPL network (from
another Regent).