jomalley
September 21st, 2005, 10:18 AM
If you are using Emerson AMS on Delta V for Fieldbus, I would like to hear how you have configured the AMS. My issues/questions are in regard to how AMS handles other vendor’s equipment.
Some of my concerns are as follows:
1 With the Delta V “.hfx” conversion have you noticed that some parameters and function blocks are not supported or show up on the explorer?
2 With non-Emerson devices how do you collect and alarm on parameters that are unique to a particular vendor with AMS? Is this easily done?
3 How do you capture valve signatures into AMS from non-Emerson devices that don’t have a supported valve signature program? Are you driving the valve up, down and making step changes, and recording the parameter feed back onto a separate graphical package and then saving the captured data to ASM as a “.bmp” or other file type?
Looking for some feed back.
Thanks,
jim
Some of my concerns are as follows:
1 With the Delta V “.hfx” conversion have you noticed that some parameters and function blocks are not supported or show up on the explorer?
2 With non-Emerson devices how do you collect and alarm on parameters that are unique to a particular vendor with AMS? Is this easily done?
3 How do you capture valve signatures into AMS from non-Emerson devices that don’t have a supported valve signature program? Are you driving the valve up, down and making step changes, and recording the parameter feed back onto a separate graphical package and then saving the captured data to ASM as a “.bmp” or other file type?
Looking for some feed back.
Thanks,
jim