1
1
7
7
5
5
6
6
-
-
Q
Q
S
S
1
1
0
0
4
4
A
A
-
-
E
E
N
N
-
-
P
P
C
C
o
o
n
n
t
t
r
r
o
o
l
l
L
L
o
o
g
g
i
i
x
x
Q
Q
u
u
i
i
c
c
k
k
S
S
t
t
a
a
r
r
t
t
Page 25
FYI
The name Local indicates that these tags are associated with a module that is in the
same chassis as the controller. The number between the colons is the slot number of
the module; in this case, the module is in slot 0. The characters appearing after the last
colon (i.e., the C, the I, and the O) indicate whether the data is
C
onfiguration,
I
nput, or
O
utput data. This particular module has all three types of data.
The Scope field above the Tag Name column displays the scope for the tags that are
displayed. The scope defines the range in which tags are recognized within the
routines. Tags created at the controller scope are accessible to all routines in all
program folders; those created at the program scope are accessible only to routines
within that single program folder.
In this case, the tag scope is Controller1 (controller), which indicates that the tags are
valid for all routines in all program folders in this controller file. If the scope field
contained a program name, then the tags would be valid only for the routines in the
program folder specified.
2. Click on the
+
sign in front of the
Local:0:C
tag to display the configuration tags for this module.
The Data Monitor refreshes to show you all of the tags underneath the Local:0:C tag. If you cannot see
the entire tag name and value, drag the edges of the respective columns to increase their width.
Allen-Bradley Parts
