1756 IF8H User Manual

ControlLogix HART Analog I/O ModulesCatalog 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.

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.

WARNINGIdentifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

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

ATTENTION Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence

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

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

http://literature.rockwellautomation.com

Table of Contents

Preface What This Preface Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 9Who Should Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . 9Purpose of This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 1About the Modules What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . 13

Description of the Modules . . . . . . . . . . . . . . . . . . . . . . . . . 13Understanding the Highway Addressable Remote Transducer (HART) Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Benefits of Integrated HART Networks . . . . . . . . . . . . . . 16Benefits of HART-enabled I/O Modules . . . . . . . . . . . . . 16

Work with Asset Management Software . . . . . . . . . . . . . . . . 17Using an I/O Module in the ControlLogix System . . . . . . . . . 17Features of the Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Using Module Identification and Status Information . . . . . . . 19Preventing Electrostatic Discharge . . . . . . . . . . . . . . . . . . . . 20Removal and Insertion Under Power . . . . . . . . . . . . . . . . . . 20

Chapter 2Understand Module Operation What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . 21

Ownership and Connections . . . . . . . . . . . . . . . . . . . . . . . . 21Using RSNetWorx and RSLogix 5000 Software . . . . . . . . . . . 22Direct Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Input Module Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Input Modules in a Local Chassis . . . . . . . . . . . . . . . . . . . . . 24

Real Time Sample (RTS) . . . . . . . . . . . . . . . . . . . . . . . . . 24Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . . 25Triggering Event Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . 26

Input Modules in a Remote Chassis . . . . . . . . . . . . . . . . . . . 27Remote Input Modules Connected Via ControlNet Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Remote Input Modules Connected Via EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Output Module Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 29Output Modules in a Local Chassis . . . . . . . . . . . . . . . . . . . 29Output Modules in a Remote Chassis . . . . . . . . . . . . . . . . . . 30

Remote Output Modules Connected Via ControlNet Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Remote Output Modules Connected Via EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Listen-only Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Multiple Owners of Input Modules . . . . . . . . . . . . . . . . . . . 32Configuration Changes in an Input Module with Multiple Owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3 Publication 1756-UM533A-EN-P - March 2007

4 Table of Contents

Chapter 3Using Module Features What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . 35

Determining Input Module Compatibility . . . . . . . . . . . . . . . 35Determining Output Module Compatibility . . . . . . . . . . . . . . 35Features Common to Analog I/O Modules . . . . . . . . . . . . . . 35

Removal and Insertion Under Power (RIUP) . . . . . . . . . . 36Module Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . . 36Fully Software Configurable . . . . . . . . . . . . . . . . . . . . . . 36Electronic Keying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Access to System Clock for Timestamping Functions . . . . 39Rolling Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Producer/Consumer Model. . . . . . . . . . . . . . . . . . . . . . . 39Status Indicator Information . . . . . . . . . . . . . . . . . . . . . . 40Full Class I Division 2 Compliance . . . . . . . . . . . . . . . . . 40UL, CSA, FM, CE, C-Tick, EEx, TUV Agency Certification . 40Field Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Sensor Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Latching of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Data Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Module Inhibiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Understanding the Relationship Between Module Resolution and Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Module Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 4About the HART Analog Input Module

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . 47Work with the Differential Wiring Method . . . . . . . . . . . . . . 47Choosing a Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Multiple Input Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . 48Module Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Real Time Sampling (RTS) . . . . . . . . . . . . . . . . . . . . . . . 50Underrange and Overrange Detection. . . . . . . . . . . . . . . 50Digital Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Process Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Rate Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Wire Off Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Wire the Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Using Input Circuit Diagrams. . . . . . . . . . . . . . . . . . . . . . . . 551756-IF8H Module Fault and Status Reporting . . . . . . . . . . . 561756-IF8H Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . 57

1756-IF8H Module Fault Word Bits . . . . . . . . . . . . . . . . . 581756-IF8H Channel Fault Tags . . . . . . . . . . . . . . . . . . . . 58

Publication 1756-UM533A-EN-P - March 2007

Table of Contents 5

Chapter 5About the HART Analog Output Module

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . 59Choosing a Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Features Specific to Analog Output Modules . . . . . . . . . . . . 60

Ramping/Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . 60Hold for Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Open Wire Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Clamping and Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . 61Clamp and Limit Alarms . . . . . . . . . . . . . . . . . . . . . . . . . 62Data Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Wire the Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Using Module Block and Output Circuit Diagrams . . . . . . . . 641756-OF8H Module Fault and Status Reporting. . . . . . . . . . . 65Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Module Fault Word Bits . . . . . . . . . . . . . . . . . . . . . . . . . 67Channel Fault Word Bits . . . . . . . . . . . . . . . . . . . . . . . . 67Channel Status Words Bits . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 6Configuring the Modules What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring Your I/O Module . . . . . . . . . . . . . . . . . . . . . . . 69Create a New Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Work with the General Dialog . . . . . . . . . . . . . . . . . . . . . . . 71Work with the Connection Dialog . . . . . . . . . . . . . . . . . . . . 73Work with the Module Info Dialog . . . . . . . . . . . . . . . . . . . 74Work with HART Analog Input Dialogs . . . . . . . . . . . . . . . . 76

Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Scaling to Engineering Units . . . . . . . . . . . . . . . . . . . . . . 81Alarm Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Work with HART Analog Output Dialogs . . . . . . . . . . . . . . . 86Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Output State Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Limits Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

HART Device Info Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Chapter 7Configuring and Using HART What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . 97

HART Configuration Quick Start . . . . . . . . . . . . . . . . . . . . . 98Pick HART Input Data Format . . . . . . . . . . . . . . . . . . . . 98Enable HART. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99HART Data in the Module Properties on the HART Device Info Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Data in the Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . 104HART Dynamic Variables . . . . . . . . . . . . . . . . . . . . . . . 105How the Module Automatically Collects Data . . . . . . . . 107


6 Table of Contents

Chapter 8Getting HART Data Using CIP MSG What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 109

Using MSG Instructions to Access the HART Object . . . . . . 109CIP Services to Access Common HART Data . . . . . . . . . . . 110

Read Dynamic Variables (Service Code = 16#4B) . . . . . 111Read Additional Status (Service Code = 16#4C) . . . . . . . 113Get Device Information (Service Code = 16#4D) . . . . . . 113

Getting HART Device Information Using CIP Generic MSG: An Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115CIP Services to Pass Through a HART Message to the HART Field Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Understanding the HART Module Scanning Diagram with Pass Through Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 120HART Pass Through CIP Message Layout Details . . . . . . . . 122

Pass Through Init (Service Code= 16#4E) . . . . . . . . . . . 122Pass Through Query (Service Code= 16#4F) . . . . . . . . . 122Flush Queue (Service Code= 16#50) . . . . . . . . . . . . . . . 123

HART Pass Through Message Ladder Logic Example . . . . . 124

Chapter 9Using HART Modules with Asset Management Software

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 129Using HART Modules with Asset Management Systems. . . . 129Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . 130

Chapter 10Unlatching Alarms and Reconfiguring Modules Using Ladder Logic

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 133Using Message Instructions . . . . . . . . . . . . . . . . . . . . . . . . 133

Processing Real-time Control and Module Services . . . . 134One Service Performed Per Instruction . . . . . . . . . . . . . 134

Creating a New Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Enter Message Configuration . . . . . . . . . . . . . . . . . . . . 136Unlatch Alarms in the Input Module . . . . . . . . . . . . . . 139Unlatch Alarms in the Output Module . . . . . . . . . . . . 141Reconfiguring a Module . . . . . . . . . . . . . . . . . . . . . . . 143

Chapter 11Troubleshooting the Modules What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 145

Using Module Indicators to Troubleshoot. . . . . . . . . . . . . . 145General Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . 146Using RSLogix 5000 Software to Troubleshoot Your Module 149Module Configuration Errors . . . . . . . . . . . . . . . . . . . . . . . 150


Table of Contents 7

Appendix ATag Definitions What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . 157

Communications Mode Tag Names and Definitions . . . . 157Module-defined Data Types (1756-IF8H modules) . . . . . . . 158

Understand Use of ResponseCode or Communication Status Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Module-defined Data Types (1756-OF8H) . . . . . . . . . . . . . 172

Appendix BCalibration Information What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . 183

Analog to Digital (A/D) Converter Accuracy . . . . . . . . . . . . 183Calibrated Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Error Calculated Over Hardware Range . . . . . . . . . . . . . . . 184How Operating Temperature Changes Affect Module Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Appendix CUsing 1492 Wiring Systems with Your Analog I/O Module

What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . 185Using a Wiring System . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Appendix DAdditional HART Protocol Information

What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . 187Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Master-slave Operation. . . . . . . . . . . . . . . . . . . . . . . . . 188Multiple Master Operation . . . . . . . . . . . . . . . . . . . . . . 188Transaction Procedure . . . . . . . . . . . . . . . . . . . . . . . . . 188Burst Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Appendix ECompany Identification Codes What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . 199

Identification Code Details. . . . . . . . . . . . . . . . . . . . . . . . . 199


8 Table of Contents

Appendix FEngineering Unit Code Numbers What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . 205

Code Number Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Index


Preface

What This Preface Contains This preface describes how to use this manual.

Who Should 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 Publication Publication

1756-IF8H, 1756-OF8H ControlLogix Analog Modules with HART Protocol Release Notes

1756-RN636

1756-IF8H ControlLogix Analog Input Module with HART Protocol Installation Instructions

1756-IN608

1756-OF8H ControlLogix Analog Output Module with HART Protocol Installation Instructions

1756-IN609

1756-A10, 1756-A13, 1756-A17, 1756-A4, 1756-A7 ControlLogix Chassis Installation Instructions 1756-IN080

1756-PH75 ControlLogix Power Supply Installation Instruction 1756-IN589

1756-PA75/B, 1756-PB75/B ControlLogix Power Supply Installation Instruction 1756-IN596

1756-PA72/C, 1756-PB72/C ControlLogix Power Supply Installation Instructions 1756-IN078

1756-IF16, 1756-IF6CIS, 1756-IF6I, 1756-IF8, 1756-IR6I, 1756-IT6I, 1756-IT6I2, 1756-OF4, 1756-OF6CI, 1756-OF6VI, 1756-OF8

ControlLogix Analog I/O Modules User Manual 1756-UM009

1756-Series ControlLogix Module Installation Instructions(each module has separate installation instructions)

Multiple 1756-IN numbers

1756-Series ControlLogix Digital I/O Modules User Manual 1756-UM058

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

ControlNet Modules in Logix5000 Control Systems CNET-UM001


http://www.literature.rockwellautomation.com

http://www.literature.rockwellautomation.com

10 Preface

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.

1734-ADN, 1734-ADNX, 1734-PDN, 1756-DNB, 1769-SDN, 1784-PCIDS, 1788-CN2DN, 1788-DNBO, 1788-EN2DN, 1794-ADN

DeviceNet Modules in Logix5000 Control Systems User Manual

DNET-UM004

1756-DHRIO ControlLogix Data Highway Plus Communication Interface Module User Manual

1756-UM514

1756-ENET ControlLogix Ethernet Communication Interface Module User Manual

1756-UM051

1756-IF4FXOF2F ControlLogix High Speed Analog I/O Module User Manual

1756-UM005

1756-Lx ControlLogix Selection Guide 1756-SG001

1756-Lx ControlLogix System User Manual 1756-UM001

1756-Lx, 1769-Lx, 1789-Lx, 1794-Lx, PowerFlex 700S Logix5000 Controllers Quick Reference 1756-QR107

1756-Lx, 1769-Lx, 1789-Lx, 1794-Lx, PowerFlex 700S Logix5000 Controllers Common Procedures Programming Manual

1756-PM001

1756-Lx, 1769-Lx, 1789-Lx, 1794-Lx, PowerFlex 700S Logix5000 Controllers Motion Instruction Set Reference Manual

1756-RM007

1756-Lx, 1769-Lx, 1789-Lx, 1794-Lx, PowerFlex 700S Logix5000 Controllers General Instructions Reference Manual

1756-RM003

Catalog Number Publication Publication


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 2…100 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 controller’s 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 1

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 Description

Removal and insertion under power (RIUP)

Use this system feature to remove and insert modules and removable terminal bases while power is applied.

Producer/consumer communication model

These communications are an intelligent data exchange between modules and other system devices in which each module produces data without having been polled.

Rolling timestamp of data 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

Multiple data formats Analog I/O modules offer this option.

Module resolution 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.

On-board features Features such as scaling to engineering units, alarming, and underrange and overrange detection increase the modules’ complexity and effectiveness.

Calibration ControlLogix analog I/O module ships from the factory with factory calibration.

Coordinated system time (CST) timestamp of data

64-bit system clock (CST) places a timestamp on the transfer of data between the module and its owner-controller within the local chassis

UL, CSA, FM, CE, C-Tick, EEx, TUV Agency Certification

Full agency certification in any application that requires approval of the agencies listed.

Agency certification varies depending on catalog number.


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 4…20 mA communication with smart (microprocessor-based) field devices. A digital signal is superimposed onto the 4…20 mA current loop to provide two means of communication from the device. The 4…20 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 4…20 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.

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.

Analog Signal

The Highway Addressable Remote Transducer (HART) protocol supports two-way digital communication, complements traditional 4…20 mA analog signals, and includes the following features:

• Predefined commands- Common practice- General purpose - Device specific

• Large installed base

• Worldwide support

Analog Signal

+0.5 mA

0.5 mA

0

1200 Hz"1"

2200 Hz"0"

HART Signal

Time (s)0 1 2

20 mA

AnalogSignal

4 mA


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.

IMPORTANT These modules do not support HART Burst mode operation or multi-drop wiring architecture.

Primary Master

Secondary Master (handheld communicator as secondary master)

Slave44219



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 4…20 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.



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.

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.

EtherNet/IP Network

Asset Management Software

44220

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

(2) 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.

IMPORTANT Removable terminal bases and interface modules are not included with your module purchase.



Features of the Modules See the figure and table that show the physical features of the ControlLogix analog I/O modules.

Physical Features of ControlLogix I/O Modules

Physical Features of the ControlLogix Analog I/O Modules

Physical Feature Description

Backplane connector The backplane connector interface for the ControlLogix system connects the module to the ControlBus backplane.

Connector pins 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).

Locking tab The locking tab anchors the RTB or IFM cable on the module, maintaining wiring connections.

Slots for keying Mechanically keys the RTB to prevent inadvertently making the wrong wire connections to your module.

Status indicators Indicators display the status of communication, module health, and input and output devices. Use these indicators to help in troubleshooting.

Top and bottom guides Guides provide assistance in seating the RTB or IFM cable onto the module.

40200-M

BackplaneConnector

Topand

BottomGuides

ConnectorPins

Indicators

Slots forKeyingthe RTB

Locking Removable Terminal Block (RTB)

ControlLogix I/O Module

Tab



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 module’s status.

Each module maintains the information as shown in the table.

Module Identification and Status Information

Module Identification Description

Product Type Module’s product type, such as Digital I/O orAnalog I/O module

Catalog Code Module’s catalog number

Major Revision Module’s major revision number

Minor Revision Module’s minor revision number

Status Module’s 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 Module manufacturer vendor, for example Allen-Bradley

Serial Number Module serial number

Length of ASCII Text String Number of characters in module’s text string

ASCII Text String Number of characters in module’s text string

IMPORTANT You must perform a WHO service to retrieve this information.



Preventing Electrostatic Discharge

This module is sensitive to electrostatic discharge.

Removal and Insertion Under Power

These modules are designed to be installed or removed while chassis power is applied.

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.

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

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


Chapter 2

Understand Module Operation

What This Chapter Contains 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 module’s position. The owner sends the I/O module configuration data to define the module’s 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.


22 Understand Module Operation

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 module’s 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.


Understand Module Operation 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 device’s 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 module’s 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 module’s 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.



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.

1

2

On-board Memory

Status Data

Channel Data

Channel Data

Channel Data

Channel Data

Channel Data

Channel Data

Ch 0

Ch 1

Ch 2

Ch 3

Ch 4

Ch 5

Timestamp

41361

IMPORTANT The real time sample value is set during the initial configuration using RSLogix 5000 software. This value can be adjusted anytime.



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

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.

On-board Memory

Status Data

Channel Data

Channel Data

Channel Data

Channel Data

Channel Data

Channel Data

Ch 0

Ch 1

Ch 2

Ch 3

Ch 4

Ch 5

Timestamp

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

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.


100 ms - Updated data

Requested Packet Interval25 ms - Same input data as the previous RTS

25 50 75 100 125 150 175 200 225 250 275 300 325 350 375 400

Time (ms) 40946

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.



Input Modules in a Remote Chassis

If an input module resides in a remote chassis, the role of the requested packet interval and the module’s 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.

The reserved spot on the network and the module’s 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.

ControlNet NetworkInput data at least as often as RPI

Input data in remote chassis at RTS and RPI

Owner-controller ControlNet Bridge Module ControlNet Bridge Module Input Module

Input Module in Remote Chassis with Requested Packet Interval Reserving Spot in Flow of Data

40947



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 module’s 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 module’s 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 module’s 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.



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 controller’s 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 module’s 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.

Data sent from owner

Owner-controller Output Module

40949



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.

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.

ControlNet Network

Output data at least as often as RPI

Immediate backplane transfers to module

Data sent from owner at module’s RPI rate

Owner-controller ControlNet Bridge Module ControlNet Bridge Module Output Module

41360

Output Module in Remote Chassis with Requested Protocol Interval Reserving a Spot in Flow of Data



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.

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 module’s requested protocol interval.

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



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 module’s 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.

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

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.



In the example, Controller A and Controller B have both been configured to be the owner of the input module.

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 controller’s data arrives first establishes a connection.

• When the second controller’s 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.

Input Module Configuration DataXxxxxXxxxxXxxxx


Initial Configuration Initial Configuration

Controller A Controller BInput Module

CTR A CTR B

Multiple Owners with Identical Configuration Data

41056



Configuration Changes in an Input Module with Multiple Owners

You must be careful when changing an input module’s 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 module’s behavior.



Modified Configuration Initial Configuration

Controller A Controller BInput Module

CTR A CTR B

Controller B is unaware that changes were made by Controller A.

Multiple Owners with Changed Configuration Data

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 module’s 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 module’s configuration in a multiple owner scenario while online:

• For each owner-controller, inhibit the controller’s 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 owner’s configuration.


Chapter 3

Using Module Features

What This Chapter Contains 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


36 Using Module Features

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.


Using Module Features 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 module’s function or RSLogix 5000 interface

• Minor Revision - Change that does not affects the module’s 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 controller’s 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.



Keying Options Available with ControlLogix Analog I/O Modules

Keying Option Definition

Exact Match All of the parameters must match or the inserted module rejects a connection to the controller.

Compatible Match

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 configuration’s major.minor revision is less than or equal to the physical module’s 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 module’s 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).



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.


