Can't configure Flowserve Logix 3400MD Positioner with AMS 11.5 / Delta V 11.3

Hy everyone,

We got 7 new Flowserve Logix 3400MD Fieldbus positioner and we are not able to configure any of them using AMS 11.5,

The posiitoner is connected to a FF H1 segment and it appears on the device three on AMS

We open the device and then we try to configure and we receibe a message that says: "The block is bussy running another method"; but this only happens with the main transducer block

The XDTB_MAIN (TRANSDUCER2000)  shows this message if we click on any of it’s methods ( Show device information, Set Specific Device Parameters, Configure Device)

 <a href="http://www.freeimagehosting.net/"><img src="http://i.imgur.com/0cTcifi.png" alt="Free Image Hosting"></a>

With the other blocks (device status, functional blocks) everithing seems to work fine

<a href="http://www.freeimagehosting.net/"><img src="http://i.imgur.com/XY4updO.png" alt="Free Image Hosting"></a>

Please see the attached file for details

Thanks in advance for your hep

Best Regards

Diego

11 Replies

  • Hi,

    have you checked in DV that alll of the devices are comissioned?

    Check for differences in DV and also check the status and diagnostics data between functioning positioners and non functioning..

    Niklas Flykt 

    Klinkmann Oy

    Key Account Manager safety products

    nikfly@gmail.com

  • In reply to Niklas Flykt:

    I  just checked up and all the positioners are commisioned and all of them show the same problem, running  the diagnostic tool everithing seems to be ok

  • In reply to Niklas Flykt:

    Hello Diego,

    Here are some thoughts why you may be having this issue.  First, can you tell me what device rev this is?  If this is a Rev 1, It should work OK.

    Comments:

    "The block is busy running another method";

    AMS can only run 1 device method at a time.  This message appears when AMS detects multiple methods being launched.

    If launching this screen executes multiple methods to populate fields, just wait a while after launching the transducer block screen.

    AMS sometimes runs methods that do not require user input, this appears in the Windows task bar only, and only looking at the taskbar looks like multiple copies of AMS are launched.

    Another thing to try is before you launch the transducer block screen, try to start a method from the DeltaV device placeholder.  If you get the same message, that is an indication that AMS is running another method, or AMS “thinks” there is another method running.

    It is possible there is a conflict in the AMS database.  

    If you are able, you could try decommission, delete placeholder, remove device from AMS database, recommission the device.

    I hope this helps.

  • In reply to dbarrigac:

    We got this problem with the new positioner model wich is flowserve logix 3400MD

  • In reply to dbarrigac:

    I need to know more detail info about this Flowserve Logix 3400MD.  What is the Revision and FW on the device?  These information is critical to the Device Descriptor for DeltaV and AMS to communicate to the device. Did you installed any DD into the system before commissioning it?

  • In reply to Tinh Phan:

    The positioner is a flowserve logix 3400MD revision one and we are using the DD file that comes with Ams 11.5

  • In reply to dbarrigac:

    It seems like it should work.  I would recommend that you use AMS Terminate Servers(Start/All Program/AMS Device Manager/Terminate Servers) to shutdown AMS methods that maybe running, relaunch AMS manually, and then try your method again but this time wait until this method complete before trying to launch another method.  Terminate Servers is the proper way to shutdown all AMS Services properly.  When you restart AMS, it will runs/Startup all AMS services properly.  This will verify that your AMS is working with DeltaV.  If you sill run into this issue after performing this, I recommend calling GSC up to support.  They can drill into your system and figure out what is the root cause.   Be aware that this still can be a device issue not responding to the AMS and DeltaV.

  • In reply to Tinh Phan:

    Do i have to do that in the ams server  or in the clients?

  • In reply to dbarrigac:

    Correct me if I'm wrong, but I believe the "methods" are device specific.  Mismatches between the device and the DeltaV/AMS DD could cause problems.  I only see a Rev 1 in the DD for this device so this may not be an issue.  Also, there is an AMS KBA on the Flowserve (You must have a Foundation support account to access KBA:  NK-1200-0043).  The KBA states that the device may stop responding during calibration methods if the RESOURCE and TRANSDUCER blocks are in AUTO.  It states that the blocks should be in MAN before executing the calibration methods.  This may or may not be applicable to the methods you are attempting.

    Are the valves in a running process?  If the process is not running, and you haven't already tried, you could execute a device reset from a handheld communicator.

  • In reply to Ben Bishop:

    I got some fresh news about this post.

    We called to Flowserve and they send us their local representative, this guy came and he made a hard reset in the fieldbus circuit board. After that we try to comission this device in DeltaV and we success, now we can calibrate the valve from AMS 11.5 and the valve is under observation, so far looks god. I'will show you more details about it.

    Flowserve’s Representative performed a HARD RESET to the positioner’s Fieldbus circuits. After that we commissioned the 3400MD positioner in our DCS with negative results, the valve doesn’t respond to the open and close DCS commands orders

    Delta V and AMS Versions

    ,   

    The positioner is recognized by the DeltaV System (Flowserve LX3400MD Rev 1) as follows

     

    1. When we use the Positioner’s Analog Output AO function block we got an error in the block diagram, the signal BKCAL_OUT of the AO block is flagged as a bad quality signal with a red “X” and the valve doesn’t respond to the DCS command signal, the valve doesn’t move.

     When we check the positioner’s AO Function Block Mode we see that the target mode is “Cascade” but the actual mode is in “Auto”.

     

    We try to change the actual AO block mode to “Cascade”  but the changes don’t affect the actual mode and it continues in “Auto” Mode

    The  Positioner’s AO Block Parameters

     

     

     

  • In reply to dbarrigac:

    Did you get this situation resolved?  Open AMS and do a rebuilt hierarchy at the DeltaV Network/go to the fieldbus Card and expand the port and scan the device by right clicking on the device.  Does the device completed the scan?  What icon do you see?

    What I am trying to see if the DD(device descriptor) and the device firmware are working together that were released by the manufacturer.