Emerson Exchange 365

How to Change Range of FF Transmitters using AMS.

Greeting Everyone,

Can anyone please tell me hoe can I change Change Range of FF transmitters Using AMS ?

At my previous site I have changed range of RMT transmitters as I got an option to do that but at my current site I want to change range of E&H transmitter and I am not getting any option to do that. I know that AMS has all the functionality of a communicator. I am able to change range using communicator as I can access the settings of FFAI blocks but in AMS I am able to see only transducer Blocks and no FFAI blocks.

Also what is the difference between AMS device Manager And AMS device Configurator ?

Siddiqui

• 2 Apr 2018 5:31 AM
• Cancel

13 Replies

• Martin V

  

  • 2 Apr 2018 9:48 AM

  Usually done in the AI block  with the parameter XD scale. 

  Not in AMS but in the database. Mind the Engineering Units

  
  

  
  

  
  

  Verzonden vanaf mijn Samsung Galaxy-smartphone.

  
  

  -------- Oorspronkelijk bericht --------

  Van: Siddiqui <bounce-Siddiqui@emersonexchange365.com>

  Datum: 02-04-18 07:33 (GMT+01:00)

  Aan: DeltaV@emersonexchange365.com

  Onderwerp: [EE365 DeltaV Group] How to Change Range of FF Transmitters using AMS.

  
  

  Update from Emerson Exchange 365 Siddiqui Greeting Everyone, Can anyone please tell me hoe can I change Change Range of FF transmitters Using AMS ? At my previous site I have changed range of RMT transmitters as I got an option to do that but at my current site I want to change range of E&H transmitter and I am not getting any option to do that. I know that AMS has all the functionality of a communicator. I am able to change range using communicator as I can access the settings of FFAI blocks but in AMS I am able to see only transducer Blocks and no FFAI blocks. Also what is the difference between AMS device Manager And AMS device Configurator ? View online   You received this notification because you subscribed to the forum.  To stop receiving updates from only this thread, go here. Flag this post as spam/abuse.

  • Cancel
• Jonas Berge

  

  • 2 Apr 2018 11:30 AM

  For FF you don't have to set the range in the transmitter the 4-20 mA way. The range is set in the system database (AI block) and downloaded to the device when the device is commissioned. You define the range once, in a single place.

  • Cancel
• Andre Dicaire

  

  • 2 Apr 2018 2:31 PM

  AMS Device Manager is a full feature Asset Management software for tracking device changes and alerts. AMS Device Configurator provides a subset of Tools from Device Manager that allows DeltaV to interface with FF Devices, and to be able to commission them onto a segment of an H1 Card in DeltaV Explorer.
  
  You should be able to re-range the FFAI block from the DeltaV control module where the block is bound.

  Andre Dicaire

  • Cancel
• Siddiqui

  

  • 3 Apr 2018 2:57 AM

  In reply to Martin V:

  Thank you

  • Cancel
• Siddiqui

  

  • 3 Apr 2018 6:22 AM

  In reply to Andre Dicaire:

  Thank you Andre,
  
  I have an FF flow transmitter in AMS it's actual mode is showing automatic but in database module its actual mode is showing Out of Service

  • Cancel
• Roddyc

  

  • 3 Apr 2018 3:32 PM

  In reply to Siddiqui:

  I recently had a similar issue, where the STATE exhibited a mismatch and I could not change the Range. The problem was the Eng Units were not matching between AMS and DeltaV, once they matched all operated as expected.

  • Cancel
• Siddiqui

  

  • 3 Apr 2018 3:48 PM

  In reply to Roddyc:

  Thank you.
  
  How did you matched the range. Did you change it using communicator ?
  
  I have set 0-50 m3/hr scale in xd_scale but when i go online and check xd_scale its different.
  
  Also when I download the module it says some parameter were not transferred to device check process history view.
  Then I checked process history view it said xd_scale write error.
  
  I am not getting what I am doing wrong. I want to change range of FF transmitter without using communicator.

  • Cancel
