Rosemount HART device not communicating with AMS

Hi all.

I have recently hooked up a 3051 pressure transmitter to our delta v (rev13.3) test rack and recorded base line readings and calibration verification into AMS (13.5) and everything worked as expected.

Once complete the E/I technician powered down disconnected the analog wiring from the device prior to disabling the HART channel and deleting the tag from the test rack controller.

The same tag was then installing out in the process area under a new controller and the 4-20ma signal (percent field value )is being used and working in the module.

The channel is HART enabled and the device was auto sensed & the proper device and revision was identified, on the channel. Once I went into AMS and tried to scan that particular device and alert came up stating that AMS could not communicate with the device.

We could go out to the device and hook up to it with a 475 with no problem and configure the device locally.

My question is, why can’t I communicate with the device via AMS? 

Is there a particular order to follow while setting up a HART device on a test rack, decommissioning it and the re commissioning it on a different controller.

thanks for your feedback in advance

  • There could be noise on the wires preventing HART communication while 4-20 mA still works. 475 can work locally because it is closer and can go into a "shout" mode if the wires are noisy. Use a multimeter to measure the noise level. See further explanation here: www.linkedin.com/.../
  • I don’t believe that it is a noise issue because the transmitter is wired up with a twisted pair shielded cable, and was not routed along higher voltage cables. I think it has something to do with the original set up on the test rack controller. Is it possible that the device locks up if it was decommissioned incorrectly?
  • In reply to Dan Mos:

    Hi Dan, since you have commissioned this device on a different channel on a different controller then decommissioned it and then move it to another DeltaV channel using the same Device tag. I believe that AMS DM is still looking at the same path as when you first commissioned the device and this is why AMS can’t communicate to the device since the path is not there anymore.
    I suggest you go to the first channel the device was on and change the DST back to its original dst and make it non HART channel (don’t forget to download) then use AMS DM remove device utility and remove that device tag from AMS database. Autosense the Device again from its current connection then do a rebuilt Hierarchy in AMS DM. This should do the trick. If it don’t, let me know and we can chat to figure this out.
  • Hi Tinh. 
    Thanks for your response, I read through books on line and contacted my LBP rep. and we discussed your response and it looks like I will have to go through the remove device utility.

    I haven’t tried the utility yet because I think there will be a couple devices to remove from the data base but one device hasn’t been hooked up to its final controller yet.

    Am I understanding correctly that when I go through the utility I will lose all the saved information for that device, like calibration records and device notes?

    Can I still execute the remove device utility if I don’t relocate the device to the original controller and channel?

    I did successfully communicate with one of my flow transmitters that was not communicating, when I wired it to the channel on the test rack where I originally set it up, but when I disabled the HART channel and wired it to a different HART channel it still wouldn’t communicate.

    My last question would be is there a proper procedure for enabling a HART device on a “test rack” calibrating & documenting into AMS then disabling the HART device and relocating it to another controller, without this problem occurring again?

    Thanks for your time and assistance 

    Dan

    Sent from my iPad

    On Feb 3, 2019, at 3:57 PM, Tinh Phan <bounce-Tinh_Phan@emersonexchange365.com> wrote:

    Update from Emerson Exchange 365
    <4TSEJO475AEY-jpg_2D00_70x70x2-jpg>
    Tinh Phan

    Hi Dan, since you have commissioned this device on a different channel on a different controller then decommissioned it and then move it to another DeltaV channel using the same Device tag. I believe that AMS DM is still looking at the same path as when you first commissioned the device and this is why AMS can’t communicate to the device since the path is not there anymore.
    I suggest you go to the first channel the device was on and change the DST back to its original dst and make it non HART channel (don’t forget to download) then use AMS DM remove device utility and remove that device tag from AMS database. Autosense the Device again from its current connection then do a rebuilt Hierarchy in AMS DM. This should do the trick. If it don’t, let me know and we can chat to figure this out.

    View online

     

    You received this notification because you subscribed to the forum.  To unsubscribe from only this thread, go here.

    Flag this post as spam/abuse.

  • In reply to Dan Mos:

    Yes, if you use remove device utility, you will lose all the device data.
    Let try one thing before removing the device out of AMS database.
    As you mentioned, you just disabled your channel and moved the device to another channel and it stop working. This time, go into the channel property and change the channel to non HART channel and change the autosense hart tag name from Ex. TT101 to a deltaV dst ex. CTLR1C01CH02 then download the card. Now go to the flow device new channel and RE-autosense the channel. Go to AMS DM and rebuild hierarchy at the DeltaV Network level. The flow device should appear in the right channel. Scan the device and this should work. If it communicates, you don’t have to remove the device out of AMS database and still have all your Device calibration and notes.
    Let me know how this goes. Good Luck
  • In reply to Tinh Phan:

    Hi Tinh.
    we have a couple quick question before we execute the rebuild hierarchy operation since we have never done it before.
    1. How long does a rebuild hierarchy operation usually take?
    2. How long does a scan new operation take, is it like the scan all operation where its recommended to do it over night when the there are no users on the system?
    3. Should we back up the data base prior to the rebuild hierarchy operation?

    Thanks
  • In reply to Dan Mos:

    1) not long at all. Within few minutes.
    2) you only need to do scan on your device you are working on. Don’t need to rescan devices that you have scanned already. This should be pretty quick but depends on how many parameters the device has. Again, it don’t take that long for one device.
    3) it’s always best to backup your AMS DM database but in this case, what you are trying to accomplish will not affect your other devices.
  • In reply to Tinh Phan:

    Hi Tinh
    I tried all of your suggestions to recover the communications with the device, unfortunately the only successful method was to delete the device from the AMS database, all the calibration data was lost as you said but I was fortunate enough to have printed off a hard copy prior to the deletion.
    Once we completed the remove device utility and restarted the AMS servers, I assigned the device to the proper controller and enabled the HART analog input channel that the device was assigned to.
    As per our configuration practices I downloaded the card and auto sensed the channel.
    Once complete in explorer I moved over to AMS device manager and executed the rebuild hierarchy at the network level and then performed the scan new device operation at the card level.
    I was very please to see my device scan properly.
    Thank you for all of your advise and assistance with this matter.

    Dan