Rockwell Automation 1738 Assembly User Manual

Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters

Catalog Numbers Bulletins 1734 and 1738 User Manual

Important User Information

WARNING

IMPORTANT

ATTENTION

SHOCK HAZARD

BURN 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

http://literature.rockwellautomation.com

) describes some important differences 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.

available from your local Rockwell Automation sales office or online at

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, and recognize the consequence.

Labels may be on or inside the equipment, such as a drive or motor, to alert people that dangerous voltage may be present.

Labels may be on or inside the equipment, such as a drive or motor, to alert people that surfaces may reach dangerous temperatures.

Allen-Bradley, Rockwell Automation, POINT I/O, ArmorPOINT I/O, RSView, RSLinx, RSLogix 5000 and TechConnect are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.

Table of Contents Preface

Why Read This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Who Should Use This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

About the Vocabulary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Common Techniques Used in this Manual. . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1

Introduction

About Assembly Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Choose a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Data Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Listen Only Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Connection Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2

Configuration

About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Configure the Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chassis Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Data Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Individual Module Configuration Options. . . . . . . . . . . . . . . . . . . . 7

Module Configuration Sent with the Connection Request . . . . . . . 8

Module Configuration with RSNetWorx for DeviceNet. . . . . . . . . 8

Calculate the Connection Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Connection Size Calculation Example . . . . . . . . . . . . . . . . . . . . . . . 9

Troubleshooting Connection Size Errors. . . . . . . . . . . . . . . . . . . . 10

Using an Assembly Connection

Assembly Structure

1734/1738 I/O Module Assembly Information

Chapter 3

Use an Assembly Connection with RSNetWorx for EtherNet/IP . . . 13

Use an Assembly Connection with RSLogix5000 . . . . . . . . . . . . . . . . 16

Add the Hardware to the I/O Configuration Tree . . . . . . . . . . . . 17

Enter the Connection Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 18

Build the Configuration Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 4

Assembly Structure Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Byte, Word, and Double Word Alignment. . . . . . . . . . . . . . . . . . . 23

Fixed Size per Slot Alignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 5

Module Assembly Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Discrete Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Analog and Specialty I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . 32

Data Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Module Specific Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Two-channel Discrete Input Modules . . . . . . . . . . . . . . . . . . . . . . 34

iii Publication 1734-UM016A-EN-P - October 2010

iv Table of Contents

Four-channel Discrete Input Modules . . . . . . . . . . . . . . . . . . . . . . 35

Eight-channel Discrete Input Modules. . . . . . . . . . . . . . . . . . . . . . 35

Two-channel Discrete Output Modules with Status . . . . . . . . . . . 37

Two-channel Discrete Output Modules. . . . . . . . . . . . . . . . . . . . . 38

Four-channel Discrete Output Modules with Status . . . . . . . . . . . 38

Four-channel Discrete Output Modules. . . . . . . . . . . . . . . . . . . . . 39

Eight-channel Discrete Output Modules with Status . . . . . . . . . . 40

Eight-channel Discrete Output Modules . . . . . . . . . . . . . . . . . . . . 41

Four-channel Discrete Diagnostic Input Modules. . . . . . . . . . . . . 41

Two-channel Relay and AC Output Modules . . . . . . . . . . . . . . . . 43

Four-channel Relay and AC Output Modules . . . . . . . . . . . . . . . . 43

Sixteen-channel Discrete Diagnostic Input Modules. . . . . . . . . . . 43

Sixteen-channel Discrete Output Modules. . . . . . . . . . . . . . . . . . . 44

Eight-channel Configurable Discrete Input/Output Modules . . . 45

Very High Speed Counter Modules . . . . . . . . . . . . . . . . . . . . . . . . 46

Counter Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Two-channel Analog Input Modules . . . . . . . . . . . . . . . . . . . . . . . 50

Four-channel Analog Input Modules . . . . . . . . . . . . . . . . . . . . . . . 51

Eight-channel Analog Input Modules. . . . . . . . . . . . . . . . . . . . . . . 54

Two-channel Analog Output Modules. . . . . . . . . . . . . . . . . . . . . . 59

