DeviceNet To

SCANport
Communication
Module with
Digital Inputs
Catalog Number 2100-GK61
Firmware 1.xx

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,
Rockwell Automation does not assume responsibility or liability (to include
intellectual property liability) for actual use based upon the examples shown
in this publication.
Rockwell Automation publication SGI-1.1, Safety Guidelines for the
Application, Installation, and Maintenance of Solid-State Control (available
from your local Rockwell Automation office), describes some important
differences between solid-state equipment and electromechanical devices
that should be taken into consideration when applying products such as
those described in this publication.
Reproduction of the contents of this copyrighted publication, in whole or in
part, without written permission of Rockwell Automation, is prohibited.
Throughout this manual we use notes to make you aware of safety
considerations:

ATTENTION: Identifies information about practices

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

Attention statements help you to:

Identify a hazard.

Avoid the hazard.

Recognize the consequences.

IMPORTANT: Identifies information that is critical for successful

application and understanding of the product.

Preface

Using this Manual

Objectives

Who Should Use this Manual?

Read this preface to become familiar with the organization of the

manual. In this preface, you will read about the following:

Who should use this manual.

An overview of the DeviceNet to SCANport Communication

Module with Digital Inputs.

The purpose of this manual.

Terms and abbreviations.

Conventions used in this manual.

Rockwell Automation support.

Use this manual if you are responsible for installing, wiring,

programming, or troubleshooting control systems that use the
DeviceNet to SCANport Communication Module with Digital Inputs.
This manual is intended for qualified service personnel responsible
for setting up and servicing the DeviceNet to SCANport
Communication Module with Digital Inputs. You must have previous
experience with and a basic understanding of electrical terminology,
programming procedures, networking, required equipment and
software, and safety precautions.

Purpose of this Manual

This manual is a learning and reference guide for the DeviceNet to

SCANport Communication Module with Digital Inputs. It describes
the procedures needed to install, configure, and troubleshoot the
adapter.

Related Publications
Title

Publication Number

1771-SDN Scanner Configuration Manual

1771-6.5.118

DeviceNet Scanner Configuration Manual

1747-6.5.2

DeviceNet Cable System Planning and Installation

Manual

DN-6.7.2

Publication 2100-UM001A-US-P January 2000

P-2

Using this Manual

Safety Precautions

Please read the following safety precautions carefully.

Terms and Abbreviations

The following terms and abbreviations are specific to this product.

For a complete listing of Allen-Bradley terminology, refer to the
Allen-Bradley Industrial Automation Glossary, Publication AG-7.1.
Terms

Publication 2100-UM001A-US-P January 2000

ATTENTION: Only personnel familiar with

SCANport products and associated machinery should
plan or implement the installation, start-up,
configuration, and subsequent maintenance of the
DeviceNet to SCANport Communication Module with
Digital Inputs. Failure to comply may result in personal
injury and/or equipment damage.

Definition

DeviceNet

An open network that provides probabilistic I/O control

through a managed bit-wise non-destructive multiplexing
scheme.

SCANport

A standard peripheral communications interface for various

Allen-Bradley drives and power products.

SCANport
Peripheral

A device that provides an interface between SCANport and

a network. It is often referred to as an adapter. For example,
the DeviceNet to SCANport Communication Module with
Digital Inputs is a SCANport peripheral.

SCANport
Product

A device that uses the SCANport communications interface

to communicate with one or more peripheral devices. For
example, a motor drive such as a 1336 PLUS is a SCANport
product.

Digital Input

ON-OFF input voltages of either 230Vac, 115Vac or

24Vdc

RSNetWorx,
RSLinx,
RSLogix,
RSLogix500

Rockwell Software products which provide communication to

a wide range of applications. Refer to
http://www.software.rockwell.com for more information

Using this Manual

Conventions Used in this

Manual

P-3

The following conventions are used throughout this manual:

Bulleted lists provide information, not procedural steps.

Numbered lists provide sequential steps or hierarchical

information.

Italic type is used for chapter names and for parameter names.

Bold type is used for names of menus, menu options, screens, and
dialog boxes.

Important: This type of paragraph contains tips or notes that have

been added to call attention to useful information.

Rockwell Automation Support

Rockwell Automation offers support services worldwide, with more

than 75 sales/support offices, more than 500 authorized distributors,
and more than 250 authorized systems integrators located throughout
the United States alone. In addition, Rockwell Automation
representatives are 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 Support

If you need to contact Rockwell Automation for technical assistance,
please call your local Rockwell Automation representative.

Publication 2100-UM001A-US-P January 2000

P-4

Using this Manual

Publication 2100-UM001A-US-P January 2000

Table of Contents
Using this Manual

Preface
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Who Should Use this Manual? . . . . . . . . . . . . . . . . . . . . . . P-1
Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-2
Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . P-2
Conventions Used in this Manual . . . . . . . . . . . . . . . . . . . . . P-3
Rockwell Automation Support . . . . . . . . . . . . . . . . . . . . . . P-3
Local Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Technical Product Support . . . . . . . . . . . . . . . . . . . . . . . . P-3

Chapter 1
Overview

Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Overview of the Communication Adapter . . . . . . . . . . . . . . 1-1
Features of the Communication Adapter . . . . . . . . . . . . . . 1-3
SCANport Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Hardware and Parts Description . . . . . . . . . . . . . . . . . . . . . 1-6
2100-GK61 Module Hardware . . . . . . . . . . . . . . . . . . . . . 1-6
Overview of Setting Up the Adapter . . . . . . . . . . . . . . . . . . 1-7
Required Tools and Equipment . . . . . . . . . . . . . . . . . . . . . 1-7

Chapter 2
Installation

Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Installing a 2100-GK61 Module . . . . . . . . . . . . . . . . . . . . . 2-1
Required Tools and Equipment . . . . . . . . . . . . . . . . . . . . 2-1
Selecting Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Installing the DeviceNet to SCANport Communication Module
with Digital Inputs (2100-GK61) . . . . . . . . . . . . . . . . . . 2-3
Removing the DeviceNet to SCANport Communication Module
with Digital Inputs (2100-GK61) . . . . . . . . . . . . . . . . . 2-10

Chapter 3
Configuring the DeviceNet to
SCANport Communication Module
with Digital Inputs Using
RSNetWorx for DeviceNet

Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Factory Default Settings for the 2100-GK61. . . . . . . . . . . . 3-1
What is RSNetWorx for DeviceNet? . . . . . . . . . . . . . . . . . . 3-2
Required Equipment and Software . . . . . . . . . . . . . . . . . . . 3-2
Using RSNetWorx to Edit Your Adapters Parameters . . . . 3-3

Chapter 4
Configuring a Scanner to Commu- Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
What is RSNetWorx for DeviceNet? . . . . . . . . . . . . . . . . . . 4-1
nicate with the Adapter
Required Equipment and Software . . . . . . . . . . . . . . . . . . . 4-1
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Using Online Mode in RSNetWorx for DeviceNet . . . . . . . . 4-2
Creating an EDS File for Your SCANport Product . . . . . . . 4-4
Configuring a PLC Scanner . . . . . . . . . . . . . . . . . . . . . 4-10
Configuring a PLC Scanner (1771-SDN) to Communicate with the
Adapter.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Configuring an SLC Scanner (1747-SDN) to Communicate with
the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Configuring an SLC Scanner . . . . . . . . . . . . . . . . . . . . 4-17

Publication 2100-UM001A-US-P - January 2000

Chapter 5
Ladder Logic Programming

Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
What is RSLogix? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
What are Ladder Logic Programs?. . . . . . . . . . . . . . . . . . . 5-2
Example Ladder Logic Programs . . . . . . . . . . . . . . . . . . . . 5-3
PLC Ladder Logic Example . . . . . . . . . . . . . . . . . . . . . . 5-5
SLC Ladder Logic Program Example . . . . . . . . . . . . . . . 5-7

Chapter 6
Using DeviceNet Explicit Messag- Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
ing
Explicit Message Program Control for PLC-5 . . . . . . . . . . . . 6-1
Message Translations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Messaging for the 1771-SDN Scanner . . . . . . . . . . . . . . . . 6-3
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
PLC-5 Ladder Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
PLC Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Explicit Message Program Control for SLC . . . . . . . . . . . . 6-9
Message Translations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Messaging for the 1747-SDN Scanner . . . . . . . . . . . . . . . 6-11
SLC Ladder Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
SLC Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Using Messages to Control SCANport Products . . . . . . . 6-16
Writing to Register Objects . . . . . . . . . . . . . . . . . . . . . . . . . 6-17

Chapter 7
Troubleshooting

Product Specifications

Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

LEDs on the 2100-GK61 Module . . . . . . . . . . . . . . . . . . . . . 7-1
DeviceNet Network Status LED States . . . . . . . . . . . . . . . . 7-2
Module Status LED States . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
SCANport Status LED States . . . . . . . . . . . . . . . . . . . . . . . 7-3
Input Status LED States . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Appendix A
Appendix Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
2100-GK61 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . A-1

DeviceNet to SCANport Communi- Appendix B

cation Module with Digital Inputs Appendix Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1
Setting the Node Address. . . . . . . . . . . . . . . . . . . . . . . . . . .B-1
Parameters
Setting the Data Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Using Datalinks and Command I/O . . . . . . . . . . . . . . . . . . .B-2
Using Master-Slave Communications . . . . . . . . . . . . . . . . .B-5
Polled Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5
COS (Change of State) Allocation. . . . . . . . . . . . . . . . . . B-7
Cyclic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-8
Polled and COS Allocation . . . . . . . . . . . . . . . . . . . . . . .B-10
Polled and Cyclic Allocation . . . . . . . . . . . . . . . . . . . . . . B-11
Using Peer-to-Peer Communications . . . . . . . . . . . . . . . . B-12
Enabling the Adapter to Receive Peer I/O . . . . . . . . . . .B-12
Enabling the Adapter to Transmit Peer I/O . . . . . . . . . .B-15
Using Fault Configurable Inputs . . . . . . . . . . . . . . . . . . . . B-16
DeviceNet to SCANport Communication Module with Digital InPublication 2100-UM001A-US-P - January 2000

puts Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17

M-S Input Parameter Configurations . . . . . . . . . . . . . . . B-24
M-S Output Parameter Configurations . . . . . . . . . . . . . B-26

DeviceNet Objects

Appendix C
Appendix Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1
Object Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Class Code 0x01 Identity Object . . . . . . . . . . . . . . . . . . C-2
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2
Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2
Instance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-3
Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-3
Get_Attribute_All Response . . . . . . . . . . . . . . . . . . . . . . C-3
Class Code 0x02 Message Router Object . . . . . . . . . . .C-4
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-4
Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-4
Instance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Common Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Class Code 0x03 DeviceNet Object . . . . . . . . . . . . . . . .C-5
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-5
Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-5
Instance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-5
Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-5
Class Code 0x05 Connection . . . . . . . . . . . . . . . . . . . . .C-6
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-6
Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-6
Instance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-7
Common Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Class Code 0x07 Register Object . . . . . . . . . . . . . . . . . C-8
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-8
Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-8
Instance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-9
Common Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
Class Code 0x0F Parameter Object . . . . . . . . . . . . . . .C-10
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-10
Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
Instance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11
Bit Definitions for Instance Attribute 4 . . . . . . . . . . . . . .C-12
Data Types for Instance Attribute 5. . . . . . . . . . . . . . . . .C-13
Common Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-14
Get_Attribute_All Response . . . . . . . . . . . . . . . . . . . . . .C-14
Object Specific Services . . . . . . . . . . . . . . . . . . . . . . . .C-15
Class Code 0x10 Parameter Group Object . . . . . . . . . .C-16
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-16
Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-16
Instance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-16
Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-17
Get_Attribute_All Response . . . . . . . . . . . . . . . . . . . . . .C-17
Class Code 0x93 SCANport Pass-Through Parameter
Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-18
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-18
Instance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-18
Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-18
Object-Specific Services . . . . . . . . . . . . . . . . . . . . . . . .C-18
Class Code 0x97 SCANport Pass-Through Fault Object C-19
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-19
Instance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-19
Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-20
Class Code 0x98 SCANport Pass-Through Warning
Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-21
Publication 2100-UM001A-US-P - January 2000

Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-21

Instance Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-22
Class Code 0x99 SCANport Pass-Through Link Object C-23
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-23
Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-23
Object-Specific Services . . . . . . . . . . . . . . . . . . . . . . . .C-23
Class Code 0x67 PCCC Object . . . . . . . . . . . . . . . . . .C-25
Class Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-25
Instance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-25
Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-25
Object Specific Services . . . . . . . . . . . . . . . . . . . . . . . .C-25
Message Structure for Execute_PCCC . . . . . . . . . . . . .C-25
Message Structure for Execute_Local_PCCC . . . . . . . .C-26

N-File Addresses

Appendix D
Appendix Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-1
N-File Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-1

Supported Emulated Block Trans- Appendix E

Appendix Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
fer Commands
What is Emulated Block Transfer? . . . . . . . . . . . . . . . . . . .E-1
Supported Emulated Block Transfer Commands . . . . . . . . E-1
Emulated Block Transfer Status Word . . . . . . . . . . . . . . . . .E-2
Parameter Value Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
PLC Block Transfer Emulation Instruction Data . . . . . . . E-3
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-3
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
Parameter Value Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4
PLC Block Transfer Emulation Instruction Data . . . . . . . .E-4
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-4
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-4
Parameter Read Full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-5
PLC Block Transfer Emulation Instruction Data . . . . . . . .E-5
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-6
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-6
Product ID Number Read . . . . . . . . . . . . . . . . . . . . . . . . . . E-8
PLC Block Transfer Emulation Instruction Data . . . . . . . .E-8
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-9
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-9
Scattered Parameter Value Read . . . . . . . . . . . . . . . . . . .E-10
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-11
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-11
Scattered Parameter Value Write . . . . . . . . . . . . . . . . . . .E-12
PLC Block Transfer Emulation Instruction Data . . . . . . E-12
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-13
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-13
NVS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-14
PLC Block Transfer Emulation Instruction Data . . . . . . .E-14
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-14
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-14
Fault Command Write . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-15
PLC Block Transfer Emulation Instruction Data . . . . . . .E-15
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-15
Fault Queue Entry Read Full . . . . . . . . . . . . . . . . . . . . . . .E-16
PLC Block Transfer Emulation Instruction Data . . . . . . E-16
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-17
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-17
Fault Queue Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-18
Publication 2100-UM001A-US-P - January 2000

PLC Block Transfer Emulation Instruction Data . . . . . . . E-18

Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-18
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-18
Trip Fault Queue Number . . . . . . . . . . . . . . . . . . . . . . . . . E-19
PLC Block Transfer Emulation Instruction Data . . . . . . . E-19
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-19
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-19
Digital Input Parameter Read . . . . . . . . . . . . . . . . . . . . . . E-20
PLC Block Transfer Emulation Instructions Data . . . . . . E-20
Message Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-21
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-21

Publication 2100-UM001A-US-P - January 2000

Chapter

Overview
Chapter Objectives

Chapter 1 provides an overview of your DeviceNet to SCANport

Communication module with Digital Inputs. In this chapter, you will
read about the following:

Function of the 2100-GK61 module.

Features of the 2100-GK61 module.

SCANport products.

Parts and hardware of the 2100-GK61 module.

Steps for setting up the adapter.

Required tools and equipment.

Overview of the
Communication Adapter
Figure 1.1
2100-GK61 Module

2100-GK61 Module - Front View

2100-GK61 Module - Top View

2100-GK61 Module

The 2100-GK61 module mounts on a panel and connects to the

SCANport product via a SCANport cable. Digital inputs of 230Vac,
115Vac or 24Vdc are connected to the adapter via discrete wires. The
voltage level used for the digital inputs is set via a dip switch SW1.

Publication 2100-UM001A-US-P January 2000

1-2

Overview

The communications adapter provides an electronic communications

interface between a DeviceNet network and any single SCANport
product.
Figure 1.2
Example of 2100-GK61 Modules Connecting SCANport Products
to DeviceNet
1336 PLUS
1305
SMC Dialog Plus

DeviceNet

In Figure 1.2, a SCANport cable connects a 2100-GK61 module to a

SCANport product through a port on the SCANport product. A
DeviceNet cable connects the module to the DeviceNet network. The
module then translates the DeviceNet messages into SCANport
messages that can be understood by the connected product.
The adapter is also capable of connecting to four (4) common switch
inputs. These inputs can monitor status of disconnect switches, starter
and contactor auxiliary contact, relays, push buttons or any ON-OFF
device capable of switching 230Vac, 115Vac, or 24Vdc.

Publication 2100-UM001A-US-P January 2000

Overview

1-3

Figure 1.3
Example of 2100-GK61 Module Connecting Digital Inputs

In Figure 1.3 discrete wiring connects up to four (4) digital inputs to

the 2100-GK61 module. A DeviceNet cable connects the module to
the DeviceNet network and a SCANport cable connects a SCANport
product to the module. The contact status is then translated into a
DeviceNet message that can be used to control SCANport devices
attached to the module or other devices on the DeviceNet network.

Features of the Communication

Adapter

The DeviceNet network is an open, global industry-standard

communication network designed to provide an interface through a
single cable from a programmable controller directly to smart
devices such as sensors, push buttons, motor starters, simple operator
interfaces and drives.
The 2100-GK61 module lets you connect your SCANport products to
a DeviceNet network. This adapter features the following:

Flash upgradeability allows for field updates in the event of

changes to the adapters firmware.

Publication 2100-UM001A-US-P January 2000

1-4

Overview

Publication 2100-UM001A-US-P January 2000

COS (Change of State) capability lets you customize this devices

activity on the network by configuring the adapter to report only
new data.

Cyclic operation lets you customize the devicess activity on the

network by configuring the adapter to report its data at specific
intervals.

Polled operation allows you to customize the devices activity on

the network to respond only after the scanner sends control data.

Peer I/O capabilities lets the drives I/O (logic command,

reference, logic status, feedback and datalinks) be broadcast to or
received from other drives connected via 1203-GU6, 1336-GM6
or 2100-GK61 adapters.

Software configuration lets you configure the adapter using

RSNetWorx for DeviceNet.

Faulted Node Recovery lets you change items, such as a node

address, of a device even when it is faulted on the network.

User-configurable fault response provides the ability to customize

the adapters actions to communication errors.

A Module Status LED helps to diagnose network, module, and

SCANport product health.

Monitor and report status of four (4) individual digital inputs.

Overview

SCANport Products

1-5

Some SCANport products support one peripheral; others support up

to six peripherals. The table below lists SCANport products, the
number of peripherals each supports, the minimum and maximum I/O
words, and the type of adapter that can be used.
I/O Words

Adapter Use

Number of
Peripherals
Supported

Minimum

Maximum

2100-GK61

1305 AC MICRO Drive

10

Yes

1336 IMPACT Drive

10

Yes

1336 PLUS AC Drive

10

Yes

1336 PLUS II Drive

10

Yes

1336 FORCE Drive

10

Yes

1394 AC Mult-Axis Motion

Control System

10

Yes

SMC Dialog Plus

Yes

SMP-3 Smart Motor Protector

Yes

1397 Digital DC Drive

10

Yes

1557 Medium Voltage Drive

10

Yes

Product

Lower horsepower products may not support a sixth peripheral. Refer to your user manual to verify that your
product supports a sixth peripheral.

Important: To connect multiple peripherals to a SCANport product,

a port expander may be required. Refer to your products
documentation for more information.
Important: If you intend to use datalinks to communicate with and
control your SCANport product, verify that your SCANport product
supports datalinks before enabling them in the adapter.

Publication 2100-UM001A-US-P January 2000

1-6

Overview

Hardware and Parts

Description

2100-GK61 Module Hardware

Figure 1.4 illustrates and the following table lists the main parts of the
2100-GK61 DeviceNet to SCANport communication module with
Digital Inputs:
Figure 1.4
Parts of the 2100-GK61 Module
1
2

3
4
6

Number

Part

Description

Panel mount

Attach module to sub-panel through mounting holes.

SCANport
Connection

Provides a standard SCANport 8-pin circular mini-DIN connector for the

SCANport cable.

Digital Input
Connector

Allows connection of switched 230Vac, 115Vac or 24Vdc inputs to module.

The 6-pin plug-in connector (PIN 192 929) is supplied with the module.

Bi-Color LEDs

Indicate the status of the DeviceNet media channel, of the SCANport connection, and of the module. For more information, refer to Chapter 7, Troubleshooting.

DeviceNet Connection

Provides a 10-pin Phoenix connector to attach the module to the DeviceNet

network. The 10-pin plug-in connector (PIN 94220605) is supplied with the
module

Input Status LEDs

Indicate the ON-OFF status of the digital inputs.

SW1

Set to match the digital input voltage applied of 230Vac, 115Vac, or 24Vdc.

Publication 2100-UM001A-US-P January 2000

Overview

Overview of Setting Up the

Adapter

1-7

To set up the DeviceNet to SCANport Communication Module with

Digital Inputs, you must perform the following tasks:
1. Install the module. Refer to Chapter 2, Installation.
2. Set the adapters node address and configure the adapters
parameters. Refer to Chapter 3, Configuring the DeviceNet to
SCANport Communication Module with Digital Inputs
3. Configure a scanner (either PLC or SLC) to communicate with
the Adapter. Refer to Chapter 4, Configuring a Scanner to
Communicate with the Adapter.
4. If necessary, create a ladder logic program to control the
SCANport product. Refer to Chapter 5, Ladder Logic
Programming.

Required Tools and Equipment

To install and configure a 2100-GK61 module, you need the

following:

DeviceNet to SCANport Communication Module with Digital

Inputs (2100-GK61).

10-pin plug-in DeviceNet connector (supplied with module).

Appropriate cables for SCANport and DeviceNet connections.

Refer to the Selecting Cables section in Chapter 2, Installation.

6-pin plug-in Input connector (supplied with module).

#10 hardware for attaching module to a panel.

A PC that is:

Running RSNetWorx.

Connected to and communicating with the DeviceNet

network using a 1784-PCD card or a 1770-KFD adapter.

Running RS Linx.

Running RSLogix5 (if using PLC) or RSLogix500 (if using

SLC).

Important: Refer to http://www.software.rockwell.com for more

information on these software products.

Publication 2100-UM001A-US-P January 2000

1-8

Overview

Publication 2100-UM001A-US-P January 2000

Chapter

Installation
Chapter Objectives

Installing a 2100-GK61 Module

Chapter 2 provides the information that you need to install the

2100-GK61 module. In this chapter, you will read about the
following:

Required tools and equipment.

Selecting cables.

Installing the adapter.

Removing the adapter.

Follow these procedures to install a 2100-GK61 module.

Required Tools and Equipment

To install your 2100-GK61 module, you will need the following tools
and equipment:

DeviceNet to SCANport Communication Module with Digital

Inputs(2100-GK61).

A 6-pin and 10-pin plug-in connector (supplied with module).

