red rio

User Manual

(Catalog Number 1757-ABRIO)

Process Remote I/O (RIO) Communication Interface Module

Important User InformationSolid 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://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.

Allen-Bradley, Rockwell Automation, RSLogix 5000, ControlLogix, ProcessLogix, RSLinx, ControlFlash, and TechConnect are trademarks of Rockwell Automation, Inc.

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

WARNINGIdentifies 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.

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

ATTENTION 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

SHOCK HAZARD Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.

BURN HAZARD Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.

http://literature.rockwellautomation.com

http://literature.rockwellautomation.com/idc/groups/literature/documents/in/sgi-in001_-en-p.pdf

Table of Contents

Preface Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Who Should Use this Manual. . . . . . . . . . . . . . . . . . . . . . . . . 7Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 1Introduction Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Process Remote I/O (RIO) Communication Interface Module . 9RSLinx Software Requirements. . . . . . . . . . . . . . . . . . . . . . . 10ProcessLogix System Quick Start . . . . . . . . . . . . . . . . . . . . . 11RSLogix 5000 System Quick Start . . . . . . . . . . . . . . . . . . . . . 12Update the 1757-ABRIO Module’s Firmware. . . . . . . . . . . . . 14

Using ControlFlash Software. . . . . . . . . . . . . . . . . . . . . . 14Using NTools with ProcessLogix Software . . . . . . . . . . . . 15

Chapter 2Configure the 1757-ABRIO Module Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

AbRioCfg Software Overview. . . . . . . . . . . . . . . . . . . . . . . . 17Mapping and Accessing RIO Network Data . . . . . . . . . . . . . 18Installing AbRioCfg Software . . . . . . . . . . . . . . . . . . . . . . . . 19Autoconfigure the I/O Racks . . . . . . . . . . . . . . . . . . . . . . . . 19Adding Block Transfer Modules. . . . . . . . . . . . . . . . . . . . . . 23

Addressing Modes for 1771 . . . . . . . . . . . . . . . . . . . . . . 24Configuring Block Transfer Modules . . . . . . . . . . . . . . . . . . 25Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Input Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Output Scaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Tags Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Create a Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Mapping Data to Tags in AbRioCfg Software . . . . . . . . . . . . 31Block Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Deleting Mapped Data . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Tips for Configuring Modules . . . . . . . . . . . . . . . . . . . . . . . 32Add Racks Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Delete Racks Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Change the Baud Rate Offline . . . . . . . . . . . . . . . . . . . . 35

Download the Configuration . . . . . . . . . . . . . . . . . . . . . . . . 35Upload the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3Publication 1757-UM007D-EN-P - December 2008 3

Table of Contents

Chapter 3Creating Generic Modules in AbRioCfg Software

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Generic Module Overview. . . . . . . . . . . . . . . . . . . . . . . . . . 37Generic Module Configuration File . . . . . . . . . . . . . . . . . . . 38

Configuration Block Transfer Write. . . . . . . . . . . . . . . . . 38Data Block Transfer Read. . . . . . . . . . . . . . . . . . . . . . . . 41Data Block Transfer Write . . . . . . . . . . . . . . . . . . . . . . . 45

Creating a Generic Module in AbRioCfg software . . . . . . . . . 48

Chapter 4Configuring the ProcessLogix Controller to Access Data on the 1757-ABRIO Module

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

CONFIG Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51INACTIVE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52ACTIVE Mode (Run) . . . . . . . . . . . . . . . . . . . . . . . . . . . 52FORCED ACTIVE Mode . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configure the 1757-PLX52 Controller . . . . . . . . . . . . . . . . . . 53

Chapter 5Configuring RSLogix 5000 Software to Access Data on the 1757-ABRIO Module

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

CONFIG Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57INACTIVE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58ACTIVE Mode (Run) . . . . . . . . . . . . . . . . . . . . . . . . . . . 58FORCED ACTIVE Mode . . . . . . . . . . . . . . . . . . . . . . . . . 59

Scheduled Digital I/O Connections in RSLogix 5000 Programs . 60

Scheduled Connection Types . . . . . . . . . . . . . . . . . . . . . 60Setup an Exclusive-owner Connection . . . . . . . . . . . . . . 60Setup Input-only Connections . . . . . . . . . . . . . . . . . . . . 63

Unscheduled I/O Connections in ControlLogix. . . . . . . . . . . 67Create Message Commands to Read and Write All RIO Network Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 6Accessing Data through a DDE or OPC Server

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Accessing Data from a DDE or OPC Server . . . . . . . . . . . . . 75

Configuring a Topic in RSLinx Software . . . . . . . . . . . . . 75Accessing the Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4 Publication 1757-UM007D-EN-P - December 2008

Table of Contents

Chapter 7Monitoring the 1757-ABRIO Module

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Monitoring the Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 77Monitoring Digital I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Monitoring the Data Value of Tags. . . . . . . . . . . . . . . . . . . . 78Monitoring the Status of a Block Transfer. . . . . . . . . . . . . . . 79Monitoring the Scanner Log. . . . . . . . . . . . . . . . . . . . . . . . . 80Monitoring Diagnostic Counters. . . . . . . . . . . . . . . . . . . . . . 81

Active Rack List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Global Diagnostic Counters . . . . . . . . . . . . . . . . . . . . . . 81

Fatal Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 8Supported 1771 Modules Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Module Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831771-IFE Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 85I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

1771-OFE Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 89I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

1771-IR Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 92I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

1771-IXE Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 95I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

1771-IL Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 98I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

1771-NOC Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 101I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

1771-NOV Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 104I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Publication 1757-UM007D-EN-P - December 2008 5

Table of Contents

1771-NIV Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 107I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

1771-NR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 111I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Chapter 9Accessing HART Data Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Sending HART Commands Using RSLogix 5000 Software MSG . 115

HART Command Data . . . . . . . . . . . . . . . . . . . . . . . . . 117Reply Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Example: HART Command 36 . . . . . . . . . . . . . . . . . . . 122

1770-HT1 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Rack Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Configuring the 1770-HT1 Module . . . . . . . . . . . . . . . . 124HART Command status . . . . . . . . . . . . . . . . . . . . . . . . 129

Appendix ASpecifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Appendix BTroubleshooting Interpret the Status Indicators . . . . . . . . . . . . . . . . . . . . . . 133

RIO Status Indicator – Remote Devices Status . . . . . . . . 133SYS Status Indicator – ControlBus Status . . . . . . . . . . . . 133OK Status Indicator – Module Health . . . . . . . . . . . . . . 134

Status Display Power-up Messages. . . . . . . . . . . . . . . . . . . 134Power Supply Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Interpret the Alphanumeric Display . . . . . . . . . . . . . . . . . . 135Using AbRioCfg Software for Troubleshooting . . . . . . . . . . 136Troubleshooting Problems. . . . . . . . . . . . . . . . . . . . . . . . . 137Using RSLogix 5000 to Diagnose Problems. . . . . . . . . . . . . 138

General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Connection Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Module Info Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Backplane Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Using Control Builder Software to Diagnose Problems . . . . 140Troubleshooting 1757-ABRIO Module Communications . . . 140


Table of Contents

Appendix COperational Comparison Between the 1757-ABRIO Module and a PLC-5 System

Normal Operational Messages . . . . . . . . . . . . . . . . . . . . . . 143Exception Handling Messages . . . . . . . . . . . . . . . . . . . . . . 145

Appendix DTag Descriptions for Scheduled Data in RSLogix 5000 Software

Configuration Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149I and O Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Status Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151


Table of Contents


Preface

Purpose of this Manual This manual describes how to configure and troubleshoot your Process Remote I/O (RIO) Communication Interface Module.

For installation information, refer to the Process Remote I/O (RIO) Communication Interface Module Installation Instructions, publication 1757-IN916.

Who Should Use this Manual

We assume you have a good understanding of Remote I/O (RIO) modules as well as the host controller system (ProcessLogix or ControlLogix).

Additional Resources These documents contain additional information concerning related Rockwell Automation products.

See I/O Module Documentation on page 84 for a listing of related ControlLogix documentation.

You can view or download publications at http://literature.rockwellautomation.com. To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.

Resource Description

Process Remote I/O (RIO) Communication Interface Module Installation Instructions, publication 1757-IN916

Provides details on how to install the 1757-ABRIO module.

Process Remote I/O (RIO) Communication Interface Module Release Notes, publication 1757-RN520

Provides release details on the 1757-ABRIO module.

Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1

Provides general guidelines for installing a Rockwell Automation industrial system.

Product Certifications website, http://ab.com

Provides declarations of conformity, certificates, and other certification details.


http://literature.rockwellautomation.com/idc/groups/literature/documents/in/1757-in916_-en-p.pdf


http://literature.rockwellautomation.com/idc/groups/literature/documents/rn/1757-rn520_-en-p.pdf

http://www.literature.rockwellautomation.com/idc/groups/literature/documents/in/1770-in041_-en-p.pdf

http://ab.com

http://literature.rockwellautomation.com

Table of Contents Preface


Chapter 1

Introduction

Introduction This chapter:

describes the 1757-ABRIO Remote I/O Module.

lists the RSLinx software requirements.

provides update procedures for the module’s firmware.

Process Remote I/O (RIO) Communication Interface Module

This document is a user guide for the 1757-ABRIO module, which lets Rockwell Automation controllers (ProcessLogix or ControlLogix) communicate with Allen-Bradley remote I/O. The module acts as a RIO network scanner. The 1757-ABRIO module facilitates connection to analog and discrete I/O devices as well as any block transfer modules.

1757-ABRIO Module Example Topology

43290

Supports Block Transfers - limit of 32 words in a block

ProcessLogix System Server

Flex Ex Modules

PLC5/C Controller

ControlNet

Netw

orkSLC Controller

Data Highway + Network

ControlNet Network

PLC5 Controller

ProcessLogix and ControlLogix Controllers

Remote I/O Network

1771 Remote I/O1746 Remote I/O

Drive


Chapter 1 Introduction

As an RIO network scanner, the module:

scans 1771 racks with rack numbers from 1 to 37 octal.

supports baud rates of 57.6, 115.2 and 230.4 kilobaud.

supports up to 32 adapters with any mix of full/partial racks.

automatically manages and performs block transfers, update time can be defined for each block transfer.

provides full diagnostic counters for alarms and maintenance.

automatically performs scaling of raw analog data.

supports scheduled connections to update digital data with a ControlLogix controller.

implements a watchdog timer in the module’s hardware.

If the firmware does not kick the watchdog within the time-out period the watchdog times out and places the module into the configured safe failure state.

automatically provides fault/fail safe commands to I/O modules and controllers.

implements a jabber inhibit timer.

If the network transmitter is on longer than 150% of the longest network frame time, the 1757-ABRIO module turns the transmitter off and places the module into the configured safe failure state.

supports firmware updates using NTools or ControlFlash software.

supports direct DDE/OPC data access.

provides support for Rockwell Automation’s 1770-HT1, 1770-HT8, and 1770-HT16 HART interface products.

provides HART command set for calibration and diagnostics.

RSLinx Software Requirements

The AbRioCfg software requires RSLinx OEM software or above. You cannot use RSLinx Lite software. To access the module using OPC or DDE, you must have RSLinx 2.31 software or above.

If you are using ProcessLogix software, refer to the corresponding ProcessLogix Installation and Upgrade Guide to determine the appropriate RSLinx software version for your release.


Introduction Chapter 1

ProcessLogix System Quick Start

Use the following steps to quickly get the module running in a ProcessLogix system. Detailed information about each step is available in other sections of this manual or in the installation manual. You can only have one scanner per RIO network. Remove any other scanners on the RIO network before continuing.

1. Install the 1757-ABRIO module in the chassis and connect it to the RIO network.

See the Process Remote I/O (RIO) Communication Interface Module Installation Instructions, publication 1757-IN916.

2. Flash the controller with the latest firmware.

See Using NTools with ProcessLogix Software on page 15.

3. Install the AbRioCfg software.

See Installing AbRioCfg Software on page 19.

4. Autoconfigure or manually configure the RIO racks. This step locates all connected racks.

See Autoconfigure the I/O Racks on page 19 and Add Racks Offline on page 33.

5. Add and configure block transfer modules.

See Adding Block Transfer Modules on page 23.

6. Create tags for access by the ProcessLogix controller.

See Create a Tag on page 30.

7. Map I/O data to the tags and save the configuration file.

See Mapping Data to Tags in AbRioCfg Software on page 31.

8. Download the configuration to the 1757-ABRIO module.

See Download the Configuration on page 35.

9. Configure the ProcessLogix controller to access information within the 1757-ABRIO module using Control Builder software.

See Configure the 1757-PLX52 Controller on page 53.

10. Access live data from the 1757-ABRIO module.

See Live Data Examples on page 56.




RSLogix 5000 System Quick Start

Use the following steps to quickly get the module running in an RSLogix 5000 system. Detailed information about each step is available in other sections of this manual or in the installation manual. You can only have one scanner per RIO network. Remove any other scanners on the RIO network before continuing.

1. Install the 1757-ABRIO module in the chassis and connect it to the RIO network.

See the Process Remote I/O (RIO) Communication Interface Module Installation Instructions, publication 1757-IN916.

2. Flash the Controller with the latest firmware.

See Using ControlFlash Software on page 14.

3. Install the AbRioCfg software.

See Installing AbRioCfg Software on page 19.

4. Autoconfigure or manually configure the RIO racks. This step locates all connected racks.

See Autoconfigure the I/O Racks on page 19 and Add Racks Offline on page 33.

5. Add and configure block transfer modules.

See Adding Block Transfer Modules on page 23.

6. Create tags to access analog data from the ControlLogix controller.

See Create a Tag on page 30.

OR

Use scheduled updates to access digital data from the ControlLogix controller.

See Scheduled Digital I/O Connections in RSLogix 5000 Programs on page 60.

7. Map I/O data to the tags and save the configuration file.

See Mapping Data to Tags in AbRioCfg Software on page 31.

8. Download the configuration to 1757-ABRIO module.

See Download the Configuration on page 35.




9. If you are using:

a. a scheduled network, establish an Exclusive Owner or Input Only connection from the ControlLogix controller to access digital data within the 1757-ABRIO module.

See Setup an Exclusive-owner Connection on page 60 or Setup Input-only Connections on page 63.

b. an unscheduled network, configure tags and ladder logic in RSLogix 5000 software to access information within the 1757-ABRIO module.

See Unscheduled I/O Connections in ControlLogix on page 67.

10. If you are using a scheduled ControlNet network, schedule your network through RSNetWorx for ControlNet software.

See the RSNetWorx Help and the ControlNet Modules in Logix5000 Control Systems User Manual, publication CNET-UM001.

11. Access live data from the 1757-ABRIO module via:

a. scheduled connections.

See Scheduled Digital I/O Connections in RSLogix 5000 Programs on page 60 and Live Data Example on page 66.

b. unscheduled connections.

See Unscheduled I/O Connections in ControlLogix on page 67 and Live Data Example on page 73.

TIP If you are using a scheduled ControlNet network, you must also complete 9b to access analog or text data from the 1757-ABRIO module.


http://literature.rockwellautomation.com/idc/groups/literature/documents/um/cnet-um001_-en-p.pdf


Update the 1757-ABRIO Module’s Firmware

The 1757-ABRIO module supports firmware upgrades using ControlFLASH or NTools software. The firmware version is displayed on the 1757-ABRIO module’s 4-character display when you power up the module.

For ProcessLogix software users, if your 1757-ABRIO module revision is:

at or less than 1.2, use ControlFlash software to update the module firmware.

greater than 1.2, use NTools software to update the module firmware.

Using ControlFlash Software

Use the following procedure to update the module firmware using ControlFLASH software.

1. Insert the 1757-ABRIO CD.

2. Click Start>Run.

3. Type this path or Browse to:

D:(or your CD-ROM drive letter)\ControlFlash\setup.exe

4. Click OK.

5. At the Welcome to ControlFLASH Setup window, click Next.

6. To accept the License Agreement, click Yes.

7. To accept the default location, click Next.

8. At the Setup Complete window,

a. Uncheck the Yes, I want to view the README file checkbox.

b. Check the Yes, I want to launch ControlFLASH checkbox.

c. Click Finish.

9. At the Welcome to ControlFLASH window, click Next.

IMPORTANT The module ships with the latest firmware installed. You do not need to download firmware to the 1757-ABRIO module when you first receive it.



10. Click 1757-ABRIO and click Next.

11. Expand the RSLinx Tree window to the location of the 1757-ABRIO module you wish to flash.

12. Select the module icon and click OK.

13. Confirm new revision for this update and click Next.

14. At the Summary window, click Finish.

15. To confirm the flash, click Yes.

16. Click OK.

If this update is successful, the Update Status window displays the following message in green:

Update Complete. Please verify this new firmware update before using the target device in its intended application.