Four-channel Analog Output Modules. . . . . . . . . . . . . . . . . . . . . . 61

Two-channel RTD Input Modules . . . . . . . . . . . . . . . . . . . . . . . . . 64

Two-channel Thermocouple Input Modules . . . . . . . . . . . . . . . . . 65

Synchronous Serial Interface Modules . . . . . . . . . . . . . . . . . . . . . . 67

Address Reserve Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

ASCII Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Publication 1734-UM016A-EN-P - October 2010

Index

Preface

Read this preface to familiarize yourself with the rest of the manual. It provides information concerning:

• the purpose of this manual

• related documentation

• conventions used in this manual

Why Read This Manual

Who Should Use This Manual

About the Vocabulary

This manual is a reference guide for using Assembly Connections with POINT I/O and ArmorPOINT I/O modules.

You must be able to program and configure industrial automation controllers and I/O to use the connections specified in this manual. You should also be familiar with the POINT I/O or ArmorPOINT I/O families of product to use these connections.

We assume that you are familiar with the material presented in this manual. If you are not, refer to product-specific documentation before you attempt to use this manual. Related documentation for Rockwell Automation products is listed in the table below.

In this manual, we refer to the:

• 1734 family as POINT I/O modules

• 1738 family as ArmorPOINT I/O modules

Common Techniques Used in this Manual

The following conventions are used throughout this manual:

• Bulleted lists such as this one provide information, not procedural steps.

• Numbered lists provide sequential steps or hierarchical information.

• Italic type is used for emphasis.

An article on wire sizes and types for grounding electrical equipment.

. To order paper copies of

Publication 1734-UM016A-EN-P - October 2010

Introduction

Chapter

About Assembly Connections

This document describes Assembly connections, a new connection type for POINT I/O and ArmorPOINT I/O EtherNet/IP adapters. These adapters currently support Rack Optimized connections between ControlLogix or CompactLogix controllers and the discrete I/O modules in the chassis.

They are also capable of bridging direct connections between any EtherNet/IP-capable connection originator and the I/O modules, via the backplane. This new functionality being presented will permit the exchange of data between an originator and all POINT I/O modules present in the chassis in one connection.

This new Assembly connection is mutually exclusive to other connection types, for example, Rack Optimized or Direct to module connections. In other words, if this connection is in use by one connection originator, other originators are prevented from making Rack Optimized or Direct Connections to the modules in the same chassis. Furthermore, the connection is all-inclusive; every module present in the backplane participates in the connection.

The I/O data that is exchanged with the adapter takes the following form:

Adapter Data Exchange

T → O produced I/O data O → T consumed I/O data

64-bit Status header Run/Idle header Slot 1 data Slot 1 data Slot 2 data Slot 2 data :: ::

(1)

Slot N

data

(1)

N is the number of I/O modules

The 64-bit Status header is optional and the packing of the data is dependant on the selected alignment choice. The exact method for determining the data structure is covered in the following sections.

Choose a Connection

1 Publication 1734-UM016A-EN-P - October 2010

The Assembly connection supports an optional 64-bit status header and also supports requests from listen-only originators.

Slot N data

2 Introduction

Data Headers

In the Target to Originator (T → O) direction, the adapter can be configured to produce a status header for the connection. The header consists of an 8-byte bitmap, where bits 1 - 63 indicate the health of each of the 63 possible backplane connections. This is similar to existing Rack Optimized connections. A "1" indicates that a module is not connected or that slot is not populated. A "0" indicates that the module is actively participating in the connection. Currently, Bit 0 is reserved and should be ignored.

When the header is used, modules may be removed and reinserted without breaking the I/O connection to the adapter. Modules not present or that are failed are reflected in the status header.

If the optional status header is not included, the adapter cannot support RIUP without breaking the I/O connection. If any one I/O module fails or is removed, the adapter will break the connection to the connection originator. Since no status is provided, this is the only way to reflect the fact that a problem exists with the I/O modules on the backplane.

