DriveTools32™ Version 2.5 Using RSLinx™ Lite Version 2.10.
Important User Information Because of the variety of uses for the products described in this publication, those responsible for the application and use of this control equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards.
Summary of Changes Summary of Changes The information below summarizes the changes to the company-wide templates since the last release. Product Changes Manual Changes The following changes have been made to DriveTools32 software: • Added ControlLogix gateway communications. • Communications interface has changed. • Fixed bugs and anomalies. Refer to the DriveTools32 Readme file. The following changes have been made to this manual: • Added information on ControlLogix gateway communications.
Notes:
Table of Contents Preface Using This Manual Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Who Should Use This Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety Precautions and Important Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii Table of Contents Chapter 4 Setting up RS-232 Point-to-Point Serial Communications for a 1395 Drive Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About RS-232 Point-to-Point Serial Communications for a 1395 Drive . . . . . . . . . . . . . Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling RSLinx . . . . . . . . . . . . . . . . . . . . .
Table of Contents iii Chapter 10 Setting Up Allen-Bradley Ethernet to RIO Block Transfer Pass Thru Communications Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1 About Ethernet Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv Table of Contents Chapter 15 Using Online Help Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding Information in Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing Context-Sensitive Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Using This Manual Objectives Read this preface to become familiar with the rest of the manual. In this preface, you will read about the following: • Who should use this manual. • The purpose of this manual. • Terms and abbreviations. • Safety precautions. • Conventions used in this manual. • Rockwell Automation support.
P-2 Using This Manual Contents of This Manual Chapter Title Contents Preface Using This Manual Purpose, background, and scope of this manual. Chapter 1 Overview Overview of DriveTools32 software, RSLinx software, types of communications that you can use, and the steps to get started using DriveTools32. Chapter 2 Installing and Starting DriveTools32 Instructions for installing DriveTools32 and RSLinx.
Using This Manual P-3 Related Documentation Refer to the following documents: For Help On: Safety Precautions and Important Information Refer to: DriveTools32 applications Online help for the individual DriveTools32 applications. All documentation for DriveTools32 is currently in the online help. Refer to Chapter 15, Using Online Help. RSLinx Online help for RSLinx. In the RSLinx Help menu, select RSLinx Help Topics to access RSLinx online help.
P-4 Using This Manual Terms and Abbreviations The following terms and abbreviations are specific to this product. For a complete listing of Allen-Bradley terminology, refer to the Allen-Bradley Industrial Automation Glossary, Publication AG-7.1. Terms Conventions Used in This Manual Definition Drive You can use DriveTools32 with many Allen-Bradley products. These products include the 1395 drive, 1336 FORCE™ drive, A-B/Stromberg drives, 160 SSC drive, and SCANport™-compatible products (e.g.
Using This Manual Rockwell Automation Support P-5 Rockwell Automation offers support services worldwide, with over 75 sales/ support offices, over 500 authorized distributors, over 250 authorized systems integrators located through the United States alone, and Rockwell Automation representatives in every major country in the world. Local Product Support Contact your local Rockwell Automation representative for: • Sales and order support. • Product technical training. • Warranty support.
P-6 Notes: Using This Manual
Chapter 1 Overview Chapter Objectives What Is DriveTools32? Chapter 1 provides an overview of the DriveTools32 software package. In this chapter, you will read about the following: • DriveTools32 software suite. • RSLinx software. • Types of communications with which DriveTools32 is used. • Hardware required for each type of communications system. The DriveTools32 software suite is a family of tools designed for Microsoft Windows 95, Windows 98, and Windows NT 4.
1-2 Overview Product: What Is RSLinx? Lets you: DriveTrending32 Program and monitor the internal drive trending functions that are supported by some drives (i.e., 1336 FORCE drives, 1395 DC drives, and 2364F Regenerative DC Bus Supply units). DriveBlockEditor32 Create and monitor function block programs that run internally in 1336 FORCE drives.
Overview 1-3 You can also communicate with a drive or controller using a network connection (Refer to Figure 1.2). Figure 1.2 Network Connection Controller Computer Network Drive Adapter A third option lets you communicate with a drive or controller using a remote connection such as a gateway (Refer to Figure 1.3). Figure 1.
1-4 Overview You can use DriveTools32 with any of the following types of communications: This Type of Communications: Required Hardware Refer To: RS-232 Point-to-Point Serial Communications for a SCANport-Compatible Product Chapter 3 RS-232 Point-to-Point Serial Communications for a 1395 Drive Chapter 4 DH+ Direct Communications Chapter 5 DH+ to RIO Block Transfer Pass Thru Communications Chapter 6 ControlNet Direct Communications Chapter 7 ControlNet to RIO Block Transfer Pass Thru Communi
Overview 1-5 Using DriveTools32 with an Allen-Bradley SCANport-Compatible Product You can use DriveTools32 with many Allen-Bradley SCANport-compatible products. For a list of Allen-Bradley SCANport products, refer to Appendix A, Products Supported by DriveTools32.
1-6 Overview Using DriveTools32 with a 1336 FORCE Drive The 1336 FORCE drives are SCANport-compatible products and offer all of the options available to SCANport-compatible products (refer to page 1-5).
Overview 1-7 Using DriveTools32 with a 1395 Drive With the 1395 drive, you have the following options: Communications Required Drive Hardware Required Computer Hardware Refer To: RS-232 Point-to-Point Serial 1300-ITSSC RS-232 port Chapter 4 RS-232 Serial to DH+ Direct Multi-Communications Adapter Board (1395-KP51) RS-232 port and 1770-KF2 Chapter 5 DH+ Direct Multi-Communications Adapter Board (1935-KP51) 1784-KT, -KTX, -KTXD, or -PCMK Chapter 5 DH+ to RIO Block Transfer Pass Thru Node Ad
1-8 Overview Using DriveTools32 with an A-B/Stromberg Drive With a 1352, 1352 C, 1352 C Plus, 3400 DC, or 3502 LGU Stromberg drive, you have the following options: Communications Required Drive Hardware Required Computer Hardware Refer To: RS-232 Serial to DH+ Direct 3500-TBX card (147096 or 157676) RS-232 port and 1770-KF2 Chapter 5 DH+ Direct 3500-TBX card (147096 or 157676) 1784 -KT, -KTX, KTXD, or -PCMK Chapter 5 RSLinx Gateway Server: Ethernet to DH+ Direct 3500-TBX card (147096 or 15767
Chapter 2 Installing and Starting DriveTools32 Chapter Objectives System Requirements Chapter 2 provides instructions for installing DriveTools32 and RSLinx. In this chapter, you will read about the following: • System Requirements. • Installing DriveTools32 and RSLinx. • Starting RSLinx and DriveTools32 applications. • Creating databases in DriveTools32. DriveTools32 runs on the Microsoft Windows 95, Windows 98, or Windows NT (4.0 or greater) operating systems.
2-2 Installing DriveTools32 Installing and Starting DriveTools32 You can install DriveTools32 on a computer running Windows 95, Windows 98, or Windows NT. Important: To install DriveTools32 on a computer running Windows NT, you must have administrator privileges on the computer. Important: If you are upgrading DriveTools32, uninstall the old version before installing the new version. ! ATTENTION: Hazard of equipment damage exists.
Installing and Starting DriveTools32 Installing RSLinx 2-3 You must have version 2.10.118 (or greater) of RSLinx or RSLinx Lite installed and properly configured before you can use DriveTools32 to communicate with a drive. It is recommended that you also install RSLinx Service Pack 1 to update RSLinx to version 2.10.167. When you finish installing DriveTools32, you are prompted to install RSLinx Lite and the necessary service packs. Important: If you already have RSLinx (version 2.10.
2-4 Installing and Starting DriveTools32 2. Follow the instructions in the Install wizard. Important: If the RSLinx Install wizard does not appear automatically, you can start it using Windows Explorer. Start Windows Explorer, click your CD-ROM drive, RSLinx, and V2.1, and then double-click Setup.exe to run the RSLinx Lite setup. Start Windows Explorer, click your CD-ROM drive, RSLinx, and V2.1_SP1, and then double-click Setup.exe to run the service pack setup.
Installing and Starting DriveTools32 DriveTools32 and Database Files 2-5 DriveTools32 uses a unique database file for each drive so that you can configure each drive individually. DriveTools32 ships with many of the database files that it will need (refer to Appendix A, Products Supported by DriveTools32). If a drive does not have a database file in DriveTools32, you will be prompted to download a database file when you try to connect to it in a DriveTools32 application.
2-6 Notes: Installing and Starting DriveTools32
Chapter 3 Setting Up RS-232 Point-to-Point Serial Communications Chapter Objectives Chapter 3 provides instructions for using DriveTools32 with RS-232 point-topoint serial communications to a SCANport-compatible product. In this chapter, you will read about the following: • Required equipment and settings. • Configuring RSLinx for RS-232 point-to-point serial communications. • Configuring a DriveTools32 application for RS-232 point-to-point serial communications. • Connecting to a drive.
3-2 Hardware Setting Up RS-232 Point-to-Point Serial Communications Required Hardware The following hardware is required for an RS-232 serial connection: Drive Required Drive Hardware Required Computer Hardware SCANport-Compatible➀ Serial Adapter(1203-SSS, 1203-GD2, 1203-GK2, or 1336-GM2) and appropriate cable(s) RS-232 port 160 SSC 160-RS1 Serial Adapter and appropriate cable RS-232 port ➀ For a list of SCANport-compatible products, refer to Appendix A, Products Supported by DriveTools32.
Setting Up RS-232 Point-to-Point Serial Communications Configuring RSLinx 3-3 The following instructions describe how to configure for RS-232 serial communications. If you have questions about RSLinx, refer to its online help. To use RSLinx for an RS-232 serial communications, you need to: • Configure the communications driver. • Map the configured driver to a KTPort Value.
3-4 Setting Up RS-232 Point-to-Point Serial Communications 5. Click OK to accept the default name. The Configure Allen-Bradley DF1 Communications Device dialog box appears. 6. In the Comm Port field, select the communications port that you computer is using. Important: Note the communications port and baud rate that you use. When you configure a DriveTools32 application, you need to enter this information in the Communication Setup dialog box. 7. In the Device field, select 1770-KF2/1785-KE.
Setting Up RS-232 Point-to-Point Serial Communications 3-5 12. Click OK to save the configuration. The new driver appears in the Configure Drivers dialog box. 13. Click Close. Mapping the Configured Driver to the KTPort Value After configuring the driver, you must map it to a legacy INTERCHANGE API xKT:0 label in RSLinx so that DriveTools32 can use it. 1. In the Communications menu, select Configure Client Applications. The Configure Client Applications dialog box appears. 2.
3-6 Setting Up RS-232 Point-to-Point Serial Communications Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you must configure the application. Important: DriveTools32 can support only one type of serial connection at a communications port at a time. If you have previously configured a serial connection to a 1395 drive, click Delete in the Communications Setup dialog box to delete that configuration.
Setting Up RS-232 Point-to-Point Serial Communications Connecting to the Drive 3-7 6. In the Enter Serial Communication Port field, type the communications port number that your computer is using. You must use the same communications port for which RSLinx is configured. 7. In the Enter The Port Baud Rate field, type the baud rate that your communications module and port are using. 8. If you are using a 1336 FORCE and its drive firmware version is 0.
3-8 Notes: Setting Up RS-232 Point-to-Point Serial Communications
Chapter 4 Setting up RS-232 Point-to-Point Serial Communications for a 1395 Drive Chapter Objectives About RS-232 Point-to-Point Serial Communications for a 1395 Drive Chapter 4 provides instructions for using DriveTools32 with RS-232 point-topoint serial communications for a 1395 drive. In this chapter, you will read about the following: • Required equipment and settings. • Disabling RSLinx if it is using the communications port of the computer.
4-2 Setting up RS-232 Point-to-Point Serial Communications for a 1395 Drive Hardware Required Hardware The following hardware is required for 1395 serial communications: Drive Required Drive Hardware Required Computer Hardware 1395 1300-ITSSC RS-232 port Setting Up the Hardware To use DriveTools32 with this type of communications, you must: Disabling RSLinx • Ensure that the drive and adapter are properly installed and powered.
Setting up RS-232 Point-to-Point Serial Communications for a 1395 Drive Setting Up Communications in a DriveTools32 Application 4-3 Before a DriveTools32 application can communicate with a drive, you must configure the application. Important: DriveTools32 can support only one type of serial connection at a communications port at a time. If you have previously configured a serial connection to a SCANport-compatible drive, click Delete in the Communications Setup dialog box to delete that configuration.
4-4 Setting up RS-232 Point-to-Point Serial Communications for a 1395 Drive 8. In the DTR Pulse Width (0 to calculate automatically) field, type 0. Important: If the transmission of your computer is too fast for the 1300-ITSSC adapter, you will have to increase the value for DTR Pulse Width. Start at 500 and increase the value by increments of 100 until communications work. 9. Connecting to the Drive Click OK.
Chapter 5 Setting Up DH+ Direct Communications Chapter Objectives About DH+ Direct Communications Chapter 5 provides instructions for using DriveTools32 with DH+ direct communications. In this chapter, you will read about the following: • Required equipment and settings. • Configuring RSLinx for DH+ direct communications. • Configuring a DriveTools32 application for DH+ direct communications. • Connecting to a drive.
5-2 Setting Up DH+ Direct Communications How you set up the hardware and configure RSLinx and DriveTools32 for DH+ direct communications depends on whether you are using an internal interface card or external converter.
Setting Up DH+ Direct Communications 5-3 Configuring RSLinx The following instructions describe how to configure RSLinx for DH+ direct communications. If you have questions about RSLinx, refer to its help. To use RSLinx for DH+ direct communications, you need to: • Configure the communications driver. • Map the configured driver to the KTPort Value. Configuring the Communications Driver A driver is the software interface to the hardware device that allows RSLinx to communicate with your drive.
5-4 Setting Up DH+ Direct Communications 5. Type a name (if desired), and then click OK. The Configure Allen-Bradley 1784-KTX/KTXD dialog box appears. Important: If you are configuring a 1784-PCMK card, a different dialog box appears (not shown). If you are using Windows NT, you must specify an interrupt in the Interrupt field. To view interrupts in Windows NT, click the Start button, and select Programs, Administrative Tools, and Windows NT Diagnostics.
Setting Up DH+ Direct Communications 5-5 Mapping the Configured Driver to the KTPort Value After configuring the driver, you must map it to a legacy INTERCHANGE API xKT:0 label in RSLinx so that DriveTools32 can use it. To map the configured driver, you need to: 1. In the Communications menu, select Configure Client Applications. The Configure Client Applications dialog box appears. 2. In an unused KT:0 field, select the new DH+ driver. Important: Note the KT:0 field that you select.
5-6 Setting Up DH+ Direct Communications Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you need to configure the application. To do so, you need to: 1. Start the DriveTools32 application. 2. In the Options menu, select Communication Setup. The Communication Setup dialog box appears. 3. Click the DH+ tab. 4. Under Connect Type, select Data Highway Plus (DH+) Direct. 5.
Setting Up DH+ Direct Communications 5-7 Connecting to the Drive After configuring RSLinx and DriveTools32, you are ready to connect to a drive. 1. In the Drive menu, select Connect to Drive. The DH+ Network Connect to Drive dialog box appears. 2. Click WHO. The WHO’s Active on DH+ Network dialog box appears. 3. Double-click the station to which you want to connect. The DriveTools32 application is now communicating with the drive. If you are prompted to create a new database, click Yes.
5-8 Setting Up DH+ Direct Communications Using RS-232 to DH+ Communications RS-232 to DH+ direct communications use an external converter (1770-KF2). Important: If you are using an internal interface card, refer to “Using DH+ Direct Communications” on page 5-2. Hardware Required Hardware The hardware required for this type of communications depends on the drive type.
Setting Up DH+ Direct Communications 5-9 Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you need to configure the application. 1. Start the DriveTools32 application. 2. In the Options menu, select Communication Setup. The Communication Setup dialog box appears. 3. Click the DH+ tab. 4. Under Connect Type, select DF1 (KF2) To Data Highway Plus (DH+). 5.
5-10 Setting Up DH+ Direct Communications 8. If you are using a 1336 FORCE and its drive firmware version is 0.10, select 1336T Two Word Header (used ONLY for 1336T version 0.10). 9. Click OK. Connecting to the Drive After configuring RSLinx and the DriveTools32 application, you are ready to connect to the drive. 1. In the Drive menu, select Connect to Drive. The DF1(KF2...) to Other Network (DH+...) dialog box appears. 2. Click WHO. The WHO’s active on DF1 to DH+ network dialog box appears. 3.
Chapter 6 Setting Up DH+ to RIO Block Transfer Pass Thru Communications Chapter Objectives About DH+ to RIO Block Transfer Pass Thru Communications Chapter 6 provides instructions for using DriveTools32 with DH+ to RIO Block Transfer (BT) Pass Thru communications. In this chapter, you will read about the following: • Required equipment and settings. • Configuring RSLinx for DH+ to RIO Block Transfer Pass Thru communications.
6-2 Setting Up DH+ to RIO Block Transfer Pass Thru Communications Figure 6.1 shows an example: Figure 6.1 DH+ to RIO Block Transfer Pass Thru Network Computer with 1770-KF2 Converter Computer with Internal Card PLC-5 OR DH+ RIO Important: In the Remote I/O communications module, Switch 1 of SW3 must be On to enable block transfer.
Setting Up DH+ to RIO Block Transfer Pass Thru Communications Using DH+ to RIO Block Transfer Pass Thru Communications 6-3 With DH+ to RIO Block Transfer communications, you must use an internal interface card (1784-KT, -KTX, -KTXD, or -PCMK) in your computer. Important: If you are using an external converter, see “Using RS-232 to DH+ to RIO Block Transfer Pass Thru Communications” on page 6-7. Hardware Required Hardware The hardware required for this type of communications depends on the drive type.
6-4 Setting Up DH+ to RIO Block Transfer Pass Thru Communications • Ensure that the controller connected to the drive is not using any Block Transfer instructions addressed to the drive in its ladder logic program. • Ensure that the controller connected to the drive is in RUN mode. If it is not in RUN mode, pass thru messages cannot be delivered to the connected drive product. Configuring RSLinx For DH+ to RIO Block Transfer Pass Thru communications, you must configure RSLinx for DH+ communications.
Setting Up DH+ to RIO Block Transfer Pass Thru Communications 5. 6-5 In the Enter INTERCHANGE Port Mapping # field, type the number of the KT:0 port used by the DH+ driver in the RSLinx Configure Client Applications dialog box. Important: To view the KT Port number used by the DH+ driver, select Configure Client Applications in the RSLinx Communications menu. 6. If you are using a 1336 FORCE and its drive firmware version is 0.10, select 1336T Two Word Header (used ONLY for 1336T version 0.10). 7.
6-6 Setting Up DH+ to RIO Block Transfer Pass Thru Communications 2. Click WHO. The Who’s Active on DH+ Network dialog box appears. 3. Double-click the controller (PLC or SLC) that has the drive connected to its RIO channel. (Note that the controller, not the drive on RIO, is displayed in the Who dialog box.) The RIO Pass Thru Network Connect to Drive dialog box reappears. 4. In the Enter Drive Rack # field, type the RIO rack number of the drive.
Setting Up DH+ to RIO Block Transfer Pass Thru Communications Using RS-232 to DH+ to RIO Block Transfer Pass Thru Communications 6-7 RS-232 to DH+ to RIO Pass Thru communications require an external converter (1770-KF2). Important: If you are using an internal interface card, refer to “Using DH+ to RIO Block Transfer Pass Thru Communications” on page 6-3. Hardware Required Hardware The hardware required for this type of communications depends on the drive type.
6-8 Setting Up DH+ to RIO Block Transfer Pass Thru Communications • Ensure that the controller connected to the drive is not using any Block Transfer instructions addressed to the drive in its ladder logic program. • Ensure that the controller connected to the drive is in RUN mode. If it is not in RUN mode, pass thru messages cannot be delivered to the connected drive product.
Setting Up DH+ to RIO Block Transfer Pass Thru Communications 5. 6-9 In the Enter INTERCHANGE Port Mapping # field, type the number of the KT:0 port used by the DF1 driver in the RSLinx Configure Client Applications dialog box. Important: To view the KT Port number used by the DF1 driver, select Configure Client Applications in the RSLinx Communications menu. 6. In the Enter Serial Communication Port field, type the number of the computer serial communications port that is being used. 7.
6-10 Setting Up DH+ to RIO Block Transfer Pass Thru Communications 2. Click WHO. The Who’s active on DF1 to DH+ network dialog box appears. 3. Double-click the controller (PLC or SLC) that has the drive connected to its RIO channel. (Note that the controller, not the RIO device, is displayed in the Who dialog box.) The RIO Pass Thru Network Connect to Drive dialog box reappears. 4. In the Enter Drive Rack # field, type the RIO rack number of the drive.
Chapter 7 Setting Up ControlNet Direct Communications Chapter Objectives About ControlNet Communications Chapter 7 provides instructions for using DriveTools32 with ControlNet communications. In this chapter, you will read about the following: • Required equipment and settings. • Configuring RSLinx for ControlNet direct communications. • Configuring a DriveTools32 application for ControlNet direct communications. • Connecting to a drive.
7-2 Setting Up ControlNet Direct Communications How you set up the hardware and configure RSLinx and DriveTools32 for ControlNet direct communications depends on whether you are using an internal interface card or external converter.
Setting Up ControlNet Direct Communications • Ensure that the adapter is correctly configured.
7-4 Setting Up ControlNet Direct Communications 3. In the Available Driver Types field, select Allen-Bradley 1784-KTC(X) devices. If you are using a 1784-PCC card, select 1784-PCC (PCMCIA for ControlNet). 4. Click Add New. The Add New RSLinx Driver dialog box appears. 5. Click OK. The Configure Allen-Bradley 1784-KTC(X) dialog box appears. 6. Verify the information is correct.
Setting Up ControlNet Direct Communications 7-5 7. Click OK to configure the driver. The new driver appears in the Configure Drivers dialog box. 8. Click Close. Mapping the Configured Driver to the KTPort Value After configuring the driver, you must map it to a legacy INTERCHANGE API xKT:0 label in RSLinx. To map the configured driver, you need to: 1. In the Communications menu, select Configure Client Applications. The Configure Client Applications dialog box appears. 2.
7-6 Setting Up ControlNet Direct Communications Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you must configure the application. To do this, you need to: 1. Start the DriveTools32 application. 2. In the Options menu, select Communication Setup. The Communication Setup dialog box appears. 3. Click the ControlNet tab. 4. Under Connect Type, select ControlNet Phase 1.5 Direct. 5.
Setting Up ControlNet Direct Communications 7-7 Connecting to the Drive After configuring RSLinx and the DriveTools32 application, you are ready to connect to a drive. 1. In the Drive menu, select Connect to Drive. The ControlNet Network Connect to Drive dialog box appears. 2. Click WHO. The Who’s active on ControlNet Network dialog box appears. 3. Double-click on the drive to which you want to connect. The DriveTools32 application is now communicating with the drive.
7-8 Setting Up ControlNet Direct Communications Using RS-232 to ControlNet Direct Communications RS-232 to ControlNet direct communications use an external converter (1770-KFC). Important: If you are using an internal interface card, refer to “Using ControlNet Direct Communications” on page 7-2. Hardware Required Hardware The hardware required for this type of communications depends on the drive type.
Setting Up ControlNet Direct Communications 7-9 Configuring RSLinx For RS-232 to ControlNet communications, you must configure RSLinx for RS-232 serial communications. Important: When configuring a driver for RS-232 to ControlNet, you should select the KFC 1.5 card in the Device field of the following RSLinx dialog box. Select KFC 1.5 Refer to the “Configuring RSLinx” section in Chapter 3, Setting Up RS-232 Point-to-Point Serial Communications, for instructions on configuring RSLinx.
7-10 Setting Up ControlNet Direct Communications Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you must configure the application. To do this, you need to: 1. Start the DriveTools32 application. 2. In the Options menu, select Communication Setup. The Communication Setup dialog box appears. 3. Click the ControlNet tab. 4. Under Connect Type, select KFC to ControlNet Phase 1.5 Direct. 5.
Setting Up ControlNet Direct Communications 7-11 Connecting to the Drive After configuring RSLinx and the DriveTools32 application, you are ready to connect to a drive. 1. In the Drive menu, select Connect to Drive. The ControlNet Network uses KFC device Connect to Drive dialog box appears. 2. Click RSWHO. The RSWHO dialog box appears. 3. Navigate to the desired drive. 4. Double-click on the drive to which you want to connect. The DriveTools32 application is now communicating with the drive.
7-12 Setting Up ControlNet Direct Communications Using a 1203-CN1 Module to Connect to a ControlNet Network A 1203-CN1 module lets you connect to a ControlNet network via its serial port. Figure 7.
Chapter 8 Setting Up ControlNet to RIO Block Transfer Pass Thru Communications Chapter Objectives About ControlNet to RIO Block Transfer Pass Thru Communications Chapter 8 provides instructions for using DriveTools32 with ControlNet to RIO Block Transfer (BT) Pass Thru communications. In this chapter, you will read about the following: • Required equipment and settings. • Configuring RSLinx for ControlNet to RIO Block Transfer Pass Thru communications.
8-2 Setting Up ControlNet to RIO Block Transfer Pass Thru Communications Figure 8.1 shows an example: Figure 8.1 ControlNet to RIO Block Transfer Pass Thru Network PLC-5C Computer with 1770-KFC Converter Computer with Internal Interface Card OR ControlNet Channel A Channel B RIO Important: In your RIO communications module, Switch 1 of SW3 must be On to enable block transfer.
Setting Up ControlNet to RIO Block Transfer Pass Thru Communications Using ControlNet to RIO Block Transfer Pass Thru Communications 8-3 ControlNet to RIO Block Transfer Pass Thru communications use an internal interface card (1784-KTC, -KTCX, or -PCC) in your computer. Important: If you are using an external interface card, refer to “Using RS-232 to ControlNet to RIO Block Transfer Pass Thru Communications” on page 8-7.
8-4 Setting Up ControlNet to RIO Block Transfer Pass Thru Communications • Ensure that the controller connected to the drive is not using any Block Transfer instructions addressed to the drive in its ladder logic program. • Ensure that the controller connected to the drive is in RUN mode. If it is not in RUN mode, pass thru messages cannot be delivered to the connected drive product.
Setting Up ControlNet to RIO Block Transfer Pass Thru Communications 5. 8-5 In the Enter INTERCHANGE Port Mapping # field, type the number of the KT:0 port used by the ControlNet driver in the RSLinx Configure Client Applications dialog box. Important: To view the KT Port number used by the ControlNet driver, select Configure Client Applications in the RSLinx Communications menu. 6. If you are using a 1336 FORCE and its drive firmware version is 0.
8-6 Setting Up ControlNet to RIO Block Transfer Pass Thru Communications The Who’s active on ControlNet network dialog box appears. 3. Double-click the controller (PLC-5C) that has the drive connected to its RIO channel. (Note that the controller, not the drive on RIO, is displayed in the Who dialog box.) The RIO Pass Thru Network Connect to Drive dialog box reappears. 4. In the Enter Drive Rack # field, type the RIO rack number of the drive.
Setting Up ControlNet to RIO Block Transfer Pass Thru Communications Using RS-232 to ControlNet to RIO Block Transfer Pass Thru Communications 8-7 RS-232 to ControlNet to RIO Block Transfer Pass Thru communications use an external converter (1770-KFC). Important: If you are using an interface card, refer to “Using ControlNet to RIO Block Transfer Pass Thru Communications” on page 8-3. Hardware Required Hardware The hardware required for this type of communications depends on the drive type.
8-8 Setting Up ControlNet to RIO Block Transfer Pass Thru Communications • Ensure that the controller connected to the drive is not using any Block Transfer instructions addressed to the drive in its ladder logic program. • Ensure that the controller connected to the drive is in RUN mode. If it is not in RUN mode, pass thru messages cannot be delivered to the connected drive product. Configuring RSLinx For RS-232 to ControlNet communications, you must configure RSLinx for RS-232 serial communications.
Setting Up ControlNet to RIO Block Transfer Pass Thru Communications 8-9 2. In the Options menu, select Communication Setup. The Communication Setup dialog box appears. 3. Click the ControlNet tab. 4. Under Connect Type, select KFC to ControlNet Phase 1.5 to PLC RIO Pass-Thru. 5. In the Enter INTERCHANGE Port Mapping field, type the number of the KT:0 port used by the ControlNet driver in the RSLinx Configure Client Applications dialog box.
8-10 Setting Up ControlNet to RIO Block Transfer Pass Thru Communications Connecting to the Drive After configuring RSLinx and the DriveTools32 application, you are ready to connect to a drive. 1. In the Drive menu, select Connect to Drive. The ControlNet Network uses KFC device dialog box appears. 2. Click RSWHO. The RSWHO dialog box appears. 3. Double-click the controller (PLC-5C) that has the drive connected to its RIO channel.
Setting Up ControlNet to RIO Block Transfer Pass Thru Communications 8-11 5. In the Enter Starting Group # field, type the RIO starting group number of the drive. The RIO starting group number is set in the communications module. Valid numbers are 0, 2, 4, and 6. 6. Select PLC Type. 7. If you are using a 1395 drive, select Use 1395 Protocol. 8. Click OK. The DriveTools32 application is now communicating with the drive. If you are prompted to create a new database, click Yes.
8-12 Notes: Setting Up ControlNet to RIO Block Transfer Pass Thru Communications
Chapter 9 Setting Up DeviceNet Direct Communications Chapter Objectives About DeviceNet Communications Chapter 9 provides instructions for using DriveTools32 with DeviceNet communications. In this chapter, you will read about the following: • Required equipment and settings. • Configuring RSLinx for DeviceNet direct communications. • Configuring a DriveTools32 application for DeviceNet direct communications. • Connecting to a drive.
9-2 Setting Up DeviceNet Direct Communications How you set up the hardware and configure RSLinx and DriveTools32 for DeviceNet communications depends on whether you are using an internal interface card or external converter.
Setting Up DeviceNet Direct Communications 9-3 Configuring RSLinx The following instructions describe how to configure RSLinx 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. Configuring the Communications Driver A driver is the software interface to the hardware device that allows RSLinx to communicate with your drive. To configure the driver, you need to: 1.
9-4 Setting Up DeviceNet Direct Communications 5. Double-click the Allen-Bradley 1784-PCIDS. The 1784-PCIDS Driver Configuration dialog box appears. 6. In the Node Address field, type a unique node address for your computer on the DeviceNet network. 7. In the Network Baud Rate field, select the baud rate that the DeviceNet network is using. 8. Click OK to configure the driver. The Add New RSLinx Driver dialog box appears.
Setting Up DeviceNet Direct Communications 9. 9-5 Type a name for the driver, and then click OK. The new driver appears in the Configure Drivers dialog box. 10. Click Close. Mapping the Configured Driver to the KTPort Value After configuring the driver, you must map it to a legacy INTERCHANGE API xKT:0 label in RSLinx. To map the configured driver, you need to: 1. In the Communications menu, select Configure Client Applications. The Configure Client Applications dialog box appears. 2.
9-6 Setting Up DeviceNet Direct Communications Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you must configure the application. To do so, you need to: 1. Start the DriveTools32 application. 2. In the Options menu, select Communication Setup. The Communication Setup dialog box appears. 3. Click the DeviceNet tab. 4. Under Connect Type, select DeviceNet using Allen-Bradley 1784-PCD (PCIDS) CARD. 5.
Setting Up DeviceNet Direct Communications 9-7 Connecting to the Drive After RSLinx and the DriveTools32 application are configured, you are ready to connect to a drive. 1. In the Drive menu, select Connect to Drive. The DeviceNet Network Connect to Drive dialog box appears. 2. Click RSWHO. The RSWHO dialog box appears. 3. Navigate to the drive to which you want to connect. You can identify the drive by its node address.
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.
Setting Up DeviceNet Direct Communications 9-9 Configuring the Communications Driver A driver is the software interface to the hardware device that allows RSLinx to communicate with your drive. To configure the driver, you need to: 1. Start RSLinx. 2. In the Communications menu, select Configure Drivers. The Configure Drivers dialog box appears. 3. In the Available Driver Types field, select DeviceNet Drivers. 4. Click Add New. The DeviceNet Driver Selection dialog box appears.
9-10 Setting Up DeviceNet Direct Communications 5. Double-click the type of adapter that you are using to connect your computer to the DeviceNet network. A Device Configuration dialog box appears. 6. Under Serial Port Setup, select the communications port and the data rate that you are using in the computer. 7. Under DeviceNet Port Setup, select a unique node address for the computer on the DeviceNet network and the DeviceNet network data rate. 8. Click OK to configure the driver.
Setting Up DeviceNet Direct Communications 9-11 Mapping the Configured Driver to the KTPort Value After configuring the driver, you must map it to a legacy INTERCHANGE API xKT:0 label in RSLinx. To map the configured driver, you need to: 1. In the Communications menu, select Configure Client Applications. The Configure Client Applications dialog box appears. 2. In an unused KT:0 field, select the DeviceNet driver. Important: Note the KT:0 field that you select.
9-12 Setting Up DeviceNet Direct Communications Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you must configure the application. To do so, you need to: 1. Start the DriveTools32 application. 2. In the Options menu, select Communication Setup. The Communication Setup dialog box appears. 3. Click the DeviceNet tab. 4. Under Connect Type, select DeviceNet using Allen-Bradley 1770-KFD. 5.
Setting Up DeviceNet Direct Communications 9-13 Connecting to the Drive After RSLinx and the DriveTools32 application are configured, you are ready to connect to a drive. 1. In the Drive menu, select Connect to Drive. The DeviceNet Network Connect to Drive dialog box appears. 2. Click RSWHO. The RSWHO dialog box appears. 3. Navigate to the drive to which you want to connect. 4. Double-click on the drive. The DriveTools32 application is now communicating with the drive.
9-14 Setting Up DeviceNet Direct Communications Using a 1203-GU6 Module to Connect to a DeviceNet Network A1203-GU6 module lets you connect to a DeviceNet network via its serial port. Figure 9.2 Connecting to a DeviceNet Network via a 1203-GU6 Module Decimal: Node 8 Octal: Node 10 Decimal: Node 52 Octal: Node 64 1203-SFC cable 1203-GU6 1203-GU6 DeviceNet Before using this type of connection, you must do the following: • Note the station number of the module on the DeviceNet network.
10 Chapter Setting Up Allen-Bradley Ethernet to RIO Block Transfer Pass Thru Communications Chapter Objectives About Ethernet Communications Chapter 10 provides information for using DriveTools32 with Allen-Bradley Ethernet to RIO block transfer (BT) pass thru communications. In this chapter, you will read about the following: • Required equipment and settings. • Configuring RSLinx for Ethernet to RIO Block Transfer Pass Thru communications.
10-2 Setting Up Allen-Bradley Ethernet to RIO Block Transfer Pass Thru Communications Figure 10.1 shows an example: Figure 10.1 Allen-Bradley Ethernet Communications PLC-5E Ethernet Ethernet RIO Important: In the Remote I/O communications module, Switch 1 of SW3 must be On to enable block transfer. 1336 FORCE Drive Hardware SCANportCompatible Product 1395 Drive Required Hardware The hardware required for this type of communications depends on the drive type.
Setting Up Allen-Bradley Ethernet to RIO Block Transfer Pass Thru Communications 10-3 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. • Ensure that an Ethernet card running TCP/IP is correctly installed. • Ensure that block transfer is enabled in your adapter.
10-4 Setting Up Allen-Bradley Ethernet to RIO Block Transfer Pass Thru Communications Configuring the Communications Driver A driver is the software interface to the hardware device that allows RSLinx to communicate with your drive. To configure the driver, you need to: 1. Start the RSLinx application. 2. In the Communications menu, select Configure Driver Types. The Configure Drivers dialog box appears. 3. In the Available Driver Types field, select Ethernet to PLC5 or 5820-El. 4. Click Add New.
Setting Up Allen-Bradley Ethernet to RIO Block Transfer Pass Thru Communications 10-5 The Configure driver for Ethernet to PLC-5 or 5820-EL dialog box appears. 6. In the Driver Station field, enter a unique station number for your computer on the Ethernet network. Valid numbers are from 0 to 63. 7. In the Current Mappings field, select an available mapping. 8. In the IP Address or hostname field, type the IP address or hostname of the controller. Important: Note the IP address.
10-6 Setting Up Allen-Bradley Ethernet to RIO Block Transfer Pass Thru Communications 10. Click OK to configure the driver. The new driver appears in the Configure Drivers dialog box. 11. Click Close. Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you must configure the application. To do so, you need to: 1. Start a DriveTools32 application. 2. In the Options menu, select Communication Setup.
Setting Up Allen-Bradley Ethernet to RIO Block Transfer Pass Thru Communications 4. 10-7 Under Connect Type, select Allen-Bradley Ethernet to PLC (SLC) with RIO pass-thru. Important: If you are running DriveMonitor32, you can access a PLC by selecting Allen-Bradley Ethernet Direct to PLC. Connecting to the Drive 5. In the Enter IP Address field, type the same IP address entered in the Configure driver for Ethernet to PLC-5 or 5820 dialog box. 6.
10-8 Setting Up Allen-Bradley Ethernet to RIO Block Transfer Pass Thru Communications 3. In the Enter Starting Group # field, type the RIO starting group number of the drive. The RIO starting group number is set in the communications module. Valid numbers are 0, 2, 4, and 6. 4. If you are using a 1395 drive, click Use 1395 Protocol. 5. In the Enter SN/B Slot Number field, type the scanner slot number. Type 0 if you are using a PLC. Type the appropriate slot number if you are using an SLC. 6.
11 Chapter Using RSLinx Gateways Chapter Objectives Chapter 11 provides instructions for using DriveTools32 with RSLinx gateways from a client computer. In this chapter, you will read about the following: • Required equipment and settings. • Configuring RSLinx for RSLinx gateway communications. • Configuring a DriveTools32 application for gateway communications. • Connecting to a drive. Important: This chapter assumes that your server is already set up.
11-2 Using RSLinx Gateways Hardware Required Hardware The hardware required for this type of communications depends on the drive type.
Using RSLinx Gateways 11-3 Setting Up the Hardware To use DriveTools32 with this type of communications, you must: Configuring RSLinx • Ensure that the drive and adapter are properly installed and powered. • Ensure that cables are securely connected and protected from damage. • Ensure that an Ethernet card running TCP/IP is correctly installed in your computer. • Ensure that you are logged on to your local area network.
11-4 Using RSLinx Gateways 4. Click Add New. The Add New RSLinx Driver dialog box appears. 5. Type a name, and then click OK. The Remote Devices via Linx Gateway dialog box appears. ControlNet Serial DH+ 6. In the Server Name list, select the server to which you want to connect. A list of Remote driver names appears. 7. In the Remote driver name list, select the driver for the network to which you want to connect.
Using RSLinx Gateways 11-5 8. Click OK to configure the driver. The new driver appears in the Configured Drivers dialog box. 9. Click Close. Mapping the Configured Driver to the KTPort Value After configuring the driver, you must map it to a legacy INTERCHANGE API xKT:0 label in RSLinx so that DriveTools32 can use it. 1. In the Communications menu, select Configure Client Applications. The Configure Client Applications dialog box appears. 2. In an unused KT:0 field, select the TC P driver.
11-6 Using RSLinx Gateways Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you must configure the application. To do so, you need to: 1. Start the DriveTools32 application. 2. In the Options menu, select Communication Setup. The Communication Setup dialog box appears. 3. Click the RSLinx Gateway tab. 4. Under Connect Type, select the appropriate communications type.
Using RSLinx Gateways 5. 11-7 In the Enter INTERCHANGE Port Mapping # field, type the number of the KT:0 port used by the gateway driver in the RSLinx Configure Client Applications dialog box. Important: To view the KT Port number used by the gateway driver, select Configure Client Applications in the RSLinx Communications menu. 6. If you are using a 1336 FORCE and its drive firmware version is 0.10, select 1336T Two Word Header (used ONLY for 1336T version 0.10).
11-8 Using RSLinx Gateways 4. Click OK. One of the following occurs: Result 5. Action Connected to a drive You are ready to use the DriveTools32 application Connect to Drive dialog box reappears You are using RIO block transfer pass thru communications. Go to Step 5. If you are using RIO block transfer pass thru communications, you must type the rack number and group number in the appropriate fields, and then click OK.
12 Chapter Using a Modem Connection Chapter Objectives About Modem Connections Chapter 12 provides instructions for using DriveTools32 with a modem connection. In this chapter, you will read about the following: • Required equipment and settings. • Configuring RSLinx for modem communications. • Configuring a DriveTools32 application for modem communications. • Connecting to a drive. A modem connection extends RS-232 serial communications over a telephone line.
12-2 Hardware Using a Modem Connection Required Hardware The following hardware is required for a modem connection: Drive Required Hardware for the SCANport product Required Hardware for the Computer SCANport-Compatible SCANport Adapter (1203-SSS, 1203RS-232 port and modem➁ GD2, 1203-GK2, 1336-GM2, 1203-CN1, or 1203-GU6), appropriate cable(s), null modem converter (1203-SNM), and modem 160 Drive 160-RS1 Serial Adapter, appropriate cable(s), null modem converter (1203SNM), and modem RS-232 port and
Using a Modem Connection Configuring RSLinx 12-3 The following instructions describe how to configure RSLinx for RS-232 pointto-point serial communications with a modem. If you have questions about RSLinx, refer to its online help. To use RSLinx with a modem communications, you need to: • Configure the communications driver. • Map the configured driver to a KTPort Value.
12-4 Using a Modem Connection 5. Click OK to accept the default name. The Configure Allen-Bradley DF1 Communications Device dialog box appears. Important: Do NOT use the AutoConfigure button to set the settings for this driver. This command does not work with a modem. 6. In the Comm Port field, select the communications port that your computer is using to access the modem. 7. In the Device field, select 1770-KF2/1785-KE. 8.
Using a Modem Connection 12-5 11. Click Configure Dialer. The Dialer Configuration dialog box appears. 12. In the New menu, select Phone Book. The New Phone Book dialog box appears. 13. Type a name for the phone book, and then click Next. The New Phone Number dialog box appears. 14. Type a name and a phone number, and then click OK.
12-6 Using a Modem Connection The phone number appears in the Dialer Configuration dialog box. 15. Click OK to save the phone number. The Configure Allen-Bradley DF1 Communications Device dialog box reappears. 16. Click OK to save the configuration. The new driver appears in the Configure Drivers dialog box. 17. Click Close.
Using a Modem Connection 12-7 Mapping the Configured Driver to the KTPort Value After configuring the driver, you must map it to a legacy INTERCHANGE API xKT:0 label in RSLinx so that DriveTools32 can use it. To map the configured driver, you need to: 1. In the Communications menu, select Configure Client Applications. The Configure Client Applications dialog box appears. 2. In an unused KT:0 field, select the DF1 device. Important: Note the KT:0 field that you select.
12-8 Using a Modem Connection Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you must configure the application. To do so, you need to: 1. Start the DriveTools32 application. 2. In the Options menu, select Communication Setup. The Communication Setup dialog box appears. 3. Click the Serial tab. 4. Under Connect Type, select RS-232/RS-485 SCANport Point-to-Point. 5.
Using a Modem Connection Connecting to the Drive 12-9 8. If you are using a 1336 FORCE and its drive firmware version is 0.10, select 1336T Two Word Header (used ONLY for 1336T version 0.10). 9. Click OK to save the configuration. After configuring RSLinx and the DriveTools32 application, you are ready to connect to a drive. 1. In the Drive menu, select Connect to Drive. The SCANport Network Connect to Drive dialog box appears. 2. Click WHO.
12-10 Notes: Using a Modem Connection
13 Chapter Using ControlLogix Gateways Chapter Objectives Chapter 13 provides instructions for using DriveTools32 with ControlLogix gateways. In this chapter, you will read about the following: • Required equipment and settings. • Configuring RSLinx for ControlLogix gateway communications. • Configuring a DriveTools32 application for ControlLogix gateway communications. • Connecting to a drive. The control functions on DrivePanel32 are disabled when you use this type of communications system.
13-2 Using ControlLogix Gateways Figure 13.1 shows an example: Figure 13.1 ControlLogix Gateway Connection Ethernet Backplane 1 ControlLogix ControlLogix ControlNet Backplane 2 DeviceNet 1203-GK5 1203-GK5 1336 FORCE Drive Hardware 1395 Drive SCANportCompatible Product Required Hardware The hardware required for this type of communications depends on the drive type.
Using ControlLogix Gateways 13-3 Setting Up the Hardware To use DriveTools32 with this type of communications, you must: Configuring RSLinx • Ensure that the ControlLogix controller has scanners for the network that you are using and network to which you want to connect. • 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 communication module are correct.
13-4 Using ControlLogix Gateways These instructions show how to set up a driver for an Ethernet connection. 1. Start RSLinx. 2. In the Communications menu, select Configure Drivers. The Configure Drivers dialog box appears. 3. In the Available Driver Types field, select Remote Device via Linx or 1756-ENET Gateway. 4. Click Add New. The Add New RSLinx Drive dialog box appears. 5. Type a name (if desired), and then click OK. The Remote Devices via Linx or 1756-ENET Gateway dialog box appears.
Using ControlLogix Gateways 13-5 6. In the Server’s IP Address or hostname field, type the IP address for the Ethernet module in the ControlLogix controller. 7. Click OK. The Configure Drivers dialog box reappears, and the new driver is running. 8. Click Close to close the dialog box. Creating a Shortcut After you create a communication driver to connect to the ControlLogix controller, you must create a shortcut to the network on which the drive is located. 1.
13-6 Using ControlLogix Gateways 3. Navigate to the network to which you want to connect. Important: Count the number of backplanes that you use. A backplane allows you to move from one network to another. If you use more than one backplane, you will need to enter the total number when you configure DriveTools32. 4. Right-click on the network, and select Create Shortcut. The Add New RSLinx Driver dialog box appears. 5. If desired, type a name in the field. 6. Click OK.
Using ControlLogix Gateways 13-7 Mapping the Configured Driver to the KTPort Value After configuring the driver, you must map it to a legacy INTERCHANGE API xKT:0 label in RSLinx so that DriveTools32 can use it. To map the configured driver, you need to: 1. In the Communications menu, select Configure Client Applications. The Configure Client Applications dialog box appears. 2. In an unused KT:0 field, select the shortcut that you created. Important: Note the KT:0 field that you select.
13-8 Using ControlLogix Gateways Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you must configure the application. To do so, you need to: 1. Start the DriveTools32 application. 2. In the Options menu, select Communication Setup. The Communication Setup dialog box appears. 3. Click the ControlLogix Gateway Using Shortcut tab. 4.
Using ControlLogix Gateways Connecting to the Drive 13-9 6. If you are connecting via more than one backplane, type the number in the Enter the total number of the ControlLogix in Shortcut field. This field appears only if you have selected Multiple ControlLogix Gateway. 7. If you are using a 1336 FORCE and its drive firmware version is 0.10, select 1336T Two Word Header (used ONLY for 1336T version 0.10). 8. Click OK to save the configuration.
13-10 Notes: Using ControlLogix Gateways
14 Chapter Using ControlLogix Gateway to RIO Block Transfer Pass Thru Communications Chapter Objectives About ControlLogix Gateways To RIO Block Transfer Pass Thru Communications Chapter 14 provides instructions for using DriveTools32 with ControlLogix gateway to RIO block transfer pass thru communications on a PLC or SLC controller. In this chapter, you will read about the following: • Required equipment and settings.
14-2 Using ControlLogix Gateway to RIO Block Transfer Pass Thru Communications You can connect between the same types of networks or between different types of networks. For example, you can connect from one ControlNet network to another ControlNet network, or you can connect from an Ethernet network to a ControlNet network. The type of network that you are using limits the possible connections.
Using ControlLogix Gateway to RIO Block Transfer Pass Thru Communications Hardware 14-3 Required Hardware The hardware required for this type of communications depends on the drive type.
14-4 Using ControlLogix Gateway to RIO Block Transfer Pass Thru Communications Configuring RSLinx For ControlLogix to RIO Block Transfer Pass Thru communications, you must configure RSLinx for ControlLogix communications. Refer to the “Configuring RSLinx” section in Chapter 13, Using ControlLogix Gateways, for instructions on configuring RSLinx. Setting Up Communications in a DriveTools32 Application Before a DriveTools32 application can communicate with a drive, you must configure the application.
Using ControlLogix Gateway to RIO Block Transfer Pass Thru Communications 5. 14-5 In the Enter INTERCHANGE Port Mapping # field, type the number of the KT:0 port used by the driver in the RSLinx Configure Client Applications dialog box. Important: To view the KT Port number used by the shortcut, select Configure Client Applications in the RSLinx Communications menu. Connecting to the Drive 6.
14-6 Using ControlLogix Gateway to RIO Block Transfer Pass Thru Communications 2. Click RSWHO. The RSWHO dialog box appears. 3. Double-click the controller (PLC or SLC) that has the drive connected to its RIO channel. (Note that the controller, not the drive on RIO, is displayed in the RSWHO dialog box.) The ControlLogix Gateway Connect to Drive dialog box reappears. 4. In the Enter Drive Rack # field, type the RIO rack number of the drive.
15 Chapter Using Online Help Chapter Objectives Accessing Online Help Chapter 15 provides instructions on how to use the DriveTools32 online help. The online help provides information and step-by-step instructions about DriveTools32 applications. In this chapter, you will read about the following: • Accessing online help. • Finding information in online help. • Accessing context-sensitive help. Online help provides information and instructions that will help you use a DriveTools32 application.
15-2 Finding Information in Online Help Using Online Help Each help file provides the following three ways to locate the information that you need: • Table of contents. • Index. • Search. Table of Contents If you are new to an application, you can access information through the contents tab. 1.Click the Contents tab. 2.Double-click a book to open it. 3.Double-click a topic. 4.View the topic.
Using Online Help Index If you are looking for specific information, use the index. 1.Click the Index tab. 2.Type the topic for which you are looking. 3.Double-click the topic. 4.View the topic. Search If you are looking for a specific word, use the search. 1.Click the Find tab. 2.Type what you are looking for. 3.Double-click the topic you want to view. 4.View the topic.
15-4 Using Online Help Accessing Context-Sensitive Help DriveTools32 applications provide context-sensitive help on menu options and dialog boxes. When you need information on one of these features, access the context-sensitive help by following these directions: • Highlight a menu option or click a dialog box. Then press the F1 key. • In the Help menu, select What’s This?. Then click on a menu option.
16 Chapter Troubleshooting Chapter Objectives Communications Messages Chapter 16 provides instructions for troubleshooting communications problems. In this chapter, you will read about the following: • Communications messages in DriveTools32 applications. • Troubleshooting procedures. When a DriveTools32 application is not able to establish communications with a drive, it displays a message.
16-2 Troubleshooting Message Communications port is not supported. Verify that you entered the correct communications port number while configuring RSLinx and the DriveTools32 application. Action Important: Your computer must support the port that you specify when you configure RSLinx and the DriveTools32 application. 1. In RSLinx, verify that the correct port number is used in the Configure Allen-Bradley DF1 Communications Device dialog box. 2.
Troubleshooting Message 16-3 Action Invalid operation 3. Verify that you are connected 1. Verify that the drive is powered and cables are securely connected to the device and the RSLinx and the to it. DriveTools32 application are properly Verify that RSLinx is configured correctly. 2. configured. 3. Restart the DriveTools32 application and verify that you configured it correctly. IP Address is no longer valid. Verify that RSLinx 1. Verify that the needed Ethernet driver is still running in RSLinx.
16-4 Troubleshooting Message Action Network address on this network is not valid. Enter an address for a node that is on the network. 1. In the DriveTools32 application Drive menu, select Connect to Drive. 2. Click the WHO button or the RSWHO button. 3. Double-click the drive to which you intend to connect. Only DH+ communications are currently available. To use a different type of communications, configure and map a driver in RSLinx. Refer to the DriveTools32 Getting Started Manual. 1.
Troubleshooting 16-5 Verifying the Hardware Setup To verify the hardware setup, you need to: • Verify that you are using the required hardware for the drive and communications system that you are using. Refer to the appropriate chapter in this manual. • Verify that the communications module is correctly configured. If necessary, refer to the manual for the communications module. • Verify that the communications module is set as instructed for the type of communications that you are using.
16-6 Troubleshooting 4. Double-click the driver that you want to view. Connected devices appear in the right pane. 5. Close the RSWho window. Verifying the DriveTools32 Application Configuration To verify that the DriveTools32 application is correctly configured, refer to the procedures in the chapter for your communications system. Important: After changing a configuration in RSLinx, you must restart the DriveTools32 application.
Appendix A Products Supported by DriveTools32 Appendix Objectives Appendix A lists the bulletin numbers of SCANport-compatible products, their product names, and the directories in which DriveTools32 saves their databases.
Products Supported by DriveTools32 Other Supported Drives The following table lists drives commonly used with DriveTools32. These drives are not accessed via SCANport.
DriveTrending32 DriveBlockEditor32 Y Y ➀ Y Y ➀ ➀ Y Y Y Y Y Y Y Y Y Y Y Y Y ➀ Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y DriveManager32 DrivePanel32 A-3 DriveMonitor32 Products Supported by DriveTools32 1336 FORCE with RS-232 to DH+ (direct) PLC Communications DH+ to RIO Pass Thru DH+ (direct) Board➂ RS-232 to ControlNet to RIO Pass Thru ControlNet to RIO Pass Thru Ethernet to RIO Pass Thru RSLinx Gateway Server: - Ethernet to DH+ (direct) - Ethernet to DH+ to RIO Pass Thru ControlLogix Gateways
A-4 Products Supported by DriveTools32 Adapter Version Requirements DriveTools32 requires the following firmware releases for the following adapters: Adapter Firmware Release 1203-CN1 1.002 or greater 1203-GK5, 1336-GM5 2.001 or greater 1203-GU6, 1336-GM6 All versions 1203-GD1, 1203-GK1, 1336-GM1 2.07 or greater 1203-GD2, 1203-GK2, 1336-GM2 All versions support DriveManager32, DrivePanel32, and DriveTrending32. DriveMonitor32 requires version 2.04. DriveBlockEditor32 requires version 2.07.
Index Numerics 1305 AC Micro Drive, refer to SCANportcompatible products 1336 FORCE drives available communications systems, 1-6 hardware required, 1-6 1336 IMPACT Drive, refer to SCANportcompatible products 1336 Line Regeneration Package, refer to SCANport-compatible products 1336 PLUS AC Drive, refer to SCANportcompatible products 1336 PLUS II Drive, refer to SCANport-compatible products 1336 SPIDER Drive, refer to SCANportcompatible products 1395 drives available communications systems, 1-7 hardware requ
I-2 Index H hardware 1336 FORCE drives, 1-6 1395 drives, 1-7 SCANport-compatible products, 1-5 troubleshooting, 16-5 help, 15-1 to 15-4 I installing DriveTools32, 2-2 installing RSLinx, 2-3 K keyword, 2-4 L login, 2-4 M manual audience, P-1 contents, P-2 conventions, P-4 purpose, P-1 messages, 16-1 modem connection, 12-1 to 12-9 O online help, 15-1 to 15-4 P passwords, 2-4 R related documentation, P-3 RS-232 point-to-point serial communications system for a 1395 drive, 4-1 to 4-4 RS-232 point-to-po
Notes
Notes
Notes
Notes
Notes
Notes
ControlNet is a trademark of ControlNet International, Ltd. DeviceNet is a trademark of the Open DeviceNet Vendor Association. Pentium is a registered trademark of Intel. Windows, Windows NT, and Microsoft are registered trademarks of Microsoft Corporation. Data Highway Plus, DH+, DriveBlockEditor32, DriveManager32, DriveMonitor32, DrivePanel32, DriveTools32, DriveTrending32, 1336 FORCE, 1336 IMPACT, and SCANport are trademarks of Rockwell Automation.
Publication 9303-5.23 - April 2000 Supersedes January 1999 191870(02) Copyright 2000 Rockwell International Corporation. All rights reserved. Printed in USA.
