1756 IF8H User Manual

ControlLogix HART Analog I/O Modules
Catalog Numbers 1756-IF8H, 1756-OF8H
User Manual
Important User Information
Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://literature.rockwellautomation.com) describes some important differences between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable. In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment. The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams. No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual. Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited. Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING
Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.
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 Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.
SHOCK HAZARD
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, ControlLogix, FactoryTalk, FactoryTalk AssetCentre, Rockwell Automation, RSLogix, RSNetWorx, RSLogix 5000, Logix5000, Data Highway Plus, Logix, ControlBus, RSLinx, RSLinx Classic, and TechConnect are trademarks of Rockwell Automation, Inc. Trademarks not belonging to Rockwell Automation are property of their respective companies.
Table of Contents
Preface
What This Preface Contains . . Who Should Use This Manual Purpose of This Manual. . . . . Additional Resources. . . . . . . Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 . 9 . 9 . 9 10
Chapter 1 About the Modules

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . Description of the Modules . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Highway Addressable Remote Transducer (HART) Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Benefits of Integrated HART Networks . . . . . . . . . . . . . . Benefits of HART-enabled I/O Modules . . . . . . . . . . . . . Work with Asset Management Software . . . . . . . . . . . . . . . . Using an I/O Module in the ControlLogix System . . . . . . . . . Features of the Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Module Identification and Status Information . . . . . . . Preventing Electrostatic Discharge . . . . . . . . . . . . . . . . . . . . Removal and Insertion Under Power . . . . . . . . . . . . . . . . . . 13 13 14 16 16 17 17 18 19 20 20
Chapter 2 Understand Module Operation

What This Chapter Contains . . . . . . . . . . . . . . . Ownership and Connections . . . . . . . . . . . . . . . Using RSNetWorx and RSLogix 5000 Software . . Direct Connections . . . . . . . . . . . . . . . . . . . . . . Input Module Operation . . . . . . . . . . . . . . . . . . Input Modules in a Local Chassis . . . . . . . . . . . . Real Time Sample (RTS) . . . . . . . . . . . . . . . . Requested Packet Interval (RPI) . . . . . . . . . . Triggering Event Tasks . . . . . . . . . . . . . . . . . Input Modules in a Remote Chassis . . . . . . . . . . Remote Input Modules Connected Via ControlNet Network . . . . . . . . . . . . . . . . . . . Remote Input Modules Connected Via EtherNet/IP Network . . . . . . . . . . . . . . . . . . Output Module Operation . . . . . . . . . . . . . . . . . Output Modules in a Local Chassis . . . . . . . . . . Output Modules in a Remote Chassis . . . . . . . . . Remote Output Modules Connected Via ControlNet Network . . . . . . . . . . . . . . . . . . . Remote Output Modules Connected Via EtherNet/IP Network . . . . . . . . . . . . . . . . . . Listen-only Mode . . . . . . . . . . . . . . . . . . . . . . . Multiple Owners of Input Modules . . . . . . . . . . Configuration Changes in an Input Module with Multiple Owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 21 22 23 23 24 24 25 26 27
. . . . . . . . . 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 29 29 30
. . . . . . . . . 30 . . . . . . . . . 31 . . . . . . . . . 32 . . . . . . . . . 32 . . . . . . . . . 34
Publication 1756-UM533A-EN-P - March 2007
Table of Contents
Chapter 3 Using Module Features

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . Determining Input Module Compatibility . . . . . . . . . . . . . . . Determining Output Module Compatibility. . . . . . . . . . . . . . Features Common to Analog I/O Modules . . . . . . . . . . . . . . Removal and Insertion Under Power (RIUP) . . . . . . . . . . Module Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . . Fully Software Configurable . . . . . . . . . . . . . . . . . . . . . . Electronic Keying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access to System Clock for Timestamping Functions . . . . Rolling Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Producer/Consumer Model. . . . . . . . . . . . . . . . . . . . . . . Status Indicator Information . . . . . . . . . . . . . . . . . . . . . . Full Class I Division 2 Compliance . . . . . . . . . . . . . . . . . UL, CSA, FM, CE, C-Tick, EEx, TUV Agency Certification . Field Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sensor Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Latching of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module Inhibiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Relationship Between Module Resolution and Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 35 35 35 36 36 36 37 39 39 39 40 40 40 40 41 41 41 41 43 43 44
Chapter 4 About the HART Analog Input Module

What This Chapter Contains . . . . . . . . . . . . . Work with the Differential Wiring Method . . . Choosing a Data Format . . . . . . . . . . . . . . . . Module Features . . . . . . . . . . . . . . . . . . . . . . Multiple Input Ranges . . . . . . . . . . . . . . . Module Filter . . . . . . . . . . . . . . . . . . . . . . Real Time Sampling (RTS) . . . . . . . . . . . . Underrange and Overrange Detection. . . . Digital Filter. . . . . . . . . . . . . . . . . . . . . . . Process Alarms . . . . . . . . . . . . . . . . . . . . Rate Alarm. . . . . . . . . . . . . . . . . . . . . . . . Wire Off Detection. . . . . . . . . . . . . . . . . . Wire the Modules . . . . . . . . . . . . . . . . . . . . . Using Input Circuit Diagrams. . . . . . . . . . . . . 1756-IF8H Module Fault and Status Reporting 1756-IF8H Fault Reporting . . . . . . . . . . . . . . . 1756-IF8H Module Fault Word Bits . . . . . . 1756-IF8H Channel Fault Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 47 48 48 48 49 50 50 51 52 53 53 54 55 56 57 58 58
Table of Contents
Chapter 5 About the HART Analog Output Module

What This Chapter Contains . . . . . . . . . . . . . . . . Choosing a Data Format . . . . . . . . . . . . . . . . . . . Features Specific to Analog Output Modules . . . . Ramping/Rate Limiting . . . . . . . . . . . . . . . . . . Hold for Initialization . . . . . . . . . . . . . . . . . . . Open Wire Detection . . . . . . . . . . . . . . . . . . . Clamping and Limiting . . . . . . . . . . . . . . . . . . Clamp and Limit Alarms . . . . . . . . . . . . . . . . . Data Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . Wire the Modules . . . . . . . . . . . . . . . . . . . . . . . . Using Module Block and Output Circuit Diagrams 1756-OF8H Module Fault and Status Reporting. . . Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . Module Fault Word Bits . . . . . . . . . . . . . . . . . Channel Fault Word Bits . . . . . . . . . . . . . . . . Channel Status Words Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 59 60 60 61 61 61 62 62 63 64 65 66 67 67 68
Chapter 6 Configuring the Modules

What This Chapter Contains . . . . . . . . . . Configuring Your I/O Module . . . . . . . . . Create a New Module . . . . . . . . . . . . . . . Work with the General Dialog . . . . . . . . . Work with the Connection Dialog . . . . . . Work with the Module Info Dialog . . . . . Work with HART Analog Input Dialogs . . Configuration Dialog . . . . . . . . . . . . . Scaling to Engineering Units. . . . . . . . Alarm Dialog . . . . . . . . . . . . . . . . . . . Work with HART Analog Output Dialogs . Configuration Dialog . . . . . . . . . . . . . Output State Dialog . . . . . . . . . . . . . . Limits Dialog . . . . . . . . . . . . . . . . . . . HART Device Info Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 69 69 71 73 74 76 76 81 83 86 87 90 92 96
Chapter 7 Configuring and Using HART

