Allen-Bradley Bulletin 100 DeviceNet Starter Auxiliary User Manual · 2019. 8. 15. · Operation...

Allen-BradleyBulletin 100DeviceNet StarterAuxiliaryCat. Nos.100-DNY41R, 100-DNY21R,100-DNY22R, 100-DNY42R, 100-DNY22S, 100-DNY42S

User Manual

Important User Information

Because of the variety of uses for this product, the user of and those responsible for applying this equipment must satisfy themselves as to the acceptability of each application and use of the equipment. In no event will the Allen-Bradley Company be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The illustrations shown in this manual are intended solely to illustrate the text of this manual. Because of the many variables and requirements associated with any particular installation, the Allen-Bradley Company cannot assume responsibility or liability for actual use based upon the illustrated uses and applications.

No patent liability is assumed by the Allen-Bradley Company with respect to use of information, circuits or equipment described in this text.

Reproduction of the content of this manual in whole or in part, without the written permission of the Allen-Bradley Company, is prohibited.

The information in this manual is organized in numbered chapters. Read each chapter in sequence and perform procedures when you are instructed to do so. Do not proceed to the next chapter until you have completed all procedures.

Attentions help you:

• Identify a hazard• Avoid the hazard• Recognize the consequences

Important: Identifies information that is especially important for successful application and understanding of the product.

!ATTENTION: Identifies information about practices or cirmcumstances that can lead to personal injury or death, property damage or economic loss.

of Contents

. . . . . . . . . . .i

. . . . . . . . . . ii

. . . . . . . . . . ii

. . . . . . . . . iii

. . . . . . . . . iv

Product Overview 1 . . . . . . . . 1-1. . . . . . . . 1-2. . . . . . . . 1-2. . . . . . . . 1-5. . . . . . . . 1-5

Installation1 . . . . . . . . 2-1. . . . . . . . 2-1. . . . . . . . 2-2. . . . . . . . 2-3. . . . . . . . 2-6. . . . . . . . 2-8. . . . . . . 2-14

Table Preface

Manual Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Who Should Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vocabulary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bill of Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DeviceNet Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . European Union Directive Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mounting and Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DSA Wiring Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input and Output Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical Wiring Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wiring the DeviceNet Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of C

Operation . . . . . . . . . . . . . . 3-1. . . . . . . . . . . . . . 3-1es) . . . . . . . . . . . 3-4. . . . . . . . . . . . . . 3-5. . . . . . . . . . . . . . 3-7. . . . . . . . . . . . . 3-14. . . . . . . . . . . . . 3-17. . . . . . . . . . . . . 3-20

Troubleshooting . . . . . . . . . . . . . . 4-1. . . . . . . . . . . . . . 4-1. . . . . . . . . . . . . . 4-1

Specifications . . . . . . . . . . . . . . A-1. . . . . . . . . . . . . . A-3. . . . . . . . . . . . . . A-5

ontents

Chapter 3Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Device Configuration and Electronic Data Sheets (EDS FilVendor Codes, Product Type Codes, Product Codes, and EDS Files. Advanced Device Configuration Parameters . . . . . . . . . . . . . . . . . . DeviceNet I/O Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DeviceNet Explicit Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Net Communication Status LED . . . . . . . . . . . . . . . . . . . . .

Chapter 4Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the DeviceNet Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix AGeneral . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

DeviceNet Information . . . . . . . . . . . B-1. . . . . . . . . . . B-2. . . . . . . . . . . B-2. . . . . . . . . . . B-4. . . . . . . . . . . B-6. . . . . . . . . . B-10. . . . . . . . . . B-15. . . . . . . . . . B-16. . . . . . . . . . B-17. . . . . . . . . . B-19. . . . . . . . . . B-20. . . . . . . . . . B-22

Appendix BDeviceNet Message Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Object Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identity Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DeviceNet Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assembly Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discrete Input Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discrete Output Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discrete Input Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discrete Output Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acknowledge Handler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preface

you with the information necessary to apply the ry using all firmware revisions. Described in this guring, and troubleshooting the Bulletin 100

rety before installing, operating, servicing, or eviceNet Starter Auxiliary.

of Rockwell Automation. (ODVA).

Using This Manual

Manual Objectives The purpose of this manual is to provideBulletin 100 DeviceNet™ Starter Auxiliamanual are methods for installing, confiDeviceNet Starter Auxiliary.

Important: Read this manual in its enticonfiguring the Bulletin 100 D

Allen-Bradley, DeviceNet Manager, PLC and SLC are trademarksDeviceNet is a trademark of Open DeviceNet Vendor Association

ii

rsonnel responsible for setting up and servicing thesience with and a basic understanding oion procedures, required equipment, and safety

etwork operations, including how slave devices cate with a DeviceNet master.

Description

es, manual organization, audience, vocabulary, reference precautions

vice features, catalog numbers, European Union Directive

ng, and hardware

information transfer

and fault descriptions

electrical, and communication specifications

ut the DeviceNet implementation

Manual Organization

Who Should Use This Manual

This manual is intended for qualified pedevices. You must have previous expercommunications terminology, configuratprecautions.

• You should understand DeviceNet noperate on the network and communi

Chapter Title

Preface Manual objectivmanuals, safety

1 Product Overview Packing list, decompliance

2 Installation Mounting, cabli

3 Operation Addressing and

4 Troubleshooting LED indications

Appendix A Specifications Environmental,

Appendix B DeviceNet Information Information abo

iii

e DeviceNet Manager™ Software for network mber 1787-MGR). This software package is

Vo

as DSA.

rogrammable Controller, PLC® controller, o

• You should be familiar with the use of thconfiguration (Allen-Bradley Catalog Nureferred to often in this manual.

cabulary In this manual we refer to:

• Bulletin 100 DeviceNet Starter Auxiliary

• DeviceNet as DNet or DNET

• Programmable Logic Controller as the PSLC™ controller.

• Earth Ground as GND.

• National Electric Code as NEC.

iv

ystem Planning and Installation Manual, Publication fore planning and installing a DeviceNet system. If cording to this document, unexpected operation and r. , please contact either the local Allen-Bradley

nd request a copy. .

Reference Manuals

et Manager Software Manual, Publication 1787-6.5.3et Scanner Module Installation Instructions, Publication 1747-5.8

et Scanner Module Configuration Manual, Publication 1747-6.5.2et Scanner Module Installation Instructions, Publication 1771-5.14

et Scanner Module Configuration Manual,tion 1771-6.5.118et Overview, Publication DN-2.5

nel familiar with DeviceNet devices and associated plement the installation, startup, configuration, and

f the DSA. Failure to comply may result in personal age.

Reference Manuals

Important: Read the DeviceNet Cable S1485-6.7.1, in its entirety bethe network is not installed acintermittent failures can occuIf this manual is not availableDistributor or Sales Office a

Product

For DeviceNet Manager Software: • DeviceNFor SLC 500 and 1747-SDN information: • DeviceN

• DeviceNFor PLC-5 and 1771-SDN information: • DeviceN

• DeviceNPublica

For DeviceNet cables and components: • DeviceN

!ATTENTION: Only personmachinery should plan or imsubsequent maintenance oinjury and/or equipment dam

Chapter 1

mtion:

Product Overview

Chapter Objectives This chapter contains the following infora

• The physical layout of the DSA

• Catalog number explanation

• DeviceNet compatibility

• European Union Directive Complianc

1-2 Product Overview

llowing items:

iliary provides a low-cost DeviceNet node for motor applications. It includes inputs that can be connected circuit breaker auxiliary contact, limit switch, 2-wire ower supply may be required; consult factory), etc., on solid-state output modules) that may be used to , etc.

