Rockwell Automation 57C411 Resolver Input Module - Manual (Page 33)

5Ć3
To test local I/O, first replace the input module. Next,
replace the processor module (s). If the problem persists,
take all of the modules except one processor module and
the input module out of the backplane. If the problem is
now corrected, one of the other modules in the rack is
malfunctioning. 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 remote I/O, first verify that the remote I/O system is
communicating with the drop that contains the input
module being tested. Next, by systematically swapping
out modules, determine whether the input module is the
only module that is not working.
If more than one module is not working correctly, the
problem most likely lies in the remote I/O system. Refer to
the the DCS 5000 Remote I/O Instruction Manual (JĆ3629)
for additional information. If the problem does not lie in the
system, it probably involves the remote rack.
To test the remote rack, first replace the input module. If
the problem persists, take all of the modules out of the
remote backplane except the slave remote I/O module
and the input module. If the problem is now corrected,
one of the other modules in the rack is malfunctioning.
Reconnect the other modules one at a time until the
problem reappears. If the problem proves to be neither in
the remote I/O system nor in the remote rack, try replacing
the backplane.
5.2 Bus Error
Problem: A 31" or 16" appears on the processor module's LED.
This error message indicates that there was a bus error when the
system attempted to access the module. The possible causes of this
error are a missing module, a module in the wrong slot, or a
malfunctioning module. It is also possible that the user has attempted
to write to the wrong registers on the module. Use the following
procedure to isolate a bus error:
Step 1.
Verify that the input module is in the correct slot and that
the I/O definitions are correct.
Refer to figure 3.2. Verify that the slot number being
referenced agrees with the slot number defined in the
configuration task. Verify that the register number is in the
range of 0Ć4.
For remote I/O installations, also verify that the master slot
and remote drop number are defined correctly.
Refer to the DCS 5000 Remote I/O Instruction Manual
(JĆ3629) for more information on configuring your remote
I/O system.
Step 2. Verify that the module can be accessed.
Connect the programming terminal to the system and run
the ReSource Software. Use the I/O MONITOR function to
display the four registers on the input module. If the
programmer is able to monitor the inputs, the problem lies
in the application software (refer to step 3). If the