Screwdriver or nutdriver and mounting screws (#10).

Appropriate cables for SCANport and DeviceNet connections.

Refer to the Selecting Cables section in this chapter.

Selecting Cables
To connect the 2100-GK61 to the SCANport product and the
DeviceNet network, you must select an appropriate DeviceNet cable
and Allen-Bradley SCANport cable. Use the following information to
select appropriate cables for each connection.

Publication 2100-UM001A-US-P January 2000

2-2

Installation

SCANport Cables
When selecting the SCANport cable to connect the 2100-GK61
module to the SCANport product, you need to:

Use an Allen-Bradley SCANport cable. Refer to the table below.

Male to Male Connection

Male to Female Connection

Length

Catalog Number

Length

Catalog Number

1/3 m

1202-C03

1/3 m

1202-H03

1m

1202-C10

1m

1202-H10

3m

1202-C30

3m

1202-H30

9m

1202-C90

9m

1202-H90

Use less than 10 meters (33 feet) of cable between the SCANport
product and adapter.

Keep SCANport cables away from high power cables to guard

against introducing noise into your system.

DeviceNet Cables
The 2100-GK61 module comes with a 10-pin (dual row 5-pin)
connector. This connector is used to wire the module for both single
drops, when only one side of the terminals are used, or to daisy chain
devices together when both sides of the terminals are used. A drop
line connects a node such as a 2100-GK61 module, in the DeviceNet
cable system to the DeviceNet trunk.
Before connecting modules to the network you must determine if
your network is within limits of the cable system. Class 1 cables are
rated 600 volts, 8 amps. Class 2 cables are rated 300 volts, 4 amps.
The cables in the chart below can be used for Trunk or Drop
applications. When used for Trunk, length limits must be observed.
Cable Type

Part Number

Data Rates
125 Kbps

250 Kbps

500 Kbps

Class 1 Flat

1485C-P1-E75

420m (1378 ft.)

200m (656 ft.)

75m (246 ft.)

Class 2 Thick Round

1485C-P1-A50

500m (1640 ft.)

250m (820 ft.)

100m (328 ft.)

Class 2 Thin Round

1485C-P1-C50

100m (328 ft.)

100m (328 ft.)

100m (328 ft.)

Class 1 round drop cable is recommended for connections between

devices and Class 1 Trunk. Maximum drop length is 6m (20 ft.)
Cumulative Drop Budget is based on Data Rate.

Publication 2100-UM001A-US-P January 2000

125 Kbps

250 Kbps

500 Kbps

156m (512 ft.)

78m (256 ft.)

39m (128 ft.)

Installation

2-3

Class 1 Drop Cable is available in three spool sizes:

Cable Part Number

Spool Size

1485C-P1-B50

50m (164 ft.)

1485C-P1-B150

150m (492 ft.)

1485C-P1-B300

300m (984 ft.)

For more information on DeviceNet cables and cable systems, refer to

the DeviceNet Cable System Planning and Installation Manual,
Publication DN-6.7.2.
Input Wires
Suitable wire to handle 230Vac, 115Vac, or 24Vdc voltage depending
on installation. The input connector is capable of installing
12-24AWG wire.

Installing the DeviceNet to SCANport Communication

Module with Digital Inputs (2100-GK61)
The following instructions explain how to physically install your
DeviceNet to SCANport Communication Module with Digital Inputs.

ATTENTION: Severe injury or death can result from

electrical shock, burn, or unintended actuation of controlled
equipment. Hazardous voltages may exist in the cabinet even
with the circuit breaker in the off position. Recommended
practice is to disconnect and lock out control equipment from
power sources, and discharge stored energy in capacitors, if
present. If it is necessary to work in the vicinity of energized
equipment, the safety related work practices of NFPA 70E,
Electrical Safety Requirements for Employee Workplaces,
must be followed.
ATTENTION: DO NOT work alone on energized
equipment!

1. Before installing the module set the Digital Input selection switch
SW1 to the proper input voltage per the table below.

SW1
VIN
#1

#2

230Vac

OFF

OFF

115Vac

OFF

ON

24Vdc

ON

OFF

Publication 2100-UM001A-US-P January 2000

2-4

Installation

SW1 is accessed through the plastic cover on the 2100-GK61

module as show in Figure 2.1

Publication 2100-UM001A-US-P January 2000

ATTENTION: To guard against possible

component damage, assure that Dip Switch
SW1 is set for the correct input voltage used
in the system before power is applied to the
module.

Installation

2-5

Figure 2.1
Dip Switch Access - Side View of 2100-GK61 Module

1 2

Dip Switch Location

2. Determine a suitable mounting location within a desired location

close to its interconnecting devices and /or components.

ATTENTION: The 2100-GK61 module is an open

panel device and must be mounted inside a suitable
enclosure.

When choosing a suitable mounting location allow 1.0 (2.54cm)

clearance from the front of the module to the door of the enclosure or other devices. This clearance is needed for DeviceNet wiring harness/bend radius.
Mount the module to the panel with #10 hardware as detailed in
Figure 2.2.

Publication 2100-UM001A-US-P January 2000

2-6

Installation

Figure 2.2
Mounting Dimensions

Digital Input
Connector

Publication 2100-UM001A-US-P January 2000

DeviceNet
Connector

Installation

2-7

3. Remove power from the network.

4. Insert the DeviceNet cable wires into the 10-pin connector. Make
sure you follow the color key next to the connector receptacle on
the module.

ATTENTION: If you wire the 10-pin header after

youve connected it to the module, static control
precautions are required. Device malfunction may occur
if you do not follow ESD control procedures. If you are
not familiar with static control procedures, refer to
Allen-Bradley Publication 8000-4.5.2, Guarding
Against Electrostatic Damage, or other applicable ESD
protection handbook.

Figure 2.3
DeviceNet Connections

Color Key
1 - Red - V+

10-pin Dual Row

DeviceNet Connection

2 - White-CAN_H
3 - Shield
4 - Blue-CAN_L
5 - Black- V-

Front View of 2100-GK61 Module

Publication 2100-UM001A-US-P January 2000

2-8

Installation

5. Plug the connector into the module.

ATTENTION: Danger of electrical shock exists if

power is not disconnected to Digital Input Devices.
Verify power is removed before proceeding.

6. Connect the Digital Inputs to the Digital Input six (6) pin connectors. Below is the connection pinout detail.
Figure 2.4
Digital Input Connections

Pin 1 = Input #1
Pin 2 = Input #2
Pin 3 = Input #3
Pin 4 = Input #4
Pin 5 = Input Common
Pin 6 = Input Common

7. Plug the Input connector into the module.

8. Connect the SCANport cable to the communications adapter and
then to the SCANport product.

Publication 2100-UM001A-US-P January 2000

Installation

2-9

Figure 2.5
SCANport Connection

SCANport Cable

9. Reapply power to the DeviceNet network.

10. If necessary, apply power to the connected SCANport product
and to the Digital Inputs.

Publication 2100-UM001A-US-P January 2000

2-10

Installation

Your 2100-GK61 module is now installed. The SCANport LED is

green. The network and module LEDs are blinking green. If your
modules LEDs are different, refer to Chapter 7, Troubleshooting, for
more information.
You must now edit the adapters node address, and you may want to
edit some of its other parameters. Refer to Chapter 3 for more
information

Removing the DeviceNet to SCANport

Communication Module with Digital Inputs
(2100-GK61)
To remove the DeviceNet to SCANport Communication Module with
Digital Inputs, you need to:
1. Disconnect Input Power from Digital Inputs.

ATTENTION: Electrical shock hazard exists if

power is not disconnected to Digital Input Devices.
Verify power is removed before proceeding.

2. Remove the SCANport cable from the SCANport product and

then from the module.
3. Unplug the 10-pin DeviceNet connector from the module.
4. Unplug the 6-pin Digital Input connector from the module.
5. Remove the module from the panel.

Publication 2100-UM001A-US-P January 2000

Chapter

Configuring the DeviceNet to

SCANport Communication Module
with Digital Inputs
Using RSNetWorx for DeviceNet
Chapter Objectives

Chapter 3 provides information that you need to configure the

2100-GK61 module over the DeviceNet network. In this chapter, you
will read about the following:

Factory-default settings for the module.

RSNetWorx software.

Equipment necessary to use RSNetWorx software.

Editing the 2100-GK61 adapters parameters using RSNetWorx

software.

This section assumes you have experience using RSNetWorx

software to configure a DeviceNet network.

Factory Default Settings for the

2100-GK61

The factory-default settings of the DeviceNet to SCANport

Communication Module with Digital Inputs include the following:

16-bit Logic Command/Status enabled for polling.

16-bit Reference/Feedback enabled for polling.

If the scanner is put into program mode or the network faults, the
SCANport product will be faulted by the module.

A node address of 63.

DeviceNet autobaud detection enabled.

Publication 2100-UM001A-US-P January 2000

3-2

Configuring the DeviceNet to SCANport Communication Module with Digital Inputs

You should change the node address by editing the DN Node Address
(2) parameter. Note: The number in ( ) following the parameter name
corresponds to the parameter number as found in Appendix B,
DeviceNet to SCANport Communication Module with Digital Inputs
Parameters. You must change the autobaud detection if no other
devices on your DeviceNet network have a fixed data rate by editing
DN Data Rate (3) parameter in the module.
Important: Refer to Appendix B, DeviceNet to SCANport
Communication Module with Digital Inputs Parameters, for
information on changing the node address or data rate.
If you wish to change other functions (e.g., Fault Configurable inputs)
or add more functions (e.g., datalinks), you must edit the adapters
parameters. To do so, refer to:

What is RSNetWorx for

DeviceNet?

Appendix B, DeviceNet to SCANport Communication Module

with Digital Inputs Parameters, for detailed information about the
adapters parameters.

Instructions in this chapter on using RSNetWorx for DeviceNet to

edit parameters.

RSNetWorx for DeviceNet is a Windows application that lets you

configure DeviceNet networks. Using a graphical representation of
your network, you can configure network-wide parameters and the
network-wide schedule.
After installing or mounting the adapter, you can use RSNetWorx for
DeviceNet to configure or edit the adapters parameters.

Required Equipment and

Software

Publication 2100-UM001A-US-P January 2000

Before configuring or editing your adapters parameters, your PC

must be:

Running RSNetWorx for DeviceNet. Refer to

http://www.software.rockwell.com for more information on this
product.

Connected to and communicating with the DeviceNet network

using a 1784-PCD card or a 1770-KFD adapter running with
RSLinx. Refer to http://www.software.rockwell.com for more
information on the RSLinx product.

Configuring the DeviceNet to SCANport Communication Module with Digital Inputs

Using RSNetWorx to Edit Your

Adapters Parameters

3-3

The following instructions describe how to use RSNetWorx for

DeviceNet in online mode to edit your adapters parameters.
1. Use RSLinx to configure the DeviceNet drivers for your system
using the Configure Drivers option in the Communications
menu.
2. Start RSNetWorx for DeviceNet. The RSNetWorx for DeviceNet
screen appears as seen in Figure 3.1.
Figure 3.1
RSNetWorx for DeviceNet Screen

3. In the Network menu, select Online, or click on the Online icon

as indicated in Figure 3.2.
4. The Browse Network screen appears asking to select which
network you wish to go online with. Select the DeviceNet
network desired and click on OK.

Publication 2100-UM001A-US-P January 2000

3-4

Configuring the DeviceNet to SCANport Communication Module with Digital Inputs

Figure 3.2
Online Screen

Step #3

Step #4

5. The network will be scanned and the screen will build the online
configuration as shown in Figure 3.3.
Figure 3.3
RSNetWorx Graphical View

In Figure 3.3, Node 00 is scanner, Node 62 is the PC, and Node 63 is

the module we are configuring.
Your module appears as Node 63 by default. If you have changed its
node address parameter and reset the module, its new node address
will appear on the screen.
Publication 2100-UM001A-US-P January 2000

Configuring the DeviceNet to SCANport Communication Module with Digital Inputs

3-5

Important: If the module does not appear:

Verify there is an EDS file for the device, refer to Creating

and EDS file for your SCANport Product section in
Chapter 4, Configuring a Scanner to Communicate with the
Adapter.

Verify that the device has a unique node address. Check the
network LED on the module. If it is red, it is not an unique
address. You must configure the module in a point-to-point
connection.

6. Double-click the icon for the 2100-GK61 module. (In our

example, it is node 63 in Figure 3.3.
The DeviceNet Configuration screen appears for the selected device.
The screen has three tabs to choose from, General, Device
Parameters, and EDS I/O Default.
The General tab allows you to give the device a name and to add
description about the device. These names and description will be
used to represent and describe the product throughout RSNetWorx for
DeviceNet.
The DeviceNet Parameters and EDS I/O Default tabs allows you to
see the parameters and configuration of the device selected.
7. Click on the Device Parameters tab. A dialog box requesting to
upload or download the devices parameters appears. Click on the
Upload button, this causes the parameters to be uploaded from
the module. The Screen listing all the devices parameters
appears. In this example the 2100-GK61 is configured with an
SMP3 device.
Figure 3.4
Device Parameters, all

Step #7

Publication 2100-UM001A-US-P January 2000

3-6

Configuring the DeviceNet to SCANport Communication Module with Digital Inputs

8. Click on the Groups pull-down arrow and select DeviceNet

Module. The display changes, listing only the parameters
associated with the 2100-GK61.
Figure 3.5
Device Parameters, Module Only

Step #10
Step #8

Step #9

Step #11

9. Double click on the parameter(s) you wish to edit. Change the

data to the desired value, refer to Appendix B for acceptable
values for each parameter. A lock icon indicates that the
parameter is read only and cannot be changed.
10. Click on the Download to Device button to save the changes
made to the module.
Important: It may be necessary to reset the adapter for the changes
to take effect. Refer to Appendix B to see if the parameter you
changed required the module to be reset in order to take effect.
11. Click on the OK button to return to the graph screen.

Publication 2100-UM001A-US-P January 2000

Chapter

Configuring a Scanner to
Communicate with the Adapter
Chapter Objectives

Chapter 4 provides instructions for configuring your scanner to

communicate with the 2100-GK61 module. This allows the product
connected to the adapter to be an active node on the DeviceNet
network. In this chapter, you will read about the following:

RSNetWorx for DeviceNet software.

Equipment and software needed for the configuration.

Configuring either a PLC or SLC scanner to communicate with

the adapter.

This chapter assumes you have experience using RSNetWorx for

DeviceNet to configure a DeviceNet network.

What is RSNetWorx for

DeviceNet?

RSNetWorx for DeviceNet is a Windows application that lets you

configure DeviceNet networks. Using a graphical representation of
your network, you can configure network-wide parameters and the
network-wide schedule.
After installing and configuring the DeviceNet to SCANport
Communication Module with Digital Inputs, you can use RSNetWorx
for DeviceNet to configure the scanner to recognize and communicate
with it.
For more information on RSNetWorx for DeviceNet, refer to the
RSNetWorx for DeviceNet online help.

Required Equipment and

Software

Before configuring the scanner, your PC must be:

Running RSNetWorx for DeviceNet. Refer to

http://www.software.rockwell.com for more information on this
product.

Connected to and communicating with the DeviceNet network

using a 1784-PCD card or a 1770-KFD adapter running with
RSLinx. Refer to http:www.software.rockwell.com for more
information.

Publication 2100-UM001A-US-P January 2000

4-2

Configuring a Scanner to Communicate with the Adapter

Getting Started

For the scanner on the DeviceNet network to transmit control I/O

and/or messages to the adapter, you must first configure it to
recognize and communicate with the adapter.
The following instructions describe how to use RSNetWorx for
DeviceNet to configure a new DeviceNet network in online mode.
The main steps in the configuration are:

Using Online Mode in

RSNetWorx for DeviceNet

Using online mode in RSNetWorx for DeviceNet.

Creating an EDS file for your SCANport product (if necessary).

Configuring the PLC scanner or SLC scanner.

Although you can configure the DeviceNet network offline, it is

easier to configure the network online because you can see a
graphical representation of your network in RSNetWorx for
DeviceNet. The following directions explain how to use online mode.
1. Start RSLinx to configure the DeviceNet Drivers for your system
using the Configure Drivers option in the Communications
menu.
2. Start RSNetWorx for DeviceNet. The RSNetWorx for DeviceNet
screen appears.
Figure 4.1
RSNetWorx for DeviceNet Screen

Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

4-3

3. In the Network menu, select Online, or click on the Online icon

as indicated to Figure 4.2.
4. The Browse Network screen appears requesting which network
you wish to go online with. Select the DeviceNet network desired
and click on OK.
Figure 4.2
Online Screen

Step # 3

Step # 4

5. The network will be scanned and the screen will build the online
configuration as shown in Figure 4.3.
Figure 4.3
Online Graphical View

Important: In our example, our module is Node 3. It has a

Unrecognized Device icon, and the error code lists it as an
unregistered device, so we will need to create an EDS file for it.

Publication 2100-UM001A-US-P January 2000

4-4

Configuring a Scanner to Communicate with the Adapter

You are now in online mode. You must check and see if you need an
EDS file for the device you are adding. Refer to the Creating an EDS
file for Your SCANport product selection in this chapter.

Creating an EDS File for Your

SCANport Product

EDS (Electronic Data Sheet) files are specially formatted ASCII files
that provide all the information necessary for a configuration tool
such as RSNetWorx for DeviceNet to access and alter the parameters
of a device. Information about each parameter (e.g. parameter min.,
max., and default values, parameter data format and scaling, and the
parameter name and units) is contained in this file.
To upload the EDS file, you need to:
1. Click on the icon of the unrecognized device, in our example it is
Node 3.
2. In the Device mode select Register Device.
Figure 4.4
Register Device Screen

Step #2

This starts the EDS Installation Wizard which will allow you to
upload EDS text from an unknown online device. Click on the Next
button to continue.
3. Select the Upload EDS option by clicking on the open circle next
to the description. The circle fills in with a solid dot.
4. Click on the Next button.

Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

4-5

Figure 4.5
EDS Upload Option Screen

Step #3
Step #4

5. At the DeviceNet description Screen enter the catalog number

that is associated with the product. For this example we have a
2100-GK61 communication module connected to a 193-C1H1
SMP-3. We will add both catalog numbers to the description,
enter 2100-GK61/193-C1H1.
6. Click on the Next button.
Figure 4.6
EDS DeviceNet Description Screen

Step #5
Step #6

7. We now enter the devices I/O characteristics. Click on the

Enable box for the polled connection, an 4 appears in the box.
8. Enter 4 in the Input Size and Output Size fields. These are the
default I/O conditions for products using a 2100-GK61 module.

Publication 2100-UM001A-US-P January 2000

4-6

Configuring a Scanner to Communicate with the Adapter

9. Click on the Next button.

Figure 4.7
EDS I/O Configuration Screen

Step #7
Step #8
Step #9

10. The EDS Wizard now uploads the following from the attached
devices.

Parameter Description Data

Parameters

Enumerated Strings

Group Information

11. The dialog box provides status information on the overall upload
of information from the devices.
12. Click on the Next button.

Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

4-7

Figure 4.8
EDS Upload Status Screen

Step #11
Step #12

13. The Change Icon screen now appears. Here we will be able to
select an icon that best represents the connected devices for the
graph presentation of the network.
14. Select the device description you wish to change. In this example
we click on the SMP via 2100-GK61.
15. Click on the Change icon...button.
Figure 4.9
EDS Change Icon Screen

Step #15

Step #14

16. Pictures of various icons appear. Select the icon by clicking on it

which best represents your device. In this example we will chose
an icon that appears similar to an SMP relay.
17. Click on the OK button.

Publication 2100-UM001A-US-P January 2000

4-8

Configuring a Scanner to Communicate with the Adapter

Figure 4.10
EDS Icon Selection Screen

Step #16

Step #17

The graphical description is uploaded to reflect the change just

selected.
18. Click on the Next button.
Figure 4.11
EDS Icon Screen Updated

Step #18

The EDS installation Wizard now informs you that you have
successfully completed the installation of the EDS file for the device.
19. click on the Finish button.

Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

4-9

Figure 4.12
EDS Installation Complete Screen

Step #19

The program updates the EDS registry for the computer and redraws
the graphical representation of the device with the new icon as shown
in Figure 4.13.
Figure 4.13
Updated Online Screen

20. Double click on the Node 3 icon just updated and the Device
configuration screen appears.

Publication 2100-UM001A-US-P January 2000

4-10

Configuring a Scanner to Communicate with the Adapter

Figure 4.14
Device Configuration Screen

Step #20

Step #21

Important: This screen allows you to edit any of the parameters in

the SMP or adapter itself. Refer to Chapter 3, Configuring the
DeviceNet to SCANport Communication Module with Digital Inputs,
for information on editing parameters.
21. Click on the Cancel button, The online Screen appears.
Once all your devices have registered EDS files for RSNetWorx to
use do one of the following.

Configuring a PLC Scanner

To configure the scanner, you verify its properties, add devices on the
network to its scan list, and determine how the scanner will
communicate (e.g., polling) with each device. Follow these
directions:
If Using:

Refer To:

PLC Scanner (1771-SDN)

Go to Configuring a PLC Scanner (1771-SDN) to

Communicate with the Adapter on page

SLC Scanner (1747-SDN)

Go to Configuring a SLC Scanner (1747-SDN) to

Communicate with the Adapter on page

RSNetworx for DeviceNet to

edit parameters.

Go to Chapter 3, Configuring the DeviceNet to

SCANport Communication Module with Digital
Inputs

Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

Configuring a PLC Scanner

(1771-SDN) to Communicate
with the Adapter.

4-11

The following instructions describe how to configure a PLC scanner

on a DeviceNet network.
Important: If you are using a SLC scanner (1747-SDN), skip this
section and refer to the Configuring a SLC (1747-SDN) to
Communicate with the Adapter section on page 4-17.
For the PLC to recognize your device, you must do the following:

Configure the PLC scanner.

Map your adapter to the PLC scanner (1771-SDN).

1. In the Online screen, double-click on the scanner icon. The 1771SDN Scanner Module properties and configuration screen appear.
Figure 4.15
1771-SDN Configuration Dialog Box

The dialog box contains 6 data tabs which are used to configure
various portions of the scanner. The General tab allows the user to
edit the name and descriptions of the scanner. The Module tab allows
the use to configure the scanner set up properties. The Scanlist tab
allows the user to choose which components the scanner will scan for
data. The Input and Output tab is where the user sets up where the
data from the scanned devices is kept to be used by the PLC
processor. Finally, the Summary tab allows the user to view a concise
summary of how the scanner has been configured.
2. On the General page place the cursor in the name field and type
the name you want to assign the scanner. If you want to add a
description to the scanner place the cursor in the description field
and enter a description. Click on the Apply button to save the
information.

Publication 2100-UM001A-US-P January 2000

4-12

Configuring a Scanner to Communicate with the Adapter

3. Click on the Module tab. A dialog box will appear requesting to

upload, or download information from the scanner. Click on the
Upload. All the scanlist information currently stored in the
scanner will be uploaded. Once the upload is complete the
Module screen will appear.
Figure 4.16
1771 SDN Module Screen

Step #4

Verify the default values listed on this page. Edit them as necessary.
Refer to RSNetworx for DeviceNet online help for more information.
4. Click Apply to save any information that you can change.
5. Click on the Scanlist tab, the Scanlist page appears.
Figure 4.17
Scanlist Screen

Step #6

Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

4-13

6. Select the available devices you wish to add to the scan list.
Verify that the Automap on Add box is checked. This will map
the devices into the scanners memory automatically when added.
Refer to the RSNetWorx for DeviceNet help menu for additional
information on automapping. Once a device is selected click on
the Add (>) or Add All (>>) button.
Figure 4.18
Scanlist Configuration Screen

Step #6
Step #7

7. Modify each devices I/O parameters if needed. Select the device

and click on the Edit I/O Parameters button. The I/O Parameters
dialog screen appears. As shown in Figure 4.19.
Figure 4.19
I/O Configuration Edit Screen

Publication 2100-UM001A-US-P January 2000

4-14

Configuring a Scanner to Communicate with the Adapter

8. Make the changes as necessary. You must configure your PLC

based on how your adapters parameters are configured and how
you want your module to send and receive data from the network.
Refer to the following table:
If Using:

Refer To:

Polled

Polled Allocation on page B-5.

COS (Change of State)

COS (Change of State) Allocation on page B-7.

Cyclic

Cyclic Allocation on page B-8.

Polled and COS

Polled and COS Allocation on page B-10.

Polled and Cyclic

Polled and Cyclic Allocation on page B-11.

9. Click on OK, to return to the Scanlist screen.

10. Click on the Apply button. A dialog box appears asking if you
wish to download the changes to the device. Click on Yes.
Important: If the processor is not in Program mode a dialog box will
appear stating which mode the processor is in. Clicking on the OK
button returns your the Scanlist screen without downloading any
information to the processor. You must now place the processor in
program mode and repeat the apply function.
11. Click on the Input tab to view the input table map. From this
screen you can customize the arrangement of the scanners data
table. Refer to the RSNetWorx online help for additional
information. As shown in Figure 4.20.
Figure 4.20
Input Data Table Map Screen

Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

4-15

12. Click on the Output tab to view the output table map. From this
screen you can customize the arrangement of the scanners data
table. Refer to the RSNetWorx online help for additional
information. As shown in Figure 4.21.
Figure 4.21
Output Data Table Map Screen

Publication 2100-UM001A-US-P January 2000

4-16

Configuring a Scanner to Communicate with the Adapter

13. Click on the Summary tab. This screen provides the user with a
concise summary of how the scanner has been configured. Note:
all of the information that appears on this page is read only. If you
want to change any of the parameters, you have to edit them on
the appropriate property page. As shown in Figure 4.22.
Figure 4.22
Summary Screen

14. Click on the OK button. You are returned to the online screen.
15. To save the information just entered to your computer select
Save As under the File menu.
16. Select a path to store the information.
17. Enter a file name and click on Save.
Figure 4.23
Save as a Dialog Screen

Step #15

Step #17

Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

4-17

Your device is now configured on the DeviceNet network. The

network LED on the module is solid green. If it is not, refer to
Chapter 7, Troubleshooting, for more information.
Refer to Chapter 5, Ladder Logic Programming, for information on
creating a PLC Ladder Logic Program.

Configuring an SLC Scanner

(1747-SDN) to Communicate
with the Adapter

The following instructions describe how to configure an SLC scanner

on a DeviceNet network.
Important: If you are using a PLC scanner (1771-SDN), skip this
section and refer to the Configuring a PLC Scanner (1771-SDN) to
Communicate with the Adapter. As shown on page 4.11.
For the SLC to recognize your device, you must do the following:

Configure the SLC Scanner.

Map your adapter to the SLC (1747-SDN).

Configuring an SLC Scanner

To configure the scanner, you verify its properties, add devices on the
network to its scan list, and determine how the scanner will
communicate (e.g., polling) with each device. Follow these
directions:
1. In the Online screen, double-click on the scanner icon. The
1747-SDN Scanner Module properties and configuration screen
appears. As shown in Figure 4.24.
Figure 4.24
1747-SDN Configuration Dialog Box

Publication 2100-UM001A-US-P January 2000

4-18

Configuring a Scanner to Communicate with the Adapter

The dialog box contains 6 data tabs which are used to configure
various portions of the scanner. The General tab allows the user to
edit the name and descriptions of the scanner. The Module tab allows
the user to configure the scanner set-up properties. The Scanlist tab
allows the user to choose which components the scanner will scan for
data. The Input an Output tab is where the user sets up where the
data from the scanned devices is kept to be used by the SLC
processor. Finally the Summary tab allows the user to view a concise
summary of how the scanner has been configured.
2. On the General page place the cursor in the name field and type
the name you want to assign to the scanner. If you want to add a
description to the scanner place the cursor in the description field
and enter a description. Click on the Apply button to save the
information.
3. Click on the Module tab. A dialog box will appear requesting to
upload, or download information from the scanner. Click on the
Upload. The scanlist information currently stored in the scanner
will be uploaded. Once the upload is complete the Module screen
will appear.
Figure 4.25
1747-SDN Module Configuration Screen

Step #4

Verify the default values listed on this page. Edit them as necessary.
Refer to RSNetWorx for DeviceNet online help for more information.
4. Click Apply to save any information that you change.
5. Click on the Scanlist tab, the Scanlist page appears.

Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

4-19

Figure 4.26
1747-SDN Scanlist Configuration Screen

Step #6

6. Select the available devices you wish to add to the Scanlist. Verify
that the Automap on Add box is checked. This will map the
devices into the scanners memory automatically when added.
Refer to the RSNetWorx for DeviceNet help menu for additional
information on automapping. Once a device is selected click on
the Add (>) or Add All (>>) button.
Figure 4.27
Scanlist Configuration Screen

Step #7

Publication 2100-UM001A-US-P January 2000

4-20

Configuring a Scanner to Communicate with the Adapter

7. Modify each devices I/O parameters if needed. Select the device

and click on the Edit I/O Parameters button. The I/O Parameters
dialog screen appears. As shown is Figure 4.28.
Figure 4.28
I/O Configuration Edit Screen

8. Make the changes as necessary. You must configure your PLC

based on how your adapters parameters are configured and how
you want your module to send and receive data from the network.
Refer to the following table.
If Using:

Refer To:

Polled

Polled Allocation on page B-5.

COS (Change of State)

COS (Change of State) Allocation on page B-7.

Cyclic

Cyclic Allocation on page B-8.

Polled and COS

Polled and COS Allocation on page B-10.

Polled and Cyclic

Polled and Cyclic Allocation on page B-11.

9. Click on OK, to return to the Scanlist screen.

10. Click on the Apply button. A dialog box appears asking if you
wish to download the changes to the device. Click on Yes.
Important: If the processor is not in Program mode a dialog box will
appear stating which mode the processor is in. Clicking on the OK
button returns you to the Scanlist screen without downloading any
information to the processor. You must now place the process in the
program mode and repeat the apply function.

Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

4-21

11. Click on the Input tab to view the input table map. From this
screen you can customize the arrangement of the scanners data
table. As shown in Figure 4.29. Refer to the RSNetWorx online
help for additional information.
Figure 4.29
Input Data Table Mapping Screen

Step #12

Publication 2100-UM001A-US-P January 2000

4-22

Configuring a Scanner to Communicate with the Adapter

12. Clicking on the Advanced button moves to the advance memory

mapping screen. From this screen you can specify where to map
the data to.
13. Selecting the Memory Arrow under the Map To: allows you to
select Discrete or M File Memory. This example leaves the
mapping in discrete memory.
Figure 4.30
Advanced Mapping Screen

Step #13

14. Click on the Output tab to view the output table map. From this
screen you can customize the arrangement of the scanners data
table. As shown is Figure 4.31. Refer to the RSNetWorx online
help for additional information.
Figure 4.31
Output Data Table Mapping Screen

15. Click on the Summary tab. This screen provides the user with a
concise summary of how the scanner has been configured. Note:
All of the information that appears on this page is read only. If
you want to change any of the parameters, you have to edit them
on the appropriate property page.
Publication 2100-UM001A-US-P January 2000

Configuring a Scanner to Communicate with the Adapter

4-23

Figure 4.32
Summary Screen

16. Click on the OK button. You are returned to the online screen.
17. To save the information, just entered to your computer select
Save As under the File menu.
18. Select a path to store the information
19. Enter a file name and click on Save.
Figure 4.33
Save As Dialog Screen

Step #17

Step #19

Publication 2100-UM001A-US-P January 2000

4-24

Configuring a Scanner to Communicate with the Adapter

Your device is now configured on the DeviceNet network. The

network LED on the module is solid green. If it is not, refer to
Chapter 7, Troubleshooting, for more information.
Refer to Chapter 5, Ladder Logic Programming, for information on
creating a PLC Ladder Logic Program.

Publication 2100-UM001A-US-P January 2000

Chapter

Ladder Logic Programming

Chapter Objectives

Chapter 5 provides information needed to create the PLC or SLC

Ladder Logic program that the controller will use to transmit control
I/O and messages to and from the SCANport product. In this chapter,
you will read about the following:

Equipment and software needed to create either a PLC or SLC

ladder logic program.

PLC and SLC ladder logic programs.

Creating a PLC or SLC ladder logic program.

This chapter assumes you are familiar with the hardware components
and programming procedures necessary to operate DeviceNet and
SCANport devices, including the following:

PLC-5 or SLC-500.

1771-SDN or 1747-SDN scanner.

Ladder programming.

RSLogix5 (for PLC-5) and RSLogix500 (for SLC-5/02 through

SLC 5/05).

You may need to refer to the documentation associated with these

products to create a ladder logic program.

Required Equipment

What is RSLogix?

Before creating a ladder logic program for the PLC or SLC, your PC
must be:

Running RSLogix5 and RSLinx if using a PLC. Refer to

http://www.software.rockwell.com for more information on these
products.

Running RSLogix500 and RSLinx if using an SLC. Refer to

http://www.software.rockwell.com for more information on these
products.

Connected to and communicating with the DeviceNet network

using a 1784-PCD card or a 1770-KFD adapter.

RSLogix5 (for the PLC-5) and RSLogix500 (for the SLC-5/03)

software let you create the ladder logic programs you need and
download them to the PLC or SLC. They also let you monitor the
program as the PLC or SLC is using it.

Publication 2100-UM001A-US-P January 2000

5-2

Ladder Logic Programming

For more information on RSLogix5 or RSLogix500, consult the

respective softwares documentation.

What are Ladder Logic

Programs?

A PLC or SLC ladder logic program lets you control the drive and the
messaging from the PLC or SLC to the drive. Figure 5.1 shows how
the I/O image table for a DeviceNet scanner relates to the 1336 PLUS
drive when an DeviceNet to SCANport Communication Module with
Digital Inputs is used.
Figure 5.1
I/O Image Table
DeviceNet

PLC,
SLC,
PC

Scanner

Output
Mapping
(Write)

Input
Mapping
(Read)

Message
Handler

SCANport

2100-GK61
Enhanced DeviceNet

1336 PLUS Drive

Word 0
Word 1
Word 2
Word 3
Word 4
Word 5
Word 6
Word 7
Word 8
Word 9

Logic Command
Reference
Datalink A1
Datalink A2
Datalink B1
Datalink B2
Datalink C1
Datalink C2
Datalink D1
Datalink D2

Logic Command
Block
Reference
Data In A1
Data In A2
Data In B1
Data In B2
Data In C1
Data In C2
Data In D1

Word 0
Word 1
Word 2
Word 3
Word 4
Word 5
Word 6
Word 7
Word 8
Word 9

Logic Status
Feedback
Datalink A1
Datalink A2
Datalink B1
Datalink B2
Datalink C1
Datalink C2
Datalink D1
Datalink D2

Logic Status
Feedback
Data Out A1
Data Out A2
Data Out B1
Data Out B2
Data Out C1
Data Out C2
Data Out D1
Data Out D2

Message
Buffers

Message Handler

Important: Datalinks are optionally enabled in the adapter and configured in the product. Refer to
Chapter 3, Configuring the DeviceNet to SCANport Communication Module with Digital Inputs and
your products user manual for more information.

Publication 2100-UM001A-US-P January 2000

Ladder Logic Programming

Example Ladder Logic

Programs

5-3

The following are example ladder logic programs for a 1305, 1336
PLUS, or 1336 PLUS II drive.

ATTENTION: The example ladder logic program

shown in this manual is intended solely for purpose of
example. Because there are many variables and
requirements associated with any particular installation,
Rockwell Automation does not assume responsibility or
liability (to include intellectual property liability) for
actual use based upon the example shown in this
publication.

Important: Refer to the user manual for your SCANport product for
specific I/O definitions. Different SCANport products have different
Logic Command, Logic Status, Reference and Feedback I/O
interpretations.

Publication 2100-UM001A-US-P January 2000

5-4

Ladder Logic Programming

The 1305, 1336 PLUS, or 1336 PLUS II drive in this example accepts
the following Logic Command Data from the controller.
Logic Status Bits
Function
15

14

13

12

11

10

X Stop
X
X
X
X

X
X
X
X
X

Description

1=Stop, 0=No Operation

Start

1=Start, 0=No Operation

Jog

1=Jog, 0=No Operation

Clear Faults

1=Clear, 0=No Operation

Direction

00=No Operation, 01=Forward,

10=Reverse

Local

1=Local, 0=Multiplexed

MOP Increment

1=Increment MOP, 0=No Operation

Accel Rate Select 00=No Operation, 01=Rate 1, 10=Rate 2

Decel Rate Select 00=No Operation, 01=Rate 1, 10=Rate 2

Reference
Selection

000=No Operation
001=External Reference 1 (Par 5)
010=External Reference 2 (Par 6)
011=Preset 3
100=Preset 4
101=Preset 5
110=Preset 6
111=Preset 7

MOP Decrement

1=Decrement MOP, 0=No Operation

The 1305, 1336 PLUS, or 1336 PLUS II drive in this example sends
the following Logic Status Data to the PLC.
Logic Status Bits
Function
15

14

13

12

11

10

X
X
X
X
X
X
X
X
X
X

Publication 2100-UM001A-US-P January 2000

Description

0
Enabled

1=Enabled, 0=Not Enabled

Running

1=Running, 0=Not Running

Command
Direction

1=Forward, 0=Reverse

Rotating Direction 1=Forward, 0=Reverse

Acceleration

1=Accelerating, 0=Not

Deceleration

1=Decelerating, 0=Not

Warning

1=Warning Present, 0=Not

Fault

1=Faulted, 0=Not Faulted

At Reference

1=At Speed, 0=Not At Speed

Local

000=Terminal I/O has Local

001=Port 1 has Local
010=Port 2 has Local
011=Port 3 has Local
100=Port 4 has Local
101=Port 5 has Local
110=Port 6 has Local
111=Multiplexed Control

Reference Source 0000=External Reference 1

0001 0111=Presets 1 7
1000=External Reference 2
1001 1110=Port 1 6 Direction
1111=Jog

Ladder Logic Programming

5-5

PLC Ladder Logic Example

The following example uses a PLC-5, a 1771-SDN DeviceNet
scanner, and a 2100-GK61 to control a 1305, 1336 PLUS, or 1336
PLUS II drive.
The example program shows how to obtain status information from
the drive and how to control it (e.g., starting the drive, stopping the
drive, jogging the drive, sending reference, and clearing faults). When
you understand this example, you should be able to customize the
program to fit you application needs.
The example assumes that there is an operators station wired to an
I/O module in slot zero of module group zero of rack zero.
Important: You may want to verify a device has not failed using
word 0 of block transfer 62 before sending control data. If a device
has failed, use block transfer 52 to find out which device failed. Refer
to the 1771-SDN DeviceNet Scanner Module Manual, Publication
1771-5.14, for more information.
Figure 5.2
Example PLC Ladder Logic Program

0000

The scanner gathers drive status information via DeviceNet.

The Block Transfer Read in this rung then moves the drive status data from the scanner to the PLCs N9 data file.
BT20:0
BTR
Block Transfer Read
EN
Module Type Generic Block Transfer
Rack
000
Group
0
Module
0
Control Block
BT20:0
Data File
N9:0
Length
62
Continuous
No

EN
DN
ER

Rungs 0001 through 0003 move the drive status from the Block Transfer Read data file to an operator display.
1305 Drive
Operator Display
RUNNING
Drive Running
Status Bit
Status Bit
O:000
N9:1
0001
10

1
1305 Drive
FAULTED
Status Bit
N9:1

Operator Display
Drive Faulted
Status Bit
O:000

0002
11

0003

Operator Display
Drive Feedback
Status Word
MOV
Move
Source
Dest

N9:2
0<
N21:1
0<

Publication 2100-UM001A-US-P January 2000

5-6

Ladder Logic Programming

Figure 5.2
Example PLC Ladder Logic Program (Continued)
This rung enables the scanner.
1771-SDN Scanner
Port A Enable
N10:0
0004
0
Rungs 0005 through 0009 move the operators inputs from the operator station to the Block Transfer Write data file
where they will be sent to the scanner and out to the drive via DeviceNet.
1305 Drive
Operator Input
START
Drive Start
Command Bit
Command Bit
N10:1
I:000
0005
10

Operator Input
Drive Stop
Command Bit
I:000

1305 Drive
STOP
Command Bit
N10:1

11

0006
Operator Input
Drive Jog
Command Bit
I:000

1305 Drive
JOG
Command Bit
N10:1

12

0007
1305 Drive
CLEAR FAULT
Command Bit
N10:1

Operator Input
Drive Clear Faults
Command Bit
I:000
0008

13
1305 Drive
REFERENCE
Command Word
MOV
Move
Source

0009

N21:0
0<
N10:2
0<

Dest

The Block Transfer Write in this rung send the drive command data to the scanner and out to the drive via DeviceNet.
BT20:0
BTW
EN
Block Transfer Write
EN
Module Type Generic Block Transfer
DN
Rack
000
Group
0
ER
Module
0
Control Block
BT20:1
Data File
N10:0
Length
62
Continuous
No

0010

END

0011

The following table represents the control file for the block transfers.
Offset

EN

ST

DN

ER

CO

EW

NR

TO

RW

RLEN

DLEN

FILE

ELE
M

BT20:0

62

00

BT20:1

62

10

00

Publication 2100-UM001A-US-P January 2000

Ladder Logic Programming

5-7

SLC Ladder Logic Program Example

The following example uses a SLC-5/03, a 1747-SDN DeviceNet
scanner, and a 2100-GK61 to control a 1336 PLUS, 1336 PLUS II or
1305 drive.
The example assumes that there is an operators station wired to an
I/O module in slot one of module group zero of rack zero.
Important: You may want to verify a device has not failed using
word I:S.0. If a device has failed, read the appropriate M1 File to find
out which device failed. Refer to the 1747-SDN DeviceNet Scanner
Module Manual, Publication 1747-5.8, for more information.
Figure 5.3
Example SLC Ladder Logic Program

0000

The scanner gathers drive status information via DeviceNet.

The M-File is copied into the SLCs N9 data file to move the drive status information into a convenient location.
COP
Copy File
Source
#M1:1.0
Dest
#N9:0
Length
128
Rungs 0001 through 0003 move the drive status from the N9 data file to an operator display.
1336PLUS
RUNNING
Status Bit
N9:0

Operator Display
Drive Running
Status Bit
O:3.0

0001
1
1336PLUS
FAULTED
Status Bit
N9:0

0
1746-O*8
Operator Display
Drive Faulted
Status Bit
O:3.0

0002
7

0003

1
1746-O*8
Operator Display
Drive Feedback
Status Word
MOV
Move
Source
N9:2
0<
Dest
N21:1
0<

Publication 2100-UM001A-US-P January 2000

5-8

Ladder Logic Programming

Figure 5.3
Example SLC Ladder Logic Program (Continued)
Rungs 0004 through 0008 move the operators inputs from the operator station to the N9 data file where they will be sent to the s
and out to the drive via DeviceNet.
Operator Input
1336PLUS
Drive Start
START
Command Bit
Command Bit
N10:0
I:2.0
0004
1

0
1746-I*16
Operator Input
Drive Stop
Command Bit
I:2.0

1336PLUS
STOP
Command Bit
N10:0

0005
0

1
1746-I*16
Operator Input
Drive Jog
Command Bit
I:2.0

1336PLUS
JOG
Command Bit
N10:0

0006
2

2
1746-I*16
Operator Input
Drive Clear Faults
Command Bit
I:2.0

1336PLUS
CLEAR FAULTS
Command Bit
N10:0

0007
3

3
1746-I*16

1336PLUS
REFERENCE
Command Word
MOV
Move
Source

0008

Dest

N21:0
0<
N10:1
0<

This rung enables the scanner. (Changes the scanner into RUN mode)
1747-SDN
Scanner
Enable
Bit
O:1.0
0009
0
1747-SDN
This rung copies the drive command data to the scanner and out to the drive via DeviceNet.
0010

0011

Publication 2100-UM001A-US-P January 2000

COP
Copy File
Source
Dest
Length

#N10:0
#M0:1.0
128

END

Chapter

Using DeviceNet Explicit

Messaging
Chapter Objectives

Chapter 6 provides information you need to monitor and configure

the SCANport device using explicit messaging on DeviceNet. In this
chapter, you will read about the following:

Required equipment.

Message translations.

Messaging guidelines for the 1771-SDN scanner.

Messaging guidelines for the 1747-SDN scanner.

Example messages.

Using messages to control SCANport products.

Writing to register objects.

Refer to Appendix C, DeviceNet Objects, for information on object

data support.

Required Equipment

Explicit Message Program

Control for PLC-5

Before using messaging, your PC must be:

Running Logix5 and RSLinx if you are using a PLC. Refer to

http://www.software.rockwell.com for more information on these
products.
-ORRunning RSLogix500 and RSLinx if you are using an SLC. Refer
to http://www.software.rockwell.com for more information on
these products.

Connected to and communicating with the DeviceNet network

using a 1784-PCD card or a 1770-KFIO adapter.

Use the Explicit Message Program Control feature to configure

device parameters on your DeviceNet network via the ladder logic
program in the PLC-5 processor that is controlling these devices.
You can use Explicit Message Program Control only with devices that
are slaves of your 1771-SDN Scanner Module. These slave devices
must be mapped in the scanner modules scan list.
Use the Explicit Message Program Control feature to:

Transmit configuration data from your scanner module to its slave

devices on your DeviceNet network

Publication 2100-UM001A-US-P January 2000

6-2

Using DeviceNet Explicit Messaging

Receive status and diagnostics from these devices on our

DeviceNet network

Make runtime adjustments to device parameters according to

changing conditions detected by your processor

Figure 6.1
How the Explicit Message Program Control Feature Works

2100-GK61
Communication Adapter

1. You format a Block Transfer Write file in the processor to send an

Explicit Message Request to the scanner module (download).
2. The scanner module transmits the Explicit Message Request to
the slave device over the DeviceNet network.
3. The slave device transmits the Explicit Message Response back
to the scanner and is queued into a block transfer buffer.
4. The processor uses a Block Transfer Read file to retrieve the
explicit Message Response from the scanners buffer (upload).
5. The Block Transfer Read file is completed. The transaction IDs
are deleted and can be reused.
Publication 2100-UM001A-US-P January 2000

Using DeviceNet Explicit Messaging

6-3

The scanner module requires a precisely-formatted block transfer

read and write size of 64 words. The Explicit Message Control table
in the scanner module is 64 words. The scanner module uses the
block transfer size as an indicator that the content is a client/server
request.

Message Translations

The communications adapter provides electronic translations of

DeviceNet explicit messages into SCANport messages and back. The
format of all DeviceNet explicit messages supported by the adapter is
8:16: within an explicit message, the class field is 8 bits long, and the
instance field is 16 bits long.

Messaging for the 1771-SDN

Scanner

The PLC uses a 64-word Block Transfer Write (BTW) to copy an

Explicit Message into the 1771-SDN scanner. Ten explicit message
buffers are available within the 1771-SDN scanner. When the BTW
completes, the scanner executes the message. The PLC must then poll
the scanner by performing a 64-word Block Transfer Read (BTR) to
complete the message. (Note: Both the BTW and BTR commands are
module type 1771-SDN DeviceNet Scanner Module and of length
64. The PLC can transfer two Explicit Messages per BTW or BTR
and the scanner can have up to 10 Explicit Messages active at any
time.)
When the BTR completes, the data received by the PLC will contain
information about the status of the current Explicit Message being
processed by the scanner. If an Explicit Message has completed, the
STATUS code in the Explicit Message Response is set to 1 and the
response message contains the data requested.
If the message status indicates that it is not completed, the BTR
should be repeated until the message is complete.
The format of Request and Response Data File messages is in Figure
6.2.

Publication 2100-UM001A-US-P January 2000

6-4

Using DeviceNet Explicit Messaging

Figure 6.2
Format of DeviceNet Messages
Format of 64-word Block Transfer
Write for Explicit Message Request
15
Transaction #1
Header
(3 words)

Transaction #2
Body (up to
29 words)

15

TXID

COMMAND

TXID

STATUS

PORT

SIZE

PORT

SIZE

SERVICE

MAC ID

SERVICE

MAC ID

Transaction #1
Body (up to
29 words)

Transaction #2
Header
(3 words)

Format of 64-word Block Transfer

Read for Explicit Message Response

CLASS

SERVICE RESPONSE DATA

INSTANCE

"

ATTRIBUTE

"

SERVICE DATA

"

"

"

word 31

TXID

COMMAND

TXID

STATUS

PORT

SIZE

PORT

SIZE

SERVICE

MAC ID

SERVICE

MAC ID

CLASS

SERVICE RESPONSE DATA

INSTANCE

"

ATTRIBUTE

"

SERVICE DATA

"

"

"

Publication 2100-UM001A-US-P January 2000

word 0

word 32

word 63

Using DeviceNet Explicit Messaging

6-5

Transaction Blocks are divided into two parts:

Transaction header contains information that identifies the

transaction to the scanner and processor.

Transaction body in a request, this contains the DeviceNet

Class, Instance, Attribute and Service Data portion of the
transaction. See Appendix C. In a response, this contains the
Service Data only.

Each of the data attributes in the transaction header are one byte in
length. The Table below details the information required:
Data Field

Description

TXID

Transaction ID when the processor creates and downloads a request to the scanner, the processors
ladder logic program assigns a TXID to the transaction. This is a one-byte integer in word 31 the range of
1 to 255. The scanner uses this value to track the transaction to completion, and returns the value with the
response that matches the request downloaded by the processor.

COMMAND

STATUS

In each message request, a command code instructs the scanner how to administer the request:
0 = Ignore transaction block (block empty)
1 = Execute this transaction block
2 = Get status of transaction TXID
3 = Reset all client/server transactions
4-255 = Reserved
In each message response, the status code provides the processor with status on the device and its
response:
0 = Ignore transaction block (block empty)
1 = Transaction completed successfully
2 = Transaction in progress (not ready)
3 = Error slave not in scan list
4 = Error slave off-line
5 = Error DeviceNet port disabled or off-line
6 = Error transaction TXID unknown
7 = Unused
8 = Error Invalid command code
9 = Error Scanner out of buffers
10 = Error Other client/server transaction in progress
11 = Error could not connect to slave device
12 = Error response data too large for block
13 = Error invalid port
14 = Error invalid size specified
15 = Error connection busy
16-255 = Reserved

Port

The DeviceNet port where the transaction is routed. The port can be zero (Channel A) or one (Channel B)
on a 1771-SDN scanner.

Size

The size of the transaction body in bytes. The transaction body can be up to 29 words (58 bytes) in length.
If the size exceeds 29 words, an error code will be returned.

SERVICE

MAC ID

The service attribute contains the DeviceNet service request and response codes that match the
corresponding request for the TXID. Service codes vary for each DeviceNet object. Appendix C details
available Service Codes referred to as Common Services for each object.
The DeviceNet network address of the slave device where the transaction is sent. This value can range
from 0 to 63. The port and MAC ID attributes coupled together identify the target slave device. The slave
device must be listed in the scanner modules scan list and be on-line for the Explicit Message transaction
to be completed.

Publication 2100-UM001A-US-P January 2000

6-6

Using DeviceNet Explicit Messaging

Examples

The following examples show messages used with the ladder logic
programs begun in Chapter 5, Ladder Logic Programming.

PLC-5 Ladder Example

ATTENTION: The example ladder logic program

shown in this manual is intended solely for purpose of
example. Because there are many variables and
requirements associated with any particular installation,
Rockwell Automation does not assume responsibility or
liability (to include intellectual property liability) for
actual use based upon the example shown in this
publication.

PLC Messaging
Figure 6.3, started in Chapter 5, Ladder Logic Programming, shows
an example PLC ladder logic program that sends an explicit message.
The message sent is contained in N30, beginning at word 0. The
response data will appear in N30 starting at word 70.
Figure 6.3
PLC Messaging Example
B3:0
ONS
0

I:000
0000
17

BTW
Block Transfer Write
Module Type 1771-SDN DeviceNet Scanner Module
Rack
000
Group
0
Module
0
Control Block
BT20:2
Data File
N30:0
Length
64
Continuous
No
MOV
Move
Source
Dest

BT20:2
0001
DN

CMP
Comparison
Expression N30:70 <> N30:0

EN
DN
ER

0
0<
N30:70
257<

BT20:3
EN

BTR
Block Transfer Read
Module Type 1771-SDN DeviceNet Scanner Module
Rack
000
Group
0
Module
0
Control Block
BT20:3
Data File
N30:70
Length
64
Continuous
No

0002

Publication 2100-UM001A-US-P January 2000

EN
DN
ER

END

Using DeviceNet Explicit Messaging

6-7

I:000/17: When you set this instruction to the true state, the next
instruction, a one-shot block transfer write, sends data to the scanner.
The Move instruction then initializes the first word of the data file that
is used by the block transfer read instruction in the next rung.
Instruction BT20:2.DN: This instruction will be true when the block
transfer write has completed. The compare instruction that follows
compares the first word of data sent from the scanner to the first word
of data you send to the scanner. When the messaging function has
completed, these two words will be equal.
Instruction BT20:3.EN: Any time the block transfer read is not
enabled, this instruction causes the block transfer read to be enabled if
the two earlier conditions are true.
BTR: Reads 64 words of data from the scanner.
The following table displays data sent to and received from the
scanner. Values are in hexadecimal.
Offset
N30:0

201

E03

97

N30:10

N30:20

N30:30

N30:40

N30:50

N30:60

N30:70

201

8E03

N30:80

N30:90

N30:100

N30:110

N30:120

N30:130

Publication 2100-UM001A-US-P January 2000

6-8

Using DeviceNet Explicit Messaging

Using the format of Figure 6.3 the above data would be defined as
follows:
BTW Format
Location

N30:0

N30:1
N30:2
N30:3
N30:4

N30:5

BTR Format

Value

Location

TXID

COMMAND

02

01

PORT

SIZE

00

06

SERVICE

MAC ID

0E

03
CLASS
0097

N30:70
N30:71
N30:72
N30:73

Value

TXID

COMMAND

02

01

PORT

SIZE

00

06

SERVICE

MAC ID

8E

03
Data
0004

INSTANCE
0000
ATTRIBUTE
0001

Data in N30:0-5 is data associated with the BTW command. All of

these values are entered into the data table. Data in N30:70-72 is data
associated with the BTR command. All of these values are entered
into the data table. Data at N30:73 is the data read from the
DeviceNet Module as a result of the commands entered data.

Publication 2100-UM001A-US-P January 2000

Using DeviceNet Explicit Messaging

6-9

In this example, there were four entries in the fault queue. Notice the
following about the data:
Location

Value

Meaning

N30:0

0x0201

TXID of 2. Command 1 (Execute)

N30:1

0x0006

Port 0. Size = 6 bytes (N30:3 5)

N30:2

0x0E03

Service E (Get Attribute Single) Node 3

N30:3

0x0097

SCANport Pass-Through Fault Object

N30:4

0x0000

Instance 0 (Class Access)

N30:5

0x0001

Attribute 1 (Number of Fault Queues)

N30:70

0x0201

TXID of 2. Status 1 (Success)

N30:71

0x0006

Port 0. Size = 6 bytes (N30:3 5)

N30:72

0x8E03

Service 8E (Get Attribute Single

Response)

N30:73

0x0004

4 fault queues

Refer to Appendix C, DeviceNet Objects, for more information on

object descriptions.

Explicit Message Program

Control for SLC

Use the Explicit Message Program Control feature to configure

device parameters on your DeviceNet network via the M0 and M1
files in the SLC processor that is controlling these devices.
You can use Explicit Message Program Control feature to:

Transmit configuration data from your scanner module to its slave

devices on your DeviceNet network.

Receive status and diagnostic from these devices on your

DeviceNet network.

Make runtime adjustments to device parameters according to

changing condition detected by your processor.

Publication 2100-UM001A-US-P January 2000

6-10

Using DeviceNet Explicit Messaging

Figure 6.4
How the Explicit Message Program Control Feature Works

2100-GK61
Communication Adapter

1. Format an MO file transfer in the processor to send an Explicit

Message Request to the scanner module (download).
2. The scanner module transmits the Explicit Message Request to
the DeviceNet Network.
3. The slave device transmits the Explicit Message Response back
to the scanner and is queued into a file transfer buffer.
4. The processor uses an M1 file transfer to retrieve the Explicit
Message Response from the scanners buffer (upload).
5. Format an M0 file transfer with a Delete Response Command and
the current transaction ID read in step 4. The transaction IDs are
deleted and can be reused.
The scanner module requires a precisely-formatted M0 and M1 file
transfer size of 32 words including words 224-255. The scanner
module uses the file memory content as client/server request.

Publication 2100-UM001A-US-P January 2000

Using DeviceNet Explicit Messaging

6-11

Message Translations

The communications adapter provides electronic translations of

DeviceNet explicit messages into SCANport messages and back. The
format of all DeviceNet explicit messages supported by the adapter is
8:16: within an explicit message, the class field is 8 bits long, and the
instance field is 16 bits long.

Examples

The following examples show messages used with the ladder logic
programs begun in Chapter 5, Ladder Logic Programming.

Messaging for the 1747-SDN

Scanner

ATTENTION: The example ladder logic program

shown in this manual is intended solely for purpose of
example. Because there are many variables and
requirements associated with any particular installation,
Rockwell Automation does not assume responsibility or
liability (to include intellectual property liability) for
actual use based upon the example shown in this
publication.

The SLC copies an Explicit Message into the scanners M0-file.

When the copy is completed the scanner moves the message into a
queue for processing. Up to 10 Explicit Messages can be in this
queue.
When the scanner receives a response message it is placed into a
queue. The first response in the queue is available from the M1-file.
When the message delete command is copied into the scanner the
message is complete and the next available response will appear in
the M1-file.

Publication 2100-UM001A-US-P January 2000

6-12

Using DeviceNet Explicit Messaging

The format of Request and Response messages is in Figure 6.5.

Figure 6.5
Format of DeviceNet Messages
Format of 32-word M0-file
Write of Explicit Message Request
15
Transaction
Header (3
words)

Transaction
Data (up to 29
words)

Format of 32-word M1-file

Read of Explicit Message Response
0

15

TXID

COMMAND

TXID

STATUS

PORT

SIZE

PORT

SIZE

SERVICE

MAC ID

SERVICE

MAC ID

CLASS

SERVICE RESPONSE DATA

INSTANCE

"

ATTRIBUTE

"

SERVICE DATA

"

"

"

word 0

word 31

For information on M-File locations, refer to the 1747-SDN

DeviceNet Scanner Module Manual, Publication 1747-5.8.
The message buffer is composed of two sections:

Publication 2100-UM001A-US-P January 2000

Transaction header three words that contain information

identifying the message transaction.

Transaction body in a request, this contains the DeviceNet

Class, Instance, Attribute and Service Data portions of the
transaction. See Appendix C. In a response, this contains the
Service Data only.

Using DeviceNet Explicit Messaging

6-13

Each of the data fields in the transaction header are one byte in length.
The Table below details the information required:
Data Field

Description

TXID

Transaction ID when the processor creates and downloads a request to the scanner, the processors
ladder logic program assigns a TXID to the transaction. This is a one-byte integer in word 31 the range of
1 to 255. The scanner uses this value to track the transaction to completion, and returns the value with the
response that matches the request downloaded by the processor.

COMMAND

STATUS

For each download, a command code instructs the scanner how to administer the request:
0 = Ignore transaction block (block empty)
1 = Execute this transaction block
2 = Get status of transaction TXID
3 = Reset all client/server transactions
4 = Delete this transaction block
5-255 = Reserved
For each upload, the status code provides the processor with status on the device and its response:
0 = Ignore transaction block (block empty)
1 = Transaction completed successfully
2 = Transaction in progress (not ready)
3 = Error Slave not in scan list
4 = Error Slave off-line
5 = Error DeviceNet port disabled or off-line
6 = Error Transaction TXID unknown
7 = Unused
8 = Error Invalid command code
9 = Error Scanner out of buffers
10 = Error Other client/server transaction in progress
11 = Error Could not connect to slave device
12 = Error Response data too large for block
13 = Error Invalid port
14 = Error Invalid size specified
15 = Error Connection busy
16-255 = Reserved

PORT

The DeviceNet port used by this message. The port must be zero (Channel A) on a 1747-SDN scanner.

SIZE

The size of the transaction body in bytes. The transaction body can be up to 29 words (58 bytes) in length.
If the size exceeds 29 words, an error code will be returned.

SERVICE

The service attribute contains the DeviceNet service request and response codes that match the
corresponding request for the TXID. Service Codes vary for each DeviceNet object. Appendix C details
available service codes referred to as Common Services for each object.

MAC ID

The DeviceNet network address of the slave device where the transaction is sent. This value can range
from 0 to 63. The port and MAC ID uniquely identify the target slave device. The slave device must be
listed in the scanner modules scan list and be on-line for the Explicit Message transaction to be
completed.

Publication 2100-UM001A-US-P January 2000

6-14

Using DeviceNet Explicit Messaging

SLC Ladder Example

SLC Messaging
Figure 6.6 shows an example message in the SLC ladder logic
program started in Chapter 5, Ladder Logic Programming.
Figure 6.6
SLC Messaging Example
LAD 4 - MESSAGING --- Total Rungs in File = 3

When B3:0/0 is set true, this rung will copy the 32 words of the Explicit Message from the buffer at N20:10 to the M0-File Explicit
Message buffer.
The 1747-SDN will send the message out over DeviceNet.
Initiate
Explicit
Message
B3:0

Explicit
Message
COP
Copy File
Source
#N20:10
Dest
#M0:1.224
Length
32

0000
0

Initiate
Explicit
Message
B3:0
U
0
When I:1.0/15 is true, and the Explicit Message response has been received and is in the M1-File, this rung:
1) Copies the response message into N10:50
2) Copies a command byte of 4 into the M1-File (commands the 1747-SDN scanner to discard the response data so
that the buffer can be used for the next available response message)
Explicit
Message
Response
Available
I:1.0