Pu


blication 1756-UM533A-EN-P - March 2007

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.

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.

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.

Status of Status Indicators

Status Display Indicates

Calibration status Module is in Calibration mode

Module status Module communication status

IMPORTANT Modules should not be pulled under power, nor should a powered RTB be removed, when a hazardous environment is present.


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.

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:

ControlLogix HART Analog Modules Multicast in These Formats

Format Type Description

Analog Only(do not get HART data)

Analog signal valuesAnalog alarm status

Analog with HART PV(get HART data)

Analog signal valuesAnalog alarm statusHART secondary process variableDevice health



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

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 module’s 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.

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.



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 13…16 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 0…20 mA mode, your module’s 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

65,536 counts

0 mA 21 mA

21 mA/65,536 counts ~ 0.34 μA/count

IMPORTANT A module’s 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.



See the table that lists the resolution for each module’s 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 module’s 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

Current Values Represented in Engineering Units

Module Range Number of Significant Bits Resolution

1756-IF8H +/- 10.25V0… 10.25V0…5.125V0…20.5 mA3.42…20.58 mA

16 bits 320 μV/count160 μV/count80 μV/count0.32 μA/count

1756-OF8H +/- 10.4V0…21mA3.42…20.58 mA

16 bits15 bits

320 μV/count0.65 μA/count

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.

Module Resolution

65,536 Counts

0 mA 21 mA

4 mA 20 mA

0% in Engineering Units

100% in Engineering Units

Module Scaling

Module scaling represents the data returned from the module to the controller



The module can operate with values beyond the 4…20 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.

IMPORTANT In choosing two points for the low and high value of your application, you do not limit the range of the module. The module’s range and its resolution remain constant regardless of how you scale it for your application.

Current Values Represented in 0…100% Engineering Units

Current Engineering Units Value

3 mA -3.625%

4 mA 0%

12 mA 50%

20 mA 100%

21 mA 103.625%



Notes:


Chapter 4

About the HART Analog Input Module

What This Chapter Contains 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:







• Producer and consumer model


• Full Class 1 Division 2 compliance

• UL, CSA, FM, CE, C-Tick, EEx, and TUV agency certification when the module is marked


• Sensor offset


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.


48 About the HART Analog Input Module

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.

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:

• -10…10V

• 0…5V

• 0…10V

• 0…20 mA

• 4…20 mA (HART instruments use this)

Features Available in Each Data Format

Data Format Features Available

Analog Only Analog signal valuesAnalog alarm status

Analog and HART PV Analog signal valuesAnalog alarm statusHART secondary process variablesDevice health


About the HART Analog Input Module 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.

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.

.707

60 Hz0



Use the table to choose a module filter setting.

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.

Module Filter Selections with Associated Performance Data

Module Filter Setting (-3dB)(1) (2) 10 Hz 50 Hz/ 60 Hz (default) 100 Hz 250 Hz 1000 Hz

Minimum Sample Time (RTS) 244 ms 44 ms 28 ms 14 ms 11 ms

Effective Resolution 16 bits 16 bits 16 bits 14 bits 12 bits

(1) For optimal 50/60 Hz noise rejection (>80 dB), choose the 10 Hz filter.(2) Worst case settling time to 100% of a step change is double the real time sample time.

Low and High Signal Limits on Nonisolated Input Modules

Input Module Available Range Lowest Signal in Range Highest Signal in Range

1756-IF8H -10…10V0…10V0…5V0…20 mA4…20 mA

-10.25V0V0V0 mA3.42 mA

10.25V10.25V5.125V20.58 mA20.58 mA



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.

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

Yn = Yn-1 + (Xn – Yn-1)[Δ t]

Δ t + TA

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

0 0.01 0.5 0.99 Time in s

16723

100%

63%

0

Amplitude

Unfiltered InputTA = 0.01 sTA = 0.5 sTA = 0.99 s



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

43153

High high

Low low

Low

High

Alarm deadbands

High high alarm turns OFFHigh alarm remains ON

High high alarm turns ONHigh alarm remains ON

Normal input range

Low low alarms turns OFFLow alarm remains ON

High alarm turns OFF

Low low alarms turns ONLow alarm remains ON

Low alarms turns OFFLow alarms turns ON

High alarm turns ON



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

These Events Occurs

Voltage • 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



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

RTN

IN4+

IN4-

IN5+

IN5-

RTN

IN6+

IN6-

IN7+

IN7-

IN0+

IN0-

IN1+

IN1-

IN2+

IN2-

IN3+

IN3-

I RTN-0

NC

I RTN-1

NC

I RTN-2

NC

I RTN-3

NC

RTN

I RTN-4

NC

I RTN-5

NC

RTN

I RTN-6

NC

I RTN-7

NC

2

4

6

8

10

12

14

16

18

20

22

24

26

28

30

32

34

36

1

3

5

7

9

11

13

15

17

19

21

23

25

27

29

31

33

35

+V

- V

Voltage Input

44222

Wiring the Module for Voltage Inputs

Channel Terminal Channel Terminal

Channel 0 IN0+, IN0- Channel 4 IN4+, IN4-






Wire the Module for Current Inputs

Using Input Circuit Diagrams

This section shows the 1756-IF8H modules’ input circuit diagrams.

RTN

IN4+

IN4-

IN5+

IN5-

RTN

IN6+

IN6-

IN7+

IN7-

IN0+

IN0-

IN1+

IN1-

IN2+

IN2-

IN3+

IN3-

I RTN-0

NC

I RTN-1

NC

I RTN-2

NC

I RTN-3

NC

RTN

I RTN-4

NC

I RTN-5

NC

RTN

I RTN-6

NC

I RTN-7

NC

2

4

6

8

10

12

14

16

18

20

22

24

26

28

30

32

34

36

1

3

5

7

9

11

13

15

17

19

21

23

25

27

29

31

33

35

2 Wire Current Input2 WireXMTR

+

-24V DCPowerSupply

+

-24V DCPowerSupply

4 Wire Current Input

4 WireXMTR

+ +

- -

+ -

44222

44223

Wire the Module for Current Inputs

Channel Terminal Channel Terminal

Channel 0 IN0+, IN0-, iRTN0 Channel 4 IN4+, IN4-, iRTN4






1756-IF8H Current Input Circuit

1756-IF8H Voltage Input Circuit

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.

0.01 μF

Analog to Digital Converter

22 KΩ

10 MΩ

RTNRTNRTN

RTN

-15 V

Jumper

+

-

0.01 μF

22 KΩ

10 MΩ

249 Ω1/4 Watt

INO+

IRTN-O

INO-

+15 V

Differential Current Input

i

0.01 μF

Analog to Digital Converter

22 KΩ10 MΩ

-15 V

+

- 0.01 μF

22 KΩ10 MΩ

249 Ω1/4 Watt

INO+

I RTN-O

INO-

+15 V

Differential Voltage Inputs

V

+

-

RTNRTNRTN

RTN



See the table that lists tags you can examine in ladder logic to indicate when a fault has occurred.

1756-IF8H Fault Reporting See the table that offers an overview of the fault reporting process for the 1756-IF8H module.

Tags That Can Be Examined in Ladder Logic

Tag Description

Module Fault Word This word provides fault summary reporting. Its tag name is ModuleFaults.

Channel Fault Word This word provides underrange, overrange, and communication fault reporting. Its tag name is ChannelFaults.

Channel Status Word 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.

HART Faults This provides HART communication status. The tag name is HARTFaults or ChxHARTFault..

HART Device Status This provides HART field device health. The tag name is HART.ChxDeviceStatus.

7 6 5 4 3

5 4 3 2 1 0

5 4 3 2 1 07 6

7 = AnalogGroupFault2 = Calibrating1 = Cal Fault6, 5, 4, and 3 arenot used

7 = Ch7Fault6 = Ch6Fault5 = Ch5Fault4 = Ch4Fault3 = Ch3Fault2 = Ch2Fault1 = Ch1Fault0 = Ch0Fault

7 = ChxCalFault6 = ChxUnderrange5 = ChxOverrange4 = ChxRateAlarm 41514

If set, any bit in the Channel Fault word also sets the Analog Group Fault in the Module Fault word.

