Liquid Level Measurement and Volume Conversion: What Data Can Show

Liquid level measurement and volume conversion are different operations. A sensor locates the surface relative to a reference; a geometric relationship or calibrated table converts that level into volume. Estimating flow from changing volume adds further assumptions about time, inlet and outlet conditions. A value labelled “50%” is therefore incomplete unless the system states whether it means level span, total volume or usable capacity.

Keep the measured and calculated quantities separate

A hydrostatic sensor measures pressure that can be converted to head, while a radar or ultrasonic instrument derives distance to a surface. The installation then relates that result to the chosen level zero. None of these principles independently establishes the shape or capacity of a tank.

Record the physical level and calculated volume as separate fields where possible. If a volume result later changes after a tank-table update, the underlying level history can still be reviewed. Storing only a converted percentage can make it difficult to distinguish a measurement change from a configuration change.

Distance instruments need a level reference before a tank table

A top-mounted sensor may report the air gap. The volume table normally needs liquid height, so the gap first has to be related to the tank zero. Confirm whether the device or receiver already performs this conversion before applying it again in a platform.

A submerged pressure probe has a different reference issue: it measures head above its diaphragm. If the probe is raised for sediment clearance, the tank-floor level includes that offset. The selected density and pressure reference must also be appropriate before the calculated height is used in a capacity table.

Keep those installation corrections outside the tank geometry record where the system permits. Replacing or moving a sensor should not require changing the physical tank dimensions to force the display to match.

Constant-area tanks allow a simple calculation

For a vertical tank with a constant horizontal area A, geometric volume above the chosen floor is V = A × h. In an illustrative rectangular tank with area 6 m², a water height of 1.2 m represents 7.2 m³. A 0.01 m level change corresponds to 0.06 m³, or 60 L.

The example also shows why a level uncertainty matters to volume. Under that constant-area assumption, a 0.01 m height uncertainty contributes approximately 60 L of volume uncertainty. Tank dimensions, reference position and any calibration-table uncertainty contribute separately; they are not removed by displaying more decimal places.

Use actual internal dimensions and the correct floor or operating reference. A nominal tank size or external dimension may not describe the contained volume closely enough for a tight inventory requirement.

Half the level is not always half the volume

A horizontal cylindrical tank has a changing horizontal liquid area as it fills. A level-to-volume table or the appropriate segment geometry is needed. At one-quarter of its diameter, an ideal horizontal cylinder contains about 19.6% of its full volume, not 25%. This figure excludes end-shape and fitting effects.

A conical lower section, sloping floor or irregular sump creates similar nonlinearity. If a calibration table is used, confirm its units, zero, applicable tank identity and interpolation method. Test the points where the geometry changes rather than checking only empty and full endpoints.

Do not extrapolate beyond the validated table range without an approved basis. A sensor may continue to report a valid level while the volume calculation has reached an undefined part of the tank geometry.

Define usable capacity instead of relabelling total volume

Water below an outlet or minimum operating level may not be available to the process. Space above a normal high-level limit may be reserved for operating headroom. Usable capacity therefore depends on the defined low and high limits, not just the tank's physical maximum.

For a hypothetical constant-area tank of 6 m² with usable limits of 0.3 m and 1.8 m, the usable capacity between those limits is 9 m³. At 1.2 m, the available volume above the lower limit is 5.4 m³, or 60% of that usable interval. That is different from the gross volume of 7.2 m³ above the floor.

The low limit must come from the operating requirements, including any pump submergence or process reserve. It should not be invented to make a percentage display convenient. Show the level and basis of the percentage alongside the capacity value.

Use volume change for net accumulation, not assumed consumption

If storage falls from 7.2 m³ to 6.0 m³ in ten minutes, the average net loss is 1.2 m³ per ten minutes, equivalent to 7.2 m³/h. It is not necessarily the outlet flow. Simultaneous inflow, a bypass or another transfer changes the relationship.

For short intervals, small level fluctuations can dominate the difference between two readings. An unsuitable smoothing or time interval can either amplify noise or hide a real change. Choose the interval and reference method for the question being investigated and preserve the original observations.

For a river or open channel, tank geometry is not a substitute for a stage-discharge relationship. Backwater and changing section conditions can make stage alone insufficient. A combined radar flow instrument uses additional velocity and section information; it should not be described as an ordinary level sensor directly measuring flow.

Assign the calculation to one part of the system

A NiuBoL NBL-L-WLPS RS485 probe supplies hydrostatic measurement data to a compatible receiver. A separate controller, logger or platform may handle tank conversion if that function is supported and configured. Do not assume that a general Modbus output includes a tank table or totalizer.

Identify which component applies the datum offset, density conversion and volume relationship. Check the raw quantity and final display for several known levels. Applying the same offset in both the device and PLC, or applying a tank table to an already converted value, can produce a plausible but incorrect result.

For a NiuBoL project enquiry, provide the tank drawing or calibration table, expected liquid conditions and the required reported quantities. State whether the receiving system needs metres, litres, percent usable capacity or a net storage-change rate. That allows the sensor and calculation scope to be assessed separately.

Project Decision FAQ

Q1. Does a level sensor directly measure tank volume?

Usually not. It measures a physical quantity related to surface position. Volume requires the relevant geometry or tank calibration relationship after the reading is converted to the correct level reference.

Q2. Is 50% level always 50% capacity?

No. The relationship depends on tank shape and the percentage definition. Even where half-height coincides with half-volume for a symmetric tank, other fractions may not match. Usable-capacity percentages also depend on operating limits.

Q3. Can a tank table compensate an incorrectly mounted sensor?

It should not be used to hide an installation-reference error. Correct the sensor datum or offset first, then apply the table to the physical level quantity for which it was created.

Q4. Can consumption be calculated from two level readings?

Only under understood conditions and with a valid volume conversion. The difference gives net storage change. Unknown simultaneous inflows or transfers prevent it from identifying consumption alone.

Q5. Does Modbus RTU include the volume formula?

No. Modbus carries defined device values. A volume calculation is a separate supported function in the instrument or receiving system. Check the actual register meaning before choosing where to perform it.

Q6. What should an acceptance test include?

Check the physical reference, raw level, intermediate conversions and final volume at representative levels. Include geometry changes and usable limits. Retain the tank-table version and units with the results.

Summary

Liquid level, stored volume and flow are related but distinct quantities. Preserve the level reference, use an appropriate geometry relationship and state any assumptions behind a storage-change calculation. A clear definition of each result prevents a detailed dashboard from reporting more than the measurements can support.