Configuration Manual: Allenćbradley

AllenĆBradley
DeviceNet
Scanner
Configuration
(Cat. No. 1747ĆSDN)
Manual
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.
The illustrations, charts, sample programs and layout examples

shown in this guide are intended solely for 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 which 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 Allen-Bradley
Company, Inc., is prohibited.
Throughout this manual we make notes to alert you to possible

injury to people or damage to equipment under specific
circumstances.
ATTENTION: Identifies information about practices

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

• Identify a hazard.
• Avoid the hazard.
• Recognize the consequences.
Important: Identifies information that is especially important for

successful application and understanding of the product.
Important: We recommend that you frequently back up your
application programs on an appropriate storage medium
to avoid possible data loss.
PLC-5, DeviceNetManager, SLC, SLC 500, SLC 5/02, FLEX I/O, DH+, and RediSTATION are trademarks of
Allen-Bradley Company, Inc.
DeviceNet is a trademark of Open DeviceNet Vendor Association (O.D.V.A.).
Windows is a trademark of Microsoft.
Microsoft is a registered trademark of Microsoft.
IBM is a registered trademark of International Business Machines, Incorporated.
All other brand and product names are trademarks or registered trademarks of their respective companies.
Summary of Changes
Revised Information The 1747-SDN scanner has added support for change-of-state and
cyclic messaging in addition to poll and strobe messaging.
Change-of-state messaging allows devices supporting

change-of-state to produce data only when actuated. Change-of-state
dramatically reduces network traffic and bandwidth usage effectively
allowing for higher performance and faster system throughput times.
Cyclic messaging allows devices supporting cyclic to be configured

to produce data at a specified rate. Cyclic data production reduces
repetitive information on the wire and in the scanner’s data table
while reducing traffic on the DeviceNet network.
The graphical screens in DeviceNetManager software, version

3.001, have changed the look of some of the 1747-SDN
configuration screens.
See the following table for specific screens and procedures that have
changed due to the graphical screens in the software.
For more information on See page

1747ĆSDN scanner configuration screen map 1-7
Using the Module and Channel Configuration screen - 3-8
edit scan list
Adding devices to the scan list 3-11
Revision Bars We use revisions bars to call your attention to new or revised
information. A revision bar appears as a thick black line on the
outside edge of the page as indicated here.
Publication 1747Ć6.5.2 - May 1997

Table of Contents
Important User Information . . . . . . . . . . . . . . . . . . . . 1
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . soc-i

Revised Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . soc-i
Revision Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . soc-i
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1

What's in This Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-2
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-2
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-4
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-4
Engineering and Field Services . . . . . . . . . . . . . . . . . . . . P-4
Technical Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-4
Repair and Exchange Services . . . . . . . . . . . . . . . . . . . . P-4
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

What's in This Chapter? . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
What You Need to Know . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
What Your Scanner Does . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Communicating with Your Devices . . . . . . . . . . . . . . . . . . 1-3
Communicating with Your SLC 500 Processor . . . . . . . . . 1-4
What Scanner Data Tables Are and What They Do . . . . . . . . 1-5
Scanner Configuration Table (SCT) . . . . . . . . . . . . . . . . . 1-5
Scan List Table (SLT) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
DeviceNetManager Software as a Configuration Tool . . . . . . 1-6
1747ĆSDN Configuration ScreenĆMap . . . . . . . . . . . . . . . 1-7
What's Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Planning Your Configuration . . . . . . . . . . . . . . . . . . . 2-1

What's in This Chapter? . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Beginning the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Planning Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
About This Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Part I - Photoelectric Sensor Mapping Input Data
for a Discrete I/O Transfer . . . . . . . . . . . . . . . . . . . . . 2-3
Part II - RediSTATION Operator Interface Mapping Input
Data for an M1 File DataĆTable Read . . . . . . . . . . . . . 2-4
ii Table of Contents
Part III - RediSTATION Operator Interface Mapping Output

Data from a Discrete I/O Data Transfer . . . . . . . . . . . . 2-5
What's Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Configuring Through DeviceNetManager Software . . 3-1

What's in This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Beginning the Configuration Process . . . . . . . . . . . . . . . . . . 3-1
Online and Offline Configuration . . . . . . . . . . . . . . . . . . . 3-2
Configuring Your 1747ĆSDN Scanner . . . . . . . . . . . . . . . . . . . . . . 3-2
Accessing the Module Configuration Screen . . . . . . . . . . . 3-3
Setting the Module's Operational Parameters . . . . . . . . . . 3-4
Assigning Names From the Project . . . . . . . . . . . . . . . . . 3-6
Accessing the Scan List Editor Screen . . . . . . . . . . . . . . . 3-7
Entering the Scan List Editor Screen Through a Project . 3-7
Entering the Scan List Editor Screen Through
Network Who . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Using the Scan List Editor Screen . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Scan List Editor Functions . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Removing Devices from the Scan List . . . . . . . . . . . . . . . 3-9
Viewing Device Information in the Scan List . . . . . . . . . . . 3-9
Adding Devices to the Scan List from the Scan List
Editor Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Configuring a Device in the Scan List . . . . . . . . . . . . . . . . 3-13
Using the Slave Mode Function . . . . . . . . . . . . . . . . . . . . 3-14
Determining DataĆMapping Preferences with Auto Map . . . 3-15
About the Data Table Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Using the Data Table Map for Custom Editing . . . . . . . . . . 3-18
Mapping Specific Bits to Specific Device Memory Locations 3-19
About Your Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
What's Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
If You Encounter Error Messages . . . . . . . . . . . . . . . . . . 3-21
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
What's in This Appendix? . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Scan List Example . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

What's in This Appendix? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Understanding a Scan List Example . . . . . . . . . . . . . . . . . . B-2
Photoelectric Sensor Input Mapping Scheme Example . . . B-3
Node Address 21 Input Data . . . . . . . . . . . . . . . . . . . . B-4
Table of Contents iii
RediSTATION Operator Interface Input Mapping

Scheme Example . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
RediSTATION Operator Interface Output Mapping
Scheme Example . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
Node Address 50 Input and Output Data . . . . . . . . . . . B-8
FLEX I/O Module Input Mapping Scheme Example . . . . . . B-9
FLEX I/O Module Output Mapping Scheme Example . . . . . B-10
Node Address 22 Input and Output Data . . . . . . . . . . . B-11
Data Map Example . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

What's in This Appendix? . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Example Input Mapping Scheme . . . . . . . . . . . . . . . . . . . . . C-1
Example Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Example Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Example Output Mapping Scheme . . . . . . . . . . . . . . . . . . . . . . . . C-4
Example Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Example Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Preface
About This Manual
What's in This Manual? Use this manual to help you understand how:
• the 1747-SDN scanner communicates with a SLC 500
processor and DeviceNet devices
• to map I/O data using DeviceNetManager software
• to configure your 1747-SDN scanner
Chapter 1
Chapter 2
Read this chapter Chapter 3
before you begin Read this chapter
configuring your to plan your Read this chapter
scanner. configuration. to configure the
scanner by using
DeviceNetManager
software.
Appendix A
Appendix B
Read this appendix
Appendix C
for help with Read this appendix
troubleshooting. to see a scan list Read this appendix
example. to see a data map
example.
Audience We assume that you:

• are developing a DeviceNet network using a SLC 500 processor
in conjunction with a 1747-SDN scanner
• know each of your device’s I/O parameters and requirements
• understand SLC processor programming and operation
• are familiar with APS or WINtelligent software
• are proficient with DeviceNetManager software
• are familiar with the Microsoft Windows environment

P–2
Conventions The following conventions appear throughout this manual to guide

you through the information and concepts.
Important: Your screens may appear slightly different than the ones
depicted in this manual if you are running
DeviceNetManager software on a platform other than
Windows NT, version 4.0.
This is a definition A definition box defines terms that may be unfamiliar to you.
box. When a word
is bold within the
text of a paragraph,
a definition box will
appear in the left
margin to further
define the term.
Screen captures are pictures of the software's actual screens.

The names of screen buttons and fields are often bolded in the
text of a procedure.
Step numbers appear on the screen captures by the

1
corresponding buttons or fields discussed in the procedure text.
The MORE" icon is placed beside any paragraph that references

sources of additional information outside of this document.
The screenĆsummary arrow points to a table that summarizes

Screen Summary each button and field of the corresponding screen capture.
The optionalĆstep arrow points to a step that is not required for

Optional Step
scanner configuration. It may be a standĆalone feature or may be
dependent upon a set list of criteria.
Related Publications Title Publication Number

DeviceNetManager Software User Manual 1787Ć6.5.3
DeviceNet 1747ĆSDN Scanner Module Installation Instructions 1747Ć5.8
Scanner
(1747ĆSDN)
Installation
Instructions
DeviceNet
Manager User
Software
(Version 2.0) Manual
(1787ĆMGR)

P–3
Terminology This term Means

Change of State The scanner module can send and receive data with slave devices
that have the change of state feature. Data is sent whenever a
data change occurs or at a userĆconfigurable heartbeat rate.
Cyclic The scanner module can send and receive data with slave devices
that have the cyclic feature. Data is only sent at a
userĆconfigurable rate.
Dual Mode The scanner is in dual mode when it serves as a master to one or
more slaves and as a slave to another master simultaneously.
EDS An electronic data sheet is a vendorĆsupplied template that dictates
how information is displayed as well as what is an appropriate
entry (value).
Explicit Messaging This messaging protocol states the meaning of the message.
The Explicit Message protocol commands the performance of a
particular task and returns the results of the task performance to
the requestor.
Heartbeat Rate The heartbeat rate is associated with producing data once every
EPR (Expected Packet Rate) duration. You may have four EPRs
before you time out. This only applies to change of state and cyclic
messaging.
I/O I/O is an abbreviation for input and output data."
Input Data This data is produced by a DeviceNet device and collected by the
scanner and made available for a PLC processor to read.
Output Data This data is produced by a PLC processor that is written to the
scanner's memory. This data is sent by the scanner to DeviceNet
devices.
MAC ID A MAC ID is the address of a DeviceNet node.
Network This is a DeviceNet network or DeviceNetManager software
representation of a network.
Node A node is the hardware that has a single address on the network
(also referred to as device).
Offline This is when the communication adapter is not able to
communicate on the network.
Online This is when the communication adapter is configured and enabled
to communicate on the network.
PC This is an abbreviation for an IBM compatible personalĆcomputer.
Poll This is a type of input/outputĆdata communication. A poll message
solicits a response from a single, specified device on the network
(a pointĆtoĆpoint transfer of data).
Processor This is a PLC programmable controller.
Record This is a node address and channelĆspecific memory assigned in
the scanner's nonĆvolatile storage for a node in the scan list.
Rx This is an abbreviation for receive".
Slave Mode The scanner is slave mode when it serves as a slave to another
master.
Strobe This is a type of input/outputĆdata communication. A strobe
message solicits a response from each scanned device (a multicast
transfer). It is a 64Ćbit message that contains one bit for each
device on the network.
Scanner This refers to the 1747ĆSDN scanner.
Tx This is an abbreviation for transmit".