In the Originator to Target (O → T) direction the adapter supports the 4-byte Run/Idle header. Sending a "1" indicates that the controller is in the Run mode and that the adapter should apply the data that was just received. Sending a "0" indicates that the controller is in program or idle mode and that the adapter should put the I\O modules in their idle mode.

Listen Only Connections

Using an Assembly connection will allow multiple originators to consume data from the POINT I/O system. However, only one owner of the connection is permitted. That one owner will control all output devices present in the chassis as well as the configuration of the connection.

Connection Points

The following table lists the connection points that are supported for the different connection styles discussed.

Publication 1734-UM016A-EN-P - October 2010

Supported Connection Points for Connection Styles

Introduction 3

Connection Configuration

Connection Point

Consumed Connection Point

Produced Connection Point

Exclusive Owner 102 100 101 Listen-only 102 191 101 Input-only 102 190 101 Owning with no status header 102 100 103 Listen-only with no status header 102 191 103 Input-only with no status header 102 190 103

Publication 1734-UM016A-EN-P - October 2010

4 Introduction

Notes:

Publication 1734-UM016A-EN-P - October 2010

Configuration

Chapter

About This Chapter

This chapter describes the various configuration options that you can use to set up assembly connections.

Configure the Connection

This connection is accepted with or without a configuration assembly present. If a configuration assembly is present, it must contain the following minimum information.

Minimal Adapter Configuration Assembly

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Config 0 Reserved (Set to 0) Config 1 Reserved (Set to 0) Config 2 Reserved (Set to 0) Config 3 Reserved (Set to 0) Config 4 Chassis size (Low Byte) Config 5 Chassis size (High Byte) Config 6 Alignment for Produced Assembly (T → O) Config 7 Size per slot (T→ O) (in Bytes) Config 8 Alignment for Consumed Assembly (O → T) Config 9 Size per slot (O → T) (in Bytes)

Chassis Size

Before establishing I/O connections, you must configure the 1734 adapters for chassis size. This ensures that the correct number of modules are present in the chassis at power up. The chassis size must include 1 count for the adapter (Chassis Size = number of I/O modules + 1).

5 Publication 1734-UM016A-EN-P - October 2010

6 Configuration

TIP

Data Alignment

Some computing devices require data to be aligned on boundaries that are proper for their data type. There are several alignment options available to reduce or prevent shifting operations in the originator:

Byte Boundaries

Each node's I/O data is mapped at the next available byte. Byte data can appear at any address.

Word Boundaries

If a node's I/O data is one byte in length, it is mapped at the next available byte. Otherwise the previous data is padded so that the node's data starts on a 16-bit boundary.

This does not mean that every slot occupies two bytes in the image. Word data can only begin on even addresses, for example, 0, 2, 4, 8, 0xA, or 0xC.

Double Word Boundaries

If a node's I/O data is one byte in length, it is mapped at the next available byte. If a node's data is two bytes in length, padding is added to ensure that it is mapped to an even address. If a node's data is greater than 2 bytes in length, padding is added to ensure that the data is mapped to a Double Word boundary.

This does not mean that every slot occupies 4 bytes in the image. Double Word data and array data larger than 2 bytes in size must be aligned on addresses ending in 0, 4, 8, and 0xC.

Fixed Boundaries

The fixed boundary allows you to choose the fixed "size per slot" that each module occupies in the I/O data. Mapping size ranges from 1…24 bytes.

The alignment choices are independently selected for each direction; O → T and T

→ O. If Fixed Boundaries are selected, the Size per Slot choice

determines how many bytes are reserved for each slot in the I/O packet. If the size selected is larger than a module's data, that module's data is padded with 0's out to the size selected. If the size selected is smaller than a module's data, that module's data is truncated at the size selected.

Publication 1734-UM016A-EN-P - October 2010

Configuration 7

When Fixed Boundaries are selected, the formula for mapping is: H+(N-1)(size per slot), where N = slot position and H is the size of the optional status header (8 if used, 0 if not used).

The choice of alignment is highly dependent on the originator used and application-specific requirements.

