TROUBLESHOOTING
START-UP FAILURES
I-E96-314A
5 - 3
Hardware Failure
This part of the troubleshooting section covers start-up fail-
ures that do not appear as configuration errors and how to
troubleshoot those failures. Hardware failures are a result of
incomplete or incorrect installation of the related FCS hard-
ware or a failure of the FCS module.
The operator interface will display an error message if there is
a hardware failure. If the operator interface is an OIS, the
operator can access the Module Problem Report (MPR). The
OIS displays a NOT RESPONDING message in the MPR when
there is a hard failure or the processor module receives BAD
QUALITY from the frequency counter slave. Refer to the OIS
Product Instruction for information explaining how to access
the module problem report. For instructions to access error
messages on other operator interfaces (i.e. PCV, CTM, CTT)
refer to the instruction manual for those devices.
To troubleshoot a hard failure:
1. Use the flowchart in Figure
to find the location of the
hard failure.
2. Refer to Table
for corrective action.
3. If there are no configuration errors or hard failures and the
FCS continues to fail to start, replace the FCS module.
4. If replacing the module does not correct the problem, call
Bailey Controls Company for assistance.
Table 5-1. Troubleshooting FCS Start-Up Failures
Problem
Cause
Action
FCS fails to start
Module not in the
execute mode
Place module in the execute mode.
Configuration errors
Check the operator interface for error messages.
Refer to the operator interface instruction and Function
Code Applications Manual for corrective action.
FCS fails to start and
there are no configura-
tion errors.
Module not in the
execute mode
Place the module in the execute mode.
