1757-um007_-en-p.pdf

8/10/2019 1757-um007_-en-p.pdf

1/160

User Manual

(Catalog Number 1757-ABRIO)

Process Remote I/O (RIO)

Communication Interface Module

8/10/2019 1757-um007_-en-p.pdf

2/160

Important User Information

Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelinesfor the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1available from your localRockwell Automation sales office or online at http://literature.rockwellautomation.com) describes some important differencesbetween 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 themselvesthat 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 theuse or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables andrequirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liabilityfor 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, orsoftware described in this manual.

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

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.

ATTENTIONIdentifies 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/idc/groups/literature/documents/in/sgi-in001_-en-p.pdfhttp://literature.rockwellautomation.com/http://literature.rockwellautomation.com/idc/groups/literature/documents/in/sgi-in001_-en-p.pdfhttp://literature.rockwellautomation.com/

8/10/2019 1757-um007_-en-p.pdf

3/160

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

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 Modules Firmware. . . . . . . . . . . . . 14

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

Chapter 2

Configure the 1757-ABRIO Module Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17AbRioCfg Software Overview. . . . . . . . . . . . . . . . . . . . . . . . 17Mapping and Accessing RIO Network Data . . . . . . . . . . . . . 18Installing AbRioCfg Software . . . . . . . . . . . . . . . . . . . . . . . . 19

Autoconfigure 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

8/10/2019 1757-um007_-en-p.pdf

4/160

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

Table of Contents

Chapter 3

Creating Generic Modules in

AbRioCfg SoftwareIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 4

Configuring the ProcessLogix

Controller to Access Data on the

1757-ABRIO Module

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

CONFIG Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51INACTIVE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

ACTIVE Mode (Run) . . . . . . . . . . . . . . . . . . . . . . . . . . . 52FORCED ACTIVE Mode . . . . . . . . . . . . . . . . . . . . . . . . . 52

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

Chapter 5

Configuring RSLogix 5000

Software to Access Data on the

1757-ABRIO Module

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

CONFIG Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57INACTIVE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

ACTIVE 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 RIONetwork Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 6

Accessing Data through a DDE or

OPC Server

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Accessing Data from a DDE or OPC Server . . . . . . . . . . . . . 75Configuring a Topic in RSLinx Software . . . . . . . . . . . . . 75

Accessing the Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

8/10/2019 1757-um007_-en-p.pdf

5/160

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

Table of Contents

Chapter 7

Monitoring the 1757-ABRIO

ModuleIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Monitoring the Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 77Monitoring Digital I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Monitoring 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 8

Supported 1771 Modules Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Module 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 101I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

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

8/10/2019 1757-um007_-en-p.pdf

6/160


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 9

Accessing HART Data Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Sending HART Commands Using RSLogix 5000 Software MSG .115

HART Command Data . . . . . . . . . . . . . . . . . . . . . . . . . 117Reply Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Example: HART Command 36 . . . . . . . . . . . . . . . . . . . 1221770-HT1 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

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

Appendix A

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Appendix B

Troubleshooting Interpret the Status Indicators . . . . . . . . . . . . . . . . . . . . . . 133RIO 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

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

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

8/10/2019 1757-um007_-en-p.pdf

7/160


Table of Contents

Appendix C

Operational 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 SoftwareConfiguration Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149I and O Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Status Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

8/10/2019 1757-um007_-en-p.pdf

8/160


Table of Contents

8/10/2019 1757-um007_-en-p.pdf

9/160


Preface

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

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

Who Should Use thisManual

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

Additional ResourcesThese documents contain additional information concerning relatedRockwell Automation products.

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

You can view or download publications athttp://literature.rockwellautomation.com. To order paper copies oftechnical documentation, contact your local Rockwell Automationdistributor or sales representative.

Resource Description

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

Provides details on how to install the1757-ABRIO module.

Process Remote I/O (RIO) Communication

Interface Module Release Notes,