Explicit
Message
Response
COP
Copy File
Source #M1:1.224
Dest
#N20:50
Length
32

0001
15
1747-SDN

EQU
Equal
Source A
Source B

0002

N20:10
257<
N20:50
257<

Explicit
Message
MVM
Masked Move
Source
N20:0
4<
Mask
00FFh
255<
Dest
M0:1.224
?<

END

Important: To originate a scanner transaction, you must use a copy

operation to M0:[slot number]:224. Then, use a copy operation to
read M1:1.224 for the results. If you have more than one message
enabled, you will have to use the TXID to determine which message
you are reading.

Publication 2100-UM001A-US-P January 2000

Using DeviceNet Explicit Messaging

6-15

The following table display data sent to and received from the
scanner. Values are in hexadecimal.
Offset
N20:0

N20:10

201

E02

97

N20:20

N20:30

N20:40

N20:50

201

8E02

N20:60

N20:70

N20:80

Using the format of Figure 6.4 the above data would be defined as
follows:
BTW Format

Location
N20:10

N20:11
N20:12
N20:13
N20:14

N20:15

BTR Format

Value

Location

TXID

COMMAND

02

01

PORT

SIZE

00

06

SERVICE

MAC ID

OE

03
CLASS
0097

N20:50
N20:51
N20:52
N20:53

