OPC90 Server
Th Bailey system will receive data
CIU interface, module two and block num
e
from this block at the ring and node address of the Bailey
ber defined by the block attribute.
t be written when a bad start or fault
condition occurs.
:
The OUT tag reports the state of the device as off (0) or on (1). This
not s
d
e RED_
the
curren
a
ag cond
ered to be in
e an
r bo
and o
vice can be
commanded to the on state its four interlock inputs and two start permissive
ll b
The
pu
ration but
Baile
. T
eported.
a
ir st
he
hen the
ma
on w
he int
being set,
this is considered a bad start. The client indicates a bad start condition using the
RT tag
ad st
also o
set after the device has been commanded on and a feedback waiting time has
The cl
a
dicate
ART tag
n
ates th
ags. If a
edback
start,
con
ault and
writ
OUT
ither a bad start or fault condition occurs, the client must use the ERR_CODE
indicate the reason for the condition. Bailey predefines the error codes as
imp
wh
ind
e
use
ack
FA
2.) The RMC type code is a number used by the Bailey consoles to identify characteristics of its
RCM faceplate display. Currently a value of zero is the only valid code.
3.) When the Device block “Set bad quality of max exception timeout” property is enabled, the
QUALITY tag of this block will be set bad if writes to the block input(s) do not occur within the
Exception Report Output Max Time setting of the block. When this occurs, bad quality will
also be written to the CIU and therefore propagated to the users of the block data within the
ABB Bailey system. The quality can also be set bad by writing a one (1) to this tag.
4.) The RMC ERR_CODE codes are defined as: 0 – no error, 1 – stopped by logic, 2 – interlock
one is not set, 3 – interlock two is not set, 4 – interlock three is not set, 5 – interlock four is
not set, 6 – feedback one is not reset, 7 – feedback two is not reset, 8 – feedback one is set,
9 feedback two is set. The appropriate error code mus
ication
Appl
block does
upport mo e. Th
TAG tag allows the client to indicate
device is
tly under red t
ition. It is always consid
manual mod
d unde
th logic
perator control. Before a de
inputs must a
e set.
interlock in
les
ts are implied to the block ope
are not reported
The client indic
to the
tes the
y conso
he start permissive inputs are r
PERM1 and PERM2 tags. W
ate using t
device is com
nded
ithout t
erlocks or permissive inputs
BAD_STA
. A b
art can
ccur when the feedback signals do not
expired.
ient must lso in
this condition as a bad start using the
BAD_ST
. The clie t indic
e two feedback signals writing to the F1
and F2 t
ny interlock or fe
signals are lost after a successful
the device is
sidered to be in f
de-energized. The client indicates this
condition by
ing a zero to the
tag and setting the FAULT tag. When
e
tag to
indicated in the above note concerning the ERR_CODE tag. The Bailey
lementation of the RMC block defines a hold condition that optionally applies
en a bad start arises. The choices are no hold, hold bad start and error
icators until successful start or hold but reset bad start and error indicators on
next stop or start request. The client indicates the hold condition by setting th
HOLD_STATUS tag. It should be reset on the next start request. The client
s the FAULT_ACK tag to indicate a fault has occurred and receive an
nowledgment of that fault when the Bailey console writes a value of zero to
ULT_ACK.
The RoviSys Company
Version 7.0
Page 97
