Rockwell Automation 61C501 AutoMax/AutoMate 115V Input Module - Manual (Page 19)

5Ć1
5.0 DIAGNOSTICS AND
TROUBLESHOOTING
This section explains how to troubleshoot the module and field
connections.
5.1 Incorrect Data
Problem: The data is either always off, always on, or different than
expected. The possible causes of this are a module in the wrong slot,
a programming error, or a malfunctioning module. It is also possible
that the input is either not wiredor wiredto the wrong device. Use the
following procedure to isolate the problem:
Step 1.
Verify that the input module is in the correct slot and, for
DCS 5000/AutoMax systems, that the I/O definitions are
correct.
Verify that the slot number being referencedagrees with
the actual slot number of the module. In the DCS
5000/AutoMax systems, this module's register number is
always zero. Verify that the bit number refers to the proper
bit. Note that the bit number andthe wire number are not
the same.
For remote I/O installations, (DCS 5000/AutoMax systems
only) also verify that the master slot andremote drop
number are defined correctly.
Step 2. Verify that the input is wiredto the correct device.
Confirm that all connections at the terminal strip are tight.
Connect a voltmeter to the proper points on the terminal
strip andtoggle the device. The voltmeter shouldalternate
between 0 and115 volts. If this does not happen, there is
a problem with either the external device, the power
supply, or the wiring to the terminal strip.
Check the cable for continuity between the faceplate
connector andthe terminal strip.
Step 3. Verify that the module can be accessed.
Connect the programming terminal to the system andrun
the ReSource Software. Use the MONITOR I/O function in
DCS 5000/AutoMax systems, or the POINT MONITOR
function in AutoMate systems. Toggle the input device to
determine whether the bit is changing state.
If the programmer is able to readthe input, the problem is
in the application software (proceedto step 4). If the
programmer cannot readthe inputs, the problem is in the
hardware (proceed to step 5).
Step 4. Verify that the user application program is correct.
For DCS 5000/AutoMax systems verify that the application
program that references the symbolic names associated
with the module has declared those name COMMON (or
global in V4.0 and later ladder tasks) in application tasks.