OPC90 Server
6 Groups
op at the group and block level. A block can be
oved from one group to another by dragging it to another group and dropping it
bled when a second instance of OPC90 is being used as the user
terface when running as a service or embedded (started automatically by an
cces
ted s
l roup C
successfully connected to the OPC90 Serv nt group is
into ver. C Client group is created, OPC Tags can
e added to ntim O of
tags sele runt ta nt
PC grou ha .
ser
OPC client group does not exist anymore.
There are two different types of OPC Groups to keep in mind. The first is the
OPC Server group. This is created within the OPC90 Server configuration and is
simply a collection of OPC90 Server Blocks or other groups. An OPC90 Server
group can be compared to a directory within a file system. Where in this case the
root directory is always an OPC90 DEVICE block. An OPC90 group is only used
to store other OPC90 groups or collections of similar OPC90 blocks. No tags
exist within an OPC90 group (tags only exist within an OPC90 block). Note that
OPC90 supports drag and dr
m
there. Likewise, dragging an entire group is also supported. All blocks within
that group are included in the drag and drop operation. The drag and drop
feature is disa
in
OPC client a s).
The other group
C
is crea by and exist within an OPC Client and is referred to
as the OPC ient g . The OPC lient creates this group after it has
er in runtime. The OPC Clie
an interface the ser After an OP
then b it in ru e. Thus the PC Client group acts as a collection
tags not blocks. OPC90 Server Addr
Server
ess space can be browsed and then OPC90
ime. These cted in gs are then placed into the OPC Clie
group. An O
When the client disconnects
Client p does not
from the
ve to match an OPC90 Server group
ver all tags are disestablished and the
The RoviSys Company Version 7.0 Page 36