Rockwell Automation T8030S Trusted OPC Server Package - Manual (Page 12)

Trusted
TM
OPC T8030S
Issue 23 April 10 PD-T8030S 12
Trusted TM Ethernet IF
Controller # 1
Controller # 2
1.2. Trusted
TM
OPC Architecture
The server can be divided into four main functions: The Browse Interface, the OPC Data Access
Interface, the OPC Alarms & Event Interface and the Communications Interface.
1.2.1. The Browse Interface
The server provides a list of tag references that OPC clients can browse in a standard manner. The
root node is the Trusted
TM Ethernet Interface. All controllers defined from ‘Edit/Controllers’ are shown
as sub-items. Selecting a controller in the tree will show a list of its tags in a window to the right.
Figure 2 Example Browse Tree Structure
Figure 2 shows an example browse tree structure. If Controller # 1 is selected, and then a tag on the
right is selected, the path would be:
TrustedEthernetIF.Controller1.
Where may be a controller level tag or a further hierarchical path to a data point.
1.2.2. OPC Data Access Interface
When an OPC Data Access client attaches to the server, a unique server object is created within the
main server application. The client can create and edit groups within this server object. Each group
has a number of tag references and an update rate. Every time the tags are to be updated, the server
will inform the client of the new values, quality, time, etc.
See the specific OPC Data Access client documentation for further information.
1.2.3. OPC Alarm & Event Interface
When an OPC Alarm & Event client attaches to the server, a unique server object is created within the
main server application. Each time an event occurs, the server informs the client of the event. Event
information includes the tag name, value, time the event occurred, etc.
See the specific OPC Alarm & Event client documentation for further information.