Rockwell Automation 1738-ADNX User Manual

ArmorPoint I/O DeviceNet Adapters

1738-ADN12, 1738-ADN18, 1738-ADN18P, 1738-ADNX

User Manual

Important User Information

SHOCK HAZARD

Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (Publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.ab.com/manuals/gi) describes some important differ enc es between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc. is prohibited.

Throughout this manual, when necessary we use notes to make you aware of safety considerations

WARNING

IMPORTANT

ATTENTION

BURN HAZARD

Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

Identifies information that is critical for successful application and understanding of the product.

Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you:

• identify a hazard

• avoid a hazard

• recognize the consequence

Labels may be located on or inside the equipment (e.g., drive or motor) to alert people that dangerous voltage may be present.

Labels may be located on or inside the equipment (e.g., drive or motor) to alert people that surfaces may be dangerous temperatures.

Preface

Purpose of This Manual

This manual describes how to install, configure, and operate your ArmorPoint I/O™ DeviceNet™ Adapters, catalog numbers 1738-ADN12, -ADN18, -ADN18P, and -ADNX.

See the following sections: Page:

Who Should Use This Manual P-2 What the Manual Contains P-2 Related Terms P-3 Related Products and Documentation P-5 Guidelines for Using Your Adapter P-6 Conventions Used in This Manual P-6

IMPORTANT

In this manual, we use ArmorPoint DeviceNet adapters to refer to all the 1738 DeviceNet adapter modules (1738-ADN12, -ADN18, -ADN18P, and

-ADNX). We use the specific catalog number (e.g., 1738-ADNX) to refer to a specific module.

In the rest of this manual (except Chapter 4), we refer to the ArmorPoint I/O DeviceNet adapters as the adapters.

Who Should Use This Manual

In Chapter 4, we refer to the ArmorPoint I/O DeviceNet adapter as the scanner because the chapter describes how to configure the adapter on the subnet.

You must be able to use RSNetWorx for DeviceNet™ software or a similar configuration software to configure your adapter.

In this manual, we assume you know how to configure an ada pte r. If you do not, refer to your software user manuals or online help before attempting to use these adapters.

We also assume you are familiar with the ArmorPoint I/O product line, including other fieldbus interfaces, I/O modules, and power supplies. If you are not familiar with these components, you can read some of the ArmorPoint I/O documents listed in the Related Products and Documentation section.

1 Publication 1738-UM001A-EN-P - February 2005

Preface 2

What the Manual Contains

This manual contains the following sections:

Chapter 1 - Install the ArmorPoint DeviceNet Adapters

Description of how to install and wire the adapter

Chapter 3 - Use Auto Start Mode

Description of how to use the Auto Start Mode on your adapter to quickly get your system up and running

Chapter 2 - What Is the ArmorPoint DeviceNet Adapter?

Overview of the adapter’s features and functionality

1738-ADN12

DeviceNet Out DeviceNet In

Adapter Status DeviceNet Status PointBus

Status

X10

PWR

System Power

Adapter Power

Chapter 4 - Configure the DeviceNet Scanner Subnet

Description of how to configure your adapter on the subnet

Chapter 5 - Add the ArmorPoint DeviceNet Adapter to the DeviceNet Scanner’s Scanlist

Description of how to configure the DeviceNet adapter and how to add it to the scanlist

Appendix B - Quick Start

Learning how to use the 1738-ADN12 with a ControlLogix system on DeviceNet

Chapter 6 - Troubleshoot the ArmorPoint DeviceNet Adapter

Description of how to use the status indicators and how to troubleshoot your adapter

Appendix C - 1738-ADNX Rules and Guidelines

Rules and guidelines regarding how to use the 1738-ADNX

Appendix A - Specifications

Listing of the ArmorPoint adapters’ specifications

Appendix D - Default Data Maps

Listing of the default data maps for 1738 ArmorPoint I/O modules

Publication 1738-UM001A-EN-P - February 2005

Preface 3

Related Terms

This manual uses the following terms:

Term: Definition:

Adapter The adapter interfaces between DeviceNet devices and

ArmorPoint I/O modules. ArmorPoint I/O DeviceNet adapters include the 1738-ADN12, -ADN18, -ADN18P, and -ADNX.

Auto Catalog Replace The ArmorPoint I/O DeviceNet adapter supports the swapping

of two identical modules connected to the adapter . That is, if a 1738-IB4M12 is in slot 3 and another 1738-IB4M12 is in slot 7, the two modules can be removed from the ArmorPoint system and the slot 3 module placed into slot 7, and vice-versa. When Automatic Device Replacement (ADR) is active, the swapped modules will be reconfigured to match the previous module in their new slot. When ADR is not active, the configuration parameters will not be modified, the swapped modules must have identical configuration and values for their EDS file parameters.

Auto Device Replacement (ADR)

This refers to the ADR feature of a ControlLogix System on DeviceNet. With ADR active, any device on the DeviceNet link may be removed and replaced with an out-of-the-box checkmark compliant DeviceNet device. The ADR feature will result in downloading the values of the configuration parameters of the EDS file of the removed device to the new device.

