How to Check Flow Computer Inputs Against Transmitter Outputs

Back to Blog

What You Need

Have the meter data sheet listing each transmitter's range and units, access to the flow computer's live-input and configuration screens, a loop calibrator for current injection, and the transmitters' local displays or a HART communicator. Familiarity with where these settings live, and how changes get logged, is covered in flow computer configuration and event log.

Compare Live Values Side by Side

With the process stable, read each variable in two places at once: the transmitter's display and the flow computer's live-input page. The values should agree closely, allowing for display resolution and a moment of process movement. Do all three variables even if only one is suspected, because a scaling error on any input biases the computed flow, and the comparison costs minutes.

Disagreement localizes the fault immediately: the transmitter display shows what the device measured, so a computer showing something else means the analog scaling, the digital mapping, or a unit conversion between them is wrong. Note the ratio or offset of the disagreement - a value wrong by a constant factor is a range or unit error, a constant offset points at an elevation or zero suppression setting, and the classification tells you which screen to open.

Verify Ranges, Units, and the Absolute-Pressure Trap

Walk the configuration on both sides: the transmitter's range must match the range the flow computer assumes for that analog input, and the units must match exactly - inches of water at a stated reference temperature versus kilopascals, degrees Fahrenheit versus Celsius. On pulse or digital inputs the same discipline applies to scaling factors. Where the transmitter is ranged differently from the computer's assumption, every reading is silently multiplied by the ratio of the ranges.

Give static pressure special attention: gas flow calculations per AGA-3 orifice metering use absolute pressure, while many transmitters measure gauge. Somewhere, exactly once, atmospheric pressure must be added - in the transmitter or in the computer's configuration, never both and never neither. Confirm which device does it and that the configured atmospheric value matches the site elevation, because a doubled or missing correction is a permanent bias on every calculated quantity.

Prove Each Channel with an Injected Signal

Live comparison proves today's operating point; injection proves the whole scale. With the meter run's values frozen or flagged per site measurement procedure, disconnect one input at a time and inject known signals - a calibrated current at several points for analog inputs, a known frequency for pulse inputs on turbine service as described in frequency-input turbine metering - and confirm the computer displays the engineering value each signal represents across the range.

Restore each connection and watch the live value return before moving to the next input. Record as-found and as-left for every channel; on custody measurement this record is what makes the check auditable rather than anecdotal, in line with API MPMS Chapter 21 practice for electronic measurement.

Verifying the Result and Common Mistakes

Close by confirming the computed flow itself is consistent: with all inputs verified, the flow computer's rate should sit where the meter's history and the process say it should. A verified-input meter that still computes a surprising rate has a calculation-configuration question - plate bore, meter constants, fluid properties - not an input question, and you have just cleanly excluded the inputs from the suspect list.

Common mistakes: checking only the suspect input and missing a second compensating error, verifying at a single point where two wrongs cancel, leaving the atmospheric-pressure addition configured in both devices, and skipping the event log afterward - the computer's own log should show your test signals, which is also how you confirm the log is actually capturing changes.

Frequently Asked Questions