publication 1757-RN520

Provides release details on the 1757-ABRIOmodule.

Industrial Automation Wiring and GroundingGuidelines, publication 1770-4.1

Provides general guidelines for installing aRockwell 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.pdfhttp://literature.rockwellautomation.com/http://literature.rockwellautomation.com/idc/groups/literature/documents/in/1757-in916_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/rn/1757-rn520_-en-p.pdfhttp://www.literature.rockwellautomation.com/idc/groups/literature/documents/in/1770-in041_-en-p.pdfhttp://ab.com/http://literature.rockwellautomation.com/http://ab.com/http://www.literature.rockwellautomation.com/idc/groups/literature/documents/in/1770-in041_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/rn/1757-rn520_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/in/1757-in916_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/in/1757-in916_-en-p.pdf

8/10/2019 1757-um007_-en-p.pdf

10/160


Table of Contents Preface

8/10/2019 1757-um007_-en-p.pdf

11/160


Chapter1

Introduction

Introduction This chapter:

describes the 1757-ABRIO Remote I/O Module.

lists the RSLinx software requirements.

provides update procedures for the modules firmware.

Process Remote I/O (RIO)

Communication InterfaceModule

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 aRIO network scanner. The 1757-ABRIO module facilitates connectionto analog and discrete I/O devices as well as any block transfermodules.

1757-ABRIO Module Example Topology

43290

SupportsBlockTransfers -limit of 32words in ablock

ProcessLogixSystem Server

Flex Ex Modules

PLC5/CController

ControlNet

NetworkSLC Controller

Data Highway + Network

ControlNet Network

PLC5Controller

ProcessLogix and ControlLogix Controllers

Remote I/O Network

1771 Remote I/O

1746 Remote I/O

Drive

8/10/2019 1757-um007_-en-p.pdf

12/160


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, updatetime 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 aControlLogix controller.

implements a watchdog timer in the modules hardware.

If the firmware does not kick the watchdog within the time-outperiod the watchdog times out and places the module into the

configured safe failure state.

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

implements a jabber inhibit timer.

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

supports firmware updates using NTools or ControlFlashsoftware.

supports direct DDE/OPC data access.

provides support for Rockwell Automations 1770-HT1,1770-HT8, and 1770-HT16 HART interface products.

provides HART command set for calibration and diagnostics.

RSLinx SoftwareRequirements

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

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

8/10/2019 1757-um007_-en-p.pdf

13/160


Introduction Chapter1

ProcessLogix System QuickStart

Use the following steps to quickly get the module running in aProcessLogix system. Detailed information about each step is availablein other sections of this manual or in the installation manual. You canonly have one scanner per RIO network. Remove any other scannerson the RIO network before continuing.

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

See the Process Remote I/O (RIO) Communication InterfaceModule 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 steplocates all connected racks.

SeeAutoconfigure the I/O Racks on page 19andAdd RacksOffline on page 33.

5. Add and configure block transfer modules.

SeeAdding 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 informationwithin 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.
http://literature.rockwellautomation.com/idc/groups/literature/documents/in/1757-in916_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/in/1757-in916_-en-p.pdf

8/10/2019 1757-um007_-en-p.pdf

14/160



RSLogix 5000 System QuickStart

Use the following steps to quickly get the module running in anRSLogix 5000 system. Detailed information about each step isavailable in other sections of this manual or in the installation manual.

You can only have one scanner per RIO network. Remove any otherscanners on the RIO network before continuing.

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

See the Process Remote I/O (RIO) Communication InterfaceModule 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 steplocates all connected racks.

SeeAutoconfigure the I/O Racks on page 19andAdd RacksOffline on page 33.

5. Add and configure block transfer modules.

SeeAdding Block Transfer Modules on page 23.

6. Create tags to access analog data from the ControlLogixcontroller.

See Create a Tag on page 30.

OR

Use scheduled updates to access digital data from theControlLogix controller.

