Joining devicenet cables, Devicenet power supply, Joining devicenet cables devicenet power supply – Rockwell Automation 2500 CENTERLINE Motor Control Centers Installation Manual User Manual
Page 86
86
Rockwell Automation Publication 2500-IN001C-EN-P - April 2014
Chapter 9
IntelliCENTER Options
Joining DeviceNet Cables
After the terminating resistors have been installed, DeviceNet cables in each
column of the network must be spliced together.
Follow these procedures to join the DeviceNet cables.
1.
Locate the DeviceNet splicing cable in the top horizontal wireway.
One end of the splicing cable is plugged into the right DeviceNet port in
the column to the left of the splice.
2.
Route the cable through the top horizontal wireway into the column to the
right of the splice.
3.
Plug the free end of the DeviceNet splicing cable into the left port in the
top horizontal wireway of the column to the right of the splice.
4.
Torque connector screws on the splicing cable plugs to 0.55 N•m.
5.
Verify the horizontal wireway is free of tools and debris.
6.
Replace horizontal wireway covers.
DeviceNet Power Supply
A power supply unit that meets DeviceNet requirements can be supplied with the
MCC. A cable connects the output of the power supply to a DeviceNet port in
the control and network wireway. This cable is already connected when the
power supply unit ships installed in the MCC. Redundant configurations are also
available.
Remote power supplies should meet the following requirements, per ODVA:
•
Rated 24V DC (±1%)
•
Rise time of less than 250 milliseconds to within 5% of 24V DC at full
load of 8 A
•
Current limit protection of 8 amps continuous and 10 amps for the first
250 ms
•
Sized correctly to provide each device with its required power—each
device typically requires 90…165 mA
•
Derated for temperature with the manufacturer’s guidelines
IMPORTANT
The DeviceNet cable system requires a 24V DC power source to operate. The
power supply must be DeviceNet compatible as specified in the ODVA
requirements.
Power supplies that do not satisfy both points above can result in damage to
the DeviceNet signal and components, as well as failure to comply with local
codes and inspection.