Value
TXID

COMMAND

02

01

PORT

SIZE

00

06

SERVICE

MAC ID

8E

03
DATA
0004

INSTANCE
0000
ATTRIBUTE
0001

Data in N20:10 - 15 is data associated with the BTW command. All

of these values are entered into the data table. Data in N20:50-52 is
data associated with the BTR command. All of these values are
entered into the data table. Data at N20:53 is the data read from the
DeviceNet Module as a result of the commands entered in the table.

Publication 2100-UM001A-US-P January 2000

6-16

Using DeviceNet Explicit Messaging

In this example, there were four entries in the fault queue. Notice the
following about the data:
Location

Value

Meaning

N20:10

0x0201

TXID of 2. Command 1 (Execute)

N20:11

0x0006

Port 0. Size = 6 bytes (N30:3 5)

N20:12

0x0E03

Service E (Get Attribute Single) Node 3

N20:13

0x0097

SCANport Pass-Through Fault Object

N20:14

0x0000

Instance 0 (Class Access)

N20:15

0x0001

Attribute 1 (Number of Fault Queues)

N20:50

0x0201

TXID of 2. Status 1 (Success)

N20:51

0x0006

Port 0. Size = 6 bytes (N30:3 5)

N20:52

0x8E03

Service 8E (Get Attribute Single

Response)

N20:53

0x0004

4 fault queues

Refer to Appendix C, DeviceNet Objects, for more information on

object descriptions.

Using Messages to Control

SCANport Products

Publication 2100-UM001A-US-P January 2000

Explicit messages provide multi-purpose, point-to-point

communication paths between two devices. It is possible to control
SCANport devices through explicit messaging on DeviceNet by
following particular guidelines and by writing to various register
objects that are buffering the I/O data. The guidelines are as follows:

The adapter cannot be allocated by a master/scanner in order to

allow explicit writes to the register object.

Write access to any register object within the adapter will not be
allowed if the message is passed through a connection whose
expected packet rate (EPR) is zero.

The adapter is required to mark any explicit connection after

allowing a write to a register object through it.

If a marked explicit connection times out based on the EPR, then

the I/O fault action will be that configured for Communication
Loss over the I/O connection.

If a marked explicit connection is deleted, then the I/O fault

action will be that configured for Idle over the I/O connection.

Multiple explicit connections can write/overwrite the control I/O

if they meet the guidelines specified. Each connection will need
to be marked individually within the adapter.

If the adapter gets allocated/re-allocated by a controller such that

valid I/O data is being sent to the adapter, or if an Idle condition
from the allocating controller is transitioned back to valid data,
then all marked explicit connections will be reset to unmarked

Using DeviceNet Explicit Messaging

6-17

and future writes blocked.

Writing to Register Objects

If a marked connection has its EPR value reset to zero (0) after
being marked, then the connection will become unmarked.

Within the DeviceNet to SCANport Communication Module with

Digital Inputs, various register objects buffer I/O in the following
fashion (RO=Read Only, R/PW=Read/Write Protected):

Instance

Access

Size

Function

RO

See M-S Output

Poll Response I/O data to controller

R/PW

See M-S Output

Buffered Poll I/O data from controller

RO

32 bits

Logic Status & Feedback

R/PW

32 bits

Datalink A from SCANport Device (if enabled)

RO

32 bits

Datalink A to SCANport Device (if enabled)

R/PW

32 bits

Datalink A from SCANport Device (if enabled)

RO

32 bits

Datalink B to SCANport Device (if enabled)

R/PW

32 bits

Datalink B from SCANport Device (if enabled)

RO

32 bits

Datalink C to SCANport Device (if enabled)

10

R/PW

32 bits

Datalink C from SCANport Device (if enabled)

11

RO

32 bits

Datalink D to SCANport Device (if enabled)

12

R/PW

32 bits

Datalink D from SCANport Device (if enabled)

13

RO

32 bits

Logic Status and Feedback

14

R/PW

32 bits

Logic Command (Last Logic Command is ANDed with the first word
in this command and ORed with the second word in the command.
The reference is not modified. This command allows bit changes to
the logic command without affecting the speed reference or other
control bits.)

Refer to the Class Code 0x07 Register Object section in

Appendix C, DeviceNet Objects for more information on the Register
Object.

Publication 2100-UM001A-US-P January 2000

6-18

Using DeviceNet Explicit Messaging

Publication 2100-UM001A-US-P January 2000

Chapter

Troubleshooting
Chapter Objectives

LEDs on the 2100-GK61 Module

Chapter 7 provides information about the adapters LEDs and basic

troubleshooting procedures. In this chapter, you will read about the
following:

Locating the LEDs.

Using the LEDs to troubleshoot the adapter.

Your communications adapter has three LED status indicators. The

LEDs provide status information about the DeviceNet network,
SCANport connection, and the adapter itself. Refer to Figure 7.1.
Figure 7.1
LED Status Indicators

SCANPort Status 1
Module Status
2
DeviceNet Status 3

Input Status 1-4

Publication 2100-UM001A-US-P January 2000

7-2

Troubleshooting

DeviceNet Network Status LED

States
LED
Viewed:

If:

The LED closest to the DeviceNet connector is the DeviceNet Status

LED, labeled NET. It functions as follows:

State:
Not powered/Not
online

No power/Duplicate
ID not completed

1. Verify that the network supply is connected and

that power is reaching the adapter through the
connector.
2. Make sure one or more nodes are communicating
on the network.
3. Make sure at least one other node on the network
is operational at the same time and data rate as the
adapter.

LED is flashing
green

Online/Not
connected

Passed duplicate
ID/No connection
established

No action needed. The LED is flashing to signify that

there are no open communication connections
between the adapter and any other device. Any
connection (I/O or explicit message) made to the
adapter over DeviceNet will cause the LED to stop
flashing and remain steady on for the duration of
any open connection.

LED is steady
green

Online/Connected

One or more
connections
established

No action needed.

LED is flashing red

Online/Time-out

I/O connection timed

out

1. Bring controller back onto the network.

2. Reduce traffic or errors on the network so that
messages can get through within the necessary
time frame.

LED is steady red

Network failure

Failed Duplicate ID
or Bus-off

1. Ensure that all nodes have unique addresses.

2. If all node addresses are unique, examine
network for correct media installation.

Module Status LED States

Module
Status LED

Action:

LED is off

Network
Status LED

LED
Viewed:

Indicates

If:

The middle LED, labeled MOD, is the Module Status LED. It

indicates the operation of the DeviceNet to SCANport
Communication Module with Digital Inputs and functions as follows:

State:

Indicates:

Action:

LED is off

Not powered

No power

Ensure that the connected SCANport product is

powered and connected to the adapter.

LED is flashing
green

Waiting for I/O data

Normal operation
No I/O, or PLC in
program

No action needed. Adapter has passed all

operational tests and is waiting to pass I/O data
between the DeviceNet and SCANport interfaces.

LED is solid green

Operational

Normal operation
I/O operational

No action needed.

LED is flashing red

Configuration
problem

Bad CRC of Adapter

parameters or flash
program

1. Power cycle the adapter to reset it.

2. Enable an adapter reset via the adapters
configuration parameter.
3. Re-flash the adapter.

LED is steady red

Hardware failure

Failed internal or
external RAM test

Replace unit.

Publication 2100-UM001A-US-P January 2000

Troubleshooting

SCANport Status LED States

LED
Viewed:

SCANport
Status LED

7-3

The LED furthest from the DeviceNet connector is the SCANport

Status LED, and is labeled SP. It indicates the status of the
SCANport connection, and functions as follows:

If:

State:

LED is off

Not powered

No power

Ensure that the connected SCANport device is

powered and that the product is connected to
the adapter.

LED is flashing
green

Online/ I/O
connecting

Requesting I/O
connections or no
I/O is selected

No action needed. Adapter is establishing one

or more of the I/O connections with the
SCANport device.

LED is steady
green

I/O operational

One or more
connections
established

No action needed.

LED is flashing
red

Configuration
fault

SCANport
problem: No
communications
seen from the
SCANport device
to request
connections

1. Reseat cable properly.

2. Replace cable.
3. Data links improperly configured reset
adapter to factory default.

LED is steady
red

Link failure

SCANport failure:
Poor cable
connection does
not allow proper
port identification
or the SCANport
device isnt
allowing the
configured I/O
connections.

1. Check all SCANport cables and

connections to the SCANport device.
2. Ensure datalinks are not enabled on a
product that doesnt support datalinks. Or,
ensure that a particular datalink is not already
being used by another adapter on the same
SCANport device.

LED is steady
orange

Failed SCANport
compatibility test

Indicates

Action:

In either case, the adapter must be properly

configured and power cycled after the problem
is fixed.
Call Rockwell Automation support.

Publication 2100-UM001A-US-P January 2000

7-4

Troubleshooting

Input Status LED States

LED
Viewed:

If:

The row of LEDs furthest right on the front of the module are the
Input Status LEDs and function as follows:

State:

Indicates

Action:

LED is Red

Input Off

No power to input

1. Input is off. No action is required.

2. Power is missing from Input 1, verify
external wiring to module.
3. Verify DIp Switch setting matches Input
voltage.

LED is Green

Input On

Input has power

applied

1. Input is on. No action is required.

2. Voltage is applied to Input, verify external
wiring to module.

LED is Red

Input Off

No power to input

1. Input is off. No action is required.

2. Power is missing from Input 2, verify
external wiring to module.
3. Verify DIp Switch setting matches Input
voltage.

LED is Green

Input On

Input has power

applied

1. Input is on. No action is required.

2. Voltage is applied to Input, verify external
wiring to module.

LED is Red

Input Off

No power to input

1. Input is off. No action is required.

2. Power is missing from Input 3, verify
external wiring to module.
3. Verify DIp Switch setting matches Input
voltage.

LED is Green

Input On

Input has power

applied

1. Input is on. No action is required.

2. Voltage is applied to Input, verify external
wiring to module.

LED is Red

Input Off

No power to input

1. Input is off. No action is required.

2. Power is missing from Input 4, verify
external wiring to module.
3. Verify DIp Switch setting matches Input
voltage.

LED is Green

Input On

Input has power

applied

1. Input is on. No action is required.

2. Voltage is applied to Input, verify external
wiring to module.

Publication 2100-UM001A-US-P January 2000

Appendix

Product Specifications
Appendix Objectives

Appendix A provides the specifications that you may need to install

or use either the 2100-GK61 module. These adapters are nonrepairable units. If they are broken, you must replace them.

2100-GK61 Specifications

The following table gives the specifications for the 2100-GK61

DeviceNet to SCANport Communication Module with Digital Inputs.
Category
Dimensions

Specifications
Mounting: 1.55W X 5.17H X 5.00D
(Mounting: 3.94cm X 13.13cm X 12.70cm)
Module: 1.55W X 3.48H X 5.00D
(Module: 3.94cm X 8.84cm X 12.70cm)

Weight

17 oz
(482g)

Operating Temperature

0 to +55C (32 to 131F)

Storage Temperature

40 to +85C (40 to 185F)

Relative Humidity
(Operating)

5 to 95% non-condensing

Relative Humidity (NonOperating)

5 to 95% non-condensing

Shock (Operating)

30g peak acceleration, 11(+/-1)ms pulse

width

Shock (Non-Operating)

50g peak acceleration, 11(+/-1)ms pulse

width

Vibration (Operating)

2.5g at 5Hz - 2KHz

Vibration (Non-Operating)

5g at 5Hz - 2KHz

Power Consumption

Supplied through DeviceNet 24Vdc,

120mA
Supplied through SCANPort 12Vdc, 50mA

Digital Inputs

At 24V, 10mA each Input

At 115V, 10mA each Input
At 230V, 10mA each Input

Regulatory Agencies

UL 508 and CUL

Publication 2100-UM001A-US-P January 2000

A-2

Product Specifications

Publication 2100-UM001A-US-P January 2000

Appendix

DeviceNet to SCANport
Communication Module with Digital
Inputs Parameters
Appendix Objectives

Appendix B provides information on the DeviceNet to SCANport

Communication Module with Digital Inputs parameters and how to
configure them. In this appendix, you will read about the following:

Setting the node address.

Setting the data rate.

Using datalinks and command I/O.

Using Master-Slave communications.

Using Peer-to-Peer communications.

Using Fault Configurable inputs.

Parameters in the DeviceNet to SCANport Communication

Module with Digital Inputs.

Important: The the number for parameters appears in parenthesis

after the name. This is the number in the adapter. If you are using
RSNetWorx for DeviceNet, the number for each adapter parameter
varies depending on the type of drive you are using.

Setting the Node Address

The DeviceNet to SCANport Communication Module with Digital

Inputs has a default node address of 63. This address should be
changed to a unique address (between 0 and 62) on your DeviceNet
network.
Important: If you are installing multiple DeviceNet to SCANport
Communication Modules with Digital Inputs on the network at the
same time or there is already a node 63 on the network, you need to
do one of the following:

Power up only one adapter at a time on the network and give

each a unique node address.

If using software that supports the Fault Node Recovery

feature of DeviceNet, power up all the adapters at the same
time and give each a unique node address.

To set the node address, you need to:

1. Access the adapters parameters over the DeviceNet network
(refer to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs).

Publication 2100-UM001A-US-P January 2000

B-2

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

2. Set the DN Node Address (2) parameter to the desired address.

3. Reset the adapter by setting the Reset Adapter (22) parameter to
Enable.

Setting the Data Rate

The DeviceNet to SCANport Communication Module with Digital

Inputs supports the following data rates:

125 Kbps

250 Kbps

500 Kbps

Autobaud

The adapter defaults to using autobaud data rate detection.

Important: At least one continually transmitting device on the
network (usually the scanner) must be set to a fixed data rate (not
autobaud). This device sets the data rate for the network that the other
nodes using autobaud detect.
If you want to change your adapters data rate, you need to:
1. Access the adapters parameters using the DeviceNet network
(refer to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs).
2. Set the DN Data Rate (3) parameter to the desired value. Refer to
the following table for information on acceptable values.
Before connecting modules to the network you must determine if
your network is within limits of the cable system. Class 1 cables are
rated 600 volts, 8 amps. Class 2 cables are rated 300 volts, 4 amps.
The cables in the chart below can be used for Trunk or Drop
applications. When used for Trunk, length limits must be observed.
Cable Type

Part Number

Data Rates
125 Kbps

250 Kbps

500 Kbps

Class 1 Flat

1485C-P1-E75