P–4
Support Services At Allen-Bradley, customer service means experienced

representatives at Customer Support Centers in key cities
throughout the world for sales, service, and support.
Our value-added services include:
Technical Support
• SupportPlus programs
• telephone support and 24-hour emergency hotline
• software and documentation updates
• technical subscription services
Engineering and Field Services
• application engineering assistance

• integration and start-up assistance
• field service
• maintenance support
Technical Training
• lecture and lab courses

• self-paced computer and video-based training
• job aids and workstations
• training needs analysis
DeviceNet courses Designing a DeviceNet Network (course no.
CCP160) and Configuring a DeviceNet Network (course no.
CCP161) are currently offered. Contact your local authorized
Allen-Bradley distributor or sales/support office for
more information.
Repair and Exchange Services
• your only “authorized” source

• current revisions and enhancements
• worldwide exchange inventory
• local support

Chapter 1
Before You Begin
What's in This Chapter? Read this chapter to understand communication between a SLC 500
processor and DeviceNet devices through a 1747-SDN scanner,
the data tables, and the DeviceNetManager screens used to
configure data tables.
For information on See page

What you need to know 1-1
What your scanner does 1-2
Communicating with your devices 1-3
Communicating with your 1-4
SLC 500 processor
What scanner data tables are 1-5
and what they do
Scanner configuration table (SCT) 1-5
Scan list table (SLT) 1-5
DeviceNetManager software as a 1-6
configuration tool
1747ĆSDN scanner configuration 1-7
screen map
What's next 1-8
What You Need to Know Before configuring your scanner, you must understand:
• the data exchange between an SLC 500 processor and DeviceNet
devices through the 1747-SDN scanner
• user-configurable scanner data tables
• the role of DeviceNetManager software

1–2 Before You Begin
What Your Scanner Does In a typical configuration, the scanner acts as an interface between
DeviceNet devices and an SLC processor. The scanner
communicates with DeviceNet devices over the network to:
• read inputs from a device
• write outputs to a device
• download configuration data
• monitor a device’s operational status
A M1/M0 file transfer The scanner communicates with the processor in the form of
is a method of M1/M0 File Transfers and/or Discrete I/O (DIO).
moving large Information exchanged includes:
amounts of data
between a SLC 500
processor and its • device I/O data
scanner. It transfers • status information
files containing a
maximum of 256 • configuration data
words and may take
more than one SLC The following is an example configuration.
programĆscan
to complete.
host computer with PLC
programming software
Discrete input and
output (DIO) is the
transfer of one to
32 words between DH+t network or DHĆ485 network
1747ĆSDN scanner
a SLC 500
processor and a
scanner. All 32
words of input data
and all 32 words of
output data are SLC 500 chassis with a 1784ĆPCD
updated on each SLC 5/02 (or greater) processor PCMCIA
SLC program scan. computer with
card DeviceNetManager
software
DeviceNet network
Flex I/Ot rack

DeviceNet devices
RediSTATIONt
operator interface
1305
drive

Before You Begin 1–3
Communicating with Your Devices
A strobe message is a Your scanner communicates with scanned device’s via strobe, poll,
multicast transfer of data change of state, and cyclic messages. It uses these messages to
(which is 64 bits in length)
sent by the scanner that solicit data from or deliver data to each device. Data received from
solicits a response from the devices, or input data, is organized by the scanner and made
each slave device. There available to your processor. Data received from your SLC processor,
is one bit for each of the
possible 64 node or output data, is organized in the scanner and sent on to
addresses. The devices your devices.
respond with their data,
which can be as many as Important: Throughout this document, input and output are defined
8 bytes.
from the SLC processor’s point-of-view. Output is data
sent from the processor to a device. Input is data
A poll message is a collected by the processor from a device.
pointĆtoĆpoint transfer of
data (0 to 255 bytes)) Important: All data sent and received on a DeviceNet network is in
sent by the scanner that byte lengths. A device may, for example, produce only
solicits a response from a
single device. The device two bits of input information. Nevertheless, since the
responds with its input minimum data size on a DeviceNet network is one byte,
data (0 to 255 bytes). two bits of information are included in the byte of data
produced by the device. In this case (only two bits of
input information), the upper six bits are insignificant.
1747ĆSDN Scanner DeviceNet Devices
A change of state
message is a pointĆtoĆ Input Data From
point transfer of data sent Input Data Storage DeviceNet Devices
whenever a data
Byte A1 A2
change occurs or at a
userĆconfigurable A1 0
Notice that bits can be mapped to
heartbeat rate. This does separate scanner memory locations; B 1
not solicit a response. this is known as map segmenting. input from the B
C 2 devices to the
This concept is illustrated in byte A."
A2 3 SLC processor C
A cyclic message is D 4
sent only at a
userĆconfigurable rate. E 5 D
...
E
Output Data To
DeviceNet Devices
Output Data Storage
X
X
Y
output from the Y
Z SLC processor

Communicating with Your SLC 500 Processor
An M1 file transfer Your processor communicates with the scanner via M1 file transfer
is the transfer of reads, M0 file transfer writes, and DIO transfers. Input data,
data from the
scanner to the gathered from the network’s devices, is organized within the scanner
processor. and made available for the processor to “read” from the M1 file.
The scanner
makes data The scanner does not send data to your processor. Data transferred
collected from the
network's devices between your scanner and processor must be initiated by
available for the the processor. Output data is sent, or “written,” to the scanner by
processor to read". your processor by placing the data in the M0 file. This data is
organized in the scanner, which in turn passes the data on to your
scanned devices via strobe, poll, change of state, or cyclic messages.
An M0 file transfer
is the transfer of SLC 500 Processor 1747ĆSDN Scanner
data from the SLC
500 processor to Discrete Input Image Internal Input
the scanner. The Data Storage
processor writes" B
data to the A1 Discrete
scanner's memory. I/O Transfer A1
M1/M0 File Transfer Data File B
I/O Map
C C
A2 M1 file A2
Dashed line boxes indicate the transfer
D (read) D
mapĆsegmented data.
E E
Discrete Output Image
X Discrete Internal Output

I/O Transfer Data Storage
M0 Data File
Z X
Y Y
I/O Map Z
M0 file
transfer
(write)

What Scanner Data Tables To manage the flow of data between your processor and a network’s
Are and What They Do devices, the scanner uses the following data tables.
• Scanner Configuration Table
• Scan List Table
• Device Input Data Table
• Device Output Data Table
• Device Active Table
• Device Failure Table
• Client/Server Transaction Tables
You may configure two of these data tables through
DeviceNetManager software. These tables are stored in the scanner’s
non-volatile memory and used to construct all other data tables:
• Scanner Configuration Table (SCT)
• Scan List Table (SLT)
Scanner Configuration Table (SCT)
The SCT controls basic information your scanner needs to function

on your DeviceNet network. It tells your scanner:
• if it can transmit and receive input and output data

• how long it waits after each scan before it scans the devices again
• when to send out its poll messages
Scan List Table (SLT)
The SLT supports I/O updating for each of your devices on the
network. It also makes it possible for your scanner to make device
data available to your SLC processor. The SLT tells your scanner:
• which devices to scan (node addresses)

• how to scan each device (strobe, poll, change of state, cyclic or
any valid combination)
• how often to scan your devices
• exactly where in each device’s memory to find the desired data
• the size of the input data/output data
• exactly where to map the input or output data for your processor
to read
• how your processor reads each device’s input data (M1/M0 file
or DIO)

DeviceNetManager Software DeviceNetManager software configures the scanner’s data tables.

as a Configuration Tool This software tool connects to the scanner via the DeviceNet
network and an RS-232 interface module (1770-KFD) or PC
Card (1784-PCD, PCMCIA interface card).
I/O communication User Data in this table DeviceNetManager See page

is the exchange configured configuration screen
and transfer of input tables
and output data.
SCT G basic operation 1747ĆSDN Module 3-3
parameters Configuration
G I/O communications
data (enable/disabled)
The interscan G interĆscan delay
delay is the time G background poll ratio
between scans.
It is the time the G scanner's node address Device Configuration For device configuration,
scanner will wait for (also known as MAC ID) Module's dip switches see publication 1787Ć6.5.3
nonĆslave device
SLT G deviceĆspecific Scan List Editor (SLE) 3-8
communication
before scanning identification data
again. G data transfer method Edit Device I/O Parameters 3-13
G transmit/receive data size
G input and output data These values can be 3-8 for SLE information
The background source and destination configured automatically or
poll ratio sets the locations through the Auto Map 3-17 for data table map
frequency of poll
function on the SLE or information
messages to a
device in relation to manually through the Data
the number of Table Map.
I/O scans.
For example: if the
ratio is set at 10,
that device will be
polled every 10
scans.

1747ĆSDN Configuration ScreenĆMap
The main dialog screen

can be accessed through
either the Network Who
or Project View.
To access the Module Configuration To access the Module Configuration

screen from a Network Who, double screen from a Project View, double click
click on the 1747ĆSDN scanner icon. on the 1747ĆSDN scanner icon.
To access the Scan List Editor,

choose Edit Scan List.
To have DeviceNetManager software
To edit the Scan List Editor display automatically map your device data,
properties choose Display Filters. choose Auto Map.
To view/edit your scan list's data table map,

To edit devices' I/O parameters, choose Data Table Map.
choose Edit I/O Parameters.

What's Next? Chapter 2 covers the configuration-process planning stage through a

data-mapping example. Chapter 3 details the configuration screens
and how to use them. Appendix A lists the possible error messages
you may see when mapping your I/O.
We recommend that you:

• read chapter 2 to become familiar with data mapping.
• read chapter 3 before configuring your scanner to become
familiar with the configuration procedure using the software.
• use appendix A to correct scan list problems prompted by
error messages.

Chapter 2
Planning Your Configuration
What's in This Chapter? This chapter introduces questions you should ask before configuring
your 1747-SDN scanner. In addition, it presents an example
DeviceNet network and I/O data mapping scheme.
For information about See page