What This Chapter Contains . . . . . . . . . . . . . . . . . . . HART Configuration Quick Start . . . . . . . . . . . . . . . . Pick HART Input Data Format . . . . . . . . . . . . . . . Enable HART. . . . . . . . . . . . . . . . . . . . . . . . . . . . HART Data in the Module Properties on the HART Info Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data in the Input Tags . . . . . . . . . . . . . . . . . . . . . HART Dynamic Variables . . . . . . . . . . . . . . . . . . . How the Module Automatically Collects Data . . . . . . . . . 97 . . . . . 98 . . . . . 98 . . . . . 99 Device . . . . 100 . . . . 104 . . . . 105 . . . . 107
Table of Contents
Chapter 8 Getting HART Data Using CIP MSG What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 109
Using MSG Instructions to Access the HART Object . . . . . CIP Services to Access Common HART Data . . . . . . . . . . Read Dynamic Variables (Service Code = 16#4B) . . . . Read Additional Status (Service Code = 16#4C) . . . . . . Get Device Information (Service Code = 16#4D) . . . . . Getting HART Device Information Using CIP Generic MSG: An Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIP Services to Pass Through a HART Message to the HART Field Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the HART Module Scanning Diagram with Pass Through Messages . . . . . . . . . . . . . . . . . . . . . . . . . . HART Pass Through CIP Message Layout Details . . . . . . . Pass Through Init (Service Code= 16#4E) . . . . . . . . . . Pass Through Query (Service Code= 16#4F) . . . . . . . . Flush Queue (Service Code= 16#50) . . . . . . . . . . . . . . HART Pass Through Message Ladder Logic Example . . . . . . . . . 109 110 111 113 113
. 115
. 119 . . . . . . 120 122 122 122 123 124
Chapter 9 Using HART Modules with Asset Management Software

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 129 Using HART Modules with Asset Management Systems. . . . 129 Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . 130
Chapter 10 Unlatching Alarms and Reconfiguring Modules Using Ladder Logic

What This Chapter Contains . . . . . . . . . . . . . . . . . . . Using Message Instructions . . . . . . . . . . . . . . . . . . . . Processing Real-time Control and Module Services One Service Performed Per Instruction . . . . . . . . . Creating a New Tag . . . . . . . . . . . . . . . . . . . . . . . . . Enter Message Configuration . . . . . . . . . . . . . . . . Unlatch Alarms in the Input Module . . . . . . . . . . Unlatch Alarms in the Output Module . . . . . . . . Reconfiguring a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 133 134 134 134 136 139 141 143
Chapter 11 Troubleshooting the Modules

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . Using Module Indicators to Troubleshoot. . . . . . . . . . . . . . General Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . Using RSLogix 5000 Software to Troubleshoot Your Module Module Configuration Errors . . . . . . . . . . . . . . . . . . . . . . . 145 145 146 149 150
Table of Contents
Appendix A Tag Definitions

What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . Communications Mode Tag Names and Definitions . . . Module-defined Data Types (1756-IF8H modules) . . . . . . Understand Use of ResponseCode or Communication Status Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module-defined Data Types (1756-OF8H) . . . . . . . . . . . . . 157 . 157 . 158 . 163 . 172
Appendix B Calibration Information

What This Appendix Contains . . . . . . . . . . . Analog to Digital (A/D) Converter Accuracy . Calibrated Accuracy . . . . . . . . . . . . . . . . . . Error Calculated Over Hardware Range . . . . How Operating Temperature Changes Affect Module Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 183 183 184
. . . . . . . . . . . 184
Appendix C Using 1492 Wiring Systems with Your Analog I/O Module
What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . 185 Using a Wiring System . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Appendix D Additional HART Protocol Information

What This Appendix Contains . Message Structure . . . . . . . . . . Master-slave Operation. . . . Multiple Master Operation . Transaction Procedure . . . . Burst Mode . . . . . . . . . . . . Status . . . . . . . . . . . . . . . . . . . Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 187 188 188 188 189 189 190
Appendix E Company Identification Codes

What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . 199 Identification Code Details. . . . . . . . . . . . . . . . . . . . . . . . . 199
Table of Contents
Appendix F Engineering Unit Code Numbers

What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . 205 Code Number Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Index
Preface
What This Preface Contains Who Should Use This Manual
This preface describes how to use this manual.
You must be able to program and operate a Rockwell Automation ControlLogix controller to efficiently use your analog I/O modules. In this manual, we assume that you know how to do this. If you do not, before attempting to use this module, refer to the Logix5000 controller documentation, as listed in the related table.
Purpose of This Manual
This manual describes how to install, configure, and troubleshoot your ControlLogix Highway Addressable Remote Transducer (HART) analog I/O modules.
Additional Resources
Refer to the table that shows related documentation for additional help when setting up and using your modules. View or download publications at http://literature.rockwellautomation.com. To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
Catalog Number 1756-IF8H, 1756-OF8H 1756-IF8H 1756-OF8H 1756-A10, 1756-A13, 1756-A17, 1756-A4, 1756-A7 1756-PH75 1756-PA75/B, 1756-PB75/B 1756-PA72/C, 1756-PB72/C 1756-IF16, 1756-IF6CIS, 1756-IF6I, 1756-IF8, 1756-IR6I, 1756-IT6I, 1756-IT6I2, 1756-OF4, 1756-OF6CI, 1756-OF6VI, 1756-OF8 1756-Series 1756-Series 1734-ACNR, 1756-CNB, 1756-CNBR, 1769-L32C, 1769-L35CR, 1784-PCC, 1784-PCIC, 1784-PCICS, 1784-PKTCS, 1788-CNC, 1788-CNCR, 1788-CNF, 1788-CNFR, 1794-ACN15, 1794-ACNR15, 1797-ACNR15
9
Publication ControlLogix Analog Modules with HART Protocol Release Notes ControlLogix Analog Input Module with HART Protocol Installation Instructions ControlLogix Analog Output Module with HART Protocol Installation Instructions ControlLogix Chassis Installation Instructions ControlLogix Power Supply Installation Instruction ControlLogix Power Supply Installation Instruction ControlLogix Power Supply Installation Instructions ControlLogix Analog I/O Modules User Manual
Publication 1756-RN636 1756-IN608 1756-IN609 1756-IN080 1756-IN589 1756-IN596 1756-IN078 1756-UM009
ControlLogix Module Installation Instructions (each module has separate installation instructions) ControlLogix Digital I/O Modules User Manual ControlNet Modules in Logix5000 Control Systems
Multiple 1756-IN numbers 1756-UM058 CNET-UM001
10
Preface
Catalog Number
Publication
Publication DNET-UM004
1734-ADN, 1734-ADNX, 1734-PDN, 1756-DNB, 1769-SDN, DeviceNet Modules in Logix5000 Control Systems User 1784-PCIDS, 1788-CN2DN, 1788-DNBO, 1788-EN2DN, Manual 1794-ADN 1756-DHRIO 1756-ENET 1756-IF4FXOF2F 1756-Lx 1756-Lx 1756-Lx, 1769-Lx, 1789-Lx, 1794-Lx, PowerFlex 700S 1756-Lx, 1769-Lx, 1789-Lx, 1794-Lx, PowerFlex 700S 1756-Lx, 1769-Lx, 1789-Lx, 1794-Lx, PowerFlex 700S 1756-Lx, 1769-Lx, 1789-Lx, 1794-Lx, PowerFlex 700S ControlLogix Data Highway Plus Communication Interface Module User Manual
1756-UM514
ControlLogix Ethernet Communication Interface Module 1756-UM051 User Manual ControlLogix High Speed Analog I/O Module User Manual ControlLogix Selection Guide ControlLogix System User Manual Logix5000 Controllers Quick Reference Logix5000 Controllers Common Procedures Programming Manual 1756-UM005 1756-SG001 1756-UM001 1756-QR107 1756-PM001
Logix5000 Controllers Motion Instruction Set Reference 1756-RM007 Manual Logix5000 Controllers General Instructions Reference Manual 1756-RM003
Glossary of Terms
Understand these terms before using this user manual. Broadcast - Data transmissions to all addresses. Compatible match - An Electronic Keying Protection mode that requires the physical module and the module configured in the software to match according to vendor, catalog number, and major revision. The minor revision of the module must be greater than or equal to that configured. Connection - The continuous communication mechanism from the controller to an I/O module in the control system. ControlBus - The backplane used by the 1756 chassis. Coordinated system time (CST) - Timer value, which is kept synchronized for all modules within a single ControlBus chassis. The CST is a 64-bit number with microsecond resolution. Direct connection - An I/O connection, where the controller establishes an individual connection with I/O modules.
Preface
11
Disable keying - An option that turns off all electronic keying to the module. Requires no attributes of the physical module and the module configured in the software to match. A connection is attempted to the module even if it is the wrong type. Download - The process of transferring the contents of a project on the workstation into the controller. Electronic keying - A system feature that makes sure that physical module attributes are consistent with what was configured in software. Exact match - An Electronic Keying Protection mode that requires the physical module and the module configured in the software to match identically, according to vendor, catalog number, major revision, and minor revision. Field side - Interface between user field wiring and I/O module. In this glossary, see related entry for system side. Flash update - The process of updating the firmware of the module. Frequency shift keying - A method of using frequency modulation to send digital information used by HART field devices. Hard Run mode - Mode where keyswitch of controller is in Run position. HART - Acronym for highway addressable remote transducer. Inhibit - A ControlLogix process that lets you configure an I/O module, but prevent it from communicating with the owner-controller. In this case, the controller does not establish a connection. Input Data format - Format that defines the type of information transferred between an I/O module and its owner-controller. This format also defines the tags created for each I/O module. Interface module (IFM) - A prewired removable terminal block (RTB). Listen-only connection - An I/O connection that lets a controller monitor I/O module data without owning the module, sending it a configuration, or controlling its outputs. Major revision - A module revision that is updated any time there is a functional change to the module, resulting in an interface change with software.
12
Preface
Minor revision - A module revision that is updated any time there is a change to the module that does not affect its function or software user interface. Multicast - Data transmissions which reach a specific group of one or more destinations. Multiple owners - A configuration set-up where multiple owner-controllers use exactly the same configuration information to simultaneously own an input module. Network update time (NUT) - The smallest repetitive time interval in which the data can be sent on a ControlNet network. The NUT can be configured over the range from 2100 ms using RSNetWorx software. Owner-controller - The controller that creates and stores the primary configuration and communication connection to a module. Program mode - In this mode, the controller program is not executing. Inputs are actively producing data. Outputs are not actively controlled and go to their configured Program mode state. Remote connection - An I/O connection where the controller establishes an individual connection with I/O modules in a remote chassis. Removable terminal block (RTB) - Field wiring connector for I/O modules. Removal and insertion under power (RIUP) - ControlLogix feature that lets you install or remove a module or RTB while power is applied. Requested packet interval (RPI) - A configurable parameter that defines when the module will multicast data. Run mode - In this mode, the controller program is executing. Inputs are actively producing data. Outputs are actively controlled. Service - A system feature that is performed on user demand. System side - Backplane side of the interface to the I/O module. In this glossary, see related entry for field side. Tag - A named area of the controllers memory where data is stored like a variable. Timestamping - ControlLogix process that stamps a change in input, output, or diagnostic data with a time reference indicating when that change occurred.
Chapter
About the Modules
What This Chapter Contains
This chapter describes the ControlLogix Highway Addressable Remote Transducer (HART) analog modules and what you must know and do before you begin to use them.
Description of the Modules
Your ControlLogix HART analog I/O modules are interface modules that convert analog signals to digital values for inputs and convert digital values to analog signals for outputs. Controllers can then use these signals for control purposes. Using the producer/consumer network model, ControlLogix analog I/O modules produce information when needed while providing additional system functions. These modules also support the HART protocol used by many process field devices. See the table for a list of the features available on ControlLogix analog I/O modules.
ControlLogix Analog I/O Module Features Feature Removal and insertion under power (RIUP) Producer/consumer communication model Rolling timestamp of data Description Use this system feature to remove and insert modules and removable terminal bases while power is applied. These communications are an intelligent data exchange between modules and other system devices in which each module produces data without having been polled. 15-bit module-specific rolling timestamp with millisecond resolution that indicates when data was sampled/applied. This timestamp can be used to calculate the interval between channel or field side updates Analog I/O modules offer this option. Analog input modules use 16-bit resolution, and analog output modules offer 15- or 16-bit resolution, depending on the output range, to detect data changes. Features such as scaling to engineering units, alarming, and underrange and overrange detection increase the modules complexity and effectiveness. ControlLogix analog I/O module ships from the factory with factory calibration. 64-bit system clock (CST) places a timestamp on the transfer of data between the module and its owner-controller within the local chassis Full agency certification in any application that requires approval of the agencies listed. Agency certification varies depending on catalog number.
Multiple data formats Module resolution On-board features Calibration Coordinated system time (CST) timestamp of data UL, CSA, FM, CE, C-Tick, EEx, TUV Agency Certification
13
14
About the Modules
Understanding the Highway Addressable Remote Transducer (HART) Feature
The HART field communications protocol is widely accepted in industry as a standard for digitally enhanced 420 mA communication with smart (microprocessor-based) field devices. A digital signal is superimposed onto the 420 mA current loop to provide two means of communication from the device. The 420 mA analog channel lets a single process variable be communicated at the fastest possible rate while the digital channel provides access to multiple process variables, data quality, and device status information. The HART protocol lets these simultaneous communications channels be used in a complementary fashion. Your modules support the HART protocol and perform these distinct operations: Convert to or from 420 mA analog signals and digital numeric values in engineering units used in the Logix controller Collect dynamic process data automatically from the connected HART field device, such as temperature, pressure, flow, or valve position Bridge HART messages from CIP clients to HART field device using a mechanism called Pass through messages See the figure(1) that shows information about the HART protocol.
The Highway Addressable Remote Transducer (HART) protocol supports two-way digital communication, complements traditional 420 mA analog signals, and includes the following features: Predefined commands - Common practice - General purpose - Device specific Large installed base Worldwide support
+0.5 mA 0
HART Signal
20 mA
0.5 mA 1200 Hz "1" 2200 Hz "0"
Analog Signal
4 mA
Analog Analog Signal Signal 0 1 2
Time (s)
Each HART field device can have two masters. Typically, one is the controller, and the other is a computer with device maintenance or management software.
(1)
The figure is from the HART Communication Protocol Specifications, April, 2001, Revision 6.0, HART Communication Foundation, All Rights Reserved.
About the Modules
15
The HART communication protocol supports two types of communication modes - Burst and Command-response. In the Burst mode, the field device is configured by a master to continuously publish process variables and status data. Burst mode can tie-up a HART communications path and is not supported by Rockwell Automation I/O platforms. In the Command-response mode, the master issues a request command and the field device provides a response. The HART protocol supports point-to-point and multi-drop wiring. Commands can be accepted from either of two master devices. The controller can be one of the master devices and be continuously obtaining information from the field device. The second master can typically be device maintenance or management software, which is used only periodically or as needed to communicate with the field device for configuration or troubleshooting. No matter what command is issued, the response always contains device status information in addition to process variable or device configuration information. As an example, see the figure that shows a handheld communicator as a secondary master.
Primary Master
Secondary Master (handheld communicator as secondary master)
Slave
44219
IMPORTANT
These modules do not support HART Burst mode operation or multi-drop wiring architecture.
16
About the Modules
Benefits of Integrated HART Networks

Most transmitters are available with a HART protocol interface. The type of data available is dependent on the type of instrument. The most common data types are primary process variable, secondary process variables, a digital representation of the analog mA signal, and device status. These data types are mapped to the HART protocol as PV (primary variable), SV (secondary variable), TV (tertiary variable), and FV (fourth variable). The device status is returned with each reply from the device. An example application is a smart mass flowmeter. Using just the standard mA signal from the flowmeter provides one field measurement - flow. Using the mA signal with HART provides additional process information. The mA signal representing flow is still available. The HART configuration of the flowmeter can be set for PV being mass flow, SV being static pressure, TV being temperature, and FV being a digital representation of the mA signal. In addition to these additional process variables, device status is also provided via HART. Instead of one process variable, the controller sees three process variables, has a check on the mA signal, and has a reading of device status. HART connectivity provides all this with no changes to the existing 420 mA wiring. This HART connectivity also provides remote configuration and troubleshooting of field devices using software such as FactoryTalk AssetCentre or Endress+Hauser FieldCare software.
Benefits of HART-enabled I/O Modules

External HART multiplexers were used with analog input modules to capture the HART data. With the 1756-IF8H and 1756-OF8H HART analog I/O modules, no additional hardware of this type is needed. HART modems are built into the analog I/O modules.
About the Modules
17
Work with Asset Management Software
You can use the modules with asset management software. See the figure that shows use of asset management software, such as FactoryTalk AssetCentre software or Endress+Hauser FieldCare software.
Asset Management Software EtherNet/IP Network
44220
Using an I/O Module in the ControlLogix System
ControlLogix modules mount in a ControlLogix chassis and use a removable terminal block (RTB) or a Bulletin 1492 Interface Module(1) cable that connects to an interface module (IFM) to connect all field-side wiring. Before you install and use your module you should have already: installed and grounded a 1756 chassis and power supply(2) as described in the appropriate publication listed in the Additional Resources section of this manual. ordered and received an RTB or IFM and its components for your application.
IMPORTANT
Removable terminal bases and interface modules are not included with your module purchase.
(1)
The ControlLogix system has been agency certified using the ControlLogix RTBs only (for example, catalog numbers 1756-TBCH, 1756-TBNH, 1756-TBSH, and 1756-TBS6H). Any application that requires agency certification of the ControlLogix system using other wiring termination methods may require application-specific approval by the certifying agency. In addition to standard ControlLogix power supplies, ControlLogix redundant power supplies are also available for your application. For more information on these supplies, see the ControlLogix Selection Guide, publication 1756-SG001, or contact your local Rockwell Automation distributor or sales representative.
(2)
18
About the Modules
Features of the Modules
See the figure and table that show the physical features of the ControlLogix analog I/O modules.
Physical Features of the ControlLogix Analog I/O Modules Physical Feature Backplane connector Connector pins Locking tab Slots for keying Status indicators Top and bottom guides Description The backplane connector interface for the ControlLogix system connects the module to the ControlBus backplane. Input/output, power and grounding connections are made to the module through these pins with the use of a removable terminal block (RTB) or interface module (IFM). The locking tab anchors the RTB or IFM cable on the module, maintaining wiring connections. Mechanically keys the RTB to prevent inadvertently making the wrong wire connections to your module. Indicators display the status of communication, module health, and input and output devices. Use these indicators to help in troubleshooting. Guides provide assistance in seating the RTB or IFM cable onto the module. Physical Features of ControlLogix I/O Modules
ControlLogix I/O Module
Indicators Locking Tab
Removable Terminal Block (RTB)
Backplane Connector
Top and Bottom Guides
Connector Pins
Slots for Keying the RTB
40200-M
About the Modules
19
Using Module Identification and Status Information
Each ControlLogix I/O module maintains specific identification information that separates it from all other modules. This information assists you in tracking all the components of your system. For example, you can track module identification information to be aware of exactly what modules are located in any ControlLogix rack at any time. While retrieving module identity, you can also retrieve the modules status. Each module maintains the information as shown in the table.
Module Identification and Status Information Module Identification Product Type Catalog Code Major Revision Minor Revision Status Description Modules product type, such as Digital I/O or Analog I/O module Modules catalog number Modules major revision number Modules minor revision number Modules status - returns this information Controller ownership (if any) Whether module has been configured Device Specific Status, such as: Self-test Flash update in progress Communications fault Not owned (outputs in Program mode) Internal fault (need flash update) Run mode Program mode (output modules only) Minor recoverable fault Minor unrecoverable fault Major recoverable fault Major unrecoverable fault Vendor ID Serial Number Length of ASCII Text String ASCII Text String Module manufacturer vendor, for example Allen-Bradley Module serial number Number of characters in modules text string Number of characters in modules text string
IMPORTANT
You must perform a WHO service to retrieve this information.
20
About the Modules
Preventing Electrostatic Discharge
This module is sensitive to electrostatic discharge. This equipment is sensitive to electrostatic discharge, which can cause internal damage and affect normal operation. Follow these guidelines when you handle this equipment: Touch a grounded object to discharge potential static. Wear an approved grounding wriststrap. Do not touch connectors or pins on component boards. Do not touch circuit components inside the equipment. Use a static-safe workstation, if available. Store the equipment in appropriate static-safe packaging, when not in use.
ATTENTION
Removal and Insertion Under Power
These modules are designed to be installed or removed while chassis power is applied. When you insert or remove the module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations.
WARNING
Be sure that power is removed or the area is nonhazardous before proceeding. Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector. Worn contacts can create electrical resistance that can affect module operation.
Chapter
Understand Module Operation
Read this chapter for information about how analog I/O modules work within the ControlLogix system.
Ownership and Connections
Every I/O module in the ControlLogix system must be owned by a ControlLogix controller to be useful. This owner-controller stores configuration data for every module that it owns and can be located locally or remotely, relative to the I/O modules position. The owner sends the I/O module configuration data to define the modules behavior and begin operation within the control system. Each ControlLogix I/O module must continuously maintain communication with its owner to operate normally. Typically, each module in the system has only one owner. Input modules can have more than one owner. Output modules are limited to a single owner.
21
22
Using RSNetWorx and RSLogix 5000 Software
The I/O configuration portion of RSLogix5000 software generates the configuration data for each I/O module in the control system, whether the module is located in a local or remote chassis. A remote chassis, also known as networked, contains the I/O module but not the modules owner-controller. Remote chassis can be connected to the controller via a scheduled ControlNet or EtherNet/IP network. Configuration data is transferred to the controller during the program download and subsequently transferred to the appropriate I/O modules. I/O modules in the local chassis, and modules in a remote chassis connected via the EtherNet/IP network, are ready to run as soon as the configuration data is downloaded. However, you must run RSNetWorx for ControlNet software to enable I/O modules in a scheduled ControlNet chassis. Running RSNetWorx software transfers configuration data to I/O modules on a scheduled ControlNet network and establishes a network update time (NUT) for the ControlNet network that is compliant with the desired communications options specified for each module during configuration. Any time a controller references an I/O module in a scheduled ControlNet chassis, you must run RSNetWorx software to configure the ControlNet network. Follow these general guidelines when configuring I/O modules: Configure all I/O modules for a given controller using RSLogix 5000 software and download that information to the controller. If the I/O configuration data references a module in a remote chassis connected by a scheduled ControlNet network, run RSNetWorx software.
IMPORTANT
You must run RSNetWorx software whenever a new module is added to a scheduled ControlNet chassis. When a module is permanently removed from a remote chassis, we recommend that RSNetWorx software be run to optimize the allocation of network bandwidth.
23
Direct Connections
A direct connection is a real-time data transfer link between the controller and the device that occupies the slot that the configuration data references. ControlLogix analog I/O modules use direct connections only. When module configuration data is downloaded to an owner-controller, the controller attempts to establish a direct connection to each of the modules the data references. If a controller has configuration data referencing a slot in the control system, the controller periodically checks for the presence of a device there. When a devices presence is first detected, the controller automatically sends the configuration data and one of the following events occurs: If the data is appropriate to the module found in the slot, a connection is made and operation begins. If the configuration data is not appropriate, the data is rejected and an error message displays in the software. In this case, the configuration data can be inappropriate for any of a number of reasons. For example, a modules configuration data can be appropriate except for a mismatch in electronic keying that prevents normal operation. The controller maintains and monitors its connection with a module. Any break in the connection, such as removal of the module from the chassis while under power, causes the controller to set fault status bits in the data area associated with the module. You can use ladder logic to monitor this data area and detect module failures.
Input Module Operation
In traditional I/O systems, controllers poll input modules to obtain their input status. In the ControlLogix system, however, the owner-controller does not poll analog input modules after a connection is established. The modules multicast their data periodically. Multicast frequency depends on the options chosen during configuration and where in the control system that input module physically resides. An input modules communication, or multicasting, behavior varies depending upon whether it operates in the local chassis or in a remote chassis, based on the network type. The following sections detail the differences in data transfers between these set-ups.
24
Input Modules in a Local Chassis
When a module resides in the same chassis as the owner-controller, the following configuration parameters affect how and when the input module multicasts data: Real-time sample Requested packet interval
Real Time Sample (RTS)

This configurable parameter instructs the module to perform the following operations: Scan all of its input channels and store the data into on-board memory. Multicast the updated channel data (as well as other status data) to the backplane of the local chassis.
On-board Memory Status Data Channel Data Channel Data
1
Ch 0 Ch 1 Ch 2 Ch 3 Ch 4 Ch 5
Channel Data Channel Data Channel Data Channel Data Timestamp
41361
IMPORTANT
The real time sample value is set during the initial configuration using RSLogix 5000 software. This value can be adjusted anytime.
25
Requested Packet Interval (RPI)

This configurable parameter also instructs the module to multicast its channel and status data to the local chassis backplane. The requested packet interval instructs the module to multicast the current contents of its on-board memory when the requested packet interval expires (the module does not update its channels prior to the multicast).
On-board Memory Status Data Channel Data Channel Data Channel Data Channel Data Channel Data Channel Data Timestamp Ch 0 Ch 1 Ch 2 Ch 3 Ch 4 Ch 5
41362
IMPORTANT
The requested packet interval value is set during the initial module configuration using RSLogix 5000 software. This value can be adjusted when the controller is in Program mode.
If the real time sample value is less than or equal to the requested packet interval, each multicast of data from the module has updated channel information. In effect, the module is only multicasting at the real time sample rate.
26
If the real time sample value is greater than the requested packet interval, the module multicasts at both the real time sample rate and the requestest packet interval rate. Their respective values dictate how often the owner-controller receives data and how many multicasts from the module contain updated channel data. In the example, the real time sample value is 100 ms and the requested packet interval value is 25 ms. Only every fourth multicast from the module contains updated channel data.
Real Time Sample (RTS) 100 ms - Updated data
Requested Packet Interval 25 ms - Same input data as the previous RTS 25 50 75 100 125 150 175 200 225 250 275 Time (ms) 300 325 350 375 400
40946
Triggering Event Tasks

When configured to do so, ControlLogix analog input modules can trigger an event task. The event task offers ControlLogix controller users a task that executes a section of logic immediately when an event (receipt of new data) occurs. Your ControlLogix analog I/O module can trigger event tasks every real time sample, after the module has sampled and multicast its data. Events tasks are useful for synchronizing process variable (PV) samples and proportional integral derivative (PID) calculations.
IMPORTANT
ControlLogix analog I/O modules can trigger event tasks at every real time sample, but not at the requested packet interval. For example, in the figure, an event task can only be triggered every 100 ms.
27
Input Modules in a Remote Chassis
If an input module resides in a remote chassis, the role of the requested packet interval and the modules real time sample behavior change slightly with respect to getting data to the owner-controller, depending on what network type you are using to connect to the modules.
Remote Input Modules Connected Via ControlNet Network

When remote analog I/O modules are connected to the owner-controller via a scheduled ControlNet network, the requested packet interval and real time sample intervals still define when the module multicasts data within its own chassis. However, only the value of the requested packet interval determines how often the owner-controller receives it over the network. When an requested packet interval value is specified for an input module in a remote chassis connected by a scheduled ControlNet network, in addition to instructing the module to multicast data within its own chassis, the requested packet interval also reserves a spot in the stream of data flowing across the ControlNet network. The timing of this reserved spot does or does not coincide with the exact value of the requested packet interval, but the control system guarantees that the owner-controller receives data at least as often as the specified requested packet interval.
Input Module in Remote Chassis with Requested Packet Interval Reserving Spot in Flow of Data Owner-controller ControlNet Bridge Module ControlNet Bridge Module Input Module
Input data in remote chassis at RTS and RPI
Input data at least as often as RPI
ControlNet Network
40947
The reserved spot on the network and the modules real time sample are asynchronous to each other. This means there are best and worst case scenarios as to when the owner-controller receives updated channel data from the module in a networked chassis.
28
Best Case Scenario - Real Time Sample

In the best case scenario, the module performs a real time sample multicast with updated channel data just before the reserved network slot is made available. In this case, the remotely-located owner-controller receives the data almost immediately.
Worst Case Scenario - Real Time Sample

In the worst case scenario, the module performs a real time sample multicast just after the reserved network slot has passed. In this case, the owner-controller does not receive updated data until the next scheduled network slot. Because it is the requested packet interval and not the real time sample that dictates when the modules data is sent over the network, we recommend the requested packet interval value be set less than or equal to the real time sample to make sure that updated channel data is received by the owner-controller with each receipt of data.
Remote Input Modules Connected Via EtherNet/IP Network

When remote analog input modules are connected to the owner-controller via an EtherNet/IP network, data is transferred to the owner-controller in the following way: At the real time sample or requested packet interval (whichever is faster), the module multicasts data within its own chassis. The 1756-ENBT module in the remote chassis immediately sends the modules data over the network to the owner-controller as long as it has not sent data within a timeframe that is 1/4 the value of the analog input modules requested packet interval. For example, if an analog input module uses an RPI = 100 ms, the 1756-ENBT module sends module data immediately on receiving it if another data packet was not sent within the last 25 ms.
29
Output Module Operation
The requested packet interval parameter governs exactly when an analog output module receives data from the owner-controller and when the output module echoes data. An owner-controller sends data to an analog output module at the period specified in the requested packet interval. Data is not sent to the module at the end of the controllers program scan. When an analog output module receives new data from an owner-controller (every requested packet interval), the module automatically multicasts or echoes a data value that corresponds to the analog signal present at the output terminals to the rest of the control system. This feature, called Output Data Echo, occurs whether the output module is local or remote. Depending on the value of the requested packet interval, with respect to the length of the controller program scan, the output module can receive and echo data multiple times during one program scan. When the requested packet interval is less than the program scan length, the controller effectively lets the modules output channels change values multiple times during a single program scan because the output module is not dependent on reaching the end of the program to send data.
Output Modules in a Local Chassis
When specifying an requested packet interval value for an analog output module, you instruct the controller when to broadcast the output data to the module. If the module resides in the same chassis as the owner-controller, the module receives the data almost immediately after the controller sends it.
Owner-controller
Output Module
Data sent from owner
40949
30
Output Modules in a Remote Chassis
If an output module resides in a remote chassis, the role of the requested packet interval changes slightly with respect to getting data from the owner-controller, depending on what network type you are using to connect to the modules.
Remote Output Modules Connected Via ControlNet Network

When remote analog output modules are connected to the owner-controller via a scheduled ControlNet network, in addition to instructing the controller to multicast the output data within its own chassis, the requested packet interval also reserves a spot in the stream of data flowing across the ControlNet network. The timing of this reserved spot does or does not coincide with the exact value of the requested packet interval, but the control system will guarantee that the output module will receive data at least as often as the specified requested packet interval.
Output Module in Remote Chassis with Requested Protocol Interval Reserving a Spot in Flow of Data Owner-controller ControlNet Bridge Module ControlNet Bridge Module Output Module
Data sent from owner at modules RPI rate
Immediate backplane transfers to module
Output data at least as often as RPI

41360
ControlNet Network
The reserved spot on the network and when the controller sends the output data are asynchronous to each other. This means there are best and worst case scenarios as to when the module receives the output data from the controller in a networked chassis.
31
Best Case Scenario - Requested Packet Interval

In the best case scenario, the controller sends the output data just before the reserved network slot is available. In this case, the remotely located output module receives the data almost immediately.
Worst Case Scenario - Requested Packet Interval

In the worst case scenario, the controller sends the data just after the reserved network slot has passed. In this case, the module does not receive the data until the next scheduled network slot. These best and worst case scenarios indicate the time required for output data to transfer from the controller to the module once the controller has produced it. The scenarios do not take into account when the module will receive new data (updated by the user program) from the controller. That is a function of the length of the user program and its asynchronous relationship with the requested protocol interval.
IMPORTANT
Remote Output Modules Connected Via EtherNet/IP Network

When remote analog output modules are connected to the owner-controller via an EtherNet/IP network, the controller multicasts data in the following way: At the requested packet interval, the owner-controller multicasts data within its own chassis. The 1756-ENBT module in the local chassis immediately sends the data over the network to the analog output module as long as it has not sent data within a timeframe that is 1/4 the value of the analog modules requested protocol interval.
32
Listen-only Mode
Any controller in the system can listen to the data from any I/O module (for example, input data or echoed output data) even if the controller does not own the module. In other words, the controller does not have to own a modules configuration data to listen to it. During the I/O configuration process, you can specify one of several Listen-only modes in the Communication Format field. Choosing a Listen-only mode option lets the controller and module establish communications without the controller sending any configuration data. In this instance, another controller owns the module being listened to.
IMPORTANT
Controllers using the Listen-only mode continue to receive data multicast from the I/O module as long as a connection between an owner-controller and I/O module is maintained. If the connection between all owner-controllers and the module is broken, the module stops multicasting data and connections to all Listening controllers are also broken.
Multiple Owners of Input Modules
Because Listening controllers lose their connections to modules when communications with the owner stop, the ControlLogix system lets you define more than one owner for input modules.
IMPORTANT
Only input modules can have multiple owners. If multiple owners are connected to the same input module, they must maintain identical configuration for that module.
33
In the example, Controller A and Controller B have both been configured to be the owner of the input module.
Multiple Owners with Identical Configuration Data
Controller A Initial Configuration Input Module Controller B Initial Configuration
Input Module Configuration Data Xxxxx Xxxxx Xxxxx
CTR A
CTR B

41056
When multiple controllers are configured to own the same input module, the following events occur: When the controllers begin downloading configuration data, both try to establish a connection with the input module. Whichever controllers data arrives first establishes a connection. When the second controllers data arrives, the module compares it to its current configuration data (the data received and accepted from the first controller). If the configuration data sent by the second controller matches the configuration data sent by the first controller the connection is also accepted. If any parameter of the second configuration data is different from the first, the module rejects the connection; RSLogix 5000 software alerts you to the rejected connection through an error message. The advantage of multiple owners over a Listen-only connection is that now either of the controllers can lose the connection to the module and the module continues to operate and multicast data to the system because of the connection maintained by the other owner-controller.
34
Configuration Changes in an Input Module with Multiple Owners
You must be careful when changing an input modules configuration data in a multiple owner scenario. When the configuration data is changed in one of the owners, for example, Controller A, and sent to the module, that configuration data is accepted as the new configuration for the module. Controller B continues to listen, unaware that any changes were made in the modules behavior.
Multiple Owners with Changed Configuration Data Controller A Input Module Controller B Initial Configuration
Modified Configuration
CTR A
CTR B
Controller B is unaware that changes were made by Controller A.
41056
IMPORTANT
A dialog in RSLogix 5000 software alerts you to the possibility of a multiple owner situation and lets you inhibit the connection before changing the modules configuration. When changing configuration for a module with multiple owners, we recommend the connection be inhibited. To prevent other owners from receiving potentially erroneous data, you much follow these steps when changing a modules configuration in a multiple owner scenario while online: For each owner-controller, inhibit the controllers connection to the module, either in the software on the Connection tab or the dialog warning of the multiple owner condition. Make the appropriate configuration data changes in the software, as described in the RSLogix 5000 software section of this manual. Repeat steps 1 and 2 for all owner-controllers, making the same changes in all controllers. Disable the Inhibit box in each owners configuration.
Chapter
Using Module Features
This chapter describes features that are common to ControlLogix analog I/O modules.
Determining Input Module Compatibility
ControlLogix analog input modules convert an analog signal of either voltage or current that is connected to the module's screw terminals into a digital value. The digital value that represents the magnitude of the analog signal is then transmitted on the backplane to either a controller or other control entities.
Determining Output Module Compatibility
ControlLogix output modules convert a digital value that is delivered to the module via the backplane into an analog signal of voltage or current. The digital value represents the magnitude of the desired analog signal. The module converts the digital value into an analog signal and provides this signal on the module's screw terminals.
Features Common to Analog I/O Modules
These features are common to all ControlLogix analog I/O modules: Removal and insertion under power Module fault reporting Fully software configurable Electronic keying Access to system clock for timestamping functions Rolling timestamp Producer/consumer model Status indicator information Full Class I Division 2 compliance UL, CSA, FM, CE, C-Tick, EEx, TUV agency certification Field calibration Sensor offset Latching of alarms
35
36
Removal and Insertion Under Power (RIUP)

All ControlLogix I/O modules can be inserted and removed from the chassis while power is applied. This feature provides greater availability of the overall control system because, while the module is being removed or inserted, there is no additional disruption to the rest of the controlled process.
Module Fault Reporting

ControlLogix analog I/O modules provide both hardware and software indication when a module fault has occurred. Each module has an LED fault indicator and RSLogix 5000 software graphically displays this fault and includes a fault message describing the nature of the fault. This feature lets you determine how your module has been affected and what action should be taken to resume normal operation.
Fully Software Configurable

The RSLogix 5000 software uses a custom, easily-understood interface to write configuration. All module features are enabled or disabled through the I/O configuration portion of the software. You can also use the software to interrogate any module in the system to retrieve: serial number. revision information. catalog number. vendor identification. error/fault information. diagnostic counters.
By eliminating such tasks as setting hardware switches and jumpers, the software makes module configuration easier and more reliable.
37
Electronic Keying
Instead of plastic mechanical backplane keys, electronic keying lets the ControlLogix system control what modules belong in the various slots of a configured system. During module configuration, you must choose one of the following keying options for your I/O module: Exact Match Compatible Match Disable Keying When the controller attempts to connect to and configure an I/O module (for example, after program download), the module compares the following parameters before letting the connection and configuration be accepted: Vendor Product Type Catalog Number Major Revision - Change that affects the modules function or RSLogix 5000 interface Minor Revision - Change that does not affects the modules function or RSLogix 5000 interface The comparison is made between the keying information present in the I/O module and the keying information in the controllers program. This feature can prevent the inadvertent operation of a control system with the wrong module in the wrong slot. For example, if you select Exact Match and a module with revision 2.2 is placed in a location configured for a module with revision 2.4, the controller does not make a connection to the new module because of the mismatched revisions.
38
Keying Options Available with ControlLogix Analog I/O Modules Keying Option Exact Match Compatible Match Definition All of the parameters must match or the inserted module rejects a connection to the controller. The Compatible Match mode lets an I/O module determine if it can emulate the module defined in the configuration sent from the controller. With ControlLogix analog I/O modules, the module can emulate older revisions. The module accepts the configuration if the configurations major.minor revision is less than or equal to the physical modules revision. For example, if the configuration contains a major.minor revision of 1.7, the module inserted into the slot must have a firmware revision of 1.7 or later for a connection to be made. When a module is inserted with a major.minor revision that is less than the revision for which the slot is configured (the module has a revison of 1.6 and the slot is configured for a module with revision 1.8), no connection is made between the controller and the I/O module.
TIP
We recommend using Compatible Match whenever possible. Remember that with major revision changes, the module only works to the level of the configuration. At the time of this printing, the ControlLogix analog I/O modules all used a major revision of 1.(1) If a new major revision for a ControlLogix analog I/O module is released, consider this example. If a slot is configured for a module with major.minor revision of 1.7 and you insert a module with a major.minor revision of 2.3, the module works at the 1.7 level, with respect to module functions that are related to RSLogix 5000 software, such as interface changes. However, fixes that are affected by the modules firmware, would work at the 2.3 revision level. If possible, we suggest you make sure configuration is updated to match the revision levels of all I/O modules. Failure to do so does not prevent the application from working but defeats the purpose of upgrading your modules revision levels.
Disable Keying
The inserted module attempts to accept a connection to the controller regardless of its type.
ATTENTION
Be extremely cautious when using the disable keying option; if used incorrectly, this option can lead to personal injury or death, property damage, or economic loss.
If keying is disabled, a controller makes a connection with most modules of the same type as that used in the slot configuration. For example, if a slot is configured for a 1756-IF16 (16-point non-isolated analog current/voltage input module), and a 1756-IF8 (8-point non-isolated analog current/voltage input module) is inserted into the slot, the controller can establish a connection because keying is disabled. Even if keying is disabled, a controller does not establish a connection if the slot is configured for one module type (for example, input module) and a module of another type (for example, output module) is inserted in the slot.
(1)
Minor revisions are incremented by single counts such that minor level 10 (major.minor revision level = 1.10) follows minor revision level 9 (1.9).
39
Access to System Clock for Timestamping Functions

Controllers within the ControlLogix chassis maintain a system clock. This clock is also known as the coordinated system time (CST). You can configure your analog I/O modules to access this clock and timestamp input data or output echo data when the module multicasts to the system. This feature provides accurate calculations between events to help you identify the sequence of events in either fault conditions or in the course of normal I/O operations. The system clock can be used between multiple modules in the same chassis.
Rolling Timestamp
Each module maintains a rolling timestamp that is unrelated to the coordinated system time. The rolling timestamp is a continuously running 15-bit timer that counts in milliseconds. For input modules, whenever a module scans its channels, it also records the value of the rolling timestamp at that time. Your program can then use the last two rolling timestamp values and calculate the interval between receipt of data or the time when new data was received. For output modules, the rolling timestamp value is updated only when new values are applied to the Digital to Analog Converter (DAC).
Producer/Consumer Model
By using the Producer/Consumer model, ControlLogix I/O modules can produce data without having been polled by a controller first. The modules produce the data and any owner or listen-only controller device can decide to consume it. For example, an input module produces data and any number of processors can consume the data at the same time. This eliminates the need for one processor to send the data to another processor.
40
Status Indicator Information

Each ControlLogix analog I/O module has status indicators on the front of the module that let you to check the module health and operational status of a module. See the table that describes what status each status indicator represents.
Status of Status Indicators Status Module status Display Indicates Module communication status
Calibration status Module is in Calibration mode
Full Class I Division 2 Compliance

All ControlLogix analog I/O modules maintain CSA Class I Division 2 system certification. This lets you place the ControlLogix system in an environment other than only a 100% hazard free.
IMPORTANT
Modules should not be pulled under power, nor should a powered RTB be removed, when a hazardous environment is present.
UL, CSA, FM, CE, C-Tick, EEx, TUV Agency Certification

Any ControlLogix analog I/O modules that have obtained various agency certifications are marked as such.
Field Calibration
ControlLogix analog I/O modules let you calibrate on a channel-by-channel or module-wide basis. RSLogix 5000 software provides a software interface to perform calibration.
41
Sensor Offset
You can add this offset directly to the input or output during calibration calculation. The purpose of this feature is to let you compensate for any sensor offset errors that may exist; such offset errors are common in thermocouple sensors.
Latching of Alarms
The latching feature lets analog I/O modules latch an alarm in the set position once it has been triggered, even if the condition causing the alarm to occur disappears.
Data Format
During initial configuration of any ControlLogix analog I/O module, you must choose a communications (Input Data) format. The format chosen determines the data format of data exchanged between the owner-controller and the I/O module. The module uses a 32-bit IEEE floating-point format.
ControlLogix HART Analog Modules Multicast in These Formats Format Type Analog Only (do not get HART data) Analog with HART PV (get HART data) Description Analog signal values Analog alarm status Analog signal values Analog alarm status HART secondary process variable Device health
Your choice of data format can restrict the features available with an I/O module.
Module Inhibiting
Module inhibiting lets you indefinitely suspend a connection between an owner-controller and an analog I/O module. This process can occur in either of the following ways:
42
You write configuration for an I/O module, but inhibit the module to prevent it from communicating with the owner-controller. In this case, the owner does not establish a connection and configuration is not sent to the module until the connection is uninhibited. In your application, a controller already owns a module, has downloaded configuration to the module, and is currently exchanging data over the connection between the devices. In this case, you can inhibit the module, and the owner-controller behaves as if the connection to the module does not exist.
IMPORTANT
Whenever you inhibit an output module, it enters the Program mode and all outputs change to the state configured for the Program mode. For example, if an output module is configured so that the state of the outputs go to zero (0) during Program mode, whenever that module is inhibited, the outputs go to zero (0). Note that inhibiting the connection causes communication with the module to stop. If, for example, a cable subsequently breaks, the module does not go to its Fault Mode settings, even if configured to do so on communication failure. It remains in its Program mode state.
The following examples are instances where you can need to use module inhibiting: Multiple controllers own the same analog input module. A change is required in the modules configuration; however, the change must be made to the program in all controllers. In this case, you can: a. inhibit the module. b. change configuration in all controllers. c. uninhibit the module. You want to FLASH upgrade an analog I/O module. We recommend you: a. inhibit the module. b. perform the upgrade. c. uninhibit the module. You are using a program that includes a module that you do not physically possess yet, but you do not want the controller to continually look for a module that does not exist yet. In this case, you can inhibit the module in your program until it physically resides in the proper slot.
43
Understanding the Relationship Between Module Resolution and Scaling
The following concepts are closely related and must be explained in conjunction with each other: Module resolution Scaling
Module Resolution
Resolution is the smallest amount of change that the module can detect. Analog input modules are capable of 16 bit resolution. Output modules are capable of 1316 bit resolution, depending on the module type. The 16 bits represent 65,536 counts. This total is fixed but the value of each count is determined by the operational range you choose for your module. For example, if you are using the 1756-IF8H module in 020 mA mode, your modules available current range equals 21 mA. Divide your range by the number of counts to figure out the value of each count. In this case, one count is approximately 0.34 A.
Module Resolution
0 mA 65,536 counts 21 mA/65,536 counts ~ 0.34 A/count
21 mA
IMPORTANT
A modules resolution is fixed. It does not change regardless of what data format you choose or how you decide to scale your module in Floating Point mode. Resolution is based on the module hardware and the range selected. If you use a sensor with limited range, you do not change the module resolution.
44
See the table that lists the resolution for each modules range.
Current Values Represented in Engineering Units Module 1756-IF8H Range +/- 10.25V 0 10.25V 05.125V 020.5 mA 3.4220.58 mA +/- 10.4V 021mA 3.4220.58 mA Number of Significant Bits 16 bits Resolution 320 V/count 160 V/count 80 V/count 0.32 A/count 320 V/count 0.65 A/count
1756-OF8H
16 bits 15 bits
IMPORTANT
Because these modules must provide for possible calibration inaccuracies, resolution values represent the available Analog to Digital or Digital to Analog counts over the specified range.
Scaling
With scaling, you change a quantity from one notation to another. For ControlLogix analog I/O modules, scaling is only available with the floating point data format. When you scale a channel, you must choose two points along the modules operating range and apply low and high values to those points. Scaling lets you configure the module to return data to the controller so that 4 mA returns a value of 0% in engineering units and 20 mA returns a value of 100% in engineering units.
Module Resolution Compared to Module Scaling
Module Resolution 0 mA Module scaling represents the data returned from the module to the controller 65,536 Counts 21 mA
4 mA Module Scaling 0% in Engineering Units
20 mA 100% in Engineering Units
45
IMPORTANT
In choosing two points for the low and high value of your application, you do not limit the range of the module. The modules range and its resolution remain constant regardless of how you scale it for your application.
The module can operate with values beyond the 420 mA range. If an input signal beyond the low and high signals is present at the module (for example, 3 mA), that data will be represented in terms of the engineering units set during scaling. See the table that shows example values that can appear based on the example.
Current Values Represented in 0100% Engineering Units Current 3 mA 4 mA 12 mA 20 mA 21 mA Engineering Units Value -3.625% 0% 50% 100% 103.625%
46
Notes:
Chapter
About the HART Analog Input Module
This chapter describes features of the 1756-IF8HControlLogix HART analog voltage/current input module. In addition to the features described in this chapter, the analog voltage/current input module supports all features described in the Using Module Features chapter of this manual including the following: Removal and insertion under power Module fault reporting Fully software configurable Electronic keying Access to system clock for timestamping functions Rolling timestamp Producer and consumer model Status indicator information Full Class 1 Division 2 compliance UL, CSA, FM, CE, C-Tick, EEx, and TUV agency certification when the module is marked Field calibration Sensor offset Latching of alarms
Work with the Differential Wiring Method
The differential wiring method provides for application where separate signal pairs or a common ground is not available. Differential wiring is used for environments where improved noise immunity is needed.
47
48
Choosing a Data Format
Data format determines which values are included in the Input tag of the module and the features that are available to your application. You choose a data format when you choose a value for Input Data. You can choose one of the following data formats as shown in the table.
Features Available in Each Data Format Data Format Analog Only Analog and HART PV Features Available Analog signal values Analog alarm status Analog signal values Analog alarm status HART secondary process variables Device health
Module Features
A list of features in 1756-IF8H modules is as follows: Multiple input range Module filter Real time sampling Underrange and overrange detection Process alarms Rate alarm Wire-off detection Highway Addressable Remote Transducer (HART) communication
Multiple Input Ranges

You can select from a series of operational ranges for each channel on your module. The range designates the minimum and maximum signals that are detectable by the module. Possible ranges include the following: -1010V 05V 010V 020 mA 420 mA (HART instruments use this)
49
Module Filter
The module filter attenuates the input signal beginning at the specified frequency. This feature is applied on a module-wide basis, affecting all channels. The module attenuates the selected frequency by approximately -3 dB or 0.707 of the applied amplitude. An input signal with frequencies above the selected frequency is attenuated more while frequencies below the selection receive no attenuation.
.707
60 Hz
In addition to frequency rejection, a by-product of the filter selection is the minimum sample rate (RTS) that is available. For example, the 1000 Hz selection does not attenuate any frequencies less than 1000 Hz, but provides for sampling of all 16 channels within 18 ms. The 10 Hz selection attenuates all frequencies above 10 Hz and only provides for sampling all 16 channels within 488 ms.
IMPORTANT
Do not use 1000 Hz module filter with HART instruments.
IMPORTANT
60 Hz is the default setting for the module filter. This setting provides approximately 3 dB of filtering of a 60 Hz input.
50
Use the table to choose a module filter setting.

Module Filter Selections with Associated Performance Data Module Filter Setting (-3dB)(1) (2) Minimum Sample Time (RTS) Effective Resolution
(1) (2)
10 Hz 244 ms 16 bits
50 Hz/ 60 Hz (default) 44 ms 16 bits
1000 Hz 11 ms 12 bits
For optimal 50/60 Hz noise rejection (>80 dB), choose the 10 Hz filter. Worst case settling time to 100% of a step change is double the real time sample time.
Real Time Sampling (RTS)

This parameter instructs the module how often to scan its input channels and obtain all available data. After the channels are scanned, the module multicasts that data. This feature is applied on a module-wide basis. During module configuration, you specify a real time sampling (RTS) period and a requested packet interval (RPI) period. Both of these features instruct the module to multicast data, but only the RTS feature instructs the module to scan its channels before multicasting.
Underrange and Overrange Detection

This feature detects when the input module is operating beyond limits of the input range. This status indication tells you that the input signal is not being measured accurately because the signal is beyond the measuring capability of the module. For example, the module cannot distinguish between 10.25V and 20V. Use the table to see the input ranges of input modules and the lowest and highest signal available in each range before the module detects an underrange and overrange condition.
Low and High Signal Limits on Nonisolated Input Modules Input Module 1756-IF8H Available Range -1010V 010V 05V 020 mA 420 mA Lowest Signal in Range -10.25V 0V 0V 0 mA 3.42 mA Highest Signal in Range 10.25V 10.25V 5.125V 20.58 mA 20.58 mA
51
Digital Filter
The digital filter smooths input data noise transients. This feature is applied on a per channel basis. The digital filter value specifies the time constant for a digital first order lag filter on the input. It is specified in units of milliseconds. A value of 0 disables the filter. The digital filter equation is a classic first order lag equation.
[ t] Yn = Yn-1 + t + TA (Xn Yn-1)
Yn = present output, filtered peak voltage (PV) Yn-1 = previous output, filtered PV t = module channel update time (seconds) TA = digital filter time constant (seconds) Xn = present input, unfiltered PV
Using a step input change to illustrate the filter response, as shown in the figure, you can see that when the digital filter time constant elapses, 63.2% of the total response is reached. Each additional time constant achieves 63.2% of the remaining response.
Filter Response
100%
63% Amplitude 0 Unfiltered Input TA = 0.01 s TA = 0.5 s TA = 0.99 s 0 0.01 0.5 0.99 Time in s
16723
52
Process Alarms
Process alarms alert you when the module has exceeded configured high or low limits for each channel. You can latch process alarms. These are set at the following configurable alarm trigger points: High high High Low Low low
The values for each limit are entered in scaled engineering units.
Alarm Deadband
You can configure an Alarm Deadband to work with the process alarms. The deadband lets the process alarm status bit remain set, despite the alarm condition disappearing, as long as the input data remains within the deadband of the process alarm. See the figure that shows input data that sets each of the alarms at some point during module operation. In this example, Latching is disabled; therefore, each alarms turns OFF when the condition that caused it to set returns to normal.
Input Data That Sets Each Of the Alarms
High high alarm turns ON High alarm remains ON High high High alarm turns ON High Normal input range Low alarms turns ON Low Low low
43153
High high alarm turns OFF High alarm remains ON
High alarm turns OFF
Low alarms turns OFF Alarm deadbands
Low low alarms turns ON Low alarm remains ON
Low low alarms turns OFF Low alarm remains ON
53
Rate Alarm
The values for each limit are entered in scaled engineering units per second. The rate alarm triggers if the rate of change between input samples for each channel exceeds the specified rate-alarm trigger point for that channel.
Wire Off Detection

The 1756-IF8H modules alert you when a signal wire is disconnected from one of its channels or the RTB is removed from the module. When a wire off condition occurs for this module, two events occur: input data for that channel changes to a specific scaled value. a fault bit is set in the input tag, which may indicate the presence of a wire off condition. Because 1756-IF8H modules can be applied in voltage or current applications, differences exist as to how a wire off condition is detected in each application. See the table that lists the differences that occur when a wire off condition occurs in various applications.
Differences When a Wire Off Condition Occurs When the Wire Off Condition Occurs in This Application Voltage These Events Occurs
Input data for that channel changes to the scaled value associated with the overrange signal value of the selected operational range (max scaled value) The ChxOverrange (x=channel number) tag is set to 1
Current Applications
Input data for that channel changes to the scaled value associated with the underrange signal value of the selected operational range (min possible scaled value) The ChxUnderrange (x=channel number) tag is set to 1 In current applications, if wire off detection occurs for one of the following reasons: The removable terminal block was disconnected from the module Both the signal wire and the jumper wire were disconnected The module reacts with the same conditions as described in differential voltage applications
54
Wire the Modules
See the figures and tables that show how to wire the module for voltage and current inputs. HART communication is active with current inputs only.
Wire the Module for Voltage Inputs
Voltage Input +V IN0+ -V IN0IN1+ IN1RTN IN2+ IN2IN3+ IN3IN4+ IN4IN5+ IN5RTN IN6+ IN6IN7+ IN72 4 6 8 1 3 5 7 I RTN-0 NC I RTN-1 NC RTN I RTN-2 NC I RTN-3 NC I RTN-4 NC I RTN-5 NC RTN I RTN-6 NC I RTN-7 NC
44222
10 9 12 11 14 13 16 15 18 17 20 19 22 21 24 23 26 25 28 27 30 29 32 31 34 33 36 35
Wiring the Module for Voltage Inputs Channel Channel 0 Channel 1 Channel 2 Channel 3 Terminal IN0+, IN0IN1+, IN1IN2+, IN2IN3+, IN3Channel Channel 4 Channel 5 Channel 6 Channel 7 Terminal IN4+, IN4IN5+, IN5IN6+, IN6IN7+, IN7-
55
Wire the Module for Current Inputs
2 Wire Current Input

2 Wire XMTR
24V DC Power Supply
+ -
+-
IN0+ IN0IN1+ IN1RTN IN2+ IN244222
2 4 6 8
1 3 5 7
I RTN-0 NC I RTN-1 NC RTN I RTN-2 NC I RTN-3 NC I RTN-4 NC I RTN-5 NC RTN I RTN-6 NC I RTN-7 NC
4 Wire Current Input
10 9 12 11 14 13 16 15 18 17 20 19 22 21 24 23 26 25 28 27 30 29 32 31 34 33 36 35
+ + + 24V DC 4 Wire Power XMTR Supply - - -
IN3+ IN3IN4+ IN4IN5+ IN5RTN IN6+ IN6IN7+ IN7-
44223
Wire the Module for Current Inputs Channel Channel 0 Channel 1 Channel 2 Channel 3 Terminal IN0+, IN0-, iRTN0 IN1+, IN1-, iRTN1 IN2+, IN2-, iRTN2 IN3+, IN3-, iRTN3 Channel Channel 4 Channel 5 Channel 6 Channel 7 Terminal IN4+, IN4-, iRTN4 IN5+, IN5-, iRTN5 IN6+, IN6-, iRTN6 IN7+, IN7-, iRTN7
Using Input Circuit Diagrams
This section shows the 1756-IF8H modules input circuit diagrams.
56
1756-IF8H Current Input Circuit

+15 V 10 M INO+ i Differential Current Input Jumper 249 IRTN-O 1/4 Watt 0.01 F INO10 M -15 V RTN RTN RTN RTN 22 K 0.01 F 22 K + Analog to Digital Converter
1756-IF8H Voltage Input Circuit

+15 V INO+ + Differential Voltage Inputs I RTN-O V INO10 M -15 V RTN RTN RTN RTN 22 K 10 M 249 1/4 Watt 0.01 F 0.01 F 22 K + -
Analog to Digital Converter
1756-IF8H Module Fault and Status Reporting
The 1756-IF8H module multicasts status/fault data to the controller with its channel data. The fault data is arranged to let you choose the level of granularity you desire for examining fault conditions. Three levels of tags work together to provide an increasing degree of detail as to the specific cause of faults on the module.
57
See the table that lists tags you can examine in ladder logic to indicate when a fault has occurred.
Tags That Can Be Examined in Ladder Logic Tag Module Fault Word Channel Fault Word Channel Status Word HART Faults HART Device Status Description This word provides fault summary reporting. Its tag name is ModuleFaults. This word provides underrange, overrange, and communication fault reporting. Its tag name is ChannelFaults. These words, one per channel, provide individual channel underrange and overrange fault reporting for process alarms, rate alarms and calibration faults. Its tag name is ChxStatus. This provides HART communication status. The tag name is HARTFaults or ChxHARTFault.. This provides HART field device health. The tag name is HART.ChxDeviceStatus.
1756-IF8H Fault Reporting

Module Fault 7 = AnalogGroupFault 2 = Calibrating 1 = Cal Fault 6, 5, 4, and 3 are not used
See the table that offers an overview of the fault reporting process for the 1756-IF8H module.
1 When the module is calibrating, all bits in the Channel Fault word are set.
Channel Fault 7 = Ch7Fault 6 = Ch6Fault 5 = Ch5Fault 4 = Ch4Fault 3 = Ch3Fault 2 = Ch2Fault 1 = Ch1Fault 0 = Ch0Fault
If set, any bit in the Channel Fault word also sets the Analog Group Fault in the Module Fault word.
Channel Status (One for each channel) 7 = ChxCalFault 6 = ChxUnderrange 5 = ChxOverrange 4 = ChxRateAlarm 3 = ChxLAlarm 2 = ChxHAlarm 1 = ChxLLAlarm 0 = ChxHHAlarm
A channel calibration fault sets the calibration fault in the Module Fault word. 7 6 5
An underrange, overrange condition sets appropriate Channel Fault bits.
Alarm bits 04 in the Channel Status word do not set additional bits at any higher level. You must monitor these conditions here.
41514
58
1756-IF8H Module Fault Word Bits

Bits in this word provide the highest level of fault detection. A nonzero condition in this word reveals that a fault exists on the module. You can examine further to isolate the fault. See the table that lists tags that can be examined in ladder logic to indicate when a fault has occurred.
Tags That Can Be Examined in Ladder Logic Tag Analog Group Fault Calibrating Calibration Fault Description This bit is set when any bits in the Channel Fault word are set. Its tag name is AnalogGroupFault. This bit is set when any channel is being calibrated. When this bit is set, all bits in the Channel Fault word are set. Its tag name is Calibrating. This bit is set when any of the individual Channel Calibration Fault bits are set. Its tag name is CalFault.
1756-IF8H Channel Fault Tags

During normal module operation, bits in the Channel Fault word are set if any of the respective channels has an Under or Overrange condition. Checking this word for a nonzero value is a quick way to check for Under or Overrange conditions on the module. See the table that lists the conditions that set all Channel Fault word bits.
Conditions That Set All Channel Fault Word Bits This Condition Sets All Channel Fault Word Bits A channel is being calibrated A communications fault occurred between the module and its owner-controller And Causes the Module to Display the Following in the Channel Fault Word Bits 16#00FF 16#FFFF
Your logic can monitor the Channel Fault Word bit for a particular input to determine the status of that point.
Chapter
About the HART Analog Output Module
This chapter describes features of the 1756-OF8H ControlLogix HART analog output module. The module supports the features described in the Using Module Features chapter of this manual including the following: Removal and insertion under power Module fault reporting Fully software configurable Electronic keying Access to system clock for timestamping functions Rolling timestamp Producer and consumer model Status indicator information Full Class I Division 2 compliance UL, CSA, FM, CE, C-Tick, EEx, TUV agency certification when product is marked Field calibration Sensor offset Latching of alarms HART communication
Choosing a Data Format
You choose a data format when you choose an Input Data format. The Input Data format: defines the format of channel data sent from the controller to the module. defines the format of the data echo that the module produces. determines the features that are available to your application. See the table that lists the features that are available in each format.
59
60
Feature Available in Each Data Format Data Format Analog Only Analog and HART PV Features Available Analog signal values Analog alarm status Analog signal values Analog alarm status HART secondary process variable Device health
Features Specific to Analog Output Modules
This list shows features of the analog output module. Ramping and rate limiting Hold for initialization Open wire detection Clamping and limited Clamp and limit alarms Data echo
Ramping/Rate Limiting
Ramping limits the speed at which an analog output signal can change. This prevents fast transitions in the output from damaging the devices that an output module controls. Ramping is also known as rate limiting. See the table that describes the types of ramping that are possible.
Ramping Types Ramping Types Run mode ramping Description This type of ramping occurs when the module is in Run mode and limits the rate at which the output changes from one commanded value to another. This type of ramping occurs when the controller is placed in the Program mode. The present output value changes to the Program Value. If the connection to the module is Inhibited, the Program mode value and ramp rate are applied. This type of ramping occurs when there is a communication or controller fault. The output signal changes to the Fault Value after a communication fault occurs.
Ramp-to-program mode
Ramp-to-fault mode
61
The maximum rate of change in outputs is expressed in engineering units per second and called the maximum ramp rate. For additional information about ramp rate, in this manual refer to Chapter 6, Configuring the Modules, which describes how you can set Ramp Rate on the output Limits dialog.
Hold for Initialization

Hold for Initialization causes outputs to hold present state until the value commanded by the controller matches the value at the output screw terminal within 0.1% of full scale, providing a bumpless transfer. If Hold for Initialization is selected, outputs hold if any of the these conditions occur: Initial connection is established after power-up A new connection is established after a communications fault occurs There is a transition to Run mode from Program state The ChxInHold bit for a channel indicates that the channel is holding.
Open Wire Detection

This feature detects when current flow is not present at any channel. The 1756-OF8H module must be configured for 020 mA or 420 mA operation to use this feature. At least 0.1 mA of current must be flowing from the output for detection to occur. When an open wire condition occurs at any channel, a status bit named ChxOpenWire is set for that channel.
Clamping and Limiting

Clamping limits the output from the analog module to remain within a range configured by the controller, even when the controller commands an output outside that range. This safety feature sets a high clamp and a low clamp. Once clamps are set for a channel, any data received from the controller that exceeds those clamps sets a limit alarm and transitions the output to that limit but not beyond the configured clamp value.
62
For example, an application may set the high clamp on a module for 8V and the low clamp for -8V. If a controller sends a value corresponding to 9V to the module, the module will only apply 8V to its screw terminals. The signal value actually applied is reflected in the Input Tag ChxData field. Clamping limits are entered in Engineering Units.
Clamp and Limit Alarms

This function works directly with clamping. When a module receives a data value from the controller that exceeds clamping limits, it applies the clamping limit to the signal value and sends a status bit to the controller, notifying it that the commanded output data value exceeds the clamping limits. Using the example, if a channel has clamping limits of 8V and -8V but then receives data to apply 9V, only 8V is applied to the screw terminals and the module sends a status bit back to the controller informing it that the 9V value exceeds the channels clamping limits. Clamping alarms can be disabled or latched on a per channel basis. Clamping limits are entered in Engineering Units.
Data Echo
Data Echo automatically multicasts channel data values which match the analog value that was applied to the modules screw terminals at that time. Fault and status data are also sent. If selected in the Input Data format, HART secondary process variables and device health are also sent. An example is that I.ChxData is the echo of O.ChxData. They might be different due to Ramp, Clamp, or Hold for Initialization.
63
Wire the Modules
See the figure that shows how to wire the module. Voltage outputs use the terminal block pins labelled VOUT-# and RTN. Current outputs use the terminal block pins labelled IOUT-# and RTN. HART communication is active with current outputs only.
44224
64
Using Module Block and Output Circuit Diagrams
This section shows the module output circuit diagram.

1756-OF8H Output Circuit
+ -
250
V OUT - #
0.1 F D/A Converter 5K 100 pF
24V
16K
+18.6V 50 2K 100
Amplifier
I OUT - x
24V
RTN RTN RTN RTN
65
1756-OF8H Module Fault and Status Reporting
The 1756-OF8H modules multicast status and fault data to the controller with their channel data. The fault data is arranged to let you choose the level of granularity you desire for examining fault conditions. Three levels of tags work together to provide increasing degree of detail as to the specific cause of faults on the module. See the table that lists tags that you can examine in ladder logic to indicate when a fault occurred.
Tags That Can Be Examined in Ladder Logic Tag Module Faults Channel Faults HART Faults Channel Status Tags Description Of What Word Provides Fault summary reporting Clamp and and communications fault reporting HART communication status Individual channel limit, hold, open wire, ramp status, and calibration faults. HART field device health Tag Name ModuleFaults ChannelFaults or Chxfault HARTFaults or ChxHARTFault ChxStatus
HART Device Status
HART.ChxDeviceStatus
66
1756-OF8H Fault Reporting

Module Faults 7 = AnalogGroupFault 4 = Calibrating 3 = CalFault 6, 5, 2, 1, and 0 are not used by the 1756-OF8H module. 7
See the figure that offers an overview of the fault reporting process.
Overview of Fault Reporting Process
When the module is calibrating, all bits in the Channel Fault word are set.
If set, any bit in the Channel Fault word, also sets the Analog Group Fault in the Module Fault word. Channel Faults 7 = Ch7Fault 6 = Ch6Fault 5 = Ch5Fault 4 = Ch4Fault 3 = Ch3Fault 2 = Ch2Fault 1 = Ch1Fault 0 = Ch0Fault 7 A channel calibration fault sets the calibration fault in the Module Fault word. 6 5 4 3 2 1 0
7 Channel Status Tags 7 = ChxOpenWire 5 = ChxNotANumber 4 = ChxCalFault 3 = ChxInHold 2 = ChxRampAlarm 1 = ChxLLimitAlarm 0 = ChxHLimitAlarm 6 is not used by 1756-OF8H modules.
Not a Number, Output in Hold, and Ramp Alarm conditions do not set additional bits. You must monitor them here.
41519
1756-OF8H modules use 8-Channel Status words.
67
Module Fault Word Bits

Bits in this word provide the highest level of fault detection. A nonzero condition in this word reveals that a fault exists on the module. You can examine further down to isolate the fault. See the table that lists tags that are found in the Module Fault word.
Tags Found in the Module Fault Word Tag Analog Group Fault Calibrating Description This bit is set when any bits in the Channel Fault word are set. This bit is set when any channel is being calibrated. When this bit is set, all bits in the Channel Fault word are set. This bit is set when any of the individual Channel Calibration Fault bits are set. Tag Name AnalogGroupFault Calibrating
Calibration Fault
CalFault
Channel Fault Word Bits

During normal module operation, Channel Fault word bits are set if any of the respective channels has a High or Low Limit Alarm or an Open Wire condition (020 mA or 420 mA configurations only). When using the Channel Fault Word, the 1756-OF8H module uses bits 07. Checking this word for a nonzero condition is a quick way to check for these conditions on a channel. See the table that lists the conditions that set all Channel Fault word bits.
Conditions That Set All Channel Fault Word Bits This Condition Sets All Channel Fault Word Bits A channel is being calibrated A communications fault occurred between the module and its owner-controller And Causes the Module to Display the Following in the Channel Fault Word Bits 00FF FFFF
Your logic should monitor the Channel Fault bit for a particular output, if you either enable output clamping or are checking for an open wire condition (020 mA configuration only). Your logic can use the bit in Channel Faults, for example, Ch2Fault, to take failure recovery action, such as signaling CVFault on a PIDE function block.
68
Channel Status Words Bits

Any of the Channel Status words (8 words for 1756-OF8H modules), one for each channel, display a nonzero condition if that particular channel has faulted. Some of these bits set bits in other Fault words. When the High or Low Limit Alarm bits (ChxHLimitAlarm or ChxLLimit Alarm) in any of the words are set, the appropriate bit is set in the Channel Fault word. When the Calibration Fault bit (CalFault) is set in any of the words, the Calibration Fault bit (bit 11) is set in the Module Fault word. See the table that lists the conditions that set each of the word bits.
Conditions That Set Each of the Word Bits Tag (status word) ChxOpenWire Bit Bit 7 Event That Sets This Tag This bit is set only if the configured Output Range is 020 or 420 mA and the circuit becomes open due to a wire falling off or being cut when the output being driven is above 0.1 mA. The bit remains set until correct wiring is restored. This bit is set when the output value received from the controller is NotANumber (the IEEE NAN value). The output channel holds its last state. This bit is set when an error occurred when calibrating. This bit also sets the appropriate bit in the Channel Fault word. This bit is set when the output channel is currently holding. The bit resets when the requested Run mode output value is within 0.1% of full-scale of the current echo value. This bit is set when the output channels requested rate of change would exceed the configured maximum ramp rate requested parameter. It remains set until the output reaches its target value and ramping stops. If the bit is latched, it remains set until it is unlatched. This bit is set when the requested output value is beneath the configured low limit value. It remains set until the requested output is above the low limit. If the bit is latched, it remains set until it is unlatched. This bit is set when the requested output value is above the configured high limit value. It remains set until the requested output is below the high limit. If the bit is latched, it remains set until it is unlatched.
ChxNotaNumber ChxCalFault ChxInHold ChxRampAlarm
Bit 5 Bit 4 Bit 3 Bit 2
ChxLLimitAlarm
Bit 1
ChxHLimitAlarm
Bit 0
Chapter
Configuring the Modules
This chapter explains how to incorporate your module into the ControlLogix system. Use RSLogix 5000 programming software to install and configure your HART module. This chapter describes how to configure your HART analog I/O modules, but is limited to a relatively brief explanation of how to use the software. For more information on the full capabilities of the software, see the softwares online help by clicking Help from dialogs.
Configuring Your I/O Module
You must configure your module upon installation. The module does not work until it has been configured. Use RSLogix 5000 software to write configuration for your ControlLogix analog I/O module. You have the option of accepting the default configuration for your module or writing point-level configuration specific to your application. When you use the RSLogix 5000 software to configure a ControlLogix analog I/O module, begin by creating a new module.
Create a New Module
After you have started RSLogix 5000 software and created a processor, you must create a new module. Use these steps to create a new module and configure it.
IMPORTANT
You cannot make changes to any field in these dialogs if you are in Hard Run mode. Hard Run mode means that the keyswitch is in the Run position.
69
70
1. From the I/O Configuration tree, click the 1756 backplane and New Module to see the Select Module dialog.
Click + next to Analog to see the list of analog modules.
2. From the Select Module dialog, click + next to Analog to see a list of analog modules.
Click Find to see the Find Text dialog.
3. From the Select Module dialog, if desired click Find and from the Find Text dialog, type in text you want to find, clicking and using Find Next, Close, and Help as needed, or proceed with the next step. 4. From the Select Module dialog, click the desired module, such as the 1756-IF8H or 1756-OF8H module, to see the General dialog that you use to configure the module.
71
Work with the General Dialog
Read this section for information about how to work with the General dialog. From the top of the New Module dialog, click General to display the General dialog.
Use these steps to work with the General dialog. 1. From the General dialog, complete these entries: Name - Type a name for the module, for example, N05_S01. Description - Type a description for the module (optional). Slot - Click the slot where the module resides, noting that the slot at the left end of the backplane is slot 0. 2. From the General dialog, click Change to see the Module Definition dialog.
72
3. From the Module Definition dialog, complete these entries: Series - Click the option that corresponds to your series. Revision - Click the number that matches the label on the side of your module, making sure the minor revision number also matches. Electronic Keying - Click an electronic keying method, refering to the Electronic Keying section of this manual. Note that electronic keying lets the ControlLogix system verify what modules belong in the various slots of a configured system. Exact Match Compatible Module Disable Keying See Chapter 3 for a detailed description. Connection Data Listen-only - has no configuration data, does not send output data (1756-OF8H module), referring if needed to the Listen-only Mode section of Chapter 2 Input Data - refer as needed to related information on Input Data in Chapter 7 in the HART Configuration Quick Start section: Analog only - for the following: - Analog signal values - Analog alarm status Analog and HART PV - for the following: - Alarm signal values and alarm status (same as Analog only) - HART secondary process variables - Device health Coordinated Time System (not changeable) Data Format (not changeable) See Chapter 7 for more details of HART configuration. 4. From the dialogs, click these as needed: OK - click to accept yo ur edits and close the dialog Cancel - click to close the dialog without accepting your edits
73
Work with the Connection Dialog
Read this for information about how to work with the Connection dialog. From the top of the New Module dialog, click Connection to display the Connection dialog.
Use these steps to work with the Connection dialog. 1. From the Connection dialog, complete the entry for Requested Packet Interval (RPI), noting 100.0 ms is the default, and 10.0750.0 ms is the range. 2. Click these, if desired: Inhibit Module - Prevents connection to the module. Use only if you do not want the module put in service. Major Fault on Controller If Connection Fails While in Run Mode - The Logix controller performs a major fault if communication to this I/O module fails. Use Scheduled Connection over ControlNet. 3. Click these as needed. OK - click to accept your edits and close the dialog Cancel - click to close the dialog without accepting your edits
74
Work with the Module Info Dialog
Read this for information about the Module Info dialog that displays module and status information about the module. It also lets you reset a module to its power-up state. The information on this dialog is not displayed if you are offline or currently creating a module. Use the dialog to determine the identity of the module. The data on this dialog comes directly from the module.
This dialog shows information about the installed I/O module. You can use it to confirm product and version information. The dialog contains values only if RSLogix 5000 software is online. Use these steps to work with the Module Info dialog. 1. From the Module Info dialog, see the entries for these items: Identification Vendor Product type Product code Revision Serial number Product name - the name displayed is read from the module. This name displays the series of the module. Status - displays the modules current operational state.
75
Major Fault - Displays None, Unrecoverable, or Recoverable. Minor Fault - Displays None, Unrecoverable, or Recoverable. Recoverable might mean you have a channel fault such as wire off. Configured - Displays a value that indicates whether the module was configured by an owner controller connected to it. Once a module is configured, it stays configured until the module is reset or power cycled, even if the owner drops connection to the module. This information applies to the I/O module only and does not apply to adapters, scanners, bridges, or other communication modules. Owned - Displays a value that indicates whether an owner controller is currently connected to the module. This information applies to the I/O module only and does not apply to adapters, scanners, bridges, or other communication modules. Module Identity - Displays Match or Mismatch as described in the table. This field does not take into account the Electronic Keying or Minor Revision selections for the module as specified on the General dialog.
Displays Match If the Physical Module Agrees with what is specified on the General dialog. For the Match condition to exist, all of the following must agree: Vendor Module type (the combination of product type and product code for a particular vendor) Major revision Mismatch Does not agree with what is specified on the General dialog.
Coordinated System Time (CST) Timer Hardware - Displays if timers hardware is OK or faulted. Timer Synced - Displays yes if the modules timer is coordinated with the master. Display no if it is not. This indicates if a CST master is providing a time reference to the module. Configure a controller to be the CST Time Master using the Controller Properties dialog. 2. From the Module Info dialog, click these as desired: Refresh - Rereads the information on the dialog from the I/O module.
76
Reset Module - Resets the module similar to a power cycle. Resetting a module causes all conections to or through the module to be closed. This can result in loss of control. Resetting the module breaks connections and restores output signals to default conditions.
WARNING
3.
Click one of these as needed. OK - Click to accept your edits and close the dialog. Cancel - Click to close the dialog without accepting your edits. Apply - Click to accept and apply your edits on any dialog and continue editing. Note that if the following conditions exist when you click Apply or OK, the information is automatically sent to the controller: you are online in Program, Remote Program, or Remote Run mode, and this controller is the owner controller, and you have changed the module's configuration in the software. The controller tries to send the information to the module (if the module's connection is not inhibited). If you don't click OK or Apply, your changes are not sent to the controller.
Work with HART Analog Input Dialogs
Read this for information about how to work with the Configuration and Alarm dialogs that are related to using the the 1756-IF8H analog input modules.
Configuration Dialog
Read this for information about how to work with the Configuration dialog that you use to configure the input channels on the module.
77
From the top of the New Module dialog, click Configuration to see the Configuration dialog.
Configurable For Each Channel
Apply to All Channels
From the Configuration dialog, follow these steps. 1. Complete these procedures to apply to the chosen channel. a. For Channel, click to select a channel to configure parameters for the specified channel 07. b. For Enable HART, check the check box to enable each channel individually, noting the following: The default is unchecked. Enable HART appears dimmed in Hard Run mode. Input range must be 420 mA. When a channel is not enabled: HART messages are not sent on this channel. HART Pass through messages are not sent. HART data for this channel is not updated in the Input Tag. If you selected the Analog with HART PV input tag on the General dialog, process data, such as PV, SV, TV, and FV, from the HART instrument is included in the input tag. If you selected Analog only, the process data is not included in the input tag. Regardless of the choice of input tag, HART communications can be enabled for each channel to provide Pass through HART message access. If Enable HART is not checked, this Pass through message access is not available.
78
We recommend you Enable HART for any channel that has a HART device connected so that information can be displayed on the HART Device Info dialog. One reason to disable HART communication is that each channel that is enabled requires time to scan, so enabling unnecessary channels reduces performance on the others. c. For Scaling, type values for High Signal, Low Signal, High Engineering, and Low Engineering, refer to the related Scaling to Engineering Units of this chapter on page 81. d. For Input Range, click one of these, noting that Input Range appears dimmed when in Hard Run mode: -1010V 05V 010V 020mA 420 mA (required for HART) e. For Sensor Offset, enter a value from -9,999,99999,999,999 (float) to set the value for the module, noting that the Sensor Offset is added to the data value to determine signal level. Sensor Offset is in engineering units. The default value is 0.00. The Sensor Offset appears dimmed in Hard Run mode. f. For Digital Filter, click a value of 020100, noting the default is 0. Select a filter time constant in milliseconds. This field is a first-order lag filter that smooths input transitions. We call it a digital filter because it is done in software by the module, not by a hardware filter. The Digital Field appears dimmed in Hard Run mode. 2. Complete these procedures to apply to all channels.
79
a. For Real Time Sample (RTS), click a value of 010,000 for the input module to determine the interval of time at which updated information is supplied to the processor. Note the default is 88 and the option appears dimmed when in Hard Run mode. In the example, the real time sample value is 100 ms and the requested packet interval is 25 ms. Only every fourth multicast from the module contains updated channel data.
Real Time Sample (RTS) 100 ms - Updated data
Requested Packet Interval 25 ms - Same input data as the previous RTS 25 50 75 100 125 150 175 200 225 250 275 300 325 350 375 400
Real Time Sample Values Module Filter, Hz 10 15 20 50 60 100 (default) 250 1000 Low Limit 488 328 248 88 88 56 28 18 High Limit 10000
b. For Module Filter (-3 dB), click a value per the the Module Filter Value table, choosing an input filter for each input channel, with the option appearing dimmed if in Hard Run mode.
80
Module Filter Value Module Filter, Hz 10 15 20 50 60 (default) 100 250 1000

