ABB 2600T Series Instruction Manual page 117

266 with foundation fieldbus communication
Table of Contents

Advertisement

2 6 0 0 T S E R I E S | P R E S S U R E T R A N S M I T T E R S | O I/ 2 6 6/ F F - E N R E V. E
Operating Mode
In manual mode, the outputs are disconnected from the algorithm and the user can set the values of O UT, RTOTAL, OUT_TRIPand
OUT_PTRIP for test purposes. No integration takes place. When the block is switched to Auto, the integration starts from the value
set manually. Each write to OUT or RTOTAL shall increment the N_RESET counter. In auto mode, the outputs follow the algorithm.
Diagnostic
Block_Err
Possible Reasons
– TIME_UNIT1 = 0
– TIME_UNIT2 = 0
– INTEG_TYPE = 0
– IF INTEG_OPTS = IN_1 ACCUMULATE
Block Configuration error
– IF INTEG_OPTS = IN_2 ACCUMULATE
– IF INTEG_TYPE = PERIODIC
Input Failure/process
The value linked in input coming from the upstream blocks has BAD Status.
variable has BAD status
Out-of-Service
The Actual_Mode is OUT OF SERVICE
NOTE A: The specific block cannot be switched out from OUT OF SERVICE due to the Configuration Error. The Bad-Configuration
Error Status is overridden by the Bad-Out Of Service Status.
OUT status
If an input has a status of Uncertain or Bad, it shall be treated as explained below. The limit status of the inputs is ignored, as is the
substatus. Either Good(C) or Good(NC) are accepted as good.
The increment calculated from an input has an internal status that is either good or bad. If the input status is Good(C) or Good(NC)
the increment status is good. If the input status is Uncertain, the increment status is bad, and the last good value is used unless
the option Use Uncertain is set in INTEG_OPTS, and then the increment status is good and the new value is used. If the input status
is Bad, the increment status is bad, and the last good value is used unless the option Use Bad is set in INTEG_OPTS, and then the
increment status is good and the last good value is used.
The two increments are added together, and the resulting status is the worst of the two.
The option Add zero if bad in INTEG_OPTS causes the net increment to be zero if its status is bad.
The percentage of bad or uncertain and bad counts may be determined by calculating the value of PCT_INCL from Rtotal and
Atotal.
Since Atotal is the sum of increments with good and bad status, and Rtotal is the sum of increments with bad status, Atotal minus
Rtotal is exactly equal to the total of increments with good status. If msp is used to mean "most significant part" and Atotal is not
zero then the percent of good values may be calculated as:
PCT_INCL = 100 * ( 1 - (msp of Rtotal) / (msp of Atotal) )
If Atotal is zero, then PCT_INCL shall be 100 if Rtotal is also zero, or 0 if Rtotal is not zero.
If the block mode is Auto, if PCT_INCL ≥ GOOD_LIM, the status of OUT shall be Good, or else if PCT_INCL ≥ UNCERT_LIM, the status
of OUT shall be Uncertain, or else the status of OUT shall be Bad.
If the block mode is Manual, then the status of OUT, OUT_PTRIP, and OUT_TRIP will be Good (NC) constant when then status option
Uncertain if Man is not selected. If this status option is selected and the block mode is manual, then the status of these three
outputs will be Uncertain constant. No limits are applied to the output.
o
PULSE_VAL1 = 0
o
PULSE_VAL2 = 0
o
CLOCK_PER = 0
OUT Status
BAD + Out Of Service
See Note A
Calculated according the algorithm.
See the OUT STATUS section below
BAD + Out Of Service
117

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

266

Table of Contents