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.
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