Allen-Bradley 1757-ABRIO User Manual
  1. Manuals
  2. Brands
  3. Allen-Bradley Manuals
  4. Control Unit
  5. 1757-ABRIO
  6. User manual
Allen-Bradley 1757-ABRIO User Manual

Allen-Bradley 1757-ABRIO User Manual

Process remote i/o rio communication interface module
Hide thumbs Also See for 1757-ABRIO:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Instruction and Installation Manual
Process Remote I/O
(RIO)
Communication
Interface Module
1757-ABRIO
User Manual
AB Spares

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 1757-ABRIO and is the answer not in the manual?

Questions and answers

Related Manuals for Allen-Bradley 1757-ABRIO

Summary of Contents for Allen-Bradley 1757-ABRIO

  • Page 1 Process Remote I/O (RIO) Communication Interface Module 1757-ABRIO User Manual AB Spares...

  • Page 2: Important User Information

    Allen-Bradley publication SGI-1.1, Safety Guidelines for the Application, Installation and Maintenance of Solid-State Control (available from your local Rockwell Automation office), describes some important differences between solid-state...

  • Page 3: Table Of Contents

    Introduction 1757-ABRIO Remote I/O Module ......1-1 RSLinx Requirements........1-2 ProcessLogix Quick Start.
  • Page 4 Modes of Operation........4-1 Access Data on the 1757-ABRIO CONFIG Mode .
  • Page 5 Table of Contents 1757-ABRIO Unscheduled I/O Connections in ControlLogix ........5-10 Create Tags For All Messages and All Storage Areas .
  • Page 6 Table of Contents Diagnostic Data ........8-16 1771-NOC .
  • Page 7 Exception Handling Messages....... B-4 the 1757-ABRIO and PLC-5 Appendix C Configuration Tag .
  • Page 8 Table of Contents viii Publication 1757-UM007C-EN-P - April 2004...

  • Page 9: Preface

    See Table 8.2 on page 8-2 for a listing of related ControlLogix documentation. Related Documentation If you need more information on these products, contact your local Allen-Bradley integrator or sales office for assistance. For more information on the documentation, refer to the Allen-Bradley Publication Index, publication SD499 or visit us at: •...
  • Page 10 Preface Notes: Publication 1757-UM007C-EN-P - April 2004...

  • Page 11: Introduction

    • describes the 1757-ABRIO Remote I/O Module • lists the RSLinx Requirements • provides update procedures for the module’s firmware This document is a user guide for the 1757-ABRIO module, which allows Process Remote I/O (RIO) Rockwell Automation controllers (ProcessLogix or ControlLogix) to Communication Interface communicate with Allen-Bradley remote I/O.

  • Page 12: Rslinx Requirements

    Introduction As a RIO 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 Kbaud. • Supports up to 32 adapters with any mix of full/partial racks. •...

  • Page 13: Processlogix Quick Start

    Remove any other scanners on the RIO network before continuing. Table 1.1 Quick Start Reference for ProcessLogix Users Step: Refer to: 1. Install the 1757-ABRIO in the The 1757-ABRIO Installation chassis and connect it to the Instructions, publication RIO network.

  • Page 14: Controllogix Quick Start

    ControlLogix Quick Start Table 1.2 Quick Start Reference for ControlLogix Users Step: Refer to: 1. Install the 1757-ABRIO in the chassis and The 1757-ABRIO Installation Instructions, connect it to the RIO network. publication 1757-IN916. 2. Flash the Controller with the latest Using ControlFlash on page 1-5.

  • Page 15: Updating The 1757-Abrio Firmware

    ControlFLASH or NTools (ProcessLogix) utilities. ControlLogix Systems use Firmware ControlFLASH to update the module firmware. The firmware version is displayed on the 1757-ABRIO 4-character display when you power up the module. For ProcessLogix Users, if your 1757-ABRIO module revision is: •...

  • Page 16: Using Ntools With Processlogix

    9. At the Welcome to ControlFLASH window, click Next. 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.
  • Page 17 Introduction 4. Click OK to acknowledge the warning about monitoring through Control Builder. 5. Click the resume button to initiate network scan. 6. Select the appropriate CNB or ENET icon. 7. Select the module to be updated in the chassis graphic. 8.
  • Page 18 Introduction Notes: Publication 1757-UM007C-EN-P - April 2004...

  • Page 19: Configure The 1757-Abrio

    • installing the AbRioCfg software • autoconfiguring I/O racks • adding and configuring block transfer modules The 1757-ABRIO ships with a configuration utility, AbRioCfg. This AbRioCfg Overview configuration program is an online configuration tool. Use it to: • query the RIO network to determine the location and size of the racks present •...

  • Page 20: Mapping And Accessing Rio Data

    Configure the 1757-ABRIO Use the provided 1757-ABRIO configuration tool (AbRioCfg) to create tags Mapping and Accessing which are arrays of digital, floating point or text values that the host processor RIO Data 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.

  • Page 21: Installing Abriocfg

    Configure the 1757-ABRIO 1. RSLinx should be installed before you install the AbRioCfg software. Installing AbRioCfg 2. Insert the CD supplied with the 1757-ABRIO and run the program setup.exe. Messages about DTL32.DLL during installation or when IMPORTANT you run the program indicate problems with the RSLinx installation.

  • Page 22: Autoconfiguring I/O Racks

    The first step in building a configuration is to perform an autoconfiguration. Autoconfiguring I/O Racks The RIO network must be connected to the 1757-ABRIO module and the module must be in “inactive” mode. When using AbRioCfg, you must left click to...
  • Page 23 Configure the 1757-ABRIO ⇒ 3. Click on Hardware Config in the network tree, then select Actions Config from the main menu. 2. Then click the Autoconfig icon on 1. To start the the toolbar. configuration, left click here once to...
  • Page 24 RIO network must operate at the same baud rate. The 1757-ABRIO then 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.

  • Page 25: Adding Block Transfer Modules

    9. Select the value that matches the Last State switch setting in the backplane of the 1771 rack, either De-energize or Hold Last State. This setting tells the 1757-ABRIO what to do if the host processor stops updating the tag that this rack’s digital data is mapped to.
  • Page 26 3. Select the Module Type from the list. 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 Table 8.2 on page 8-2 for a list of related ControlLogix documentation.

  • Page 27: Addressing Modes For 1771

    Configure the 1757-ABRIO Addressing Modes for 1771 Allen-Bradley 1771 racks 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).

  • Page 28: Configuring Block Transfer Modules

    The 1757-ABRIO performs scaling between raw I/O data and floating point user values. You send floating point output values to the 1757-ABRIO which it then converts to raw output values using the scaling values you supplied in the configuration. Similarly, the 1757-ABRIO converts raw input data to floating point values, using the scaling you enter.

  • Page 29: Input Scaling

    Configure the 1757-ABRIO 2-11 Input Scaling For analog input modules, you supply the floating point values you want the minimum and maximum raw data scaled to. • minimum corresponds to the lowest raw value • maximum corresponds to the maximum raw value...

  • Page 30: Tags Defined

    The PLX or CLX accesses data for the 1757-ABRIO using unscheduled messages that read or write tags. Before you program the PLX or CLX to read or write to the 1757-ABRIO, you must define the Tags in AbRioCfg. The 1757-ABRIO supports five types of tags.

  • Page 31: Create A Tag

    This is the time during which the host processor must update the tag. The range of values is 100 to 15000 ms. The default is 5000 ms. If the tag time-out is exceeded, the tag times out and the 1757-ABRIO takes appropriate action.

  • Page 32: Mapping Data To Tags In Abriocfg

    If you are using a CLX, no actions are necessary to read or write digital data Mapping Data to Tags in with scheduled connections. Refer to 1757-ABRIO Scheduled Digital I/O AbRioCfg Connections in ControlLogix on page 5-4 for more information.

  • Page 33: I/O

    Data is not affected for the other modules mapped to the same tag. Use the largest range of raw values possible for the 1757-ABRIO and Tips for Configuring optimum data resolution. The scaling should be done to engineering units in Modules the module.

  • Page 34: Offline Adding And Deleting Racks

    2-16 Configure the 1757-ABRIO Offline Adding and Deleting Racks To add a rack: 1. Right click on 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.

  • Page 35: Offline Baud Rate Changes

    You will be asked whether you want to set the baud rate in an ABRIO • If you select Yes, an RSWho window will appear and you can select the path the 1757-ABRIO module. • If you select No, the change will be made only in the offline file.

  • Page 36: Downloading The Configuration

    Scaling data for modules that have not been mapped to tags is not downloaded with the configuration. You can upload a configuration from a 1757-ABRIO module using the Uploading a Configuration ⇒ Actions Upload config command from the menu or using the Upload Config From Module button on the toolbar.

  • Page 37: Chapter 3 Introduction

    I/O module that uses 16-bit integer data. To use these features, you need: • Firmware version 2.1 or above of the firmware for the 1757-ABRIO • AbRioCfg version 2.1 or above AbRioCfg version 2.1 or above can open or upload configurations made with previous versions of AbRioCfg.

  • Page 38: Generic Module Configuration File

    Creating Generic Modules in AbRioCfg The Generic Module configuration file consists of three sections: Generic Module Configuration File – the configuration block transfer write – 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;...
  • Page 39 Creating Generic Modules in AbRioCfg The value can be in one of the following formats: Format Range Binary 0b0000000000000000 to 0b1111111111111111 Hexadecimal 0x0000 to 0xFFFF Unsigned integer 0 to 65535 Signed integer -32768 to 32767 Binary values start with a leading “0b”. Hexadecimal values start with a leading “0x”.

  • Page 40: Example: 1771-Ife Module

    Creating Generic Modules in AbRioCfg Example: 1771-IFE Module The following configuration block transfer write file configures a 1771-IFE for: • differential operation (8 input channels) • each channel set for 1-5 VDC or 4-20 mA • two's complement binary data format •...

  • Page 41: Example: 1771-Ofe Module

    Creating Generic Modules in AbRioCfg 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 configbtw, 13 ; length 13 4, 0x8000 ;...
  • Page 42 Some modules have data underrange and overrange bits to indicate out of range inputs. • If the underrange or overrange bit is set, the 1757-ABRIO sets the I/O value to NaN. • If the module does not have overrange or underrange bits, leave those fields blank in the configuration file.

  • Page 43: Flag Data

    Creating Generic Modules in AbRioCfg • If the polarity bit is set, the 1757-ABRIO assigns the corresponding data a negative value. • The 1757 ABRIO uses the polarity offset and bit only for the BCD data type. It ignores them for the other data types.

  • Page 44: Example: 1771-Ife Module

    Creating Generic Modules in AbRioCfg 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.
  • Page 45 Creating Generic Modules in AbRioCfg BTW raw underrange, set if the calculated output value is less than the defined raw minimum. ABRIO clamps the output at the raw minimum. BTW raw overrange, set if the calculated output value is greater than the defined raw maximum.

  • Page 46: Sample 1771-Ife Configuration File

    3-10 Creating Generic Modules in AbRioCfg Sample 1771-IFE Configuration File configbtw, 21 ; length 21 2, 0x0500 ; differential inputs, binary 5, 0 6, 0x4095 ; channel 1 scaling 7, 0 8, 0x4095 ; channel 2 scaling 9, 0 10, 0x4095 ;...

  • Page 47: Numeric Data

    Creating Generic Modules in AbRioCfg 3-11 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 checks the number of values to be defined against the actual number of definitions and indicates an error if they do not match.

  • Page 48: Flag Data

    3-12 Creating Generic Modules in AbRioCfg The 1757 ABRIO 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.

  • Page 49: Sample 1771-Ofe Configuration File

    Creating Generic Modules in AbRioCfg 3-13 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.

  • Page 50: Creating A Generic Module In Abriocfg

    3-14 Creating Generic Modules in AbRioCfg To add a generic module in AbRioCfg: Creating a Generic Module in AbRioCfg 1. Right click on the rack to which the module will be added and select Add Module. 2. Select a Module Type of Generic Module, the location for the module and click OK.
  • Page 51 Creating Generic Modules in AbRioCfg 3-15 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.
  • Page 52 3-16 Creating Generic Modules in AbRioCfg Notes: Publication 1757-UM007C-EN-P - April 2004...

  • Page 53: Chapter 4 Introduction

    • ACTIVE (Run) • FORCED ACTIVE Two of the modes INACTIVE (Program) and ACTIVE (Run) relate to RIO network operations. The mode of the 1757-ABRIO module determines the RIO network mode. Modes related to RIO operations: • INACTIVE (Program) mode, digital inputs continue to update but digital outputs and block transfers do not.

  • Page 54: Inactive Mode

    FORCED ACTIVE mode by AbRioCfg. 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.

  • Page 55: Configure The 1757-Plx52

    Configuring ProcessLogix to Access Data on the 1757-ABRIO To access tag data on the 1757-ABRIO from a ProcessLogix controller, you Configure the 1757-PLX52 use REQNUMARRAY, REQFLAGARRAY and REQTEXTARRAY Exchange Blocks with CIPREAD and CIPWRITE commands to read and write tags.
  • Page 56 Configuring ProcessLogix to Access Data on the 1757-ABRIO 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 Figure 4.1 Array Examples Flag Arrays...
  • Page 57 Configuring ProcessLogix to Access Data on the 1757-ABRIO 10. Set the Path from the PLX to the 1757-ABRIO. Refer to page 5-16 or Control Builder Help for information on entering the path. 11. Set the FileName in the Exchange Blocks to the names of the tags you created in the 1757-ABRIO.
  • Page 58 Configuring ProcessLogix to Access Data on the 1757-ABRIO Figure 4.2 Live Data Examples Double-click function block Publication 1757-UM007C-EN-P - April 2004...

  • Page 59: Chapter 5 Introduction

    • ACTIVE (Run) • FORCED ACTIVE Two of the modes INACTIVE (Program) and ACTIVE (Run) relate to RIO network operations. The mode of the 1757-ABRIO module determines the RIO network mode. Modes related to RIO operations: • INACTIVE (Program) mode, digital inputs continue to update but digital outputs and block transfers do not.

  • Page 60: Inactive Mode

    FORCED ACTIVE mode by AbRioCfg. 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.

  • Page 61: Forced Active Mode

    Configuring ControlLogix to Access Data on the 1757-ABRIO 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 to the module. It is intended primarily for setting up and testing RIO systems.

  • Page 62: 1757-Abrio Scheduled Digital I/O Connections

    This section describes how to configure the module and describes the format of the scheduled data. When you add a 1757-ABRIO to the I/O Configuration of a ControlLogix using the generic 1757-MODULE profile, a data connection is created for the digital remote I/O data.

  • Page 63: Add A Module As An Exclusive Owner Connection

    Configuring ControlLogix to Access Data on the 1757-ABRIO processor Run or Program mode. If the owner ControlLogix processor is in Program Mode, the 1757-ABRIO is in program mode (even if the ABRIO is receiving messages). If the ControlLogix processor is in Remote Test mode, the remote I/O mode for the 1757-ABRIO is program.

  • Page 64: Output Priority

    Configuring ControlLogix to Access Data on the 1757-ABRIO 7. Set the Input Assembly Instance to 1 and the Input Size to 250. 8. Set the Output Assembly Instance to 2 and the Output Size to 248. 9. Set the Configuration Assembly Instance to 4 and the Configuration Size to 0.

  • Page 65: Setup Input Only Connections

    1757 ABRIO 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, you must be offline. 1. If you are creating a new project, select File New to create a new project, give the processor a name, and enter the slot it occupies in the ControlLogix rack.
  • Page 66 Configuring ControlLogix to Access Data on the 1757-ABRIO 8. Set the Output Assembly Instance to 3. 9. Set the Configuration Assembly Instance to 4 and the Configuration Size to 0. 10. Set the Status Input Assembly Instance to 5 and the Status Input Size to 11.
  • Page 67 Configuring ControlLogix to Access Data on the 1757-ABRIO 14. Click Finish to complete the module configuration. 15. Save the program and download it to the ControlLogix processor. All new tags associated with the 1757-ABRIO display. Refer to Tag Descriptions for...

  • Page 68: 1757-Abrio Unscheduled I/O Connections

    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. 1. Create Tags For All Messages and All Storage Areas Figure 5.6 RSLogix 5000 Example Tags in Program Mode...

  • Page 69: Create Message Commands To Read And Write All Rio Data

    2-13 for more information. Table 5.1 shows the source (write) or destination (read) data type to use with each 1757-ABRIO tag type and the size for each type. Table 5.1 ControlLogix Data types 1757-ABRIO tag Source/destination type Storage Data Size...
  • Page 70 2. Select the Message Type. The Message type should be either CIP Data Table Read to read a tag from the 1757-ABRIO or CIP Data Table Write to write a tag to the 1757-ABRIO. 3. Select the Source Element.
  • Page 71 5-13 If you are writing to the 1757-ABRIO, this is the ControlLogix tag. If you are reading from the 1757-ABRIO, this is the name of the tag in the 1757-ABRIO. If you are reading flag read tags using a ControlLogix IMPORTANT Processor, you must append [100] to the ABRIO tag name.
  • Page 72 5-14 Configuring ControlLogix to Access Data on the 1757-ABRIO Figure 5.8 1757-ABRIO Tag Name Example • Use this ABRIO Tag Name to flag read for status and digital data. This is the message needed to get to analog data. • If you are writing a tag from the 1757-ABRIO, this is the ControlLogix tag name.
  • Page 73 • When you are using scheduled connections in ControlLogix this will automatically be populated with your ABRIO name/address through an RSNetworx network polling. 7. Enter the path from the ControlLogix processor to the 1757-ABRIO module. AB Spares Publication 1757-UM007C-EN-P - April 2004...
  • Page 74 5-16 Configuring ControlLogix to Access Data on the 1757-ABRIO 8. If you need to manually input the communications path to a module, here is a general example of how to find the path to the rack you need to map to: Figure 5.10 RSLinx Communications Path...
  • Page 75 Configuring ControlLogix to Access Data on the 1757-ABRIO 5-17 9. Click OK to accept the MSG instruction. 10. After all message instructions are configured, save the program and download to the ControlLogix processor. Figure 5.11 Live Data Example AB Spares...
  • Page 76 5-18 Configuring ControlLogix to Access Data on the 1757-ABRIO Figure 5.12 Ladder Rung Example Publication 1757-UM007C-EN-P - April 2004...

  • Page 77: Accessing Data Through Opc/Dde

    • describes the operating modes of the 1757-ABRIO • describes how to access data on the module using OPC/DDE. You can access data on the 1757-ABRIO directly using a DDE or OPC server Accessing Data from such as RSLinx, without the intervention of a host processor.

  • Page 78: Accessing The Data

    Accessing Data through OPC/DDE If you are using a bridge device to communicate with the 1757-ABRIO, select Remote and configure the bridging. Refer to the RSLinx documentation for detailed information on how to configure bridging. 12. Click Done to accept the DDE/OPC topic.

  • Page 79: Monitoring The 1757-Abrio

    Chapter Monitoring the 1757-ABRIO This chapter provides the following information: Introduction • monitoring the operation of the 1757-ABRIO • monitoring the data value of tags • monitoring the status of a block transfer • monitoring the scanner log • interpreting fatal errors...

  • Page 80: Monitoring The Data Value Of Tags

    Clear Diag Counters button on the toolbar. If you attempt to monitor a tag that has not been downloaded to the 1757-ABRIO, AbRioCfg displays a message that indicates there is a Publication 1757-UM007C-EN-P - April 2004...

  • Page 81: Monitoring The Status Of A Block Transfer

    Monitoring the 1757-ABRIO configuration mismatch between the configuration in AbRioCfg and the configuration in the 1757-ABRIO. Use the same procedure to monitor digital and text data. To monitor the current status of a block transfer: Monitoring the Status of a Block Transfer 1.

  • Page 82: Monitoring The Scanner Log

    Running count of protocol errors for this block transfer write. The scanner log displays messages from the firmware running on the Monitoring the Scanner Log 1757-ABRIO, showing its normal operation and error messages. It may be useful in tracking down errors and for Technical Support. ⇒...

  • Page 83: Monitoring Diagnostic Counters

    This counter increments each time the 1757-ABRIO transmits a packet. RxGood This counter increments when the 1757-ABRIO receives a good packet. RxTout This counter increments when the 1757-ABRIO sends a packet but does not receive a reply. RxBadCRC This counter increments when the 1757-ABRIO receives a packet with a bad CRC.

  • Page 84: Fatal Errors

    This counter increments when the 1757-ABRIO receives a packet with a bad CRC from this rack. Tout This counter increments when the 1757-ABRIO 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 receives a packet from this rack that does not make sense in terms of the protocol.

  • Page 85: Supported 1771 Modules

    Introduction • lists the supported 1771 modules • describes module configuration, I/O Data, and diagnostic data The 1757-ABRIO supports all digital 1771 and the following 1771 block Module Description transfer modules. For information on how to communicate with other block transfer I/O modules, Refer to Chapter 3, Creating Generic Modules in AbRioCfg.

  • Page 86: 1771-Ife

    Supported 1771 Modules Refer to the following publications for information on installing and using the supported modules. Table 8.2 I/O Module Documentation Module Installation User Manual 1771-ASB 1771-UM001 1771-IFE 1771-5.46 1771-6.5.90 1771-5.45 1771-6.5.115 1771-OFE 1771-5.44 1771-6.5.30 1771-IR 1771-5.63 1771-6.5.76 1771-IXE/B 1771-5.64 1771-6.5.77 1771-IL...
  • Page 87 Supported 1771 Modules • module update time When you add a 1771-IFE module to a rack, the 1771-IFE Module dialog box appears. To configure the 1771-IFE: 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.

  • Page 88: I/O Data

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

  • Page 89: Diagnostic Data

    Supported 1771 Modules Table 8.4 IFE I/O Data Numeric Offset Description Channel 10 data (if applicable) Channel 11 data (if applicable) Channel 12 data (if applicable) Channel 13 data (if applicable) Channel 14 data (if applicable) Channel 15 data (if applicable) Channel 16 data (if applicable) You map this data to a numeric read tag.

  • Page 90: 1771-Ofe

    Channel 15 overrange Channel 16 overrange The Good Communication bit is set when the 1757-ABRIO 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.
  • Page 91 3. Set the LAST STATE jumper setting to match the jumpers on the 1771-OFE module. The setting can be one of Last, Min, Mid or Max. This value determines how the 1757-ABRIO responds to a loss of communication with the host processor. 4. Set the Update Time.

  • Page 92: I/O Data

    Channel 3 data invalid bit Channel 4 data invalid bit The good communication bit is set if the 1757-ABRIO 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.

  • Page 93: 1771-Ir

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

  • Page 94: I/O Data

    8-10 Supported 1771 Modules To configure the 1771-IR module: 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.

  • Page 95: Diagnostic Data

    Supported 1771 Modules 8-11 Diagnostic Data The 1771-IR returns 16 bits of diagnostic data to the host processor. Table 8.9 1771-IR Diagnostic Data Data Bit Description Module good communication Channel 1 underrange Channel 2 underrange Channel 3 underrange Channel 4 underrange Channel 5 underrange Channel 6 underrange reserved...
  • Page 96 8-12 Supported 1771 Modules • the gain and offset for each channel • if desired, the real-time sampling (RTS) rate for the module • the block transfer update time for the module When you add a 1771-IXE/B module to a rack, the 1771-IXE/B Module dialog box displays.

  • Page 97: I/O Data

    Supported 1771 Modules 8-13 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.

  • Page 98: 1771-Il

    8-14 Supported 1771 Modules Table 8.11 1771-IXE/B Diagnostic Data Description Channel 2 underrange Channel 3 underrange Channel 4 underrange Channel 5 underrange Channel 6 underrange Channel 7 underrange Channel 8 underrange Channel 1 overrange Channel 2 overrange Channel 3 overrange Channel 4 overrange Channel 5 overrange Channel 6 overrange...
  • Page 99 Supported 1771 Modules 8-15 • Optionally enabling real-time sampling and setting the sampling rate • Setting the update rate for the module block transfer read When you add a 1771-IL module to a rack, the 1771-IL Module dialog box displays. To configure the 1771-IL: 1.

  • Page 100: I/O Data

    8-16 Supported 1771 Modules 3. If desired, enable real-time sampling 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. 4. Set the Update Time for the module’s data. The range is 1 to 16382 milliseconds.

  • Page 101: 1771-Noc

    Supported 1771 Modules 8-17 Table 8.14 1771-IL Diagnostic Data Description RTS time-out Invalid filter reserved Hardware failure reserved Channel 1 underrange Channel 2 underrange Channel 3 underrange Channel 4 underrange Channel 5 underrange Channel 6 underrange Channel 7 underrange Channel 8 underrange Channel 1 overrange Channel 2 overrange Channel 3 overrange...
  • Page 102 This can be either Minimum, Maximum, Last State or User Value. This is the value the channel output will be if the 1771-NOC loses communication with the 1757-ABRIO or the host processor stops updating the tag to which the 1771-NOC’s data is mapped. If the Reset State is set to User Value, you must also enter a reset value.

  • Page 103: I/O Data

    Supported 1771 Modules 8-19 4. 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.

  • Page 104: 1771-Nov

    8-20 Supported 1771 Modules Table 8.16 1771-NOC Diagnostic Data Description reserved Channel 1 data invalid Channel 2 data invalid Channel 3 data invalid Channel 4 data invalid Channel 5 data invalid Channel 6 data invalid Channel 7 data invalid Channel 8 data invalid This data can be mapped to a flag read tag.
  • Page 105 This can be either Minimum, Maximum, Last State or User value. This is the value the channel output will be if the 1771-NOV loses communication with the 1757-ABRIO or the host processor stops updating the tag to which the 1771-NOV’s data is mapped.

  • Page 106: I/O Data

    8-22 Supported 1771 Modules 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;...

  • Page 107: 1771-Niv

    Supported 1771 Modules 8-23 Table 8.18 1771-NOV Diagnostic Data Description reserved reserved reserved Channel 1 data invalid Channel 2 data invalid Channel 3 data invalid Channel 4 data invalid Channel 5 data invalid Channel 6 data invalid Channel 7 data invalid Channel 8 data invalid This data can be mapped to a flag read tag.
  • Page 108 8-24 Supported 1771 Modules 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. 3. If desired, enable real-time sampling and set the sampling rate, from 0.1 to 10.0 seconds.

  • Page 109: I/O Data

    Supported 1771 Modules 8-25 I/O Data The 1771-NIV returns 8 words of floating point data to the host processor. Table 8.19 1771-NIV I/O Data Word Description Channel 1 data Channel 2 data Channel 3 data Channel 4 data Channel 5 data Channel 6 data Channel 7 data Channel 8 data...

  • Page 110: 1771-Nr

    8-26 Supported 1771 Modules Table 8.20 1771-NIV Diagnostic Data Description Channel 8 bad calibration Bad program Module fault Program verify 0 Program verify 1 I/O reset RTS time-out Mod alarm Bad channel data Channel 1 data Underrange Channel 2 data Underrange Channel 3 data Underrange Channel 4 data Underrange Channel 5 data Underrange...

  • Page 111: Module Configuration

    Supported 1771 Modules 8-27 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. Module Configuration Configuring the 1771-NR consists of: • setting the RTD type for each channel. For 10 ohm copper RTDs, you can enter an offset at 25C.

  • Page 112: I/O Data

    8-28 Supported 1771 Modules To configure a 1771-NR module: 1. Set the RTD type for each channel. 2. For any channels that are set to 10-ohms copper, set the offset at 25C. 3. Set the units of measurement for the temperature, either degrees Fahrenheit or Celsius.

  • Page 113: Diagnostic Data

    Supported 1771 Modules 8-29 Diagnostic Data The 1771-NR returns 40 bits of diagnostic data. Table 8.22 1771-NR Diagnostic Data Description Module good communication reserved reserved reserved reserved reserved reserved reserved Channel 1 bad calibration Channel 2 bad calibration Channel 3 bad calibration Channel 4 bad calibration Channel 5 bad calibration Channel 6 bad calibration...
  • Page 114 8-30 Supported 1771 Modules Table 8.22 1771-NR Diagnostic Data Description Channel 1 data Overrange Channel 2 data Overrange Channel 3 data Overrange Channel 4 data Overrange Channel 5 data Overrange Channel 6 data Overrange Channel 7 data Overrange Channel 8 data Overrange This data can be mapped to a flag read tag.

  • Page 115: Accessing Hart Data

    • send HART commands using ControlLogix messaging • access data through a 1771-HT1 module The 1757-ABRIO can send HART messages cyclically to devices on the Sending HART Commands HART network. Messages can be sent a single time using the configuration using ControlLogix MSG program AbRioCfg.
  • Page 116 Accessing HART Data The MSG Configuration dialog appears. 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. The Instance is entered in decimal. The low 4 bits of the Instance are always 0.

  • Page 117: Hart Command Data

    Accessing HART Data 13. Set the Destination to be the tag that will contain the reply to the HART message. HART Command Data The contents of the message are similar to what is described in the manual for the 1770-HT1, with some differences. You fill in the HART command in the Source Element tag.
  • Page 118 Accessing HART Data Table 9.2 Possible Types and Byte Counts Type Byte Count unit byte 3bytes float date text n where n < 4 and n < 64. The byte count is n * 3/4 • If either length is an odd number of bytes, round up to calculate the number of words.
  • Page 119 Accessing HART Data • 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 •...

  • Page 120: Reply Data

    Accessing HART Data 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. Table 9.3 Word High Byte Low Byte Channel - 1 Interface command, usually 10 Interface status Interface error...
  • Page 121 Accessing HART Data • 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. •...

  • Page 122: 1770-Ht1

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

  • Page 123: Rack Requirements

    Accessing HART Data • The 1757-ABRIO is intended to be used with HART input devices. It is not suitable for use with output devices. Rack Requirements The 1770-HT1 can be set for any rack number from 1 to 37 octal. The 1770-HT1 must be configured at starting I/O group 0.
  • Page 124 9-10 Accessing HART Data know are occupied. (For the 1770-HT, in the non-multiplex mode, Channels = HART devices connected to the 1770-HT8) If you have four HART devices connected to the 1770-HT8 then check Chan 1-4. 43281 2. Select those channels you want to search. 3.
  • Page 125 Accessing HART Data 9-11 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. To send a message to a device or add a cyclic command to a device: 1.
  • Page 126 9-12 Accessing HART Data The HART Command dialog box for that command appears. • If the Command has any required arguments, enter them in the Command Arguments area. • 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.
  • Page 127 Accessing HART Data 9-13 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 occupies an entire numeric read, flag read or text read tag.

  • Page 128: Hart Command Status

    9-14 Accessing HART Data 9. Save the configuration and download it to the 1757-ABRIO. Do not add write commands as cyclic commands HART Command status The HART command status byte contains the following bits. Table 9.6 HART Command Status Meaning...

  • Page 129: Troubleshooting

    Appendix Troubleshooting The 1757-ABRIO module has three LEDs that indicate the state of the LEDs network connection, the state of communication with the host processor, and the overall module health. These LEDs can be used in conjunction with the 4-character scrolling display and the monitor program to determine the cause of the problem.

  • Page 130: Ok Led - Module Health

    Troubleshooting OK LED - Module Health A bicolor OK LED indicates module health. A red LED indicates that module startup diagnostics have failed or a major module fault such as watchdog bite or jabber inhibit has occurred. Green indicates that the module has passed all power-up diagnostics and is functioning normally.

  • Page 131: Using The Configuration Program For Troubleshooting

    Monitor tags to see if the tag is being updated by the host processor and to see the values of the data that the 1757-ABRIO is sending to or receiving from the host processor. 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.

  • Page 132: Data 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 shows the rack. View the Scanner Log to see if there are any messages that indicate the source of the problem.

  • Page 133: General Tab

    Connection Tab The Inhibit Module checkbox breaks the exclusive ownership connection between the 1757-ABRIO and the CLX. If you would like to download to the ABRIO with out putting your controller in Program mode, check Inhibit Module. Once you are done updating the ABRIO, uncheck Inhibit Module and your connection will be re-established.

  • Page 134: Backplane Tab

    • The Status at the bottom of the screen indicates the Status status of the connection to the module. All communication between PLX and the 1757-ABRIO is via exchange blocks. Using Control Builder to If these exchange blocks are producing errors or do not seem to be working...

  • Page 135: Still Having A Problem

    1. Put processor (PLX or CLX) in program or inactive mode or check Inhibit Module in the Module Properties window, Connection tab in RSLogix 5000 (for CLX only). The 1757-ABRIO goes inactive. ⇒ 2. Put the ABRIO in Forced Active Mode, select Actions Forced Active Mode from the toolbar in 1757-AbRioCfg.
  • Page 136 Troubleshooting 8. Verify that the correct data is being written to the ABRIO from the processor using the same tag monitor screen in AbRioCfg. 9. Verify that data is being written correctly from the ABRIO to the processor by observing flag read data within RSLogix 5000 for a CLX or Control Builder for a PLX.

  • Page 137: Normal Operational Messages

    Appendix Operational Comparison Between the 1757-ABRIO and PLC-5 The 1757-ABRIO is designed to respond, as much as possible, like a PLC-5 Normal Operational system. In PLC-5 applications, all I/O modules are physically configured for Messages safe state if the PLC-5 is in Program or Fault mode.
  • Page 138 Operational Comparison Between the 1757-ABRIO and PLC-5 Table B.1 Equivalent PLC Modes ABRIO PLC-5 Description ACTIVE 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.
  • Page 139 Operational Comparison Between the 1757-ABRIO and PLC-5 Table B.2 Normal Operational Comparison Between the PLC-5 and the 1757-ABRIO 1757-ABRIO ACTIVE or From the PLC-5 Perspective From the 1757-ABRIO Perspective PLC-5 RUN Modes digital inputs digital output data updates. Data update in the PLC...

  • Page 140: Exception Handling Messages

    These health bits are included in the “Tag” along with the channel states. In addition, the 1757-ABRIO 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.
  • Page 141 Operational Comparison Between the 1757-ABRIO and PLC-5 Table B.3 Exception Conditions Comparison Between the PLC-5 and the 1757-ABRIO Exception Condition Message From 1757-ABRIO Perspective From the PLC-5 Perspective • Good communication bit for the rack is • Status bit for the rack is cleared...
  • Page 142 Operational Comparison Between the 1757-ABRIO and PLC-5 Table B.3 Exception Conditions Comparison Between the PLC-5 and the 1757-ABRIO Exception Condition Message From 1757-ABRIO Perspective From the PLC-5 Perspective • 1757-ABRIO sets block transfer write data • N/A Numeric write tag times out mapped to the tag to the state set by the user in the module configuration.

  • Page 143: Configuration Tag

    Status tag Configuration Tag The configuration tag gets created when you configure the 1757-ABRIO as a 1756-MODULE, but the contents of the configuration tag are not used by the 1757-ABRIO. I and O Tags The I and O tags are associated with the digital I/O data.

  • Page 144: Publication 1757-Um007C-En-P - April

    Tag Descriptions for ControlLogix Scheduled Data Table C.2 Input Tags Address Description Local:<slot>:I.Data[17] Rack 2, I/O group 7 inputs 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 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...

  • Page 145: 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 and is not communicating, and are 0 otherwise. If any configured rack is not communicating, the global status is set.
  • Page 146 Tag Descriptions for ControlLogix Scheduled Data Table C.4 Status Tag Address Description Local:<slot>:S.Data[3].8 Rack 6, I/O group 0 error Local:<slot>:S.Data[3].9 Rack 6, I/O group 2 error Local:<slot>:S.Data[3].10 Rack 6, I/O group 4 error Local:<slot>:S.Data[3].11 Rack 6, I/O group 6 error Local:<slot>:S.Data[3].12 Rack 7, I/O group 0 error Local:<slot>:S.Data[3].13...
  • Page 147 Tag Descriptions for ControlLogix Scheduled Data Table C.4 Status Tag Address Description Local:<slot>:S.Data[5].12 Rack 17 octal, I/O group 0 error Local:<slot>:S.Data[5].13 Rack 17 octal, I/O group 2 error Local:<slot>:S.Data[5].14 Rack 17 octal, I/O group 4 error Local:<slot>:S.Data[5].15 Rack 17 octal, I/O group 6 error Local:<slot>:S.Data[6].0 Rack 20 octal, I/O group 0 error Local:<slot>:S.Data[6].1...
  • Page 148 Tag Descriptions for ControlLogix Scheduled Data Table C.4 Status Tag Address Description Local:<slot>:S.Data[8].0 Rack 30 octal, I/O group 0 error Local:<slot>:S.Data[8].1 Rack 30 octal, I/O group 2 error Local:<slot>:S.Data[8].2 Rack 30 octal, I/O group 4 error Local:<slot>:S.Data[8].3 Rack 30 octal, I/O group 6 error Local:<slot>:S.Data[8].4 Rack 31 octal, I/O group 0 error Local:<slot>:S.Data[8].5...

  • Page 149: Appendix D Specifications

    Appendix Specifications The 1757-ABRIO is a standard ControlBus module with the following specifications: Parameter Specification Module Location ProcessLogix or ControlLogix chassis Maximum Backplane Current Load 675 mA @ +5.1V DC and 5 mA @ 24 V DC from I/O chassis backplane...
  • Page 150 Specifications Parameter Specification User Manual Publication 1757-UM007 Enclosure Type Rating None (open-style) Certifications: c-UL-us UL Listed Industrial Control Equipment, certified for US and (when product is marked) Canada CSA Certified Process Control Equipment for Class I, Division 2 Group A,B,C,D Hazardous Locations European Union 89/336/EEC EMC Directive, compliant with: EN 61000-6-4;...
  • Page 151 ___Yes, please call me ___Yes, please email me at __________________________ ___Yes, please contact me via ________________________ Return this form to: Allen-Bradley Marketing Communications, 1 Allen-Bradley Dr., Muffled Hts., OH 44124-9705 Phone: 440-646-3176 Fax: 440-646-3525 Email: RADocumentComments@ra.rockwell.com AB Spares Publication ICCG-5.21- January 2001...
  • Page 152 PLEASE FASTEN HERE (DO NOT STAPLE) Other Comments PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE 1 ALLEN-BRADLEY DR MAYFIELD HEIGHTS OH 44124-9705...
  • Page 153 AB Spares...

  • Page 154: Rockwell Automation Support

    Rockwell Automation provides technical information on the web to assist you in using Rockwell Automation our products. At http://support.rockwellautomation.com, you can find technical Support 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.
  • Page 155 AB Spares...

Table of Contents