HART/IP

Though data on the HART/IP protocol is still difficult to come by – unless you want to shell out a membership or purchase the specifications for just under $1000. The need for the HART/IP protocol was for the backhaul network between WirelessHart gateways and the control system to provide access to the configuration and diagnostics information in the underlying WirelessHart transmitters, not just the process variable in a single environment. Until the HART/IP gateways are available and the protocol is ported to the associated Control systems, Users will continue to have to map parameters to other protocols such as Modbus/TCP or Ethernet/IP via the gateway access point.

HART/IP uses standard Ethernet hardware it therefore makes the HART network including the WirelessHart devices compatible with commercial and industrial grade LAN switches, fiber optic media converters, Wi-Fi access points, and related equipment.

Because the application layer is the same for HART field devices and HART/IP, time consuming and error- prone data mapping is eliminated thus making HART/IP is the backhaul network best suited for WirelessHART gateways and 4-20 mA/Hart multiplexers.

Just like USB and Ethernet complement each other on a computer the fieldbuses and their associated Ethernet network layers complement each other in the control system.

Other additions to the protocol ‘in response to User requests’ announced at the same time include:

Condensed Device Status Indicators – providing standardized support for NAMUR NE107 diagnostics.

Key Performance Indicators (KPI’s) - additional standardized commands to support NAMUR NE124 for network health and reliability data.

Discrete Functionality - support of several types of discrete and “on/off” type devices with diagnostics.

Infrared Device Access –for device configuration and maintenance.

Like all protocols, HART is not standing still and of course with FDI in the future of all DD based protocols there will be more news on the horizon.

What are your comments?

You cannot post comments until you have logged in. Login Here.

Comments

  • Products with HART-IP (note with dash, not a slash) are available since quite some time; for example, WirelessHART gateways from Emerson, Phoenix Contact, P+F, and E+H as well as in 4-20 mA/HART multiplexer from Ifak. The HART OPC server as well as the configuration software and intelligent device management (IDM) software from multiple vendors based on it also support HART-IP. This eliminates Modbus mapping for all the configuration and diagnostics parameters in massive amounts of devices. commDTMs for the gateways are also available allowing integration in configuration software and IDM software from multiple vendors based on FDT/DTM. Steam trap monitoring software from Emerson and Armstrong use HART-IP as does the machinery health management software from Emerson. There is already an HART-IP ecosystem forming. But sure, beyond IDM software I personally think it would be great if the Ethernet IO cards themselves in more DCS supported HART-IP such that Modbus mapping for the PV could also be eliminated.

    The HART-IP specification HCF_SPEC-085 rev 2.0 chapter 10 is not so helpful to users. I think an FAQ and white paper on HART-IP would be more useful.

    Reply

RSS feed for comments on this page | RSS feed for all comments