Auto Start Mode A feature that lets the ArmorPoint I/O system get “up and

running” without the prerequisite to configure any of the EDS parameters for the PointBus Using Auto Start Mode will result in a scan list within the adapter that stores the modules identity information.

Autobaud A feature in devices (e.g., ArmorPoint I/O modules) on the

DeviceNet network that causes them to listen to communications on the network and set their own baudrate to match the network rate.

Backplane The PointBus that consists of ArmorPoint I/O modules

connected to the ArmorPoint DeviceNet adapter.

Baudrate Rate of communications between devices on the DeviceNet

network. Backplane baudrate is used for the 1738-ADN12,

-ADN18, and -ADN18P. Subnet baudrate is used for the 1738-ADNX.

Change of State (COS) DeviceNet communications method in which the adapter

sends data based on detection of any changed value within the input data. Data is independently received based on a change of state from the sender . Data in both directions can be acknowledged or unacknowledged depending on the run-time configuration of the system.

Commissioning The period in time associated with post startup activities.

Commissioning implies that the system has been validated and all configuration parameters are correct, all modules are in good operating condition, and the adapter scanlist is complete.

ControlFlash™ Utility software you can use to update the adapter’s firmware

with the most current boot and application code.

™ or ArmorPoint I/O modules.

Publication 1738-UM001A-EN-P - February 2005

Preface 4

Term: Definition:

Cyclic DeviceNet communications method in which the adapter

sends data cyclically based on a configured time value. Data is independently received cyclically from the sender . Data in both directions can be acknowledged or unacknowledged

depending on the run time configuration of the system. MACID Media Access Control Identifier (DeviceNet network address). Master A DeviceNet network device (e.g., 1771-SDN) that initiates

communication with DeviceNet slave devices (e.g.,

ArmorPoint I/O modules) to retrieve data. The master only

receives unprompted data when the slave is enabled for COS

and there is a change in the device’s operating state. Max Backplane MACID The 1738-ADNX has a unique attribute, Max(imum)

Backplane MACID. This value represents the highest node

address of a module residing on the backplane. This value

must be greater than or equal to the right most backplane

ArmorPoint I/O module, but must be less than that of any

non-backplane Subnet module. Offline State of the adapter when it is not powered or maintaining

normal communication exchanges with other DeviceNet

devices. Online State of the adapter when it is powered and maintaining

normal communication exchanges with other DeviceNet

devices. PointBus The ArmorPoint I/O backplane PointBus maintains all

DeviceNet network protocol but also offers configuration

capabilities. Polled DeviceNet communications method in which a module sends

data in response to received data. Primary Network The primary DeviceNet network is defined as the DeviceNet

link that provides the direct connection between the

ArmorPoint DeviceNet adapter and a DeviceNet scanner. RSNetWorx for DeviceNet Configuration software for the adapter and Subnet modules.

Publication 1738-UM001A-EN-P - February 2005

Scanlist The list of Subnet modules connected to the adapter. When

ADR is active, the scanlist stores the configured values of

each of the Subnet modules’ configurable parameters. When

ADR is not active, the scanlist stores only the module identity

information. Scanner Operating state of the ArmorPoint DeviceNet adapter when it

retrieves I/O data from Subnet modules. Slave A DeviceNet network device that cannot initiate

communication (except when configured with COS enabled)

but responds to a DeviceNet master device. Strobe Adapter sends data in response to the strobe command. The

single bit allocated to the adapter in the strobe message is not

used. If the configured size of the input data (sent from the

adapter) is greater than 8 bytes, the strobe connection

establishment will fail. In this case, the input size must be

reconfigure to 8 bytes or less.

Term: Definition:

Subnet 1738-ADNX only.

The Subnet DeviceNet network is defined as the DeviceNet

link that provides the expansion of the PointBus to let the

1738-ADNX use its lower connector to add an additional 500

meters and up to 63 nodes. These nodes will be bridged

through the 1738-ADNX up to the primary network. Note that

backplane modules are also part of the Subnet.

Preface 5

Guidelines for Using Your Adapter

Conventions Used In This Manual

Remember the following operational guidelines when using your ArmorPoint DeviceNet adapter.

• Do not leave spaces in the I/O. Instea d, instal l all ArmorPoint I/O modules adjacent to each other.

• Populate every position on the mounting base.

• ArmorPoint does not support removal and insertion under

power (RIUP). When an I/O module is removed, the IP67 seal is broken and the backplane bus is interrupted.

• Use Allen-Bradley terminal markers to identify your ArmorPoint I/O modules.

For more information on the Allen-Bradley terminal marking kits, see the documents list on page

The following conventions are used thro ughout this manual:

• bullet lists (such as this one) provide information, not procedural steps

• numbered lists provide sequential steps

• text written like this identifies screen, menu, toolbar names, field

names, buttons, and check boxes on screens

• a menu item in this format File>Save identifies the submenu item after the caret (>) that is accessed from the main menu (name before the caret)