• John Rezabek

  

  • 3 Apr 2018 4:35 PM

  In reply to Siddiqui:

  Not using a communicator is the method I prefer. Using an engineering-capable DeltaV workstation, open the module that contains the transmitter's AI block. For this issue I would open it "offline" with Control Studio.
  
  Make sure that you have assigned the AI block to your device of choice, and "save" the module (not download).
  
  If you are fortunate enough to have a later versions of DeltaV (at least 11.x.x if I remember correctly) you can now select the AI block you assigned, and select the XD_SCALE parameter. If you see a checkbox like "allow user entered value", uncheck it. Alternately you can select the field and click "What's This" or "Help", and then click the link for "valid units and channel numbers for fieldbus devices". Use the help field to locate your device make & model number / revision, noting the acceptable units and channel. Ensure you have chosen / set eng. units and channel appropriately. Then set the minimum and maximum units as you desire (re-range).
  
  I have not tried this with a communicator. I would use "Control Studio".
  
  When you are finsihed, download from Control Studio. Ensure you know all the modules using your measurementm, as it will cycle through OOS as the d/l proceeds. If the connected modules do not utilize measurement status, they may behave in an undesirable fashion.

  • Cancel
• Andre Dicaire

  

  • 3 Apr 2018 4:58 PM

  In reply to Siddiqui:

  The Eng Units must be supported by the device to be accepted. John explains how later version of DeltaV helps with this by identifying supported Units. You may need to review the device manual and find the right syntax.

  Andre Dicaire

  • Cancel
• Roddyc

  

  • 4 Apr 2018 7:03 AM

  Hi Siddiqui

   

  I changed the xd_scale in DeltaV to match the existing units in the transmitter.

   

  The errors are exactly as I was seeing.

   

  In my case the Xmitter was setup as Kg/H and I had used Kg/Hr in the XD_SCALE in error. Changing this to Kg/H allowed the configuration to load and all values report correctly.

   

  IF you want to change the units I think this may require to use the communicator, but a simple range change using the existing units should be OK with XD_SCALE values.

   

   

  • Cancel
• John Rezabek

  

  • 4 Apr 2018 1:10 PM

  In reply to Roddyc:

  In my experience, Kg/H does not equal Kg/Hr.

  I have never had to set any units in a device using a communicator, interacting with all varieties of FF devices for the last 20 years or so. I have a friend who throws all handheld communicators in the ocean when he finds one.

  The units must match exactly. From what I have seen, the device will adopt the units of XD_SCALE if indeed you choose compatible units. DeltaV will display all engineering units known to man (practically) but a specific device (E+H if I recall correctly) will only function with a relatively limited subset of units. Choose a unit that is displayed in DeltaV Books Online help for the specific make, model, and revision.

  Download the module (necessary).

  If you are still having issues, use DeltaV to open the devices "Configure" screen (this is AMS functionality which should be in any DeltaV system licensed for FF) - right click on the live device as seen in DeltaV Explorer - and ensure that "requested mode" in all transducer and resource blocks is set to "Automatic".

  These screenshots depict the sequence of dialog boxes to learn the units that are okay for a given device. Note they are not the same for every channel.

  

  • Cancel
• Siddiqui

  

  • 6 Apr 2018 10:19 AM

  In reply to John Rezabek:

  Thank you everyone for your response,

  Andre,

  I have looked the ranges and kept it accordingly but still while downloading it says failed to write some parameter to device check process history view. Transmitter isnt accepting xd_scale range.

  Is there some write protection in the transmitter which prevent DCS to write data onto transmmitter block.?

  • Cancel
• Jonas Berge

  

  • 6 Apr 2018 2:24 PM

  In reply to Siddiqui:

  block has to be in out-of-service mode to write xd_scale

  • Cancel