(1)
C.ModuleFilter 0 7 6 1 2 3 4
(1)
Do not choose 1000 with HART enabled.
c. For Keep HART Replies for, click a value from 1255, with a default of 15.
IMPORTANT
We do not recommend less than 15.
HART Pass through message replies are kept for this time. HART replies that are received from the Field Device in response to Pass through messages you have sent are kept for this long. You must retrieve them within this time or the module discards them. Keep HART Replies for appears dimmed in Hard Run mode. d. For Pass through, click one of these values, to choose how often Pass through messages occur, noting that Once per two channels scanned is the default and Pass through appears dimmed in Hard Run mode: Once per two channels scanned - After 2 channels have PVs scanned to Input Tag, a Pass through message is sent (if one is pending). Once per module scan - Select this value if you want to minimize the impact Pass through message clients have on reading the PVs into the Input Tag. Once per channel scan - After each channel has its PVs scanned to Input Tag, a Pass through message is sent (if one is pending). Select this value if you want to give Pass through messages from clients, such as Factory Talk Asset Centre, higher priority than reading PV, SV, TV, FV and field device health into the Input Tag.
81
3.
Click these as needed. OK - Click to accept your edits and close the dialog. Cancel - Click to close the dialog without accepting your edits. Apply - Click to accept and apply your edits on any dialog and continue editing.
Scaling to Engineering Units

Channel data values in the output tag can be in engineering units such as Kg, m, or percentage. To configure the relationship between engineering units and the physical signal in volts or mA, set the Low and High Signal and the Low and High Engineering values.
For example, if you have a temperature transmitter on channel 3 which produces 4 mA current at -180 degrees C and 20 mA of current at 750 degrees C, and you want to use Degrees C in your control program, then configure the values as in the following table.
Signal High Low 20 4 Engineering
750 -180
If you are using HART field devices, we recommend setting Engineering High and Low to the field device's Upper Range Value and Lower Range Value so that the field device uses the same engineering units as the 1756-IF8H module. If online, these values are displayed on the HART Device Info dialog.
82
Scaling High Signal

Set the High Signal value for the module. The High Signal value must be greater than the Low Signal value. See the table for valid values.
Range -1010V 020 mA 420 mA 05V 010V Low Limit -10.00 0.00 4.00 0 1 High Limit 10.00 20.00 20.00 5 10
The default value is 20.00. Scaling High Signal appears dimmed in Hard Run mode.
Scaling Low Signal

