How can i get a specific device parameter over foundation fieldbus to deltav

Hi,

I am new to the world of DeltaV and just starting to deal with it at my new job.. been working with Foxboro I/A before that..

I wanted to get a specific parameter from a MicroMotion2700 (MVD2700 ver 8) series foundation fieldbus flowmeter into DeltaV so that i can use it in control studio but can't seem to figure out how..

The parameter mnemonic  i am looking for is "ALARM2_STATUS" so that i can use the determination of a not full pipe pipe to delay control and alarming..

The device data file doesnot has it.. so there is no specific tag that i can browse to and get data in.. it essentially has the transducer objects, AIs, AOUTs, DOs etc.. along with fieldbus alarms of Advise, Comms, failed, maint..

using Foxboro and  HART i could refer to the parameter i needed and set up a Real In fielddevice block to get the data.. so would point to FTXXX/STATUS1 for get value for STATUS1 from device..

According to the manual the FT , parameter mnemonic "ALARM2_STATUS" has OD index of 12, message type ENUM, datatype bit string (2 bytes)..

Is there a way to get that into a control control strategy wherein i can parse it using a BFO block to get value for bit 13 (value of 0x1000) that i need to delay alarming..

Thankyou

  • Jas why not just bring in the density using an AI block. When the density is outside the range for the substance of interest that would indicate a not-full pipe. I believe it should also go to "BAD" or "UNCERTAIN" quality.

    Otherwise - you can use OPC mirror and browse to the block that has the parameter and map it to a variable in your module. That may require some licensing upgrades . . .
  • In reply to John Rezabek:

    Appreciate the reply John,
    I will look into the density quality when i get a chance..
    for the OPC i tried using OPCWatchIt to try to browse and read the parameter and it failed.. i was able to browse to the FIT/transducer1600/Alarm2_status/CV
    Status: "Get item failed: 80040154"
    Error Meg: "Class not registered "
    and the path: "DEVICE:00031020000009172015075807127375/1600/ALARM2_STATUS.CV"

    Not sure what is missing.. thank you
  • In reply to jas:

    Quick note.. seems like it is not just this one fieldbus device.. i tried a few more and same result..
    I can get to the data from profibus devices though..
    Tried to just set path to AI1 folder but OPC fails to dive into the folder for that one..
  • In reply to jas:

    As best I recall, I get the same message from OPCWatchit. I believe there's a divide between the DeltaV OPC server and the AMS OPC server. I can browse to the AMS (transducer block) parameters using OPC mirror. I think you can find OPC Mirror on one of the install discs (like "DeltaV Extras" maybe) and there might even be some trial licensing available.

    My system is also licensed for a couple gobs of OPC points, since that is how we serve data to the business network historian. If you have a node that is so licensed, you might want to try it (browse to the device parameter) from there . . .

    As for the problem you're solving - I took a look at one of our 2700's and there's a setting for "slug flow" which I believe is what you're trying to detect. It is based on density, so I think you can do the same thing with the "Rosemount" AI block, which can be configured with a discrete output (handy). There is no additional licensing - Duncan charges you a DST for the first block but any additional blocks are "free".
  • In reply to John Rezabek:

    That is excellent info John !! very much appreciate it..
    I am not sure if I have access to all components of the system yet.. too early to trust me with it :) but I will discuss it with my colleagues and see if we can check out the OPC mirror and the slug detection..
    and reading through the slug detection.. if may provide value as it is looking for any entrained gas..
    Thanks for the info.. hope to try it out soon and report back ..
  • In reply to John Rezabek:

    Personally I love the fact that DeltaV charges only a single tag for a Fieldbus device although you may actually use on average maybe 3 I/O per FF device. Together with the fact you don’t need to run wires for and use up I/O channels for each signal, this makes it faster and cheaper to take advantage of the full functionality of digital devices. Just like a Coriolis mass-flow meter, an intelligent on-off valve has 3 I/O signals but is counted as a single Fieldbus device. An electric actuator / Motor Operated Valve (MOV) has 16 I/O signals but is a single Fieldbus device:
    www.linkedin.com/.../how-one-plant-cut-44-wires-down-2-jonas-berge
  • I am not sure if you already had a look in Books Online. Search for "Accessing intelligent field device diagnostic data" and you'll find a couple of examples. As for your problem with OPCWatchit, you can run it on any station, but you MUST point it to use an OPC server which has both AMS and DeltaV installed. Pointing it to your local machine (Host = Local Machine) will not work if the station does not have AMS.
  • In reply to István Orbán:

    Hi, I tried looking at the Books Online did not find specifically what I was looking for..
    Still have not got a chance to seek out any my colleagues how can try this out for me..
    And seems like we don't have many instances that have both AMS and DeltaV opc licensed :)..
    Will continue to seek out my colleagues and we see if we try routes as suggested.. thanx..
  • In reply to jas:

    The server that serves for OPC mirror also has only DeltaV OPC installed and not the AMS.. so no luck there.. may have to look at slug flow or see if we have an option for both servers somehow.. thankyou