Emerson Exchange 365

AMS interface with HART devices of 3rd Party Systems thru Modbus TCP in PK Controllers

Can someone explain how can we access the HART devices from a 3rd party systems thru Modbus TCP on PK Controllers in AMS? The DeltaV version is v14.3.

Which interface are we going to select in AMS? Is it the DeltaV Network?

Thanks for your replies.

Rein

• 3 Sep 2019 4:47 PM
• Cancel

4 Replies

• Jonas Berge

  

  • 4 Sep 2019 2:00 AM

  Modbus/TCP is more for PV integration into DCS and PLC. Modbus/TCP is not good for device intelligence integration. To integrate HART devices use either native AMS protocol or HART-IP:
  www.emerson.com/.../product-data-sheet-hart-ip-interface-ams-en-5548898.pdf

  • Cancel
• Andre Dicaire

  

  • 4 Sep 2019 3:53 PM

  Sounds like you have multiple layers of communication. Reminds of Shrek...
  
  AMS has multiple device interfaces to connect to HART devices. However, your device is integrated into DeltaV via Modbus TCP. There is no path through the PK controller for AMS to access the end device. The DeltaV Network interface allows access to all HART devices connected to HART enabled DeltaV IO, including the WirelessHART Gateways and Wireless IO Card.
  
  Although you can probably map the HART data into Modbus Holding registers, the PK controller will be able to read these into control modules, but there is no mechanism to pass these to AMS as device data.
  
  As Jonas suggests, the device would require some sort of interface supported by AMS. For third part connected HART devices, the HART Multiplexer or Wireless Thumb are connected to the 4-20 mA signal to extract the HART data and send to AMS. AMS supports HART IP so if the device also supports HART IP, it would be possible set up a connection directly from AMS to the device, possibly over the same Ethernet network used by Modbus TCP. However, you now have to consider Cybersecurity and how to do this securely.
  
  This may also depend on the version of AMS. I believe the Generic HART IP interface for custom applications is only available on AMS v14.
  
  Some devices have a 4-20 mA HART output that can be connected to a DeltaV AI channel. While Modbus provides access to additional data at a faster update rate, the HART connection provides pass through connectivity to AMS.
  
  On Profibus, there is a Class 2 Master that allows AMS to connect to HART devices that are wired to IO nodes, like Stahl IS1 IO Node. The HART data can be mapped into Profibus data to the DeltaV Controller, but AMS connects to the device via this separate gateway. In AMS, these devices would be shown under this gateway rather than under the DeltaV network.
  
  I don't know if such a device exists for Modbus TCP interfaces.

  Andre Dicaire

  • Cancel
• Rein

  

  • 6 Sep 2019 10:37 AM

  In reply to Andre Dicaire:

  That means, it's either the conventional or the HART-IP interface.

  For conventional, the HART devices from 3rd party will be connected to HART-Mux then to Converter via RS485, then to AMS Server via RJ45.
  The RJ45 port of the PK controller is not meant for this purpose.

  For HART-IP interface, we just need the license. The HART-IP Interface is available with AMS Device Manager version 14.0 and higher.

  Below are the supported HART-IP Host Systems:„

  -Tricon CX v11.5„

  -HIMax Major Version 5„

  -Phoenix Contact Ethernet HART® Multiplexer

  • Cancel
• Jonas Berge

  

  • 5 Jun 2020 3:56 PM

  Thought I'd share some new information on HART-IP and how it relates to Modbus/TCP. The ultimate user guide to HART-IP between Intelligent Device Management (IDM) software, predictive analytics, HART multiplexers, WirelessHART gateways, and third-party SIS :
  -Justification
  -Technical description
  -Integration & architectures
  -Interoperability & interchangeability
  -Commissioning & management
  -Cybersecurity
  -Troubleshooting
  -Migration
  Here:
  www.linkedin.com/.../

  • Cancel