Set the Low Signal value for the module. The Low Signal value must be less than the High Signal value. See the table for valid values.
Range -1010V 020 mA 420 mA 05V 010V Low Limit -10.00 0.00 4.00 0 0 High Limit 10.00 20.00 20.00 5 10
The default value is 4.00. Scaling Low Signal appears dimmed in Hard Run mode.
Scaling High Engineering

Set the High Engineering value for the module. The High Engineering value must not equal the Low Engineering value. This is the value in engineering units that corresponds with a signal value equal to the High signal. Valid values are in the range of -10,000,000100,000,000. The default value is 100.00. Scaling High Engineering appears dimmed in Hard Run mode.
83
Scaling Low Engineering

Set the Low Engineering value for the module. The Low Engineering value must not equal the High Engineering value. This is the value in engineering units that corresponds with a signal value equal to the Low signal. Valid values are in the range of -10,000,000100,000,000. The default value is 0.00. Scaling Low Engineering appears dimmed in Hard Run mode.
Alarm Dialog
Read this for information about how to work with the Alarm dialog. From the top of the New Module dialog, click Alarm to see the Alarm dialog.
For related information, see the About the Analog Input Modules chapter of this manual for a description of process alarms. Use this dialog to configure alarms on the 1756-IF8H module. You can perform the following: Select the channel you want to configure. Configure process alarms. Disable all alarms. Choose to latch alarms.
84
From the Alarm dialog, use these procedures to work with the dialog. 1. For Channel, click to select a channel to configure the parameters for the corresponding channel. 2. Check the checkbox for these entries, as desired: Disable All Alarms - Check to disable all alarms for a channel; appears dimmed in Hard Run mode. Latch Process Alarms - Check to maintain an alarm triggered condition for any of the process alarms, even after the condition ceases. The alarm unlatches only with an explicit message acknowledging the alarm. Latch Process Alarms appears dimmed in Hard Run mode. Latch Rate Alarm - When you enable this alarm, a Rate Alarm indication remains set, even when the alarm condition returns to normal. This latch lets you maintain the alarm even after the condition ceases. The alarm unlatches only with an explicit message acknowledging the alarm. Latch Rate Alarm appears dimmed in Hard Run mode. 3. For Deadband, type the value from 0.00 to 99,999,999, noting the default is 0.00. Deadband appears dimmed in Hard Run mode. Enter a value where an alarm, once set, will not disable as long as the input value remains within the deadband range of the alarm trigger point. (This value in combination with the process alarms creates the range.) This prevents the alarm from cycling on and off if the process value hovers near the alarm threshold. For related information, refer to the diagram in the Alarm Deadband section in Chapter 6. 4. For Rate Alarm, type the alarm limit value from 0.00 to 99,999,999, noting the following: The default is 0.00 Enter a Maximum Ramp Rate value to trigger a Rate Alarm when the Input Signal rate of change exceeds the set point. Set this alarm in engineering units/second. This is useful for detecting rapid process changes. Rate Alarms appears dimmed in Hard Run mode. 5. Click Unlatch All to unlatch all alarms, as needed, for the channel. Unlatch All appears dimmed when offline.
85
6. Click Unlatch to unlatch the adjacent alarm condition. Unlatch appears dimmed when offline. 7. For Process Alarms, type a value or use the slider to make entries for the following: High High - Set the level of input to a channel that causes the module to set the High High alarm. The alarm remains active until the input returns below this level by more than the deadband. If Latch Process Alarms is checked, the ChXHHAlarm indication remains set until explicitly cleared. High - Set the level of input to a channel that causes the module to set the High alarm. The alarm remains until the input returns below this level by more than the deadband. If Latch Process Alarms is checked, the ChXLAlarm indication remains set until explicitly cleared. Low - Set the level of input on a channel that causes the module to set the Low alarm. The alarm remains until the input returns above this level by more than the deadband. If Latch Process Alarms is checked, the ChXLAlarm indication remains set until explicitly cleared. Low Low - Set the level of input to a channel that causes the module to set a Low Low alarm. The alarm remains until the input returns above this level, more than the deadband. If Latch Process Alarms is checked, the ChXLLAlarm indication remains set until explicitly cleared. Alarm thresholds are in engineering units. Process alarms appear dimmed in Hard Run mode. To use the slider controls, see the Slider Controls table, noting the following: You use the slider bar to visualize where the process alarm trigger parts are set for your process; you can also drag the process alarm flags to adjust the trigger point. To change the trigger points by whole numbers only, hold down the shift key while dragging the flag on the slider bar. A deadband appears around each value.
86
Values for High Engineering and Low Engineering are the maximum and minimum slider control values and are set from the Configuration dialog.
Slider Controls Use this marker HH H L LL To update this value High High High Low Low Low
8. Click these as needed. OK - click to accept your edits and close the dialog. Cancel - click to close the dialog without accepting your edits. Apply - click to accept and apply your edits on any dialog and continue editing. If all of the following conditions exist when you click Apply or OK, the information is automatically sent to the controller: You are online in Program, Remote Program, or Remote Run mode. This controller is the owner controller. You changed the modules configuration in the software. The controller tries to send the information to the module (if the modules connection is not inhibited). If you do not click Apply, your changes are not sent to the controller.
Work with HART Analog Output Dialogs
Read this for information about how to work with the dialogs related to using the 1756-OF8H analog output modules to include: Configuration dialog. Output State dialog. Limits dialog.
87
Read this for information about how to work with the Configuration dialog. From the top of the New Module dialog, click Configuration to see the Configuration dialog.
From the Configuration dialog, follow these steps. 1. Complete these procedures to apply to channels chosen. a. Click a button 07 to configure the parameters for that channel. b. For Enable HART, check the check box to enable each channel individually, noting the following: The default is unchecked. Enable HART appears dimmed in Hard Run mode. Output range must be 420 mA. When a channel is not enabled: - HART messages are not sent on this channel. - HART Pass through messages are not sent. - HART data for this channel is not updated in the Input Tag. If you selected the Analog with HART PV input tag on the General dialog, process data, such as PV, SV, TV, and FV, from the HART instrument is included in the input tag. If you selected Analog only, the process data is not included in the input tag.
88
Regardless of the choice of input tag, HART communications can be enabled for each channel to provide Pass through HART message access. If Enable HART is not checked, this Pass through message access is not available. We recommend you Enable HART for any channel that has a HART device connected so that information can be displayed on the HART Device Info dialog. One reason to disable HART communication is that each channel that is enabled requires time to scan, so enabling unnecessary channels reduces performance on the others. c. For Scaling, type values for High Signal, Low Signal, High Engineering, and Low Engineering, referring to the related Scaling to Engineering Units section of this manual. d. For Output Range, click a value to set the operating range and signal type for the channel, with the default being 4...20 mA. -10...10V 0...20 mA 4...20 mA e. For Sensor Offset, enter a value from -9,999,99999,999,999 (float) to set the value for the module. The Sensor Offset is added to the data value to determine signal level. Sensor Offset is in engineering units. The default value is 0.00, with Sensor Offset appearing dimmed in Hard Run mode. f. For Hold for Initialization, check this box to cause the module to hold the output signal unchanged until the output value received from the controller in the ChxData field is within 0.1% of full scale of the value being held. The output holds when the following occurs: Power-up occurs (holds at zero) A new connection is established (brings it out of fault state and it holds at the fault value from the previous configuration). The controller returns to Run mode after Program mode (continues to hold at the configured value that was held in Program mode, see the Output State dialog). The output channel holding lets the controller synchronize with the output, enables smooth output transitions and avoids rapid transients when control resumes from an interruption.
89
The output can be ramping to the configured hold value when the transition occurs. In this case, it continues the ramp until it completes or until the output value from the controller is within the 0.1% of the output signal. When the Hold for Initialization box is not checked, the output switches as quickly as possible to the first value commanded by the controller. Hold for Initialization appears dimmed in Hard Run. 2. Complete these procedures, which apply to all channels. a. For Keep HART Replies for, click a value from 1255 s.
IMPORTANT
We do not recommend use of less than 15 s.
This is how long you want to keep HART replies. HART replies that are received from the Field Device in response to Pass Through messages you have sent are kept for this long. You must retrieve them within this time or the module discards them. Keep HART Replies for appears dimmed in Hard Run mode. b. For Pass Through, click one of these values to choose how often Pass through messages occur, noting that Once per two channels scanned is the default and Pass through appears dimmed in Hard Run mode: Once per two channels scanned - After 2 channels have PVs scanned to the Input Tag, a Pass Through message is sent (if one is pending). Once per module scan - Select this value if you want to minimize the impact Pass through message clients have on reading the PVs into the Input Tag. Once per channel scan - After each channel has its PVs scanned to Input Tag, a Pass through message is sent (if one is pending). Select this value if you want to give Pass through message clients, such as Factory Talk Asset Centre, higher priority than reading PV, SV, TV, FV and field device health into the Input Tag. 3. Click these as needed: OK - Click to accept your edits and close the dialog. Cancel - Click to close the dialog without accepting your edits. Apply - Click to accept and apply your edits on any dialog and continue editing.
90
Output State Dialog

Read this for information about how to work with the Output State dialog. Use this dialog to configure output behavior when the controller is in Fault or Program mode. From this dialog you can select the: channel you want to configure. output behavior in Program mode. output behavior in Controller Fault mode. output behavior if communication fails.
From the top of the New Module dialog, click Output State to see the dialog.
From the Output State dialog, use these steps to complete entries. 1. Click a channel 07 to configure the parameters for the corresponding channel. 2. Note that Ramp Rate displays the ramping rate, where output ramping limits the speed at which an analog output signal can change. This prevents fast transitions in output from damaging equipment that the output controls. You can set Ramp Rate on the output Limits dialog.
91
3. From the Output State in Program Mode section, click one of these, noting that Output State in Program Mode appears dimmed in Hard Run mode and referring to the table: Hold Last State User Defined Value - type a value at -9,999,99999,999,999 with a default of 0 Ramp to User Defined Value
Output State in Program Mode Selecting Configures the Output Channel for the Following When the Controller Transitions from Run to Program Mode Leave the current output at its last value. Go to the specific value when the owner controller is switched into Program mode. If you select this, enter a value. If Hold Last State - this field is disabled. User Defined Value - check if you want the output to ramp to the user-defined value at the specified ramp rate. The ramp rate is selected from the output Limits dialog. If unchecked, output signal steps to the User Defined Value immediately on entering Program mode.
Hold Last State User Defined Value
Ramp to User Defined Value
4. From the Output State in Fault Mode section, click one of these, noting that Output State in Fault Mode appears dimmed in Hard Run mode and referring to the table: Hold Last State User Defined Value - type a value at -9,999,99999,999,999 with a default of 0 Ramp to User Defined Value Note the module enters Program mode state if the Connection from Logix is inhibited. If communication subsequently fail, all channels of the module remain in Program mode.
Output State in Fault Mode Select Hold Last State User Defined Value Ramp to User Defined Value To configure the output module to one of these Leave the output signal at its last value Go to a specific value if a fault occurs. If you select this button, enter a value. Hold Last State - This field is disabled. User Defined Value - You can check this if you want the output to ramp to the user-defined value at the specified ramp rate. The ramp rate is selected on the output Limits dialog. If unchecked, the output signal steps to the user-defined value immediately on entering Fault mode.
92
Note that the output signal goes to Fault mode when the controller faults or when communication between an output module and its controller is lost. Output State in Fault Mode appears dimmed in Hard Run mode. 5. From the Communications Failure section, click one of these noting that if communication fails while in Run mode, the output signal goes to its Fault Mode state: Leave outputs in Program Mode state Change outputs to Fault Mode state If communication fails while in Program mode, refer to the table.
Select Leave outputs in Program mode state Change output to Fault mode state To Leave output signal at the configured Program mode value Change output signal at configured Fault mode value if a communication fails (connection from controller breaks)
6.
Click one of these as needed: OK - click to accept your edits and close the dialog. Cancel - click to close the dialog without accepting your edits. Apply - click to apply your edits on any dialog and continue editing. Note that if all of the following conditions exist when you click Apply or OK, the information is automatically sent to the controller and the controller tries to send the information to the module (if the modules connection is not inhibited):
you are online in Program, Remote Program, or Remote Run mode this controller is the owner controller you changed the modules configuration in the software.
Limits Dialog
Read this for information about how to work with the Limits dialog. From the top of the New Module dialog, click Limits to see the dialog. Use the dialog to configure output limits on the 1756-OF8H module, performing the following: Select the channel you want to configure.
93
Enter clamp limits. Configure output ramping. Configure and disable all alarms. Use these steps to complete the entries on the dialog.
1. From the top of the dialog, click a channel 07 to configure the parameters for that channel. 2. Check the check box for these: Disable All Alarms - check to disable alarm for the current channel. If checked, all alarm entries beneath this checkbox are disabled. Disable All Alarms appeared dimmed in Hard Run mode. Latch Limit Alarms - Check to remember the high and low limit alarms even after the condition ceases. The high and low limit alarm is set if the requested output is beyond the clamp limit (>High or <Low). This is useful if you want to detect a transient alarm condition and preserve its indication until the alarm is explicitly unlatched. Alarms can be unlatched using the Unlatch button on this dialog of the configuration profile, or by sending a CIP message using the MSG instruction. Latch Limit Alarms appears dimmed in Hard Run mode.
94
Latch Rate Alarm - Check to maintain the rate alarm even after the condition ceases. The ramp rate alarm is set if there is a minimum change of input between samples of a channel. Note that the Max Ramp Rate should be greater than zero when this box is checked. This is useful useful if you want to detect a transient alarm condition and preserve its indication until the alarm is explicitly unlatched. Alarms can be unlatched using the Unlatch button on this dialog of the configuration profile, or by sending a CIP message using the MSG instruction. Latch Rate Alarm appears dimmed in Hard Run. 3. For Limits, type a value for the following, noting that Limits appears dimmed in Hard Run mode and clamp limits are in engineering units. For example, if your output controls a valve positioner that is configured to use Percent of Stroke for engineering units, and you don't want the valve to be over 62% open at any time for any reason, then you can enter 0 as the Low Clamp and 62 for High Clamp. Even if a PIDE instruction calculates the valve should be open more to achieve process Setpoint, the output module clamps it to 62% open. High Clamp at -9,999,99999,999,999, with default of 100.00, entering the highest value an output channel can reach in the control process Low Clamp at -9,999,99999,999,999, with default of 0, entering the lowest value an output channel can reach in the control process 4. For Limits, click these as desired: Unlatch - click to unlatch the adjacent alarm condition. Unlatch appears dimmed when offline or if alarms are disabled. Unlach All - click to unlatch all alarms for the channel. Unlatch All appears dimmed when offline or if Latch Limit or Latch Rate alarms are disabled. 5. For Limits, type a value or use the slider to make entries for the following: High Clamp default of 100.00 Low Clamp default of 0.0 To use the slider controls, see the Slider Controls table, noting that values for High Engineering and Low Engineering are the maximum and minimum slider control values and are set from the Configuration dialog. Hold the shift key while dragging the marker on the slider bar to constrain to whole numbers. Use the
95
bar to visualize where the process limit trigger values are set for your process. You can also drag the process alarm markers to adjust the clamp limit points. The slider bar appears dimmed in Hard Run mode.
Slider Controls Use this marker HI LO To update this value High clamp Low clamp
6. For Ramp in Run Mode, check the check box to enable ramping during Run mode. Ramping occurs between the current output level and any new output value received. If ramping is enabled, the output only can change at the configured ramp rate limit. Ramp in Run Mode appears dimmed in Hard Run mode. 7. For Ramp Rate, type a value, if you checked the box for Ramp in Run Mode, at -9,999,9999999,999,999, with default of 0, noting the following: Enter the maximum rate of change an output can make in engineering units/second. This also serves as a trigger point for a Ramp Rate Limit alarm when the Ramp in Run mode is selected. You can also use the Ramp Rate Limit for ramping to a user-defined value in Program or Fault mode. A non-editable copy of Ramp Rate is shown on the Output State dialog. Ramp Rate appears dimmed in Hard Run mode. 8. From the bottom of the dialog, click Apply to apply your edits and continue editing, noting that if all of these conditions exist when you click Apply or OK, the information is automatically sent to the controller: you are online in Program, Remote Program, or Remote Run mode this controller is the owner controller you changed the modules configuration in the software The controller tries to send the information to the module (if the modules connection is not inhibited). If you do not click Ok or Apply, your changes are not sent to the controller.
96
HART Device Info Dialog
For information about the HART Device Info dialog, see Chapter 7, Configuring and Using HART, in the HART Data in the Module Properties on the HART Device Info Dialog section.
Chapter
Configuring and Using HART
In this chapter, we show how to configure the 1756-IF8H and 1756-OF8H HART modules to collect data from the HART field device and place it in the module's Input Tag. The fields of the Input Tag are described and an overview of the HART data collection process is presented. Access HART field device data by using the 1756-OF8H or 1756-IF8H modules in two ways. Automatic collection of the HART Field Device Process Variables and Health information in the module's Input Tag Pass through messages, providing the data to an Asset Management system, as described in Chapter 9, such as FactoryTalk AssetCentre or to a Logix controller via explicit MSG instructions, as described in Chapter 8. This chapter shows you how to configure the module to automatically collect the data and put it in the Input Tag. Note that the update rate for the HART part of the Input Tag is slower than for the analog part. The actual rate varies, depending on HART network traffic, but if all 8 channels have HART enabled, update rates are in the range of 10 seconds. Be sure to consider this slow response time in your control strategy and also check the data quality indications provided with the HART data to ensure a robust control system. See the table that shows which configuration options provide HART data in the Input tag and which provide Pass through message access.
HART Data Configuration Options Input Data Format from the General Dialog Analog only Analog and HART PV Enable HART Checkbox on Configuration Dialog No check Checked No check Checked Fields present in tag, but data for this channel not valid Yes HART Data Input Tag of Logix Controller No Pass Through Message Access for MSG or Asset Management No Yes No Yes
97
98
HART Configuration Quick Start
Read this for quick start information.
Pick HART Input Data Format

To set the module to collect data from your HART instrument and place it in the Input Tag, choose the Input Data format: Analog and HART PV. If you choose Analog Only, you can access HART data via Pass through messages, but it is not included in the module's Input Tag data.
For Input Data, click Analog and HART PV.
Even if you aren't using HART on all 8 channels, the Analog and HART PV input tag includes space for the data, but it will be marked with a HARTFault to indicate it isn't valid. This lets HART instruments be added later without disturbing the tag layout.
99
Enable HART
From the Module Properties Configuration dialog, use these procedures.
Check the Enable HART checkbox.
1. Check the Enable HART checkbox. 2. Note that you can check Enable HART on some channels and not on others if only some channels have HART field devices attached. Since the HART modem is shared by all the channels, HART response time is better if you enable only the needed HART channels. 3. Complete these entries. Input Range as 420 mA - HART devices use only 420 mA analog signaling range. Module Filter - Since the digital HART communication signals are in the 12002400 Hz range, the module filter can not be set to 1000 Hz if HART is enabled.
100
Keep HART Replies for: xx s - Pass through message timeout. This sets a timeout the module uses for HART Pass through messaging. It isn't important for setting up the Input Tag, but 15 s is usually a good number to use. See the sections on HART Pass through in Chapter 8, Getting HART Data Over CIP MSG, for more information. Pass through - The relative priority of collecting Process Variables and Health for the Input Tag versus sending HART Pass through messages for an Asset Management application can be set to one of three policies. For more information, see the chapter on HART Pass through messages and the table that shows Pass through setting, ratio, and priority.
Pass Through Setting, Ratio, and Priority Setting Once per channel scan Once per two channels scanned Once per module scan Scan:Pass through ratio 1:1 1:2 1:8 Gives priority to Asset management Default setting Input Tag scan
HART Data in the Module Properties on the HART Device Info Dialog
The dialog you see when you click HART Device Info Tab displays configuration information about the attached HART field device.
101
From this dialog, you can perform the following: View manufacturer and revision information View tag, message, and description entered into the HART Field device Check ranges and Primary Variable configuration Refresh the device information Note that the data on this dialog are collected by the HART module from the HART field device. If you selected a Listen-Only communication format when you created the module, this dialog is not available. If HART is not enabled for this channel, a message is displayed like that shown in the dialog.
If HART is not enabled for this channel, a message displays.
102
If HART is enabled, but the HART Field Device is not responding, you see an error display like that in the dialog.
If HART device is not responding, you see this.
These describe the information available on this dialog: Channel - Click a channel to display the parameters for the corresponding channel. Refresh - Click to update all attributes displayed on this dialog for the corresponding channel. Tag - Displays the tag name of the HART Field Device. The tag name is entered into the Field Device to indicate its location and purpose in the plant. Message - Displays the text that was entered in the Message parameter of the HART Field Device. The use of this parameter can vary. One possible use is to store information such as who last calibrated the device, or reference to documentation. Descriptor - Displays the Descriptor field from the HART Field Device. The Descriptor is a text message that can be stored in the device to help identify the device or it can be used for other plant specific purposes.
103
Date - Displays the date entered in the device. This date is often used to record the last calibration date, but it is up to the end user to maintain it. It is displayed in the format selected for your computer using the Regional and Language settings on the Control Panel. Write Protect - Displays a Yes or No indicating if the HART Field Device is write protected. If a device is write protected, some parameters cannot be changed via HART communication. Note that sometimes devices do not indicate that the configuration changed when their write-protect setting changes. This causes the previous value to remain displayed here. You can inhibit/uninhibit the HART module to refresh this. Manufacturer ID - Displays the manufacturer name (for example, Allen-Bradley or Endress + Hauser) or the numeric value for the manufacturer. Use the Company Identification Code table as a guide, as shown in Appendix E. Device Type - Displays the device type for Endress + Hauser devices or a numeric value for all other manufacturer devices. Device type indicates the manufacturer's type of the device, or product name. For example, Cerabar S pressure transmitters from Endress + Hauser have Device Type 7. Device ID - Displays a number that represents the device ID. Device ID is a serial number assigned by the manufacturer that is unique among all devices produced by that manufacturer. Final Assembly Number - Displays a number that represents the final assembly number. The Final Assembly Number is used for identifying the materials and electronics that comprise the field device. It is normally changed when electronics or other components are upgraded in the field. In some instances, this number references a drawing number. PV - In HART, the Primary Variable (PV) is signaled on the 4 to 20 mA analog channel. It can also be read back using HART messages. In many HART devices, the relationship between the PV and the analog signal can be adjusted. This section displays the following Process Variable attributes: Upper Range Value - to use the same engineering units in your Logix controller as in the Field Device, enter this value in High Engineering on the Configuration dialog. Lower Range Value - to use the same engineering units in your Logix controller as in the Field Device, enter this value in Low Engineering on the Configuration dialog. Damping Transfer Function - describes how the HART field device transforms the signal on its transducer to the PV. Usually Linear, but sometimes Square Root (for example, for flow), or other relationships.
104
Revision - Displays the following revision attributes. Universal - this denotes the version of the HART specification to which the device conforms. Device Software Hardware OK - Click to close the dialog. Cancel - Click to close the dialog. Help - Click for help on this dialog.
Data in the Input Tags

When HART data is included in the Input Tag and a channel has HART enabled, the 1756-IF8H or 1756-OF8H module automatically collects HART data and places the most common Dynamic Process Data and Device Health information directly in the Input Tag. See the Appendix for a complete listing of the fields in the Input, Output, and Configuration Tags. An overview of the HART data includes the following: HART Faults - At the beginning of the Input Tag included even if you click Analog Only Input data tag format. These faults indicate that HART communication is not successful. For example, Ch0HARTFault is set if Ch0Config.HARTEn is 0 or if no HART Field Device is attached. HART Device Status - A collection of status indicators that reflect the HART communication details and overall device health. Init - Module is searching for a HART device. Fault - HART communication is not successful. If this is 1 and Initializing is 0, probable cause is HART not enabled on this channel. Message Ready - A HART Pass through message reply is ready to be collected using the Pass through Query CIP message. See the chapter on using CIP MSGs to access HART for more information. Current Fault - The analog current doesn't match the readback of the current received over the HART communication. This might be caused by an inaccurate field device, faulty wiring, or water in the conduit. Sometimes a rapid change in the signal results in a transient current fault as the analog and digital representations are sampled at slightly different times and at different places in the signal path.
105
Configuration Changed - The Field Device configuration has changed and new Field Device configuration information can be obtained from the 1756-IF8H module via CIP MSG GetDeviceInfo, which will clear this bit. ResponseCode - HART Communication Status or Response Code. 0 means success. See the table in the Tag appendix for details. FieldDeviceStatus - HART device health, such as PV out of range or device malfunction. See the table in the Tag appendix for details.
HART Dynamic Variables

Most HART Devices are capable of measuring several different process characteristics or of deriving other measurements from directly sensed measurements. For example, many differential pressure transmitters can also sense the process temperature and can calculate the flow, or they might calculate the volume in a tank based on a measurement of its head pressure and knowledge of tank geometry and product density. The most important of these direct or derived measurements is assigned to the PV (Primary Variable) and the analog signal will represent its value. Additionally, the measurements can be read from the HART field device over the HART communication protocol. HART provides a standard message for reading four of the dynamic variables, called PV, SV, TV, and FV (sometimes called QV). These four dynamic variables are the four measurements of interest to a controller. These four dynamic variables - PV, SV, TV, and FV - are automatically collected from the HART field device and placed in the 1756-IF8H or 1756-OF8H Input Tag in HART.ChxPV (if Analog and HART PV data type is selected). In some HART devices, the choice of which of the available measurements to assign to PV, SV, TV, and FV can be changed via configuration. In other more simple devices, the assignment is done at the factory and cannot be changed. An example for a Flow Meter might be: PV - Primary Variable. Flow Rate in Liters per Minute. SV - Secondary Variable. Process Temperature in Degrees C. TV - Third or Tertiary Variable. Product Density in Grams per Cubic Centimeter. FV - Fourth or Quaternary Variable
106
An example for a Valve Positioner might be: PV - Primary Variable. Commanded position in %. SV - Secondary Variable. Actual position in %. TV - Third or Tertiary Variable. Air Pressure in PSI. FV - Fourth or Quaternary Variable. Loop current in mA.
In addition to the measurement value, HART devices can provide status information that indicates the quality of the measurement.
Device Family Specific Status Process Data Status 11 Good 01 Poor Accuracy 10 Manual/Fixed 00 Bad Limit Status 11 Constant 01 Low Limited 10 High Limited 00 Not Limited More Device Variable Status Available
For example, if a valve positioner cannot open any further, it should set its HART.ChxSVStatus to 2#11100000 to indicate that the actual position value in the SV is Good (accurately measured) but is the subject of a High Limit. This status information can be used for windup control in PID loops and for other diagnostic purposes. Note that Device Variable Status (PVStatus, SVStatus, TVStatus, FVStatus) is a relatively new feature in HART and many devices do not support it. In that case, the 1756-IF8H or 1756-OF8H module synthesizes a status value based on the communication status with the HART Field Device. If the Dynamic Variables are being collected without communication error, the Status value is 16#C0 (2#11000000) which means good. Otherwise, it is 0, meaning bad. Note that some devices don't have four dynamic variables. In this case, they can report a NaN value to indicate they have no valid value for that parameter. The Dynamic Variables do not update as fast as the Analog Signal. The actual rate depends on the number of channels configured for HART, the number of Pass through message commands, the presence of handheld communicators or other secondary masters, and the response speed of the field device.
107
With eight channels are in use, the HART update rate is in the 10 s range.
IMPORTANT
Verify that the actual HART update rate is appropriate for your application. Remember that Pass through message traffic, Additional Status Information, secondary masters, and communication errors can delay the update rate. Note that since the HART modem is shared by all channels, increased delay on one channel affects other channels also.
IMPORTANT
Verify that HART data is valid by checking ChxFault, HARTFault, and values such as PVStatus and SVStatus.
How the Module Automatically Collects Data

The 1756-IF8H or 1756-OF8H module automatically sends HART messages to characterize the HART field device and collect the dynamic variables. It also collects additional status information when the device indicates it is available. When the device indicates its configuration has changed, HART messages are sent to reread the configuration information so that a current copy is cached in the 1756-IF8H or 1756-OF8H module. The diagram shows the general flow of the startup characterization, response to a new configuration, and cyclic scanning of Dynamic Variables. Not shown are periodic checks of the current and reading the additional status information. In addition to the HART activities outlined in the diagram, if there are HART Pass through messages to send, they are interleaved in the auto scanning. Logix controllers can send Pass through messages using CIP MSG instructions, and Asset Management systems can send them. See the chapter on using HART with CIP MSG or Asset Management for more information. Note that HART messages are only sent on one channel at a time. Note that if the HART Field Device configuration is changed - from a handheld, asset management or device faceplate - cyclic reading of the Dynamic Variables pauses briefly while the configuration changes are assimilated. The HART.ChxDeviceStatus.ConfigurationChanged status is set when the updated configuration is retrieved from the HART Field Device and stored in the 1756-IF8H or 1756-OF8H to indicate that new data is available for GetDeviceInfo CIP MSG. See the chapter on using HART with CIP MSG for more details.
108
Device in Scan List?
No
Send Command 0 Read Unique Identifier Yes Reply? Send Command 3 or 9 to Read Dynamic Process Yes
Read Configuration Information, Such as Tag, Units, Range Signal Configuration Changed in Input Tag Put Device in Scan
No
Reply? Yes
No
Update Input
Remove Device from Scan List
New Configuration Indicated?