• pictures of symbols and/or scre ens represent th e actual symbols you see or the screens you use

Preface-5.

Publication 1738-UM001A-EN-P - February 2005

Install the ArmorPoint DeviceNet Adapters

What Is the ArmorPoint DeviceNet Adapter?

Chapter 1

Mount the Adapter and I/O Base. . . . . . . . . . . . . . . . . . . . 1-1

Set the Node Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Wire the DeviceNet Adapters. . . . . . . . . . . . . . . . . . . . . . . 1-3

1738-ADN12 and 1738-ADNX. . . . . . . . . . . . . . . . . . . . 1-3

1738-ADN18 and 1738-ADN18P . . . . . . . . . . . . . . . . . . 1-3

1738 ArmorPoint DeviceNet Auxiliary Power . . . . . . . . 1-4

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . 1-4

Chapter 2

Use the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Set Subnet/Backplane Baudrate . . . . . . . . . . . . . . . . . . 2-3

Set Subnet/Backplane I/O Module Addresses . . . . . . . . 2-3

Configure the Subnet I/O. . . . . . . . . . . . . . . . . . . . . . . 2-3

Configure the Primary DeviceNet Network . . . . . . . . . . 2-4

Remove and Reinsert Modules on the Backplane . . . . . 2-5

Understand the DeviceNet Network and Subnet. . . . . . . . . 2-6

DeviceNet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Backplane/Subnet Network . . . . . . . . . . . . . . . . . . . . . 2-7

Adapter Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Communicate Through the Adapter . . . . . . . . . . . . . . . . . . 2-18

Map the Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Overview of the Communication Process . . . . . . . . . . . 2-19

Image Table Mapping . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Communicate With I/O Modules . . . . . . . . . . . . . . . . . . . . 2-23

Use Diagnostic Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . 2-26

Chapter 3

Use Auto Start Mode

i Publication 1738-UM001A-EN-P - February 2005

Why Use Auto Start Mode? . . . . . . . . . . . . . . . . . . . . . . . . 3-2

What Does Auto Start Mode Do?. . . . . . . . . . . . . . . . . . 3-2

How Is I/O Data Mapped Using Auto Start Mode?. . . . . 3-3

Requirement To Using Auto Start Mode . . . . . . . . . . . . 3-4

Install the I/O Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Remove the Module From the Mounting Base. . . . . . . . 3-5

Use RSNetWorx for DeviceNet. . . . . . . . . . . . . . . . . . . . . . 3-5

Begin Auto Start Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Use Custom Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . 3-10

Configure the DeviceNet Scanner Subnet

Add the ArmorPoint DeviceNet Adapter to the DeviceNet Scanner’s Scanlist

Troubleshoot the ArmorPoint DeviceNet Adapter

Chapter 4

Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Add the Scanner To Your Network. . . . . . . . . . . . . . . . 4-2

Add I/O Modules To Your Network . . . . . . . . . . . . . . . 4-3

Set the Scanner’s Parameters. . . . . . . . . . . . . . . . . . . . . 4-3

Go On Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . 4-8

Chapter 5

Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Add the Adapter to Your Network . . . . . . . . . . . . . . . . 5-2

Set the Adapter’s Parameters. . . . . . . . . . . . . . . . . . . . . 5-3

Go On Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Chapter 6

Use the Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Guidelines for Using Your Adapter . . . . . . . . . . . . . . . . . . 6-3

Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Specifications

Quick Start For the 1738-ADNX

Rules and Guidelines For the 1738-ADNX

Appendix A

Appendix B

What’s In This Appendix? . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Review of the 1738-ADNX Rules and the MACID Parameter B-9

Review of Auto Start Mode. . . . . . . . . . . . . . . . . . . . . B-11

Browse the Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15

Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . B-19

Navigate Between Networks. . . . . . . . . . . . . . . . . . . . B-24

Appendix C

Publication 1738-UM001A-EN-P - February 2005

Default Data Maps

iii

Appendix D

1738-IA2 Input Module . . . . . . . . . . . . . . . . . . . . . . . . D-2

1738-IB2 Sink Input Module. . . . . . . . . . . . . . . . . . . . . D-2

1738-IB4 Sink Input Module. . . . . . . . . . . . . . . . . . . . . D-2

1738-IB8 Sink Input Module. . . . . . . . . . . . . . . . . . . . . D-3

1738-IV4 Source Input Module . . . . . . . . . . . . . . . . . . . D-3

1738-IV8 Source Input Module . . . . . . . . . . . . . . . . . . . D-3

1738-OA2 Output Module . . . . . . . . . . . . . . . . . . . . . . D-4

1738-OB2E Electronically Protected Output Module . . . D-4

1738-OB2EP Protected Output Module . . . . . . . . . . . . . D-4

1738-OB4E Electronically Protected Output Module . . . D-5

1738-OB8E Electronically Protected Output Module . . . D-5

1738-OV4E Protected Sink Output Module . . . . . . . . . . D-6

