Control Techniques UD77 DeviceNet Startup Manual

Start Up Guide

for

UD77 DeviceNet

Systems

Version 1.00 August 2000

Control Techniques, 2000

P/N UD77-SUG

Page 1 of 77

SLC 500

Unidrive UD77 DeviceNet

Start-Up Guide

Overview

This Start-Up Guide is intended to aid installation of one or more Unidrives, each fitted with the
UD77 DeviceNet option and an Allen Bradley Modular SLC 500 PLC.

This guide presents an example start up of a SLC 5/04 PLC used with a 1747-SDN DeviceNet
Scanner and two or more Unidrives, each Unidrive fitted with the UD77 DeviceNet option.
However, the same principles should apply when using the SLC 5/02, or SLC 5/03, or SLC 5/05
(other types of SLC) in conjunction with a 1747-SDN DeviceNet Scanner. This guide could also
provide some limited guidance for installing the MD25 DeviceNet interface for the Mentor 2 with
a SLC 500 PLC.

WARNING

This guide does not address power wiring and associated safety practices.
Start-up of this nature can be hazardous and should only be performed
by qualified technicians familiar with motors and drives of this sort. This
guide is meant to supplement the Unidrive Installation Manual and the
User’s Guide which must be consulted (specifically section 2-1 in the User
Guide) prior to this guide being used. Power wiring, keypad operation and
related instructions are to be found in these manuals.

A experienced start-up engineer will be able to apply previous experience when a line is being
commissioned that uses a DeviceNet fieldbus to link the PLC to the Unidrives. Prior to the
application of power, the engineer will need to determine if that section of the system is both
safe and ready for power to resume. The engineer will also need to check, correct and validate
the entire “process pyramid” in manageable pieces and will need to proceed in a thorough and
systematic manner until everything is functioning as designed and as required.

The experienced startup engineer will learn the techniques used to establish and validate useful
communication and control links from the PLC(s) to the Unidrives via DeviceNet. The engineer
will also learn how product configuration information from Control Techniques, with software­based configuration tools from other vendors, is integrated to establish the required
communication and control links on a system that uses a DeviceNet fieldbus.

Every complex control scheme can be broken down and evaluated as a series of combinations
of a simple control scheme. The simple control scheme presented in this guide consists of a
single executive controller and two controlled Motor / Drive / Machine-process Sections, with
some form of communication and control link between the controller and the controlled. On a
Control Techniques supplied DeviceNet system, the executive controller is usually a separate
PLC or Process computer with some form of Human Interface, and the controlled Drive is a

Page 2 of 77

Unidrive (or Mentor 2 or Quantum 3) fitted with a DeviceNet Interface. The link is a DeviceNet
fieldbus.

In the context of modern “smart” and “programmable” Motor Drives, such as the Unidrive, the
default configuration provided serves as the standard product design. The use of the default
DeviceNet configuration files is illustrated in this guide, as is the configuration and establishment
of the default cyclic links between the 1747-SDN Scanner and the Unidrives.

DeviceNet Manager (and RSLogix500 as well) is organized around the concept of a “project”.
In this sense, a “project” functions as a “container” for the various files and data structures
created (or needed) by the program during the specification and configuration of one or more
related DeviceNet networks.

This start up guide is organized as a series of blocks that take the reader through the required
concepts and tasks for installation of the hardware and software and for creation of a DeviceNet
project. References to other materials for guidance about tasks not covered here are provided
at the end of the document.

Page 3 of 77

Table of Contents

OVERVIEW................................................................................................................................................................ 2

TABLE OF CONTENTS............................................................................................................................................ 4

REQUIRED MATERIALS........................................................................................................................................ 5

EVICENET NETWORK SOFTWARE CONFIGURATION TOOLS REQUIREMENTS ........................................................... 5

D
SLC 500 PLC P
PC H

ARDWARE REQUIREMENTS................................................................................................................................5

F

UNCTIONAL DEVICENET NETWORK HARDWARE REQUIREMENTS ........................................................................... 6

HARDWARE INSTALLATION............................................................................................................................... 9

S

TEP 1. ASSEMBLE MODULES AND SLC RACK INTO A COMPLETE PLC .................................................................... 9

TEP 2. ASSEMBLE THE DEVICENET NETWORK...................................................................................................... 10

S
S

TEP 3. USING A “EMPTY.RSS” PROJECT .............................................................................................................. 15

DEVICENET MANAGER INSTALLATION ....................................................................................................... 16