17. Click OK and then click Cancel at the Welcome to ControlFLASH Setup window.

18. Click Yes to end the configuration session.

Using NTools with ProcessLogix Software

On a ProcessLogix system, if the module firmware is at 1.2 or greater, use the following procedure to update the module firmware using NTools.

1. On the ProcessLogix Server, click Start>Run.

2. Type >ntools -c -u<.

3. To launch the Network Tools application, click OK.

4. Click OK at the warning about monitoring through Control Builder software.

5. To initiate the network scan, click Resume.

6. Select the appropriate CNB or ENET icon.

7. Select the module to be updated in the chassis graphic.



8. Click the firmware button and click Yes to acknowledge the warning.

9. Navigate to:

D:(or your CD-ROM drive letter)\Firmware_NTools

10. Select the appropriate .nvs file.

11. To start the firmware load, click Open.

12. To confirm, click Yes.

The Status field in the lower portion of the Network Tools window tracks the load progress.

13. When the load completes, click OK.


Chapter 2

Configure the 1757-ABRIO Module


provides an overview of the AbRioCfg software.

gives an introduction to mapping and accessing RIO network data.

explains how to install the AbRioCfg software.

explains how to autoconfigure I/O racks.

explains how to add and configure block transfer modules.

AbRioCfg Software Overview

The 1757-ABRIO module ships with configuration software, called AbRioCfg. This configuration software is an online configuration tool. Use the configuration software to:

query the RIO network to determine the location and size of the racks present.

manually add and configure racks present in RIO network.

add and configure supported block transfer modules.

import comma separated variable files to define the Generic Module as any block transfer module that uses 16-bit integer data.

add, edit, and delete racks offline.

create tags for access by the controller.

map I/O data to those tags.

download the configuration to the module, using RSLinx software.

monitor data and diagnostics on the module.

change the baud rate of network communications in a configuration and download to the module.

change the configuration of racks in a configuration and download to the module.

upload a configuration from a module.

print the configuration.


Chapter 2 Configure the 1757-ABRIO Module

Mapping and Accessing RIO Network Data

Use the provided AbRioCfg software to create tags which are arrays of digital, floating point or text values that the host controller reads or writes using unscheduled messages.

You map data that the module receives or sends into these tags. The data mapping is stored in flash memory on the 1757-ABRIO module.

The 1757-ABRIO Module and Data Mapping

WARNING It is essential that the control program on the host controller matches the addresses in the mapping configuration on the 1757-ABRIO module. Otherwise the control program may inadvertently write to the incorrect I/O locations. If you change the data mappings on the 1757-ABRIO module, make sure that the control program is using the correct addresses.

1757-ABRIO Module

Tag

TagControlLogix or ProcessLogix

Controller

Write Data

Remote I/O Modules

R/W Analog Data with Block Transfer StatusR/W digital DataScales Analog Data

Analog/Digital ModulesHard Configured for Safe/Fault States

RIO Network

Read Data

Scan List

RIO Network Scanner

Remote I/O Modules


Configure the 1757-ABRIO Module Chapter 2

Installing AbRioCfg Software

1. Verify that RSLinx software and RSLinx OEM or RSLinx Professional (not RSLinx Lite) software is installed before you install the AbRioCfg software.

2. Insert the CD supplied with the 1757-ABRIO module and run the program setup.exe.

3. Confirm that you have RSLinx OEM or RSLinx Professional (not RSLinx Lite) software installed.

Before you install a new version of AbRioCfg software, you must delete the old version. Use the Add or Remove Programs utility in your Windows Control Panel to remove the previous version.

Autoconfigure the I/O Racks

The first step in building a configuration is to perform an autoconfiguration. To complete an autoconfiguration, the RIO network must be connected to the 1757-ABRIO module and the module must be in “inactive” mode.

1. Start AbRioCfg software.

IMPORTANT Messages about the DTL32.DLL during installation or when you run the software indicate problems with the RSLinx software installation.

If you get these messages, install the proper version of RSLinx software before you continue.

IMPORTANT Removing the software does not delete stored configuration files.

TIP If you see question marks for the 1757-ABRIO module when running RSNetWorx or RSLinx software, install the EDS file from the provided CD.

You do not need to load the firmware on the CD into your 1757-ABRIO module as the module ships with the latest version of firmware. The firmware is on the CD for archival purposes only.

ATTENTION When using AbRioCfg software, you must left-click to select/highlight before you can right-click to activate menu options.



2. Click Hardware Config to highlight it and activate the AbRioCfg menu toolbar.

3. Click the Autoconfig button in the toolbar.

An RSWho window opens.

TIP With AbRioCfg software, 2.0 and higher, you can also manually configure the I/O racks in your network. Refer to Add Racks Offline on page 33 for more information.



4. Navigate to the 1757-ABRIO module.

5. Select the module and click OK.

The Select Baud Rate dialog box opens.

6. Select the appropriate baud rate and click OK.

The baud rate in this example is set by switches on the 1771-ASB adapter. See your device documentation for how to set the desired baud rate. All racks or devices on one RIO network must operate at the same baud rate.



The 1757-ABRIO module sends messages to all possible racks and builds the network rack configuration from the responses. It displays a list of the racks it found in the network tree.

If you expand a rack, the partial racks that make up that rack number are displayed.

7. If you are using 1771 remote I/O modules,

a. Right-click the rack in the network tree and select Enter Rack Switch Setting.

The Select Rack Setting dialog box opens.



b. Select the value that matches the Last State switch setting in the backplane of the I/O chassis, either De-energize or Hold Last State.

This setting tells the 1757-ABRIO module what to do if the controller stops updating the tag to which this chassis’s digital data is mapped.

c. Repeat steps 7a and 7b for all racks that contain 1771 remote I/O modules.

Adding Block Transfer Modules

Autoconfiguration can locate the racks present on the network but it cannot detect the analog I/O modules in those racks. Remote I/O protocol does not allow for module identification to be communicated on the network. Because of this, Block Transfer modules need to be added manually. You do not have to add digital modules.

To add a block transfer module, complete the following steps.

1. Expand the rack that contains the analog I/O module in the network tree.

2. Right-click the partial rack that contains the module and select Add Module.

The Add BT Module dialog box opens.

3. Select the Module Type from the pull-down menu.



4. Select the slot location for the module.

To do this, you should be familiar with Allen-Bradley addresses and, in particular, with 1771 addressing modes (see below). See I/O Module Documentation on page 84 for a list of related ControlLogix documentation.

5. Click OK.

Addressing Modes for 1771

The 1771 chassis have three addressing modes - 1/2-slot, 1-slot and 2-slot addressing. The addressing mode is set by switches in the backplane of the chassis and is set on a per-chassis basis. The addressing mode determines how physical block transfer modules map into logical addresses (rack, I/O group and slot).

In the following tables, the addresses used for modules in a 16-slot rack in each addressing mode. The rack switches are set for rack 1, starting I/O group 0.

As illustrated in the 2-slot addressing table below, the controller addresses two I/O module slots as one I/O group. For example, for a chassis at rack 1, starting I/O group 0, a block transfer module in the first slot would be at address rack 1, I/O group 0, slot 0. A module in the next slot would be at rack 1, I/O group 0, slot 1.

As illustrated in the 1-slot addressing table below, the controller addresses one I/O module slot as one I/O group. For example, for a chassis at rack 1, starting I/O group 0, a block transfer module in the first slot would be at address rack 1, I/O group 0, slot 0. A module in the next slot would be at rack 1, I/O group 1, slot 0.

2-Slot Addressing

Slot in chassis 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Rack 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

I/O Group 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7

Slot 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1

1-Slot Addressing

Slot in chassis 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Rack 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2

I/O Group 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7

Slot 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



As illustrated in the 1/2-slot addressing table below, the controller addresses 1/2 of an I/O module slot as one I/O group. For example, for a chassis at rack 1, starting I/O group 0, a block transfer module in the first slot would be at address rack 1, I/O group 0, slot 0. A module in the next slot would be at rack 1, I/O group 2, slot 0.

Configuring Block Transfer Modules

When you add a block transfer module, the configuration dialog box for that module opens. The contents of the dialog box are specific to each module type.

See Supported 1771 Modules on page 83 or the online help for information on configuring individual modules.

To edit the configuration for a module, double-click the module in the network tree, or right-click the module and select Configure.

1/2-Slot Addressing

Slot in chassis 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Rack 1 1 1 1 2 2 2 2 3 3 3 3 4 4 4 4

I/O Group 0 2 4 6 0 2 4 6 0 2 4 6 0 2 4 6

Slot 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

TIP You cannot change the location of a module in the configuration once you have created it. You must delete the module and create a new one at the new location.



Scaling Part of the configuration procedure for analog modules is entering scaling values. The 1757-ABRIO module performs scaling between raw I/O data and floating point user values.

You can send floating point output values to the 1757-ABRIO module which it converts to raw output values using the scaling values you supplied in the configuration. Similarly, the 1757-ABRIO module converts raw input data to floating point values, using the scaling you enter. The 1757-ABRIO module supports scaling values from -3.4e38 to 3.4e38. Scaling is done on a per-channel basis.

Input Scaling

For analog input modules, you must supply the floating point values to which you want the minimum and maximum raw data scaled.

Minimum corresponds to the lowest raw value.

Maximum corresponds to the maximum raw value.

EXAMPLE If a raw input range is 1 5 V dc and you set the minimum scaling value to 12.3 and the maximum scaling value to 77.4, a raw input voltage of 1 produces a scaled input value of 12.3. A raw input voltage of 5 V dc produces a scaled input value of 77.4

A raw input value outside the range of 1 5 V dc produces an input of NaN (not a number). Modules also have underrange and overrange bits to indicate data overflows.



Output Scaling

For output modules, you supply the floating point values you want to correspond to the minimum and maximum raw output values.

ATTENTIONThe minimum scale value may not be larger than the maximum scale value

EXAMPLE If a channel has a range of 1 5 V dc and you set the minimum scaling value to 12.3 and the maximum scaling value to 77.4, when you set the output value to 12.3, the module produces a raw output value of 1 V dc. When you set the output value to 77.4, the module produces a raw output of 5 V dc.

If you set the value outside the minimum and maximum scaling values, the raw output is clamped at the minimum or maximum.



Tags Defined The ProcessLogix or ControlLogix controller accesses data for the 1757-ABRIO module using unscheduled messages that read or write tags. For more information on how the controllers access this data, see Configuring the ProcessLogix Controller to Access Data on the 1757-ABRIO Module on page 51 and Configuring RSLogix 5000 Software to Access Data on the 1757-ABRIO Module on page 57.

Before you program the controller to read or write to the 1757-ABRIO module, you must define the tags in AbRioCfg software.

The 1757-ABRIO module supports the following five types of tags.

Numeric Read (1) and Numeric Write (2) tags

– Numeric read and numeric write tags are arrays of 64 scaled floating point values.

– You can map data from block transfer modules to these tags.



Flag Read (3) and Flag Write (4) tags

– Flag read and write tags are arrays of 512 bits.

– Block transfer modules also have status bits that can be mapped to flag read tags.

– Dragging an entire I/O Grp to a Flag Read or Flag Write tag will expose all discrete read or write values for that rack as well as the Rack Global Status tag.

Text Read (5) tags

– Text read tags are arrays of 64 bytes.

– They are used only with the 1770-HT1 HART module.

From the ProcessLogix or ControlLogix perspective, the HART interface is read only. You can read text and tags from the HART, but you can’t write data to the HART.



Create a Tag

If you are planning to use automatic digital tags via a scheduled connection to the 1757-ABRIO module from a ControlLogix controller, do not create tags. Refer to Scheduled Digital I/O Connections in RSLogix 5000 Programs on page 60. For all other tag types (analog, text) and unscheduled connections, tags must be manually created.

To create a tag, complete the following steps.

1. Select the appropriate tab for the type of tag you want to create.

2. Right-click the root of the tree in the tag area and select Add Tag.

The Add a Tag dialog box opens.

3. Type a tag name.

Tag names can be from 1 to 32 characters in length and must be unique.

4. Type a message timeout time.

This is the time during which the host controller must update the tag. The range of values is from 100 to 15000 ms. The default is 5000 ms.

If the message timeout is exceeded, the tag times out and the 1757-ABRIO module takes the appropriate action.

5. Click OK to accept the tag.

You can create a maximum of 64 tags, of any combination of types.



Mapping Data to Tags in AbRioCfg Software

If you are using a ControlLogix controller, no actions are necessary to read or write digital data with scheduled connections. Refer to Scheduled Digital I/O Connections in RSLogix 5000 Programs on page 60 for more information.

If you are using a ProcessLogix controller, you need to create flag read and flag write tags in AbRioCfg software to have access to this data.

Block Transfers

When mapping block transfer modules, drag the analog module from the network tree to the location in the tag where you want the data to be located.

Block transfer read data can be mapped to numeric read tags.

Block transfer write data can be mapped to numeric write tags.

You cannot map individual registers; all the data for a rack or I/O module is mapped to the tag. You can map data from many I/O modules into the same tag.

Mappings must be unique. You cannot map a block transfer module to more than one tag of the same type or to multiple locations within the same tag.

In addition, block transfer modules have status information that can be mapped to flag read tags. Refer to Supported 1771 Modules on page 83 for detailed information on status information.

TIP Rack Digital Data

If you would like to use scheduled ControlNet connections to the 1757-ABRIO module via a ControlLogix controller, do not map any racks to digital tags. This is done for you when the scheduled connection is established. Refer to Scheduled Digital I/O Connections in RSLogix 5000 Programs on page 60 for more information.



I/O

To map I/O data to a tag, complete the following steps.

1. Expand the tag to show the tag elements.

2. Scroll to display the destination in the tag where you want to add the data.

3. Drag the rack or block transfer module to the desired location in the tag.

Deleting Mapped Data

To delete mapped data from a tag, complete the following steps.

1. Select any element of the data.

2. Click Delete.

You cannot delete individual elements of the data for an I/O module. When you delete an element you delete all the data for the particular module. Data is not affected for the other modules mapped to the same tag.

Tips for Configuring Modules

Use the largest range of raw values possible for the 1757-ABRIO module and optimum data resolution. The scaling should be done to engineering units in the module.

The following operations are features of firmware version 2.1. To use these features, you need the following:

Firmware version 2.1 or above for the 1757-ABRIO module

AbRioCfg software version 2.0 or above

AbRioCfg software version 2.0 or above can open or upload configurations made with previous versions of AbRioCfg software.



Add Racks Offline

To add a rack, complete the following steps.

1. Right-click Hardware Config and select Add A Rack.

2. Enter the Rack Number (1 to 37 octal), Starting I/O Group (0,2,4,6) and Ending I/O Group (1,3,5,7) and click OK.



Delete Racks Offline

To delete racks offline, complete the following steps.

1. Right-click the partial rack and select Delete Rack.

A warning dialog box opens.

2. Click OK.

When you delete a rack, all I/O modules on the rack and flag mappings for the rack are deleted. If this partial rack is the only one in the rack number, the rack number will be deleted from the tree.



Change the Baud Rate Offline

To change the baud rate offline, complete the following steps.

1. Select Actions>Change Baud Rate.

The Select Baud Rate dialog box opens.

2. Select the desired baud rate and click OK.

A warning window opens

3. To select the path to the 1757-ABRIO module from an RSWho window, click Yes.

To make this change in the offline file only, click No.

Download the Configuration

To download the configuration to the 1757-ABRIO module from AbRioCfg software, select Actions>Download config or click the Download Configuration to Module button on the toolbar.

WARNING Downloading a configuration disrupts communication between the 1757-ABRIO module and the RIO network.

If the module is in active or forced active mode, the configuration program asks if you want to remove it from active mode.

Scaling data for modules that have not been mapped to tags is not downloaded with the configuration.



Upload the Configuration To upload a configuration from a 1757-ABRIO module, select Actions>Upload config or click the Upload Config From Module button on the toolbar.


Chapter 3

Creating Generic Modules in AbRioCfg Software

Introduction This chapter describes using a generic module type which supports any block transfer I/O module that uses 16-bit integer data. To use these features, you need the following:

Firmware version 2.1 or above of the firmware for the 1757-ABRIO module

AbRioCfg software version 2.1 or above

AbRioCfg software version 2.1 or above can open or upload configurations made with previous versions of AbRioCfg software.

If you are using a 1771 module refer to Supported 1771 Modules on page 83.

If you need to access HART data refer to Accessing HART Data on page 115.

Generic Module Overview The generic module type makes it possible to do the following:

Configure and communicate with any block transfer I/O module that uses 16-bit integer data. You create the configuration file as a comma-separated variable (CSV) file, using a spreadsheet or text editor, and import it using AbRioCfg software.

Configure a block transfer module that is already supported by AbRioCfg software in ways that the standard configuration does not allow, for example, using fewer channels than in the standard module configuration, or adding features not supported by the standard configuration.

