Rockwell Automation 57C570 AutoMax PC3000 User Manual User Manual
Page 212
19Ć20
Use the following procedure to isolate the cause of a
communication failure:
Step 1.
Verify that the drop number of the slave modules is
unique and the drop number is set correctly via the
Change Drop command.
Step 2.
Verify that drop depth has been specified. If you have
performed the self test function, the module will power up
with a drop depth of 0". If the Network module is used in
an AutoMax Version 1.0 system or a DCS 5000 system, it
will also power up with a drop depth of 0". Writing a valid
drop depth to register 20 or running an application task
that defines drop depth will clear this error.
Step 3.
Verify that the drop depth specifications for each slave
module are such that the slave modules do not overlap in
drop numbers. Only one slave module can be configured
to respond to any given drop number.
NOTE: Use steps 4 through 8 below if you have a coaxial
cable network. If you have a fiberĆoptic network, see
chapter 21.
Step 4.
Verify that the network connections to each module are
secure. Check the drop cable connection at the module
faceplate and at the passive tap. Verify that the coax
cable connections are secure.
Step 5.
Verify that the network cabling is terminated correctly.
There must be a line terminator at each end of the
network.
Step 6.
Verify that the cabling between Network modules is
installed in its own separate conduit held free from major
noise sources, such as power or other signal wires.
Step 7.
Inspect and test the cable system following the
instructions in sections 3.5.1 and 3.5.4.
Step 8.
Verify that the network cabling does not exceed the
maximum allowable length given the number of physical
drops and its electrical characteristics.
19.2.3
Interpreting AĆB Remote I/O Error Codes
You can view the AĆB Remote I/O error codes by using any of the
following:
D Processor Info. screen
D monitoring register 2002, the AllenĆBradley Remote I/O Error
Code, of the PC3000 Application Interface
Use the following table to help you interpret the AĆB Remote I/O
Interface error codes: