Emerson Exchange 365

• Not Answered

Setting up alarms/alerts in DeltaV and AMS

Dear all,

 

We developed a DD for a HART device and successfully installed it in AMS and DeltaV

Due to historical reasons the the status bytes of our device have some bits set if status is ok (eg. Ready_And_Remote).

-          In AMS Device Manager those bits are marked red and show up as fault.

-          In DeltaV it is displayed as ADVISORY alarm.

 

To get those bits ignored (by means of DD and device installation package) I tried following approaches:

-          Setup an alert file without those bits described à seem to be ignored and replaced by a generated alert file

-          Configured the Alarm Conditions in DeltaV manually, made an export of the database to fhx (‘c:\DeltaV\bin\dbImpExpClient.exe -e DeltaV_System dvExport.fhx’) and inserted the device specific settings into the fhx file of the device installation package, to make it common usable with every installation – but no success L

 

My conclusion is:

-          The alert/alm/fhx files seem to be ignored during ‘Add Device Type’ process – a file diff between the ones provided in the device install kit versus the ones in \ams\devices\HART\... directory let guess it.

-          Also the ddinstall.log seem to document it:

08/20/18 14:02:35          Installing AUMA SIPOS SEVEN actuator (HART) Rev 1 DD Rev 1

08.20.18 14:02:35          AmsHartFileGen:  Parsing file C:\AMS\devices\Transfer\\sfvc.\0101.fm8

08.20.18 14:02:36          AmsHartFileGen:  Parsing file C:\AMS\devices\Transfer\\sfvc.\0101.fm8

08.20.18 14:02:36          AmsHartFileGen:  ALERT file generation succeed.

08.20.18 14:02:36          AmsHartFileGen|ALM Generation:  ALM file generation succeed.

08.20.18 14:02:36          AmsHartFileGen|FHX Generation:  FHX file generation succeed.

 

Is there a way to configure those alarms? How to solve it?

 

Kind regards Mathias   i.A. Mathias Monse R&D SWR   SIPOS Aktorik GmbH Im Erlet 2 • 90518 Altdorf | Germany Tel +49 9187 9227-5234 • Fax +49 9187 9227-75234 mathias.monse@sipos.de • www.sipos.de Registered: Altdorf / Commercial Registries: Nürnberg HRB 16546 Managing Directors: Dr. Jörg Hoffmann, Dr. Thomas Suckut

 

 

Mathias Monse

• 21 Aug 2018 7:43 AM
• Cancel

2 Replies

• Tinh Phan

  

  • 21 Aug 2018 3:34 PM

  Hi Mathias,
  I am not a DD developer to advise how to correct this in your DD but I have a suggestion. You can go the the DeltaV device library and modify those alerts setting to your specification. You can then export the device and get an fhx output. When you import this device back into another DeltaV system of same version, it should have the alerts setting per your specification. You will need to package your DD in a why where both AMS Device Manager and DeltaV will be in sync. Download a DD from the Emerson Install Kits website and maybe you can mimic it. site: www.emerson.com/.../software-downloads-drivers
  
  Note: there is an Emerson 3rd party test team that do evaluation of devices and create these DeltaV and AMS Device Manager install kits and post them on this site as well. You might want to utilize them and get a second hand look at your quality of work. They already have test plans developed and automation system to run your device. email me if you like to get connected to this team.
  
  Have this device been through the HART Foundation certifcation program?

  • Cancel
• Mathias Monse

  

  • 22 Aug 2018 12:47 PM

  In reply to Tinh Phan:

  Hi Tinh,
  
  thank you for your reply.
  Our device is not registred with Field Comm Group yet. But it is scheduled at end of this year. But it passed the HART conformance test with HCF_KIT-192.
  
  I followed your proposed approch but unfortunately without success.
  - built a template from the device to adjust the Alarm Conditions setting, exported it to fhx and merged the result into the device install kit
  - checked the definitions in alm/fhx/alert files for consistency - with reference to some of the listed device drivers from Emerson
  - then deleted the DD from the DeltaV system (proof: after removing the device type I auto-sensed the HART device what yield a message like 'device type unknown -- please add device desription')
  - after re-installation the device installation kit the alarm list was still the same as before
  
  I cross-checked all steps and changes but could not find a typo, inconsistency or the like. But all changes were not effective.
  
  Kind regards
  Mathias

  • Cancel