Have up to 100 different generic module types in an 1757-ABRIO configuration file, and an unlimited number of modules made from those 100 types.


Chapter 3 Creating Generic Modules in AbRioCfg Software

Generic Module Configuration File

The Generic Module configuration file consists of these sections.

– the configuration block transfer write (BTW)– the data block transfer read– the data block transfer write

Most configuration files have a configuration block transfer write. Some may have both data block transfer read and data block transfer write sections; others will have just one or the other. The maximum size for each section is 64 words of data.

You can add comments to the file by preceding them with a semicolon. Comments can be added to the end of an existing line or can occupy separate lines. The configuration file can be created as a text file or as a spreadsheet using a program like Excel and saved as a CSV file.

To use a text file, separate the data fields with commas. To use a spreadsheet, put the data values in separate columns.

Configuration Block Transfer Write

The configuration block transfer write section (Config BTW) contains the data that is sent to the module to set how it operates. The configuration block transfer write is sent:

at powerup

when communication is restored after being lost

when the remote I/O network switches from program to run

The first line of the configuration block transfer write is the keyword “configbtw”, followed by the block transfer length, in words.

This is followed by data definitions that consist of an offset and a value.

IMPORTANT The length of a CSV filename must not exceed 31 characters.

TIP Sample configuration files are available for your use. The files are located in the \GenProfile directory on the supplied 1757-ABRIO CD.

EXAMPLE configbtw, 13


Creating Generic Modules in AbRioCfg Software Chapter 3

The offset is the offset into the block transfer and ranges from 0 to the block transfer length - 1. For example, if the block transfer is 10 words long, the allowed offsets range from 0 to 9.

The value can be in one of the following formats:

Binary values start with a leading “0b”. Hexadecimal values start with a leading “0x”. It's usually easier and less prone to error to enter the values in binary or hexadecimal.

Format Range

Binary 0b0000000000000000 to 0b1111111111111111

Hexadecimal 0x0000 to 0xFFFF

Unsigned integer 0 to 65535

Signed integer -32768 to 32767

TIP If a module does not require a configuration block transfer write, you can omit the Config BTW section of the configuration file. For example, an SLC analog module does not require a Config BTW section in the file.

EXAMPLE 0, 0b10110011001000017, 0xB32111, 45857

Only non-zero values need be entered; all other values in the configuration block transfer will default to 0.



Example: 1771-IFE Module

The following configuration block transfer write file configures a 1771-IFE for the following:

differential operation (8 input channels)

each channel set for 1-5 VDC or 4-20 mA

two's complement binary data format

each channel's raw data scaled between 0 and 4095

Refer to the 1771-IFE module documentation for configuration details.

configbtw, 21 ; length 210, 01, 02, 0x0500 ; differential inputs, binary3, 04, 05, 06, 0x4095 ; channel 1 scaling7, 08, 0x4095 ; channel 2 scaling9, 010, 0x4095 ; channel 3 scaling11, 012, 0x4095 ; channel 4 scaling13, 014, 0x4095 ; channel 5 scaling15, 016, 0x4095 ; channel 6 scaling17, 018, 0x4095 ; channel 7 scaling19, 020, 0x4095 ; channel 8 scaling



Example: 1771-OFE module

The following configuration block transfer write file configures a 1771-OFE for:

binary data format

raw data from 0 to 0x0fff (0 to 4095 decimal) on each channel

0 values have been omitted.

Refer to the 1771-OFE module documentation for the details.

Data Block Transfer Read

The data block transfer read defines the cyclic block transfer read that is used to read data from an input module, and is sometimes used to read status data from an output module.

The data block transfer read consists of a numeric section and a flag section.

The beginning of the data block transfer read section is marked by the keyword “databtr”, followed by the block transfer read length.

Numeric Data

The numeric section of the data block transfer read defines the I/O data - its location, format, and scaling.

The beginning of the numeric section is marked by the keyword “numeric”, followed by the number of values to be defined, and the data format.

EXAMPLE databtr, 15

configbtw, 13 ; length 134, 0x8000 ; binary data format6, 0x0fff ; maximum raw value channel 18, 0x0fff ; maximum raw value channel 210, 0x0fff ; maximum raw value channel 312, 0x0fff ; maximum raw value channel 4



AbRioCfg software checks the number of values to be defined against the actual number of definitions and indicates an error if they do not match.

The format can be one of:

All items must have the same format.

This is followed by definitions for the I/O data values, each on a row of the spreadsheet (or line of a text file). Each definition consists of the following fields:

Some modules have data underrange and overrange bits to indicate out-of-range inputs.

If the underrange or overrange bit is set, the AbRioCfg software sets the I/O value to NaN.

Format Range of values

BCD 0 to 9999

Unsigned 0 to 65535

Integer -32768 to 32767

EXAMPLE numeric, 4, BCDnumeric, 8, integer

Quantity Description

BTR offset Offset into BTR data The BTR offset is the offset into the BTR data for the I/O data value

Underrange offset(1)

(1) If the offset is not used, the field must be left blank (not 0).

Word offset of underrange bit, 0–15

Underrange bit Bit number, 0–15

Overrange offset(1) Word offset of overrange bit, 0–15

Overrange bit Bit number, 0–15

Polarity offset(1) Word offset of polarity bit, 0–15

Polarity bit Bit number, 0–15

Minimum raw value Minimum raw input

Maximum raw value Maximum raw input

Minimum scale value Minimum floating point scaled value that corresponds to minimum raw value

Maximum scale value Maximum floating point scaled value that corresponds to maximum raw value



If the module does not have overrange or underrange bits, leave those fields blank in the configuration file.

Some modules have a separate polarity bit to indicate the sign of an input.

If the polarity bit is set, the 1757-ABRIO module assigns the corresponding data a negative value.

the 1757-ABRIO module uses the polarity offset and bit only for the BCD data type. It ignores them for the other data types.

If the data type is BCD, enter the raw minimum and maximum values in decimal, not hexadecimal. For example is the range is 0 to 9999, enter the value as 9999, not 0x9999.

Flag Data

In some cases the block transfer read contains data that we want to map to flag read tags, for example, a module error bit. If a module has flag data defined, you can then map it to flag read data in AbRioCfg software.

The flag data section of the Data Block Transfer read defines the location of this discrete data.

The beginning of the flag section is marked by a line containing the keyword “flag”, followed by the total length of the flags data, in bits. The length must be a multiple of 8.

This is followed by a number of lines that define where the flag data is found. Each line consists of an offset and a length. The maximum number of flag data definition lines is 4.

EXAMPLE A 1771-IFE module has channel 1 data at offset 4, the underrange bit is in offset 1, bit 0, the overrange bit is in offset 2, bit 0, and the polarity bit is in offset 3, bit 0. The raw data ranges from 0 to 4095. We want to scale the raw data to floating point values from 0 to 1000.

In a text file:

4,1, 0, 2, 0, 3, 0, 0, 4095, 0, 1000

In a spreadsheet:

EXAMPLE flag, 32

numeric 4 BCD4 1 0 2 0 3 0 0 4095 0 1000



The offset is an offset into the block transfer. It can range from 0 to the length of the block transfer - 1. If the offset is followed by an “H”, it refers to the high byte of the block transfer word. The length can range from 8 to 504 and must be a multiple of 8. The sum of the lengths in the data definitions must match the length in the “flag” line.

Example: 1771-IFE Module

The following definitions assign the underrange and overrange bits from a 1771-IFE module to flag data.

Special Flag Read Data

In addition to any flag read data you define in the configuration file, the Generic Module always has 8 bits of predefined flag read data. This data is found at the beginning of the flag data for the module. It consists of the following flags:

EXAMPLE flag, 32

Bit Description

0 Good communication, set to 1 if the block transfer to the module is updating, 0 otherwise.

1 BTR Raw underrange bit, set if the raw input to the module is less than the defined raw minimum. The module sets the scaled input to NaN.

2 BTR raw overrange, set if the raw input to the module is greater than the defined raw maximum. The module sets the scaled input to NaN.

3 Reserved

4 Reserved

5 BTW raw underrange, set if the calculated output value is less than the defined raw minimum. The module clamps the output at the raw minimum.

6 BTW raw overrange, set if the calculated output value is greater than the defined raw maximum. The module clamps the value at the raw maximum.

7 BTW NaN, set if the floating point value written from the host is NaN.

0,82H,84,16

flag, 321,162,16



Sample 1771-IFE Configuration File

Data Block Transfer Write

The data block transfer write defines the cyclic block transfer read that is used to write data to an output module. The data block transfer write consists of a numeric section and a flag section. The beginning of the data block transfer write section is marked by the keyword “databtw, followed by the block transfer write length.

EXAMPLE databtw, 12

configbtw, 21 ; length 212, 0x0500 ; differential inputs, binary5, 06, 0x4095 ; channel 1 scaling7, 08, 0x4095 ; channel 2 scaling9, 010, 0x4095 ; channel 3 scaling11, 012, 0x4095 ; channel 4 scaling13, 014, 0x4095 ; channel 5 scaling15, 016, 0x4095 ; channel 6 scaling17, 018, 0x4095 ; channel 7 scaling19, 020, 0x4095 ; channel 8 scalingdatabtr, 12numeric, 4, signed4, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 10005, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 10006, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 10007, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 10008, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 10009, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 100010, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 100011, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 1000flag, 321, 162, 16



Numeric Data

The numeric section of the data block transfer write defines the I/O data - its location, format, and scaling.

The beginning of the numeric section is marked by the keyword “numeric”, the number of values to be defined, and the data format.

AbRioCfg software checks the number of values to be defined against the actual number of definitions and indicates an error if they do not match.

The format can be one of the following.

All items must have the same format.

This line is followed by definitions for the I/O data values, each on a row of the spreadsheet (or line of a text file). Each definition consists of the following fields:

The BTW offset is the offset into the BTW data for the I/O data value.

Some modules have a separate polarity bit to indicate the sign of an input. If the data being written is negative, the 1757-ABRIO module sets the polarity bit.

Format Range of values

BCD 0 to 9999

Unsigned 0 to 65535

Integer -32768 to 32767

EXAMPLE numeric, 4, BCDnumeric, 8, integer

Quantity Description

BTW offset Offset into BTW data

Polarity offset Word offset of polarity bit

Polarity bit Bit number, 0-15

Minimum raw value Minimum raw output

Maximum raw value Maximum raw output

Minimum scale value Minimum floating point scaled value that corresponds to minimum raw value

Maximum scale value Maximum floating point scaled value that corresponds to maximum raw value



The 1757-ABRIO module uses the polarity offset and bit only for the BCD data type. It ignores them for the other data types.

If the scaled valued written is NaN, the raw output gets set to the corresponding value in the configuration data. For example, if an I/O data value is at offset 7 in the data block transfer write, the value at offset 7 in the configuration block transfer write is written if the host controller writes NaN to the tag that is mapped to the I/O value.

Flag Data

In some cases the block transfer write contains data that we want to map to flag write tags.

The flag data section of the Data Block Transfer write defines the location of this discrete data.

The beginning of the flag section is marked by a line containing the keyword “flag”, followed by the total length of the flags data, in bits. The length can be from 8 to 504 and must be a multiple of 8.

This is followed by a number of lines that define where the flag data is found. Each line consists of an offset and a length. The maximum number of flag definition lines is 4.

The offset is an offset into the block transfer. It can range from 0 to the length of the block transfer - 1. If the offset is followed by an “H”, it refers to the high byte of the block transfer word.

The length can range from 8 to 504 and must be a multiple of 8.

TIP If the data type is BCD, enter the raw minimum and maximum values in decimal, not hexadecimal. For example is the range is 0 to 9999, enter the value as 9999, not 0x9999.

EXAMPLE A 1771-OFE module has channel 1 data at offset 0. The polarity bit is offset 4 bit 0. We want to write floating point values from 0 to 1000 and have them scaled to the raw values 0 to 4095.

In a text file:

0, 4, 0, 0, 4095, 0, 1000

In a spreadsheet:

EXAMPLE flag, 32

0 4 0 0 4095 0 1000



The sum of the lengths in the data definitions must match the length in the “flag” line.

Example 1771-OFE Configuration File

Creating a Generic Module in AbRioCfg software

To add a generic module in AbRioCfg software, complete the following steps.

1. Right-click the rack to which the module will be added and select Add Module.

EXAMPLE flag, 320,82H,84,16

configbtw, 13 ; length 134, 0x8000 ; binary data format6, 0x0fff ; maximum raw value channel 18, 0x0fff ; maximum raw value channel 210, 0x0fff ; maximum raw value channel 312, 0x0fff ; maximum raw value channel 4databtw, 12numeric, 40, 4, 0, 0, 4095, 0, 10001, 4, 1, 0, 4095, 0, 10002, 4, 2, 0, 4095, 0, 10003, 4, 3, 0, 4095, 0, 1000



2. Select a Module Type of Generic Module, the location for the module and click OK.

3. Browse to or type the CSV file and path and click Import.

AbRioCfg software imports the configuration file and displays the contents, or gives an error message if it finds problems with the file.

4. Assign values for the BTR and BTW Update Times.

5. Click OK to accept the module.

You can now map the data to tags by dragging the Generic module to the desired numeric read, numeric write, flag read or flag write tag.

To change the configuration, re-import the configuration. If the generic module was mapped to tags, the mappings will be deleted and must be reassigned.



You can export the generic module configuration by clicking the Export button in the Generic Module dialog box. Since comments in the original file are not imported (and therefore are not exported), it is usually better to modify the original configuration file and save it with a new name. Export may be useful if you upload a configuration that contains a generic module from a 1757-ABRIO module and you do not have the original file.


Chapter 4

Configuring the ProcessLogix Controller to Access Data on the 1757-ABRIO Module

Introduction This chapter describes:

the operating modes of the 1757-ABRIO module.

how to access data on the module from a ProcessLogix controller.

Modes of Operation There are four modes of operation for the module.

CONFIG

INACTIVE (Program)

ACTIVE (Run)

FORCED ACTIVE

The mode of the 1757-ABRIO module determines the RIO network mode.

Modes related to RIO network operations:

INACTIVE (Program) mode, digital inputs continue to update but digital outputs and block transfers do not.

ACTIVE (Run) mode, digital inputs and outputs update, and block transfers update.

CONFIG Mode

The module is in CONFIG mode while AbRioCfg software downloads a configuration. CONFIG mode is largely invisible to the user unless the configuration being downloaded is large. After downloading, the software returns the module to INACTIVE mode.


Chapter 4 Configuring the ProcessLogix Controller to Access Data on the 1757-ABRIO Module

INACTIVE Mode

The module is in INACTIVE mode when it is not receiving messages from either a host controller or via OPC/DDE. The module is also in INACTIVE mode when it has not been put in FORCED ACTIVE mode by AbRioCfg software.

When the module is in INACTIVE mode, the RIO network is placed in program mode with input updates but no output updates. The 1757-ABRIO module must be in the INACTIVE mode to accept a download.

ACTIVE Mode (Run)

The module is in ACTIVE mode when it receives a message from either a host controller or from an OPC or DDE server. When the module is in ACTIVE mode, the RIO network is in run mode.

The module is in ACTIVE mode as long as any tag is being updated. Each tag has an associated time-out. The tag is considered to be updating until the time-out expires. If all tags have timed out, the 1757-ABRIO module automatically switches to INACTIVE mode.

If you try to download a configuration when the module is in ACTIVE mode, AbRioCfg software asks if you want to take the module out of ACTIVE mode. If you click OK, AbRioCfg software changes the mode, downloads the configuration, then puts the module in INACTIVE mode.

FORCED ACTIVE Mode

The module is in FORCED ACTIVE mode when you set ACTIVE mode from the AbRioCfg program. FORCED ACTIVE mode lets you send and receive data without having to create messages in the module. It is intended primarily for setting up and testing RIO networks.

If you try to download a configuration when the module is in FORCED ACTIVE mode, AbRioCfg software asks if you want to take the module out of ACTIVE mode. If you click OK, AbRioCfg software changes the mode, downloads the configuration, then puts the module in INACTIVE mode.

IMPORTANT When the module is in FORCED ACTIVE mode, the RIO network is in run mode.


Configuring the ProcessLogix Controller to Access Data on the 1757-ABRIO Module Chapter 4

Configure the 1757-PLX52 Controller

To access tag data on the 1757-ABRIO module from a ProcessLogix controller, use the REQNUMARRAY, REQFLAGARRAY and REQTEXTARRAY Exchange Blocks with CIPREAD and CIPWRITE commands to read and write tags.

Use Control Builder software to complete the following steps.

1. Select the Exchange Block from the Library in Control Builder.

2. Add the desired Exchange Block to the CM (Control Module) by dragging it into the CM window.