No
Yes
Read Configuration Information, Such As Tag, Units, Range Signal Configuration Changed in Input
Process 1 Pass through Message
Next Channel
Last Channel?
Yes
No
Go To First Channel
Chapter
Getting HART Data Using CIP MSG
This chapter shows you how to use HART data in your Logix controller via MSG instructions. You might do this because you need: only occasional access to the data, and don't want to use the extra network capacity and memory for the larger Analog with HART PV Input Tag. additional information, such as device tag, ranges, or manufacturer-specific information. to send a manufacturer-specific command to the HART device. Usually, everything you need to use your HART instrument is automatically collected and placed in your Input Tag, and these CIP MSG instructions are not needed. The 1756-IF8H and 1756-OF8H modules support these broad categories of MSG based HART access: CIP formatted messages to retrieve common HART data cached in the module. CIP messages containing HART formatted commands that are passed directly to the HART Field Device for processing. These are called Pass through messages. Using these mechanisms your Logix controller has easy access to some commonly used data and with some extra effort, access to any HART feature. The features described in this chapter use MSG instructions. For more information and examples about MSG instructions, refer to Chapter 10, which explains how to use MSG instructions to unlatch alarms or reconfigure modules.
Using MSG Instructions to Access the HART Object
Both categories of MSG are handled by the HART Object contained in the 1756-IF8H or 1756-OF8H module. Conceptually, there are eight instances of the HART Object, one for each channel. Some CIP messages can be sent to the Class Instance or Instance 0 of the HART object. Most MSGs are sent to a specific instance of the HART object associated with a particular channel.
109
110
See the table that shows channel and instance correspondence.