Beginning the process 2-1
Planning example 2-2
Mapping input data for DIO 2-3
Mapping input data for M1 files 2-4
Mapping output data for DIO 2-5
What You Need to Know To map data via your scanner module, you must understand:
• your network requirements
• how to map input data
• how to map output data
Beginning the Process Planning before configuring your scanner helps make sure that
you can:
• use your memory and bandwidth efficiently
• cater to device-specific needs and requirements
• give priority to critical I/O transfers
• leave room for expansion
A very important question to answer is “what is on your network?”
You should be familiar with each device’s:
• communication requirements
• I/O importance and size
• frequency of message delivery
You should also ask “how might this network appear in the future?”
At this point in your planning, it is advantageous for you to have
some idea of how the network could be expanded. When mapping
your I/O, you have the opportunity to allot room for future I/O. This
can save time and effort in the future.

2–2 Planning Your Configuration
Planning Examples The following examples illustrate a data-mapping plan for a

DeviceNet network.
About This Example
This example has the following characteristics:

• an SLC 500 processor
• a 1747-SDN scanner
• four Series 9000 photoelectric sensors
• four RediSTATION operator interfaces (polled)
Important: In the following examples, output is data sent to a
device. Input is data collected from a device.
Series 9000 photoelectric sensor RediSTATION operator interface
Two input bits from each photoelectric Two input bits from each RediSTATION
sensor will be mapped: one status bit and indicator light operator interface will be mapped: one bit
one data bit. The data bit is needed for the green start button and one bit for the
quickly; therefore, this input data will be green start button red stop button. One output bit for each
mapped to the scanner's discrete operator interface will also be mapped: one
input data table. red stop button bit for each operator interface's indicator
light (on/off). Bit 4 of the input byte indicates
The photoelectric sensor if the bulb is missing.
produces one byte of input status The RediSTATION bit for green button
data in response to the bit operator interface produces
strobe message. one byte of input data and bit for
consumes one byte of input 1 byte
data red button
input 1 byte output data.
bit
bit for
output 1 byte
indicator light
RediStation operator interfaces

PC containing SLC
programming and photoelectric sensors
DeviceNetManager
software
DH 485 for
APS software
1784ĆPCD
PCMCIA
card
Node 1 Node 2 Node 5 Node 6
DeviceNet network
SLC 500 chassis with a SLC Node 3 Node 7 Node 8 Node 4

5/02 (or greater) processor.
photoelectric photoelectric
sensor sensor
RediStation operator interfaces

Planning Your Configuration 2–3
Part I - Photoelectric Sensor

Mapping Input Data for a Discrete I/O Transfer
The photoelectric sensor inputs are mapped to the scanner’s discrete

input data table and then to the SLC 500 processor’s input
image table.
Series 9000 Photoelectric Sensor Inputs

Note: The 1747ĆSDN resides in the
= unused bits for future use
chassis's second I/O slot.
D = data bit
ÈÈ
S = status bit
ÈÈ = bits reserved for module
ÈÈ
usage example: 3D = data bit for photoelectric sensor #3 status word
2S = status bit for photoelectric sensor #2
Photoelectric Sensor Input Bytes
What's Happening? photoelectric sensor node address 1 photoelectric sensor node address 2
1 The status and data bits from 1 byte 1S 1D 1 byte 3S 3D

each photoelectric sensor are
mapped into the scanner's
discrete input data table.
photoelectric sensor node address 3 photoelectric sensor node address 4
2 The discrete input data table
is then transferred via DIO to 1 byte 2S 2D 1 byte 4S 4D
the SLC 500 processor's
input image table.
1
Important: The scanner only
makes the data available for the
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈÈ
ÈÈÈ
ÈÈÈÈ
ÈÈ
ÈÈ
ÈÈ
processor to read. The scanner 1747ĆSDN Scanner Discrete Input Image Table
does not move the data to
the processor.
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈÈ
ÈÈÈ
ÈÈÈÈ
ÈÈ
ÈÈ
ÈÈ reserved for module status word word 0
data bits for 4D 3D 2D 1D word 1

SLC 500 Processor devices 0Ć63
Input Image Table are mapped to
words 1Ć4 word 2
(APS Software View)
Data
word 3
I:2.0 0000 0000 0000 0000
I:2.1 0000 0000 0000 0000
word 4
I:2.2 0000 0000 0000 0000
2
I:2.3 0000 0000 0000 0000
Address
I:2.4 4S 3S 2S 1S word 5
0000 0000 0000 0000
I:2.5 0000 0000 0000 0000 status bits for
word 6
I:2.6 0000 0000 0000 0000 devices 0Ć63
I:2.7 are mapped to
0000 0000 0000 0000
words 5Ć8 word 7
I:2.8 0000 0000 0000 0000
word 8
Example: The data bit for photoelectric
sensor #2 (2D) appears at address up to
I:2.1/1 (decimal) in the input image table
of your SLC processor.
word 31

Part II - RediSTATION Operator Interface

Mapping Input Data for an M1 File DataĆTable Read
Each RediSTATION operator interface’s input byte is mapped to the

scanner’s M1 File data table. In each station’s byte is a bit for the:
• red button (on/off)
• green button (on/off)
RediSTATION Inputs
= unused bits for future use
R = bit for red button The RediSTATION operator
ÈÈ
ÈÈ
G = bit for green button interfaces each have one green start
button, one red stop button, and a = bits reserved for module
ÈÈ
usage example: 5R = redĆbutton bit for station #5
5G = greenĆbutton bit for station #5 red indicator light. status word
What's Happening? RediSTATION Input Bytes

1 The bits for each
RediSTATION operator start/stop station node address 5 start/stop station node address 6
interface's red and green
buttons are mapped into the 1 byte 5G 5R 1 byte 6G 6R
scanner's M1 file data table.
2 The M1 file is then
transferred to the SLC 500 start/stop station node address 7 start/stop station node address 8
processor's input data file.
1 byte 7G 7R 1 byte 8G 8R
makes the data available for the
processor to read. The scanner 1
the processor.
1747ĆSDN Scanner M1 File Data Table
SLC 500 Processor
Input Data File 5G 5R word 0
(APS Software View)
Data
6G 6R word 1
N7:0 0000 0000 0000 0000
N7:1 0000 0000 0000 0000 7G 7R word 2
N7:2 0000 0000 0000 0000
Address
N7:3 0000 0000 0000 0000 8G 8R word 3
N7:4 0000 0000 0000 0000 2
N7:5 0000 0000 0000 0000
word 4
Example: The green start button from

RediSTATION #7 (7G) appears in the
SLC processor's input dataĆfile address N7:3/9.
up to
word
149

Planning Your Configuration 2–5
Part III - RediSTATION Operator Interface

Mapping Output Data from a Discrete I/O Data Transfer
Each RediSTATION operator interface’s output is mapped to the

scanner’s discrete output data table. Within each of these output
bytes is a bit for the indicator light. The discrete output data table is
then transferred from the SLC 500 processor’s output image table
via DIO. This example highlights the poll messages from which each
RediSTATION operator interface receives its output bit.
Mapping Example Part III

RediSTATION Output = unused bits for expansion
Note: The 1747ĆSDN resides in the
ÈÈ
L = bit for the station indicator light chassis' second slot. The RediSTATION
usage example: 7L = station indicatorĆlight bit operator interfaces each have one green
for RediSTATION #7 start button, one red stop button, and a
ÈÈ = bits reserved for the
ÈÈ
red indicator light. module command word
RediSTATION Output Bytes

What's Happening?
1 The indicatorĆlight bit
for each RediSTATION start/stop station node address 5 start/stop station node address 6
operator interface is
mapped to the scanner's 1 byte 5L 1 byte 6L
discrete output data table.
2 The discrete output dataĆtable
is then sent out to the operator start/stop station node address 7 start/stop station node address 8
interfaces via poll messages 2
from which each operator 1 byte 7L 1 byte 8L
interface receives its
indicatorĆlight bit.
SLC 500 Processor

ÈÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈÈ
ÈÈÈÈ
ÈÈ
1747ĆSDN Scanner Discrete Output Data Table
Output Image Table
ÈÈÈ
ÈÈÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈÈ
ÈÈÈÈ
ÈÈ
ÈÈÈ
ÈÈÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈÈ
ÈÈÈÈ
ÈÈ
(APS Software View) reserved for module command word word 0
Data
O:2.0 0000 0000 0000 0000 8L 7L 6L 5L word 1
O:2.1 0000 0000 0000 0000
Address O:2.3 0000 0000 0000 0000 1 word 2
O:2.4 0000 0000 0000 0000
O:2.5 0000 0000 0000 0000 data bits for word 3
devices 0Ć63
are mapped to
words 1Ć4 word 4
Example: RediSTATION operator interface #3's

indicatorĆlight bit (7L) is taken from
address O:2.1/2 in the SLC processor's Output
Image Table.

What's Next? The next step is to understand how to configure the scanner and
perform I/O data mapping through DeviceNetManager software.
The next chapter details:
• 1747-SDN Module Configuration
• 1747-SDN Scan List Editor
• Edit Display Properties
• Edit Device I/O Parameters
• 1747-SDN Auto Map
• 1747-SDN Data Table Map
• 1747-SDN Scan List Editor upload and download

Chapter 3
Configuring Through
DeviceNetManager Software
What's in This Chapter This chapter presents a summary and entry procedure for each
DeviceNetManager software scanner-configuration screen.

Beginning the configuration process 3-1
Configuring your 1747ĆSDN scanner 3-2
Using the Scan List Editor screen 3-8
About the data table map 3-17
About your files 3-21
What's next 3-21
What You Need to Know To configure your scanner, you should understand how to use these
DeviceNetManager software screens:
• Module Configuration
• Scan List Editor
• Edit Scan List Editor Display Filters
• Edit Device I/O Parameters
• Auto Map
• Data Table Map
• Upload
• Download
Beginning the The scanner configuration process begins on the Module

Configuration Process Configuration screen. The configuration process will follow these
steps:
• set your scanner’s basic I/O transfer parameters
• setup and/or edit your scan list
• view your finished scan list
Important: We recommend that you are familiar with data mapping
and have a mapping scheme planned for your
DeviceNet network before continuing. We further
recommend that you thoroughly read the following
procedures before attempting to configure your scanner.

3–2 Configuring Through DeviceNetManager Software
Online and Offline Configuration
You can configure your scanner module in an online or offline mode.

The following illustrates a typical process for each mode.
• Online configuration
1. Load settings into the configuration utility (editor)
- from a previously stored file.
- from a previously stored file referenced in a project.
- from the SDN (scanner module’s non-volatile memory).
2. Save settings to the SDN.
3. (optional) Save settings to a file.
This file can be “stand alone” or associated with a project.
• Offline configuration
1. Enter all device data and configuration settings.
2. Store settings in the project.
Settings are saved using file references. Depending on the
configuration screen you are saving, extensions can be
*.sm4, *.sl4, *.lr4, *.mr4, or *.clc.
Configuration Utilities
(MC, SLE, Data Table Map)
supplemental
information
Projects load and save configuration
file references settings (possible only when online) 1747ĆSDN
scanner
file references
load and save
configuration files
(always permitted)
1747 chassis
DeviceNet
disk
(floppy or hard drive)
Configuring Your The Module Configuration screen is the screen from which all other
1747ĆSDN Scanner scanner configuration screens are reached.