– REQFLAGARRAY for flag data

– REQNUMARRAY for numeric data

– REQTEXTARRAY for text data

3. Expand the Exchange Block by double-clicking on it.

4. Select the Main tab.

5. Give the block a name and set the execution order.

6. Select either CIPREAD or CIPWRITE for the message command.



7. Set the number of values to be read or written.

a. Flag arrays, 512 max

b. Numeric arrays, 64 max

c. Text arrays, 64 max

Array Examples

8. Set the data type to be read or written.

a. Numeric arrays, set Data Type in Target Device to FLOAT32.

b. Text arrays, set the Number of String Values to 1 and the Char Length of String Values to 64.

9. Select the Communications tab.

10. Set the Path from the ProcessLogix controller to the 1757-ABRIO module.

See the tip on page 72 or Control Builder Help for information on entering the path.

Flag Arrays Numeric Arrays Text Arrays


Configuring the ProcessLogix Controller to Access Data on the 1757-ABRIO Module Chapter 4

11. Set the File Name in the Exchange Blocks to the names of the tags you created in the 1757-ABRIO module.

12. Perform any other configuration required by your application on the other tabs.

13. Click OK to accept the block.

14. Wire the ready flag (READYFL) to the send flag (SENDFL) for each exchange block.

15. Download the CM to the ProcessLogix controller and activate it.

IMPORTANT Be sure to expose the Error codes in your Exchange Blocks.



Live Data Examples

Double-click function block


Chapter 5

Configuring RSLogix 5000 Software to Access Data on the 1757-ABRIO Module

Introduction This chapter describes:

the operating modes of the 1757-ABRIO module.

how to access data on the module from a ControlLogix controller.

Modes of Operation There are four modes of operation for the module.

CONFIG

INACTIVE (Program)

ACTIVE (Run)

FORCED ACTIVE

The mode of the 1757-ABRIO module determines the RIO network mode.

Modes related to RIO network operations:

INACTIVE (Program) mode, digital inputs continue to update but digital outputs and block transfers do not.

ACTIVE (Run) mode, digital inputs and outputs update, and block transfers update.

CONFIG Mode

The module is in CONFIG mode while AbRioCfg software downloads a configuration. CONFIG mode is largely invisible to the user unless the configuration being downloaded is large. After downloading, the software returns the module to INACTIVE mode.


Chapter 5 Configuring RSLogix 5000 Software to Access Data on the 1757-ABRIO Module

INACTIVE Mode

The module is in INACTIVE mode when it is not receiving messages from either a host controller or via OPC/DDE. The module is also in INACTIVE mode when it has not been put in FORCED ACTIVE mode by AbRioCfg software.

When the module is in INACTIVE mode, the RIO network is placed in program mode with input updates but no output updates. The 1757-ABRIO module must be in the INACTIVE mode to accept a download.

When scheduled connections are used, the 1757-ABRIO module’s mode will always follow the ControlLogix controller’s mode regardless if it is receiving messages. For example, when the controller is in PROGRAM mode, the module is in INACTIVE mode.

ACTIVE Mode (Run)

The module is in ACTIVE mode when it receives a message from either a host controller or from an OPC or DDE server. When the module is in ACTIVE mode, the RIO network is in run mode.

The module is in ACTIVE mode as long as any tag is being updated. Each tag has an associated time-out. The tag is considered to be updating until the time-out expires. If all tags have timed out, the 1757-ABRIO module automatically switches to INACTIVE mode.

If you try to download a configuration when the module is in ACTIVE mode, AbRioCfg software asks if you want to take the module out of ACTIVE mode. If you click OK, AbRioCfg software changes the mode, downloads the configuration, then puts the module in INACTIVE mode.

When scheduled connections are used, the 1757-ABRIO module’s mode will always follow the ControlLogix controller’s mode regardless if it is receiving messages. For example, when the controller is in RUN mode, the module is in ACTIVE mode.


Configuring RSLogix 5000 Software to Access Data on the 1757-ABRIO Module Chapter 5

FORCED ACTIVE Mode

The module is in FORCED ACTIVE mode when you set ACTIVE mode from the AbRioCfg program. FORCED ACTIVE mode lets you send and receive data without having to create messages in the module. It is intended primarily for setting up and testing RIO networks.

If you try to download a configuration when the module is in FORCED ACTIVE mode, AbRioCfg software asks if you want to take the module out of ACTIVE mode. If you click OK, AbRioCfg software changes the mode, downloads the configuration, then puts the module in INACTIVE mode.

IMPORTANT When the module is in FORCED ACTIVE mode, the RIO network is in run mode.



Scheduled Digital I/O Connections in RSLogix 5000 Programs

1757-ABRIO module firmware versions 1.2 and above support scheduled connections for exchanging digital input and output data between the 1757-ABRIO module and the host ControlLogix controller. This results in much faster updates for the digital data than is possible using unscheduled messages. This section describes how to configure the module and the format of the scheduled data.

When you add a 1757-ABRIO module to the I/O Configuration of an RSLogix 5000 program using the generic 1757-MODULE profile, a data connection is created for the digital remote I/O data. See Tag Descriptions for Scheduled Data in RSLogix 5000 Software on page 149 for more information about the status tag when using ControlLogix. The status tag gives global status for digital data and individual rack status.

Scheduled Connection Types

There are two types of scheduled connection.

Exclusive Owner, read/write

Input Only, read only

Setup an Exclusive-owner Connection

Configure a generic module profile in RSLogix 5000 software to represent the 1757-ABRIO module. This dictates the format and amount of scheduled data, and how often the scheduled data is transferred. The ControlLogix controller is the owner of the connection and controls the digital outputs. The connection is referred to as an exclusive-owner connection.

TIP In order to access any numeric read, numeric write, or text read data from the ControlLogix controller you must also complete Unscheduled I/O Connections in ControlLogix on page 67.

IMPORTANT In order for the scheduled connection to control the outputs of a chassis, the chassis must not be mapped to any flag write tag in the AbRioCfg software configuration that has been downloaded to the 1757-ABRIO module.



Remote I/O Operating Modes

If there is an exclusive-owner connection to the 1757-ABRIO module, the module’s remote I/O mode (run or program) follows the owner ControlLogix controller’s Run or Program mode. If the owner ControlLogix controller is in Program mode, the 1757-ABRIO module is in program mode (even if the module is receiving messages). If the ControlLogix controller is in Remote Test mode, the remote I/O mode for the 1757-ABRIO module is program.

The remote I/O mode is not affected by the operating mode of a ControlLogix controller that has an input-only connection to the 1757-ABRIO module. In the absence of an exclusive-owner connection, the 1757-ABRIO module’s remote I/O mode is determined by whether it is receiving messages, as before.

Add a Module as an Exclusive-owner Connection

To configure the 1757-ABRIO module in RSLogix 5000 software, the ControlLogix controller must be offline.

1. Create a new project for your type of controller.

2. Type a name for the controller, and select the slot it occupies in the ControlLogix chassis.

3. Click OK.

4. Right-click on I/O configuration and select New Module.

5. Under Other, select the 1756-MODULE Generic 1756 Module and click OK.

The Module Properties dialog box opens.



6. Type a Name and a Description for the module, if desired.

7. Set the Slot number for the module in the ControlLogix chassis.

8. For the Comm Format, select Data - INT - With Status.

9. Select the following values for the Connection Parameters.

10. Verify that the Open Module Properties checkbox is checked and click OK.

11. Set the module’s Requested Packet Interval (RPI).

This is how often the module's scheduled data is updated in the controller. The value can range from 0.2 to 750 ms. The default time is 5 ms.

12. Click OK.

13. Save the program and download it to the ControlLogix controller.

Assembly Instance

Size

Input 1 250

Output 2 248

Configuration 4 0

Status Input 5 10

Status Output 6 N/A



Output Priority

If a digital rack is mapped to a flag write tag in the AbRioCfg software, the flag data takes precedence over the digital outputs in the scheduled connection, even if nothing is writing to the flag write tag. To control outputs on a chassis using a scheduled connection, make sure the chassis is not mapped to a flag write tag.

Setup Input-only Connections

The 1757-ABRIO module also supports input-only connections. In a ControlLogix system, multiple controllers can receive inputs from a module, but only one controller can control the outputs. An input-only connection does not require the presence of an exclusive owner connection. More than one ControlLogix controller can open an input-only connection to the 1757-ABRIO module and receive its inputs.

Add a Module as an Input-only Connection

To configure an input-only connection to the 1757-ABRIO module in RSLogix 5000 software, you must be offline.

1. Create a new project for your type of controller.

2. Type a name for the controller, and select the slot it occupies in the ControlLogix chassis.

3. Click OK.

4. Right-click on I/O configuration and select New Module.

5. Under Other, select the 1756-MODULE Generic 1756 Module and click OK.



The Module Properties dialog box opens.

6. Type a Name and a Description for the module, if desired.

7. Set the Slot number for the module in the ControlLogix chassis.

8. For the Comm Format, select Input Data - INT - With Status.

9. Select the following values for the Connection Parameters.

Assembly Instance

Size

Input 1 250

Output 3 N/A

Configuration 4 0

Status Input 5 10

Status Output 6 N/A



10. Verify that the Open Module Properties checkbox is checked and click OK.

11. Set the module’s Requested Packet Interval.

This is how often the module's scheduled data is updated in the controller. The value can range from 0.2 to 750 ms. The default is 5 ms.



12. Click OK.

13. Save the program and download it to the ControlLogix controller.

Live Data Example

Click the 1757-ABRIO module to display the new tags. See Tag Descriptions for Scheduled Data in RSLogix 5000 Software on page 149 for details.



Unscheduled I/O Connections in ControlLogix

There are several tasks you need to complete before you can access data from ControlLogix. You need to create the following:

Tags for messages

Tags for storage areas

Message commands to read RIO network data

Message commands to write RIO network data

Use RSLogix 5000 message instructions (MSG) to access tags on the 1757-ABRIO module. Refer to RSLogix 5000 Online Help and the Logix5000 Controllers General Instructions Reference Manual, publication 1756-RM003, for details on messages.

Before you create the MSG instruction, create a tag of type MESSAGE to act as a control for the MSG instruction. You must also create a source (write) or destination (read) tag for the data written to or read from the 1757-ABRIO module.

1. Create Tags For All Messages and All Storage Areas

RSLogix 5000 Example Tags in Program Mode

For message type, select CIP Data Table Read or Data Table Write.

On a Read, the source is a 1757-ABRIO Tag Name. The Destination, on a Read, is an RSLogix 5000 Tag Name.

These are the tags you will reference in your message commands.


http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm003_-en-p.pdf


2. Create Message Commands to Read and Write All RIO Network Data

RSLogix 5000 Example Message Commands in Program Mode

This table shows the source (write) or destination (read) data type to use with each 1757-ABRIO tag type and the size for each type.

Use the Browse button ( ) to locate the read/write tags you want to reference in your message commands. See Create a Tag on page 30 for more information.

ControlLogix Data types

1757-ABRIO Tag Source/destination Type Storage Data Size

Numeric read REAL 64

Numeric write REAL 64

Flag read DINT 16

Flag Write DINT 16

Text read SINT 64



Use the following steps to add the MSG instruction.

1. Add the MSG instruction to the ladder logic, along with whatever logic you want to use to cause the instruction to execute.

2. Open the Message Configuration dialog box by clicking the

button in the instruction.

3. Select the Message Type.

The Message type should be either CIP Data Table Read to read a tag from the 1757-ABRIO module or CIP Data Table Write to write a tag to the 1757-ABRIO module.

WARNING The EN_CC bit in a ControlLogix MESSAGE tag defaults to on. If the message executes successfully even once, it gets retried periodically, even if the ladder logic has disabled the message. If you want to keep the connection open no matter what, turn on the bit.

Turn off the EN_CC bit in any ControlLogix MESSAGE tag you use in a MSG instruction to access data on the 1757-ABRIO module.



4. Select the Source Element.

If you are writing to the 1757-ABRIO module, this is the ControlLogix controller tag.

If you are reading from the 1757-ABRIO module, this is the name of the tag in the 1757-ABRIO module.

The 1757-ABRIO module must return different data types to ProcessLogix and ControlLogix controllers. For example, to read a tag with name FlagRead, you would create a MSG instruction with Source Element set to FlagRead[100].

5. Type the Number of Elements.

This is usually the number from the table on page 68. You can select a size smaller than the maximum if not all of the elements in the 1757-ABRIO module tag have been mapped.

6. Select the Destination Element.

TIP

IMPORTANT If you are reading flag read tags using a ControlLogix controller, you must append [100] to the 1757-ABRIO tag name. This tells the 1757-ABRIO module that the message is coming from a ControlLogix controller.

Use this tag To

All_Analog_Read Read data from input modules.

The tag is listed under Numeric Read Tags.

All_Flag_Read[100] Flag read for status and digital data.

This is the message needed to get to analog data.



7. Select the Communication tab.

8. Type the path from the ControlLogix controller to the 1757-ABRIO module.



When you are using scheduled connections in ControlLogix this is automatically populated with your 1757-ABRIO module’s name and address through an RSNetworx network polling.

9. Click OK to accept the MSG instruction.

10. After all message instructions are configured, save the program and download it to the ControlLogix controller.

TIP The 1757-ABRIO module, ProcessLogix controller and ControlLogix controller (most likely) will not be in the same racks. Refer to RSLogix 5000 Online Help and the Logix5000 Controllers General Instructions Reference Manual, publication 1756-RM003 for details on MSG paths.

TIP If you need to manually input the communications path to a module, follow this general example of how to find the path to the rack.

Illustrated is the path from the ProcessLogix or the ControlLogix controller to the remote 1757-ABRIO module.Path = 1,4,2,20,1,2

1: From the backplane

4: Node, 1756-CNBR Module in slot 4

2: Path out of the CNBR, ControlNet

20: MAC ID of the target CNBR in the remote rack

2:Slot location of the 1757-ABRIO module

1: From the CNBR, via the backplane


http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm003_-en-p.pdf


Live Data Example



Ladder Rung Example


Chapter 6

Accessing Data through a DDE or OPC Server

Introduction This chapter describes how to access data on the module using a DDE or OPC Server.

Accessing Data from a DDE or OPC Server

You can access data on the 1757-ABRIO module directly using a DDE or OPC server such as RSLinx software, without the intervention of a host controller.

Configuring a Topic in RSLinx Software

Use the following procedure to use RSLinx software as a DDE or OPC server to access data on the 1757-ABRIO module.

1. Start RSLinx software

2. Select DDE/OPC Topic Configuration from the main menu.

3. Click New to create a new DDE or OPC topic, and give the topic a name.

4. Select the Data Source tab and browse to the 1757-ABRIO module.

5. Select the Data Collection tab.

6. Set the Processor Type to Logix5000.

7. Check Polled Messages and set the poll period to an appropriate value.

8. Un-check Unsolicited Messages.

9. Leave the remaining values at their default values and click Apply.

10. Select the Advanced Communication tab.

11. Select the Communications Driver you are using.


Chapter 6 Accessing Data through a DDE or OPC Server

12. Change Local or Remote Addressing defaults to Local.

If you are using a bridge device to communicate with the 1757-ABRIO module, select Remote and configure the bridging. Refer to the RSLinx software documentation for detailed information on how to configure bridging.

13. Click Done to accept the DDE/OPC topic.

Accessing the Data

1. Start your DDE or OPC client.

2. Connect to RSLinx software.

The 1757-ABRIO module supports browsing of tags.

3. Type or browse to the tags you want to monitor in the client.


Chapter 7

Monitoring the 1757-ABRIO Module

Introduction This chapter provides the following information on:

monitoring the operation of the 1757-ABRIO module.

monitoring the data value of tags.

monitoring the status of a block transfer.

monitoring the scanner log.

recognizing and clearing fatal errors.

Monitoring the Operation The AbRioCfg software lets you monitor the operation of the module and perform maintenance operations. Tag, block transfer, and module diagnostic counters are available only from AbRioCfg software, and are not available to a ProcessLogix or ControlLogix controller.

AbRioCfg software can be used to:

display the current values of the digital inputs and outputs.

display the current values of block transfer data, along with diagnostic information on the block transfer.

display the current contents of a tag.

display the module log, which consists of messages from the firmware running on the module.

clear the log.

copy the contents of the log to the clipboard for use by another application. This is often useful for technical support.

clear fatal errors and dump the fatal error log to a file for use by technical support.

Monitoring Digital I/O To monitor the current value of digital inputs or digital outputs on all racks, select Tools>Monitor Inputs or Tools>Monitor Outputs.

Rows correspond to racks 1 to 37 octal; columns correspond to I/O groups 0 to 7.

Data can be displayed in hexadecimal, signed decimal, or unsigned decimal using the View menu or buttons on the toolbar. The default format is hexadecimal. One hexadecimal digit corresponds to 4 digital bits.