Channel and Instance Channel 0 1 2 3 4 5 6 7 Instance 1 2 3 4 5 6 7 8
See the tables that show service codes for CIP services.
Service Codes for CIP Services Cached on the Module by the HART Object Class 16#35D Service Code 16#4B 16#4C 16#4D Function Read Dynamic Variables Read Additional Status Get HART Device Information
Service Codes for CIP Services for Pass Through Messages to HART Field Devices Class 16#35D Service Code 16#4E 16#4F 16#50 Pass Through Messages Init Query Flush Queue
CIP Services to Access Common HART Data
You can get the following kinds of HART data easily from the HART object: HART Field Device Information. Similar to that displayed on RSLogix 5000 Module Properties HART Device Info dialog. Additional Status. HART devices that support extended diagnostics can indicate in their Field Device Status that some additional diagnostic information is available. Dynamic Variables. The same PV, SV, TV, FV that are in the Input Tag. Also gives the Device Variable Code they are mapped to and the engineering units.
111
The data in these commands is returned in the format used by Logix controllers, so it is very easy to use in your control program. HART data is natively in a different format, called big-endian, but the 1756-IF8H or 1756-OF8H module converts the values in these messages for you. See the tables that list the data in the CIP messages and the example of getting the Device Info. In the following sections the definition CMD#0 byte 3, for example, means HART command 0, byte 3. If your field device user manual includes information about HART command responses, this information will be helpful to you. Consult the HART protocol specification for further information on HART commands. See Appendix D - Additional HART Protocol Information for related information.
Read Dynamic Variables (Service Code = 16#4B)

See the related tables.
HART Read Dynamic Variables - MSG Source-element Structure Offset Field Data Type Definition No requested data Request size = 0 bytes
The 1756-IF8H or 1756-OF8H module responds with the reply message in this table if there is a failure.
HART Read Dynamic Variables - MSG Destination Structure Offset 0 1 Field Status Pad Data Type USINT Definition Command status Pad byte
Reply size = 2 bytes Request Failed
The 1756-IF8H or 1756-OF8H module responds with the reply message in this table if the Dynamic Variable request succeeds. See Appendix F for the table of unit codes.
112
HART Read Dynamic Variables - MSG Destination Structure Offset 0 1 2 3 47 811 1215 1619 20 21 22 23 24 25 26 27 28 Field Status HARTCommandStatus HARTFieldDeviceStatus HARTExtDevice Status PV SV TV FV PV Units SV Units TV Units FV Units PV Assignment Code SV Assignment Code TV Assignment Code FV Assignment Code PV Status USINT REAL Data Type USINT Definition Command status HART Device reply Status Byte # 1 (response code) HART Device reply Status Byte # 2 Status Byte returned from Cmd 9 or 0 for 5.x rev HART devices HART Primary variable HART Secondary variable HART Third variable HART Fourth variable Primary variable unit code Secondary variable unit code Third variable unit code Fourth variable unit code Primary variable assignment code Secondary variable assignment code Third variable assignment code Fourth variable assignment code 1 byte status from Cmd 9(Rev 6.x) or if Rev 5.x device: 0xC0 = Connected 0x00 = Not Connected 1 byte status from Cmd 9 or if Rev 5.x device: 0xC0 = Connected and Device provides this value in CMD 3 (that is, does not truncate) 0x00 = Not Connected 1 byte status from Cmd 9 or if Rev 5.x device: 0xC0 = Connected and Device provides this value in CMD 3 (that is, does not truncate) 0x00 = Not Connected 1 byte status from Cmd 9 or if Rev 5.x device: 0xC0 = Connected and Device provides this value in CMD 3 (that is, does not truncate) 0x00 = Not Connected REAL Device reported digital loop current value. (Value from Cmd 3 for Rev 5.x devices or Cmd 2 if Rev 6.x device)
29
SV Status
30
TV Status
31
FV Status
3235
Loop Current
Reply Size = 36 bytes
113
Read Additional Status (Service Code = 16#4C)

See the tables that show read additional status.
HART Read Additional Status - MSG Source Element Structure Offset Field Data Type Definition No requested data Request size = 0 bytes
The 1756-IF8H or 1756-OF8H module responds with the reply in this table if there is an error.
HART Read Additional Status - MSG Destination Structure Offset 0 1 Field Status Pad Data Type USINT Definition Command status Pad byte
Reply size = 2 bytes Request Failed
The 1756-IF8H or 1756-OF8H module respond with the message in the table.
HART Read Additional Status - MSG Destination Structure Offset 0 1 226 Offset Status Count Ext Status Bytes Data Type USINT Definition Command status Number of Ext Status bytes available Extended Status bytes returned by CMD48
Reply Size = 228 bytes (pad byte may be attached to end since data is 16 bit aligned)
Get Device Information (Service Code = 16#4D)

See the tables for Get Device Information details.
HART Get Device Information - MSG Source Element Structure - Get Currently Cached Device Information For Given Channel) Offset Field Data Type Definition No requested data Request size = 0 bytes
114
The 1756-IF8H or 1756-OF8H module responds with the reply in this table if there is an error.
HART Get Device Information - MSG Destination Structure Offset 0 1 Field Status Pad Data Type USINT Definition Command status Pad byte
Reply size = 2 bytes
The 1756-IF8H or 1756-OF8H modules respond as shown in the table if successful.

HART Get Device Information - MSG Destination Structure Offset 0 1 2 3 4 5 6 7 8 9 10 11 1214 15 1627 2847 48 49 5051 5255 5691 Field Status Manufacturer Device Type Preamble Universal Command Code Transducer Spec Code Software Revision Hardware Revision Flags Pad_1 for 32 bit alignment Pad_2 for 32 bit alignment Pad_3 for 32 bit alignment HARTDeviceIDNumber Pad_4 for 32 bit alignment Tag Descriptor DateDay DateMonth DateYear FinalAssemblyNumber Message INT DINT HARTMsg HARTTag HARTDescriptor SINT CMD#13, Bytes 05 CMD#13, Bytes 617 CMD#13, Byte 18 CMD#13, Byte 19 CMD#13, Byte 20 (+ 1900) CMD#16, Bytes 02 CMD#12, Bytes 023 DINT CMD#0, Bytes 911 Data Type SINT Definition(1) Command status CMD#0, Byte 1 CMD#0, Byte 2 CMD#0, Byte 3 CMD#0, Byte 4 CMD#0, Byte 5 CMD#0, Byte 6 CMD#0, Byte 7 CMD#0, Byte 8
115
HART Get Device Information - MSG Destination Structure Offset 92 93 94 95 96 97 98 99 100 101 102 103 104107 108111 112115 116 117 118 119 Field PVCode SVCode TVCode FVCode PVUnits SVUnits TVUnits FVUnits TransferFunction RangeUnits Pad_6 for 32 bit alignment Pad_7 for 32 bit alignment PVLowerRange PVUpperRange DampingValue WriteProtectCode Pad_8 for 32 bit alignment Pad_9 for 32 bit alignment Pad_10 for 32 bit alignment SINT REAL CMD#15, Bytes 36 CMD#15, Bytes 710 CMD#15, Bytes 1114 CMD#15, Byte 15 Data Type SINT Definition(1) CMD#50, Bytes 0, 16#ff if not supported CMD#50, Bytes 1, 16#ff if not supported CMD#50, Bytes 2, 16#ff if not supported CMD#50, Bytes 3, 16#ff if not supported CMD#3, Byte 4 CMD#3, Byte 9, 0 if not present CMD#3, Byte 14, 0 if not present CMD#3, Byte 19, 0 if not present CMD#15, Byte 1 CMD#15, Byte 2

(1)
See Appendix D for related information.
Getting HART Device Information Using CIP Generic MSG: An Example
This rung of ladder logic retrieves fresh HART device information whenever the 1756-IF8H or 1756-OF8H module indicates new configuration is available.
Note that if the Device Information is critical to your application, be sure to check for .ER errors and implement a recovery strategy.
116
See the MSG configuration dialog.
Get Device Info Service Code HART Instance 8 for Channel 7
HART Object Class
This reads the device information for the HART Device on channel 7 and puts the information in DevInfoAnswer.
117
The Destination tag is as shown in the Controller Tags dialog.
118
See the figure that shows string types for HARTTag, HARTDescriptor, and HARTMsg.
HARTTag
HARTDescriptor
HARTMsg
119
CIP Services to Pass Through a HART Message to the HART Field Device
The HART object supports these CIP messages for HART Pass through messaging: Pass through Init, Pass through Query, Flush Queue (rarely needed). With these three CIP messages, your Logix controller can format the individual bytes of a HART command, send it to a HART Field Device, and retrieve the response in HART format. Note that native HART data is in a different format than used by Logix controllers. HART uses the Big Endian format and Logix uses Little Endian format. This means the order of the bytes in a number are in the opposite order so they must be reversed before use. Logix Little Endian means that the least significant byte of a number is stored at the lowest address (array index). Logix also aligns data on boundaries that permit fast access and HART packs them into the smallest space. HART encodes text strings using 6 bits per letter into a format called Packed ASCII. When using Pass through messaging, your Logix program must be aware of these data layout issues. The Pass through message CIP services supported by the HART object are somewhat simplified. The module provides the 5-byte address usually required by HART messages and the Checksum is calculated automatically for you. Follow these steps to send a HART Pass through message. 1. Send a CIP message to tell the 1756-IF8H or 1756-OF8H module to send a message to a HART field device (Init). 2. Send a CIP message to retrieve the HART Reply from the 1756-IF8H or 1756-OF8H module (Query).
Pass Through Init Pass Through Query Source HART Command Bytes Destination Handle Source Handle Destination HART Reply Bytes
MSG Service 16#4E
MSG Service 16#4F
44405
120
If your Input Tag includes the HART PV data, a status indicator HART.ChxDeviceStatus.MsgReady tells your program a HART reply is ready to retrieve with the Pass through Query command. The CIP reply from the Init service includes a number called the handle. This handle identifies the HART message that was placed in a queue for transmission to the field device. When the reply is received and MsgReady is set to 1, your Logix controller should send a Query containing that same handle to retrieve the HART reply. The reason these steps are necessary is that it can take a long time for the HART command to be transmitted and a reply received. If all 8 channels are in use, the time for a reply would be about 10 seconds if there was no other Pass through traffic.
Understanding the HART Module Scanning Diagram with Pass Through Messages
When HART Pass through messages are being sent, the normal data acquisition sequence is modified as shown in the diagram. In this case, the Pass through is configured to send one Pass through message for each channel scanned.
121
It can be configured for lower priority on the Configuration dialog of module properties.
Device in Scan List?
No
Send Command 0 Read Unique Identifier Yes Reply? Send Command 3 or 9 to Read Dynamic Process Yes
Read Configuration Information, Such as Tag, Units, Range Signal Configuration Changed in Input Tag Put Device in Scan
No
Reply? Update Input Yes

No
Remove Device from Scan List
New Configuration Indicated?

No
Yes
Read Configuration Information, Such As Tag, Units, Range Signal Configuration Changed in Input
Process 1 Pass through Message
Next Channel
Last Channel?
Yes
No
Go To First Channel
122
HART Pass Through CIP Message Layout Details
See the related tables.
Pass Through Init (Service Code= 16#4E)

See the related table.
HART Pass Through Init - MSG Source Element Structure Offset 0 1 2256 Field HART Command HART Data Size HART Data bytes Data Type 0255 (1 byte) 0255 (1 byte) As many bytes as in HART Data Size Definition HART Command Number(1) Number of Data Bytes for Selected HART Command(1) HART Command Data(1)
Request Size = 2257 bytes

(1)
See Appendix D - Additional HART Protocol Information for related documentation.
The 1756-IF8H or 1756-OF8H module responds as shown in the table.

HART Pass Through Init - MSG Destination Structure Offset 0 Field Status 32 = Busy (Queues full) 33 = Initiate (Pass through success) 35 = Dead 1 2 3 HART Command Handle Queue Space Remaining 0255 (1 byte) 1255 (1 byte) (1 byte) Data Type Definition Command Status Busy - try again later Initiate - command started - send query to get the reply Dead - Device not online Echo of HART Command Handle Used in Query Operation Number of Queues Still Available for This Channel
Pass Through Query (Service Code= 16#4F)

HART Pass Through Query - MSG Source Element Structure Offset 0 Field Handle Data Type 1255 (1 byte) Definition Handle for Query (from Handle Field above)
Request Size = 1 byte
123
The 1756-IF8H or 1756-OF8H responds as shown in the table.

HART Pass through Query - MSG Destination Structure Offset 0 Offset Status Data Type 00 = Success 34 = Running 35 = Dead 0255 (1 byte) (1 byte) (1 byte) 0255 (1 byte) Definition Query Status If running, try again later (See MsgReady in Input Tag) Echo of HART Command HART Reply Status Byte #1 (response code) HART Reply Status Byte #2 Number of Data Bytes in Reply for HART Command Data Bytes Returned in Data Field of HART Reply to Requested Command
1 2 3 4 5257
HART Command HART CommStatus HART FieldDeviceStatus Data Size HART Reply Data
Flush Queue (Service Code= 16#50)

HART Flush Queue - MSG Source Element Structure Offset Field Data Type Definition No requested data Request size = 0 bytes
The 1756-IF8H or 1756-OF8H module respond as shown in the table.

Set Flush Queue - MSG Destination Structure Offset Field Data Type Definition
Note that Flush Queue can be sent to have the 1756-IF8H or 1756-OF8H module discard any pending HART replies awaiting a Query command. These replies are automatically discarded after a period of time, which is configurable on the Configuration Tab of the module properties. This value is usually 15 seconds. Unless you need to discard the replies faster than 15 seconds, you won't need to use this Flush Queue command.
124
HART Pass Through Message Ladder Logic Example
This is an example of sending HART command 9, which reads Device Variables from the HART Field Device. You send a list of the Device Variable codes you want, and the Field Device responds with its values, units, classification, and status. This is a new command with HART 6, and most devices don't support it, but this example gives you an idea of how to send any Pass through message command you want.
Note that SWPB reverses the order of bytes in the PV, SV, TV, FV floating-point numbers to be in the Logix REAL format.
125
The following is an Init Message configuration dialog for sending Command 9 to HART device on channel 0. Note instance 1 means channel 0.
User-defined Type: HARTCmd9InitSrc Size of HARTCmd9InitSrc Destination: HARTInitDst
126
This the Message Path Browser dialog.
See the query-message configuration dialog.
HARTQuerySrc
HARTCmd9QueryDst
127
See the dialog that shows tags. The data types are explained next.
See the dialogs that show the data-type definition and structure examples used for the following: Init message Source (User-defined Type: HARTCmd9InitSrc) Destination (HARTInitDst Type) Query message Source (HARTQuerySrc Type) Destination (HARTCmd9QueryDst Type)
See the HART command 9 example dialogs.
128
Chapter
Using HART Modules with Asset Management Software
This chapter describes important points about using 1756-IF8H and 1756-OF8H modules with asset management systems.
Using HART Modules with Asset Management Systems
Read this for important points about using 1756-IF8H and 1756-OF8H modules with asset management systems such as FactoryTalk AssetCentre or Endress+Hauser FieldCare systems. HART must be enabled before any asset management system access is possible, including scanning for multiplexors, if supported by your asset management software. You do not need to include HART PV data in your Input Tag, but you do need to check the Enable HART checkbox on the Configuration dialog of the Module Properties dialog. The Logix Controller must be connected to the 1756-IF8H or 1756-OF8H module. If the Logix controller is not connected, the module configuration was not sent to the HART module, and the channel is not yet configured for HART access. If using a handheld HART communicator and configuration tool, such as Rosemount 275 or Meriam, configure the tool as the secondary master. The Meriam handheld has a High-speed mode, which assumes it is the only master present. In this mode, the handheld may conflict with the 1756-IF8H or 1756-OF8H module. Usually, the Meriam handheld automatically detects the proper setting, but if not, set it manually. The ConfigurationChanged indication in the Field Device Status is automatically reset by the 1756-OF8H or 1756-IF8H module. Asset management systems might miss this indication if they are offline at the time of a change. A separate configuration-changed indication is in the field device status for the primary master (1756-IF8H module) and secondary master (handheld, for example). The 1756-IF8H or 1756-OF8H module do not reset the secondary master configuration changed status. Note that HART traffic from asset management Pass through messsages or from secondary masters slows the update rate of HART data in the controller or other Pass through message clients. Extra traffic on one channel affects other channels also.
129
130
Frequently Asked Questions
Read this section for answers to frequently asked questions. How do you use ControlLogix HART I/O modules as part of an asset management system? HART I/O modules let most asset management software packages communicate through the modules to HART field devices. Use RSLinx software to let the asset management software communicate through the NetLinx networks and 1756 backplane. Which RSLinx software is needed to support asset management software? You need RSLinx Classic software with a Professional, Gateway, or OEM activation. What else do I need to use asset management software with a ControlLogix HART I/O module? For Field Device Tool (FDT)/Device Type Manager (DTM) based asset management software such as E+H FieldCare, you use communication DTMs from Rockwell Automation. These same communication DTMs also work in the upcoming FactoryTalk AssetCentre software. For non FDT/DTM based asset management software, such Emerson AMS, use Connects software, available from Spectrum Controls http://www.spectrumcontrols.com/. What is FDT/DTM? FDT/DTM is a technology for managing intelligent devices. E+H FieldCare asset management software is an FDT frame application. The frame application runs the DTM files. The DTM files are executable files provided by control and device vendors. There are communication DTMs and device DTMs. We provide communication DTMs for components in the integrated architecture. Companies such as Endress+Hauser and Metso provide device DTMs for their instruments and valves. The device DTMs provide visualization of the parameters needed to configure, monitor, and maintain the devices. See www.fdtgroup.org for more information on FDT/DTM technology and to search for registered DTMs.
131
What communication DTMs are used with the ControlLogix HART I/O modules? One communication DTM is for RSLinx software and the 1756 backplane. Two communication DTMs are for the ControlLogix HART I/O modules themselves. Contact Rockwell Automation to get these DTMs. Can I get asset management software from Rockwell Automation? Yes. Rockwell offers a software bundle (catalog number 9504-SPECHARTENE), which contains E+H FieldCare asset management software, RSLinx Classic Professional software, and a one-year TechConnect support contract. The FieldCare software supports 512 field device tags. What version of Spectrum Connects software is needed for the ControlLogix HART I/O modules?
Spectrum Connects software, version 3.0 or later. This is needed only for asset management software that is not FDT/DTM based What if a DTM is not available for my HART field device? A generic DTM is available (included with FieldCare) which provides basic access to devices.
132
Notes:
Chapter
10
Unlatching Alarms and Reconfiguring Modules Using Ladder Logic
You can use ladder logic to perform run time services on your module. For example, in this chapter, we show how to unlatch alarms on a module using ladder logic. In addition to performing run time services, you can use ladder logic to change configuration.
Using Message Instructions
In ladder logic, you can use message instructions to send occasional services to any ControlLogix I/O module. Message instructions send an explicit service to the module, causing specific behavior to occur, for example, unlatching a high alarm. Message instructions maintain the following characteristics: Messages use unscheduled portions of system communications bandwidth. One service is performed per instruction. Performing module services does not impede module functionality, such as sampling inputs or applying new outputs.
133
134
Processing Real-time Control and Module Services

Services sent via message instructions are not as time critical as the module behavior defined during configuration and maintained by a real-time connection. Therefore, the module processes messaging services only after the needs of the I/O connection are met. For example, you want to unlatch all process alarms on the module, but real-time control of your process is still occurring using the input value from that same channel. Because the input value is critical to your application, the module prioritizes the sampling of inputs ahead of the unlatch service request. This prioritization lets input channels be sampled at the same frequency and the process alarms be unlatched in the time between sampling and producing the real-time input data.
One Service Performed Per Instruction

Message instructions cause a module service to be performed once per execution. For example, if a message instruction sends a service to the module to unlatch the high high alarm on a particular channel, that channels high high alarm unlatches, but can be set on a subsequent channel sample. The message instruction must then be reexecuted to unlatch the alarm a second time.
Creating a New Tag
To create a new tag, use this procedure, writing ladder logic in the Main Routine. 1. Double-click to enter the Main Routine, as shown in the figure.
Double-click here to enter the Main Routine.
135
2. Add a message instruction to a rung. 3. Create a tag for the message instruction added. a. Right-click the question mark (?). b. Click New Tag to see the New Tag dialog.
After adding a message instruction to a rung, you must create a tag for the message instruction as follows: A. Right-click the question mark (?) . B. Click New Tag to see the New Tag dialog.
4. From the New Tag dialog, fill-in this information:

From the New Tag dialog, complete these procedures: A. Name the tag. B. Click Base for tag type. C. Click Message data type. D. Click Controller scope, noting that to create message tags you must use Controller Scope.
IMPORTANT
We suggest you name the tag to indicate what module service is sent by the message instruction. In the example, the message instruction is used to unlatch a high alarm, and the tag names reflects this.
a. b. c. d.
Name the tag. Click Base for Tag Type. Click Message for Data Type. Click Controller for Scope, noting that to create message tags you must use Controller Scope.
136
Enter Message Configuration

After creating a new tag, you must enter message configuration.
Click here to see the message configuration dialogs
Enter message configuration on the following dialogs: Configuration Communication A description of the purpose and set-up of each dialog follows.
IMPORTANT
RSLogix 5000 software fills in fields such as the following, depending on the Message Type:
Service Code Object Type Object ID Object Attribute Source Number of Elements Destination
You are required to choose a Service Type and configure the Instance field. Instance represents the module channel on which the service is performed, if appropriate.
137
This dialog provides information on what module service to perform and where to perform it. For example, you must use this dialog to unlatch high high alarms (module service) on channel 0 of a module (where to perform service).
RSLogix 5000 Software, Version 10 and Later
Use this dialog to choose the Service Type. The list of available services includes multiple services to unlatch high high, high, low low, low, ramp, and rate alarms.
138
Communication Dialog
This dialog provides information on the path of the message instruction. For example, the slot number of a 1756-IF6I module distinguishes exactly which module a message is designated for.
IMPORTANT
Use the Browse button to see a list of the I/O modules in the system. You choose a path when you choose a module from the list. You must name an I/O module during initial module configuration to choose a path for your message instruction.
RSLogix 5000 Software, Version 10 and Later
Use this Browse button to see a list.
139
Unlatch Alarms in the Input Module

Example Rungs 04 show how to unlatch the following alarms: Channel 0 High high alarm - Rung 0 Channel 0 High alarm - Rung 1 Channel 0 Low alarm - Rung 2 Channel 0 Low low alarm - Rung 3 Channel 0 Rate alarm - Rung 4
IMPORTANT
An I/O module must be configured to latch alarms, before you can perform unlatch services using ladder logic. If an unlatch service is received by a module not configured to latch alarms, the message instruction errors. All alarms for channel 0 can be unlatched simultaneously with a single message instruction by leaving the object attribute field blank.
Rung 0 unlatches the high high alarm.
Rung 1 unlatches the high alarm.
Rung 2 unlatches the low alarm.
Click the box in each rung to see the configuration and communication information dialog associated with it.
Rung 3 unlatches the low low alarm.
Rung 4 unlatches the rate alarm.
140
See the Configuration dialog for Rung 0.
Choose choose a service type and configure the instance. Instance 1 is for channel 0.
See the Communication dialog for Rung 0. This dialog is the same for each rung of this example.
IMPORTANT
You must name an I/O module to set the message path under that modules communication dialog.
141
Unlatch Alarms in the Output Module

Example Rungs 57 show how to unlatch the following alarms. High limit alarm - Rung 5 Low limit alarm - Rung 6 Ramp alarm - Rung 7
Click the box in each rung to see the configuration and communication information dialog associated with it.
Rung 5 unlatches the high limit alarm.
Rung 6 unlatches the low limit alarm.
Rung 7 unlatches the ramp alarm.
See the Configuration dialog for Rung 5.
Choose a service type and configure the instance.
142
See the Communication dialog for Rung 5. This dialog is the same for each rung in this example.
IMPORTANT
You must name an I/O module to set the message path under that modules communication dialog.
143
Reconfiguring a Module
It is sometimes advantageous to change the functional operation of a module in the ControlLogix system automatically via the user program rather than using RSLogix 5000 software to reconfigure it. This way, changes in the process can dictate when the reconfiguration should take place rather than the user performing that function manually. Use the steps in this example when reconfiguring a module via ladder. 1. Move new configuration parameters to the Configuration portion of the Tag Structure associated with the module. 2. Use a message instruction to send a Reconfigure Module service to the same module. Before the new configuration parameters are sent to the module, you must make sure that their relationship to each other is in a format the module accepts (see tables).
IMPORTANT
Reconfiguring analog modules via ladder should be limited to functions that involve the changing of values only. We do not recommend that enabling or disabling features be done via ladder. Use RSLogix 5000 software to enable or disable these features.
144
See the tables that list module parameters that you can change via ladder logic:
Analog Input Module Parameters You Can Change Via Ladder Logic Feature High Engineering Value Low Engineering Value High-High Alarm Value High Alarm Value Low Alarm Value Low-Low Alarm Value Deadband Restriction Must not be equal to low engineering value Must not be equal to high engineering value Must be greater than or equal to high alarm value Must be greater than low alarm value Must be less than high alarm value Must be less than or equal to low alarm value Must be less than half of high alarm minus low alarm
Analog Output Module Parameters You Can Change Via Ladder Logic Feature High Clamp Value(1) Low Clamp Value(1)
(1)
Restriction Must be greater than low clamp value Must be less than high clamp value
The values for user-defined state at Fault or Program (set during initial configuration) must fall within the range of the High and Low Clamp values.
Chapter
11
Troubleshooting the Modules
This chapter describes how to interpret LED indicators and troubleshoot the modules.
Using Module Indicators to Troubleshoot
The analog I/O modules have indicators that provide indication of module status. ControlLogix modules use LED indicators as shown in the table. See the figure that shows the LED displays used with ControlLogix analog input HART modules.
LED Displays on Analog Input HART Modules ANALOG INPUT
CAL OK
20962-M
ControlLogix Module LED Indicators LED OK OK OK OK CAL

(1)
Display Means Steady Green The inputs are being multicast. Flashing Green The module has passed internal diagnostics, but is not currently performing connected communication. Flashing Red Previously established communication has timed out. Steady Red It is likely the module should be replaced Flashing Green The module is in calibration mode
Recommended Action None. None. Check controller. See LED blink code.(1) None.
Under fault conditions the module communicates a particular error via LED blink code. See the table that provides a description of the fault conditions and CAL LED blink codes.
145
146
CAL LED Blink Codes and Fault Status OK LED Red Red Red Red Red Red Red CAL LED Flashing Green 3 Blinks 4 Blinks 5 Blinks 6 Blinks 9 Blinks 10 Blinks Fault Status Firmware Download in Process Major Nonrecoverable Major Nonrecoverable Major Nonrecoverable Major Recoverable Major Nonrecoverable Major Recoverable Recommended Action Wait for download to complete. Boot code section has failed the CRC check. Send in module for repair. Serial Number not programmed. Send in module for repair. Boot code section has failed the CRC check. Send in module for repair. Application code section has failed the CRC check. Try reprogramming the module firmware. If condition persists send module in for repair. Module has lost its calibration data. Send in module for repair. Module firmware watchdog timer has timed out. Try resetting module. If condition persists send module in for repair.
To see fault status in RSLogix5000 software, from the Module Properties dialog, click Module Info. A channel fault such as wire off is displayed as a "Recoverable" Minor Fault.
General Troubleshooting Tips
When troubleshooting, consider these typical problems: Check the Enable HART box if you want any HART communication access to the channel including from asset management and Pass through messages. Choose the Input Tag Data Format that includes HART if you want to use the secondary process variables and device health information in your controller or display it on the RSView product. Put a jumper wire from IN0- to I-RTN-0 if using 420 mA devices. If you are mixing 2-wire and 4-wire HART devices on the same module, do not tie RTN-X together. Note that channel buttons apply to current dialogs only.
Channel buttons apply to the current dialog.
From RSLinx software, if you click RSWho and see 1756-Module, install the EDS file from www.ab.com/networks. In version 15 of RSLogix 5000 software, the module isnt in the list. Install the AddOnProfile from http://www.rockwellautomation.com/support by clicking Add On Profiles from the left. In version 15 of RSLogix 5000 software, with an error about ControlNet Attribute, use Scheduled Connections, or shutdown and restart the RSLogix 5000 software.
147
If you cant find HART data, look in sub-field Local:7:I.HART at bottom of the tag. See the ControlLogix Analog Module with HART Protocol Release Notes, publication 1756-RN636. When troubleshooting, consider these more obscure problems. The same device appears to be connected to every channel because a wiring problem causes signals to get connected across channels. In some cases, loose IRET wires cause the path to ground to flow through other channels. If Keep HART Replies for XX seconds is set small less than 5 the module throws away replies before you get a chance to retrieve them. This affects both MSG Pass through messages and PC-based asset management, such as FieldCare software. We recommend 15 seconds for this parameter. Be sure you have a HART device. FF, ProfiPA, and plain 420 devices look the same on the outside and power up OK. Write protect jumper is not reported correctly. This gets refreshed only if the device tells us it changed. E&H and Rosemount devices dont. Unenable HART then re-enable HART to get it refreshed on the HART Device Info dialog. For Pass through message troubleshooting issues, use these tips: Check module-specific online help. Copy the Handle to the Query. Check sizes of MSG and HART command. Check packing, alignment, and byte ordering. Use MsgReady. Use care in naming tags and UDTs to cause them to be grouped. Check .ER and Status.
For Input Tag troubleshooting, use these tips: Local:7:I.Ch0Fault if 1, suspect wiring/instrument problem. Local:7:I.Ch0HARTFault if 1, check Local:7:C.HARTEn (Enable HART). Local:7:I.HART.Ch0DeviceStatus.Init HART is enabled, but still trying to get a response from device. Local:7:I.HART.Ch0DeviceStatus.Fail HART is disabled, or not responding. Local:7:I.HART.Ch0DeviceStatus.CurrentFault the mA current measured doesnt match what is reported via HART. Could be caused by a recent change in value. This is intended to indicate a current leak, such as water in the conduit.
148
Local:7:I.HART.Ch0DeviceStatus.ResponseCode if negative, some communication problem. If positive, device is indicating some problem withthe command. 16#40 means command not supported. Local:7:I.HART.Ch0DeviceStatus.FieldDeviceStatus 0 is good; refer to help or see the Field Device Status table in Appendix D - Additional HART Protocol Information of this manual. Local:7:I.HART.Ch0PVStatus 16#C0 is good. 0 is bad. This could be a communication problem or something wrong with device. For example, with SVStatus, this could mean the device is not supported. When working with the HART Device Info dialog for troubleshooting, use these tips: HART Initializing means that HART is enabled, but not communicating. If this persist for 10 seconds after you click Refresh several times, suspect a HART communications problem or no device. Be sure a channel is HART Enabled. Be sure values appear, meaning HART communication is ok. Check PV values Local:7:HART.Ch0PV for changing numbers. Check analog values Local:7:Ch0Data for changing numbers; for the 1756-OF8H module, check that is valid.
149
Note that you must have a Logix connection or asset management, as this delivers the configuration to the module. From the Module Properties dialog, click Hart Device Info to see if it shows information.
HART Initializing
HART Initializing
Be sure a channel is HART enabled.
Using RSLogix 5000 Software to Troubleshoot Your Module
In addition to the LED display on the module, RSLogix 5000 software alerts you to fault conditions. You are alerted in one of these ways. Warning signal in the I/O Configuration next to the module This occurs when the connection to the module is broken Fault message in a status line Notification in the Tag Monitor General module faults Diagnostic faults Status on the Module Info Page
150
See the figure that shows fault notification on the Module Properties dialog.
Module Configuration Errors

Error Codes for 1756-IF8H Modules Extended Fault Code 0x0002 0x0003 0x0004 0x0005 0x0006 0x0007 0x0008 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E 0x000F 0x0010 0x0011 0x0012 Channel NA NA NA 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The additional fault code value details the configuration error if (16#0009) module configuration rejected: parameter error was received. See the table for a description.
Description INVALID FILTER INVALID RTS INVALID HART HANDLE TIME PROCESS ALARM LATCH NOT DISABLED RATE ALARM LATCH NOT DISABLED INVALID INPUT RANGE DIGITAL FILTER GREATER THAN TWICE THE RTS RATE INVALID RATE ALARM SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE INVALID HIGH LOW ALARM INVALID LOW LOW ALARM INVALID HIGH HIGH ALARM INVALID ALARM DB
151
Error Codes for 1756-IF8H Modules Extended Fault Code 0x0015 0x0016 0x0017 0x0018 0x0019 0x001A 0x001B 0x001C 0x001D 0x001E 0x001F 0x0020 0x0021 0x0022 0x0025 0x0026 0x0027 0x0028 0x0029 0x002A 0x002B 0x002C 0x002D 0x002E 0x002F 0x0030 0x0031 0x0032 0x0035 0x0036 0x0037 0x0038 0x0039 3 0x003A 0x003B 0x003C Channel 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 Description PROCESS ALARM LATCH NOT DISABLED RATE ALARM LATCH NOT DISABLED INVALID INPUT RANGE DIGITAL FILTER GREATER THAN TWICE THE RTS RATE INVALID RATE ALARM SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE INVALID HIGH LOW ALARM INVALID LOW LOW ALARM INVALID HIGH HIGH ALARM INVALID ALARM DB PROCESS ALARM LATCH NOT DISABLED RATE ALARM LATCH NOT DISABLED INVALID INPUT RANGE DIGITAL FILTER GREATER THAN TWICE THE RTS RATE INVALID RATE ALARM SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE
INVALID HIGH LOW ALARM INVALID LOW LOW ALARM INVALID HIGH HIGH ALARM
INVALID ALARM DB PROCESS ALARM LATCH NOT DISABLED RATE ALARM LATCH NOT DISABLED INVALID INPUT RANGE DIGITAL FILTER GREATER THAN TWICE THE RTS RATE INVALID RATE ALARM SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN
152
Error Codes for 1756-IF8H Modules Extended Fault Code 0x003D 0x003E 0x003F 0x0040 0x0041 0x0042 0x0045 0x0046 0x0047 0x0048 0x0049 0x004A 0x004B 0x004C 0x004D 0x004E 0x004F 0x0050 0x0051 0x0052 0x0055 0x0056 0x0057 0x0058 0x0059 0x005A 0x005B 0x005C 0x005D 0x005E 0x005F 0x0060 0x0061 0x0062 0x0065 0x0066 Channel 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 5 5 5 5 5 5 5 5 5 5 5 5 5 5 6 6 Description HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE INVALID HIGH LOW ALARM INVALID LOW LOW ALARM INVALID HIGH HIGH ALARM INVALID ALARM DB PROCESS ALARM LATCH NOT DISABLED RATE ALARM LATCH NOT DISABLED INVALID INPUT RANGE DIGITAL FILTER GREATER THAN TWICE THE RTS RATE INVALID RATE ALARM SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE INVALID HIGH LOW ALARM INVALID LOW LOW ALARM INVALID HIGH HIGH ALARM INVALID ALARM DB PROCESS ALARM LATCH NOT DISABLED RATE ALARM LATCH NOT DISABLED INVALID INPUT RANGE DIGITAL FILTER GREATER THAN TWICE THE RTS RATE INVALID RATE ALARM SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE INVALID HIGH LOW ALARM INVALID LOW LOW ALARM INVALID HIGH HIGH ALARM INVALID ALARM DB PROCESS ALARM LATCH NOT DISABLED RATE ALARM LATCH NOT DISABLED
153
Error Codes for 1756-IF8H Modules Extended Fault Code 0x0067 0x0068 0x0069 0x006A 0x006B 0x006C 0x006D 0x006E 0x006F 0x0070 0x0071 0x0072 0x0075 0x0076 0x0077 0x0078 0x0079 0x007A 0x007B 0x007C 0x007D 0x007E 0x007F 0x0080 0x0081 0x0082 Channel 6 6 6 6 6 6 6 6 6 6 6 6 7 7 7 7 7 7 7 7 7 7 7 7 7 7 Description INVALID INPUT RANGE DIGITAL FILTER GREATER THAN TWICE THE RTS RATE INVALID RATE ALARM SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING
INVALID HART RATE
INVALID HIGH LOW ALARM INVALID LOW LOW ALARM INVALID HIGH HIGH ALARM INVALID ALARM DB PROCESS ALARM LATCH NOT DISABLED RATE ALARM LATCH NOT DISABLED INVALID INPUT RANGE DIGITAL FILTER GREATER THAN TWICE THE RTS RATE INVALID RATE ALARM SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE INVALID HIGH LOW ALARM INVALID LOW LOW ALARM INVALID HIGH HIGH ALARM INVALID ALARM DB
Error Codes for 1756-OF8H Modules Extended Fault Code 0x0001 0x0004 0x0005 0x0006 0x000A Channel NA NA 0 0 0 Description INVALID REVISION NUMBER INVALID HART HANDLE TIME BAD RAMP LATCH BAD CLAMP LATCH BAD RAMP TO IDLE
154
Error Codes for 1756-OF8H Modules Extended Fault Code 0x000B 0x000C 0x000D 0x000E 0x000F 0x0010 0x0011 0x0012 0x0013 0x0014 0x0015 0x001B 0x001C 0x0020 0x0021 0x0022 0x0023 0x0024 0x0025 0x0026 0x0027 0x0028 0x0029 0x002A 0x002B 0x0031 0x0032 0x0036 0x0037 0x0038 0x0039 0x003A 0x003B 0x003C 0x003D 0x003E Channel 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 Description BAD RAMP TO FAULT INVALID INPUT RANGE BAD MAX RAMP BAD FAULT VALUE BAD IDLE VALUE SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE BAD CLAMP BAD RAMP LATCH BAD CLAMP LATCH BAD RAMP TO IDLE BAD RAMP TO FAULT INVALID INPUT RANGE BAD MAX RAMP BAD FAULT VALUE BAD IDLE VALUE SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE BAD CLAMP BAD RAMP LATCH BAD CLAMP LATCH BAD RAMP TO IDLE BAD RAMP TO FAULTS INVALID INPUT RANGE BAD MAX RAMP BAD FAULT VALUE BAD IDLE VALUE SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN
155
Error Codes for 1756-OF8H Modules Extended Fault Code 0x003F 0x0040 0x0041 0x0047 0x0048 0x004C 0x004D 0x004E 0x004F 0x0050 0x0051 0x0052 0x0053 0x0054 0x0055 0x0056 0x005D 0x005E 0x0062 0x0063 0x0064 0x0065 0x0066 0x0067 0x0068 0x0069 0x006A 0x006B 0x006C 0x006D 0x0073 0x0074 0x0078 0x0079 0x007A 0x007B Channel 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 5 5 5 5 5 5 Description HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE BAD CLAMP BAD RAMP LATCH BAD CLAMP LATCH BAD RAMP TO IDLE BAD RAMP TO FAULT INVALID INPUT RANGE BAD MAX RAMP BAD FAULT VALUE BAD IDLE VALUE SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE BAD RAMP LATCH BAD CLAMP LATCH BAD RAMP TO IDLE BAD RAMP TO FAULT INVALID INPUT RANGE BAD MAX RAMP BAD FAULT VALUE BAD IDLE VALUE SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE BAD CLAMP BAD RAMP LATCH BAD CLAMP LATCH BAD RAMP TO IDLE BAD RAMP TO FAULT INVALID INPUT RANGE BAD MAX RAMP
156
Error Codes for 1756-OF8H Modules Extended Fault Code 0x007C 0x007D 0x007E 0x007F 0x0080 0x0081 0x0082 0x0083 0x0089 0x008A 0x008E 0x008F 0x0090 0x0091 0x0092 0x0093 0x0094 0x0095 0x0096 0x0097 0x0098 0x0099 0x009F 0x00A0 0x00A4 0x00A5 0x00A6 0x00A7 0x00A8 0x00A9 0x00AA 0x00AB 0x00AC 0x00AD 0x00AE 0x00AF Channel 5 5 5 5 5 5 5 5 6 6 6 6 6 6 6 6 6 6 6 6 6 6 7 7 7 7 7 7 7 7 7 7 7 7 7 7 Description BAD FAULT VALUE BAD IDLE VALUE SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE BAD CLAMP BAD RAMP LATCH BAD CLAMP LATCH BAD RAMP TO IDLE BAD RAMP TO FAULT INVALID INPUT RANGE BAD MAX RAMP BAD FAULT VALUE IBAD DLE VALUE SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE BAD CLAMP BAD RAMP LATCH BAD CLAMP LATCH BAD RAMP TO IDLE BAD RAMP TO FAULT INVALID INPUT RANGE BAD MAX RAMP BAD FAULT VALUE BAD IDLE VALUE SIGNAL OUT OF RANGE LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL CAL BIAS SET TO NAN HIGH ENGINEERING EQUAL TO LOW ENGINEERING INVALID HART RATE BAD CLAMP
Appendix
Tag Definitions
What This Appendix Contains
This appendix provides information about data tags.
Communications Mode Tag Names and Definitions

The set of tags associated with any module depends on the module type and the communication format. These sets of tags apply: Input Output Configuration See the table that shows input data choice, tag, and main module type.
1756-IF8H Input Data Choice and Tags Input Data Choice Analog Only Tag Input Output Configuration Analog and HART PV Input Output Configuration 1756-OF8H Input Data Choice and Tags Input Data Choice Analog Only Tag Input Output Configuration Analog and HART PV Input Output Configuration Main Module Defined Type AB:1756_OF8H_Analog:I:0 AB:1756_OF8H:O:0 AB:1756_OF8H:C:0 AB:1756_OF8H_HARTPV:I:0 AB:1756_OF8H:O:0 AB:1756_OF8H:C:0 Subtype Used by Main Type None None AB:1756_OF8H_ChConfig_Struct:C:0 AB:1756_OF8H_HARTData:I:0 AB:1756_OF8H_HARTStatus_Struct:I:0 None AB:1756_OF8H_ChConfig_Struct:C:0 Main Module Defined Type AB:1756_IF8H_Analog:I:0 None AB:1756_IF8H:C:0 AB:1756_IF8H_HARTPV:I:0 None AB:1756_IF8H:C:0 Subtype Used by Main Type None None AB:1756_IF8H_ChConfig_Struct:C:0 AB:1756_IF8H_HARTData:I:0 AB:1756_IF8H_HARTStatus_Struct:I:0 None AB:1756_IF8H_ChConfig_Struct:C:0
157
158
Tag Definitions
Module-defined Data Types (1756-IF8H modules)

Member Name ChannelFaults Ch0Fault Type INT Boolean
See the table that lists and describes module-defined data types. These tables include information for input (as indicated by an I) and configuration (as indicated by a C).
Module-defined Data Type: AB:1756_IF8H_Analog:I:0 and Module-defined Data Type: AB:1756_IF8H_HARTPV:I:0 Default Display Style Binary Description Contains Ch0Fault through Ch7BrokenWire. See following ChannelFaults.0 Indicates a problem with analog data on Channel 0 or broken communication between the Logix controller and the 1756-IF8H module Example: Set if Analog signal in Ch0Data is larger than the Ch0Config.HHAlarmLimit or any of the other Alarm conditions in Ch0Status Ch1Fault Ch2Fault Ch3Fault Ch4Fault Ch5Fault Ch6Fault Ch7Fault Ch0BrokenWire Ch1BrokenWire Ch2BrokenWire Ch3BrokenWire Ch4BrokenWire Ch5BrokenWire Ch6BrokenWire Ch7BrokenWire HARTFaults Ch0HARTFault Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean Binary HARTFaults.0 Indicates a problem with HART data from the Field Device on Channel 0. Examples are HART not enabled, HART device not connected, HART communication failure due, for example, to noise HARTFaults.1 HARTFaults.2 HARTFaults.3 HARTFaults.4 HARTFaults.5 HARTFaults.6 HARTFaults.7 ChannelFaults.1 ChannelFaults.2 ChannelFaults.3 ChannelFaults.4 ChannelFaults.5 ChannelFaults.6 ChannelFaults.7 ChannelFaults.8 ChannelFaults.9 ChannelFaults.10 ChannelFaults.11 ChannelFaults.12 ChannelFaults.13 ChannelFaults.14 ChannelFaults.15
Ch1HARTFault Ch2HARTFault Ch3HARTFault Ch4HARTFault Ch5HARTFault Ch6HARTFault Ch7HARTFault
Boolean Boolean Boolean Boolean Boolean Boolean Boolean
Tag Definitions
159
Module-defined Data Type: AB:1756_IF8H_Analog:I:0 and Module-defined Data Type: AB:1756_IF8H_HARTPV:I:0 Member Name ModuleFaults CalFault Calibrating AnalogGroupFault Ch0Status Ch0HHAlarm Type SINT Boolean Boolean Boolean SINT Boolean Binary Default Display Style Binary ModuleFaults.1 1756-IF8H Module Calibration Failed ModuleFaults.2 (Bits 3...6 unused) Calibration in progress ModuleFaults.7 Indicates a fault has occurred on any channel (any of ChannelFaults) Indicates various Alarms on the Analog signal. Also sets Ch0Fault. See the individual alarm descriptions for details Ch0Status:0 Ch0Data > Ch0HHAlarmLimit. If Process Alarms are configured to Latch by setting Ch0Config.ProcessAlarmLatch this bit remains set even after the condition returns to normal, until reset via explicit CIP message. This message can be sent from RSLogix 5000 module properties Alarm dialog or from Logix Controller via MSG instruction Ch0Status:1 Ch0Data < Ch0LLAlarmLimit If Ch0Config.ProcessAlarmLatch is set, this alarm remains latched until it is unlatched Ch0Status:2 Ch0Data > Ch0HAlarmLimit If Ch0Config.ProcessAlarmLatch is set, this alarm remains latched until it is unlatched Ch0Status:3 Ch0Data < Ch0LAlarmLimit If Ch0Config.ProcessAlarmLatch is set, this alarm remains latched until it is unlatched Ch0Status:4 Ch0Data changing faster than Ch0RateAlarmLimit. Both Positive and Negative changes can cause this alarm. If Ch0Config.RateAlarmLatch is set, this alarm remains latched until it is unlatched Ch0Status:5 Analog signal is greater than or equal to the maximum detectable signal. Since the signal cannot be measured, it may be significantly above the maximum value Ch0Status:6 Analog signal is less than or equal to the minimum detectable signal. Since the signal cannot be measured, it may be significantly below the minimum value Ch0Status:7 Set if an error occurs during calibration for Channel 0, causing a bad calibration. Also sets CalFault Binary Ch1Status:0(1) Ch1Status:1(1) Ch1Status:2(1) Ch1Status:3(1)
Description
Ch0LLAlarm
Boolean
Ch0HAlarm
Boolean
Ch0LAlarm
Boolean
Ch0RateAlarm
Boolean
Ch0Overrange
Boolean
Ch0Underrange
Boolean
Ch0CalFault Ch1Status Ch1HHAlarm Ch1LLAlarm Ch1HAlarm Ch1LAlarm
Boolean SINT Boolean Boolean Boolean Boolean
160
Tag Definitions
Module-defined Data Type: AB:1756_IF8H_Analog:I:0 and Module-defined Data Type: AB:1756_IF8H_HARTPV:I:0 Member Name Ch1RateAlarm Ch1Overrange Ch1Underrange Ch1CalFault Ch2Status Ch2HHAlarm Ch2LLAlarm Ch2HAlarm Ch2LAlarm Ch2RateAlarm Ch2Overrange Ch2Underrange Ch2CalFault Ch3Status Ch3HHAlarm Ch3LLAlarm Ch3HAlarm Ch3LAlarm Ch3RateAlarm Ch3Overrange Ch3Underrange Ch3CalFault Ch4Status Ch4HHAlarm Ch4LLAlarm Ch4HAlarm Ch4LAlarm Ch4RateAlarm Ch4Overrange Ch4Underrange Ch4CalFault Type Boolean Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Binary Ch4Status:0(1) Ch4Status:1(1) Ch4Status:2(1) Ch4Status:3(1) Ch4Status:4(1) Ch4Status:5(1) Ch4Status:6(1) Ch4Status:7(1) Binary Ch3Status:0(1) Ch3Status:1(1) Ch3Status:2(1) Ch3Status:3(1) Ch3Status:4(1) Ch3Status:5(1) Ch3Status:6(1) Ch3Status:7(1) Binary Ch2Status:0(1) Ch2Status:1(1) Ch2Status:2(1) Ch2Status:3(1) Ch2Status:4(1) Ch2Status:5(1) Ch2Status:6(1) Ch2Status:7(1) Default Display Style Description Ch1Status:4(1) Ch1Status:5(1) Ch1Status:6(1) Ch1Status:7(1)
Tag Definitions
161
Module-defined Data Type: AB:1756_IF8H_Analog:I:0 and Module-defined Data Type: AB:1756_IF8H_HARTPV:I:0 Member Name Ch5Status Ch5HHAlarm Ch5LLAlarm Ch5HAlarm Ch5LAlarm Ch5RateAlarm Ch5Overrange Ch5Underrange Ch5CalFault Ch6Status Ch6HHAlarm Ch6LLAlarm Ch6HAlarm Ch6LAlarm Ch6RateAlarm Ch6Overrange Ch6Underrange Ch6CalFault Ch7Status Ch7HHAlarm Ch7LLAlarm Ch7HAlarm Ch7LAlarm Ch7RateAlarm Ch7Overrange Ch7Underrange Ch7CalFault Ch0Data Ch1Data Ch2Data Ch3Data Type SINT Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean REAL REAL REAL REAL Float Float Float Float Binary Ch7Status:0(1) Ch7Status:1(1) Ch7Status:2(1) Ch7Status:3(1) Ch7Status:4(1) Ch7Status:5(1) Ch7Status:6(1) Ch7Status:7(1) Value of analog signal on Channel 0 after conversion to Engineering Units Binary Ch6Status:0(1) Ch6Status:1(1) Ch6Status:2(1) Ch6Status:3(1) Ch6Status:4(1) Ch6Status:5(1) Ch6Status:6(1) Ch6Status:7(1) Default Display Style Binary Ch5Status:0(1) Ch5Status:1(1) Ch5Status:2(1) Ch5Status:3(1) Ch5Status:4(1) Ch5Status:5(1) Ch5Status:6(1) Ch5Status:7(1) Description
162
Tag Definitions
Module-defined Data Type: AB:1756_IF8H_Analog:I:0 and Module-defined Data Type: AB:1756_IF8H_HARTPV:I:0 Member Name Ch4Data Ch5Data Ch6Data Ch7Data CSTTimestamp Type REAL REAL REAL REAL DINT[2] Default Display Style Float Float Float Float Hex Timestamp taken at the time the input data was sampled in terms of Coordinated System Time, which is a 64-bit value in microseconds coordinated across the modules in the 1756 backplane Timestamp taken at the time the input data was sampled in millisecond resolution Contains HART field device health and dynamic process variables - applies to 1756_IF8H_HARTPV:I:0 only; for details, see the Module-defined Data Type: AB:1756_IF8H_HARTStatus_Struct:I:0 Description
RollingTimestamp HART
INT Module-defined Data Type: AB:1756_IF8H_HART Data:I:0
Decimal
(1)
See Ch0 equivalent in this table for description.
Tag Definitions
163
Module-defined Data Type: AB:1756_IF8H_HARTStatus_Struct:I:0 Member Name Init Type Boolean Default Display Style Description Searching for or Initializing HART device. If this is 0 and Fail is 1, then HART is not Enabled on this channel. If both are 1, then 1756-IF8H is sending out HART messages attempting to establish communication with a HART device HART communication failure or device not found or HART not enabled. If this bit is 1, none of the other data in the HART part of the Input Tag are valid. (HART. PVStatus will be set to 0 to also indicate this) Pass through message reply is ready Analog current measurement does not match the current the Field Device reported over HART network The Field Device configuration has changed and new Field Device configuration information can be obtained from the 1756-IF8H module via CIP MSG GetDeviceInfo, which will clear this bit Binary Binary HART communication status byte or Response code from a recent HART reply. See table below for details HART device status byte from a recent HART reply. Indicates the health of the HART Field device. See table below for details
Fail
Boolean
MsgReady CurrentFault ConfigurationChanged
Boolean Boolean Boolean
ResponseCode FieldDeviceStatus
SINT SINT
Understand Use of ResponseCode or Communication Status Table

This byte is multiplexed with the Response Code byte and indicates field device detection of a communication error. A communication error is always indicated when the most significant bit is set to one. The Communication Status is defined as a bit field table.
164
Tag Definitions
See the Communication Status table. The Communication Status is returned when a communication error is detected by the field device.
Communication Status Bit 7 = 1: Communication Errors Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 16#40 16#20 16#x10 16#x08 16#x04 16#x02 16#x01 Parity Error Overrun Error Framing Error Checksum Error (Reserved) RX Buffer Overflow (undefined) Vertical parity error - The parity of one or more of the bytes received by the device was not odd Overrun error - At least one byte of data in the receive buffer of the UART was overwritten before it was read (for example, the slave did not process incoming byte fast enough) Framing error - The Stop Bit of one or more bytes received by the device was not detected by the UART (for example, a mark or 1 was not detected when a Stop Bit should have occurred) Longitudinal parity error - The Longitudinal Parity calculated by the device did not match the Check Byte at thend of the message Reserved - Set to zero Buffer overflow - The message was too long for the receive buffer of the define Reserved - Set to zero
In RSLogix 5000 software, if the leftmost bit of the ResponseCode is set, it displays a negative number. In this case, the Response Code represents a Communication Fault, and the Communication Status table preceding shows how to interpret it. Change the display format to Hexadecimal to interpret communication status. If the leftmost bit of ResponseCode is 0 (value 0127), then there was no communication error and the value is a Response Code from the HART Field Device. To understand the Response Code, contact your HART field device manufacturer or the HART specification. See the Communication Status - Command Errors table in the Response Codes section of Appendix D of this manual for response code meanings.
Module-defined Data Type: AB:1756_IF8H_HARTData:I:0 Member Name Ch0DeviceStatus Ch1DeviceStatus Ch2DeviceStatus Ch3DeviceStatus Ch4DeviceStatus Type AB:1756_IF8H_HARTStatus_Struct ure:I:0 AB:1756_IF8H_HARTStatus_Struct ure:I:0 AB:1756_IF8H_HARTStatus_Struct ure:I:0 AB:1756_IF8H_HARTStatus_Struct ure:I:0 AB:1756_IF8H_HARTStatus_Struct ure:I:0 Default Display Style Description HART device health information and communication status for Channel 0
Tag Definitions
165
Module-defined Data Type: AB:1756_IF8H_HARTData:I:0 Member Name Ch5DeviceStatus Ch6DeviceStatus Ch7DeviceStatus Ch0PV Type AB:1756_IF8H_HARTStatus_Struct ure:I:0 AB:1756_IF8H_HARTStatus_Struct ure:I:0 AB:1756_IF8H_HARTStatus_Struct ure:I:0 REAL Float HART Primary Variable. The main value being measured by this HART instrument. The analog equivalent of this value is signaled on the Analog channel For example, a flow transmitter sends the flow rate in the PV field. (Many HART devices let this be configured to any of several dynamic variables, such as flow or density and also let the Units be configured). To see if this value is valid see Ch0PVStatus and the Ch0HARTFault and Ch0Fault. Ch0SV REAL Float HART Secondary Variable. Many HART instruments can measure more than one process parameter. For example, a flow transmitter might also provide the process temperature HART Tertiary or Third Variable. A HART flow transmitter might put the density here HART Fourth or Quaternary Variable. A HART flow transmitter might put the totalized flow here. Not all devices have more than 1 dynamic Variable HART status of the PV. If 16#C0, it is Good. See the HART PV, SV, TV, and FV Status Values table for details HART status of the SV. If 16#C0, it is Good. See the HART PV, SV, TV, and FV Status Values table for details HART status of the TV. If 16#C0, it is Good. See the HART PV, SV, TV, and FV Status Values table for details HART status of the FV. If 16#C0, it is Good. See the HART PV, SV, TV, and FV Status Values table for details Default Display Style Description
Ch0TV Ch0FV
REAL REAL
Float Float
Ch0PVStatus Ch0SVStatus Ch0TVStatus Ch0FVStatus
SINT SINT SINT SINT
Hex Hex Hex Hex
166
Tag Definitions
Module-defined Data Type: AB:1756_IF8H_HARTData:I:0 Member Name Ch1PV Ch1SV Ch1TV Ch1FV Ch1PVStatus Ch1SVStatus Ch1TVStatus Ch1FVStatus Ch2PV Ch2SV Ch2TV Ch2FV Ch2PVStatus Ch2SVStatus Ch2TVStatus Ch2FVStatus Ch3PV Ch3SV Ch3TV Ch3FV Ch3PVStatus Ch3SVStatus Ch3TVStatus Ch3FVStatus Ch4PV Ch4SV Ch4TV Ch4FV Ch4PVStatus Ch4SVStatus Ch4TVStatus Ch4FVStatus Ch5PV Ch5SV Ch5TV Type REAL REAL REAL REAL SINT SINT SINT SINT REAL REAL REAL REAL SINT SINT SINT SINT REAL REAL REAL REAL SINT SINT SINT SINT REAL REAL REAL REAL SINT SINT SINT SINT REAL REAL REAL Default Display Style Float Float Float Float Hex Hex Hex Hex Float Float Float Float Hex Hex Hex Hex Float Float Float Float Hex Hex Hex Hex Float Float Float Float Hex Hex Hex Hex Float Float Float Description See Ch0 equivalent in this table for description
Tag Definitions
167
Module-defined Data Type: AB:1756_IF8H_HARTData:I:0 Member Name Ch5FV Ch5PVStatus Ch5SVStatus Ch5TVStatus Ch5FVStatus Ch6PV Ch6SV Ch6TV Ch6FV Ch6PVStatus Ch6SVStatus Ch6TVStatus Ch6FVStatus Ch7PV Ch7SV Ch7TV Ch7FV Ch7PVStatus Ch7SVStatus Ch7TVStatus Ch7FVStatus Type REAL SINT SINT SINT SINT REAL REAL REAL REAL SINT SINT SINT SINT REAL REAL REAL REAL SINT SINT SINT SINT Default Display Style Float Hex Hex Hex Hex Float Float Float Float Hex Hex Hex Hex Float Float Float Float Hex Hex Hex Hex Description See Ch0 equivalent in this table for description
HART PV, SV, TV, and FV are Dynamic Variables contain the values of Device Variables, which are various direct or indirect process measurements performed by the HART Field Device. Some devices let a set of their internal device variables be mapped to the PV, SV, TV, FV Dynamic Variables that are automatically collected in the 1756-IF8H Input Tag. This mapping is part of the Field Device configuration, usually performed via a handheld configurator or asset management system, such as FactoryTalk AssetCentre or Endress+Hauser FieldCare system.
168
Tag Definitions
HART PVStatus, SVStatus, TVStatus, FVStatus are known as Device Variable Status values. These Status values are composed of groups of bits that indicate the quality of the associated device variable.
Device Family Specific Status Process Data Status 11 Good 01 Poor Accuracy 10 Manual/Fixed 00 Bad Limit Status 11 Constant 01 Low Limited 10 High Limited 00 Not Limited More Device Variable Status Available
The Limit Status can be used to control windup in PID loops.

HART PV, SV, TV, and FV Status Values HART PV, SV, TV FV Status Values Decimal 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Hex 0 1 2 3 4 5 6 7 8 9 A B C D E F 10 11 12 13 14 Binary 00000000 00000001 00000010 00000011 00000100 00000101 00000110 00000111 00001000 00001001 00001010 00001011 00001100 00001101 00001110 00001111 00010000 00010001 00010010 00010011 00010100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 01 01 01 01 Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Not Limited Low Limited Low Limited Low Limited Low Limited Low Limited Quality Limit More Status Available? 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 no no no no no no no no yes yes yes yes yes yes yes yes no no no no no Device Family Specific Binary 000 001 010 011 100 101 110 111 000 001 010 011 100 101 110 111 000 001 010 011 100 Decimal 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4
Tag Definitions
169
HART PV, SV, TV, and FV Status Values 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 00010101 00010110 00010111 00011000 00011001 00011010 00011011 00011100 00011101 00011110 00011111 00100000 00100001 00100010 00100011 00100100 00100101 00100110 00100111 00101000 00101001 00101010 00101011 00101100 00101101 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad Bad 01 01 01 01 01 01 01 01 01 01 01 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Low Limited Low Limited Low Limited Low Limited Low Limited Low Limited Low Limited Low Limited Low Limited Low Limited Low Limited High Limited High Limited High Limited High Limited High Limited High Limited High Limited High Limited High Limited High Limited High Limited High Limited High Limited High Limited 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 no no no yes yes yes yes yes yes yes yes no no no no no no no no yes yes yes yes yes yes 101 110 111 000 001 010 011 100 101 110 111 000 001 010 011 100 101 110 111 000 001 010 011 100 101 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5
Note that this Device Variable Status byte is a new HART feature in HART protocol revision 6 and many HART devices do not yet support it. For those devices, the 1756-IF8H or 1756-OF8H module creates a status value based on the communication status of the device. If the PV, SV, TV, FV are being collected without communication errors, the value is set to 16#C0, indicating Good, Not Limited. Otherwise, the value is set to 0, indicating Bad, Not Limited, no specific information available.
170
Tag Definitions
Module-defined Data Type: AB:1756_IF8H_ChConfig_Struct:C:0 Member Name ChConfig (Bits 0...3 not used) RateAlarmLatch ProcessAlarmLatch AlarmDisable HARTEn RangeType DigitalFilter RateAlarmLimit LowSignal HighSignal LowEngineering HighEngineering LAlarmLimit HAlarmLimit LLAlarmLimit HHAlarmLimit AlarmDeadband CalBias Type SINT Boolean Boolean Boolean Boolean SINT INT REAL REAL REAL REAL REAL REAL REAL REAL REAL REAL REAL Decimal Decimal Float Float Float Float Float Float Float Float Float Float Float Default Display Style Binary ChConfig:4 ChConfig:5 ChConfig:6 ChConfig:7 Description
Tag Definitions
171
Module-defined Data Type: AB:1756_IF8H:C:0 Member Name ModuleFilter RealTimeSample AB:1756_IF8H_ChConfig_Struct:C:0 AB:1756_IF8H_ChConfig_Struct:C:0 AB:1756_IF8H_ChConfig_Struct:C:0 AB:1756_IF8H_ChConfig_Struct:C:0 AB:1756_IF8H_ChConfig_Struct:C:0 AB:1756_IF8H_ChConfig_Struct:C:0 AB:1756_IF8H_ChConfig_Struct:C:0 AB:1756_IF8H_ChConfig_Struct:C:0 PassthroughHandleTimeout PassthroughConfig PassthroughCmdFreq_14 PassthroughCmdFreq_15 INT INT Boolean Boolean Decimal Binary Bits 0...13 not used PassthroughConfig14 PassthroughConfig15 Type SINT INT Default Display Style Decimal Decimal Ch0Config Ch1Config Ch2Config Ch3Config Ch4Config Ch5Config Ch6Config Ch7Config Description
172
Tag Definitions
Module-defined Data Types (1756-OF8H)
See the tables that list and describe module-defined data types for the 1756-OF8H HART analog output module. These tables include information for input (as indicated by an I), output (as indicated by an O), and configuration (as indicated by a C).
Module-defined Data Type: AB:1756_OF8H:O:0 Member Name Ch0Data Ch1Data Ch2Data Ch3Data Ch4Data Ch5Data Ch6Data Ch7Data Type REAL REAL REAL REAL REAL REAL REAL REAL Default Display Style Float Float Float Float Float Float Float Float Description Value in Engineering units to output on the analog signal of Channel 0
Module-defined Data Type: AB:1756_OF8H - Analog:I:0 and Module-defined Data Type: AB:1756_OF8H_HARTPV:I:0 Member Name Type Default Display Style Binary ChannelFaults.0 ChannelFaults.1 ChannelFaults.2 ChannelFaults.3 ChannelFaults.4 ChannelFaults.5 ChannelFaults.6 ChannelFaults.7 ChannelFaults.8 (bits 9...15 unused) Binary HARTFault.0 Indicates a problem with HART data from the Field Device on Channel 0. Examples are HART not enabled, HART device not connected, HART communication failure due to noise HARTFault.1 HARTFault.2 HARTFault.3 Description
Channel Faults Ch0Fault Ch1Fault Ch2Fault Ch3Fault Ch4Fault Ch5Fault Ch6Fault Ch7Fault LoopOutputFault HARTFaults Ch0HARTFault
INT Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean
Ch1HARTFault Ch2HARTFault Ch3HARTFault
Boolean Boolean Boolean
Tag Definitions
173
Module-defined Data Type: AB:1756_OF8H - Analog:I:0 and Module-defined Data Type: AB:1756_OF8H_HARTPV:I:0 Ch4HARTFault Ch5HARTFault Ch6HARTFault Ch7HARTFault CalFault Calibrating Ch0Status Ch0OpenWire Ch0NotANumber Ch0CalFault Ch0InHold Ch0RampAlarm Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Binary Ch0Status:7 Only valid in Current mode (example 420 mA). 1 indicates no current is flowing, probably due to open circuit. Ch0Status:5 Ch0Data is not a valid floating point number Ch0Status:4 Fault during calibration of channel 0 Ch0Status:3 Channel holding its last output value, waiting for controller to match the value, indicating that bumpless initialization of the control loop is complete Ch0Status:2 Rate of change in Ch0Data exceeds Ch0Config.MaxRampRate. Rate of change is determined by the change in Ch0Data divided by the RPI period. Thus if a step change in Ch0 cannot be reached via the configured MaxRampRate within one RPI, then Ch0RampAlarm is set to 1. If Ch0Config.RampAlarmLatch is 1, then Ch0RampAlarm remains set until explicitly reset using CIP message even if the condition returns to normal. The CIP message can be sent via MSG instruction in Logix controller or from the RSLogix Module Properties Limit page Ch0Status:1 The analog output signal is being limited by the Ch0Config.LowLimit value.If Ch0Config.LimitAlarmLatch is 1, alarm is retained until explicitly reset. Ch0Status:0 The analog output signal is being limited by the Ch0Config.HighLimit value.If Ch0Config.LimitAlarmLatch is 1, alarm is retained until explicitly reset. Binary Ch1Status:7(1) Ch1Status:5(1) Ch1Status:4(1) Ch1Status:3(1) Ch1Status:2(1) Ch1Status:1(1) Ch1Status:0(1) Binary Ch2Status:7(1) Ch2Status:5(1) Ch2Status:4(1) Ch2Status:3(1) HARTFault.4 HARTFault.5 HARTFault.6 HARTFault.7 ModuleFaults.1 A fault during calibration on any channel ModuleFaults.2 (bits 36 not used)Calibration in progress ModuleFaults.7 A fault in the analog signal on any channel
AnalogGroupFault Boolean
Ch0LLimitAlarm Ch0HLimitAlarm Ch1Status Ch1OpenWire Ch1NotANumber Ch1CalFault Ch1InHold Ch1RampAlarm Ch1LLimitAlarm Ch1HLimitAlarm Ch2Status Ch2OpenWire Ch2NotANumber Ch2CalFault Ch2InHold
Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean
174
Tag Definitions
Tag Definitions
175
176
Tag Definitions
Module-defined Data Type: AB:1756_OF8H - Analog:I:0 and Module-defined Data Type: AB:1756_OF8H_HARTPV:I:0 Ch2RampAlarm Ch2LLimitAlarm Ch2HLimitAlarm Ch3Status Ch3OpenWire Ch3NotANumber Ch3CalFault Ch3InHold Ch3RampAlarm Ch3LLimitAlarm Ch3HLimitAlarm Ch4Status Ch4OpenWire Ch4NotANumber Ch4CalFault Ch4InHold Ch4RampAlarm Ch4LLimitAlarm Ch5Status Ch5OpenWire Ch5NotANumber Ch5CalFault Ch5InHold Ch5RampAlarm Ch5LLimitAlarm Ch5HLimitAlarm Ch6Status Ch6OpenWire Ch6NotANumber Ch6CalFault Ch6InHold Ch6RampAlarm Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Binary Ch6Status:7(1) Ch6Status:5(1) Ch6Status:4(1) Ch6Status:3(1) Ch6Status:2(1) Binary Ch5Status:7(1) Ch5Status:5(1) Ch5Status:4(1) Ch5Status:3(1) Ch5Status:2(1) Ch5Status:1(1) Ch5Status:0(1) Binary Ch4Status:7(1) Ch4Status:5(1) Ch4Status:4(1) Ch4Status:3(1) Ch4Status:2(1) Ch4Status:1(1) Binary Ch3Status:7(1) Ch3Status:5(1) Ch3Status:4(1) Ch3Status:3(1) Ch3Status:2(1) Ch3Status:1(1) Ch3Status:0(1) Ch2Status:2(1) Ch2Status:1(1) Ch2Status:0(1)
Tag Definitions
177
Module-defined Data Type: AB:1756_OF8H - Analog:I:0 and Module-defined Data Type: AB:1756_OF8H_HARTPV:I:0 Ch6LLimitAlarm Ch6HLimitAlarm Ch7Status Ch7OpenWire Ch7NotANumber Ch7CalFault Ch7InHold Ch7RampAlarm Ch7LLimitAlarm Ch7HLimitAlarm Ch0Data Boolean Boolean SINT Boolean Boolean Boolean Boolean Boolean Boolean Boolean REAL Float Binary Ch0Status:7(1) Ch0Status:5(1) Ch0Status:4(1) Ch0Status:3(1) Ch0Status:2(1) Ch0Status:1(1) Ch0Status:0(1) Analog Value actually output in Engineering units. This might be different than Output Tag Ch0Data if the value exceeds the LowLimit or HighLimit, has a MaxRampRate applied, is being Held for initialization, or controller in Fault or Program mode Ch6Status:1(1) Ch6Status:0(1)
Ch1Data Ch2Data Ch3Data Ch4Data Ch5Data Ch6Data Ch7Data CSTTimestamp[2]
REAL REAL REAL REAL REAL REAL REAL DINT[2]
Float Float Float Float Float Float Float 64-bit Coordinated System Time Timestamp in microseconds of the last output update. Timebase synchronized with other modules in the rack 16 bit timestamp in milliseconds. Timebase local to the 1756-OF8H module HART data read from the output device. Note that this updates more slowly than the analog portions of the input tag. This applies to AB:1756_OF8H_HARTPV:I:O only; for details on what appears in the variables, see the Module-defined Data Type: AB:1756_OF8H_HARTData:I:0 table
RollingTimestamp INT HART

AB:1756_OF8H _HARTData:I:O
(1)
See Ch0 equivalent in this table for description.
178
Tag Definitions
Module-defined Data Type: AB:1756_OF8H_HARTStatus_Struct:I:0 Member Name Init Fail MsgReady CurrentFault ConfigurationChanged ResponseCode FieldDeviceStatus Type Bit Boolean Bit Boolean Bit SINT SINT Binary Binary Default Display Style Description Channel:0 Channel:1 Channel:2 Channel:3 Channel:4
Module-defined Data Type: AB:1756_OF8H_HARTData:I:0 Member Name Type Default Display Style Description
AB:1756_OF8H_HARTStatus_Structure:I:0 AB:1756_OF8H_HARTStatus_Structure:I:0 AB:1756_OF8H_HARTStatus_Structure:I:0 AB:1756_OF8H_HARTStatus_Structure:I:0 AB:1756_OF8H_HARTStatus_Structure:I:0 AB:1756_OF8H_HARTStatus_Structure:I:0 AB:1756_OF8H_HARTStatus_Structure:I:0 AB:1756_OF8H_HARTStatus_Structure:I:0 Ch0PV REAL Float
Ch0DeviceStatus Ch1DeviceStatus Ch2DeviceStatus Ch3DeviceStatus Ch4DeviceStatus Ch5DeviceStatus Ch6DeviceStatus Ch7DeviceStatus Digital readback of the Primary Variable. For example, on a valve controller, the command valve position in engineering units such as % Secondary Variable - in a valve positioner, perhaps the Actual valve position Third or Tertiary Variable - in a pneumatic valve positioner, perhaps the air supply pressure Fourth or Quaternary Variable - in a motor operated valve positioner, perhaps the torque
Ch0SV Ch0TV
REAL REAL
Float Float
Ch0FV Ch0PVStatus Ch0SVStatus Ch0TVStatus Ch0FVStatus
REAL SINT SINT SINT SINT
Float Hex Hex Hex Hex
Tag Definitions
179
Module-defined Data Type: AB:1756_OF8H_HARTData:I:0 Ch1PV Ch1SV Ch1TV Ch1FV Ch1PVStatus Ch1SVStatus Ch1TVStatus Ch1FVStatus Ch2PV Ch2SV Ch2TV Ch2FV Ch2PVStatus Ch2SVStatus Ch2TVStatus Ch2FVStatus Ch3PV Ch3SV Ch3TV Ch3FV Ch3PVStatus Ch3SVStatus Ch3TVStatus Ch3FVStatus Ch4PV Ch4SV Ch4TV Ch4FV Ch4PVStatus Ch4SVStatus Ch4TVStatus Ch4FVStatus Ch5PV Ch5SV Ch5TV Ch5FV Ch5PVStatus REAL REAL REAL REAL SINT SINT SINT SINT REAL REAL REAL REAL SINT SINT SINT SINT REAL REAL REAL REAL SINT SINT SINT SINT REAL REAL REAL REAL SINT SINT SINT SINT REAL REAL REAL REAL SINT Float Float Float Float Hex Hex Hex Hex Float Float Float Float Hex Hex Hex Hex Float Float Float Float Hex Hex Hex Hex Float Float Float Float Hex Hex Hex Hex Float Float Float Float Hex See Ch0 equivalent in this table for description See Ch0 equivalent in this table for description See Ch0 equivalent in this table for description See Ch0 equivalent in this table for description See Ch0 equivalent in this table for description
180
Tag Definitions
Module-defined Data Type: AB:1756_OF8H_HARTData:I:0 Ch5SVStatus Ch5TVStatus Ch5FVStatus Ch6PV Ch6SV Ch6TV Ch6FV Ch6PVStatus Ch6SVStatus Ch6TVStatus Ch6FVStatus Ch7PV Ch7SV Ch7TV Ch7FV Ch7PVStatus Ch7SVStatus Ch7TVStatus Ch7FVStatus SINT SINT SINT REAL REAL REAL REAL SINT SINT SINT SINT REAL REAL REAL REAL SINT SINT SINT SINT Hex Hex Hex Float Float Float Float Hex Hex Hex Hex Float Float Float Float Hex Hex Hex Hex See Ch0 equivalent in this table for description See Ch0 equivalent in this table for description
Tag Definitions
181
Module-defined Data Type: AB:1756_OF8H_ChConfig_Struct:C:0 Member Name RampToFault RampToProg RampToRun ProgMode FaultMode LimitAlarmLatch RampAlarmLatch AlarmDisable HoldForInit HARTEnable RangeType MaxRampRate FaultValue ProgValue LowSignal HighSignal LowEngineering HighEngineering LowLimit HighLimit CalBias Type Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean INT REAL REAL REAL REAL REAL REAL REAL REAL REAL REAL Float Float Float Float Float Float Float Float Float Float Default Display Style Description ConfigBits:9 ConfigBits:8 ConfigBits:7 ConfigBits:6 ConfigBits:5 ConfigBits:4 ConfigBits:3 ConfigBits:2 ConfigBits:1 ConfigBits:0
182
Tag Definitions
Module-defined Data Type: AB:1756_OF8H:C:0 Member name AB:1756_OF8H_ChConfig_Struct:C:0 AB:1756_OF8H_ChConfig_Struct:C:0 AB:1756_OF8H_ChConfig_Struct:C:0 AB:1756_OF8H_ChConfig_Struct:C:0 AB:1756_OF8H_ChConfig_Struct:C:0 AB:1756_OF8H_ChConfig_Struct:C:0 AB:1756_OF8H_ChConfig_Struct:C:0 AB:1756_OF8H_ChConfig_Struct:C:0 PassthroughHandleTimeout PassthroughFreq_14 PassthroughFreq_15 INT Boolean Boolean Decimal PassthroughConfig:14 PassthroughConfig:15 Type Default Display Style Description Ch0Config Ch1Config Ch2Config Ch3Config Ch4Config Ch5Config Ch6Config Ch7Config
Appendix
Calibration Information
What This Appendix Contains Analog to Digital (A/D) Converter Accuracy
This appendix offers reference calibration information to assist you in using the ControlLogix analog I/O module.
Two types of calibration occur on a ControlLogix analog I/O module. The user-directed and user-performed calibration process. This type of calibration occurs only when you determine it is necessary and involves an external calibration instrument. A self-calibration process that takes place internally on ControlLogix analog I/O modules when either module power is cycled or you begin the user calibration. The A/D self-calibration feature maintains the accuracy of the A/D convertor found on all 1756 isolated analog modules. This feature executes each time the module cycles power or when a self-calibration cycle is initiated. The self-calibration compensates for inaccuracies of the on-board reference signal and the A/D convertor only. In other words, the self-calibration feature makes sure that the A/D convertor itself is accurate with respect to its on-board voltage reference that is used for a conversion of the input signal. Together with user calibration, the modules total accuracy is maintained.
Calibrated Accuracy
The calibrated accuracy specification represents the modules accuracy when its ambient (operating) temperature is the same as the temperature at which the module was calibrated. Immediately following a calibration, a ControlLogix analog I/O module is most accurate. Because the module was calibrated at its zero and span, the inaccuracy is largely non-linearity between zero and span. Assuming the module is operating at the exact temperature when it was calibrated and uses the same voltage source to check the post-calibration accuracy, a module can be as accurate as 0.01% to 0.05% of range. Once the module begins operation, its accuracy lessens as components change over time.
183
184
Calibration Information
However, this change (in components or accuracy) is different from the gain drift with temperature specification. Other than non-linearity, the calibrated accuracy at 25 C (77 F) specification represents a time drift/aging specification between calibrations. A module with a calibration accuracy of 0.01% of range immediately following calibration is estimated to be better than 0.1% of range @ 25 C (77 F) for one year (the calibration cycle). The reason for the difference between 0.01% and 0.1% of range is that the calibrated accuracy at 25 C (77 F) specification must capture the effect of component aging until the next time the module is calibrated. Primarily, the module's operating conditions, such as temperature, humidity, and power cycling, affect component aging. Because ControlLogix analog I/O modules operate in different conditions, the specific accuracy deviation from 0.01% of range cannot be measured. Typically, however, a modules calibrated accuracy at 25 C (77 F) is closer to 0.05% of range than 0.1% of range as the 0.1% of range is determined by the worst-case scenario operating conditions.
Error Calculated Over Hardware Range
A ControlLogix analog I/O modules calibration accuracy at 25 C (77 F) is calculated over the full hardware range of the module and is not dependent on the applications use of the range. The error is the same if you are measuring it across a 10% or 100% portion of a given range. However, a modules accuracy at 25 C (77 F) is dependent on the hardware range in which the module operates.
How Operating Temperature Changes Affect Module Accuracy
The following specifications take into account how the modules operating temperature changes can affect a modules accuracy: Gain Drift With Temperature Module Error Over Full Temperature Range Gain drift with temperature represents the calibration inaccuracy that occurs as a modules ambient (operating) temperature drifts from the temperature at which it was calibrated. You can use the gain drift with temperature specification (varies for each catalog number) to determine the modules calibration inaccuracy for each degree between calibration and operating temperature. The gain drift with temperature specification represents a percentage of the full operating range that the modules calibration is inaccurate to for each degree difference. The specification is determined with the following formula: Gain Drift with Temperature = (PPM/C) x Modules Full Range
Appendix
Using 1492 Wiring Systems with Your Analog I/O Module
What This Appendix Contains Using a Wiring System
This appendix provides information about an alternative to buying removable terminal blocks and connecting the wires yourself.
As an alternative to buying removable terminal blocks and connecting the wires yourself, you can buy a wiring system of these items: Analog interface modules (AIFM) that mount on DIN rails and provide the output terminal blocks for the I/O module - Use the AIFMs with the prewired cables that match the I/O module to the interface module. For a list of the AIFMs available for use with ControlLogix analog I/O modules, see the table that provides the list. I/O module-ready prewired cables - One end of the cable assembly is a removable terminal base that plugs into the front of the I/O module. The other end has individually color-coded conductors that connect to a standard terminal block. For a list of the prewired cables available for use with ControlLogix analog I/O modules, see the table that provides the list.
Analog Interface Modules
I/O Module Prewired Cable Analog Interface Module
IMPORTANT
The ControlLogix system has been agency certified using the ControlLogix removable terminal bases (RTBs) only (for example, catalog numbers 1756-TBCH, 1756-TBNH, 1756-TBSH, and 1756-TBS6H). Any application that requires agency certification of the ControlLogix system using other wiring termination methods may require application-specific approval by the certifying agency.
185
186
Using 1492 Wiring Systems with Your Analog I/O Module
Analog Interface Module and Prewired Cables For 1756-IF8H 1756-OF8H Use 1492-AIFM8-3 With 1492-ACABLExUD (current) 1492-ACABLExUC (voltage) 1492-ACABLExWB
Analog Interface Modules Available for Use with ControlLogix Analog I/O Modules Catalog Number 1492-AIFM8-3 Type of Analog Interface Module Feed-through Description 8 channels with 3 terminals per channel
I/O Module-ready Prewired Cables Used with ControlLogix Analog I/O Modules Catalog Number(1) 1492-ACABLExUC 1492-ACABLExUD 1492-ACABLExWB
(1)
Number of Conductor Nominal Outer Conductors(2) Size Diameter 9 twisted pairs 22 AWG 6.8 mm (0.27 in.)
Removable Terminal Block at the I/O Module End 1756-TBCH 1756-TBNH
Cables are available in lengths of 0.5 m, 1.0 m, 2.5 m, and 5.0 m. To order, insert the code for the desired cable length into the catalog number in place of the x: 005=0.5 m, 010=1.0 m, 25=2.5 m, 050=5 m. Build-to-order cable lengths are also available. Each cable for analog I/O has an overall shield with a ring lug on a 200 mm (8.87 in.) exposed drain wire at the I/O module end of the cable.
(2)
Appendix
Additional HART Protocol Information
This appendix describes the HART protocol and provides references for additional information about the protocol. Consult the HART protocol specification and vendor-provided documentation for specifics on HART commands. This appendix provides the following: HART protocol background information Common practice command sets Extended command sets References to additional information
HART Field Communications Protocol is widely accepted in the industry as the standard for digitally enhanced 420mA communication with smart field instruments. The HART Protocol message structure, command set, and status are discussed in this appendix. The HART command set is organized into these groups and provides read and write access to a wide array of information available in smart field instruments: Universal commands provide access to information that is useful in normal plant operation such as the instrument manufacturer, model, tag, serial number, descriptor, range limits, and process variables. All HART devices must implement universal commands. Common practice commands provide access to functions that can be carried out by many devices. Device specific commands provide access to functions that can be unique to a particular device.
Message Structure
Read this section for a description of transaction procedure, character coding, and message structure of the HART protocol. These correspond to layer 2 (data-link layer) of the OSI protocol reference model.
187
188
Master-slave Operation
HART is a master-slave protocol. This means that each message transaction is originated by the master; the slave (field) device replies when it receives a command message addressed to it. The reply from the slave device acknowledges that the command was received and can contain data requested by the master.
Multiple Master Operation

The HART protocol provides for two active masters in a system: one primary and one secondary. The two masters have different addresses. Each can positively identify replies to its own command messages. The 1756-IF8H or 1756-OF8H modules act as primary master. A secondary master such as a handheld configuration device may be connected also.
Transaction Procedure
HART is a half-duplex protocol. After completion of each message, the FSK carrier signal must be switched off to let the other station transmit. The carrier control timing rules state that the carrier should be turned on not more than 5 bit times before the start of the message (that is, the preamble) and turned off not more than 5 bit times after the end of the last byte of the message (the checksum). The master is responsible for controlling message transactions. If there is no reply to a command within the expected time, the master should retry the message. After a few retries, the master should abort the transaction, since presumably the slave device or the communication link has failed. After each transaction is completed, the master should pause for a short time before sending another command, to provide an opportunity for the other master to break in if it wishes. This way, two masters (if they are present) take turns at communicating with the slave devices. Typical message lengths and delays allow two transactions per second.
189
Burst Mode
Burst mode is not supported by the 1756-IF8H and 1756-OF8H modules.
Status
Two bytes of status also called the response code and field device status are included in every reply message from a field or slave device. These two bytes convey communication errors, command response problems, and field device status. If an error is detected in the outgoing communication, the most significant bit (bit 7) of the first byte is set to 1 and the details of the error are reported in the rest of that byte. The second byte is then all zeros. Communication errors are typically those that would be detected by a UART (parity overrun and framing errors). The field device also reports overflow of its receive buffer and any discrepancy between the message content and the checksum received. In RSLogix 5000 software if the leftmost bit of the ResponseCode is set, it displays a negative number. In this case, the Response Code represents a Communication Fault, and the Communication Status table shows how to interpret it.
Communication Status - Communication Errors Bit 7 = 1: Communication Errors Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 16#40 16#20 16#10 16#08 16#04 16#02 16#01 Parity Error Overrun Error Framing Error Checksum Error (Reserved) RX Buffer Overflow (undefined) Vertical parity error - The parity of one or more of the bytes received by the device was not odd Overrun error - At least one byte of data in the receive buffer of the UART was overwritten before it was read (for example, the slave did not process incoming byte fast enough) Framing error - The Stop Bit of one or more bytes received by the device was not detected by the UART (for example, a mark or 1 was not detected when a Stop Bit should have occurred) Longitudinal parity error - The Longitudinal Parity calculated by the device did not match the Check Byte at thend of the message Reserved - Set to zero Buffer overflow - The message was too long for the receive buffer of the define Reserved - Set to zero
Change the display format to Hexadecimal to interpret communication status.
190
Response Codes
If the leftmost bit of ResponseCode is 0 (value 0127), then there was no communication error and the value is a Response Code from the HART Field Device. Response codes indicate if the device performed the command. 0 means no error. Other values are errors or warnings. To understand the Response Code, contact your HART field device manufacturer or the HART specification. See the table following that shows a few typical and popular response codes.
Response Code Meaning (decimal) Bit 7 = 0: Command Errors Bit 60 (not bit-mapped) 0 1 3 4 5 6 7 8 9 10 11 12 13 14 16 32 64 No command specific error (undefined) Value too large Value too small Not enough bytes in command Transmitter-specific command error In Write-protect mode Update Failed - Update In Progress - Set to Nearest Possible Value Applied Process Too High - Lower Range Value Too High - Not In Fixed Current Mode Applied Process Too Low - Lower Range Value Too Low - MultiDrop Not Supported In MultiDrop Mode - Invalid Transmitter Variable Code - Upper Range Value Too High Invalid Unit Code - Upper Range Value Too Low Both Range Values Out of Limits Pushed Upper Range Value Over Limit - Span Too Small Access restricted Device busy Command not implemented
If no error was detected in the outgoing communication, the second byte contains status information pertaining to the operational state of the field or slave device.
191
Field Device Status Bit Mask Definitions Bit 7 6 5 4 3 2 1 0 Bit Mask 16#80 16#40 16#20 16#10 16#08 16#04 16#02 16#01 Definition Device malfunction - The device detected a serious error or failure that compromises device operation Configuration changed - An operation was performed that changed the devices configuration Cold start - A power failure or device reset occured More status available - More status information is available via command 48, Read Additional Status Information Loop current fixed - The loop current is being held at a fixed value and is not responsding to process variations Loop current saturated - The loop current has reached its upper or lower endpoint limit and cannot increas or decrease any further Non-primary variable out of limits - A device variable not mapped to the PV is beyond its operating limits Primary variable out of limits - The PV is beyond its operating limit
HART Universal Commands(1) Command

No. Function
Data in Command
Byte Data Type
Data in Reply
Byte Data Type
Contained in
Input CIP Tag MSG
Read Unique Identified
None
0 1 2 3 4 5 6 7 8 911 0 14
254 (expansion) Manufacturer identification code Manufacturer device type code Number of preambles required Universal command revision Device-specific command revision Software revision Hardware revision Device function flags(2) Device ID number PV units code Primary variable Current (mA) Primary variable % Current (mA) PV units code Primary variable SV units code Secondary variable TV units code Third variable FV units code Fourth variable(3)
(H) (B) (F) (F) (F) x x x
x x x x x x x x x x x x x x x x x x x x x x x
1 2
Read primary variable Read current and percent of range Read current and four (predefined) dynamic variables None
03 47 03 4 58 9 1013 14 1518 19 2023
None
x x x x
192
HART Universal Commands(1) Command

No. Function
Data in Command
Byte Data Type
Data in Reply
Byte Data Type
Contained in
Input CIP Tag MSG
6 11
Write polling address Read unique identifier associated with tag Read message Read tag, descriptor, date Read PV sensor information
0 05
Polling address Tag (A) 011
As in command
12 13
None
023 05 617 1820 02 3 47 811 1215 0 1 2 36 710 1114 15 16
Message (32 characters) Tag (8 characters) Descriptor (16 characters) Date Sensor serial number Units code for sensor limits and min span Upper sensor limit Lower sensor limit Min span Alarm select code Transfer function code PV/range units code Upper range value Lower range value Damping value (s) Write-protect code Private-label distributor code Final assembly number
(A) (A) (A) (D) (B) (F) (F) (F)
x x x x
14
15
Read output information
(F) (F) (F) (B)
x x x x x x x
16
Read final assembly number Write message Write tag, descriptor, date 023 05 617 1820
None
02
17 18
Message (32 characters) Tag (8 characters) Descriptor (16 characters) Date Final assembly number
(A) (A) (A) (D) (B)
As in command
19
Write final assembly number
02
(1) (2) (3)
(A) = Packed ASCII, (B) = 3-byte integer, (D) = Date, (F) = Floating Point (HART format), (H) = HART flag. Bit 6 = multisensor device. Bit 1 = EEPROM control required. Bit 2 = protocol bridge device. Truncated after last supported variable.
193
Common Practice Commands(1) Command

No. Function
Data in Command
Byte Data Type
Data in Reply
Byte Data Type
Contained in Input Tag CIP MSG
33
Read transmitter variables
None
0 1 25 6 7 811 12 13 1417 18 19 2023 (F)
Transmitter variable code for slot 0 Units code for slot 0 Variable for slot 0 Transmitter variable code for slot 1 Units code for slot 1 Variable for slot 1 Transmitter variable code for slot 2 Units code for slot 2 Variable for slot 2 Transmitter variable code for slot 3 Units code for slot 3 Variable for slot 3(7) As in command
(F) (F) (F) (F)
34
Write damping value Write range values Set upper-rang e value (= push SPAN button) Set lower-rang e value (= push ZERO button) Reset "configurat ion changed" flag EEPROM control Enter/exit Fixed Current mode
03
Damping value (s)
35
0 14 58
Range units code Upper-range value (F) Lower-range (F) value None None
(F) (F)
36
37
38
39 40
EEPROM control code(4) (F)
As in command As in command
03(2) Current (mA)
194

No. Function
Data in Command
Byte Data Type
Data in Reply
Byte Data Type
41
Perform device self-test Perform master reset Set (trim) PV zero Write PV units Trim DAC zero Trim DAC gain Write transfer function Read additional device status Write PV sensor serial number Read dynamic variable assignmen ts 02 0 03 03 0
None
None
42
43 44 45 46 47
PV units code Measured current (mA) (F) Transfer function code None 05 67 810 1113 1424
As in command
48
Device-specific status Operational modes Analog outputs saturated(8) Analog outputs fixed(9) Device-specific status As in command
s(11)
x x x x x
49
Sensor serial number
50
None
0 1 2 3
PV transmitter variable code SV transmitter variable code TV transmitter variable code FV transmitter variable code
x x x x
195

No. Function
Data in Command
Byte Data Type
Data in Reply
Byte Data Type
51
Write dynamic variable assignmen ts
0 1 2 3
PV transmitter variable code SV transmitter variable code TV transmitter variable code FV transmitter variable code Transmitter variable code
As in command
52
0 Set transmitter variable zero Write transmitter variable units Read transmitter variable informatio n
53
Transmitter variable code
54
Transmitter variable code
0 13 4 58 912 1316
Transmitter variable code Transmitter variable sensor serial Transmitter variable limits units code (F) Transmitter variable upper limit (F) Transmitter variable lower limit (F) Transmitter variable damping value (s) As in command
55
0 Write transmitter 14 variable damping value 0 Write transmitter 13 variable sensor serial number Read unit tag, description , date Write unit tag, descriptor, date Write number of response preambles 05
Transmitter variable code Transmitter variable damping value (s) Transmitter variable code Transmitter variable sensor
56
As in command
57
None
05 617 1820
(A) (A) (D)
x x x x
58
(A) Unit tag (8 characters) 617 Unit descriptor (16 (A) (D) 1820 characters) Unit date 0 Number of response preambles
59
196

No. Function
Data in Command
Byte Data Type
Data in Reply
Byte Data Type
60
Read analog output and percent of range Read dynamic variables and PV analog output
Analog output number code
0 1 25 69 0 14 5 69 10 1114 15 1619 20 2124 0 1 25 6 7 81 1 12 13 14 17 18 19 20 23 0 1 2 3 47 811 1215
Analog output number code Analog output units code Analog output level Analog output percent of range PV analog output units code PV analog output level PV units code Primary variable SV units code Secondary variable TV units Tertiary variable FV units code Fourth variable Slot 0 analog output number code Slot 0 Slot 0 level Slot 1 Slot 1 Slot 1 level Slot 2 Slot 2 Slot 2 level Slot 3 Slot 3 Slot 3 level(10)
61
None
(F) (F) (F) (F) (F) x x x x x x x x x x x x
62
Read analog outputs
0 1 2 3(3)
Analog output number; code for slot 0 Analog output number; code for slot 1 Analog output number; code for slot 2 Analog output number; code for slot 3(5) Analog output number code
(F) (F) (F) (F)
63
Read analog output information
Analog output number code Analog output alarm select code Analog output transfer function code Analog output range units code (F) Analog output upper-range value (F) Analog output lower-range value (F) Analog output additional damping value (s)
197

No. Function
Data in Command
Byte Data Type
Data in Reply
Byte Data Type
64
Write analog output additional damping value Write analog output range value
0 14
Analog output number code Analog output additional damping value (s)
As in command (F)
65
0 1 25 69
Analog output number code Analog output range units code (F) Analog output upper-range value (F) Analog output lower-range value Analog output number code Analog output units code Analog output level(6) Analog output number code Analog output units code Externally measured analog output level Analog output number code Analog output units code Externally measured analog output level Analog output number code Analog output transfer function code Analog output number code 0 1 25 69 Analog output number code Analog output endpoint units code Analog output upper endpoint value Analog output lower endpoint value
66
Enter/exit Fixed Analog Output mode
0 1 26
(F)
67
Trim 0 analog output zero 1 26
(F)
68
Trim 0 analog output gain 1 26
(F)
69
Write analog output transfer function Read analog output endpoint values
0 1
70
198

No. Function
Data in Command
Byte Data Type
Data in Reply
Byte Data Type
107
Write Burst mode transmitter variables (for command 33)
0 1 2 3
Transmitter variable code for slot 0 Transmitter variable code for slot 1 Transmitter variable code for slot 2 Transmitter variable code for slot 3 Burst mode command number
As in command
108
Write Burst 0 mode command number Burst mode 0 control Read all dynamic variables
As in command
109
Burst mode control code (0 = exit, 1 = enter) None 0 14 5 69 10 1114 15 1619 PV units code PV value SV units code SV value TV units code TV value FV units code FV value (F) (F) (F) (F) x x x x x x x x x x x x
110
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(A) = Packed ASCII, (B) = 3-byte integer, (D) = Date, (F) = Floating Point (HART format), (H) = HART flag. 0 = exit Fixed Current mode. Truncated after last requested code. 0 = burn EEPROM, 1 = copy EEPROM to RAM. Truncated after last requested code. Not a number exits Fixed-output mode. Truncated after last requested code. Truncated after last requested variable. 24 bits each LSBMSB refers to A0 #124. 24 bits each LSBMSB refers to A0 #124. Truncated after last requested level. Sint []
Appendix
Company Identification Codes
What This Appendix Contains Identification Code Details
This appendix provides details about company identification codes, as described in the chapter on configurating and using HART.
See the table that shows company identification code details.

Company Identification Codes Decimal 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Hex 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 Company Name Acromag Allen-Bradley Ametek Analog Devices Elsag Bailey Beckman Bell Microsenser Bourns Bristol Babcock Brooks Instrument Chessell Combustion Engineering Daniel Industries Delta Dieterich Standard Dohrmann Endress+Hauser Elsag Bailey Fisher Controls Foxboro Fuji ABB Automation Honeywell ITT Barton Kay Ray/Sensall
199
200
Company Identification Codes Decimal 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 Hex 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D Company Name ABB Automation Leeds & Northup Leslie M-System Co. Measurex Micro Motion Moore Industries Moore Products Ohkura Electric Paine Rochester Instrument Systems Ronan Rosemount Peek Measurement Schlumberger Sensall Siemens Weed Toshiba Transmation Rosemount Analytic Meso Automation Flowserve Varec Viatran Delta/Weed Westinghouse Xomox Yamatake Yokogawa Nuovo Pignone Promac Exac Corporation Meggitt Mobrey Arcom Control System Princo
201
Company Identification Codes Decimal 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 Hex 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 58 59 59 5A 5B 5C 5D 5E 5F 60 61 Company Name Smar Foxboro Measurement Technology Applied System Technologies Samson Sparling Instruments Fireye Krohne Betz Druck SOR Elcon Instruments EMCO Termiflex Corporation VAF Instruments Westlock Controls Drexelbrook Saab Tank Control K-TEK Flowdata Draeger Raytek Siemens Milltronics PI BTG Magnetrol Metso Automation Milltronics HELIOS Anderson Instrument Company INOR ROBERTSHAW PEPPERL+FUCHS ACCUTECH Flow Measurement KAMSTRUP Knick
202
Company Identification Codes Decimal 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 Hex 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85 Company Name VEGA MTS Systems Corp. Oval Masoneilan-Dresser BESTA Ohmart Harold Beck and Sons rittmeyer instrumentation Rossel Messtechnik WIKA Bopp & Reuther Heinrichs PR Electronics Jordan Controls Valcom s.r.l. US ELECTRIC MOTORS Apparatebau Hundsbach Dynisco Spriano Direct Measurement Klay Instruments Action Instruments MMG Automatiky DTR Buerkert Fluid Control Systems AALIANT Process Mgt PONDUS INSTRUMENTS ZAP S.A. Ostrow Wielkopolski GLI Fisher-Rosemount Performance Technologies Paper Machine Components LABOM Danfoss Turbo TOKYO KEISO SMC Status Instruments Huakong
203
Company Identification Codes Decimal 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 250 Hex 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 FA Company Name Duon System Vortek Instruments, LLC AG Crosby Action Instruments Keystone Controls Thermo Electronic Co. ISE-Magtech Rueger Mettler-Toledo Det-Tronics TN Technologies DeZURIK Phase Dynamics WELLTECH SHANGHAI ENRAF 4tech ASA Brandt Instruments Nivelco Camille Bauer Metran Milton Roy Co. PMV Turck Panametrics Stahl Analytical Technologies Inc. Fieldbus International BERTHOLD InterCorr China BRICONTE Co Ltd Electron Machine Sierra Instruments Fluid Components Intl Not used
204
Company Identification Codes Decimal 251 252 253 Hex FB FC FD Company Name None Unknown Special
Appendix
Engineering Unit Code Numbers
This appendix provides a table that maps engineering unit code numbers to their meaning and abbreviations. These codes are used in the process variable range display.
Code Number Details

Engineering Unit Code Number Mapping Unit Codes 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
See the table that maps engineering unit code numbers to their meaning and abbreviations.
Resource Identification PRESSURE_ID_1 PRESSURE_ID_2 PRESSURE_ID_3 PRESSURE_ID_4 PRESSURE_ID_5 PRESSURE_ID_6 PRESSURE_ID_7 PRESSURE_ID_8 PRESSURE_ID_9 PRESSURE_ID_10 PRESSURE_ID_11 PRESSURE_ID_12 PRESSURE_ID_13 PRESSURE_ID_14 VOLUMETRIC_FLOW_ID_15 VOLUMETRIC_FLOW_ID_16 VOLUMETRIC_FLOW_ID_17 VOLUMETRIC_FLOW_ID_18 VOLUMETRIC_FLOW_ID_19 VELOCITY_ID_20 VELOCITY_ID_21 VOLUMETRIC_FLOW_ID_22 VOLUMETRIC_FLOW_ID_23 VOLUMETRIC_FLOW_ID_24
Description from HART Specification inches of water at 68 degrees F inches of mercury at 0 degrees C feet of water at 68 degrees F millimeters of water at 68 degrees F millimeters of mercury at 0 degrees C pounds per square inch bars millibars grams per square centimeter kilograms per square centimeter pascals kilopascals torr atmospheres cubic feet per minute gallons per minute liters per minute imperial gallons per minute cubic meter per hour feet per second meters per second gallons per second million gallons per day liters per second
Abbreviated Units inH2O (68 F) inHg (0 C) ftH2O (68 F) mmH2O (68 F) mmHg (0 C) psi bar mbar g/square cm kg/square cm Pa kPa torr atm cubic ft/min usg/min L/min impgal/min cubic m/h ft/s m/s usg/s million usg/d L/s
205
206
Engineering Unit Code Number Mapping Unit Codes 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Resource Identification VOLUMETRIC_FLOW_ID_25 VOLUMETRIC_FLOW_ID_26 VOLUMETRIC_FLOW_ID_27 VOLUMETRIC_FLOW_ID_28 VOLUMETRIC_FLOW_ID_29 VOLUMETRIC_FLOW_ID_30 VOLUMETRIC_FLOW_ID_31 TEMPERATURE_ID_32 TEMPERATURE_ID_33 TEMPERATURE_ID_34 TEMPERATURE_ID_35 ELECTRICAL_ID_36 ELECTRICAL_ID_37 MISCELLANEOUS_ID_38 ELECTRICAL_ID_39 VOLUME_ID_40 VOLUME_ID_41 VOLUME_ID_42 VOLUME_ID_43 LENGTH_ID_44 LENGTH_ID_45 VOLUME_ID_46 LENGTH_ID_47 LENGTH_ID_48 LENGTH_ID_49 TIME_ID_50 TIME_ID_51 TIME_ID_52 TIME_ID_53 VISCOSITY_ID_54 VISCOSITY_ID_55 MISCELLANEOUS_ID_56 MISCELLANEOUS_ID_57 ELECTRICAL_ID_58 MISCELLANEOUS_ID_59 MASS_ID_60 Description from HART Specification million liters per day cubic feet per second cubic feet per day cubic meters per second cubic meters per day imperial gallons per hour imperial gallons per day Degrees Celsius Degrees Fahrenheit Degrees Rankine Kelvin millivolts ohms hertz milliamperes gallons liters imperial gallons cubic meters feet meters barrels inches centimeters millimeters minutes seconds hours days centistokes centipoise microsiemens percent volts pH grams Abbreviated Units ML/day cubic ft/s cubic ft/d cubic m/s cubic m/d impgal/h impgal/d C F R K mV ohm hz mA usg L impgal cubic m ft m bbl in cm mm min s h d centistokes cP microsiemens % V pH g
207
Engineering Unit Code Number Mapping Unit Codes 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 Resource Identification MASS_ID_61 MASS_ID_62 MASS_ID_63 MASS_ID_64 MASS_ID_65 MISCELLANEOUS_ID_66 MISCELLANEOUS_ID_67 MISCELLANEOUS_ID_68 ENERGY_ID_69 MASS_FLOW_ID_70 MASS_FLOW_ID_71 MASS_FLOW_ID_72 MASS_FLOW_ID_73 MASS_FLOW_ID_74 MASS_FLOW_ID_75 MASS_FLOW_ID_76 MASS_FLOW_ID_77 MASS_FLOW_ID_78 MASS_FLOW_ID_79 MASS_FLOW_ID_80 MASS_FLOW_ID_81 MASS_FLOW_ID_82 MASS_FLOW_ID_83 MASS_FLOW_ID_84 MASS_FLOW_ID_85 MASS_FLOW_ID_86 MASS_FLOW_ID_87 MASS_FLOW_ID_88 ENERGY_ID_89 MASS_PER_VOLUME_ID_90 MASS_PER_VOLUME_ID_91 MASS_PER_VOLUME_ID_92 MASS_PER_VOLUME_ID_93 MASS_PER_VOLUME_ID_94 MASS_PER_VOLUME_ID_95 MASS_PER_VOLUME_ID_96 Description from HART Specification kilograms metric tons pounds short tons long tons milli siemens per centimeter micro siemens per centimeter newton newton meter grams per second grams per minute grams per hour kilograms per second kilograms per minute kilograms per hour kilograms per day metric tons per minute metric tons per hour metric tons per day pounds per second pounds per minute pounds per hour pounds per day short tons per minute short tons per hour short tons per day long tons per hour long tons per day deka therm specific gravity units grams per cubic centimeter kilograms per cubic meter pounds per gallon pounds per cubic feet grams per milliliter kilograms per liter Abbreviated Units kg t lb short ton long ton millisiemens/cm microsiemens/cm N Nm g/s g/min g/h kg/s kg/min kg/h kg/d t/min t/h t/d lb/s lb/min lb/h lb/d short ton/min short ton/h short ton/d long ton/h long ton/d Dth specific gravity units g/cubic cm kg/cubic m lb/usg lb/cubic ft g/mL kg/L
208
Engineering Unit Code Number Mapping Unit Codes 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 Resource Identification MASS_PER_VOLUME_ID_97 MASS_PER_VOLUME_ID_98 MASS_PER_VOLUME_ID_99 MASS_PER_VOLUME_ID_100 MISCELLANEOUS_ID_101 MASS_PER_VOLUME_ID_102 MASS_PER_VOLUME_ID_103 MASS_PER_VOLUME_ID_104 MISCELLANEOUS_ID_105 MISCELLANEOUS_ID_106 MISCELLANEOUS_ID_107 MISCELLANEOUS_ID_108 MISCELLANEOUS_ID_109 VOLUME_ID_110 VOLUME_ID_111 VOLUME_ID_112 VOLUME_ID_113 VELOCITY_ID_114 VELOCITY_ID_115 VELOCITY_ID_116 RADIAL_VELOCITY_ID_117 RADIAL_VELOCITY_ID_118 RADIAL_VELOCITY_ID_119 VELOCITY_ID_120 VOLUMETRIC_FLOW_ID_121 VOLUMETRIC_FLOW_ID_122 VOLUMETRIC_FLOW_ID_123 VOLUME_ID_124 MASS_ID_125 ENERGY_ID_126 POWER_ID_127 ENERGY_ID_128 POWER_ID_129 VOLUMETRIC_FLOW_ID_130 VOLUMETRIC_FLOW_ID_131 VOLUMETRIC_FLOW_ID_132 Description from HART Specification grams per liter pounds per cubic inch short tons per cubic yard degrees twaddell degrees brix degrees baume heavy degrees baume light degrees API percent solids per weight percent solids per volume degrees balling proof per volume proof per mass bushels cubic yards cubic feet cubic inches inches per second inches per minute feet per minute degrees per second revolutions per second revolutions per minute meters per hour normal cubic meter per hour normal liter per hour standard cubic feet per minute bbl liq ounce foot pound force kilo watt kilo watt hour horsepower cubic feet per hour cubic meters per minute barrels per second Abbreviated Units g/L lb/cubic in short ton/cubic yd Tw Bx BH BL API % solid/weight % solid/volume degrees balling proof/volume proof/mass bushel cubic yd cubic ft cubic in in/s in/min ft/min /s rev/s rpm m/hr normal cubic m/h normal L/h standard cubic ft/min bbl liq oz ft lb force kW kW h hp cubic ft/h cubic m/min bbl/s
209
Engineering Unit Code Number Mapping Unit Codes 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 235 236 Resource Identification VOLUMETRIC_FLOW_ID_133 VOLUMETRIC_FLOW_ID_134 VOLUMETRIC_FLOW_ID_135 VOLUMETRIC_FLOW_ID_136 VOLUMETRIC_FLOW_ID_137 VOLUMETRIC_FLOW_ID_138 MISCELLANEOUS_ID_139 POWER_ID_140 POWER_ID_141 POWER_ID_142 MISCELLANEOUS_ID_143 MISCELLANEOUS_ID_144 PRESSURE_ID_145 MASS_PER_VOLUME_ID_146 MASS_PER_VOLUME_ID_147 MISCELLANEOUS_ID_148 MISCELLANEOUS_ID_149 MISCELLANEOUS_ID_150 MISCELLANEOUS_ID_151 MISCELLANEOUS_ID_152 MISCELLANEOUS_ID_153 MISCELLANEOUS_ID_154 MISCELLANEOUS_ID_155 MISCELLANEOUS_ID_160 MISCELLANEOUS_ID_161 ENERGY_ID_162 ELECTRICAL_ID_163 ENERGY_ID_164 ENERGY_ID_165 VOLUME_ID_166 VOLUME_ID_167 VOLUME_ID_168 MISCELLANEOUS_ID_169 VOLUMETRIC_FLOW_ID_235 VOLUME_ID_236 Description from HART Specification barrels per minute barrels per hour barrels per day gallons per hour imperial gallons per second liters per hour parts per million mega calorie per hour mega joule per hour british thermal unit per hour degrees radian inches of water at 60 degrees F micrograms per liter micrograms per cubic meter percent consistency volume percent percent steam quality feet in sixteenths cubic feet per pound picofarads mililiters per liter microliters per liter percent plato percent lower explosion level mega calorie Kohms mega joule british thermal unit normal cubic meter normal liter standard cubic feet parts per billion gallons per day hectoliters Abbreviated Units bbl/min bbl/h bbl/d usg/h impgal/s L/h ppm Mcal/h MJ/h BTU/h degrees rad inH2O (60 F) micrograms/L micrograms/cubic m % consistency volume % % steam quality ft in sixteenths cubic ft/lb pF mL/L microliters/L % plato % lower explosion level Mcal kohm MJ BTU normal cubic m normal L normal cubic ft parts/billion usg/d hL
210
Engineering Unit Code Number Mapping Unit Codes 237 238 239 Resource Identification PRESSURE_ID_237 PRESSURE_ID_238 PRESSURE_ID_239 Description from HART Specification megapascals inches of water at 4 degrees C millimeters of water at 4 degrees C Abbreviated Units MPa inH2O (4 C) mmH2O (4 C)
Index
A
agency certifications 13, 40 alarm deadband 52 alarms latching 41
H
HART additional protocol information 187 configuring 97 definition 11 getting data over CIP MSG 109 using 97 help 69
B
backplane connector 18
C
CE certification 13, 40 company identification codes 199 configuring the modules 69 connections 10 as related to module ownership 21 direct connections 10, 23 listen-only connections 11, 32 ControlNet network 22, 27-28, 30-31 coordinated system time (CST) 10, 13 rolling timestamp 39 timestamping 39 CSA certification 13, 40 C-Tick certification 13, 40
I
inhibiting the module 11 in RSLogix 5000 41 input circuit diagram 1756-IF8H voltage 56 interface module 17
K
keying electronic 37
L
ladder logic message configuration 136 message instructions 133, 135 unlatching alarms in the 1756-IF6I module 139-140 unlatching alarms in the 1756-OF6VI module 141-142 latching alarms 41 listen-only connections 11, 32
D
data echo 62 data format 13, 41 data tags 1756-IF8H modules 158 1756-OF8H modules 172 direct connections 10, 23
M E
EEx certification 13, 40 electronic keying 11, 37 compatible match 10, 38 disable keying 11, 38 exact match 11, 38 electrostatic discharge preventing 20 engineering unit code numbers 205 EtherNet/IP network 22, 28, 31 event tasks 26 major revision 11, 37 mechanical keying 18 minor revision 12, 37 module identification information 19 ASCII text string 19 catalog code 19 major revision 19 minor revision 19 product type 19 serial number 19 status 19 vendor ID 19 WHO service 19 module resolution 13 as related to scaling and data format 43 module status retrieving 19
F
FM certification 13, 40
Index
N
Network Update Time (NUT) for ControlNet network 12, 22
O
online help 69 output data echo 29 ownership 21 changing configuration in multiple owner-controllers 34 multiple owners 12, 32, 34 owner-controller 12
requested packet interval (RPI) 12, 25 retrieving module identification information 19 retrieving module status 19 revision major 11 minor 12 rolling timestamp 13 RSNetworx software adding a new module to a remote ControlNet chassis 22 using with RSLogix 5000 software 22
P
Pass through messages 14, 77, 109, 119, 120, 122, 124, 146, 147 preventing electrostatic discharge 20 producer/consumer model 13, 39 product identification catalog number 37 major revision 37 minor revision 37 product type 37 vendor 37 publications, related 9
S
scaling as related to module resolution and data format 44 status indicators 18, 40
T
tasks event 26 timestamp rolling 13 timestamping 39 triggering event tasks 26 troubleshooting status indicators 18 TUV certification 13, 40
R
real time sample (RTS) in a local chassis 24 in a remote chassis 27 related publications 9 remote chassis connecting via ControlNet network 27-28, 30-31 connecting via EtherNet/IP network 28, 31 removable terminal block (RTB) 17 removal and insertion under power (RIUP) 12, 13, 20, 36
U
UL certification 13, 40
W
who should use this manual 9 wiring using the IFM 17 using the RTB 17
How Are We Doing?

Your comments on our technical publications will help us serve you better in the future. Thank you for taking the time to provide us feedback.You can complete this form and mail (or fax) it back to us or email us at RADocumentComments@ra.rockwell.com
Please complete the sections below. Where applicable, rank the feature (1=needs improvement, 2=satisfactory, and 3=outstanding).
Pub. Title/Type ControlLogix HART Analog I/O Modules Cat. No. Catalog Numbers 1756-IF8H, 1756-OF8H 1 2 3 Pub. No. 1756-UM533A-EN-P Pub. Date March 2007 Part No. 953030-33
Overall Usefulness
How can we make this publication more useful for you?
Completeness (all necessary information is provided)
Can we add more information to help you? procedure/step example explanation illustration guideline definition feature other
Technical Accuracy (all provided information is correct)
Can we be more accurate? text illustration
Clarity 1 (all provided information is easy to understand)
How can we make things clearer?
Other Comments
You can add additional comments on the back of this form.
Your Name Your Title/Function Location/Phone Would you like us to contact you regarding your comments? ___No, there is no need to contact me ___Yes, please call me ___Yes, please email me at _______________________ ___Yes, please contact me via _____________________ Return this form to: Rockwell Automation Technical Communications, 1 Allen-Bradley Dr., Mayfield Hts., OH 44124-9705 Fax: 440-646-3525 Email: RADocumentComments@ra.rockwell.com
Publication CIG-CO521C-EN-P- May 2003
957782-91
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
PLEASE REMOVE
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products. At http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools. For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer TechConnect Support programs. For more information, contact your local distributor or Rockwell Automation representative, or visit http://support.rockwellautomation.com.
Installation Assistance
If you experience a problem with a hardware module 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 module up and running. United States Outside United States 1.440.646.3223 Monday Friday, 8am 5pm EST Please contact your local Rockwell Automation representative for any technical support issues.
New Product Satisfaction Return

Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning, it may need to be returned. United States Contact your distributor. You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process. Please contact your local Rockwell Automation representative for return procedure.
Outside United States
Publication 1756-UM533A-EN-P - March 2007 7
PN 953030-33
Copyright 2007 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

1756 IF8H User Manual

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

1756 IF8H User Manual

Încărcat de

Drepturi de autor:

Formate disponibile

ControlLogix HART Analog I/O Modules

Catalog Numbers 1756-IF8H, 1756-OF8H

Important User Information

Chapter 1 About the Modules

Chapter 2 Understand Module Operation

Publication 1756-UM533A-EN-P - March 2007

Chapter 3 Using Module Features

Chapter 4 About the HART Analog Input Module

Publication 1756-UM533A-EN-P - March 2007

Chapter 5 About the HART Analog Output Module

Chapter 6 Configuring the Modules

Chapter 7 Configuring and Using HART

Publication 1756-UM533A-EN-P - March 2007

. 119 . . . . . . 120 122 122 122 123 124

Chapter 9 Using HART Modules with Asset Management Software

Chapter 10 Unlatching Alarms and Reconfiguring Modules Using Ladder Logic

Chapter 11 Troubleshooting the Modules

Publication 1756-UM533A-EN-P - March 2007

Appendix A Tag Definitions

Appendix B Calibration Information

Appendix D Additional HART Protocol Information

Appendix E Company Identification Codes

Publication 1756-UM533A-EN-P - March 2007

Appendix F Engineering Unit Code Numbers

Publication 1756-UM533A-EN-P - March 2007

What This Preface Contains Who Should Use This Manual

This preface describes how to use this manual.

Purpose of This Manual

Publication 1756-RN636 1756-IN608 1756-IN609 1756-IN080 1756-IN589 1756-IN596 1756-IN078 1756-UM009

Multiple 1756-IN numbers 1756-UM058 CNET-UM001

Publication 1756-UM533A-EN-P - March 2007

Publication 1756-UM533A-EN-P - March 2007

Publication 1756-UM533A-EN-P - March 2007

Publication 1756-UM533A-EN-P - March 2007

About the Modules

What This Chapter Contains

Description of the Modules

Publication 1756-UM533A-EN-P - March 2007

About the Modules

Understanding the Highway Addressable Remote Transducer (HART) Feature

0.5 mA 1200 Hz "1" 2200 Hz "0"

Analog Analog Signal Signal 0 1 2

Publication 1756-UM533A-EN-P - March 2007

About the Modules

Secondary Master (handheld communicator as secondary master)

Publication 1756-UM533A-EN-P - March 2007

About the Modules

Benefits of Integrated HART Networks

Benefits of HART-enabled I/O Modules

Publication 1756-UM533A-EN-P - March 2007

About the Modules

Work with Asset Management Software

Asset Management Software EtherNet/IP Network

Using an I/O Module in the ControlLogix System

Publication 1756-UM533A-EN-P - March 2007

About the Modules

Features of the Modules

ControlLogix I/O Module

Indicators Locking Tab

Removable Terminal Block (RTB)

Top and Bottom Guides

Slots for Keying the RTB

Publication 1756-UM533A-EN-P - March 2007