User Manual ControlLogix HART Analog I/O Modules Catalog Numbers 1756-IF8H, 1756-IF16H, 1756-OF8H
Important User Information Solid-state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.rockwellautomation.com/literature/) describes some important differences between solid-state equipment and hard-wired electromechanical devices.
Summary of Changes This manual contains new and updated information. Changes throughout this revision are marked by changes bars, as shown to the right of this paragraph. New and Updated Information This table contains the changes made to this revision. Topic Page Additional Input Data tag, Analog and HART by Channel, is available for the 1756-IF8H and 1756-OF8H analog I/O modules. 54, 80 Power supply wiring diagrams are available for the 1756-IF8H analog input module.
Summary of Changes 4 Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Table of Contents Preface Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Chapter 1 ControlLogix HART Analog I/O Modules Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Chapter 3 ControlLogix Module Operation Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Direct Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input Module Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input Modules in a Local Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Chapter 5 1756-IF16H HART Analog Input Module Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Chapter 7 Configure the Modules with RSLogix 5000 Software Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Create a New Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 HART Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Flush Queue (Service Code= 16#50). . . . . . . . . . . . . . . . . . . . . . . . . . 136 HART Pass-through Message Ladder Logic Example. . . . . . . . . . . . . . . 136 Chapter 9 HART Modules Used with Asset Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Considerations for Asset Management Systems . . . . . . . . . . . . . . . . . . . . 141 Management Software Frequently Asked Questions . . . . . . . . . . . . . . .
Table of Contents Analog and HART by Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Appendix B Use 1492 Wiring Systems with Your Analog I/O Module Wiring System Uses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Appendix C Additional HART Protocol Information Introduction . . . . . . . . . . . . . . . . . . . . .
Preface This manual describes how to install, configure, and troubleshoot ControlLogix highway addressable remote transducer (HART) analog I/O modules. Audience You must be able to program and operate a Rockwell Automation ControlLogix controller to efficiently use your analog I/O modules. In this manual, we assume that you know how to do this. If you do not, before attempting to use this module, refer to the Logix5000 controller documentation, as listed in the related table.
Preface Notes: 12 Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Chapter 1 ControlLogix HART Analog I/O Modules Introduction ControlLogix HART analog I/O modules connect a Logix controller to your process. 1756-IF8H and 1756-IF16H input modules receive the signals from process value transmitters and convert them to temperature, flow, pressure, pH, and other measurements for use in the Logix controller. By using 1756-OF8H HART output modules, the controller adjusts the setting of valves and other devices to keep your process running as desired.
Chapter 1 ControlLogix HART Analog I/O Modules Module Components This figure shows the physical features of the ControlLogix analog I/O modules. 5 3 1 Removable Terminal Block (RTB) 2 6 4 45118 # Physical Feature Description 1 Backplane connector The backplane connector interface for the ControlLogix system connects the module to the ControlBus backplane.
ControlLogix HART Analog I/O Modules Chapter 1 See the figure(1) that shows information about the HART protocol. The Highway Addressable Remote Transducer (HART) protocol supports two-way digital communication, complements traditional 4…20 mA analog signals, and includes the following features: · Predefined commands - Common practice - General purpose - Device specific +0.5 mA 20 mA 0.
Chapter 1 ControlLogix HART Analog I/O Modules Commands can be accepted 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 typically be device maintenance, for example a handheld communicator, as shown below. Primary Master Secondary Master (handheld communicator as secondary master) Slave 44219 Integrated HART Networks Most transmitters are available with a HART protocol interface.
ControlLogix HART Analog I/O Modules Asset Management Software Chapter 1 You can use the modules with asset management software. The following figure shows the use of asset management software, such as FactoryTalk AssetCentre software or Endress+Hauser FieldCare software.
Chapter 1 ControlLogix HART Analog I/O Modules You can find revision information on the General tab of a module’s Properties dialog box. Figure 1 - General Tab IMPORTANT Changing electronic keying selections online may cause the I/O communication connection to the module to be disrupted and may result in a loss of data.
ControlLogix HART Analog I/O Modules EXAMPLE Chapter 1 In the following scenario, Exact Match keying prevents I/O communication. The module configuration is for a 1756-IB16D module with module revision 3.1. The physical module is a 1756-IB16D module with module revision 3.2. In this case, communication is prevented because the Minor Revision of the module does not match precisely.
Chapter 1 ControlLogix HART Analog I/O Modules Release notes for individual modules indicate the specific compatibility details. When a module is created, the module developers consider the module’s development history to implement capabilities that emulate those of the previous module. However, the developers cannot know future developments.
ControlLogix HART Analog I/O Modules EXAMPLE Chapter 1 In the following scenario, Compatible keying allows I/O communication: The module configuration is for a 1756-IB16D module with module revision 2.1. The physical module is a 1756-IB16D module with module revision 3.2. In this case, communication is allowed because the major revision of the physical module is higher than expected and the module determines that it is compatible with the prior major revision.
Chapter 1 ControlLogix HART Analog I/O Modules If you use Disabled keying, you must take full responsibility for understanding whether the module that is being used can fulfill the functional requirements of the application. EXAMPLE In the following scenario, Disable keying prevents I/O communication: The module configuration is for a 1756-IA16 digital input module. The physical module is a 1756-IF16 analog input module.
ControlLogix HART Analog I/O Modules IMPORTANT Timestamping Chapter 1 Changing electronic keying selections online may cause the I/O communication connection to the module to be disrupted and may result in a loss of data. Controllers within the ControlLogix chassis maintain a system clock. This clock is also known as the coordinated system time (CST). You can configure your analog I/O modules to access this clock and timestamp input data or output echo data when the module multicasts to the system.
Chapter 1 ControlLogix HART Analog I/O Modules Module Scaling When using scaling, you change a quantity from one notation to another. To scale a channel, choose two points along the module's operating range and apply corresponding low and high unit values to those points. Scaling lets you configure the module to return data to the controller in units that match the quantity being measured. For example, the analog input module can provide the temperature in degrees Celsius or the pressure in mbar.
Chapter 2 Module Installation Introduction The 1756-IF8H, 1756-OF8H, and 1756-IF16H analog modules use the HART protocol with eight and 16 channels, respectively. This chapter describes basic installation procedures. The table explains the topics discussed in this chapter.
Chapter 2 Module Installation Environment and Enclosure ATTENTION: This equipment is intended for use in a Pollution Degree 2 industrial environment, in overvoltage Category II applications (as defined in IEC 60664-1), at altitudes up to 2000 m (6562 ft) without derating. This equipment is considered Group 1, Class A industrial equipment according to IEC/CISPR 11.
Module Installation Chapter 2 WARNING: • This equipment must be installed in an enclosure providing at least IP54 • • • • • protection when applied in Zone 2 environments. This equipment shall be used within its specified ratings defined by Rockwell Automation. Provision shall be made to prevent the rated voltage from being exceeded by transient disturbances of more than 40% when applied in Zone 2 environments. This equipment must be used only with ATEX certified Rockwell Automation backplanes.
Chapter 2 Module Installation Removal and Insertion Under Power (RIUP) WARNING: When you insert or remove the module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding. Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector. Worn contacts may create electrical resistance that can affect module operation.
Module Installation Power Requirements Chapter 2 ATTENTION: To comply with the CE low voltage directive (LVD), all connected I/O must be powered from a source compliant with safety extra low voltage (SELV) or protected extra low voltage (PELV). WARNING: Use supply wires suitable for 30 °C (86 °F) above surrounding ambient. These modules receive power from the 1756 chassis power supply and require these two sources of power from the backplane. Module Power Requirements, max 1756-IF8H • 300 mA at 5.
Chapter 2 Module Installation Install the Module You can install or remove the module while chassis power is applied. ATTENTION: The module is designed to support removal and insertion under power (RIUP). However, when you remove or insert an RTB with fieldside power applied, unintended machine motion or loss of process control can occur. Exercise extreme caution when using this feature. 1. Align the circuit board with the top and bottom chassis guides. 20861 2.
Module Installation Key the Removable Terminal Block/Interface Module Chapter 2 Wedge-shaped keying tabs and U-shaped keying bands come with your RTB to prevent connecting the wrong wires to your module. Key the positions on the module that correspond to unkeyed positions on the RTB. For example, if you key the first position on the module, leave 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 20850 2.
Chapter 2 Module Installation Wire the Removable Terminal Block WARNING: If you connect or disconnect wiring while the field-side power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding. Wire the RTB with a 3.3 mm (0.13 in.) screwdriver before installing it onto the module. Shielded cable is required when using this module. We recommend using Belden 8761 cable to wire the RTB.
Module Installation Chapter 2 If you cannot ground at the field device, follow these steps. 1. Prepare one end of the cable as shown in step 1 on page 32. Ground at an earth ground on the chassis. Connect the drain wire to a chassis mounting tab. Use any chassis mounting tab that is designated as a functional signal ground. 4M or 5M (#10 or #12) Star Washer 4M or 5M (#10 or #12) Phillips Screw and Star Washer (or SEM screw) Chassis Mounting Tab Drain Wire with Ground Lug 20918 2.
Chapter 2 Module Installation Wire the Module Refer to the individual module chapters for wiring information. Removal Terminal Block Assembly and Installation For this module Page 1756-IF8H 60 1756-IF16H 72 1756-OF8H 83 The following sections describe the steps needed to assemble and install the RTB. Assemble the Removable Terminal Block and the Housing 1. Align the grooves at the bottom of each side of the housing with the side edges of the RTB. 2.
Module Installation Chapter 2 Install the Removable Terminal Block WARNING: When you connect or disconnect the Removable Terminal Block (RTB) with field side power applied, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding. Before installing the RTB, make certain of the following items: • The field-side wiring of the RTB has been completed.
Chapter 2 Module Installation Remove the Removable Terminal Block ATTENTION: The RTB is designed to support removal and insertion under power (RIUP). However, when you remove or insert an RTB with field-side power applied, unintended machine motion or loss of process control can occur. Exercise extreme caution when using this feature. We recommended that field-side power be removed before removing the module. Before removing the module, you must remove the RTB. 1.
Module Installation Remove the Module Chapter 2 Do these steps to remove a module. 1. Push in the top and bottom locking tabs. 20856 2. Pull the module out of the chassis.
Chapter 2 Module Installation Notes: 38 Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Chapter 3 ControlLogix Module Operation Introduction Every I/O module in the ControlLogix system must be owned by a ControlLogix controller. This owner-controller stores configuration data for every module that it owns and can be located locally or remotely, relative to the I/O module’s position. The owner sends the I/O module configuration data to define the module’s behavior and begin operation within the control system.
Chapter 3 ControlLogix Module Operation Direct Connections A direct connection is a real-time data transfer link between the controller and the device that occupies the slot that the configuration data references. ControlLogix analog I/O modules use direct connections only. When module configuration data is downloaded to an owner-controller, the controller attempts to establish a direct connection to each of the modules the data references.
ControlLogix Module Operation Input Modules in a Local Chassis Chapter 3 When a module resides in the same chassis as the owner-controller, the following configuration parameters affect how and when the input module multicasts data: • Real-time sample • Requested packet interval Real Time Sample (RTS) This configurable parameter instructs the module to perform the following operations: • Scan all of its input channels and store the data into on-board memory.
Chapter 3 ControlLogix Module Operation Requested Packet Interval (RPI) This configurable parameter also instructs the module to multicast its channel and status data to the local chassis backplane. The requested packet interval instructs the module to multicast the current contents of its on-board memory when the requested packet interval expires (the module does not update its channels prior to the multicast).
ControlLogix Module Operation Chapter 3 In the example below, the real time sample value is 100 ms and the requested packet interval value is 25 ms. Only every fourth multicast from the module contains updated channel data.
Chapter 3 ControlLogix Module Operation Input Modules in a Remote Chassis If an input module resides in a remote chassis, the role of the requested packet interval and the module’s real time sample behavior change slightly with respect to getting data to the owner-controller, depending on what network type you are using to connect to the modules.
ControlLogix Module Operation Chapter 3 Best Case Scenario - Real Time Sample In the best case scenario, the module performs a real time sample multicast with updated channel data just before the reserved network slot is made available. In this case, the remotely-located owner-controller receives the data almost immediately. Worst Case Scenario - Real Time Sample In the worst case scenario, the module performs a real time sample multicast just after the reserved network slot has passed.
Chapter 3 ControlLogix Module Operation Output Module Operation The requested packet interval parameter governs exactly when an analog output module receives data from the owner-controller and when the output module echoes data. An owner-controller sends data to an analog output module at the period specified in the requested packet interval. Data is not sent to the module at the end of the controller’s program scan.
ControlLogix Module Operation Output Modules in a Remote Chassis Chapter 3 If an output module resides in a remote chassis, the role of the requested packet interval changes slightly with respect to getting data from the owner-controller, depending on what network type you are using to connect to the modules.
Chapter 3 ControlLogix Module Operation Best Case Scenario - Requested Packet Interval In the best case scenario, the controller sends the output data just before the reserved network slot is available. In this case, the remotely located output module receives the data almost immediately. Worst Case Scenario - Requested Packet Interval In the worst case scenario, the controller sends the data just after the reserved network slot has passed.
ControlLogix Module Operation Listen-only Mode Chapter 3 Any controller in the system can listen to the data from any I/O module (that is, input data or ‘echoed’ output data) even if the controller does not own the module. In other words, the controller does not have to own a module’s configuration data to listen to it. During the I/O configuration process, you can specify a ‘Listen-Only’ mode in the Connection box of the Module Definition section on the Module Properties dialog box.
Chapter 3 ControlLogix Module Operation When multiple controllers are configured to own the same input module, the following events occur: • When the controllers begin downloading configuration data, both try to establish a connection with the input module. • Whichever controller’s data arrives first establishes a connection. • When the second controller’s data arrives, the module compares it to its current configuration data (the data received and accepted from the first controller).
ControlLogix Module Operation Configuration Changes in an Input Module with Multiple Owners Chapter 3 You must be careful when changing an input module’s configuration data in a multiple owner scenario. When the configuration data is changed in one of the owners, for example, Controller A, and sent to the module, that configuration data is accepted as the new configuration for the module. Controller B continues to listen, unaware that any changes were made in the module’s behavior.
Chapter 3 ControlLogix Module Operation Notes: 52 Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Chapter 4 1756-IF8H HART Analog Input Module Introduction This chapter describes the features of the 1756-IF8H ControlLogix HART analog input module. The table explains the topics discussed in this chapter.
Chapter 4 1756-IF8H HART Analog Input Module Data Formats Data format determines which values are included in the Input tag of the module and the features that are available to your application. Select the data format on the General tab in RSLogix 5000 software. The following data formats are available for the 1756-IF8H module.
1756-IF8H HART Analog Input Module Chapter 4 Module Filter The module filter attenuates the input signal beginning at the specified frequency. This feature is applied on a module-wide basis, affecting all channels. The module attenuates the selected frequency by approximately -3 dB or 0.707 of the applied amplitude. An input signal with frequencies above the selected frequency is attenuated more while frequencies below the selection receive no attenuation. .
Chapter 4 1756-IF8H HART Analog Input Module 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.
1756-IF8H HART Analog Input Module Chapter 4 Digital Filter The digital filter smooths input data noise transients. This feature is applied on a per channel basis. The digital filter value specifies the time constant for a digital first order lag filter on the input. It is specified in units of milliseconds. A value of 0 disables the filter. The digital filter equation is a classic first order lag equation.
Chapter 4 1756-IF8H HART Analog Input Module 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 are set at the following configurable alarm trigger points: • High high • High • Low • Low low The values for each limit are entered in scaled engineering units. Alarm Deadband You can configure an alarm deadband to work with the process alarms.
1756-IF8H HART Analog Input Module Chapter 4 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.
Chapter 4 1756-IF8H HART Analog Input Module Wiring Diagrams See the figures and tables that show how to wire the module for voltage and current inputs. HART communication is active with current inputs only.
1756-IF8H HART Analog Input Module Chapter 4 The 1756-IF8H is a differential input module. However, there are limitations on its use in Differential mode. Any time 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 happens.
Chapter 4 1756-IF8H HART Analog Input Module For devices powered by individual supplies, when the ground potential of the supplies is expected to differ, Differential mode is recommended. This prevents ground loop currents from flowing between the supplies. However, the potential difference allowable between the supplies must remain within the specified limits.
1756-IF8H HART Analog Input Module Chapter 4 Figure 10 - Simplified 1756-IF8H Voltage Input Circuit +15 V INO+ + Differential Voltage Inputs 10 MΩ 22 KΩ + 249 Ω 1/4 Watt I RTN-O V 0.01 μF 0.01 μF Analog to Digital Converter INO22 KΩ 10 MΩ -15 V RTN RTN RTN RTN 1756-IF8H Module Fault and Status Reporting The 1756-IF8H module multicasts status/fault data to the controller with its channel data.
Chapter 4 1756-IF8H HART Analog Input Module 1756-IF8H Fault Reporting The graphic below offers an overview of the fault reporting process for the 1756-IF8H module. When the module is calibrating, all bits in the Channel Fault word are set. Module Faults 6, 5, 4, and 0 are not used for fault reporting 7 Analog GroupFault 6 2 3 Updated Calibrating StatusReady 1 CalFault If set, any bit in the Channel Fault word also sets the Analog Group Fault in the Module Fault word.
1756-IF8H HART Analog Input Module Chapter 4 1756-IF8H Module Fault Word Bits Bits in this word provide the highest level of fault detection. A nonzero condition in this word reveals that a fault exists on the module. You can examine further to isolate the fault. Table 7 lists tags that can be examined in ladder logic to indicate when a fault has occurred.
Chapter 4 1756-IF8H HART Analog Input Module 1756-IF8H Channel Status Tags Table 9 describes the channel status tags. Table 9 - Tags That Show Channel Status Tag Bit Description ChxCalFault 7 This bit is set if an error occurs during calibration for Channel x, causing a bad calibration. Also sets CalFault in the Module Faults. ChxUnderrange 6 This bit is set when the analog signal is less than or equal to the minimum detectable signal.
Chapter 5 1756-IF16H HART Analog Input Module Introduction This chapter describes the features of the 1756-IF16H ControlLogix HART analog current input module. The table explains the topics discussed in this chapter.
Chapter 5 1756-IF16H HART Analog Input Module Data Formats Data format determines which values are included in the Input tag of the module and the features that are available to your application. Select the data format on the General tab in RSLogix 5000 software. The following data formats are available for the 1756-IF16H module.
1756-IF16H HART Analog Input Module Chapter 5 Module Filter The module filter attenuates the input signal beginning at the specified frequency. This feature is applied on a module-wide basis, affecting all channels. The module attenuates the selected frequency by approximately -3 dB or 0.707 of the applied amplitude. An input signal with frequencies above the selected frequency is attenuated more while frequencies below the selection receive no attenuation. .
Chapter 5 1756-IF16H HART Analog Input Module Real Time Sampling (RTS) This parameter instructs the module how often to scan its input channels and obtain all available data. After the channels are scanned, the module multicasts that data. This feature is applied on a module-wide basis. During module configuration, you specify a real time sampling (RTS) period and a requested packet interval (RPI) period.
1756-IF16H HART Analog Input Module Chapter 5 Digital Filter The digital filter smooths input data noise transients. This feature is applied on a per channel basis. The digital filter value specifies the time constant for a digital first order lag filter on the input. It is specified in units of milliseconds. A value of 0 disables the filter. The digital filter equation is a classic first order lag equation.
Chapter 5 1756-IF16H HART Analog Input Module 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 corresponding to the Underrange condition.
1756-IF16H HART Analog Input Module Chapter 5 The 1756-IF16H is a differential input module. However there are limitations on its use in differential mode. Any time 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 happens.
Chapter 5 1756-IF16H HART Analog Input Module For devices powered by individual supplies, when the ground potential of the supplies is expected to differ, differential mode is recommended. This prevents ground loop currents from flowing between the supplies. However, the potential difference allowable between the supplies must remain within the specified limits. Figure 15 - Power Supplies with Isolated Grounds HART Device 1 Power Supply 1 Ground wire isolated from each other.
1756-IF16H HART Analog Input Module 1756-IF16H Module Fault and Status Reporting Chapter 5 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 conditions. Three levels of tags work together to provide an increasing degree of detail as to the specific cause of faults on the module.
Chapter 5 1756-IF16H HART Analog Input Module 1756-IF16H Fault Reporting This graphic offers an overview of the fault reporting process for the 1756-IF16H module. Module Faults 0…5 are not used 7 Analog GroupFault … 6 CalFault 1 When the module is calibrating, all bits in the Channel Fault word are set. 0 Module Status 7 … 1 0 Updated Calibrating StatusReady If set, any bit in the Channel Fault word also sets the Analog Group Fault in the Module Fault word.
1756-IF16H HART Analog Input Module Chapter 5 1756-IF16H Module Fault Word Bits Bits in this word provide the highest level of fault detection. A nonzero condition in this word reveals that a fault exists on the module. You can examine further to isolate the fault. Table 13 lists tags that can be examined in ladder logic to indicate when a fault has occurred.
Chapter 5 1756-IF16H HART Analog Input Module Notes: 78 Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Chapter 6 1756-OF8H HART Analog Output Module Introduction This chapter describes features of the 1756-OF8H ControlLogix HART analog output module. The table explains the topics discussed in this chapter.
Chapter 6 1756-OF8H HART Analog Output Module Data Formats Data format determines which values are included in the Input tag of the module and the features that are available to your application. Select the data format on the General tab in RSLogix 5000 software. The following data formats are available for the 1756-IF8H module.
1756-OF8H HART Analog Output Module Chapter 6 Ramping/Rate Limiting Ramping limits the speed at which an analog output signal can change. This prevents fast transitions in the output from damaging the devices that an output module controls. Ramping is also known as rate limiting. Table 15 describes the types of ramping that are possible.
Chapter 6 1756-OF8H HART Analog Output Module Open Wire Detection This feature detects when current flow is not present at any channel. The 1756-OF8H module must be configured for 0…20 mA or 4…20 mA operation to use this feature. At least 0.1 mA of current must be flowing from the output for detection to occur. When an open wire condition occurs at any channel, a status bit named ChxOpenWire is set for that channel.
1756-OF8H HART Analog Output Module Chapter 6 Data Echo Data Echo automatically multicasts channel data values that match the analog value that was applied to the module’s screw terminals at that time. Fault and status data are also sent. If selected in the Input Data format, HART secondary process variables and device health are also sent. An example is that I.ChxData is the echo of O.ChxData. They might be different due to Ramp, Clamp, or Hold for Initialization.
Chapter 6 1756-OF8H HART Analog Output Module Use Module Block and Output Circuit Diagrams This section shows the module output circuit diagram. Figure 18 - 1756-OF8H Output Circuit Diagram V OUT - # 250 Ω + - 24V 0.1 μF D/A Converter 16K 5K +18.
1756-OF8H HART Analog Output Module 1756-OF8H Module Fault and Status Reporting Chapter 6 The 1756-OF8H modules multicast status and fault data to the controller with their channel data. The fault data is arranged to let you choose the level of granularity you desire for examining fault conditions. Three levels of tags work together to provide increasing degree of detail as to the specific cause of faults on the module.
Chapter 6 1756-OF8H HART Analog Output Module 1756-OF8H Fault Reporting The graphic below offers an overview of the fault reporting process. When the module is calibrating, all bits in the Channel Fault word are set. Module Faults 6, 5, 4, and 0 are not used for fault reporting 7 Analog GroupFault 6 5 3 2 Updated Calibrating StatusReady 4 7 Ch7Fault 6 Ch6Fault 5 Ch5Fault 0 If set, any bit in the Channel Fault word, also sets the Analog Group Fault in the Module Fault word.
1756-OF8H HART Analog Output Module Chapter 6 Module Fault Word Bits Bits in this word provide the highest level of fault detection. A nonzero condition in this word reveals that a fault exists on the module. You can examine further down to isolate the fault. Table 17 lists tags that are found in the Module Fault word. Table 17 - Tags Found in the Module Fault Word Tag Description Tag Name Analog Group Fault This bit is set when any bits in the Channel Fault word are set.
Chapter 6 1756-OF8H HART Analog Output Module Channel Status Tags Any of the channel status words (eight words for 1756-OF8H modules), one for each channel, display a nonzero condition if that particular channel has faulted. Some of these bits set bits in other Fault words. When the High or Low Limit Alarm bits (ChxHLimitAlarm or ChxLLimit Alarm) in any of the words are set, the appropriate bit is set in the Channel Fault word.
Chapter 7 Configure the Modules with RSLogix 5000 Software Introduction The information in this chapter describes how to configure the ControlLogix HART analog I/O modules with RSLogix 5000 software. The table explains the topics discussed in this chapter.
Chapter 7 Configure the Modules with RSLogix 5000 Software The Select Module window appears. 2. Expand the Analog modules and select your module . 3. Click OK. The New Module dialog box appears.
Configure the Modules with RSLogix 5000 Software General Tab Chapter 7 Complete the se instructions for a general configuration. 1. On the General tab, do these steps: a. Type a name for the module. b. Type an optional description for the module. c. Select the slot number for the module. 2. On the Module Definition box, click Change. The Module Definition dialog box appears. 3.
Chapter 7 Configure the Modules with RSLogix 5000 Software HART Configuration The Input Data formats on the General tab let you access HART field device data through automatic collection of the HART Field Device Process Variables and Health information. You can also access HART field device data with pass-through messages. See Getting HART Data By Using CIP MSG on page 121 and HART Modules Used with Asset Management Software on page 141 for more information.
Configure the Modules with RSLogix 5000 Software Connection Tab Chapter 7 Use the following information to make selections on the Connection tab. Parameter Description Requested Packet Interval Defines when the module multicasts its data onto the local chassis backplane. Inhibit Module Prevents connection to the module. Use only if you do not want the module put into service.
Chapter 7 Configure the Modules with RSLogix 5000 Software Module Info Tab 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 tab displays the module’s current operational state. See the descriptions in the following table. Parameter Description Major Fault None, Unrecoverable, or Recoverable.
Configure the Modules with RSLogix 5000 Software Chapter 7 Coordinated System Time (CST) The CST box in the lower, left-hand column of the Module tab provides the following information. Parameter Description Timer Hardware Displays OK or faulted for the timer’s hardware. Timer Sync’ed Displays yes if the module’s timer is coordinated with the master. Display no if it is not. This indicates if a CST master is providing a time reference to the module.
Chapter 7 Configure the Modules with RSLogix 5000 Software Configuration Tab - Input Modules The following information describes how to configure the module’s input channels. Differences in the modules are noted. Changes made to the parameters in the Channel box only apply to the individual channel that is selected. Changes made to these parameters apply to all channels.
Configure the Modules with RSLogix 5000 Software Chapter 7 Configure the Individual Channels With an individual channel button selected, use this table to configure the parameters in the Channel box that apply to the individual channels. Parameter Action Notes Available in Hard Run Mode? Enable HART Check or uncheck for the 1756-IF8H and 1756-OF8H modules. • Input range must be 0…20 mA or 4…20 mA. • When a channel is not enabled: – HART messages are not sent on this channel.
Chapter 7 Configure the Modules with RSLogix 5000 Software 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.
Configure the Modules with RSLogix 5000 Software Chapter 7 Scaling Low Engineering Set the Low Engineering value for the module. The Low Engineering value must not equal the High Engineering value. This is the value in engineering units that corresponds with a signal value equal to the Low signal. Valid values are in the range of -10,000,000…100,000,000. The default value is 0.00.
Chapter 7 Configure the Modules with RSLogix 5000 Software This sets up a relationship between the electrical signal generated by your tank gauge and the number sent to the Logix Controller for use in your control system. Graphically, this relationship looks like this: Note that the module can measure signals slightly higher and lower than the sensor will provide for this tank. Setting the High or Low Engineering Units will not limit the values to within that range.
Configure the Modules with RSLogix 5000 Software Chapter 7 Configure All Channels Use this table to configure the parameters on the Configuration tab that apply to all the channels.. Parameter Action Notes Available in Hard Run mode? Real Time Sample (RTS) Choose a value from 0…10,000. • Determines the interval of time at which updated information is supplied to the controller. • The default is 88. • See Real Time Sample (RTS) on page 41 for more information.
Chapter 7 Configure the Modules with RSLogix 5000 Software 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 mA and 10.0003 mA, but it would not distinguish 10 mA from 10.0002 mA.
Configure the Modules with RSLogix 5000 Software Chapter 7 Table 23 - Module Filter Values Module Filter, Hz 10 (1) C.ModuleFilter 0 15 7 20 6 50 1 60 (default) 2 100 3 250 4 1000(2) 5 (1) 10 Hz not supported in the 1756-IF16H module. (2) Do not choose 1000 with HART enabled. Alarm Tab 1756-IF8H Module The following information describes how to configure the parameters on the Alarm tab for the 1756-IF8H module.
Chapter 7 Configure the Modules with RSLogix 5000 Software With an individual channel button selected, use these parameter descriptions to configure the alarms. Table 24 - Alarm Tab Parameters Parameter Action Notes Available in Hard Run Mode? Process Alarms Enter values or drag the corresponding flags on the slider bar to set the values. • The maximum and minimum values for these alarms are set by the High Engineering and Low Engineering parameters on the Configuration tab.
Configure the Modules with RSLogix 5000 Software Configuration Tab Output Module Chapter 7 The following information describes how to configure the module’s input channels. Changes made to the parameters in the Channel box only apply to the individual channel that is selected. Changes made to these parameters apply to all channels.
Chapter 7 Configure the Modules with RSLogix 5000 Software Table 25 - Configuration Tab Parameters Parameter Action Notes Available in Hard Run Mode? Output Range Chose a value from the drop-down menu. 0…20 mA or 4…20 mA is required for HART. No Sensor Offset Enter a value from -9,999,999…99,999,999 (float). • The default value is 0.00. • The offset value is in engineering units. • The Sensor Offset is added to the data value to determine signal level.
Configure the Modules with RSLogix 5000 Software Chapter 7 Table 27 - Pass -through Setting, Ratio, and Priority Output State Tab Output Module Setting Scan:Pass-through ratio Gives priority to Once per channel scan 1:1 Asset management Once per two channels scanned 1:2 Default setting Once per module scan 1:8 Input tag scan Use the following information to configure the parameters on the Output State tab.
Chapter 7 Configure the Modules with RSLogix 5000 Software Output State in Program Mode These parameters are not available in Hard Run mode. Selecting Configures the Output Channel for the Following When the Controller Transitions from Run to Program Mode Hold Last State Leave the current output at its last value. User Defined Value Go to the specific value when the owner controller is switched into Program mode. If you select this, enter a value from 9,999,999…99,999,999, default is 0.
Configure the Modules with RSLogix 5000 Software Chapter 7 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.
Chapter 7 Configure the Modules with RSLogix 5000 Software Table 28 - Alarm Tab Parameters (Continued) Parameter Action Notes Available in Hard Run Mode? Ramp in Run Mode Check • Enables ramping in Run mode. • Ramping occurs between the current output level and any new output value received. • If ramping is enabled, the output only can change at the configured ramp rate limit. No Ramp Rate Enter a value from 9,999,9999 to 999,999,999, default is 0.
Configure the Modules with RSLogix 5000 Software HART Device Info Tab Chapter 7 The HART Device Info tab displays information about the attached HART field device that is collected by the HART module. Enhanced diagnostic and status codes are available here depending on your configuration. • If you selected a Listen-Only communication format when you created the module, this tab is not available. • If HART is not enabled for this channel, Channel Not HART Enabled is displayed.
Chapter 7 Configure the Modules with RSLogix 5000 Software • If HART is enabled, but the HART Field Device is not responding, HART initializing is displayed. Table 29 - HART Device Info Tab 112 Parameter Description Channel Click a channel to display the parameters for the corresponding channel. Refresh Click to update all attributes displayed on this tab for the corresponding channel. Tag Displays the tag name of the HART Field Device.
Configure the Modules with RSLogix 5000 Software Chapter 7 Table 29 - HART Device Info Tab Data in the Input Tags Parameter Description PV 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.
Chapter 7 Configure the Modules with RSLogix 5000 Software – Current Fault - The analog current doesn't match the readback of the current received over the HART communication. This might be caused by an inaccurate field device, faulty wiring, or water in the conduit. Sometimes a rapid change in the signal results in a transient current fault as the analog and digital representations are sampled at slightly different times and at different places in the signal path.
Configure the Modules with RSLogix 5000 Software Chapter 7 An example for a Flow Meter might be: • PV - Primary Variable. Flow Rate in Liters per Minute. • SV - Secondary Variable. Process Temperature in °C. • TV - Third or Tertiary Variable. Product Density in Grams per Cubic Centimeter. • FV - Fourth or Quaternary Variable An example for a Valve Positioner might be: • PV - Primary Variable. Commanded position in %. • SV - Secondary Variable. Actual position in %. • TV - Third or Tertiary Variable.
Chapter 7 Configure the Modules with RSLogix 5000 Software The module collects the PV, SV, TV, and FV data as described in Table 30.
Configure the Modules with RSLogix 5000 Software Chapter 7 How the Module Automatically Collects Data The ControlLogix HART analog module automatically sends HART messages to characterize the HART field device and collect the dynamic variables. It also collects additional status information when the device indicates it is available. When the device indicates its configuration has changed, HART messages are sent to reread the configuration information so that a current copy is cached in the modules.
Chapter 7 Configure the Modules with RSLogix 5000 Software Figure 19 - 1756-IF8H and 1756-OF8H Flow Chart Device in Scan List? No Send Command 0 Read Unique Identifier Read Configuration Information, Such as Tag, Units, Range Yes Reply? Signal Configuration Changed in Input Tag Yes Send Command 3 or 9 to Read Dynamic Process Variable Put Device in Scan List No Reply? Yes Update Input Tag No Remove Device from Scan List New Configuration Indicated? Yes Read Configuration Information, Such
Configure the Modules with RSLogix 5000 Software Chapter 7 Figure 20 - 1756-IF16H Flow Chart No Device in Scan List? Send Command 0 Read Unique Identifier Yes Read Configuration Information, Such as Tag, Units, Range Yes Reply? No Signal Configuration Changed in Input Tag Send Command 3 or 9 to Read Dynamic Process Variable Reply? Put Device in Scan List Update Input Tag Yes No Remove Device from Scan List New Configuration Indicated? Yes Read Configuration Information, Such As Tag, Units,
Chapter 7 Configure the Modules with RSLogix 5000 Software Notes: 120 Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Chapter 8 Getting HART Data By Using CIP MSG Introduction This chapter shows you how to use HART data in your Logix controller via MSG instructions. You might do this because you need the following: • Only occasional access to the data, and don't want to use the extra network capacity and memory for the larger Analog with HART PV or Analog and HART by Channel input tags. • Additional information, such as device tag, ranges, or manufacturer-specific information.
Chapter 8 Getting HART Data By Using CIP MSG Using MSG Instructions to Access the HART Object Both categories of MSG are handled by the HART Object contained in the module. There is one HART Object for each channel. Some CIP messages can be sent to the Class Instance or Instance 0 of the HART object. Most MSGs are sent to a specific instance of the HART object associated with a particular channel. This table shows channel and instance correspondence.
Getting HART Data By Using CIP MSG CIP Services to Access Common HART Data Chapter 8 You can get the following kinds of HART data easily from the HART object: • HART field device information - Similar to that displayed on the Module Properties HART Device Info tab of RSLogix 5000 software. • Additional status - HART devices that support extended diagnostics can indicate in their Field Device Status that some additional diagnostic information is available.
Chapter 8 Getting HART Data By Using CIP MSG See Appendix E on page 213 for an explanation of the engineering unit code numbers. Table 33 - Reply Packet - Request Succeeded Offset Field Data Type Definition 0 Status USINT Command status 1 HARTCommandStatus HART Device reply Status Byte # 1 (response code) 2 HARTFieldDeviceStatus HART Device reply Status Byte # 2 3 HARTExtDevice Status Status Byte returned from Cmd 9 or 0 for 5.
Getting HART Data By Using CIP MSG Chapter 8 Read Additional Status (Service Code = 16#4C) These tables show the request and reply packet structures for the Read Additional Status service. Reply Size = 2…224 bytes.
Chapter 8 Getting HART Data By Using CIP MSG Get Device Information (Service Code = 16#4D) These tables show the request and reply packet structures for the Get Device Information service.
Getting HART Data By Using CIP MSG Chapter 8 Table 39 - Reply Packet - Request Succeeded Offset Field Data Type Definition(1) 56…91 Message HARTMsg CMD#12, Bytes 0…23 See HARTMsg on page 130 for more information.
Chapter 8 Getting HART Data By Using CIP MSG Getting HART Device Information By Using CIP Generic MSG For an example, this rung of ladder logic retrieves fresh HART device information whenever the 1756-IF8H or 1756-OF8H module indicates new configuration is available. Note that if the Device Information is critical to your application, be sure to check for .ER errors and implement a recovery strategy. This is the Message Configuration dialog box.
Getting HART Data By Using CIP MSG Chapter 8 The Destination tag is as shown in the Controller Tags dialog box.
Chapter 8 Getting HART Data By Using CIP MSG The following figure shows string types for HARTTag, HARTDescriptor, and HARTMsg.
Getting HART Data By Using CIP MSG CIP Services to Passthrough a HART Message to the HART Field Device Chapter 8 The HART object supports these CIP messages for HART pass-through messaging: Pass-through Init, Pass-through Query, Flush Queue (rarely needed). With these three CIP messages, your Logix controller can format the individual bytes of a HART command, send it to a HART field device, and retrieve the response in HART format.
Chapter 8 Getting HART Data By Using CIP MSG If your input tag includes the HART PV data, a status indicator HART.ChxDeviceStatus.MsgReady tells your program a HART reply is ready to retrieve with the Pass-through Query command. The CIP reply from the Init service includes a number called the handle. This handle identifies the HART message that was placed in a queue for transmission to the field device.
Getting HART Data By Using CIP MSG HART Module Scanning Diagram with Pass-through Messages Chapter 8 When HART pass-through messages are being sent, the normal data acquisition sequence is modified as shown in the diagram. In this case, the Pass-through is configured to send one pass-through message for each channel scanned. It can be configured for lower priority on the Configuration tab of the Module Properties dialog box.
Chapter 8 Getting HART Data By Using CIP MSG HART Pass-through CIP Message Layout Details See the following tables for pass-through information. Pass-through Init (Service Code= 16#4E) These tables show the request and reply packet structures for the Pass-through Init service.
Getting HART Data By Using CIP MSG Chapter 8 Table 43 - Reply Packet Offset Offset Data Type Definition 0 Status USINT Query Status 00 = Success 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) 3 HART FieldDeviceStatus USINT HART Reply Status Byte #2(1) If status (bit 0) is 35, refer to Table 44 for the error code description.
Chapter 8 Getting HART Data By Using CIP MSG Flush Queue (Service Code= 16#50) These tables show the request and reply packet structures for the Flush Queue service. Table 45 - Request Packet Offset Field Data Type Definition No request data Request size = 0 bytes Table 46 - Reply Packet Offset Field Data Type Definition Note that Flush Queue can be sent to have the 1756-IF8H or 1756-OF8H module discard any pending HART replies awaiting a query command.
Getting HART Data By Using CIP MSG Chapter 8 Note that SWPB reverses the order of bytes in the PV, SV, TV, FV floating-point numbers to be in the Logix REAL format. The following dialog boxes are the Init Message Configuration and Communication tabs when Command 9 is sent to HART device on channel 0. Note instance 1 means Channel 0.
Chapter 8 Getting HART Data By Using CIP MSG This is the Message Path Browser dialog box. See the query-message configuration dialog box.
Getting HART Data By Using CIP MSG Chapter 8 See the dialog box that shows tags. The data types are explained next.
Chapter 8 Getting HART Data By Using CIP MSG These are the HART command 9 example dialog boxes.
Chapter 9 HART Modules Used with Asset Management Software Introduction This chapter describes important points about using the ControlLogix HART analog modules with asset management systems. These topics are discussed in this chapter.
Chapter 9 HART Modules Used with Asset Management Software 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 1756 backplane.
HART Modules Used with Asset Management Software Chapter 9 What communication DTMs are used with the ControlLogix HART analog I/O modules? Go to http://www.ab.com/io/downloads and click the HART DTM Files link to obtain the DTMs. Can I get asset management software from Rockwell Automation? Yes. Rockwell offers a software bundle (catalog number 9504SPECHARTENE), which contains E+H FieldCare asset management software, RSLinx Classic Professional software, and a one-year TechConnect support contract.
Chapter 9 HART Modules Used with Asset Management Software Notes: 144 Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Chapter 10 Unlatch Alarms and Reconfigure Modules By Using Ladder Logic Introduction The information in this chapter applies only to the 1756-IF8H and 1756-OF8H modules. Alarms are not available in the 1756-IF16H module. These topics are discussed in this chapter.
Chapter 10 Unlatch Alarms and Reconfigure Modules By Using Ladder Logic Processing Real-time Control and Module Services Services sent via message instructions are not as time critical as the module behavior defined during configuration and maintained by a real-time connection. Therefore, the module processes messaging services only after the needs of the I/O connection are met.
Unlatch Alarms and Reconfigure Modules By Using Ladder Logic 2. Add a message instruction to a rung by clicking the MSG button the toolbar above the ladder project. Chapter 10 on 3. Create a tag for the message instruction that you are adding. a. Right-click the question mark (?). b. Choose New Tag. The New Tag dialog box appears. 4. On the New Tag dialog box, complete these procedures: a. Name the tag. b. Click Base for tag type. c. Click Message data type. d.
Chapter 10 Unlatch Alarms and Reconfigure Modules By Using Ladder Logic Enter Message Configuration After creating a new tag, you must enter message configuration. The small box with the ellipsis provides access to the Message Configuration dialog box. There are two dialog boxes on which you enter message configuration: – Configuration – Communication A description of the purpose and setup of each dialog box is explained on the following pages.
Unlatch Alarms and Reconfigure Modules By Using Ladder Logic Chapter 10 The Configuration tab provides information on what module service to perform and where to perform it. For example, you must use this dialog to unlatch high high alarms (module service) on channel 0 of a module (where to perform service). You select a service type by clicking the drop-down. A list of available services includes to unlatch high high, high, low low, low, low, ramp, and rate alarms.
Chapter 10 Unlatch Alarms and Reconfigure Modules By Using Ladder Logic Unlatch Alarms in the 1756-IF8H Module The example ladder logic rungs 0…4 show how to unlatch the following alarms: • Channel 0 High high alarm - Rung 0 • Channel 0 High alarm - Rung 1 • Channel 0 Low alarm - Rung 2 • Channel 0 Low low alarm - Rung 3 • Channel 0 Rate alarm - Rung 4 Rung 0 unlatches the high high alarm. Click the box in each rung to see the configuration and communication information dialog associated with it.
Unlatch Alarms and Reconfigure Modules By Using Ladder Logic Chapter 10 Choose a service type and configure the instance. Instance 1 is for channel 0. The example shows the communication path for Rung 0 IMPORTANT You must name an I/O module to set the message path under that module’s communication dialog.
Chapter 10 Unlatch Alarms and Reconfigure Modules By Using Ladder Logic Unlatch Alarms in the 1756-OF8H Module The example ladder logic rungs 5…7 show how to unlatch the following alarms. • High limit alarm - Rung 5 • Low limit alarm - Rung 6 • Ramp alarm - Rung 7 Click the box in each rung to see the configuration and communication information dialog associated with it. Rung 5 unlatches the high limit alarm. Rung 6 unlatches the low limit alarm. Rung 7 unlatches the ramp alarm.
Unlatch Alarms and Reconfigure Modules By Using Ladder Logic The example shows the communication path for Rung 5 IMPORTANT Chapter 10 . You must name an I/O module to set the message path under that module’s communication dialog.
Chapter 10 Unlatch Alarms and Reconfigure Modules By Using Ladder Logic Reconfigure a Module It is sometimes advantageous to change the functional operation of a module in the ControlLogix system automatically via the user program rather than using RSLogix 5000 software to reconfigure a module. This way, changes in the process can dictate when the reconfiguration should take place rather than the user performing that function manually.
Chapter 11 Module Troubleshooting Introduction This chapter describes how to interpret status indicators and troubleshoot the modules. These topics are discussed in this chapter. Topic Use Module Indicators Page Use Module Indicators 155 General Troubleshooting Tips 156 Use RSLogix 5000 Software to Troubleshoot a Module 159 Module Configuration Errors 160 The analog I/O modules have indicators that provide indication of module status.
Chapter 11 Module Troubleshooting Table 50 - Status Indicator Blink Codes and Fault Status If OK Is Red Red Red Red Red And CAL Is Flashing Green 3 Blinks 4 Blinks 5 Blinks 6 Blinks Fault Status Firmware Download in Process Major Nonrecoverable Major Nonrecoverable Major Nonrecoverable Major Recoverable Red Red 9 Blinks 10 Blinks Major Nonrecoverable Major Recoverable Recommended Action Wait for download to complete. Boot code section has failed the CRC check. Send in module for repair.
Module Troubleshooting Chapter 11 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.
Chapter 11 Module Troubleshooting • Local:7:I.HART.Ch0PVStatus – 16#C0 is good. 0 is bad. This could be a communication problem or something wrong with device. For example, with SVStatus, this could mean the device does not support more than one measurement. When working with the HART Device Info dialog for troubleshooting, use these tips: • HART Initializing means that HART is enabled, but not communicating.
Module Troubleshooting Use RSLogix 5000 Software to Troubleshoot a Module Chapter 11 In addition to the status displayed on the module, RSLogix 5000 software alerts you to fault conditions. You are alerted in one of these ways.
Chapter 11 Module Troubleshooting Module Configuration Errors The additional fault code value describes the configuration error if “(Code 16#0009) Module Configuration Rejected: Parameter Error” is displayed on the Connection Tab in RSLogix 5000 software. Additional Fault Codes - Module Level Table 51 shows error codes used by ControlLogix HART Analog modules for module level conditions (conditions that do not occur in a specific channel).
Module Troubleshooting Chapter 11 Additional Fault Codes - Channel Level Each module has channel level error codes that are specific to the individual modules. These channel level error codes, which display in the Module Fault box on the Connection tab dialog box, are described in the following tables.
Chapter 11 Module Troubleshooting Table 53 - 1756-IF16H Channel Level Error Codes Channel x Extended Status = Channel 0 Error Value + (x *16) Extended Fault Codes Channel Channel Status 0 1 2 3 4 5 6 7 16#0007 16#0017 16#0027 16#0037 16#0047 16#0057 16#0067 16#0077 Invalid Input Range 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 outsi
Appendix A Tag Definitions Communication Mode Member Names and Definitions The set of tags associated with any module depends on the module type and the communication format. The tables below show input data choice, tag, and main module type. IMPORTANT The Analog and HART PV input data type for the 1756-IF8H and 1756-OF8H modules has a :1 as the suffix instead of :0 in firmware revision 2.1.
Appendix A Tag Definitions Table 57 - 1756-OF8H Input Data Choice and Tags Input Data Choice Tag Main Module Defined Type Subtype Used by Main Type Analog and HART PV Configuration AB:1756_OF8H:C:0 AB:1756_OF8H_ChConfig_Struct:C:0 Input AB:1756_OF8H_HARTPV:I:1 AB:1756_OF8H_HARTData:I:1 AB:1756_OF8H_HARTStatus_Struct:I:1 Output AB:1756_OF8H:O:0 None Configuration AB:1756_OF8H:C:0 AB:1756_OF8H_ChConfig_Struct:C:0 Input AB:1756_OF8H_AnalogHARTbyChannel:I:0 AB:1756_OF8H_HARTDataAll_Struct:I
Tag Definitions Appendix A Table 58 - Configuration (AB:1756_IF8H:C:0) Member Name Type Style Description HighSignal REAL Float Upper current value for scaling to engineering units. Default is 20 mA. Must be more than LowSignal and less than or equal to the maximum Input Range. See Scaling to Engineering Units on page 98 for more information. LowEngineering REAL Float Measured quantity in engineering units that results in a signal level equal to LowSignal.
Appendix A Tag Definitions Table 59 - Analog Only (AB:1756_IF8H_Analog:I:0) Member Name Type Style Description HARTFaults (Ch0…Ch7) SINT Binary Indicates a problem with HART data from the Field Device on Channel x. Examples are HART not enabled, HART device not connected, HART communication failure due to noise. The following Field Device Status conditions also cause this to be set: Device Malfunction, PV Out of Limits, Loop Current Saturated, and Loop Current Fixed. BOOL Decimal HARTFaults.
Tag Definitions Appendix A Table 59 - Analog Only (AB:1756_IF8H_Analog:I:0) Member Name Type Style Description ChxData (Ch0…Ch7) REAL Float Value of analog signal on Channel x after conversion to engineering units. CSTTimestamp DINT[2] Hex Timestamp taken at the time the input data was sampled in terms of coordinated system time, which is a 64-bit value in microseconds coordinated across the modules in the 1756 backplane.
Appendix A Tag Definitions Table 60 - Analog and HART PV (AB:1756_IF8H_HARTPV:I:1) Member Name Type Style Description Ch0HAlarm BOOL Ch0Status.2 Ch0Data > Ch0HAlarmLimit If Ch0Config.ProcessAlarmLatch is set, this alarm remains set until it is unlatched Ch0LAlarm BOOL Ch0Status.3 Ch0Data < Ch0LAlarmLimit If Ch0Config.ProcessAlarmLatch is set, this alarm remains set until it is unlatched. Ch0RateAlarm BOOL Ch0Status.4 Ch0Data changing faster than Ch0RateAlarmLimit.
Tag Definitions Appendix A Table 60 - Analog and HART PV (AB:1756_IF8H_HARTPV:I:1) Member Name CurrentFault Type Style BOOL Description Analog current measurement does not match the current the field device reported over the HART network. ConfigurationChanged BOOL The field device configuration has changed and new field device configuration information can be obtained from the 1756-IF8H module via CIP MSG GetDeviceInfo, which will clear this bit.
Appendix A Tag Definitions Analog and HART by Channel Table 61 - Analog and HART by Channel (AB:1756-IF8H_AnalogHARTbyChannel:I:0) Member Name Type Style Description ChannelFaults (Ch0…Ch7) INT Binary Indicates a problem with analog data on Channel x or broken communication between the Logix controller and the 1756-IF8H module. Example: Set if analog signal is larger than 20 mA. ChxFault BOOL ModuleFaults SINT Binary CalFault BOOL Decimal ModuleFaults.
Tag Definitions Appendix A Table 61 - Analog and HART by Channel (AB:1756-IF8H_AnalogHARTbyChannel:I:0) Member Name Type Style Description Changed BOOL Decimal An operation was performed that changed the device’s configuration. Malfunction BOOL Decimal The device detected a serious error or failure that compromises device operation. AlarmStatus SINT Binary Indicates various alarms on the analog signal. Also sets Ch0Fault for Overrange, Underrange, and CalFault.
Appendix A Tag Definitions Table 61 - Analog and HART by Channel (AB:1756-IF8H_AnalogHARTbyChannel:I:0) Member Name Type Ch05 AB:1756_IF8H_HARTDataAll_Struct:I:0, Channel 05 analog and HART data. Ch06 AB:1756_IF8H_HARTDataAll_Struct:I:0, Channel 06 analog and HART data. Ch07 AB:1756_IF8H_HARTDataAll_Struct:I:0, Channel 07 analog and HART data.
Tag Definitions Module-defined Data Types, 1756-IF16H Module Appendix A These tables describe module-defined data types for the 1756-IF16H module and include information for configuration and input tags. Configuration This table describes the configuration tags available in the 1756-IF16H module. Table 62 - Configuration (AB:1756_IF16H:C:0) Member Name Type Style Description ModuleFilter (bits 0…7) SINT Decimal See the Module Filter Values table on page 103.
Appendix A Tag Definitions Table 62 - Configuration (AB:1756_IF16H:C:0) Member Name Type Style Ch14Config AB:1756_IF16H_ChConfig_Struct:C:0 Ch15Config AB:1756_IF16H_ChConfig_Struct:C:0 PassthroughHandle Timeout INT Decimal Description Seconds to keep a reply to a HART pass-through service request before discarding; 15 seconds is recommended. Analog Only This table describes the input tags available in the Analog Only data format.
Tag Definitions Appendix A Table 63 - Analog Only (AB:1756_IF16H_Analog:I:0) Member Name Type Style Description Ch02Status SINT Binary Indicates various alarms on the analog signal. Also sets Ch02Fault. Ch03Status SINT Binary Indicates various alarms on the analog signal. Also sets Ch03Fault. Ch04Status SINT Binary Indicates various alarms on the analog signal. Also sets Ch04Fault. Ch05Status SINT Binary Indicates various alarms on the analog signal. Also sets Ch05Fault.
Appendix A Tag Definitions Table 64 - Analog and HART PV (AB:1756_IF16H_HARTPV:I:0) Member Name Type Style Description BrokenWireFaults (bit0…15) INT Binary Indicates that current is not flowing through the module as expected. This might be caused by broken wiring, RTB removal, or a powered-off field device. BOOL Decimal BrokenWireFaults.0…BrokenWireFaults.15 INT Binary Indicates a problem with HART data from the Field Device on Channel x.
Tag Definitions Appendix A Table 64 - Analog and HART PV (AB:1756_IF16H_HARTPV:I:0) Member Name Type Style Description Ch09Data REAL Float Value of analog signal on Channel 09 after conversion to engineering units. Ch10Data REAL Float Value of analog signal on Channel 10 after conversion to engineering units. Ch11Data REAL Float Value of analog signal on Channel 11 after conversion to engineering units.
Appendix A Tag Definitions Table 64 - Analog and HART PV (AB:1756_IF16H_HARTPV:I:0) Member Name Type Style Description Ch13DeviceStatus AB:1756_IF16H_HARTStatus_Struct:I:0, Channel 13 HART Device status info. Ch14DeviceStatus AB:1756_IF16H_HARTStatus_Struct:I:0, Channel 14 HART Device status info. Ch15DeviceStatus AB:1756_IF16H_HARTStatus_Struct:I:0, Channel 15 HART Device status info.
Tag Definitions Appendix A Table 65 - Analog and HART by Channel (AB:1756-IF16H_AnalogHARTbyChannel:I:0) Member Name Type ConfigurationChanged BOOL Style Description Decimal The field device configuration has changed and new field device configuration information can be obtained from the 1756-IF16H module via CIP MSG GetDeviceInfo, which will clear this bit. MaintenanceRequired BOOL Bit 0 of Extended Device Status (if using CMD 9, or from CMD 48 if supported).
Appendix A Tag Definitions Table 65 - Analog and HART by Channel (AB:1756-IF16H_AnalogHARTbyChannel:I:0) Member Name Type Ch10 AB:1756_IF16H_HARTDataAll_Struct:I:0, Channel 10 analog and HART data. Ch11 AB:1756_IF16H_HARTDataAll_Struct:I:0, Channel 11 analog and HART data. Ch12 AB:1756_IF16H_HARTDataAll_Struct:I:0, Channel 12 analog and HART data. Ch13 AB:1756_IF16H_HARTDataAll_Struct:I:0, Channel 13 analog and HART data.
Tag Definitions Module-defined Data Types, 1756-OF8H Module Appendix A These tables describe module-defined data types for the 1756-OF8H module and include information for configuration, input, and output tags. Configuration This table describes the configuration tags available in the 1756-OF8H module. Table 66 - Configuration (AB:1756_OF8H:C:0) Member Name Type Style Description ProgToFaultEN BOOL Decimal Ch0Config AB:1756_OF8H_ChConfig_Struct:C:0 RampToFault BOOL Decimal ConfigBits:9.
Appendix A Tag Definitions Table 66 - Configuration (AB:1756_OF8H:C:0) Member Name Type Style Description Ch5Config AB:1756_OF8H_ChConfig_Struct:C:0 Ch6Config AB:1756_OF8H_ChConfig_Struct:C:0 Ch7Config AB:1756_OF8H_ChConfig_Struct:C:0 PassthroughHandleTime out INT Decimal Seconds to keep a reply to a HART pass-through service request before discarding. 15 seconds recommended.
Tag Definitions Appendix A Table 67 - Analog Only (AB:1756_OF8H_Analog:I:0) Member Name Type Style Description Ch0NotANumber BOOL Decimal Ch0Status:5 Ch0Data is not a valid floating point number. Ch0OpenWire BOOL Decimal Ch0Status:7 Only valid in current mode (example 4…20 mA). 1 indicates no current is flowing, probably due to open circuit. Ch1Status SINT Binary Indicates various alarms on the analog signal. Also sets Ch1Fault.
Appendix A Tag Definitions Analog and HART PV This table describes the input tags available in the Analog and HART PV data format. Table 68 - Analog Only (AB:1756_OF8H_HARTPV:I:1) Member Name Type Style Channel Faults (bits 9...15 unused) INT Binary ChxFault BOOL Decimal ChannelFaults.x, Indicates communication fault or fault condition from ChXStatus. LoopOutputFault BOOL Decimal ChannelFaults.
Tag Definitions Appendix A Table 68 - Analog Only (AB:1756_OF8H_HARTPV:I:1) Member Name Type Style Description Ch5Status SINT Binary Indicates various alarms on the analog signal. Also sets Ch5Fault. Ch6Status SINT Binary Indicates various alarms on the analog signal. Also sets Ch6Fault. Ch7Status SINT Binary Indicates various alarms on the analog signal. Also sets Ch7Fault. ChxData REAL Float Analog value actually output in engineering units.
Appendix A Tag Definitions Table 68 - Analog Only (AB:1756_OF8H_HARTPV:I:1) Member Name Type Style Description Ch3DeviceStatus AB:1756_OF8H_HARTStatus_Struct:I:0, Channel 3 HART Device status information. Ch4DeviceStatus AB:1756_OF8H_HARTStatus_Struct:I:0, Channel 4 HART Device status information. Ch5DeviceStatus AB:1756_OF8H_HARTStatus_Struct:I:0, Channel 5 HART Device status information. Ch6DeviceStatus AB:1756_OF8H_HARTStatus_Struct:I:0, Channel 6 HART Device status information.
Tag Definitions Appendix A Table 69 - Analog and HART by Channel (AB:1756-OF8H_AnalogHARTbyChannel:I:0) Member Name Type Style Description BOOL Decimal Analog current measurement does not match the current the field device reported over the HART network. ConfigurationChanged BOOL Decimal The field device configuration has changed and new field device configuration information can be obtained from the 1756-OF8H module via CIP MSG GetDeviceInfo, which will clear this bit.
Appendix A Tag Definitions Table 69 - Analog and HART by Channel (AB:1756-OF8H_AnalogHARTbyChannel:I:0) Member Name Type Style Description PowerLow BOOL Decimal Low power. PV REAL Float Primary value. This is the same value as signaled on the analog channel and is the most important measurement made by this device. SV REAL Float Secondary value. TV REAL Float Third value. FV REAL Float Fourth value. PVStatus SINT Hex Primary status. 16#C0 = Connected. 16#00 = Not Connected.
Tag Definitions Appendix A Output This table describes the output tags available in the 1756-OF8H module. Table 70 - Output (AB:1756_OF8H:O:0) Member Name Type Style Description Ch0Data REAL Float Value in engineering units to output on the analog signal of Channel 0. Ch1Data REAL Float Value in engineering units to output on the analog signal of Channel 1. Ch2Data REAL Float Value in engineering units to output on the analog signal of Channel 2.
Appendix A Tag Definitions Notes: 190 Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Appendix B Use 1492 Wiring Systems with Your Analog I/O Module 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.
Appendix B Use 1492 Wiring Systems with Your Analog I/O Module The table lists 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. Table 71 - Analog Interface Module and Pre-wired Cables I/O Cat. No. Mode AIFM Cat. No. AIFM Cat. No.
Appendix C Additional HART Protocol Information Introduction 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.
Appendix C Additional HART Protocol Information Message Structure Read this section for a description of transaction procedure, character coding, and message structure of the HART protocol. These correspond to layer 2 (datalink layer) of the OSI protocol reference model. Master-slave Operation HART is a master-slave protocol. This means that each message transaction is originated by the master; the slave (field) device replies when it receives a command message addressed to it.
Additional HART Protocol Information Response Code and Field Device Status Appendix C Two bytes of status also called the response code and field device status are included in every reply message from a field or slave device. These two bytes convey communication errors, command response problems, and field device status. If an error is detected in the outgoing communication, the most significant bit (bit 7) of the first byte is set to 1 and the details of the error are reported in the rest of that byte.
Appendix C Additional HART Protocol Information Table 73 - Response Codes and Field Device Status (Continued) Response Code Description If Bit 7 is And Bits 6…0 are 0 8 Update Failed - Update In Progress - Set to Nearest Possible Value 0 9 Applied Process Too High - Lower Range Value Too High - Not In Fixed Current Mode 0 10 Applied Process Too Low - Lower Range Value Too Low - MultiDrop Not Supported 0 11 In MultiDrop Mode - Invalid Transmitter Variable Code - Upper Range Value Too High 0
Additional HART Protocol Information Appendix C Table 75 - HART Universal Commands Command No.
Appendix C Additional HART Protocol Information Table 75 - HART Universal Commands Command Data in Command Data in Reply (1) No.
Additional HART Protocol Information Appendix C Table 76 - Common Practice Commands Command No.
Appendix C Additional HART Protocol Information Table 76 - Common Practice Commands Command No.
Additional HART Protocol Information Appendix C Table 76 - Common Practice Commands Command Data in Command No.
Appendix C Additional HART Protocol Information Table 76 - Common Practice Commands Command Data in Command Data in Reply No.
Additional HART Protocol Information Appendix C 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.
Appendix C Additional HART Protocol Information Table 77 - HART PV, SV, TV, and FV Status Values 23 17 00010111 00 Bad 01 Low Limited 0 No 111 7 24 18 00011000 00 Bad 01 Low Limited 1 Yes 000 0 25 19 00011001 00 Bad 01 Low Limited 1 Yes 001 1 26 1A 00011010 00 Bad 01 Low Limited 1 Yes 010 2 27 1B 00011011 00 Bad 01 Low Limited 1 Yes 011 3 28 1C 00011100 00 Bad 01 Low Limited 1 Yes 100 4 29 1D 00011101 00 Bad 01 Low Limited 1 Yes 10
Appendix D Manufacturer Identification Codes Introduction This appendix identifies the manufacturer with their assigned code.
Appendix D 206 Manufacturer Identification Codes Decimal Hex Company Name 33 21 PRIME Measurement Products 34 22 Ohkura Electric 35 23 Paine 36 24 Rochester Instrument Systems 37 25 Ronan 38 26 Rosemount 39 27 Peek Measurement 40 28 Actaris Neptune 41 29 Sensall 42 2A Siemens 43 2B Weed 44 2C Toshiba 45 2D Transmation 46 2E Rosemount Analytic 47 2F Metso Automation 48 30 Flowserve 49 31 Varec 50 32 Viatran 51 33 Delta/Weed 52 34 Westinghouse
Manufacturer Identification Codes Decimal Hex Company Name 72 48 SOR 73 49 Elcon Instruments 74 4A EMCO 75 4B Termiflex Corporation 76 4C VAF Instruments 77 4D Westlock Controls 78 4E Drexelbrook 79 4F Saab Tank Control 80 50 K-TEK 81 51 SENSIDYNE, INC 82 52 Draeger 83 53 Raytek 84 54 Siemens Milltronics PI 85 55 BTG 86 56 Magnetrol 87 58 Metso Automation 88 59 Siemens Milltronics PI 89 59 HELIOS 90 5A Anderson Instrument Company 91 5B INOR 92
Appendix D 208 Manufacturer Identification Codes Decimal Hex Company Name 111 6F Valcom s.r.l. 112 70 US ELECTRIC MOTORS 113 71 Apparatebau Hundsbach 114 72 Dynisco 115 73 Spriano 116 74 Direct Measurement 117 75 Klay Instruments 118 76 CiDRA CORP. 119 77 MMG AM DTR 120 78 Buerkert Fluid Control Systems 121 79 AALIANT Process Mgt 122 7A PONDUS INSTRUMENTS 123 7B ZAP S.A.
Manufacturer Identification Codes Decimal Hex Company Name 150 96 Brandt Instruments 151 97 Nivelco 152 98 Camille Bauer 153 99 Metran 154 9A Milton Roy Co. 155 9B PMV 156 9C Turck 157 9D Panametrics 158 9E R. Stahl 159 9F Analytical Technologies Inc.
Appendix D 210 Manufacturer Identification Codes Decimal Hex Company Name 189 BD Badger Meter 190 BE HIMA 191 BF GP:50 192 C0 Kongsberg Maritime 193 C1 ASA S.p.A. 194 C2 Hengesbach 195 C3 Lanlian Instruments 196 C4 Spectrum Controls 197 C5 Kajaani Process Measurements 198 C6 FAFNIR 199 C7 SICK-MAIHAK 200 C8 JSP Nova Paka 201 C9 MESACON 202 CA Spirax Sarco Italy 203 CB L&J TECHNOLOGIES 204 CC Tecfluid S.A.
Manufacturer Identification Codes Decimal Hex Company Name 24578 6002 TASI FLOW 24579 6003 Daihan Control 24580 6004 APM 24581 6005 ORANGE INSTRUMENTS.
Appendix D 212 Manufacturer Identification Codes Decimal Hex Company Name 24617 6029 Pulsar 24618 602A Elemer 24619 602B Soft Tech Group Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Appendix E Engineering Unit Code Numbers 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.
Appendix E Engineering Unit Code Numbers 214 Unit Codes Description from HART Specification Abbreviated Units 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 40 gallons usg 41 liters L 42 imperial gallons impgal 43 cubic meters cubic m 44 feet ft 45 meters m 46 barrels bbl 47 inches in 48 centimeters cm 49 millimeters
Engineering Unit Code Numbers Appendix E Unit Codes Description from HART Specification Abbreviated Units 70 grams per second g/s 71 grams per minute g/min 72 grams per hour g/h 73 kilograms per second kg/s 74 kilograms per minute kg/min 75 kilograms per hour kg/h 76 kilograms per day kg/d 77 metric tons per minute t/min 78 metric tons per hour t/h 79 metric tons per day t/d 80 pounds per second lb/s 81 pounds per minute lb/min 82 pounds per hour lb/h 83 pounds p
Appendix E Engineering Unit Code Numbers 216 Unit Codes Description from HART Specification Abbreviated Units 109 proof per mass proof/mass 110 bushels bushel 111 cubic yards cubic yd 112 cubic feet cubic ft 113 cubic inches cubic in 114 inches per second in/s 115 inches per minute in/min 116 feet per minute ft/min 117 degrees per second °/s 118 revolutions per second rev/s 119 revolutions per minute rpm 120 meters per hour m/hr 121 normal cubic meter per hour norm
Engineering Unit Code Numbers Appendix E Unit Codes Description from HART Specification Abbreviated Units 148 percent consistency % consistency 149 volume percent volume % 150 percent steam quality % steam quality 151 feet in sixteenths ft in sixteenths 152 cubic feet per pound cubic ft/lb 153 picofarads pF 154 mililiters per liter mL/L 155 microliters per liter microliters/L 156 percent plato % plato 157 percent lower explosion level % lower explosion level 158 mega calo
Appendix E Engineering Unit Code Numbers Notes: 218 Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Glossary The following terms and abbreviations are used throughout this manual. For definitions of terms not listed here, refer to the Allen-Bradley Industrial Automation Glossary, publication AG-7.1. 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 221). broadcast Data transmissions to all addresses.
Glossary exact match An Electronic Keying Protection mode that requires the physical module and the module configured in the software to match identically, according to vendor, catalog number, major revision, and minor revision. field side Interface between user field wiring and I/O module. In this glossary, see related entry for system side. flash update The process of updating the firmware of the module.
Glossary 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 113 for more information. Program mode In this mode, the controller program is not executing. Inputs are actively producing data.
Glossary Notes: 222 Rockwell Automation Publication 1756-UM533C-EN-P - February 2011
Index Numerics 1756-IF16H module analog and HART by channel tags 178 analog and HART PV tags 175 analog only tags 174 configuration tags 173 fault reporting 75 features 67 input module 67 1756-IF8H module analog and HART by channel tags 170 analog and HART PV tags 167 analog only tags 165 configuration tags 164 features 53 input channel ranges 54 input module 53 1756-OF8H module analog and HART by channel tags 186 analog and HART PV tags 184 analog only tags 182 configuration tags 181 fault reporting 85 fea
Index electrostatic discharge prevent 26 enclosure environment 26 engineering unit code numbers 213 scaling 98 environment enclosure 26 EtherNet/IP network 45, 48 event tasks 43 F fault codes 160 communication 109 reporting 1756-IF8H module 63 features 1756-IF16H module 67 1756-IF8H module 53 1756-OF8H module 79 filter digital 57, 71 input module 69 module 55 fourth value definition 16 G general tab 91 glossary of terms 219 grounding module 32 H HART additional protocol information 193 communication 14
Index operation 39 refresh 95 removal 37 resolution 102 scaling 24 status 94 tab 94 troubleshooting 155 wiring 34 N network update iime (NUT) for ControlNet network 220 O open wire detection 82 operation input module 40 module 39 output 46 output data echo 46 error codes 162 module channel status 88 circuit diagrams 84 clamp limit 82 data formats 80 local chassis 46 ramp rate 107 ramp/rate 81 remote chassis 47 resolution 80 wiring 83 operation 46 state module tab 107 overrange detection 56, 70 ownership
Index output state 107 tag definitions 163 tasks event 43 third value definition 16 timestamp 23 triggering event tasks 43 troubleshooting modules 155 status indicators 14 U underrange detection 56, 70 unicast communication’ communication unicast 51 226 connection 93 unlatch alarms 150 V variables HART 114 W wire-off detection 72 wiring analog interface modules (AIFM) 191 input diagrams 60, 72 module 34 output module 83 power supply 61, 73 pre-wired cables 191 RTB 32 Rockwell Automation Publication 1
Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products. At http://www.rockwellautomation.com/support/, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.
