Allen-Bradley

DriveTools
TM

Communications
Set Up
Set Up Manual
Important User Because of the variety of uses for the products described in this
Information 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.

The illustrations, charts, sample programs and layout examples

shown in this guide are intended solely for purposes of example.
Since there are many variables and requirements associated with any
particular installation, Allen-Bradley does not assume responsibility
or liability (to include intellectual property liability) for actual use
based upon the examples shown in this publication.

Allen-Bradley publication SGI-1.1, Safety Guidelines for the

Application, Installation, and Maintenance of Solid-State Control
(available from your local Allen-Bradley office), describes some
important differences between solid-state equipment and
electromechanical devices that should be taken into consideration
when applying products such as those described in this publication.

Reproduction of the contents of this copyrighted publication, in

whole or in part, without written permission of Rockwell
Automation, is prohibited.

Throughout this manual we use notes to make you aware of safety

considerations:

ATTENTION: Identifies information about practices

or circumstances that can lead to personal injury or
! death, property damage or economic loss.

Attention statements help you to:

• identify a hazard
• avoid the hazard
• recognize the consequences
Important: Identifies information that is critical for successful
application and understanding of the product.

1336 IMPACT is a trademark of Rockwell Automation.

 Table of Contents

Setting Up Your Communication

Hardware Chapter 1
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
DH+ Communication Hardware Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Installing the KT/KL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
Installing the PCMK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
DriveTools Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
Using 6200 Software Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
Memory Management and Windows Startup Problems . . . . . . . . . . . . . 1–14
Adding More Upper Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–14
Card and Socket Services Other than CardWare . . . . . . . . . . . . . . . . . . 1–15
Installing the Modem (KF2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–16
Setting Up the SCANPort Communication Hardware . . . . . . . . . . . . . . 1–17

Setting Up Communications Chapter 2

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
Setting Up the Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
Setting Up the PC Modem Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5

Starting Communications Chapter 3

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Connecting to the Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Using the ScanPort Network Connect to Drive dialog box . . . . . . . . . . . 3–2
Using the DH+ Network Connect to Drive dialog box . . . . . . . . . . . . . . 3–3
Using the RIO Pass Through Network Connect to Drive dialog box . . . 3–4
Searching for Active Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7

1–1
 Table of Contents

1–2
 Chapter

1
Setting Up Your Communication Hardware

General
Your DriveTools software can communicate with a variety of Allen–Bradley
drive products using different hardware configurations to connect to the
drives. Release 2.01 of the DriveTools software implements a protocol
interface to the Allen–Bradley SCANPort protocol. This feature allows the
software to connect at some level of functionality to all existing SCANPort
based products (such as the 1305 Micro, 1336 Plus, and 1336 Force). The
actual hardware used for the connection depends on the type of drive product
and the method you are using for drive communications. With the release of
the 1203–GD2 communications module, you can directly connect to
SCANPort–based devices using your PC’s RS–232 serial port.
Although the software supports connection to some level for all SCANPort
based devices, the database information distributed with the DriveTools
software only supports the products listed in Table 1–1. For products not
listed in this table, the DriveManager and DrivePanel programs can create an
appropriate database from the drive product itself when you establish a
communications connection with the drive. The shaded region in Table 1–1
indicates communication options which have been added in release 2.01.
Unshaded portions of Table 1–1 indicate communication options which
existed in DriveTools release 1.01.
Table 1–1
Drive Type Comm Type Drive Side Hardware PC Side Hardware Protocol

1395 Point to Point 1300–SC RS–232 Port 1395 protocol

1305, 1336S, 1336T, Point to Point 1203–GD2
RS–232 Port DF1 point to point
1336G, SMC, 1557 encapsulating SCANPort
1305, 1336S, 1336T, Remote Point 1203–GD2
, Modem RS–232 Port, DF1 point to point
1336G, SMC, 1557 to Point Modem encapsulating SCANPort
1305, 1336S, 1336T, Multi–Drop 1203–GD2
, RS232/485 RS–232 Port DF1 multi–drop
1336G, SMC, 1557 Converter encapsulating SCANPort
1305, 1336S, 1336T, Remote 1203–GD2
, RS232/485 RS–232 Port DF1 multi–drop
1336G, SMC, 1557 Multi–Drop Converter, Modem Modem encapsulating SCANPort
1305, 1336S, 1336T, RIO Block PLC5, 1203–GD1 (for 1784 –KT, –KL, BT Pass Thru on DH+
1336G, SMC, 1557, Transfer Pass all SCANPort devices), –PCMK encapsulating SCANPort
1395 Thru Multi–Comm or Node or 1395 protocol
Adapter (1395)
1336T, 1395 DH+ PLC Comm (1336T), 1784 –KT, –KL, DH+ (PCCC)
Multi–Comm (1395) –PCMK encapsulating SCANPort
or 1395
1336T, 1395 Serial DH+ PLC Comm (1336T), RS–232 Port Serial Transport
Multi–Comm (1395), containing DH+ (PCCC)
1770–KF encapsulating SCANPort
or 1395
1336T, 1395 Remote DH+ PLC Comm (1336T), RS–232 Port Serial Transport
Multi–Comm (1395), Modem containing DH+ (PCCC)
1770–KF, Modem encapsulating SCANPort
or 1395

1–1
 Chapter 1
Setting Up Your Communication Hardware

1203–GD2 –– The same functionality is also available in GM2 or GK2.

The products differ only in input voltage requirements and packaging.
RS–232/485 Converter –– To connect to an RS–485 network using GD2
modules configured for RS–485 operation, you need to convert the RS–232
connection of the PC to RS–485. You can use a commercially available
RS–232/RS–485 converter for this. Some PCs provide for internal RS–485
support. Refer to your PC’s documentation to determine if you require an
external RS–232/485 converter.
Important: The only tested RS–232/RS–485 converter is the black box
LD485A–HS. Refer to Figure 1–6.
Important: Communication support for DH485 using a revised version of
the 1203–GD2 module will be provided in a subsequent release of the
DriveTools software after DH485 support has been added to the GD2
module.
The following set of figures illustrates the various communication
configurations.

Point to Point
Serial Connection PC
RS–232/RS–422
1395 Protocol
RS–232
RS–232
1395 Protocol
RS–232
1300–SC
RS–422

Serial
Port
1395
DC Drive

Figure 1–1: 1395 Point to Point Communication (existing in DriveTools

version 1.01)

1–2
 Chapter 1
Setting Up Your Communication Hardware

Point to Point
Serial Connection PC
RS–232/DF1
DF1 Point to Point
Protocol RS–232 RS–232

DF1
RS–232 GD2
GM2
SCANPort GK2

or or or or or or
RIO DH+
PLC
Adapter
SCANPort SCANPort SCANPort SCANPort SCANPort SCANPort
SMC 1305 1336S 1336G 1336T 1557
Micro Plus Fibers Force Med V.

Figure 1–2: SCANPort Device Point to Point Communication (Added in

DriveTools version 2.01)

Multi–Drop PC OR PC
Serial Connection
RS–485/DF1
DF1 RS–485 RS–232 DF1 RS–232
RS–485
DF1 Multi–Drop Protocol

RS–485 RS–485 RS–485 RS–485 RS–485 RS–485

DF1 DF1 DF1 DF1 DF1 DF1
RS–485 GD2 RS–485 GD2 RS–485 GD2 RS–485 GD2 RS–485 GD2 RS–485 GD2
GM2 GM2 GM2 GM2 GM2 GM2
SCANPort GK2 SCANPort GK2 SCANPort GK2 SCANPort GK2 SCANPort GK2 SCANPort GK2

RIO DH+
PLC
Adapter
SCANPort SCANPort SCANPort SCANPort SCANPort SCANPort
SMC 1305 1336S 1336G 1336T 1557
Micro Plus Fibers Force Med V.

Figure 1–3: SCANPort Device Multi–Drop Communication (Added in

DriveTools version 2.01)

1–3
 Chapter 1
Setting Up Your Communication Hardware

Multi–Point
Serial Connection P PC PC
L
DH+ C
1770–KF
DH+ KT, KL, PCMK RS–232 DF1 RS–232
DH+

DH+ Direct DH+ Read/Write

RIO DH+ RIO BT

Pass Thru
RIO GD1 RIO GD1 RIO GD1 RIO GD1 RIO GD1
GM1 GM1 GM1
SCANPort GK1 SCANPort GK1 SCANPort GM1
GK1 SCANPort
GM1
GK1 SCANPort GK1

RIO DH+ RIO DH+

Multi–Comm PLC
Adapter Adapter
Serial Port SCANPort SCANPort SCANPort SCANPort SCANPort SCANPort

1395 SMC 1305 1336S 1336G 1336T 1557

DC Drive Micro Plus Fibers Force Med V.

Figure 1–4: DH+ Direct and RIO Pass Thru Network (Partially
supported in DriveTools version 1.01, completed in 2.01)

Modem Support
Options Using PC
RS–232/DF1

Modem
DF1 RS–232
Phone Line Connection
OR OR
Modem Modem Modem

RS–232 RS–232 GD2 RS–232

1770–KF GM2
DH+ SCANPort GK2 RS–485
DH+ RS–485/DF1 Multi–Drop
SCANPort Device
DH+ Device DH+ Device RS–485 GD2 RS–485 GD2
SMC GM2 GM2
1395 DC 1395 DC 1305 Micro SCANPort GK2 SCANPort GK2
1336T 1336T 1336S Plus
PLC5 PLC5 1336G Fibers
1336T Force SCANPort Device SCANPort Device
1557 Medium V
SMC SMC
1305 Micro 1305 Micro
1336S Plus 1336S Plus
1336G Fibers 1336G Fibers
1336T Force 1336T Force
1557 Medium V 1557 Medium V

Figure 1–5: Optional Modem Support

1–4
 Chapter 1
Setting Up Your Communication Hardware

Jumper Setting
XW1A DCE*
W8 B–C 2–Wire
W15 B–C Data enable (maximum speed is 64K)
W5 B–C RTS/CTS/CD delay (CTS inhibited if CD is present when RTS is
raised)
W9 RTS/CTS delay (The time before the RS–485 driver is enabled and CTS is
asserted after RTS is asserted. The RS–485 driver is always enabled.)
D ON
W17 When W15 is in the B–C (data enabled) position, this is the time the
RS–485 driver remains enabled after a low–to–high transition on the DATA
line to prevent disabling the driver in the middle of a character.
E 0.15 msec.
W16 Turnaround delay (When W8 is in the B–C (2–wire) position, this is the
time after the driver is disabled and before the receiver is enabled.)
A 0 msec.
Note: The delays from W17 and W16 are cumulative.
S1 OUT*
S2 ON RS–485 Receiver terminated.
S3 OFF* Line bias off.
TB1 2–wire terminal block
TxA<––>RxA (Pink wire) –––––––> to GD2 pin 9
TxB<––>RxB (Black wire) ––––––> to GD2 pin 4

The asterisks (*) designate the factory–preset jumper settings.

The pink wire inside the cable

PC The black wire

inside the cable
RS–232 Comm. Adapters 25 pin
Female Connector
Pin 4 Pin 9
1203–GD2
The Jumper
The Jumper between
RxB RxA TxB TxA
between RxB and TxB RxA and TxA
1203–GD2

1203–GD2

Top Face of the RS–232<––>485/422

Converter (Inside)

Figure 1–6: Jumper Setting and Configuration on RS–232 to RS485/422

Converter
Important: This configuration has only been tested on the following
RS–232/485 converter: BlackBox model LD485A–HS.

1–5
 Chapter 1
Setting Up Your Communication Hardware

DH+ Communication Hardware Set Up

Before DriveTools can communicate with your drives using the
Allen–Bradley DH+ communication network, your PC requires a hardware
interface to the network. This interface may be any of the following devices,
depending on your PCs requirements:
Catalog Hardware Type
1784KT 16 bit standard 1/2 size PC bus card
1784KL Reduced size PC card for use in portable PCs
1784PCMK PCMCIA compatible card
1770–KF2 External RS–232/DH+ Converter

The remaining sections of this chapter provide information about the

following:
❒ Installing the KT/KL
❒ Installing the PCMK
❒ Installing the modem (KF2)

1–6
 Chapter 1
Setting Up Your Communication Hardware

Installing the KT/KL

To use the PC card type devices, you need to do the following:
❒ Modify your PCs config.sys and autoexec.bat files to accommodate the
hardware devices.
❒ Configure the Allen–Bradley Information Interchange software that
DriveTools uses to interact with the hardware.
The Interchange software consists of the following disk files:
File Function
cfg_kt.exe configures the KT hardware to operate with the DTL drivers
dtl_kt.exe configures the Interchange drivers
rna.exe KT resident communication drivers
rnatsr.exe PC TSR which interfaces with the Interchange software in
Windows
abicrun.bat batch file used to load the Interchange configuration and drivers
abicstop.bat batch file to unload the Interchange drivers
cfg_kt.ini configuration file used for the Interchange drivers

These files are located in the ABIC\BIN directory within the directory where
your DriveTools application(s) are located.
Setup
To set up your PC to run DriveTools, perform the following steps for the KT
or KL:
1. Verify that the card has been installed per the instructions that came with
the hardware. Record the switch and jumper settings that determine the
IRQ number and the memory address assigned to the card.
2. Open the config.sys file for your PC and verify that the memory region
assigned to your DH+ communication card has been excluded.
Important: On some PCs, you may need to use a higher memory block
for the DH+ communication card as some video card memory blocks and
other installed hardware may interfere with the DH+ communication card
memory block.
3. Open the cfg_kt.ini file and verify that the set up in this file corresponds to
the settings for the card you are using. Refer to the instructions provided
in the cfg_kt.ini file and the documentation for the hardware card being
used.
Important: If you are using Allen–Bradley 6200 software with your
DriveTools application(s) and you are running 6200 software from within
a DOS window in Windows, you need to use the 6200 version of the
Interchange drivers. Refer to your 6200 documentation for further
information on how to configure Interchange for 6200.
4. Load the DTL drivers before starting Windows. You may either load the
drivers as a part of the autoexec.bat file or separately. You can use the
abicrun.bat batch file located in the \ABIC\BIN directory within the
DriveTools (DTLS default) directory to load the Interchange drivers unless
you are loading the drivers provided with your 6200 software. abicrun.bat
first loads the drivers and then starts Windows. To load the drivers as a
part of your autoexec.bat file, you can either call abicrun.bat as the last line

1–7
 Chapter 1
Setting Up Your Communication Hardware

in your autoexec.bat file, or copy the appropriate lines from abicrun.bat into
your autoexec.bat file.
Important: DriveTools does not recognize the DH+ communication
hardware unless the commands performed in the abicrun.bat file are
executed before Windows.
Important: In the default DriveTools installation, you should add the
following to your path statement: C:\DTLA\ABIC\BIN.
5. If the directory where the Information Interchange software is located is
not in the path, add it in the autoexec.bat file path command.
6. Run your DriveTools application. To run a DriveTools application, click
on the program icon in the DriveTools application group within the
Windows Program Manager.
7. Select the Connect to Drive option of the Drive pull–down menu.
Depending on how your communications are currently set up, you will
see either the Serial Connect to Drive dialog box or the Network
Connect to Drive dialog box. You need the Network Connect to Drive
dialog box. Chapter 3 of this manual provides more information about
using the Connect to Drive option and the Network Connect to Drive
dialog box.
8. In the Network Connect to Drive dialog box, click on the WHO button.

When the DH+ WHO’s Active dialog box is displayed, you will see the
DH+ network scanner operate as indicated by the LEDs in the dialog. If
communication has been correctly established, the scanner should move
through the LEDs at a moderate rate, stopping occasionally as DH+ stations
are encountered. Upon successful completion, the list box displays a list of
all the DH+ stations read, excluding the station for the PC on which you are
running the DriveTools application.

Troubleshooting
If no stations are displayed in the DH+ WHO’s Active dialog box, the
following information can help you diagnose where the problem is:
❒ If the DH+ WHO’s Active dialog box scans through the stations quickly
without stopping, then the hardware drives were probably loaded
incorrectly or the drivers were not loaded at all. Verify that steps 1–4
under Setup were performed correctly. Also, try to load the drivers
without immediately loading Windows to verify that they loaded without
error.
❒ If the DH+ WHO’s Active dialog box scans through the stations very
slowly, stopping at each station, then it is likely that the Interchange
drivers were loaded, but one of the following may be true:
a. The interrupt is not set on the KT or PCMK card to match the cfg_kt.ini
file. This must be set to something other than None.
b. There is a duplicate station number to the one set in the cfg_kt.ini file.
c. The configuration may be incorrect.
d. No stations are attached to the network.
e. The communication cabling is faulty.

1–8
 Chapter 1
Setting Up Your Communication Hardware

Installing the PCMK

DriveTools supports the PCMK card by using the KT driver software. If you
have 6200 software installed on the computer, you can use the drivers from
the IPDS directory to program the PCMK card.
Important: To use DriveTools, you must load the multi–session drivers
before going into Windows.
The following procedure details how to setup the software for DriveTools.
❒ To use card and socket services software other than the ones that ship
with the PCMK card, see your PCMK manual for instructions.
❒ To use the software that DriveTools installs to communicate with the
PCMK, proceed to step one of the DriveTools procedure.
❒ To use 6200 software, proceed to step one of the 6200 procedure.

DriveTools Procedure
To use the software that DriveTools installs to communicate with the PCMK,
follow these steps:
1. Backup your config.sys and autoexec.bat files.
2. Install the Cardware software.
3. Copy the files that end in .bin from the PCMKIPDS directory to the
\DTLS\ABIC\BIN directory, overwriting the .bin files currently in that
directory. These files allow the PCMK card to look like a KT card to the
software. Use the copy command on the utilities disk that came with the
PCMK card.
Assuming that DriveTools is installed on the C drive and the utilities disk
is in the A drive, use the command: copy a: \pcmkipds\*.bin
c:\dtls\abic\bin\*.bin.
4. Modify your config.sys and autoexec.bat files. The two excludes on the
EMM386.EXE (X=CE00–CEFF X = CF00–CFFF) are used for Cardware and
the PCMK card. You may use any valid upper memory range as long as
you change cardware.ini and \DTLS\ABIC\BIN\cfg_kt.ini to match the values
that you choose.

DEVICE=C:\DOS\HMEM.SYS
DEVICE = C:\DOS\EMM386.EXE NOEMS X=CE00–CEFF X=CF00–CFFF
REM – – – Previous line modified by CardWare Setup
DOS=HIGH,UMB
FILES = 40
BUFFERS = 20

REM – – – Following lines added by CardWare Setup

DEVICEHIGH=C:\CARDWARE\PCSS.EXE
DEVICEHIGH=C:\CARDWARE\PCCS.EXE
DEVICEHIGH=C:\CARDWARE\PCENABLE.EXE

REM – – – You may delete the line below if you do not need support for PCMCIA Hard Drive Cards
REM DEVICE = C:\CARDWARE\PC DISK.EXE
REM – – – Previous lines added by Cardware Setup

1–9
 Chapter 1
Setting Up Your Communication Hardware

5. Add the following lines to autoexec.bat:

PROMPT $P$G
REM – – – Following line modified by CardWare Setup
PATH C:\CARDWARE;C:\DOS;C:WINDOWS;C:\IPDS
SET TEMP=C:\DOS
C:\DOS\SHARE.EXE
REM – – – Following lines activate the Multi–Session Driver***
C:\DTLS\ABIC\BIN\DTL_KT.EXE.
C:\DTLS\ABIC\BIN\CFG_KT.EXE.
C:\DTLS\ABIC\BIN\RNATSR.EXE.
C:\DTLS\ABIC\BIN\RNA.EXE
REM *** Previous lines activate the Multi–Session Driver***

6. Edit the file \DTLS\ABIC\BIN\cfg_kt.ini. Use one of the entries at the bottom
of the file by deleting the semicolons at the beginning of the line as
shown in the following example. This software emulates a KT card. This
means that the Memory= line should say CC00 even though the PCMK
card is at CF00. Use the chart that is in cfg_kt.ini as a guide for other
addresses. Also, change the Name= line to include a space (that is,
DTL_KT 1).
Important: The NAME entry must be eight characters long. Include
spaces if necessary.

[DTL_KT.1]
DEVICE=PCMK
MEMORY=CC00
IRQ=5
STATION=77
NAME=DTL_KT 1

7. Add the following line to the autoexec.bat file:

C:\DTLS\ABIC\BIN

1–10
 Chapter 1
Setting Up Your Communication Hardware

8. Edit the file \CARDWARE\cardware.ini to match the MEMORY RANGE values

in config.sys and cfg_kt.ini. Refer to the PCMK users manual for more
information.
Note: The cardware.ini file can be edited using the Windows Cardware
program that came with the PCMK card. Refer to the manual for the
PCMK card for more information.

[Resources]
MEM=0xCE000,0x1000,E {First 4K range of memory, Used for cardware software.}
MEM=0xCF000,0x1000,E {Second 4K range of memory, Used for the PCMK card}
I/O=0x210,0x68,E,10
I/O=0x27C,0x04,E,10
I/O=0x320,0x040,E,10
XIRQ=15,E
XIRQ=14,E
XIRQ=13,E
XIRQ=12,E
XIRQ=11,E

[Cards]
NumberOfRecords=1
1=ALLEN–BRADLEY CO 1784–PCMK,15,6,270,ALLEN–BRADLEY CO,1784–PCMK
[SpecificAssociations]
NumberOfRecords=1
1=6 {1 = 6 means the ’1’ entry in [Cards] above uses the ’6’ entry in [logical devices]}
[GenericAssociations]
NumberOfRecords=2
1 = 1,2,3,4
2=5
[LogicalDevices]
NumberOfRecords=6
;name,memBase,memSize,IOSize,IRQ,IO2Base,IO2Size,Type,mem2Base,mem2Size,flags
1 =COM1, , ,0x3F8, 8, 4, , , ,0, , ,2
1 =COM2, , ,0x2F8, 8, 3, , , ,0, , ,2
1 =COM3, , ,0x3E8, 8, 4, , , ,0, , ,2
1 =COM4, , ,0x3E8, 8, 3, , , ,0, , ,2
5 =ATA, , ,0x10,0xFFFF, , ,3, , ,3
6 =PCMK_CF00, 0xCF000, 0x1000, 0x0, 0x0, 0x5, 0x1, 0x0, 0x0, 0x0

Name (The _CF00 is Actual address where the Free IRQ for the card to use
just a description) card is. If you change this IRQ 5 is normally for lpt2 so
please add the extra zero: should be free in most cases.
CF000, not CF00.

Using 6200 Software Procedure

If you plan to use the 6200 software, follow these steps:
1. Backup your config.sys and autoexec.bat files.
2. Run the install program on the Utilities disk to make sure that your
software is the latest version.
1–11
 Chapter 1
Setting Up Your Communication Hardware

3. Install the Cardware software.

4. Modify your config.sys file as shown in the following example. The two
excludes on the EMM386.EXE (X=CE00–CEFF X =CF00–CFFF) are used for
Cardware and the PCMK card. You may use any valid upper memory
range as long as you change cardware.ini and \IPDS\ATTACH\cfg_kt.ini to
match the value that you choose.

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS X=CE00–CEFF X=CF00–CFFF
REM – – – Previous line modified by CardWare Setup
DOS=HIGH, UMB
FILES=40
BUFFERS=20

REM – – – Following lines added by CardWare Setup

DEVICEHIGH=C:\CARDWARE\PCSS.EXE
DEVICEHIGH=C:\CARDWARE\PCCS.EXE
DEVICEHIGH=C:\CARDWARE\PCENABLE.EXE

You may delete the following line if you do not need support for PCMCIA Hard Drive cards
REM – – – Following line is required only if a PCMCIA disk is installed
rem DEVICE=C:\CARDWARE\PCDISK.EXE
REM – – – Previous lines added by CardWare Setup

5. Add the following lines to the autoexec.bat file:

PROMPT $P$G
REM – – – Following line modified by CardWare Setup
PATH C:\CARDWARE;\DOS;C:\WINDOWS;C:\IPDS
SET TEMP=C:\DOS
C:\DOS\SHARE.EXE
REM – – – Following lines activate the Multi–Session Driver***
C:\IPDS\ATTACH\DTL_KT.EXE
C:\IPDS\ATTACH\CFG_KT.EXE
C:\IPDS\ATTACH\RNATSR.EXE
C:\IPDS\ATTACH\RNA.EXE
REM – – – Previous lines activate the Multi–Session Driver***

6. Edit the file \IPDS\ATTACH\cfg_kt.ini. Use one of the entries at the bottom
of the file by deleting the semicolons at the beginning of the line as
shown in the following example.
This software directly supports the PCMK card so the memory line
should read CF00. Use the chart that is in cfg_kt.ini as a guide for other
addresses.

1–12
 Chapter 1
Setting Up Your Communication Hardware

Note: The NAME entry must be eight characters long. Include spaces if
necessary.

[DTL_KT.1]
DEVICE=PCMK
MEMORY=CF00
IRQ=5
STATION=77
NAME=DTL_KT 1

7. Edit the cardware.ini file that is in the directory \CARDWARE to match the
MEMORY RANGE values in config.sys and cfg_kt.ini as shown in the
following example.
8. Edit the file CARDWARE\cardware.ini to match the MEMORY RANGE values
in config.sys and cfg_kt.ini. Refer to the PCMK users manual.
Note: This is part of the cardware.ini file.
Note: The cardware.ini file can be edited using the Windows Cardware
program that came with the PCMK card. Refer to the manual for the
PCMK card for more information.

[Resources]
MEM=0xCE000,0x1000,E {First 4K range of memory, Used for cardware software.}
MEM=0xCF000,0x1000,E {Second 4K range of memory, Used for the PCMK card}
I/O=0x210,0x68,E,10
I/O=0x27C,0x04,E,10
I/O=0x320,0x40,E,10
XIRQ=15,E
XIRQ=14,E
XIRQ=13,E
XIRQ=12,E
XIRQ=11,E
[Cards]
NumberOfRecords=1
1=ALLEN–BRADLEY CO 1784–PCMK,15,6,270,ALLEN–BRADLEY CO,1784–PCMK

[SpecificAssociations]
NumberOfRecords=1
1=6 {1 = 6 means the ’1’ entry in [Cards] above uses the ’6’ entry in [logical devices]}
[GenericAssociations]
NumberOfRecords=2
1 = 1,2,3,4
2=5

1–13
 Chapter 1
Setting Up Your Communication Hardware

[LogicalDevices]
NumberOfRecords=6
;name,memBase,memSize,IOBase,IOSize,IRQ,IO2Size,Type,mem2Base,mem2Size,flags
1 =COM1, , ,0x3F8, 8, 4, , , ,0, , ,2
1 =COM2, , ,0x2F8, 8, 3, , , ,0, , ,2
1 =COM3, , ,0x3E8, 8, 4, , , ,0, , ,2
1 =COM4, , ,0x3E8, 8, 3, , , ,0, , ,2
5 =ATA, , ,0x10,0xFFFF, , ,3, , ,3
6 =PCMK_CF00, 0xCF000, 0x1000, 0x0, 0x0, 0x5, 0x0, 0x0, 0x1, 0x0, 0x0, 0x0

Name (The _CF00 is Actual address where the Free IRQ for the card to use
just a description) card is. If you change this IRQ 5 is normally for lpt2 so
please add the extra zero: should be free in most cases.
CF000, not CF00.

Memory Management and Windows Startup Problems

In the config.sys file, the EMM386 statement reserves two blocks of memory
from system use. These blocks are segment addresses that are 4K each. The
first block is at CE00 and is used by the Cardware software. The second
block is at CF00 and the location of the 1784–PCMK. Cardware requires 4K
and normally each PCMCIA Card requires 4K.
The cardware.ini file must then setup the memory resources for the enable
software (PCENABLE) to determine what memory it can use for the cards
and which cards are assigned which addresses.
If you have problems starting Windows and see the following message,
“Insufficient memory or address space to initialize Windows in 386 enhanced mode,”
this is due to a mismatch between the config.sys file EMM386.EXE X=
statements and the cardware.ini file MEM= statements. To correct this
problem, match the X= statements with the MEM= statements.

Adding More Upper Memory

To add extra memory to the Upper Memory (UMB) on NEC and Toshiba
units, follow these steps:
1. In the config.sys file add to the EMM386.EXE line the include statement:
DEVICE=C:\DOS\EMM386.EXE NOEMS X=CE00–CEFF X=CF00–CFFF
I=B000–B7FF
2. Move the file C:\DOS\monoumb.386 to C:\WINDOWS\SYSTEM.
3. Edit the windows system.ini file and add in the [Enh386] section:
[Enh 386]
device=monoumb.386

1–14
 Chapter 1
Setting Up Your Communication Hardware

Card and Socket Services Other Than CardWare

The 1784–PCMK does not have a special driver. Allen–Bradley software
uses the “PCMCIA Generic Enable” supplied by CardWare, the program
PCENABLE.EXE, to communicate with the 1784–PCMK. Other PCMCIA
Card and Socket Services software may work with the 1784–PCMK. If the
vendor does not supply a generic enabler, you may be able to use the
CARDWARE generic enabler PCENABLE.EXE.
Other Card and Socket Services vendors may supply a generic enabler;
Allen–Bradley cannot support any users in these cases.
Important: The Cardware Windows Software for configuration of the card
will not work when a vendor supplied Card and Socket Services are used, and
the CardWare Generic Enabler is loaded. Any changes must be done
manually to the cardware.ini file. Use the PCMKDIAG to test the card. If all
tests pass, then the PCMK is working.

1–15
 Chapter 1
Setting Up Your Communication Hardware

Installing the Modem (KF2)

To install the KF2 modem on your drive, you need to do the following:
1. Connect the blue hose (containing the Data Highway) from the drive to
the KF2 modem at the point marked Data Highway.
2. Connect one end of the RS–232 cable to the KF2 modem at the point
marked Computer Asynchronous.
3. Connect the other end of the RS–232 cable to the telephone.
If you are using the KF2 modem, you also need a modem on the other end of
the telephone line.

1–16
 Chapter 1
Setting Up Your Communication Hardware

Setting Up the SCANPort Communication Hardware

To install the GD2/GM2 on your drive, you need to follow the instructions
provided with the GD2. In most cases, you should use the factory–set
defaults. However, if your PC supports a baud rate of 19200, you can change
the baud rate that DriveTools uses by doing the following:
❒ Set Switch 2–1 on the GD2 to ON.
❒ Change the baud rate listed in the Communication Setup dialog box to
19200.
If you decide not to use the default settings, please read the following notes
before changing the settings.
❒ If you change the address for the GD2 module, you can use the WHO
button on the DH+ Network Connect to Drive dialog box to read the
address from the GD2 module.
❒ Do not change the checksum from BCC to CRC. DriveTools requires that
you use the BCC Checksum.
❒ If you decide to use multi–drop, you need to set Switch 2–7 to ON and
change the protocol selection with Switches 1–1 and 1–2. Refer to the
GD2 user manual for changing the protocol selection.
For additional information, refer to the 1203–GD2 Communication Manual.

1–17
 Chapter 1
Setting Up Your Communication Hardware

This Page Intentionally Blank

1–18
 Chapter

2
Setting Up Communications

General
This chapter provides information about the following:
❒ Setting up communication between the PC and the drive
❒ Setting up the PC modem support

Setting Up the Communication

To set up the communication between the PC and the drive, select the
Communication Setup command from the Options pull–down menu to
access the Communication Setup dialog box. The Communication Setup
dialog box allows you to select the type of communication to use and the
information DriveTools needs to set up communications. The
Communication Setup dialog box provides different options depending on
whether you choose to use serial communication or Data Highway Plus
(DH+) communication.
Using Serial Communication
When you check the Serial check box in the Communications section, the
following Communication Setup dialog box is displayed:

2–1
 Chapter 2
Setting Up Communications

The Communication Setup dialog box provides the following options when
Serial is checked.
Communication Type: This set of check boxes allows you to choose the
type of communication hardware you are going to use. The following check
boxes are available:
❒ RS–232/RS–485 ScanPort
Select RS–232/RS–485 ScanPort to use the RS–232 serial port of the PC
to communicate point–to–point with a 1203–GD2 module connected to a
ScanPort based device. When configured in this manner, the GD2
module must be set up to support point–to–point RS–232 operation.
Refer to the 1203–GD2 instruction manual for details on how to configure
the GD2 module for RS–232 operation.
❒ 1395 RS–232
Select 1395 RS–232 to use the RS–232 serial port of the PC to
communicate point–to–point with a 1300–ITSSC (RS–232/422) signal
converter connected to a 1395 drive. The 1300–ITSSC converter
converts RS–232 to RS–422 compatible with the 1395 serial port.
Important: The Control Panel controls in DrivePanel are disabled when
communicating with a 1395 drive.
❒ RS–232/RS–485 ScanPort Multi–Drop
Select RS–232/RS–485 ScanPort Multi–Drop to use the RS–232 serial
port of the PC to communicate with an RS–232/RS–485 converter
connected to an RS–485 serial network connected to one or more
1203–GD2 modules configured for RS–485 operation. When configured
in this manner, the GD2 modules must be set up to support unique
network addresses for each drive they are connected to. Refer to the
1203–GD2 instruction manual for details on how to configure the GD2
module for RS–485 network operation.
Setup: The Setup portion of the dialog box allows you to set the PC’s serial
communication port and the baud rate to be used for communication.
❒ Enter Serial Port Com #(1–4)
Enter the PC serial port number that you are using for serial connection.
Valid port numbers are 1, 2, 3, and 4.
❒ Enter Comm Port Baud Rate
Enter the PC serial port baud rate. Valid selections will vary depending
on the specific type of serial communication selected in the
Communication Type section of this dialog box.
Important: The serial port of your PC must be set to the same settings that
you specify in this dialog. To view the serial port settings on your PC, use
the Ports function in the Windows Control Panel application.

2–2
 Chapter 2
Setting Up Communications

Using Data Highway Plus (DH+) Communication

When you check the Data Highway Plus (DH+) checkbox in the
Communications section, the following Communication Setup dialog box is
displayed:

The Communication Setup dialog box provides the following options when
Data Highway Plus (DH+) is checked:
Communication Type: This set of check boxes allows you to choose the
type of communication hardware you are going to use. The following check
boxes are available:
❒ Data Highway Plus (DH+)
Select Data Highway Plus (DH+) to have the PC communicate directly
with drives that are directly connected to the DH+ network using either an
internal PC card (1784 –KT, –KL, or –PCMK), or using an external
RS–232 to DH+ converter module (1700–KF). The specific hardware
device used is determined by the KT card number entered in the Setup
section of this dialog box. When the KT Card number is 0, the software
uses the external KF module. When the KT card number is non–zero, the
software uses an internal PC card.
Important: The Control Panel controls in DrivePanel are disabled when
communicating with a 1395 drive.
❒ DH+ to PLC RIO Pass–Thru
Select DH+ to PLC RIO Pass–Thru to have the PC communicate
indirectly with drive products using the PLC RIO Block Transfer
Pass–Thru mechanism. The hardware used is determined in the same
manner as that used for the direct DH+ connection. The only difference
between this selection and the DH+ selection is the protocol used and the
fact that communication is being passed through a PLC, rather than
directly to a drive using the DH+ network.

2–3
 Chapter 2
Setting Up Communications

Attention: Using the RIO Block Transfer Pass–Thru method of

communication with the drive from the PC may conflict with
Block Transfer messages in the PLC program. If you select
communication using RIO Block Transfer Pass–Thru, you cannot
use Block Transfer messages in the PLC drive control program to
communicate with the drive.

DriveTools displays the following warning dialog when you select this
communication method. To continue using the RIO Block Transfer Pass
Thru method, click on 
. To continue using the previously selected
method of communication, click on Cancel.

Important: DriveMonitor does not support communication using RIO Pass

Thru.
Important: The Control Panel controls in DrivePanel are disabled when
using RIO Pass Thru.
Setup: The Setup portion of the dialog allows you to select the hardware
configuration to be used for the communication type selected in the
Communications and Communication Type sections of this dialog box.
❒ Enter KT Card #
Enter the KT card number (1–4) for the internal PC communication card
that is being used for direct connection to the DH+ network, or enter zero
(0) if you are using an external KT module. If a KT card number of 1
through 4 is entered, then this is the only selection which must be entered
in the Setup portion of this dialog box. If a KT card number of 0 is
entered, then you must enter the other Setup information.
Important: The KT card number applies to all internal communication
cards (KT, KL, or PCMK). The KT card number must match the KT card
number specified in the kt_cfg.ini file used to initialize the communication
card and the Allen–Bradley Interchange software that is used to
communicate with the card.
❒ Enter KF2 Serial Port Com #
If a KT card number of 0 has been entered, this selection determines the
PC serial port to which the KF module is connected.
❒ Enter KF2 Comm Port Baud Rate
If a KT card number of 0 has been entered, then this selection determines
the baud rate of the PC serial port being used to communicate with the KF
module.
❒ KF2 Setup–>BCC, No Parity, No Embedded Responses!

2–4
 Chapter 2
Setting Up Communications

Setting Up the PC Modem Support

To set up the PC modem support for remote communication, you need to
access the Modem Setup for Connect to Drive dialog box by selecting the
Modem Support command from the Options pull–down menu.

The Modem Setup for Connect to Drive dialog box allows you to set the
following information:
❒ Modem Status
This list box indicates the dialog between the modem and the software.
❒ Dial Out button
Click on Dial Out to initialize the modem using the modem initialization
string and then dial the phone number entered in the phone number edit
control. If successful, the modem status indicates that the modem link is
connected. Once the modem link has been established, the program
maintains this link until you click on the HangUp button in this dialog
box to explicitly command the modem link to hang up.
❒ HangUp button
Click on HangUp to close (hang up) the modem connection.
❒ Modem (Serial) Port
This indicates the currently selected PC serial port that is used for modem
communication. The port is selected using the Communication Setup
dialog box.
❒ Dial Timeout
Enter the timeout for communication errors when attempting to dial out
on the modem port.
❒ Phone Number
Enter the telephone number that you want the modem to dial. You must
enter the telephone number in its entirety, including any extra leading
digits that are required to access an external line (for example, 8 or 9).
The phone number must also contain a comma between the area code,
external access number, country number, etc.

2–5
 Chapter 2
Setting Up Communications

The program uses push button telephone operation only. To support this,
the command code ATDT is sent to the modem as a prefix to the actual
telephone number being sent. Telephone lines which require a dial
number are not supported.
Examples:
You are inside a facility that requires using 9 to access an external line,
and the number you are calling is (603) 846–8169. The phone number
entered in the edit control would be:
9,603,8468169
The actual command sent to the modem in this case would be:
ATDT9,603,8468169
You are in a hotel room that requires using 8 to access an external line,
and the number you are calling is to a foreign country and is 011 44 675
45–55345. The phone number entered in the edit control would be:
8,011,44,675,4555345
The actual command sent to the modem in this case would be:
ATDT8,011,44,675,4555345
❒ Modem Initialization String
Enter the modem initialization string. This initialization string is
specified in the manual for the modem you are using. This initialization
string is required to set up the modem for the type of communication you
are going to use.
The program supports Hayes compatible modems and the associated AT
command set. The program uses the following default initialization
string:
ATE1M1Q0V1&C1&D2&T5
Where:
AT Attention
E1 Commands are echoed back to the PC. This must be set if you
want to echo commands sent to the modem in the Modem
Status box.
M1 Monitor speaker on until carrier detected.
Q0 Result codes returned from modem to PC.
V1 Results returned as text to PC. This is required to display the
status information as text in the Modem Status box.
&C1 Only assert DCD while connected to a remote modem.
&D2 Hang up and switch from on–line to command state when DTR
goes from on to off.
&T5 Disable response to request for remote digital loopback.
Highlighted commands indicate required commands.
Refer to the instruction manual for your modem to enter this string.
Important: The modem MUST be setup so that compression is turned
off.
❒ Manual Entry
This edit control allows you to manually enter each command you wish to
send to the modem. The Send button located next to the edit control
sends the entered string to the modem.

2–6
 Chapter 2
Setting Up Communications

❒ Modem Support ON
Use the Modem Support ON check box to turn on/off the modem
support. Modem support is on when checked.
❒ Communication Setup button
Click on Communication Setup to access the Communication Setup
dialog box.

2–7
 Chapter 2
Setting Up Communications

This Page Intentionally Blank

2–8
 Chapter

3
Starting Communications
General

This chapter provides information about the following:

❒ Connecting to the drive
❒ Using the ScanPort Network Connect to Drive dialog box
❒ Using the DH+ Network Connect to Drive dialog box
❒ Using the RIO Pass Through Network Connect to Drive dialog box
❒ Searching for active drives

Connecting to the Drive

Connecting to a drive may occur when the Connect to Drive command is
selected or as a part of some other operation such as downloading to a drive.
Issuing a Connect to Drive command causes the software to attempt to
establish a communication to a drive. This command may in turn call one of
several dialogs depending on the current settings in the Communication
Setup dialog box as follows:
❒ Serial 1395 Point to Point – The software immediately attempts to
connect to a 1395 drive using the PCs serial port selected in the
Communication Setup dialog box. If successful, the software
immediately performs the function of connecting to a drive.
❒ Serial ScanPort (Point to Point or Multi–Drop) – The software
displays the ScanPort Network Connect to Drive dialog box.
❒ Data Highway Plus (direct) – The software displays the DH+ Network
Connect to Drive dialog box.
❒ Data Highway Plus (Pass Thru) – The software displays the RIO Pass
Through Network Connect to Drive dialog box.
If the Connect to Drive operation is being performed from the menu
command, then once communication has been established with a drive, a
new child window is displayed. The child window contains the appropriate
type of drive data for the DriveTools application establishing an online
connection (for example, Parameter/Link Table for DriveManager, Function
Block Program for DriveBlockEditor, etc.).
All online child windows contain an online control bar at the top of the
window. The online control bar contains two LED displays that indicate the
status of the communication link and the drive operational status. In
addition, depending on the specific DriveTools application, there may be
toolbar buttons which apply specifically to online operations that are
available in that application.
Data displayed in the online window is periodically read from the drive and
updated on the screen. Data is updated only for the portion of the data base
that is currently displayed on the screen. For example, in the DriveManager
application, parameter values are scanned and links are updated periodically.
In the DriveblockEditor application, node values are scanned. Windows
which do not have the status/toolbar are offline windows, and contain static
data, typically derived from a disk file.
3–1
 Chapter 3
Starting Communications

In addition to the online control bar at the top of the child window, the title
bar for online windows contain data indicating the online connection type.
Shortcuts
Toolbar:

Using the ScanPort Network Connect to Drive dialog box

The ScanPort Network Connect to Drive dialog box allows you to attempt
to establish communication with a drive. This dialog box is only displayed if
serial ScanPort (point–to–point or multi–drop) communication is currently
selected in the Communication Setup dialog box.
ScanPort Network Connect to Drive dialog box

The ScanPort Network Connect to Drive dialog box provides the

following:
❒ Enter ScanPort Adapter Station
Enter the ScanPort adapter station number which is set on the 1203–GD2
module associated with the drive you wish to connect to. The 1203–GD2
module contains switch settings that determine the adapter station
number. The station number applies when either point–to–point or
multi–drop communication is used. The only difference between the
single and multi–drop operations is that RS–232 is used for single point
and RS–485 is used for multi–drop. When configured for multi–drop,
each GD2 module must have a unique adapter station number. Refer to
the 1203–GD2 instruction manual for information about configuring this
module.
If a drive data base child window is already displayed, the station number
is preloaded with the station number associated with the currently active
child window, if a station number has been defined. If you do not know
the station number of the adapter, click on the WHO button to scan the
communication link for station numbers.
Important: An optional field in the general information associated with
the drive is the network station number. This can be entered using the
Drive Information command in the Drive menu. If there is no network
station number is currently specified for the drive, use the network WHO
button to select a drive.
❒ Communication Setup
Click on Communication Setup to call the Communication Setup
dialog box if you need to setup the PC communication. If you change the
communication type, the appropriate connection dialog is displayed when
you exit the Communication Setup dialog box.

3–2
 Chapter 3
Starting Communications

❒ WHO
Click on WHO to call the WHO’s Active dialog box which provides a
network map of the devices and their station numbers. This is true
whether you are connected point–to–point or multi–drop, as each GD2
module has a station number independent of the serial communication
type. To connect to a drive, select the drive from the network map by
either double–clicking on the drive in the list or selecting the drive and
clicking on the OK button.
By selecting a drive in the list, you will command the program to attempt
to establish communication with the drive located at that station number
independent of any previously defined drive hardware/firmware
information. In this case, the program first attempts to establish
communication with the specified drive. If successful, the program then
reads the drive hardware/firmware configuration from the drive. The
information read from the drive is used to define the new data base,
including the network station information.

Using the DH+ Network Connect to Drive dialog box

The DH+ Network Connect to Drive dialog box allows you to attempt to
establish communication with a drive. This dialog box only appears if Data
Highway Plus communication is currently selected in the Communication
Setup dialog box.

The DH+ Network Connect to Drive dialog box provides the following:
❒ Enter DH+ Station
Enter the DH+ station number which is set on the drive communication
adapter (Multi–Comm for 1395, PLC Comm for the 1336T).
If a drive data base child window is already displayed, the station number
is preloaded with the station number associated with the currently active
child window, if a station number has been defined. If you do not know
the station number of the drive, use the WHO button to scan the Data
Highway link for station numbers.
Important: An optional field in the general information associated with
the drive is the network station number. This can be entered using the
Drive Information command in the Drive pull–down menu. If no
network station number is currently specified for the drive, use the WHO
button to select a drive.
❒ Communication Setup
Click on Communication Setup to call the Communication Setup
dialog box, which allows you to set up the PC communication. If the
communication type changes, the appropriate connection dialog is
displayed when you exit from the Communication Setup dialog box.

3–3
 Chapter 3
Starting Communications

❒ WHO
Click on WHO to call the DH+ WHO’s Active dialog box, which
provides a network map of the devices and their station numbers. To
connect to a drive, select the drive from the network map by either
double–clicking on the drive in the list or by selecting the drive and
clicking on the OK button.
By selecting a drive in the list, you command the program to attempt to
establish communication with the drive located at that station number
independent of any previously defined drive hardware/firmware
information. In this case, the program first attempts to establish
communication with the specified drive. If successful, the program then
reads the drive hardware/firmware configuration from the drive. The
information read from the drive is used to define the new data base,
including the network station information.

Using the RIO Pass Through Network Connect to Drive dialog box
The RIO Pass Through Network Connect to Drive dialog box allows you
to attempt to establish communication with a drive. The RIO Pass Through
mechanism requires that a drive be connected to a PLC 5 as an RIO device
on the PLC’s RIO network. Drives may be connected as an RIO device
using several different hardware options depending on the drive type. These
options include:

Bulletin Hardware Option

1395 DC Drive Node adapter or multi–comm adapter
1305 Micro, 1336 Plus,
SMC, or 1557 1203 GD1 communication module
1336 Force PLC comm adapter or 1203–GD1 module
To communicate with a drive over RIO, the drive must be set up to appear as
an RIO device. This setup includes specifying the Rack and Group number
where the drive is to appear on the RIO network. This information must be
entered into the RIO Pass Through Network Connect to Drive dialog box
in order to establish communication with a drive. Refer to the
documentation for the specific drive and communication module for
information on configuring the drive as an RIO device.

3–4
 Chapter 3
Starting Communications

This dialog box only appears if Data Highway Plus RIO Pass Thru
communication is currently selected in the Communication Setup dialog
box.

The RIO Pass Through Network Connect to Drive dialog box provides the
following:
❒ Enter DH+ Station
Enter the DH+ station number which is set on the drive communication
adapter (Multi–Comm for 1395 or PLC Comm for the 1336T).
If a drive data base child window is already displayed, the PLC station
number is preloaded with the station number associated with the currently
active child window, if a station number has been defined. If you do not
know the station number of the drive, click on the WHO button to scan
the Data Highway link for PLC station numbers.
Important: An optional field in the general information associated with
the drive is the network station number. This can be entered using the
Drive Information command in the Drive pull–down menu. If no
network station number is currently specified for the PLC associated with
this drive, click on the network WHO button to select the PLC station
number.
❒ Enter Drive Rack #
Enter the RIO rack number associated with this drive. This number is set
in the drive’s communication hardware module.
❒ Enter Starting Group #
Enter the RIO starting group number associated with this drive which is
set in the drive’s communication hardware module.
❒ WHO
Click on the WHO button to call the DH+ WHO’s Active dialog box,
which provides a network map of the devices and their station numbers.
To select the PLC associated with this drive, select the PLC from the
network map by either double clicking on the PLC in the list or selecting
the PLC and clicking on the OK button.
By selecting a PLC in the list, you will load its station number into the
DH+ station number edit control in the RIO Pass Through Network
Connect to Drive dialog box. The software cannot read the Rack and
Group information from the PLC RIO network; therefore, you still need
3–5
 Chapter 3
Starting Communications

to enter the Rack and Group information manually before establishing a

connection.
❒ Select a Drive Type
Specify the type of drive that you will be communicating with using the
RIO Pass Through mechanism. You must specify the drive type because
the Pass Through mechanism does not report this information
automatically to the software.
❒ Communication Setup
Click on the Communication Setup button to call the Communication
Setup dialog box, which allows you to setup the PC communication. If
the communication type changes the appropriate connection dialog is
displayed when you exit from the Communication Setup dialog box.

3–6
 Chapter 3
Starting Communications

Searching for Active Drives

The DH+ WHO’s Active dialog box displays a list of the currently active
devices on the DH+ network or ScanPort link.

You may select a device from this list and then enter a data point within that
device. To select a device, highlight the device in the list and click on it, or
click on the OK button. If a device is selected, a second dialog is displayed
which allows you to select the data point for the device which was selected.
The DH+ WHO’s Active dialog box provides the following buttons:
❒ SCAN
Click on the SCAN button to rescan the network to read station
information.
❒ KT Card
The KT Card radio buttons allow you to change the currently selected
DH+ network KT card from within the WHO’s Active dialog box. When
you change the KT Card definition, the dialog rescans the network based
on the new setting. This selection does not apply when you use ScanPort
communication.
❒ Serial
The Serial button is always used when ScanPort communication is active.
When DH+ communication is active, the Serial button allows you to scan
a DH+ network that is linked through the PC’s serial port. In this case,
the PC is connected to the DH+ network through a KF2 module that
converts from serial to DH+. The serial connection may also be made
using a modem either contained in the PC or externally connected to the
PC’s serial port. The modem provides remote connection to a KF2
module at the remote site where the DH+ network is located. Refer to the
description for the Communication Setup dialog box for further
information on setting up the serial port to use the KF2 module and the
Modem Setup dialog box description for information on using a remote
modem connection.

3–7
 Chapter 3
Starting Communications

Network Map Window

The main window displayed in the DH+ WHO’s Active dialog box shows
the information read from the network WHO command. The information
consists of the following:
❒ Sta#
Specifies the network station number for each device on the network.
❒ Device Type
Specifies the type of device that is associated with the network station
number.
❒ Station Number
This is the textual description contained in the device at the network
station number. Important: The Bulletin 1395 drive does not support a
network station name; therefore, the name shown on the network map is
the same for 1395 drives. Also, for 1336T drives, the network name is
used to preload the drive name in the Drive Information dialog box.
❒ Comm Device
Specifies the communication device type as it is identified on the
network. Note: Bulletin 1395 drives are displayed as a 1785–LT
communication device type when using DH+ network communication.

3–8
1
 Allen-Bradley has been helping its customers improve productivity and quality for 90 years. We
design, manufacture and support a broad range of control and automation products worldwide.
They include logic processors, power and motion control devices, man-machine interfaces,
sensors and a variety of software. Allen-Bradley is a subsidiary of Rockwell International, one of
the world’s leading technology companies.

With major offices worldwide.

Algeria • Argentina • Australia • Austria • Bahrain • Belgium • Brazil • Bulgaria • Canada • Chile • China, PRC • Colombia • Costa Rica • Croatia • Cyprus • Czech Republic
• Denmark • Ecuador • Egypt • El Salvador • Finland • France • Germany • Greece • Guatemala • Honduras • Hong Kong • Hungary • Iceland • India • Indonesia • Israel •
Italy • Jamaica • Japan • Jordan • Korea • Kuwait • Lebanon • Malaysia • Mexico • New Zealand • Norway • Oman • Pakistan • Peru • Philippines • Poland • Portugal •
Puerto Rico • Qatar • Romania • Russia–CIS • Saudi Arabia • Singapore • Slovakia • Slovenia • South Africa, Republic • Spain • Switzerland • Taiwan • Thailand • The
Netherlands • Turkey • United Arab Emirates • United Kingdom • United States • Uruguay • Venezuela • Yugoslavia

World Headquarters, Allen-Bradley, 1201 South Second Street, Milwaukee, WI 53204 USA, Tel: (1) 414 382-2000 Fax: (1) 414 382-4444

Publication 9303–5.12 – July, 1995 P/N 95638901

Copyright 1995, Allen-Bradley Company, Inc. Printed in U.S.A.