7.11.17 Troubleshooting
Refer to Table 7-26 to troubleshoot any problems that you encounter.
Table 7-26 Troubleshooting
Mode will not leave
OOS
Process and/or block
alarms will not work
Value of output does
not make sense
1. Target mode not set
2. Configuration error
3. Resource block
4. Schedule
1. Features
2. Notification
3. Status Options
1. Linearization Type
2. Scaling
1. Set target mode to something other than OOS.
2. BLOCK_ERR will show the configuration error bit set. The
following are parameters that must be set before the block is
allowed out of OOS:
a. CHANNEL must be set to a valid value and cannot be left at
initial value of 0.
b. XD_SCALE.UNITS_INDX must match the units in the
transducer block channel value.
c. L_TYPE must be set to Direct, Indirect, or Indirect Square Root
and cannot be left at initial value of 0.
3. The actual mode of the Resource block is OOS. See Resource
Block Diagnostics for corrective action.
4. Block is not scheduled and therefore cannot execute to go to
Target Mode. Schedule the block to execute.
1. FEATURES_SEL does not have Alerts enabled. Enable the Alerts
bit.
2. LIM_NOTIFY is not high enough. Set equal to MAX_NOTIFY.
3. STATUS_OPTS has Propagate Fault Forward bit set. This should
be cleared to cause an alarm to occur.
1. Does not make L_TYPE must be set to Direct, Indirect, or
Indirect Square Root and cannot be left at initial value 0.
2. Scaling parameters are set incorrectly:
a. XD_SCALE.EU0 and EU100 should match that of the
transducer block channel value.
b. OUT_SCALE.EU0 and EU100 are not set properly.
Cannot Set HI_LIMIT,
HI_HI_LIMIT
LO_LIMIT, or
LO_LO_LIMIT
Values
1. Scaling 1. Limit values are outside the OUT_SCALE.EU0 and
OUT_SCALE.EU100 values. Change OUT_SCALE or set values
within range.
To Next Page
Loading...