You can use the monitor program to edit data.


Chapter 7 Monitoring the 1757-ABRIO Module

Use the Edit>Write toolbar button or the menu item to enable editing. You can now change any data and it will be written to the network (outputs) or to the data table (inputs). However if the same data is being updated by I/O modules or the controller, the value you write is overwritten the next time this I/O module is scanned.

Monitoring the Data Value of Tags

To monitor the current data value in a tag, complete the following steps.

1. Select the corresponding tab for the data type of the tag you want to monitor (Numeric read, etc.).

2. Select the tag you want to monitor.

3. Right-click the tag and select Monitor Tag.

The tag monitor displays the raw data for the tag, as well as diagnostic data.

The raw data can be displayed as floating point, hexadecimal, signed, or unsigned integer.

Refer to the following table for tag diagnostic information.

To clear the diagnostic counters, select Actions>ClearDiagCounters or click the Clear Diag Counters button on the toolbar.

Tag Diagnostic Counters

Counter Description

Tag Name The tag name in AbRioCfg software

Command Read or write

Type Numeric, flag or text

MsgNum 0 to 63, used internally by the 1757-ABRIO module

Len Tag length, units are bytes for flag and text tags, floats for numeric tags

Req count Number of updates this tag has been accessed (read or written)

Avg Req Time Average update time for this tag, in ms. This is the average of the previous 64 updates.

Min Req Time Minimum request time for this tag, in ms

Max Req Time Maximum update time for this tag, in ms

Time out The message time-out, in ms

Status Active or Inactive


Monitoring the 1757-ABRIO Module Chapter 7

If you attempt to monitor a tag that has not been downloaded to the 1757-ABRIO module, AbRioCfg software displays a message that indicates there is a configuration mismatch between the configuration in AbRioCfg software and the configuration in the 1757-ABRIO module.

Monitoring the Status of a Block Transfer

To monitor the current status of a block transfer, complete the following steps.

1. Expand the chassis where the block transfer module you want to monitor is located.

2. Select the module you want to monitor.

3. Right-click the module to highlight and select Monitor BT from the menu.

The block transfer monitor displays the raw data for the block transfer and some diagnostic information. For input modules there is both a block transfer read and a block transfer write. The write consists of configuration data.

The raw data can be displayed as hexadecimal, signed, or unsigned integer. The default for block transfer data is hexadecimal.

Refer to the following table for diagnostic information on block transfer reads.

TIP Use the same procedure to monitor digital and text data.

Block Transfer Read Diagnostics

Counter Description

State Active/Inactive

Type Module type

BTR Len Block transfer read length

Req Update Time Requested update time in the module configuration, in ms

Avg Update Time Average update time for this block transfer read, in ms. This is the average of the previous 8 updates.

Min Update Time Minimum update time for this block transfer read, in ms

Max Update Time Maximum update time for this block transfer read, in ms

Update Count Running count of updates for this block transfer read



Refer to the following table for block transfer write diagnostics.

Monitoring the Scanner Log The scanner log displays messages from the 1757-ABRIO firmware, showing its normal operation and error messages. It may be useful in tracking down errors and for Technical Support.

To monitor the scanner log, select Tools>Monitor Scanner Log.

To clear the scanner log, select Edit>ClearLog or click the Clear Log button.

To copy the contents of the log to the Windows clipboard for use in another application, select Edit>Copy or click Select All then the Copy button.

Ignored Req Running count of update requests ignored by the block transfer module.

Prot Errors Running count of protocol errors for this block transfer read.

If this counter is incrementing, the module isn't responding correctly. Possible causes are length mismatch, invalid reply.

Request Count Count of the number of times on successive scans this block transfer was requested. If this is consistently a high number, increase the requested update time - the module cannot respond quickly enough at the current requested time. The counter applies to both the BTR and BTW for this module.

Block Transfer Write Diagnostic Data

Counter Description

CFG len Length of the configuration data for this module.

BTW data len data length

Req Update Time Requested update time in module configuration, in ms.

Avg Update Time Average update time for this block transfer write, in ms. This is the average of the previous 8 updates.

Min Update Time Minimum update time for this block transfer write, in ms.

Max Update Time Maximum update time for this block transfer write, in ms.

Update Count Running count of updates for this block transfer write.

Ignored Req Running count of update requests ignored by the destination module for this block transfer write.

Prot Errs Running count of protocol errors for this block transfer write.

Block Transfer Read Diagnostics

Counter Description


Monitoring the 1757-ABRIO Module Chapter 7

Monitoring Diagnostic Counters

The 1757-ABRIO module maintains diagnostic counters that indicate the state of communication on the entire RIO network, as well as counters related to each chassis. It also maintains an active rack list.

To monitor the diagnostic counters, select Tools>Monitor Diagnostic Counters or click the Start the Diagnostics Counters Monitor button.

Active Rack List

The active rack list shows where the racks are located. If the bit is set there is a rack at that rack number and starting I/O group. It does not show the rack size.

The rows represent starting I/O groups. The columns represent the rack numbers.

Global Diagnostic Counters

The global diagnostic counters consist of the following.

Global Diagnostic Counters

Counter Description

Tx This counter increments each time the 1757-ABRIO module transmits a packet.

RxGood This counter increments when the 1757-ABRIO module receives a good packet.

RxTout This counter increments when the 1757-ABRIO module sends a packet but does not receive a reply.

RxBadCRC This counter increments when the 1757-ABRIO module receives a packet with a bad CRC. Check cabling and termination on the RIO network.

RxNoise This counter increments when the 1757-ABRIO module hears a carrier without receiving a packet. Check cabling and termination on the RIO network.

RxAbort This counter increments when the 1757-ABRIO module receives an opening flag, then the packet ends without a closing flag.

PrtclErr This counter increments when the 1757-ABRIO module receives a packet that makes no sense in terms of the protocol.

UpdAvg Average update time for all configured racks. This is the average of the previous 64 updates.

UpdMin Minimum update time for all configured racks.

UpdMax Maximum update time for all configured racks.



The rack diagnostic counters consist of the following counters for each partial rack.

Fatal Errors Fatal errors occur when the firmware on the module encounters an unexpected condition. The module stops scanning, turns all three status indicators red, displays the fatal error number on the 4-character display, and stores a fatal error log that indicates the cause of the fatal error.

To clear the fatal error and capture the fatal error log:

1. Cycle power to the module.

The 4-character display should show “FatalErrorCapture required”.

2. Start AbRioCfg software.

3. Select Tools>Fatal Error Capture.

4. Store the fatal error log to a file.

This also clears the fatal error on the module.

5. Contact Rockwell Automation Technical Support and provide them with the fatal error log, which will help diagnose the cause of the problem.

Clearing fatal errors also clears the configuration on the module. After you clear the fatal error, download the configuration to the module using AbRioCfg software.

Rack Diagnostic Counters

Counter Description

Rx This counter increments when the 1757-ABRIO module receives a packet from this rack.

Crc This counter increments when the 1757-ABRIO module receives a packet with a bad CRC from this rack.

Tout This counter increments when the 1757-ABRIO module sends a packet to this rack and does not receive a reply within the time-out period.

Prtcl This counter increments when the 1757-ABRIO module receives a packet from this rack that does not make sense in terms of the protocol.


Chapter 8

Supported 1771 Modules


lists the supported 1771 modules.

describes module configuration, I/O Data, and diagnostic data.

Module Description The 1757-ABRIO module supports all digital 1771 modules and the following 1771 block transfer modules. For information on how to communicate with other block transfer I/O modules, see Creating Generic Modules in AbRioCfg Software on page 37.

Refer to the corresponding pages in this chapter for information about configuring these modules with the 1757-ABRIO module.

The AbRioCfg software handles the details of module configuration using the parameters you supply. For applicable modules, the 1757-ABRIO module scales the raw data to floating point values using optimal data resolution on the I/O module.

Supported modules

Module Description Page

1771-IFE Analog input module 84

1771-OFE Analog output module 89

1771-IR RTD input module 92

1771-IXE Thermocouple/millivolt module 95

1771-IL Analog input module 98

1771-NOC High resolution current output module 101

1771-NIV High resolution voltage input module 107

1771-NOV High resolution voltage output module 104

1771-NR RTD input module 110


Chapter 8 Supported 1771 Modules

Refer to the following publications for information on installing and using the supported modules.

1771-IFE Module The 1771-IFE module is a 12-bit analog input module that can be configured as 16 single-ended inputs or 8 differential inputs. Each channel can be configured as one of the following.

Select between current or voltage by using jumpers on the module. Select the range when you configure the 1771-IFE module in AbRioCfg software.

I/O Module Documentation

Module Installation Instructions User Manual

1771-ASB NA 1771-UM001

1771-IFE 1771-5.45 1771-6.5.901771-6.5.115

1771-OFE 1771-IN044 1771-6.5.30

1771-IR 1771-5.63 1771-6.5.76

1771-IXE 1771-5.64 1771-6.5.130

1771-IL 1771-5.62 1771-6.5.91

1771-NOC NA 1771-UM127

1771-NIV NA 1771-UM127

1771-NOV NA 1771-UM127

1771-NR NA 1771-UM127

1770-HT1 NA 1770-6.5.19

IFE Channel Configurations

1 to 5 VDC 4 to 20 mA


-5 to 5 VDC -20 to 20 mA

-10 to 10 VDC


http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1771-um001_-en-p.pdf

















Supported 1771 Modules Chapter 8

Module Configuration

Configuring the 1771-IFE module consists of setting the following:

single-ended or differential operation

range and scaling for each channel

digital filter and time constant

real time sampling and time constant

module update time

When you add a 1771-IFE module to a rack, the 1771-IFE Module dialog box opens.



To configure the 1771-IFE module, complete the following steps.

1. Set the Input Type to single-ended or differential operation.

2. For each channel select the voltage or current range and enter the scaling values.

The low scaling value corresponds to the minimum input voltage or current; the high scaling value corresponds to the maximum voltage or current.

For example, if the scaling values are 10.0 and 22.5 and the range is configured for 0 to 5V dc, an input of 0V dc produces a scaled input value of 10.0 and an input of 5V dc produces a scaled input of 22.5. The range of scaling values is -3.4e38 to 3.4e38.

3. If desired, enable digital filtering and set the digital filtering time constant.

If digital filtering is enabled, it applies to all channels. The digital filtering time constant can range from 0.01 to .99 seconds.

4. If desired, enable real-time sampling.

If real-time sampling is enabled, the sampling rate is set for the data and overrides the Update Time. The real-time sampling period can range from 0.1 to 3.1 seconds.

5. Type the Update Time.

The Update Time is the rate at which the block transfer read, which reads the data from the 1771-IFE module, executes. The range of values is 1 to 16382 ms. This sets the requested update rate, the actual rate depends on the baud rate, the number of racks on the RIO network and whether block transfers are running to other modules in the same rack.

6. Click OK to accept the configuration.

If you edit an existing 1771-IFE module and change the module between single-ended and differential, any existing mappings for the module will be deleted.



I/O Data

The 1771-IFE module returns the 8 or 16 words of floating point data to the host controller, depending on whether the module is configured for single-ended or differential operation.

Map this data to a numeric read tag.

Diagnostic Data

The 1771-IFE module has 40-bits of diagnostic data that can be mapped to a flag read tag.

IFE I/O Data

Numeric Offset Description

0 Channel 1 data

1 Channel 2 data

2 Channel 3 data

3 Channel 4 data

4 Channel 5 data

5 Channel 6 data

6 Channel 7 data

7 Channel 8 data

8 Channel 9 data (if applicable)








IFE Diagnostic Data

Bit Description

0 Module good communication

8 Channel 1 underrange






The Good Communication bit is set when the 1757-ABRIO module is successfully communicating with the 1771-IFE module, and is 0 otherwise.

The underrange and overrange bits are set when the raw input for a channel is outside the configured voltage or current range.













24 Channel 1 overrange
















IFE Diagnostic Data

Bit Description



1771-OFE Module The 1771-OFE module is a four-channel analog output module. The module is available in three different types.

The 1771-OFE1 module has jumper-selectable voltage ranges.

The 1771-OFE2 module is a 4 to 20 mA current module.

The 1771-OFE3 module is a 0 to 50 mA current module.

The 1771-OFE1 module supports ranges of 1 to 5V dc, 0 to 10V dc and -10 to 10V dc.


When you add a 1771-OFE module to a rack, the 1771-OFE Module dialog box opens.

To configure a 1771-OFE module, complete the following steps

1. Select the Module Type, either OFE1, OFE2 or OFE3.



2. For each channel select the range for each channel and enter the scaling values.

The low scaling value corresponds to the minimum output voltage or current; the high scaling value corresponds to the maximum output voltage or current.

3. Set the LAST STATE jumper setting to match the jumpers on the 1771-OFE module.

The setting can be Last, Min, Mid, or Max. This value determines how the 1757-ABRIO module responds to a loss of communication with the host controller.

4. Set the Update Time.

The Update Time is the rate at which the block transfer write, which writes data to the 1771-OFE module, occurs. The range of values is from 1 to 16382 ms. This sets the requested update rate; the actual rate depends on the baud rate, the number of racks on the RIO network and whether block transfers are running to other modules in the same rack.

5. Click OK to accept the module configuration.

I/O Data

4 words of floating point data are written to the 1771-OFE module.

You map this data to a numeric write tag.

EXAMPLE If the scaling values are 10.0 and 22.5 and the range is configured for 0 to 5V dc, a value of 10.0 produces an output of 0V dc and a value of 22.5 produces an output of 5V dc. The range of scaling values is -3.4e38 to 3.4e38.

Values received from a controller that are outside the scaled range are clamped to the scaled range value.

1771-OFE I/O Data

Data Word Description

0 Channel 1 data

1 Channel 2 data

2 Channel 3 data

3 Channel 4 data



Diagnostic Data

The 1771-OFE module has 8 bits of diagnostic data that can be mapped to a flag read tag.

The good communication bit is set if the 1757-ABRIO module is successfully communicating with the 1771-OFE module.

The data invalid bits are set if the value written to the channel is outside the range of the scaling values entered in the configuration dialog.

OFE Diagnostic Data

Bit Description

0 OFE good communication bit

1 reserved

2 reserved

3 reserved

4 Channel 1 data invalid bit






1771-IR Module The 1771-IR module is a 6-channel RTD module. Supported RTDs include 100-ohm platinum and 10-ohm copper. You can use any other type but the results are returned in ohms.


When you add a 1771-IR module to a rack, the 1771-IR Module dialog box displays.



To configure the 1771-IR module, complete the following steps.

1. Set the global RTD type to either 10-ohm copper or 100-ohm platinum. If the RTD you are using is neither of these two, you will override each channel to report the results in ohms.

2. If the RTD type is set to 10-ohm copper, enter the resistance value at 25 C.

3. Select the Units of measurement, either degrees Fahrenheit or Celsius, or Ohms.

4. If Ohms is the selected unit of measurement, select a resolution of 10 M per count or 30 M per count.

5. For each channel, set the bias, gain and offset.

Refer to the RTD Input Module User Manual, publication 1771-6.5.129, for more information.

6. If you want any of the channel results to be returned in Ohms, check the Channel Units Override box for that channel.

7. If you want to use real-time sampling (RTS), check the RTS Rate Enabled box and select the sampling rate from 0.1 to 3.1 seconds.

8. Type the module Update Time.

The Update Rate is the rate at which the block transfer read, which reads the data from the 1771-IR module, occurs. The range of values is 1 to 16382 ms. This sets the requested update rate; the actual rate depends on the baud rate, the number of racks on the RIO network and whether block transfers are running to other modules in the same rack.

9. Click OK to accept the values.




I/O Data

The 1771-IR module returns 6 words of floating point data to the host controller.

This data is mapped to a numeric read tag.

Diagnostic Data

The 1771-IR module returns 16 bits of diagnostic data to the host controller.

This data can be mapped to a flag read tag.

1771-IR Module I/O Data


0 Channel 1 data

1 Channel 2 data

2 Channel 3 data

3 Channel 4 data

4 Channel 5 data

5 Channel 6 data

1771-IR Module Diagnostic Data

Data Bit Description








7 reserved







14 reserved

15 reserved



1771-IXE Module The 1771-IXE module is an 8-channel thermocouple input module. The channels are configured in groups of four. The module supports types E, J, K, T, R and S thermocouples.

The module can also be used as a millivolt input module. The range is from -100 to 100 mV.


When you add a 1771-IXE module to a rack, the 1771-IXE Module dialog box displays.

To configure the 1771-IXE module, complete the following steps.

1. Select the thermocouple type for each of the two groups of channels, either one of the supported thermocouple types or millivolts.

2. Set the units of measurement, either degrees Fahrenheit or Celsius.