S

TEP 1. DEVICENET MANAGER INSTALLATION TO HARD DRIVE............................................................................. 16

S

TEP 2. INSTALLATION OF CONTROL TECHNIQUES “EDS” FILES TO DEVICENET MANAGER .................................. 18

S

TEP 3. CREATION OF THE “FIRST” DEVICENET PROJECT WITH DEVICENET MANAGER ....................................... 22

TEP 4. CONFIGURING INITIAL “INTERFACE-TO-SCANNER” COMMUNICATION ....................................................... 24

S
S

TEP 5. UNIDRIVE UD77 NETWORK CONFIGURATION ............................................................................................. 28

S

TEP 6. DEFINING AND MAPPING CYCLIC LINKS ..................................................................................................... 30

RSLOGIX500 AND RSLINX LITE USE ............................................................................................................... 50

ROGRAMMING TOOLS REQUIREMENTS............................................................................................. 5

S

TEP 1. CONFIGURING INITIAL COMMUNICATION TO THE SLC 500......................................................................... 50

TEP 2. USING AN “EMPTY.RSS” PROJECT TO INITIALIZE A SLC 5/0X PROCESSOR.............................................. 59

S
S

TEP 3. USING A “FIRST.RSS” PROJECT TO CONFIRM DEVICENET NETWORK....................................................... 59

S

TEP 4. SLC FAULT-AT-RUN TROUBLESHOOTING................................................................................................... 69

S

TEP 5. CLOS ING RSLOGIX500 AND RSLINX LITE .................................................................................................. 74

APPENDIX................................................................................................................................................................ 77

U

SEFUL PUBLICATIONS AND APPLICATION NOTES .................................................................................................. 77

Page 4 of 77

Required Materials

DeviceNet Network Software Configuration Tools Requirements

DeviceNet Manager for Windows (P/N 1787-MGR available from Allen Bradley)

• Version 3.01 is the minimum usable

• Ver 3.04 is current product

• Ver 3.02 is used in this guide

• RSNetWorx for DeviceNet (is also usable, but not described in this guide)

Generic Electronic Data Sheets, bitmap and icon files for the Unidrive

• *.EDS, *.BMP and *.ICO files for Unidrive and Mentor 2 are available for free from the
Control Techniques SSPD support site and any Control Techniques Drive Center. These are
usually distributed as a single compressed file, “DEVNET.ZIP”.

SLC 500 PLC Programming Tools Requirements

SLC 500 PLC Program Development Software

• RSLogix500 (P/N 9324-RL0300ENx is English/Standard edition available from Allen
Bradley)

• Version 3.01.09 is illustrated, Ver 3.0x.0x is current product

RSLinx Lite (is included on RSLogix installation CDROM)

• Version 2.0.18 minimum for use with DeviceNet

PC Hardware Requirements

Recommended PC minimums reflect the guide’s use of a single serial port for both configuring
the fieldbus and programming the SLC 500.

PC - Pentium Class PC @100 MHz or better with:

• 32 MB available RAM with Win95 or Win98 for OS

• 64 MB available RAM with NT4.0 for OS

• 120 MB Total Hard Disk Space free (20 MB for Applications, and 100 MB for OS swap file

use)

• CDROM quad-speed or better (for loading of RSLogix500 and RSLinx Lite)

• 3 ½ “ 1.44 MB floppy drive (needed for RSLogix500 and loading DeviceNet Manager)

• 1 available serial port, 16550 compatible UART

• Mouse and suitable port (PS-2 style requires PS-2 port, serial mouse requires a second

serial port)

Note that NT4.0 requires “Local Administrator” or “Power User” privileges to install software
on the machine. Use the latest applicable OS Service Release(s) available.

Also note that, while this guide has not been tested with Windows 2000, the requirements
should be similar to the NT 4.0 requirements, and it is assumed that the tasks described in
this guide can also be accomplished under Windows 2000 Professional.

Page 5 of 77

Functional DeviceNet Network Hardware Requirements

Note: This guide describes a small DeviceNet network, or something larger that has been
reduced to two Unidrives and two UD77s.

Modular SLC 500 PLC, SLC 5/02 processor or better.

• SLC 5/04 is recommended, unless additional Ethernet connectivity required.

• SLC 5/05 is recommended if additional Ethernet connectivity is needed.

SLC 500 modular chassis

Needed to house the power supply, processor, scanner and I/O module(s). A 1746-A4 4­slot-rack is described in this guide.

