Emerson Exchange 365

• Not Answered

DeltaV Profibus Card and Siemens Remote IO Analogue Card HART Values

Hi all I am looking at using Siemens IO as Remote IO and I would like in some cases to be able to gain access to the HART data of some (not all) of the instrument I have on site, I have been reading various sites (a lot of which say in cant be done) but I have come across some sites that say it can by reading the Acyclic data is this possible in DeltaV and is there a guide on how to do this?

"Find out what functions exist in your Delta V DCS to do DPV1 related acyclic Dataset reading/writingfrom DP Slaves (the functionality is standardised by Profibus International, a Siemens PLC has SFC58/59 as well as SFB52/53 available for this purpose)."

GaryL

• 1 Feb 2016 4:06 PM
• Cancel

3 Replies

• Andre Dicaire

  

  • 1 Feb 2016 5:19 PM

  Connecting Third Party IO to a DeltaV Controller is not the primary go to solution and we would rather see DeltaV IO for full functionality. That said, Siemens IO will talk Profibus, and with the right GSD file, you can set up an IO node on the DeltaV PRofibus IO card. Emerson has tested the Stahl IS1 product as a Zone 1 IO product for this purpose. Also note that the primary function of Profibus integration to DeltaV is for Drives, MCC's, VFD's and the like.
  
  Although you can pull Acyclic Data from the Profibus Device, you will not be able to pull HART data from the connected field devices. To read HART variables into DeltaV, they must be mapped to the 244 Byte Input map from the device and configured as signals in DeltaV. DeltaV IO licensing in v12 provides the first 16 signals from a device for 1 DST. Signals above this will be licensed individually. If you have four transmitters with 4 HART variables, that will require 1 AI DST. If you have 4 more transmitters with 4 variables, that will require an additional 16 AI DST's. If you wire 8 HART transmitters to DeltaV IO, that will require 8 DST's.
  
  Another consideration is the maximum 244 Bytes per device on the Profibus segment. Each variable is 4 Bytes, and with the 4-20 mA signal, that can be 20 Bytes per device, so a maximum of 10 or 11 devices per node. Even if you do not use all the variables in DeltaV, they may still be mapped into the input map. The configuration options of the node may also dictate how the data map is laid out.
  
  Assuming the data map configuration suits your requirements, and you wish to retrieve HART data into the AMS Device manager database, you cannot use the Acyclic data reporting for this. You can add a Class 2 master to the Profibus segment to connect to the AMS Device manager computer. The Trebing and Himstedt device allows AMS to Poll HART data over Profibus. This is a third party device and you'll have to contact them for more details on installation. The device must be addressed on the segment at an address that does not conflict with DeltaV (1, or 0) or any other device on your segment. You would also need the connector in AMS to poll this device.

  Andre Dicaire

  • Cancel
• István Orbán

  

  • 3 Feb 2016 11:51 AM

  It might be worth to look in Books Online: Configuration/Module Reference/Accessing intelligent field device diagnostic data. But I doubt that you could get the HART info out with this method.

  • Cancel
• Nicholas Meyer

  

  • 3 Feb 2016 2:38 PM

  In reply to István Orbán:

  AMS Device Manager has many installations that access HART data (configuration or diagnostics) over a Profibus network. Our datasheet can provide you with more information. www2.emersonprocess.com/.../amsdm_ds_hartprofibus.pdf
  
  One important thing to note, the Trebing & Himstedt gateway that is referenced in the datasheet and above, has recently been added to the Softing portfolio.

  • Cancel