A channel calibration fault sets the calibration fault in the Module Fault word.

3 = ChxLAlarm2 = ChxHAlarm1 = ChxLLAlarm0 = ChxHHAlarm

An underrange, overrange condition sets appropriate Channel Fault bits.

When the module is calibrating, all bits in the Channel Fault word are set.

2 1

7 6

Alarm bits 0…4 in the Channel Status word do not set additional bits at any higher level. You must monitor these conditions here.

Module Fault

Channel Fault

Channel Status (One for each channel)



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.

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.

Your logic can monitor the Channel Fault Word bit for a particular input to determine the status of that point.


Tag Description

Analog Group Fault This bit is set when any bits in the Channel Fault word are set. Its tag name is AnalogGroupFault.

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

Calibration Fault This bit is set when any of the individual Channel Calibration Fault bits are set. Its tag name is CalFault.

Conditions That Set All Channel Fault Word Bits

This Condition Sets All Channel Fault Word Bits And Causes the Module to Display the Following in the Channel Fault Word Bits

A channel is being calibrated “16#00FF”

A communications fault occurred between the module and its owner-controller “16#FFFF”


Chapter 5

About the HART Analog Output Module

What This Chapter Contains 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:







• Producer and consumer model


• Full Class I Division 2 compliance

• UL, CSA, FM, CE, C-Tick, EEx, TUV agency certification when product is marked


• Sensor offset


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


60 About the HART Analog Output Module

Feature Available in Each Data Format

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.

Data Format Features Available

Analog Only Analog signal valuesAnalog alarm status

Analog and HART PV Analog signal valuesAnalog alarm statusHART secondary process variableDevice health

Ramping Types

Ramping Types Description

Run mode ramping 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.

Ramp-to-program mode 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.

Ramp-to-fault mode 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.


About the HART Analog Output Module 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 0…20 mA or 4…20 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.



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 channel’s 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 module’s 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.



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



Using Module Block and Output Circuit Diagrams

This section shows the module output circuit diagram.

1756-OF8H Output Circuit

0.1 μF

D/AConverter

250 Ω

Amplifier

100 pF5K50 Ω

16K

RTNRTNRTN

RTN

-

+

+18.6V

+

-

2K

24V

24V

I OUT - x

V OUT - #

100 Ω



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.


Tag Description Of What Word Provides

Tag Name

Module Faults Fault summary reporting ModuleFaults

Channel Faults Clamp and and communications fault reporting

ChannelFaults or Chxfault

HART Faults HART communication status HARTFaults or ChxHARTFault

Channel Status Tags Individual channel limit, hold, open wire, ramp status, and calibration faults.

ChxStatus

HART Device Status HART field device health HART.ChxDeviceStatus



1756-OF8HFault Reporting

See the figure that offers an overview of the fault reporting process.

Overview of Fault Reporting Process

Module Faults

Channel Faults

Channel Status Tags

7 6 5 4 3

5 4 3 2 1 0

5 4 3 2 1 07 6

7 = AnalogGroupFault4 = Calibrating3 = CalFault6, 5, 2, 1, and 0 are not used by the 1756-OF8H module.

7 = Ch7Fault6 = Ch6Fault5 = Ch5Fault4 = Ch4Fault3 = Ch3Fault2 = Ch2Fault1 = Ch1Fault0 = Ch0Fault

7 = ChxOpenWire5 = ChxNotANumber4 = ChxCalFault3 = ChxInHold2 = ChxRampAlarm1 = ChxLLimitAlarm0 = ChxHLimitAlarm

41519

Not a Number, Output in Hold, and Ramp Alarm conditions do not set additional bits. You must monitor them here.

6 is not used by 1756-OF8H modules.

If set, any bit in the Channel Fault word, also sets the Analog Group Fault in the Module Fault word.

A channel calibration fault sets the calibration fault in the Module Fault word.

When the module is calibrating, all bits in the Channel Fault word are set.

1756-OF8H modules use 8-Channel Status words.

7 6



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.

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 (0…20 mA or 4…20 mA configurations only). When using the Channel Fault Word, the 1756-OF8H module uses bits 0…7. 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.

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 (0…20 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.

Tags Found in the Module Fault Word

Tag Description Tag Name

Analog Group Fault

This bit is set when any bits in the Channel Fault word are set.

AnalogGroupFault

Calibrating This bit is set when any channel is being calibrated. When this bit is set, all bits in the Channel Fault word are set.

Calibrating

Calibration Fault This bit is set when any of the individual Channel Calibration Fault bits are set.

CalFault

Conditions That Set All Channel Fault Word Bits

This Condition Sets All Channel Fault Word Bits

And Causes the Module to Display the Following in the Channel Fault Word Bits

A channel is being calibrated 00FF

A communications fault occurred between the module and its owner-controller

FFFF



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) Bit Event That Sets This Tag

ChxOpenWire Bit 7 This bit is set only if the configured Output Range is 0…20 or 4…20 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.

ChxNotaNumber Bit 5 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.

ChxCalFault Bit 4 This bit is set when an error occurred when calibrating. This bit also sets the appropriate bit in the Channel Fault word.

ChxInHold Bit 3 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.

ChxRampAlarm Bit 2 This bit is set when the output channel’s 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.

ChxLLimitAlarm Bit 1 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.

ChxHLimitAlarm Bit 0 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.


Chapter 6

Configuring the Modules

What This Chapter Contains 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 software’s 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.


70 Configuring the Modules

1. From the I/O Configuration tree, click the 1756 backplane and New Module to see the Select Module dialog.

2. From the Select Module dialog, click + next to Analog to see a list of analog modules.

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.

Click + next to Analog to see the list of analog modules.

Click Find to see the Find Text dialog.


Configuring the Modules 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.



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



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.0…750.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



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 module’s current operational state.



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

• Coordinated System Time (CST)

• Timer Hardware - Displays if timer’s hardware is OK or faulted.

• Timer Sync’ed - Displays yes if the module’s 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.

Displays If the Physical Module

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



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

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.

WARNING Resetting the module breaks connections and restores output signals to default conditions.



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 the chosen channel.

a. For Channel, click to select a channel to configure parameters for the specified channel 0…7.

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 4…20 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.

Configurable For Each Channel

Apply to All Channels



• 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:

• -10…10V

• 0…5V

• 0…10V

• 0…20mA

• 4…20 mA (required for HART)

e. For Sensor Offset, enter a value from -9,999,999…99,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 0…20100, 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.



a. For Real Time Sample (RTS), click a value of 0…10,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.

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.


100 ms - Updated data

Requested Packet Interval25 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 Low Limit High Limit

10 488 10000

15 328

20 248

50 88

60 88

100 (default) 56

250 28

1000 18



c. For Keep HART Replies for, click a value from 1…255, with a default of 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.

Module Filter Value

Module Filter, Hz C.ModuleFilter

10 0

15 7

20 6

50 1

60 (default) 2

100 3

250 4

1000(1)

(1) Do not choose 1000 with HART enabled.

5

IMPORTANT We do not recommend less than 15.







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.

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.

Signal Engineering

High 20 750

Low 4 -180



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.

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.

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,000…100,000,000. The default value is 100.00.

Scaling High Engineering appears dimmed in Hard Run mode.

Range Low Limit High Limit

-10…10V -10.00 10.00

0…20 mA 0.00 20.00

4…20 mA 4.00 20.00

0…5V 0 5

0…10V 1 10

Range Low Limit High Limit

-10…10V -10.00 10.00

0…20 mA 0.00 20.00

4…20 mA 4.00 20.00

0…5V 0 5

0…10V 0 10



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,000…100,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.



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.



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.



• Values for High Engineering and Low Engineering are the maximum and minimum slider control values and are set from the Configuration dialog.


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

Slider Controls

Use this marker To update this value

HH High High

H High

L Low

LL Low Low




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 0…7 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 4…20 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.

• 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,999…99,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.



• 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 1…255 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:




IMPORTANT We do not recommend use of less than 15 s.



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 0…7 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.



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,999…99,999,999 with a default of 0

• 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,999…99,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 Program Mode

Selecting Configures the Output Channel for the Following When the Controller Transitions from Run to Program Mode

Hold Last State Leave the current output at its last value.

User Defined Value Go to the specific value when the owner controller is switched into Program mode. If you select this, enter a value.

Ramp to User Defined 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.

Output State in Fault Mode

Select To configure the output module to one of these

Hold Last State Leave the output signal at its last value

User Defined Value Go to a specific value if a fault occurs. If you select this button, enter a value.

Ramp to User Defined 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.



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.

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 module’s connection is not inhibited):

• you are online in Program, Remote Program, or Remote Run mode

• this controller is the owner controller

• you changed the module’s 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.

Select To

Leave outputs in Program mode state Leave output signal at the configured Program mode value

Change output to Fault mode state Change output signal at configured Fault mode value if a communication fails (connection from controller breaks)



• 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 0…7 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.



• 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,999…99,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,999…99,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



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.

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,9999…999,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 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 do not click Ok or Apply, your changes are not sent to the controller.

Slider Controls

Use this marker To update this value

HI High clamp

LO Low clamp



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 7

Configuring and Using HART

What This Chapter Contains 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

Enable HART Checkbox on Configuration Dialog

HART Data Input Tag of Logix Controller

Pass Through Message Access for MSG or Asset Management

Analog only No check No No

Checked Yes

Analog and HART PV No check Fields present in tag, but data for this channel not valid

No

Checked Yes Yes


98 Configuring and Using HART

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.

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.

For Input Data, click Analog and HART PV.


Configuring and Using HART 99

Enable HART

From the Module Properties Configuration dialog, use these procedures.

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 4…20 mA - HART devices use only 4…20 mA analog signaling range.

• Module Filter - Since the digital HART communication signals are in the 1200…2400 Hz range, the module filter can not be set to 1000 Hz if HART is enabled.

Check the Enable HART checkbox.



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

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.

Pass Through Setting, Ratio, and Priority

Setting Scan:Pass through ratio Gives priority to

Once per channel scan 1:1 Asset management

Once per two channels scanned 1:2 Default setting

Once per module scan 1:8 Input Tag scan



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.



If HART is enabled, but the HART Field Device is not responding, you see an error display like that in the dialog.

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.

If HART device is not responding, you see this.



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



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



• 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



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.

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.

Device Family Specific Status

More Device Variable Status AvailableLimit Status 11 Constant 01 Low Limited 10 High Limited 00 Not Limited

Process Data Status 11 Good 01 Poor Accuracy 10 Manual/Fixed 00 Bad



With eight channels are in use, the HART update rate is in the 10 s range.

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.

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.



Yes

Update Input

Device in Scan List?

Send Command 3 or 9 to Read Dynamic Process

Reply?

Read Configuration Information, Such as Tag, Units, Range

Put Device in Scan

Send Command 0 Read Unique Identifier

New Configuration Indicated?

Remove Device from Scan List

Read Configuration Information, Such As Tag, Units, Range

Signal Configuration Changed in Input

Go To First Channel

Next Channel

Last Channel?

No

Signal Configuration Changed in Input TagYes

Reply?

Yes

No

Yes

Process 1 Pass through Message

No

No

No

Yes


Chapter 8

Getting HART Data Using CIP MSG

What This Chapter Contains 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.


110 Getting HART Data Using CIP MSG

See the table that shows channel and instance correspondence.

See the tables that show service codes for CIP services.

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.

Channel and Instance

Channel Instance

0 1

1 2

2 3

3 4

4 5

5 6

6 7

7 8

Service Codes for CIP Services Cached on the Module by the HART Object

Class Service Code Function

16#35D 16#4B Read Dynamic Variables

16#4C Read Additional Status

16#4D Get HART Device Information

Service Codes for CIP Services for Pass Through Messages to HART Field Devices

Class Service Code Pass Through Messages

16#35D 16#4E Init

16#4F Query

16#50 Flush Queue


Getting HART Data Using CIP MSG 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.

The 1756-IF8H or 1756-OF8H module responds with the reply message in this table if there is a failure.

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.

HART Read Dynamic Variables - MSG Source-element Structure

Offset Field Data Type Definition

No requested data

Request size = 0 bytes

HART Read Dynamic Variables - MSG Destination Structure


0 Status USINT Command status

1 Pad Pad byte

Reply size = 2 bytes

Request Failed



HART Read Dynamic Variables - MSG Destination Structure



1 HARTCommandStatus HART Device reply Status Byte # 1 (response code)

2 HARTFieldDeviceStatus HART Device reply Status Byte # 2

3 HARTExtDevice Status Status Byte returned from Cmd 9 or 0 for 5.x rev HART devices

4…7 PV REAL HART Primary variable

8…11 SV HART Secondary variable

12…15 TV HART Third variable

16…19 FV HART Fourth variable

20 PV Units USINT Primary variable unit code

21 SV Units Secondary variable unit code

22 TV Units Third variable unit code

23 FV Units Fourth variable unit code

24 PV Assignment Code Primary variable assignment code

25 SV Assignment Code Secondary variable assignment code

26 TV Assignment Code Third variable assignment code

27 FV Assignment Code Fourth variable assignment code

28 PV Status 1 byte status from Cmd 9(Rev 6.x) or if Rev 5.x device:0xC0 = Connected0x00 = Not Connected

29 SV Status 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

30 TV Status 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

31 FV Status 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

32…35 Loop Current REAL Device reported digital loop current value. (Value from Cmd 3 for Rev 5.x devices or Cmd 2 if Rev 6.x device)

Reply Size = 36 bytes