See Scheduled Digital I/O Connections in RSLogix 5000Programs 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.
http://literature.rockwellautomation.com/idc/groups/literature/documents/in/1757-in916_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/in/1757-in916_-en-p.pdf

8/10/2019 1757-um007_-en-p.pdf

15/160



9. If you are using:

a. a scheduled network, establish an Exclusive Owner or InputOnly connection from the ControlLogix controller to accessdigital data within the 1757-ABRIO module.

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

b. an unscheduled network, configure tags and ladder logic inRSLogix 5000 software to access information within the1757-ABRIO module.

See Unscheduled I/O Connections in ControlLogix onpage 67.

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

See the RSNetWorx Help and the ControlNet Modules inLogix5000 Control Systems User Manual, publicationCNET-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 60and Live Data Example on page 66.

b. unscheduled connections.

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

TIP If you are using a scheduled ControlNet network, youmust 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.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/um/cnet-um001_-en-p.pdf

8/10/2019 1757-um007_-en-p.pdf

16/160



Update the 1757-ABRIOModules Firmware

The 1757-ABRIO module supports firmware upgrades usingControlFLASH or NTools software. The firmware version is displayedon the 1757-ABRIO modules 4-character display when you power upthe module.

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

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

greater than 1.2, use NTools software to update the modulefirmware.

Using ControlFlash Software

Use the following procedure to update the module firmware usingControlFLASH 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 the1757-ABRIO module when you first receive it.

8/10/2019 1757-um007_-en-p.pdf

17/160



10. Click 1757-ABRIO and click Next.

11. Expand the RSLinx Tree window to the location of the1757-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 beforeusing the target device in its intended application.

17. Click OK and then click Cancel at the Welcome to ControlFLASHSetup 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 usingNTools.

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

2. Type >ntools -c -u

8/10/2019 1757-um007_-en-p.pdf

18/160



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

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 Toolswindow tracks the load progress.

13. When the load completes, click OK.

8/10/2019 1757-um007_-en-p.pdf

19/160


Chapter2

Configure the 1757-ABRIO Module

Introduction This chapter:

provides an overview of the AbRioCfg software.

gives an introduction to mapping and accessing RIO networkdata.

explains how to install the AbRioCfg software.

explains how to autoconfigure I/O racks.

explains how to add and configure block transfer modules.

AbRioCfg SoftwareOverview

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

query the RIO network to determine the location and size of theracks 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 integerdata.

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

monitor data and diagnostics on the module.

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

change the configuration of racks in a configuration anddownload to the module.

upload a configuration from a module.

print the configuration.

8/10/2019 1757-um007_-en-p.pdf

20/160


Chapter 2 Configure the 1757-ABRIO Module

Mapping and AccessingRIO Network Data

Use the provided AbRioCfg software to create tags which are arrays ofdigital, 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. Thedata mapping is stored in flash memory on the 1757-ABRIO module.

The 1757-ABRIO Module and Data Mapping

WARNI NG It is essential that the control program on the host controllermatches 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 orProcessLogix

Controller

Write Data

Remote I/OModules

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

ScanList

RIO NetworkScanner

Remote I/OModules

8/10/2019 1757-um007_-en-p.pdf

21/160


Configure the 1757-ABRIO Module Chapter2

Installing AbRioCfgSoftware

1. Verify that RSLinx software and RSLinx OEM or RSLinxProfessional (not RSLinx Lite) software is installed before youinstall the AbRioCfg software.

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

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

Before you install a new version of AbRioCfg software, you mustdelete the old version. Use the Add or Remove Programs utility in

your Windows Control Panel to remove the previous version.

Autoconfigure the I/ORacks

The first step in building a configuration is to perform anautoconfiguration. To complete an autoconfiguration, the RIOnetwork must be connected to the 1757-ABRIO module and the

module must be in inactive mode.

1. Start AbRioCfg software.