scription Quantity

m I/O module 1

rminal block 5mm spacing 1

minal block 5mm spacing 1

block with test points (5.08mm) 1

tion 0100-5.3 1

Bill of Material Your DSA product package includes the fo

Device Description The Bulletin 100 DeviceNet Starter Auxstarters and general I/O communicationto hard contacts such as a contactor orproximity, 3-wire photoswitch (external pand outputs (with external power supplyenergize contactor(s), solenoids, lamps

Item De

DSA Module 22.5m

Input Plug Black pluggable te

Output Plug Grey pluggable ter

DeviceNet Daisy Chain Plug Grey daisy chain terminal

User Manual Publica

Product Overview 1-3

OutputConnecto

OU

TP

UT

Figure 1.1 DeviceNet Starter Auxiliary

DeviceNetConnector

InputConnector

Heade

INPUT

OUTPUT

InputStatus LE

OuputStatus LE

1-4 Product Overview

DeviceNet Starter Auxiliary is explained in Figure 1.2 gin with 100-DN, which stands for Bulletin 100

R

tion Fourth Position Fifth Position

puts/ Input Voltage Output Type

-out-out

1 = 120 V AC 2 = 24V DC

S = Solid StateR = Relay

Device Description (cont.)

Catalog Numbers

The catalog numbering scheme for the below. Note that all catalog numbers beDeviceNet.

Figure 1.2 Catalog Number Explanation100 - DN Y 4 1

First Position Second Position Third Posi

Bulletin Number Package Width Number of InOutputs

DN = DeviceNet X = 45mm Y=22.5mm

4 = 4-in/22 = 2-in/1

Product Overview 1-5

DeCo

device via the DeviceNet Protocol. It supports the OS) I/O messaging of the predefined master/slave very and Configuration Consistency Value.

EuDiCo

ropean Union or EEA regions, the following

tive 89/336/EEC Electromagnetic Compatibility le or in part:

tandard, Part 1 - Residential Environment

tandard, Part 2 - Industrial Environment

tandard, Part 1 - Residential Environment

tandard, Part 2 - Industrial Environment

ar and Control Gear Standard

cil Directive 73/23/EEC Low Voltage by applying nd Controlgear.

viceNet mpatibility

The DSA communicates as a group 2 slaveExplicit, Polled I/O, and Change of State (Cconnection set, Group 4 Faulted Node Reco

ropean Union rective mpliance

When this product is installed within the Euregulations apply.

EMC Directive

This product is tested to meet Council Direc(EMC) using the following standards in who

• EN 50081-1 EMC - Generic Emission S

• EN 50081-2 EMC - Generic Emission S

• EN 50082-1 EMC - Generic Immunity S

• EN 50082-2 EMC - Generic Immunity S

• EN 60947-1/A11 Low Voltage Switchge

Low Voltage Directive

This product is also designed to meet CounIEC 947/EN 60947 Low-Voltage Switchgear a

Chapter 2

Installation

Chapter Objectives This chapter contains information about:

• Device storage and operating environment

• Mounting the device

• Connecting and wiring the device

Read this chapter completely before you attempt to install or configure your DeviceNet Starter Auxiliary. Double check all connections and option selections before you apply power.

Storage and Operation

To prolong the product life, take the following precautions:

• Store within an ambient temperature range of -40°C to +85°C (-4 °F to 18 °F).

• Store within a relative humidity range of 0% to 95%, non-condensing.

• Avoid storing or operating the device where it could be exposed to a corrosive atmosphere.

• Protect from moisture and direct sunlight.

• Operate at an ambient temperature range of 0°C to +60°C (32°F to 14 °F).

2-2 Installation

Rail mounted or panel mounted (see Figure 2.1 n) clearance at the top to remove the DeviceNet e in the front for the input and output connector.

DIN Rail Mounting Clip

981)

3.63(92.22)

.22(5.7)

.177(4.5)

.43(10.9)

3.35(85)

Rail

ail

Back

Panel Mounting Screw Location

Mounting and Dimensions

The DeviceNet Starter Auxiliary may be DINbelow). The unit requires 37.4 mm (1-1/2 iconnector and 32.8mm (1-9/32 in) clearanc

Figure 2.1 Bulletin 100-DNY Dimensions

Output Wiring

Output Wiring

Input Wiring

Input Wiring

Top

.89 (22.5)

4.33(110)

1.50(38.11)

1.50(38.05)

3.07(78)

.71 (18.16) .71(18.16) 1.2

(32..20(.5)

.10(2.5).71 (18.16)

DIN

DIN R

DIN Rail

Front Side

INPUT

OUTPUT

Dimensions shown in inches (mm)

Installation 2-3

DSDi

l wiring diagrams for three versions of the DSA ific type is located on the right side of the device

123

OUT AT B

2 IN 3 NEG

External Connections

A Wiring agrams

Figure 2.2 through Figure 2.4 shows typicamodule. The wiring diagram for each spechousing.

Figure 2.2Wiring Diagram - 24V DC Input/Relay Output(Cat. No. 100-DNY42R shown)

DNET24V+

(RED)

CAN H (WHITE)

CAN L (BLUE)

DNET24V-

(BLACK)

4

OU

V+ IN 0 IN 1 IN

DC

DC

2-4 Installation

IN 1 IN 2 IN 3 NEG

1234

OUT A

OUT B

+

-24VP.S.


DSA Wiring Diagrams (cont.)

Figure 2.3 Wiring Diagram - 24V DC Input/Solid-State Output(Cat. No. 100-DNY42S Shown)

DNET24V+

(RED)

CAN H (WHITE)

CAN L (BLUE)

DNET24V-

(BLACK)

V+ IN 0

DC

DC

Installation 2-5

12

OUT A

VCOM IN 1IN 0

L2

L1

120V AC


Figure 2.4Wiring Diagram - 120V AC Input/Relay Output(Cat. No. 100-DNY 21R shown)

DNET24V+

(RED)

CAN H (WHITE)

CAN L (BLUE)

DNET24V-

(BLACK)

2-6 Installation

input and output connectors.

Grey Plug5mm Pitch

OutputConnector

Header

OU

TP

UT

Input and Output Connections

Figure 2.5 below shows the location of the

Figure 2.5 Input/Output Connections

DeviceNetConnector

InputConnector

Header

Black Plug5mm Pitch

INPUT

OUTPUT

InputStatus LED

OuputStatus LED

Installation 2-7

ourced from its isolated internal power supply via he power is derived from the DeviceNet power

ower supply for the 120V inputs.

wer supply connected between Ext 24V+ (Pin 1) r header.

4V DC according to ratings in Appendix A,

t rating information.

ternal power for 24V

24V DC Input DSA

For the 24V DC input DSA, input power is sthe V+ pin on the input connector header. Tsource (24V +).

120V AC Input DSA

The 120V AC Input DSA requires external p

24V DC Solid-State Output

The outputs require an external 24V DC poand Ext 24V- (Pin 4) of the output connecto

Relay Output

DSAs are suitable for either 240/120V AC or 2Specifications.

Important: Refer to Appendix A for contac

!ATTENTION: Do not apply exDC input version.

2-8 Installation

lay Output) and Sensor Connection

for equivalent.

r source

plication

193-DNY42R

NEG "DSA"

IN 3 "DSA"

V+ "DSA"

DC

DC

Typical Wiring Examples

Figure 2.6 Motor Starter with DSA (24V DC Input/Re

① Remote Device: 42 GRM 9000-QD or equivalent. Consult factory

② Transient Suppressor recommended

③ It is suggested that coil power be supplied from a separate powe

➃ Remote Device: Consult factory for proper 3-wire photoswitch ap

M

NEMA Wiring Diagram

Installation 2-9

lay Output) and Sensor Connection

for equivalent.

r source

plication.

➃

DSA Cat. No. 100-DNY42RV+

Figure 2.7 Motor Starter with DSA (24V DC Input/Re

① Remote Device: 42 GRM 9000-QD or equivalent. Consult factory


③ It is suggested that coil power be supplied from a separate powe

➃ Remote Device: Consult factory for proper 3-wire photoswitch ap

IEC Wiring Diagram

2-10 Installation

id-State Output) and Sensor Connection

①

②

③

Cat. No. 100-DNY42S

V+

Typical Wiring Examples (cont.)

Figure 2.8 Motor Starter with DSA (24V DC Input/Sol

① Remote Device: 871 TM DHSNE or equivalent:


③ Suggested external 24V DC power supply

NEMA Wiring Diagram

Installation 2-11

id-State Output) and Proximity Sensor Connection

V+

DSA Cat. No. 100-DNY42S

Figure 2.9 Motor Starter with DSA (24V DC Input/Sol

① Remote Device: 871 TM DHSNE or equivalent:


③ Suggested external 24V DC power supply

IEC Wiring Diagram

2-12 Installation

AC Input / Relay Output)

Incom ing Lines

FuseClips

(W henused)

L1

1L1

L2

1L2

DS

L3

1L3

Cat. No. 100-DNX41R

DNET 24V-CANLSHIELDCANHDNET 24V+

BLACKBLUEBARE

WHITERED

COMIN 0IN 1IN 2IN 3

OUT A (1)OUT A (2)OUT B (3)OUT B (4)

1L11L2

1

X2 X1

TRANS.

GND

"J"H1 H2 H3 H4

Vcom

Typical Wiring Examples (cont.)

Figure 2.10 Reversing Motor Starter with DSA (120V

13 135L3

5L3

3L2

3L2

1L1

1L1

T36

T36

T24

T24

T12

T12

A1A1

A2

A2

A2

R F14 14

1

7

2 1

T3T2T1

T36

T24

T12

9 6

3

8

110

X2

X2

1L3

1L3

1L31L2

1L2

1L21L1

1L1

1L1

3 5

3

59 9

697

985

M

7 3

11

1

891011

2

1

X2

6

DeviceNetComm Cable

NEMA Wiring Diagram

Installation 2-13

AC Input / Relay Output)

am

DSA Cat. No. 100-DNY41R

Figure 2.11 Reversing Motor Starter with DSA (120V

IEC Wiring Diagr

2-14 Installation

through the DeviceNet Connector. DeviceNet r terminal block as shown in Table 2A. Refer to ption specifications.

nal bloc k

Wiring theDeviceNet Connector

The DSA receives power and communicationscable wires connect to the plug-in connectoAppendix A, Specifications, for power consum

Figure 2.12 Wiring the DeviceNet Connector

Dual position DeviceNet termiGray connector 5.08mm pitch

NOTE: Use either single or dual terminal block as required. Fasten the two screws on the DeviceNet plug to the top of the DSA module to avoid accidental disconnection.

Installation 2-15

Color

- Black

Blue

Bare

White

4V DC+ Red

Table 2A

① Class II Power Limited NEC 725.

Terminal Signal Function

1 V- Common 24V DC

2 CANL Signal Low

3 SHIELD Shield

4 CANH Signal High

5 V+ Power Supply① 2

Chapter 3

Operation

Chapter Objectives This chapter contains the following information:

• Configuring the DSA modul

• I/O message format

• Communication status LED

Basic Device Configuration

Configuring the device consists of setting the DeviceNet communication port baud rate and the DeviceNet MAC ID (commonly referred to as the node address).

DeviceNet Baud Rate

When the DSA is energized, the device will attempt to determine the baud rate at which the other devices on the network are operating and set its baud rate to the same baud. While the DSA is determining the network baud rate, the communication status LED will blink green for 1/4 second, red for 1/4 second and then turn off.

3-2 Operation

, the device will be unable to determine a network D will continue to execute the above sequence

oper baud rate is set, the communication status if a connection is established between it and

ected.

abled, and a baud rate may be configured as follows:

ware. From the Utilities menu, choose Setup

ISABLE . See th Advanced Device on how to set parameter values.

missioning.... You see this screen:

Basic Device Configuration (cont.)

NOTE: If there is no traffic on the networkbaud rate, and the communication status LEuntil network traffic is detected. Once the prLED will either blink green, turn solid greenanother device, or turn red if an error is det

The above autobaud sequence may be dis

1. Execute the DeviceNet Manager™ softOnline Connection to go on-line.

2. Set the Autobaud parameter to a value of DConfiguration on page 3-7for instructions

3. From the Utilities menu, choos Node Com

Operation 3-3

k Apply Node Settings button. Click Close

y be set to a value from 0 to 63. Note that, in most by a master device, such as a Bulletin 1771 or 1747

enerally the factory default for slave devices. The as follows.

re and go on-line by choosing Setup Onlin

4. Choose the required baud rate and clicthebutton.

5. Cycle power to device.

DeviceNet MAC ID

The DeviceNet MAC ID (node address) maDeviceNet systems, node address 0 is usedScanner Module, and node address 63 is gDSA’s DeviceNet MAC ID may be changed

1. Execute the DeviceNet Manager softwaConnection in the Utilities menu.

3-4 Operation

missioning.... You see this screen:

Node Settings button.

address, various other parameters may also be oare and Electronic Data Sheet (EDS) files. that provide all of the information necessary for

Manager to access and alter the parameters of a uch as parameter minimum, maximum, and default contained in the EDS file.

Basic Device Configuration (cont.)

2. From the Utilities menu, choosNode Com

3. Choose a node address and click the Apply

Advanced Device Configuration and Electronic Data Sheets (EDS Files)

Besides configuring the baud rate and nodeconfigured using the DeviceNet Manager sftwEDS files are specially formatted ASCII filesa configuration tool such as the DeviceNet device. Information about each parameter svalues and parameter names and units are

Node address changed to 1

Operation 3-5

VePrPrED

n a variety of I/O configurations. Each I/O t of parameters and, therefore, each DSA type eviceNet Manager uses vendor codes, device type, to use for a given DSA type. DeviceNet Manager ter’s hard disk to store EDS files. This directory t type codes, product codes, and device revision is usually a directory named EDS, and for the

ted in the same directory as the DeviceNet izes the directory structure used by DeviceNet SA products.

the DSA; you will need to place the EDS files in ry structure as shown in Table 3.B. You may ion of the EDS files from the internet at http://

ndor Codes, oduct Type Codes, oduct Codes, and S Files

DeviceNet Starter Auxiliaries are available iconfiguration supports a slightly different seneeds its own EDS file. For example, the Dand product codes to identify which EDS fileuses a directory structure on its host compustructure is based on vendor codes, producnumbers. The root of this directory structureDeviceNet Manager, this EDS directory is locaManager executable file. Table 3.B summarManager to store EDS files for the various D

Important: EDS files are not included withyour DeviceNet Manager directodownload the most current revivwww.ab.com/networks/eds.

3-6 Operation

as follows: “product_code”.cod\

A vendor code for Allen-Bradley, “7.type Discrete I/O device, “1060.cod” through A types and “4.eds” represents the major revision

Cat. No. Directory Structure

00-DNY41R eds\1.vnd\7.typ\1060.cod\4.eds




00-DNY42S eds\1.vnd\7.typ\1064.cod\4.eds

00-DNY22S eds\1.vnd\7.typ\1065.cod\4.eds

Vendor Codes, Product Type Codes, Product Codes, and EDS Files (cont.)

Table 3.B EDS Files

Note that the EDS file directory structure iseds\ “vendor_code”.vnd\ “device_type”.typ\ “major_revision”.eds

In the directory structure, “1.vnd” is the ODVsignifies that the DSA is a General Purpose“1065.cod” are the product codes for the DSof the firmware in this release.

Product Code Device Type

1060 4-120V In / 2-Relay Out 1

1061 2-120V In / 1-Relay Out 1

1062 4-24V In / 2-Relay Out 1

1063 2-24V In / 1-Relay Out 1

1064 4-24V In / 2-Solid-state Out 1

1065 2-24V In /1-Solid-state Out 1

Operation 3-7

AdCoPa

EDS files and appear in a Device Configuration ager. To invoke a Device Configuration

ou see this window:

vanced Device nfiguration rameters

The following parameters are defined in theEnhanced Modwindow of the DeviceNet Manwindow:

1. Select a DSA in a Network Who window. Y

3-8 Operation

e this window:
Advanced Device Configuration Parameters (cont.)
2. Press the Config Device... button. You se

Operation 3-9

double-click on the desired parameter or select the button. For example, when you double-click this screen.

ple, to disable the Autobaud parameters,

k the Save to Device button. Click OK .

may occur when g to the application

3. To change the settings of a parameter, parameter and click the Modify Parameteron the Autobaud parameter, you will see

4. Make the desired changes. In this examclick the DISABLE option.

5. Once you have made your changes, clic

!ATTENTION: Injury or damageparameters are not set accordinrequirements.

3-10 Operation

, the DSA will attempt to match the network baud a value DISABLE, the power-up autobaud feature changed, the new value will be applied when Autobaud screens are shown above.)

during a communication fault. The factory communication fault. This behavior may be

e during a communication fault. Refer to Chapter 4


Autobaud

When this parameter has the value ENABLErate at power-up. When this parameter hasis disabled. When the Autobaud parameter ispower is cycled after saving to device. (The

Fault State

This parameter defines the behavior of outputsdefault behavior is to reset outputs during achanged so that outputs hold their last statfor instructions on resetting after faults.

Operation 3-11

during an idle state (when a PLC controller is vior is to reset outputs during an idle condition. uts hold their last state during an idle condition.

Idle State

This parameter defines the behavior of outputsin program mode). The factory default behaThis behavior may be changed so that outp

3-12 Operation

for the DSA to recognize a valid input signal. This


Off to On Delay

This parameter defines the time necessaryparameter defaults to a value of 0 (no delay).

Operation 3-13

ut signal dropping below its valid level to lts to a value of 0 (no delay).

On to Off Delay

This parameter defines the time from an inprecognition by the DSA. This parameter defau

3-14 Operation

-Bradley DeviceNet scanners to turn on a DSA’s , and also to read a DSA’s fault status. The size and predetermined for communication with DeviceNet

nd consumes single-byte I/O messages to and a when one of its inputs changes state, or one of its the device produces data when a Change of State also produces data in response to an I/O message roduces data when a Polled I/O connection is onsumed data is given in the tables below. Note ven if some bits in the message are unused.

Bit 2 Bit 1 Bit 0

Input3 Input2 Input1

X Output2 Output1

DeviceNet I/O Messaging

DeviceNet I/O messages are used by Allenoutputs, to read the status of a DSA’s inputsformat of these DeviceNet I/O messages isStarter Auxiliaries.

The DeviceNet Starter Auxiliary produces afrom a master. The device can produce datI/O points becomes faulted. This is the way(COS) connection is allocated. The device from its master. This is the way the device pallocated. The format of the produced and cthat all I/O messages are 1 byte in length, e

Table 3.C 4-Input/2-Output Devices.

① Produces (Transmit) 1 byte of data② Consumes (Receive) 1 byte of dataX=Reserved

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3

Produces① InStat X OutStat2 OutStat1 Input4

Consumes② X X X X X

Operation 3-15

by a DSA consist of individual bits, each bit r the health status of some aspect of the DSA. Th

individual bit in a DSA’s produced I/O message.

it 2 Bit 1 Bit 0

Stat A Input 1 Input 0

X X Output A

Table 3.D 2-Input/1-Output Devices

① Produces (Transmit) 1 byte of data② Consumes (Receive) 1 byte of dataX=Reserved

Reading Input Status and Fault Status

The DeviceNet I/O messages that are producedcontaining the status of an individual input otable below contains a description of each

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 B

Produces① InStat X X X X Out

Consumes② X X X X X

3-16 Operation

umed by a DSA consist of individual bits, each bit . The table below contains a description of each e.

n

0 (0=OFF, 1=ON)

1 (0=OFF, 1=ON)

F, 1=ON) (4 in/2 out only)

F, 1=ON) (4 in/2 out only)