If you have selected millivolts for the returned data, this entry is ignored.



3. Set the gain and offset for each channel.

See the Thermocouple/Millivolt Input Module User Manual, publication 1771-6.5.130, for more information.

4. If desired, enable real-time sampling (RTS) and set the sampling rate, from 0.1 to 3.1 seconds.

This becomes the effective data update rate and may override the update rate if the update rate is smaller.

5. Set the Update Time for the module’s block transfer.

The range is 1 to 16382 milliseconds. This sets the requested update rate; the actual rate depends on the baud rate, the number of racks on the RIO network and whether block transfers are running to other modules in the same rack.

I/O Data

The 1771-IXE module returns 9 words of floating point data.

This data can be mapped to a numeric read tag.

1771-IXE Module I/O Data


0 Channel 1 data

1 Channel 2 data

2 Channel 3 data

3 Channel 4 data

4 Channel 5 data

5 Channel 6 data

6 Channel 7 data

7 Channel 8 data

8 Cold junction temperature




Diagnostic Data

The 1771-IXE module returns 24 bits of diagnostic data.


1771-IXE Module Diagnostic Data

Bit Description


1 Out of range

2 RTS time-out

3 reserved

4 Low cold junction temperature

5 High cold junction temperature

6 reserved

7 Calibration EEPROM failed



















1771-IL Module The 1771-IL module is an 8-channel voltage or current input module. Select voltage or current for each channel using jumpers on the module.

The module supports the following ranges:


When you add a 1771-IL module to a rack, the 1771-IL Module dialog box displays.

1771-IL Module Ranges

Voltage Current



-5 to 5 VDC -20 to 20 mA

-10 to 10 VDC



To configure the 1771-IL module, complete the following steps.

1. For each channel, select the range for each channel and enter the scaling values.

The low scaling value corresponds to the minimum input voltage or current; the high scaling value corresponds to the maximum voltage or current.

For example, if the scaling values are 10.0 and 22.5 and the range is configured for 0 to 5V dc, an input of 0V dc produces a scaled input value of 10.0 and an input of 5V dc produces a scaled input of 22.5. The range of scaling values is -3.4e38 to 3.4e38.

2. If desired, enable digital filtering and set the digital filtering time constant.

If digital filtering is enabled, it applies to all channels. The digital filtering time constant can range from 0.1 to .99 seconds.

3. If desired, enable real-time sampling and set the sampling rate, from 0.1 to 3.1 seconds.


4. Set the Update Time for the module’s data. The range is from 1 to 16382 milliseconds.

This sets the requested update rate; the actual rate depends on the baud rate, the number of racks on the RIO network and whether block transfers are running to other modules in the same rack.


I/O Data

The 1771-IL module returns 8 words of scaled floating point values.

1771-IL Module I/O Data


0 Channel 1 data

1 Channel 2 data

2 Channel 3 data

3 Channel 4 data




Diagnostic Data

The 1771-IL module returns 24 bits of diagnostic data.

4 Channel 5 data

5 Channel 6 data

6 Channel 7 data

7 Channel 8 data

1771-IL Module Diagnostic Data

Bit Description


1 Out of range

2 Invalid scaling (should never be set)

3 RTS time-out

4 Invalid filter

5 reserved

6 Hardware failure

7 reserved














1771-IL Module I/O Data





1771-NOC Module The 1771-NOC module is an 8-channel high resolution (16-bit) current output module. Each channel has a range of 0 to 25 mA.


When you add a 1771-NOC module to a rack, the 1771-NOC(V) dialog box opens.




1771-IL Module Diagnostic Data

Bit Description



To configure the 1771-NOC module, complete the following steps.

1. For each channel, enter the scaling values.

The low scaling value corresponds to the minimum output current; the high scaling value corresponds to the maximum output current.

For example, if the scaling values are 10.0 and 22.5, a value of 10.0 produces an output of 0 mA and a value of 22.5 produces an output of 25 mA. The range of scaling values is -3.4e38 to 3.4e38.

2. For each channel, set the Reset State.

This can be either Minimum, Maximum, Last State, or User Value. This is the value the channel output will be if the 1771-NOC module loses communication with the 1757-ABRIO module or the host controller stops updating the tag to which the 1771-NOC module’s data is mapped. If the Reset State is set to User Value, you must also enter a reset value.






I/O Data

The host application writes 8 words of floating point data to the 1771-NOC module.

1771-NOC Module I/O Data

Word Description

0 Channel 1 data

1 Channel 2 data

2 Channel 3 data



This data can be mapped to a numeric write tag.

Diagnostic Data

The 1771-NOC module returns 16 bits of diagnostic data.


3 Channel 4 data

4 Channel 5 data

5 Channel 6 data

6 Channel 6 data

7 Channel 7 data

1771-NOC Module Diagnostic Data

Bit Description


1 reserved

2 reserved

3 reserved

4 reserved

5 reserved

6 reserved

7 reserved

8 Channel 1 data invalid








1771-NOC Module I/O Data

Word Description



1771-NOV Module The 1771-NOV module is an 8-channel high resolution (16-bit) voltage output module. Each channel has a range of -10 to 10V dc.


When you add a 1771-NOV module to a rack, the 1771-NOC(V) dialog box opens.

To configure the 1771-NOV module, complete the following steps.


The low scaling value corresponds to the minimum output current; the high scaling value corresponds to the maximum output current.

For example, if the scaling values are 10.0 and 22.5, a value of 10.0 produces an output of -10V dc and a value of 22.5 produces an output of 10V dc. The range of scaling values is -3.4e38 to 3.4e38.



2. For each channel, set the Failure State.

This can be either Minimum, Maximum, Last State, or User value. This is the value the channel output will be if the 1771-NOV module loses communication with the 1757-ABRIO module or the host controller stops updating the tag to which the 1771-NOV module’s data is mapped.

3. If the Failure State for a channel is set to User Value, enter the User value.

The is the value the output will be set to on loss of communication.






I/O Data

The host application writes 8 words of floating point data to the 1771-NOV module.

This data can be mapped to a numeric write tag.

1771-NOV Module I/O Data

Word Description

0 Channel 1 data

1 Channel 2 data

2 Channel 3 data

3 Channel 4 data

4 Channel 5 data

5 Channel 6 data

6 Channel 6 data

7 Channel 7 data



Diagnostic Data

The 1771-NOV module returns 16 bits of diagnostic data.


1771-NOV Module Diagnostic Data

Bit Description


1 reserved

2 reserved

3 reserved

4 reserved

5 reserved

6 reserved

7 reserved











1771-NIV Module The 1771-NIV module is an 8-channel high resolution (16-bit) analog voltage input module. Each channel has a range of -5 to 5V dc.


When you add a 1771-NIV module to a rack, the 1771-NIV Module dialog box opens.

To configure the 1771-NIV module, complete the following steps.


The low scaling value corresponds to the minimum input voltage; the high scaling value corresponds to the maximum input voltage. For example, if the scaling values are 10.0 and 22.5, an input voltage of -5V dc produces a value of 10.0 and an input voltage of 5V dc produces a value of 22.5. The range of scaling values is -3.4e38 to 3.4e38.



2. If desired, enable digital filtering on any channel by selecting a non-zero time constant.

The values range from 0.1 to 9.9 seconds. Set the value to N/A to disable digital filtering.



4. Set the Update Time for the module’s data.



I/O Data

The 1771-NIV module returns 8 words of floating point data to the host controller.


1771-NIV Module I/O Data

Word Description

0 Channel 1 data

1 Channel 2 data

2 Channel 3 data

3 Channel 4 data

4 Channel 5 data

5 Channel 6 data

6 Channel 7 data

7 Channel 8 data



Diagnostic Data

The 1771-NIV module returns 40 bits of diagnostic data to the host controller.

1771-NIV Module Diagnostic Data

Bit Description


1 reserved

2 reserved

3 reserved

4 reserved

5 reserved

6 reserved

7 reserved

8 Channel 1 bad calibration








16 Bad program

17 Module fault

18 Program verify 0

19 Program verify 1

20 I/O reset

21 RTS time-out

22 Mod alarm

23 Bad channel data

24 Channel 1 data Underrange











1771-NR Module The 1771-NR module is an 8-channel RTD input module. It supports the following types of RTDs:

100 ohm platinum US standard

100 ohm platinum European standard

10 ohm copper

120 ohm nickel

ohms mode

The module:

reports the temperature in degrees Fahrenheit or Celsius.

supports digital filtering on any channel, with a time constant from 0.1 to 9.9 seconds.

32 Channel 1 data Overrange








1771-NIV Module Diagnostic Data

Bit Description




When you add a 1771-NR module to a rack, the 1771-NR Module dialog box opens.



To configure a 1771-NR module, complete the following steps.

1. Set the RTD type for each channel.

2. For any channels that are set to 10-ohms copper, set the offset at 25 C.

3. Set the units of measurement for the temperature, either degrees Fahrenheit or Celsius. For channels that are configured for ohms, this will be ignored.

4. If desired, enable digital filtering by setting the digital filter time constant to a non-zero value, from 0.1 to 10 seconds. To disable digital filtering, set the time constant to N/A.

5. If desired, enable real-time sampling and set the sampling rate, from 0.1 to 10.0 seconds. This becomes the effective data update rate and may override the update rate if the update rate is smaller.

6. Set the Update Time for the module’s block transfer. The range is 1 to 16382 milliseconds. This sets the requested update rate; the actual rate depends on the baud rate, the number of racks on the RIO network and whether block transfers are running to other modules in the same rack.




I/O Data

The 1771-NR module returns 8 words of floating point data to the host controller.


Diagnostic Data

The 1771-NR module returns 40 bits of diagnostic data.

1771-NR Module I/O Data


0 Channel 1 data

1 Channel 2 data

2 Channel 3 data

3 Channel 4 data

4 Channel 5 data

5 Channel 6 data

6 Channel 7 data

7 Channel 8 data

1771-NR Module Diagnostic Data

Bit Description


1 reserved

2 reserved

3 reserved

4 reserved

5 reserved

6 reserved

7 reserved












16 Bad program

17 Module fault

18 Program verify 0

19 Program verify 1

20 I/O reset

21 RTS time-out

22 Mod alarm

23 Bad channel data

















1771-NR Module Diagnostic Data

Bit Description


Chapter 9

Accessing HART Data

Introduction This chapter describes how to:

send HART commands using ControlLogix messaging.

access data through a 1770-HT1 module.

Sending HART Commands Using RSLogix 5000 Software MSG

The 1757-ABRIO module can send HART messages cyclically to devices on the HART network. Messages can be sent a single time using the AbRioCfg software. In addition, messages can be sent programmatically from RSLogix 5000 software using the MSG instruction.

1. Create a tag of type MESSAGE to act as a control tag for the MSG instruction.

2. Create a tag of type INT and array size large enough to hold the outgoing message.

3. Create another tag of type INT and array size large enough to hold the reply.

4. Create a MSG instruction in the RSLogix 5000 software ladder logic, along with any logic required to control the instruction execution.

5. Assign the MESSAGE tag you created as the Message Control.


Chapter 9 Accessing HART Data

6. Click on the … box in the MSG instruction to configure the message.

The MSG Configuration dialog box opens.

7. Set the Message Type to CIP Generic.

8. Set the Service Type to Custom.

9. Set the Service Code to 32 Hex.

10. Set the Class to c5 Hex.

11. Type the Instance in decimal.

The low 4 bits of the Instance are always 0. The upper 12 bits of the Instance are the rack number that has been assigned to the 1770-HT1 module. For example, if the rack number is 1, the Instance is 10 hex, or 16 decimal.

12. Set the Attribute to 0.

13. Set the Source Element to the tag that contains the outgoing HART message.

14. Set the Destination to the tag that will contain the reply to the HART message.


Accessing HART Data Chapter 9

HART Command Data

The contents of the message are similar to what is described in the manual for the 1770-HT1 module, with some differences. You fill in the HART command in the Source Element tag. When the MSG instruction executes, the reply is stored in the Destination tag.

The following table describes the contents of the reply. More detailed descriptions follow.

Reply Contents

Word High Byte Low Byte

0 Expected reply length, in words, 7 + returned data

Length to send, in words, 7 + required parameters

1 Channel - 1 Interface command, usually 10 hex

2 Interface parameter, set to 0 Interface control, set to 0

3 HART address Manufacturer ID (from HartCfg.exe)

HART delimiter = 82 hex for long frame address

4 Device ID, most significant byte Manufacturer device type, from HartCfg.exe

5 Device ID, least significant byte Device ID, middle byte

6 Byte count, number of bytes of parameters for the HART command

HART command

… parameter data

N 0 Check byte = 0



Word 0

The \Program Files\1757AbRio\HartCmd directory contains files that show the parameters required by each HART command and the data returned by that command. For example, for command 1, read primary variable, the file contains the following:

Cmd 01 Read Primary Variable from HART DeviceRspunit Primary Variable Unitfloat Primary Variable

If either length is an odd number of bytes, round up to calculate the number of words.

There are no parameters in the Cmd section, so in this case the low byte, length to send, contains 7 + 0 = 7.

The high byte, expected reply length, contains 7 + 3 = 10 (5 bytes, rounded up to 3 words)

The Source Length in the MSG configuration dialog should be set to match the length, in bytes, of the data to be sent. If the length is 8 words, set the Source Length to 16.

Possible Types and Byte Counts

Type Byte Count

unit 1

byte 1

3bytes 3

float 4

date 3

text n where n < 4 and n < 64. The byte count is n * 3/4

TIP If the command requires a float parameter, the value must be reversed, byte by byte, before sending the data on the HART network. Byte 0 becomes byte 3, byte 1 becomes byte 2, and so on. Similarly, if the reply data contains a float, the bytes must be reversed.



Word 1

The low byte contains 10 hex, send message to device. For more information, see the Smart Transmitter Interface Products (HART Protocol) User Manual, publication 1770-6.5.19.

The high byte contains the channel number for the destination device, minus 1. Channels are numbered from 1 to 16, so this byte contains 0 to F hex.

Word 2

The low byte contains the interface control, which should contain 0.

The high byte contains the interface parameter, which should also be set to 0. For more information, see the Smart Transmitter Interface Products (HART Protocol) User Manual, publication 1770-6.5.19.

Word 3

The low byte contains the HART delimiter, which should be set to 82 hex for a long frame address.

The high byte contains the manufacturer ID. This can be obtained from HartCfg.exe, version 1.01.0 or above. For example, the following screen capture shows a Rosemount 3044D. The manufacturer ID is 26 hex, the device type is 0d hex, and the device ID is 01b1ae hex.

Word 4

The low byte contains the manufacturer device type. In the previous screen capture, this is 0d hex

The high byte contains the device ID most significant byte. In the previous screen capture, this is 01 hex.

Word 5

The low byte contains the device ID middle byte. In the previous screen capture, this is b1 hex.

The high byte contains the device ID least significant byte. In the previous screen capture, this is ae hex.





Word 6

The low byte contains the HART command. For example, to send Read Primary Variable, enter 01 hex.

The high byte contains the number of bytes of parameters from the command file.

Words 7…

If there are any parameters to the HART command, the following words contain those parameters.

Word N

The last word contains 0. Both the upper and lower byte (check byte) should be 0.

Reply Data

When the MSG command executes, the reply to the command will be stored in the Destination tag.

The following table shows the contents of the reply.

Reply Contents

Word High Byte Low Byte

0 Channel - 1 Interface command, usually 10 hex

1 Interface status Interface error

2 HART address Manufacturer ID HART delimiter = 86 hex for ACK with long frame address

3 Device ID, most significant byte Manufacturer device type, from HartCfg.exe

4 Device ID, least significant byte Device ID, middle byte

5 Byte count, number of following bytes of response data until the check byte

HART command

6 HART response code, second byte, 0 for no error

HART response code, first byte, 0 for no error

… data data

data



Word 0

The low byte contains 10 hex, send message to device. For more information, see the Smart Transmitter Interface Products (HART Protocol) User Manual, publication 1770-6.5.19.

The high byte contains the channel number for the destination device, minus 1. Channels are numbered from 1 to 16, so this byte contains 0 to F hex.

Word 1

For more information, see the Smart Transmitter Interface Products (HART Protocol) User Manual, publication 1770-6.5.19.

Word 2

The low byte contains the HART delimiter, which should be 86 hex for an ACK with a long frame address.

The high byte contains the manufacturer ID.

Word 3

The low byte contains the manufacturer device type.

The high byte contains the device ID most significant byte.

Word 4

The low byte contains the device ID middle byte.

The high byte contains the device ID least significant byte.

Word 5

The low byte contains the HART command.

The high byte contains the number of bytes of response data to follow, including the two HART response code bytes.

Word 6