IMPORTANTMessages 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 whenrunning 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.

8/10/2019 1757-um007_-en-p.pdf

22/160



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

3. Click the Autoconfig button in the toolbar.

An RSWho window opens.

TIP With AbRioCfg software, 2.0 and higher, you can also manuallyconfigure the I/O racks in your network. Refer to Add Racks

Offline on page 33for more information.

8/10/2019 1757-um007_-en-p.pdf

23/160



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.

8/10/2019 1757-um007_-en-p.pdf

24/160



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

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

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

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

The Select Rack Setting dialog box opens.

8/10/2019 1757-um007_-en-p.pdf

25/160



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

This setting tells the 1757-ABRIO module what to do if the

controller stops updating the tag to which this chassiss digitaldata is mapped.

c. Repeat steps 7aand 7bfor all racks that contain 1771 remoteI/O modules.

Adding Block TransferModules

Autoconfiguration can locate the racks present on the network but itcannot detect the analog I/O modules in those racks. Remote I/Oprotocol does not allow for module identification to be communicatedon the network. Because of this, Block Transfer modules need to beadded 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 thenetwork tree.

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

The Add BT Module dialog box opens.

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

8/10/2019 1757-um007_-en-p.pdf

26/160



4. Select the slot location for the module.

To do this, you should be familiar with Allen-Bradley addressesand, in particular, with 1771 addressing modes (see below).See I/O Module Documentation on page 84for 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 and2-slot addressing. The addressing mode is set by switches in thebackplane of the chassis and is set on a per-chassis basis. Theaddressing mode determines how physical block transfer modulesmap into logical addresses (rack, I/O group and slot).

In the following tables, the addresses used for modules in a 16-slotrack 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 controlleraddresses two I/O module slots as one I/O group. For example, for achassis at rack 1, starting I/O group 0, a block transfer module in thefirst slot would be at address rack 1, I/O group 0, slot 0. A module inthe next slot would be at rack 1, I/O group 0, slot 1.

As illustrated in the 1-slot addressing table below, the controlleraddresses one I/O module slot as one I/O group. For example, for achassis at rack 1, starting I/O group 0, a block transfer module in thefirst slot would be at address rack 1, I/O group 0, slot 0. A module inthe 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

8/10/2019 1757-um007_-en-p.pdf

27/160



As illustrated in the 1/2-slot addressing table below, the controlleraddresses 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 inthe first slot would be at address rack 1, I/O group 0, slot 0. A modulein the next slot would be at rack 1, I/O group 2, slot 0.

Configuring Block TransferModules

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

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

To edit the configuration for a module, double-click the module in thenetwork 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 theconfiguration once you have created it. You must delete the

module and create a new one at the new location.

8/10/2019 1757-um007_-en-p.pdf

28/160



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

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

Input Scaling

For analog input modules, you must supply the floating point valuesto 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 minimumscaling 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.

8/10/2019 1757-um007_-en-p.pdf

29/160



Output Scaling

For output modules, you supply the floating point values you want tocorrespond 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 minimumscaling 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.

8/10/2019 1757-um007_-en-p.pdf

30/160



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

Before you program the controller to read or write to the 1757-ABRIOmodule, 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 scaledfloating point values.

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

8/10/2019 1757-um007_-en-p.pdf

31/160



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 bemapped to flag read tags.

Dragging an entire I/O Grp to a Flag Read or Flag Write tagwill expose all discrete read or write values for that rack aswell 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 HARTinterface is read only. You can read text and tags from theHART, but you cant write data to the HART.

8/10/2019 1757-um007_-en-p.pdf

32/160



Create a Tag

If you are planning to use automatic digital tags via a scheduledconnection to the 1757-ABRIO module from a ControlLogix controller,

do not create tags. Refer to Scheduled Digital I/O Connections inRSLogix 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 AddTag.

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

4. Type a message timeout time.

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

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

