For a device whose output rises in a straight line with the value it measures, you only need to pin down two points to define the whole line, and those two points are its zero and its span. A two-point calibration exploits exactly this geometry. This guide explains how a two-point calibration sets zero and span at the endpoints of the range, when two points are genuinely sufficient versus when a five-point check is needed to catch mid-scale nonlinearity, the step-by-step adjust procedure, and how the result is recorded in SCADA.
Two-Point Calibration (Zero & Span) in one line: A two-point calibration sets a linear instrument at just two references - one at the bottom of its range to fix the zero and one at the top to fix the span. Because a straight-line response is fully defined by two points, adjusting the device to read correctly at both endpoints makes it read correctly everywhere in between, assuming the response really is linear. It is the standard method for linear transmitters such as pressure, level, and temperature devices, and it is faster than a multi-point check while giving no information about mid-scale behavior.
Two numbers govern a linear instrument's calibration: the zero and the span. The zero, sometimes called the lower range value, is the input at which the output should sit at the bottom of its scale - for a transmitter with a 4 to 20 milliamp output, that is the input that should produce 4 milliamps. The span is the width of the input range that stretches the output across to its top value, so the upper range value plus the zero defines where the output should read 20 milliamps. Between those two anchors, a linear device draws a straight line, and geometry guarantees that a straight line is completely determined by any two of its points.
That is the entire justification for a two-point calibration. If you apply a known input at the low end and adjust until the output is exactly right, then apply a known input at the high end and adjust until that is exactly right, every point in between falls into place automatically - provided the device's underlying response is truly linear. Choosing the two points at or near the range endpoints is deliberate: the further apart they are, the more precisely they fix the slope of the line, so endpoint calibration gives the tightest control over the span. Points bunched near the middle would define the same line far less confidently.
The catch is the assumption of linearity itself. A two-point calibration verifies and corrects the endpoints but says nothing about what the device does at, say, half scale. If the instrument has developed a bow or an S-shape in its response, both endpoints can read perfectly while a mid-scale value is off. Two points cannot see that error because two points cannot describe a curve. This is why the method is appropriate for genuinely linear instruments and why anything suspected of nonlinearity needs more than two references.
The procedure is a disciplined loop of apply, read, and adjust. First, apply a stable, known input at the low end of the range using a reference source and record the device's output as found, before touching anything. Then adjust the zero until the output matches the intended low value. Next apply a known input at the high end, record the as-found output, and adjust the span until the output matches the intended high value. Because moving the span slightly disturbs the zero and vice versa on many devices, the technician repeats the low and high checks and trims each until both endpoints read correctly at once. Only then is the as-left condition recorded.
A five-point check follows the same apply-and-read idea but adds references at intermediate values - commonly at the low end, quarter, mid, three-quarter, and high points - and, importantly, it is often used to verify rather than to adjust. Its purpose is to expose nonlinearity that a two-point calibration is blind to: if the device reads correctly at the endpoints but deviates at mid-scale, the five-point check catches it while the two-point method would pass the device as good. The mid-scale points also reveal hysteresis when the check is run both up and down the range.
The choice between them comes down to the instrument and the stakes. A modern, inherently linear transmitter in a routine service is well served by a two-point calibration, which is quicker and disturbs the process less. A device known or suspected to be nonlinear, a critical or custody measurement where mid-scale errors carry real cost, or an instrument being characterized for the first time warrants the fuller five-point picture. Many programs use both: a five-point verification to prove linearity, then routine two-point calibrations once the device has demonstrated it stays straight.
A two-point calibration produces a compact but important record: the as-found and as-left readings at the zero and span points, the reference values applied, the equipment used, the date, and who performed it. Capturing that record is not paperwork for its own sake - the as-found readings are the raw material of drift analysis and interval decisions, since they show how far the device had wandered since its last calibration. A two-point calibration whose result is not recorded has verified the instrument but taught the program nothing.
When the results live in a cloud SCADA such as Merobix rather than on a loose certificate, they attach to the specific metering point or instrument tag, so each device accumulates a history of its zero and span behavior over time. Because the platform already knows the tag's range and configuration, the recorded endpoints can be checked against the expected values, and a device that keeps arriving with a growing zero offset or a shrinking span becomes visible as a trend rather than a series of isolated events.
For field operations this closes a practical gap. A technician calibrating a level transmitter on a remote tank can enter the two-point results against that tag, and the platform links the calibration to the same point the operator watches every day. The next scheduled calibration is driven from the same system, and the accumulated endpoint history feeds decisions about whether the device still merits a simple two-point check or has started to warrant closer scrutiny. The calibration and the live measurement it protects stay bound to one record.
Zero is the reference at the bottom of the instrument's range - the input that should produce the lowest output, such as 4 milliamps on a 4 to 20 milliamp transmitter. Span is the width of the input range that carries the output up to its highest value, fixing where the output should read at the top of scale. A two-point calibration sets both, so the instrument reads correctly at both endpoints and, if it is linear, everywhere in between.
Two points are sufficient when the instrument's response is genuinely linear, because a straight line is fully defined by any two of its points. Most modern pressure, level, and temperature transmitters in routine service qualify, and a two-point calibration is quicker and disturbs the process less. When a device is suspected of nonlinearity, or the measurement is critical enough that a mid-scale error would matter, a five-point check is warranted because two points cannot detect a curve.
No, and that is its main limitation. A two-point calibration only checks and adjusts the endpoints of the range, so a device with a bowed or S-shaped response can read perfectly at zero and span while being off at mid-scale. Detecting that kind of error requires additional reference points between the endpoints, which is exactly what a five-point verification provides.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.