Rockwell Automation 9303 DRIVE TOOLS 32 VER 2.50 GETTING STARTED - Manual (Page 145)

Chapter
16
Troubleshooting
Chapter Objectives Chapter 16 provides instructions for troubleshooting communications problems.
In this chapter, you will read about the following:
• Communications messages in DriveTools32 applications.
• Troubleshooting procedures.
Communications
Messages When a DriveTools32 application is not able to establish communications with a
drive, it displays a message. The following table lists the communications
messages that may appear and the actions to take to establish communications.
Messages are in alphabetical order.
Message Action
Baud rate selected for the communications port
is not valid. Select a baud rate that is supported
by your computer and configured in RSLinx and
the DriveTools32 application. Important: Your computer must support the baud rate that you specify
when you configure RSLinx and the DriveTools32 application.
1. In RSLinx, verify that the correct baud rate is used in the
Configure Device dialog box.
2. Restart the DriveTools32 application, and then verify that the
correct baud rate is used in the Communication Setup dialog
box and, if necessary, the Connect to Drive dialog box.
Communications port is configured to use both
DF1 and 1395 serial communications. You can
use only one of these at a time. If you have
communications problems, disable the DF1
driver in RSLinx or switch to a different
communications port. • If you are using 1395 serial communications after connecting to a
SCANport-compatible product, disable the DF1 driver in RSLinx.
Delete the DF1 driver in DriveTools32 by clicking Delete in the
Communication Setup dialog box, and then restart the
application.
• If you are using a DF1 driver after connecting to a 1395 drive,
delete the 1395 serial driver by clicking Delete in the
Communication Setup dialog box, and then restart the
application.
• If you are using both 1395 serial communications and serial
communications to a SCANport-compatible product, use one port
for the DF1 driver and a different port for the 1395 serial
communications. Ensure that you specify the correct port when
configuring RSLinx and the DriveTools32 application.