SLAAEH0 November   2023 AFE781H1 , AFE782H1 , AFE881H1 , AFE882H1 , DAC161P997 , DAC161S997 , DAC7750 , DAC7760 , DAC8740H , DAC8741H , DAC8742H , DAC8750 , DAC8760 , DAC8771 , DAC8775

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction to the HART Protocol
    1. 1.1 Different Forms of the HART Protocol
    2. 1.2 HART as an Enhancement to the 4-20 mA Loop
    3. 1.3 The HART FSK Signal
    4. 1.4 HART Configurations
    5. 1.5 HART Protocol Structure
      1. 1.5.1 HART Communication
      2. 1.5.2 HART Bytes
      3. 1.5.3 HART Data Frame Structure
        1. 1.5.3.1 HART Start Byte
        2. 1.5.3.2 HART Device Addressing
        3. 1.5.3.3 HART Commands
  5. 2HART Protocol and Test Specifications
    1. 2.1 The OSI Protocol Model
    2. 2.2 HART Protocol Specifications
    3. 2.3 HART Test Specifications
  6. 3TI HART Enabled Devices
    1. 3.1 TI DACs with HART Connections
    2. 3.2 TI HART Modems
  7. 4Conclusion
  8. 5References

HART Commands

The HART command is sent in a single byte after the expansion bytes in the frame. Commands from a host to a field device can read information from a device such as variables, status, or device information. Commands also can write to a field device to set polling addresses, and write descriptors and messages.

Commands are classified into several categories. First, there are universal commands that are required for all field devices and must be supported for the HART protocol. Second, common-practice commands are implemented for many, but not all devices in a standard format. There are also device-specific commands that can be used for a particular device or device manufacturer. Finally, there are device family commands that can be used for standard functions for a set of device types or manufacturer defined measurements for generic access to the family.

Universal commands are defined for commands 0 - 30, 38, and 48 and describe basic transactions between the host and the field device. Universal commands read device identification, dynamic variables, and other information. These commands also write polling addresses and other identifying information to the device memory. To be compliant with the HART protocol, universal commands must be implemented. Note that with a single byte, basic commands are limited from 0 to 255. Command 31 indicates a 16-bit command number shown in the data field which significantly expands possible commands to a field device.

Common-practice commands are defined from 32 to 121 (except 38 and 48) and are not used in all field devices. When used, common-practice commands must be implemented as described in the protocol. Additional common-practice commands include commands 512 - 767 through expansion.

Commands 122 - 126 are intended for factory use, and 129 and 254 to 511 are reserved. There are additional device-specific commands depending on sensor or actuator type for field devices, and other commands for wireless devices, and WirelessHART within the 16-bit expansion.