Accessing the Module Configuration 3-3
screen
Assigning names from the project 3-6
Accessing the Scan List Editor screen 3-7

Configuring Through DeviceNetManager Software 3–3
Accessing the Module Configuration Screen
To access the Module Configuration screen, the screen from which

all other scanner configuration screens are reached, double-click on
the 1747-SDN scanner icon.
Project View
Network Who
" When there is more than one scanner in the Project or Network Who
screen, you can tell what scanner a device belongs to by the color
that surrounds the device. You can also place the cursor over the
device until the yellow box is activated with the Product Type
information.
For example, a device highlighted in red belongs to the scan list in

the scanner highlighted in red.
A number also appears in the upper right corner of a device

indicating the scan list to which it belongs.
Important: The colors surrounding a device or scanner are arbitrary

and indicate nothing more than the scanner/device
relationship.

You see this screen.
The scan list editor title bar

indicates (in parenthesis)
where the data comes from
(file, project, SDN, or Who).
The Module Configuration screen allows you to set the scanner’s

module operational parameters and identify PLC addresses for
input and output data.
Setting the Module's Operational Parameters
1. Click on the I/O Comms check box to enable the input and output
communications.
This indicates to the scanner whether you want it to exchange I/O
data. If the scanner is enabled, it is able to actively transmit and
receive data to and from network devices.
Important: Your scanner cannot transmit or receive
anything on the network if this box is not
marked with an checkmark.
2. Enter the time the scanner waits between scans (between 2 and
9000 milliseconds) in the Interscan Delay edit box.
The default Interscan Delay is 10 milliseconds.
3. Enter the ratio of foreground to background polls (between 1 and
65535) in the Foreground to Bkgd Poll Ratio edit box.
Devices can be polled at a background rate instead of every scan.
Whether a device is polled every scan or at a background rate is
determined in the Edit I/O Parameters screen discussed on page
3–13. For example, if the value of 5 is set, the scanner polls the
selected device(s) once every six scans.

4. Set the loading options (files with an .sm4 extension):

Important: The software does not include the scanner or
itself in the scan list it builds.
A. To load data from your scanner’s non-volatile memory, in the
Load From field, choose SDN.
The screen is automatically updated with what was received
from the scanner.
B. Load data from a file in your pc, in the Load From field,
choose File.
You see a screen similar to this one.
You will only see the Network button if your pc is connected

to a network. This is unlikely for a mobile network pc.
Select the file you wish to load and choose OK.
C. To load module defaults from your scanner, in the Load From
field, choose Module Defaults.
With step C, the Module Configuration screen is
automatically updated. The title and status bars will reflect
the change.
From title bar
From status bar
5. From the Access drop list, choose the means by which

DeviceNetManager software will access the network for
configuring your scanner.
Currently the DeviceNet network is the only selection available.

6. Enter your scanner’s slot characteristics in the Slot edit box.

The slot value has been physically set on the scanner module with
DIP switches and are entered here for the software to
appropriately assign DIO addresses for mapping purposes.
7. Save your data:
To In this Field Choose
Save data to your scanner's nonĆvolatile memory1 Save to SDN
Save data to a file in your pc Save to File
1 This induces a flashĆmemory update if the scanner is in idle mode.
Assigning Names From the Project
To assign the project names you specified in the Project View screen
to the configuration file, choose Assign Names from Project.
Names include project, module, and network.
The Module Configuration screen automatically updates with the

names from the project.
Important: You can only assign names from a project when you
access the Module Configuration screen through the
Project View screen, not the Network Who screen.

Accessing the Scan List Editor Screen
Entering the Scan List Editor Screen Through a Project

project view module configuration scan list editor
or
*.sl4 file project device list
Entering the Scan List Editor Screen Through Network Who

Network Who module configuration scan list editor
Network Who device list

Using the Scan List The 1747-SDN Scan List Editor screen displays a summary of the
Editor Screen network residing on the channel selected in the Module
Configuration screen.

Scan list editor functions 3-8
Removing devices from the scan list 3-9
Viewing device information in the 3-9
scan list
Adding devices to the scan list from the 3-11
Scan List Editor screen
Configuring a device in the scan list 3-13
Determining dataĆmapping preferences 3-15
with auto map
Scan List Editor Functions
The 1747-SDN Scan List Editor screen displays a summary of the

network residing on the channel selected in the Module
Configuration screen and allows you to determine I/O and
data-mapping preferences.
" The Scan List Editor screen supports a multiple-selection method.

You can select multiple devices for edit at one time (these devices do
not have to be consecutive). For example, you can choose nodes 1
and 2, then skip to nodes 5 and 10. You do not have to choose the
nodes between 2 and 5 or 5 and 10. Highlight the specific nodes or
range of nodes then choose the desired function.
When you choose SDN Slave Mode, the scanner becomes enabled to
be placed in another scanner’s scan list as a slave device.

Removing Devices from the Scan List
To remove devices from the scan list in the Scan List Editor screen,
highlight the device(s) you want to eliminate and choose Remove.
Viewing Device Information in the Scan List
1. Set the loading options (files with an .sm4 extension):

Important: File operations are permitted online and offline.
However, if you are offline, you must save or
load your configuration settings to or from a file;
you cannot save or load to SDN.
Important: The software does not include the scanner or
itself in the scan list it builds.
A. To load data from your scanner’s non-volatile memory, in the
Load From field, choose SDN.
The screen is automatically updated with what is received
from the scanner.
B. Load data from a file in your pc, in the Load From field,
choose File.

Select the file you wish to load and choose OK.

C. To load module defaults from your scanner, in the Load From
field, choose Module Defaults.
With step C, the Module Configuration screen is
automatically updated. The title and status bars will reflect
the change.
From title bar
From status bar
2. Click on the device you wish to view so it is highlighted.

3. Click on the Active in Scanlist check box to include the device in
the scan cycle.
4. Click on the appropriate check boxes in the Electronic Key field
that you wish to facilitate device-record keying.
These items are a list of criteria that you can customize to fit your
application’s specific needs. An “X” in an item’s box indicates
that it is an active keying parameter. These selections are
hierarchical in descending order. For example, you cannot
choose Vendor without Device Type.
5. To edit the Scan List Editor display, choose Display Filters.

6. Customize the display by clicking on the box next to your

choice(s).
Important: Certain display-property combinations can result
in a blank Scan List Editor screen.
7. Choose OK.
You return to the Scan List Editor screen.
8. Save your data:
Adding Devices to the Scan List from the Scan List Editor Screen
When adding devices to the scan list, the source from which devices
are taken depends upon how you entered the scanner configuration
screens – through project view or Network Who.
If you entered the Then devices are added from

configuration screens through
Project view The project
Network Who The who
Follow these directions to add devices to your scan list from the scan
list editor.
1. Choose the appropriate button in the Add Devices From group

(Proj or Who).

You see the Add Devices to Scan List screen.
If you see this screen, the devices are currently scanned but are
not in the network. Click on the device(s) you want to add to the
scan list and choose OK.
2. To add a device to a scanner’s scan list, click on the device with

the left mouse button and drag it onto the scanner.

Notice the red box and the node number next to the device
indicating to which scan list it belongs.
3. Once you’ve made your changes, choose OK.
" You can double-click on the scanner you wish to configure. Devices
can then be dragged onto the scanner that is the device’s master.
Configuring a Device in the Scan List
1. To edit your device’s I/O communication parameters, choose

Edit I/O Parameters.
" When editing your devices, you can select one device or multiple
devices at a time. Highlight the desired devices and choose Edit
I/O Parameters. The entries made are then applied to all
highlighted devices.

2. Click on the Enabled check box in the appropriate field,

depending upon whether your device is strobed, polled,
change-of-state, or cyclic.
Important: Once you click on the check box next to
Enabled in the change of state/cyclic field, you
must click on the appropriate radio button next
to change-of-state or cyclic, depending upon
your device.
For this messaging type Enter
Strobed Strobed sizes
Polled Polled sizes and poll rate
ChangeĆofĆstate I/O size and heartbeat
Cyclic I/O size and send rate
" To have DeviceNetManager software set the EDS file to the

default setting, choose Set to EDS Default.
3. Choose OK.
4. Save your data:
Using the Slave Mode Function
1. Click on the 1747 scanner you wish to act in slave mode.

2. Choose SDN Slave Mode.
3. Choose Edit I/O Parameters.
Notice you are editing a slave device.

4. Click on the box Enabled check box in the appropriate field,

depending upon whether your device is strobed, polled,
change-of-state, or cyclic.
Important: Once you click on the Enabled check box in the
change-of-state/cyclic field, you must click on
the appropriate radio button next to
change-of-state or cyclic, depending upon your
device.
For this messaging type Enter
Strobed Strobed sizes
Polled Polled sizes and poll rate
ChangeĆofĆstate I/O size and heartbeat
Cyclic I/O size and send rate
" To have DeviceNetManager software set the EDS file to the

default setting, choose Set to EDS Default.
5. Choose OK.
6. Save your data:
Determining DataĆMapping Preferences with Auto Map
" For simpler and faster data mapping, use the auto map function to
map non-critical I/O devices and use the Data Table Map screen to
manually map critical I/O devices. You could use auto map as a
“first-pass” mapping procedure and the manual-mapping method as a
“fine-tuning” procedure.
1. Select the device(s) you would like to auto map in the scan list so
it is highlighted.
2. Choose Auto Map.

If you have a device that has already been mapped,

you have the option to reverse the process. Unmap
does not delete the selected device from the scan list,
but only removes any data mapping for the selected
device.
3. Click on the Input File and/or Output File check box, depending
upon your device.
File type Designates
Input Locations within your processor to which the
selected device's data is mapped
Output Where data destined for the selected device resides
in your processor's memory
4. From the appropriate drop list, depending upon what you selected
in the above step, select the appropriate region to which you want
to begin mapping the selected device’s input and/or output data.
5. Enter the appropriate word within the region where the data
begins in the Start Word edit box.
Important: Word 0 is reserved for processor/scanner
specific communication. The software will
automatically allocate this word as a part of its
mapping routine.
6. Click on the radio button next to the desired mapping method.
This mapping method Maps
Node order Your devices according to their node
address (lowest to highest address)
Size order Your devices according to the size of
their I/O data (largest to smallest)
Byte Align All All data on byte boundaries in
incrementing node address order
Word Align All All data on word boundaries in
incrementing node address order
7. To map the selected device’s data, choose Map.


