Doppler Flow Meter: Data Output, Not Wi-Fi, Is Key

The Doppler flow meter shows flow and a running total on its panel, but nothing reaches the monthly report. Start here: Wi-Fi is not the missing measurement interface. The older Compuflow unit has no identified external output beyond its screen, so a Wi-Fi gateway has no signal to read.

Your first decision is whether the installed meter exposes usable data at terminals, a service connector, or an internal interface documented by the manufacturer. If it does not, replace or supplement the measurement device. Spending money on reporting software before establishing that signal path wastes time.

Check the meter output first

Inspect the manual, terminal diagram, nameplate, and configuration menus. Record the exact meter model before selecting hardware. Look for a pulse output, analog output, or documented digital communications interface. A connector alone proves nothing; it may be reserved for service.

Finding	Meaning	Next check
Only the local display is documented	No conventional gateway can acquire the reading directly	Check whether the manufacturer offers an output module; otherwise evaluate another flow instrument
Pulse output is available	A counter can accumulate volume using the documented volume-per-pulse factor	Verify pulse type, electrical rating, maximum frequency, and behavior after power loss
Analog output is available	A data logger can record instantaneous flow	Determine the documented signal range and scaling; calculate total volume in the logger
Documented digital output is available	A compatible gateway may read flow, total, status, and diagnostics	Match the physical layer, protocol, addressing, register definitions, and data format
An undocumented port is present	Its electrical and protocol characteristics are unknown	Request interface documentation from the manufacturer

Do not buy a generic serial-to-Wi-Fi adapter merely because the meter has a connector. The adapter cannot infer an undocumented protocol, register map, scaling factor, or checksum.

Decide whether the existing measurement is usable

An accessible signal does not prove the measurement suits the application. Confirm that the Doppler installation can measure the pumped flow in the available location before automating it.

1. Resolve whether the pipe is 6 inch or 8 inch. Entering the wrong internal diameter creates a systematic area error in any velocity-based flow calculation.
2. Verify the actual internal diameter rather than relying only on nominal pipe size. Pipe material, wall thickness, and lining affect flow area.
3. Confirm that the selected location maintains the hydraulic conditions required by the meter. Check pipe fill, sensor coupling or alignment, acoustic conditions, and disturbance from pumps, valves, bends, and the lagoon inlet.
4. Compare instantaneous flow with pump state. A stopped pump should not produce unexplained accumulated volume; a running pump should produce a stable, plausible reading.
5. Compare a measured operating interval against an independent volume reference when one is available. Use the result to expose diameter, scaling, installation, or zero-flow errors before regulatory reporting begins.

If the local total is already unreliable, transmitting it faster only creates a remote copy of bad data. Correct the sensing installation or select another measurement method before building the communications system.

Select the acquisition path from the signal

Choose the data logger only after identifying the output. The input must match both the signal type and its electrical characteristics.

For a pulse output, configure the logger from the documented pulse weight:

Total volume = pulse count × volume per pulse

Retain the counter across communication outages and controlled restarts. Decide how replacement, counter rollover, and reset events will be recorded so the monthly total remains auditable.

For an analog flow signal, convert each sample to engineering units using the meter's documented endpoints. Accumulate volume using the actual interval between samples:

Incremental volume = flow rate × elapsed time
Monthly volume = sum of incremental volumes

Keep time units consistent. If flow is expressed per minute, convert elapsed time to minutes before multiplication. Detect an input below or above the valid range instead of silently treating it as legitimate flow.

For digital communications, confirm byte order, signed or unsigned representation, unit multiplier, totalizer width, and reset behavior from the interface documentation. Reading the wrong address can still return a believable number.

Separate logging from Wi-Fi transport

Build two independent functions: acquire and retain the measurements locally, then transport records over Wi-Fi. A network outage must not erase flow that occurred during the outage.

1. Log timestamped flow, accumulated volume, device status, and communication quality locally.
2. Read rainfall and temperature through documented interfaces from the selected weather equipment. Do not assume consumer display data is externally accessible.
3. Store records in nonvolatile memory with enough capacity for the longest expected outage.
4. Transmit queued records when connectivity returns. Mark records as delivered only after the receiving system accepts them.
5. Protect configuration and reporting access with unique credentials and an encrypted transport supported by both endpoints.

Wi-Fi coverage at the lagoon is a separate reading. Test signal quality at the proposed antenna position with the enclosure closed and equipment operating. Also record whether internet service remains available there; joining a local access point does not prove that the logger can reach the reporting destination.

Define the monthly record before buying software

The state reporting obligation determines the data architecture. Obtain the required reporting interval, units, submission format, deadline, retention period, treatment of missing data, and acceptance criteria directly from the responsible agency. Automation may prepare a report, but it must not invent values for outages or invalid measurements.

At minimum, retain the opening total, closing total, calculated monthly volume, timestamps, units, invalid-data intervals, power interruptions, meter resets, and manual corrections. Monthly volume from a cumulative totalizer is:

Monthly volume = closing total − opening total

That subtraction works only when both readings use the same units and no undocumented reset or rollover occurred. Rainfall and temperature should remain separate timestamped channels; they do not repair a missing flow record.

Check whether the reporting destination accepts an automated upload, an emailed file, or only manual entry. A custom software package is unnecessary if a compatible logger can export the accepted format, but the acceptance format must be settled before hardware selection.

Commission the resolving branch

If the existing Compuflow has no documented output, the resolving branch is an output-equipped replacement or an independent measurement channel. Select it for the pipe, fluid, hydraulic condition, required accuracy, environmental exposure, power source, and one input type supported by the logger.

1. Record the old total and timestamp before changing equipment.
2. Install the measurement device at the qualified location ahead of the lagoon inlet.
3. Configure the actual pipe dimensions and documented output scaling.
4. Wire the signal to the matching logger input and prove signal isolation, polarity, pulse capture, or communications settings as applicable.
5. Run a controlled interval. Compare the instrument display, logger values, transmitted records, and receiving-system totals.
6. Disconnect Wi-Fi while flow continues, restore it, and verify that the missing interval uploads once without gaps or duplicates.
7. Cycle power under controlled conditions and verify timekeeping, configuration retention, totalizer continuity, and queued-data recovery.
8. Export a trial monthly report and check units, timestamps, totals, rainfall, temperature, exceptions, and file format against the agency's requirements.

Do not remove manual checks immediately. Run parallel readings until the remote total and local total agree across normal pump cycles and at least one communications interruption.

FAQ

Stop and escalate to official manufacturer support when the Compuflow interface, output scaling, connector function, or totalizer behavior is undocumented. Escalate to the responsible state agency when reporting units, outage handling, retention, or automated-submission acceptance remains unclear; do not place the remote system into regulatory service until those decisions are recorded.