RoviSys OPC90 - Page 65

OPC90 Server
causes communication with the interface to occur
normally with the input values to the AOL and DOL
blocks to be automatically updated with simulated
values that would normally be provided by an OPC
client. This simulation option also allows
configuration of the percent of the total values to
change per second.
TAG to
iley
d
STARTUP Array Config Picks the initial OPC status that will be reported
OPC clients for all of the tag values until the Ba
interface has been initialized with the configure
database and has begun to report the actual
values.
STA all
n
RTUP Complete Boolean Config Normally the STARTUP device tag resets when
of the points are established in the CIU. Setting
this option delays the STARTUP reset conditio
until after all of the blocks receive initial values
from the ABB Bailey DCS.
Set
Max Exception Timeout
, DOL,
ODD, OMSDD, ORCM, ORMC, ORMSC and
s do not
utput
bad quality
therefore
ints in the
ABB Bailey system. This property should only be
used when OPC clients writing the input values to
even when
perty).
Bad Output Quality on Boolean Config The QUALITY tag will indicate bad for AOL
OSTN blocks when writes to the input tag
occur within the block’s exception report o
max time setting. When this occurs the
condition is also written to the CIU and
propagated to the users of these data po
these blocks does so on a regular basis
the value has not changed (see next pro
Any Input Write Applies to
All Out
Boolean Config With this option set, an input write to any AOL,
lity
option
d
lar basis
whereas analogs usually are. A write to any input
value becomes the indicator the OPC client is still
put Blocks
DOL, ODD, OMSDD, ORCM, ORMC, PRMSC and
OSTN block reset the internal bad qua
maximum timer for all of these blocks. This
is useful when digitals are not changing an
therefore not being written on a regu
alive.
CO
UPD
structs OPC90 to report all data change tags at
the data change cycle even when they have not
d from the last reported value. This option
OPC data stale or bad when it is not received on a
be set.
NTINUOUS OPC Boolean Config In
ATES
change
is useful when interfacing to OPC clients that mark
regular basis. Most clients do not need this option
to
XRP Supervisory control writes to DD, MSDD, RCM,
RMC, RMSC and STN blocks are sent directly to
the Bailey system without updating the OPC tag
se. The OPC tag database gets updated
the Bailey exception report is received
firming the write was received and accepted.
This option may be useful when implementing OPC
so
tion
WRITE CONFIRM Boolean Config
databa
en wh
con
client supervisory control ramping functions. Al
some Bailey block logic could have supervisory
control locks in place. These locks prevent the
block from completing the request but no excep
report is generated indicating the request was
rejected.
The RoviSys Company Version 7.0 Page 65