I am attempting to test an Edress-Hauser foundation fieldbus transmitter on my DeltaV system. I initially tested the device on the bench top to review all of the configuration parameters. I have installed the device in my process where an Emerson 3051 Fieldbus pressure transmitter was located. I decommissioned the original 3051, set the device tag properties and commissioned the new PT to the original tag. I had removed the device tag assignment from the control studio module and downloaded the module with an AI block missing an assignment. I then reassigned the device tag to the AI block, set the channel, scale, etc, and downloaded the module. However, I get an error out of the pressure transmitter because the actual mode of the device is 'OOS'.
I have checked the actual device and all the transducer and resource modes are in 'Auto'. The actual device is reading the correct readout on it's display panel. I have also set up new modules from scratch and assigned the device to a new AI block and the device then reads correctly and is in the correct mode. But whenever I try to assign it to the original control module it will not work.
Does anyone have any suggestions? The Emerson Global Support center has not been able to come up with a solution at this point.
Mike,
I am making some guesses here. So, my answer may not be right. When you decommission a Fieldbus device with the intent of replacing it, you also have to make it a spare. If I remember right, the manufacturer serial number (or its equivalent) also gets stored in the database and it will not get removed until you make it a spare. You may want to compare what is the offline data (on the Proplus) versus what is in the online data (field instrument) to see if there are any remaining data from the old 3051.
I don't recall as to where exactly in DeltaV explorer is a place where you can "scan for new devices". I know that there is a place where you can do this. This feature will identify a new instrument and then scan all its properties (manufacturer, model number, serial number etc) and then bring it into the database. Once that is done, you should be able to commission the new device.
As I mentioned above, this is just a guess on my part. Usually decommissioning an instrument is the equivalent of "temporarily taking it off line with the intent of returning the same instrument back in line later" where as making it a spare is the equivalent of "putting it on a shelf" so that it can be used some other place.
Not sure if this helps. Good Luck.
Kris
In reply to Kris Chandrashekar:
Hello Kris,
Yes, I made the original device a spare. I was able to commission the new device and assign it to the original device tag. I then check the diagnostics of the new device before I attempted to assign it in the control module. Everything with the actual device is working well. I can start a new control module and assign the device to an AI block with the exact same settings programmed into it and the device works correctly. But in the original control module it is not working.
It seems like one step was missing. When the original device was decommissioned, it should be made a spare. The place holder for the 3051 should be changed to the EH device type and the port downloaded. The EH device can be now dragged from standby to the place holder. Download the port. The AI block in control studio should be automatically unassigned, but if it is not, it would not hurt to unassign it, save and download the module, assign the block to EH , save and download the module. It should work. If there are problems, download the port again.
(Posted by Dave Imming - answer from Marcos Peluso)
In reply to Dave Imming:
Dave,
That is exactly what I did. I started by decommissioning the 3051 and making it a spare. I do not believe I could have even commissioned the EH in the same tag if I had not made the original a spare.
I changed the device properties of the place holder to the EH, commissioned the EH and downloaded the device. I then opened the device parameters through AMS diagnostics and reviewed all of the transducer and resource blocks to ensure everything was in the proper mode and that I had a good reading through the PV tab. Everything was good. I then assigned it in the control module to the AI block and I get a OOS mode when it is in the control module. If I unassign the PT from the AI block in the module and start a completely new module with a new AI block assigned to the PT on channel 1, then it works perfectly well and I get a good reading. Just not in the original control module.
My initial thinking was that it was something with the control valve not talking correctly to the new PT but the error signal is on the output of the AI block, not on the input to the PID block.
In reply to mikesteiger:
Mike
Did you check the online parameters od AI fb? Open your software module online and make large the parameters windows you will see 2 columns "ONLINE" & "DEFAULT" value, is some of online parameter is different from default value this mean that ff device can not accept this value, mostly there is a problem with xd_scale (pv_scale) or alarms limits, for example 3015 need mmh2o (at 4C) if you set this for you EH transmitter can be not correct (check the Valid Engineering Units for your EH). Also the alarms limits even if some alarm is disable the limit must be set inside the range of the transmitter. After the download of module there is an information at download window that some of the parameter has been not transmitted you can verify the events log (PHV) and see what is wrong. So the OOS mean also that the confi
Let me also know which bits are set in ai block_err and bad_active parameters.
Regards
Dawid
In reply to Dawid.Zieba:
David,
It ended up being the valid engineering units for the EH. Apparently valid units for the PV scale and XD scale have to be 'PSI' for an absolute E&H pressure transmitter. The instrument is set for absolute measurement but won't support the unit of PSIA, even though I requested PSIA for the units.