SLC 500 power supply

A 1746-P1 rated at 2.0A/0.46A (at 5 V/24V) is described in this guide.

At least one Discrete Input Module.

• A “1746-IO12DC” combination input/output module is recommended for a small DeviceNet
network and is described, but not used, in this guide.

1747-SDN DeviceNet scanner module

PC-to-DeviceNet interface

This is required for configuring the scanner, and useful for commissioning the Unidrives.

• M/N 1770-KFD RS-232 interface is described in this guide. This interface can take its power
directly from the DeviceNet 24.0 VDC supply, so an optional 9.0 VDC supply is not required
unless isolating point-to-point taps are used with the interface.
Note that the interface cable that comes with this scanner can also be used as a 1747-CP3
cable into channel 0 of the processor to permit communication between the processor and
the PC.

• M/N 1784-PCD PCMCIA interface is usable, but not described further.

• M/N 1784-PCID PCI interface is also usable, but not described further.

Unidrive size 1 is recommended for evaluation, due to size. This includes Model Number(s)
UNI1401, UNI1402, UNI1403, UNI1404 or UNI1405. The Unidrive comes configured for
open loop operation as default, and this mode is assumed in this guide.

UD77 (UD70 with DeviceNet Interface) for each Unidrive.

The UD77TB (P/N 9290-56) is a small adapter PCB that provides a standard DeviceNet
open-style terminal connector and one is supplied with each UD77. A UD77 that is “up to
revision” contains the following subassemblies and firmware:

• UD70 System file DNET.SYS (V2.6.0 is earliest, V2.7.6 or later is recommended)

• UD70 Hardware UD70 issue 3

• UD77 Firmware (V2.00)

• UD77 Hardware UD77 Issue 2

DeviceNet Physical Media (the wire, power supply and terminating resistors)

Page 6 of 77

DeviceNet cable with five (5) conductors

• 1 pair for 24V DC

• 1 pair for CAN data transmission

• 1 shield

• Conductors (color coded to Open DeviceNet Network Vendors Association standard)

Thin Cable and/or Thick Cable.

• Thin Cable P/N 1485C-P1-Cxxx (where xxx is length in meters) is rated at 3.0 amps DC.
Thin Cable can be used for the physical media for both Trunk Line and any Drop Line on a
small DeviceNet network.

• Thick Cable P/N 1485-A1-Axxx (where xxx is length in meters) is rated at 4.0 amps DC
(NEC in North America) or 8.0 amps elsewhere in the world. Thick Cable is usually used for
a DeviceNet Trunk Line, and details of its use are not described further in this guide.

Note: This guide describes an open-style daisy chain DeviceNet network with a single Trunk
Line utilizing Thin Cable.

Terminating Resistor

DeviceNet cable uses two open-style terminating resistors. These are included with
each 1747-SDN scanner. These have a value of 121 ohms (+/- 1%) and are rated at ¼
watt.

24 Volt DC regulated power supply

Rated from 1.0 to 8.0 amps, depending on the media used. For verification of a small
DeviceNet network such as described in this guide, the unregulated 24 Volt DC supply
found on the SLC 500 is adequate, and the use of Thin Cable for the media is
recommended. A regulated AC to DC +24 volt power supply rated at 1.0 amp (25 watts)
minimum to a maximum of 3.0 amps (75 watts) is required for a practical DeviceNet
network. Switching Regulators in a DIN-rail mounting format are among the latest
designs for these applications and are recommended.

Page 7 of 77

SLC500 Rack

1746-IO12DC

6 - Discrete Inputs

6 - Discrete Outputs

(slot 2)

SLC 5/04

Processor

(slot 0)

RS-232 to Host PC

*T.R.

1747-SDN

DeviceNet

Scanner

(slot 1)

+24V DC

P/S

1770-KFD

DevceNet

to

RS-232

serial interface

Unidrive

# 2

UD77

UD77

TB

Evaluation DeviceNet Network

logical layout

Unidrive

# 1

UD77

UD77

TB

*T.R. - Termination

*T.R.

Page 8 of 77

Hardware Installation

p

Step 1. Assemble Modules and SLC Rack into a Complete PLC

1747-SDN

Power Supply
Module

SLC 5/04

rocessor

DeviceNet
Scanner

1746-IODC 12
Discrete I/O