5. Click OK to accept the tag.

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

8/10/2019 1757-um007_-en-p.pdf

33/160



Mapping Data to Tags inAbRioCfg Software

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

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

Block Transfers

When mapping block transfer modules, drag the analog module fromthe network tree to the location in the tag where you want the data tobe 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/Omodule is mapped to the tag. You can map data from many I/Omodules into the same tag.

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

In addition, block transfer modules have status information that canbe mapped to flag read tags. Refer to Supported 1771 Modules onpage 83for 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 60for more

information.

8/10/2019 1757-um007_-en-p.pdf

34/160



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 toadd the data.

3. Drag the rack or block transfer module to the desired location inthe 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 particularmodule. Data is not affected for the other modules mapped to thesame tag.

Tips for ConfiguringModules

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

The following operations are features of firmware version 2.1. To usethese 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 uploadconfigurations made with previous versions of AbRioCfgsoftware.

8/10/2019 1757-um007_-en-p.pdf

35/160



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.

8/10/2019 1757-um007_-en-p.pdf

36/160



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 flagmappings for the rack are deleted. If this partial rack is the only one inthe rack number, the rack number will be deleted from the tree.

8/10/2019 1757-um007_-en-p.pdf

37/160



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 RSWhowindow, click Yes.

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

Download theConfiguration

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

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

8/10/2019 1757-um007_-en-p.pdf

38/160



Upload the Configuration To upload a configuration from a 1757-ABRIO module, selectActions>Upload config or click the Upload Config From Modulebutton on the toolbar.

8/10/2019 1757-um007_-en-p.pdf

39/160


Chapter3

Creating Generic Modules in AbRioCfgSoftware

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

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

AbRioCfg software version 2.1 or above

AbRioCfg software version 2.1 or above can open or uploadconfigurations made with previous versions of AbRioCfgsoftware.

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

If you need to access HART data refer toAccessing HART Data onpage 115.

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

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

Configure a block transfer module that is already supported byAbRioCfg software in ways that the standard configuration doesnot allow, for example, using fewer channels than in thestandard module configuration, or adding features not

supported by the standard configuration.

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

8/10/2019 1757-um007_-en-p.pdf

40/160


Chapter 3 Creating Generic Modules in AbRioCfg Software

Generic ModuleConfiguration 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 maximumsize for each section is 64 words of data.

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

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

Configuration Block Transfer Write

The configuration block transfer write section (Config BTW) containsthe data that is sent to the module to set how it operates. Theconfiguration 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 keywordconfigbtw, followed by the block transfer length, in words.

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

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

TIP Sample configuration files are available for your use. The filesare located in the \GenProfile directory on the supplied

1757-ABRIO CD.

EXAMPLE configbtw, 13

8/10/2019 1757-um007_-en-p.pdf

41/160


Creating Generic Modules in AbRioCfg Software Chapter3

The offset is the offset into the block transfer and ranges from 0 to theblock transfer length - 1. For example, if the block transfer is 10 wordslong, 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 witha 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 transferwrite, 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, 0xB321

11, 45857

Only non-zero values need be entered; all other values in the

configuration block transfer will default to 0.

8/10/2019 1757-um007_-en-p.pdf

42/160



Example: 1771-IFE Module

The following configuration block transfer write file configures a1771-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 21

0, 0

1, 0

2, 0x0500 ; differential inputs, binary

3, 0

4, 05, 0

6, 0x4095 ; channel 1 scaling

7, 0


9, 0


11, 0


13, 0


15, 0

16, 0x4095 ; channel 6 scaling17, 0


19, 0


8/10/2019 1757-um007_-en-p.pdf

43/160



Example: 1771-OFE module

The following configuration block transfer write file configures a1771-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 thatis used to read data from an input module, and is sometimes used toread status data from an output module.

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

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

Numeric Data

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

The beginning of the numeric section is marked by the keywordnumeric, followed by the number of values to be defined, and thedata format.