420m (1378 ft.)

200m (656 ft.)

75m (246 ft.)

Class 2 Thick Round

1485C-P1-A50

500m (1640 ft.)

250m (820 ft.)

100m (328 ft.)

Class 2 Thin Round

1485C-P1-C50

100m (328 ft.)

100m (328 ft.)

100m (328 ft.)

Class 1 round drop cable is recommended for connections between

devices and Class 1 Trunk. Maximum drop length is 6m (20 ft.)
Cumulative Drop Budget is based on Data Rate.

Publication 2100-UM001A-US-P January 2000

125 Kbps

250 Kbps

500 Kbps

156m (512 ft.)

78m (256 ft.)

39m (128 ft.)

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

B-3

Class 1 Drop Cable is available in three spool sizes:

Cable Part Number

Spool Size

1485C-P1-B50

50m (164 ft.)

1485C-P1-B150

150m (492 ft.)

1485C-P1-B300

300m (984 ft.)

3. Reset the adapter by setting the Reset Adapter (22) parameter to

Enable.

Using Datalinks and Command

I/O

Command I/O provides two 16-bit words of input and two 16-bit
words of output when enabled. Datalinks let you increase the size of
I/O to and from a SCANport device (provided the SCANport device
supports datalinks). By enabling datalinks, you can continuously
change or monitor the value of a parameter without using the
DeviceNet to SCANport messaging function.
Datalinks consist of two 16-bit words of input and two 16-bit words
of output when enabled. They provide up to eight words (in and out)
of data if they are supported in the connected SCANport product.

Publication 2100-UM001A-US-P January 2000

B-4

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

SCANport devices that support this function have a group of

parameters for datalink configuration. These parameters are Data In
A1 D2 and Data Out A1 D2.
If you intend to use command I/O and/or datalinks, you must do the
following:
1. Access the adapters parameters using DeviceNet network (refer
to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs).
2. Enable the Cmd/Stat Config (4) parameter and/or desired
DataLink (5 8) parameters within the DeviceNet to SCANport
Communication Module with Digital Inputs.
Figure B.1
Module I/O Configuration
Cmd/Stat Config
Datalink A Config
Datalink B Confi g
Datalink C Confi g
Module Input

Datalink D Confi g

Logic Command
Reference
DL A1 Inp
DL A2 Inp

Data from
DeviceNet

DL B1 Inp
DL B2 Inp
DL C1 Inp

Data to the
SCANport
Device

DL C2 Inp
DL D1 Inp
DL D2 Inp

Module Output
Logic Status
Feedback
DL A1 Out
DL A2 Out

Data to
DeviceNet

DL B1 Out
DL B2 Out
DL C1 Out

Data from the

SCANport
Device

DL C2 Out
DL D1 Out
DL D2 Out

3. Configure or link the Data In A1 D2 and Data Out A1 D2

parameters in the SCANport product. Refer to the documentation
for your SCANport product.
4. Configure the M-S Input parameter and M-S Output parameter as
desired. Refer to the M-S Input Parameter Configurations
section or the M-S Output Parameter Configurations sections in
this chapter.
5. Reset the adapter by setting the Reset Adapter (22) parameter to
Enable.

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

Using Master-Slave
Communications

B-5

To have your DeviceNet to SCANport Communication Module with

Digital Inputs receive its I/O from a scanner (PLC or SLC) on the
DeviceNet network, you must configure it for Master-Slave
communications.
Figure B.2
Master-Slave Communications
M-S Input (24)

MSB

M-S Output (25)

LSB

MSB

LSB

1=Enable
0=Disable

Adapter Input
Logic Command
Reference
DL A1 Inp
DL A2 Inp

Master Data from

DeviceNet

DL B1 Inp
DL B2 Inp
DL C1 Inp

Data to the
SCANport
Device

DL C2 Inp
DL D1 Inp
DL D2 Inp

Adapter Output
Logic Status
Feedback
DL A1 Out
DL A2 Out

Slave Data to
DeviceNet

DL B1 Out
DL B2 Out
DL C1 Out

Data from the

SCANport
Device

DL C2 Out
DL D1 Out
DL D2 Out

Master-Slave communications let you transmit 2 10 words of I/O

data between the adapter and the scanner.
How you configure your adapter and scanner depends on the type of
allocation you are using. The adapter supports the following:

Polled.

COS (Change of State).

Cyclic.

Polled and COS.

Polled and Cyclic.

Polled Allocation
In polling, the scanner sends control data to the adapter, and then the
adapter responds with its status data. To use polling, you must enable
polling in the adapter and in the scanner.

Publication 2100-UM001A-US-P January 2000

B-6

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

Enabling Polling in the Adapter

The following must be configured in the adapter.
1. Enable the desired I/O and datalinks (parameters 4 8).
2. Set the M-S Input (24) parameter. Refer to the M-S Input
Parameter Configurations section in this chapter.
3. Set the M-S Output (25) parameter. Refer to the M-S Output
Parameter Configurations section in this chapter.
4. Reset the adapter by setting the Reset Adapter (22) parameter to
Enable.
Enabling Polling in the Scanner
Use RSNetWorx to enable polling in the scanner. Refer to Chapter 4,
Configuring a Scanner to Communicate with the Adapter, for more
information on configuring the scanner.
Polling must be enabled in the Edit Device I/O Parameters dialog
box.
Figure B.3
Edit Device I/O Parameters Dialog Box for Polling

Step #1

1. In the Polled section, click Enabled. An 4 appears.

2. In the Rx field, enter the size for the I/O input. Enter 4 for each
datalink enabled and 4 if Com/Ref is enabled. For example, if
Cmd/Ref and all 4 datalinks are enabled, you would enter 20.
3. In the Tx field, enter the size of the I/O output. Enter 4 for each
datalink enabled and 4 if Com/Ref is enabled. For example, if
Cmd/Ref and all 4 datalinks are enabled, you would enter 20.
4. In the Poll Rate field, select the desired rate.
5. Click OK.

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

B-7

COS (Change of State) Allocation

When you set up COS allocation, the scanner sends data to the
adapter at a constant rate (called a heartbeat). If data in the adapter
changes between messages from the scanner, your adapter sends its
new status to the scanner. To use COS, you must enable COS in the
adapter and in the scanner.
Enabling COS in the Adapter
1. Enable the desired I/O and datalinks (parameters 4 8).
2. Set the M-S Input (24) parameter. Refer to the M-S Input
Parameter Configurations section in this chapter.
3. Set the M-S Output (25) parameter. Refer to the M-S Output
Parameter Configurations section in this chapter.
4. Ensure the Cmd/Stat Config (4) parameter is On.
5. Ensure the lowest bit in the M-S Output (25) parameter is set to 1.
For example, xxx0, 0001. This enables status/feedback to be sent
over the slave connection.
6. Set the COS Status Mask (26) parameter to specify which bits in
the logic status word will trigger a message to the scanner when
changed. (0 = do not check the corresponding bit.)
7. Set the COS Fdbk Change (27) parameter to specify the amount
of change required in the reference word needed to trigger a
message to the scanner. (0 = do not check the corresponding bit)
8. Reset the adapter by setting the Reset Adapter (22) parameter to
Enable.

Publication 2100-UM001A-US-P January 2000

B-8

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

Enabling COS in the Scanner

Use RSNetWorx to enable COS in the scanner. Refer to Chapter 4,
Configuring a Scanner to Communicate with the Adapter , for more
information on configuring the scanner.
COS must be enabled in the Edit Device I/O Parameters dialog box.
Figure B.4
Edit Device I/O Parameters Dialog Box for COS

Step #2
Step #3

Step #1

1. If necessary, unselect the Polled section by clicking on the 4

box next to the Polled.
2. In the Change of State/Cyclic section, click on the box next to
Change of State/Cyclic a 4 appears.
3. Click Change of State.
4. In the Rx field, enter 4 for the size for the I/O input.
5. In the Tx field, enter 4 for the size of the I/O output.
6. In the Heartbeat Rate field, enter the desired time for the
maximum interval between messages.
7. Click OK.
Important: After you have configured the scanner and adapter for
COS, you can verify the desired heartbeat rate is used by viewing the
COS/CYC Interval (28) parameter in the adapter.

Cyclic Allocation
When you set up cyclic allocation, your adapter sends or receives data
based on a periodic time interval. To use Cyclic, you must enable
Cyclic in the adapter and in the scanner.

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

B-9

Enabling Cyclic in the Adapter

1. Enable the desired command I/O and datalinks. Refer to the
Using Datalinks and Command I/O section in this chapter.
2. Set the M-S Input (24) parameter. Refer to the M-S Input
Parameter Configurations section in this chapter.
3. Set the M-S Output (25) parameter. Refer to the M-S Output
Parameter Configurations section in this chapter.
4. Ensure the Cmd/Stat Config (4) parameter is set to On.
5. Ensure the lowest bit in M-S Output (25) parameter is set to 1.
6. Reset the adapter by setting the Reset Adapter (22) parameter to
Enable.
Enabling Cyclic in the Scanner
Use RSNetWorx to enable Cyclic in the scanner. Chapter 4,
Configuring a Scanner to Communicate with the Adapter , for more
information on configuring the scanner.
Cyclic must be enabled in the Edit Device I/O Parameters dialog
box.
Figure B.5
Edit Device I/O Parameters Dialog Box for Cyclic

Step #2
Step #3

Step #1

1. If necessary, unselect the Polled section by clicking on the 4

box next to the Polled.
2. In the Change of State/Cyclic section, click on the box next to
Change of State/Cyclic a 4 appears.
3. Click Cyclic.
4. In the Rx field, enter 4 for the size for the I/O input.

Publication 2100-UM001A-US-P January 2000

B-10

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

5. In the Tx field, enter 4 for the size of the I/O output.

6. In the Send Rate field, enter the desired time for the interval
between messages.
7. Click OK.
Important: After you have configured the scanner and adapter for
Cyclic, you can verify the desired send rate is used by viewing the
COS/CYC Interval (28) parameter in the adapter.

Polled and COS Allocation

You can enable both polling and COS allocations. This lets the
scanner poll the adapter at a fixed interval and the adapter report its
status changes to the scanner after they occur.
Enabling Polling and COS in the Adapter
Refer to both the Polled Allocation and the COS (Change of State)
Allocation sections in this chapter for information.
Enabling Polling and COS in the Scanner
Use RSNetWorx to enable polling in the scanner. Refer to Chapter 4,
Configuring a Scanner to Communicate with the Adapter , for more
information on configuring the scanner.
Polling and COS must be enabled in the Edit Device I/O Parameters
dialog box.
Figure B.6
Edit Device I/O Parameters Dialog Box for Polling and COS

Step #5
Step #6
Step #1

1. In the Polled section by click on the box next to Polled. A 4

appears.
2. In the Rx field, enter the size for the I/O input. Enter 4 for each
datalink enabled and 4 if Com/Ref is enabled. For example, if
Cmd/Ref and all 4 datalinks are enabled, you would enter 20.

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

B-11

3. In the Tx field, enter the size of the I/O output. Enter 4 for each
datalink enabled and 4 if Com/Ref is enabled. For example, if
Cmd/Ref and all 4 datalinks are enabled, you would enter 20.
4. In the Poll Rate field, select the appropriate rate.
5. In the Change of State/Cyclic section, click the box next to
Change of State/Cyclic a 4 appears.
6. Click Change of State.
7. In the Rx field, enter 4 for the size for the I/O input.
8. In the Heartbeat Rate field, enter the desired time for the
maximum interval between messages.
9. Click OK.

Polled and Cyclic Allocation

You can enable both polling and cyclic allocations. This allows the
scanner to poll the adapter at fixed intervals and the adapter to send its
status to the scanner at fixed intervals.
Enabling Polling and Cyclic in the Adapter
Refer to both the Polled Allocation section and the Cyclic
Allocation section in this chapter for information.
Enabling Polling in the Scanner
Use RSNetWorx to enable polling in the scanner. Refer to Chapter 4,
Configuring a Scanner to Communicate with the Adapter , for more
information on configuring the scanner.
Polling and Cyclic must be enabled in the Edit Device I/O
Parameters dialog box.
Figure B.7
Edit Device I/O Parameters Dialog Box for Polling and Cyclic

Step #5
Step #6

Step #1

Publication 2100-UM001A-US-P January 2000

B-12

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

1. In the Polled section by click on the box next to Polled. A 4

appears.
2. In the Rx field, enter the size for the I/O input. Enter 4 for each
datalink enabled and 4 if Com/Ref is enabled. For example, if
Cmd/Ref and all 4 datalinks are enabled, you would enter 20.
3. In the Tx field, enter the size of the I/O output. Enter 4 for each
datalink enabled and 4 if Com/Ref is enabled. For example, if
Cmd/Ref and all 4 datalinks are enabled, you would enter 20.
4. In the Poll Rate field, select the appropriate rate.
5. In the Change of State/Cyclic section, click the box next to
Change of State/Cyclic a 4 appears.
6. Click Cyclic.
7. In the Rx field, enter 4 for the size for the I/O input.
8. In the Send Rate field, enter the time for the message interval.
9. Click OK.

Using Peer-to-Peer
Communications

To have your adapter receive data from or transmit data to another

2100-GK61, 1203-GU6 or 1336-GM6 on the DeviceNet network,
you must configure it for peer-to-peer communications. Peer-to-peer
communications are best used in the following instances:

A PLC sends data to a drive. That drive re-transmits the data to

other drives on the network.

A drive is configured on a network. It sends data to other drives

on the network.

Important: After setting up peer-to-peer communications, you must

make sure the configuration that you set up works as you intend it to
work.
To enable peer-to-peer communications, you must enable one adapter
to transmit peer I/O and one or more adapters to receive peer I/O.

Enabling the Adapter to Receive Peer I/O

To have your DeviceNet to SCANport Communication Module with
Digital Inputs receive input data from another DeviceNet to
SCANport Communication Module with Digital Inputs on the
network, you must configure it for peer-to-peer communications.

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

B-13

Figure B.8
Receiving I/O from a Peer Device
Peer A Input
Module Input
Peer Cmd Mask
Peer Ref Adjust

Logic Command
Reference
DL A1 Inp
DL A2 Inp

Peer Input
Data from
DeviceNet

DL B1 Inp
DL B2 Inp
DL C1 Inp

Data to the
SCANport
Device

DL C2 Inp

Peer A Word 1

DL D1 Inp

Peer A Word 2

DL D2 Inp

Peer B Word 1
Peer B Word 2

Module Output
Logic Status
Feedback
DL A1 Out
DL A2 Out
DL B1 Out
DL B2 Out
DL C1 Out

Data from the

SCANport
Device

DL C2 Out
DL D1 Out
DL D2 Out

Peer B Input

In Peer-to-Peer communications, you can receive 2 or 4 I/O words

from another adapter. Follow these directions:
1. Enable the desired I/O and datalinks within the adapter and
SCANport product. Refer to the Using Datalinks and Command
I/O section in this chapter.
2. Ensure the Peer Inp Enable (36) parameter is Off.
3. Set the Peer Node to Inp (34) parameter to the number of the node
from which you want to receive data.

Publication 2100-UM001A-US-P January 2000

B-14

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

4. Set the Peer A Input (29) parameter to a destination for the first 2
words of data.
5. If using 4 words of input, set the Peer B Input (30) parameter to a
destination for the second two words of data.
6. If receiving Cmd/Ref input data, set the bits in the Peer Cmd
Mask (31) parameter according to the following table.
Important: If both Master-Slave data and Peer data are being used to
control the adapter, make sure you know which one is transmitting
which control bits. The adapter will receive each control bit from only
one source. This includes the stop bit.
If receiving I/O from:

Then set bit to:

Master device (PLC or SLC)

Peer device (another DeviceNet to

SCANport Communication Module with
Digital Inputs)

7.

If sending Cmd/Ref I/O data, set the percentage in the Peer Ref
Adjust (23) parameter. The adapter multiplies this value with the
speed reference value to determine the drives speed.

8. Set the Peer Inp Timeout (35) parameter to the maximum amount
of time the adapter will wait for a message before timing out.
Important: This value must be greater than the product of Peer Out
Time (41) parameter multiplied by the Peer Out Skip (42) parameter
in the adapter from which you are receiving I/O.
9. Set the Peer Flt Action (33) parameter to determine what the
adapter should do if it times out.
10. Set the Peer Inp Enable (36) parameter to On.
11. Check the Peer Inp Status (37) parameter to verify operation. It
should either be Waiting (meaning it is waiting for the first Tx) or
Running (meaning it is receiving input data).
Your adapter is now configured to accept I/O data from another
DeviceNet to SCANport Communication Module with Digital Inputs.
Make sure another DeviceNet to SCANport Communication Module
with Digital Inputs on the DeviceNet network is configured to
transmit peer data. Refer to the Enabling the Adapter to Transmit
Peer I/O section in this chapter.

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

B-15

Enabling the Adapter to Transmit Peer I/O

You can have your DeviceNet to SCANport Communication Module
with Digital Inputs send I/O data to another DeviceNet to SCANport
Communication Module with Digital Inputs on the network.
Figure B.9
Transmitting I/O to Another Adapter

Peer A Output

Peer Input
Data from
DeviceNet

M-S Input
Data from
DeviceNet
Module Input
Logic Command
Reference
DL A1 Inp
DL A2 Inp

Peer Output
Data to
DeviceNet

DL B1 Inp
DL B2 Inp
DL C1 Inp

Data to the
SCANport
Device

DL C2 Inp

Peer A Word 1

DL D1 Inp

Peer A Word 2

DL D2 Inp

Peer B Word 1
Peer B Word 2

Module Output
Logic Status
Feedback
DL A1 Out
DL A2 Out
DL B1 Out
DL B2 Out
DL C1 Out

Data from the

SCANport
Device

DL C2 Out
DL D1 Out
DL D2 Out

Peer B Output

To have your adapter send output data to another adapter, you need to:
1. Ensure the Peer Output Enable (40) parameter is Off.
2. Set the Peer A Output (38) parameter to the source of the output
data.
3. If transmitting 4 words, set the Peer B Output (39) parameter to a
different source of output data.
4. Set the Peer Output Time (41) parameter to the minimum time
interval between peer messages.
5. Set the Peer Output Skip (42) parameter to a value between 1 and
16. The product of this value and the value of the Peer Output
Time (41) parameter determine the maximum time interval
between peer messages if there is not a change in status.
6. Set the Peer Output Enable (40) parameter to On.
Your adapter is now configured to transmit I/O data to another
DeviceNet to SCANport Communication Module with Digital Inputs.
Make sure another DeviceNet to SCANport Communication Module
with Digital Inputs on the DeviceNet network is configured to receive
peer data. Refer to the Enabling the Adapter to Receive Peer I/O
section in this chapter.

Publication 2100-UM001A-US-P January 2000

B-16

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

Using Fault Configurable

Inputs

You can select constant values that your adapter will maintain in the
event of a controller mode change or error. These constant values are
referred to as Fault Configurable inputs. When the controller is placed
in program mode or a DeviceNet network fault occurs, the control
outputs from the adapter to the SCANport product can be set to
automatically switch to the constant values set in the Fault Cfg In
parameters. This lets you define a safe operating state for controlled
devices that depend on pre-programmed output from the adapter.

ATTENTION: Risk of severe bodily injury or

equipment damage exists. The Idle Flt Action (9) and
Comm Flt Action (10) parameters allow the user to
change the default configuration that would allow the
module and associated drive to continue to operate if
communication is lost. Precautions should be taken to
assure that your settings for these parameters and your
application do not create a hazard of bodily injury or
equipment damage.

If you intend to use Fault Configurable inputs, you must do the

following:
1. Set desired values for the Fault Cfg Logic (11), Fault Cfg Ref
(12), and Fault Cft In (13 20) parameters.
2. Set the Idle Fault Config (9) parameter and/or the Comm Flt
Action (10) parameter to Fault Cfg.
Refer to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs for instructions on
editing parameters.

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

DeviceNet to SCANport
Communication Module with
Digital Inputs Parameters

B-17

The following table provides information on the DeviceNet to

SCANport Communication Module with Digital Inputs parameter set.
Important: When accessing this parameter set through the
DeviceNet Parameter Class, add the adapters parameter number
to the number of the last parameter of the SCANport device. When
accessing this parameter set through the vendor-specific SCANport
Variables-Linear Class, add the adapters parameter number to
4000H.

Valid Values/
Settings

Default

Writable

Reset or
Power
Cycle

SCANport
Adapter

0-7

NA

No

No

Identifies the port number to-which the adapter

is connected on the SCANport product.

DN Node
Address

0-63

63

Yes

Yes

Identifies the DeviceNet Node Address for the

adapter.

DN Data Rate

125K
250K
500K
Auto

Auto

Yes

Yes

Identifies the data rate used on the DeviceNet

network.
Important: At least one node on your
DeviceNet network must be configured to a
data rate (125, 250, or 500 K), not autobaud.

Cmd/Stat Config

Off, On

On

Yes

Yes

Determines whether to pass logic command and

analog reference control data from a DeviceNet
connection to a SCANport product.

Datalink A Cfg

Off, On

Off

Yes

Yes

Determines whether to pass control data

contained in datalink A from a DeviceNet
connection to the SCANport product.

Datalink B Cfg

Off, On

Off

Yes

Yes

Determines whether to pass control data

contained in datalink B from a DeviceNet
connection to the SCANport product.

Datalink C Cfg

Off, On

Off

Yes

Yes

Determines whether to pass control data

contained in datalink C from a DeviceNet
connection to the SCANport product.

Datalink D Cfg

Off, On

Off

Yes

Yes

Determines whether to pass control data

contained in datalink D from a DeviceNet
connection to the SCANport product.

Name

Description

Important: For information on accessing and editing parameters refer to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs

Publication 2100-UM001A-US-P January 2000

B-18

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

Name

Idle Flt Action

Valid Values/
Settings
Fault
Zero Data
Hold Last
Fault Cfg

Default

Writable

Reset or
Power
Cycle

Fault

Yes

No

Description

Determines the action the adapter should

instruct the SCANport product to take if the
adapter detects that the PLC is set to program
mode.
Important: If you change this parameters
value, the user application may not be able to
control the product after a fault.

10

Comm Flt
Action

Fault
Zero Data
Hold Last
Fault Cfg

Fault

Yes

No

ATTENTION:Risk of severe
bodily injury or equipment
damage exists. The Idle Flt
Action (9) and Comm Flt
Action (10) parameters
allow the user to change the
default configuration that
would allow the module
and associated drive to
continue to operate if
communication is lost.
Precautions should be
taken to assure that your
settings for these
parameters and your
application do not create a
hazard of bodily injury or
equipment damage.

Determines the action the adapter should

instruct the SCANport product to take if the
adapter detects a network failure.
Important: If you change this parameters
value, the user application may not be able to
control the product after a fault.

ATTENTION:Risk of severe
bodily injury or equipment
damage exists. The Comm Flt
Action (10) parameter allows the
user to change the default
configuration that would allow
the module and associated drive
to continue to operate if
communication is lost.
Precautions should be taken to
assure that your settings for
these parameters and your
application do not create a
hazard of bodily injury or
equipment damage.

Important: For information on accessing and editing parameters refer to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

B-19

Name

Valid Values/
Settings

Default

Writable

Reset or
Power
Cycle

11

Fault Cfg Logic

0 65535

Yes

No

Provides the logic command data to the

SCANport product when the adapter is
instructed to use the values for the Fault Cfg
parameters.

12

Fault Cfg Ref

0 65535

Yes

No

Provides the analog reference data to the

SCANport product when the adapter is
instructed to use the values for the Fault Cfg
parameters.

13

Fault Cfg A1 In

0 65535

Yes

No

Provides the first word of datalink A data to the

SCANport product when the adapter is
instructed to use the values for the Fault Cfg
parameters.

14

Fault Cfg A2 In

0 65535

Yes

No

Provides the second word of datalink A data to

the SCANport product when the adapter is
instructed to use the values for the Fault Cfg
parameters.

15

Fault Cfg B1 In

0 65535

Yes

No

Provides the first word of datalink B data to the

SCANport product when the adapter is
instructed to use the values for the Fault Cfg
parameters.

16

Fault Cfg B2 In

0 65535

Yes

No

Provides the second word of datalink B data to

the SCANport product when the adapter is
instructed to use the values for the Fault Cfg
parameters.

17

Fault Cfg C1 In

0 65535

Yes

No

Provides the first word of datalink C data to the

SCANport product when the adapter is
instructed to use the values for the Fault Cfg
parameters.

18

Fault Cfg C2 In

0 65535

No

No

Provides the second word of datalink C data to

the SCANport product when the adapter is
instructed to use the values for the Fault Cfg
parameters.

19

Fault Cfg D1 In

0 65535

Yes

No

Provides the first word of datalink D data to the

SCANport product when the adapter is
instructed to use the values for the Fault Cfg
parameters.

20

Fault Cfg D2 In

0 65535

Yes

No

Provides the second word of datalink D data to

the SCANport product when the adapter is
instructed to use the values for the Fault Cfg
parameters.

21

Digital Input

xxxx 0000 xxxx 1111

NA

No

No

Digital Input Status.

1 = power applied to Input
0 = no power at Input

