2 device block, device behavior, Cyclic data traffic acyclic data traffic – INFICON BCG450-SP ATM to Ultra-High Vacuum Triple Gauge (Profibus) User Manual
Page 21

tira41e1 (2005-06) BCG450SPv1.cp
21
This parameter corresponds to the Manufacturer Exception Detail Alarm Byte 0 of
the Exception Detail Alarm (ID 27).
This parameter corresponds to the Common Exception Detail Warning Byte 0 of
the Exception Detail Warning (ID 28).
This parameter corresponds to the Device Exception Detail Warning Byte 0 … 3 of
the Exception Detail Warning (ID 28).
This parameter corresponds to the Device Exception Detail Warning Byte 4 … 6
the Exception Detail Warning (ID 28).
This parameter corresponds to the Manufacturer Exception Detail Warning Byte 0
of the Exception Detail Warning (ID 28).
The BCG450-SP behaves as described in the status diagram below.
NORMAL
RUNNING
OK
SELFTESTING
EXECUTING
SELFTEST
EXCEPTION
ABORT
(0)
CRITICAL
FAULT
INIT
IDLE
(1
4
)
(1
3
)
(1
0
)
(8
)
(5)
(9)
(4)
(1
3)
(13
)
(2
)
(1
)
(3
)
After the start, the gauge independently runs through the INIT and SELFTESTING
status and eventually changes to the IDLE status (if there is no error) or to the
SELFTEST_EXCEPTION status (if there is a gauge error).
When data traffic is taken up, a difference has to be made between cyclic and
acyclic data traffic.
As soon as cyclic data interchange is taken up, the gauge automatically changes to
the EXECUTING status.
In acyclic data traffic, a START service has to be transmitted to bring the gauge to
the EXECUTING status.
3.1.1.16 Copy Manufacturer
Exception Detail Alarm 0
ID 207
3.1.1.17 Copy Common Exception
Detail Warning 0
ID 208
3.1.1.18 Copy Device Exception
Detail Warning 0 … 3
ID 209
3.1.1.19 Copy Device Exception
Detail Warning 4 … 6
ID 210
3.1.1.20 Copy Manufacturer
Exception Detail
Warning 0 ID 211
3.1.2 Device Block,
Device Behavior
Cyclic data traffic
Acyclic data traffic