About the Data Table Map The Data Table Map screen facilitates customized data mapping.
You can specify exact memory locations and data sizes (in bits) for
your I/O data communication. In addition, it provides a useful
browsing tool for scan list data table-map viewing.

Using the data table map for 3-18
custom editing
Mapping specific bits to specific device 3-19
memory locations
There are three symbols that may be displayed in the data table map:
This symbol Means

R Reserved locations such as the module status word
Duplicate mapping condition. This will occur if you map more than one bit
X
to the same bit location, mapping one on top of the other.
- Unmapped bit
Input Data Map
Output Data Map
" Apply Segment inserts the values from the Data Entry fields into
your scan list’s data table map.
" Delete Segment removes selected devices from a data table map.
This button deletes a device’s data from the scan list. A device
whose data is not mapped is not scanned. The only exception is in
the case of a strobe-out, which has no map requirement.
" Print to File prints the data table map to a text file using the .mr4
file extension.

Using the Data Table Map for Custom Editing
You can select specific bits of input data and map them to specific
scanner memory locations by following these directions.
1. To edit the data table map, click on the radio button next to
Data Entry.
You enter the Data Table Map screen under browse mode
by default.
2. Select a device to edit from the Device Select drop list.
Whatever device appears in the Device Select field is the device
you are editing.
3. Click on the appropriate radio button in the Data Map field
depending upon whether you are mapping input or output data.
4. Click on the appropriate radio button in the Map Segment field.
You can map input data using up to four map segments.
5. Click on the desired input data’s location in the Map Data To
drop list.
This indicates to the scanner which type of message will arrive –
strobe, poll, change-of-state, or cyclic. This entry must match the
type of communication you chose when defining the device’s
communication characteristics in the Edit I/O Parameters screen.
6. Enter the location of the input data by indicating where in the
DeviceNet message to begin mapping input bits in the Byte and
Bit edit boxes.
You need to indicate the exact byte and bit location.
7. Click on the desired location in your scanner’s memory where
you want to store the input data in the Map Data From drop list.
8. Enter the input data’s mapping location by indicating the word
and bit at which the data begins in your scanner’s memory in the
N* and Bit edit boxes.
9. Enter the size of the input data you are mapping to the location in
the Map Data To field in the No. Bits edit box.
Important: The input value must be equal to or less than the
strobe, poll, change-of-state, or cyclic receive
value entered when defining communication
characteristics in the Edit I/O Parameters screen.
Important: Each scanned device can have as many as 255
bytes of input data; however, you can map only
as many as 128 bytes per map segment. You
must use more than one map segment for a
device with more than 128 bytes of input data.

Mapping Specific Bits to Specific Device Memory Locations
1. To edit the data table map, click on the radio button next to
Data Entry.
Once you've completed the following

procedure, the map segment's data is
displayed in the appropriate position
within this window.
2. Select a device to edit in the Device Select drop list.

Whatever device appears in the Device Select field is the device
you are editing.
3. Click on the radio button in the Data Map field next to output.
Notice the output data map appears in the map tool’s display
window.
4. Click on the appropriate radio button in the Map Segment field.
Important: Each scanned device can have as many as 255
bytes of output data; however, you can map only
as many as 128 bytes per map segment.
Therefore, you must use more than one map
segment for a device with more than 128 bytes
of output data.
5. Click on the desired type of message to put the output data in the
Map Data To drop list.
You must choose in what type of message the output data is sent
to your device.
6. Enter the location of the output data by indicating where in the
DeviceNet message to begin mapping output bits in the Byte and
Bit edit boxes.

You need to indicate the exact byte and bit location.

7. Click on the desired location in your scanner’s memory to
retrieve the output data in the Map Data From drop list.
You can choose a discrete or block transfer location.
Important: If you are mapping from a discrete data table, do
not exceed the discrete I/O capability of your
scanner’s address density (slot-addressing
mode).
8. Enter the output data’s mapping location by indicating the word
and bit at which the data begins in your scanner’s memory in the
N* and Bit edit boxes.
The radix for discrete I/O is octal while the radix for block
transfers is decimal.
9. Enter the size of the output data you are mapping from the
location in the Map Data To field in the No. Bits edit box.
" To view a specific data table word on the bit level, double-click
on the desired word. The data table map display window changes
to view just those bits within the selected word.

About Your Files When you save Module Configuration or Scan List Editor
information to a file, each is given a specific extension.
• MCC data is stored in .sm4 files
• Scan list data is stored in .sl4 files
• Scan list reports are stored in .lr4 files
• Scan list map reports are stored in .mr4 files
• Custom launch data is stored in .clc files
When you access the scanner configuration screens from Project
View, scanner files are stored at the project level.
When you access the scanner configuration screens from Network

Who, you choose where to store the scanner files. This is because
there is no project data attached to Network Who.
What's Next? If you feel ready to proceed with your configuration process, apply
to your system the procedures discussed in chapters 2 and 3. If you
need further information, continue on to the scan list file example in
appendix B.
• Photoelectric sensor scanlist example
• RediSTATION operator interface scanlist example
If You Encounter Error Messages
If you encounter error messages while building your scanlist file,

refer to the troubleshooting table in appendix A.
• Input maps 1-4 errors
• Input message-type errors
• Output maps 1-4 errors
• Output message-type errors
• Mapping and/or auto map errors

Appendix A
Troubleshooting
What's in This Appendix? This appendix lists possible DeviceNetManager software error
messages specific to scan list configuration.
The first column, Message, is further divided into these categories:
Input Maps 1Ć4 Error messages resulting from inputĆdata entries for
one of your input map segments, 1, 2, 3, or 4
Input Message Type Error messages resulting from a I/O type mismatch.
Parameters set in the Edit Device I/O Parameters
screen (strobe, poll, change of state, and/or cyclic) do
not match the Map Data From entry in the Data Table
Map screen
Output Maps 1Ć4 Error messages resulting from outputĆdata entries for
one of your output mapĆsegments, 1, 2, 3, or 4
Output Message Type Error messages resulting from a I/O type mismatch.
Parameters set in the Edit Device I/O Parameters
screen (strobe, poll, change of state, and/or cyclic) do
not match the Map Data To entry in the Data Table
Map screen
Data Mapping Error messages resulting from manual or auto data
maps that cannot be defined under one of the above
troubleshooting categories
Important: The troubleshooting table includes only those errors

detected by DeviceNetManager software while using
the data-mapping screens. This table does not include
general errors particular to DeviceNetManager software
itself, nor does it list any errors that may be displayed in
a number code on the scanner module itself.
For scanner module numeric-coded error messages, please refer to
the 1747-SDN Scanner Module Installation Instructions,
publication 1747-5.8.

A–2 Troubleshooting
Message Description Recommendation

Input Maps 1Ć4
Number of strobe bits exceeds strobe Rx size The no. bit value exceeds the The no. bits (number of bits) indicated in the
strobe Rx size value. input dataĆmap must be equal to or less than the
strobe Rx size. Please note that no. bits indicates
bits while the strobe Rx size indicates bytes.
Number of poll bits exceeds poll Rx size The no. bit value exceeds the poll The no. bits (number of bits) indicated in the
Rx size value. input dataĆmap must be equal to or less than the
poll Rx size. Please note that the no. bits
indicates bits while the poll Rx size
indicates bytes.
Data table bits mapped to module status register Input bits have been mapped to Reevaluate where you would like to map your
an area in the input data table input bits. Enter the correct values for word and
that is reserved for the module bit in the input dataĆmap's Map Data To.
status word. The first word of an
input data table is always
reserved for module status.
Data bits mapped beyond end of the M1 table Input bits have been mapped Reevaluate where you would like to map your
outside the boundaries of input bits. Enter the correct values in for word
the M1 table. and bit in the output map's Map Data To.
Input Message Type
Scan type prohibits poll bit assignment The type of I/O communication Determine what mode of communication you
Scan type prohibits strobe bit assignment indicated does not match the wish to use: strobe, poll, change of state, and/or
Scan type prohibits strobe and poll bit assignment input data map's Map Data From. cyclic. Be sure that I/O values are entered for the
appropriate communication mode.
Output Maps 1Ć4
Number of strobe bits greater than 1 Each device has one bit of Reenter the correct value for no. bits (number
information in the output strobe of bits). This must be either one or zero.
message; therefore, it is not
possible to map more than one
bit of output data per device into
the strobe message.
Strobe bit assignment inconsistent with device The bit mapping is incorrect for Match the device's node address to the proper
node address the designated device. position within the strobe message. For example:
node address 1 would be mapped to bit 1 of byte
0. See page C-5 for more information on
mapping data for strobed devices in your
scan list.
Number of poll bits exceeds poll Tx size The value entered for bit exceeds The no. bits (number of bits) indicated in the
the value entered for poll Tx size. output dataĆmap must be equal to or less than
the poll Tx size. Please note that the no. bits
indicates bits while the poll Tx size
indicates bytes.
Data table bits mapped to module command register Output bits have been mapped Reevaluate from where you would like to map
from an area in the output data your output bits. Enter the correct values for word
table that is reserved for the and bit in the output map's Map Data From.
module command word. The first
word of an output data table is
always reserved for
module status.
Data bits mapped beyond end of the M0 table Output bits have been mapped Reevaluate from where you would like to map
from outside the boundaries of your output bits. Enter the correct values for word
the M0 table. and bit in the output map's Map Data From.

Troubleshooting A–3
Message Description Recommendation

Output Message Type
Scan type prohibits poll bit assignment The type of I/O communication Determine what mode of communication you
Scan type prohibits strobe bit assignment indicated does not match the wish to use: strobe, poll change of state, and/or
Scan type prohibits strobe, poll, change of state, output data Map's Map Data To. cyclic. Be sure that the correct I/O values are
or cyclic bit assignment entered for the appropriate communication
mode.
Data Mapping
No output strobe, poll, change state, and cyclic data The scanner has been instructed Type in the appropriate value in the output data
size specified for currentscan type to strobe, poll, change of state, or map's no. of bits.
cyclic a message but has not
been allotted any bits to carry out
the command.
Poll Tx size: current scan type prohibits poll A poll bit has been assigned Set the mode of communication to poll in Edit
bit assignment without the communication type Device I/O Parameters screen.
set as poll.
Input source byte: bit offset is greater than 7 The source bit value is greater Correctly identify the byte and bit offset for the
than seven. Eight bits comprise data element desired. Reenter the corrected
one byte. When counting the values for byte and bit in the input dataĆmap's
number bits in a byte, the first bit Map Data From.
begins with zero. Any value
greater than seven indicates
more than eight bits and therefore
more than one byte.
Output dest byte: bit offset is greater than 7 The destination bit value is Correctly identify the byte and bit offset for the
greater than seven. Eight bits data element desired. Reenter the corrected
comprise one byte. When values for byte and bit in the output data map's
counting the number bits in a Map Data To.
byte, the first bit begins with zero.
Any value greater than seven
indicates more than eight bits and
therefore more than one byte.