EXAMPLE databtr, 15


4, 0x8000 ; binary data format

6, 0x0fff ; maximum raw value channel 1




8/10/2019 1757-um007_-en-p.pdf

44/160



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

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 rowof the spreadsheet (or line of a text file). Each definition consists ofthe following fields:

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

If the underrange or overrange bit is set, the AbRioCfg softwaresets 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 intothe 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, 015

Underrange bit Bit number, 015

Overrange offset(1) Word offset of overrange bit, 015

Overrange bit Bit number, 015

Polarity offset(1) Word offset of polarity bit, 015

Polarity bit Bit number, 015

Minimum raw value Minimum raw input

Maximum raw value Maximum raw input

Minimum scale value Minimum floating point scaled value that correspondsto minimum raw value

Maximum scale value Maximum floating point scaled value thatcorresponds to maximum raw value

8/10/2019 1757-um007_-en-p.pdf

45/160



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

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

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

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

If the data type is BCD, enter the raw minimum and maximum valuesin 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 tomap to flag read tags, for example, a module error bit. If a module hasflag data defined, you can then map it to flag read data in AbRioCfgsoftware.

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

The beginning of the flag section is marked by a line containing thekeyword 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 datais found. Each line consists of an offset and a length. The maximumnumber 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 offset2, 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

numeri c 4 B CD

4 1 0 2 0 3 0 0 4095 0 1000

8/10/2019 1757-um007_-en-p.pdf

46/160



The offset is an offset into the block transfer. It can range from 0 tothe 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 canrange from 8 to 504 and must be a multiple of 8. The sum of thelengths in the data definitions must match the length in the flag line.

Example: 1771-IFE Module

The following definitions assign the underrange and overrange bitsfrom 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. Itconsists of the following flags:

EXAMPLE flag, 32

Bit Description

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

1 BTR Raw underrange bit, set if the raw input to the module is less than thedefined 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 thedefined 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 thedefined raw minimum. The module clamps the output at the raw minimum.

6 BTW raw overrange, set if the calculated output value is greater than thedefined 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,8

2H,8

4,16

flag, 32

1,16

2,16

8/10/2019 1757-um007_-en-p.pdf

47/160



Sample 1771-IFE Configuration File

Data Block Transfer Write

The data block transfer write defines the cyclic block transfer read thatis used to write data to an output module. The data block transfer

write consists of a numeric section and a flag section. The beginningof the data block transfer write section is marked by the keyworddatabtw, followed by the block transfer write length.

EXAMPLE databtw, 12


2, 0x0500 ; differential inputs, binary

5, 06, 0x4095 ; channel 1 scaling

7, 0


9, 0


11, 0


13, 0


15, 0


17, 018, 0x4095 ; channel 7 scaling

19, 0


databtr, 12

numeric, 4, signed

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

5, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 1000

6, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 1000

7, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 1000

8, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 1000

9, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 1000

10, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 1000

11, 1, 0, 2, 0, 3, 0, 0, 4095, 0, 1000

flag, 32

1, 16

2, 16

8/10/2019 1757-um007_-en-p.pdf

48/160



Numeric Data

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

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

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

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 arow 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 aninput. If the data being written is negative, the 1757-ABRIO modulesets 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 correspondsto minimum raw value

Maximum scale value Maximum floating point scaled value that correspondsto maximum raw value

8/10/2019 1757-um007_-en-p.pdf

49/160



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

If the scaled valued written is NaN, the raw output gets set to thecorresponding value in the configuration data. For example, if an I/Odata value is at offset 7 in the data block transfer write, the value atoffset 7 in the configuration block transfer write is written if the hostcontroller 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 tomap to flag write tags.

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

The beginning of the flag section is marked by a line containing thekeyword 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 datais found. Each line consists of an offset and a length. The maximumnumber of flag definition lines is 4.

