User manual

136 Publication ENET-UM001I-EN-P - January 2010
Chapter 9 Communicate with PanelView Terminals
Organize Controller Data
for a PanelView Terminal
Organize data for a PanelView terminal based on how the data is used.
To access the I/O tags of the PanelView or PanelView Plus terminal, use the
following address
format:
where:
Connections to RSView
Applications
To establish communication to an RSView application, configure RSLinx
software to collect tags from the controller. An RSView 32 or RSView
Enterprise application uses RSLinx software as a data server.
RSLinx Enterprise software defaults to four read c
onnections and one write
connection per configured controller. Modify the RSLinx software
configuration as needed.
Controller Data Organization
For data that is Do this
Time critical (for example, data
that controls a mac
hine)
Use the I/O tags of the terminal.
The tags for this data were created when you added the terminal to the I/O configuration of the
controller
. They resemble the I/O modules’ tags.
Not time critical Create arrays to store the data.
1. For each screen, create a BOOL array with enough elements for the bit-level objects on the screen.
For example, the BOOL[32] array gives you 32 bits for push buttons or indicators.
2. For each screen, create a DINT array with enough elements for the word-level objects on the
screen.
For example, the DINT[28] array provides 28 values for numeric entry controls or numeric displays.
Terminal Function Requirement
Writes the data name_of_terminal:I.Data[x].y
Reads the data name_of_terminal:O.Data[x].y
This address variable Is
name_of_terminal Name of the instance in the I/O configuration of the controller.
x Element of the input (I) or output (O) structure.
y Bit number within the input or output element.