Beruflich Dokumente
Kultur Dokumente
User Manual
(Catalog Number 1757-ABRIO)
IMPORTANT
ATTENTION
Identifies information that is critical for successful application and understanding of the product.
Identifies information about practices or circumstances that can lead to personal injury or death,
property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and
recognize the consequence
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.
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.
Table of Contents
Preface
Chapter 1
Introduction
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process Remote I/O (RIO) Communication Interface Module
RSLinx Software Requirements. . . . . . . . . . . . . . . . . . . . . . .
ProcessLogix System Quick Start . . . . . . . . . . . . . . . . . . . . .
RSLogix 5000 System Quick Start . . . . . . . . . . . . . . . . . . . . .
Update the 1757-ABRIO Modules Firmware. . . . . . . . . . . . .
Using ControlFlash Software. . . . . . . . . . . . . . . . . . . . . .
Using NTools with ProcessLogix Software . . . . . . . . . . . .
. 9
. 9
10
11
12
14
14
15
Chapter 2
Configure the 1757-ABRIO Module Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
AbRioCfg Software Overview. . . . . . . . . . . .
Mapping and Accessing RIO Network Data .
Installing AbRioCfg Software . . . . . . . . . . . .
Autoconfigure the I/O Racks . . . . . . . . . . . .
Adding Block Transfer Modules. . . . . . . . . .
Addressing Modes for 1771 . . . . . . . . . .
Configuring Block Transfer Modules . . . . . .
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input Scaling . . . . . . . . . . . . . . . . . . . . .
Output Scaling. . . . . . . . . . . . . . . . . . . .
Tags Defined . . . . . . . . . . . . . . . . . . . . . . .
Create a Tag . . . . . . . . . . . . . . . . . . . . .
Mapping Data to Tags in AbRioCfg Software
Block Transfers . . . . . . . . . . . . . . . . . . .
I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Mapped Data . . . . . . . . . . . . . .
Tips for Configuring Modules . . . . . . . . . . .
Add Racks Offline . . . . . . . . . . . . . . . . .
Delete Racks Offline . . . . . . . . . . . . . . .
Change the Baud Rate Offline . . . . . . . .
Download the Configuration . . . . . . . . . . . .
Upload the Configuration . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
17
18
19
19
23
24
25
26
26
27
28
30
31
31
32
32
32
33
34
35
35
36
Table of Contents
Chapter 3
Creating Generic Modules in
AbRioCfg Software
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generic Module Overview. . . . . . . . . . . . . . . . . .
Generic Module Configuration File . . . . . . . . . . .
Configuration Block Transfer Write. . . . . . . . .
Data Block Transfer Read. . . . . . . . . . . . . . . .
Data Block Transfer Write . . . . . . . . . . . . . . .
Creating a Generic Module in AbRioCfg software .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
37
37
38
38
41
45
48
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
51
51
51
52
52
52
53
Chapter 4
Configuring the ProcessLogix
Controller to Access Data on the
1757-ABRIO Module
Introduction . . . . . . . . . . . . . . . . . . .
Modes of Operation . . . . . . . . . . . . .
CONFIG Mode. . . . . . . . . . . . . . .
INACTIVE Mode . . . . . . . . . . . . .
ACTIVE Mode (Run) . . . . . . . . . .
FORCED ACTIVE Mode . . . . . . . .
Configure the 1757-PLX52 Controller .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 5
Configuring RSLogix 5000
Software to Access Data on the
1757-ABRIO Module
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
CONFIG Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
INACTIVE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
ACTIVE Mode (Run) . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
FORCED ACTIVE Mode . . . . . . . . . . . . . . . . . . . . . . . . . 59
Scheduled Digital I/O Connections in RSLogix 5000 Programs .
60
Scheduled Connection Types . . . . . . . . . . . . . . . . . . . . . 60
Setup an Exclusive-owner Connection . . . . . . . . . . . . . . 60
Setup Input-only Connections . . . . . . . . . . . . . . . . . . . . 63
Unscheduled I/O Connections in ControlLogix. . . . . . . . . . . 67
Create Message Commands to Read and Write All RIO
Network Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Chapter 6
Accessing Data through a DDE or
OPC Server
Introduction . . . . . . . . . . . . . . . . . . . . . . .
Accessing Data from a DDE or OPC Server
Configuring a Topic in RSLinx Software
Accessing the Data. . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
75
75
75
76
Table of Contents
Chapter 7
Monitoring the 1757-ABRIO
Module
Introduction . . . . . . . . . . . . . . . . . . . . . .
Monitoring the Operation . . . . . . . . . . . .
Monitoring Digital I/O. . . . . . . . . . . . . . .
Monitoring the Data Value of Tags. . . . . .
Monitoring the Status of a Block Transfer.
Monitoring the Scanner Log. . . . . . . . . . .
Monitoring Diagnostic Counters. . . . . . . .
Active Rack List . . . . . . . . . . . . . . . . .
Global Diagnostic Counters . . . . . . . .
Fatal Errors . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
77
77
77
78
79
80
81
81
81
82
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
83
83
84
85
87
87
89
89
90
91
92
92
94
94
95
95
96
97
98
98
99
100
101
101
102
103
104
104
105
106
Chapter 8
Supported 1771 Modules
Introduction . . . . . . . . . .
Module Description. . . . .
1771-IFE Module. . . . . . .
Module Configuration
I/O Data . . . . . . . . . .
Diagnostic Data . . . . .
1771-OFE Module . . . . . .
Module Configuration
I/O Data . . . . . . . . . .
Diagnostic Data . . . . .
1771-IR Module. . . . . . . .
Module Configuration
I/O Data . . . . . . . . . .
Diagnostic Data . . . . .
1771-IXE Module . . . . . .
Module Configuration
I/O Data . . . . . . . . . .
Diagnostic Data . . . . .
1771-IL Module . . . . . . . .
Module Configuration
I/O Data . . . . . . . . . .
Diagnostic Data . . . . .
1771-NOC Module . . . . .
Module Configuration
I/O Data . . . . . . . . . .
Diagnostic Data . . . . .
1771-NOV Module . . . . .
Module Configuration
I/O Data . . . . . . . . . .
Diagnostic Data . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Table of Contents
1771-NIV Module . . . . . .
Module Configuration
I/O Data . . . . . . . . . .
Diagnostic Data . . . . .
1771-NR Module . . . . . . .
Module Configuration
I/O Data . . . . . . . . . .
Diagnostic Data . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
107
107
108
109
110
111
113
113
Chapter 9
Accessing HART Data
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Sending HART Commands Using RSLogix 5000 Software MSG .
115
HART Command Data . . . . . . . . . . . . . . . . . . . . . . . . . 117
Reply Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Example: HART Command 36 . . . . . . . . . . . . . . . . . . . 122
1770-HT1 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Rack Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Configuring the 1770-HT1 Module . . . . . . . . . . . . . . . . 124
HART Command status . . . . . . . . . . . . . . . . . . . . . . . . 129
Appendix A
Specifications
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Appendix B
Troubleshooting
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
133
133
133
134
134
134
135
136
137
138
138
138
139
139
140
140
Table of Contents
Appendix C
Operational Comparison Between Normal Operational Messages . . . . . . . . . . . . . . . . . . . . . .
Exception Handling Messages . . . . . . . . . . . . . . . . . . . . . .
the 1757-ABRIO Module and a
PLC-5 System
Appendix D
Tag Descriptions for Scheduled
Configuration Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I and O Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data in RSLogix 5000 Software
143
145
149
149
Status Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Table of Contents
Preface
Additional Resources
Description
Industrial Automation Wiring and Grounding Provides general guidelines for installing a
Guidelines, publication 1770-4.1
Rockwell Automation industrial system.
Product Certifications website,
http://ab.com
Table of Contents
Preface
Chapter
Introduction
Introduction
This chapter:
describes the 1757-ABRIO Remote I/O Module.
lists the RSLinx software requirements.
provides update procedures for the modules firmware.
This document is a user guide for the 1757-ABRIO module, which lets
Rockwell Automation controllers (ProcessLogix or ControlLogix)
communicate with Allen-Bradley remote I/O. The module acts as a
RIO network scanner. The 1757-ABRIO module facilitates connection
to analog and discrete I/O devices as well as any block transfer
modules.
1757-ABRIO Module Example Topology
ProcessLogix
System Server
ControlNet Network
Data Highway + Network
PLC5
Controller
ControlNet
Network
SLC Controller
Flex Ex Modules
PLC5/C
Controller
43290
Drive
Supports
Block
Transfers limit of 32
words in a
block
Chapter 1
Introduction
RSLinx Software
Requirements
10
Introduction
Chapter 1
11
Chapter 1
Introduction
12
Introduction
Chapter 1
13
Chapter 1
Introduction
14
Introduction
Chapter 1
15
Chapter 1
Introduction
16
Chapter
Introduction
This chapter:
provides an overview of the AbRioCfg software.
gives an introduction to mapping and accessing RIO network
data.
explains how to install the AbRioCfg software.
explains how to autoconfigure I/O racks.
explains how to add and configure block transfer modules.
AbRioCfg Software
Overview
17
Chapter 2
Use the provided AbRioCfg software to create tags which are arrays of
digital, floating point or text values that the host controller reads or
writes using unscheduled messages.
You map data that the module receives or sends into these tags. The
data mapping is stored in flash memory on the 1757-ABRIO module.
The 1757-ABRIO Module and Data Mapping
1757-ABRIO Module
Tag
Write Data
Tag
Read Data
ControlLogix or
ProcessLogix
Controller
Scan
List
WARNING
18
RIO Network
Remote I/O
Remote I/O
Modules
Modules
Analog/Digital Modules
Hard Configured for Safe/Fault States
Installing AbRioCfg
Software
Chapter 2
TIP
19
Chapter 2
With AbRioCfg software, 2.0 and higher, you can also manually
configure the I/O racks in your network. Refer to Add Racks
Offline on page 33 for more information.
20
Chapter 2
21
Chapter 2
If you expand a rack, the partial racks that make up that rack
number are displayed.
22
Chapter 2
b. Select the value that matches the Last State switch setting in
the backplane of the I/O chassis, either De-energize or Hold
Last State.
This setting tells the 1757-ABRIO module what to do if the
controller stops updating the tag to which this chassiss digital
data is mapped.
c. Repeat steps 7a and 7b for all racks that contain 1771 remote
I/O modules.
23
Chapter 2
10
11
12
13
14
15
Rack
I/O Group
Slot
10
11
12
13
14
15
Rack
I/O Group
Slot
24
Chapter 2
10
11
12
13
14
15
Rack
I/O Group
Slot
TIP
When you add a block transfer module, the configuration dialog box
for that module opens. The contents of the dialog box are specific to
each module type.
25
Chapter 2
Scaling
Input Scaling
For analog input modules, you must supply the floating point values
to which you want the minimum and maximum raw data scaled.
Minimum corresponds to the lowest raw value.
Maximum corresponds to the maximum raw value.
EXAMPLE
26
Chapter 2
Output Scaling
For output modules, you supply the floating point values you want to
correspond to the minimum and maximum raw output values.
ATTENTION
The minimum scale value may not be larger than the maximum
scale value
EXAMPLE
27
Chapter 2
Tags Defined
28
Chapter 2
29
Chapter 2
Create a Tag
If you are planning to use automatic digital tags via a scheduled
connection to the 1757-ABRIO module from a ControlLogix controller,
do not create tags. Refer to Scheduled Digital I/O Connections in
RSLogix 5000 Programs on page 60. For all other tag types (analog,
text) and unscheduled connections, tags must be manually created.
To create a tag, complete the following steps.
1. Select the appropriate tab for the type of tag you want to create.
2. Right-click the root of the tree in the tag area and select Add
Tag.
The Add a Tag dialog box opens.
30
Chapter 2
Block Transfers
When mapping block transfer modules, drag the analog module from
the network tree to the location in the tag where you want the data to
be located.
Block transfer read data can be mapped to numeric read tags.
Block transfer write data can be mapped to numeric write tags.
You cannot map individual registers; all the data for a rack or I/O
module is mapped to the tag. You can map data from many I/O
modules into the same tag.
Mappings must be unique. You cannot map a block transfer module
to more than one tag of the same type or to multiple locations within
the same tag.
In addition, block transfer modules have status information that can
be mapped to flag read tags. Refer to Supported 1771 Modules on
page 83 for detailed information on status information.
31
Chapter 2
I/O
To map I/O data to a tag, complete the following steps.
1. Expand the tag to show the tag elements.
2. Scroll to display the destination in the tag where you want to
add the data.
3. Drag the rack or block transfer module to the desired location in
the tag.
Use the largest range of raw values possible for the 1757-ABRIO
module and optimum data resolution. The scaling should be done to
engineering units in the module.
The following operations are features of firmware version 2.1. To use
these features, you need the following:
Firmware version 2.1 or above for the 1757-ABRIO module
AbRioCfg software version 2.0 or above
AbRioCfg software version 2.0 or above can open or upload
configurations made with previous versions of AbRioCfg
software.
32
Chapter 2
33
Chapter 2
2. Click OK.
When you delete a rack, all I/O modules on the rack and flag
mappings for the rack are deleted. If this partial rack is the only one in
the rack number, the rack number will be deleted from the tree.
34
Chapter 2
Download the
Configuration
WARNING
35
Chapter 2
36
Chapter
Introduction
37
Chapter 3
Generic Module
Configuration File
To use a text file, separate the data fields with commas. To use a
spreadsheet, put the data values in separate columns.
TIP
Sample configuration files are available for your use. The files
are located in the \GenProfile directory on the supplied
1757-ABRIO CD.
configbtw, 13
38
Chapter 3
The offset is the offset into the block transfer and ranges from 0 to the
block transfer length - 1. For example, if the block transfer is 10 words
long, the allowed offsets range from 0 to 9.
The value can be in one of the following formats:
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. It's usually easier and less prone to error to enter the
values in binary or hexadecimal.
TIP
EXAMPLE
39
Chapter 3
40
Chapter 3
1
2
3
4
databtr, 15
Numeric Data
The numeric section of the data block transfer read defines the I/O
data - its location, format, and scaling.
The beginning of the numeric section is marked by the keyword
numeric, followed by the number of values to be defined, and the
data format.
41
Chapter 3
Range of values
BCD
0 to 9999
Unsigned
0 to 65535
Integer
-32768 to 32767
numeric, 4, BCD
numeric, 8, integer
This is followed by definitions for the I/O data values, each on a row
of the spreadsheet (or line of a text file). Each definition consists of
the following fields:
Quantity
Description
BTR offset
Offset into BTR data The BTR offset is the offset into
the BTR data for the I/O data value
Underrange offset(1)
Underrange bit
Overrange offset(1)
Overrange bit
Polarity offset(1)
Polarity bit
(1)
If the offset is not used, the field must be left blank (not 0).
42
Chapter 3
Flag Data
In some cases the block transfer read contains data that we want to
map to flag read tags, for example, a module error bit. If a module has
flag data defined, you can then map it to flag read data in AbRioCfg
software.
The flag data section of the Data Block Transfer read defines the
location of this discrete data.
The beginning of the flag section is marked by a line containing the
keyword flag, followed by the total length of the flags data, in bits.
The length must be a multiple of 8.
EXAMPLE
flag, 32
This is followed by a number of lines that define where the flag data
is found. Each line consists of an offset and a length. The maximum
number of flag data definition lines is 4.
Publication 1757-UM007D-EN-P - December 2008
43
Chapter 3
The offset is an offset into the block transfer. It can range from 0 to
the length of the block transfer - 1. If the offset is followed by an H,
it refers to the high byte of the block transfer word. The length can
range from 8 to 504 and must be a multiple of 8. The sum of the
lengths in the data definitions must match the length in the flag line.
flag, 32
EXAMPLE
0,8
2H,8
4,16
44
Bit
Description
BTR Raw underrange bit, set if the raw input to the module is less than the
defined raw minimum. The module sets the scaled input to NaN.
BTR raw overrange, set if the raw input to the module is greater than the
defined raw maximum. The module sets the scaled input to NaN.
Reserved
Reserved
BTW raw underrange, set if the calculated output value is less than the
defined raw minimum. The module clamps the output at the raw minimum.
BTW raw overrange, set if the calculated output value is greater than the
defined raw maximum. The module clamps the value at the raw maximum.
BTW NaN, set if the floating point value written from the host is NaN.
Chapter 3
databtw, 12
45
Chapter 3
Numeric Data
The numeric section of the data block transfer write defines the I/O
data - its location, format, and scaling.
The beginning of the numeric section is marked by the keyword
numeric, the number of values to be defined, and the data format.
AbRioCfg software checks the number of values to be defined against
the actual number of definitions and indicates an error if they do not
match.
The format can be one of the following.
Format
Range of values
BCD
0 to 9999
Unsigned
0 to 65535
Integer
-32768 to 32767
numeric, 4, BCD
numeric, 8, integer
This line is followed by definitions for the I/O data values, each on a
row of the spreadsheet (or line of a text file). Each definition consists
of the following fields:
Quantity
Description
BTW offset
Polarity offset
Polarity bit
The BTW offset is the offset into the BTW data for the I/O data value.
Some modules have a separate polarity bit to indicate the sign of an
input. If the data being written is negative, the 1757-ABRIO module
sets the polarity bit.
46
Chapter 3
The 1757-ABRIO module uses the polarity offset and bit only for the
BCD data type. It ignores them for the other data types.
TIP
If the data type is BCD, enter the raw minimum and maximum
values in decimal, not hexadecimal. For example is the range is
0 to 9999, enter the value as 9999, not 0x9999.
If the scaled valued written is NaN, the raw output gets set to the
corresponding value in the configuration data. For example, if an I/O
data value is at offset 7 in the data block transfer write, the value at
offset 7 in the configuration block transfer write is written if the host
controller writes NaN to the tag that is mapped to the I/O value.
EXAMPLE
0 0 4095 0 1000
Flag Data
In some cases the block transfer write contains data that we want to
map to flag write tags.
The flag data section of the Data Block Transfer write defines the
location of this discrete data.
The beginning of the flag section is marked by a line containing the
keyword flag, followed by the total length of the flags data, in bits.
The length can be from 8 to 504 and must be a multiple of 8.
EXAMPLE
flag, 32
This is followed by a number of lines that define where the flag data
is found. Each line consists of an offset and a length. The maximum
number of flag definition lines is 4.
The offset is an offset into the block transfer. It can range from 0 to
the length of the block transfer - 1. If the offset is followed by an H,
it refers to the high byte of the block transfer word.
The length can range from 8 to 504 and must be a multiple of 8.
Publication 1757-UM007D-EN-P - December 2008
47
Chapter 3
The sum of the lengths in the data definitions must match the length
in the flag line.
EXAMPLE
flag, 32
0,8
2H,8
4,16
format
value channel
value channel
value channel
value channel
1
2
3
4
48
Chapter 3
3. Browse to or type the CSV file and path and click Import.
AbRioCfg software imports the configuration file and displays
the contents, or gives an error message if it finds problems with
the file.
4. Assign values for the BTR and BTW Update Times.
5. Click OK to accept the module.
You can now map the data to tags by dragging the Generic module to
the desired numeric read, numeric write, flag read or flag write tag.
To change the configuration, re-import the configuration. If the
generic module was mapped to tags, the mappings will be deleted
and must be reassigned.
49
Chapter 3
50
Chapter
Introduction
Modes of Operation
CONFIG Mode
The module is in CONFIG mode while AbRioCfg software downloads
a configuration. CONFIG mode is largely invisible to the user unless
the configuration being downloaded is large. After downloading, the
software returns the module to INACTIVE mode.
51
Chapter 4
INACTIVE Mode
The module is in INACTIVE mode when it is not receiving messages
from either a host controller or via OPC/DDE. The module is also in
INACTIVE mode when it has not been put in FORCED ACTIVE mode
by AbRioCfg software.
When the module is in INACTIVE mode, the RIO network is placed in
program mode with input updates but no output updates. The
1757-ABRIO module must be in the INACTIVE mode to accept a
download.
52
Chapter 4
53
Chapter 4
Numeric Arrays
Text Arrays
10. Set the Path from the ProcessLogix controller to the 1757-ABRIO
module.
See the tip on page 72 or Control Builder Help for information
on entering the path.
54
Chapter 4
11. Set the File Name in the Exchange Blocks to the names of the
tags you created in the 1757-ABRIO module.
12. Perform any other configuration required by your application on
the other tabs.
IMPORTANT
55
Chapter 4
56
Chapter
Introduction
Modes of Operation
CONFIG Mode
The module is in CONFIG mode while AbRioCfg software downloads
a configuration. CONFIG mode is largely invisible to the user unless
the configuration being downloaded is large. After downloading, the
software returns the module to INACTIVE mode.
57
Chapter 5
INACTIVE Mode
The module is in INACTIVE mode when it is not receiving messages
from either a host controller or via OPC/DDE. The module is also in
INACTIVE mode when it has not been put in FORCED ACTIVE mode
by AbRioCfg software.
When the module is in INACTIVE mode, the RIO network is placed in
program mode with input updates but no output updates. The
1757-ABRIO module must be in the INACTIVE mode to accept a
download.
When scheduled connections are used, the 1757-ABRIO modules
mode will always follow the ControlLogix controllers mode regardless
if it is receiving messages. For example, when the controller is in
PROGRAM mode, the module is in INACTIVE mode.
58
Chapter 5
59
Chapter 5
60
Chapter 5
61
Chapter 5
Size
Input
250
Output
248
Configuration
Status Input
10
Status Output
N/A
62
Chapter 5
Output Priority
If a digital rack is mapped to a flag write tag in the AbRioCfg software,
the flag data takes precedence over the digital outputs in the
scheduled connection, even if nothing is writing to the flag write tag.
To control outputs on a chassis using a scheduled connection, make
sure the chassis is not mapped to a flag write tag.
63
Chapter 5
64
Assembly
Instance
Size
Input
250
Output
N/A
Configuration
Status Input
10
Status Output
N/A
Chapter 5
65
Chapter 5
66
Unscheduled I/O
Connections in
ControlLogix
Chapter 5
There are several tasks you need to complete before you can access
data from ControlLogix. You need to create the following:
Tags for messages
Tags for storage areas
Message commands to read RIO network data
Message commands to write RIO network data
Use RSLogix 5000 message instructions (MSG) to access tags on the
1757-ABRIO module. Refer to RSLogix 5000 Online Help and the
Logix5000 Controllers General Instructions Reference Manual,
publication 1756-RM003, for details on messages.
Before you create the MSG instruction, create a tag of type MESSAGE
to act as a control for the MSG instruction. You must also create a
source (write) or destination (read) tag for the data written to or read
from the 1757-ABRIO module.
67
Chapter 5
This table shows the source (write) or destination (read) data type to
use with each 1757-ABRIO tag type and the size for each type.
ControlLogix Data types
68
1757-ABRIO Tag
Source/destination Type
Numeric read
REAL
64
Numeric write
REAL
64
Flag read
DINT
16
Flag Write
DINT
16
Text read
SINT
64
Chapter 5
WARNING
69
Chapter 5
To
All_Analog_Read
All_Flag_Read[100]
IMPORTANT
70
Chapter 5
71
Chapter 5
If you need to manually input the communications path to a module, follow this
general example of how to find the path to the rack.
TIP
72
Chapter 5
73
Chapter 5
74
Chapter
Introduction
This chapter describes how to access data on the module using a DDE
or OPC Server.
You can access data on the 1757-ABRIO module directly using a DDE
or OPC server such as RSLinx software, without the intervention of a
host controller.
75
Chapter 6
76
Chapter
Introduction
The AbRioCfg software lets you monitor the operation of the module
and perform maintenance operations. Tag, block transfer, and module
diagnostic counters are available only from AbRioCfg software, and
are not available to a ProcessLogix or ControlLogix controller.
AbRioCfg software can be used to:
display the current values of the digital inputs and outputs.
display the current values of block transfer data, along with
diagnostic information on the block transfer.
display the current contents of a tag.
display the module log, which consists of messages from the
firmware running on the module.
clear the log.
copy the contents of the log to the clipboard for use by another
application. This is often useful for technical support.
clear fatal errors and dump the fatal error log to a file for use by
technical support.
77
Chapter 7
Use the Edit>Write toolbar button or the menu item to enable editing.
You can now change any data and it will be written to the network
(outputs) or to the data table (inputs). However if the same data is
being updated by I/O modules or the controller, the value you write is
overwritten the next time this I/O module is scanned.
Description
Tag Name
Command
Read or write
Type
MsgNum
Len
Tag length, units are bytes for flag and text tags, floats for
numeric tags
Req count
Average update time for this tag, in ms. This is the average of
the previous 64 updates.
Time out
Status
Active or Inactive
78
Chapter 7
If you attempt to monitor a tag that has not been downloaded to the
1757-ABRIO module, AbRioCfg software displays a message that
indicates there is a configuration mismatch between the configuration
in AbRioCfg software and the configuration in the 1757-ABRIO
module.
TIP
Counter
Description
State
Active/Inactive
Type
Module type
BTR Len
Average update time for this block transfer read, in ms. This
is the average of the previous 8 updates.
Update Count
79
Chapter 7
Description
Ignored Req
Prot Errors
Request Count
Counter
Description
CFG len
data length
Average update time for this block transfer write, in ms. This
is the average of the previous 8 updates.
Update Count
Ignored Req
Prot Errs
80
Monitoring Diagnostic
Counters
Chapter 7
Counter
Description
Tx
RxGood
RxTout
RxBadCRC
RxNoise
RxAbort
PrtclErr
UpdAvg
Average update time for all configured racks. This is the average of the
previous 64 updates.
UpdMin
UpdMax
81
Chapter 7
Fatal Errors
Counter
Description
Rx
Crc
Tout
Prtcl
82
Chapter
Introduction
This chapter:
lists the supported 1771 modules.
describes module configuration, I/O Data, and diagnostic data.
Module Description
The 1757-ABRIO module supports all digital 1771 modules and the
following 1771 block transfer modules. For information on how to
communicate with other block transfer I/O modules, see Creating
Generic Modules in AbRioCfg Software on page 37.
Refer to the corresponding pages in this chapter for information about
configuring these modules with the 1757-ABRIO module.
Supported modules
Module
Description
Page
1771-IFE
84
1771-OFE
89
1771-IR
92
1771-IXE
Thermocouple/millivolt module
95
1771-IL
98
1771-NOC
101
1771-NIV
107
1771-NOV
104
1771-NR
110
83
Chapter 8
1771-IFE Module
Module
Installation Instructions
User Manual
1771-ASB
NA
1771-UM001
1771-IFE
1771-5.45
1771-6.5.90
1771-6.5.115
1771-OFE
1771-IN044
1771-6.5.30
1771-IR
1771-5.63
1771-6.5.76
1771-IXE
1771-5.64
1771-6.5.130
1771-IL
1771-5.62
1771-6.5.91
1771-NOC
NA
1771-UM127
1771-NIV
NA
1771-UM127
1771-NOV
NA
1771-UM127
1771-NR
NA
1771-UM127
1770-HT1
NA
1770-6.5.19
4 to 20 mA
0 to 5 VDC
0 to 20 mA
-5 to 5 VDC
-20 to 20 mA
-10 to 10 VDC
84
Chapter 8
Module Configuration
Configuring the 1771-IFE module consists of setting the following:
single-ended or differential operation
range and scaling for each channel
digital filter and time constant
real time sampling and time constant
module update time
When you add a 1771-IFE module to a rack, the 1771-IFE Module
dialog box opens.
85
Chapter 8
86
Chapter 8
I/O Data
The 1771-IFE module returns the 8 or 16 words of floating point data
to the host controller, depending on whether the module is
configured for single-ended or differential operation.
IFE I/O Data
Numeric Offset
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
10
11
12
13
14
15
Diagnostic Data
The 1771-IFE module has 40-bits of diagnostic data that can be
mapped to a flag read tag.
IFE Diagnostic Data
Bit
Description
Channel 1 underrange
Channel 2 underrange
10
Channel 3 underrange
11
Channel 4 underrange
87
Chapter 8
Description
12
Channel 5 underrange
13
Channel 6 underrange
14
Channel 7 underrange
15
Channel 8 underrange
16
Channel 9 underrange
17
Channel 10 underrange
18
Channel 11 underrange
19
Channel 12 underrange
20
Channel 13 underrange
21
Channel 14 underrange
22
Channel 15 underrange
23
Channel 16 underrange
24
Channel 1 overrange
25
Channel 2 overrange
26
Channel 3 overrange
27
Channel 4 overrange
28
Channel 5 overrange
29
Channel 6 overrange
30
Channel 7 overrange
31
Channel 8 overrange
32
Channel 9 overrange
33
Channel 10 overrange
34
Channel 11 overrange
35
Channel 12 overrange
36
Channel 13 overrange
37
Channel 14 overrange
38
Channel 15 overrange
39
Channel 16 overrange
88
1771-OFE Module
Chapter 8
Module Configuration
When you add a 1771-OFE module to a rack, the 1771-OFE Module
dialog box opens.
89
Chapter 8
2. For each channel select the range for each channel and enter the
scaling values.
The low scaling value corresponds to the minimum output
voltage or current; the high scaling value corresponds to the
maximum output voltage or current.
EXAMPLE
If the scaling values are 10.0 and 22.5 and the range is
configured for 0 to 5V dc, a value of 10.0 produces an output of
0V dc and a value of 22.5 produces an output of 5V dc. The
range of scaling values is -3.4e38 to 3.4e38.
Values received from a controller that are outside the scaled
range are clamped to the scaled range value.
3. Set the LAST STATE jumper setting to match the jumpers on the
1771-OFE module.
The setting can be Last, Min, Mid, or Max. This value determines
how the 1757-ABRIO module responds to a loss of
communication with the host controller.
4. Set the Update Time.
The Update Time is the rate at which the block transfer write,
which writes data to the 1771-OFE module, occurs. The range of
values is from 1 to 16382 ms. This sets the requested update
rate; the actual rate depends on the baud rate, the number of
racks on the RIO network and whether block transfers are
running to other modules in the same rack.
5. Click OK to accept the module configuration.
I/O Data
4 words of floating point data are written to the 1771-OFE module.
1771-OFE I/O Data
Data Word
Description
Channel 1 data
Channel 2 data
Channel 3 data
Channel 4 data
90
Chapter 8
Diagnostic Data
The 1771-OFE module has 8 bits of diagnostic data that can be
mapped to a flag read tag.
OFE Diagnostic Data
Bit
Description
reserved
reserved
reserved
91
Chapter 8
1771-IR Module
Module Configuration
When you add a 1771-IR module to a rack, the 1771-IR Module dialog
box displays.
92
Chapter 8
93
Chapter 8
I/O Data
The 1771-IR module returns 6 words of floating point data to the host
controller.
1771-IR Module I/O Data
Data Word
Description
Channel 1 data
Channel 2 data
Channel 3 data
Channel 4 data
Channel 5 data
Channel 6 data
Diagnostic Data
The 1771-IR module returns 16 bits of diagnostic data to the host
controller.
1771-IR Module Diagnostic Data
Data Bit
Description
Channel 1 underrange
Channel 2 underrange
Channel 3 underrange
Channel 4 underrange
Channel 5 underrange
Channel 6 underrange
reserved
Channel 1 overrange
Channel 2 overrange
10
Channel 3 overrange
11
Channel 4 overrange
12
Channel 5 overrange
13
Channel 6 overrange
14
reserved
15
reserved
94
1771-IXE Module
Chapter 8
Module Configuration
When you add a 1771-IXE module to a rack, the 1771-IXE Module
dialog box displays.
95
Chapter 8
I/O Data
The 1771-IXE module returns 9 words of floating point data.
1771-IXE Module I/O Data
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
96
Chapter 8
Diagnostic Data
The 1771-IXE module returns 24 bits of diagnostic data.
1771-IXE Module Diagnostic Data
Bit
Description
Out of range
RTS time-out
reserved
reserved
Channel 1 underrange
Channel 2 underrange
10
Channel 3 underrange
11
Channel 4 underrange
12
Channel 5 underrange
13
Channel 6 underrange
14
Channel 7 underrange
15
Channel 8 underrange
16
Channel 1 overrange
17
Channel 2 overrange
18
Channel 3 overrange
19
Channel 4 overrange
20
Channel 5 overrange
21
Channel 6 overrange
22
Channel 7 overrange
23
Channel 8 overrange
97
Chapter 8
1771-IL Module
Current
1 to 5 VDC
4 to 20 mA
0 to 5 VDC
0 to 20 mA
-5 to 5 VDC
-20 to 20 mA
-10 to 10 VDC
Module Configuration
When you add a 1771-IL module to a rack, the 1771-IL Module dialog
box displays.
98
Chapter 8
I/O Data
The 1771-IL module returns 8 words of scaled floating point values.
1771-IL Module I/O Data
Data Word
Description
Channel 1 data
Channel 2 data
Channel 3 data
Channel 4 data
99
Chapter 8
Description
Channel 5 data
Channel 6 data
Channel 7 data
Channel 8 data
Diagnostic Data
The 1771-IL module returns 24 bits of diagnostic data.
1771-IL Module Diagnostic Data
100
Bit
Description
Out of range
RTS time-out
Invalid filter
reserved
Hardware failure
reserved
Channel 1 underrange
Channel 2 underrange
10
Channel 3 underrange
11
Channel 4 underrange
12
Channel 5 underrange
13
Channel 6 underrange
14
Channel 7 underrange
15
Channel 8 underrange
16
Channel 1 overrange
17
Channel 2 overrange
18
Channel 3 overrange
19
Channel 4 overrange
20
Channel 5 overrange
Chapter 8
Description
21
Channel 6 overrange
22
Channel 7 overrange
23
Channel 8 overrange
1771-NOC Module
Module Configuration
When you add a 1771-NOC module to a rack, the 1771-NOC(V) dialog
box opens.
101
Chapter 8
I/O Data
The host application writes 8 words of floating point data to the
1771-NOC module.
1771-NOC Module I/O Data
102
Word
Description
Channel 1 data
Channel 2 data
Channel 3 data
Chapter 8
Description
Channel 4 data
Channel 5 data
Channel 6 data
Channel 6 data
Channel 7 data
Diagnostic Data
The 1771-NOC module returns 16 bits of diagnostic data.
1771-NOC Module Diagnostic Data
Bit
Description
reserved
reserved
reserved
reserved
reserved
reserved
reserved
10
11
12
13
14
15
103
Chapter 8
1771-NOV Module
Module Configuration
When you add a 1771-NOV module to a rack, the 1771-NOC(V) dialog
box opens.
104
Chapter 8
I/O Data
The host application writes 8 words of floating point data to the
1771-NOV module.
1771-NOV Module I/O Data
Word
Description
Channel 1 data
Channel 2 data
Channel 3 data
Channel 4 data
Channel 5 data
Channel 6 data
Channel 6 data
Channel 7 data
105
Chapter 8
Diagnostic Data
The 1771-NOV module returns 16 bits of diagnostic data.
1771-NOV Module Diagnostic Data
Bit
Description
reserved
reserved
reserved
reserved
reserved
reserved
reserved
10
11
12
13
14
15
106
1771-NIV Module
Chapter 8
Module Configuration
When you add a 1771-NIV module to a rack, the 1771-NIV Module
dialog box opens.
107
Chapter 8
I/O Data
The 1771-NIV module returns 8 words of floating point data to the
host controller.
1771-NIV Module I/O Data
Word
Description
Channel 1 data
Channel 2 data
Channel 3 data
Channel 4 data
Channel 5 data
Channel 6 data
Channel 7 data
Channel 8 data
108
Chapter 8
Diagnostic Data
The 1771-NIV module returns 40 bits of diagnostic data to the host
controller.
1771-NIV Module Diagnostic Data
Bit
Description
reserved
reserved
reserved
reserved
reserved
reserved
reserved
10
11
12
13
14
15
16
Bad program
17
Module fault
18
Program verify 0
19
Program verify 1
20
I/O reset
21
RTS time-out
22
Mod alarm
23
24
25
26
27
28
29
30
31
Chapter 8
Description
32
33
34
35
36
37
38
39
1771-NR Module
110
Chapter 8
Module Configuration
When you add a 1771-NR module to a rack, the 1771-NR Module
dialog box opens.
111
Chapter 8
112
Chapter 8
I/O Data
The 1771-NR module returns 8 words of floating point data to the host
controller.
1771-NR Module I/O Data
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
Diagnostic Data
The 1771-NR module returns 40 bits of diagnostic data.
1771-NR Module Diagnostic Data
Bit
Description
reserved
reserved
reserved
reserved
reserved
reserved
reserved
10
11
12
13
14
Chapter 8
Description
15
16
Bad program
17
Module fault
18
Program verify 0
19
Program verify 1
20
I/O reset
21
RTS time-out
22
Mod alarm
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
114
Chapter
Introduction
115
Chapter 9
116
Chapter 9
Word
High Byte
Low Byte
Channel - 1
HART command
parameter data
Check byte = 0
117
Chapter 9
Word 0
The \Program Files\1757AbRio\HartCmd directory contains files that
show the parameters required by each HART command and the data
returned by that command. For example, for command 1, read
primary variable, the file contains the following:
Cmd
Rsp
unit
float
Byte Count
unit
byte
3bytes
float
date
text n
118
Chapter 9
Word 1
The low byte contains 10 hex, send message to device. For more
information, see the Smart Transmitter Interface Products (HART
Protocol) User Manual, publication 1770-6.5.19.
The high byte contains the channel number for the destination
device, minus 1. Channels are numbered from 1 to 16, so this
byte contains 0 to F hex.
Word 2
The low byte contains the interface control, which should
contain 0.
The high byte contains the interface parameter, which should
also be set to 0. For more information, see the Smart Transmitter
Interface Products (HART Protocol) User Manual, publication
1770-6.5.19.
Word 3
The low byte contains the HART delimiter, which should be set
to 82 hex for a long frame address.
The high byte contains the manufacturer ID. This can be
obtained from HartCfg.exe, version 1.01.0 or above. For
example, the following screen capture shows a Rosemount
3044D. The manufacturer ID is 26 hex, the device type is 0d
hex, and the device ID is 01b1ae hex.
Word 4
The low byte contains the manufacturer device type. In the
previous screen capture, this is 0d hex
The high byte contains the device ID most significant byte. In
the previous screen capture, this is 01 hex.
Word 5
The low byte contains the device ID middle byte. In the
previous screen capture, this is b1 hex.
The high byte contains the device ID least significant byte. In
the previous screen capture, this is ae hex.
119
Chapter 9
Word 6
The low byte contains the HART command. For example, to
send Read Primary Variable, enter 01 hex.
The high byte contains the number of bytes of parameters from
the command file.
Words 7
If there are any parameters to the HART command, the following
words contain those parameters.
Word N
The last word contains 0. Both the upper and lower byte (check byte)
should be 0.
Reply Data
When the MSG command executes, the reply to the command will be
stored in the Destination tag.
The following table shows the contents of the reply.
Reply Contents
Word
High Byte
Low Byte
Channel - 1
Interface status
Interface error
HART command
data
data
data
120
Chapter 9
Word 0
The low byte contains 10 hex, send message to device. For more
information, see the Smart Transmitter Interface Products (HART
Protocol) User Manual, publication 1770-6.5.19.
The high byte contains the channel number for the destination
device, minus 1. Channels are numbered from 1 to 16, so this
byte contains 0 to F hex.
Word 1
For more information, see the Smart Transmitter Interface Products
(HART Protocol) User Manual, publication 1770-6.5.19.
Word 2
The low byte contains the HART delimiter, which should be 86
hex for an ACK with a long frame address.
The high byte contains the manufacturer ID.
Word 3
The low byte contains the manufacturer device type.
The high byte contains the device ID most significant byte.
Word 4
The low byte contains the device ID middle byte.
The high byte contains the device ID least significant byte.
Word 5
The low byte contains the HART command.
The high byte contains the number of bytes of response data to
follow, including the two HART response code bytes.
Word 6
Word 6 contains the two HART response code bytes. For more
information, see the Smart Transmitter Interface Products (HART
Protocol) User Manual, publication 1770-6.5.19.
Words 7
These contain any response data.
121
Chapter 9
07
07
0707
00
10
0010
00
00
0000
26
82
2682
01
0D
010D
AE
B1
AEB1
00
24
0024
00
00
0000
00
10
0010
80
00
8000
26
86
2686
01
0D
010D
AE
B1
AEB1
02
24
0224
40
00
4000
122
1770-HT1 Module
Chapter 9
Rack Requirements
The 1770-HT1 module can be set for any rack number from 1 to 37
octal. The 1770-HT1 module must be configured at starting I/O
group 0. No other device can use the same rack number.
123
Chapter 9
124
Chapter 9
The purpose of this dialog box is to make the search for HART
devices faster by including only channels that you know are
occupied. (For the 1770-HT module, in the non-multiplex mode,
Channels = HART devices connected to the 1770-HT8 module) If
you have four HART devices connected to the 1770-HT8 module
then check Channels 1, 2, 3, and 4.
2. Select those channels you want to search.
3. Use All and None to select or deselect blocks of channels.
If you dont know which channels are being used, select them
all. Set the maximum address (range 0 to 15) to search on each
channel. If you have one HART device on each channel set Max
Address to 1.
125
Chapter 9
126
Chapter 9
127
Chapter 9
5. If you have not already done so, create tags to accept the data
from the HART commands and map the 1770-HT1 module to
those tags.
The 1770-HT1 module occupies an entire numeric read,
flag-read or text-read tag.
6. After you select HART command 1, Read Primary Variable, from
the command list, select an offset for the location where the data
will be stored in the HART Data tags you have or will create.
7. Click Execute.
The Execution results are shown, to confirm that you are
receiving the desired data.
128
Chapter 9
Meaning
Configuration changed
Cold start
When you enter a flag offset when you create a cyclic command, this
is what gets returned at that offset.
Nothing is displayed if you monitor the block transfers to the
1770-HT1 module.
129
Chapter 9
130
Appendix
Specifications
Value
Module Location
Backplane Current
675 mA @ +5.1V dc
5 mA @ 24 V dc
4W
Isolation Voltage
Wiring Category(1)
2 - on communications ports
Wire Size
20 AWG, 0.519mm
Wire Type
(1)
Use this Conductor Category information for planning conductor routing. Refer to Industrial Automation Wiring
and Grounding Guidelines, publication 1770-4.1.
Environmental Specifications
Attribute
Value
Temperature,
operating
060 C (32140 F)
IEC 60068-2-1 (Test Ad, Operating Cold),
IEC 60068-2-2 (Test Bd, Operating Dry Heat),
IEC 60068-2-14 (Test Nb, Operating Thermal Shock)
Temperature,
nonoperating
4085 C (40185 F)
IEC 60068-2-1 (Test Ab, Un-packaged Nonoperating Cold),
IEC 60068-2-2 (Test Bb, Un-packaged Nonoperating Dry Heat),
IEC 60068-2-14 (Test Na, Un-packaged Nonoperating Thermal
Relative Humidity
595% noncondensing
IEC 60068-2-30 (Test Db, Un-packaged Nonoperating Damp Heat)
Shock, operating
Shock, nonoperating
Vibration
Emissions
131
Appendix A
Specifications
Environmental Specifications
Attribute
Value
ESD immunity
IEC 61000-4-2:
6 kV contact discharges
8 kV air discharges
Radiated RF
immunity
IEC 61000-4-3
10V/m with 1 kHz sine-wave 80%AM from 80 MHz to 2000 MHz
10V/m with 200 Hz 50% Pulse 100%AM at 900 Mhz
EFT/B immunity
IEC 61000-4-4:
2 kV at 5 kHz on communication ports
Surge Transient
Immunity
IEC 61000-4-5:
2 kV line-earth (CM) on communication ports
Conducted RF
Immunity
IEC 61000-4-6:
10V rms with 1 kHz sine-wave 80%AM from 150 kHz to 80 MHz
Enclosure Type
Rating
None (open-style)
North American
temperature code
T4A
Certifications
Certification
Value
Certifications
(when product is
marked)(1)
132
See the Product Certification link at http://ab.com for Declarations of Conformity, Certificates, and other
certification details.
Appendix
Troubleshooting
Status
Green
Yellow
Red
Indicator
Status
Green
Yellow
Idle, no requests received from the backplane in the last five seconds.
Red
The module has returned an error to a request from the backplane within
the last second.
133
Appendix A
Troubleshooting
Status
Green
Red
IMPORTANT
If all three status indicators are solid red and the 4-character
display shows the #xx, (where xx is the error number) this is
where the fatal area occurs. Refer to publication
1757-UM007C, the 1757-ABRIO User Manual for information on
clearing fatal errors. Be sure to make a note of the error code
numbers to give Tech Support, if you need to call for help.
Boot
POWER Indicator
Off
Not operating
Recommended Action
Turn power switch ON.
Check power wiring connections.
Check fuse.
On
134
Operating
Troubleshooting
Appendix A
Description
Config
Inactive
Active
Forced Active
The module has been put into active mode by the configuration
program.
Error: Heard Another RIO Another master has been detected on the network because of
Master
the following possible reasons.
The module is connected to a network with another RIO
master.
The module is connected to a Data Highway Plus network.
The rack size in the stored configuration on the module for the
rack at rack number xx octal, starting I/O group yy, does not
match the rack size on the network.
The rack at rack number xx octal, starting I/O group yy, is not
responding.
Firmware Update
135
Appendix A
Troubleshooting
136
Troubleshooting
Troubleshooting Problems
Symptom
Autoconfiguration fails or does not
find racks
Appendix A
The following are some possible problems you may encounter and
their possible causes.
Possible Problems
Notes
137
Appendix A
Troubleshooting
General Tab
Item
Description
Type
Vendor
Allen-Bradley
Name
Description
Comm Format
Slot
Connection
Parameter
Connection Tab
The Inhibit Module checkbox breaks the exclusive ownership
connection between the 1757-ABRIO module and the ControlLogix
controller. If you would like to download to the 1757-ABRIO module
without putting the controller in Program mode, check Inhibit
Module. Once you are done updating the 1757-ABRIO module,
uncheck Inhibit Module and your connection will be re-established.
138
Then
Troubleshooting
Appendix A
Description
Vendor
Allen-Bradley
Product Type
Communications Adapter
Product Code
107
Revision
Serial Number
Product Name
57ABRIO
Status Section
Refresh
Backplane Tab
Item
Description
ControlBus Status
ControlBus Parameters
Chassis
Error Counters
Status
139
Appendix A
Troubleshooting
Troubleshooting
1757-ABRIO Module
Communications
If the Data in the various Tag Storage files in your controller is not
what you expect, try the following possible solutions.
Check that the 1757-ABRIO module is active. If it is not active,
your controller is probably not in Run mode.
Confirm that the 1757-ABRIO tags referenced in your message
commands or exchange blocks exactly match the tag names in
the 1757-ABRIO module.
In the AbRioCfg software, right-click on the Tag Name, select
Monitor Tag, and confirm that 1757-ABRIO module is seeing the
correct data.
Both 1757-ABRIO tag name read and write data should match
the data in your controller.
140
Troubleshooting
Appendix A
To write data, you have to enable writes, using either the menu
item Edit/WriteEna or using the Toolbar button.
6. Enter data in the Tag Monitor window and see how that data
matches the indicator lights on the SIM module.
For observing Flag read data, flip the switches on the SIM
module and see how that change affects a flag read tag for that
rack
7. Put the controller in Run Mode or uncheck Inhibit Module.
8. Verify that the correct data is being written to the 1757-ABRIO
module from the controller using the same tag monitor screen in
AbRioCfg software.
9. Verify that data is being written correctly from the 1757-ABRIO
module to the controller by observing flag read data within
RSLogix 5000 software (ControlLogix controller) or Control
Builder software (ProcessLogix controller).
10. Also, read SIM module switches from the controller.
If you are using message instructions in RSLogix 5000 software
to read this flag data, remember to append the tag name with
the [100] offset. See Unscheduled I/O Connections in
ControlLogix on page 67 for more details.
141
Appendix A
142
Troubleshooting
Appendix
Normal Operational
Messages
143
Appendix B
Equivalent Modes
1757-ABRIO
Module
PLC-5
Controller
Description
ACTIVE
Run
INACTIVE
Program
CONFIG
Program
FORCED ACTIVE
TIP
Digital inputs
Digital outputs
Digital input data updates. Data update in the PLC Digital output data updates (in the 1757-ABRIO
data table is asynchronous to the I/O update,
module) based on the scan list. Data updates by the
based on the PLC I/O scan.
controller asynchronously when the tag is read by the
controller.
Digital inputs
Digital input data updates. Data update in the PLC Digital input data updates in the 1757-ABRIO module.
data table is asynchronous to the I/O update.
Data does not update in the host controller since tags
are not being read.
Digital outputs
144
Exception Handling
Messages
Appendix B
145
Appendix B
N/A
N/A
N/A
N/A
146
Appendix B
N/A
N/A
N/A
N/A
N/A
147
Appendix B
148
Appendix
Description
Status tag
Configuration Tag
The configuration tag gets created when you configure the
1757-ABRIO module as a 1756-MODULE, but the contents of the
configuration tag are not used by the 1757-ABRIO module.
I and O Tags
The I and O tags are associated with the digital I/O data. The input
tag also contains rack global status. The following tables show how
the tag contents correspond to the racks.
Input Tags
Address
Description
Local:<slot>:I.Data[0]
Local:<slot>:I.Data[1]
Local:<slot>:I.Data[2]
Local:<slot>:I.Data[3]
...
Local:<slot>:I.Data[9]
Publication 1757-UM007D-EN-P - December 2008
Appendix C
Input Tags
Address
Description
Local:<slot>:I.Data[10]
...
Local:<slot>:I.Data[17]
...
Local:<slot>:I.Data[242]
...
Local:<slot>:I.Data[249]
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
Output Tags
Address
Description
Local:<slot>:O.Data[0]
Local:<slot>:O.Data[1]
...
Local:<slot>:O.Data[7]
Local:<slot>:O.Data[8]
...
Local:<slot>:O.Data[15]
...
Local:<slot>:O.Data[240]
...
Local:<slot>:O.Data[247]
The offset for the output data for any rack and the I/O group
can be found from:
offset = 8 * (rack - 1) + I/O group
where the rack number is in decimal
150
Appendix C
Status Tag
The status tag contains a global status as well as individual status flags
for all possible partial racks. The status bits are set if the rack with the
corresponding rack number and starting I/O group is configured in
the 1757-ABRIO module and is not communicating, and are 0
otherwise. If any configured rack is not communicating, the global
status is set.
The following table shows the contents of the Status Tag.
Status Tag
Address
Description
Local:<slot>:S.Data[0]
Local:<slot>:S.Data[1]
Local:<slot>:S.Data[2].0
Not used
Local:<slot>:S.Data[2].1
Not used
Local:<slot>:S.Data[2].2
Not used
Local:<slot>:S.Data[2].3
Not used
Local:<slot>:S.Data[2].4
Local:<slot>:S.Data[2].5
Local:<slot>:S.Data[2].6
Local:<slot>:S.Data[2].7
Local:<slot>:S.Data[2].8
Local:<slot>:S.Data[2].9
Local:<slot>:S.Data[2].10
Local:<slot>:S.Data[2].11
Local:<slot>:S.Data[2].12
Local:<slot>:S.Data[2].13
Local:<slot>:S.Data[2].14
Local:<slot>:S.Data[2].15
Local:<slot>:S.Data[3].0
Local:<slot>:S.Data[3].1
Local:<slot>:S.Data[3].2
Local:<slot>:S.Data[3].3
Local:<slot>:S.Data[3].4
Local:<slot>:S.Data[3].5
Local:<slot>:S.Data[3].6
Local:<slot>:S.Data[3].7
151
Appendix C
Status Tag
152
Address
Description
Local:<slot>:S.Data[3].8
Local:<slot>:S.Data[3].9
Local:<slot>:S.Data[3].10
Local:<slot>:S.Data[3].11
Local:<slot>:S.Data[3].12
Local:<slot>:S.Data[3].13
Local:<slot>:S.Data[3].14
Local:<slot>:S.Data[3].15
Local:<slot>:S.Data[4].0
Local:<slot>:S.Data[4].1
Local:<slot>:S.Data[4].2
Local:<slot>:S.Data[4].3
Local:<slot>:S.Data[4].4
Local:<slot>:S.Data[4].5
Local:<slot>:S.Data[4].6
Local:<slot>:S.Data[4].7
Local:<slot>:S.Data[4].8
Local:<slot>:S.Data[4].9
Local:<slot>:S.Data[4].10
Local:<slot>:S.Data[4].11
Local:<slot>:S.Data[4].12
Local:<slot>:S.Data[4].13
Local:<slot>:S.Data[4].14
Local:<slot>:S.Data[4].15
Local:<slot>:S.Data[5].0
Local:<slot>:S.Data[5].1
Local:<slot>:S.Data[5].2
Local:<slot>:S.Data[5].3
Local:<slot>:S.Data[5].4
Local:<slot>:S.Data[5].5
Local:<slot>:S.Data[5].6
Local:<slot>:S.Data[5].7
Local:<slot>:S.Data[5].8
Local:<slot>:S.Data[5].9
Local:<slot>:S.Data[5].10
Local:<slot>:S.Data[5].11
Appendix C
Status Tag
Address
Description
Local:<slot>:S.Data[5].12
Local:<slot>:S.Data[5].13
Local:<slot>:S.Data[5].14
Local:<slot>:S.Data[5].15
Local:<slot>:S.Data[6].0
Local:<slot>:S.Data[6].1
Local:<slot>:S.Data[6].2
Local:<slot>:S.Data[6].3
Local:<slot>:S.Data[6].4
Local:<slot>:S.Data[6].5
Local:<slot>:S.Data[6].6
Local:<slot>:S.Data[6].7
Local:<slot>:S.Data[6].8
Local:<slot>:S.Data[6].9
Local:<slot>:S.Data[6].10
Local:<slot>:S.Data[6].11
Local:<slot>:S.Data[6].12
Local:<slot>:S.Data[6].13
Local:<slot>:S.Data[6].14
Local:<slot>:S.Data[6].15
Local:<slot>:S.Data[7].0
Local:<slot>:S.Data[7].1
Local:<slot>:S.Data[7].2
Local:<slot>:S.Data[7].3
Local:<slot>:S.Data[7].4
Local:<slot>:S.Data[7].5
Local:<slot>:S.Data[7].6
Local:<slot>:S.Data[7].7
Local:<slot>:S.Data[7].8
Local:<slot>:S.Data[7].9
Local:<slot>:S.Data[7].10
Local:<slot>:S.Data[7].11
Local:<slot>:S.Data[7].12
Local:<slot>:S.Data[7].13
Local:<slot>:S.Data[7].14
Local:<slot>:S.Data[7].15
153
Appendix C
Status Tag
154
Address
Description
Local:<slot>:S.Data[8].0
Local:<slot>:S.Data[8].1
Local:<slot>:S.Data[8].2
Local:<slot>:S.Data[8].3
Local:<slot>:S.Data[8].4
Local:<slot>:S.Data[8].5
Local:<slot>:S.Data[8].6
Local:<slot>:S.Data[8].7
Local:<slot>:S.Data[8].8
Local:<slot>:S.Data[8].9
Local:<slot>:S.Data[8].10
Local:<slot>:S.Data[8].11
Local:<slot>:S.Data[8].12
Local:<slot>:S.Data[8].13
Local:<slot>:S.Data[8].14
Local:<slot>:S.Data[8].15
Local:<slot>:S.Data[9].0
Local:<slot>:S.Data[9].1
Local:<slot>:S.Data[9].2
Local:<slot>:S.Data[9].3
Local:<slot>:S.Data[9].4
Local:<slot>:S.Data[9].5
Local:<slot>:S.Data[9].6
Local:<slot>:S.Data[9].7
Local:<slot>:S.Data[9].8
Local:<slot>:S.Data[9].9
Local:<slot>:S.Data[9].10
Local:<slot>:S.Data[9].11
Local:<slot>:S.Data[9].12
Local:<slot>:S.Data[9].13
Local:<slot>:S.Data[9].14
Local:<slot>:S.Data[9].15
1757-ABRIO
Pub. No.
1757-UM007D-EN-P
Part No.
N/A
Please complete the sections below. Where applicable, rank the feature (1=needs improvement, 2=satisfactory, and 3=outstanding).
Overall Usefulness
Completeness
(all necessary information
is provided)
Technical Accuracy
(all provided information
is correct)
Clarity
1
(all provided information is
easy to understand)
procedure/step
illustration
feature
example
guideline
other
explanation
definition
Other Comments
illustration
Your Name
Your Title/Function
Location/Phone
Email: RADocumentComments@ra.rockwell.com
NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES
1 ALLEN-BRADLEY DR
MAYFIELD HEIGHTS OH 44124-9705
PLEASE REMOVE
Other Comments
Rockwell Automation
Support
Installation Assistance
If you experience a problem within the first 24 hours of installation, please
review the information that's contained in this manual. You can also contact
a special Customer Support number for initial help in getting your product up
and running.
United States
1.440.646.3434
Monday Friday, 8am 5pm EST
Outside United
States
Outside United
States
Copyright 2008 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.