The offset is an offset into the block transfer. It can range from 0 tothe 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 maximumvalues 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 polaritybit 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

8/10/2019 1757-um007_-en-p.pdf

50/160



The sum of the lengths in the data definitions must match the lengthin the flag line.

Example 1771-OFE Configuration File

Creating a Generic Modulein AbRioCfg software

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

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

EXAMPLE flag, 32

0,82H,8

4,16


4, 0x8000 ; binary data format





databtw, 12numeric, 4

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

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

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

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

8/10/2019 1757-um007_-en-p.pdf

51/160



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

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

AbRioCfg software imports the configuration file and displaysthe contents, or gives an error message if it finds problems withthe 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 tothe desired numeric read, numeric write, flag read or flag write tag.

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

8/10/2019 1757-um007_-en-p.pdf

52/160



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

8/10/2019 1757-um007_-en-p.pdf

53/160


Chapter4

Configuring the ProcessLogix Controller toAccess 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 ProcessLogixcontroller.

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

Modes related to RIO network operations:

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

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

CONFIG Mode

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

8/10/2019 1757-um007_-en-p.pdf

54/160


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 messagesfrom either a host controller or via OPC/DDE. The module is also in

INACTIVE mode when it has not been put in FORCED ACTIVE modeby AbRioCfg software.

When the module is in INACTIVE mode, the RIO network is placed inprogram mode with input updates but no output updates. The1757-ABRIO module must be in the INACTIVE mode to accept adownload.

ACTIVE Mode (Run)

The module is in ACTIVE mode when it receives a message fromeither a host controller or from an OPC or DDE server. When themodule 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 beupdating until the time-out expires. If all tags have timed out, the1757-ABRIO module automatically switches to INACTIVE mode.

If you try to download a configuration when the module is in ACTIVEmode, 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 INACTIVEmode.

FORCED ACTIVE Mode

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

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

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

is in run mode.

8/10/2019 1757-um007_-en-p.pdf

55/160


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

Configure the 1757-PLX52Controller

To access tag data on the 1757-ABRIO module from a ProcessLogixcontroller, use the REQNUMARRAY, REQFLAGARRAY andREQTEXTARRAY Exchange Blocks with CIPREAD and CIPWRITEcommands 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) bydragging 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.

8/10/2019 1757-um007_-en-p.pdf

56/160



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 CharLength of String Values to 64.

9. Select the Communications tab.

10. Set the Path from the ProcessLogix controller to the 1757-ABRIOmodule.

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

Flag Arrays Numeric Arrays Text Arrays

8/10/2019 1757-um007_-en-p.pdf

57/160


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

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

12. Perform any other configuration required by your application onthe other tabs.

13. Click OK to accept the block.

14. Wire the ready flag (READYFL) to the send flag (SENDFL) foreach 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.

8/10/2019 1757-um007_-en-p.pdf

58/160



Live Data Examples

Double-click function block

8/10/2019 1757-um007_-en-p.pdf

59/160


Chapter5

Configuring RSLogix 5000 Software to AccessData 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 ControlLogixcontroller.

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

Modes related to RIO network operations:

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

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

CONFIG Mode

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

8/10/2019 1757-um007_-en-p.pdf

60/160


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 messagesfrom either a host controller or via OPC/DDE. The module is also in

INACTIVE mode when it has not been put in FORCED ACTIVE modeby AbRioCfg software.

When the module is in INACTIVE mode, the RIO network is placed inprogram mode with input updates but no output updates. The1757-ABRIO module must be in the INACTIVE mode to accept adownload.

When scheduled connections are used, the 1757-ABRIO modulesmode will always follow the ControlLogix controllers mode regardlessif it is receiving messages. For example, when the controller is inPROGRAM mode, the module is in INACTIVE mode.

ACTIVE Mode (Run)

The module is in ACTIVE mode when it receives a message fromeither a host controller or from an OPC or DDE server. When themodule 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, the1757-ABRIO module automatically switches to INACTIVE mode.