1738-OW4 Relay Sink/Source Output Module . . . . . . . . D-6

1738-IE2C Analog Current Input Module. . . . . . . . . . . . D-7

1738-IE2V Analog Input Module. . . . . . . . . . . . . . . . . . D-8

1738-OE2C Analog Current Output Module. . . . . . . . . . D-9

1738-OE2V Analog Output Module. . . . . . . . . . . . . . . . D-9

1738-IJ Encoder/Counter Module . . . . . . . . . . . . . . . . D-10

1738-IR2 RTD Input Module. . . . . . . . . . . . . . . . . . . . D-10

1738-IT2I Isolated Thermocouple Input Module . . . . . D-11

1738-VHSC 24V dc High Speed Counter Module . . . . . D-12

1738-SSI Synchronous Serial Interface Absolute

Encoder Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12

1738-232ASC ASCII Module . . . . . . . . . . . . . . . . . . . . D-13

1738-485ASC ASCII Module . . . . . . . . . . . . . . . . . . . . D-13

Publication 1738-UM001A-EN-P - February 2005

Chapter

1.9 in.

2.0 in.

0.87 in.

2.0 in.

0.87 in.

2.0 in.

Drilling Dimension Drawing

Install the ArmorPoint DeviceNet Adapters

This chapter describes how to install and wire your adapter.

See the following sections: Page:

Mount the Adapter and I/O Base 1-1 Set the Node Address 1-2 Wire the DeviceNet Adapters 1-3 Chapter Summary and What’s Next 1-4

Mount the Adapter and I/O Base

Adapter

4.02 in. 102 mm

To mount the ArmorPoint adapter on a wall or panel, use the screw holes provided in the adapter.

A mounting illustration for the ArmorPoint adapter with I/O bases is shown below.

47.2 mm

1.81 in. 46 mm

50 mm

22 mm

50 mm

22 mm

Install the mounting base as follows:

1. Lay out the required points as shown in the drilling dimension drawing.

50 mm

43769

2. Drill the necessary holes for #8 (M4) machine or self-tapping screws.

3. Mount the adapter and I/O bases using #8 (M4) screws.

4. Ground the system using the ground lug connection in the I/O

base. (The ground lug connection is also a mounting hole.)

1 Publication 1738-UM001A-EN-P - February 2005

1-2 Install the ArmorPoint DeviceNet Adapters

5. Mount the terminating base that was shipped with the adapter as the last base in the backplane instead of the base that was shipped with the I/O module.

Terminating base

Mounting hole Ground connection

Set the Node Address

Latching mechanism holes

43787

Valid node addresses are 00 through 63.

Set the node address using either the rotary switches, RSNetWorx for DeviceNet, DeviceNetManager, or another software configuration tool. Setting the switches at any number from 64 through 99 lets the software have address control.

Each module is shipped with the switches set for node address 63. Remove the caps on the front of the module to access the switches (refer to the X10 and X1 on the front of the module). The two switches are:

• X10 (most significant digit) - left side of module

• X1 (least significant digit) - right side of module

This example shows the node address set at 63.

31433-M

Publication 1738-UM001A-EN-P - February 2005

To reset the node addre ss, use a sma ll blade screwdriv er to rotate the switches. Line up the small notch on the switch with the number setting you wish to use and then cycle power.

Install the ArmorPoint DeviceNet Adapters 1-3

The rotary switches are read periodically. If the switches have been changed since the last time they were read and th ey no longer match the on line address, a minor fault will occur, which is indicated by a flashing red Adapter Status LED. Settings of 64 through 99 cause the module to use the last valid node address stored internally

. For example, the last setting internal ly was 40. If a change is made to 68, and then you power up, the address will default to 40.

The module is equipped with AutoBaud detect. AutoBaud lets the module read the settings already in use on your DeviceNet network and automatically adjusts to follow those settings.

Wire the DeviceNet Adapters

Following are wiring instructions for the ArmorPoint DeviceNet adapters.

1738-ADN12 and 1738-ADNX

ale In Connector Female Out Connector (1738-ADN12)

(Subnet Out - 1738-ADNX only)

(view into connector) Pin 1 - Drain Pin 2 - +V Pin 3 - -V Pin 4 - CAN_High

43763

Pin 5 - CAN_Low

43764

1738-ADN18 and 1738-ADN18P

Male In Connector Female Out Connector (1738-ADN18P only)

43746

(view into connector) Pin 1 - Drain Pin 2 - +V Pin 3 - -V Pin 4 - CAN_High Pin 5 - CAN_Low

43749

Publication 1738-UM001A-EN-P - February 2005

1-4 Install the ArmorPoint DeviceNet Adapters

1738 ArmorPoint DeviceNet Auxiliary Power

Male In Connector

(view into connector) Pin 1 - User Power + Pin 2 - Adapter Power +

Adapter/Subnet + (1738-ADNX only)

Pin 3 - Adapter Power -

43587

Pin 4 - User Power -

Adapter/Subnet - (1738-ADNX only)

Chapter Summary and What’s Next

