Filter
Top Products
4/00 UDC 3300 Controller Product Manual 249
Status Tests
Table 9-5 lists the Status tests, the reason for their failure, and how to
correct the failure.
Table 9-5 Status Tests
Test
(Lower
Display)
Definition Upper
Display
Reason for Failure How to Correct the Failure
FAILSAFE
Failsafe Fault NO No Failure
FAILSF2
(Loop 2)
YES Burnout configured for none
and input fails.
–RAM TEST failed
–CONFTEST failed
–CALTEST failed
1. Step through the rest of the STATUS
check to identify the particular failure.
Also see Table 9-6, Background tests
RAM TEST
PASS No Failure RAM test passed.
RAM test run at
power-up
FAIL RAM Failure 1. Power cycle to see if the error clears.
PASS No Failure Configuration checksum passed.
CONF
TEST
Configuration
Checksum
FAIL Configuration data is in
error.
1. Step through STATUS tests – the
controller will recalculate the
checksum.
2. Check all configuration prompts for
accuracy. See Section 3 -
Configuration
CAL TEST
Working
Calibration
PASS No Failure Working calibration checksum passed.
FAIL The working calibration
constants in the controller
are in error.
1. If the controller has not been field
calibrated, see Section 3 -
Configuration and change the input to
a different type. Enter it, loop through
the status tests, then return the input
type to the original one.
2. If the controller has been field
calibrated, recalibrate the controller.
FACT CRC
Factory
calibration test
PASS No Failure Factory calibration cyclic redundancy test
passed
FAIL Factory set input constants
have been changed due to
the change in input type.
1. Cycle through Status to clear the error.
2. Check the calibration. Make sure 0 %
and 100 % are correct values.
3. Recalibrate if step 1 is unsatisfactory.
Refer to Section 7 - Input Calibration.