Description

Important: For information on accessing and editing parameters refer to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs

Publication 2100-UM001A-US-P January 2000

B-20

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

Name

22

Reset Adapter

23

Active I/O Cfg

Default

Writable

Reset or
Power
Cycle

Ready
Enable
Set Defaults

Ready

Yes

No

Ready = No change or reset.

Enable = Resets the module.
Set Defaults = Sets all parameters to their
factory-default values.

0 or 1 for each
bit

N/A

No

No

Displays what I/O is activated in the adapter.

Valid Values/
Settings

Description

datalink
datalink

datalink

datalink

Cmd/

xxx0, 0000
0 = Off
1 = On
24

M-S Input

0 or 1 for each
bit

xxx0,
0001

Yes

Yes

Determines the source of the bits for input.

datalink
datalink

datalink

datalink

Cmd/Ref

xxx0, 0000
0 = Peer or other input
1 = Master-Slave input
For more information, refer to the M-S Input
Parameter Configurations section in this
chapter.
25

M-S Output

0 or 1 for each
bit

xxx0,
0001

Yes

Yes

Determines the source of the bits for output.

datalink
datalink

datalink

datalink

Stat/

xxx0, 0000
0 = Peer or other output
1 = Master-Slave output
For more information, refer to the M-S Output
Parameter Configurations section in this
chapter.
Important: For information on accessing and editing parameters refer to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

B-21

Default

Writable

Reset or
Power
Cycle

0 or 1 for each
bit

Yes

No

Provides a mask of the Logic Status word to

define which bits are checked for changes
during COS allocation.
0 = Off (not checked)
1 = On (checked)
Important: Refer to your SCANport products
documentation for information on its Logic
Status word.

COS Feedback Change

0 = disable

0 = disable

Yes

No

Determines how much (+/-) the feedback word

can change before a message is sent during
COS operations.

28

COS/Cyc
Interval

N/A

N/A

No

No

Displays the interval used by the controller to

check for data in the adapter during COS or
Cyclic allocation.

29

Peer A Input

Off,
Cmd/Ref
DL A Input
DL B Input
DL C Input
DL D Input

Off

Yes

No

Determines where the peer A input is sent in the

SCANport product.
Important: This parameter cannot be changed
when the Peer Inp Enable (36) parameter is On.

30

Peer B Input

Off
Cmd/Ref
DL A Input
DL B Input
DL C Input
DL D Input

Off

Yes

No

Determines where the peer B input is sent in the

SCANport product.
Important: This parameter cannot be changed
when the Peer Inp Enable (36) parameter is On.

31

Peer Cmd
Mask

0 or 1 for each
bit

Yes

Yes

Provides a mask for the Logic Status word

when it is received through peer input.
0 = Off (input received from Master)
1 = On (input received from Peer)

32

Peer Ref
Adjust

0-200.00%

Yes

No

Provides the percentage of the Reference value

received through peer input that will be applied
to the SCANport reference value.

Name

Valid Values/
Settings

26

COS Status
Mask

27

Description

Important: For information on accessing and editing parameters refer to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs

Publication 2100-UM001A-US-P January 2000

B-22

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

Name

33

Peer Flt Action

Valid Values/
Settings
Fault
Zero Data
Hold Last
Fault Cfg

Default

Writable

Reset or
Power
Cycle

Fault

Yes

No

Description

Determines the action the adapter should

instruct the SCANport product to take if the
adapter does not receive peer input in the
allowed time.

ATTENTION:Risk of severe
bodily injury or equipment
damage exists. The Peer Flt
Action (33) parameter allows
the user to change the default
configuration that would allow
the module and associated
drive to continue to operate if
communication is lost.
Precautions should be taken
to assure that your settings for
these parameters and your
application do not create a
hazard of bodily injury or
equipment damage.

34

Peer Node to
Inp

0-63

Yes

No

Determines the node address of the node

producing I/O for the adapter to receive.
Important: This parameter cannot be changed
when the Peer Inp Enable (36) parameter is On.

35

Peer Inp Timeout

.01-180.00 sec

10.00

Yes

No

Determines the time out time. If the adapter

does not receive input from the peer node in this
amount of time, it will do what is selected in
Peer Flt Action (33) parameter.

36

Peer Inp
Enable

Off, On

Off

Yes

No

Off = Disables peer input communications.

On = Enables peer input communications.

37

Peer Inp Status

Off
Waiting
Running
Faulted

NA

No

No

Displays the status of the consumed peer input

connection.

38

Peer A Output

Off
Cmd/Ref
DL A Input
DL B Input
DL C Input
DL D Input
DL A Output
DL B Output
DL C Output
DL D Output

Off

Yes

No

Determines the source of peer A output data in

the SCANport product.
Important: This parameter cannot be changed
when the Peer Out Enable (40) parameter is On.

Important: For information on accessing and editing parameters refer to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

B-23

Default

Writable

Reset or
Power
Cycle

Off
Cmd/Ref
DL A Input
DL B Input
DL C Input
DL D Input
DL A Output
DL B Output
DL C Output
DL D Output

Off

Yes

No

Determines the source of peer B output data in

the SCANport product.
Important: This parameter cannot be changed
when the Peer Out Enable (40) parameter is On.

Peer Out
Enable

On, Off

Off

Yes

No

Off = Disables peer output communications.

On = Enables peer output communications.

41

Peer Out Time

0.01 10.00

1.00

Yes

No

Determines the minimum interval of time

between peer transmissions.

42

Peer Out Skip

1 16

Yes

No

Determines the maximum interval of time

between peer transmissions by multiplying this
value by the value in the Peer Out Time (41)
parameter.

Name

39

Peer B Output

40

Valid Values/
Settings

Description

Important: For information on accessing and editing parameters refer to Chapter 3, Configuring the DeviceNet to SCANport
Communication Module with Digital Inputs

Publication 2100-UM001A-US-P January 2000

B-24

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

M-S Input Parameter Configurations

The M-S Input (24) parameter has the following five configurable
bits.
Figure 7.2
Bits and Corresponding I/O
datalink
datalink

datalink

datalink

Cmd/Ref
0 = Peer or other input
1 = Master-Slave input

xxx0, 0000

When you enable Cmd/Stat (4) or datalink (5-8) parameter(s) in the

adapter, you must set the corresponding bit in the M-S Input (24)
parameter if you want the input data to come from the scanner or
master device.
The following table lists possible configurations for the M-S Input
(24) parameter and the types of allocation associated with each.

ADAPTER
CONFIGURATION

ALLOCATION (Number Of Words)

Data Size Sent From The Controller To The Adapter

M-S Input

M-S
Output

Poll Only

COS Only

Cyclic
Only

Poll &
COS

Poll &
Cyclic

00000

xxxx0

NA

NA

NA

NA

00001

xxxx0

NA

NA

NA

NA

00010

xxxx0

NA

NA

NA

NA

00011

xxxx0

NA

NA

NA

NA

00100

xxxx0

NA

NA

NA

NA

00101

xxxx0

NA

NA

NA

NA

00110

xxxx0

NA

NA

NA

NA

00111

xxxx0

NA

NA

NA

NA

01000

xxxx0

NA

NA

NA

NA

01001

xxxx0

NA

NA

NA

NA

01010

xxxx0

NA

NA

NA

NA

01011

xxxx0

NA

NA

NA

NA

01100

xxxx0

NA

NA

NA

NA

01101

xxxx0

NA

NA

NA

NA

01110

xxxx0

NA

NA

NA

NA

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

ADAPTER
CONFIGURATION

B-25

ALLOCATION (Number Of Words)

Data Size Sent From The Controller To The Adapter

M-S Input

M-S
Output

Poll Only

COS Only

Cyclic
Only

Poll &
COS

Poll &
Cyclic

01111

xxxx0

NA

NA

NA

NA

10000

xxxx0

NA

NA

NA

NA

10001

xxxx0

NA

NA

NA

NA

10010

xxxx0

NA

NA

NA

NA

10011

xxxx0

NA

NA

NA

NA

10100

xxxx0

NA

NA

NA

NA

10101

xxxx0

NA

NA

NA

NA

10110

xxxx0

NA

NA

NA

NA

10111

xxxx0

NA

NA

NA

NA

11000

xxxx0

NA

NA

NA

NA

11001

xxxx0

NA

NA

NA

NA

11011

xxxx0

NA

NA

NA

NA

11100

xxxx0

NA

NA

NA

NA

11101

xxxx0

NA

NA

NA

NA

11110

xxxx0

NA

NA

NA

NA

11111

xxxx0

10

NA

NA

NA

NA

00000

xxxx1

0/0

0/0

00001

xxxx1

2/0

2/0

00010

xxxx1

2/0

2/0

00011

xxxx1

4/0

4/0

00100

xxxx1

2/0

2/0

00101

xxxx1

4/0

4/0

00110

xxxx1

4/0

4/0

00111

xxxx1

6/0

6/0

01000

xxxx1

2/0

2/0

01001

xxxx1

4/0

4/0

01010

xxxx1

4/0

4/0

01011

xxxx1

6/0

6/0

01100

xxxx1

4/0

4/0

01101

xxxx1

6/0

6/0

Publication 2100-UM001A-US-P January 2000

B-26

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

ALLOCATION (Number Of Words)

ADAPTER
CONFIGURATION

Data Size Sent From The Controller To The Adapter

M-S Input

M-S
Output

Poll Only

COS Only

Cyclic
Only

Poll &
COS

Poll &
Cyclic

01110

xxxx1

6/0

6/0

01111

xxxx1

8/0

8/0

10000

xxxx1

2/0

2/0

10001

xxxx1

4/0

4/0

10010

xxxx1

4/0

4/0

10011

xxxx1

6/0

6/0

10100

xxxx1

4/0

4/0

10101

xxxx1

6/0

6/0

10110

xxxx1

6/0

6/0

10111

xxxx1

8/0

8/0

11000

xxxx1

4/0

4/0

11001

xxxx1

6/0

6/0

11011

xxxx1

8/0

8/0

11100

xxxx1

6/0

6/0

11101

xxxx1

8/0

8/0

11110

xxxx1

8/0

8/0

11111

xxxx1

10

10

10

10/0

10/0

M-S Output Parameter Configurations

The M-S Output parameter has the following five configurable bits.
Figure 7.3
Bits and Corresponding I/O
datalink
datalink

datalink

datalink

Stat/

xxx0, 0000

0 = Peer or other
output

When you enable Cmd/Stat (4) or datalink (5-8) parameter(s) in the

adapter, you must set the corresponding bit in the M-S Output (25)
parameter if you want the output data to be sent to the scanner or
master device.

Publication 2100-UM001A-US-P January 2000

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

B-27

The following table lists possible configurations for the M-S Output
(25) parameter and the types of allocation associated with each.
ALLOCATION (Number Of Words)
M-S Output

Data Size Sent From The Adapter To The Controller

Poll Only

COS Only

Cyclic
Only

Poll &
COS

Poll &
Cyclic

00000

NA

NA

NA

NA

00010

NA

NA

NA

NA

00100

NA

NA

NA

NA

00110

NA

NA

NA

NA

01000

NA

NA

NA

NA

01010

NA

NA

NA

NA

01100

NA

NA

NA

NA

01110

NA

NA

NA

NA

10000

NA

NA

NA

NA

10010

NA

NA

NA

NA

10100

NA

NA

NA

NA

10110

NA

NA

NA

NA

11000

NA

NA

NA

NA

11010

NA

NA

NA

NA

11100

NA

NA

NA

NA

11110

NA

NA

NA

NA

00001

2/2

2/2

00011

4/2

4/2

00101

4/2

4/2

00111

6/2

6/2

01011

6/2

6/2

01101

6/2

6/2

01111

8/2

8/2

10001

4/2

4/2

10011

6/2

6/2

10101

6/2

6/2

10111

8/2

8/2

11001

6/2

6/2

Publication 2100-UM001A-US-P January 2000

B-28

DeviceNet to SCANport Communication Module with Digital Inputs Parameters

ALLOCATION (Number Of Words)
M-S Output

Data Size Sent From The Adapter To The Controller

Poll Only

COS Only

Cyclic
Only

Poll &
COS

Poll &
Cyclic

11011

8/2

8/2

11101

8/2

8/2

11111

10

10/2

10/2

Publication 2100-UM001A-US-P January 2000

Appendix

DeviceNet Objects
Appendix Objectives

Appendix C defines the DeviceNet object classes, class services, and

attributes that are supported by the DeviceNet to SCANport
Communication Module with Digital Inputs. These objects can be
used to develop programs for the module.
This appendix assumes that you have experience in object
programming.

Object Classes

The DeviceNet to SCANport Communication Module with Digital

Inputs supports the following object classes:
Class

Object

Page

0x01

Identity

C-2

0x02

Message Router

C-4

0x03

DeviceNet

C-5

0x05

Connection

C-6

0x07

Register

C-8

0x0F

Parameter

C-10

0x10

Parameter Group

C-16

0x93

SCANport Pass-Through Parameter

C-18

0x97

SCANport Pass-Through Fault Queue

C-19

0x98

SCANport Pass-Through Warning

Queue

C-21

0x99

SCANport Pass-Through Link

C-23

0x67

PCCC Object

C-25

Publication 2100-UM001A-US-P January 2000

C-2

DeviceNet Objects

Class Code 0x01 Identity

Object

The identity object provides identification and general information

about the device.

Class Attributes
Attribute
ID

Access
Rule

Get

Name
Max
Instance

Data
Type
UINT

Description
Maximum instance
number of an object
currently created in this
class level of the device.

Instances
The total number of instances depends on the number of
microprocessors in the SCANport product connected to the module.

Instance 1 includes information on both the adapter and the

product.

The instances for the SCANport products microprocessors start

at instance 2.

The instance for the adapter is present after all the instances for
the SCANport products microprocessors.
Instance
1
2 through n - 1
n

Publication 2100-UM001A-US-P January 2000

Description
Total Product
Product components
DeviceNet to SCANport Communication
Module with Digital Inputs

The value of n is the maximum instance in the object. This value is obtainable via class
attribute 2.

DeviceNet Objects

C-3

Instance Attributes
Attribute ID

Access
Rule

Name

Data Type

Get

Vendor ID

UINT

Identification of each vendor by number.

1 = Allen-Bradley

Get

Device Type

UINT

Indication of general type of product.

0x69 = Sub-Component
0x7A = SCANport Device

Get

Product Code

UINT

Identification of a particular product of an individual vendor.

0xXX02 = 1336 PLUS 0.5 10 HP -S/B 0xXX02
0xXX03 = 1336 PLUS 7.5 800 HP -S/B 0xXX03
0xXX07 = 1336 PLUS II -S/B 0xXX07
0xXX10 = 1336 FORCE w/ PLC Adapter -S/B 0xXX10
0xXX11 = 2364F RGU -S/B 0xXX11
0xXX12 = 1394 Motion Drive -S/B 0xXX12
0xXX13 = 1557 Medium Voltage AC Drive -S/B 0xXX13
0xXX14 =193 SMP-3 -S/B 0xXX14
0xXX15 = 150 SMC Dialog Plus -S/B 0xXX15
0xXX17 = 1305 AC Drive -S/B 0xXX17
0xXX18 = 1397 DC Drive -S/B 0xXX18
0xXX19 = 1336 VSC -S/B 0xXX19
0xXX20 = 1336T Force w/ Std Adapter -S/B 0xXX20
0xXX22 = 1336 IMPACT -S/B 0xXX22

Description

Note: The high byte of each code indicates a particular size

or configuration within a product family.
4

Get

Revision

STRUCT of

Major Revision

USINT

Minor Revision

USINT

Revision of the item that this instance of the Identity Object

represents.
Value varies based on product.

Get

Status

WORD

Summary status of product.

Value varies based on product.

Get

Serial Number

UDINT

Serial number of product.

Value varies based on product.

Get

Product Name

SHORT_
STRING

Human readable identification.

Value varies based on product.

Common Services
Service
Code

Implemented for:
Service Name
Class

Instance

0x05

Yes

No

Reset

0x0E

Yes

Yes

Get_Attribute_Single

0x10

No

No

Set_Attribute_Single

0x11

Yes

N/A

Find_Next_Obj_Instan
ce

Get_Attribute_All Response
None supported.

Publication 2100-UM001A-US-P January 2000

C-4

DeviceNet Objects

Class Code 0x02 Message

Router Object

The Message Router Object provides a messaging connection point

through which a client may address to any object class or instance
residing in the physical devices.

Class Attributes
Not supported.

Instances
Instance

Description

Message Router Object

Instance Attributes
Attribute
ID

Acces
s Rule

Get

Number
available

UINT

Maximum number of
connections supported by
the message router.

Get

Number
active

UINT

Number of connections
currently used by system
components.

Get

Active
connectio
ns

ARRA
Y of
UINT

A list of the connection IDs

of the currently active
connections. This attribute
not used.
Reserved for compatibility
purposes.

Name

Data
Type

Description

Common Services
Implemented for:
Service Code

0x0E

Publication 2100-UM001A-US-P January 2000

Service Name
Class

Instance

Yes

Yes

Get_Attribute_Sin
gle

DeviceNet Objects

Class Code 0x03 DeviceNet

Object

C-5

The DeviceNet Object is used to provide the configuration and status

of a physical attachment to DeviceNet. A product must support one
(and only one) DeviceNet Object per physical network attachment.

Class Attributes
Attribute
ID

Access
Rule

Get

Name
DeviceNet
Specification

Data
Type
Word

Description
Returns 2

Instances
Not supported.

Instance Attributes
Attribute
ID

Access
Rule

Get

Mac ID

USINT

Node Address

Get

Data Rate

USINT

Data Rate

Get

BOI

BOOL

Default = 0

Set

Bus Off
Counter

USINT

Increments if BOI is nonzero and Bus Off occurs.

Can only be set to zero.

Get

Allocation
Information

STRUC
T of
BYTE
USINT

The allocation
information a slave
supports when the
master allocates.

Get

Node Adx
Switch Err

BOOL

If non-zero, the Node

Address NVS value does
not match the online
value.

Get

Data Rate
Switch Err

BOOL

If non-zero, the Data

Rate NVS value does not
match the online value.

Get

Node Adx
Switch

USINT

The actual value in the

EEPROM

Get

Data Rate
Switch Val

USINT

The actual value in the

EEPROM or the
operating value after an
autobaud was
completed.

Name

Data
Type

Description

Common Services
Not supported.

Publication 2100-UM001A-US-P January 2000

C-6

DeviceNet Objects

Class Code 0x05 Connection

The Connection Class allocates and manages the internal resources

associated with both I/O and Explicit Messaging Connections. The
specific instance generated by the Connection Class is referred to as a
Connection Instance or a Connection Object.
Important: An externally visible interface to the Connection Class
across Explicit Messaging Connections DOES exist. Unless
otherwise noted, all services/attributes noted in the following sections
are accessible using Explicit Messaging.
A Connection Object within a particular module actually represents
one of the end-points of a Connection. It is possible for one of the
Connection end-points to be configured and active (e.g.,
transmitting) without the other end-point(s) being present.
Connection Objects are used to model the communication specific
characteristics of a particular Application-to-Applications(s)
relationship. A specific Connection Object Instance manages the
communication-specific aspects related to an end-point.
A Connection Object on DeviceNet uses the services provided by a
Link Producer and/or Link Consumer to perform low-level data
transmission and reception functions.

Class Attributes
Attribute ID

Access Rule

Get

Name

Data Type

Description

UINT

Revision of the Connection Object class

definition upon which the implementation is
based
Range 1 65535

Revision

Instances
Instance

Publication 2100-UM001A-US-P January 2000

Description

Group 2 Messaging

Group 2 Polling

Group 2 COS/Cyclic

Group 3 Messaging

Group 3 Messaging

Group 3 Messaging

Group 3 Messaging

10

Group 3 Messaging

DeviceNet Objects

C-7

Instance Attributes
Attribute ID

Access Rule

Name

Data Type

Get

State

USINT

State of the connection as defined in the

DeviceNet specification

Get

Instance type

USINT

Indicates I/O or Messaging connection

Get

Transport Class
Trigger

USINT

The Transport Class Trigger for this

instance

Get

Produced Cnxn ID

USINT

CAN Identifier to transmit on

Get

Consumed Cnxn ID

USINT

CAN Identifier to receive on

Get

Initial Comm Char

USINT

Defines the DeviceNet message groups

that the tx/rx Cnxns apply

Get

Produced Cnxn Size

UINT

Max bytes to transmit across this

connection

Get

Consumed Cnxn
Size

UINT

Max bytes to receive across this connection

Get/Set

EPR

UINT

Expected Packet Rate

12

Get/Set

Watchdog Action

13

Get

Produced Path
Length

14

Get

Produced Cnxn Path

15

Get

Consumed Path
Length

UINT

16

Get

Consumed Cnxn
Path

ARRAY of
USINT

Specifies the application object to receive

the data consumed by this application

17

Get/Set

Production Inhibit
Time

UINT

Defines minimum time between new data

production for COS connections

USINT
UINT
ARRAY of
USINT

Description

How to handle inactivity/watchdog timeouts

Number of bytes in the produced
connection path attribute
Specifies the application object whose data
is to be produced by this connection
Number of bytes in the consumed
connection path attribute

Common Services
Not supported.

Publication 2100-UM001A-US-P January 2000

C-8

DeviceNet Objects

Class Code 0x07 Register

Object

The Register Object is used to address individual bits or a range of

bits. It may operate as either a producer (input) register or a consumer
(output) register. A producer register object produces data onto the
network. A consumer register object consumes data from the
network.
Message writes to the Register Object can perform control functions.
Therefore, message writes are only allowed when the controller is not
actively controlling the module and the message write is done through
a connection with a time-out value not equal to zero. Writes cannot be
performed through an unconnected message. After a write, any
time-out or closure of the connection may cause the SCANport
product to fault.
Refer to Chapter 6, Using DeviceNet Explicit Messaging, for
information about writing to the Register Object.

Class Attributes
Not supported.

Instances
Instance

Publication 2100-UM001A-US-P January 2000

Description

All polled data being read from the SCANport device

(read-only)

All polled data written to the SCANport device (read/

write)

Logic Status and Feedback data (read-only)

Logic Command and Reference data (read/write)

Datalink A input data (read-only)

Datalink A output data (read/write)

Datalink B input data (read-only)

Datalink B output data (read/write)

Datalink C input data (read-only)

10

Datalink C output data (read/write)

11

Datalink D input data (read-only)

12

Datalink D output data (read/write)

13

Logic Status and Feedback Data (read-only)

14

Logic Command and Reference Data (read/write)

The command word is set to the value of the first word of the data where there are ones
in the second word of the data. Command = (word 1 and not word 2) or (word 1 and
word 2). This only controls specified bits in the logic command data to the SCANport
product and does not change the reference value.

DeviceNet Objects

C-9

Instance Attributes
Setting of an assembly attribute can only be accomplished through a
connection. This feature is to prevent accidental control of the
SCANport product.
Attribute
ID

Access
Rule

Name

Data
Type

Get

Bad Flag

BOOL

If set to 1, then attribute

4 may contain invalid,
bad or otherwise
corrupt data.
0 = good
1 = bad

Get

Direction

BOOL

Direction of data
transfer
0 = Producer Register
1 = Consumer Register

Get

Size

UINT

Size of register data in

bits

Conditional

Data

ARRAY
of BITS

Data to be transferred

Description

The access rule of Set is optional if attribute 2, Direction = 1. If Direction = 0, the access
rule is Get.

Common Services
Service
Code

Implemented for:
Service Name
Class

Instance

0x0E

Yes

Yes

Get_Attribute_Single

0x10

No

Yes

Set_Attribute_Single

Publication 2100-UM001A-US-P January 2000

C-10

DeviceNet Objects

Class Code 0x0F Parameter

Object

The Parameter Object provides a known, public interface for device

configuration data. This object also provides all the information
necessary to define and describe each individual configuration
parameter of a device.

Class Attributes
Attribute
ID

Access
Rule

Name

Data
Type

Get

Revision

UINT

Revision of this object.

First revision, value = 1.

Get

Max
Instance

UINT

Maximum instance
number of an object
currently created in this
class level of the device.

Get

Parameter
Class
Descriptor

WORD

Get

Configurati
on
Assembly
Instance

UINT

10

Set

Native
Language

USINT

Description

Bits that describe

parameters.
Instance number of the
configuration assembly.
This attribute is set to
zero because a
configuration assembly
is not supported.
Language ID for all
character array
accesses.
0 = English
1 = French
2 = Spanish
3 = Italian
4 = German
5 = Japanese
6 = Portuguese

Instances
The number of instances varies based on the number of parameters in
your SCANport product. The adapter parameters immediately follow
the SCANport product parameters.
Instance

Publication 2100-UM001A-US-P January 2000

Description

1 through n - 41

SCANport Product Parameters

n - 41 through n

Module Parameters

The value of n is the maximum instance in the object. This value is obtainable via class
attribute 2.

DeviceNet Objects

C-11

Instance Attributes
Attribute ID

Access
Rule

Stub/Full

Stub

Parameter Value

Get

Stub

Link Path Size

Get

Stub

Link Path

Name

Data Type

Description