ATTENTION

Make sure all connectors and caps are securely tightened to properly seal the connections against leaks and maintain IP67 requirements.

In this chapter , you learned how to install and wire your DeviceNet adapter. Move to chapter 2 to learn about the ArmorPoint DeviceNet adapters.

Publication 1738-UM001A-EN-P - February 2005

Chapter

What Is the ArmorPoint DeviceNet Adapter?

This chapter describes the ArmorPoint I/O DeviceNet adapter, including descriptions of the adapter’s features and functionality.

See the following sections: Page:

Use the Adapter 2-2 Understand the DeviceNet Network and Subnet 2-6 Adapter Features 2-8 Communicate Through the Adapter 2-18 Communicate With I/O Modules 2-23 Use Diagnostic Tables 2-24 Chapter Summary and What’s Next 2-26

1 Publication 1738-UM001A-EN-P - Februa ry 2005

2-2 What Is the ArmorPoint DeviceNet Adapter?

Use the Adapter

The adapter resides on the primary DeviceNet network and the Subnet simultaneously.

The adapter interfaces between DeviceNet devices and ArmorPoint I/O modules. The graphic below shows the adapter on the DeviceNet network and PointBus.

ControlLogix chassis

IMPORTANT

The PointBus maintains all DeviceNet network protocol but also offers configuration capab ilities.

computer with PLC programming software

ControlNet network

1784-PCD PCMCIA card

computer with RSNetWorx for DeviceNet software

DeviceNet network

See page 2-19 for an explanation of the number sequence.

ArmorPoint I/O modules

1738-ADN12 adapter

Subnet (1738-ADNX only)

DeviceNet Out

DeviceNet In

x10

PWR

1738-IB8M12

1738-ADN12

Adapter Status DeviceNet Status PointBus Status

System Power

Adapter Power

24V dc In

MOD

NET

1 2

3 4 5

6 7

1738-OB8EM12

24V dc Out

MOD

NET

0 1

43852

2 3

4 5

6 7

After you have installed your adapter into a ArmorPoint I/O system, you must perform the following tasks:

1. Set Subnet/Backplane Baudrate

2. Set Subnet/Backplane I/O Module Addresses

3. Configure the Subnet I/O

4. Configure the Primary Device Net Network

The steps mentioned above are explained briefly here and then in greater detail throughout this manual. Y ou must complete the steps for the adapter to work with DeviceNet masters (e.g., 1756-DNB) on the primary network and Subnet modules.

Publication 1738-UM001A-EN-P - February 2005

What Is the ArmorPoint DeviceNet Adapter? 2-3

1. Set Subnet/Backplane Baudrate

The adapter and Subnet/Backplane modules must use the same baudrate to communicate with each other. Use one or both of the following to set a Subnet/Backplane baudrate.

• Enable or disable the Backplane Autobaud feature for ArmorPoint I/O modules. ArmorPoint I/O modules have Autobaud enabled as the default- See page

• Set the adapter baudrate for the Subnet. The default for the 1738-ADN12, -ADN18, and -ADN18P is 1Mbaud. The default for the 1738-ADNX is 125Kbaud - See page

You set the backplane baudrate for the 1738-ADN12, -ADN18, and -ADN18P. You set the Subnet baudrate for the 1738-ADNX.

2-12.

2-9.

2. Set Subnet/Backplane I/O Module Addresses

Once the adapter and ArmorPoint I/O modules are communicating at the same rate on the backplane, you must make sure all modules use a valid MACID.

Set the Auto Address feature for ArmorPoint I/O modules - See page 2-13.

For the 1738-ADNX, a DeviceNet configuration tool, such as RSNetW orx for DeviceNet, may be required to set the node addre ss. (if node address switches are not present on the Subnet device).

3. Configure the Subnet I/O

In the first two steps, you set a consistent communication rate and made sure each module uses valid addresse s for communication. Next you must configure the PointBus (e.g., set scan list).

You can configure the PointBus using one of two methods:

• Auto Start Mode (ASM) or

• Manually

For more information on configuring the PointBus, see Chapter 3 for ASM or see Chapter 4 for manual configuration.

Publication 1738-UM001A-EN-P - Februa ry 2005

2-4 What Is the ArmorPoint DeviceNet Adapter?

4. Configure the Primary DeviceNet Network

Finally, you must configure the adapter for communication with a master (e.g., 1756-DNB).

For more information on configuring the Devic eNet network, see Chapter 5, Add the ArmorPoint DeviceNet Adapter to the DeviceNet Scanner’s Scanlist.

You must understand all of the adapter’s features to effectively use it in your ArmorPoint I/O system. Keep these four steps in mind as you read this manual:

1. Set Subnet/Backplane Baudrate

2. Set Subnet/Backplane I/O Module Addresses

3. Configure the Subnet I/O

4. Configure the Primary Device Net Network

Publication 1738-UM001A-EN-P - February 2005

What Is the ArmorPoint DeviceNet Adapter? 2-5

Remove and Reinsert Modules on the Backplane

