Using rs232 to devicenet direct communications, Using rs-232 to devicenet direct communications -8, Using rs-232 to devicenet direct communications – Rockwell Automation 9303 DRIVE TOOLS 32 VER 2.50 GETTING STARTED User Manual
Page 92

9-8
Setting Up DeviceNet Direct Communications
Using RS-232 to
DeviceNet Direct
Communications
RS-232 to DeviceNet Direct communications use an external converter
(1770-KFD).
If you are using an internal interface card, refer to “Setting Up DeviceNet Direct
Communications” on page 9-2.
Hardware
Required Hardware
The following hardware is required for a DeviceNet connection:
Setting Up the Hardware
To use DriveTools32 with this type of communications, you must:
•
Ensure that the drive and adapter are properly installed and powered.
•
Ensure that cables are securely connected and protected from damage.
•
Verify that the settings in your communications module are correct. Refer to
the appropriate manual:
Important: If you are using a 1203-GK5 or 1336-GM5, it must have firmware
2.001 or greater.
Configuring RSLinx
The following instructions describe how to configure RSLinx 2.xx for
DeviceNet communications. If you have questions about RSLinx, refer to its
online help.
•
Configure the communications driver.
•
Map the configured driver to the KTPort Value.
Drive
Required Drive Hardware
Required Computer Hardware
SCANport-Compatible
➀
DeviceNet Adapter (1203-GK5, 1203-
GU6, 1336-GM5, or 1336-GM6) and
appropriate cable(s)
1770-KFD
➀
For a list of SCANport-compatible products, refer to Appendix A, Products Supported by DriveTools32.
Communications Module
Refer To:
1203-GK5 or 1336-GM5
Bulletin 1203 DeviceNet Communications Module
User Manual
1203-GU6 or 1336-GM6
Enhanced DeviceNet Communications Module User
Manual