Specified in
Descriptor,
Data Type
and Data
Size
attributes.

Actual value of parameter. Data type

specified in descriptor, data type, and
data size.

USINT

Size of Link Path attribute. If this

attribute is 0, then no link is specified.
Number of BYTEs in attribute 3.

ARRAY of
path segments

Path to the object from where this

parameter value is retrieved.
The link path is limited to 255 BYTEs.

Segment type/port

BYTE

Segment Address

Path (format
depends on
data
contained in
segment
type/port)

Get

Stub

Descriptor

WORD

Descriptor of parameter. Refer to the

table on page C-12.

Get

Stub

Data Type

USINT

Data type code. Refer to the table on

page C-13.

Get

Stub

Data Size

USINT

Number of BYTEs in attribute 1,

Parameter Value.

Get

Full

Parameter Name
String

SHORT_
STRING

A human readable string

representing the parameter name.
For example, frequency #1.
The maximum number of characters
is 16. (The first byte is a length code.)

Get

Full

Units String

SHORT_
STRING

Engineering unit string.

The maximum number of characters
is 4. (The first byte is a length code.)

Get

Full

SHORT_
STRING

The maximum number of characters

is 64. (The first byte is a length code.)
Always returns 0.

10

Get

Full

Minimum Value

Same as
attribute 1

The minimum valid actual value to

which attribute 1, Parameter Value
can be set.

11

Get

Full

Maximum Value

Same as
attribute 1

The maximum valid actual value to

which attribute 1, Parameter Value
can be set.

The access rule is defined in bit 4 of instance attribute 4, the Descriptor. If bit 4 is 0 the access rule is Set and the Parameter Value can be read and
written. If bit 4 is 1, the access rule is Get and the Parameter Value can only be read.

Data type specified in instance attributes 4 (Descriptor), 5 (Data Type) and 6 (Data Size).

Publication 2100-UM001A-US-P January 2000

C-12

DeviceNet Objects

Attribute ID

Access
Rule

Stub/Full

12

Get

Full

Default Value

13

Get

Full

Scaling Multiplier

UINT

Multiplier for scaling formula.

14

Get

Full

Scaling Divisor

UINT

Divisor for scaling formula.

15

Get

Full

Scaling Base

UINT

Base for scaling formula.

16

Get

Full

Scaling Offset

UINT

Offset for scaling formula.

17

Get

Full

Multiplier Link

UINT

Parameter object instance number of

multiplier source.

18

Get

Full

Divisor Link

UINT

Parameter object instance number of

base source.

19

Get

Full

Base Link

UINT

Parameter object instance number of

offset source.

20

Get

Full

Offset Link

UINT

Parameter object instance number of

offset source.

21

Get

Full

Decimal Precision

Name

Data Type
Same as
attribute 1

USINT

Description
The actual value attribute 1, Parameter
Value should be set to when the user
wants the default for the parameter.

Specifies number of decimal places to use

when displaying the scaled engineering
value. Also used to determine actual
increment value so that incrementing a
value causes a change in scaled
engineering value to this precision.

The access rule is defined in bit 4 of instance attribute 4, the Descriptor. If bit 4 is 0 the access rule is Set and the Parameter Value can be read and
written. If bit 4 is 1, the access rule is Get and the Parameter Value can only be read.

Data type specified in instance attributes 4 (Descriptor), 5 (Data Type) and 6 (Data Size).

Bit Definitions for Instance Attribute 4

Bit

Definition

Value

Supports settable path

0 = Link path can not be set.

1 = Link path can be set.

Supports enumerated strings

0 = Enumerated strings are not supported.

1 = Enumerated strings are supported and may be read with the Get_Enum_String
service.

Supports scaling

0 = Scaling not supported.

1 = Scaling is supported. The scaling attributes are implemented and the value
presented is in engineering units.

Supports scaling links

0 = Scaling links not supported.

1 = The values for the scaling attributes may be retrieved from other parameter
object instances.

Read only parameter

0 = Parameter value attribute can be written (set) and read (get). Access rule is set.
1 = Parameter value attribute can only be read. Access rule is get.

Monitor parameter

0 = Parameter value attribute is not updated in real time by the device.

1 = Parameter value attribute is updated in real time by the device.

Supports extended precision

scaling

0 = Extended precision scaling is not supported.

1 = Extended precision scaling should be implemented and the value presented to
the user in engineering units.

Publication 2100-UM001A-US-P January 2000

DeviceNet Objects

C-13

Data Types for Instance Attribute 5

Attribute
ID Value

Definition

Data Type Description

Scaling
Supported on
this Data Type

WORD

16-bit word

No

UINT

16-bit unsigned integer

Yes

INT

16-bit signed integer

Yes

BOOL

Boolean

No

SINT

Short integer

Yes

DINT

Double integer

Yes

LINT

Long integer

Yes

USINT

Unsigned short integer

Yes

Not Supported

Unsigned double
integer

Yes

10

Not Supported

Unsigned long integer

Yes

11

Not Supported

Single floating point

format (IEEE 754)

Yes

12

Not Supported

Double floating point

format (IEEE 754)

Yes

13

Not Supported

Duration (short)

Yes

14

Not Supported

Duration

Yes

15

Not Supported

Duration (high
resolution)

Yes

16

Not Supported

Duration (long)

Yes

17

Not Supported

Date

No

18

Not Supported

Time of Day

No

19

Not Supported

Date and time

No

20

Not Supported

8-bit per character

string

No

21

Not Supported

16-bit per character

string

No

22

Not Supported

N-byte per character

string

No

23

Not Supported

Short N-byte character

string

No

24

Not Supported

8-bit string

No

25

Not Supported

32-bit string

No

26

Not Supported

64-bit string

No

Publication 2100-UM001A-US-P January 2000

C-14

DeviceNet Objects

Common Services
Service
Code

Implemented for:
Service Name
Class

Instance

0x01

No

Yes

Get_Attribute_All

0x0E

Yes

Yes

Get_Attribute_Single

0x10

No

Yes

Set_Attribute_Single

0x4B

No

Yes

Get_Enum_String

0x05

Yes

No

Reset_Request (sets
all parameters to
default values)

0x15

Yes

No

Restore_Request

0x16

Yes

No

Save_Request

Get_Attribute_All Response
Not supported.
At the instance level, the order of attributes returned in the
Get_Attributes_All response is as follows:
Class
Attribute ID

Publication 2100-UM001A-US-P January 2000

Attribute Name and Default Value

Parameter Value

Link Path Size

Link Path

Descriptor

Data Type

Data Size

Parameter Name String, default character count = 0

Units String, default character count = 0

Help String, default character count = 0

10

Minimum Value default = 0

11

Maximum Value default = 0

12

Default Value default = 0

13

Scaling Multiplier Default = 1

14

Scaling Divisor Default = 1

15

Scaling Base Default = 1

16

Scaling Offset Default = 0

17

Multiplier Link Default = 0

18

Divisor Link Default = 0

19

Base Link Default = 0

20

Offset Link Default = 0

21

Decimal Precision Default = 0

DeviceNet Objects

C-15

Object Specific Services

Service
Code
0x4B

Implemented for:
Service Name
Class

Instance

No

Yes

Get_Enum_String

Enumerated strings are human-readable strings that describe either a

bit or a value depending on the data type of instance attribute 1, the
Parameter Value. If the data type is a BYTE or WORD, the
enumerated string is a bit enumerated string. If the data type is INT or
UINT, the enumerated string is a value enumerated string. Any other
data type does not have enumerated strings.
The table below lists the parameters for the Get_Enum_String request
service.
Name

Data Type

Enumerated
String Number

USINT

Description of Attribute
Number of enumerated string to
retrieve (MAX value is 255).

If the string to be returned is a bit enumerated string, then the

enumerated string number represents a bit position and the
Get_Enum_String service returns a string from that bit.

If the string to be returned is a value enumerated string, then the

enumerated string number represents a value and the
Get_Enum_String service returns a string for that value.

The enumerated string is returned in the form of a SHORT_STRING

and is 16 characters long plus the preceding length byte.

Publication 2100-UM001A-US-P January 2000

C-16

DeviceNet Objects

Class Code 0x10 Parameter

Group Object

The Parameter Group Object identifies and provides access to groups

of parameters in a device grouping. The Parameter Group Object
provides convenient access to related sets of parameters.

Class Attributes
Attribute
ID

Access
Rule

Get

Parameter
group
version

UINT

Returns 1

Get

Max
Instance

UINT

Maximum instance
number of an object
currently created in this
class level of the device.

Get

Native
Language

Name

Data
Type

USINT

Description

Language ID for all

STRING accesses.
0 = English
1 = French
2 = Spanish (Mexican)
3 = Italian
4 = German
5 = Japanese
6 = Portuguese

Instances
The number of instances varies based on the number of groups in the
SCANport product. One additional group is added for the module.
Instance
1 (n - 1)
n

Description
SCANport product groups
Module group

n is the value returned by a get from class attribute 2 (max instance).

Instance Attributes
Attribute ID

Access Rule

Name

Get

Group Name
String

Get

Number of
Members in Group

UINT

Number of parameters in group.

Get

1st Parameter
Number in Group

UINT

Parameter instance number.

Get

2nd Parameter
Number in Group

UINT

Parameter instance number.

Get

(n-2)th Parameter
Number in Group

UINT

Parameter instance number.

Publication 2100-UM001A-US-P January 2000

Data Type
SHORT_
STRING

Description
A human-readable string representing the group
name (e.g., set-up, frequency set).
Maximum number of characters = 16

DeviceNet Objects

C-17

Common Services
Service
Code
0x0E

Implemented for:
Service Name
Class

Instance

Yes

Yes

Get_Attribute_Single

Get_Attribute_All Response
Not supported.

Publication 2100-UM001A-US-P January 2000

C-18

DeviceNet Objects

Class Code 0x93 SCANport

Pass-Through Parameter
Object

The SCANport Pass-Through Parameter Object lets you perform a

scattered read or write.

Class Attributes
Not supported.

Instance Attributes
Not supported.

Common Services
Service Code

Implemented for
Parameter Number:

0x0E

21 (digital inputs)

Service Name
Get_Attribute_Single

Object-Specific Services
Service
Code

Implemented for:
Service Name
Class

Instance

0x32

Yes

No

Scattered_Parameter_
Value_Read

0x34

Yes

No

Scattered_Parameter_
Value_Write

Must be directed to Attribute 0, Instance 0.

The table below lists the parameters for the Scattered_Parameter_

Value_Read and Scattered_Parameter_Value_Write object-specific
services:
Name

Data Type

Description

Scattered
Parameters

STRUCT of

Parameter
Number

WORD

Parameter to read or write

Parameter
Value

WORD

Parameter value to write (zero when

reading)

Important: The STRUCT may repeat up to 32 times in a single

message.

Publication 2100-UM001A-US-P January 2000

DeviceNet Objects

Class Code 0x97 SCANport

Pass-Through Fault Object

C-19

The SCANport Pass-Through Fault Object provides information on

the products fault queue.

Class Attributes
Attribute ID

Access Rule

Name

Data Type

Description

Set

Write Fault
Command

BYTE

1 = Clear Faults
2 = Clear Fault Queue
3 = Reset Product

Get

BYTE

Reads the number of fault queue entries.

Get

Read Number of
Fault Queue Entries
Read Fault Queue
Trip Index

BYTE

Reads the index of the fault that tripped

the product.

Instance Attributes
Attribute ID

Access Rule

Get

Name
Read Fault Queue
Entry Full/All Info
Fault Text
Fault Code
Fault Time Stamp

128

Get

Data Type
STRUCT of
ARRAY of BYTE
WORD
STRUCT

BYTE
BYTE

Minute (0 59).
Hour (0 23).

BYTE

Day of Week (0 6).

BYTE
BYTE

Date (1 31).
Month (1 12).

BYTE

Year (0 99).

Fault Code and Time

Stamp

STRUCT of

Fault Code
Fault Time Stamp

WORD
STRUCT of

Sunday is a value of zero.

Year is an offset from 1990.

Fault Code.

BYTE
BYTE

1/100 Second (0 99).

Second (0 59).

BYTE
BYTE

Minute (0 59).
Hour (0 23).

BYTE
BYTE
Read Fault Text
String Only

Fault Code.
1/100 Second (0 99).
Second (0 59).

BYTE

Get

16 character string (no length information,

no terminating null).

BYTE
BYTE

BYTE

129

Description

ARRAY of BYTE

Day of Week (0 6).

Date (1 31).
Month (1 12).

Year (0 99).
16 character string (no length information,
no terminating null).

Publication 2100-UM001A-US-P January 2000

C-20

DeviceNet Objects

Common Services
Implemented for:
Service Code

Publication 2100-UM001A-US-P January 2000

Service Name
Class

Instance

0x0E

Yes

Yes

Get_Attribute_Single

0x10

Yes

Yes

Set_Attribute_Single

DeviceNet Objects

Class Code 0x98 SCANport

Pass-Through Warning Object

C-21

The SCANport Pass-Through Warning Object provides information

on the products warning queue.

Class Attributes
Attribute
ID

Access
Rule

Set

Write
Warning
Command

BYTE

Set

Read
Number of
Warning
Queue
Entries

BYTE

Name

Data
Type

Description
Write Warning
Command.
1 = Clear Warnings
2 = Clear Warning
Queue
3 = Reset Product

Instance Attributes
Attribute
ID
0

Access
Rule
Get

Name
Read
Warning
Queue
Entry Full/
All Info
Warning
Text
Warning
Code
Warning
Time
Stamp
(Time
Stamps not
available in
all
products)

Data
Type
STRUCT
of

ARRAY
of BYTE
WORD

Sunday is a value of zero.

Year is an offset from 1990.

16 character string (no

length information, no
terminating null).
Fault Code.

STRUCT

BYTE
BYTE

1/100 Second (0 99).

Second (0 59).

BYTE
BYTE

Minute (0 59).
Hour (0 23).

BYTE

Description

BYTE

Day of Week (0 6).

Date (1 31).

BYTE
BYTE

Month (1 12).
Year (0 99).

Publication 2100-UM001A-US-P January 2000

C-22

DeviceNet Objects
Attribute
ID
128

Access
Rule
Get

129

Get

Name
Warning
Code and
Time
Stamp
(Time
Stamps not
available in
all
products)
Warning
Code
Warning
Time
Stamp
(Time
Stamps not
available in
all
products)

Read
Warning
Text String
Only

Sunday is a value of zero.

Year is an offset from 1990.

Data
Type
STRUCT
of

WORD

Description

Fault Code.

STRUCT
of

BYTE

1/100 Second (0 99).

BYTE
BYTE

Second (0 59).
Minute (0 59).

BYTE
BYTE

Hour (0 23).

BYTE
BYTE

Date (1 31).
Month (1 12).

BYTE
ARRAY
of BYTE

Day of Week (0 6).

Year (0 99).
16 character string (no
length information, no
terminating null).

Common Services
Implemented for:
Service Code

Publication 2100-UM001A-US-P January 2000

Service Name
Class

Instance

0x0E

Yes

Yes

Get_Attribute_Single

0x10

Yes

Yes

Set_Attribute_Single

DeviceNet Objects

Class Code 0x99 SCANport

Pass-Through Link Object

C-23

The SCANport Pass-Through Link Object lets you perform a

scattered read or write of a number of links or a single read or write of
a link.

Class Attributes
Attribute ID

Access Rule

Name

Data Type

Description

Set

Link Command

BYTE

1 = Clear all links.

Get

NVS Link Diagnostic Value

WORD

Checksum.

Instance Attributes

Attribute ID

Access Rule

Set

Name

Data Type

Description

WORD

Parameter Link Reference

An instance in this class is the number of a parameter that is to get its value from another parameter.

The Parameter Link Reference value is the number of the parameter whose value is to be transferred.

Common Services
Implemented for:
Service Code

Service Name
Class

Instance

0x0E

Yes

Yes

Get_Attribute_Single

0x10

Yes

Yes

Set_Attribute_Single

Object-Specific Services
Implemented for:
Service Code

Service Name
Class

Instance

0x32

Yes

No

Scattered_Link_
Reference_Value_Read

0x34

Yes

No

Scattered_Link_
Reference_Value_Write

Must be directed to Attribute 0, Instance 0.

Publication 2100-UM001A-US-P January 2000

C-24

DeviceNet Objects

The table below lists parameters for Scattered_Link_Reference_Read

and Scattered_Link_Reference_Write object-specific services.
Name
Scattered Link Read/Write

Data Type

Description

STRUCT of

Parameter Number

WORD

Parameter Link Reference to read or write.

Parameter Link Reference

WORD

Link Reference value to write (zero when reading).

Important: The STRUCT may repeat up to 32 times in a single

message.

Publication 2100-UM001A-US-P January 2000

DeviceNet Objects

Class Code 0x67 PCCC

Object

C-25

The PCCC Object is used to process encapsulated PCCC messages

from DeviceNet. The PCCC Object does not implement any specific
class or instance attributes, so the instance field for any received
messages is ignored.

Class Attributes
Not supported.

Instance Attributes
Not supported.

Common Services
Not supported.

Object Specific Services

Implemented for:
Service Code

Service Name
Class

Instance

0x4B

No

Yes

Execute_PCCC

0x4D

No

Yes

Execute_Local_PCCC

Message Structure for Execute_PCCC

Request
Name

Data
Type

Response
Description

Name

Data
Type

Description

Length

USINT

Length of requestor ID

Length

USINT

Length of requestor ID

Vendor

UINT

Vendor number of
requestor

Vendor

UINT

Vendor number of
requestor

Serial Number

UDINT

ASA serial number of

requestor

Serial Number

UDINT

ASA serial number of

requestor

Other

Product
Specific

Identifier of user, task, etc.

on the requestor

Other

Product
Specific

Identifier of user, task, etc.

on the requestor

CMD

USINT

Command byte

CMD

USINT

Command byte

STS

USINT

STS

USINT

Status byte

TNSW

UINT

Transport word

TNSW

UINT

Transport word. Same

value as the request.

FNC

USINT

Function code. Not used for

all CMDs.

EXT_STS

USINT

Extended status. Not used

for all CMDs.

PCCC_params

ARRAY of
USINT

CMD/FNC specific
parameters

PCCC_results

ARRAY of
USINT

CMD/FNC specific result

data

Publication 2100-UM001A-US-P January 2000

C-26

DeviceNet Objects

Message Structure for Execute_Local_PCCC

Request
Name

Data
Type

Response
Description

Name

Data
Type

Description

CMD

USINT

Command byte

CMD

USINT

Command byte

STS

USINT

STS

USINT

Status byte

TNSW

UINT

Transport word

TNSW

UINT

Transport word. Same

value as the request.

FNC

USINT

Function code. Not used for

all CMDs.

EXT_STS

USINT

Extended status. Not used

for all CMDs.

PCCC_params

ARRAY
of
USINT

CMD/FNC specific
parameters

PCCC_results

ARRAY of
USINT

CMD/FNC specific result

data

Publication 2100-UM001A-US-P January 2000

Appendix

N-File Addresses
Appendix Objectives

Appendix D provides information on the N-File addresses used when

accessing the PCCC object. When using messages, you can use the
N-file addresses to locate information about the adapter or SCANport
product.

N-File Addresses

The 2100-GK61 support the N-file addresses shown below:

Address

N-File Addresses

N10:0

Number of SCANport product parameters

N10:1 999

SCANport product parameters 1 999 (value only)

N11:0 999

SCANport product parameters 1000 1999 (value only)

N12:0 999

SCANport product parameters 2000 2999 (value only)

N13:0

Number of SCANport adapter parameters

N13:1 999

SCANport adapter parameters 1 999 (value only)

N30:1 999

SCANport product parameters 1 999 (all information read

only)

N31:1 999

SCANport product parameters 1000 1999 (all information

read only)

N32:1 999

SCANport product parameters 2000 2999 (all information

read only)

N33:1 999

SCANport adapter parameters 1 999 (all information read

only)

N40:0 63

Block Transfer Emulation file

N42:5

1203-Gx2 Firmware Emulation Version The firmware version of

the 1203-Gx2 this adapter emulates for DriveTools compatibility.

N42:6

Max Network Node The maximum DeviceNet Node Number

N42:7

Adapter Port # The SCANport adapter port number the adapter

is connected to on the SCANport product

N42:8

Reserved for future use Always zero

N50:0

Number of SCANport product parameters

N50:1 249

SCANport product parameters 1 249 (value only)

Publication 2100-UM001A-US-P January 2000

D-2

N-File Addresses
Address
N51:0 249

N-File Addresses
SCANport product parameters 250 499 (value only)

.
.
.
N61:0 249

SCANport product parameters 2750 2999 (value only)

N90:1 249

SCANport product parameters 1 249 (value only)

N91:0 249

SCANport product parameters 250 499 (value only)

.
.
.
N101:0 249

Publication 2100-UM001A-US-P January 2000

SCANport product parameters 2750 2999 (value only)

Appendix

Supported Emulated Block Transfer

Commands
Appendix Objectives

Appendix E provides information about the Emulated Block Transfer

commands supported by the DeviceNet adapter. In this appendix, you
will learn about the following:

Emulated block transfer commands.

Emulated block transfer error response.
Setting up the data files for each of the emulated block transfer
commands listed.
Examples of each emulated block transfer command listed.

What is Emulated Block

Transfer?

Emulated block transfer is a method used by some SCANport

peripherals to read and write information using PCCC messages.
Some Allen-Bradley DeviceNet products can send PCCC messages.
Other products can send PCCC messages using a DF-1 connection.
This appendix assumes that you have experience using emulated
block transfer commands with SCANport peripherals.

Supported Emulated Block

Transfer Commands

ATTENTION: Hazard of equipment damage exists. If

explicit messages are programmed to frequently write
parameter data, the EEPROM (Non-Volatile Storage)
will quickly exceed its life cycle and cause the product
to malfuction. Do not create a program that frequently
uses explicit message to write parameter data to a
product. Datalinks do not write to the EEPROM and
should be used for frequency changed parameters.

The following table lists the supported emulated block transfer

commands and pages in this appendix where you can find more
information on them.
Command
Parameter Value Read
Parameter Value Write
Parameter Read Full
Product ID Number Read
Scattered Parameter Read Value
Scattered Parameter Write Value
NVS Functions
Fault Command Write
Fault Queue Entry Read Full
Fault Queue Size
Trip Fault Queue Number

Page
E-3
E-4
E-5
E-8
E-10
E-12
E-14
E-15
E-16
E-18
E-19

This function can be accessed in the module and product. The following examples describe
how to access it in the product. To do so in the module, add 16384 to the decimal value of
header word 2.

Publication 2100-UM001A-US-P January 2000

E-2

Supported Emulated Block Transfer Commands

Emulated Block Transfer

Status Word

When an operation is unsuccessful, header word 2 of the drive

response contains a negative value (bit 15 = 1).
If an error occurs, the drive also returns a status word to indicate the
reason for the failure. The location of the status word is typically
header word 4 in the drive response, but will depend on the message.
Figure E.1
Example Message Structure and Error Message Reply
PLC Request
Drive Response
Message Length 4

Header 1

Header 2

Data

Header Word 0

Header Word 1

Message Length

Header 1.OR.0x8000

Header Word 0

Header Word 1

Header Word 2
Header 2

Header Word 2

Error Code

Header Word 3

Data Word 3

The following table lists the error codes.

Value

Publication 2100-UM001A-US-P January 2000

Description

No error occurred.

The service failed due to an internal reason, and the drive could
not perform the request.

The requested service is not supported.

An invalid value in the block transfer emulation request header

word 2.

An invalid value in the block transfer emulation request header

word 3.

An invalid value in the block transfer emulation request header

word 2.

The data value is out of range.

There is a drive state conflict. The drive is in an incorrect state to

perform the function. The drive cannot be running when you
perform certain functions.

Supported Emulated Block Transfer Commands

Parameter Value Read

E-3

Parameter Value Read reads the 16-bit parameter data value for the
selected parameter number.

PLC Block Transfer Emulation Instruction Data

PLC request instruction length: 3 words
Drive response instruction length: 1 word
Figure E.2
Message Structure
PLC Request
Drive Response
Message Length
3
PLC Decimal Value

Header Word 0
Header Word 1

769
Parameter Number
(See Drive List)

Header
Word 0

Header 0
PLC Decimal Value
769=OK 31999=Error

Header
Word 1

Header 2

Header
Word 2

Header Word 2

Parameter Value or
Status Word

Data
Word 3

Message Operation
Parameter Value Read reads parameter values from the drive and
places that value (or an error code) in word 3 of the drive response
data file. The value is shown in device units. Device units are listed in
the user manual for the device you are using.
If an error occurs:

Word 3 of the response contains the status code.

The status area of the data file is non-zero.

Example
In this example, the value of parameter 20 was requested from a 1336
PLUS drive and a value of 4096 was returned. 4096 is the internal
drive unit value for Maximum Rated Voltage. This corresponds to a
value of 100% Drive Rated Volts in Display Units.
Data File Format
0

PLC request

769

20*

Drive response

769

20*

4069*
* Example only These values vary depending on parameters and
products.

Publication 2100-UM001A-US-P January 2000

E-4

Supported Emulated Block Transfer Commands

