There are enhancements to seven specifications and the addition of three new Device Family Specifications:
- HART Protocol Communication Specification (TS20013 r7.10)
- Network Management (TS20085 r4.1)
- Command Summary (TS20099 r11.1)
- Common Practice Command (TS20151 r14.0)
- Device Families (TS20151 r3.0)
- Temperature Device Family (TS20160-04 r3.0) (New)
- Pressure Device Family (TS20160-05 r1.0)
- PID Control Device Family (TS20160-07 r2.0) (New)
- Totalizer Device Family (TS20160-10 r1.0) (New)
- Level Device Family (TS20160-11 r1.02)
- Modulating Final Control Device Family (TS20160-15 r1.0)
- Common Tables (TS20183 r28.0)
- Block Transfer (TS20190 r2.0)
Major Improvements
The specifications include the following major improvements:
- Simplified release process for Device Family and Block Transfer specifications, enabling the promulgation of 5 device family specifications.
- Modulating Final Control Family supporting a wide range of actuator types for final control elements. Includes innovative Override support for performing maintenance on the control element.
- Extensive clarification and guidance for implementing compliant data caching in HART-IP I/O Systems.
- Fine-tuned and clarified SafeHART requirements and procedures based on developer feedback and recommendations from exida IEC 61508 assessment.
- Clarified use of Device Variable Classification codes throughout the Protocol and retired code 0 "Not Yet Classified" that was included for HART 5 backward compatibility.
This is an important maintenance release incorporating lessons learned over the past 3+ years. In addition, per standard practice, editorial improvements, clarifications, and corrections were made as part of the general review of the specifications.
Details
The improvements are summarized by specification as follows.
Network Management r4.1
Based on feedback from member company developers, two areas of the Network Management specification have been improved: HART-IP I/O System Caching (Subsection 10.1.1) clarifications and SafeHART (Section 11).
- Extensive guidance and clarification have been provided to HART-IP I/O Systems caching requirements. Subjects include Delayed Response transactions, caching dynamic (process) data, stale data calculations, and refreshing the cache.
- Improvements to SafeHART requirements clarify and correct ambiguities identified by developers. In addition, a minor alignment was made based on feedback received during the exida IEC 61508 assessment.
Command Summary r11.1
This minor revision was primarily made to rationalize requirements and use of Device Variable Classification codes.
- Clarified use of Device Variable Classification codes and requirements for special requirements for Volumetric Flow Classification codes.
- Classification code 0 "Not Yet Classified" was included for HART 5 backward compatibility and has been retired. Classification code 0 shall not be used in new Device Types or in Device Revisions.
Common Practice Command r14.0
To improve the orthogonality of the Protocol, Command 554 "Read Instrument Type Code" has been added. Aside from this major change, the remaining improvements to the Common Practice Commands consist of clarifications:
- Clarified dependencies between Common Practice Commands and corresponding implementation requirements.
- Improved the wording of Commands 71 and 76 to clarify the function of securing host exclusive access to a field device.
- Clarified that engineering units in Command 79 must match the Device Variable units, eliminating ambiguities associated with unit code classification.
Block Transfer r2.0
This major revision simplifies and streamlines promulgation of port specifications while aligning with FieldComm Group best practices (balloting).
Device Families
Common Practice commands are general purpose and applicable to a wide range of device types and device variables. Device Families (r3.0) expands interoperability from the general to specialization by the addition of measurement and control.
This major revision simplifies the promulgation of Device Family specifications by adopting FieldComm Group best practices (balloting), enabling the release of five Device Families.
Temperature Device Family r3.0
Temperature is one of the original Device Families and supports the parameters and commands for Temperature measurement. This revision enhanced the Temperature family as follows:
- Introduced two new commands for supporting custom RTD Resistances and added the new data item "RTD Resistance" to Command 1025.
- Added additional Temperature Probe Types to Table 3.
- Added "Probe Short Detected" to Device Variable Status.
Pressure Device Family r1.0
(New) The Pressure Device Family allows the configuration of a pressure measurement to be determined. The properties are common to many pressure applications, including static pressure, differential pressure (e.g., to measure flow), and liquid level applications.
PID Device Family r2.0
PID is one of the original Device Families and defines the mandatory and optional properties required to configure and operate a simple PID controller. This revision clarified:
- Operation of Unit Code Classifications.
- Applying the input and output ranging functions.
- Operation of PID co-located in Actuators.
Totalizer Device Family r1.0
(New) This Device Family integrates a flow (mass, volumetric, power, etc.) rate to produce the total transferred by the connected flow. That flow is integrated to increment or decrement the total. Using the Totalizer Preset action facilitates use of the Totalizer Device Family in batching applications.
Level Device Family r1.02
The Level Device Family received a corrigendum update in this release, including updated illustrations.
MFC Device Family r1.0
(New) The Modulating Final Control Device Family provides a simple modulated analog output used to control the connected process. Examples of potential physical elements include heaters, servo-motors, linear actuators, valves, and variable speed drives. The Device Family is designed to be compatible with the PID Control Device Family.