healthy, 1=faulted)

1=faulted) (4 in/2 out only)

healthy, 1=faulted)

DeviceNet I/O Messaging (cont.)

Table 3.E

Turning the Outputs ON or OFF

The DeviceNet I/O messages that are conscontaining the status of an individual outputindividual bit in a DSA’s consumed I/O messag

Bit # Name Descriptio

0 Input0 The ON/OFF status of Input

1 Input1 The ON/OFF status of Input

2 Input2 The ON/OFF status of Input 2 (0=OF

3 Input3 The ON/OFF status of Input 3 (0=OF

4 OutStatA Health status of Output A (0=

5 OutStatB Health status of Output B (0=healthy,

6 x Not used

7 InStat Health status of all inputs (0=

Operation 3-17

DeM

used to configure a DeviceNet device. Manager” use Explicit Messages when uch as Rockwell Software’s “RSServer fo

build custom DeviceNet system user interfaces foeful to be able to control a DSA output or read the

ation:

in response to the message. Services exist for riting information to a device.

send the service to. Classes are identified by their a complete list of classes that are implemented in

n

OFF, 1=ON)

ON) (4 in/2 out only)

Table 3.F

viceNet Explicit essaging

DeviceNet Explicit Messages are generallyConfiguration tools such as the “DeviceNetcommunicating with a device. Some tools, sDeviceNet”, use Explicit Messages to help a PC. When using such a tool, it is often usstatus of a DSA input using explicit messaging.

Explicit messages contain the following inform

Service: Tells the device what action to takereading information from a device and for w

Class: Tells the device which object class tonumeric “class code”. Appendix B contains the DSA.

Bit # Name Descriptio

0 OutputA Controls Output A (0=

1 OutputB Controls Output B (0=OFF, 1=

2 - 7 x not used

3-18 Operation

or more “instances” of that class in a given device. e 1. The value “0” refers to the class itself, not any contains a complete list instances that are

formation related to an object class or instance. number 1. Note that attributes need not be s a complete list of attributes for each class and

single instance of the class “Discrete Input Point” tance 1, Input 1 is represented by instance 2, etc. Value” (attribute 3,) which contains the ON/OFF input status of input 1 can be done by sending an t :

0E hex)

DeviceNet Explicit Messaging (cont.)

Instance: Each object class can contain oneInstances are numbered starting at instancindividual instance of that class. Appendix Bimplemented for each class in the DSA.

Attribute: An attribute is a single piece of inAttributes are numbered starting at attributenumbered sequentially. Appendix B containinstance implemented in the DSA.

Reading Input Status

Each input in the DSA is represented by a (class code 8). Input 0 is represented by insEach instance contains an attribute named “status of that input. Therefore, reading the explicit message with the following informaion

Service: Get_Attribute_Single (service codeClass: “Discrete Input Point” (class code 8Instance: 1 (since we want to read input 0)Attribute: “Value” (attribute number 3)

Operation 3-19

single instance of the class “Discrete Output Point” d by instance 1 and Output B is represented by ute named “Value” (attribute 3), which is used to olling Output A can be done by sending an explicit

0 hex)

t A)

e output ON

d when trying to control an output with explicit

cit messaging if a DeviceNet I/O connection SA. For example, if a DeviceNet scanner has ge attempting to control an output will result in

response to the message, and the output will not

cit messaging unless the explicit connection has a ppendix B for details on the explicit message

Turning the Outputs ON or OFF

Each output in the DSA is represented by a(class code 9), e.g., Output A is representeinstance 2. Each instance contains an attribturn the output ON or OFF. Therefore, contrmessage with the following information:

Service: Set_Attribute_Single (service code 1Class: “Discrete Output Point” (class code 9)Instance: 1 (since we want to control outpuAttribute: “Value” (attribute number 3)Value: 0 to turn the output OFF, 1 to turn th

There are a few special rules to keep in minmessages:

1. An output cannot be controlled via expliexists and is sending “live” data to the Dcontrol of a DSA, then an explicit messathe DSA returning an error response inchange state.

2. An output cannot be controlled via explinon-zero Expected Packet Rate. (See Aconnection object instance).

3-20 Operation

d/green) LED that provides status information on marizes the operation of the LED.

Description

alizing.

ther to a duplicate node address being coverable fault.

Device is allocated to a master.

allocated to a master.

Device Net Communication Status LED

The Mod/Net status LED is a bi-colored (reDeviceNet communications. Table 3.D sum

Table 3.G Communication Status LED

Comm LED

Color State

None No Device Power, or initi

Red Solid Recoverable fault due eidetected or another unre

Green Solid Normal operating state.

Green Flashing Device is on-line but not

Chapter 4

ou troubleshoot your DeviceNet Starter Auxiliary.

the DSA will auto-reset all faults.

s status information on the status of the DeviceNet to use the LED to detect common operation problems.

Troubleshooting

Chapter Objectives The purpose of this chapter is to help y

Resetting Faults This procedure is no longer required, as

Using the DeviceNet Status LED

The communication status LED provideStarter Auxiliary. Table 4.0 shows how

4-2 Troubleshooting

What To Do:

Check the DeviceNet power and cable connections.

baud The DSA cannot determine the network baud rate if there is no network traffic. Induce network traffic by invoking a Network Who in DeviceNet manager.

des Using the DeviceNet Managers Node Commissioning feature, set the DSA node address to a unique node address.

. Cycle power to the network. If the fault still exists, return the DSA for inspection.

Using the DeviceNet Managers Node Commissioning feature, set the baud rate to the baud rate of the rest of the network.

No action required.

aster. Check that the DeviceNet master is configured correctly. If an Allen-Bradley PLC scanner is being used, check that the scan list is correctly configured.

Table 4.0

Color State What It Means:

None Off The DSA is not receiving power.

GreenRedOff

Green for 1/4 sec.Red for 1/4 sec.Off for 5 sec.

The DSA is trying to determine the networkrate. One cycle per baud rate attempt.

Red Solid Duplicate DeviceNet node address. Two nocannot have the same address.

Red Solid Diagnostics detected a fatal fault in the DSA

Red Solid Invalid baud rate setting if Auto-Baud is disabled.

Green Solid Normal operating state.

Green Flashing The DSA is on-line but not allocated to a m

Appendix A

Specifications

General Table A.1

Electrical

DeviceNet Supply Voltage 11 to 25 V DC

DeviceNet Input Current Maximum 270mA

Surge Current at Power Up Less than 3A for 5ms

DeviceNet Power Consumption 3W Maximum

Environmental

Ambient Temperature OperatingStorage

-25 to 60°C (-32 to 140°F)-40 to 85°C (-40 to 185°F)

Relative Humidity 0 to 95% non-condensing

Shock OperatingNon-operating

30 g peak acceleration50 g peak acceleration

Vibration 2.5 g @ 10-500 Hz

DeviceNet Communications

Baud Rates 125, 250, 500 kbps

Distance Maximum 500 meters (1640 ft) @125 kbps200 meters (656 ft) @250 kbps100 meters (328 ft) @500 kbps

A-2 Specifications

CSA certifiedUL listedCE marked for all applicable directives

Sizes

colla0.2 -2.5 mm2/0.2 -2.5 mm2/24-12 AWG

0.25-2.5 mm2/0.25-2.5mm2

anded

colla

colla

0.2-1 mm2/ 0.2 - 1.5mm2

0.25 - 1 mm2

0.5-1.5mm2

oltageurrent

300V5A

Use 75°C copper wire minimum0.5 - 0.6 Nm (4.4-5.3 lb-in)

2.5mm2 (14 AWG)

General (cont.) Table A.1 (Cont.)

ApprovalsAgency Certification

Terminal BlockPlugs: Pitch 5 and 5.08mmConnection Capacity

Solid/Stranded/ Conductor

Stranded with Ferrules with/without Plastic

Multiple Connection (2 conductors with same cross section)

Solid/Str

Stranded with Ferrules without Plastic

Stranded with TWIN ferrules with plastic

Headers: Pitch 5 and 5.08mm V C

Wire DetailsWire TypeTightening TorqueWire Size

Specifications A-3

InNY41RNY21R

V AC

AC

mA

puts Table A.2 Cat. Nos. 100-DNY41R, 100-DNY21R

Inputs per Device 4 : 100-D2 : 100-D

On-State Voltage Range 50/60 Hz 80 - 132

On-State Current

MaximumMinimum

2mA1.2mA

Off-State Voltage Maximum 40V AC

Off-State Current Minimum 0.6mA

Transition Voltage 40 - 79V

Transition Current 0.6 - 1.2

A-4 Specifications

100-DNY42S, 100-DNY22S

100-DNY42R, 100-DNY42S 100-DNY22R, 100-DNY22S

- 30V DC

A @ 30VA @ 10V

DC

mA

10V DC

- 3mA

- 25V DCA

Inputs (cont.) Table A.3 Cat. Nos. 100-DNY42R, 100-DNY22R,

Inputs per Device 4 :2 :

On State Voltage Range 10

On State Current MaximumMinimum

11m3m

Off State Voltage Maximum 5V

Off State Current Maximum 1.5

Transition Voltage 5 -

Transition Current 1.5

Sensor Source VoltageCurrent

19 35m

Specifications A-5

Ou DNY42R, 100-DNY22R (Relay Output)

2 - 100-DNY41R, 100-DNY42R1 - 100-DNY21R, 100-DNY22R

240V AC, 30V DC

3600 VAUL: B300IEC: AC-15, 5A

5A

tputs Table A.4 Cat. Nos. 100-DNY41R, 100-DNY21R, 100-

Outputs per Device

Outputs Voltage Range Maximum

Switching Capacity Maximum

Thermal Continuous Current (per output) Maximum

A-6 Specifications

(Solid-State Output)

2 - 100-DNY42S1 - 100-DNY22S

15 - 30V DC, ± 0%

0.25V @ 2A

2A per output

1.5mA

4A for 50ms

Outputs (cont.) Table A.5 Cat. Nos. 100-DNY42S, 100-DNY22S

Outputs per Device

Output Voltage Range

On-State Voltage Drop Maximum

On-State Current (per output) Maximum

Off-State Leakage Current Maximum

Surge Current (per output)

Appendix B

DeviceNet InformationServices Supported The DSA supports Explicit messaging, Polled I/O messaging, and Change of Stat

(COS) messaging of the predefined master/slave connection set.

This appendix defines the DeviceNet message types, class services, and objects that are supported by the DSA.

DeviceNet Message Types

The DSA supports the following message types:

Table B.1 DeviceNet Message Types

xxxxxx = DSA Node Address

Identifier Field Message Identifier Field

10xxxxxx111 Duplicate MAC ID Check Messages

10xxxxxx110 Unconnected Explicit Request Messages

10xxxxxx101 Master I/O Poll Command/ COS Messages

10xxxxxx100 Master Explicit Request Messages

10xxxxxx011 Slave Explicit Response Messages

10xxxxxx010 Master COS Acknowledge Messages

01111xxxxxx Slave I/O Poll Response Messages

01101xxxxxx Slave I/O COS Messages

11111101100 Communication Faulted Response Message

11111101101 Communication Faulted Request Message

B-2

lasses:

n and general information about the device.

Object

oint

t Point

roup

t Group

andler

Object Classes The DSA supports the following object c

Table B.2 Object Classes

Identity Object Class Code 1 (01hex)

The Identity Object provides identificatio

Class Attributes: None

Number of Instances: 1

Class

1 (01hex) Identity

3 (03hex) DeviceNet

4 (04hex) Assembly

5 (05hex) Connection

8 (08hex) Discrete Input P

9 (09hex) Discrete Outpu

15 (0Fhex) Parameter

29 (1Dhex) Discrete Input G

31 (1Fhex) Discrete Outpu

43 (2Bhex) Acknowledge H

B-3

ataype

Value

171060=100-DNY41R1061=100-DNY21R1062=100-DNY42R1063=100-DNY22R1064=100-DNY42S1065=100-DNY22S

ture of:INTINT

45

D 0=not owned by master1=owned by master

T unique number for each deviceture of:INTRING

14DSA 4-in/2-outor DSA 2-in/1-outunique number for any parameter configuration

Table B.3 Instance Attributes

Attribute IDAccess

RuleName

DT

1 Get Vendor UINT2 Get Device Type UINT3 Get Product Code UINT

4 Get Revision Major Revision Minor Revision

Struc US US

5 Get Status WOR

6 Get Serial Number UDIN7 Get Product Name

String Length ASCII String

Struc US ST

9 Get ConfigurationConsistencyValue

UINT

B-4

ration and status information for the device.

Service Name

Get_Attribute_Single

Reset

Data Type Value

UINT 2

Identity Object (cont.)

Table B.4 Common Services

DeviceNet Object Class Code 3 (03hex)

The DeviceNet Object provides configu

Table B.5 Class Attributes


Service CodeImplemented for:

Class Instance

14 (0Ehex) Yes Yes

5 (05hex) No Yes

Attribute ID Access Rule Name

1 Get Revision

B-5

Data Type Value

USINT 0 - 63USINT 0=125K

1=250K2=500K

BOOL 0=Not Set1=Set

USINT 0-255Structure of: BYTE USINT

Allocation_byte0-63 = address255 = unallocated

BOOL 1=Disable0=Enable

Service Name


Set_Attribute_Single

Allocate_Master/Slave _Connection_Set

Release_Master/Slave _Connection_Set




1 Get/Set Node Address2 Get/Set Baud Rate

3 Get BOI

4 Get/Set Bus-off Counter5 Get Allocation Info

Allocation Choice Master Node Addr

100 Get/Set Auto Baud Disable


Class Instance

14 (0Ehex) Yes Yes

16 (10hex) No Yes

75 (4Bhex) No Yes

76 (4Chex) No Yes

B-6

f multiple objects, allowing data to or from each object nection. I/O Assemblies are generally used to pass nfiguration assemblies are used to pass device it connection.

, 2-input/1-output devices consume the data attribute ttribute has the following format:

by 2-in/1-out devices)

Data Type Value

UINT 105 (69hex) for 4-in/2-out106 (6Ahex) for 2-in/1-out

Bit 2 Bit 1 Bit 0

OutputA

Assembly Objects Class Code 4 (04hex)

The Assembly Object binds attributes oto be sent or received over a single coninformation over an I/O connection. Coconfiguration information over an explic


Format of I/O Assembly Data AttributeFor polled I/O and COS I/O connectionsof output assembly instance 31. This a

Table B.9 Instance 31 (Output Assembly used


2 Get Max Instance

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3

0

B-7

input/2-output devices consume the data attribute ute has the following format:

-in/2-out devices)

Attribute mapping for Output Assemblies.

input/2-output devices produce the data attribute of has the following format:

in/2-out devices)

it 2 Bit 1 Bit 0

OutputB OutputA

Instance NumberAttribute

Name Number

1 Value 3

2 Value 3

3 Bit 2 Bit 1 Bit 0

t3 Input2 Input1 Input0

For polled I/O and COS I/O connections, 4-of output assembly instance 32. This attrib

Table B.10 Instance 32 (Output Assembly used by 4

Table B.11 indicates the I/O Assembly Data

Table B.11

For polled I/O and COS I/O connections, 4-input assembly instance 105. This attribute

Table B.12 Instance 105 (Input Assembly used by 4-

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 B

0

Data NameClass

Name Number

OutputA Discrete Output Point 9 (09hex)

OutputB Discrete Output Point 9 (09hex)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit

0 InStat OutStatB OutStatA Inpu

B-8

, 2-input/1-output devices produce the data attribute of bute has the following format:

y 2-in/1-out devices)

ata Attribute mapping for Input Assemblies.

Bit 2 Bit 1 Bit 0

utStatA Input1 Input0


Name Number

1 Value 3

2 Value 3

3 Value 3

4 Value 3

1 Status 4

2 Status 4

x) 1 Status 5

Assembly Objects (cont.)

For polled I/O and COS I/O connectionsinput assembly instance 106. This attri

Table B.13 Instance 106 (Input Assembly used b

Table B.14 indicates the I/O Assembly D

Table B.14

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3

0 InStat O

Data NameClass

Name Number

Input0 Discrete Input Point 8 (08hex)




OutStatA Discrete Output Point 9 (09hex)

OutStatB Discrete Output Point 9 (09hex)

InStat Discrete Input Group 29 (1Dhe

B-9

e

mbly Data Attribute mapping.

2 Bit 1 Bit 0

aud IdleState FltState


Name Number

1 Fault State 7

1 Idle State 9

6 Auto Baud 3

1 Off-On Delay 6

1 On-Off Delay 7

Format of Configuration Assembly Data Attribut

Table B.15 Instance 104 (Configuration Assembly)

Table B.16 indicates the Configuration Asse

Table B.16

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit

0 AutoB

1 On Delay (low byte)

2 On Delay (high byte)

3 Off Delay (low byte)

4 Off Delay (high byte)

Data NameClass

Name Number

FltState Discrete Output Group 30 (1Ehex)

IdleState Discrete Output Group 30 (1Ehex)

AutoBaud Parameter 15 (0Fhex)

On Delay Discrete Input Group 29 (1Dhex)

Off Delay Discrete Input Group 29 (1Dhex)

B-10

sources associated with both Each individual Connection Instance represents one o

Service Namece



Assembly Objects (cont.)

Table B.17Common Services

Connection Object Class Code 5 (05hex)

The Connection Object manages the reI/O and Explicit Message connections. the end-points of a DeviceNet connection.




Class Instan

14 (0Ehex) Yes Yes

16 (10hex) No Yes

B-11

Explicit Connection)

e Data Type Value

USINT 0=nonexistent1=configuring3=established4=timed out

USINT 0=Explicit Message

er USINT 131 (83hex) - Server,

Transport Class 3n ID UINT 10xxxxxx011

xxxxxx=node address

on ID UINT 10xxxxxx100xxxxxx=node address

teristics USINT 33 (21hex)

n Size UINT 97 (61hex)

on Size UINT 97 (61hex)

te UINT in millisecondsUSINT 1=auto delete

3=deferred deleten Path Length UINT 0n Path Emptyon Path Length UINT 0on Path Empty

Table B.18 Instance 1 Attributes (Predefined Slave

Attribute ID Access Rule Nam

1 Get State

2 Get Instance Type

3 Get Transport Class Trigg

4 Get Produced Connectio

5 Get Consumed Connecti

6 Get Initial Comm Charac

7 Get Produced Connectio

8 Get Consumed Connecti

9 Get/Set Expected Packet Ra12 Get Watchdog Action

13 Get Produced Connectio14 Get Produced Connectio15 Get Consumed Connecti16 Get Consumed Connecti

B-12

lave Polled I/O Connection)

eDataType

Value

USINT 0=nonexistent1=configuring3=established4=timed out

USINT 1= I/O ConnectionUSINT 130 (82hex) - Server,

Transport Class 2 ID UINT Depends on DSA node

address settingn ID UINT Depends on DSA node

address settingristics USINT 1Size UINT 1 = 1 byten Size UINT 1 = 1 byte

UINT in millisecondsUSINT 0=transition to timed out

1=auto delete2=auto reset

Path Length UINT 6

Connection Object (cont.)

Table B.19 Instance 2 Attributes (Predefined S


1 Get State

2 Get Instance Type3 Get Transport Class Trigger

4 Get Produced Connection

5 Get Consumed Connectio

6 Get Initial Comm Characte7 Get Produced Connection 8 Get Consumed Connectio9 Get/Set Expected Packet Rate12 Get/Set Watchdog Action

13 Get Produced Connection

B-13

COS I/O Connection)

4 in/2 out - 20 04 24 69 30 032 in/1 out -20 04 24 6A 30 03

Length UINT 64 in/2 out - 20 04 24 20 30 032 in/1 out -20 04 24 1F 30 03

Data Type Value

USINT 0=nonexistant1=configuring3=established4=timed out

USINT 1=I/O Connection

USINT 19

UINT Depends on DSA node address setting

UINT Depends on DSA node address setting

USINT 1

UINT 1 = 1 byte

UINT 1 = 1 byte

Table B.20 Instance 4 Attributes (Predefined Slave

14 Get/Set Produced Connection Path

15 Get Consumed Connection Path16 Get/Set Consumed Connection Path


1 Get State

2 Get Instance Type

3 Get Transport Class Trigger

4 Get Produced Connection ID

5 Get Consumed Connection ID

6 Get Initial Comm Characteristics

7 Get Produced Connection Size

8 Get Consumed Connection Size

B-14

UINT in milliseconds

USINT 0=transition to timed out1=auto delete2=auto reset

ath Length UINT 6

ath 4 in/2 out - 20 04 24 69 30 032 in/1 out -20 04 24 6A 30 0

Path Length UINT 6

Path 4 in/2 out - 20 04 24 20 30 032 in/1 out -20 04 24 1F 30 03

, PIT UINT in milliseconds

ServiceNamee

Reset



Connection Object (cont.)


9 Get/Set Expected Packet Rate

12 Get Watchdog Action

13 Get Produced Connection P

14 Get Produced Connection P

15 Get Consumed Connection

16 Get Consumed Connection

17 Get/Set Production Inhibit Time

ServiceCode

Implemented for:

Class Instanc

5 (05hex) No Yes

14 (0Ehex) No Yes

16 (10hex) No Yes

B-15

Di

discrete inputs of a device.

ta Type Value

UINT 3

ta Type Value

L 0=OFF, 1=ONL 0=OFF, 1=ON

Service Name


screte Input Point Class Code 8 (08hex)

The Discrete Input Point Object models the


Number of Instances: 2 or 4



Attribute ID Access Rule Name Da

1 Get Revision

Attribute ID Access Rule Name Da

3 Get Value BOO4 Get Status BOO


Class Instance

14 (0Ehex) Yes Yes

B-16

ls the discrete outputs of a device.

e Data Type Value

BOOL 0=OFF, 1=ONBOOL 0=OFF, 1=ON

Service Namee



Discrete Output Point

Class Code 9 (09hex)

The Discrete Output Point Object mode


Number of Instances: 1 or 2




3 Get Value4 Get Status


Class Instanc

14 (0Ehex) No Yes

16 (10hex) No Yes

B-17

Pa

erface to a devices configuration data.

me Data Type Value

UINT 6escriptor WORD 9

embly Instance UINT 104

Data Type Value

lue See Data Type and Data Size Attributes

Parameter Dependent

e USINT 6

/portress

BYTEpath data dependent

Path to specific device object attribute if applicable

WORD Parameter Dependent: USINT Parameter DependentUSINT Parameter Dependent

rameter Object Class Code 15 (0Fhex)

The Parameter Object provides a public int




Attribute ID Access Rule Na

2 Get Max Instances8 Get Parameter Class D9 Get Configuration Ass


1 Get / Setonly get is supported for monitoring parameters

Parameter Va

2 Get Link Path Siz3 Get Link Path

Segment typeSegment add

4 Get Descriptor5 Get Data Type6 Get Data Size

B-18

Data Type

Min/Max

Default Value

OL 0 - 1 0 0=Disable1=Enable

NT 0 - 4 0 0=0 ms1=2 ms2=4 ms3=8 ms4=16 ms

NT 0 - 4 0 0=0 ms1=2 ms2=4 ms3=8 ms4=16 ms

OL 0 - 1 0 0=Reset Outputs1=Hold Last State

OL 0 - 1 0 0=Reset Outputs1=Hold Last State

INT 0 - 3 0 0=No Action1=Reset Output 12=Reset Output 2 (4in/2out)2=Reset Inputs (2in/1out)3=Reset Inputs (4in/2out only)

Parameter Object (cont.)

Table B.29 Parameters Supported

Param Parameter

NameObject MappingClass/Inst/Attrib

1 Auto Baud 3 /1 / 100 BO

2 On Delay 15 / 2 / 1 UI

3 Off Delay 15 / 3 / 1 UI

4 Fault State 30 / 1 / 7 BO

5 Idle State 30 / 1 / 9 BO

6 Reset Fault 15 / 6 / 1 US

B-19

Di

f the discrete input points in the DSA. All input

Service Name



Data Type Value

s USINT 2 (2in/1out)4 (4in/2out)

ARRAY of UINT 1,2 (2in/1out), 1,2,3,4 (4in/2out)BOOL 0=OK

1=FaultedUINT microsecondsUINT microseconds

Table B.30 Common Services Supported

screte Input Group Class Code 29 (1Dhex)

The Discrete Input Group Object binds all opoints share the attributes in this object.





Class Instance

14 (0Ehex) No Yes

16 (10hex) No Yes


3 Get Number of Bound Instance

4 Get Binding Instance IDs5 Get Status

6 Get/Set Off-On Delay7 Get/Set On-Off Delay

B-20

s all of the discrete output points in the DSA. All object.

Service Namence



Discrete Input Group (cont.)


Discrete Output Group

Class Code 30 (1Ehex)

The Discrete Output Group Object bindoutput points share the attributes in this




Class Insta

14 (0Ehex) No Yes

16 (10hex) No Yes

B-21

Data Type Value

ances USINT 1 (2in/1out)2 (4in/2out)

ARRAY of UINT 1 (2in/1out)1,2 (4in/2out)

BOOL 0BOOL 0=idle

1=runBOOL 0=reset output

1=hold last stateBOOL 0BOOL 0=reset output

1=hold last stateBOOL 0

Service Name






3 Get Number of Bound Inst

4 Get Binding Instance IDs

5 Get Status6 Get/Set Command

7 Get/Set Fault State

8 Get/Set Idle Value9 Get/Set Idle State

10 Get/Set Idle Value


Class Instance

14 (0Ehex) No Yes

16 (10hex) No Yes

B-22

ges the reception of Change of State connection

Data Type Value

er UINT millisecondsUSINT 1

ceUINT 4

Service Namece



Acknowledge Handler

Class Code 43 (2Bhex)

The Acknowledge Handler Object manaacknowledge messages from a master.






1 Get/Set Acknowledge Tim2 Get Retry Limit3 Get COS Producing

Connection Instan


Class Instan

14 (0Ehex) No Yes

16 (10hex) No Yes

Allen-Bradley Bulletin 100 DeviceNet Starter Auxiliary User Manual · 2019. 8. 15. · Operation...

Documents

Transcript of Allen-Bradley Bulletin 100 DeviceNet Starter Auxiliary User Manual · 2019. 8. 15. · Operation...