• If data size is at a premium, Byte alignment is the most efficient choice.

• If the originator can only process data on DINT boundaries (as is the case with RSLogix controllers), then Double Word alignment should be used.

• If ease of programming is desired, the Fixed Boundaries option allows for easy location of the data within the data packet. Additionally the use of Fixed Boundaries along with the 1734-ARM module will allow modules to be added later without having the location of any slot's data change. The ARM module will reserve data space for future modules. Since each slot occupies the same size in the data image, when the ARM module is replaced with a future module, the data boundaries are preserved.

Individual Module Configuration Options

The request for an Assembly connection is accepted with or without a configuration assembly present. If a configuration assembly is present, it must contain the minimum information presented in the Configuring the Connection section. See TableMinimal Adapter Configuration Assembly on page 5. If individual module configuration is required, it can be appended to the end of the minimum configuration structure for any or all modules that require configuration. The construction of this configuration data structure is a manual process.

Alternatively any tool that is capable of sending CIP packets can configure the parameters of individual POINT I/O modules. The configuration is stored locally in the module's non-volatile storage. When the configuration is sent from the connection originator via the connection request, the adapter also stores a copy of this configuration and restores it if that module is ever replaced. This is similar to the Automatic Device Replacement feature of DeviceNet scanners. If the configuration is sent from the connection originator via the connection request, the configuration assembly size is limited to the maximum packet size of 510 bytes. This may be an issue in larger systems that require module configuration. Configuring modules through a separate tool will allow the configuration to be sent to modules individually, effectively eliminating the packet size limitation. Furthermore, the configuration tool of choice may provide a rich graphical user interface, reducing the possibility that configuration is incorrectly entered. One such tool is RSNetWorx for DeviceNet.

Publication 1734-UM016A-EN-P - October 2010

8 Configuration

Module Configuration Sent with the Connection Request

Individual module configuration must be manually constructed and appended to the minimal configuration assembly specified in the table Minimal Adapter Configuration Assembly on page 5. For each module that needs to be configured, the following information must be provided:

Module Configuration Information

Field Data Type Description

Slot number USINT The slot number to identify modules that require

configuration data.

Configuration size USINT The size, in bytes, of the Configuration Data for the

given module. It does not include the size of the first three fields shown here.

Configuration assembly instance

Configuration data Array of

UINT The adapter reads this field to access the module

configuration assembly’s instance number. The configuration assembly data as defined by the

BYTE

module's EDS file.

This structure may be repeated for as many modules as necessary until the whole assembly exceeds 509 bytes. The module order is not important as long as all module configuration follows the minimal header information from the table Minimal Adapter Configuration Assembly on page 5.

If any part of the configuration assembly is wrong (either the minimal assembly or a portion directed to an I/O module), the connection request will be rejected with the General Return Code indicating an Error in the Data Segment (0x09). The Extended Error code will indicate the byte offset into the configuration data segment where the error was detected. The Configuration assembly details for all of the 1734 and 1738 I/O modules are presented in Module Assembly Information on page 31.

Module Configuration with RSNetWorx for DeviceNet

Publication 1734-UM016A-EN-P - October 2010

RSNetWorx for DeviceNet provides a rich parameter-based configuration user interface. The POINT I/O and ArmorPOINT I/O adapters have the capability to present their backplane as a DeviceNet subnet to RSLinx. The subnet can be used to bridge configuration data from RSNetWorx for DeviceNet to backplane devices. With this method, all configuration for a POINT I/O backplane can be stored to the DeviceNet network file (.DNT) and restored via this file if necessary.

Configuration 9

Cat # A

E N T

I B 8

I E 2 C

O B 4 E

Slot # 0 1 2 3

Module Tx size Rx size

IB8 1 – byte 0 OB4E 1 – byte 1 – byte IE2C 6

- int

- byte

Calculate the Connection Size

