Rockwell Automation 57C435 Processor Module, AutoMax - Manual (Page 33)

5Ć7
5.5 Incorrect Data
Problem: The data used by application tasks is either always off,
always on, or different than expected. The possible causes of this are
thefollowing: a modulein thewrong slot, a programming error, or a
malfunctioning module.
Step 1.
Verify that all inputs to the rack are wired to the correct
devices.
Confirm that all connections at the terminal strip are tight.
Connect a voltmeter to the proper points on the terminal
strip and toggle each device. Verify that the device is
generating the correct voltage or current, depending upon
themoduleyou aretesting. If thevoltageor current is
incorrect, there is a problem with the external device, its
power supply, or thewiring to theterminal strip.
Check the cable for continuity between the faceplate
connector and the terminal strip.
Step 2. Verify that the input circuit on each input module is
working correctly.
Toggle the input devices to verify that the LED associated
with each is also toggling. If it is not toggling, either the
LED or theinput moduleitself is malfunctioning.
Step 3. Verify that each module can be accessed.
Connect the personal computer to the rack and run the
ReSource AutoMax Programming Executive.
Stop all programs that may berunning.
UsetheI/O Monitor function to display theindividual I/O
points or registers on the module, whichever is
appropriate. If thepoints can bemonitored, theproblem
lies in the application software (refer to steps 4 and 5). If
thepoints cannot bemonitored, theproblem lies in the
software(go on to step 6).
Step 4. For all modules in the rack, verify that the configuration
references the correct slot and register locations. For
remote I/O installations, also verify that the master slot and
drop number are referenced correctly.
Step 5. Verify that the application programs running in the rack
arecorrect.
Check to see that the application programs that reference
thesymbolic names associated with thehardwarein the
rack have declared those names COMMON.
Step 6. Verify that the hardware is working correctly.
To test local I/O, systematically swap out the module in
question and the Processor module(s). If the problem
persists, take all of the modules except the module in
question and oneProcessor out of therack. If theproblem
is now corrected, one of the other modules in the rack is
causing the problem. Reconnect the other modules one at
a time until the problem reappears. If none of these tests
reveals the problem, replace the backplane.
To test the remote I/O system, first verify that the remote
I/O system is communicating with the drop that contains
the module being tested. Next, by systematically