Removal and Insertion Under Power (RIUP) is not recommended in a ArmorPoint System because of the following reasons.

• Removing a module breaks the IP 67 seal.

• Removing a module breaks the backp lan e bu s. Mod ule s to the

right of the removed module will be ‘lost’ to the adapter. Also, the terminating resistor will be removed, causing system uncertainty.

• Inserting a module under power may cause the adjacent module to reset due to the addition of a large capacitive load on the power bus.

IMPORTANT

If the module is removed wh ile it is under power, all the modules to the right of the removed module will disconnect from the PointBus and field power until the module is reinstalled.

If you must remove and reinsert modules, we recommend the following:

• Do not move I/O modules to different locations on the mounting base after they have been installed and configured.

• If adjacent modules (i.e., 2 or more) are remo ved from the backplane, replace all of them before attempting to operate the ArmorPoint I/O system. Input data will hold last state until all previously removed modules are replaced.

– If adjacent modules are removed and all but one is returned,

the adapter cannot verify the location of the returned modules. For example, if modules are removed from node s 3 and 4 and only the module from node 4 is returned, the adapter cannot verify the location. In this case, the adapter alerts you via a flashing red PointBus status LED that it cannot verify the presence of modules in the affected locations. I/O data will not be exchanged with this node until both modules have been reinserted.

– If modules of different types are removed and returned to

the wrong locations, the adapter identifies the returned modules and alerts you (via RSNetWorx for DeviceNet) that the error has occurred and must be corrected.

Publication 1738-UM001A-EN-P - Februa ry 2005

2-6 What Is the ArmorPoint DeviceNet Adapter?

– If modules of the same type are removed and returned to the

wrong locations, the adapter identifies the returned modules, updates their MACIDs, and continues operation.

IMPORTANT

The removal and return scenario ex ists whether the system is under power or not. If the system is under power, the scenario arises immediately. If the system is not under power, the scenario arises in the next power cycle.

Also, the example above shows removal of two adjacent modules. The scenario described exists anytime 2 or more adjacent modules are removed and all are not returned.

Care must be taken when replacing backplane I/O modules. Each I/O module stores its configuration parameters in internal non-volatile memory. You must either enable ADR for all modules or manually configure each module in a non-manufacturing environment when the module is being replaced or placed on the network for the first time. Failure to do so could result in inadvertent control attributed to different configuration settings.

Understand the DeviceNet Network and Subnet

DeviceNet Network

Your adapter serves as a slave to DeviceNet masters. The adapter receives data from and returns data to the master through the following I/O connections:

• Change of State (COS)

• Cyclic

• Polled

• Strobe

Publication 1738-UM001A-EN-P - February 2005

What Is the ArmorPoint DeviceNet Adapter? 2-7

Backplane/Subnet Network

On the Backplane/Subnet, your adapter acts as a scanner and is the master of the Subnet modules. The adapter performs the following functions:

• Exchanges I/O data with devices on the Backplane/Subnet

• Collects I/O data from the Backplane/Subnet and sends it to

devices on the DeviceNet network (e.g., scanners or controllers)

• Supplies power to the backplane I/O modules (See Appendix A for power supply rules regarding I/O modules power requirements.)

Data Collection

The adapter collects I/O data from up to 63 modules via the Backplane/Subnet. The I/O modules appear on the primary DeviceNet network as a single node, though, and require only one DeviceNet node address.

IMPORTANT

If Automatic Device Replacement (ADR) is enabled on the adapter, you can only connect up to 62 modules via the Subnet.

For more information on ADR, see page 2-15.

Module Power

The adapter supplies 5V logic power to ArmorPoint I/O modules by converting 24V dc field power to PointBus 5V power.

You can connect up to 63 I/O modules to each adapter and you can power the backplane I/O modules from the adapter (with a maximum of 10A of field power). You may use the integrated, isolated 24V dc expansion power unit (1738-EP24DC) to power additional I/O modules, as shown below.

738-ADN12 adapter

1738-OB8EM12

1738-IB8M12

1738-ADN12

24V dc In

System Power Adapter Power

MOD

NET

1 2

3 4 5

5 6 7

DeviceNet Out

Adapter Status

DeviceNet In

DeviceNet Status PointBus Status

x10

PWR

24V dc Out

MOD

NET

0 1 2

4 5

57 6 7

ArmorPoint I/O modules

1738-OB8EM12

1738-IB8M12

24V dc Out

24V dc In

MOD

NET

1 2

6 4 5

5 6 7

1738-EP24DC expansion power unit

1738-IB8M12

24V dc Power Supply

24V dc In

MOD

NET

0 1

4 5

ArmorPoint I/O modules

1738-OB8EM12

1738-EP24DC

24V dc Out

MOD

NET

0 1

SYSTEM

POWER FIELD

POWER

E R

4 5

6 7

1738-OB8EM12

1738-IB8M12

24V dc Out

24V dc In

MOD

NET

1 2

3 4 5

6 7

MOD

NET

0 1 2 3