Word 6 contains the two HART response code bytes. For more information, see the Smart Transmitter Interface Products (HART Protocol) User Manual, publication 1770-6.5.19.

Words 7…

These contain any response data.






Example: HART Command 36

In this example, we are sending command 36, Set primary variable upper range value, to a Rosemount 3044C module. The manufacturer ID is 26 hex, the device type is 0d hex, and the device ID is 1b1ae hex. The device is attached to channel 1 of a 1770-HT8 module.

The command file for command 36 contains:

Cmd 36 Set Upper Range ValueRsp

There are no command parameters or response data, so the length to send and expected reply length are both 7. The source file therefore contains:

The reply contains:

There are 7 words of data, including 2 bytes of response data (the HART response codes). The first response byte is 0, indicating the command executed without error. The second response byte is 40 hex, indicating that the configuration changed.

Example Source File Contains

Word High byte, hex Low byte, hex Word data, hex

0 07 07 0707

1 00 10 0010

2 00 00 0000

3 26 82 2682

4 01 0D 010D

5 AE B1 AEB1

6 00 24 0024

7 00 00 0000

Example Source File Reply

Word High byte, hex Low byte, hex Word data, hex

0 00 10 0010

1 80 00 8000

2 26 86 2686

3 01 0D 010D

4 AE B1 AEB1

5 02 24 0224

6 40 00 4000



1770-HT1 Module The 1757-ABRIO module supports scanning HART devices connected to a 1770-HT1 module.

The 1770-HT1 module occupies one quarter rack on the RIO network.

The 1757-ABRIO module can execute HART commands cyclically to the various HART devices.

You can also use the 1757-ABRIO module to execute HART commands manually (one time only) to configure HART devices. This includes manually writing to the HART devices.

You can only execute commands cyclically.

Depending on the HART command, the returned data is either floating point (numeric read tag) or text (text read tag).

The command status is returned as a single byte of flag data. Since only one command is active to a specific device at one time, if you want to view the message status for a device, you need map it only once, even if there are multiple messages to the same device.

The 1757-ABRIO module is intended to be used with HART input devices. It is not suitable for use with output devices.

Rack Requirements

The 1770-HT1 module can be set for any rack number from 1 to 37 octal. The 1770-HT1 module must be configured at starting I/O group 0. No other device can use the same rack number.



Configuring the 1770-HT1 Module

To configure a 1770-HT1 module and create cyclic messages to HART devices, complete the following steps.

1. If you have not already done so, autoconfigure the RIO network.

2. Add the 1770-HT1 module to the appropriate rack. The 1770-HT1 module must be the only module in that rack.

At this point, the 1757-ABRIO module does not know how to complete the rest of the HART configuration until it has the configuration with the 1770-HT1 module included. You must download the configuration to the 1757-ABRIO module before the HART configuration program can run.

Immediately after you add the 1770-HT1 module, AbRioCfg software prompts you to download the configuration with the 1770-HT1 module to the 1757-ABRIO module.

3. Click OK to download.

After AbRioCfg software downloads the configuration, it starts the separate HART configuration program. The main AbRioCfg program is automatically minimized when the HART configuration is running. When you close the HART configuration program, the main configuration program is automatically restored.



Configuring the HART Network

The first step in configuring the HART network is to scan for HART devices.

1. Right-click Hart Config and select SearchHart, or select Actions>Search Hart.

The HART Search dialog box opens.

The purpose of this dialog box is to make the search for HART devices faster by including only channels that you know are occupied. (For the 1770-HT module, in the non-multiplex mode, Channels = HART devices connected to the 1770-HT8 module) If you have four HART devices connected to the 1770-HT8 module then check Channels 1, 2, 3, and 4.

2. Select those channels you want to search.

3. Use All and None to select or deselect blocks of channels.

If you don’t know which channels are being used, select them all. Set the maximum address (range 0 to 15) to search on each channel. If you have one HART device on each channel set Max Address to 1.



4. Click OK to start the search.

The HART Configuration program displays a progress bar as it searches the HART network devices. When the search is complete, expand the HART Config to display the devices found.

Send a Message or Add a Cyclic Command to a Device

To send a message to a device or add a cyclic command to a device, complete the following steps.

1. Select the HART device.

2. Right-click the device and select Send>Add Message.

A dialog box opens with available HART commands.



3. Select the command you want to execute and click Open.

The HART Command dialog box for that command opens.

a. If the Command has any required arguments, enter them in the Command Arguments area.

b. To execute a command just once, click Execute. For example, you could execute a command to confirm that the command works correctly, or to configure a device.

c. To add a cyclic command, enter the offset (Numeric or Text) where the data returned from the command will be stored.

d. To return the message status to a flag tag, enter the offset into the Flag Ofs field.

4. Click AddCyclic.

When you have finished adding cyclic commands, close the HART configuration program.

TIP The first time you configure a HART interface module, the dialog box that opens may contain the folder HART Command File. Choose this file to view all available commands



5. If you have not already done so, create tags to accept the data from the HART commands and map the 1770-HT1 module to those tags.

The 1770-HT1 module occupies an entire numeric read, flag-read or text-read tag.

6. After you select HART command 1, Read Primary Variable, from the command list, select an offset for the location where the data will be stored in the HART Data tags you have or will create.

7. Click Execute.

The Execution results are shown, to confirm that you are receiving the desired data.

8. To have the data read repeatedly and attached to the 1757-ABRIO tag, click Add Cyclic.

9. Save the configuration and download it to the 1757-ABRIO module.

TIP Do not add write commands as cyclic commands.



HART Command status

The HART command status byte contains the following bits.

When you enter a flag offset when you create a cyclic command, this is what gets returned at that offset.

Nothing is displayed if you monitor the block transfers to the 1770-HT1 module.

HART Command Status

Bit Meaning

0 Field device malfunction

1 Configuration changed

2 Cold start

3 More status available

4 Analog output current fixed

5 Analog output saturated

6 Non-primary variable out of limits

7 Primary variable out of limits


Appendix A

Specifications

Process Remote I/O (RIO) Communication Interface Module - 1757-ABRIO

Attribute Value

Module Location ProcessLogix or ControlLogix chassis

Backplane Current 675 mA @ +5.1V dc5 mA @ 24 V dc

Power dissipation, max 4 W

Isolation Voltage 30V, continuous, basic insulation type

Screw Terminal Torque 0.5...0.6 Nm (5...7 lb-in)

Wiring Category(1)

(1) Use this Conductor Category information for planning conductor routing. Refer to Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1.

2 - on communications ports

Wire Size 20 AWG, 0.519mm

Wire Type Belden 9463 Twinaxial

Environmental Specifications

Attribute Value

Temperature, operating

0…60 °C (32…140 °F)

IEC 60068-2-1 (Test Ad, Operating Cold),

IEC 60068-2-2 (Test Bd, Operating Dry Heat),

IEC 60068-2-14 (Test Nb, Operating Thermal Shock)

Temperature, nonoperating

–40…85 °C (–40…185 °F)

IEC 60068-2-1 (Test Ab, Un-packaged Nonoperating Cold),

IEC 60068-2-2 (Test Bb, Un-packaged Nonoperating Dry Heat),

