Clamp-On Flow Surveys: Record Damping Before Comparing Pump Response
A portable clamp-on flow meter can make a pump look slow when the display itself is deliberately smoothed. Before comparing how quickly two pumps respond, record the instrument’s damping setting and the logging interval. A steady number helps with reading a settled operating point; it does not, by itself, prove that a short flow event has been captured faithfully.
Separate the three time scales
There are three different questions: how quickly the liquid flow changes, how the meter processes that change, and how often your record stores a value. Changing one does not necessarily change the others. A fast logger cannot reconstruct detail already removed by filtering. Equally, reducing damping cannot recover an event that occurred between widely spaced stored readings.
Start by defining the survey’s purpose. Comparing settled duty points needs a different recording plan from investigating a short fluctuation. Write down the shortest event you need to distinguish and the evidence you will use to recognise its start. A pump command timestamp identifies a command; it is not an independent measurement of the resulting flow.
ProSense’s ProSight handheld clamp-on flow meter is offered for portable surveys, commissioning and maintenance. Confirm the supplied instrument, transducer set and manual revision before planning a response test. Similar-looking handheld meters can have different menus, firmware and output behaviour.

What a manufacturer manual actually establishes
Holykell’s TUF-2000H manual provides a useful documented example. It identifies M40 as the flow-rate damping setting and explains that stronger damping steadies the reading while slowing its response. It separately identifies M51 for recording start time, interval and duration. These references describe that manual, not a verified firmware match for every ProSight-branded instrument. Check the exact supplied documentation before changing a setting.
The manual also distinguishes low-flow cut-off from damping. Cut-off can replace sufficiently small flow readings with zero; damping changes the response to variation. Treat them as separate settings in the survey record. A zero reading near a configured cut-off is a different diagnostic problem from a slowly moving display.
Do not convert a damping value into a guaranteed settling time or a percentage response unless the exact instrument documentation defines that relationship. Do not assume that the displayed flow, communications output, stored samples and totaliser all use the same processing path. Ask for confirmation when that distinction matters.
Build a repeatable comparison
1. Save the baseline. Record model, firmware where available, damping, cut-off, logging interval, units, clock setting and any logger averaging. Photograph the relevant screens. Preserve the original configuration so an authorised temporary change can be reversed.
2. Establish measurement quality first. Confirm pipe data, transducer arrangement and coupling against the supplied instructions. Record the available signal diagnostics before and during the observation. Smoothing is not a repair for a poor acoustic measurement, intermittent coupling or an unsuitable measurement location.
3. Choose an approved observation. Use normal operating events or a controlled test approved by the responsible team. Keep mounting and other configuration unchanged between comparisons. Do not abruptly stop pumps or move valves simply to create a sharp trace; process limits, personnel safety and equipment protection govern the test.
4. Change one authorised setting at a time. If a different damping setting is needed, use a value permitted by the exact manual. Record when it changed and allow the measurement to settle before evaluating a stable point. Keep event timestamps and measurement clocks aligned. Retain the original data rather than only a screenshot of the smoothest trace.
5. Report what was observed. Include configuration, signal conditions, observation window and limitations with each result. Restore the agreed operating configuration and document the restoration. If settings cannot be confirmed, report the response comparison as inconclusive.
A hypothetical survey decision
Suppose a team wants to investigate a five-second flow disturbance but stores one reading every 30 seconds. Even with no display damping, the saved record may miss that event. Increasing the storage frequency could help, but only after confirming the meter’s output update behaviour and any upstream filtering. This is a planning example, not a claimed performance result for the pictured product.
For a separate comparison of steady pump duty points, the same team might deliberately retain damping and use a longer stable observation window. Both approaches can be reasonable; their suitability depends on the question. They should not be mixed in one report without explaining the configuration difference.
Common mistakes and the next action
Avoid comparing yesterday’s heavily damped display with today’s differently configured logger, treating a flat trace as proof of stable flow, or calling a delayed indication a pump fault. Independent evidence is needed before attributing a measured delay to the process. A temporary survey is also not proof of suitability for a protective control function.
Before the survey, send ProSense the exact meter identification, pipe and liquid details, expected event duration, required output and proposed recording method. Request confirmation of damping and logging behaviour for that unit. That gives the team a defensible test plan and makes the eventual flow record easier to interpret.
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.
Instrument enquiries: sales@prosenseinstruments.com.au | 1800 560 854
Project enquiries: sales@prosense.com.au. Software enquiries: info@prosightsoftware.com.


Comments