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

5Ć4
programmer cannot monitor the inputs, the problem lies in
the hardware (refer to step 4).
Step 3. Verify that the user application program is correct.
Registers 0 through 2 of the input module cannot be
written to. If a BASIC task caused the bus error, the error
log will contain the statement number in the task where
the error occurred. If a control block task caused the error,
you will need to search the task for any instances where
you wrote to an input.
Step 4. Verify that the hardware is working correctly.
Verify the hardware functionality by systematically
swapping out modules. After each swap, if the problem is
not corrected, replace the original item before swapping
out the next item.
To test local I/O, replace the input module, the processor
modules (s), and finally the backplane.
For remote I/O, determine whether the input module is the
only module that is not working. If it is not, the problem
most likely lies in the remote I/O system. Refer to the DCS
5000 Remote I/O Instruction Manual (JĆ3629) for additional
information. If the problem does not lie in the remote I/O
system, it probably involves the remote rack.
To test the remote rack, systematically swap out the input
module, the slave remote I/O module, and finally the
backplane. After each swap, if the problem is not
corrected, replace the original item before going on to the
next swap. If none of these actions correct the problem,
troubleshoot the remote I/O system.
5.3 Interrupt Problems
Problem: No interrupts at all or too many (unexpected) interrupts,
signified by error codes on the screen. Note that this module must be
in the same rack as the processor module that is to receive the
interrupts. Go through the following steps first before going on to the
more specific troubleshooting steps.
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 configuration task contains the proper
interrupt control definitions. Refer to the example in
section 4.6.
Step 2. Verify that the user application program is correct.
Verify that the application program that uses the symbolic
names defined in the configuration task has defined those
names as COMMON.
Compare your interrupt task with the examples given in
sections 4.5.1 and 4.5.2. Make certain that the actions
shown in the examples are performed in the same order in
your task.