AI Function Block
December 2009
4-133
Troubleshooting
Refer to table 4-55 to troubleshoot any problem that
you encounter.
Table 4-55. Troubleshooting
Symptom Possible Causes Corrective Action
Mode will not leave OOS Target mode is not set Set target mode to something other than OOS
Configuration error
BLOCK_ERR [6] will show the configuration error bit set.
The following are parameters that must be set before the
block is allowed out of OOS:
CHANNEL [15] must be set to a valid value and cannot
be left at initial value of 0.
XD_SCALE [10]. UNITS_INDEX must match the units in
the transducer block channel value.
L_TYPE [16] must be set to Direct, Indirect, or Indirect
Square Root and cannot be left at an initial value of 0.
Resource block
The actual mode of the Resource block is OOS. See
Resource Block Diagnostics for corrective action.
Schedule
Block is not scheduled and therefore cannot execute to go
to Target Mode. Schedule the block to execute.
Process and/or block alarms will not work
Features
FEATURES_SEL [18] in the resource block does not have
Alerts enabled. Enable the Reports Supported bit.
Notification
LIM_NOTIFY [32] in the resource block is not high enough.
Set equal to MAX_NOTIFY [31], also in the resource block.
Status Options
STATUS_OPTS [14] has Propagate Fault Forward bit set.
This should be cleared to cause an alarm to occur.
Value of output does not make sense
Linearization Type
L_TYPE [16] must be set to Direct, Indirect, or Indirect
Square Root and cannot be left at an initial value of 0.
Scaling
Scaling parameters are set incorrectly:
XD_SCALE.EU0 and EU100 should match that of the
transducer block channel value.
OUT_SCALE.EU0 and EU100 are not set properly.
Cannot set HI_LIMIT [28], HI_HI_LIMIT
[26], LO_LIMIT [30], or LO_LO_LIMIT [32]
VALUES
Scaling
Limit values are outside the OUT_SCALE.EU0 and
OUT_SCALE.EU100 values. Change OUT_SCALE [11] or
set values within range.
4
To Next Page
Loading...
Need help?
General