Parameter Value Write

Parameter Value Write writes a 16-bit parameter data value to the

selected parameter number.

PLC Block Transfer Emulation Instruction Data

PLC request instruction length: 1 word
Drive response instruction length: 4 words
Figure E.3
Message Structure
PLC Request
Drive Response
Header Word 0

Message Length
4

Header

PLC Decimal Value

31999

Header Word 1

PLC Decimal Value

769 Message OK
31999 Message Error

Header
Word 1

Parameter Number

Data Word 2

Parameter Data

Data Word 3

Message Length
4

Word 0

Data

Parameter Number

Word 2
Data

Status Word

Word 3

Message Operation
Parameter Value Write sends a new value to the specified
parameter. The value must be in device units. Units for each
parameter are listed in the device manual.
If an error has occurred, word 1 of the response returns a value of
31999, and word 3 contains a status code.

Example
In this example, a value of 4096 was sent to Parameter 20. 4096 is in
drive units and indicates a value of 100% Drive Rated Volts, as
defined in P147, Drive Rated Volts.
Data File Format
0

PLC request

31999

20*

4096*

Drive response

769

20*

* Example only These values vary depending on parameters and products.

Publication 2100-UM001A-US-P January 2000

Supported Emulated Block Transfer Commands

Parameter Read Full

E-5

Parameter Read Full provides all known attributes for the

parameters requested. This information includes the parameters
current value, descriptor, multiply and divide value, base value, offset
value, text string, group element reference, minimum value,
maximum value, default value, and unit text string.

PLC Block Transfer Emulation Instruction Data

PLC request instruction length: 3 words
Drive response instruction length: 20 words
Figure E.4
Message Structure
PLC Request
Message Length
3
PLC Decimal Value
768
Parameter Number
(See Drive List)

Header Word 0

Header Word 1
Header Word 2

Message Length
23

Header

PLC Decimal Value

768 Message OK
31999 Message Error

Header
Word 1

Parameter Number

Parameter Value
or Status Word
Descriptor

Multiply Value

Divide Value

Base Value

Word 0

Data
Word 2
Data
Word 3
Data
Word 4
Data
Word 5
Data
Word 6
Data
Word 7
Data

Offset Value

Word 8

Char 2

Char 1

Data
Word 9

Char 4

Char 3

Data
Word 10

Char 6

Char 5

Data
Word 11

Char 8

Char 7

Char 10

Char 9

Word 13

Char 12

Char 11

Word 14

Char 14

Char 13

Word 15

Char 16

Char 15

Word 16

Parameter
Text

Data
Word 12
Data

Data

Data

Data

Publication 2100-UM001A-US-P January 2000

E-6

Supported Emulated Block Transfer Commands

Figure E.4
Message Structure (Continued)

Drive Response

File, Group, Element

Minimum Value

Maximum Value

Default Value

Data
Word 17
Data
Word 18
Data
Word 19
Data
Word 20

Char 2

Char 1

Char 4

Char 3

Data
Word 21

Unit Text
Data
Word 22

Message Operation
Parameter Read Full retrieves the attributes of the specified
parameter. The attributes for each parameter include the data,
minimum and maximum values, and the parameter text. The response
message returns this information.
If an error has occurred in reading any of the values, word 3 contains
the status word.
The parameter text is returned with each data word containing two
ASCII characters per word. The first and second characters are in
opposite order.

Example
In this example, a Parameter Read Full was performed through
block transfer on a 1336 PLUS drive. N10:10 shows the header
message for the request. The data is returned in the response data file,
starting with word 3, for parameter 20. Word 3 shows the present
value in drive units. Word 4 through word 8 provide scaling
information, used to convert drive units to engineering units for the
Human Interface Module (HIM). Word 9 through word 16 provide the
parameter name.

Publication 2100-UM001A-US-P January 2000

Supported Emulated Block Transfer Commands

E-7

This example shows the response message in both binary and ASCII.
Note the ASCII information beginning with word 9. The parameter
name characters return in reverse order for each word. Word 9 has the
ASCII value of (aM). To read this, reverse the word to read (Ma). The
next word (ix), reversed, gives you (xi). These words, along with the
following two words, form the word Maximum. You can see the
parameter name Maximum Voltage in word 9 through word 16 of the
response message. In addition, words 21 22 are also returned in this
format. These words provide the units in which the parameter is
defined. In this example it is vlts.
Word 17 contains the file, group, and element which are used to
reference the parameter.
Words 18 20 contain the minimum, maximum, and default values of
this parameter.
Data File Format
0

PLC request

768

20*

Drive response

23

768

20*

4096*

355*

1*

4096*

460*

0*

24909*

(Decimal)

27000*

30061*

8301*

28502*

29804*

26465*

8293*

1794*

1024*

4915*

4096*

27734*

29556*

Drive response

\00\17

\03\00

\00\14

\10\00

\01 c

\00\01

\10\00

\01\CC

\00\00

aM

(ASCII)

ix

um

oV

tl

ga

07 02

04 00

\13 0

\10\00

lV

st
* Example only These values vary depending on parameters and products.

Publication 2100-UM001A-US-P January 2000

E-8

Supported Emulated Block Transfer Commands

Product ID Number Read

Product ID Number Read returns the product ID of the device to

which the DeviceNet adapter is connected.

PLC Block Transfer Emulation Instruction Data

PLC request instruction length: 3 words
Drive response instruction length: 4 words
Figure E.5
Message Structure
PLC Request
Drive Response
Message Length
3
PLC Decimal Value
256

Header Word 0
Message Length
6

Header

PLC Decimal Value

256 Message OK
32512 Message Error

Header
Word 1

Header
Word 2

Word 0

Header Word 1

Data Word 2

Product ID Number

Data
Word 3

Product
Code (Hex)

Product
Code
(Decimal)

Bulletin
Number

0x02

1336S

1336 PLUS Fractional HP

0x03

1336S

1336 PLUS

0x07

1336F

1336 PLUS II

0x10

16

1336T

1336 FORCE w/PLC Adapter Board

0x11

17

2364F

2364 RGU DC Bus Regen Front End

0x12

18

1394

1394 Motion Drive

0x13

19

1557

1557 Medium Voltage AC Drive

0x14

20

193

SMP-3

0x15

21

150

SMC Dialog Plus

0x17

23

1305

1305 AC Drive

0x18

24

1397

1397 DC Drive

0x19

25

1336R

1336 Line Regeneration Package

0x20

32

1336T

1336 FORCE w/Standard Adapter Board

0x22

34

1336E

1336 IMPACT

Publication 2100-UM001A-US-P January 2000

Product

Supported Emulated Block Transfer Commands

E-9

Message Operation
Product ID Number Read, through the drive response message
word 3, indicates the type of device the DeviceNet adapter is
connected to. This value is defined in the message response chart
shown above.
If an error has occurred, word 1 of the response returns a negative
value of 32512.

Example
In this example, the Product ID Number Read was requested. The
drive response contained a value of 3 in word 3 of its message
response, indicating a connection to a 1336 PLUS drive.
Data File Format
0

PLC request

256

Drive Response

256

3*
* Example only These values vary depending on parameters and products.

Publication 2100-UM001A-US-P January 2000

E-10

Supported Emulated Block Transfer Commands

Scattered Parameter Value

Read

Scattered Parameter Value Read reads a scattered list of

parameters.
PLC Block Transfer Emulation Instruction Data
PLC request instruction length: 5 63 words
Drive response instruction length: 5 63 words
Figure E.6
Message Structure
PLC Request
Drive Response
Message Length
5 63
PLC Decimal Value
3
Number of Parameter
Values to Read

Header Word 0

Header Word 1
Header Word 2

Header

PLC Decimal Value

3 Message OK
32765 Message Error

Header

Number of Parameter
Values to Read

Parameter Number
1

Data Word 3

Data Word 4

Parameter Number

Message Length
5 63

bit
15

Data Word 5

Parameter Number
1

Parameter Value or
Status Word
1

Word 0

Word 1
Data
Word 2
Data
Word 3
Data
Word 4

2
0

Data Word 6

Parameter Number
3

Data Word 7

Data Word 8

Parameter Number
30

Data Word 61

Data Word 62

bit
15

Parameter Number
2

Parameter Value or
Status Word
2
bit
15

Parameter Number
3

Parameter Value or
Status Word
3

bit
15

Data
Word 6
Data
Word 7
Data
Word 8

Parameter Number
30

Parameter Value or
Status Word
30

Publication 2100-UM001A-US-P January 2000

Data
Word 5

Data
Word 61
Data
Word 62

Supported Emulated Block Transfer Commands

E-11

Message Operation
Scattered Parameter Value Read reads a pre-defined group of
parameter values, in any order, from the device. You define the
number of parameters to read in word 2 of the request. The
parameters to be read and their order is defined starting with word 3.
An unused word is left between each parameter request, so the drive
can respond with the parameter value, as shown.
If an error has occurred in reading any of the parameters:

Word 1 of the drive response returns a value of 32765.

Bit 15 of the drive response word for the number of that

parameter is set.

The drive response word for the value of that parameter returns a
status word instead of returning the parameter value.

Example
In this example, eight parameters were read from a 1336 PLUS drive,
as defined in word 2 of the request. Parameter numbers 5, 7, 8, 20, 18,
17, 19, and 36 were requested. The drive response returned the values
of these parameters in the data file. These values are in drive units.
Data File Format

PLC request

Drive response

19

8*

5*

7*

8*

20*

18*

0*

17*

19*

36*

19

8*

5*

6*

7*

1000*

8*

1000*

4096*

18*

4096*

17*

51*

19*

60*

36*

6144*

20*

* Example only These values vary depending on parameters and products.

Publication 2100-UM001A-US-P January 2000

E-12

Supported Emulated Block Transfer Commands

Scattered Parameter Value

Write

Scattered Parameter Value Write writes to a scattered list of

parameters and returns the status of each parameter. If any of the
states have errors, the parameter number is negative.

PLC Block Transfer Emulation Instruction Data

PLC request instruction length: 5 63 words
Drive response instruction length: 5 63 words
Figure E.7
Message Structure
PLC Request
Drive Response
Message Length
5 63
PLC Decimal Value
32765
Number of Parameter
Values to Write
Parameter Number
1
Parameter Value
1

Header Word 0
Message Length
5 63
Header Word 1
Header Word 2

PLC Decimal Value

3 Message OK
32765 Message Error
Number of Parameter
Values to Write

Data Word 3
bit
15

Parameter Number
1

Data Word 4
Status Word 1

Parameter Number
2

Data Word 5
bit
15

Parameter Value
2
Parameter Number
3
Parameter Value
3

Publication 2100-UM001A-US-P January 2000

Data Word 6

Data Word 7
bit
15

Parameter Number
3

Data Word 8

Parameter Number
30

Data Word 61

Word 0
Header
Word 1
Data
Word 2
Data
Word 3
Data
Word 4
Data
Word 5
Data

Status Word 2

Parameter Value
30

Parameter Number
2

Header

Status Word 3

bit
15

Word 6
Data
Word 7
Data
Word 8

Parameter Number
30

Data Word 62

Data
Word 61
Data

Status Word 30

Word 62

Supported Emulated Block Transfer Commands

E-13

Message Operation
Scattered Parameter Value Write writes data values to a
pre-defined group of device parameters in any order. You define the
number of parameters to write in word 2. The parameters to be
written to and their order is defined starting with word 3.
If an error occurs while writing to any of the parameters:

Word 1 of the drive response returns a value of 32765.

Bit 15 of the drive response word for that parameters number is

set.

The drive response word for that parameters status word is

non-zero.

If no error has occurred:

Word 1 of the drive response returns a value of 3.

Each of the drive responses parameter numbers are the same as

in the request.

Each of the drive response status words returns a value of 0.

Example
In this example, six parameters were written to in a 1336 PLUS drive.
Word 2 of the request defines the number of parameter values that are
transferred. Beginning with word 3, the message lists each parameter
number followed by the value of the parameter. The values are
entered in device units.
The drive response returns the status of each parameter write. If the
request was successful, a zero is returned. If an error has occurred, the
response returns a status word code for the error.
Data File Format

PLC request

Drive response

15

32765

6*

90*

1*

150*

4*

30*

20*

31*

10*

10*

2*

12*

5*

15

6*

90*

0*

150*

0*

30*

0*

31*

0*

10*

0*

12*

0*

* Example only These values vary depending on parameters and products.

Publication 2100-UM001A-US-P January 2000

E-14

Supported Emulated Block Transfer Commands

NVS Functions

NVS (Non-Volatile Storage) Functions activates the specified NVS

functions.

PLC Block Transfer Emulation Instruction Data

PLC request instruction length: 4 words
Drive response instruction length: 3 words
Figure E.8
Message Structure
PLC Request
Drive Response
Message Length
4

Header Word 0
Message Length
3

PLC Decimal Value

31998

Header Word 1

Header Word 2

PLC Decimal Value

770 Message OK
31998 Message Error

Header
Word 0
Header
Word 1
Header

Word 2
NVS Command

Value

Data Word 3

NVS Command

00
01
02
03

Not Used
NVS Save
NVS Recall
NVS Default Initialize

Message Operation
The NVS storage function allows three different message requests:

NVS Save saves parameter information from the working

memory or RAM to NVS Storage.

NVS Recall retrieves the last saved data from NVS Storage and
places it in the working memory or RAM.

NVS Default Initialize clears the RAM and NVS Storage and sets
all parameter values to default.

If an error has occurred, response word 1 returns a value of -31998.

Example
This example requests the NVS Storage Save function be performed.
Data File Format
0

PLC request

31998

0*

0, 1, 2, or 3

Drive response

770

0*

* Example only These values vary depending on parameters and products.

Publication 2100-UM001A-US-P January 2000

Supported Emulated Block Transfer Commands

Fault Command Write

E-15

Fault Command Write activates the Clear Fault, Clear Fault Queue,
and Drive Reset functions.

PLC Block Transfer Emulation Instruction Data

PLC request instruction length: 4 words
Drive response instruction length: 4 words
Figure E.9
Message Structure
PLC Request
Drive Response
Message Length
4

Header Word 0

PLC Decimal Value

30976

Header Word 1

Header Word 2

Fault Command

Value

Header

Message Length
4

Word 0

PLC Decimal Value

1792 Message OK
30976 Message Error

Header
Word 1

Header
Word 2

Status Word

Data
Word 3

Data Word 3

Fault Command

00
01
02
03

Not Used
Clear Fault
Clear Fault Queue
Drive Reset (1336 FORCE

Message Operation
The specified fault Clear/Reset function sends a fault handling
request to the device.

A Clear Fault request clears the last fault that occurred.

A Clear Fault Queue clears the entire fault buffer. Certain devices
may store more than one fault.

A Drive Reset is used with the 1336 FORCE drive product only.
This function resets the drive; it clears the fault queue and writes
the parameter information stored in NVS Storage to RAM.

Data File Format

0

PLC request

30976

0, 1, 2, or 3

Drive
response

1792

0*

* Example only These values vary depending on parameters and products.

Publication 2100-UM001A-US-P January 2000

E-16

Supported Emulated Block Transfer Commands

Fault Queue Entry Read Full

Fault Queue Entry Read Full reads the contents of the specified
fault queue entry. A message is returned which includes the fault text
and fault code associated with the specified fault queue entry. The
1336 FORCE drive also returns the time stamp associated with the
fault.

PLC Block Transfer Emulation Instruction Data

PLC request instruction length: 3 words
Drive response instruction length: 12 or 16 words
Figure E.10
Message Structure
PLC Request
Drive Response
Message Length
3
PLC Decimal Value
1792
Fault Queue
Entry Number

Header Word 0

Header Word 1

Header Word 2

Message Length
18

Header

PLC Decimal Value

1792 Message OK
30976 Message Error

Header

Fault Queue
Entry Number

Header

Char 2

Char 1

Char 4

Char 3

Char 6

Char 5

Char 8

Char 7

Char 10

Char 9

Char 12

Char 11

Char 14

Char 13

Fault Text

Word 0

Word 1

Word 2
Data
Word 3
Data
Word 4
Data
Word 5
Data
Word 6
Data
Word 7
Data
Word 8
Data
Word 9
Data

Char 16

Char 15

Fault Code Value

1336
FORCE
Drive Only

Word 10
Data
Word 11
Data

SES

REF

Hour

Minute

Data
Word 13

Date

Day

Data
Word 14

Year

Month

Clock
Time

Word 12

Data
Word 15

Publication 2100-UM001A-US-P January 2000

Supported Emulated Block Transfer Commands

E-17

Message Operation
Fault Queue Entry Read Full reads the contents of the fault queue
specified in word 3 of the request. The response returns the fault text
which can be ASCII text. Every two characters of text are in reverse
order. Also, the 1336 FORCE drive returns a time stamp, indicating
the day and time the fault occurred.
If an error has occurred, word 1 of the response returns a negative
value.

Example
In this example, Fault Queue Entry number 3 was retrieved from a
1336 PLUS drive. The drive response returned the ASCII text Drive
Reset Flt, with each character reversed. The fault code for this
example is 22.
Data File Format
0

PLC request

1792

3*

Drive response

18

1792

8303*

22*

\00\12

\07\00

\00\16

Drive response

3*

29252*

20313*

8293*

25938*

25971*

8308*

27718*

\03\00

rD

vi

eR

es

lF

* Example only These values vary depending on parameters and products.

Publication 2100-UM001A-US-P January 2000

E-18

Supported Emulated Block Transfer Commands

Fault Queue Size

Fault Queue Size gets the number of fault entries allowed in the fault
queue.

PLC Block Transfer Emulation Instruction Data

PLC request instruction length: 3 words
Drive response instruction length: 4 words
Figure E.11
Message Structure
PLC Request
Drive Response
Message Length
3
PLC Decimal Value
1793
0

Header Word 0

Header Word 1

Message Length
5

Header

PLC Decimal Value

1793 Message OK
30975 Message Error

Header

Header
Word 2

Word 0

Header Word 2

Word 1

Data

Fault Queue Size

Word 3

Message Operation
Fault Queue Size reads back the size of the fault queue available in
the product. Each product may have a different number of fault queue
entries available for storage.
If an error has occurred, word 1 of the response returns a value of
-30975.

Example
In this example, a 1336 PLUS drive was used. This product has a fault
queue of four storage locations available to store faults. This value is
seen in word 3 of the response header message.
Data File Format
0

PLC request

1793

Drive response

1793

4*
* Example only These values vary depending on parameters and products.

Publication 2100-UM001A-US-P January 2000

Supported Emulated Block Transfer Commands

Trip Fault Queue Number

E-19

Trip Fault Queue Number provides the fault queue number of the
fault that caused the device to trip.

PLC Block Transfer Emulation Instruction Data

PLC request instruction length: 3 words
Drive response instruction length: 4 words
Figure E.12
Message Structure
PLC Request
Drive Response
Message Length
3

Header Word 0

Header

Message Length

4
PLC Decimal Value
1794
0

Word 0

PLC Decimal Value

1794 Message OK
30984 Message Error

Header Word 1

Header Word 2

Header
Word 1
Header

Word 2
Header

Number of Trip Fault

Word 3

Message Operation
Trip Fault Queue Number provides the number of the entry in the
fault queue that tripped the device in word 3 of the drive response.
The fault queue number is 0 when the device is not faulted.
If an error has occurred in the block transfer, word 1 of the response is
negative.

Example
In this example, the device has stored a fault in the first entry of the
fault queue that caused the drive to trip. Word 3 of the response
indicates the entry number.
Data File Format
0

PLC request

1794

Drive response

1794

1*
* Example only These values vary depending on parameters and products.

Publication 2100-UM001A-US-P January 2000

E-20

Supported Emulated Block Transfer Commands

Digital Input Parameter Read

Digital Input Parameter Read reads the value of the digital input
parameter based on the status of the digital inputs.

PLC Block Transfer Emulation Instructions Data

PLC request instruction length: 3 words
PLC response instruction length: 1 word
Figure 7.4
Message Structure

PLC Request
Module Response
Header Word 0
XXXX

Header Word 0

xxxx
Header Word 1
XX 06

Header Word 2
OEXX
Data 1
93
Data 2
4015
Data 3
01

Publication 2100-UM001A-US-P January 2000

Header Word 1
XX02
Header Word 2
8EXX

Data
XXXX

Supported Emulated Block Transfer Commands

E-21

Message Operation
Digital Input Parameter Read reads the value of the digital input
status. Consists of 4 bits of data with each bit corresponding to the
status of 1 input. A 1 indicated power applied to unit and a 0
indicates no power to the unit.

Example
In this example the value of Digital Input Parameters at HEX location
4015 (Note: GK61 parameters can always be found at 4000hex plus
the parameter number independent of the SCANport device attached.
Thus the digital input parameter is always located at parameter
4015hex for any GK61 configuration.) Here the PLC request data
from the module and returns a value at word 3 or the response. This
value can then be decoded to determine input status.

PLC request

xxxx

xx06

oexx

0093

4015

0001

GK61 Response

xxxx

xx02

8exx

1111

This example shows all inputs have power applied. This value can vary from 0000-1111 in any combination.

In this example, six parameters were written to a 1336 PLUS drive.

Note: All values shown in HEX.

Publication 2100-UM001A-US-P January 2000

E-22

Supported Emulated Block Transfer Commands

Publication 2100-UM001A-US-P January 2000

Index

Numerics
2100-GK61
default settings, 3-1 to 3-2
description, 1-3
editing parameters in, 3-3
EDS file, 4-7
function, 1-1
hardware, 1-6
illustration, 1-6
installation, 2-1
LEDs, 7-1 to 7-3
network node address, B-17
parameters, B-17 to B-23
resetting, B-20
setting up, 1-7
specifications, A-1
troubleshooting, 7-1
A
audience for this manual, P-1
B
baud rate
DeviceNet
parameter, B-17
setting, B-2
block transfer emulation, refer to emulated
block transfer commands
C
cables
DeviceNet
connecting to adapter, 2-7
selecting, 2-1
SCANport
connecting to module, 2-3

selecting, 2-1
change of state, B-7
Cyclic, B-8
D
data rate on DeviceNet, see baud rate
datalinks
description, B-2
list of, B-17
using, B-3
DeviceNet
cable, 2-2
definition, P-2
network node addresses, B-17
overview, 1-1
setting data rate, B-2
RSNetWorx
configuring an SLC scanner, 4-17
creating an EDS file for SCANport
product, 4-4
editing a modules parameters, 3-3
using online mode, 4-2
DeviceNet objects, C-1 to C-26
connection, C-6
DeviceNet, C-5
identify, C-2
message router, C-4
parameter, C-10
PCCC, C-25
register, C-8
SCANport pass-through fault queue,
C-19
SCANport pass-through link, C-23
SCANport pass-through parameter,
C-18
SCANport pass-through warning
queue, C-21
Publication 2100-UM001A-US-P - January 2000

I2

Index

E
EDS files, 4-4
emulated block transfer commands
fault command write, E-15
fault queue entry read full, E-16
fault queue size, E-18
NVS functions, E-14
parameter read full, E-5
parameter value read, E-3
parameter value write, E-4
product ID number read, E-8
scattered parameter value read, E-10
scattered parameter value write, E-12
trip fault queue number, E-19
equipment required, 1-7
configuring a scanner, 4-1
installation
2100-GK61, 2-1
ladder logic programming, 5-1
F
fault configurable inputs, B-16
I

M
manual
audience, P-1
contents, P-1
conventions, P-3
purpose, P-1
master-slave communications, B-5
master-slave input configurations, B-24
master-slave output configurations, B-26
messaging
controlling devices with 1747-SDN,
6-16
controlling devices with 1771-SDN,
6-16
description, 6-10
emulated block transfer, E-1
examples, 6-14 to 6-16
explicit
1747-SDN scanner, 6-6
1771-SDN scanner, 6-3
N-file structure, D-1
writing to register object, 6-17
N

I/O data, B-3

network node address, B-17

installation
of 2100-GK61, 2-1

N-file structure, D-1

O

L
ladder logic programs
description, 5-2
example, 5-3 to 5-8
LEDs
DeviceNet, 7-2
location, 7-1
module, 7-2
SCANport, 7-3
Input Status

objects, refer to DeviceNet objects

P
parameters
module
datalinks, B-2
editing, 3-3
fault configurable inputs, B-16
list of, B-17 to B-23
SCANport product
using emulated block transfer
E-3 to E-13
peer-to-peer communications, B-12

Publication 2100-UM001A-US-P - January 2000

Index

I3

PLC
ladder logic programs, 5-5
polling, B-5
polling and change of state, B-10
polling and Cyclic, B-11
R
RSLogix, 5-1
S
safety precautions, P-2
SCANport
cables, 2-2
definition, P-2
peripherals, 1-5
products, 1-5
SLC
configuring to communicate with
module, 4-17
ladder logic programs, 5-7
specifications, A-1
T
technical support, P-3
terms and abbreviations, P-2
troubleshooting, 7-1

Publication 2100-UM001A-US-P - January 2000

I4

Index

Publication 2100-UM001A-US-P - January 2000

Publication 2100-UM001A-US-P January 2000

Copyright 2000 Rockwell International Corporation.

Printed in USA