If you try to download a configuration when the module is in ACTIVEmode, 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 INACTIVEmode.

When scheduled connections are used, the 1757-ABRIO modulesmode will always follow the ControlLogix controllers mode regardlessif it is receiving messages. For example, when the controller is in RUN

mode, the module is in ACTIVE mode.

8/10/2019 1757-um007_-en-p.pdf

61/160


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

FORCED ACTIVE Mode

The module is in FORCED ACTIVE mode when you set ACTIVE modefrom the AbRioCfg program. FORCED ACTIVE mode lets you send

and receive data without having to create messages in the module. Itis intended primarily for setting up and testing RIO networks.

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

IMPORTANTWhen the module is in FORCED ACTIVE mode, the RIO network

is in run mode.

8/10/2019 1757-um007_-en-p.pdf

62/160



Scheduled Digital I/OConnections in RSLogix5000 Programs

1757-ABRIO module firmware versions 1.2 and above supportscheduled connections for exchanging digital input and output databetween the 1757-ABRIO module and the host ControlLogixcontroller. This results in much faster updates for the digital data thanis possible using unscheduled messages. This section describes howto configure the module and the format of the scheduled data.

When you add a 1757-ABRIO module to the I/O Configuration of anRSLogix 5000 program using the generic 1757-MODULE profile, a dataconnection is created for the digital remote I/O data. See TagDescriptions for Scheduled Data in RSLogix 5000 Software onpage 149for more information about the status tag when usingControlLogix. The status tag gives global status for digital data andindividual 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 torepresent the 1757-ABRIO module. This dictates the format andamount of scheduled data, and how often the scheduled data istransferred. The ControlLogix controller is the owner of theconnection and controls the digital outputs. The connection is referredto as an exclusive-owner connection.

TIP In order to access any numeric read, numeric write, or text readdata 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 achassis, 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.

8/10/2019 1757-um007_-en-p.pdf

63/160



Remote I/O Operating Modes

If there is an exclusive-owner connection to the 1757-ABRIO module,the modules remote I/O mode (run or program) follows the owner

ControlLogix controllers Run or Program mode. If the ownerControlLogix controller is in Program mode, the 1757-ABRIO moduleis in program mode (even if the module is receiving messages). If theControlLogix controller is in Remote Test mode, the remote I/O modefor the 1757-ABRIO module is program.

The remote I/O mode is not affected by the operating mode of aControlLogix controller that has an input-only connection to the1757-ABRIO module. In the absence of an exclusive-ownerconnection, the 1757-ABRIO modules remote I/O mode is determinedby 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, theControlLogix 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 inthe 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 Moduleand click OK.

The Module Properties dialog box opens.

8/10/2019 1757-um007_-en-p.pdf

64/160



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 checkedand click OK.

11. Set the modules Requested Packet Interval (RPI).

This is how often the module's scheduled data is updated in thecontroller. 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 ControlLogixcontroller.

AssemblyInstance

Size

Input 1 250

Output 2 248

Configuration 4 0

Status Input 5 10

Status Output 6 N/A

8/10/2019 1757-um007_-en-p.pdf

65/160



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, makesure the chassis is not mapped to a flag write tag.

Setup Input-only Connections

The 1757-ABRIO module also supports input-only connections. In aControlLogix system, multiple controllers can receive inputs from amodule, but only one controller can control the outputs. Aninput-only connection does not require the presence of an exclusive

owner connection. More than one ControlLogix controller can openan input-only connection to the 1757-ABRIO module and receive itsinputs.

Add a Module as an Input-only Connection

To configure an input-only connection to the 1757-ABRIO module inRSLogix 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 inthe 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 Moduleand click OK.

8/10/2019 1757-um007_-en-p.pdf

66/160



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

1757-um007_-en-p.pdf

Documents

Transcript of 1757-um007_-en-p.pdf