Main Menu
I/O Module Diagnostics and I/O Calibration
Diagnostics
Revision 9
900 Control Station User Guide
45
May 2014
Status
Possible Cause
Controller Action
What to do
MISSING/NO
COMM
Main CPU is unable
to communicate to
the module for one of
the following reasons:
1. Module is not
installed
2. The module cannot
communicate with the
controller CPU or the
expansion rack CPU
because of a
backplane problem.
3. Module is on an
expansion rack and
the expansion rack
communications is
failing
See MISMATCH.
Action is based on the RACK STATUS
indication. If RACK STATUS is not
MODULE ERROR, then follow the
prescribed action defined for the RACK
STATUS diagnostic.
For MODULE ERROR, do the following:
1. Verify configuration
2. Install module.
BAD MODULE
Module is reporting a
diagnostic condition.
See
Table 23
.
See MISMATCH.
User should inspect the module’s status
LED to determine the nature of the
problem.
Table 23 describes the user
action for the various LED diagnostics.
BAD
CHANNEL
See Table 24
1. Associated block sets its fail pin on, its
warn pin off, and its output pin to the
failsafe value.
2. Associated block sets its IO status as
denoted in Table 24.
3. Associated rack monitor block’s module
fail pin is turned on.
4. Associated rack monitor block’s RACK
OK pin is turned off.
5. SYSTEM MONITOR block’s HW OK
pin is turned off.
See
Table 24