RoviSys OPC90 - Page 10

OPC90 Server
Composer, G.Michaels DBDOC, etc)
POLL
Poll Value any block
RCM Remote Control Memory – RCM 62
RMC Remote Motor Control – RMC 136
RMSC Remote Manual Set Constant – RMSC 68
SOE Sequence of Events 99, 243
SPEC Specification – SPEC any block
STN
Control Station – STN 21, 22, 23, 80
TXT Text Selector – TEXT 151
TEXTSTR
Text String - TEXTSTR 194
The common Bailey computer interfaces used to gain access to the Bailey
exception report blocks presented in the above table also support the ability to
allow a system to emulate and output most of these same point types. They are
called “output report” block types. Bailey consoles receive the point type,
exception reported data directly from the Bailey interface in the same format as if
it was coming from an equivalent Bailey controller. This allows the predefined
Bailey console faceplates for each of these control point types to be utilized when
receiving data from the OPC90 Server report point types. Instead of addressing
the tags to a block in a Bailey controller, they are addressed to a block number
assigned within the Bailey interface that OPC90 is communicating. The ring and
node address to use is that assigned to the interface with a fixed module address
of two.
The following table presents a list of Bailey interfaces supporting the output
report block types.
Bailey Interface Bailey System
Max. Number
of points
Supported by
OPC90 Server
NCIU02 Network 90 2,500 Yes
NCIU03 Network 90 5,000 Yes
NCIU04 Infi 90 10,000 Yes
INPCI02 Infi 90 / Symphony 5,000 Yes
IIMCP01 Network 90 10,000 Yes
IIMCP02 Infi 90 / Symphony 30,000 Yes
INICI01 Infi 90 / Symphony 10,000 Yes
INICI12 Infi 90 / Symphony 10,000 Yes
INICI13 Infi 90 / Symphony 30,000 Yes
INICI03 Infi 90 / Symphony 30,000 Yes
The RoviSys Company Version 7.0 Page 10