Appendix B
Scan List Example
What's in This Appendix? The following pages combine the data mapping examples from
chapter 2 with DeviceNetManager software.

Understanding a scan list example B-2
Photoelectric sensor input mapping B-3
scheme example
Node address 21 input data B-4
RediSTATION operator interface B-6
input mapping scheme example
RediSTATION operator interface B-7
output mapping scheme example
Node address 50 input and output data B-8
FLEX I/O module input mapping B-9
scheme example
FLEX I/O module output mapping B-10
scheme example
Node address 22 input and output data B-11

B–2 Scan List Example
Understanding a This example illustrates how each Scan List Configuration screen
Scan List Example appears when the mapping example’s network is configured.
Series 9000 photoelectric sensor RediSTATION operator interface

Two input bits from each photoelectric Two input bits from each RediSTATION
sensor will be mapped. One status bit and indicator light operator interface will be mapped.
one data bit. The data bit is needed One bit for the green start button and
quickly; therefore, this input data will be green start button one bit for the red stop button.
mapped to the scanner's discrete input One output bit for each operator interface
data table. red stop button will also be mapped: one bit for each
operator interface's indicator
light (on/off).
The photoelectric sensor produces The RediSTATION
one byte of input data and consumes operator interface produces bit for
one bit of output data. one byte of input data and green button
status consumes one byte of
bit output data. input bit for
1 byte red button
1 byte data
bit
bit for
output 1 byte
indicator light
RediSTATION operator interfaces

PC containing SLC
programming software and photoelectric sensors
DeviceNetManager software
ControlNet network or
DH+ network for
6200 software 1784ĆPCD
PCMCIA Node 1 Node 2 Node 5 Node 6
card
DeviceNet network
Chassis containing
a SLCĆ500 processor Node 22 Node 3 Node 7 Node 8 Node 4
and a 1747ĆSDN
scanner
1747ĆSDN scanner module

(in second slot of chassis) FLEX I/Ot rack
Node 0
photoelectric photoelectric
sensor RediSTATION operator interfaces sensor

Scan List Example B–3
host computer with SLC

programming software
ControlNett network
1747ĆSDN scanner
1784ĆPCD
SLCĆ500 processor PCMCIA computer with
card DeviceNet Manager
software
DeviceNet network
FLEX I/Ot rack

DeviceNet devices
RediSTATIONt
operator interface
1305
drive
Photoelectric Sensor Input Mapping Scheme Example

photoelectric sensor node address 1 photoelectric sensor node address 2
1 The status and data bits
from each photoelectric
sensor are mapped into 1 byte 1S 1D 1 byte 3S 3D
the scanner's discrete input
Photoelectric Sensor Input Bytes
data table.
2 The discrete input data table photoelectric sensor node address 3 photoelectric sensor node address 4
is then transferred via DIO to
the SLCĆ500 processor's 1 byte 2S 2D 1 byte 4S 4D
input image table.
1
SLCĆ500 Processor
Input Image Table
(6200 Software View)
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
I:000 0000 0000 0000 0000 1747ĆSDN Scanner Discrete Input Data Table
slot 0
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
I:001 0000 0000 0000 0000
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
I:002 0000 0000 0000 0000 2 4S 4D 3S 3D 2S 2D 1S 1D reserved word 0
slot 1
I:003 0000 0000 0000 0000
I:004 0000 0000 0000 0000
slot 2
I:005 0000 0000 0000 0000

Node Address 21 Input Data

Series 9000 photoelectric sensor
photoelectric sensor input byte
1 byte 21S 21D
The photoelectric sensor at node address 21 is

a strobed device that produces 1 byte of
input data.
Remember that this node must be enabled in
21S 21D the scanlist before it may participate in I/O
communication with the scanner.
In map segment 1, input data is taken from the
strobe response starting at byte 0, bit 0.
This input data is mapped to the scanner's
discrete input data table starting at word 0,
bit 10. Remember that discrete mapping's radix
is octal.
The number of bits mapped is 2 (1 data bit
and 1 status bit).

photoĆeye input byte
1 byte 22S 22D
The photoelectric sensor at node address 22 is a

strobed device that produces 1 byte of input data.
the scanlist before it may participate in I/O
22S 22D
strobe response starting at byte 0, bit 0.
discrete input data table starting at word 0,
bit 12. Remember that discrete mapping's radix
is octal.
and 1 status bit).


1 byte 23S 23D
The photoelectric sensor at node address 23

is a strobed device that produces 1 byte of
input data.
In map segment 1, input data is taken from
the strobe response starting at byte 0, bit 0.
discrete input data table starting at word 0, bit
14. Remember that discrete mapping's radix
is octal.
and 1 status bit).

1 byte 25S 25D
The photoelectric sensor at node address 25

is a strobed device that produces 1 byte of
input data.
In map segment 1, input data is taken from
the strobe response starting at byte 0, bit 0.
discrete input data table starting at word 0, bit
16. Remember that discrete mapping's radix
is octal.
and 1 status bit).

RediSTATION Operator Interface Input Mapping Scheme Example
What's Happening? RediSTATION Operator Interface Input Bytes
1 The bits for each start/stop station node address 5 start/stop station node address 6
RediSTATION operator
interface's red and green 1 byte 5G 5R 1 byte 6G 6R
buttons are mapped into the
scanner's M1 data table.
2 The M1 data table is then start/stop station node address 7 start/stop station node address 8
transferred via BT to the
SLCĆ500 processor's input 1 byte 7G 7R 1 byte 8G 8R
data file.
makes the data available for the 1
processor to read. The scanner
ÈÈ
ÈÈ
ÈÈ
ÈÈÈ
ÈÈÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
È
the processor. 1747ĆSDN Scanner M1 File Transfer Data Table
ÈÈ
ÈÈ
ÈÈ
ÈÈÈ
ÈÈÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
È
ÈÈ
ÈÈ
ÈÈ
ÈÈÈ
ÈÈÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
È
reserved for module status word word 0
SLCĆ500 Processor
Input Data File 5G 5R word 1
N7:00 0000 0000 0000 0000 6G 6R word 2
N7:01 0000 0000 0000 0000
N7:02 0000 0000 0000 0000 7G 7R
2 word 3
N7:03 0000 0000 0000 0000
N7:04 0000 0000 0000 0000 8G 8R word 4
N7:05 0000 0000 0000 0000
N7:61 0000 0000 0000 0000

word 61

RediSTATION Operator Interface Output Mapping

Scheme Example
1 The station indicatorĆlight bit RediSTATION Operator Interface Output Bytes

for each RediSTATION
operator interface is RediSTATION node address 5 RediSTATION node address 6
mapped to the scanner's
discrete output data table. 1 byte 5L 1 byte 6L
2 The discrete output data table
is then sent to the operator
interfaces via four poll RediSTATION node address 7 RediSTATION node address 8
messages, from which each
operator interface receives its 2
1 byte 7L 1 byte 8L
indicatorĆlight bit.
SLCĆ500 Processor
Output Image Table
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
È
ÈÈ
1747ĆSDN Scanner Discrete Output Data Table
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
È
ÈÈ
O:000 0000 0000 0000 0000
slot 0
O:001 0000 0000 0000 0000
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
ÈÈ
È
ÈÈ
8L 7L 6L 5L reserved word 0
O:002 0000 0000 0000 0000
slot 1 1
O:003 0000 0000 0000 0000 word 1
O:004 0000 0000 0000 0000
slot 2
O:005 0000 0000 0000 0000
Example: RediSTATION #5's indicatorĆlight

bit is taken from address 0:002/10 (octal) in
the SLCĆ500 processor's output image table.

Node Address 50 Input and Output Data

RediSTATION operator interface
RediSTATION input byte

1 byte
The RediSTATION operator interface at node

address 50 is a polled device that produces 1
byte of input data.
poll response starting at byte 0, bit 0.
input data table in the BT 62 area starting at
word 1, bit 8. Remember that BT mapping's raĆ
dix is decimal.
The number of bits mapped is 8.
RediSTATION operator interface
Poll message
for node address 50
50L
The RediSTATION operator interface at node

address 50 is a polled device that receives a 1
byte poll message containing its output data.
50L the scanlist before it may participate in I/O
In map segment 1, output data is mapped to a 1
byte poll message starting at byte 0, bit 0.
This output data is mapped from the scanner's
discrete output data table starting at word 0, bit 10.
Remember that a discrete transfer's radix is octal.
The number of bits mapped is 1. Each
RediSTATION operator interface receives a bit for
its indicator light which is either on or off.

FLEX I/O Module Input Mapping Scheme Example

FLEX I/O Module Input Bytes The FLEX I/O module produces 6 bytes
What's Happening? of input data and consumes 4 bytes of
output data.
1 The bits for each
FLEX I/O module are 1794ĆADN 1794ĆIB16 1794ĆOB16
mapped into the adapter module input module output module
scanner's 61Ćword
M1 data table.
2 The M1 data table is then
transferred via BT to the FLEX I/O module node address 22
SLCĆ500 processor's input
1 byte 1 byte 1 byte 1 byte 1 byte 1 byte
data file.
makes the data available for the Module Status Input Bits from 1794ĆIB16 Ignore
processor to read. The scanner A B C
the processor.
We assume the SLCĆ500 processor is programmed to perform a M1 File Transfer of
61 words to the scanner's rack group slot using data table N9:0 - N9:60.
Input Map Segment
1747ĆSDN Scanner M1 File Transfer 61ĆWord Input Data Table
B A word 0
SLCĆ500 Processor
Input Data File C word 1
N9:00 0000 0000 0000 0000
M1 61 words word 2
N9:01 0000 0000 0000 0000
N9:02 0000 0000 0000 0000
2 word 3
N9:03 0000 0000 0000 0000
N9:04 0000 0000 0000 0000
word 4
N9:05 0000 0000 0000 0000
N9:60 0000 0000 0000 0000

word 60

FLEX I/O Module Output Mapping Scheme Example

FLEX I/O Module Output Bytes
1 I/O data in the SLC processor
is 61Ćword BT written to the
scanner's BT 61Ćword 1794ĆADN 1794ĆIB16 1794ĆOB16
output data table. adapter module input module output module
2 The FLEX I/O output message