Complete SLC 500 PLC 4 slot Modular Rack, Power Supply, 5/04 Processor, Scanner and
Combination I/O. Note that discrete I/O module is not yet plugged in, and is not used in this

guide.

Refer to the following Allen Bradley installation instructions for additional and more detailed
information (these Allen Bradley publications are included with the respective module).

• SLC 500 Modular Chassis

• SLC 500 Power Supplies

• SLC 5/03, 5/04, and 5/05 Modular Processors

• DeviceNet Scanner Module

• DeviceNet RS-232 Interface Module

• Discrete I/O Modules

1. Be sure the incoming AC supply is turned off.

2. Mount and properly ground your SLC chassis. Use a dedicated ground strap.

3. Align and slide the SLC power supply until flush with the chassis, then fasten the supply to
the chassis with the screws to the left side of the supply. Set the input voltage jumper to
match the input voltage, then connect the chassis ground and incoming AC power. Finally
remove the protective label.

4. Insure the back-up battery is properly connected to the processor, then insert the SLC 5/0x
processor into the leftmost slot (slot 0) of the SLC Rack.

Page 9 of 77

5. Insert the 1747-SDN scanner into the rack. This guide recommends using slot 1, which is
right next to the SLC 5/0x processor slot.

6. Insert the Discrete I/O module into the next slot. Do not yet seat the module into the back­plane connector. The initial RSLogix500 project file does not declare an I/O module, and
downloading a project file with undeclared modules fitted to a rack produces a major fault.

Step 2. Assemble the DeviceNet Network

1. Assemble the UD77 DeviceNet Module(s) and fit the assembly into each respective
Unidrive.

A. Fit one UD77TB DeviceNet open-style terminal connector to each UD77 Coprocessor.
B. Insert the assembled Co-processor into the large option bay in each Unidrive.

2. Continue to insure incoming power is turned off, and mount and properly earth ground each
Unidrive as appropriate.

3. Continue to insure incoming power is turned off, and connect the input voltage and control
connections to the Unidrive. Then connect the motor leads as described in the Unidrive
Installation and User’s Guide.

A. For a development and evaluation DeviceNet network that is not fitted with any AC

Motors, or is only operating the AC Motors unloaded, the Unidrive(s) can be adequately
powered via a fused, single phase 415 to 460 VAC supply. Operation without motors is
normally done only in open loop mode on the Unidrive.

B. Practical networks on real control systems driving real motor loads have the Unidrive(s)

powered via fused 460 VAC 3 phase supplies following guidelines set out by the NEC
(or equivalent jurisdiction) regarding the details concerning wiring conductor size,
insulation type, and over-current protection requirements. This guide does not provide
further guidance on this subject.

C. A development and evaluation DeviceNet network requires a jumper or a single pole

single throw switch controlling continuity from terminal 31 to terminal 30 (Drive enable)
on each Unidrive as the minimum control connection required for useful operation. This
means one jumper or switch for each Unidrive.

D. Practical networks on real control systems driving real motor loads have Emergency

Stop / Reset logic in hardwired relay ladders that provide a contact to each Unidrive to
control continuity from terminal 31 to terminal 30. This means one normally open
contact for each Unidrive, closed in a no-fault (reset) condition.

4. Mount the 1770-KFD DeviceNet interface.

A. For most network configuration(s) the 1770-KFD Interface can take its power from the

DeviceNet network 24 Volt supply.

B. A separate 9.0 Volt DC supply just for the Interface is only needed if the DeviceNet

Interface is connected to the network via isolating taps and network +24 Volts DC is not
available to the 1770-KFD interface. Continue to insure power is off, and connect the
DeviceNet devices together using the appropriate DeviceNet cabling.

Page 10 of 77

5. Connect the DeviceNet Nodes together using suitable DeviceNet Physical Media.

A. For a development and evaluation DeviceNet network, Thin Cable (P/N 1485-P1-C) is

suitable for use on the open-style daisy-chain, the single main Trunk Line that makes up
the DeviceNet network.

B. Larger, practical networks on “real” control systems with many DeviceNet “devices” use

Thick Cable (P/N 1485-A1-A) for the Main Trunk and Thin Cable (P/N 1485-P1-C) on the
Drop Lines. Such networks usually also include additional DeviceNet parts such as
“Taps”, “DeviceNet Connectors”, and “Terminating Plugs” to facilitate connection of
network devices.

C. The 1747-SDN Scanner and the 1770-KFD DeviceNet connectors are color coded to

indicate conductor location.