4 5

6 7

1738-IB8M12

24V dc In

MOD

NET

1 2

3 4 5

6 7

1738-OB8EM12

24V dc Out

MOD

NET

0 1 2 3

4 5

6 7

24V dc In

24V dc Out

MOD

NET

0 1

4 5

1738-OB8EM12

1738-IB8M12

43851

For more information on the 1738-EP24DC expansion power unit, see the ArmorPoint I/O 24V dc Expansion Power Supply Installation Instructions, publication 1738-IN020.

Publication 1738-UM001A-EN-P - Februa ry 2005

2-8 What Is the ArmorPoint DeviceNet Adapter?

Adapter Features

Your adapter uses the following features on both the DeviceNet network and the PointBus:

• Self-Test

• Field Upgradable Firmware

• Fully Configurable Software

• Connections

• Baudrates

Self-Test

When power is applied to the adapter, the adapter performs a self-test. The adapter tests various internal and programmatic memories and checks the status indicators (LEDs).

Field Upgradable Firmware

You can update the adapter’s firmware with the ControlFlash Utility software. This feature lets you always use the most current firm ware.

Fully Software Configurable

The adapter is fully software configurable using RSNetWorx for DeviceNet. You must configure the adapter to be used with a DeviceNet master (e.g., 1756-DNB) and separately to be used with Subnet devices.

For more information on how to configure your adapter to use with a DeviceNet master, see Chapter 5, Add the ArmorPoint DeviceNet Adapter to the DeviceNet Scanner’s Scanlist.

For more information on how to configure your adapter to use with Subnet modules, see Chapter 4, Configure the DeviceNet Scanner Subnet.

Connections

Y o ur adapter supports the following connections on both the primary DeviceNet network and Subnet:

• I/O connections:

– Polled – Strobe – Cyclic – COS

• Explicit connections

Publication 1738-UM001A-EN-P - February 2005

What Is the ArmorPoint DeviceNet Adapter? 2-9

You can use I/O mapping to determine the data contained in each connection.

The adapter supports Master/Slave connection types on the DeviceNet network. On the Subnet, the adapter functions as a scanner device, exchanging data with I/O modules.

Baudrates

Choose baudrates for the adapter in the RSNetWorx for DeviceNet software. The adapter supports these rates:

• 125Kbaud

• 250Kbaud

• 500Kbaud

• Autobaud - The adapter detects the primary DeviceNet network

baudrate and automatically sets its own baudrate to match the network.

• For the 1738-ADN12, -ADN18, and -ADN18P, the Po intBus can be configured to operate at 1Mbaud (1000Kbaud).

• For the 1738-ADNX, the Subnet can be configured to operate at 125K, 250K, and 500K baud only.

Auto Start Mode

Auto Start Mode lets you easily get your adapter installed and operating. In this mode, the adapter’s configurable features operate as they were most recently configured. For example, if Autobaud on DeviceNet was enabled in the adapter’s last configuration, it will be enabled when Auto Start Mode is used.

For a more detailed explanation of how to use Auto Start Mode, see Chapter 3.

Publication 1738-UM001A-EN-P - Februa ry 2005

2-10 What Is the ArmorPoint DeviceNet Adapter?

Auto Catalog Replace

Auto Catalog Replace corrects errors that might occur when backplane modules of the same type are removed and replaced in the wrong location. If modules of the same ty pe are removed and returned to th e wrong locations, the adapter identifies the returned modules, updates their MAC IDs, and continues operation.

IMPORTANT

If modules of different types are removed and returned to the wrong locations, the adapter identifies the returned modules and alerts you (via RSNetWorx for DeviceNet, the Node Status Table, and the Faulted Node Table) that the error has occurred and must be corrected.

Backplane (1738-ADN12, -ADN18, -ADN18P)/Subnet (1738-ADNX) Baudrate

EDS parameter Backplane Baudrate is accessible from the primary DeviceNet and sets a specific baudrate for all backplane I/O modules.

Set this parameter in RSNetWorx for DeviceNet to one of the following baudrates:

• 125 Kbaud

• 250 Kbaud

• 500 Kbaud

• 1 Mbaud (available for all the ArmorPoint DeviceNet adapters

except the 1738-ADNX)

Publication 1738-UM001A-EN-P - February 2005

When you download this parameter , the adapter sends a command to reset all present I/O modules on the backplane to the new baudrate. If additional modules are connected to the adapter, you must download the Backplane/Subnet Baudrate to make sure the new modules use the same rate as the others.

What Is the ArmorPoint DeviceNet Adapter? 2-11

The baudrate may not take effect until power is recycled or the I/O modules are reset.

IMPORTANT

Changes to the Backplane/Subnet Baudrate parameter only take effect if they are downloaded on an individual basis. (For example, if you change the Backplane/Subnet Baudrate and download the changes with additional changes to other features, the Backplane/Subnet Baudrate remains at the previous setting.)

Also, this parameter should be set to ‘Do Nothing’ when you download all parameters or when Automatic Device Replacement is enabled for the adapter.

