Rockwell SoniCrafter 1771-SDN User Manual
PLC-5 DeviceNet
Scanner Module
1771-SDN
User 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 purposes of example. Since there are
many variables and requirements associated with any particular
installation, Allen-Bradley does not assume responsibility or liability (to
include intellectual property liability) for actual use based upon the
examples shown in this publication.
Allen-Bradley publication SGI-1.1, Safety Guidelines for the Application,
Installation and Maintenance of Solid-State Control (available from your
local Allen-Bradley office), describes some important differences between
solid-state equipment and electromechanical devices that should be taken
into consideration when applying products such as those described in this
publication.
Reproduction of the contents of this copyrighted publication, in whole or
part, without written permission of Rockwell Automation, is prohibited.
Throughout this manual we use notes to make you aware of safety
considerations:
ATTENTION
Identifies information about practices or
circumstances that can lead to personal injury or
death, property damage or economic loss
!
Attention statements help you to:
• identify a hazard
• avoid a hazard
• recognize the consequences
IMPORTANT
Allen-Bradley, Data Highway Plus, and PLC-5 are trademarks of Rockwell Automation.
ControlNet is a trademark of ControlNet International, Ltd.
DeviceNet is a trademark of Open DeviceNet Vendor Association (ODVA), Inc.
Ethernet is a trademark of Digital Equipment Corporation, Intel, and Xerox Corporation.
RSLinx, RSLogix 5, and RSNetWorx are trademarks of Rockwell Software.
Windows 95/98 and Windows NT are trademarks of Microsoft Corporation.
Identifies information that is critical for successful
application and understanding of the product.
European Communities (EC) Directive Compliance
If this product has the CE mark it is approved for installation within
the European Union and EEA regions. It has been designed and tested
to meet the following directives.
EMC Directive
This product is tested to meet the Council Directive 89/336/EC
Electromagnetic Compatibility (EMC) by applying the following
standards, in whole or in part, documented in a technical construction
file:
EN 50081-2 EMC — Generic Emission Standard, Part 2 —
•
Industrial Environment
EN 50082-2 EMC — Generic Immunity Standard, Part 2 —
•
Industrial Environment
This product is intended for use in an industrial environment.
Low Voltage Directive
This product is tested to meet Council Directive 73/23/EEC Low
Voltage, by applying the safety requirements of EN 61131-2
Programmable Controllers, Part 2 - Equipment Requirements and
Tests. For specific information required by EN 61131-2, see the
appropriate sections in this publication, as well as the Allen-Bradley
publication Industrial Automation Wiring and Grounding Guidelines
For Noise Immunity, publication 1770-4.1.
This equipment is classified as open equipment and must be mounted
in an enclosure during operation to provide safety protection.
About This User Manual
Preface
Introduction
This user manual is designed to provide you enough information to
get a small example application up and running. Use this manual if
™
you are knowledgeable about DeviceNet
may not have used the products in conjunction. The information
provided is a base; modify or expand the examples to suit your
particular needs.
The manual contains instructions on configuring a DeviceNet network
using RSLinx and RSNetWorx for DeviceNet software. It also describes
how to use the PLC-5 pass-through feature to communicate with the
DeviceNet network for adjustment and tuning of network devices via
other networks, including:
ControlNet
•
Ethernet
•
Data Highway Plus (DH+)
•
The example application demonstrates how to perform control on
DeviceNet using a PLC-5 processor and the 1771-SDN module. You
use RSLogix 5 programming software to create a ladder logic program
to control a photoeye and a RediSTATION
and PLC-5™ products, but
™
.
IMPORTANT
1 Publication 1771-6.5.132 - June 2000
This User manual should be used in conjunction
with the 1771-SDN DeviceNet Scanner Module
Installation Instructions, publication 1771-5.14. The
Installation Instructions contain important
information on configuring your scanner.
P-2 About This User Manual
Contents
This user manual contains the following chapters:
Before You Begin
1
go to Chapter 1
2
Planning Your
Configuration
go to Chapter 2
Setting Up the
3
Hardware
go to Chapter 3
Troubleshooting
7
go to Chapter 7
Configuring the
4
DeviceNet Network
go to Chapter 4
Configuring DeviceNet
5
From Another Network
go to Chapter 5
6
Creating and Running
the Application Program
go to Chapter 6
Audience
This manual is intended for control engineers and technicians who are
installing, programming, and maintaining a control system that
includes a PLC-5 processor communicating on a DeviceNet network
through a 1771-SDN module.
We assume that you:
are developing a DeviceNet network using a PLC-5 processor in
•
conjunction with the 1771–SDN scanner module
• know each of your device’s I/O parameters and requirements
• understand PLC-5 processor programming and operation
®
• are experienced with the Microsoft
• are familiar with RSNetWorx for DeviceNet software
Windows™ environment
Publication 1771-6.5.132 - June 2000
About This User Manual P-3
The Example Application
Product Name Catalog Number Series Revision
Qty Hardware
1
PLC-5C processor
1 1771 Universal I/O chassis 1771-A1B, -A2B, -A3B, -A3B1,
1 DeviceNet Scanner module 1771-SDN/B B -
1
Ethernet Interface module
1 DeviceNet Quad-Tap 1492-DN3TW - -
1 RediSTATION operator interface module 2705-TxDN1x42x-xxxx - -
1 Series 9000 Photoeye 42GNP-9000 or equivalent
1 DeviceNet RS-232 interface module 1770-KFD - -
1 RS-232 cables 1787-RSCABL/A (PC to 1770-KFD) - -
- DeviceNet dropline or trunkline
cables, as needed
1 24V Power Supply Regulated 24VDC, 8A - -
1 PC IBM-compatible
Software
RSLogix 5 9324-RL5300xxx - 3.22
RSNetWorx for DeviceNet 9357-DNETL3 - 2.11
(1)
(2)
RSLinx 9355-WABxxx - 2.10
The minimum requirement for the processor is that it support block transfer instructions.
A ControlNet version of the Processor is required if interfacing the DeviceNet network and a ControlNet network (see chapters 5 and 6).
Required if interfacing the DeviceNet network and an Ethernet network. See chapters 5 and 6.
This manual describes how to set up an example application. The
manual provides examples of each step of the setup, with references
to other manuals for more details.
System Components
We used the following devices and software for the example
application. For your own application, substitute your own devices to
fit your needs. The recommended configurations in this user manual
will help you set up the test system and get it working. Your eventual
configuration will depend on your application.
Note: If you use different software or fimware versions of these
products some of your screens may appear slightly different from
those shown in the example.
(1)
(2)
1785-L20C15, -L40C15, -L80C15 - -
B-
-A4B
1785-ENET - -
1787-PCABL, -TCABL, -MCABL - -
Windows 95/98, NT 4.0
Publication 1771-6.5.132 - June 2000
P-4 About This User Manual
More
Common Techniques Used in This Manual
The following conventions are used throughout this manual:
Bulleted lists provide information, not procedural steps.
•
Numbered lists provide sequential steps.
•
Information in bold contained within text identifies menu
•
windows, or screen options, screen names and areas of the
screen, such as dialog boxes, status bars, radio buttons and
parameters.
TIP
This is a definition
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 text.
This symbol identifies helpful tips.
A definition box defines terms that may be
unfamiliar to you.
Screen captures are pictures of the software’s
actual screens. The names of screen buttons and
fields are often in bold in the text of a
procedure. Pictures of keys represent the actual
keys you press.
The “MORE” icon is placed beside any
paragraph that references sources of additional
information outside of this document.
Publication 1771-6.5.132 - June 2000
About This User Manual P-5
Where to Find
More
Refer to the following publications as needed for additional help
when setting up and using your DeviceNet network:
More Information
For information about See this publication Publication Number
the 1771-SDN DeviceNet scanner 1771-SDN Scanner Module Installation Instructions 1771-5.14
the PLC-5 processor ControlNet PLC-5 Programmable Controllers User Manual
Phase 1.5
PLC-5 Instruction Set Reference Manual 1785-6.1
1785-PLC-5 Programmable Controllers Quick Reference 1785-7.1
the1785-ENET Ethernet interface module PLC-5 Ethernet Interface Module User Manual 1785-6.5.19
the 1771 I/O chassis Universal I/O Chassis 1771-2.210
the 1770-KFD communication module DeviceNet RS-232 Interface Module Installation Instructions 1770-5.6
a 1784-PCD communication card NetLinx DeviceNet Communication Card Installation Instructions 1784-5.29
a 1784-PCID or 1784-PCIDS card DeviceNet PCI Communication Interface Card Installation 1784-5.31
the RediSTATION RediSTATION Operator Interface User Manual 2705-804
the 9000 Series photoeye {refer to the information that came with your photoeye} n/a
DeviceNet DeviceNet System Overview DN-2.5
DeviceNet Design Manual (online) DNET-AT-001A-EN
connecting the DeviceNet network DeviceNet Cable Planning and Installation Manual DN-6.7.2
DeviceNet Cable Planning and Installation Release Note 1 DN-6.7.2-RN1
RSLinx software RSLinx Lite User’s Guide 9399-WAB32LUG
RSLogix 5 software Getting Results With RSLogix 5 9399-RL53GR
RSNetWorx for DeviceNet software DeviceNet Demo CD 9398-DNETDEMO
terms and definitions Allen-Bradley Industrial Automation Glossary AG-7.1
1785-6.5.22
TIP
TIP
Many of the above are available online from the
Automation Bookstore:
http://www.theautomationbookstore.com
.
For more information about Rockwell Software
products, visit the Rockwell Software internet site:
http://www.software.rockwell.com
.
Publication 1771-6.5.132 - June 2000
P-6 About This User Manual
Terminology
This term Means
Bridge The scanner module’s support of explicit message transfer.
Change of State A type of I/O data communication. 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. Data is updated at the rate of the
heartbeat.
Communication
The 1771-SDN scanner module or the 1770-KFD module.
Module
Cyclic A type of I/O data communication. 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.
EDS Electronic Data Sheet. A vendor-supplied template that specifies how
information is displayed as well as what is an appropriate entry (value).
Explicit
Messaging
A type of messaging used for lower priority tasks, such as configuration
and data monitoring.
Heartbeat Rate Devices that are configured for change of state data can also send a
“heartbeat” signal to indicate proper operation.
Host Platform The computer that hosts the 1771-SDN scanner module.
I/O An abbreviation for “input and output”.
Implicit
Messaging
The type of messaging used for high priority I/O control data; e.g., change
of state, cyclic, polled, or strobed.
Input Data Data produced by a DeviceNet device and collected by the scanner module
for a host platform to read.
MAC ID The network address of a DeviceNet node.
Network The DeviceNet network or the RSNetWorx for DeviceNet software
representation of the network.
Node Hardware that is assigned a single address on the network (also referred
to as device).
Offline When the PC communication scanner is not communicating on the
network.
Online When the PC communication scanner is configured and enabled to
communicate on the network.
Output Data Data produced by a host platform that is written to the scanner module’s
memory. This data is sent by the scanner module to DeviceNet devices.
®
PC Abbreviation for an IBM
compatible personal-computer.
Polled A type of input/output-data communication. A polled message solicits a
response from a single, specified device on the network (a point-to-point
transfer of data).
Record The node address and channel-specific memory assigned in the scanner
module’s non-volatile storage for a node in the scanlist.
Rx An abbreviation for “receive”.
Scanlist The list of devices (nodes) with which the scanner is configured to
exchange I/O data.
Scanner The function of the 1771-SDN scanner module to support the exchange of
I/O with slave modules.
Slave Mode The scanner module is in slave mode when it is placed in another scanner
module’s scanlist as a slave device.
Strobed A type of I/O data communication. A strobed message solicits a response
from each strobed device (a multicast transfer). It is a 64-bit message that
contains one bit for each device on the network.
Tx An abbreviation for “transmit”.
Publication 1771-6.5.132 - June 2000
About This User Manual P-7
Rockwell Automation Support
Rockwell Automation offers support services worldwide, with over 75
sales/support offices, 512 authorized distributors, and 260 authorized
systems integrators located throughout the United States alone, plus
Rockwell Automation representatives in every major country in the
world.
Local Product Support
Contact your local Rockwell Automation representative for:
sales and order support
•
product technical training
•
warranty support
•
support service agreements
•
Technical Product Assistance
If you need to contact Rockwell Automation for technical assistance,
call your local Rockwell Automation representative, or call Rockwell
directly at: 1 440 646-6800.
For presales support, call 1 440 646-3NET.
You can obtain technical assistance online from the following
Rockwell Automation WEB sites:
www.ab.com/mem/technotes/kbhome.html
•
www.ab.com/networks/eds
•
(electronic data sheets)
(knowledge base)
Your Questions or Comments about This Manual
If you find a problem with this manual, please notify us of it on the
enclosed Publication Problem Report (at the back of this manual).
If you have any suggestions about how we can make this manual
more useful to you, please contact us at the following address:
Rockwell Automation, Allen-Bradley Company, Inc.
Control and Information Group
Technical Communication
1 Allen-Bradley Drive
Mayfield Heights, OH 44124-6118
Publication 1771-6.5.132 - June 2000
P-8 About This User Manual
Publication 1771-6.5.132 - June 2000
Before You Begin
Planning Your Configuration and
Data Mapping Your Devices
Table of Contents
Chapter 1
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
What You Need to Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
What Your 1771-SDN Module Does . . . . . . . . . . . . . . . . . . . . 1-2
Address Density and Discrete I/O . . . . . . . . . . . . . . . . . . . . . . 1-4
Communicating with Your Devices . . . . . . . . . . . . . . . . . . . . . 1-6
Communicating with Your PLC-5 Processor. . . . . . . . . . . . . . . 1-7
What 1771-SDN Module Data Tables Are and What They Do . . 1-8
The Scanner Configuration Table (SCT) . . . . . . . . . . . . . . . 1-8
The Scanlist Table (SLT) . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
RSNetWorx Software as a Configuration Tool . . . . . . . . . . . . . 1-9
RSNetWorx for DeviceNet Configuration Screen Map . . . . 1-10
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Chapter 2
What You Need to Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Beginning the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
The Example Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Example Network Devices . . . . . . . . . . . . . . . . . . . . . . . . 2-2
RediSTATION Operator Interface Data Mapping. . . . . . . . . 2-4
Mapping RediSTATION Input Data
for a Block Transfer Read . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Mapping RediSTATION Output Data
for a Block Transfer Write . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Photoeye Input Data Mapping. . . . . . . . . . . . . . . . . . . . . . 2-7
Mapping Photoeye Input Data for a Block Transfer Read . . 2-8
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Chapter 3
Hardware Setup
i Publication 1771-6.5.132 - June 2000
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Installing the 1770-KFD Interface Module . . . . . . . . . . . . . . . . 3-1
Installing the PLC-5 Processor . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Setting the I/O Chassis Backplane Switches . . . . . . . . . . . . 3-2
Going Online to the PLC-5 Processor. . . . . . . . . . . . . . . . . 3-3
Installing the 1785-ENET Ethernet Module. . . . . . . . . . . . . . . . 3-5
Installing the 1771-SDN Scanner Module . . . . . . . . . . . . . . . . . 3-7
Setting the Channel 1 Data Rate
and Node Address Switches . . . . . . . . . . . . . . . . . . . . . . . 3-8
Setting the I/O Chassis Addressing Node Switches . . . . . . . 3-8
Installing the Scanner Module in the Chassis . . . . . . . . . . . 3-9
Connecting the Scanner to the DeviceNet Network . . . . . 3-10
Installing the RediSTATION Operator Interface . . . . . . . . . . . 3-11
Installing the Series 9000 Photoeye . . . . . . . . . . . . . . . . . . . . 3-12
How Your Example System Will Look. . . . . . . . . . . . . . . . . . 3-13
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Table of Contents ii
Configuring the
DeviceNet Network
Communicating with DeviceNet
from Another Network
Chapter 4
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Using RSLinx to Configure the DeviceNet Driver . . . . . . . . . . . 4-2
Using RSNetWorx for DeviceNet to Configure the Scanlist . . . . 4-4
Setting Up an Online Connection . . . . . . . . . . . . . . . . . . . 4-4
Setting the 1771-SDN Node Address . . . . . . . . . . . . . . . . . 4-6
Configuring the I/O Devices . . . . . . . . . . . . . . . . . . . . . . . 4-9
Verifying the Photoeye Configuration. . . . . . . . . . . . . 4-12
Verifying the RediSTATION Configuration . . . . . . . . . 4-13
AutoMapping the Devices into the Scanlist . . . . . . . . . 4-14
Download the Configuration to the Scanner . . . . . . . . 4-17
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Chapter 5
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Where to Find More Information. . . . . . . . . . . . . . . . . . . . . . . 5-2
Communicating with DeviceNet from a ControlNet Network . . 5-3
Configuring the DeviceNet Pass-Through Driver. . . . . . . . . 5-3
Communicating with the DeviceNet Network. . . . . . . . . . . 5-6
Communicating with DeviceNet from an Ethernet Network. . . 5-9
Configuring the Ethernet to PLC-5 Communications Driver . 5-9
Configuring the DeviceNet Pass-Through Driver. . . . . . . . 5-12
Communicating with the DeviceNet Network. . . . . . . . . . 5-15
Communicating with DeviceNet from a DH+ Network . . . . . 5-18
Configuring the DeviceNet Pass-Through Driver. . . . . . . . 5-18
Communicating with the DeviceNet Network. . . . . . . . . . 5-21
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Creating and Running the Example
Application Program
Publication 1771-6.5.132 - June 2000
Chapter 6
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Creating the Example Application Program . . . . . . . . . . . . . . . 6-2
Downloading and Running the Program . . . . . . . . . . . . . . . . . 6-6
Downloading and Running the Program
via a ControlNet Network . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Testing the Example Program . . . . . . . . . . . . . . . . . . . 6-8
Downloading and Running the Program
via an Ethernet Network . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Testing the Example Program . . . . . . . . . . . . . . . . . . 6-11
Downloading and Running the Program
via a DH+ Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Testing the Example Program . . . . . . . . . . . . . . . . . . 6-14
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Troubleshooting
1785-ENET Module
Channel Configuration
Installing and Configuring the
ControlNet Communications
Driver
Installing and Configuring the
DH+ Communications Driver
Data Map Example
Index
Table of Contents iii
Chapter 7
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Module Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Network Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Node/Error Code Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Appendix A
Configuring the Communications Channel. . . . . . . . . . . . . . . . A-1
Appendix B
Installing the 1784-KTCX15 Communication Interface Card . . . B-1
Configuring the 1784-KTCX15 Communications Driver . . . . B-2
Appendix C
Installing the 1784-KTX Communication Interface Card . . . . . . C-1
Configuring the 1784-KTX Communications Driver . . . . . . . . . C-2
Appendix D
Example Input Mapping Scheme. . . . . . . . . . . . . . . . . . . . . . D-1
Example Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Example Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Input Data Table Formats . . . . . . . . . . . . . . . . . . . . . . . . D-3
Example Output Mapping Scheme . . . . . . . . . . . . . . . . . . . . D-6
Example Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . D-6
Example Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6
Output Data Table Formats . . . . . . . . . . . . . . . . . . . . . . . D-7
Publication 1771-6.5.132 - June 2000
Table of Contents iv
Publication 1771-6.5.132 - June 2000
Before You Begin
Chapter
1
What This Chapter Contains
What You Need to Know
This chapter provides an overview of communication between a
PLC-5 processor and DeviceNet devices via a 1771-SDN module. The
data tables and the RSNetWorx for DeviceNet screens and windows
used to configure the data tables are also described.
The following table identifies what this chapter contains and where to
find specific information.
For information about See page
What You Need to Know 1-1
What Your 1771-SDN Module Does 1-2
Communicating with Your Devices 1-6
What 1771-SDN Module Data Tables Are and What They Do 1-8
The Scanner Configuration Table (SCT) 1-8
The Scanlist Table (SLT) 1-8
RSNetWorx Software as a Configuration Tool 1-9
RSNetWorx for DeviceNet Configuration Screen Map 1-10
Before configuring your 1771-SDN scanner module, you must
understand:
the data exchange between the PLC -5 processor and DeviceNet
•
devices through the 1771-SDN module
user-configurable 1771-SDN module data tables
•
• the role of RSNetWorx for DeviceNet software
1 Publication 1771-6.5.132 - June 2000
1-2 Before You Begin
What Your 1771-SDN Module Does
1771 I/O
Chassis
PLC-5
Processor
In a typical configuration, the 1771-SDN module acts as an interface
between DeviceNet devices and the PLC-5 processor.
1771-SDN
Scanner module
Series 9000
Photoeye
DeviceNet Network
RediSTATION
1770-KFD PC
Communication
Module
FLEX I/O Rack
DeviceNet
Devices
PC with RSNetWorx
for DeviceNet software
1305 Drive
The 1771-SDN module 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
The 1771-SDN module communicates with the processor in the form
of Block Transfers (BT) and/or Discrete I/O (DIO). Information
exchanged includes:
• device I/O data
• status information
• configuration data
Publication 1771-6.5.132 - June 2000
Before You Begin 1-3
A processor to I/O DeviceNet configuration is shown in the following
figure. See the referenced chapters for more information.
Input Read by Processor (Chapter 2)
Output Write by
Processor (Chapter 2)
Input Data from
Device to SDN
(Chapter 2)
Input
Device
Processor to I/O
Configure SDN module (Chapter 4)
Mapping Table (Chapters 2 and 4)
Output Data to Devices
from SDN (Chapter 2)
DeviceNet Network
PC running
RSNetWorx
for DeviceNet
Output
Device
Publication 1771-6.5.132 - June 2000
1-4 Before You Begin
Industrial
workstation
running RSView
The 1771-SDN scanner module can also be used to bridge a
DeviceNet network with another network.
Configuring Devices and Data Collection on
Higher-Level Networks Via PLC-5/SDN
Laptop PC
running
RSNetWorx
ControlNet, DH+, or Ethernet Network
Target Device to
be configured
Address Density and Discrete I/O
Configuration of device
using RSNetWorx
(Chapters 4 & 5)
You can use three addressing methods with your 1771-SDN scanner
module. The number of discrete I/O bits you have available for data
transfer is affected by the addressing mode selected.
SDN scanner
module
DeviceNet Network
Addressing Mode Discrete Inputs Discrete Outputs
2-slot 0 bits 0 bits
1-slot 8 bits 8 bits
1/2-slot 24 bits 24 bits
Collection of status
or alarm data
(Chapter 6)
Source Device
to collect data
Publication 1771-6.5.132 - June 2000
= bits reserved for 1771-SDN and
processor communication
= bits available for discrete
data transfer
Before You Begin 1-5
The concept described below applies to both input and output data
tables. For example, when using your 1771-SDN in 1-slot addressing
mode, you have eight bits of discrete input and eight bits of output
available.
In the scanner’s input and output data tables, there is one byte of memory that is
reserved for communication between the processor and the scanner.
Processor-specific responses from the scanner are read by the processor in this byte
of the input data table. Scanner-specific instructions are written to this byte of the
output data table.
0 bits for discrete data transfer
8 bits for discrete data transfer
24 bits for discrete data transfer
2-slot addressing
In 2-slot addressing mode, the only memory that would have
been available for discrete data transfer (8 bits) is taken up by
scanner/processor communication.
1-slot addressing
In 1-slot addressing mode, there are 16 bits: eight bits for
scanner/processor communication, and eight bits for discrete
data transfer.
1/2-slot addressing
In 1/2-slot addressing mode, there are 32 bits: eight bits used for
scanner/processor communication, and 24 bits for discrete data
transfer.
More
The address density is set via dip switches on the 1771-SDN module
and 1771 chassis. For more information about setting your module’s
address density with switches, refer to the 1771-SDN Scanner Module
Installation Instructions, publication 1771-5.14. For more information
about 1771-module addressing, refer to chapter 3 and to your PLC
programmable controller system-level installation manual and design
manual.
Publication 1771-6.5.132 - June 2000
1-6 Before You Begin
A strobe message is a
multicast transfer of data
(which is 64 bits in length)
sent by the 1771-SDN
module that solicits a
response from each strobed
slave device. There is one bit
for each of the possible 64
node addresses. The devices
respond with their data,
which can be as much as 8
bytes.
A poll message is a
point-to-point transfer of
data (0-255 bytes) sent by
the 1771-SDN module that
solicits a response from a
single device. The device
responds with its input data
(0-255 bytes).
A change of state message
is a transfer of data sent
whenever a data change
occurs. A user-configurable
heartbeat rate can also be
set to allow devices to
indicate proper operation
during intervals between
data changes. This does not
solicit response data, but
may receive an acknowledge
message.
A cyclic message is sent only
at a user-configurable rate,
such as every 10 ms.
Communicating with Your Devices
The 1771-SDN module communicates with a device via
and/or
change of state,
cyclic
messages. It uses these messages to solicit
strobe, poll,
data from or deliver data to each device. Data received from the devices,
or input data, is organized by the 1771-SDN module and made available
to the processor. Data received from your PLC-5 processor, or output data,
is organized in the 1771-SDN module and sent on to your devices.
IMPORTANT
Throughout this document,
from the PLC-5 processor’s point of view. Output is data
sent from the PLC-5 processor
collected by the PLC-5 processor
input
and
output
to
a device. Input is data
from
a device.
All data sent and received on a DeviceNet network is in
byte lengths. A device may, for example, produce only
two bits of input information. Nevertheless, since the
minimum data size on a DeviceNet network is one byte,
two bits of information are included in the byte of data
produced by the device. In this example (only two bits of
input information), the upper six bits are insignificant.
DeviceNet Devices
Input Data From
DeviceNet Devices
A1
Output Data To
DeviceNet Devices
Y
Data from a single device can
be mapped to separate
1771-SDN module memory
locations. For example,
“On/Off” values can be mapped
to one location, diagnostic
values to another, etc. This is
known as “map segmenting”.
This concept is illustrated by
byte A, stored separately as
segments A1 and A2.
,
1771-SDN Scanner Module
Input Data Storage
Byte
A1
B
C
A2
D
E
E
Output Data Storage
X
Y
Y
Y
Y
Z
0
1
2
3
4
5
6
input from the
devices to the
PLC-5 processor
output from
the PLC-5
processor
are defined
A2
B
C
D
E
X
Y
Y
Z
Publication 1771-6.5.132 - June 2000
Before You Begin 1-7
Communicating with Your PLC-5 Processor
A block transfer read (BTR) is
a block transfer of data from
the 1771-SDN module to the
PLC processor. The processor
reading
is
by the 1771-SDN module
(i.e., DeviceNet input data).
A block transfer write (BTW)
is a block transfer of data
from the PLC processor to
the 1771-SDN module. The
processor is
to the 1771-SDN’s memory
(i.e., DeviceNet output data).
the data collected
writing
the data
Your processor communicates with the 1771-SDN scanner module via
block transfer reads, block transfer writes, and DIO transfers.
Input data, gathered from the network’s devices, is organized within
the 1771-SDN and made available for the processor to “read”.
The 1771-SDN module does not send data to your processor.
Data transferred between the module and the processor must be
initiated by the processor. Output data is sent, or “written”, to the
scanner by your processor. This data is organized in the 1771-SDN
module, which in turn passes the data on to your scanned devices via
strobe, poll, change of state, or cyclic messages.
PLC-5 Processor
Discrete Input Image
B
A1
Block Transfer Data File
C
A2
D
E
E
Discrete I/O
Tra n s f e r
I/O Map
Block
Transfer
Read
1771-SDN Scanner
Internal Input
Data Storage
A1
B
C
A2
D
E
E
Input from
the devices
Discrete Output Image
X
Block Transfer Data File
Z
Y
Y
Y
Y
Discrete I/O
Transfer
I/O Map
Block
Transfer
Write
Internal
Output Data
X
Y
Y
Y
Y
Z
Output to
the devices
Publication 1771-6.5.132 - June 2000
1-8 Before You Begin
What 1771-SDN Module Data Tables Are and What They Do
To manage the flow of data between your processor and the network
devices, the 1771-SDN module uses the following data tables.
1771-SDN Module Configuration Table
•
Scanlist Table
•
Device Input Data Table
•
Device Output Data Table
•
Device Idle Table
•
Device Failure Table
•
You can configure two of these data tables through RSNetWorx
software. These two tables are stored in the 1771-SDN module’s
non-volatile memory and used to construct all other data tables:
Scanner Configuration Table (SCT)
•
Scanlist Table (SLT)
•
The Scanner Configuration Table (SCT)
The SCT controls basic information your 1771-SDN module needs to
function on your DeviceNet network. It tells your 1771-SDN module:
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
•
The Scanlist Table (SLT)
The SLT supports I/O updating for each of your devices on the
network. It also makes it possible for your 1771-SDN module to make
device data available to your processor. The SLT tells your 1771-SDN
module:
• which device node addresses to scan
Publication 1771-6.5.132 - June 2000
• how to scan each device (strobe, poll, change of state, cyclic or
any valid combination)
• how often to scan your devices
Before You Begin 1-9
exactly where in each device’s total data 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 or write
Interscan delay is the time between
I/O scans (polled and strobed). It is
the time the 1771-SDN module will
wait between the last poll message
request and the start of the next scan
cycle.
Background poll ratio sets the
frequency of poll messages to a
device in relation to the number of
I/O scans. For example, if the ratio
is set at 10, that device will be
polled once every 10 scans.
RSNetWorx Software as a Configuration Tool
User
Configured
Tab le s
SCT • basic operation
SLT • device-specific
Data In This Table RSNetWorx Configuration
Screen
1771-SDN Module Configuration
• module parameters
• interscan delay
• background poll ratio
Scanlist Editor (SLE)
identification data
• data transfer method
• transmit/receive data size
• input and output data
source and destination
locations
Edit Device I/O Parameters
These values can be configured
automatically through the
AutoMap function or manually
through the Data Table Map.
RSNetWorx for DeviceNet software is used to configure the 1771-SDN
module’s data tables. This software tool connects to the 1771-SDN
module over the DeviceNet network via a PC RS–232 interface
(1770–KFD module), or PC Card (1784-PCD, -PCID, or PCIDS).
TIP
RSNetWorx for DeviceNet software can also
communicate with the 1771-SDN module via a
ControlNet, Ethernet, or Data Highway Plus network.
See chapter 5.
Publication 1771-6.5.132 - June 2000
1-10 Before You Begin
The main RSNetWorx for DeviceNet screen.
The configuration screen map below shows the RSNetWorx for
DeviceNet screens used to configure the 1771-SDN module and the
navigation paths between them. The use of these screens is described
in Chapter 4.
RSNetWorx for DeviceNet Configuration Screen Map
To browse the network,
click on the Online button
and select the driver.
To automatically map input
devices, select the Input tab
and click on the AutoMap
button.
To access the 1771-SDN scanner Module,
double-click on the 1771-SDN icon.
To access the scanlist,
click on the Scanlist tab.
To automatically map output
devices, select the Output tab
and click on the AutoMap
button.
To download the scanlist, click on
the Download to Scanner button.
To edit a device’s I/O parameters,
double-click on the device in
the scanlist.
Publication 1771-6.5.132 - June 2000
Before You Begin 1-11
What’s Next?
The remaining sections of this manual provide the following
information:
Chapter 2 covers the configuration process planning stage
•
through a data mapping example.
Chapter 3 describes the hardware setup for the example
•
application.
Chapter 4 covers configuration of the DeviceNet network using
•
RSNetWorx for DeviceNet software.
Chapter 5 describes how to communicate with a DeviceNet
•
network from another network.
Chapter 6 describes how to create, download, and run the
•
example application program.
Chapter 7 covers the diagnostics provided for troubleshooting
•
the 1771-SDN module.
Publication 1771-6.5.132 - June 2000
1-12 Before You Begin
Publication 1771-6.5.132 - June 2000
Chapter
2
Planning Your Configuration and Data
Mapping Your Devices
This chapter introduces questions you should ask before configuring
your 1771-SDN Scanner. In addition, it presents an example DeviceNet
network and I/O data mapping scheme for a photoeye and a
RediSTATION operator interface module. The following table
identifies what this chapter covers and where to find specific
information.
For information about See page
What You Need to Know 2-1
Beginning the Process 2-1
The Example Network 2-2
Example Network Devices 2-2
Photoeye Input Data Mapping 2-7
Mapping Photoeye Input Data for a Block Transfer Read 2-8
RediSTATION Operator Interface Data Mapping 2-4
Mapping RediSTATION Input Data for a Block Transfer Read 2-5
Mapping RediSTATION Output Data for a Block Transfer Write 2-6
What You Need to Know
Beginning the Process
1 Publication 1771-6.5.132 - June 2000
To map data via your 1771-SDN Scanner module, you must
understand:
your network requirements
•
how input data is mapped
•
• how output data is mapped
Planning before configuring your 1771-SDN module 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
2-2 Planning Your Configuration and Data Mapping Your Devices
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. I/O data mapping can
be performed automatically by the RSNetWorx software. But when
mapping your I/O, you also have the opportunity to allot room for
future I/O. This can save time and effort in the future.
For example, RSNetWorx will automatically map the devices as
efficiently as possible, but the result is that multiple devices may share
the same word location in memory. However, you can also have the
system map the devices such that no two devices share the same
memory location by selecting the “Dword align” option when
performing automapping. You can manually map the devices if you
need to assign them to specific memory locations.
The Example Network
For details refer to the Help screens provided by the RSNetWorx for
DeviceNet software. Additional support can be found at the Rockwell
Software website: http://www.software.rockwell.com.
The following example illustrates a data mapping plan for a
DeviceNet network. Note that even if the mapping is performed
automatically by the RSNetWorx software, you must know where the
devices are mapped in order to use them in your network.
Example Network Devices
This example network has the following devices:
• a PC running RSNetWorx for DeviceNet software
• a 1771-SDN Scanner module interfacing a PLC-5 processor with
DeviceNet
• a Series 9000 photoelectric sensor (strobed)
• a RediSTATION operator interface (polled)
Publication 1771-6.5.132 - June 2000
Loading...