D. The DeviceNet open-connector terminal strip on the UD77TB is not color-coded. See

illustrations for guidance.

6. Mount and connect one or more suitable +24 VDC Power Supply or Supplies.

A. For a development and evaluation DeviceNet network, the 24 Volt DC available from the

SLC 500 modular power supply can also be used to provide the DeviceNet +24 Volt DC
supply. As this supply is not regulated, and the DeviceNet specification states that this
voltage must not be above 25 Volts DC, it is prudent to measure and insure that the
voltage is not above 25 Volts DC, once power is applied to the network. A one-to-three
amp switching +24 Volt DC supply (in a DIN rail format) is otherwise recommended.

B. On larger, practical networks on “real” control systems with many DeviceNet “devices”,

the use of one or more regulated +24 Volt supplies and “Power Taps” are an important
part of the design and specification of a DeviceNet network. Documentation and
software tools to assist in this portion of specifying a “real” DeviceNet system can be
found in manuals listed in the Appendix.

RS-232 to PC

7. Terminate each end of the Main Trunk Line with a 121-ohm 0.25 Watt resistor.

See the following illustrations for guidance.

Photo of 1747-KFD serial RS-232 DeviceNet interface

Page 11 of 77

DeviceNet to rest of network

UD77 with DeviceNet
Terminal Block installed

Photo of UD77 including DeviceNet UD77TB open terminal adapter

(P/N 9290-0056)

Photo of 121-ohm 0.25 Watt Termination Resistor fitted to 1747-SDN Scanner

Page 12 of 77

at the beginning of the Trunk Line

Photo of 121-ohm 0.25 Watt Termination Resistor fitted to UD77

Page 13 of 77

at the end of the Trunk Line

(furthest from the Scanner)

UD77 #1

9200-0056

UD77TB

Unidrive

Unidrive

No. 1

No. 2

DeviceN et to

1770-KFD

UD77 #2

9200-0056

UD77TB

Thin CAble 1485-P1-C

Connection Detail

Thin CAble 1485-P1-C

RS-232

interface

Small, Evaluation DeviceNet Network Main Trunk

1747-SDN

Connection Diagram for Evaluation DeviceNet Network

Page 14 of 77

SCANNER

Conductor color details shown

from

24 volt

supply

Step 3. Using a “EMPTY.RSS” project

When a SLC 500 Rack is first assembled, with a new processor that just had the Battery
Backup connected, the processor powers up to a checksum fault.

One of the ways to clear this checksum fault condition is to configure communication from your
PC with RSLinx and download an “empty” project into the Processor with RSLogix500. Project
“EMPTY.RSS” is a RSLogix500 project that assumes only the Processor is plugged into the
SLC 500 Rack (Discrete I/O and 1747-SDN modules unplugged with power OFF).

For most Laptops and Desktop PC(s), a null-modem style cable, such as an serial “Interlink”
cable or a serial “Laplink” cable is required for establishing communication from the PC to the
processor. The cable that comes with the 1770-KFD DeviceNet Serial interface can also be
used. A simple 9-pin “D-shell” straight-through male-to-female RS-232 extension cable and a
gender-changer will not work. See the Appendix for the connection(s) to make an adapter for
use with this type of extension cable.

Configuring the RSLinx Driver “RS-232 DF1 Devices” to communicate from the configuration PC
into the SLC “DF-1 CH0” port (the default), loading a project from disk into RSLogix500, and
downloading that project into the SLC processor are covered in detail in the section “Using
RSLogix500 and Linx Lite” of this Start Up Guide.

Note: If the processor does not require re-initialization, (for example, the processor had already
had a previous program loaded into its memory) project “FIRST.RSS can be ignored.

Page 15 of 77

DeviceNet Manager Installation

In this guide, COMM1 will be used for both configuring the DeviceNet Scanner and
network with DeviceNet Manager, then later to program the SLC 500 with RSLogix500.
This will allow either a laptop or a desktop PC use. Only one of the programs can use
the port at a time, however. If a PC is available with 2 ports, It is recommended that

COMM1 be dedicated for use by DeviceNet Manager (and the 1770-KFD interface) and
COMM2 be dedicated for use by the “DF1 protocol” and RSLogix500.

This guide shows DeviceNet Manager installation and *.EDS file downloads from a 3 ½
inch floppy, drive “A”. If installing from CD-ROM media, make changes to drive
designations as necessary.

