top of page

Ultrasonic Flow Holds Steady During Signal Loss? Check the Hold Setting

2 days ago
4 min read

An ultrasonic flow meter can continue presenting a plausible number after its acoustic measurement becomes unreliable. Before calling a flat trace steady flow, check whether the instrument is configured to retain its last good value during poor signal conditions. Repeatedly receiving that number does not, on its own, prove that the meter is producing fresh valid measurements.


The practical answer is to review the instrument’s fault-output policy before changing damping, zero or calibration. Then test the documented response of the particular display, output and recording path used by the application. A value deliberately retained by the field instrument is a different problem from a dashboard that has stopped receiving data.


Identify the hold setting on the exact instrument


The Holykell UF2000-series manual describes M28 as retaining the last good value during poor signal conditions, with YES shown as the default setting. Its menu table separately identifies M40 for damping and M29 for an empty-pipe signal threshold. These functions should not be treated as interchangeable explanations for a stationary flow number.


That is a documented UF2000-series example. It does not establish that another converter, handheld instrument or firmware uses the same menu numbers or output behaviour. Retrieve the supplied unit’s manual and record its model, firmware and actual setting. Do not change a production meter merely to match the example.


The pictured ProSight handheld ultrasonic flow meter is a catalogue example of a portable survey instrument. Confirm its applicable manual and fault-handling functions separately; the photograph is not evidence that the Holykell UF2000 menu table applies to that unit.


Orange handheld ultrasonic flow meter held beside two transducers clamped to a white pipe in a catalogue demonstration photograph.
ProSight handheld ultrasonic flow meter with externally clamped transducers. ProSense catalogue demonstration photograph; not a customer installation or evidence of site performance.

Separate three different reasons for a flat trace


First, flow may actually be steady and the instrument may be measuring normally. Second, an instrument may be substituting a retained value while its measurement is impaired. Third, a logger or display may be showing an old value because communications or collection stopped. Similar graphs can result from different mechanisms.


Start at the instrument rather than assuming a software fault. Compare the displayed number with the applicable measurement diagnostics, then compare that evidence with the receiver’s transaction history and timestamps. Record which observation comes from which layer. A successful register read can establish communications without establishing that the numerical value represents a new acoustic measurement.


Damping addresses response smoothing; a hold function addresses what value is presented under its specified condition. Reducing a damping time is therefore not a demonstrated remedy for an active hold policy. Equally, adjusting zero to make a retained nonzero value disappear can conceal the original problem and introduce another error.


Write an output-by-output acceptance record


List only the interfaces actually fitted and used: local display, analogue output, pulse output, digital communications, internal totaliser and exported record as applicable. For each, document the normal response, poor-signal response, available diagnostic indication and recovery response. Mark undocumented behaviour as unresolved.


Do not infer that every output follows the same policy. In particular, a statement about holding a flow value does not prove whether a particular totaliser continues accumulating, stops, or marks a diagnostic. Obtain the exact interface documentation and verify the behaviour required by the project before accepting calculated volumes.


  1. Preserve the current configuration and an unedited sample of the questionable trace, including units and timestamps. Record the hold-related setting before making any approved change.

  2. Agree a safe test method with the responsible technician. Use a suitable spare instrument, controlled test rig or manufacturer-supported simulation; do not drain a process pipe or disturb a live installation to create a fault.

  3. Establish normal measurement and record the corresponding diagnostics. Apply the approved test condition and observe the number, diagnostic state and timestamps together.

  4. Check each used output and the final record. For a simulated test of receiving software, identify the data as simulated; that test does not prove the field instrument’s behaviour.

  5. Restore the approved arrangement and verify recovery. Retain the observations, configuration revision and unresolved questions with the survey record.


Worked example: fresh messages carrying a retained number


Suppose a hypothetical receiver obtains 12 m³/h once a minute for ten minutes. The meter’s diagnostic history identifies five of those minutes as poor signal, and an authorised test establishes that the used interface retains the last good rate in that condition. The arrival timestamps are current, but the five affected rate values are not evidence of five fresh valid measurements.


Blindly integrating the retained 12 m³/h over those five minutes would add 1 m³ to a calculated volume. That is arithmetic based on a substituted rate, not independently measured volume. Preserve the interval and its qualification. Do not use the example to predict what the instrument’s own totaliser did; examine its documented and tested response separately.


Close the investigation before changing calibration


Avoid declaring stable pumping from an unchanging number, treating every successful poll as a valid measurement, or hiding a diagnostic interval by replacing it with zero. Where retained values are intentionally used, the receiving application needs an agreed interpretation and a visible qualification. There is no universal timeout or fault value suitable for every process.


For the next technical enquiry, provide the exact model and firmware, the relevant manual page, hold-setting evidence, diagnostics, a timestamped sample and the interface used. Ask ProSense to confirm the supplied configuration and test requirements. Suitability for ProSight Software or any control application requires separate verification; a temporary survey does not validate a protective function.


Need help with your application?


ProSense Instruments - explore instruments, sensors, data loggers and test equipment.


ProSense Solutions - discuss complete monitoring and automation systems.


ProSight Software - explore cloud dashboards, alarms and reporting. Device integration must be confirmed for your application.



Project enquiries: sales@prosense.com.au. Software enquiries: info@prosightsoftware.com.

Comments


bottom of page