Question: Issues with E+H Prowirl 200 series FF bus vortex flow meters
Thread Content
Question: Issues with E+H Prowirl 200 series FF bus vortex flow meters. DCS: Zhejiang University Zhongkong. The on-site meter display shows a normal value of 2.5 cubic meters per hour, while the FIELD_VAL value of the AI module in the FF hardware configuration is only around 0.0007. Why must out_scale be set to 360,000 for the PV value of the central DCS to match the display on site? ?
When the FIELD_VAL value of the AI module in the FF hardware configuration is around 0.0007, what is the value of the out_scale setting? ?
This post was last edited by RZT4007110 on 2018-3-16 at 15:40. Regardless of the value set for out_scale, when the volume on site is around 2.5 cubic meters, the FIELD_VAL value is around 0.0007; when the volume is around 1 cubic meter, the FIELD_VAL value is around 0.00027.
Oh, I haven’t worked with FF meters yet, but the menu interface in this picture seems a bit similar to that of HART meters. FF meters should also have access testing functions, right?
Please try changing L_TYPE to direct or direct independent range
It doesn’t matter if it’s changed; whether it’s direct or indirect, it makes no difference. However, if the variable is changed to temperature, it will switch between Celsius and absolute temperature.
The main purpose of the L_TYPE parameter is to select between direct, indirect, or indirectly squared root signal conversion. When the poster selects a certain range in OUT_SCALE, the data matches, which suggests that a linearization transformation may have been applied. Since FF is digital communication itself, it is recommended to try it directly.
I suggest you make the following changes and try again: First, change XD_SCALE to the range you need, such as 0-50 m3/h. Second, also change OUT_SCALE to 0-50 m3/h. Third, change L_TYPE to directly
The last edit to this post was made by RZT4007110 on 2018-3-18 at 17:24; the value of L_TYPE was changed, and the output value became FIELD_Val. It’s possible that there is still some setting issue – I’ll take another look tomorrow :( During the initial debugging phase, I consulted with the after-sales and control system engineers from E+H, and they also set the value to 360,000. Given the high requirements of the process, I didn’t dare make any changes arbitrarily. Recently, another unit was added elsewhere, so I need to learn more about it*:Q
It is presumed that the unit of FIELD_VAL is m3/s, and multiplying by 3600 gives m3/h
There is a field where the unit for the header should be changed to cubic meters per minute; the DCS range (cubic meters per hour) can only be set to 6000, otherwise it will not match the actual flow rate: L:L. We also suspect it’s a setting issue on the device, but it can’t be 360,000 either – it’s not a multiple of either hours or seconds, nor of milliseconds.