This guide recommends and illustrates that DeviceNet Manager installation to the
Configuration PC be immediately followed by the installation of all Control Techniques
“*.EDS” files that are included with “dvnet.zip”.

DeviceNet Manager will be installed and configured to properly recognize the capabilities
of Control Techniques products.

Step 1. DeviceNet Manager Installation to Hard Drive

Insert DeviceNet Manager “Disk 1” into floppy drive “A:” and Run A:\Setup.exe.
Follow the on-screen prompts. Default installation paths are recommended.

From the Start menu select Run and type “A:\Setup.exe”, “click OK

Page 16 of 77

Basic application installation is complete. Click “Run Application”.

DeviceNet Manager launches and displays this “opening splash screen”.

Page 17 of 77

Main frame window for the DeviceNet Manager Version 3.002 awaits user input, ready
for installation of Control Techniques “ *.EDS” files.

Step 2. Installation of Control Techniques “EDS” files to DeviceNet
Manager

The following steps demonstrate installation of Unidrive and Mentor 2 files.

Insert the floppy disk with the files “unzipped” from the Control Techniques supplied file
“devnet.zip” into floppy drive “A:”.

Page 18 of 77

Use Windows Explorerâ to check and confirm that the necessary files are present.

From the DeviceNet Manager menu, click on Utilities, and click on “I

nstall EDS Files”.

A ”locate file style” window with a “*.eds” filter appears. From the “Drives:” list
box, select “a”.

Page 19 of 77

Select and install the generic Unidrive “EDS” and bitmap files first. Click on the g2*.eds
and g3*.eds files. The screen should now look like the one above. Click OK. After the
file copy, a confirmation box will appear, click OK.

A “locate file” style dialog box appears with a “*.bmp” filter. From the “Drives” list box,
select “a”.

Page 20 of 77

This view of the floppy files will appear; select “unidrive.bmp”. Click OK.

The next steps download the Mentor2. From the DeviceNet Manager menu, select
Utilities and click on “I

nstall EDS Files”.

Navigate to “a:” and select the g4*.eds and g5*.eds files as shown. Click OK. A
confirmation box will appear, click OK.

Page 21 of 77

Navigate to “a:”. This view of the floppy files is shown; select “mentor2.bmp”. Click OK.
Installation of the Control Techniques “EDS” files into DeviceNet Manager is complete.
The main frame window for DeviceNet Manager is ready for the next step.

Step 3. Creation of the “FIRST” DeviceNet Project with DeviceNet Manager

The project “FIRST” is a starting point, which defines “DEMO”, a simple
DeviceNet network consisting of a single SLC5/04 processor, a 1747-SDN
scanner, a 1770-KFD serial interface, and two Unidrive(s) each fitted with a
UD77 DeviceNet Interface with co-processor.

The setup and validation strategy is to create the project, get the DeviceNet
Scanner and DeviceNet Interface communicating at the default data rate without
any of the Unidrive(s) present on the network, and then power up, configure, and
add the Unidrive(s) to a working network.

Note that this guide shows use of a Scanner MAD-ID of “63” (default), and a
network data rate of 125Kbits/sec (default). This guide describes configuring the
Unidrives for a MAC-ID of “1” and “2”. Configuration at different MAC-ID(s) and
different network data rats is covered in the Control Techniques application note
“Allen Bradley SLC500 PLC with DeviceNet”.

Before starting, close DeviceNet Manager and then re-start DeviceNet Manager. This
forces DeviceNet Manager to read its *.ini(s) and properly initialize details such as the
program data paths that will be used.

Page 22 of 77

From the DeviceNet Manager menu, select File and click on “New Project…”.

In the “New Project” dialog window, enter “FIRST” in the “Project Name” field and
“Project Description” as shown. The default installation path is recommended. Click
OK.

At the “Add Network to project” dialog box, complete the fields as shown. Click OK.

Page 23 of 77

This empty network graphic for network “DEMO” in project “FIRST” appears when the
project and network are defined.

Step 4. Configuring Initial “Interface-to-Scanner” Communication

The next step is to get DeviceNet Manager communicating via the 1770-SDN
interface to the 1746-KFD Scanner without any other DeviceNet “devices” on the
fieldbus.

Apply control power only to the SLC 500 Rack, the DeviceNet 24-Volt Power Supply and
the 1770-KFD interface. Be sure that the Unidrives remain powered down for the next
step.

From the DeviceNet Manager menu, click on Utilities and select “S
Connection”.

Page 24 of 77

etup Online