ControlLogix HART Analog I - O Modules
ControlLogix HART Analog I - O Modules
Modules
Catalog Numbers 1756-IF8H, 1756-IF8HK, 1756-IF8IH,
1756-IF8IHK, 1756-IF16H, 1756-IF16HK, 1756-IF16IH,
1756-IF16IHK, 1756-OF8H, 1756-OF8HK, 1756-OF8IH,
1756-OF8IHK
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably
trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this
equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with
any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property damage, or economic loss.
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.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
These labels may also be on or inside the equipment to provide specific precautions.
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.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to
potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL
Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).
Identifies information that is useful and can help to make a process easier to do or easier to understand.
Preface
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Download Firmware, AOP, EDS, and Other Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 1
ControlLogix HART Analog I/O Module Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Modules Module Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Key the Removable Terminal Block/Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
HART Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Integrated HART Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
HART-enabled I/O Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Asset Management Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Timestamping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Module Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 2
ControlLogix Module Operation Direct Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Input Module Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Input Modules in a Local Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Real Time Sample (RTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Trigger Event Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Input Modules in a Remote Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Remote Input Modules Connected Via EtherNet/IP Network . . . . . . . . . . . . . . . . . . 24
Output Module Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Output Modules in a Local Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Output Modules in a Remote Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Remote Output Modules Connected Via EtherNet/IP Network . . . . . . . . . . . . . . . . 25
Listen-only Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Implicit Protected Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Enter and Exit Implicit Protected Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Restrictions Imposed by Implicit Protected Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Multiple Owners of Input Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuration Changes in an Input Module with Multiple Owners. . . . . . . . . . . . . . . . . . 28
Unicast Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 3
1756-IF8H HART Analog Input Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Module Input Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Input Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Module Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Rockwell Automation Publication 1756-UM533F-EN-P - August 2023 3
Table of Contents
Real-time Sampling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Underrange and Overrange Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Digital Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Process Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Rate Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Wire-off Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Wire the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Circuit Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1756-IF8H Module Fault and Status Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1756-IF8H Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1756-IF8H Module Fault Word Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1756-IF8H Channel Fault Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1756-IF8H Channel Status Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Module Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
1756-IF8H Tag Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Analog Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Analog and HART PV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Analog and HART by Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Chapter 4
1756-IF8IH HART Isolated Analog Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Input Module HART Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
HART Handheld Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Input Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Input Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Module Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Digital Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Real-time Sampling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Underrange and Overrange Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Open Circuit Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Auto-Configure HART Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Rate Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Process Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Wire the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Circuit Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
1756-IF8IH Module Fault and Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
1756-IF8IH Module Fault Word Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
1756-IF8IH Channel Fault Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Module Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Module Calibration Via Logix Designer Application. . . . . . . . . . . . . . . . . . . . . . . . . . 58
Module Calibration Via Output Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Module-defined Data Types, 1756-IF8IH Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Configuration - Configure HART Device = No . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Configuration - Configure HART Device = Yes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Input - Analog Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Input - Analog and HART PV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Input - Analog and HART by Channel, Configure HART Device = No . . . . . . . . . . . . 63
Input - Analog and HART by Channel, Configure HART Device = Yes. . . . . . . . . . . . 65
Chapter 5
1756-IF16H HART Analog Input Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Module Input Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Input Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Module Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Real-time Sampling (RTS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Underrange and Overrange Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Digital Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Wire-off Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Wire the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Circuit Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
1756-IF16H Module Fault and Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
1756-IF16H Module Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
1756-IF16H Module Fault Word Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
1756-IF16H Channel Fault Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
1756-IF16H Channel Status Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Module Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Module-defined Data Types, 1756-IF16H Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Analog Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Analog and HART PV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Analog and HART by Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Chapter 6
1756-IF16IH HART Isolated Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Analog Input Module HART Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
HART Handheld Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Input Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Input Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Module Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Digital Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Real-time Sampling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Underrange and Overrange Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Open Circuit Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Wire the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Circuit Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
1756-IF16IH Module Fault and Status Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
1756-IF16IH Module Fault Word Bits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
1756-IF16IH Channel Fault Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
1756-IF16IH Channel Status Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Module Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Module-defined Data Types, 1756-IF16IH Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Analog Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Analog and HART PV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Analog and HART PV by Channel Grouped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Chapter 7
1756-OF8H HART Analog Output Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Module Input Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Ramping/Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Hold for Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Open Wire Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Clamping and Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Clamp and Limit Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Data Echo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Wire the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Use Module Block and Output Circuit Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
1756-OF8H Module Fault and Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
1756-OF8H Fault Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Module Fault Word Bits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Channel Fault Word Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Channel Status Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Module Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Module-defined Data Types, 1756-OF8H Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Analog Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Analog and HART PV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Analog and HART by Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Chapter 8
1756-OF8IH HART Isolated Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Analog Output Module Input Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Powerup State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Fault Mode Output State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Ramping/Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Hold for Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Open Wire Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Clamping (Limiting). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Clamp and Limit Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Data Echo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
HART Device Auto-configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Write HART Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Wire the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Output Circuit Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
1756-OF8IH Module Fault and Status Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
1756-OF8IH Module Fault Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Module Fault Word Bits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Channel Fault Word Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Channel Status Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Module Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Module Calibration Via Logix Designer Application. . . . . . . . . . . . . . . . . . . . . . . . . 120
Module Calibration Via Output Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Module-defined Data Types, 1756-OF8IH Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Chapter 9
Configure and Calibrate Modules Add a New Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Configure Your Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
HART Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
View Module Information and Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Coordinated System Time (CST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Refresh or Reset Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Apply Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Set Module Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Use the Channels View To Configure Multiple Channels . . . . . . . . . . . . . . . . . . . . . . . . 136
Channels View - Input Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Channels View - Output Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Use the ChX View To Configure a Single Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
ChX View - Input Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
ChX View - Output Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Scaling to Engineering Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Scaling High and Low Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Scaling High Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Scaling Low Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Scaling Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Set Module Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Set Input Module Alarms - 1756-IF8H, 1756-IF8IH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Set Output Module Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Limits Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Configure HART Field Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
View HART Device Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Set HART Device Information (1756-IF8IH and 1756-OF8IH Modules). . . . . . . . . . . 153
Calibrate Your Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Chapter 10
HART Data in the Input Tags HART Dynamic Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
How the Module Automatically Collects Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Chapter 11
Use a CIP MSG to get HART Data Use MSG Instructions to Access the HART Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
CIP Services to Access Common HART Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Read Dynamic Variables (Service Code = 16#4B) . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Chapter 12
Use HART Modules with Asset Considerations for Asset Management Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Management Software Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Chapter 13
Use Ladder Logic to Unlatch Using Message Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Alarms and Reconfigure Values Processing Real-time Control and Module Services . . . . . . . . . . . . . . . . . . . . . . . . 183
One Service Performed Per Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Creating a New Tag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Enter Message Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Unlatch Alarms in the 1756-IF8H or 1756-IF8IH Module. . . . . . . . . . . . . . . . . . . . . . . . . . 189
Unlatch Alarms in the 1756-OF8H or 1756-OF8IH Module . . . . . . . . . . . . . . . . . . . . . . . . 191
Reconfigure a Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Chapter 14
Troubleshoot the Module Use Module Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
General Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Use the Logix Designer Application to Troubleshoot a Module . . . . . . . . . . . . . . . . . . . 197
Module Configuration Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Additional Fault Codes - Module Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Additional Fault Codes - Channel Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Remove the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Appendix A
Use 1492 Wiring Systems with Wiring System Uses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Your Analog I/O Module
Appendix B
Additional HART Protocol Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Information Master-slave Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Multiple Master Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Transaction Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Burst Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Response Code and Field Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
HART PV, SV, TV, and FV Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Appendix C
Manufacturer Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Codes
Appendix D
Engineering Unit Code Numbers Code Number Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Appendix E
Remote Connections Via a Using RSNetWorx and RSLogix 5000 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
ControlNet Network Remote Input Modules Connected Via ControlNet Network. . . . . . . . . . . . . . . . . . . . . . 224
Remote Output Modules Connected Via ControlNet Network . . . . . . . . . . . . . . . . . . . . 225
Appendix F
Configure and Calibrate Modules Add a New Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
With Older Programming Customize Your Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
HART Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Software
Set Module Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
View Module Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Coordinated System Time (CST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Refresh or Reset Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Apply Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Configure Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Configure Individual Input Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Configure Individual Output Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Scaling to Engineering Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Configure All Input Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Configure All Output Module Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Module Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Set Input Module Alarms - 1756-IF8H, 1756-IF8IH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Set Output Module Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Ramp Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Output State in Program Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Output State in Fault Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Communication Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Set Output Module Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Set HART Command - 1756-IF8IH, 1756-OF8IH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
View HART Device Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Set HART Device Information (1756-IF8IH and 1756-OF8IH Modules). . . . . . . . . . . 248
Calibrate a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
About This Publication This manual describes how to install, configure, and troubleshoot ControlLogix® HART
(Highway Addressable Remote Transducer) analog I/O modules.
We assume that you can program and operate an Allen-Bradley® ControlLogix programmable
automation controller. If you can’t, see the Logix 5000® controller documentation that is listed
under Additional Resources before attempting to use these modules.
Rockwell Automation recognizes that some of the terms that are currently used in our industry
and in this publication aren’t in alignment with the movement toward inclusive language in
technology. We’re proactively collaborating with industry peers to find alternatives to such
terms and making changes to our products and content. Please excuse the use of such terms
in our content while we implement these changes.
Download Firmware, AOP, Download firmware, associated files (such as AOP, EDS, and DTM), and access product release
notes from the Product Compatibility and Download Center at rok.auto/pcdc.
EDS, and Other Files
Summary of Changes This publication contains the following new or updated information. This list includes
substantive updates only and is not intended to reflect all changes.
Topic Page
Removed 1756-IF8IH, 1756-OF8IH, and 1756-IF16H from the lists of modules compatible with the 11, 15, 202
1492 analog interface module (AIFM) wiring system
Added information regarding Implicit Protected Mode 26
Updated screen captures and procedures regarding how to Configure and Calibrate Modules 129
Created Appendix for information regarding ControlNet® information 223
Created Appendix for Configure and Calibrate Modules With Older Programming Software 227
Added Calibration information to new Appendix regarding how to Configure and Calibrate 249
Modules With Older Programming Software
Updated to include 1756-IF8H and 1756-IF16H Series B module information Throughout
Added conformal coated product catalog numbers Throughout
Additional Resources These documents contain additional information concerning related products from Rockwell
Automation. You can view or download publications at rok.auto/literature.
Resource Description
1756 ControlLogix I/O Modules Specifications Technical Data, Provides specifications for ControlLogix I/O modules, including the HART analog I/O
publication 1756-TD002 modules.
Bulletin 1492 Digital/Analog Programmable Controller Wiring Systems Provides information for the AIFMs and pre-wired cables that can be used with the
Technical Data, publication 1492-TD008 1756-IF8H, 1756-IF16H, and 1756-OF8H modules.
ControlLogix System User Manual, publication 1756-UM001 Provides configuration and operational procedures for ControlLogix controllers.
Electronic Keying in Logix 5000 Control Systems Application Technique, Provides information on Electronic Keying in Logix 5000 control systems.
publication LOGIX-AT001
Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1 Provides general guidelines for installing a Rockwell Automation industrial system.
Product Certifications website, rok.auto/certifications. Provides declarations of conformity, certificates, and other certification details.
ControlLogix® HART analog I/O modules connect a Logix controller to your process. HART input
modules (1756-IF8H, 1756-IF8HK, 1756-IF8IH, 1756-IF8IHK, 1756-IF16H, 1756-IF16HK, 1756-IF16IH,
and 1756-IF16IHK) receive signals from process value transmitters and convert them to
corresponding measurement values for use in the Logix controller (for example, temperature,
flow, pressure, or pH). HART output modules (1756-OF8H, 1756-OF8HK, 1756-OF8IH, and
1756-OF8IHK) provide current or voltage output signals that adjust the settings of valves and
other devices in accord with desired process behavior.
Instruments that support the HART protocol allow several process parameters to be measured
with one field device, provide status and diagnostics information, and allow remote
configuration and troubleshooting.
Catalog numbers followed by a “K” indicate ControlLogix HART analog I/O modules
available with a conformal coating option. These modules have the same features
as their regular counterparts, along with extended protection for use in harsh,
corrosive environments.
Module Components This figure shows the physical features of ControlLogix analog I/O modules.
5
ANALOG INPUT 1756-IF16H
CAL IN
3 FLT O
K
OK IN
FLT
HART
6
4
1
Item Description
1 Backplane connector - Connects the module to the ControlBus™ backplane.
2 Connector pins - Input/output, power, and ground connections are made through these pins with the
use of an RTB (removable terminal block) or IFM (interface module).
3 Locking tab - Anchors the RTB or IFM cable on the module, which helps to maintain wire connections.
Slots for keying - Mechanically key the RTB to help prevent inadvertently making the wrong wire
4 connections to the module.
Status indicators - Display the status of communication, module health, and input and output devices.
Use these indicators to help in troubleshooting. Some modules offer calibration and module status-only
5 indicator LEDs, whereas other modules offer additional per-channel status and fault indicator LEDs. For
more information, see Use Module Indicators on page 193.
6 Top and bottom guides - Help to seat the RTB or IFM cable onto the module.
Module Accessories These modules mount in a ControlLogix chassis and use a separately ordered removable
terminal block (RTB) or 1492 analog interface module (AIFM) to connect all field-side wiring.
The ControlLogix HART analog I/O modules use one of the following RTBs and support these
AIFMs.
Module RTBs(1) AIFMs(2)
• 1492-AIFM8-3 (current and voltage)
• 1756-TBCH 36-position cage clamp RTB
1756-IF8H • 1492-AIFM8-F-5 (current and voltage)
• 1756-TBS6H 36-position spring clamp RTB
• 1492-RAIFM8-3 (current and voltage)
• 1756-TBCH 36-position cage clamp RTB
1756-IF8IH N/A
• 1756-TBS6H 36-position spring clamp RTB
• 1756-TBCH 36-position cage clamp RTB
1756-IF16H • 1492-AIFM16-F-3 (current and voltage)
• 1756-TBS6H 36-position spring clamp RTB
• 1756-TBCH 36-position cage clamp RTB
1756-IF16IH N/A
• 1756-TBS6H 36-position spring clamp RTB
• 1756-TBNH 20-position NEMA RTB • 1492-AIFM8-3 (current and voltage)
1756-OF8H
• 1756-TBSH 20-position spring clamp RTB • 1492-RAIFM-8-3 (current and voltage)
• 1756-TBCH 36-position cage clamp RTB
1756-OF8IH N/A
• 1756-TBS6H 36-position spring clamp RTB
(1) Use an extended-depth cover (1756-TBEz) for applications with heavy gauge wiring or requiring additional routing space.
(2) See the AIFMs for the respective modules on page 202. Consult the documentation that came with it to connect all wiring.
ATTENTION: The ControlLogix system has been agency certified with only the
ControlLogix RTBs (catalog numbers 1756-TBCH, 1756-TBS6H, 1756-TBNH, and
1756-TBSH). Any application that requires agency certification of the
ControlLogix system with other wiring termination methods can require
application-specific approval by the certifying agency.
Key the Removable Wedge-shaped keying tabs and U-shaped keying bands come with your RTB to help prevent
connecting the wrong wires to your module. Key the positions on the module that correspond
Terminal Block/Interface to unkeyed positions on the RTB. For example, if you key the first position on the module, leave
Module the first position on the RTB unkeyed.
1. To key the module, insert the U-shaped band and push the band until it snaps into
place.
U-shaped Bands
2. To key the RTB/IFM, insert the wedge-shaped tab with the rounded edge first and push
the tab until it stops.
Wedge-shaped Tab
HART Communication The HART field communication 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 on the 4…20 mA current loop to provide two means of
communication from the device. The 4…20 mA analog channel lets the primary process
variable be communicated at the fastest possible rate while the digital channel communicates
multiple process variables, data quality, and device status. The HART protocol lets these
simultaneous communication channels be used in a complementary fashion.
The ControlLogix HART analog I/O modules support the HART protocol and perform these
operations:
• Conversion of 4…20 mA analog signals to digital numeric values in engineering units
(such as kg, m, or percent) that are used in the Logix controller.
• Conversion of digital numeric values in engineering units to 4…20 mA analog signals to
control process devices.
• Automatic collection of dynamic process data from the connected HART field device
(for example, temperature, pressure, flow, or valve position).
• Facilitation of configuration and troubleshooting of the HART field device from your
control room with FactoryTalk® AssetCentre service.
+0.5 mA
The Highway Addressable Remote Transducer
HART Signal
(HART) protocol supports two-way digital 0
communication, complements traditional 4…20 mA 4 mA
0.5 mA
analog signals, and includes the following features:
1200 220
• Predefined commands
Hz "1" Hz "0"
- Common practice
- General purpose
Analog
- Device specific
Signal
• Large installed base
• Worldwide support
Analog
20 mA Signal
0 1 Time (seconds) 2
(1) The figure is from the HART Communication Protocol Specifications, April 2001, Revision 6.0, HART Communication
Foundation, All Rights Reserved.
With the ControlLogix HART analog I/O modules, both the controller and software for device
maintenance and management can access field device data.
The ControlLogix HART analog I/O modules can accept commands from either of two master
devices. The controller is one of the master devices and continuously obtains information
from the field device. The second master can be used for device maintenance, for example a
handheld communicator, as shown here.
Primary Master
Secondary Master
(handheld communicator as
secondary master)
Slave
Device status information is also provided via HART. Instead of one process variable, with
HART the controller sees four process variables, has a check on the mA signal, and has a
reading of device status. HART connectivity provides all this information with no changes to
the existing 4…20 mA wiring.
FDT/DTM technology via HART connectivity also provides remote configuration and
troubleshooting of field devices by using software such as FactoryTalk AssetCentre or
Endress+Hauser FieldCare software.
Asset Management You can use the HART analog I/O modules with asset management software, such as
FactoryTalk AssetCentre software or Endress+Hauser FieldCare software. For more
Software information, see Use HART Modules with Asset Management Software on page 181.
Timestamping Controllers in 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 time stamp input data or output echo data when the module multicasts to the
system.
This feature provides accurate calculations of time between events to help you identify the
sequence of events in fault conditions or in the course of normal
I/O operation. The system clock can be used for multiple modules in the same chassis.
Each module maintains a rolling time stamp that is unrelated to the coordinated system time.
The rolling time stamp is a continuously running 15-bit timer that counts in milliseconds.
When an input module scans its channels, it also records the value of the rolling time stamp.
Your program can use the last two rolling time stamp values to calculate the interval between
receipt of data or the time when new data was received.
For output modules, the rolling time stamp value is updated only when new values are applied
to the Digital to Analog Converter (DAC).
Module Scaling Use module scaling to specify the range of engineering units that corresponds to the analog
input or output signal of a module. Choose two points along the module operating range and
specify corresponding low and high engineering unit values for those points.
Scaling lets you configure the module to return data to the controller in units that match the
quantity being measured. For example, an analog input module can report temperature in
degrees Celsius or pressure in mbar. An analog output module can receive commands in the
stroke % of a valve. Scaling makes it easier to use the values in your control program instead
of using the raw signal value in mA.
For more information about scaling, see Scaling to Engineering Units on page 143.
Electronic Keying Electronic Keying reduces the possibility that you use the wrong device in a control system. It
compares the device that is defined in your project to the installed device. If keying fails, a
fault occurs.
Attributes Compared During Electronic Keying
Attribute Description
Vendor The device manufacturer.
Device Type The general type of the product, for example, digital I/O module.
Product Code The specific type of the product. The Product Code maps to a catalog number.
Major Revision A number that represents the functional capabilities of a device.
Minor Revision A number that represents behavior changes in the device.
Carefully consider the implications of each keying option when selecting one.
For more detailed information on Electronic Keying, see Electronic Keying in Logix 5000 Control
Systems Application Technique, publication LOGIX-AT001.
A ControlLogix® controller must own every I/O module in the ControlLogix system. The owner
controller stores configuration data for every module that it owns. The owner controller can be
located locally (in the same chassis) or remotely (in another chassis), relative to the position of
the I/O module. The owner controller sends configuration data to the I/O module to define the
behavior of the module 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 multiple
owners. Output modules are limited to one owner.
With the Producer/Consumer model, ControlLogix I/O modules can produce data without a
controller polling them first. The modules produce the data and any owner or listen-only
controller device can consume it.
For example, an input module produces data and any number of controllers can consume the
data simultaneously. This feature minimizes the need for one controller to send data to
another controller.
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 an owner controller downloads module configuration data, the controller attempts to
establish a direct connection to each of the modules the data references.
If a controller has configuration data that references a slot in the control system, the
controller periodically checks for the presence of a module there. When the presence of a
module 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 isn’t appropriate, the module rejects the data and an error
code displays in the software. For example, configuration data for a module can be
appropriate except for a mismatch in electronic keying that prevents normal operation.
For more information about error codes, see Module Configuration Errors on page 198.
The controller maintains and monitors its connection with a module. Any break in the
connection (for example, module removal under power) causes the controller to set fault
status bits in the data area that is associated with the module. You can use ladder logic to
monitor this data area and detect module failures.
Input Module Operation In the ControlLogix system, 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 that are chosen during configuration and the physical location of the
module in the control system.
The communication or multicasting behavior of a module varies depending upon whether the
module operates in a local or remote chassis (relative to the owner controller), based on
network type. The following sections detail the differences in data transfers between these
setups.
Input Modules in a 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:
Local Chassis
• Real-time sample (RTS)
• Requested packet interval (RPI)
Onboard Memory
Status Data
Time stamp
IMPORTANT The real-time sample value is set during the initial configuration with
the Studio 5000 Logix Designer® application. This value can be
adjusted at any time.
This configurable parameter also instructs the module to multicast the current contents of
its onboard memory when the requested packet interval expires. (The module does not update
its channels before the multicast.)
Onboard Memory
Status Data
Time stamp
IMPORTANT The requested packet interval value is set during the initial module
configuration with the Logix Designer application. This value can be
adjusted when the controller is in Program mode.
If the real-time sample value is less than or equal to the requested packet interval, each
multicast of data from the module has updated channel information. In effect, the module is
only multicasting at the real-time sample rate.
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 requested 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 below, the real-time sample value is 100 ms and the requested packet interval
value is 25 ms. Only each fourth multicast from the module contains updated channel data.
25 50 75 100 125 150 175 200 225 250 275 300 325 350 375 400
Time (ms)
A ControlLogix analog I/O module can trigger event tasks each real-time sample, after the
module has sampled and multicast its data. Event tasks are useful for synchronization of
process variable (PV) samples and proportional integral derivative (PID) calculations.
IMPORTANT ControlLogix analog I/O modules can trigger event tasks at each
real-time sample, but not at the requested packet interval. For
example, in the figure, an event task can be only triggered each 100 ms.
Input Modules in a For an input module in a remote chassis, the roles of requested packet interval and real-time
sample behavior change slightly regarding data communication to the owner controller. This
Remote Chassis change depends on what network type is used to communicate with the modules.
The Ethernet module either multicasts the module data to all devices on the network or
unicasts to a specific owner controller depending on the setting of the Unicast option, as
shown on page 135.
For more information, see the Guidelines to Specify an RPI Rate for I/O Modules
section in the Logix 5000 Controllers Design Considerations Reference Manual,
publication 1756-RM094.
Output Module Operation The RPI parameter governs 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 once per RPI. Data isn’t sent to the module at the end of the controller
program scan.
When an analog output module receives new data from an owner controller (each RPI), it
automatically multicasts, or echoes, a data value to the rest of the control system. This data
value corresponds to the analog signal present at the output terminals of the module. This
feature, called Output Data Echo, occurs whether the output module is local or remote.
If the output module isn’t responding according to how it has been programmed, it
could be for one of the following reasons:
• The commanded value falls outside the Configured Limits and is therefore being
clamped.
• The commanded value changed faster than the configured max Rate Limit, and is
being clamped.
• The module is in Start-up Hold mode following a connection break or Run mode
transition. The module is waiting for the control system to synchronize with the
prevailing setting to facilitate a bumpless startup.
Depending on the length of the RPI relative to the length of the controller program scan, an
output module can receive and echo data multiple times during one program scan. The output
module does not wait for the end of the program scan to send data. When RPI is less than
program scan length, the controller effectively lets the module output change values multiple
times during one program scan.
Output Modules in a By specifying an RPI value for an analog output module, you instruct the controller when to
broadcast output data to the module. If the module resides in the same chassis as the owner
Local Chassis controller, the module receives the data almost immediately after the controller sends it.
Owner Controller Output Module
Output Modules in a For output modules in remote chassis, the role of RPI in getting data from the owner controller
changes slightly, depending on the network.
Remote Chassis
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 RPI, the owner controller multicasts data within its own chassis.
• The EtherNet/IP communication module in the local chassis immediately sends the
data over the network to the analog output module. This condition occurs as long as it
hasn’t sent data within a time frame that is 1/4 the value of the requested packet
interval of the analog module.
Listen-only Mode Any controller in the system can listen to the data from any I/O module (input data or echoed
output data) even if the controller does not own the module. The controller does not have to
own the configuration data of a module to listen to it.
During the I/O configuration process, you can specify a ‘Listen-Only’ mode as the Connection
type on the Device Definition dialog. See page 131 for more details.
In Listen-Only mode, the controller and module establish communication without the controller
sending any configuration data. Another controller owns the module being listened to.
Implicit Protected Mode When in Implicit Protected Mode, a module is operational, but has implemented defenses
against disruptive changes that would take the product out of service for the process.
Implicit Protected Mode is a security enhancement that occurs on the I/O module level and
helps prevent unauthorized changes that can affect system behavior.
When in Implicit Protected Mode, the module helps prevent execution of the following tasks:
• Updating the module firmware revision
• Calibration
Implicit Protected Mode Availability and Calibration Exceptions
Module 1756-IF8H 1756-IF8IH 1756-IF16H 1756-IF16IH 1756-OF8H 1756-OF8IH
Series A B A A B A A A
Implicit Protected Mode Available? No Yes Yes No Yes Yes No Yes
Can Calibrate in Run Mode Using Output Tags When In Implicit Protected Mode?(1) - - Yes - - - - Yes
Can Calibrate in Run Mode Using Output Tags When Not In Implicit Protected Mode? - - No - - - - No
(1) For more information about using Output tags to calibrate the 1756-IF8IH and 1756-OF8IH modules, see page 58 and page 120.
Multiple Owners of Because listening controllers lose their connections to modules when communication with the
owner stops, the ControlLogix system lets you define multiple owners for input modules.
Input Modules
IMPORTANT Only input modules can have multiple owners. If multiple owners are
connected to the same input module, they must maintain an identical
configuration for that module.
In this example, Controller A and Controller B have both been configured as an owner of the
input module.
Multiple Owners with Identical Configuration Data
Controller A Input Module Controller B
When multiple controllers are configured to own the same input module, the following events
occur:
• When the controllers begin to download configuration data, both try to establish a
connection with the input module.
• The controller data that arrives first establishes a connection.
• When data from the second controller arrives, the module compares it to its current
configuration data (the data that was received and accepted from the first controller).
- If the configuration data that the second controller sends matches the configuration
data that the first controller sends, the connection is also accepted.
- If any parameter of the second configuration data differs from the first, the module
rejects the connection. The Logix Designer application alerts you to the rejected
connection through an error message.
The module can continue to operate and multicast data even when one of the controllers loses
its connection to the module. This feature is the advantage of multiple owners over a Listen-
only connection.
Configuration Changes in an You must be careful when you change the configuration data of an input module in a multiple
owner scenario. When the configuration data is changed in one of the owners, for example,
Input Module with Multiple Controller A, and sent to the module, that configuration data is accepted as the new
Owners configuration for the module. Controller B continues to listen, unaware that any changes were
made in the behavior of the module.
Controller A Input Module Controller B
Unicast Communication Use unicast EtherNet/IP communication to reduce broadcast network traffic. Some facilities
block multicast Ethernet packets as part of their network administration policy. You can
configure multicast or unicast connections for
I/O modules by using the Logix Designer application, version 18 or later.
IMPORTANT The Analog and HART by Channel data type is available only for
1756-IF8H firmware revision 2.002 or later.
• Multiple current and voltage input ranges
• Module filter
• Real-time sampling
• Underrange and overrange detection
• Process alarms
• Rate alarm
• Wire-off detection
• Highway addressable remote transducer (HART) communication
Select Analog and HART PV if you prefer the members of the tag to be arranged similar to non-
HART analog input modules. The analog values for all channels are grouped near the end of the
tag. This option makes it easy to view all eight analog values at once.
Select Analog and HART by Channel if you prefer Status, Analog Value, and Device Status for
each channel to be together in the tag. This arrangement makes it easier to view all data that
is related to one field device.
Input Ranges
You can select from a series of operational ranges for each channel on the 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 range.)
Module Filter
The module filter attenuates the input signal at the specified frequency and above. This
feature is applied on a module-wide basis and affects all channels.
The module filter 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.
0.707
0 60 Hz
In addition to frequency rejection, a by-product of the filter selection is the minimum sample
rate (RTS) that is available. For example, the 1000 Hz selection does not attenuate any
frequencies less than 1000 Hz, and provides for sampling of all 8 channels within 18 ms. The
10 Hz selection attenuates all frequencies above 10 Hz and provides for sampling all 8 channels
only within 488 ms.
Real-time Sampling
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.
This table shows the input ranges of the 1756-IF8H module and the lowest and highest signal
available in each range before the module detects an underrange and overrange condition.
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’s specified in units of milliseconds. A value of 0 disables the filter.
This figure illustrates the filter response to a step input. 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 to a Step Input
Process Alarms
Process alarms alert you when the module has exceeded configured high or low thresholds for
each channel. You can latch process alarms. These alarms are set at the following
configurable 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 disappearance of the alarm condition, as long
as the input remains within the process alarm deadband.
This figure shows input data that sets each of the alarms at some point during module
operation. In this example, Latching is disabled; therefore, each alarm turns OFF when the
condition that caused it to set returns to normal.
Input Data That Sets Each of the Alarms
High high
High alarm High alarm turns OFF
turns ON
High
Low low
Rate Alarm
The value for the Rate Alarm Limit is 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. Rate Alarm uses the signal value after
filtering by the Module Filter and before the Digital Filter is applied.
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 can 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.
This table identifies the conditions that are reported in the input tag when a wiring anomaly is
detected.
Wire-off Detection
Condition Reported in Input Tag
Input Range Wiring Problem
Input Data Changes to ChXOverrange ChXBrokenWire ChXUnderrange
-10V…+ 10V
Voltage 0V …+5V INx or INx removed Maximum scaled value 1 1
(overrange value)
0V…+10V
RTB removed or INx and Maximum scaled value 1 1
I RTN-x jumper removed (overrange value)
Minimum scaled value
0…20 mA Only INx removed (jumper in place) 0 1
(underrange value)
Maximum scaled value
Only jumper removed 1 1
(overrange value)
Current
RTB removed or INx and Maximum scaled value 1 1
I RTN-x jumper removed (overrange value)
Minimum scaled value
4…20 mA Only INx removed (jumper in place) 1 1
(underrange value)
Maximum scaled value
Only jumper removed 1 1
(overrange value)
Wire the Module Use this figure to wire the module for voltage and current inputs. HART communication is
active with current inputs only.
1756-IF8H Voltage and Current Inputs
Voltage Inputs Current Inputs
Voltage Input
+V
2-wire Current Input
IN0+ 2 1 I RTN-0 2-wire
-V IN0- 4 3 NC 24V DC
+ +-
IN0+ 2 1 I RTN-0
IN1+ 6 5 I RTN-1 Power
Supply- IN0- 4 3 NC
IN1- 8 7 NC
IN1+ 6 5 I RTN-1
RTN 10 9 RTN
IN1- 8 7
IN2+ 12 11 I RTN-2 4-wire Current Input NC
RTN 10 9 RTN
IN2- 14 13 NC
24V DC
+ + 4-wire
+ IN2+ 12 11 I RTN-2
IN3+ 16 15 I RTN-3 Power
Supply- MTR IN2- 14 13 NC
IN3- 18 17 NC - -
IN3+ 16 15 I RTN-3
IN4+ 20 19 I RTN-4
IN4- 22 21 NC IN3- 18 17 NC
IN4+ 20 19 I RTN-4
Table 1 - IN5+ 24 23 I RTN-5
Table 1 - IN4- 22 21 NC
IN5- 26 25 NC
Channel Usage Pin # RTN 28 27 RTN Channel Usage Pin # IN5+ 24 23 I RTN-5
26 25
IN0+ 2 IN6+ 30 29 I RTN-6
iRTN0 1
IN5- NC
0 IN6- 32 31 NC RTN 28 27 RTN
IN0- 4 0 IN0+ 2
IN7+ 34 33 I RTN-7 IN6+ 30 29 I RTN-6
IN1+ 6 IN0- 4
1 IN7- 36 35 NC IN6- 32 31 NC
IN1- 8 iRTN1 5 IN7+ 34 33 I RTN-7
IN2+ 12 1 IN1+ 6 IN7- 36 35 NC
2
IN2- 14 IN1- 8
IN3+ 16 iRTN2 11
3
IN3- 18 2 IN2+ 12
IN4+ 20 IN2- 14
4
IN4- 22 iRTN3 15
IN5+ 24 3 IN3+ 16
5
IN5- 26 IN3- 18
IN6+ 30 iRTN4 19
6
IN6- 32 4 IN4+ 20
IN7+ 34 IN4- 22
7
IN7- 36 iRTN5 23
5 IN5+ 24
IN5- 26
iRTN6 29
6 IN6+ 30
IN6- 32
iRTN7 33
7 IN7+ 34
IN7- 36
The 1756-IF8H is a differential input module. However, there are limitations on its use in
differential mode. Anytime the low ends of the terminal block pins are connected together,
they must also be jumpered to the RTN pin on the terminal block. There are two scenarios in
which this condition happens.
First, if one power supply is used for multiple devices, then the low ends from all channels are
connected together and connected to the ground return of the power supply.
Single Power Supply with Multiple HART Devices
IN0+ IRTN-0
+ HART
Power Supply 1 Device 1
IN0-
-
IN1+ IRTN-1
HART
Device 1
IN1-
RTN
The second way for channels to share a ground is to have multiple power supplies connected
to the same ground. In this case, the low ends of the channels are effectively connected
together by the common ground of the power supplies.
Multiple Power Supplies with a Common Ground
IN0+ IRTN-0
+ HART
Device 1
Power Supply 1 IN0-
-
RTN
For devices powered by individual supplies, when the ground potential of the supplies is
expected to differ, differential mode is recommended. This practice helps prevent ground loop
currents from flowing between the supplies. However, the potential difference allowable
between the supplies must remain within specified limits.
Power Supplies with Isolated Grounds
IN0+ IRTN-0
+ HART
Device 1
Power Supply 1
IN0-
-
Ground wires isolated
from each other IN1+ IRTN-1
HART
+ Device 1
Power Supply 1 IN1-
-
RTN
The low ends of the terminal block pins are now isolated from each other. The inputs can
be configured as true differential inputs as long as the voltage difference between them
does not exceed 7V.
Circuit Diagrams This section shows circuit diagrams for the 1756-IF8H module.
Simplified 1756-IF8H Current Input Circuit
+15V
10 M
22 K
INO+
+
Analog to
i 249 Digital
IRTN-O 1/4 Watt -
Jumper Converter
Differential 0.01 F 0.01 F
Current Input
INO-
22 K
10 M
-15V
RTN
RTN
RTN
RTN
+15V
10 M 22 K
INO+ +
Analog to
Differential 249
- Digital
Voltage + I RTN-O 1/4 Watt Converter
Inputs V
0.01 F 0.01 F
-
INO-
22 K
10 M
-15V
RTN
RTN
RTN
RTN
1756-IF8H Module Fault and 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 to examine fault
Status Reporting conditions. Three levels of tags work together to provide an increasing degree of detail as to
the specific cause of faults on the module.
This table lists tags that you can examine in ladder logic to indicate when a fault has occurred.
1756-IF8H Tags That Can Be Examined in Ladder Logic
Tag Name Tag Name
Tag Description Analog and HART PV Analog and HART by Channel(1)
Module Fault Word This word provides fault summary reporting. ModuleFaults ModuleFaults
ChannelFaults ChannelFaults
Channel Fault Word This word provides underrange, overrange, and communication fault reporting. ChxFault ChxFault
Channel Status Word These words provide individual channel underrange and overrange fault Chx.DeviceStatus
ChxStatus
indications and report process alarms, rate alarms, and calibration faults. Chx.DeviceStatus.AlarmStatus
HART Faults These bits provide HART communication status. HARTFaults, ChxHARTFault Chx.DeviceStatus.HARTFault
HART Device Status This data reports HART field device health. HART.ChxDevice Status Chx.DeviceStatus.FieldDeviceStatus
(1) Available only for 1756-IF8H firmware revision 2.002 or later
Module Faults
6, 5, 4, and 0 aren’t used for fault reporting When the module is calibrating, all bits in the Channel Fault word are set.
7 6 5 4 3 2 1 0
Analog Updated Calibrating CalFault
GroupFault StatusReady
If set, any bit in the Channel Fault word also sets the Analog
Channel Faults Group Fault in the Module Fault word.
7 6 5 4 3 2 1 0
Ch7Fault Ch6Fault Ch5Fault Ch4Fault Ch3Fault Ch2Fault Ch1Fault Ch0Fault
Ch7
Ch6
Ch5
Ch4
Ch3
Ch2
7 6 5 4 3 2 1 0
CalFault Underrange Overrange RateAlarm LAlarm HAlarm LLAlarm HHAlarm Ch1
Ch0
Channel Status Tags Alarm bits 0…4 in the Channel Status word do not set other bits at any higher
One set of tags for each channel level. Monitor these conditions here.
This table lists conditions that set all Channel Fault word bits.
Module Calibration You can initiate calibration of the 1756-IF8H module via the Logix Designer application
Calibration view.
The Calibration view in the Logix Designer application provides a button to initiate module
calibration and a display of the results. Refer to Calibrate Your Module on page 154 for more
information.
1756-IF8H Tag Definitions This section describes the module-defined data types for the 1756-IF8H module and includes
information for configuration and input tags.
Available tags depend on the selected input data format, as shown in this table.
Configuration
This table describes the configuration tags available in the 1756-IF8H module.
1756-IF8H Configuration Tags - (AB:1756_IF8H:C:0)
Member Name Type Style Description
ModuleFilter SINT Decimal See the Series A Module Filter Selections with Associated Performance Data table on page 31.
(bits 0…7)
RealTimeSample INT Decimal Milliseconds between reading signal values. See Real Time Sample (RTS) on page 22 for more information.
(bits 0…15)
ChxConfig (x=0…7) AB:1756_IF8H_ChConfig_Struct:C:0
Config SINT Binary
BOOL Decimal Ch0Config.Config.4, After a Rate Alarm is detected, keep I.ChxRateAlarm set even after Rate returns to normal, until
RateAlarmLatch unlatched by CIP™ Service Message.
Ch0Config.Config.5, After a Process Alarm such as LL is detected, keep I.ChxLLAlarm set even after measurement
ProcessAlarmLatch BOOL Decimal returns to normal, until unlatched by CIP Service Message.
AlarmDisable BOOL Decimal Ch0Config.Config.6, Do not report Process or Rate Alarms.
BOOL Decimal Ch0Config.Config.7, Enable HART communication. Must be 1 for valid HART data in Input Tag and Asset Management
HARTEn access to HART Field Device.
0 = -10…+10 V.
1 = 0…5 V.
RangeType SINT Decimal 2 = 0…10 V.
3 = 0…20 mA.
4 = 4…20 mA.
DigitalFilter INT Decimal Time Constant of low pass filter in ms. See Digital Filter on page 32 for more information.
Analog Only
This table describes the input tags available in the Analog Only data format.
1756-IF8H Input Tags - Analog Only (AB:1756_IF8H_Analog:I:0)
Member Name Type Style Description
Indicates a problem with analog data on Channel x or broken communication between the Logix controller and the 1756-
ChannelFaults INT Binary IF8H module. Example: Set if the analog signal is larger than 20 mA.
ChxFault BOOL Decimal ChannelFaults.0…ChannelFaults.7
(Ch0…Ch7)
ChannelFaults.8…ChannelFaults.15
ChxBrokenWire BOOL Decimal Indicates that current isn’t flowing through the module as expected. Broken wiring, RTB removal, or a powered-off field
(Ch0…Ch7) device can cause this indication.
Indicates a problem with HART data from the Field Device on Channel x.
HARTFaults Examples are HART not enabled, HART device not connected, HART communication failure due to noise.
SINT Binary
(Ch0…Ch7) These Field Device Status conditions also cause this to be set: Device Malfunction, PV Out of Limits, Loop Current
Saturated, and Loop Current Fixed.
ChxHARTFault BOOL Decimal HARTFaults.0…HARTFaults.7
ModuleFaults SINT Binary Module level fault status bits
CalFault BOOL Decimal (ModuleFaults.1) 1756-IF8H Module Calibration Failed.
Calibrating BOOL Decimal (ModuleFaults.2) Calibration in progress.
AnalogGroupFault BOOL Decimal (ModuleFaults.7) Indicates that a fault has occurred on any channel (any of ChannelFaults).
ChxStatus SINT Binary Indicates various alarms on the analog signal. Also sets Ch0Fault for Overrange, Underrange, and CalFault.
(Ch0…Ch7)
ChxStatus.0
ChxData > ChxHHAlarmLimit.
ChxHHAlarm BOOL If Process Alarms are configured to Latch by setting ChxConfig.ProcessAlarmLatch this bit remains set even after the
condition returns to normal, until reset via an explicit CIP message. This message can be sent from the Studio 5000
Logix Designer Module Properties Alarm dialog or from the Logix controller via a MSG instruction.
ChxStatus.1
ChxLLAlarm BOOL ChxData < ChxLLAlarmLimit
If ChxConfig.ProcessAlarmLatch is set, this alarm remains set until it’s unlatched
ChxStatus.2
ChxHAlarm BOOL ChxData > ChxHAlarmLimit
If ChxConfig.ProcessAlarmLatch is set, this alarm remains set until it’s unlatched
Notes:
Module Features The 1756-IF8IH module is an isolated, 8-channel, current-only input module capable of HART
communication on all channels. Each channel is individually configurable. The 1756-IF8IH
module has the following features:
• Eight isolated, individually configurable input channels with a separate HART modem on
each channel
• Channel-to-channel, channel-to-backplane, and channel-to-frame ground galvanic
isolation at a continuous level of 250V AC rms
• Two input ranges: 0...20 mA and 4...20 mA
• Choice of four data types:
- Analog Only
- Analog and HART PV
- Analog and HART by channel with Configure HART Device = No
- Analog and HART by channel with Configure HART Device = Yes
• Supports full simultaneous HART 1200 baud bandwidth to all channels
• Channel ADC filter (one setting per module)
• Digital filtering (configurable per channel)
• Real-time sampling
• Auto-scanning of HART variables (PV, SV, TV, FV)
• HART pass-through interface
• Option to configure a HART device with user-supplied data. You can configure PV
damping value, PV range values, PV transfer function, and PV units code. This option is
available only when the data format is Analog and HART by Channel with Configure HART
device = Yes
• User scaling of input data
• Time stamping
• Alarms and fault detection
- Open wire detection(4...20 mA range)
- Underrange and overrange detection
- Fault reporting
- Process and Rate alarms and alarm latching (if Configure HART Device = No)
- Status indicator information
• User Calibration via CIP™ messaging
• Calibration via output word (available only when the data format is Analog and HART by
Channel with Configure HART Device = Yes)
• Downloadable firmware using ControlFLASH™
• Add-on Profile (AOP)
• “Bumpless” configuration for a smooth transition in new configurations.
• Removal and insertion under power (RIUP)
HART Compatibility
The 1756-IF8IH functions as a HART master. It communicates with HART devices that have a
HART revision of 5, 6, or 7. Each channel has its own HART modem and functions as a HART
primary master.
The 1756-IF8IH module does not support burst mode, phase shift keying (PSK), or multi-drop
network configuration. The module detects and turns off a bursting device at initial
connection with the device.
Choose Analog and HART PV if you prefer the analog values for all channels to be grouped near
the end of the tag. This format makes it easy to view all eight analog values at once.
Choose Analog and HART by Channel if you prefer Status, Analog Value, and Device Status for
each channel to be together in the tag. This format makes it easier to view all data for one
field device.
Input Ranges
You can select one of two input ranges for each channel on the module. The range designates
the minimum and maximum signals that are detectable by the module. These are the possible
ranges:
• 0…20 mA
• 4…20 mA (HART instruments use this range.)
Module Filter
Each channel has an ADC filter that affects 50 Hz and 60 Hz rejection, noise, accuracy, and the
minimum sample time (RTS). The module filter attenuates the input signal at the specified
frequency and above.
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.
0.707
0 60 Hz
A by-product of the filter selection is the minimum available sample rate (RTS). For example,
the 1000 Hz selection does not attenuate frequencies less than 1104 Hz, but allows all
8 channels to be sampled within 15 ms. The 10 Hz selection attenuates all frequencies above
2.2 Hz but only allows all 8 channels to be sampled within 488 ms.
IMPORTANT 60 Hz is the default setting for the module filter. Do not use the 1000 Hz
module filter with HART instruments.
There’s one filter setting that is applied globally to all channels. Use this table to help choose a
filter setting.
Module Filter Selections with Associated Performance Data for 1756-IF8IH
Module Filter Setting (-3 dB) 10 Hz 15 Hz 20 Hz 50 Hz 60 Hz 100 Hz 250 Hz 1000 Hz
Minimum Sample Time (RTS ms) 488 328 275 115 115 61 25 15
Effective Resolution 18 bits 18 bits 18 bits 17 bits 17 bits 16 bits 16 bits 15 bits
(0…20 mA, 4…20 mA range) 0.08 A 0.08 A 0.08 A 0.16 A 0.16 A 0.32 A 0.32 A 0.64 A
-3 dB Frequency 2.2 Hz 11.5 Hz 13.8 Hz 34.5 Hz 34.5 Hz 69.0 Hz 221 Hz 1104 Hz
50 Hz Common Rejection 100 dB 100 dB
50 Hz Normal Rejection 95 dB 74 dB
60 Hz Normal Rejection 95 dB 74 dB 97 dB
60 Hz Common Rejection 100 dB 100 dB 100 dB
Channel ADC Update Rate (samples per second) 30 SPS 50 SPS 60 SPS 150 SPS 150 SPS 300 SPS 960 SPS 4800 SPS
Settling Time 100 ms 80 ms 66.7 ms 26.7 ms 26.7 ms 13.3 ms 4.17 ms 0.83 ms
Digital Filter
The digital filter smooths input data noise transients. There’s a separate digital filter for each
channel.
The digital filter value specifies the time constant in milliseconds for a digital first order lag
filter on the input. A value of 0 disables the filter.
This figure illustrates the filter response to a step input. 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 to a Step Input
Real-time Sampling
This parameter instructs the module how often to scan its input channels and obtain new
sampled data. After the channels are scanned, the module broadcasts that data (multicast or
unicast) to the local chassis backplane. 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). Both of these features instruct the module to broadcast data, but only
the RTS feature instructs the module to scan its channels before broadcasting.
For more RTS information, see Real Time Sample (RTS) on page 22.
This table shows the input ranges of the 1756-IF8IH module and the lowest and highest signal
available in each range before the module detects an underrange and overrange condition.
In the 0...20 mA range, an open-circuit condition results in a measured value of 0 mA, which is
the same as a measured value of 0 mA when there isn’t an open-circuit condition. The
appropriate Underrange bit is set but the ChxBrokenWire bit isn’t set.
The valid range of HART configuration values depends on the HART device that is connected to
the module. The Logix Designer application does not check that the values that are entered in
the HART Command view are appropriate. Confirm on your own that valid values for your HART
devices are used.
Rate Alarm
This feature isn’t available if Configure HART Device = Yes.
The value for the Rate Alarm Limit is entered in scaled engineering units per second. The rate
alarm triggers if the rate of change between input samples for a channel exceeds the
specified rate-alarm trigger point for that channel. Rate Alarm uses the signal value after
filtering by the Module Filter and before the Digital Filter is applied.
Process Alarms
This feature isn’t available if Configure HART Device = Yes.
This feature enables you to specify alarm limits for input level and have the module report
when those levels have been exceeded. It’s available only if Configure HART Device = No. In
module configuration, you specify values for high-high, high, low, and low-low limits. Process
alarms can be latched.
Only status bits in the input table are affected during runtime after a valid configuration; no
fault bit is set.
AlarmDeadband determines when the AlarmLimit bits are cleared. Once the bit is set by
exceeding the AlarmLimit, it can’t be cleared until the input has passed the deadband delta
from the AlarmLimit value. For example, if the deadband is 0.5 and the HAlarmLimit is 10.0, the
HAlarm status bit isn’t cleared until the input is 9.5 or less. Likewise, if the LAlarmLimit is 1.0,
the associated LAlarm bit would clear when the input is 1.5 or more for the same deadband
value.
Alarm bits are cleared when the input falls inside the specified Alarm Limit. The exception is
when ProcessAlarmLatch is set in the configuration. In that case, clearing alarm bits requires
the command ‘Unlatch Alarm Status’ be issued to all alarms or individual alarms.
Wire the Module This figure shows module wiring information. We recommend using a separate power supply
for each input to help maintain isolation.
1756-IF8IH Wiring Diagram
i
+ + Not Used 2 1 Not Used
4-wire IN0 4 3 IN1
24V DC
Transmitter
– RTN0 6 5 RTN1
– Reserved Reserved
8 7
Reserved 10 9 Reserved
IN2 12 11 IN3
Shield Ground
RTN2 14 13 RTN3
Reserved 16 15 Reserved
Reserved 18 17 Reserved
IN4 20 19 IN5
RTN4 22 21 RTN5
Reserved 24 23 Reserved
i Reserved 26 25 Reserved
2-wire – IN6 IN7
28 27
Transmitter
+ 24V DC RTN6 30 29 RTN7
+ – Reserved 32 31 Reserved
Reserved 34 33 Reserved
Shield Ground Not Used 36 35 Not Used
Circuit Diagram This figure is a simplified diagram of the input circuit that is used in the 1756-IF8IH module.
1756-IF8IH Simplified Input Circuit
Overcurrent protection
HART Tx and Rx
4 ~ 20 mA Transmitter
1756-IF8IH Module Fault and The 1756-IF8IH 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
Status Reporting conditions. Three levels of tags work together to provide an increasing degree of detail about
the cause of faults on the module. This figure offers an overview of how faults are reported.
1756-IF8IH Module Fault Reporting
When the module is calibrating, all bits in the
Module Faults
Channel Fault word are set.
6, 5, 4, and 0 aren’t used for fault reporting
7 6 5 4 3 2 1 0
Analog Updated Calibrating CalFault
GroupFault StatusReady
If set, any bit in the Channel Fault word also sets the Analog
Channel Faults Group Fault in the Module Fault word.
7 6 5 4 3 2 1 0
Ch7Fault Ch6Fault Ch5Fault Ch4Fault Ch3Fault Ch2Fault Ch1Fault Ch0Fault
Ch7
Ch6
Ch5
Ch4
Ch3
Ch2
7 6 5 4 3 2 1 0
CalFault Underrange Overrange RateAlarm LAlarm HAlarm LLAlarm HHAlarm Ch1
Ch0
Channel Alarm Status Tags Alarm bits 0…4 in the Channel/Alarm Status word do not set other bits at any higher level; monitor
(one set of tags per channel) these conditions here. These bits are available only when Configure HART Device = No.
This table lists tags that you can examine in ladder logic to indicate when a fault has occurred.
1756-IF8IH Tags That Can Be Examined in Ladder Logic
Tag Name Tag Name
Tag Description Analog and HART PV Analog and HART by Channel
Module Fault Word This word provides fault summary reporting. ModuleFaults ModuleFaults
This word provides underrange, overrange, and ChannelFaults ChannelFaults
Channel Fault Word communication fault reporting. ChxFault ChxFault
These words provide individual channel underrange and
Channel Status Word overrange fault indications and reporting for process ChxStatus Chx.DeviceStatus.AlarmStatus
alarms, rate alarms, and calibration faults.
HART Faults These bits provide HART communication status. HARTFaults Chx.DeviceStatus.HARTFault
HART Device Status This data reports HART field device health. HART.ChxDevice Status Chx.DeviceStatus.FieldDeviceStatus
This table lists conditions that set all Channel Fault word bits.
Module Calibration There are two ways to initiate calibration of the 1756-IF8IH module:
• Logix Designer application Calibration view
• Module Output Word
See Table on page 66 for descriptions of the tags in the 1756-IF8IH output word.
To perform a module calibration via the output word, set and clear bits in sequence to perform
the calibration tasks. This table shows 1756-IF8IH calibration bits.
Step Output Word Bit Description
The date that you want to be associated with this calibration;
Set the calibration date CalibrationDate typically the current date. Set the date before starting the
calibration.
Set this bit to initiate calibration, and keep it set until the
Initiate calibration ChxCalibrate calibration sequence is complete. If this bit clears before the
calibration is complete, the calibration is aborted.
ChxCalLowRef Perform low calibration at the low reference point (0.5 mA).
Perform low calibration Connect a valid low reference signal before setting this bit.
ChxCalHighRef Perform high calibration at the high reference point (20 mA).
Perform high calibration Connect a valid high reference signal before setting this bit.
ChxCalibrate
Abort calibration ChxCalLowRef Setting all three calibration bits aborts calibration.
ChxCalHighRef
Module-defined Data Types, This section describes module-defined data types for the 1756-IF8IH module and includes
information for configuration and input tags.
1756-IF8IH Module
Available tags depend on the selected input data format, as shown in this table.
1756-IF8IH Input Tags - Analog and HART by Channel, Configure HART Device = No (AB:1756_IF8IH_AnalogHARTbyChannel:I:0)
Member Name Type Style Description
BrokenWire BOOL Decimal Indicates that current isn’t flowing through the module as expected. Broken wiring, RTB removal, or a powered-off
field device can cause this.
Indicates a problem with HART data from the field device on Channel x. Examples are HART not enabled, HART
HARTFault BOOL Decimal device not connected, HART communication failure due to noise. These field device status conditions also cause
this to be set: Device Malfunction, PV Out of Limits, Loop Current Saturated, and Loop Current Fixed.
HART communication status byte or Response code from a recent HART reply.
ResponseCode SINT Binary See Response Code and Field Device Status on page 204 for more information.
HART device status byte from a recent HART reply. Indicates the health of the HART field device.
FieldDeviceStatus SINT Binary See Field Device Status Bit Mask Definitions on page 205 for more information.
PVOutOfLimits BOOL Decimal (FieldDeviceStatus.0) The primary variable is beyond its operating limit.
VariableOutOfLimits BOOL Decimal (FieldDeviceStatus.1) A device variable that is not mapped to the PV is beyond its operating limits.
(FieldDeviceStatus.2) The loop current has reached its upper or lower endpoint limit and can’t increase or decrease
CurrentSaturated BOOL Decimal any further.
CurrentFixed BOOL Decimal (FieldDeviceStatus.3) The loop current is being held at a fixed value and isn’t responding to process variations.
MoreStatus BOOL Decimal (FieldDeviceStatus.4) More status information is available via command 48, ‘Read Additional Status’ information.
ColdStart BOOL Decimal (FieldDeviceStatus.5) A power failure or device reset occurred.
Changed BOOL Decimal (FieldDeviceStatus.6) An operation was performed that changed the configuration of the device.
Malfunction BOOL Decimal (FieldDeviceStatus.7) The device detected a serious error or failure that compromises device operation.
AlarmStatus SINT Binary Channel x alarm status bits.
ChxData > ChxHHAlarmLimit.
If Process Alarms are configured to Latch by setting ChxConfig.ProcessAlarmLatch this bit remains set even after
HHAlarm BOOL Decimal the condition returns to normal, until reset via explicit CIP message. This message can be sent from the Studio
5000 Logix Designer Module Properties Alarm dialog or from the Logix controller via MSG instruction.
ChxData < ChxLLAlarmLimit.
LLAlarm BOOL Decimal If ChxConfig.ProcessAlarmLatch is set, this alarm remains set until it’s unlatched.
ChxData > ChxHAlarmLimit.
HAlarm BOOL Decimal If ChxConfig.ProcessAlarmLatch is set, this alarm remains set until it’s unlatched.
ChxData < ChxLAlarmLimit.
LAlarm BOOL Decimal If ChxConfig.ProcessAlarmLatch is set, this alarm remains set until it’s unlatched.
ChxData changing faster than ChxRateAlarmLimit.
RateAlarm BOOL Decimal Both Positive and Negative changes can cause this alarm.
If ChxConfig.RateAlarmLatch is set, this alarm remains set until it’s unlatched.
Analog signal is greater than or equal to the maximum detectable signal. Because the signal can’t be measured, it
Overrange BOOL Decimal can be significantly above the maximum value.
Analog signal is less than or equal to the minimum detectable signal. Because the signal can’t be measured, it can
Underrange BOOL Decimal be significantly below the minimum value.
CalFault BOOL Decimal Set if an error occurs during calibration for Channel x, which causes a bad calibration. Also sets CalFault.
ExtDeviceStatus INT Binary Extended device status (from HART cmd9).
MaintenanceRequired BOOL Decimal Maintenance is needed.
DeviceVariableAlert BOOL Decimal Device reports a problem with some measurement.
PowerLow BOOL Decimal Low power.
PV REAL Float Channel x HART PV value.
SV REAL Float Channel x HART SV value.
TV REAL Float Channel x HART TV value.
FV REAL Float Channel x HART FV value.
PVStatus HEX SINT Channel x HART PV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
SVStatus HEX SINT Channel x HART SV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
TVStatus HEX SINT Channel x HART TV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
FVStatus HEX SINT Channel x HART FV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
CSTTimeStamp HEX DINT (2)
RollingTimeStamp HEX INT
1756-IF8IH Input Tags - Analog and HART by Channel, Configure HART Device = Yes (AB:1756_IF8IH_AnalogHARTbyChannel_1:I:0)
Member Name Type Style Description
CalGoodLowRef BOOL Decimal A valid Low Reference signal has been sampled on this channel.
CalBadLowRef BOOL Decimal The Low Reference signal is grossly out of the expected range.
CalGoodHighRef BOOL Decimal A valid high reference signal has been sampled on the channel.
CalBadHighRef BOOL Decimal The high reference signal is grossly out of the expected range.
This bit is set after valid High and Low points are captured and the Calibrate bit in the output word has been
CalSuccessful BOOL Decimal cleared.
PV REAL Float Channel x HART PV value.
SV REAL Float Channel x HART SV value.
TV REAL Float Channel x HART TV value.
FV REAL Float Channel x HART FV value.
PVStatus HEX SINT Channel x HART PV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
SVStatus HEX SINT Channel x HART SV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
TVStatus HEX SINT Channel x HART TV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
FVStatus HEX SINT Channel x HART FV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
Time stamp that is taken at the time that the input data was sampled in terms of coordinated system time,
CSTimeStamp HEX DINT (2) which is a 64-bit value in microseconds coordinated across the modules in the 1756 backplane.
RollingTimeStamp HEX INT Time stamp that is taken at the time that the input data was sampled in millisecond resolution.
Input Ranges
You can select one of two input ranges for each channel on the module. The range designates
the minimum and maximum signals that are detectable by the module. The two ranges are:
• 0…20 mA
• 4…20 mA (HART instruments use this range)
Module Filter
The module filter attenuates the input signal beginning at the specified frequency. This
feature is applied on a module-wide basis, which affects all channels.
The module attenuates the selected frequency by approximately -3 dB or 0.707 of the applied
amplitude.
An input signal with frequencies above the selected frequency is attenuated more while
frequencies below the selection receive no attenuation.
.707
0 60 Hz
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, and
provides for sampling of all 16 channels within 11 ms. The 15 Hz selection attenuates all
frequencies above 15 Hz and provides only for sampling all 16 channels within 328 ms.
IMPORTANT Do not use the 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 attenuation of a 60 Hz input.
Use these tables to choose a module filter setting.
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.
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’s specified in units of milliseconds. A value of 0 disables the filter.
This figure uses a step input change to illustrate the filter response. 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
Wire-off Detection
The 1756-IF16H module alerts you when a signal wire is disconnected from one of its channels
or the RTB is removed from the module if the channel is configured for 4…20 mA range. When
a wire-off condition occurs for this module, two events occur:
• Input data for that channel changes to the scaled value that corresponds to the
Underrange condition.
• A fault bit is set in the input tag (ChxxUnderrange and ChxxBrokenWire tags are set to 1),
which can indicate the presence of a wire-off condition.
Wire the Module Use this information to wire the current inputs.
1756-IF16H Module Current Inputs
The 1756-IF16H is a differential input module. However there are limitations on its use in
differential mode. Anytime the low ends of the terminal block pins are connected together they
must also be jumpered to the RTN pin on the terminal block. There are two scenarios in which
this shared connection is needed.
First, if one power supply is used for multiple devices then the low ends from the channels are
connected together and connected to the ground return of the power supply.
Single Power Supply with Multiple HART Devices
IN00+ IN00-
HART Device 1
Power Supply 1 + -
IN01+ IN01-
+ -
Second, if multiple power supplies are used, they can be connected to the same ground. In this
case, the low ends of the channels are effectively connected together by the common grounds
of the power supplies.
Multiple Power Supplies with a Common Ground
IN00+ IN00-
HART Device 1
Power Supply 1 + -
IN01+ IN01-
Ground wire from AC + -
source common to
both DC power
supplies
HART Device 2 RTN
Power Supply 2
For devices powered by separate supplies, when the ground potential of the supplies is
expected to differ, differential mode is recommended. Using differential mode helps prevent
ground loop currents from flowing between the supplies. However, the potential difference
allowable between the supplies must remain within specified limits.
HART Device 1
Power Supply 1 + -
The low ends of the terminal block pins are now isolated from each other and the inputs
can be configured as true differential inputs as long as the voltage difference between
them does not exceed 7V.
Some devices, such as AC powered four wire devices, are recommended to be used in
differential mode only. Combinations of differential and single-ended configurations are
allowed but care must be taken to make sure that the differential input grounds really are
isolated from the single-ended inputs.
Circuit Diagram This figure is a simplified input circuit diagram for the 1756-IF16H module.
1756-IF16H Simplified Current Input Circuit
113 22 K
INO+ 10 M
i
+
IGND - Analog to
0.01 F 23.7 0.01 F Digital
Converter
Current INO- 113 22 K
Input
10 M
RTN
IGND
IGND
1756-IF16H Module Fault and The 1756-IF16H module sends 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
Status Reporting conditions. Three levels of tags work together to provide an increasing degree of detail as to
the specific cause of faults on the module.
This table shows the tags that can be examined in ladder logic to indicate when a fault has
occurred.
1756-IF16H Tags That Can Be Examined in Ladder Logic
Tag Name Tag Name
Tag Description Analog and HART PV Analog and HART by Channel
Module Fault Word This word provides fault summary reporting. ModuleFaults ModuleFaults
ChannelFaults ChannelFaults
Channel Fault Word This word provides clamp and communication fault reporting. ChxxFault ChxxFault
These words provide individual channel limit, hold, open wire, ramp ChxxStatus Chxx.Device Status
Channel Status Tags status, and calibration faults. Chxx.DeviceStatus.AlarmStatus
HART Faults This provides HART communication status. HARTFaults, ChxxHARTFault Chxx.DeviceStatus.HARTFault
HART Device Status This provides HART field device health. HART.ChxxDevice Status Chxx.DeviceStatus.FieldDeviceStatus
Module Faults
0…5 aren’t used
7 6 … 1 0
Analog When the module is calibrating, all
CalFault
GroupFault bits in the Channel Fault word are set.
Module Status
7 6 … 1 0
Updated Calibrating
StatusReady
If set, any bit in the Channel Fault word also sets the Analog
Channel Faults Group Fault in the Module Fault word.
15 14 13 12 … 2 1 0
Ch15Fault Ch14Fault Ch13Fault Ch12Fault Ch02Fault Ch01Fault Ch00Fault
A channel calibration
fault sets the
calibration fault in the
Module Fault word.
Ch15
Ch14
Ch13
Ch12
…
7 Ch02
CalFault or 6 5 4 3 2 1 0
Ch01
Device. Underrange Overrange
CalFault Ch00
Channel Fault bits for all channels are also set (16#FFFF) if calibration is being performed or a
communication fault has occurred between the module and its owner controller.
Module Calibration You can initiate calibration of the 1756-IF16H module via the Logix Designer application
Calibration view.
The Calibration view in the Logix Designer application provides a button to initiate module
calibration and a display of the results. Refer to Calibrate Your Module on page 154 for more
information.
Module-defined Data Types, This section describes module-defined data types for the 1756-IF16H module and includes
information for configuration and input tags.
1756-IF16H Module
Available tags depend on the selected input data format, as shown in this table.
Configuration
This table describes the configuration tags available for the 1756-IF16H module.
1756-IF16H Configuration Tags (AB:1756_IF16H:C:0)
Member Name Type Style Description
ModuleFilter SINT Decimal See the Series A Module Filter Selections with Associated Performance Data table on page 68.
(bits 0…7)
RealTimeSample INT Decimal Milliseconds between reading signal values. See Real-time Sampling (RTS) on page 69 for more information.
(bits 0…15)
ChxxConfig (xx = 00…15) AB:1756_IF16H_ChConfig_Struct:C:0
Config SINT Binary
ChxxConfig.Config.7, Enable HART communication. Must be 1 for valid HART data in input tag and asset
HARTEn BOOL Decimal management access to HART field device.
0 = 0…20 mA
RangeType SINT Decimal 1 = 4…20 mA
DigitalFilter INT Decimal Time constant of low pass filter in ms. See Digital Filter on page 70 for more information.
Lower current value for scaling to engineering units. Default is 4 mA. Must be less than HighSignal and more
LowSignal REAL Float than or equal to the minimum input range. See Scaling to Engineering Units on page 143 for more information.
Upper current value for scaling to engineering units. Default is 20 mA. Must be more than LowSignal and less
HighSignal REAL Float than or equal to the maximum input Range. See Scaling to Engineering Units on page 143 for more information.
Measured quantity in engineering units that results in a signal level equal to LowSignal. See Scaling to
LowEngineering REAL Float Engineering Units on page 143 for more information.
Measured quantity in engineering units that results in a signal level equal to HighSignal. See Scaling to
HighEngineering REAL Float Engineering Units on page 143 for more information.
CalBias REAL Float Sensor Offset in engineering units added to the measured signal before reporting Chxx.Data.
PassthroughHandle Seconds to keep a reply to a HART pass-through service request before discarding; 15 seconds
INT Decimal
Timeout is recommended.
Analog Only
This table describes the input tags available in the Analog Only data format for the 1756-IF16H
module.
1756-IF16H Input Tags - Analog Only (AB:1756_IF16H_Analog:I:0)
Member Name Type Style Description
Indicates a problem with analog data on Channel x or broken communication between the Logix controller and
ChannelFaults INT Binary the 1756-IF16H module.
(bits 0…15) Example: Set if the analog signal is larger than 20 mA.
ChxxFault (xx = 00…15) BOOL Decimal ChannelFaults.0…ChannelFaults.15
Module Status SINT Binary
Calibrating BOOL ModuleStatus.0, Calibration in progress
ModuleStatus.1, Module has collected updated Additional Device Status from HART command 48. This status can
UpdatedStatusReady BOOL be retrieved by using the Read Additional Status service, 16#4C. For more information about this service, see
Read Additional Status (Service Code = 16#4C) on page 170.
ModuleFaults SINT Binary Module level fault status bits (bits 0…5 not used)
CalFault BOOL Decimal (ModuleFaults.6) 1756-IF16H Module Calibration Failed.
AnalogGroupFault BOOL Decimal (ModuleFaults.7) Indicates that a fault has occurred on any channel (any of ChannelFaults).
BrokenWireFaults Indicates that current isn’t flowing through the module as expected. Broken wiring, RTB removal, or a powered-
INT Binary
(bit 0…15) off field device can cause this. If configured for 4…20 mA, a broken wire fault sets this bit.
ChxxBroken Wire BOOL Decimal BrokenWireFaults.0…BrokenWireFaults.15
Indicates a problem with HART data from the Field Device on Channel x.
HARTFaults Examples are HART not enabled, HART device not connected, HART communication failure due to noise.
INT Binary
(Ch00…Ch15) These Field Device Status conditions also cause this to be set: Device Malfunction, PV Out of Limits, Loop
Current Saturated, and Loop Current Fixed.
ChxxHARTFault BOOL Decimal HARTFaults.0…HARTFaults.15
ChxxStatus (xx = 00…15) SINT Binary Indicates various alarms on the analog signal. Also sets ChxxFault.
ChxxStatus.5
ChxxOverrange BOOL Analog signal is greater than or equal to the maximum detectable signal. Because the signal can’t be measured,
it can be significantly above the maximum value.
ChxxStatus.6
ChxxUnderrange BOOL Analog signal is less than or equal to the minimum detectable signal. Because the signal can’t be measured, it
can be significantly below the minimum value.
ChxxStatus.7
ChxxCalFault BOOL Set if an error occurs during calibration for Chxx, which causes a bad calibration. Also sets CalFault.
ChxxData (xx = 00…15) REAL Float Value of analog signal on Channel xx after conversion to engineering units.
Time stamp that is taken at the time that the input data was sampled in terms of Coordinated System Time,
CSTTimestamp DINT[2] Hex which is a 64-bit value in microseconds coordinated across the modules in the 1756 backplane.
RollingTimestamp INT Decimal Time stamp that is taken at the time that the input data was sampled in millisecond resolution.
Notes:
Module Features The 1756-IF16IH module is an isolated, 16-channel, current-only input module capable of HART
communication on all channels. Each channel is individually configurable.
HART Compatibility
The 1756-IF16IH functions as a HART master. It communicates with HART devices that have a
HART revision of 5, 6, or 7. Each channel has its own HART modem and functions as a HART
primary master.
The 1756-IF16IH module does not support burst mode, phase shift keying (PSK), or multi-drop
network configuration. The module detects and turns off a bursting device at initial
connection with the device.
• Choose Analog and HART PV if you prefer the members of your tag to be arranged
similar to non-HART analog input modules. With this selection, the analog values for all
channels are grouped near the end of the tag. This arrangement makes it easy to view
all 16 analog values at once.
• Choose Analog and HART PV by Channel Grouped if you prefer Status, Analog Value, and
Device Status for each channel to be together in the tag. This arrangement makes it
easier to view all data that is related to one field device.
Input Ranges
You can select one of two input ranges for each channel on the module. The possible ranges
that designate the minimum and maximum signals detectable by the module are:
• 0…20 mA
• 4…20 mA (HART instruments use this range)
Module Filter
The module filter attenuates the input signal at the specified frequency and above. This
feature is applied on a module-wide basis, which affects 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.
0.707
0 60 Hz
A by-product of the filter selection is the minimum available sample rate (RTS). For example,
the 1000 Hz selection does not attenuate any frequencies less than 1000 Hz, and provides for
sampling of all 16 channels within 11 ms. The 15 Hz selection attenuates all frequencies above
15 Hz and provides only for sampling all 16 channels within 328 ms.
IMPORTANT Do not use the 1000 Hz module filter with HART instruments.
Digital Filter
The digital filter smooths input data noise transients. There’s a separate digital filter for each
channel.
The digital filter value specifies the time constant in milliseconds for a digital first order lag
filter on the input. A value of 0 disables the filter.
This figure illustrates the filter response to a step input. 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 to a Step Input
Real-time Sampling
This parameter instructs the module how often to scan its input channels and obtain new
sampled data. After the channels are scanned, the module broadcasts that data (multicast or
unicast) to the local chassis backplane. 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 broadcast data, but
only the RTS feature instructs the module to scan its channels before broadcasting.
For more RTS information, see Real Time Sample (RTS) on page 22.
This table shows the input ranges of the 1756-IF16IH module and the lowest and highest signal
available in each range before the module detects an underrange and overrange condition.
In the 0...20 mA range, an open-circuit condition results in a measured value of 0 mA, which is
the same as a measured value of 0 mA when there isn’t an open-circuit condition. The
appropriate Underrange bit is set but the ChxBrokenWire bit isn’t set.
Wire the Module Use the information in this figure to wire the current inputs.
1756-IF16IH Current Inputs
Circuit Diagram This figure is a simplified input circuit diagram for the 1756-IF16IH module.
1756-IF16IH Simplified Current Input Circuit
Overcurrent protection
HART Tx and Rx
4 mA ~ 20 mA
Transmitter
1756-IF16IH Module Fault The 1756-IF16IH module sends 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
and Status Reporting conditions. Three levels of tags work together to provide an increasing degree of detail as to
the specific cause of faults on the module. This figure offers an overview of the fault reporting
process for the 1756-IF16IH module offers an overview of how faults are reported.
Module Faults
0…5 aren’t used
Module Status
7 6 … 1 0
Updated Calibrating
StatusReady
If set, any bit in the Channel Fault word also sets the Analog
Channel Faults Group Fault in the Module Fault word.
15 14 13 12 … 2 1 0
Ch15Fault Ch14Fault Ch13Fault Ch12Fault Ch2Fault Ch1Fault Ch0Fault
A channel calibration
fault sets the
calibration fault in the
Module Fault word.
Ch15
Ch14
Ch13
Ch12
…
7 Ch2
CalFault or 6 5 4 3 2 1 0
Device. Underrange Overrange Ch1
CalFAUlt Ch0
Channel Status Tags
One set of tags for each channel
0…4 aren’t used
This table shows the tags that can be examined in ladder logic to indicate when a fault has
occurred.
1756-IF16IH Tags That Can Be Examined in Ladder Logic
Tag Name Tag Name
Tag Description Analog and HART PV Analog and HART PV by Channel Grouped
Module Fault Word This word provides fault summary reporting. ModuleFaults ModuleFaults
This word provides clamp and communication fault ChannelFaults ChannelFaults
Channel Fault Word reporting. ChxxFault ChxxFault
These words provide individual channel limit, hold, open Chxx.Device Status
Channel Status Tags ChxxStatus
wire, ramp status, and calibration faults. Chxx.DeviceStatus.AlarmStatus
HART Faults This provides HART communication status. HARTFaults, ChxxHARTFault Chxx.DeviceStatus.HARTFault
HART Device Status This provides HART field device health. HART.ChxxDevice Status Chxx.DeviceStatus.FieldDeviceStatus
Module Calibration You can initiate calibration of the 1756-IF16IH module via the Logix Designer application
Calibration view.
The Calibration view in the Logix Designer application provides a button to initiate module
calibration and a display of the results. Refer to Calibrate Your Module on page 154 for more
information.
Module-defined Data Types, This section describes module-defined data types for the 1756-IF16IH module and includes
information for configuration and input tags.
1756-IF16IH Module
Available tags depend on the selected input data format, as shown in this table.
Configuration
This table describes the configuration tags available for the 1756-IF16IH module.
1756-IF16IH Configuration Tags (AB:1756_IF16IH:C:0)
Member Name Type Style Description
ModuleFilter SINT Decimal See the Module Filter Selections with Associated Performance Data for 1756-IF16IH table on page 85.
(bits 0…7)
RealTimeSample INT Decimal Milliseconds between reading signal values. See Real-time Sampling on page 86 for more information.
(bits 0…15)
ChxxConfig (xx = 00…15) AB:1756_IF16IH_ChConfig_Struct:C:0
Config SINT Binary
ChxxConfig.Config.7, Enable HART communication. Must be 1 for valid HART data in input tag and asset
HARTEn BOOL Decimal management access to HART field device.
0 = 0…20 mA
RangeType SINT Decimal 1 = 4…20 mA
DigitalFilter INT Decimal Time constant of low pass filter in ms. See Digital Filter on page 86 for more information.
Lower current value for scaling to engineering units. Default is 4 mA. Must be less than HighSignal and more
LowSignal REAL Float than or equal to the minimum input range. See Scaling to Engineering Units on page 143 for more information.
Upper current value for scaling to engineering units. Default is 20 mA. Must be more than LowSignal and less
HighSignal REAL Float than or equal to the maximum input Range. See Scaling to Engineering Units on page 143 for more information.
Measured quantity in engineering units that results in a signal level equal to LowSignal. See Scaling to
LowEngineering REAL Float Engineering Units on page 143 for more information.
Measured quantity in engineering units that results in a signal level equal to HighSignal. See Scaling to
HighEngineering REAL Float Engineering Units on page 143 for more information.
CalBias REAL Float Sensor Offset in engineering units added to the measured signal before reporting Chxx.Data.
PassthroughHandle INT Decimal Seconds to keep a reply to a HART pass-through service request before discarding; 15 seconds is recommended.
Timeout
Analog Only
This table describes the input tags available in the Analog Only data format for the 1756-IF16IH
module.
1756-IF16IH Input Tags - Analog Only (AB:1756_IF16IH_Analog:I:0)
Member Name Type Style Description
Indicates a problem with analog data on Channel x or broken communication between the Logix controller and
ChannelFaults INT Binary the 1756-IF16IH module.
(bits 0 … 15) Example: Set if the analog signal is larger than 20 mA.
ChxxFault (xx = 00 … 15) BOOL Decimal ChannelFaults.0…ChannelFaults.15
Module Status SINT Binary
Calibrating BOOL ModuleStatus.0, Calibration in progress
ModuleStatus.1, Module has collected updated Additional Device Status from HART command 48. This status can
UpdatedStatusReady BOOL be retrieved by using the Read Additional Status service, 16#4C. For more information about this service, see
Read Additional Status (Service Code = 16#4C) on page 170.
Module level fault status bits
ModuleFaults SINT Binary (bits 0…5 not used)
CalFault BOOL Decimal (ModuleFaults.6) 1756-IF16IH Module Calibration Failed.
AnalogGroupFault BOOL Decimal (ModuleFaults.7) Indicates that a fault has occurred on any channel (any of ChannelFaults).
BrokenWireFaults Indicates that current isn’t flowing through the module as expected. Broken wiring, RTB removal, or a powered-
INT Binary
(bit 0…15) off field device can be the cause. If configured for 4…20 mA, a broken wire fault sets this bit.
ChxxBroken Wire BOOL Decimal BrokenWireFaults.0…BrokenWireFaults.15
Indicates a problem with HART data from the Field Device on Channel x.
HARTFaults Examples are HART not enabled, HART device not connected, HART communication failure due to noise.
INT Binary
(Ch00…Ch15) These Field Device Status conditions also cause this to be set: Device Malfunction, PV Out of Limits, Loop
Current Saturated, and Loop Current Fixed.
ChxxHARTFault BOOL Decimal HARTFaults.0…HARTFaults.15
ChxxStatus (xx = 00…15) SINT Binary Indicates various alarms on the analog signal. Also sets ChxxFault.
ChxxStatus.5
ChxxOverrange BOOL Analog signal is greater than or equal to the maximum detectable signal. Because the signal can’t be measured,
it can be significantly above the maximum value.
ChxxStatus.6
ChxxUnderrange BOOL Analog signal is less than or equal to the minimum detectable signal. Because the signal can’t be measured, it
can be significantly below the minimum value.
ChxxStatus.7
ChxxCalFault BOOL Set if an error occurs during calibration for Chxx, which causes a bad calibration. Also sets CalFault.
ChxxData (xx = 00…15) REAL Float Value of analog signal on Channel xx after conversion to engineering units.
Time stamp that is taken at the time that the input data was sampled in terms of Coordinated System Time,
CSTTimestamp DINT[2] Hex which is a 64 bit value in microseconds coordinated across the modules in the 1756 backplane.
RollingTimestamp INT Decimal Time stamp that is taken at the time that the input data was sampled in millisecond resolution.
1756-IF16IH Input Tags - Analog and HART PV by Channel Grouped (AB:1756-IF16IH_AnalogHARTbyChannel:I:0) (Continued)
Member Name Type Style Description
Secondary status
SVStatus SINT Hex 16#C0 = Connected
16#00 = Not Connected
Third status
TVStatus SINT Hex 16#C0 = Connected
16#00 = Not Connected
Fourth status
FVStatus SINT Hex 16#C0 = Connected
16#00 = Not Connected
Time stamp that is taken at the time that the input data was sampled in terms of coordinated system time,
CSTTimestamp DINT[2] Hex which is a 64-bit value in microseconds coordinated across the modules in the 1756 backplane.
RollingTimestamp INT Decimal Time stamp that is taken at the time that the input data was sampled in millisecond resolution.
Notes:
IMPORTANT The Analog and HART by Channel data type is available only for
1756-OF8H firmware revision 2.002 or later.
• 15-bit or 16-bit resolution
• Ramping and rate limiting
• Hold for initialization
• Open wire detection
• Clamping and limited
• Clamp and limit alarms
• Data echo
• Choose Analog and HART PV if you prefer the members of the tag to be arranged similar
to non-HART analog input modules. With this selection, analog values for all channels
grouped near the end of the tag. This arrangement makes it easy to view all eight
analog values at once.
• Choose Analog and HART by Channel if you prefer Status, Analog Value, and Device
Status for each channel to be together in the tag. This arrangement makes it easier to
view all data that is related to one field device.
Resolution
The output module can use 15-bit or 16-bit resolution.
Ramping/Rate Limiting
Output ramping limits the speed at which an analog output signal can change. This feature
helps prevent fast transitions in the output from damaging the devices that an output module
controls. Ramping is also known as rate limiting.
The maximum rate of change in outputs is expressed in engineering units per second and
called the maximum ramp rate.
For more information about how to set Ramp Rate on the output Limits view, see Set Output
Module Limits on page 148.
The ChxInHold bit for a channel indicates that the channel is holding.
Once clamps are set for a channel, any data that is received from the controller that exceeds
the clamps sets a limit alarm and transitions the output to that limit but not beyond the
configured clamp value. For example, suppose that an application sets the high clamp on a
module for 8V and the low clamp for -8V. If a controller sends a value that corresponds to 9V to
the module, the module applies only 8V to its screw terminals. The signal value that is applied
is reflected in the Input Tag ChxData field.
Clamping limits are entered in engineering units.
For example, if a channel has clamping limits of 8V and -8V but receives data to apply 9V, the
module applies 8V to the screw terminals and sends a status bit to the controller. This status
bit informs the controller that the 9V value exceeds the channel 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 that match the analog value that is
applied to the module screw terminals.
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. The values can differ due to Ramp,
Clamp, or Hold for Initialization.
The echo value is the current level being attempted. If the wire is off or damaged, the actual
current can be 0.
Wire the Module Use this figure to wire the module. Voltage outputs use the terminal block pins labeled VOUT-#
and RTN. Current outputs use the terminal block pins labeled IOUT-# and RTN.
Voltage Output
XMTR1
Current Output
XMTR2
Use Module Block and This figure shows the module output circuit diagram.
Output Circuit Diagrams 1756-OF8H Output Circuit Diagram
+ V OUT - #
250
0.1 F 24V
D/A
Converter 16K +18.6V
5K 100 pF
50
2K
-
+
Amplifier 100
I OUT - x
24V
RTN
RTN
RTN
RTN
1756-OF8H Module Fault and 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
Status Reporting 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.
This table lists tags that you can examine in ladder logic to indicate when a fault occurred.
1756-OF8H Tags That Can Be Examined in Ladder Logic
Tag Name Tag Name
Tag Description Analog and HART PV Analog and HART by Channel(1)
Module Fault Word This word provides fault summary reporting. ModuleFaults ModuleFaults
This word provides clamp and communication fault ChannelFaults ChannelFaults
Channel Fault Word reporting. ChxFault ChxFault
These words, one per channel, provide individual channel Chx.DeviceStatus
Channel Status Tags ChxStatus
limit, hold, open wire, ramp status, and calibration faults. Chx.DeviceStatus.AlarmStatus
HART Faults This provides HART communication status. HARTFaults, ChxHARTFault Chx.DeviceStatus.HARTFault
HART Device Status This provides HART field device health. HART.ChxDevice Status Chx.DeviceStatus.FieldDeviceStatus
(1) Available only for 1756-OF8H firmware revision 2.002 or later.
1756-OF8H Fault Reporting This figure offers an overview of the fault reporting process.
1756-OF8H Module Fault Reporting
7 6 5 4 3 2 1 0
Analog Updated Calibrating CalFault
GroupFault StatusReady
If set, any bit in the Channel Fault word, also sets the Analog
Channel Faults Group Fault in the Module Fault word.
A channel
calibration fault
sets the
8 7 6 5 4 3 2 1 0
calibration fault
LoopOutput Ch7Fault Ch6Fault Ch5Fault Ch4Fault Ch3Fault Ch2Fault Ch1Fault Ch0Fault
in the Module
Fault
Fault word.
Ch7
Ch6
Ch5
Ch4
Ch3
Ch2
7 6 5 4 3 2 1 0
OpenWire NotA CalFault InHold Ramp LLimit HLimit Ch1
Number Alarm Alarm Alarm Ch0
This table lists tags that are found in the Module Fault word.
This table lists the conditions that set all Channel Fault word bits.
Your logic monitors the Channel Fault bit for a particular output under the following
conditions:
• You enable output clamping
• You’re checking for an open wire condition (0…20 mA configuration only)
• You must know if the output module isn’t communicating with the controller
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.
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. This table lists the conditions that set each of the word bits.
ChxNotaNumber(2) 5 This bit is set when the output value that is received from the controller is NotANumber (the IEEE NaN value). The
Chx.DeviceStatus.NotANumber output channel holds its last state.
ChxCalFault This bit is set when an error occurred when calibrating. This bit also sets the appropriate bit in the Channel Fault
4
Chx.DeviceStatus.CalFault word.
ChxInHold(2) 3 This bit is set when the output channel is holding. The bit resets when the requested Run mode output value is
Chx.DeviceStatus.InHold within 0.1% of the full-scale current echo value.
This bit is set when the requested rate of change of the output channel exceeds the configured maximum ramp
ChxRampAlarm(2) 2 rate requested parameter. It remains set until the output reaches its target value and ramping stops. If the bit is
Chx.DeviceStatus.RampAlarm latched, it remains set until it’s unlatched.
ChxLLimitAlarm This bit is set when the requested output value is beneath the configured low limit value. It remains set until the
1
Chx.DeviceStatus.LLimitAlarm requested output is above the low limit. If the bit is latched, it remains set until it’s unlatched.
ChxHLimitAlarm This bit is set when the requested output value is above the configured high limit value. It remains set until the
0
Chx.DeviceStatus.HLimitAlarm requested output is below the high limit. If the bit is latched, it remains set until it’s unlatched.
(1) Bit 6 isn’t used.
(2) This bit does not set additional bits at any higher level.
Module Calibration
You can initiate calibration of the 1756-OF8H module via the Logix Designer application Calibration view.
The Calibration view in the Logix Designer application provides a button to initiate module calibration and a display of the results. Refer
to Calibrate Your Module on page 154 for more information.
Module-defined Data Types, This section describes module-defined data types for the 1756-OF8H module and includes
information for configuration, input, and output tags.
1756-OF8H Module
Available tags depend on the selected input data format, as shown in this table.
Configuration
This table describes the configuration tags available in the 1756-OF8H module.
1756-OF8H Configuration Tags (AB:1756_OF8H:C:0)
Member Name Type Style Description
ProgToFaultEN BOOL Decimal
ChxConfig (Ch 0…Ch7) AB:1756_OF8H_ChConfig_Struct:C:0
RampToFault BOOL Decimal ConfigBits:9.
RampToProg BOOL Decimal ConfigBits:8.
RampToRun BOOL Decimal ConfigBits:7.
ProgMode BOOL Decimal ConfigBits:6.
FaultMode BOOL Decimal ConfigBits:5.
LimitAlarmLatch BOOL Decimal ConfigBits:4.
RampAlarmLatch BOOL Decimal ConfigBits:3.
AlarmDisable BOOL Decimal ConfigBits:2.
HoldForInit BOOL Decimal ConfigBits:1.
HARTEn BOOL Decimal ConfigBits:0, HART enabled.
0 = 0…20 mA.
RangeType INT Decimal 1 = 4…20 mA.
MaxRampRate REAL Float
FaultValue REAL Float
ProgValue REAL Float
Lower current value for scaling to engineering units. Default is 4 mA. Must be less than HighSignal and more than
LowSignal REAL Float minimum input range. See Scaling to Engineering Units on page 143 for more information.
Upper current value for scaling to engineering units. Default is 10 mA. Must be more than LowSignal and less
HighSignal REAL Float than maximum input range. See Scaling to Engineering Units on page 143 for more information.
Measured quantity in engineering units that results in a signal level equal to LowSignal.
LowEngineering REAL Float See Scaling to Engineering Units on page 143 for more information.
Measured quantity in engineering units that results in a signal level equal to HighSignal.
HighEngineering REAL Float See Scaling to Engineering Units on page 143 for more information.
LowLimit REAL Float Output signal is clamped at this value in engineering units even if Ch0Data is lower than this.
HighLimit REAL Float Output signal is clamped at this value in engineering units if Ch0Data is larger than this.
CalBias REAL Float Sensor offset in engineering units added to the measured signal before reporting Ch0.Data.
Analog Only
This table describes the input tags available in the Analog Only data format.
1756-OF8H Input Tags - Analog Only (AB:1756_OF8H_Analog:I:0)
Member Name Type Style Description
ChannelFaults INT Binary ChannelFaults.x Indicates communication fault or fault condition from ChXStatus. (bits 9…15 unused).
ChxFault (Ch 0…Ch7) BOOL Decimal Indicates a channel fault on channel x.
This is a hardware fault where the module has detected that the power supply to the isolated (analog) side of the
LoopOutputFault BOOL Decimal board has failed (no power). It does not roll into any other bits. The OK status indicator is set to steady red.
HARTFaults SINT Binary
HARTFault.x
Indicates a problem with HART data from the field device on Channel x. Examples are HART not enabled,
ChxHARTFault BOOL Decimal HART device not connected, HART communication failure due to noise.
These field device status conditions also cause this to be set:
Device Malfunction, PV Out of Limits, Loop Current Saturated, and Loop Current Fixed.
ModuleFaults SINT Binary
CalFault BOOL Decimal (ModuleFaults.1) 1756-OF8H module calibration failed.
Calibrating BOOL Decimal (ModuleStatus.2) Calibration in progress.
AnalogGroupFault BOOL Decimal (ModuleFaults.7) Indicates that a fault has occurred on any channel (any of ChannelFaults).
ChxStatus (Ch 0…Ch7) SINT Binary Indicates various alarms on the analog signal. Also sets ChxFault for Overrange, Underrange, and CalFault.
(ChxStatus.0) The analog output signal is being limited by the ChxConfig.HighLimit value. If
ChxHLimitAlarm BOOL Decimal ChxConfig.LimitAlarmLatch is 1, the alarm is retained until explicitly reset.
(ChxStatus.1) The analog output signal is being limited by the ChxConfig.LowLimit value. If
ChxLLimitAlarm BOOL Decimal ChxConfig.LimitAlarmLatch is 1, the alarm is retained until explicitly reset.
(ChxStatus.2) Rate of change in ChxData exceeds ChxConfig.MaxRampRate.
The change in ChxData divided by the RPI period determines the rate of change. Thus if a step change in Chx
can’t be reached via the configured MaxRampRate within one RPI, then ChxRampAlarm is set to 1. If
ChxRampAlarm BOOL Decimal ChxConfig.RampAlarmLatch is 1, then ChxRampAlarm remains set until explicitly reset using the CIP™ message
even if the condition returns to normal.
The CIP message can be sent via MSG instruction in the Logix controller or from the Module Properties Limit
dialog in the Logix Designer application.
(ChxStatus.3) Channel holding its last output value, waiting for the controller to match the value, indicating that
ChxInHold BOOL Decimal bumpless initialization of the control loop is complete.
ChxCalFault BOOL Decimal (ChxStatus.4) Fault during calibration of channel 0.
(ChxStatus.5)
ChxNotANumber BOOL Decimal ChxData isn’t a valid floating point number.
(ChxStatus.7) Only valid in current mode (example 4…20 mA). 1 indicates that no current is flowing, probably due
ChxOpenWire BOOL Decimal to an open circuit.
Analog value actually output in engineering units. This can be different than output tag ChxData if the value
ChxData (Ch 0…Ch7) REAL Float exceeds the LowLimit or HighLimit, has a MaxRampRate applied, is being Held for initialization, or the controller
is in Fault or Program mode.
64-bit coordinated system time time stamp in microseconds of the last output update. Time base synchronized
CSTTimestamp DINT[2] Decimal with other modules in the rack.
RollingTimestamp INT Decimal 16-bit time stamp in milliseconds. Time base local to the 1756-OF8H module.
Output
This table describes the output tags available in the 1756-OF8H module.
1756-OF8H Output Tags (AB:1756_OF8H:O:0)
Member Name Type Style Description
ChxData (Ch0…Ch7) REAL Float Value in engineering units to output on the analog signal of Channel x.
Choose Analog and HART PV if you prefer the members of your tag to be arranged similar to
non-HART analog input modules. With this selection, the analog values for all channels grouped
near the end of the tag. This arrangement makes it easy to view all eight analog values at
once.
Choose Analog and HART by Channel if you prefer Status, Analog Value, and Device Status for
each channel to be together in the tag. This arrangement makes it easier to view all data that
is related to one field device.
Powerup State
On power-up, the outputs of the 1756-OF8IH module are set to their reset state (0 mA) until
module diagnostics and configuration are complete. Outputs are then set at their configured
program values (ChxConfig.ProgValue).
Ramping/Rate Limiting
Ramping limits the rate at which an analog output signal can change. This feature helps
prevent fast transitions in the output from damaging the devices that an output module
controls.
Ramping Types
Ramping Types Description
When the module is in Run mode, it limits the rate at which the output changes from one
Ramp-to-Run commanded value to another.
When the controller goes into program mode, the present output value ramps to the
Ramp-to-Program configured Program Value. If the connection to the module is inhibited, the Program mode
value and ramp rate are applied.
Ramp-to-Fault When a communication fault occurs, the output signal ramps to the configured fault value.
The maximum rate of change in outputs is expressed in engineering units per second and
called the maximum ramp rate.
For more information about how to set Ramp Rate on the output Limits view, see Set Output
Module Limits on page 148.
If Hold for Initialization is selected, outputs hold if any of these conditions occur:
• Initial connection is established after power-up.
• A new connection is established after a communication fault occurs.
• There’s a transition from Program mode to Run mode.
The ChxInHold bit for a channel indicates that the channel is holding.
When an open wire condition occurs at any channel, a status bit named ChxOpenWire is set for
that channel.
Clamping (Limiting)
Clamping limits the output from the analog module to remain within a range that the controller
configures, even when the controller commands an output outside that range. This safety
feature sets a high clamp value and a low clamp value.
Once clamps are set for a channel, data from the controller that exceeds the clamp values sets
a limit alarm. The output transitions to that limit but not beyond the configured clamp value.
For example, suppose that an application sets the high clamp on a module for 18 mA and the
low clamp for 4 mA. If a controller sends a value that corresponds to 19 mA to the module, the
module only applies 18 mA via its screw terminals. The signal value that is applied is reflected
in the Input Tag ChxData field.
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 that match the analog value that is
applied to the module screw terminals.
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 can be different due to Ramp,
Clamp, or Hold for Initialization.
The echo value is the current level being attempted. If the wire is off or damaged, the actual
current can be 0.
This feature is available only with the Analog and HART by Channel data format with Configure
HART Device = Yes.
Wire the Module Use this figure to wire the module. The 1756-OF8IH module has only current outputs, which use
the terminal block pins labeled IOUT# and RTN#.
For each output, HART communication is active only when it’s enabled in the Logix Designer
application.
Wiring Diagram for the 1756-OF8IH Module
Valve or Actuator
Not Used 2 1 Not Used
IOUT0 4 3 IOUT1
RTN0 6 5 RTN1
Not Used 8 7 Reserved
Not Used 10 9 Reserved
IOUT2 12 11 IOUT3
RTN2 14 13 RTN3
Not Used 16 15 Not Used
Not Used 18 17 Not Used
IOUT4 20 19 IOUT5
RTN4 22 21 RTN5
Not Used 24 23 Not Used
Not Used 26 25 Not Used
IOUT6 28 27 IOUT7
RTN6 30 29 RTN7
Not Used 32 31 Not Used
Not Used 34 33 Not Used
Not Used 36 35 Not Used
Output Circuit Diagram This figure shows the module output circuit diagram.
1756-OF8IH Output Circuit Diagram
VCC
PowerSupply
Power
Supply
SPI
AD 5420
Current I out
DAC
Amplifier Reverse
HART MODEM Protection
Current Output
HART Tx
Internal Vref Device
50 Ohm~750
Ohm
HART Rx
1756-OF8IH Module Fault The 1756-OF8IH 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
and Status Reporting 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.
This table lists tags that you can examine in ladder logic to indicate when a fault occurred.
1756-OF8IH Tags That Can Be Examined in Ladder Logic
Tag Name Tag Name
Tag Description Analog and HART PV Analog and HART by Channel
The bits in this word are set when a fault of the corresponding type has
Module Fault Word ModuleFaults ModuleFaults
occurred on any channel.
ChannelFaults ChannelFaults
Channel Fault Word These bits report faults that occur on the corresponding channel. ChxFault ChxFault
These words, one per channel, indicate individual channel limit, hold, open ChxStatus Chx.DeviceStatus
Channel Status Tags wire, ramp status, and calibration faults. Chx.DeviceStatus.AlarmStatus
HART Faults The bits in this word show HART communication status for each channel. HARTFaults, ChxHARTFault Chx.DeviceStatus.HARTFault
HART Device Status This data provides information about the HART field device. HART.ChxDevice Status Chx.DeviceStatus.FieldDeviceStatus
7 6 5 4 3 2 1 0
Analog Updated Calibrating CalFault
GroupFault StatusReady
If set, any bit in the Channel Fault word, also sets the Analog
Channel Faults Group Fault in the Module Fault word.
A channel
calibration fault
sets the
8 7 6 5 4 3 2 1 0
calibration fault
LoopOutput Ch7Fault Ch6Fault Ch5Fault Ch4Fault Ch3Fault Ch2Fault Ch1Fault Ch0Fault
in the Module
Fault
Fault word.
Ch7
Ch6
Ch5
Ch4
Ch3
Ch2
7 6 5 4 3 2 1 0
OpenWire PVConfig NotA CalFault InHold Ramp LLimit HLimit Ch1
Failed Number Alarm Alarm Alarm Ch0
Notes:
• NotANumber, InHold, RampAlarm, and PVConfigFailed conditions do not set other bits; monitor them here.
• Bits 0 and 1 not used if Configure HART Device = Yes
• Bit 6 not used if Configure HART Device = No
Monitor the Channel Fault bit for a particular output in ladder logic for the following reasons:
• You enable output clamping, are checking for an open wire condition (4…20 mA
configuration only)
• You must know if the output module isn’t communicating with the controller
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.
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. This table lists the conditions that set each of the word bits.
1756-OF8IH Conditions That Set Channel Status Word Bits(1), Configure HART Device = No
Tag (Status Words) Bit Event That Sets This Tag
ChxOpenWire This bit is set only if the circuit becomes open due to a wire falling off or being cut when the output being driven is
7
Chx.DeviceStatus.OpenWire above 0.1 mA. The bit remains set until the correct wiring is restored.
ChxNotaNumber(2) 5 This bit is set when the output value that is received from the controller is NotANumber (the IEEE NaN value). The
Chx.DeviceStatus.NotANumber output channel holds its last state.
ChxCalFault This bit is set when an error occurred when calibrating. This bit also sets the appropriate bit in the Channel Fault
Chx.DeviceStatus.CalFault 4 word.
ChxInHold(2) 3 This bit is set when the output channel is holding. The bit resets when the requested Run mode output value is
Chx.DeviceStatus.InHold within 0.1% of the full-scale current echo value.
This bit is set when the requested rate of change for an output channel would exceed the configured maximum
ChxRampAlarm(2) 2 ramp rate requested parameter. It remains set until the output reaches its target value and ramping stops. If the
Chx.DeviceStatus.RampAlarm bit is latched, it remains set until it’s unlatched.
ChxLLimitAlarm This bit is set when the requested output value is beneath the configured low limit value. It remains set until the
1
Chx.DeviceStatus.LLimitAlarm requested output is above the low limit. If the bit is latched, it remains set until it’s unlatched.
ChxHLimitAlarm This bit is set when the requested output value is above the configured high limit value. It remains set until the
0
Chx.DeviceStatus.HLimitAlarm requested output is below the high limit. If the bit is latched, it remains set until it’s unlatched.
(1) Bit 6 isn’t used.
(2) This bit does not set other bits at any higher level.
1756-OF8IH Conditions That Set Channel Status Word Bits(1), Configure HART Device = Yes
Tag (Status Words) Bit Event That Sets This Tag
ChxOpenWire This bit is set only if the circuit becomes open due to a wire falling off or being cut when the output being driven is
7
Chx.DeviceStatus.OpenWire above 0.1 mA. The bit remains set until the correct wiring is restored.
CHxPVConfigFailed 6 PV auto-configuration failed.
Chx.DeviceStatus.PVConfigFailed
ChxNotaNumber(2) 5 This bit is set when the output value that is received from the controller is NotANumber (the IEEE NaN value).
Chx.DeviceStatus.NotANumber The output channel holds its last state.
ChxCalFault This bit is set when an error occurred when calibrating. This bit also sets the appropriate bit in the Channel Fault
4
Chx.DeviceStatus.CalFault word.
ChxInHold(2) 3 This bit is set when the output channel is holding. The bit resets when the requested Run mode output value is
Chx.DeviceStatus.InHold within 0.1% of the full-scale current echo value.
This bit is set when the requested rate of change for an output channel would exceed the configured maximum
ChxRampAlarm(2) 2 ramp rate requested parameter. It remains set until the output reaches its target value and ramping stops. If the
Chx.DeviceStatus.RampAlarm bit is latched, it remains set until it’s unlatched.
(1) Bits 0 and 1 are not used.
(2) This bit does not set other bits at any higher level.
Module Calibration There are two ways to initiate calibration of the 1756-OF8IH module:
• Logix Designer application Calibration view
• Module Output Word
See Output, Configure HART Device = Yes on page 128 for output bit descriptions.
To perform a module calibration via the output word, set and clear bits in sequence to perform
the calibration tasks. This table shows the tags that are involved in calibration.
Step Calibration Word Bits Description
Set this bit to initiate calibration, and keep it set until the
Initiate calibration Ch[x].Calibrate calibration sequence is complete. If this bit clears before
the calibration is complete, the calibration is aborted.
Output low calibration Ch[x].CalOutputLowRef Sets the output to 4 mA.
reference
Pass measured low
calibration output to Ch[x].CalLowRefPassed Captures the low calibration value.
ChxData
Output high calibration Ch[x].CalOutputHighRef Sets the output to 20 mA.
reference
Pass measured high
calibration output to Ch[x].CalHighRefPassed Captures the high calibration value.
Chx Data
Initiates calculation of the calibration for that channel. If
Finish calibration Ch[x].CalFinished all other channels have been calculated and complete, the
calibration date is written and calibration ends.
Ch[x].Calibrate
Abort calibration Ch[x].CalOutputLowRef If necessary, this bit combination aborts calibration.
Ch[x].CalOutputHighRef
The date to be recorded with a successful calibration,
Set the calibration date CalibrationDate typically the current date.
Module-defined Data Types, This section describes module-defined data types for the 1756-OF8IH module and include
information for configuration, input, and output tags.
1756-OF8IH Module Available tags depend on the selected input data format, as shown in Table .
This table describes the configuration tags available in the 1756-OF8IH module when Configure
HART Device is set to No.
1756-OF8IH Configuration Tags, Configure HART Device = No (AB:1756_OF8IH:O:0)
Member Name Type Style Description
0 – Disabled. 1 – Enable programmed fault states.
Determines how outputs can behave if a communication fault occurs while the module is in program mode.
ProgToFaultEn BOOL Decimal When set, the bit causes the outputs to transition to their programmed fault state. If not set, outputs remain in
their configured program state despite a communications fault occurring.
ChxConfig (Ch 0…Ch7) AB:1756_OF8IH_ChConfig_Struct:C:0
Enables ramping of the output value to the value specified by FaultValue.
RampToFault BOOL Decimal MaxRampRate defines the transition ramp rate.
HoldOnFault must be set to 1 if RampToFault is set to 1.
Selects the ramping behavior when the system transitions from Run to Idle/Program mode.
Enable ramping of the output to the fvalue specified by IdleProgValue.
RampToProg BOOL Decimal MaxRampRate defines the ramp rate.
HoldOnIdle must be set to 1 if RampToProg is set to 1 and MaxRampRate must be > 0.
Enables ramping of the output value during Run mode between the current output level and a newly requested
RampToRun BOOL Decimal output.
MaxRampRate defines the transition ramp rate and must be > 0.
ProgMode BOOL Decimal
FaultMode BOOL Decimal
Enables latching for the clamp limit alarms. Latching causes the limit alarms to remain set until an unlatch
LimitAlarmLatch BOOL Decimal service is explicitly sent to the channel or alarm.
(1 = enable, 0 = disable.)
Enables latching for the rate alarm. Latching causes the rate alarm to remain set until an unlatch service is
RampAlarmLatch BOOL Decimal explicitly sent to the channel or alarm.
(1 = enable, 0 = disable.)
Disables all alarms for the channel: HLimitAlarm, LLimitAlarm, RampAlarm.
AlarmDisable BOOL Decimal (1 = disable alarms, 0 = do not disable alarms.)
Configures the channel to hold, or not change, until initialized with a value within 0.1% of full scale or its current
value when one of the following conditions occurs:
HoldForInit BOOL Decimal • Module initial connection power-up.
• Module transition from Program mode to Run mode.
• Module re-establishes communication after a fault.
HARTEn BOOL Decimal Enables HART communication.
1756-OF8IH Input Tags - Analog and HART PV Data Format (AB:1756_OF8IH_HARTPV:I:1) (Continued)
Member Name Type Style Description
HART communication status byte or Response code from a recent HART reply (first status byte). See Response
ResponseCode INT Binary Code and Field Device Status on page 204 for more information.
HART device status byte from a recent HART reply. Indicates the health of the HART field device. See Field
FieldDeviceStatus INT Binary Device Status Bit Mask Definitions on page 205 for more information.
PVOutOfLimits BOOL Decimal The primary variable is beyond its operating limit.
VariableOutOfLimits BOOL Decimal A device variable that is not mapped to the PV is beyond its operating limits.
CurrentSaturated BOOL Decimal The loop current has reached its upper or lower endpoint limit and can’t increase or decrease any further.
CurrentFixed BOOL Decimal The loop current is being held at a fixed value and isn’t responding to process variations.
MoreStatus BOOL Decimal More status information is available via command 48, ‘Read Additional Status’ information.
ColdStart BOOL Decimal A power failure or device reset occurred.
Changed BOOL Decimal An operation was performed that changed the configuration of the device.
Malfunction BOOL Decimal The device detected a serious error or failure that compromises device operation.
ExtDeviceStatus INT Binary Extended device status (from HART cmd9)xx.
MainetnanceRequired BOOL Decimal
DeviceVariableAlert BOOL Decimal Device reports a problem with some measurement.
PowerLow Low power.
ChxPV (Ch 0…Ch7) Channel x HART PV value.
ChxSV (Ch 0…Ch7) Channel x HART SV value.
ChxTV (Ch 0…Ch7) Channel x HART TV value.
ChxFV (Ch 0…Ch7) Channel x HART FV value.
ChxPVStatus (Ch 0…Ch7) Channel x HART PV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
ChxSVStatus (Ch 0…Ch7) Channel x HART SV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
ChxTVStatus (Ch 0…Ch7) Channel x HART TV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
ChxFVStatus (Ch 0…Ch7) Channel x HART FV status. See HART PV, SV, TV, and FV Status on page 210 for more information.
1756-OF8IH Input Tags - Analog and HART by Channel, Configure HART Device = No (AB:1756_OF8IH_AnalogHARTbyChannel:I:0)
Member Name Type Style Description
BrokenWire BOOL Decimal Indicates that current isn’t flowing through the module as expected. Broken wiring, RTB removal, or a powered-
off field device can cause this.
Indicates a problem with HART data from the field device on Channel x. Examples are HART not enabled, HART
HARTFault BOOL Decimal device not connected, HART communication failure due to noise. These field device status conditions also
cause this to be set: Device Malfunction, PV Out of Limits, Loop Current Saturated, and Loop Current Fixed.
HART communication status byte or Response code from a recent HART reply (first status byte). See Response
ResponseCode SINT Binary Code and Field Device Status on page 204 for more information.
FieldDeviceStatus SINT Binary Field device status byte (second status byte).
PVOutOFLimits BOOL Decimal The primary variable is beyond its operating limit.
VariableOutOfLimits BOOL Decimal A device variable that is not mapped to the PV is beyond its operating limits.
CurrentSaturated BOOL Decimal The loop current has reached its upper or lower endpoint limit and can’t increase or decrease any further.
CurrentFixed BOOL Decimal The loop current is being held at a fixed value and isn’t responding to process variations.
MoreStatus BOOL Decimal More status information is available via command 48, ‘Read Additional Status’ information.
ColdStart BOOL Decimal A power failure or device reset occurred.
Changed BOOL Decimal An operation was performed that changed the configuration of the device.
Malfunction BOOL Decimal The device detected a serious error or failure that compromises device operation.
ChxStatus (Ch0…Ch7) SINT Binary
User value equal to or greater than HighLimit configuration value.
HLimitAlarm BOOL Decimal Automatically set to zero when AlarmDisable config bit is set.
User value equal to or greater than the LowLimit configuration value.
LLimitAlarm BOOL Decimal Automatically set to zero when AlarmDisable config bit is set.
Set when Output is ramping to new user value. Cleared when ramping complete. This bit isn’t set if
RampAlarm BOOL Decimal MaxRampRate config value is 0. Automatically set to zero when the AlarmDisable config bit is set.
InHold BOOL Decimal If the HoldForInit config bit is set, the module is waiting for the appropriate Output word.
CalFault BOOL Decimal Set when calibration is invalid for this channel.
NotANumber BOOL Decimal Set when Output word has all 8 bits set (bits 23…30).
Set when Output is commanded to at least 0.1 mA and the circuit is physically open. Open circuit indication can
OpenWire BOOL Decimal also exist if the load resistance exceeds specification.
ExtDeviceStatus SINT Binary Extended device status (from HART cmd9).
MaintenanceRequired BOOL Decimal
DeviceVariableAlert BOOL Decimal Device reports a problem with some measurement.
PowerLow BOOL Decimal
PV REAL Float HART device primary value.
SV REAL Float HART device second value.
TV REAL Float HART device third value.
FV REAL Float HART device fourth value.
PVStatus SINT Hex HART device PV status.
SVStatus SINT Hex HART device SV status.
VStatus SINT Hex HART device TV status.
FVStatus SINT Hex HART device FV status.
64-bit Coordinated System Time. Time stamp that is taken at the time that the input data was sampled in terms
CSTTimestamp INT (2) Hex of coordinated system time, which is a 64-bit value in microseconds coordinated across the modules in the 1756
backplane.
15-bit time from power on/reset in milliseconds. This value is updated when the Output Table changes. If
RollingTimestamp INT Decimal ramping is enabled, the value continuously updates until the output value reaches the user value. If the module
has entered a faulted state, the value is updated continuously.
1756-OF8IH Input Tags - Analog and HART PV by Channel, Configure HART Device = Yes (AB:1756_OF8IH_AnalogHARTbyChannel_1:I:0)
Member Name Type Style Description
Calibrating BOOL Decimal Calibration for the channel is in progress.
CalGoodLowRef BOOL Decimal A valid Low Reference signal has been sampled on this channel.
CalBadLowRef BOOL Decimal The Low Reference signal is grossly out of the expected range.
CalGoodHighRef BOOL Decimal A valid high reference signal has been sampled on the channel.
CalBadHighRef BOOL Decimal The high reference signal is grossly out of the expected range.
This bit is set after valid High and Low points are captured and the Calibrate bit in the output word has been
CalSuccessful BOOL Decimal cleared.
PV REAL Float HART device primary value.
SV REAL Float HART device second value.
TV REAL Float HART device third value.
FV REAL Float HART device fourth value.
PVStatus SINT Hex HART device PV status.
SVStatus SINT Hex HART device SV status.
VStatus SINT Hex HART device TV status.
FVStatus SINT Hex HART device FV status.
64-bit Coordinated System Time. Time stamp that is taken at the time that the input data was sampled in terms
CSTTimestamp INT (2) Hex of coordinated system time, which is a 64-bit value in microseconds coordinated across the modules in the 1756
backplane.
15-bit time from power on/reset in milliseconds. This value is updated when the Output Table changes. If
RollingTimestamp INT Decimal ramping is enabled, the value continuously updates until the output value reaches the user value. If the module
has entered a faulted state, the value is updated continuously.
This chapter includes screen captures that show the configuration and calibration of a
ControlLogix® HART analog I/O module with one of the following:
• 1756 HART I/O Analog Add-On Profile (AOP), version 40.12.23 or later installed for Studio
5000 Logix Designer® application, version 35 or earlier
• Studio 5000 Logix Designer application, version 36 or later
These screen captures, showcasing an updated user interface, feature 1756-IF8H and
1756-IF8IH modules. However the procedures are similar for any ControlLogix HART analog I/O
module with either update installed.
For information about configuration and calibration with older versions of programming
software that feature the previous, tab-based user interface, see Appendix F.
Add a New Module Follow these steps to add a ControlLogix HART analog I/O module to your Studio 5000 Logix
Designer application project.
IMPORTANT You can’t change any information in these views if you are in Hard Run
mode. Hard Run mode means that the keyswitch is in the Run position.
1. From the I/O Configuration tree, right-click the 1756 backplane and select New Module.
2. Find and select the module that you want to add, and select Create.
The Device Definition dialog appears.
Configure Your Module To change your module configuration, on the Module Properties tab for the module, select
Overview from the left navigation.
You can review the current setup, or select Device Definition to modify these parameters.
Overview View and Module Definition Parameters
Parameter Action Values
Select the series letter that matches the series of your
Series module. This can be determined using FactoryTalk® Linx Dropdown menu
or by referencing the label on the side of your module.
Select the revision number that matches the major and Dropdown menu
Revision minor revisions of your module.
• Exact Match
Select the electronic keying method
Electronic Keying See Electronic Keying on page 20 for more information • Compatible Module (default)
• Disable Keying
• Data
Connection Select the connection type • Listen-only - has no configuration data, doesn’t send output data
See Listen-only Mode on page 26 for more information.
• Analog Only
• Analog and HART PV
Input Data Select the input data mode
• Analog and HART by Channel
See HART Configuration for more information.
Configure HART Device(s) Enable or disable the Configure HART Device(s) feature.
Values that can be added in the HART Command view are PV
NOTE: Available only for the 1756-IF8IH and If you select Yes, a HART Command view is added to the Damping (seconds), PV Units, PV Upper Range, PV Lower Range, and
1756-OF8IH modules when the Input Data left navigation, in which you specify configuration PV Transfer Function.
format is Analog and HART by Channel. values to be sent to the HART device.
Coordinated System Time Not configurable Timestamped
Data Format Not configurable Float
HART Configuration
The Input Data type that you select on the Device Definition dialog determines how HART field
device data can be accessed.
HART field device data is gathered through the automatic collection of HART Field Device
Process Variables and Health information. You can also access HART field device data with
pass-through messages. See Use a CIP MSG to get HART Data on page 167 and Use HART
Modules with Asset Management Software on page 181 for more information.
This table shows which configuration options provide HART data in the input tag and which
provide pass-through message access.
HART Data Configuration Options
Enable HART Checkbox HART Data Input Tag Present? HART Data Valid For This Channel? Pass-through Message Access for
Input Data Format (Channels or ChX view) MSG or Asset Management
Not selected No
Analog only No No
Selected Yes
Not selected Yes No No
Analog and HART PV
Selected Yes Yes Yes
Not selected Yes No No
Analog and HART by Channel
Selected Yes Yes Yes
Choose Analog and HART PV if you prefer the members of the tag to be arranged similar to
non-HART analog input modules. The analog values for all channels are grouped near the end
of the tag. This option makes it easy to view all eight analog values at once.
Choose Analog and HART by Channel if you prefer Status, Analog Value, and Device Status for
each channel to be together in the tag. This arrangement makes it easier to view all data that
is related to one field device.
Even if you don’t enable HART on all channels, the Analog and HART PV and Analog and HART by
Channel input tags include space for the data. However, this data space is marked with a HART
Fault to indicate that the data isn’t valid. This feature lets you add HART instruments later
without disturbing the tag layout.
View Module Information To view identification, status, and other details about your module, select Device Information
from the left navigation.
and Status
The Device Information view appears. The data that is displayed comes directly from the
module when the project is online.
Identification
The Identification section lists the Vendor, Product Type, Product Name, Revision, Product
code, and Serial number associated with your module.
Status
The Status section displays the current operational status of the module.
Parameter Description
Major Fault None, Unrecoverable, or Recoverable.
None, Unrecoverable, or Recoverable.
Minor Fault Recoverable can mean that you have a channel fault such as wire off.
Internal State Indicates the module mode.
Indicates if an owner controller that is connected to the module configured the module. Once a
Configured module is configured, it stays configured until the module is reset or power is cycled, even if the
owner drops connection to the module.(1)
Owned Indicates if an owner controller is connected to the module.(1)
Displays Match or Mismatch. This field does not account for the Electronic Keying or Minor
Revision selections for the module as specified on the Device Definition dialog.
Displays If the Physical Module
For this condition to exist, the following elements of Device Information must mirror
Module Identity the values configured in the Device Definition:
Match • Vendor
• Module type (the combination of product type and code for a particular vendor)
• Major revision
Mismatch Does not agree with what is specified on the Device Definition dialog.
(1) This information applies to the I/O module only and not to adapters, scanners, bridges, or other communication modules.
IMPORTANT You can refresh the module at any time while online, but you cannot
reset the module when in implicit protected mode.
Resetting the module restores output signals to default conditions.
Apply Changes
If the following conditions exist when you select OK or Apply, the information that is displayed
is automatically sent to the controller:
• You’re online in Program, Remote Program, or Remote Run mode, and
• This controller is the owner controller, and
• You’ve changed the module configuration in the software.
The controller tries to send the information to the module (if the module connection isn’t
inhibited). If you do not select OK or Apply, your changes aren’t sent to the controller.
Set Module Connection To configure the connection between your input module and a controller, select Connection
from the left navigation.
Use the Channels View To To configure multiple channels in a single view, select Channels from the left navigation.
Configure Multiple Channels
These parameters are not available in Run mode.
IMPORTANT Unless specifically noted, parameters are not available in Run mode.
Changes made to the parameters that are displayed in the Changes made to the parameters located below the Channels table
Channels table apply only to the individual channel that is selected. apply to all channels.
The Channels table found at the top of the Channels view displays a list of all channels and
some of the parameters that you can configure per channel. Changes that are made in the
Channels table apply only to the channel that’s selected.
Input Module Channel Parameters in the Channels Table
Parameter Action Notes
Select a value from Indicates the input type as Current or Voltage.
Input Type the dropdown
menu. • The 1756-IF8IH module does not support voltage ranges
Select a value from
Input Range the dropdown If HART is enabled, the input range must be 0…20 mA or 4…20 mA.
menu.
• When HART isn’t enabled for a channel:
– HART messages aren’t sent on this channel.
– HART pass-through messages aren’t sent.
– HART data for this channel isn’t updated in the input tag.
• If you select a HART PV or HART by Channel input tag on the Device Definition dialog, process data (PV, SV, TV, and FV)
from the HART instrument is included in the input tag. If you selected Analog only, the additional process data isn’t
Select or clear the included in the input tag.
Enable HART checkbox for the • Regardless of the choice of input tag, HART communication can be enabled for each channel to provide pass-through
channel. HART message access. If Enable HART isn’t selected, this pass-through message access isn’t available.
• We recommend that you Enable HART for any channel that has a connected HART device. This selection is so that
information can be displayed on the HART Device Information view and accessed by FactoryTalk AssetCentre software.
• On the 1756-IF8H module, all channels share the HART modem. For this module, HART response time is better if you enable
only the needed HART channels. The other input modules (1756-IF16H, 1756-IF16IH, and 1756-IF8IH) have a separate HART
modem for each channel.
Changes made to the parameters located below the Channels table on the Channels view of an
input module apply to all channels listed in the table.
Parameters That Apply To All Input Channels
Parameter Action Notes
• Determines the interval of time at which updated information is supplied to the controller.
Select a value from • The default is 88.
Real Time Sample (RTS) 18…10,000 ms.
• See Real Time Sample (RTS) on page 22 for more information.
• See Real-Time Sample Values table on page 137 for RTS choices available for each Module Filter setting.
• Because the digital HART communication signals are in the 1200…2400 Hz range, the module filter can’t be set to 1000 Hz
Select a value from if HART is enabled.
Device Filter (-3 dB) the dropdown • See the Module Filter Values table on page 145 to select a value.
menu.
• See Module Filter on page 30 (1756-IF8H) or page 51 (1756-IF8IH) for more information.
• HART replies that are received from the Field Device in response to pass-through messages that have been sent are kept
for this long. Retrieve them within this time or the module discards them.
Select a value from • The default is 15.
Keep HART Replies 1…255 s. IMPORTANT: We do not recommend a value of less than 15 seconds.
• See Use a CIP MSG to get HART Data on page 167 for more information.
• Determines how often pass-through messages occur.
– Once per two channels scanned (default)- After two channels have PVs scanned to the input tag, a pass-through
message is sent (if one is pending).
Select a value from – Once per module scan - Select this value if you want to minimize the impact pass-through message clients have on
Pass through(1) the dropdown reading the PVs into the input tag.
menu. – Once per channel scan - After each channel has its PVs scanned to the 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 FactoryTalk AssetCentre,
higher priority than reading PV, SV, TV, FV, and field device health into the input tag. See the Input Module Pass-through
Setting, Ratio, and Priority table on page 137 for more information.
(1) Series B modules do not support Pass-through Setting. Pass-through scanning is fixed at one pass-through per channel scan on Series B modules.
Changes made to the parameters that are displayed in the Changes made to the parameters located below the Channels table
Channels table apply only to the individual channel that is selected. apply to all channels.
The Channels table that is found at the top of the Channels view displays a list of all output
channels and some of the parameters that you can configure per channel. Changes that are
made in the Channels table apply only to the output channel that’s selected.
Individual Output Channel Parameters in the Channels Table
Parameter Action Notes
Choose a value from the Indicates the output type as Current or Voltage.
Output Type dropdown menu • The 1756-OF8IH module does not support voltage ranges.
Choose a value from the 0…20 mA or 4…20 mA is required for HART.
Output Range dropdown menu
• Unselected by default.
• Output range must be 0…20 mA or 4…20 mA.
• When a channel isn’t enabled:
– HART messages aren’t sent on this channel.
– HART pass-through messages aren’t sent.
– HART data for this channel isn’t updated in the input tag.
• If you selected HART PV or HART by Channel as the Input Data on the Device Definition dialog, process data (PV, SV, TV, and
FV) from the HART instrument is included in the input tag. If you selected Analog only, the process data isn’t included in the
Select or clear the input tag.
Enable HART checkbox for the channel.
• Regardless of the choice of input tag, HART communication can be enabled for each channel to provide pass-through HART
message access. If Enable HART isn’t selected, this pass-through message access isn’t available.
• We recommend you Enable HART for any channel that has a HART device that is connected so that information can be
displayed on the HART Device Information view.
• 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.
• On the 1756-OF8H module, all channels share the HART modem. For this module, HART response time is better if you enable
only the needed HART channels. The 1756-OF8IH module has a separate HART modem for each channel.
Changes made to the parameters located below the Channels table on the Channels view of an
output module apply to all channels listed in the table.
Parameters That Apply To All Output Channels
Parameter Action Notes
• 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 that you have sent are kept for this long. You must retrieve them within this time or the module
Keep HART Select a value from discards them.
Replies 1…255 s
• The default is 15.
IMPORTANT: We do not recommend a value of less than 15 seconds.
• Determines how often pass-through messages occur.
– Once per two channels scanned (default)- 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
Select a value from the
Pass through(1) dropdown menu reading the PVs into the input tag.
– Once per channel scan - After each channel has its PVs scanned to the 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 FactoryTalk AssetCentre
higher priority than reading PV, SV, TV, FV, and field device health into the input tag. See the Output Module Pass-through
Setting, Ratio, and Priority table on page 139 for more information.
When Specifies the behavior of the outputs if communications fail in Program mode:
Communication Select an option • Leave outputs in Program Mode state
Fails in Program
Mode • Change outputs to Fault Mode state
(1) Series B modules do not support Pass-through Setting. Pass-through scanning is fixed at one pass-through per channel scan on Series B modules.
Use the ChX View To To configure the parameters for an individual module channel, expand Channels in the left
navigation and select a specific ChX.
Configure a Single Channel These parameters are not available in Run mode.
IMPORTANT Unless specifically noted, parameters are not available in Run mode.
Scaling to Engineering Units Channel data values in the output tag can be in engineering units such as kg, m, or percent. 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, suppose that you have a temperature transmitter that produces 4 mA current at
-180 °C (-292 °F) and 20 mA current at +750 °C (1382 °F). If you want to use °C in your control
program, configure the values as shown in this table.
Signal Engineering
High 20 750
Low 4 -180
If you’re using HART field devices, we recommend setting Engineering High and Low to the field
device Upper Range and Lower Range Values. This selection is so that the field device and
module use the same engineering units. If online, these values are displayed on the HART
Device Information view.
Scaling High Engineering appears dimmed in Run and Hard Run mode.
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 Run and Hard Run mode.
Scaling Example
To configure the module to tell you how full a tank is, you’d want it to give 0% when the tank is
empty and 100% when the tank is full. If the sensor that measures the tank signals 4.5 mA
when the tank is empty and 17 mA when the tank is full, the configuration would be as shown.
This configuration creates a relationship between the electrical signal that the tank gauge
generates and the number that is sent to the Logix Controller for use in the control system.
Graphically, the relationship looks like this:
The module measures the signals that are slightly higher and lower than the sensor provides
for this tank. Setting the High or Low Engineering Units does not limit the values to within that
range. The module still measures signals from 4…20 mA. In this example, if the module senses
20 mA, it reports that the tank is 124% full. A signal of 0 mA is reported as -4% full, or ‘less
than empty’.
To have the tank level reported in liters instead of percent, put the capacity of the tank as the
High Engineering value. If you have a 750 liter tank, as in the previous example, put 750
instead of 100 and you get the scaling relationship shown.
Set Module Resolution Resolution is the smallest amount of change that the module can detect.
Resolution is sometimes expressed in bits. If 16 bits of resolution are available, the module can
detect 65536 different signal values. If configured for 4…20 mA, it could discern the difference
between 10…10.0003 mA, but it wouldn’t distinguish between10…10.0002 mA.
Resolution affects how the module measures analog signals. Scaling converts the analog
signal to Engineering Units for convenience in your control system. In the previous 16-bit
example and the 750 liter tank example in the previous section, you would have a resulting
resolution of 0.0146 liters. As the tank fills, the volume reading could jump from a reading of
250 liters to 250.015 liters without displaying any values between. Because of sampling,
filtering, and RPI, you can see more or fewer intermediate values, depending on the fill rate.
The resolution of analog input modules depends on the module and the filter configuration. To
measure a rapidly changing signal, a configuration with less resolution is used. For
information about the resolution available, see the following locations.
Available Resolution for This Module Page
1756-IF8H 30
1756-IF8IH 51
1756-IF16H 68
1756-IF16IH 85
1756-OF8H 98
1756-OF8IH 111
Set Input Module Alarms - To configure alarm parameters for each individual input module channel, expand Channels in
the left navigation, expand a specific ChX, and select Alarms.
1756-IF8H, 1756-IF8IH
The ChX - Alarms view appears.
Use these parameter descriptions to configure the alarms for the 1756-IF8H and 1756-IF8IH
modules. For more information, see Process Alarms on page 33 or page 54, and Rate Alarm on
page 33 or page 54.
ChX - Alarms view Parameters
Available in
Parameter Action Notes Hard Run Mode?
Disable All Alarms Select Disables all alarms for a channel. No
Maintains an alarm triggered condition for any of the process alarms, even after the condition ceases. The
Latch Process Alarms Select No
alarm unlatches only with an explicit message that acknowledges the alarm.
• The High Engineering and Low Engineering parameters on the Channel or ChX view set the maximum and
minimum values for these alarms.
Process Alarming • Alarm thresholds are in engineering units.
• A deadband appears around each value.
• Sets the level of input to a channel that causes the module to set the High High alarm.
High High (HH) • The alarm remains active until the input returns below this level by more than the deadband.
• If Latch Process Alarms is selected, the ChXHHAlarm indication remains set until explicitly cleared.
• Sets the level of input to a channel that causes the module to set the High alarm.
High (HI) Enter the values • The alarm remains until the input returns below this level by more than the deadband. No
• If Latch Process Alarms is selected, the ChXHAlarm indication remains set until explicitly cleared.
• Sets the level of input on a channel that causes the module to set the Low alarm.
Low (LO) • The alarm remains until the input returns above this level by more than the deadband.
• If Latch Process Alarms is selected, the ChXLAlarm indication remains set until explicitly cleared.
• Set the level of input to a channel that causes the module to set a Low Low alarm.
Low Low (LL) • The alarm remains until the input returns above this level, more than the deadband.
• If Latch Process Alarms is selected, the ChXLLAlarm indication remains set until explicitly cleared.
Set Output Module Limits To configure limit parameters for each individual output module channel, expand Channels in
the left navigation, expand a specific ChX, and select Limits.
Limits Example
If your output controls a valve positioner that’s configured to use Percent of Stroke for
engineering units, you can enter 0 as the Low Clamp and 62 for High Clamp. Enter 62 only if
you don’t want the valve to be over 62% open at any time for any reason. Even if a PIDE
instruction calculates the valve must open more to achieve process Setpoint, the output
module clamps it to 62% open.
Configure HART Field Device When Configure HART Device is set to Yes in the Device Definition settings of a 1756-IF8IH or
1756-OF8IH module, you can access the ChX - HART Command view.
The ChX - HART Command view allows you to configure and send PV Damping and PV Range
values to the HART Field Device connected to the selected channel.
To configure the HART Field Device parameters for an individual module channel, expand
Channels in the left navigation, expand a specific ChX, and select HART Command.
These HART Field Device parameters can be configured in the ChX - HART Command view.
Checkbox Parameter Description
Value that changes the response time of
the HART Field Device to smooth variations
Enable HART Device PV Damping Configuration PV Damping in output readings caused by rapid
changes in input.
Engineering units for the HART PV. Select
PV Units from the dropdown menu. See Appendix D
for a list of unit codes.
Highest value for PV in the specified
PV Upper Range
Enable HART Device PV Range Configuration engineering units.
Lowest value for PV in the specified
PV Lower Range engineering units.
PV Transfer Function Form of the PV transfer function. Select
from the dropdown menu.
To view information about the attached HART field device that the HART module collects,
expand Channels in the left navigation, expand a specific ChX, and select HART Device
Information.
These parameters can be examined in the ChX - HART Device Information view.
HART Device Information Parameters
Parameter Description
Displays the tag name of the HART Field Device. The tag name is entered into the Field Device to
Tag indicate its location and purpose in the plant.
Displays the text that was entered in the Message parameter of the HART Field Device. The use
Message of this parameter can vary. One possible use is to store information such as who last calibrated
the device, or reference to documentation.
Displays the Descriptor field from the HART Field Device. The Descriptor is a text message that
Descriptor can be stored in the device to help identify the device or it can be used for other plant-specific
purposes.
Displays the date that is entered in the device. This date is often used to record the last
Date calibration date, but it’s up to you to maintain it. It’s displayed in the format that is selected for
your computer with the Regional and Language settings on the Control Panel.
Displays a Yes or No indicating if the HART Field Device is write protected. If a device is write
protected, some parameters can’t be changed via HART communication. Sometimes devices do
Write Protect not indicate that the configuration has changed when their write-protect setting changes. This
condition causes the previous value to remain displayed here. You can inhibit/uninhibit the
HART module to refresh this value.
Displays the manufacturer name (for example, Allen-Bradley or Endress + Hauser) or the
Manufacturer ID numeric value for the manufacturer. Use the Company Identification Code table as a guide, as
shown in Appendix E.
Displays the device type for Endress + Hauser devices or a numeric value for all other
manufacturer devices. Device type indicates the type of the device of the manufacturer, or
Device Type product name. For example, Cerabar S pressure transmitters from Endress + Hauser have
Device Type 7.
Displays a number that represents the device ID. Device ID is a serial number that is assigned by
Device ID the manufacturer that is unique among all devices that are produced by that manufacturer.
Displays a number that represents the final assembly number. The Final Assembly Number is
Final Assembly used for identifying the materials and electronics that comprise the field device. It’s normally
Number changed when electronics or other components are upgraded in the field. In some instances,
this number references a drawing number.
Channel status is available only for:
• 1756-IF8H and 1756-OF8H firmware revision 2.002 or later
Status
• 1756-IF16H firmware revision 1.002 or later
• 1756-IF16IH firmware revision 1.001 or later
Device status is available only for:
• 1756-IF8H and 1756-OF8H firmware revision 2.002 or later
Diagnostic Code
• 1756-IF16H firmware revision 1.002 or later
• 1756-IF16IH firmware revision 1.001 or later
In HART, the Primary Variable (PV) is signaled on the 4…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 area 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 HART Device Information view.
PV • 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 HART Device Information view.
• 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.
Displays the following revision attributes.
• Universal - denotes the version of the HART specification to which the device conforms.
Revision • Device
• Software
• Hardware
Refresh Select to update all attributes that are displayed on this view for the corresponding channel.
When the HART Device Status is not OK, of the following messages will appear in place of the
HART Device Information parameters in the view.
HART Device Status Message
The HART module is offline No online data is shown because the project is offline. (Standard message)
HART is enabled, but the HART Field No online data is shown because the HART device is initializing.
Device isn’t responding
HART not found No online data is shown because the HART device is not found.
HART isn’t enabled for this channel No online data is shown because the HART device is not enabled
You can specify a tag name, message, and descriptor for the HART device on the selected
channel. You can enter values in the text fields or copy existing entries that are already stored
on the device. When you select OK, the specified values are sent to the device via HART
messages.
Calibrate Your Module Follow these steps to calibrate your module and view the calibration data that is exchanged
via CIP™ messages for each channel.
IMPORTANT The module must be online and not be in Implicit Protected Mode. We
recommend that you inhibit your module before calibration.
1. Select Connection from the left navigation.
The Connection view appears.
This table describes the data that is displayed on the Calibration view.
Parameter Description (All Fields Are Read-only)
Displays 0…20 mA for current channels or -10…10V for voltage channels, which
Calibration Range are based on the output range selection on the Channels or ChX view.
Calibration Gain Displays the calibration gain when the module is on line.
Calibration Offset Displays the calibration offset when the module is on line.
Displays OK or Error, depending on the result of the last calibration, when the
Calibration Status module is on line.
Displays the date on which a successful calibration was most recently
Last Successful Calibration performed.
6. Select OK.
The Calibration Wizard appears.
7. Select the desired channels for calibration, and use the radio button to calibrate all
simultaneously, or individually.
12. If any channel reports an error, return to step 8 and select Retry until the channel
calibration status is OK.
13. If the error persists indefinitely, select Stop to exit calibration.
The channel remains calibrated to the accuracy level achieved at the factory or as of
the last field calibration.
14. Once the channel status is OK, select Next to proceed to the next channel.
15. Once the status of all channels is OK, select Next.
The Attach High Reference dialog appears.
16. Set the current source to the high reference range. Set the precision source to the high
reference noted in the high reference column. Click 'Next' to perform the calibration.
The next channel will be ready for the high reference. Click 'Next' to proceed to calibrate
the next channel.
17. Repeat step 9 until all selected channels are calibrated to the high reference. When all
channels are calibrated to the high reference, click 'Next' again to complete calibration.
18. Calibration is now complete. Select 'Finish' to close the Calibration Wizard.
The Calibration view is now updated with the most recent calibration data.
Notes:
When HART data is included in the input tag and a channel has HART enabled, the
ControlLogix® HART I/O module automatically collects HART data. The module also places the
most common Dynamic Process Data and Device Health information directly in the input tag.
See the chapter for each module for a complete listing of the fields in the input, output, and
configuration tags.
The most important of these direct or derived measurements is assigned to the PV (Primary
Variable) and the analog signal represents its value. Additional 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 input tag of the module in HART.ChxPV (for Analog and HART PV
data format) or Chxx.PV (for Analog and HART by Channel data format). 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 can’t be changed.
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 can’t open any further, it can set its I.HART.Ch03.SVStatus to
2#11100000. This configuration indicates 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.
The module collects the PV, SV, TV, and FV data as described in this table.
Command 3 does not provide PVStatus, SVStatus, TVStatus, or FVStatus. HART devices that
indicate Command 3 have their Dynamic Variable Status values reported 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’s 0, meaning bad.
Some devices do not have four dynamic variables. In this case, they can report a NaN value to
indicate that 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 that are configured for HART (for the
8-channel modules), the number of pass-through message commands, the presence of
handheld communicators or other secondary masters, and the response speed of the field
device.
When eight channels are in use on the non-isolated 8-channel modules, the HART update rate
is in the 10-second range.
IMPORTANT Verify that the actual HART update rate is appropriate for your
application. Remember that pass-through message traffic, additional
status information, secondary masters, and communication errors can
delay the update rate. On the non-isolated 8-channel modules, because
all channels share the HART modem, 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.
The diagrams on page 164 and page 165 show 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’re interleaved in the auto scanning. Logix controllers can send pass-
through messages by using CIP MSG instructions, and Asset Management systems can send
them.
HART messages are sent on only one channel at a time when you’re using the 1756-IF8H or
1756-OF8H module. When you’re using the 1756-IF8IH, 1756-OF8IH, 1756-IF16H, or 1756-IF16IH
module, messages are sent on all channels simultaneously.
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 module to indicate that new data is available for GetDeviceInfo CIP MSG.
See Use a CIP MSG to get HART Data for more information, and specifically page 176 for HART
pass-through schedule choices.
1756-IF8H and 1756-OF8H Flowchart
Yes
Signal Configuration
Yes Changed in Input Tag
Reply?
Send Command 3
or 9 to Read Put Device in Scan List
Dynamic Process
Variable
No
No
Read
New Configuration
Remove Device
Configuration Information,
from Scan List
Indicated? Yes Such As Tag,
Units, Range
No
Next Channel
Last Yes
Channel?
No
Go To First Channel
Device in No
Scan List?
Send Command 0
Read Unique Identifier
Yes
Read Configuration
Yes Information, Such as
Reply?
Tag, Units, Range
No
Signal Configuration
Changed in Input Tag
Send Command 3
or 9 to Read
Dynamic Process Put Device in Scan List
Variable
No
Read
New Configuration
Remove Device Configuration
from Scan List Information,
Indicated? Yes Such As Tag,
Units, Range
No
Signal Configuration
Changed in Input Tag
Process 1 Pass-
through Message
Notes:
This chapter shows how to use HART data in your Logix controller via MSG instructions.
Examples of reasons to do this include the following:
• You need only occasional access to the data, and do not want to use the extra network
capacity and memory that is required for the Analog with HART PV or Analog and HART
by Channel input tags.
• You need extra information, such as device tag, ranges, or manufacturer-specific
information.
• You must send a manufacturer-specific command to the HART device.
Usually, everything you must use a HART instrument is automatically collected and placed in
the input tag, and these CIP™ MSG instructions aren’t needed.
The 1756 ControlLogix® HART analog modules support these broad categories of MSG-based
HART access:
• CIP formatted messages to retrieve common HART data cached in the module.
• CIP messages that contain HART formatted commands that are passed directly to the
HART field device for processing. These messages are called pass-through messages.
By 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 that are described in this chapter use MSG instructions. For more information
and examples about MSG instructions, refer to Chapter 13, which explains how to use MSG
instructions to unlatch alarms or reconfigure modules.
Use MSG Instructions to The HART Object that is contained in the module handles both categories of MSG. There’s one
HART Object for each channel. Some CIP messages can be sent to the Class Instance (Instance
Access the HART Object 0) of the HART object. Most MSGs are sent to a specific instance of the HART object that is
associated with a particular channel.
This table shows channel and instance correspondence.
Channel Instance
0 1
1 2
2 3
3 4
… …
15 16
CIP Services to Access You can get the following kinds of HART data easily from the HART object:
Common HART Data • HART field device information - Similar to data displayed on the Module Properties HART
Device Information view of the Studio 5000 Logix Designer® application.
• 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 is in the input tag. The mapped Device
Variable Code and the engineering units are included.
The data in these commands is returned in the format that is used by Logix controllers, so it’s
easy to use in your control program. HART data is natively in another format, called big-endian,
but the 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 is helpful to you. Consult the HART protocol specification for further
information on HART commands. See Appendix on page 203 for more information.
See Appendix on page 219 for an explanation of the engineering unit code numbers.
Reply Packet - Request Succeeded
Offset Field Data Type Definition
0 Status Command status
1 HARTCommandStatus HART Device reply Status Byte # 1 (response code)
USINT
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 HART Primary variable
8…11 SV HART Secondary variable
REAL
12…15 TV HART Third variable
16…19 FV HART Fourth variable
Use a CIP Generic MSG to In this example, this rung of ladder logic retrieves fresh HART device information whenever the
1756-IF8H, 1756-IF8IH, 1756-IF16H, 1756-IF16IH, 1756-OF8H, or 1756-OF8IH module indicates that
get HART Device a new configuration is available.
Information
If the Device Information is critical to your application, be sure to check for .ER errors and
implement a recovery strategy.
The device information for the HART Device on channel 7 is read and put in DevInfoAnswer.
The following figures show string types for HARTTag, HARTDescriptor, and HARTMsg.
HARTTag String Type
For more information and sample code demonstrating a HART device Get Device Information
Message, see Knowledgebase Technote, 1756 I/O HART Message Sample Code: Get Device
Information.
IMPORTANT You must sign in to the Rockwell Automation website before accessing
the Knowledgebase.
Use CIP Services to The HART object supports these CIP messages for HART pass-through messaging: Pass-
through Init, Pass-through Query, Flush Queue (rarely needed).
Pass-through a HART
Message to a HART 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.
Field Device
Native HART data is in another format than used by Logix controllers. HART uses the big-
endian format and Logix uses the little-endian format. This means the order of the bytes in a
number is 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 that are supported by the HART object are simplified.
The module provides the 5-byte address that is required by HART messages and the Checksum
is calculated automatically for you.
Source
HART Command Bytes
MSG
Destination
Service 16#4E
Handle
Pass-through Query
Source
Handle
MSG
Service 16#4F Destination
HART Reply Bytes
The CIP reply from the Init service includes a number that is 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 sends 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 eight channels are in use, the time for a reply would be about 10 seconds if there was no
other pass-through traffic.
HART Module Scanning 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
Diagram with Pass-through pass-through message for each channel scanned.
Messages
It can be configured for lower priority in the Channels view of the Module Properties.
1756-IF8H and 1756-OF8H Flowchart
Yes
Signal Configuration
Yes Changed in Input Tag
Reply?
Send Command 3
or 9 to Read Put Device in Scan List
Dynamic Process
Variable
No
No
Read
New Configuration
Remove Device
Configuration Information,
from Scan List
Indicated? Yes Such As Tag,
Units, Range
No
Next Channel
Last Yes
Channel?
No
Go To First Channel
Device in No
Scan List?
Send Command 0
Read Unique Identifier
Yes
Read Configuration
Yes Information, Such as
Reply?
Tag, Units, Range
No
Signal Configuration
Changed in Input Tag
Send Command 3
or 9 to Read
Dynamic Process Put Device in Scan List
Variable
No
Read
New Configuration
Remove Device Configuration
from Scan List Information,
Indicated? Yes Such As Tag,
Units, Range
No
Signal Configuration
Changed in Input Tag
Process 1 Pass-
through Message
HART Pass-through CIP See the tables in this section for pass-through information.
Message Layout Details
Pass-through Init (Service Code 16#4E)
These tables show the request and reply packet structures for the Pass-through Init service.
Short Format (Ladder) Request Packet (Service Code 16#4E)
Offset Field Data Type Definition
0 HART Command USINT HART Command Number(1) (2)
1 HART Data Size USINT Number of Data Bytes for Selected HART Command(1)(2)
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 B on page 203 for more information.
(2) If this field is displayed as SINT in the Logix Designer application, values > 127 appear negative.
3 Queue space remaining USINT Number of queues still Available for This Channel(1)
If status (bit 0) is 35, refer to Pass-through Error Codes on page 179 for the error code description.
Reply Size = 4 bytes
(1) If this field is displayed as SINT in the Logix Designer application; values > 127 appear negative.
Reply Packet
Offset Offset Data Type Definition
Query Status
00 = Success
0 Status USINT 34 = Running - try again later
35 = Dead
(See MsgReady in Input Tag)
1 HART Command USINT Echo of HART Command(1)
2 HART CommStatus USINT HART Reply Status Byte #1 (response code)(1)
HART Reply Status Byte #2(1)
3 HART FieldDeviceStatus USINT If status (bit 0) is 35, refer to the Pass-through Error Codes on page 179 for
the error code description.
4 Data Size USINT Number of Data Bytes in Reply for HART Command(1)
5…259 HART Reply Data … USINT Data Bytes Returned in Data Field of HART Reply to Requested Command(1)
Reply Size = 6…260 bytes
(1) If this field is displayed as SINT in the Logix Designer application, values > 127 appear negative.
This table defines the error codes that are received when the pass-through status (bit 0) is
Dead (35).
Pass-through Error Codes
Value Definition Notes
16#81 No response from HART device
16#82 Invalid long frame address Applies to only FULL-HART format
16#83 Invalid HART message checksum Applies to only FULL-HART format
16#84 HART Command not allowed (blocked by module) Applies to only Ladder Pass-through
16#85 Invalid channel selected N/A for 1756-IF16H and 1756-IF16IH modules
16#86 Channel isn’t HART Enabled
16#87 Channel does not have a device that is connected Module hasn’t established HART communication on this channel
Size of CIP message too small to hold size of HART message Module reviews HART data size field in request and validates that the incoming CIP message size is
16#89 large enough to send all data
16#8A Invalid handle Applies to only Query message
16#8B Invalid start delimiter Applies to only FULL-HART format
Flush Queue can be sent to have a ControlLogix HART Analog I/O module discard any pending
HART replies awaiting a query command. These replies are automatically discarded after a
period, which is configurable in the Channels view of the Module Properties. This value is
usually 15 seconds. Unless you must discard the replies faster than 15 seconds, you do not
need to use this Flush Queue command.
HART Pass-through You use HART Pass-through Messaging to send HART commands. For example, HART command
18 writes the tag, descriptor, and date.
Message Ladder Logic
Example For more information and sample code demonstrating the setup of HART command 18,
specifically, see Knowledgebase Technote, 1756 I/O HART Message Sample Code: pass-thru
Message. The sample code can be referenced as an example of how to send any pass-through
message command. Additional information HART commands can be found in Appendix B.
Instance 1 means Channel 0 within the INIT message.
For HART command 18, data will need ASCII packed and unpacked.
For add-on instructions for the ASCII pack and unpack operation, see Knowledgebase
Technote, 1756 I/O HART Message Sample Code: AOI instructions for handling HART Packed ASCII
format.
HART Read Dynamic The principles of the HART Pass-through Message Ladder Logic Example can be applied to
sending HART command 9, which reads Device Variables from the HART field device. You send
Variables Example the list of the Device Variable codes that you want, and the field device responds with its
values, units, classification, and status.
For this specific operation, the information obtainable via HART command 9 can instead be
obtained more easily by using service 4B messaging.
For an example of a Reading Dynamic Variables with service 4B, see Knowledgebase Technote,
1756 I/O HART Message Sample Code: Read Dynamic Variables.
Considerations for Asset The following must be considered before using the I/O modules with asset management
systems, such as FactoryTalk® AssetCentre or Endress+Hauser FieldCare systems.
Management Systems
• HART must be enabled before any asset management system access is possible,
including scanning for multiplexers, if supported by your asset management software.
You do not need to include HART PV or HART by Channel data in your input tag. You must
select the Enable HART option in the ChX view, however.
• The Logix controller must be connected to the I/O module. If the Logix controller isn’t
connected, the module configuration wasn’t sent to the HART module, and the channel
isn’t yet configured for HART access.
• If you use 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’s the only master present. In this mode, the
handheld can conflict with the I/O 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 I/O module. Asset management systems can miss this indication if they’re offline
at the time of a change.
• A separate configuration-changed indication is in the field device status for the primary
master (1756-IF8H, 1756-IF8IH, 1756-IF16, or 1756-IF16IH module) and secondary master
(handheld, for example). The I/O modules do not reset the secondary master
configuration changed status.
HART traffic from asset management pass-through messages or from secondary masters
slows the update rate of HART data in the controller or other pass-through message clients.
With 1756-IF8H Series A and 1756-OF8H Series A modules, extra traffic on one channel affects
other channels. With all other HART modules or series, this is not the case.
Frequently Asked Questions Read this section for answers to frequently asked questions.
How do you use ControlLogix® HART analog 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 the 1756
backplane.
What else is required to use asset management software with a ControlLogix® HART analog 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 FactoryTalk AssetCentre
software. For non-FDT/DTM based asset management software, such as Emerson AMS,
use Connects software, available from Spectrum Controls.
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 that are 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 that
are necessary to configure, monitor, and maintain the devices. See https://
www.fdtgroup.org/ for more information on FDT/DTM technology and to search for
registered DTMs.
What communication DTMs are used with ControlLogix HART analog I/O modules?
Go to the Rockwell Automation Product Compatibility and Download Center (rok.auto/
pcdc), select Downloads by Product, search for “1756 DTM”, and chose the desired
version.
What version of Connects software by Spectrum Controls is needed for the ControlLogix HART
analog I/O modules?
Use Spectrum Connects software, version 6.0 or later. This software is needed only for
asset management software that is not FDT/DTM-based.
This information does not apply to the following modules, as Alarms and Limits aren’t
available:
• 1756-IF16H, 1756-IF16HK
• 1756-IF16IH, 1756-IF16IHK
• 1756-IF8IH, 1756-IF8IHK (when Configure HART Device(s) = Yes)
• 1756-OF8IH, 1756-OF8IHK (when Configure HART Device(s) = Yes)
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 and
cause specific behavior to occur, for example, the unlatching of a high alarm.
For example, you want to unlatch all process alarms on the module, but real-time control of
your process still occurs 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.
2. Add a message instruction to a rung by selecting MSG on the toolbar above the ladder
project.
IMPORTANT We suggest you name the tag to indicate the module service that the
message instruction sends. In the example, the message instruction is
used to unlatch a high alarm, and the tag name reflects this.
5. Select Create.
The Configuration tab of the Message Configuration dialog provides information on what
module service to perform and where to perform it. For example, unlatch high alarms (module
service) on channel 0 of a module (where to perform the service).
IMPORTANT The Studio 5000 Logix Designer® application defaults information, such
as the following, depending on the message type:
• Service type
• Service Code
• Class
• Instance
• Attribute
• Source element
• Source length
• Destination
You’re required to select a Service type and configure the Instance field.
Instance represents the module channel on which the service is
performed, if appropriate.
From the Service Type pull-down menu, select a service. Available services include unlatching
high high, high, low low, low, ramp, and rate alarms.
The Communication tab of the Message Configuration dialog provides information on the path
of the message instruction. For example, the slot number of a 1756-OF8IH module
distinguishes exactly for which module a message is designated.
3. Select OK.
The module name appears in the Path field on the Communication tab of the Message
Configuration dialog.
Unlatch Alarms in the The ladder logic rungs 0…4 in this example show how to unlatch the High high, High, Low, Low
low, and Rate alarms.
1756-IF8H or 1756-IF8IH
Module
IMPORTANT An I/O module must be configured to latch alarms, before you can
perform unlatch services using ladder logic. If a module that is not
configured to latch alarms receives an unlatch service, the message
instruction errors.
All alarms for channel 0 can be unlatched simultaneously with one
message instruction by leaving the Attribute box blank.
IMPORTANT An I/O module must be configured to latch alarms, before you can
perform unlatch services using ladder logic. If a module that is not
configured to latch alarms receives an unlatch service, the message
instruction errors.
All alarms for channel 0 can be unlatched simultaneously with one
message instruction by leaving the Attribute box blank.
Unlatch Alarms in the The ladder logic rungs 5…7 in this example show how to unlatch the high limit, low limit, and
ramp alarms.
1756-OF8H or 1756-OF8IH
Module
Rung 6 unlatches the low limit alarm. Select the box in each
rung to see the
configuration and
communication
Rung 7 unlatches the ramp alarm. information dialog that
is associated with it.
From the Configuration dialog for Rung 5, you can select a service type and configure the
instance.
IMPORTANT Name an I/O module to set the message path under the communication
dialog for that module.
Reconfigure a Module It’s sometimes advantageous to change the functional operation of a module in the
ControlLogix system automatically via ladder logic rather than using the Logix Designer
application to reconfigure a module. This way, changes in the process can dictate when the
reconfiguration takes place rather than performing that function manually.
Use the steps in this example when reconfiguring a module via ladder logic.
1. Move the new configuration parameters to the Configuration portion of the tag
structure that is 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, make sure that their
relationship to each other is in a format the module accepts.
These tables list module parameters that you can change via ladder logic:
Use Module Indicators HART analog I/O modules have indicators to show module status.
Modules with Status-Only Indication Modules with Per-Channel Indication
CALIBRATION IN
CAL IN
O FLT O
K K
FLT
OK IN
OK
FLT
To see fault status, select the Device Information view on the Module Properties tab of the
Studio 5000 Logix Designer® application. A channel fault, such as wire off, is displayed as a
‘Recoverable’ minor fault.
• From the RSLinx® software, if you select RSWho and see 1756-Module, install the EDS file
available from the Rockwell Automation Product Compatibility and Download Center at
rok.auto/pcdc.
• In some versions of the Logix Designer application or RSLogix 5000® software, the
profiles for the ControlLogix® HART analog I/O modules aren’t included. Access the
Rockwell Automation Product Compatibility and Download Center at rok.auto/pcdc and
download the Add-on Profile (AOP).
• In RSLogix 5000 software, version 15 and later or the Logix Designer application, with an
error about ControlNet® Attribute, use Scheduled Connections, or shutdown and restart
the RSLogix 5000 software or the Logix Designer application.
• If you can’t find HART data, look in the subfield Local:7:I.HART at the bottom of the tag or
in chassis:7:I.Chxx.PV for data that are grouped by channel.
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 seconds, the module
throws away replies before you get a chance to retrieve them. This action affects both
MSG pass-through messages and PC-based asset management, such as FieldCare
software. We recommend 15 seconds for this parameter.
• Be sure that you have a HART device. Foundation Fieldbus, PROFIBUS PA, and plain 4…20
devices look the same on the outside and power up OK.
• Write protect jumper isn’t reported correctly. This condition gets refreshed only if the
device reports it changed. Endress+Hauser and Rosemount devices do not. Disable
HART then re-enable HART to get it refreshed on the HART Device Info dialog.
For issues encountered while troubleshooting the pass-through message, 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.
• Name tags and UDTs similarly to group them together for convenience. For example,
start the related tags with the same prefix.
• Check .ER and Status.
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 condition
persists for 10 seconds after you select Refresh several times, suspect a HART
communication problem or no device.
• Be sure that a channel is HART Enabled in the Channel view.
• Be sure that values appear, meaning HART communication is okay.
• Check PV values Local:7:I:HART.Ch0PV or Local:12:I.Ch00.Data for numbers that are
changing.
• Check analog values Local:7:I:Ch0Data or Local:12:I.Ch00.Data for numbers that are
changing; for the 1756-OF8H module, check that is valid.
• You must have a Logix connection for asset management to deliver the configuration to
the module. From the Module Properties dialog, select HART Device Info to see if it
shows information.
Use the Logix Designer In addition to the status displayed on the module, the Logix Designer application alerts you to
fault conditions in one of these ways:
Application to Troubleshoot
• Warning symbol in the I/O Configuration next to the module - This symbol appears when
a Module the connection to the module is broken
Module Configuration Errors In the Logix Designer application, if “(Code 16#0009) Module Configuration Rejected:
Parameter Error” is displayed in the Connection view of the Module Properties tab, the
additional fault code value describes the configuration error.
16#000E 16#001E 16#002E 16#003E 16#004E 16#005E 16#006E 16#007E Invalid HART rate, HART rate fixed at 1:1
16#000F 16#001F 16#002F 16#003F 16#004F 16#005F 16#006F 16#007F High Alarm < Low Alarm
16#0010 16#0020 16#0030 16#0040 16#0050 16#0060 16#0070 16#0080 Low Low Alarm > Low
16#0011 16#0021 16#0031 16#0041 16#0051 16#0061 16#0071 16#0081 High High alarm < High Alarm
16#0012 16#0022 16#0032 16#0042 16#0052 16#0062 16#0072 16#0082 Invalid Alarm Deadband
16#0008 16#0018 16#0028 16#0038 16#0048 16#0058 16#0068 16#0078 Invalid Digital Filter
16#000A 16#001A 16#002A 16#003A 16#004A 16#005A 16#006A 16#007A High Signal and/or Low Signal outside of selected input range
16#000B 16#001B 16#002B 16#003B 16#004B 16#005B 16#006B 16#007B High Signal Low Signal
16#000C 16#001C 16#002C 16#003C 16#004C 16#005C 16#006C 16#007C Sensor Offset set to NaN
16#000D 16#001D 16#002D 16#003D 16#004D 16#005D 16#006D 16#007D High Engineering = Low Engineering
Channel (cont.)
8 9 10 11 12 13 14 15
16#0087 16#0097 16#00A7 16#00B7 16#00C7 16#00D7 16#00E7 16#00F7 Invalid Input Range
Extended Fault Codes
16#0088 16#0098 16#00A8 16#00B8 16#00C8 16#00D8 16#00E8 16#00F8 Invalid Digital Filter
16#008A 16#009A 16#00AA 16#00BA 16#00CA 16#00DA 16#00EA 16#00FA High Signal and/or Low Signal outside of selected input range
16#008B 16#009B 16#00AB 16#00BB 16#00CB 16#00DB 16#00EB 16#00FB High Signal Low Signal
16#008C 16#009C 16#00AC 16#00BC 16#00CC 16#00DC 16#00EC 16#00FC Sensor Offset set to NaN
16#008D 16#009D 16#00AD 16#00BD 16#00CD 16#00DD 16#00ED 16#00FD High Engineering = Low Engineering
16#0011 16#0027 16#003D 16#0053 16#0069 16#007F 16#0095 16#00AB Low Signal Greater or Equal to High Signal
16#0012 16#0028 16#003E 16#0054 16#006A 16#0080 16#0096 16#00AC Sensor Offset set to NaN
16#0013 16#0029 16#003F 16#0055 16#006B 16#0081 16#0097 16#00AD High Engineering Equal to Low Engineering
16#0014 16#002A 16#0040 16#0056 16#006C 16#0082 16#0098 16#00AE Invalid HART Rate
16#0015 16#002B 16#0041 16#0057 16#006D 16#0083 16#0099 16#00AF Bad Clamp
Wiring System Uses As an alternative to buying removable terminal blocks and connecting the wires yourself, you
can buy a wiring system with 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 pre-wired cables that match the I/O
module to the interface module. This section provides a list of the AIFMs available for
use with ControlLogix® analog I/O modules.
• I/O module-ready pre-wired 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.
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 that uses other wiring termination methods can require
application-specific approval by the certifying agency.
These tables list the AIFMs and pre-wired cables that can be used with the 1756-IF8H, 1756-
IF16H, and 1756-OF8H modules.
IMPORTANT For the latest list, see the Digital/Analog Programmable Controller
Wiring Systems Technical Data, publication 1492-TD008.
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.
HART Field Communication 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 many devices can
perform.
• Device-specific commands provide access to functions that can be unique to a
particular device.
Message Structure Read this section for a description of the 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.
Master-slave Operation
HART is a master-slave protocol. This means that the master originates each message
transaction; the slave (field) device replies when it receives a command message that is
addressed to it. The reply from the slave device acknowledges that the command was
received and can contain data that the master requested.
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 the
following:
• Not to turn on the carrier more than 5 bit times before the start of the message (the
preamble)
• Not to turn off more than 5 bit times after the end of the last byte of the message (the
checksum)
After each transaction is completed, the master pauses for a short time before sending
another command, to provide an opportunity for the other master to break in if it wishes. This
way, the two masters (if they’re present) take turns communicating with the slave devices.
Typical message lengths and delays allow two transactions per second.
Burst Mode
The ControlLogix® HART analog modules do not support burst mode.
Response Code and Field Two bytes of status that are 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
Device Status 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. The details
of the error are also reported in the rest of that byte. The second byte is then all zeros.
Communication errors are typically errors that are 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 the Studio 5000 Logix Designer® application, if the leftmost bit of the ResponseCode is set,
it displays a negative number. In this case, the ResponseCode represents a communication
fault. Change the display format to hexadecimal to interpret communication status.
If the leftmost bit of the ResponseCode is 0 (value 0…127), then there was no communication
error and the value is a ResponseCode 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 ResponseCode, contact your HART field device manufacturer or the HART
specification.
Response Codes and Field Device Status
Response Code
Description
If Bit 7 is And Bits 6…0 are
1 16#40 Parity Error Vertical parity error - The parity of one or more of the bytes received by the device wasn’t odd
Overrun error - At least one byte of data in the receive buffer of the UART was overwritten before it was read (for
1 16#20 Overrun Error example, the slave did not process an incoming byte fast enough)
Framing error - The UART did not detect the Stop Bit of one or more bytes received by the device (for example, a
1 16#10 Framing Error mark or 1 wasn’t detected when a Stop Bit should have occurred)
Longitudinal parity error - The Longitudinal Parity that was calculated by the device did not match the Check
1 16#08 Checksum Error Byte at the end of the message
1 16#04 (Reserved) Reserved - Set to zero
1 16#02 RX Buffer Overflow Buffer overflow - The message was too long for the receive buffer of the device
1 16#01 (undefined) Reserved - Set to zero
0 0 No command-specific error
If no error was detected in the outgoing communication, the second byte contains status
information that pertains to the operational state of the field or slave device.
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 configuration of the device
5 16#20 Cold start - A power failure or device reset occurred
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 isn’t responding to process variations
2 16#04 Loop current saturated - The loop current has reached its upper or lower endpoint limit and can’t increase or decrease any further
1 16#02 Non-primary variable out of limits - A device variable that is 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
IMPORTANT The 16# means that this number is Hex display style.
HART PV, SV, TV, and FV HART PV, SV, TV, and FV are dynamic variables that contain the values of device variables,
which are various direct or indirect process measurements that are performed by the HART
Status 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, performed via a handheld configurator
or asset management system, such as FactoryTalk® AssetCentre or Endress+Hauser FieldCare
system.
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.
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 module creates a status value that is
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, which indicates Good, Not Limited. Otherwise, the value is set to 0, which indicates
Bad, Not Limited, no specific information available.
Notes:
Code Number Details This table maps engineering unit code numbers to their meaning and abbreviations. These
codes are used in the process variable range display.
Unit Codes Description from HART Specification Abbreviated Units
1 inches of water at 20 °C (68 °F) inH2O (20 °C or 68 °F)
2 inches of mercury at 0 °C (32 °F) inHg (0 °C or 32 °F)
3 feet of water at 20 °C (68 °F) ftH2O (20 °C or 68 °F)
4 millimeters of water at 20 °C (68 °F) mmH2O (20 °C or 68 °F)
5 millimeters of mercury at 0 °C (32 °F) mmHg (0 °C or 32 °F)
6 pounds per square inch psi
7 bars bar
8 millibars mbar
9 grams per square centimeter g/square cm
10 kilograms per square centimeter kg/square cm
11 pascals Pa
12 kilopascals kPa
13 torr torr
14 atmospheres atm
15 cubic feet per minute cubic ft/min
16 gallons per minute usg/min
17 liters per minute L/min
18 imperial gallons per minute impgal/min
19 cubic meter per hour cubic m/h
20 feet per second ft/s
21 meters per second m/s
22 gallons per second usg/s
23 million gallons per day million usg/d
24 liters per second L/s
25 million liters per day ML/day
26 cubic feet per second cubic ft/s
27 cubic feet per day cubic ft/d
28 cubic meters per second cubic m/s
29 cubic meters per day cubic m/d
30 imperial gallons per hour impgal/h
31 imperial gallons per day impgal/d
32 Degrees Celsius °C
33 Degrees Fahrenheit °F
34 Degrees Rankine °R
35 Kelvin °K
36 millivolts mV
37 ohms ohm
38 hertz hz
39 milliamperes mA
This appendix offers reference information regarding connecting with ControlLogix® HART
analog I/O modules in a remote chassis via a ControlNet® network.
For more information about ControlLogix ControlNet modules, see the ControlNet Network
Configuration User Manual, publication CNET-UM001.
For information about how to migrate from an existing ControlNet network to an EtherNet/IP™
network, see the ControlNet to EtherNet/IP Migration Reference Manual,
publication CNET-IN005.
Using RSNetWorx and The I/O configuration portion of the RSLogix 5000® programming software generates the
configuration data for each I/O module in the control system, whether the module is in a local
RSLogix 5000 Software or remote chassis. A remote chassis, also known as networked, contains the I/O module but
not the module’s owner-controller. A remote chassis can be connected to the controller via a
scheduled connection on the ControlNet network or an EtherNet/IP network.
RSLogix 5000 configuration data is transferred to the controller during the program download
and later 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, or unscheduled
connections on the ControlNet network, are ready to run as soon as the configuration data has
been downloaded. However, to enable scheduled connections to I/O modules on the ControlNet
network, you must schedule the network by using RSNetWorx for ControlNet software.
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 communication options that are specified for each module
during configuration.
IMPORTANT You must run RSNetWorx for ControlNet software whenever a new I/O
module is added to a scheduled ControlNet chassis. When a module is
permanently removed from a remote chassis, we recommend that you
run RSNetWorx for ControlNet software to reschedule the network and
optimize the allocation of network bandwidth.
Remote Input Modules Consider the case of an analog I/O module that is connected to the owner controller via a
scheduled ControlNet® network. In this case, the RPI and real-time sample interval define
Connected Via ControlNet when the module multicasts data within its own chassis. Only the RPI value, however,
Network determines how often the owner controller receives module data over the network.
The specified RPI not only instructs the module to multicast data within its own chassis, but
reserves a spot in the data stream that flows across the ControlNet network. The timing of this
reserved spot does not coincide with the exact RPI value. The control system makes sure that
the owner controller receives data at least as often as the specified requested packet interval.
Input Module in Remote Chassis with Requested Packet Interval Reserving Spot in Flow of Data
ControlNet Network
Input data at least as often as RPI
The reserved spot in the network data stream and the module real-time sample is
asynchronous. So there are best and worst case scenarios as to when the owner controller
receives updated channel data from the module in a networked chassis.
• 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 - 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.
RPI, not real-time sample interval, dictates when module data is sent over the network.
Therefore, we recommend that you set the RPI less than or equal to the real-time sample
interval. This setting helps make sure that the owner controller receives updated channel data
with each receipt of data.
Remote Output Modules The RPI value instructs the controller to multicast output data within its own chassis, and
reserves a spot in the stream of data that flows across the ControlNet network. These
Connected Via ControlNet conditions occur when remote analog output modules are connected to the owner controller
Network via a scheduled ControlNet network.
The timing of this reserved spot does or does not coincide with the exact value of the
requested packet interval. However, the control system makes sure that the output module
receives data at least as often as the specified requested RPI.
Output Module in Remote Chassis with Requested Packet Interval Reserving a Spot in Flow of Data
.
Output Module
Owner Controller ControlNet Bridge ControlNet Bridge
ControlNet Network
Output data at least as often as RPI
The reserved spot on the network and when the controller sends the output data are
asynchronous. So there are best and worst case scenarios as to when the module receives the
output data from the controller in a networked chassis.
• 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 - 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.
IMPORTANT These best and worst case scenarios indicate the time that is required
for output data to transfer from the controller to the module once the
controller has produced it.
The scenarios do not consider when the module receives new data
(updated by the user program) from the controller. That result is a
function of the length of the user program and its asynchronous
relationship with the requested packet interval.
Notes:
Add a New Module Follow these steps to add a ControlLogix HART analog I/O module to your Studio 5000 Logix
Designer® application project.
IMPORTANT You can’t change any field in these tabs if you are in Hard Run mode.
Hard Run mode means that the keyswitch is in the Run position.
1. From the I/O Configuration tree, right-click the 1756 backplane and select New Module.
2. In the Select Module Type dialog, find and select the module that you want to add.
3. Select Create.
The New Module dialog appears.
Customize Your Module To create a custom configuration for your module, select Change on the General tab.
HART Configuration
The Input Data selection that you make in the Module Definition dialog determines how HART
field device data can be accessed. Access the Module Definition dialog from the General tab.
HART field device data is gathered through the automatic collection of HART Field Device
Process Variables and Health information. You can also access HART field device data with
pass-through messages. See Use a CIP MSG to get HART Data on page 167 and Use HART
Modules with Asset Management Software on page 181 for more information.
This table shows which configuration options provide HART data in the input tag and which
provide pass-through message access.
HART Data Configuration Options
Enable HART Checkbox Pass-through Message Access for MSG or
Input Data Format HART Data Input Tag Present?
(Configuration Tab) Asset Management
Not selected No
Analog only No
Selected Yes
Fields present in tag, but data for this
Not selected No
Analog and HART PV channel not valid
Selected Yes Yes
Fields present in tag, but data for this
Not selected No
Analog and HART by Channel channel not valid
Selected Yes Yes
Even if you aren’t enabling HART on all channels, the Analog and HART PV input tag includes
space for the data. However, this data space is marked with a HART Fault to indicate that the
data isn’t valid. This feature lets you add HART instruments later without disturbing the tag
layout.
Set Module Connection Use the following information to make selections on the Connection tab.
Parameter Description
Defines when the module multicasts its data onto the local chassis
Requested Packet Interval backplane.
Helps prevent connection to the module. Use only if you do not want
Inhibit Module the module to be put into service.
Major Fault on Controller If Connection Fails The Logix controller performs a major fault if communication to this
While in Run Mode I/O module fails.
Appears only for HART analog modules that use the Logix Designer
application version 18 or later in a remote EtherNet/IP chassis.
Use Unicast Connection over EtherNet/IP™ Use the default checkbox if there are no other controllers in ‘Listen-
Only’ mode.
Clear the checkbox if there are other ‘listening’ controllers in the
system.
View Module Information The Module Info tab displays module and status information. This tab is populated with data
that comes directly from the module. The information on this window is displayed when the
project is online.
Status
The Status box in the right-hand column of the Module Info tab displays the current
operational stats of the module.
Parameter Description
Major Fault None, Unrecoverable, or Recoverable.
None, Unrecoverable, or Recoverable.
Minor Fault Recoverable can mean that you have a channel fault such as wire off.
Internal State Indicates the module mode.
Indicates if an owner controller that is connected to the module configured the module. Once
Configured a module is configured, it stays configured until the module is reset or power is cycled, even
if the owner drops connection to the module.(1)
Owned Indicates if an owner controller is connected to the module.(1)
Displays Match or Mismatch as described in the table. This field does not account for the
Electronic Keying or Minor Revision selections for the module as specified on the General tab.
Displays If the Physical Module
Agrees with what is specified on the General tab. For the Match condition to
Module Identity exist, the following items must agree:
• Vendor
Match
• 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 tab.
(1) This information applies to the I/O module only and does not apply to adapters, scanners, bridges, or other communication
modules.
IMPORTANT Resetting the module breaks connections and restores output signals
to default conditions.
Apply Changes
If the following conditions exist when you select Apply or OK, the information is automatically
sent to the controller:
• You’re online in Program, Remote Program, or Remote Run mode, and
• This controller is the owner controller, and
• You’ve changed the module configuration in the software.
The controller tries to send the information to the module (if the module connection isn’t
inhibited). If you do not select OK or Apply, your changes aren’t sent to the controller.
Configure Channels The following information describes how to configure the module channels. Differences
among the modules are noted.
Available in Hard
Parameter Action Notes Run Mode?
• Unselected by default.
• Output range must be 0…20 mA or 4…20 mA.
• When a channel isn’t enabled:
– HART messages aren’t sent on this channel.
– HART pass-through messages aren’t sent.
– HART data for this channel isn’t updated in the input tag.
• If you selected a HART PV or HART by Channel input tag on the General tab, process data (PV, SV,
TV, and FV) from the HART instrument is included in the input tag. If you selected Analog only, the
Enable HART Select or clear process data isn’t included in the input tag. No
• Regardless of the choice of input tag, HART communication can be enabled for each channel to
provide pass-through HART message access. If Enable HART isn’t selected, this pass-through
message access isn’t available.
• We recommend you Enable HART for any channel that has a HART device that is connected so
that information can be displayed on the HART Device Info tab.
• 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.
Enter scaling values for High
Scaling Signal, Low Signal, High See Scaling to Engineering Units on page 236 for more information. No
Engineering, and Low Engineering
Output Range Choose a value from the 0…20 mA or 4…20 mA is required for HART. No
pull-down menu
• The default value is 0.00.
Sensor Offset Enter a value from • The offset value is in engineering units. No
-9,999,999…99,999,999 (float)
• The Sensor Offset is added to the data value to determine signal level.
• Select this option 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 the value being held. The
output holds when the following occurs:
– Powerup 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).
Hold for – The controller returns to Run mode after Program mode (continues to hold at the configured
Select or clear value that was held in Program mode. No
Initialization
• 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 option isn’t selected, the output
switches as quickly as possible to the first value commanded by the controller.
For example, suppose that you have a temperature transmitter that produces 4 mA current at
-180 °C (-292 °F) and 20 mA current at +750 °C (1,382 °F). If you want to use °C in your control
program, configure the values as shown in this table.
Signal Engineering
High 20 750
Low 4 -180
If you’re using HART field devices, we recommend setting Engineering High and Low to the field
device Upper Range and Lower Range Values. This selection is so that the field device and
module use the same engineering units. If online, these values are displayed on the HART
Device Info tab.
Scaling High and Low Signal
Set the High and Low Signal values for the module. The High Signal value must be greater than
the Low Signal value.
Set the High Engineering value for the module. The High Engineering value must not equal the
Low Engineering value. This value is in engineering units and 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.
Set the Low Engineering value for the module. The Low Engineering value must not equal the
High Engineering value. This value is in engineering units and 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 Example
To configure the module to tell you how full a tank is, you would configure scaling to give you
0% when the tank is empty and 100% when the tank is full. Suppose the sensor that measures
the tank signals 4.5 mA when the tank is empty and 17 mA when the tank is full. You would
configure scaling as shown.
This configuration creates a relationship between the electrical signal the tank gauge
generates and the number sent to the Logix Controller for use in the control system.
Graphically, the relationship looks like this:
The module measures signals slightly higher and lower than the sensor provides for this tank.
Setting the High or Low Engineering Units does not limit the values to within that range. The
module still measures signals from 4…20 mA. In this example, if the module senses 20 mA, it
reports that the tank is 124% full. A signal of 0 mA is reported as -4% full, or ‘less than empty’.
To have the tank level reported in liters instead of percent, put the capacity of the tank as the
High Engineering value. If you have a 750 liter tank, as in the previous example, put 750
instead of 100 and you get the scaling relationship shown.
Module Resolution
Resolution is the smallest amount of change that the module can detect.
Resolution is sometimes expressed in bits. If 16 bits of resolution are available, the module can
detect 65536 different signal values. If configured for 4…20 mA, it could discern the difference
between 10…10.0003 mA, but it wouldn’t distinguish between10…10.0002 mA.
Resolution affects how the module measures analog signals. Scaling converts the analog
signal to Engineering Units for convenience in your control system. In the previous 16-bit
example and the 750 liter tank example in the previous section, you would have a resulting
resolution of 0.0146 liters. As the tank fills, the volume reading could jump from a reading of
250 liters to 250.015 liters without displaying any values between. Because of sampling,
filtering, and RPI, you can see more or fewer intermediate values, depending on the fill rate.
The resolution of analog input modules depends on the module and the filter configuration. To
measure a rapidly changing signal, a configuration with less resolution is used. For
information about the resolution available, see the following locations.
Available Resolution for This Module Page
1756-IF8H 30
1756-IF8IH 51
1756-IF16H 68
1756-IF16IH 85
1756-OF8H 98
1756-OF8IH 111
Set Input Module Alarms - The following information describes how to configure the parameters on the Alarm tab for the
1756-IF8H and 1756-IF8IH modules. For more information, see Process Alarms on page 33 or
1756-IF8H, 1756-IF8IH page 54, and Rate Alarm on page 33 or page 54.
With an individual channel selected, use these parameters to configure the alarms.
Alarm Tab Parameters
Available in
Parameter Action Notes Hard Run Mode?
• The High Engineering and Low Engineering parameters on the Configuration tab set the maximum and
minimum values for these alarms.
• Alarm thresholds are in engineering units.
Process Alarms
• 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.
• Sets the level of input to a channel that causes the module to set the High High alarm.
High High (HH) Enter the values or • The alarm remains active until the input returns below this level by more than the deadband.
drag the • If Latch Process Alarms is selected, the ChXHHAlarm indication remains set until explicitly cleared.
corresponding No
flags on the slider • Sets the level of input to a channel that causes the module to set the High alarm.
High (HI) bar to set the • The alarm remains until the input returns below this level by more than the deadband.
values. • If Latch Process Alarms is selected, the ChXLAlarm indication remains set until explicitly cleared.
• Sets the level of input on a channel that causes the module to set the Low alarm.
Low (LO) • The alarm remains until the input returns above this level by more than the deadband.
• If Latch Process Alarms is selected, the ChXLAlarm indication remains set until explicitly cleared.
• Set the level of input to a channel that causes the module to set a Low Low alarm.
Low Low (LL) • The alarm remains until the input returns above this level, more than the deadband.
• If Latch Process Alarms is selected, the ChXLLAlarm indication remains set until explicitly cleared.
Disable All Alarms Select Disables all alarms for a channel. No
Maintains an alarm triggered condition for any of the process alarms, even after the condition ceases. The
Latch Process Alarms Select No
alarm unlatches only with an explicit message that acknowledges the alarm.
When enabled, a Rate Alarm indication remains set, even when the alarm condition returns to normal. This
Latch Rate Alarm Select latch lets you maintain the alarm even after the condition ceases. The alarm unlatches only with an explicit No
message that acknowledges the alarm.
Set Output Module Behavior The 1756-OF8H and 1756-OF8IH modules have an Output State tab. With an individual channel
selected, the Output State tab lets you program output behavior in Program and Fault modes.
Ramp Rate
The Ramp Rate limits the speed at which an analog output signal can change. This value helps
prevent fast transitions in output from damaging equipment that the output controls. This
feature is available in Run mode. Ramping in Run mode and the ramp rate are set on the
Limits tab.
For the 1756-OF8IH module with Configure HART Device set to Yes, ramping in Run mode and
ramp rate are set on the Output State tab.
The module enters Program mode state if the Connection from Logix is inhibited. If
communication later fails, all channels of the module remain in Program mode.
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.
Communication Failure
If communication fails while in Run mode, the output signal goes to its Fault Mode state. If
communication fails while in Program mode, the output signal behaves as follows.
Select To
Leave outputs in Program mode state Leave the output signal at the configured Program mode value
Change output signal at configured Fault mode value if a
Change output to Fault mode state communication fails (connection from controller breaks)
Set Output Module Limits Use this information to configure the parameters on the Limits tab.
With an individual channel selected, use these parameters to configure the limits.
Output Module Limits Parameters
Available in
Parameter Action Notes Hard Run Mode?
• The High Engineering and Low Engineering parameters on the Configuration tab set the maximum and minimum
values for these alarms.
Limits Enter the • Clamp limits are in engineering units.
values or drag • To change the trigger points by whole numbers, hold down the shift key while dragging the flag on the slider bar.
the
corresponding • See the Limit Example below for further explanation. No
flags on the • The highest value that an output channel can reach in the control process.
High Clamp (HI) slider bar to
• -9,999,999…99,999,999, default is 100.00.
set the values.
• The lowest value that an output channel can reach in the control process.
Low Clamp (LO)
• -9,999,999…99,999,999, default is 0.
Limit Example
If your output controls a valve positioner that’s configured to use Percent of Stroke for
engineering units, you can enter 0 as the Low Clamp and 62 for High Clamp. Enter 0 only if you
don’t want the valve to be over 62% open at any time for any reason. Even if a PIDE instruction
calculates the valve must open more to achieve process Setpoint, the output module clamps it
to 62% open.
Set HART Command - When Configure HART Device is set to Yes for the 1756-IF8IH and 1756-OF8IH modules, a HART
Command tab appears in the Module Properties dialog.
1756-IF8IH, 1756-OF8IH
With an individual channel selected on the HART Command tab, you can specify the HART
device parameters for that channel. These values are sent to the HART device.
View HART Device With an individual channel selected, the HART Device Info tab displays information about the
attached HART field device that the HART module collects.
Information
• If you selected a Listen-Only communication format when you created the module, this
tab isn’t available.
• If HART isn’t enabled for this channel, Channel Not HART Enabled is displayed.
• If HART is enabled, but the HART Field Device isn’t responding, HART initializing is
displayed.
Calibrate a Module Follow these steps to calibrate your module and view the calibration data that is exchanged
via CIP™ messages for each channel.
2. Select Apply.
3. On the Calibration Tab, select Start Calibration.
4. Select OK.
The Calibration Wizard appears.
5. Select the desired channels for calibration, and use the radio button to calibrate all
simultaneously, or individually.
The status of the channel after calibrating for a low reference will appear.
10. If any channel reports an error, return to step 8 and select Retry until the channel
calibration status is OK.
If the error persists indefinitely, select Stop to exit calibration. The channel remains
calibrated to the accuracy level achieved at factory, or the last field calibration.
11. Once the channel status is OK, select Next to proceed to the next channel.
12. Once the status of all the channels is OK, select Next.
The Attach High Reference Voltage Signals dialog appears.
The status of the channel after calibrating for a high reference will appear.
15. If any channel reports an error, return to step 13 and select Retry until the channel
calibration status is OK.
If the error persists indefinitely, select Stop to exit calibration. The channel remains
calibrated to the accuracy level achieved at factory, or the last field calibration.
16. Once the channel status is OK, select Next to proceed to the next channel.
17. Once the status of all the channels is OK, select Next.
The Calibration Completed dialog appears.
The Calibration tab is updated with the most recent calibration data.
This table describes the data that is displayed on the Calibration tab.
Parameter Description (All Fields Are Read-only)
Displays 0…20 mA for current channels or -10…10V for voltage channels, which
Calibration Range are based on the output range selection on the configuration tab.
Calibration Gain Displays the calibration gain when the module is on line.
Calibration Offset Displays the calibration offset when the module is on line.
Displays OK or Error, depending on the result of the last calibration, when the
Calibration Status module is on line.
Displays the date on which a successful calibration was most recently
Last Successful Calibration performed.
Notes:
The following terms and abbreviations are used throughout this manual.
balanced circuit 1) A circuit whose two sides are electrically alike and symmetrical to a common reference
point, usually ground. 2) Contrasted with unbalanced circuit (page 257).
CIP Acronym for Common Industrial Protocol; a communication protocol, or language, between
industrial devices. CIP™ provides seamless communication for devices on DeviceNet®,
ControlNet®, and EtherNet/IP™ networks.
compatible match An Electronic Keying Protection mode that requires the physical module and the module that is
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.
coordinated system time (CST) Timer value, which is kept synchronized for all modules within one ControlBus™ chassis. The
CST is a 64-bit number with microsecond resolution.
differential 1) Pertaining to a method of signal transmission through two wires. The transmission always
has opposite states. The signal data is the polarity difference between the wires; when one is
high, the other is low. Neither wire is grounded. The circuit can be either a balanced circuit, a
floating circuit, or a circuit with a high-impedance path to ground from either end. Used
regarding encoders, analog I/O circuits, and communication circuits. 2) Contrasted with
single-ended (page 256).
direct connection An I/O connection, where the controller establishes an individual connection with I/O modules.
disable keying An option that turns off all electronic keying to the module. Requires no attributes of the
physical module and the module that is 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 that is
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.
fourth value (FV) Also abbreviated as QV for quaternary value, this dynamic variable contains the fourth value of
Device Variables, which are direct or indirect process measurements by a HART field device.
frequency shift keying A method of using frequency modulation to send digital information that is used by HART field
devices.
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 that is transferred between an I/O module and its
owner-controller. This format also defines the tags that are created for each I/O module.
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, and
results in an interface change with software.
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 that reach a specific group of one or more destinations.
multiple owners A configuration setup where multiple owner-controllers use 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.
primary value (PV) Dynamic variable that contains the primary value of Device Variables, which are direct or
indirect process measurements by a HART field device. See page 16 for more information.
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 ControlLogix feature that lets you install or remove a module or RTB while power is applied.
(RIUP)
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.
secondary value (SV) Dynamic variable that contains the secondary value of Device Variables, which are direct or
indirect process measurements by a HART field device.
single-ended 1) Unbalanced, as when one side is grounded. See unbalanced circuit (page 257) 2) Contrasted
with differential (page 255).
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 memory of the controller where data is stored like a variable.
third value (TV) Dynamic variable that contains the tertiary, or third, value of Device Variables, which are
direct or indirect process measurements by a HART field device.
timestamping ControlLogix process that stamps a change in input, output, or diagnostic data with a time
reference that indicates when that change occurred.
unbalanced circuit 1) A circuit whose two sides are electrically dissimilar, as when one side is grounded. 2)
Contrasted with balanced circuit (page 255).
Notes:
G L
glossary of terms 255 ladder logic
message configuration 185
message instructions 183
H unlatch alarms (1756-OF6VI module) 191
HART limits
additional protocol information 203 view 148
communication 17 listen-only connection 26
data via MSG instructions 167 local chassis
definition 255 input module 22
device output module 25
auto-configuration 114
configuration 132
getting data over CIP MSG 167 M
integrated networks 18 major revision 256
Logix controller 13
protocol 17 manufacturer ID codes 213
variables 162 minor revision 256
writing variables 114 module
HART compatibility accessories 15
1756-IF8IH module 50 calibration 129
hold components 14
initialization 98, 113 configuration 129, 131
data collection 163
filter 30
I channel ADC filter 51, 85
keying 20
implicit protected mode 26 operation 21
inhibit module 256 refresh 134
initialization removal 199
hold 98, 113 reset 134
input resolution 145
circuit diagram scaling 19
1756-IF16H module 74 status 133
1756-IF8H module, current 38 troubleshooting 193
1756-IF8H module, voltage 38 module faults
1756-IF8IH module 55 1756-OF8IH module 118
error codes 198, 199 moduleinformation
module view 133
channel ranges 30
channel status 41, 76, 90
filter 68 N
local chassis 22 network update time (NUT)
multiple owners 27
operation 22 for ControlNet network 256
real time sample 31, 52, 86
remote chassis 24
tag data 161 O
input ranges open circuit detection 53
1756-IF16H module 67 open wire detection 98, 113
1756-IF16IH module 84 operation
1756-IF8IH module 49, 50 input module 22
input tags module 21
analog and HART by channel output 25
Configure HART Device = No 94 output
isolation circuit diagram
1756-IF8IH module 49 1756-OF8H module 101
1756-OF8IH module 115
data echo 25
K error codes 199
keying module
electronic 20 channel status 104, 119
RTB 16 circuit diagrams 101
clamp limit 99, 113
local chassis 25
ramp rate 142
ramp/rate 98, 113
remote chassis 25 S
resolution 98
wiring 100 scaling
operation 25 engineering units 143
overrange module 19
detection 32, 53, 69, 87 secondary value definition 18
overview Set Device Information 153
view 131 software
ownership asset management 19
changing configuration in multiple owner- status
controllers 28 module 133
multiple owners 27, 28, 256
owner-controller 256
T
P tasks
event 24
pass-through messages 167, 175, 176, 178, 180, third value definition 18
195 timestamp 19
power supply triggering event tasks 24
input wiring 36 troubleshooting
wiring 72
module 193
powerup state
1756-OF8IH module 112
primary value definition 18 U
process alarms 54
underrange
protocol
detection 32, 53, 69, 87
HART 17 unicast
communication 28
R connection 135
unlatch alarms 189
ramp rate limit
output module 98, 113, 142
rate alarm 54 V
real time sample (RTS) 22, 31, 52, 69, 86 variables
in a local chassis 22 HART 162
in a remote chassis 24 view
refresh module 134
1756-IF8H alarm 146
remote chassis 1756-IF8IH alarm 146
connecting via EtherNet/IP network 24, 25 alarms 146
input module 24 channels 136
output module 25 ChX 140
remove connection 135
and insert under power (RIUP) 256 device information 133
module 199 limits 148
requested packet interval (RPI) 23, 256 module information 133
local chassis 22 overview 131
reset
module 134 W
resolution
module 145 wire-off detection 70
output module 98 wiring
revision analog interface modules (AIFM) 201
major 256 input diagrams 35, 71, 88
minor 256 output module 100
RPI 22, 23 power supply 36, 72
RSNetWorx pre-wired cables 201
wiring diagram
using with RSLogix 5000 223
RTB keying 16 1756-IF16H module 71
1756-IF16IH module 88
RTS. See real time sample 1756-IF8H module 35
1756-IF8IH module 55
1756-OF8H module 100
1756-OF8IH module 115
Documentation Feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the
form at rok.auto/docfeedback.
At the end of life, this equipment should be collected separately from any unsorted municipal waste.
Rockwell Automation maintains current product environmental compliance information on its website at rok.auto/pec.
Allen-Bradley, ControlBus, ControlFLASH, ControlLogix, expanding human possibility, FactoryTalk, i-Sense, Logix 5000, Rockwell Automation, RSLinx, RSLogix 5000, RSNetWorx, and Studio 5000
Logix Designer are trademarks of Rockwell Automation, Inc.
CIP, ControlNet, DeviceNet, and EtherNet/IP are trademarks of ODVA, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.Ş. Kar Plaza İş Merkezi E Blok Kat:6 34752, İçerenköy, İstanbul, Tel: +90 (216) 5698400 EEE Yönetmeliğine Uygundur