Read Additional Status (Service Code = 16#4C)

See the tables that show read additional status.

The 1756-IF8H or 1756-OF8H module responds with the reply in this table if there is an error.

The 1756-IF8H or 1756-OF8H module respond with the message in the table.

Get Device Information (Service Code = 16#4D)

See the tables for Get Device Information details.

HART Read Additional Status - MSG Source Element Structure


No requested data


HART Read Additional Status - MSG Destination Structure



1 Pad Pad byte


Request Failed

HART Read Additional Status - MSG Destination Structure

Offset Offset Data Type Definition


1 Count Number of Ext Status bytes available

2…26 Ext Status Bytes Extended Status bytes returned by CMD48

Reply Size = 2…28 bytes (pad byte may be attached to end since data is 16 bit aligned)

HART Get Device Information - MSG Source Element Structure - Get Currently Cached Device Information For Given Channel)


No requested data




The 1756-IF8H or 1756-OF8H module responds with the reply in this table if there is an error.

The 1756-IF8H or 1756-OF8H modules respond as shown in the table if successful.

HART Get Device Information - MSG Destination Structure



1 Pad Pad byte



Offset Field Data Type Definition(1)

0 Status SINT Command status

1 Manufacturer CMD#0, Byte 1

2 Device Type CMD#0, Byte 2

3 Preamble CMD#0, Byte 3

4 Universal Command Code CMD#0, Byte 4

5 Transducer Spec Code CMD#0, Byte 5

6 Software Revision CMD#0, Byte 6

7 Hardware Revision CMD#0, Byte 7

8 Flags CMD#0, Byte 8

9 Pad_1 for 32 bit alignment



12…14 HARTDeviceIDNumber DINT CMD#0, Bytes 9…11


16…27 Tag HARTTag CMD#13, Bytes 0…5

28…47 Descriptor HARTDescriptor CMD#13, Bytes 6…17

48 DateDay SINT CMD#13, Byte 18

49 DateMonth CMD#13, Byte 19

50…51 DateYear INT CMD#13, Byte 20 (+ 1900)

52…55 FinalAssemblyNumber DINT CMD#16, Bytes 0…2

56…91 Message HARTMsg CMD#12, Bytes 0…23



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.

92 PVCode SINT CMD#50, Bytes 0, 16#ff if not supported

93 SVCode CMD#50, Bytes 1, 16#ff if not supported

94 TVCode CMD#50, Bytes 2, 16#ff if not supported

95 FVCode CMD#50, Bytes 3, 16#ff if not supported

96 PVUnits CMD#3, Byte 4

97 SVUnits CMD#3, Byte 9, 0 if not present

98 TVUnits CMD#3, Byte 14, 0 if not present

99 FVUnits CMD#3, Byte 19, 0 if not present

100 TransferFunction CMD#15, Byte 1

101 RangeUnits CMD#15, Byte 2



104…107 PVLowerRange REAL CMD#15, Bytes 3…6

108…111 PVUpperRange CMD#15, Bytes 7…10

112…115 DampingValue CMD#15, Bytes 11…14

116 WriteProtectCode SINT CMD#15, Byte 15





(1) See Appendix D for related information.


Offset Field Data Type Definition(1)



See the MSG configuration dialog.

This reads the device information for the HART Device on channel 7 and puts the information in DevInfoAnswer.

Get Device Info Service Code

HART Instance 8 for Channel 7

HART Object Class



The Destination tag is as shown in the Controller Tags dialog.



See the figure that shows string types for HARTTag, HARTDescriptor, and HARTMsg.

HARTDescriptor

HARTTag

HARTMsg



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 InitPass Through Query HART Reply Bytes

Handle

Destination

MSG

Source

Source

Handle

Destination

HART Command BytesMSG

Service 16#4F

Service 16#4E

44405



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.



It can be configured for lower priority on the Configuration dialog of module properties.

Yes

Update Input

Device in Scan List?

Send Command 3 or 9 to Read Dynamic Process

Reply?

Read Configuration Information, Such as Tag, Units, Range

Put Device in Scan

Send Command 0 Read Unique Identifier

New Configuration Indicated?

Remove Device from Scan List

Read Configuration Information, Such As Tag, Units, Range

Signal Configuration Changed in Input

Go To First Channel

Next Channel

Last Channel?

No

Signal Configuration Changed in Input TagYes

Reply?

Yes

No

Yes

Process 1 Pass through Message

No

No

No

Yes



HART Pass Through CIP Message Layout Details

See the related tables.

Pass Through Init (Service Code= 16#4E)

See the related table.

The 1756-IF8H or 1756-OF8H module responds as shown in the table.

Pass Through Query (Service Code= 16#4F)


HART Pass Through Init - MSG Source Element Structure


0 HART Command 0…255 (1 byte) HART Command Number(1)

1 HART Data Size 0…255 (1 byte) Number of Data Bytes for Selected HART Command(1)

2…256 HART Data bytes As many bytes as in HART Data Size HART Command Data(1)

Request Size = 2…257 bytes

(1) See Appendix D - Additional HART Protocol Information for related documentation.

HART Pass Through Init - MSG Destination Structure


0 Status32 = Busy (Queues full)33 = Initiate (Pass through success)35 = Dead

Command StatusBusy - try again laterInitiate - command started - send query to get the replyDead - Device not online

1 HART Command 0…255 (1 byte) Echo of HART Command

2 Handle 1…255 (1 byte) Handle Used in Query Operation

3 Queue Space Remaining

(1 byte) Number of Queues Still Available for This Channel


HART Pass Through Query - MSG Source Element Structure


0 Handle 1…255 (1 byte) Handle for Query (from Handle Field above)

Request Size = 1 byte



The 1756-IF8H or 1756-OF8H responds as shown in the table.

Flush Queue (Service Code= 16#50)


The 1756-IF8H or 1756-OF8H module respond as shown in the table.

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.

HART Pass through Query - MSG Destination Structure

Offset Offset Data Type Definition

0 Status 00 = Success34 = Running 35 = Dead

Query StatusIf running, try again later(See MsgReady in Input Tag)

1 HART Command 0…255 (1 byte) Echo of HART Command

2 HART CommStatus (1 byte) HART Reply Status Byte #1 (response code)

3 HART FieldDeviceStatus

(1 byte) HART Reply Status Byte #2

4 Data Size 0…255 (1 byte) Number of Data Bytes in Reply for HART Command

5…257 HART Reply Data … Data Bytes Returned in Data Field of HART Reply to Requested Command

Reply Size = 6…260 bytes

HART Flush Queue - MSG Source Element Structure


No requested data


Set Flush Queue - MSG Destination Structure




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.



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



This the Message Path Browser dialog.

See the query-message configuration dialog.

HARTQuerySrc

HARTCmd9QueryDst



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.




Chapter 9

Using HART Modules with Asset Management Software

What This Chapter Contains 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.


130 Using HART Modules with Asset Management Software

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.


Using HART Modules with Asset Management Software 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 Using HART Modules with Asset Management Software

Notes:


Chapter 10

Unlatching Alarms and Reconfiguring Modules Using Ladder Logic

What This Chapter Contains 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.


134 Unlatching Alarms and Reconfiguring Modules Using Ladder Logic

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 channel’s 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.


Unlatching Alarms and Reconfiguring Modules Using Ladder Logic 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.

4. From the New Tag dialog, fill-in this information:

a. Name the tag.

b. Click Base for Tag Type.

c. Click Message for Data Type.

d. Click Controller for Scope, noting that to create message tags you must use Controller Scope.

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.

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.



Enter Message Configuration

After creating a new tag, you must enter message configuration.

Enter message configuration on the following dialogs:

• Configuration

• Communication

A description of the purpose and set-up of each dialog follows.

Click here to see the message configuration dialogs

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.




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.



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.

Use this Browse button to see a list.

RSLogix 5000 Software, Version 10 and Later



Unlatch Alarms in the Input Module

Example Rungs 0…4 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.

Rung 3 unlatches the low low alarm.

Rung 4 unlatches the rate alarm.

Click the box in each rung to see the configuration and communication information dialog associated with it.




See the Configuration dialog for Rung 0.


See the Communication dialog for Rung 0. This dialog is the same for each rung of this example.

Choose choose a service type and configure the instance.

Instance 1 is for channel 0.

IMPORTANT You must name an I/O module to set the message path under that module’s communication dialog.



Unlatch Alarms in the Output Module

Example Rungs 5…7 show how to unlatch the following alarms.

• High limit alarm - Rung 5

• Low limit alarm - Rung 6

• Ramp alarm - Rung 7


See the Configuration dialog for Rung 5.

Rung 5 unlatches the high limit alarm.

Rung 6 unlatches the low limit alarm.

Rung 7 unlatches the ramp alarm.

Click the box in each rung to see the configuration and communication information dialog associated with it.

Choose a service type and configure the instance.




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 module’s communication dialog.



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.



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 Restriction

High Engineering Value Must not be equal to low engineering value

Low Engineering Value Must not be equal to high engineering value

High-High Alarm Value Must be greater than or equal to high alarm value

High Alarm Value Must be greater than low alarm value

Low Alarm Value Must be less than high alarm value

Low-Low Alarm Value Must be less than or equal to low alarm value

Deadband Must be less than half of high alarm minus low alarm

Analog Output Module Parameters You Can Change Via Ladder Logic

Feature Restriction

High Clamp Value(1)

(1) 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.

Must be greater than low clamp value

Low Clamp Value(1) Must be less than high clamp value


Chapter 11

Troubleshooting the Modules

What This Chapter Contains 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

20962-M

ANALOG INPUT

CAL

OK

ControlLogix Module LED Indicators

LED Display Means Recommended ActionOK Steady Green The inputs are being multicast. None.OK Flashing Green The module has passed internal diagnostics, but is not currently performing connected

communication.None.

OK Flashing Red Previously established communication has timed out. Check controller. OK Steady Red It is likely the module should be replaced See LED blink code.(1)

CAL Flashing Green The module is in calibration mode None.(1) 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.


146 Troubleshooting the Modules

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 4…20 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.

• 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 isn’t 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.

CAL LED Blink Codes and Fault Status

OK LED CAL LED Fault Status Recommended ActionRed Flashing Green Firmware Download in Process Wait for download to complete. Red 3 Blinks Major Nonrecoverable Boot code section has failed the CRC check. Send in module for repair.Red 4 Blinks Major Nonrecoverable Serial Number not programmed. Send in module for repair.Red 5 Blinks Major Nonrecoverable Boot code section has failed the CRC check. Send in module for repair.Red 6 Blinks Major Recoverable Application code section has failed the CRC check. Try reprogramming the

module firmware. If condition persists send module in for repair.Red 9 Blinks Major Nonrecoverable Module has lost its calibration data. Send in module for repair.Red 10 Blinks Major Recoverable Module firmware watchdog timer has timed out. Try resetting module. If

condition persists send module in for repair.

Channel buttons apply to the current dialog.


Troubleshooting the Modules 147

• If you can’t 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 4…20 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 don’t. 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 doesn’t 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.



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



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

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

HART Initializing HART Initializing

Be sure a channel is HART enabled.



See the figure that shows fault notification on the Module Properties dialog.

Module Configuration Errors

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.

Error Codes for 1756-IF8H Modules

Extended Fault Code Channel Description

0x0002 NA INVALID FILTER

0x0003 NA INVALID RTS

0x0004 NA INVALID HART HANDLE TIME

0x0005 0 PROCESS ALARM LATCH NOT DISABLED

0x0006 0 RATE ALARM LATCH NOT DISABLED

0x0007 0 INVALID INPUT RANGE

0x0008 0 DIGITAL FILTER GREATER THAN TWICE THE RTS RATE

0x0009 0 INVALID RATE ALARM

0x000A 0 SIGNAL OUT OF RANGE

0x000B 0 LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL

0x000C 0 CAL BIAS SET TO NAN

0x000D 0 HIGH ENGINEERING EQUAL TO LOW ENGINEERING

0x000E 0 INVALID HART RATE

0x000F 0 INVALID HIGH LOW ALARM

0x0010 0 INVALID LOW LOW ALARM

0x0011 0 INVALID HIGH HIGH ALARM

0x0012 0 INVALID ALARM DB



































0x0039 3 3 INVALID RATE ALARM












































































Error Codes for 1756-OF8H Modules


0x0001 NA INVALID REVISION NUMBER

0x0004 NA INVALID HART HANDLE TIME

0x0005 0 BAD RAMP LATCH

0x0006 0 BAD CLAMP LATCH

0x000A 0 BAD RAMP TO IDLE



0x000B 0 BAD RAMP TO FAULT

0x000C 0 INVALID INPUT RANGE

0x000D 0 BAD MAX RAMP

0x000E 0 BAD FAULT VALUE

0x000F 0 BAD IDLE VALUE

0x0010 0 SIGNAL OUT OF RANGE

0x0011 0 LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL

0x0012 0 CAL BIAS SET TO NAN

0x0013 0 HIGH ENGINEERING EQUAL TO LOW ENGINEERING

0x0014 0 INVALID HART RATE

0x0015 0 BAD CLAMP

0x001B 1 BAD RAMP LATCH

0x001C 1 BAD CLAMP LATCH

0x0020 1 BAD RAMP TO IDLE

0x0021 1 BAD RAMP TO FAULT


0x0023 1 BAD MAX RAMP

0x0024 1 BAD FAULT VALUE

0x0025 1 BAD IDLE VALUE





0x002A 1 INVALID HART RATE

0x002B 1 BAD CLAMP




0x0037 2 BAD RAMP TO FAULTS



0x003A 2 BAD FAULT VALUE

0x003B 2 BAD IDLE VALUE

0x003C 2 SIGNAL OUT OF RANGE

0x003D 2 LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL

0x003E 2 CAL BIAS SET TO NAN





0x003F 2 HIGH ENGINEERING EQUAL TO LOW ENGINEERING


0x0041 2 BAD CLAMP



0x004C 3 BAD RAMP TO IDLE

0x004D 3 BAD RAMP TO FAULT

0x004E 3 INVALID INPUT RANGE

0x004F 3 BAD MAX RAMP








0x005D 4 BAD RAMP LATCH

0x005E 4 BAD CLAMP LATCH









0x006A 4 CAL BIAS SET TO NAN

0x006B 4 HIGH ENGINEERING EQUAL TO LOW ENGINEERING

0x006C 4 INVALID HART RATE

0x006D 4 BAD CLAMP





0x007A 5 INVALID INPUT RANGE

0x007B 5 BAD MAX RAMP





0x007C 5 BAD FAULT VALUE

0x007D 5 BAD IDLE VALUE

0x007E 5 SIGNAL OUT OF RANGE

0x007F 5 LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL




0x0083 5 BAD CLAMP


0x008A 6 BAD CLAMP LATCH

0x008E 6 BAD RAMP TO IDLE

0x008F 6 BAD RAMP TO FAULT




0x0093 6 IBAD DLE VALUE






0x0099 6 BAD CLAMP

0x009F 7 BAD RAMP LATCH

0x00A0 7 BAD CLAMP LATCH

0x00A4 7 BAD RAMP TO IDLE

0x00A5 7 BAD RAMP TO FAULT

0x00A6 7 INVALID INPUT RANGE

0x00A7 7 BAD MAX RAMP

0x00A8 7 BAD FAULT VALUE

0x00A9 7 BAD IDLE VALUE

0x00AA 7 SIGNAL OUT OF RANGE

0x00AB 7 LOW SIGNAL GREATER THAN OR EQUAL TO HIGH SIGNAL

0x00AC 7 CAL BIAS SET TO NAN

0x00AD 7 HIGH ENGINEERING EQUAL TO LOW ENGINEERING

0x00AE 7 INVALID HART RATE

0x00AF 7 BAD CLAMP




Appendix A

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 Tag Main Module Defined Type Subtype Used by Main Type

Analog Only Input AB:1756_IF8H_Analog:I:0 None

Output None None

Configuration AB:1756_IF8H:C:0 AB:1756_IF8H_ChConfig_Struct:C:0

Analog and HART PV Input AB:1756_IF8H_HARTPV:I:0 AB:1756_IF8H_HARTData:I:0AB:1756_IF8H_HARTStatus_Struct:I:0

Output None None

Configuration AB:1756_IF8H:C:0 AB:1756_IF8H_ChConfig_Struct:C:0

1756-OF8H Input Data Choice and Tags

Input Data Choice Tag Main Module Defined Type Subtype Used by Main Type

Analog Only Input AB:1756_OF8H_Analog:I:0 None

Output AB:1756_OF8H:O:0 None

Configuration AB:1756_OF8H:C:0 AB:1756_OF8H_ChConfig_Struct:C:0

Analog and HART PV Input AB:1756_OF8H_HARTPV:I:0 AB:1756_OF8H_HARTData:I:0AB:1756_OF8H_HARTStatus_Struct:I:0

Output AB:1756_OF8H:O:0 None

Configuration AB:1756_OF8H:C:0 AB:1756_OF8H_ChConfig_Struct:C:0


158 Tag Definitions

Module-defined Data Types (1756-IF8H modules)

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

Member Name Type Default Display Style

Description

ChannelFaults INT Binary Contains Ch0Fault through Ch7BrokenWire. See following

Ch0Fault Boolean 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 Boolean ChannelFaults.1







Ch0BrokenWire Boolean ChannelFaults.8








HARTFaults SINT Binary

Ch0HARTFault Boolean 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

Ch1HARTFault Boolean HARTFaults.1








Tag Definitions 159

ModuleFaults SINT Binary

CalFault Boolean ModuleFaults.1 1756-IF8H Module Calibration Failed

Calibrating Boolean ModuleFaults.2 (Bits 3...6 unused) Calibration in progress

AnalogGroupFault Boolean ModuleFaults.7 Indicates a fault has occurred on any channel (any of ChannelFaults)

Ch0Status SINT Binary Indicates various Alarms on the Analog signal. Also sets Ch0Fault. See the individual alarm descriptions for details

Ch0HHAlarm Boolean 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

Ch0LLAlarm Boolean Ch0Status:1Ch0Data < Ch0LLAlarmLimitIf Ch0Config.ProcessAlarmLatch is set, this alarm remains latched until it is unlatched

Ch0HAlarm Boolean Ch0Status:2Ch0Data > Ch0HAlarmLimitIf Ch0Config.ProcessAlarmLatch is set, this alarm remains latched until it is unlatched

Ch0LAlarm Boolean Ch0Status:3Ch0Data < Ch0LAlarmLimit If Ch0Config.ProcessAlarmLatch is set, this alarm remains latched until it is unlatched

Ch0RateAlarm Boolean Ch0Status:4Ch0Data 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

Ch0Overrange Boolean 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

Ch0Underrange Boolean 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

Ch0CalFault Boolean Ch0Status:7 Set if an error occurs during calibration for Channel 0, causing a bad calibration. Also sets CalFault

Ch1Status SINT Binary

Ch1HHAlarm Boolean Ch1Status:0(1)

Ch1LLAlarm Boolean Ch1Status:1(1)

Ch1HAlarm Boolean Ch1Status:2(1)

Ch1LAlarm Boolean Ch1Status:3(1)



Description


160 Tag Definitions

Ch1RateAlarm Boolean Ch1Status:4(1)

Ch1Overrange Boolean Ch1Status:5(1)

Ch1Underrange Boolean Ch1Status:6(1)

Ch1CalFault Boolean Ch1Status:7(1)






























Description


Tag Definitions 161




























Ch0Data REAL Float Value of analog signal on Channel 0 after conversion to Engineering Units

Ch1Data REAL Float

Ch2Data REAL Float

Ch3Data REAL Float



Description


162 Tag Definitions

Ch4Data REAL Float

Ch5Data REAL Float

Ch6Data REAL Float

Ch7Data REAL Float

CSTTimestamp DINT[2] 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

RollingTimestamp INT Decimal Timestamp taken at the time the input data was sampled in millisecond resolution

HART Module-defined Data Type: AB:1756_IF8H_HARTData:I:0

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

(1) See Ch0 equivalent in this table for description.



Description


Tag Definitions 163

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.

Module-defined Data Type: AB:1756_IF8H_HARTStatus_Struct:I:0


Description

Init Boolean 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

Fail Boolean 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)

MsgReady Boolean Pass through message reply is ready

CurrentFault Boolean Analog current measurement does not match the current the Field Device reported over HART network

ConfigurationChanged Boolean 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 SINT Binary HART communication status byte or Response code from a recent HART reply. See table below for details

FieldDeviceStatus SINT Binary HART device status byte from a recent HART reply. Indicates the health of the HART Field device. See table below for details


164 Tag Definitions

See the Communication Status table. The Communication Status is returned when a communication error is detected by the field device.

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 0…127), 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.

Communication Status

Bit 7 = 1: Communication Errors

Bit 6 16#40 Parity Error Vertical parity error - The parity of one or more of the bytes received by the device was not odd

Bit 5 16#20 Overrun Error 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)

Bit 4 16#x10 Framing Error 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)

Bit 3 16#x08 Checksum Error Longitudinal parity error - The Longitudinal Parity calculated by the device did not match the Check Byte at thend of the message

Bit 2 16#x04 (Reserved) Reserved - Set to zero

Bit 1 16#x02 RX Buffer Overflow Buffer overflow - The message was too long for the receive buffer of the define

Bit 0 16#x01 (undefined) Reserved - Set to zero

Module-defined Data Type: AB:1756_IF8H_HARTData:I:0


Description

Ch0DeviceStatus AB:1756_IF8H_HARTStatus_Structure:I:0

HART device health information and communication status for Channel 0






Tag Definitions 165




Ch0PV 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

Ch0TV REAL Float HART Tertiary or Third Variable. A HART flow transmitter might put the density here

Ch0FV REAL Float HART Fourth or Quaternary Variable. A HART flow transmitter might put the totalized flow here. Not all devices have more than 1 dynamic Variable

Ch0PVStatus SINT Hex HART status of the PV. If 16#C0, it is Good. See the HART PV, SV, TV, and FV Status Values table for details

Ch0SVStatus SINT Hex HART status of the SV. If 16#C0, it is Good. See the HART PV, SV, TV, and FV Status Values table for details

Ch0TVStatus SINT Hex HART status of the TV. If 16#C0, it is Good. See the HART PV, SV, TV, and FV Status Values table for details

Ch0FVStatus SINT Hex HART status of the FV. If 16#C0, it is Good. See the HART PV, SV, TV, and FV Status Values table for details



Description


166 Tag Definitions

Ch1PV REAL Float See Ch0 equivalent in this table for description

Ch1SV REAL Float

Ch1TV REAL Float

Ch1FV REAL Float

Ch1PVStatus SINT Hex

Ch1SVStatus SINT Hex

Ch1TVStatus SINT Hex

Ch1FVStatus SINT Hex

Ch2PV REAL Float

Ch2SV REAL Float

Ch2TV REAL Float

Ch2FV REAL Float





Ch3PV REAL Float

Ch3SV REAL Float

Ch3TV REAL Float

Ch3FV REAL Float





Ch4PV REAL Float

Ch4SV REAL Float

Ch4TV REAL Float

Ch4FV REAL Float





Ch5PV REAL Float

Ch5SV REAL Float

Ch5TV REAL Float



Description


Tag Definitions 167

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.

Ch5FV REAL Float See Ch0 equivalent in this table for description





Ch6PV REAL Float

Ch6SV REAL Float

Ch6TV REAL Float

Ch6FV REAL Float





Ch7PV REAL Float

Ch7SV REAL Float

Ch7TV REAL Float

Ch7FV REAL Float







Description


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.

The Limit Status can be used to control windup in PID loops.

Device Family Specific Status

More Device Variable Status AvailableLimit Status 11 Constant 01 Low Limited 10 High Limited 00 Not Limited

Process Data Status 11 Good 01 Poor Accuracy 10 Manual/Fixed 00 Bad

HART PV, SV, TV, and FV Status Values

HART PV, SV, TV FV Status Values Quality Limit More Status Available?

Device Family Specific

Decimal Hex Binary Binary Decimal

0 0 00000000 00 Bad 00 Not Limited 0 no 000 0








8 8 00001000 00 Bad 00 Not Limited 1 yes 000 0

9 9 00001001 00 Bad 00 Not Limited 1 yes 001 1

10 A 00001010 00 Bad 00 Not Limited 1 yes 010 2

11 B 00001011 00 Bad 00 Not Limited 1 yes 011 3

12 C 00001100 00 Bad 00 Not Limited 1 yes 100 4

13 D 00001101 00 Bad 00 Not Limited 1 yes 101 5

14 E 00001110 00 Bad 00 Not Limited 1 yes 110 6

15 F 00001111 00 Bad 00 Not Limited 1 yes 111 7

16 10 00010000 00 Bad 01 Low Limited 0 no 000 0






Tag Definitions 169

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.




24 18 00011000 00 Bad 01 Low Limited 1 yes 000 0

25 19 00011001 00 Bad 01 Low Limited 1 yes 001 1

26 1A 00011010 00 Bad 01 Low Limited 1 yes 010 2

27 1B 00011011 00 Bad 01 Low Limited 1 yes 011 3

28 1C 00011100 00 Bad 01 Low Limited 1 yes 100 4

29 1D 00011101 00 Bad 01 Low Limited 1 yes 101 5

30 1E 00011110 00 Bad 01 Low Limited 1 yes 110 6

31 1F 00011111 00 Bad 01 Low Limited 1 yes 111 7

32 20 00100000 00 Bad 10 High Limited 0 no 000 0








40 28 00101000 00 Bad 10 High Limited 1 yes 000 0

41 29 00101001 00 Bad 10 High Limited 1 yes 001 1

42 2A 00101010 00 Bad 10 High Limited 1 yes 010 2

43 2B 00101011 00 Bad 10 High Limited 1 yes 011 3

44 2C 00101100 00 Bad 10 High Limited 1 yes 100 4

45 2D 00101101 00 Bad 10 High Limited 1 yes 101 5

HART PV, SV, TV, and FV Status Values


170 Tag Definitions

Module-defined Data Type: AB:1756_IF8H_ChConfig_Struct:C:0


Description

ChConfig (Bits 0...3 not used)

SINT Binary

RateAlarmLatch Boolean ChConfig:4

ProcessAlarmLatch Boolean ChConfig:5

AlarmDisable Boolean ChConfig:6

HARTEn Boolean ChConfig:7

RangeType SINT Decimal

DigitalFilter INT Decimal

RateAlarmLimit REAL Float

LowSignal REAL Float

HighSignal REAL Float

LowEngineering REAL Float

HighEngineering REAL Float

LAlarmLimit REAL Float

HAlarmLimit REAL Float

LLAlarmLimit REAL Float

HHAlarmLimit REAL Float

AlarmDeadband REAL Float

CalBias REAL Float


Tag Definitions 171

Module-defined Data Type: AB:1756_IF8H:C:0


Description

ModuleFilter SINT Decimal

RealTimeSample INT Decimal

AB:1756_IF8H_ChConfig_Struct:C:0 Ch0Config








PassthroughHandleTimeout INT Decimal

PassthroughConfig INT Binary Bits 0...13 not used

PassthroughCmdFreq_14 Boolean PassthroughConfig14

PassthroughCmdFreq_15 Boolean PassthroughConfig15


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


Description

Ch0Data REAL Float Value in Engineering units to output on the analog signal of Channel 0

Ch1Data REAL Float

Ch2Data REAL Float

Ch3Data REAL Float

Ch4Data REAL Float

Ch5Data REAL Float

Ch6Data REAL Float

Ch7Data REAL Float

Module-defined Data Type: AB:1756_OF8H - Analog:I:0 and Module-defined Data Type: AB:1756_OF8H_HARTPV:I:0


Description

Channel Faults INT Binary









LoopOutputFault Boolean ChannelFaults.8 (bits 9...15 unused)

HARTFaults SINT Binary

Ch0HARTFault Boolean HARTFault.0Indicates 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

Ch1HARTFault Boolean HARTFault.1




Tag Definitions 173





CalFault Boolean ModuleFaults.1 A fault during calibration on any channel

Calibrating Boolean ModuleFaults.2 (bits 3…6 not used)Calibration in progress

AnalogGroupFault Boolean ModuleFaults.7 A fault in the analog signal on any channel


Ch0OpenWire Boolean Ch0Status:7 Only valid in Current mode (example 4…20 mA). 1 indicates no current is flowing, probably due to open circuit.

Ch0NotANumber Boolean Ch0Status:5 Ch0Data is not a valid floating point number

Ch0CalFault Boolean Ch0Status:4 Fault during calibration of channel 0

Ch0InHold Boolean 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

Ch0RampAlarm Boolean 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

Ch0LLimitAlarm Boolean 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.

Ch0HLimitAlarm Boolean 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.


Ch1OpenWire Boolean Ch1Status:7(1)

Ch1NotANumber Boolean Ch1Status:5(1)


Ch1InHold Boolean Ch1Status:3(1)

Ch1RampAlarm Boolean Ch1Status:2(1)

Ch1LLimitAlarm Boolean Ch1Status:1(1)

Ch1HLimitAlarm Boolean Ch1Status:0(1)








174 Tag Definitions































Tag Definitions 175































176 Tag Definitions



































Tag Definitions 177











Ch0Data REAL Float 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

Ch1Data REAL Float

Ch2Data REAL Float

Ch3Data REAL Float

Ch4Data REAL Float

Ch5Data REAL Float

Ch6Data REAL Float

Ch7Data REAL Float

CSTTimestamp[2] DINT[2] 64-bit Coordinated System Time Timestamp in microseconds of the last output update. Timebase synchronized with other modules in the rack

RollingTimestamp INT 16 bit timestamp in milliseconds. Timebase local to the 1756-OF8H module

HART AB:1756_OF8H_HARTData:I:O

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

(1) See Ch0 equivalent in this table for description.



178 Tag Definitions

Module-defined Data Type: AB:1756_OF8H_HARTStatus_Struct:I:0


Description

Init Bit Channel:0

Fail Boolean Channel:1

MsgReady Bit Channel:2

CurrentFault Boolean Channel:3

ConfigurationChanged Bit Channel:4

ResponseCode SINT Binary

FieldDeviceStatus SINT Binary

Module-defined Data Type: AB:1756_OF8H_HARTData:I:0


Description

AB:1756_OF8H_HARTStatus_Structure:I:0 Ch0DeviceStatus








Ch0PV REAL Float Digital readback of the Primary Variable. For example, on a valve controller, the command valve position in engineering units such as %

Ch0SV REAL Float Secondary Variable - in a valve positioner, perhaps the Actual valve position

Ch0TV REAL Float Third or Tertiary Variable - in a pneumatic valve positioner, perhaps the air supply pressure

Ch0FV REAL Float Fourth or Quaternary Variable - in a motor operated valve positioner, perhaps the torque






Tag Definitions 179


Ch1SV REAL Float

Ch1TV REAL Float

Ch1FV REAL Float






Ch2SV REAL Float

Ch2TV REAL Float

Ch2FV REAL Float






Ch3SV REAL Float

Ch3TV REAL Float

Ch3FV REAL Float






Ch4SV REAL Float

Ch4TV REAL Float

Ch4FV REAL Float






Ch5SV REAL Float

Ch5TV REAL Float

Ch5FV REAL Float




180 Tag Definitions





Ch6SV REAL Float

Ch6TV REAL Float

Ch6FV REAL Float






Ch7SV REAL Float

Ch7TV REAL Float

Ch7FV REAL Float







Tag Definitions 181

Module-defined Data Type: AB:1756_OF8H_ChConfig_Struct:C:0


Description

RampToFault Boolean ConfigBits:9

RampToProg Boolean ConfigBits:8

RampToRun Boolean ConfigBits:7

ProgMode Boolean ConfigBits:6

FaultMode Boolean ConfigBits:5

LimitAlarmLatch Boolean ConfigBits:4

RampAlarmLatch Boolean ConfigBits:3

AlarmDisable Boolean ConfigBits:2

HoldForInit Boolean ConfigBits:1

HARTEnable Boolean ConfigBits:0

RangeType INT

MaxRampRate REAL Float

FaultValue REAL Float

ProgValue REAL Float

LowSignal REAL Float

HighSignal REAL Float

LowEngineering REAL Float

HighEngineering REAL Float

LowLimit REAL Float

HighLimit REAL Float

CalBias REAL Float


182 Tag Definitions

Module-defined Data Type: AB:1756_OF8H:C:0

Member name Type Default Display Style Description

AB:1756_OF8H_ChConfig_Struct:C:0 Ch0Config








PassthroughHandleTimeout INT Decimal

PassthroughFreq_14 Boolean PassthroughConfig:14

PassthroughFreq_15 Boolean PassthroughConfig:15


Appendix B

Calibration Information


This appendix offers reference calibration information to assist you in using the ControlLogix analog I/O module.

Analog to Digital (A/D) Converter Accuracy

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 module’s total accuracy is maintained.

Calibrated Accuracy The calibrated accuracy specification represents the module’s 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.


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 module’s 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 module’s calibration accuracy at 25 °C (77 °F) is calculated over the full hardware range of the module and is not dependent on the application’s 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 module’s 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 module’s operating temperature changes can affect a module’s accuracy:

• Gain Drift With Temperature

• Module Error Over Full Temperature Range

Gain drift with temperature represents the calibration inaccuracy that occurs as a module’s 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 module’s 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 module’s calibration is inaccurate to for each degree difference. The specification is determined with the following formula:

Gain Drift with Temperature = (PPM/°C) x Module’s Full Range


Appendix C

Using 1492 Wiring Systems with Your Analog I/O Module


This appendix provides information about an alternative to buying removable terminal blocks and connecting the wires yourself.

Using a Wiring System 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

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.

I/O Module Prewired Cable Analog Interface Module


186 Using 1492 Wiring Systems with Your Analog I/O Module

Analog Interface Module and Prewired Cables

For Use With

1756-IF8H 1492-AIFM8-3 1492-ACABLExUD (current)

1492-ACABLExUC (voltage)

1756-OF8H 1492-ACABLExWB

Analog Interface Modules Available for Use with ControlLogix Analog I/O Modules

Catalog Number Type of Analog Interface Module

Description

1492-AIFM8-3 Feed-through 8 channels with 3 terminals per channel

I/O Module-ready Prewired Cables Used with ControlLogix Analog I/O Modules

Catalog Number(1)

(1) 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.

Number of Conductors(2)

(2) 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.

Conductor Size

Nominal Outer Diameter

Removable Terminal Block at the I/O Module End

1492-ACABLExUC 9 twisted pairs 22 AWG 6.8 mm (0.27 in.)

1756-TBCH

1492-ACABLExUD

1492-ACABLExWB 1756-TBNH


Appendix D

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 4…20mA 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.


188 Additional HART Protocol Information

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.


Additional HART Protocol Information 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.

Change the display format to Hexadecimal to interpret communication status.

Communication Status - Communication Errors

Bit 7 = 1: Communication Errors

Bit 6 16#40 Parity Error Vertical parity error - The parity of one or more of the bytes received by the device was not odd

Bit 5 16#20 Overrun Error 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)

Bit 4 16#10 Framing Error 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)

Bit 3 16#08 Checksum Error Longitudinal parity error - The Longitudinal Parity calculated by the device did not match the Check Byte at thend of the message

Bit 2 16#04 (Reserved) Reserved - Set to zero

Bit 1 16#02 RX Buffer Overflow Buffer overflow - The message was too long for the receive buffer of the define

Bit 0 16#01 (undefined) Reserved - Set to zero



Response Codes If the leftmost bit of ResponseCode is 0 (value 0…127), 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.

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.

Response Code Meaning (decimal)

Bit 7 = 0: Command Errors

Bit 6…0 (not bit-mapped)

0 No command specific error

1 (undefined)

3 Value too large

4 Value too small

5 Not enough bytes in command

6 Transmitter-specific command error

7 In Write-protect mode

8 Update Failed - Update In Progress - Set to Nearest Possible Value

9 Applied Process Too High - Lower Range Value Too High - Not In Fixed Current Mode

10 Applied Process Too Low - Lower Range Value Too Low - MultiDrop Not Supported

11 In MultiDrop Mode - Invalid Transmitter Variable Code - Upper Range Value Too High

12 Invalid Unit Code - Upper Range Value Too Low

13 Both Range Values Out of Limits

14 Pushed Upper Range Value Over Limit - Span Too Small

16 Access restricted

32 Device busy

64 Command not implemented



Field Device Status Bit Mask Definitions

Bit Bit Mask Definition

7 16#80 Device malfunction - The device detected a serious error or failure that compromises device operation

6 16#40 Configuration changed - An operation was performed that changed the device’s configuration

5 16#20 Cold start - A power failure or device reset occured

4 16#10 More status available - More status information is available via command 48, Read Additional Status Information

3 16#08 Loop current fixed - The loop current is being held at a fixed value and is not responsding to process variations

2 16#04 Loop current saturated - The loop current has reached its upper or lower endpoint limit and cannot increas or decrease any further

1 16#02 Non-primary variable out of limits - A device variable not mapped to the PV is beyond its operating limits

0 16#01 Primary variable out of limits - The PV is beyond its operating limit

HART Universal Commands(1)

Command Data in Command Data in Reply Contained in

No. Function Byte Data Type Byte Data Type Input Tag

CIP MSG

0 Read Unique Identified

None 0123456789…11

254 (expansion)Manufacturer identification codeManufacturer device type codeNumber of preambles requiredUniversal command revisionDevice-specific command revisionSoftware revisionHardware revisionDevice function flags(2)

Device ID number(H)(B)

xxxxxxxxxx

1 Read primary variable

01…4

PV units codePrimary variable (F) x

xx

2 Read current and percent of range

None 0…34…7

Current (mA)Primary variable %

(F)(F)

xx

xx

3 Read current and four (predefined) dynamic variables

None 0…345…8910…131415…181920…23

Current (mA)PV units codePrimary variableSV units codeSecondary variableTV units codeThird variableFV units codeFourth variable(3)

x

x

x

x

xxxxxxxxx



6 Write polling address

0 Polling address As in command

11 Read unique identifier associated with tag

0…5 Tag (A) 0…11

12 Read message

None 0…23 Message (32 characters) (A) x

13 Read tag, descriptor, date

0…56…1718…20

Tag (8 characters)Descriptor (16 characters)Date

(A)(A)(D)

xxx

14 Read PV sensor information

0…234…78…1112…15

Sensor serial numberUnits code for sensor limits and min spanUpper sensor limitLower sensor limitMin span

(B)

(F)(F)(F)

15 Read output information

0123…67…1011…141516

Alarm select codeTransfer function codePV/range units codeUpper range valueLower range valueDamping value (s)Write-protect codePrivate-label distributor code

(F)(F)(F)

xxxxxx

16 Read final assembly number

None 0…2 Final assembly number (B) x

17 Write message

0…23 Message (32 characters)

(A) As in command

18 Write tag, descriptor, date

0…5

6…17

18…20

Tag (8 characters)Descriptor(16 characters)Date

(A)

(A)

(D)

19 Write final assembly number

0…2 Final assembly number

(B)

(1) (A) = Packed ASCII, (B) = 3-byte integer, (D) = Date, (F) = Floating Point (HART format), (H) = HART flag.

(2) Bit 6 = multisensor device. Bit 1 = EEPROM control required. Bit 2 = protocol bridge device.

(3) Truncated after last supported variable.

HART Universal Commands(1)



CIP MSG



Common Practice Commands(1)



CIP MSG

33 Read transmitter variables

None 012…5678…11121314…17181920…23

Transmitter variable code for slot 0Units code for slot 0Variable for slot 0Transmitter variable code for slot 1Units code for slot 1Variable for slot 1Transmitter variable code for slot 2Units code for slot 2Variable for slot 2Transmitter variable code for slot 3Units code for slot 3Variable for slot 3(7)

(F)

(F)

(F)

34 Write damping value

0…3 Damping value (s) (F) As in command (F)

35 Write range values

01…45…8

Range units codeUpper-range valueLower-range value

(F)(F)

(F)

(F)

36 Set upper-range value (= push SPAN button)

None None

37 Set lower-range value (= push ZERO button)

38 Reset "configuration changed" flag

39 EEPROM control

0 EEPROM control code(4)

As in command

40 Enter/exit Fixed Current mode

0…3(2) Current (mA) (F) As in command



41 Perform device self-test

None None

42 Perform master reset

43 Set (trim) PV zero

44 Write PV units

0 PV units code As in command

45 Trim DAC zero

0…3 Measured current (mA)

46 Trim DAC gain

0…3 (F)

47 Write transfer function

0 Transfer function code

48 Read additional device status

None 0…56…78…1011…1314…24

Device-specific statusOperational modesAnalog outputs saturated(8)

Analog outputs fixed(9)

Device-specific status

s(11) xxxxx

49 Write PV sensor serial number

0…2 Sensor serial number

As in command

50 Read dynamic variable assignments

None 0123

PV transmitter variable codeSV transmitter variable codeTV transmitter variable codeFV transmitter variable code

xxxx




CIP MSG



51 Write dynamic variable assignments

0

1

2

3

PV transmitter variable codeSV transmitter variable codeTV transmitter variable codeFV transmitter variable code

As in command

52 Set transmitter variable zero

0 Transmitter variable code

53 Write transmitter variable units

Transmitter variable code

54 Read transmitter variable information

Transmitter variable code

01…345…89…1213…16

Transmitter variable codeTransmitter variable sensor serial Transmitter variable limits units codeTransmitter variable upper limitTransmitter variable lower limitTransmitter variable damping value (s)

(F)(F)(F)

55 Write transmitter variable damping value

0

1…4

Transmitter variable codeTransmitter variable damping value (s)

As in command

56 Write transmitter variable sensor serial number

0

1…3

Transmitter variable codeTransmitter variable sensor

As in command

57 Read unit tag, description, date

None 0…56…1718…20

(A)(A)(D)

xxxx

58 Write unit tag, descriptor, date

0…5

6…1718…20

Unit tag (8 characters)Unit descriptor (16 characters)Unit date

(A)

(A)(D)

59 Write number of response preambles

0 Number of response preambles




CIP MSG



60 Read analog output and percent of range

0 Analog output number code

012…56…9

Analog output number codeAnalog output units codeAnalog output levelAnalog output percent of range

61 Read dynamic variables and PV analog output

None 01…456…91011…141516…192021…24

PV analog output units codePV analog output levelPV units codePrimary variableSV units codeSecondary variableTV unitsTertiary variableFV units codeFourth variable

(F)

(F)

(F)

(F)

(F)

x

x

x

x

xxxxxxxx

62 Read analog outputs 0

1

2

3(3)

Analog output number;code for slot 0Analog output number;code for slot 1Analog output number;code for slot 2Analog output number;code for slot 3(5)

012…5678…11121314…17181920…23

Slot 0 analog output number code Slot 0 Slot 0 levelSlot 1 Slot 1 Slot 1 levelSlot 2 Slot 2 Slot 2 levelSlot 3 Slot 3 Slot 3 level(10)

(F)

(F)

(F)

(F)

63 Read analog output infor-mation


01234…78…1112…15

Analog output number codeAnalog output alarm select codeAnalog output transfer function codeAnalog output range units codeAnalog output upper-range valueAnalog output lower-range valueAnalog output additional damping value (s)

(F)(F)(F)




CIP MSG



64 Write analog output additional damping value

0

1…4

Analog output number codeAnalog output additional damping value (s)

(F)

As in command

65 Write analog output range value

0

1

2…5

6…9

Analog output number codeAnalog output range units codeAnalog output upper-range valueAnalog output lower-range value

(F)

(F)

66 Enter/exit Fixed Analog Output mode

0

12…6

Analog output number codeAnalog output units codeAnalog output level(6)

(F)

67 Trim analog output zero

0

12…6

Analog output number codeAnalog output units codeExternally measured analog output level

(F)

68 Trim analog output gain

0

12…6

Analog output number codeAnalog output units codeExternally measured analog output level

(F)

69 Write analog output transfer function

0

1

Analog output number codeAnalog output transfer function code

70 Read analog output endpoint values


012…56…9

Analog output number codeAnalog output endpoint units codeAnalog output upper endpoint valueAnalog output lower endpoint value




CIP MSG



107 Write Burst mode transmitter variables (for command 33)

0

1

2

3

Transmitter variable code for slot 0Transmitter variable code for slot 1Transmitter variable code for slot 2Transmitter variablecode for slot 3

As in command

108 Write Burst mode command number

0 Burst mode command number

As in command

109 Burst mode control

0 Burst mode control code (0 = exit, 1 = enter)

110 Read all dynamic variables

None 01…456…91011…141516…19

PV units codePV valueSV units codeSV valueTV units codeTV valueFV units codeFV value

(F)

(F)

(F)

(F)

x

x

x

x

xxxxxxxx

(1) (A) = Packed ASCII, (B) = 3-byte integer, (D) = Date, (F) = Floating Point (HART format), (H) = HART flag.

(2) 0 = exit Fixed Current mode.

(3) Truncated after last requested code.

(4) 0 = burn EEPROM, 1 = copy EEPROM to RAM.

(5) Truncated after last requested code.

(6) Not a number exits Fixed-output mode.

(7) Truncated after last requested code. Truncated after last requested variable.

(8) 24 bits each LSB…MSB refers to A0 #1…24.

(9) 24 bits each LSB…MSB refers to A0 #1…24.

(10) Truncated after last requested level.

(11) Sint []




CIP MSG


Appendix E

Company Identification Codes


This appendix provides details about company identification codes, as described in the chapter on configurating and using HART.

Identification Code Details See the table that shows company identification code details.


Decimal Hex Company Name

1 01 Acromag

2 02 Allen-Bradley

3 03 Ametek

4 04 Analog Devices

5 05 Elsag Bailey

6 06 Beckman

7 07 Bell Microsenser

8 08 Bourns

9 09 Bristol Babcock

10 0A Brooks Instrument

11 0B Chessell

12 0C Combustion Engineering

13 0D Daniel Industries

14 0E Delta

15 0F Dieterich Standard

16 10 Dohrmann

17 11 Endress+Hauser

18 12 Elsag Bailey

19 13 Fisher Controls

20 14 Foxboro

21 15 Fuji

22 16 ABB Automation

23 17 Honeywell

24 18 ITT Barton

25 19 Kay Ray/Sensall


200 Company Identification Codes

26 1A ABB Automation

27 1B Leeds & Northup

28 1C Leslie

29 1D M-System Co.

30 1E Measurex

31 1F Micro Motion

32 20 Moore Industries

33 21 Moore Products

34 22 Ohkura Electric

35 23 Paine

36 24 Rochester Instrument Systems

37 25 Ronan

38 26 Rosemount

39 27 Peek Measurement

40 28 Schlumberger

41 29 Sensall

42 2A Siemens

43 2B Weed

44 2C Toshiba

45 2D Transmation

46 2E Rosemount Analytic

47 2F Meso Automation

48 30 Flowserve

49 31 Varec

50 32 Viatran

51 33 Delta/Weed

52 34 Westinghouse

53 35 Xomox

54 36 Yamatake

55 37 Yokogawa

56 38 Nuovo Pignone

57 39 Promac

58 3A Exac Corporation

59 3B Meggitt Mobrey

60 3C Arcom Control System

61 3D Princo




Company Identification Codes 201

62 3E Smar

63 3F Foxboro

64 40 Measurement Technology

65 41 Applied System Technologies

66 42 Samson

67 43 Sparling Instruments

68 44 Fireye

69 45 Krohne

70 46 Betz

71 47 Druck

72 48 SOR

73 49 Elcon Instruments

74 4A EMCO

75 4B Termiflex Corporation

76 4C VAF Instruments

77 4D Westlock Controls

78 4E Drexelbrook

79 4F Saab Tank Control

80 50 K-TEK

81 51 Flowdata

82 52 Draeger

83 53 Raytek

84 54 Siemens Milltronics PI

85 55 BTG

86 56 Magnetrol

87 58 Metso Automation

88 59 Milltronics

89 59 HELIOS

90 5A Anderson Instrument Company

91 5B INOR

92 5C ROBERTSHAW

93 5D PEPPERL+FUCHS

94 5E ACCUTECH

95 5F Flow Measurement

96 60 KAMSTRUP

97 61 Knick





98 62 VEGA

99 63 MTS Systems Corp.

100 64 Oval

101 65 Masoneilan-Dresser

102 66 BESTA

103 67 Ohmart

104 68 Harold Beck and Sons

105 69 rittmeyer instrumentation

106 6A Rossel Messtechnik

107 6B WIKA

108 6C Bopp & Reuther Heinrichs

109 6D PR Electronics

110 6E Jordan Controls

111 6F Valcom s.r.l.

112 70 US ELECTRIC MOTORS

113 71 Apparatebau Hundsbach

114 72 Dynisco

115 73 Spriano

116 74 Direct Measurement

117 75 Klay Instruments

118 76 Action Instruments

119 77 MMG Automatiky DTR

120 78 Buerkert Fluid Control Systems

121 79 AALIANT Process Mgt

122 7A PONDUS INSTRUMENTS

123 7B ZAP S.A. Ostrow Wielkopolski

124 7C GLI

125 7D Fisher-Rosemount Performance Technologies

126 7E Paper Machine Components

127 7F LABOM

128 80 Danfoss

129 81 Turbo

130 82 TOKYO KEISO

131 83 SMC

132 84 Status Instruments

133 85 Huakong




Company Identification Codes 203

134 86 Duon System

135 87 Vortek Instruments, LLC

136 88 AG Crosby

137 89 Action Instruments

138 8A Keystone Controls

139 8B Thermo Electronic Co.

140 8C ISE-Magtech

141 8D Rueger

142 8E Mettler-Toledo

143 8F Det-Tronics

144 90 TN Technologies

145 91 DeZURIK

146 92 Phase Dynamics

147 93 WELLTECH SHANGHAI

148 94 ENRAF

149 95 4tech ASA

150 96 Brandt Instruments

151 97 Nivelco

152 98 Camille Bauer

153 99 Metran

154 9A Milton Roy Co.

155 9B PMV

156 9C Turck

157 9D Panametrics

158 9E Stahl

159 9F Analytical Technologies Inc.

160 A0 Fieldbus International

161 A1 BERTHOLD

162 A2 InterCorr

163 A3 China BRICONTE Co Ltd

164 A4 Electron Machine

165 A5 Sierra Instruments

166 A6 Fluid Components Intl

250 FA Not used





251 FB None

252 FC Unknown

253 FD Special




Appendix F

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 See the table that maps engineering unit code numbers to their meaning and abbreviations.

Engineering Unit Code Number Mapping

Unit Codes Resource Identification Description from HART Specification Abbreviated Units

1 PRESSURE_ID_1 inches of water at 68 degrees F inH2O (68 °F)

2 PRESSURE_ID_2 inches of mercury at 0 degrees C inHg (0 °C)

3 PRESSURE_ID_3 feet of water at 68 degrees F ftH2O (68 °F)

4 PRESSURE_ID_4 millimeters of water at 68 degrees F mmH2O (68 °F)

5 PRESSURE_ID_5 millimeters of mercury at 0 degrees C mmHg (0 °C)

6 PRESSURE_ID_6 pounds per square inch psi

7 PRESSURE_ID_7 bars bar

8 PRESSURE_ID_8 millibars mbar

9 PRESSURE_ID_9 grams per square centimeter g/square cm

10 PRESSURE_ID_10 kilograms per square centimeter kg/square cm

11 PRESSURE_ID_11 pascals Pa

12 PRESSURE_ID_12 kilopascals kPa

13 PRESSURE_ID_13 torr torr

14 PRESSURE_ID_14 atmospheres atm

15 VOLUMETRIC_FLOW_ID_15 cubic feet per minute cubic ft/min

16 VOLUMETRIC_FLOW_ID_16 gallons per minute usg/min

17 VOLUMETRIC_FLOW_ID_17 liters per minute L/min

18 VOLUMETRIC_FLOW_ID_18 imperial gallons per minute impgal/min

19 VOLUMETRIC_FLOW_ID_19 cubic meter per hour cubic m/h

20 VELOCITY_ID_20 feet per second ft/s

21 VELOCITY_ID_21 meters per second m/s

22 VOLUMETRIC_FLOW_ID_22 gallons per second usg/s

23 VOLUMETRIC_FLOW_ID_23 million gallons per day million usg/d

24 VOLUMETRIC_FLOW_ID_24 liters per second L/s


206 Engineering Unit Code Numbers

25 VOLUMETRIC_FLOW_ID_25 million liters per day ML/day

26 VOLUMETRIC_FLOW_ID_26 cubic feet per second cubic ft/s

27 VOLUMETRIC_FLOW_ID_27 cubic feet per day cubic ft/d

28 VOLUMETRIC_FLOW_ID_28 cubic meters per second cubic m/s

29 VOLUMETRIC_FLOW_ID_29 cubic meters per day cubic m/d

30 VOLUMETRIC_FLOW_ID_30 imperial gallons per hour impgal/h

31 VOLUMETRIC_FLOW_ID_31 imperial gallons per day impgal/d

32 TEMPERATURE_ID_32 Degrees Celsius °C

33 TEMPERATURE_ID_33 Degrees Fahrenheit °F

34 TEMPERATURE_ID_34 Degrees Rankine °R

35 TEMPERATURE_ID_35 Kelvin °K

36 ELECTRICAL_ID_36 millivolts mV

37 ELECTRICAL_ID_37 ohms ohm

38 MISCELLANEOUS_ID_38 hertz hz

39 ELECTRICAL_ID_39 milliamperes mA

40 VOLUME_ID_40 gallons usg

41 VOLUME_ID_41 liters L

42 VOLUME_ID_42 imperial gallons impgal

43 VOLUME_ID_43 cubic meters cubic m

44 LENGTH_ID_44 feet ft

45 LENGTH_ID_45 meters m

46 VOLUME_ID_46 barrels bbl

47 LENGTH_ID_47 inches in

48 LENGTH_ID_48 centimeters cm

49 LENGTH_ID_49 millimeters mm

50 TIME_ID_50 minutes min

51 TIME_ID_51 seconds s

52 TIME_ID_52 hours h

53 TIME_ID_53 days d

54 VISCOSITY_ID_54 centistokes centistokes

55 VISCOSITY_ID_55 centipoise cP

56 MISCELLANEOUS_ID_56 microsiemens microsiemens

57 MISCELLANEOUS_ID_57 percent %

58 ELECTRICAL_ID_58 volts V

59 MISCELLANEOUS_ID_59 pH pH

60 MASS_ID_60 grams g




Engineering Unit Code Numbers 207

61 MASS_ID_61 kilograms kg

62 MASS_ID_62 metric tons t

63 MASS_ID_63 pounds lb

64 MASS_ID_64 short tons short ton

65 MASS_ID_65 long tons long ton

66 MISCELLANEOUS_ID_66 milli siemens per centimeter millisiemens/cm

67 MISCELLANEOUS_ID_67 micro siemens per centimeter microsiemens/cm

68 MISCELLANEOUS_ID_68 newton N

69 ENERGY_ID_69 newton meter N m

70 MASS_FLOW_ID_70 grams per second g/s

71 MASS_FLOW_ID_71 grams per minute g/min

72 MASS_FLOW_ID_72 grams per hour g/h

73 MASS_FLOW_ID_73 kilograms per second kg/s

74 MASS_FLOW_ID_74 kilograms per minute kg/min

75 MASS_FLOW_ID_75 kilograms per hour kg/h

76 MASS_FLOW_ID_76 kilograms per day kg/d

77 MASS_FLOW_ID_77 metric tons per minute t/min

78 MASS_FLOW_ID_78 metric tons per hour t/h

79 MASS_FLOW_ID_79 metric tons per day t/d

80 MASS_FLOW_ID_80 pounds per second lb/s

81 MASS_FLOW_ID_81 pounds per minute lb/min

82 MASS_FLOW_ID_82 pounds per hour lb/h

83 MASS_FLOW_ID_83 pounds per day lb/d

84 MASS_FLOW_ID_84 short tons per minute short ton/min

85 MASS_FLOW_ID_85 short tons per hour short ton/h

86 MASS_FLOW_ID_86 short tons per day short ton/d

87 MASS_FLOW_ID_87 long tons per hour long ton/h

88 MASS_FLOW_ID_88 long tons per day long ton/d

89 ENERGY_ID_89 deka therm Dth

90 MASS_PER_VOLUME_ID_90 specific gravity units specific gravity units

91 MASS_PER_VOLUME_ID_91 grams per cubic centimeter g/cubic cm

92 MASS_PER_VOLUME_ID_92 kilograms per cubic meter kg/cubic m

93 MASS_PER_VOLUME_ID_93 pounds per gallon lb/usg

94 MASS_PER_VOLUME_ID_94 pounds per cubic feet lb/cubic ft

95 MASS_PER_VOLUME_ID_95 grams per milliliter g/mL

96 MASS_PER_VOLUME_ID_96 kilograms per liter kg/L





97 MASS_PER_VOLUME_ID_97 grams per liter g/L

98 MASS_PER_VOLUME_ID_98 pounds per cubic inch lb/cubic in

99 MASS_PER_VOLUME_ID_99 short tons per cubic yard short ton/cubic yd

100 MASS_PER_VOLUME_ID_100 degrees twaddell °Tw

101 MISCELLANEOUS_ID_101 degrees brix °Bx

102 MASS_PER_VOLUME_ID_102 degrees baume heavy BH

103 MASS_PER_VOLUME_ID_103 degrees baume light BL

104 MASS_PER_VOLUME_ID_104 degrees API °API

105 MISCELLANEOUS_ID_105 percent solids per weight % solid/weight

106 MISCELLANEOUS_ID_106 percent solids per volume % solid/volume

107 MISCELLANEOUS_ID_107 degrees balling degrees balling

108 MISCELLANEOUS_ID_108 proof per volume proof/volume

109 MISCELLANEOUS_ID_109 proof per mass proof/mass

110 VOLUME_ID_110 bushels bushel

111 VOLUME_ID_111 cubic yards cubic yd

112 VOLUME_ID_112 cubic feet cubic ft

113 VOLUME_ID_113 cubic inches cubic in

114 VELOCITY_ID_114 inches per second in/s

115 VELOCITY_ID_115 inches per minute in/min

116 VELOCITY_ID_116 feet per minute ft/min

117 RADIAL_VELOCITY_ID_117 degrees per second °/s

118 RADIAL_VELOCITY_ID_118 revolutions per second rev/s

119 RADIAL_VELOCITY_ID_119 revolutions per minute rpm

120 VELOCITY_ID_120 meters per hour m/hr

121 VOLUMETRIC_FLOW_ID_121 normal cubic meter per hour normal cubic m/h

122 VOLUMETRIC_FLOW_ID_122 normal liter per hour normal L/h

123 VOLUMETRIC_FLOW_ID_123 standard cubic feet per minute standard cubic ft/min

124 VOLUME_ID_124 bbl liq bbl liq

125 MASS_ID_125 ounce oz

126 ENERGY_ID_126 foot pound force ft lb force

127 POWER_ID_127 kilo watt kW

128 ENERGY_ID_128 kilo watt hour kW h

129 POWER_ID_129 horsepower hp

130 VOLUMETRIC_FLOW_ID_130 cubic feet per hour cubic ft/h

131 VOLUMETRIC_FLOW_ID_131 cubic meters per minute cubic m/min

132 VOLUMETRIC_FLOW_ID_132 barrels per second bbl/s




Engineering Unit Code Numbers 209

133 VOLUMETRIC_FLOW_ID_133 barrels per minute bbl/min

134 VOLUMETRIC_FLOW_ID_134 barrels per hour bbl/h

135 VOLUMETRIC_FLOW_ID_135 barrels per day bbl/d

136 VOLUMETRIC_FLOW_ID_136 gallons per hour usg/h

137 VOLUMETRIC_FLOW_ID_137 imperial gallons per second impgal/s

138 VOLUMETRIC_FLOW_ID_138 liters per hour L/h

139 MISCELLANEOUS_ID_139 parts per million ppm

140 POWER_ID_140 mega calorie per hour Mcal/h

141 POWER_ID_141 mega joule per hour MJ/h

142 POWER_ID_142 british thermal unit per hour BTU/h

143 MISCELLANEOUS_ID_143 degrees degrees

144 MISCELLANEOUS_ID_144 radian rad

145 PRESSURE_ID_145 inches of water at 60 degrees F inH2O (60 °F)

146 MASS_PER_VOLUME_ID_146 micrograms per liter micrograms/L

147 MASS_PER_VOLUME_ID_147 micrograms per cubic meter micrograms/cubic m

148 MISCELLANEOUS_ID_148 percent consistency % consistency

149 MISCELLANEOUS_ID_149 volume percent volume %

150 MISCELLANEOUS_ID_150 percent steam quality % steam quality

151 MISCELLANEOUS_ID_151 feet in sixteenths ft in sixteenths

152 MISCELLANEOUS_ID_152 cubic feet per pound cubic ft/lb

153 MISCELLANEOUS_ID_153 picofarads pF

154 MISCELLANEOUS_ID_154 mililiters per liter mL/L

155 MISCELLANEOUS_ID_155 microliters per liter microliters/L

156 MISCELLANEOUS_ID_160 percent plato % plato

157 MISCELLANEOUS_ID_161 percent lower explosion level % lower explosion level

158 ENERGY_ID_162 mega calorie Mcal

159 ELECTRICAL_ID_163 Kohms kohm

160 ENERGY_ID_164 mega joule MJ

161 ENERGY_ID_165 british thermal unit BTU

162 VOLUME_ID_166 normal cubic meter normal cubic m

163 VOLUME_ID_167 normal liter normal L

164 VOLUME_ID_168 standard cubic feet normal cubic ft

165 MISCELLANEOUS_ID_169 parts per billion parts/billion

235 VOLUMETRIC_FLOW_ID_235 gallons per day usg/d

236 VOLUME_ID_236 hectoliters hL





237 PRESSURE_ID_237 megapascals MPa

238 PRESSURE_ID_238 inches of water at 4 degrees C inH2O (4 °C)

239 PRESSURE_ID_239 millimeters of water at 4 degrees C mmH2O (4 °C)




Index

Aagency certifications 13, 40alarm deadband 52alarms

latching 41

Bbackplane connector 18

CCE certification 13, 40company identification codes 199configuring the modules 69connections 10

as related to module ownership 21direct connections 10, 23listen-only connections 11, 32

ControlNet network 22, 27-28, 30-31coordinated system time (CST) 10, 13

rolling timestamp 39timestamping 39

CSA certification 13, 40C-Tick certification 13, 40

Ddata echo 62data format 13, 41data tags

1756-IF8H modules 1581756-OF8H modules 172

direct connections 10, 23

EEEx certification 13, 40electronic keying 11, 37

compatible match 10, 38disable keying 11, 38exact match 11, 38

electrostatic dischargepreventing 20

engineering unit code numbers 205EtherNet/IP network 22, 28, 31event tasks 26

FFM certification 13, 40

HHART

additional protocol information 187configuring 97definition 11getting data over CIP MSG 109using 97

help 69

Iinhibiting the module 11

in RSLogix 5000 41input circuit diagram

1756-IF8H voltage 56interface module 17

Kkeying

electronic 37

Lladder logic

message configuration 136message instructions 133, 135unlatching alarms in the 1756-IF6I

module 139-140unlatching alarms in the 1756-OF6VI

module 141-142latching alarms 41listen-only connections 11, 32

Mmajor revision 11, 37mechanical keying 18minor revision 12, 37module identification information 19

ASCII text string 19catalog code 19major revision 19minor revision 19product type 19serial number 19status 19vendor ID 19WHO service 19

module resolution 13as related to scaling and data format 43

module statusretrieving 19


2 Index

NNetwork Update Time (NUT)

for ControlNet network 12, 22

Oonline help 69output data echo 29ownership 21

changing configuration in multiple owner-controllers 34

multiple owners 12, 32, 34owner-controller 12

PPass through messages 14, 77, 109, 119,

120, 122, 124, 146, 147preventing electrostatic discharge 20producer/consumer model 13, 39product identification

catalog number 37major revision 37minor revision 37product type 37vendor 37

publications, related 9

Rreal time sample (RTS)

in a local chassis 24in a remote chassis 27

related publications 9remote chassis

connecting via ControlNet network 27-28, 30-31

connecting via EtherNet/IP network 28, 31

removable terminal block (RTB) 17removal and insertion under power

(RIUP) 12, 13, 20, 36

requested packet interval (RPI) 12, 25retrieving module identification

information 19retrieving module status 19revision

major 11minor 12

rolling timestamp 13RSNetworx software

adding a new module to a remote ControlNet chassis 22

using with RSLogix 5000 software 22

Sscaling

as related to module resolution and data format 44

status indicators 18, 40

Ttasks

event 26timestamp

rolling 13timestamping 39triggering event tasks 26troubleshooting

status indicators 18TUV certification 13, 40

UUL certification 13, 40

Wwho should use this manual 9wiring

using the IFM 17using 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 [email protected]

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

Pub. No. 1756-UM533A-EN-P Pub. Date March 2007 Part No. 953030-33

Overall Usefulness 1 2 3 How can we make this publication more useful for you?

Completeness(all necessary information

is provided)

1 2 3 Can we add more information to help you?

procedure/step illustration feature

example guideline other

explanation definition

Technical Accuracy(all provided information

is correct)

1 2 3 Can we be more accurate?

text illustration

Clarity(all provided information is

easy to understand)

1 2 3 How can we make things clearer?

Other Comments You can add additional comments on the back of this form.

Your Name

Your Title/Function Would you like us to contact you regarding your comments?

Location/Phone ___No, there is no need to contact me

___Yes, please call me

___Yes, please email me at _______________________

___Yes, please contact me via _____________________

Return this form to: Rockwell Automation Technical Communications, 1 Allen-Bradley Dr., Mayfield Hts., OH 44124-9705

Fax: 440-646-3525 Email: [email protected]

Publication CIG-CO521C-EN-P- May 2003 957782-91

Other Comments

PLEASE FOLD HERE

NO POSTAGE NECESSARY IF MAILED

IN THE UNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH

POSTAGE WILL BE PAID BY THE ADDRESSEE

1 ALLEN-BRADLEY DRMAYFIELD HEIGHTS OH 44124-9705

PLEASE FASTEN HERE (DO NOT STAPLE)

PLEA

SE R

EMOV

E

Publication 1756-UM533A-EN-P - March 2007 7 PN 953030-33Copyright © 2007 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

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.

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 1.440.646.3223Monday – Friday, 8am – 5pm EST

Outside United States

Please contact your local Rockwell Automation representative for any technical support issues.

United States Contact your distributor. You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process.

Outside United States

Please contact your local Rockwell Automation representative for return procedure.

http://support.rockwellautomation.com

http://support.rockwellautomation.com

Documents

1756 IF8H User Manual