IEC 60068-2-14 (Test Na, Un-packaged Nonoperating Thermal

Relative Humidity 5…95% noncondensing

IEC 60068-2-30 (Test Db, Un-packaged Nonoperating Damp Heat)

Shock, operating IEC60068-2-27 (Test Ea, Unpackaged shock), 30g

Shock, nonoperating IEC60068-2-27 (Test Ea, Unpackaged shock), 50g

Vibration IEC60068-2-6 (Test Fc, Operating): 2 g @ 10…500 Hz

Emissions CISPR 11: Group 1, Class A


Appendix A Specifications

ESD immunity IEC 61000-4-2:

6 kV contact discharges

8 kV air discharges

Radiated RF immunity

IEC 61000-4-3

10V/m with 1 kHz sine-wave 80%AM from 80 MHz to 2000 MHz

10V/m with 200 Hz 50% Pulse 100%AM at 900 Mhz

EFT/B immunity IEC 61000-4-4:

±2 kV at 5 kHz on communication ports

Surge Transient Immunity

IEC 61000-4-5:

±2 kV line-earth (CM) on communication ports

Conducted RF Immunity

IEC 61000-4-6:

10V rms with 1 kHz sine-wave 80%AM from 150 kHz to 80 MHz

Enclosure Type Rating

None (open-style)

North American temperature code

T4A

Certifications

Certification Value

Certifications

(when product is marked)(1)

c-UL-usUL Listed Industrial Control Equipment, certified for US and Canada. See UL File E219376.UL Listed for Class I, Division 2 Group A,B,C,D Hazardous Locations, certified for U.S. and Canada.See UL File E314476.

CEEuropean Union 2004/108/EC EMC Directive, compliant with:EN 61326; Meas./Control/Lab., Industrial RequirementsEN 61000-6-2; Industrial ImmunityEN 61000-6-4; Industrial EmissionsEN 61131-2; Programmable Controllers (Clause 8, Zone A & B)

(1) See the Product Certification link at http://ab.com for Declarations of Conformity, Certificates, and other certification details.

Environmental Specifications

Attribute Value


http://ab.com

Appendix B

Troubleshooting

Interpret the Status Indicators

The three status indicators on the module provide information about your module and the status of communication with a host processor and with the remote I/O network. The following tables outline the indicator condition and the corresponding status for each indicator.

RIO Status Indicator – Remote Devices Status

The RIO indicator displays the status of the remote I/O network connection.

SYS Status Indicator – ControlBus Status

The SYS indicator displays the status of communication with the processor.

Indicator Status

Green Successful communication with all configured racks.

Yellow Idle, no racks are configured.

Red One or more configured racks is not responding or a protocol error has occurred within the last second.

Indicator Status

Green The module has successfully processed a request from the ControlBus backplane within the last five seconds.

Yellow Idle, no requests received from the backplane in the last five seconds.

Red The module has returned an error to a request from the backplane within the last second.


Appendix A Troubleshooting

OK Status Indicator – Module Health

Status Display Power-up Messages

The alphanumeric display shows the following messages at power-up.

If the indicator on the 1757-ABRIO module does not cycle through these messages on powerup, refer to the Troubleshooting section of publication 1757-UM007C, the 1757-ABRIO User Manual.

Power Supply Indicator

Indicator Status

Green Indicates that module has passed all power-up diagnostics and is functioning normally.

Red Indicates that module startup diagnostics have failed or a major module fault such as watchdog time-out or jabber inhibit has occurred.

IMPORTANT If all three status indicators are solid red and the 4-character display shows the #xx, (where xx is the error number) this is where the fatal area occurs. Refer to publication 1757-UM007C, the 1757-ABRIO User Manual for information on clearing fatal errors. Be sure to make a note of the error code numbers to give Tech Support, if you need to call for help.

B#nn Stages in the start-up processes, nn is a hexadecimal number

Boot Next stage in power-up sequence

57ABRIO Ver x.xx.xx Module firmware version

POWER Indicator Power Supply Status Recommended Action

Off Not operating Turn power switch ON.

Check power wiring connections.

Check fuse.

On Operating None, normal operation.




Troubleshooting Appendix A

Interpret the Alphanumeric Display

The Process Remote I/O (RIO) Communication Interface Module displays alphanumeric messages that provide diagnostic information about your module. The warning messages display twice, then the normal display resumes. The following table summarizes the messages.

Alphanumeric Display Message Descriptions

Message Description

57ABRIO Version x.xx.xx The module’s firmware version, displayed at powerup. The three parts of the version number are the major revision, the minor revision and the build number.

Config The module is being configured from the configuration program.

Inactive The module is not receiving any messages that read or write tags. It is scanning discrete I/O in program mode. Block transfers are not updating.

Active The module is receiving messages that read or write tags. It is scanning discrete I/O in run mode. Block transfers are updating.

Forced Active The module has been put into active mode by the configuration program.

RIO Flash Config Invalid The configuration stored in Flash memory on the module is invalid due to the following possible reasons.

The module has never been configured.

The module firmware has been updated and the configuration format has changed.

A fatal error has been captured.

To clear the invalid state, download the I/O configuration.

Error: Heard Another RIO Master

Another master has been detected on the network because of the following possible reasons.

The module is connected to a network with another RIO master.

The module is connected to a Data Highway Plus network.

RIO Master Config Scan At startup, the module scans the RIO network to see what racks are connected.

Rack xx I/O Grp yy Size Mismatch

The rack size in the stored configuration on the module for the rack at rack number xx octal, starting I/O group yy, does not match the rack size on the network.

Rack xx I/O Grp yy Offline

The rack at rack number xx octal, starting I/O group yy, is not responding.

Firmware Update The firmware on the module is being updated.



Using AbRioCfg Software for Troubleshooting

AbRioCfg software can be used in the following ways to troubleshoot problems with the 1757-ABRIO module:

Monitor digital input and output data to determine if the raw data as seen by the module is correct.

Monitor block transfers to see if the raw data is correct and if the block transfer is updating.

Monitor tags to see if the tag is being updated by the host controller and to see the values of the data that the 1757-ABRIO module is sending to or receiving from the host controller.

Monitor the diagnostic counters to see if the active station list is correct, to see if the module is sending and receiving packets, and to see if any network errors are occurring.

View the Scanner Log. If a network error occurs, information will be logged to the Scanner Log that indicates the cause of the problem.



Troubleshooting Problems The following are some possible problems you may encounter and their possible causes.

Symptom Possible Problems Notes

Autoconfiguration fails or does not find racks

The 1757-ABRIO module must be in INACTIVE mode to autoconfigure

The baud rate is incorrect

Check the cabling (Line 1, shield, Line 2)

Check network termination

Data is not updating 1757-ABRIO module is not in ACTIVE or FORCED ACTIVE mode

Incorrect rack address used when creating the module

Modules are not mapped to the tags

Rack is offline

Update time is set too long

Digital outputs turned on at the same location as the block transfer

View the scanner log to see if it contains information about why the block transfer is failing.

Rack is offline or is not updating Rack is not included in the configuration

Problems with cabling and termination

Check the active rack list to see if the 1757-ABRIO module shows the rack.

View the Scanner Log to see if there are any messages that indicate the source of the problem.

Menu items are dimmed Click in the network tree (left pane) of the configuration program before you select an item.



Using RSLogix 5000 to Diagnose Problems

Right-click the module while online in RSLogix 5000 software to display the Module Properties dialog box. This may help in diagnosing some problems, especially connection errors.

General Tab

Connection Tab

The Inhibit Module checkbox breaks the exclusive ownership connection between the 1757-ABRIO module and the ControlLogix controller. If you would like to download to the 1757-ABRIO module without putting the controller in Program mode, check Inhibit Module. Once you are done updating the 1757-ABRIO module, uncheck Inhibit Module and your connection will be re-established.

Item Description

Type 1756-MODULE Generic 1756 Module

Vendor Allen-Bradley

Name Defined when you configured the module.

Description Defined when you configured the module.

Comm Format Matches what you defined when module was configured.

Slot Matches what you defined when module was configured.

Connection Parameter

Matches what you defined when module was configured.

If this box is checked Then

Major Fault on Controller if Connection Fails While in Run Mode

This causes the module to fault the controller if the connection between the ControlLogix controller and the module fails.



Module Info Tab

Backplane Tab

Item Description

Vendor Allen-Bradley

Product Type Communications Adapter

Product Code 107

Revision Matches the firmware revision level of the module.

Serial Number Matches the serial number on the module

Product Name 57ABRIO

Status Section contains information about the connection status, including:

Major fault

Minor fault

Internal state

Configured

Owned

Module Identity

Refresh Updates information on the screen

Item Description

ControlBus Status displays backplane faults

ControlBus Parameters The Multicast CRC error threshold is fixed at 8.

The Transmit Retry Limit defaults to 45 but can be edited.

Chassis The Chassis area contains information that relates to the chassis, not the module.

It contains the rack Revision, Serial Number, Size, and the 1757-ABRIO module slot number.

Error Counters These refer to communications across the backplane.

They should all be 0.

Status The Status at the bottom of the screen indicates the status of the connection to the module.



Using Control Builder Software to Diagnose Problems

All communication between the ProcessLogix controller and the 1757-ABRIO module is via exchange blocks. If these exchange blocks are producing errors or do not seem to be working properly, check these items:

Path from the ProcessLogix controller to 1757-ABRIO module is correct

1757-ABRIO tag name is correct

If you see error codes on your exchange blocks, in Knowledge Builder, refer to Knowledge Builder>R500>Troubleshooting and Maintenance Guide>Fault Codes>Exchange Block ERRCODE Fault Codes.

Troubleshooting 1757-ABRIO Module Communications

If the Data in the various Tag Storage files in your controller is not what you expect, try the following possible solutions.

Check that the 1757-ABRIO module is active. If it is not active, your controller is probably not in Run mode.

Confirm that the 1757-ABRIO tags referenced in your message commands or exchange blocks exactly match the tag names in the 1757-ABRIO module.

In the AbRioCfg software, right-click on the Tag Name, select Monitor Tag, and confirm that 1757-ABRIO module is seeing the correct data.

Both 1757-ABRIO tag name read and write data should match the data in your controller.

Still having a problem?

Try sending data to and reading data from an I/O Module.

1. Put the controller (ProcessLogix or ControlLogix) into program or inactive mode (or inhibit the ControlLogix controller in RSLogix 5000 software).

The 1757-ABRIO module goes inactive.

2. Put the 1757- ABRIO module into Forced Active Mode, select Actions>Forced Active Mode from the toolbar in AbRioCfg software.

3. Select Flag Write from the tabs in the bottom right window.



4. Select a flag write tag and right-click on the tag name.

5. Select Monitor Tag from the menu.

This should be a rack flag write tag pertaining to a rack that has a SIM Module. SIM modules simulate inputs and outputs and will indicate where data is being written to and read from.

6. Enter data in the Tag Monitor window and see how that data matches the indicator lights on the SIM module.

For observing Flag read data, flip the switches on the SIM module and see how that change affects a flag read tag for that rack

7. Put the controller in Run Mode or uncheck Inhibit Module.

8. Verify that the correct data is being written to the 1757-ABRIO module from the controller using the same tag monitor screen in AbRioCfg software.

9. Verify that data is being written correctly from the 1757-ABRIO module to the controller by observing flag read data within RSLogix 5000 software (ControlLogix controller) or Control Builder software (ProcessLogix controller).

10. Also, read SIM module switches from the controller.

If you are using message instructions in RSLogix 5000 software to read this flag data, remember to append the tag name with the [100] offset. See Unscheduled I/O Connections in ControlLogix on page 67 for more details.

IMPORTANT To write data, you have to enable writes, using either the menu item Edit/WriteEna or using the Toolbar button.


Appendix C

Operational Comparison Between the 1757-ABRIO Module and a PLC-5 System

Normal Operational Messages

The 1757-ABRIO module is designed to respond, as much as possible, like a PLC-5 system. In PLC-5 applications, all I/O modules are physically configured for safe state if the PLC-5 controller is in Program or Fault mode.

There is one important difference - the PLC-5 controller has well-defined, built-in modes of operation, either program or run. The 1757-ABRIO module has additional modes due to increased capabilities (see the table on page 144). The 1757-ABRIO module uses the concept of a tag to store data that is exchanged between the 1757-ABRIO module and controllers. A tag is a user configured data array that is composed of data read from or written to I/O modules.

As long as any tag is being refreshed from a Read/Write generated by a controller or from a DDE or OPC server, the 1757-ABRIO module scans remote I/O in ACTIVE (Run) mode. In ACTIVE mode all block transfers run and digital inputs and outputs update.

If all tags have timed out (have not been refreshed within the configured refresh time), the 1757-ABRIO module indicates INACTIVE mode. Inputs continue to be updated. Output modules are placed in safe state via Program mode.

In AbRioCfg software, mode block transfers are held which causes the analog modules to be set to configured safe state (usually Last, Min, Max or Safe value). Digital outputs also do what they have been configured at the rack to do - hold last state or shut-off.

While the PLC-5 controller immediately changes from program to run or from run to program modes based on user input, the 1757-ABRIO module has the ability to change between inactive to active when communication with a controller is established. However, the change from active to inactive occurs only after the longest time-out period for any tag after the last tag has been updated by the host controller.


Appendix B Operational Comparison Between the 1757-ABRIO Module and a PLC-5 System

.

Equivalent Modes

1757-ABRIO Module

PLC-5 Controller

Description

ACTIVE Run Data is transferred and diagnostics are enabled.

INACTIVE Program Inputs are updated and outputs are treated the same as PLC-5 Program mode.

CONFIG Program Inputs are held and outputs are treated the same as PLC-5 Program mode.

FORCED ACTIVE Inputs are updated and outputs are set by the user through AbRioCfg software.

TIP Any data “read tag” refers to data being read by a controller.

Any data “write tag” refers to data being written by a controller.

Normal Operational Comparison Between a PLC-5 System and a 1757-ABRIO Module

1757-ABRIO ACTIVE orPLC-5 RUN Modes

From the PLC-5 Perspective From the 1757-ABRIO Perspective

Digital inputs Digital output data updates. Data update in the PLC data table is asynchronous to the I/O update, based on the PLC I/O scan.

Digital input data updates (in the 1757-ABRIO module) based on the scan list. Data updates by the controller asynchronously when the tag is read by the controller.

Digital outputs Digital input data updates. Data update in the PLC data table is asynchronous to the I/O update, based on the PLC I/O scan.

Digital output data updates (in the 1757-ABRIO module) based on the scan list. Data updates by the controller asynchronously when the tag is read by the controller.

Block transfer read data Updates when the block transfer instruction executes. Block transfers to the local rack are faster than block transfers to the 1757-ABRIO module.

Updates the 1757-ABRIO module tag when the block transfer cycle executes based on the scan list and user configured Block Transfer Update time. Updates in the controller when the tag data is exchanged.

Block transfer write data Updates on the module when the block transfer instruction executes. Block transfers to the local rack are faster than block transfers to 1757-ABRIO module.

Updates on the 1757-ABRIO module when the control process exchanges data. Updates on the module when the block transfer cycle executes.

1757-ABRIO INACTIVE and or PLC-5 Program Mode

From the PLC-5 Perspective From the 1757-ABRIO Perspective

Digital inputs Digital input data updates. Data update in the PLC data table is asynchronous to the I/O update.

Digital input data updates in the 1757-ABRIO module. Data does not update in the host controller since tags are not being read.

Digital outputs Digital output data does not update. Digital output data does not update.

Block transfer read data Block transfers do not execute. Block transfers do not execute.

Block transfer write data Block transfers do not execute. Block transfers do not execute.


Operational Comparison Between the 1757-ABRIO Module and a PLC-5 System Appendix B

Exception Handling Messages

The 1757-ABRIO module provides a good communication flag for each digital partial rack. It also maintains a good communication flag for each configured block transfer module. These bits are set when the rack or block transfer module is updating without errors, and are cleared when an error occurs. These health bits are included in the “Tag” along with the channel states.

In addition, the 1757-ABRIO module has underrange and overrange bits for data on each channel for analog input modules. These are treated as communication errors per channel setting outputs to configured state (min, max, mid, last value) based on module hardware jumpers.

These bits are included when you map a digital rack or block transfer module to a flag read tag. Exceptions cause messages to be logged in the scanner log.

Exception Conditions Comparison Between a PLC-5 System and a 1757-ABRIO Module

Exception Condition Message From 1757-ABRIO Perspective From the PLC-5 Perspective

No RIO network communication Good communication bits for all racks and all block transfers are cleared and set to 0.

Digital Data does not update

Digital inputs hold their last state

Digital outputs go to the state set on the rack last state switch in the rack

Block transfers do not update

Data from block transfer read modules is set to Not a Number (NaN)

Block transfer write data goes to the state configured on the I/O module (module dependent)

Tags with digital or block transfer data mapped to the rack continue to update

Front panel displays a message for the last rack in error, twice

RIO network status indicator is red

Status table bits for all racks are cleared and set to 0.

Digital data does not update


Digital outputs go to the state set on the rack last state switch

Block transfers do not update

Block transfer read data holds its last state

Block transfer write data goes to the state configured on the I/O module

Error bits are set for all enabled block transfer instructions



Rack Missing Good communication bit for the rack is cleared

Good communication bits for block transfer modules in the rack are cleared



Digital outputs go to the state set on the rack last state switch in the rack

Block transfers to the rack do not update

Data from block transfer read modules goes to Not a Number (NaN)


Tags with digital or block transfer data mapped to the rack continue to update

Front panel displays the missing rack for 5 seconds

RIO network status indicator is red

Status bit for the rack is cleared

Block transfers to modules in the rack error



Digital outputs go to the state set on the rack last state switch

Block transfer read data holds its last state


Block transfer module missing or not responding

Good communication bit for the block transfer module is never set

Block transfer doesn't update, BT ignored request diagnostic counter slowly increments

Error with module location is entered in the scanner log each time the BT is retried

Tags to which the module is mapped update

Initial configuration block transfer write to the module fails, block transfer error bit is set

Invalid configuration data to block transfer module

Can not happen, configuration program should validate configuration

Initial block transfer write to the module fails, block transfer error bit is set for that block transfer

Block transfer read to configured input module fails

Good communication flag for module is cleared

Input data is set to Not a Number(1)

Block transfer read error bit is set

Input data holds last state

Block transfer write to configured output module fails

Good communication flag for module is cleared

Output data is set to a value that depends on the module configuration or jumpers

Block transfer write error bit is set

Output data is set to a value that depends on the module configuration or jumpers

Flag write tag to digital rack times out

1757-ABRIO module sets outputs mapped to the tag to the state set on the backplane switches (last state or 0)

N/A

Flag read tag times out Inputs continue to update in the 1757-ABRIO module. N/A

Numeric read tag times out Data continues to update in the 1757-ABRIO module but nothing is reading them.

N/A

Numeric write tag times out 1757-ABRIO module sets block transfer write data mapped to the tag to the state set by the user in the module configuration. Possible choices (last state, etc.) depend on the module.

N/A

Analog output data out of configured range

Data invalid bit for the channel is set

Output for the channel clamped to min/max value

See specific output module documentation for appropriate response.




Operational Comparison Between the 1757-ABRIO Module and a PLC-5 System Appendix B

Analog input voltage or current out of valid over/under range for channel configuration

Underrange or overrange bit for the channel is set

Input data for the channel in the tag is set to NaN

Set status bit.

Write NaN (Not a Number) to one element of a numeric write tag from a ProcessLogix controller

Value that has NaN sets the output to the configured fault value

The block transfer continues to update

The remaining values in the tag continue to be written correctly

Overrange bit for the channel is set

N/A

Write to or read from tag that doesn't exist

Message gets an error status

DDE or OPC server item has bad quality

N/A

Write beyond end of tag Message gets an error indicating the length or offset is incorrect

DDE or OPC server item has bad quality

N/A

Write to or read from a tag that has one (faulted) module mapped to it

Read or write message succeeds

Data from faulted input module is set to NaN

State of outputs on faulted output module depend on the module configuration

N/A

Write to or read from a tag that has multiple modules mapped to it, only one module faulted

Read or write message succeeds

Data for non-faulted modules continues to update correctly.

N/A

Read from or write to tag that has nothing mapped to it

Read or write message fails, empty tags are not downloaded to the 1757-ABRIO module.

N/A

OPC/DDE reads or writes tags but control program has died or gone away

1757-ABRIO module continues in ACTIVE mode

The output values are the last values written by the control program, or the values written by DDE/OPC

N/A

(1) In a ProcessLogix file, seen as NaN.In an RSLogix 5000 file, seen as 1.#QNAN (the controller has a function that detects this)In the ABRIO Monitor, seen as 1.#QNB.




Appendix D

Tag Descriptions for Scheduled Data in RSLogix 5000 Software

When you create an exclusive owner or input only connection, several tags are automatically created for the each 1757-ABRIO module. For example, if your 1757-ABRIO module is located in the supervisory rack, slot 3, then the configuration tag associated with it would be Local:3:C.

Configuration Tag

The configuration tag gets created when you configure the 1757-ABRIO module as a 1756-MODULE, but the contents of the configuration tag are not used by the 1757-ABRIO module.

I and O Tags

The I and O tags are associated with the digital I/O data. The input tag also contains rack global status. The following tables show how the tag contents correspond to the racks.

Generated Tag Extensions

Tag Extension

Description

C Configuration tag, created but not used

I Digital input data tag

O Digital output data tag

S Status tag

Input Tags

Address Description

Local:<slot>:I.Data[0] Rack global status, 0 if all configured racks are communicating with no errors, FFFF hex otherwise.

Local:<slot>:I.Data[1] Rack global status, 0 if all configured racks are communicating with no errors, FFFF hex otherwise.

Local:<slot>:I.Data[2] Rack 1, I/O group 0 inputs


...



Appendix C Tag Descriptions for Scheduled Data in RSLogix 5000 Software

The offset for the input data for any rack and the I/O group can be found from:

offset = 8 * (rack - 1) + I/O group + 2

where the rack number is in decimal

The offset for the output data for any rack and the I/O group can be found from:

offset = 8 * (rack - 1) + I/O group

where the rack number is in decimal


...


...

Local:<slot>:I.Data[242] Rack 37 octal, I/O group 0 inputs

...

Local:<slot>:I.Data[249] Rack 37 octal, I/O group 7 inputs

Output Tags

Address Description

Local:<slot>:O.Data[0] Rack 1, I/O group 0 outputs


...



...


...

Local:<slot>:O.Data[240] Rack 37 octal, I/O group 0 outputs

...

Local:<slot>:O.Data[247] Rack 37 octal, I/O group 7 outputs

Input Tags

Address Description


Tag Descriptions for Scheduled Data in RSLogix 5000 Software Appendix C

Status Tag

The status tag contains a global status as well as individual status flags for all possible partial racks. The status bits are set if the rack with the corresponding rack number and starting I/O group is configured in the 1757-ABRIO module and is not communicating, and are 0 otherwise. If any configured rack is not communicating, the global status is set.

The following table shows the contents of the Status Tag.

Status Tag

Address Description

Local:<slot>:S.Data[0] Rack global status, 0 if all configured racks are communicating with no errors, FFFF hex otherwise.

Local:<slot>:S.Data[1] Rack global status, 0 if all configured racks are communicating with no errors, FFFF hex otherwise.

Local:<slot>:S.Data[2].0 Not used




Local:<slot>:S.Data[2].4 Rack 1, I/O group 0 error






























Local:<slot>:S.Data[4].0 Rack 10 octal, I/O group 0 error




























Status Tag

Address Description


Tag Descriptions for Scheduled Data in RSLogix 5000 Software Appendix C





































Status Tag

Address Description



































Status Tag

Address Description


How Are We Doing?Your comments on our technical publications will help us serve you better in the future.Thank you for taking the time to provide us feedback.

You can complete this form and mail (or fax) it back to us or email us at
[email protected].
Please complete the sections below. Where applicable, rank the feature (1=needs improvement, 2=satisfactory, and 3=outstanding).

Pub. Title/Type Process Remote I/O (RIO) Communication Interface Module

Cat. No. 1757-ABRIO Pub. No. 1757-UM007D-EN-P Pub. Date December 2008 Part No. N/A

Overall Usefulness 1 2 3 How can we make this publication more useful for you?

Completeness(all necessary information

is provided)

1 2 3 Can we add more information to help you?

procedure/step illustration feature

example guideline other

explanation definition

Technical Accuracy(all provided information

is correct)

1 2 3 Can we be more accurate?

text illustration

Clarity(all provided information is

easy to understand)

1 2 3 How can we make things clearer?

Other Comments You can add additional comments on the back of this form.

Your Name

Your Title/Function Would you like us to contact you regarding your comments?

Location/Phone ___No, there is no need to contact me

___Yes, please call me

___Yes, please email me at _______________________

___Yes, please contact me via _____________________

Return this form to: Rockwell Automation Technical Communications, 1 Allen-Bradley Dr., Mayfield Hts., OH 44124-9705

Fax: 440-646-3525 Email: [email protected]

Publication CIG-CO521D-EN-P- July 2007

Other Comments

PLEASE FOLD HERE

NO POSTAGE NECESSARY IF MAILED

IN THE UNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH

POSTAGE WILL BE PAID BY THE ADDRESSEE

1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705

PLEASE FASTEN HERE (DO NOT STAPLE)

PLEA

SE R

EMOV

E

Rockwell Automation Support

Rockwell Automation provides technical information on the Web to assist you in using its products. At http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.

For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer TechConnect support programs. For more information, contact your local distributor or Rockwell Automation representative, or visit http://support.rockwellautomation.com.

Installation Assistance

If you experience a problem within the first 24 hours of installation, please review the information that's contained in this manual. You can also contact a special Customer Support number for initial help in getting your product up and running.

New Product Satisfaction Return

Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.

United States 1.440.646.3434Monday – Friday, 8am – 5pm EST

Outside United States

Please contact your local Rockwell Automation representative for any technical support issues.

United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process.

Outside United States

Please contact your local Rockwell Automation representative for the return procedure.

Publication 1757-UM007D-EN-P - December 2008 158 Supersedes Publication 1757-UM007C-EN-P - April 2004 Copyright © 2008 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

http://support.rockwellautomation.com

http://support.rockwellautomation.com

red rio

Engineering

electromechanical equipment

actual use

user manual catalog

property damage

successful application

intended application

controlflash software

rslinx software requirements