The I/O assembly size is limited to the maximum size that can be specified in the standard Forward_Open service (509 bytes). The size needs to be manually calculated based on the alignment choices, inclusion of the optional status header, and the I/O sizes for the modules present in the chassis. The adapter validates the connection size in the forward open against what it calculates from the backplane and the alignment choice. If the two do not match, the connection request is rejected with extended error code 0x0109, Invalid Connection Size.

Connection Size Calculation Example

The following system will be used to demonstrate the connection size calculation. The adapter's produced size (T optional status header is included. In some software the consumed size (O

→T) does not need to account for the 4 byte Run/Idle header as it is

assumed and already included. For the example both header sizes have been included.

POINT I/O system example

→ O) must include 8 bytes if the

T → O alignment T → O size O → T alignment O → T size

1 Byte 16 bytes Byte 5 bytes

status 8 bytes slot 1 byte slot 2 int slot 2 int slot 2 byte slot 2 byte slot 3 byte

Publication 1734-UM016A-EN-P - October 2010

run /idle 4 bytes

slot 3 byte

10 Configuration

T → O alignment T → O size O → T alignment O → T size

2 Double Word 19 bytes Double Word 5 bytes

status 8 bytes slot 1 byte slot 1 pad slot 1 pad slot 1 pad slot 2 int slot 2 int slot 2 byte slot 2 byte slot 3 byte

3 6 bytes per slot 26 bytes 1 byte per slot 7 bytes

run / idle 4 bytes slot 3 byte

status 8 bytes slot 1 6 bytes slot 2 6 bytes slot 3 6 bytes

run /idle 4 bytes slot 1 byte slot 2 byte slot 3 byte

In row 1, the data is packed on byte boundaries. This is the most efficient data representation when alignment is not a concern.

In row 2 the data for slot 1 is padded so that slot 2's data began on a Double Word bound ary.

In row 3 every slot takes up the selected size per slot regardless of whether that module has any data to produce.

This section touches briefly on data alignment. More comprehensive examples of data alignment are provided in Assembly Structure Examples on page 23.

Troubleshooting Connection Size Errors

If the adapter returns the Invalid Connection Size error in response to a connection request, it is possible to query the adapter for its calculated size.

Publication 1734-UM016A-EN-P - October 2010

This section highlights a technique that can be used to help resolve connection size errors.

The adapter cannot validate connection sizes until the request to open the connection is received. It is within that request that the adapter receives the alignment choice and status election. Based on all the information in the request and the modules present, the request may be rejected by the adapter because of a size error.

Configuration 11

1. Open the adapter's web page and select the Diagnostics folder.

2. On the Diagnostic Messaging tab, enter the Slot, Class, Instance, and

Attribute to get the adapter's calculated connection sizes.

Diagnostic Messaging Field Description

Field Description

Service Get Attribute Single Slot Position 0 Class 4

Publication 1734-UM016A-EN-P - October 2010

12 Configuration

Diagnostic Messaging Field Description

Field Description

Instance 100 (O → T data)

101 (T → O data with status) 103 (T → O data without status)

Attribute 4 Response 8E 00 00 00 xx xx

8E 00 — Indicates message was processed successfully 00 00 — 0 = success. Non-zero indicates an error code

xx xx — Indicates size (Little Endian format)

(1)

in Little Endian format, the least significant byte is shown first. A returned value of A2 01 should be interpreted as 0x01A2 hex (418 decimal).

(1)

Once you have the sizes from the adapter, return to your calculations to resolve the differences between your expected size and the size from the adapter.

Publication 1734-UM016A-EN-P - October 2010

Using an Assembly Connection

Chapter

Use an Assembly Connection with RSNetWorx for EtherNet/IP

This section provides an illustration of the steps needed to configure the Assembly connection using RSNetWorx for EtherNet/IP.

1. Browse the EtherNet/IP network.

2. Select the connection originator that will make the connection to the

1734-AENT. Right click that device and select Scanlist Configuration to launch the Scanlist Configuration tool.

13 Publication 1734-UM016A-EN-P - October 2010

14 Using an Assembly Connection

3. Right click the targeted adapter and select Insert Connection to display the Connection Properties dialog.