is mapped from the 61Ćword 1 byte 1 byte 1 byte 1 byte
output data table area. A
single bit change detected at
this point causes a new output D = data sent to E = data mapped to
message to be sent to the 1794ĆIB16 data IB16 1794ĆOB16 data OB16
FLEX I/O module.
We assume the SLCĆ500 processor is programmed to perform a M1 File Transfer of
61 words to the scanner's rack group slot using data table N10:0 - N10:60 outputs.
Output Map Segment

with change of state detection
2
SLCĆ500 Processor
Output Data File
(6200 Software View) 1747ĆSDN Scanner M0 File Transfer 61ĆWord Output Data Table
BTW 61 words
N10:00 0000 0000 0000 0000 E D word 0
N10:01 0000 0000 0000 0000 output word input word
N10:02 0000 0000 0000 0000 1
word 1
N10:03 0000 0000 0000 0000
N10:04 0000 0000 0000 0000 word 2
N10:05 0000 0000 0000 0000
word 3
word 4
N10:60 0000 0000 0000 0000
word 60

Node Address 22 Input and Output Data

FLEX I/O module FLEX I/O input bytes
1 byte 1 byte 1 byte 1 byte 1 byte 1 byte
The FLEX I/O module at node address 22 is a

change of state device that produces 6 bytes of
input data.
The input bits are mapped to the scanlist before it may participate in I/O
the BT input data table in the communication with the scanner.
BT 61 area starting at word
1, bit 8. In map segment 1, input data is taken from the
change of state response starting at byte 0,
bit 0.
input data table in the BT 61 area starting at
word 5, bit 0. Remember that BT mapping's raĆ
dix is decimal.
61 The number of bits mapped is 16.
FLEX I/O module Change of state message

for node address 9
1 byte 1 byte 1 byte 1 byte
The FLEX I/O module at node address 9 is a

change of state device that receives 4 bytes of a
change of state message containing its
output data.
In map segment 1, output data is mapped to a 1
byte poll message starting at byte 0, bit 0.
This output data is mapped from the scanner's
discrete output data table starting at word 1, bit 0.
Remember that a discrete transfer's radix is octal.
The number of bits mapped is 16.
61

Appendix C
Data Map Example
What's in This Appendix? This appendix illustrates a basic mapping example that connects a
DeviceNet network to 62 simple sensor-type devices. Each device
sends one data byte that contains one data bit and one status bit.
These are given in response to a strobe message.

Example input mapping scheme C-1
Example characteristics C-1
Example framework C-2
Example output mapping scheme C-4
Example characteristics C-4
Example framework C-4
Example Input This example’s input mapping scheme is a simplified and fixed map
Mapping Scheme of discrete input data and status bits for DeviceNet devices. It is
mapped to discrete inputs and the device input data table.
Example Characteristics
• strobe is used to query DeviceNet devices