If you want to set an I/O module to use a specific baudrate (i.e., 125, 250, 500), you must first disable Backplane Autobaud for that module.

Backplane/Subnet Baudrate performs the following functions:

• Sets the adapter’s Subnet baudrate

• Sends a message to all connected backplane I/O modules. If an

I/O module is set to autobaud, it receives the message but ignores the new baudrate.

Publication 1738-UM001A-EN-P - Februa ry 2005

2-12 What Is the ArmorPoint DeviceNet Adapter?

Backplane Autobaud

The adapter itself never autobauds on the Subnet. Backplane Autobaud automatically enables or disables Autobaud for all I/O modules currently attached to the backplane. The adapter does not set a specific rate though (as with Backplane Baudrate).

If you enable Backplane Autobaud in the adapter or the EDS parameter access that you set from the primary DeviceNet, the adapter only enables the Autobaud in all backplane I/O modules. When the modules listen to communications on the DeviceNet network, they detect the rate of communication and auto matically set their own baudrates to match the network rate.

The module does not automatically detect the backplane baudrate until power is cycled or the module is reset.

TIP

Autobaud, when enabled, is useful if you swap ArmorPoint I/O modules between networks that are operating at different baudrates.

Enable Backplane Baudrate in RSNetWorx for DeviceNet.

IMPORTANT

Changes to the Backplane Autobaud parameter only take effect if they are downloaded on an individual basis. (For example, if you enable the Backplane Autobaud setting and download the change with additional changes to other features, the Backplane Baudrate remains disabled.)

This parameter should be set to ‘Do Nothing’ when you download all parameters or when Automatic Device Replacement is enabled for the adapter.

If you want to set an I/O module to use a specific baudrate (i.e., 125, 250, 500), you must first disable Autobaud for that module.

Publication 1738-UM001A-EN-P - February 2005

What Is the ArmorPoint DeviceNet Adapter? 2-13

Auto Address

The EDS parameter Auto Address is available from the primary DeviceNet and lets the user sequentially order the node ad dresses of backplane I/O modules. This parameter is not a mode but occurs on a single occurrence only. The node address sele cte d is assigned to the module closest to the adapter. The next closest module is assi gned the next numerically higher value. The numbering pattern continues for all connected backplane I/O modules.

Enable this parameter in the RSNetWorx for DeviceNet software.

IMPORTANT

Changes to the Auto Address parameter only take effect if they are downloaded on an individual basis. (For example, if you enable the Auto Address and download the changes with additional changes to other features, the node addresses of the I/O modules remains disabled.)

This parameter should be set to ‘Do Nothing’ when you download all parameters or when Automatic Device Replacement is enabled for the adapter.

Physical List Acquire Status

The adapter maintains a physical list that indicates the order of the node addresses of all ArmorPoint I/O modules present on the backplane. Physical List Acquire Status shows the status of this physical list acquire process.

The adapter requires that each backplane I/O module has a MACID greater than that of its neighbor to its immediate left. The list is created when power is applied to the adapter and each time a module is inserted on the backplane.

The valid values are:

• Idle

• Busy

• Auto Start Mode

Publication 1738-UM001A-EN-P - Februa ry 2005

2-14 What Is the ArmorPoint DeviceNet Adapter?

Cycling Node Status

Using the Cycling Node Status parameter, you can easily determine the status of any ArmorPoint I/O modules with which the adapter is experiencing problems. A corresponding text string appears, including the MAC ID, and a description of the status code reported in the Node Status Table. For more information on the Node Status Table, see page 2-24.

For the connection sizes mentioned below, the I/O connection sizes on DeviceNet are dependent on the scanlist configuration on the backplane.

Poll/COS Connection Consume Size

Poll/COS Connection Consume Size shows the size (number of data bytes) consumed by the poll/COS (Instance 2) I/O connection on the primary DeviceNet.

Poll Connection Produce Size

Poll Connection Produce Size shows the size (number of data bytes) produced by the polled (Instance 2) I/O connection on the primary DeviceNet.

COS/Cyclic Connection Produce Size

COS Produce Size shows the size (number of data bytes) prod uced by the Change of State I/O connection on the primary DeviceNet.

Strobe Connection Produce Size

The Strobe Produce Size shows the size (number of data bytes) produced by the Strobe I/O connection on the primary DeviceNet.

Publication 1738-UM001A-EN-P - February 2005

+ 104 hidden pages

Rockwell Automation 1738-ADNX User Manual

Important User Information

Preface

Purpose of This Manual

Who Should Use This Manual

What the Manual Contains

Related Terms

Guidelines for Using Your Adapter

Conventions Used In This Manual

Table Of Contents

Install the ArmorPoint DeviceNet Adapters

Mount the Adapter and I/O Base

Set the Node Address

Wire the DeviceNet Adapters

Chapter Summary and What’s Next

What Is the ArmorPoint DeviceNet Adapter?

Use the Adapter

Understand the DeviceNet Network and Subnet

Adapter Features