4. On the Connection tab of this dialog, select the connection from the Connection Name pull-down (for example, Exclusive Owner and Listen-Only connections). Listen-Only connections are only accepted if an Exclusive Owner connection already exists.

Publication 1734-UM016A-EN-P - October 2010

Using an Assembly Connection 15

TIP

You can also select the Requested Packet Interval and connection sizes. For a full discussion on connections sizes, refer to the Configuration Setting tab step that follows and Calculate the Connection Size. The defaults reflect an empty system (with the adapter only).

In RSNetWorx, the 4-byte Run/Idle header is not considered when calculating the Output Size. When you enter the connection size on this dialog, make sure to subtract 4 bytes from your calculated size. Also note that this dialog expresses the size in Words. If your calculation was performed in Bytes, you must divide by 2.

5. In the Details tab, you can select between Point to Point and Multicast

for the Target to Scanner data.

Publication 1734-UM016A-EN-P - October 2010

16 Using an Assembly Connection

TIP

6. The Configuration Setting tab displays the configuration options for the connection. Here, you can specify the Chassis Size and Data Alignment. The terms T2O and O2T are abbreviations for Target to Originator and Originator to Target.

Use an Assembly Connection with RSLogix5000

Remember when specifying the Chassis Size to include 1 for the adapter.

See Data Alignment for alignment choices.

The Assembly connection can be used with RSLogix5000 and the Generic EtherNet/IP profile. When this connection is used in RSLogix5000, there are no intelligent Tags created for the adapter. All Input, Output, and Configuration data are in unstructured Tag arrays.

Publication 1734-UM016A-EN-P - October 2010

Using an Assembly Connection 17

Add the Hardware to the I/O Configuration Tree

1. Add a new module to the Ethernet network in the I/O Configuration

section of the Controller Organizer pane.

2. Select a Generic Ethernet Module.

Publication 1734-UM016A-EN-P - October 2010

18 Using an Assembly Connection

Enter the Connection Parameters

In the New Module Properties dialog, enter Connection Parameters, the Comm Format, the module's IP Address, and a name.

Enter a Name for the module that RSLogix 5000 uses in the tags that are created for this module. The Data - SINT Comm Format should be selected, indicating that all sizes are to be interpreted as a number of bytes. If this connection is a Listen only connection, select the Input Data - SINT Comm Format since it is otherwise not possible to enter an Output config assembly size of 0.

Next, enter the Assembly Instances for the desired connection as described in Connection Points. Enter the sizes (in bytes) for the Input and Output instances per your calculations. See Calculate the Connection Size for details on obtaining the sizes. If the optional status header is being used, its size (8 bytes) must be included in the Input Size. For RSLogix 5000 the Output Size does not include the Run/Idle header. Here the terms Input and Output refer to the adapter's Produced and Consumed data respectively.

It is possible to make the connection without sending any configuration data. The adapter's Chassis Size can be set from its web page and the adapter will align produced and consumed data by default on byte boundaries. If these options and the default configuration of all I/O modules are acceptable, a 0 can be entered for the Configuration Size on the Module Properties dialog. The configuration Assembly Instance must be entered even if the size is 0. The following section will describe the steps taken when configuration is needed.

Publication 1734-UM016A-EN-P - October 2010

Build the Configuration Tag

If any configuration is required, the minimum configuration header must be sent and then any individual module configuration may follow. Open the

Using an Assembly Connection 19

Controller Tags by right-clicking the Controller Tags option from the Controller Organizer pane. Select Monitor Tags.

Monitor Tags

You should see three Tags with the module's name. They will have an C, I, or O suffix denoting Configuration, Input, or Output respectively. Note that the I and O Tags are sized according to the sizes that were entered on the properties page. The C Tag always has 400 bytes allocated for it regardless of the size specified.

Add Configuration Header

Bytes 0…9 must contain the minimum configuration header information described in Minimal Adapter Configuration Assembly. As can be seen from the figure below, the Chassis Size is set to 0x12 (18 decimal). The produced

Publication 1734-UM016A-EN-P - October 2010

+ 57 hidden pages