• poll is disabled
• the input data bit is fixed and occupies the lowest-order bit in the
lowest-order byte of the strobe (bit #1)
• one bit of status data is accepted from each node responding to
the strobe
• the status data bit is fixed and occupies the next lowest-order bit
in the next lowest-order byte (after the input data bit) of the
strobe (bit #2)
• input and status data bits accepted from each node are mapped to
the scanner’s discrete input data table
• input and status data bits accepted from each node are fixed and
predefined

C–2 Data Map Example
Example Framework
This example adheres to the following structure:

• there cannot be any 1771-SDN scanners or other 1747-SDNs on
that network
• DeviceNet devices may reside only at nodes 1-62
• address 63 is reserved for DeviceNetManager software
• address 0 must be used for the scanner
• the first word in the device input data table contains the module
status word (this is applicable under any mapping scheme)
• input data and status bits received from nodes 1-62 are mapped to
the scanner’s discrete input data table

Data Map Example C–3
The following illustrates an input-data mapping scheme example for

the 1747-SDN scanner. Input bits are mapped from a device’s
message, to the scanner’s input data table, and to the processor’s
input image table.
The status and data bits for each scanned device are mapped to the
scanner's discrete input data table. Data bits are mapped in the first DeviceNet Message from
four words while status bits are mapped in the next four words of the Node # 11
table. The bit numbering for device data bits begins with 0. This
numbering starts over in word 5 for device status bits. This feature 1 byte S
makes it possible to directly correlate a device's MAC ID with the
placement of its bits in the data table. For example, the data bit for D
node #11 is mapped to bit 11, word 1 in the data table. Its status bit is
mapped to bit 11, word 5 of the data table. 1747ĆSDN Scanner Discrete
Input Data Table
The processor reads the scanner's data table to transfer its contents 15 0 word 0
to the SLC processor input image table.
SLC Processor Input Image Table 15 11 0 word 1
word 0 31 16 word 2
Status
47 32 word 3
63 48 word 4
words 1Ć31 DeviceNet Input Data (31 words)

15 11 0 word 5
31 16 word 6
SLC Processor M1 File 47 32 word 7
63 48 word 8
bit number
words 0Ć149 DeviceNet Input Data (211 words)
In this example, nothing is mapped to the DeviceNet input data

area of the processor's M1 file. All input data is mapped to the
words 150Ć210 Reserved (61 words) processor's input image table via the scanner's discrete input
data table.
word 211 Scan Counter (1 word)
words 212Ć215 Device Active Table (4 words)
words 216Ć219 Device Failure Table (4 words)
words 220Ć223 Auto Verify Table (4 words)
words 224Ć255 Client Server Table (32 words)

C–4 Data Map Example
Example Output This example’s output mapping scheme is a simplified and fixed map
Mapping Scheme of the discrete outputs and data from the device output data table to
DeviceNet devices.
Devices present in the default database are strobed only; therefore,

the output data-map bits are mapped into each network’s strobe
message. If the discrete table is available, it serves as a source for the
strobe bits; otherwise, the source is found in M1/M0 file
transfer locations.
Example Characteristics
• strobe is used to send output to the DeviceNet devices

• poll is disabled
• one output data bit each is sent to nodes 1-62
• the output data bits are embedded in the 8 byte (64 bit) data
portion of the DeviceNet strobe message
• the output bit string source within the strobe message is divided
across the discrete outputs in the scanner’s discrete output data
table
Example Framework
This example adheres to the following structure:

• when a 1747-SDN is running this configuration, there cannot be
any other 1747-SDN or 1771-SDN on that network
• DeviceNet devices may reside only at nodes 1-62
• address 63 is reserved for DeviceNetManager software
• address 0 must be used for the scanner
• the first word in the device output-image data table always
contains the module command word (this is applicable under any
mapping scheme)
• output bits received from processor for nodes 1-62 are mapped to
the scanner’s discrete output data table

Data Map Example C–5
The following illustrates an output-data mapping scheme example

for the 1747-SDN scanner. Output bits are mapped from the
processor’s output image table, to the scanner’s output data table,
and to each device via strobe message.
The processor writes output data for each scanned device in the scanner's
discrete output data table. The scanner then maps each bit into a strobe 1747ĆSDN Output Strobe Message
message that is sent to all scanned devices. The bit number, where a
The strobe message contains one bit for
particular device's data is mapped, directly corresponds to that device's
each scanned device on the network.
MAC ID. This is true for mapping into the scanner's data table as well as
the scanner's strobe message. For example, node # 11's output bit is 63 11 0
mapped in bit number 11 of the scanner's output data table. In addition,
this same output bit is mapped from bit 11 of the data table to bit number
11 in the strobe message.
1747ĆSDN Scanner Discrete

SLC Processor Output Image Table Output Data Table
15 0 word 0
word 0 Command (1 word)
15 11 0 word 1
31 16 word 2
words 1Ć31 Device Output Data (31 words)
47 32 word 3
63 48 word 4
SLC Processor M0 File bit number
words 0Ć223 DeviceNet Output Data (224 words)
In this example, nothing is mapped from the DeviceNet output

data area of the processor's M0 file. All output data is mapped
from the processor's output image table to the scanner's
discrete input data table.
words 224Ć255 Client Server Table (32 words)

C–8 Index
Pub. Name DeviceNet Scanner Configuration Manual
Cat. No. 1747ĆSDN Pub. No. 1747Ć6.5.2 Pub. Date May 1997 Part No. 955128Ć25
Check Problem(s) Type: Describe Problem(s): Internal Use Only
Technical Accuracy text illustration
Completeness procedure/step illustration definition info in manual

What information is missing? example guideline feature (accessibility)
explanation other info not in
manual
Clarity
What is unclear?
Sequence
What is not in the right order?
Other Comments
Use back for more comments.
Your Name Location/Phone
Return to: Technical Communication, AllenĆBradley Co., 1 AllenĆBradley Drive, Mayfield Hts., OH 44124 Phone: (216)646Ć3166
FAX: (216)646Ć4320
Publication ICCGĆ5.21ĆAugust 1995 PN 955107Ć82

PLEASE FASTEN HERE (DO NOT STAPLE)
Other Comments
PLEASE REMOVE
PLEASE FOLD HERE
NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
Technical Communication
1 ALLEN BRADLEY DR
MAYFIELD HEIGHTS OH 44124-9705
Index
Symbols communicating with your SLCĆprocessor

discrete I/O (DIO), 1-2
.clc, 3-2, 3-21 M1/M0 file transfers, 1-2
.lr4, 3-2, 3-21 communication requirements, 2-1
.mr4, 3-2, 3-17, 3-21 configuration, 1-2
.sl4, 3-2, 3-21 beginning, 3-1
.sm4, 3-2, 3-5, 3-9, 3-21 data, 1-2
devices in the scan list, 3-13
example, 1-2
Numbers offline, 3-2
online, 3-2
1747ĆSDN, data exchange, 1-1 online/offline, 3-2
scanner, 3-2
A conventions, P-2
custom editing, datatable map, 3-18
access, 3-5
method, 3-5 cyclic, 1-4, 1-5
definition, P-3
active in scan list, 3-10 message, definition, 1-3
Add Devices to Scan List screen, 3-12 messaging, 3-14, 3-15
apply, 3-17
assign names from project, 3-6 D
auto map, 3-15
screen, 1-7 data entry mode, 3-18
auto verify table, C-3 data exchange, 1-1

configuration data, 1-2
device I/O data, 1-2
B status information, 1-2
data map example
background poll ratio, 3-4
auto verify table, C-3
definition, 1-6
client server transaction tables, C-5
bandwidth, 2-1 client/server transaction tables, C-3
block transfer, 3-16 command word, C-5
device active table, C-3
browse mode, 3-18
device failure table, C-3
byte device output data, C-5
align all, 3-16 DeviceNet input data, C-3
and bit, 3-18 DeviceNet output data, C-5
input data mapping scheme, C-3
input mapping scheme, C-1
C output data mapping scheme, C-5
change of state, 1-4, 1-5 scan counter, C-3
definition, P-3 status word, C-3
message, definition, 1-3 data mapping, 3-1
messaging, 3-14, 3-15, B-11 definition, A-1
client/server transaction tables, 1-5, C-3, error messages, A-3
C-5 example, 2-2
characteristics, 2-2
colors, surrounding a device, 3-3
input data for DIO, 2-3
command word, C-5
I–2 Index
input data for M1 read, 2-4 edit scan list, 3-8

output data for DIO, 2-5 EDS, definition, P-3
datatable map electronic key
apply, 3-17 catalog number, 3-10
browse mode, 3-18 device type, 3-10
byte and bit, 3-18 vendor, 3-10
custom editing, 3-18
data entry mode, 3-18 engineering services, P-4
definition, 3-17 error messages
delete, 3-17 data mapping, A-3
device select, 3-18 input maps, A-2
display symbols (R,X,-), 3-17 input message type, A-2
input data map, 3-17 output maps, A-2
map data to, 3-18 output message type, A-3
map segment, 3-18 exchange services, P-4
no. bits, 3-18
expansion, 2-1
output data map, 3-17
print to file, 3-17 extensions
screen, 1-7, 3-17 (.sm4, .sl4, .lr4, .mr4, .clc), 3-2
word and bit, 3-18 (.sm7, .sl7, .lr7, .mr7), 3-21
delete, 3-17
DeviceNet input data, C-3 F
DeviceNet output data, C-5 field services, P-4
DeviceNetManager software, 1-6 file extensions
configuring with, 3-1 (.sm4, .sl4, .lr4, .mr4, .clc), 3-2
devices (.sm7, .sl7, .lr7, .mr7), 3-21
active table, 1-5, C-3
Add Devices to Scan List screen, 3-12
adding to scan list, scan list editor H
screen, 3-11
configuration, 1-6 heartbeat rate, definition, P-3
configuring in scan list, 3-13
failure table, 1-5, C-3
I/O data, 1-2
I
input data table, 1-5 I/O
output data, C-5 comms, 3-4
output data table, 1-5 enable, 3-4
removing from scan list, 3-9 communication, definition, 1-6
select, 3-18 definition, P-3
surrounded in color, 3-3 importance, 2-1
type, 3-10 size, 2-1
dip switches, 1-6 transfers, 2-1
discrete I/O (DIO), 1-2, 1-4, 1-5, 2-5 input
definition, 1-2 block Xfer, 3-16
data, 1-5
display filters, 3-10
definition, P-3, 1-3
screen, 1-7
data map, 3-17
dual mode, definition, P-3 image table, 2-3
mapping scheme, C-1
characteristics, C-1
E FLEX I/O module, B-9
edit device I/O parameters, 1-6, 3-18 framework, C-2
screen, 1-7, 3-13, 3-14 photoelectric sensor, B-3
edit Rx/Tx size, 3-14, 3-15
Index I–3
RediSTATION operator interface , module configuration (MC), screen, 1-7,

B-6 3-2, 3-4
maps module settings, 3-4
definition, A-1
error messages, A-2
message type N
definition, A-1
error messages, A-2 names, assigning from project, 3-6
input , data file, 2-4 network
definition, P-3
input data, 1-5
who, 3-3
interscan delay, 3-4 screen, 1-7
definition, 1-6
no. bits, 3-18
node
L definition, P-3
order, 3-16
load from
file, 3-5, 3-9
SDN, 3-5, 3-6, 3-9, 3-11, 3-14, O
3-15
offline, definition, P-3
online, definition, P-3
M
output
M0 file transfer, definition, 1-4 block Xfer, 3-16
M1 file transfer data, 1-4
definition, 1-4 definition, P-3, 1-3
read, 2-4 data map, 3-17
image table, 2-5
M1/M0 file transfers, 1-2, 1-5 maps
definition, 1-2 definition, A-1
MAC ID, definition, P-3 error messages, A-2
map message type
data to, 3-18 definition, A-1
segment, 3-18 error messages, A-3
definition, 1-3 output , data, 1-5
mapping output data, 1-5
bits to memory locations, 3-19 output mapping scheme, C-4
method characteristics, C-4
byte align all, 3-16 FLEX I/O module, B-10
node order, 3-16 framework, C-4
size order, 3-16 RediSTATION operator interface, B-7
word align all, 3-16
scheme, 3-1
memory, 2-1 P
messaging pc, definition, P-3
change of state, B-11
planning
change-of-state/cyclic, 3-14, 3-15
configuration process, 2-1
frequency, 2-1
steps, 2-1
polled, 3-14, 3-15
strobed, 3-14, 3-15 poll, 1-4, 1-5
definition, P-3
module configuration
device, 2-2
definition, 3-3
screen, 3-7
I–4 Index
message, 3-14, 3-15 scanner

definition, 1-3 configuration table, 1-5
print to file, 3-17 definition, 1-5
data tables, definition, 1-5
processor, definitioin, P-3 definition, P-3
project view, 3-3 functions, 1-2
screen, 1-7 select defaults, module, 3-5, 3-10
publications, related, P-2 services
engineering and field, P-4
repair and exchange, P-4
R support, P-4
R, 3-17 size order, 3-16
record, definition, P-3 slave mode, 3-8
related publications, P-2 definition, P-3
removing devices from scan list, 3-9 SLC processor, data exchange, 1-1
repair services, P-4 status information, 1-2
Rx, 3-14, 3-15 status word, C-3
definition, P-3 strobe, 1-4, 1-5
definition, P-3
message, 3-14, 3-15
S definition, 1-3
save to, SDN, 3-6, 3-11, 3-14, 3-15 support
saving files, 3-21 services, P-4
technical, P-4
scan counter, C-3
scan list
Add Devices to Scan List screen, 3-12 T
adding devices to, scan list editor screen,
3-11 technical
auto map, 3-15 support, P-4
configuring a device, 3-13 training, P-4
display filters, 3-9 tips, 3-3, 3-8, 3-13, 3-14, 3-15,
removing devices, 3-9 3-17, 3-20
table, 1-5 training, technical, P-4
definition, 1-5
troubleshooting, A-1
viewing device information, 3-9
Tx, 3-14, 3-15
scan list editor (SLE)
definition, P-3
accessing, 3-7
Network Who, 3-7
Project view, 3-7
U
definition, 3-8
screen, 1-6, 1-7, 3-2, 3-8 unmap, 3-16
scan list example, B-1
input data
node 1, B-4 V
node 2 , B-4 vendor, 3-10
node 3, B-5
node 4, B-5
input/output data W
node 22, B-11
node 5, B-8 word
understanding, B-2 align all, 3-16
Index I–5
and bit, 3-18
X
X, 3-17
AllenĆBradley, a Rockwell Automation Business, has been helping its customers improve proĆ
ductivity and quality for more than 90 years. We design, manufacture and support a broad range
of automation products worldwide. They include logic processors, power and motion control
devices, operator interfaces, sensors and a variety of software. Rockwell is one of the world's
leading technology companies.
Worldwide representation.
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 • Ireland • Israel • Italy
• Jamaica • Japan • Jordan • Korea • Kuwait • Lebanon • Malaysia • Mexico • Netherlands • New Zealand • Norway • Pakistan • Peru • Philippines • Poland • Portugal •
Puerto Rico • Qatar • Romania • Russia-CIS • Saudi Arabia • Singapore • Slovakia • Slovenia • South Africa, Republic • Spain • Sweden • Switzerland • Taiwan • Thailand •
Turkey • United Arab Emirates • United Kingdom • United States • Uruguay • Venezuela • Yugoslavia
AllenĆBradley Headquarters, 1201 South Second Street, Milwaukee, WI 53204 USA, Tel: (1) 414 382Ć2000 Fax: (1) 414 382Ć4444
Publication 1747Ć6.5.2 - May 1997 PN 955128Ć25

Supersedes Publication 1747Ć6.5.2- September 1996 Copyright 1997 AllenĆBradley Company, Inc. Printed in USA

Configuration Manual: Allenćbradley

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuration Manual: Allenćbradley

Uploaded by

Copyright:

Available Formats

AllenĆBradley

The illustrations, charts, sample programs and layout examples

Allen-Bradley publication SGI-1.1, “Safety Guidelines For The

Reproduction of the contents of this copyrighted publication, in

Throughout this manual we make notes to alert you to possible

ATTENTION: Identifies information about practices

Attention helps you:

Important: Identifies information that is especially important for

Change-of-state messaging allows devices supporting

Cyclic messaging allows devices supporting cyclic to be configured

The graphical screens in DeviceNetManager software, version

For more information on See page

Publication 1747Ć6.5.2 - May 1997

Important User Information . . . . . . . . . . . . . . . . . . . . 1

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . soc-i

About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Planning Your Configuration . . . . . . . . . . . . . . . . . . . 2-1

Part III - RediSTATION Operator Interface Mapping Output

Configuring Through DeviceNetManager Software . . 3-1

Scan List Example . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

RediSTATION Operator Interface Input Mapping

Data Map Example . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

About This Manual

Audience We assume that you:

Publication 1747Ć6.5.2 - May 1997

Conventions The following conventions appear throughout this manual to guide

Screen captures are pictures of the software's actual screens.

Step numbers appear on the screen captures by the

The MORE" icon is placed beside any paragraph that references

The screenĆsummary arrow points to a table that summarizes

The optionalĆstep arrow points to a step that is not required for

Related Publications Title Publication Number

Publication 1747Ć6.5.2 - May 1997

Terminology This term Means

Publication 1747Ć6.5.2 - May 1997

Support Services At Allen-Bradley, customer service means experienced

Engineering and Field Services

• application engineering assistance

• lecture and lab courses

Repair and Exchange Services

• your only “authorized” source

Publication 1747Ć6.5.2 - May 1997

For information on See page

Publication 1747Ć6.5.2 - May 1997

Flex I/Ot rack

Publication 1747Ć6.5.2 - May 1997

Communicating with Your Devices

Publication 1747Ć6.5.2 - May 1997

Communicating with Your SLC 500 Processor

Discrete Output Image

X Discrete Internal Output

Publication 1747Ć6.5.2 - May 1997

Scanner Configuration Table (SCT)

The SCT controls basic information your scanner needs to function

• if it can transmit and receive input and output data

Scan List Table (SLT)

• which devices to scan (node addresses)

Publication 1747Ć6.5.2 - May 1997

DeviceNetManager Software DeviceNetManager software configures the scanner’s data tables.

I/O communication User Data in this table DeviceNetManager See page

Publication 1747Ć6.5.2 - May 1997

1747ĆSDN Configuration ScreenĆMap

The MORE" icon is placed beside any paragraph that references