What Is Transmitter Ranging?

Back to Blog

Lower and Upper Range Values

Every transmitter has a sensor with a wide overall capability, but you rarely use all of it. Ranging sets the lower range value - the process value that produces 4 mA - and the upper range value - the value that produces 20 mA. The difference between them is the span. A level transmitter with a sensor good for 0 to 100 inches might be ranged 10 to 60 inches so the useful part of the tank fills the whole 4-20 mA output.

Narrowing the range concentrates all 16 mA of output swing over a smaller process window, which improves resolution and reduces the reading error for a given percentage of span. This is why ranging is chosen to fit the actual operating range of the process point, not the sensor's full capability.

Turndown and Rangeability

You cannot narrow the range without limit. Turndown, or rangeability, is the ratio between the widest and narrowest span a transmitter can be ranged to while holding its accuracy specification - for example a 10:1 turndown on a 0-300 psi sensor allows spans down to 30 psi. Push the span narrower than the rated turndown and the transmitter's stated accuracy no longer holds, because its absolute error becomes a large fraction of the tiny span.

Smart transmitters publish accuracy as a function of turndown, and the accuracy degrades as you range them tighter. Choosing a sensor whose range comfortably matches the process, so the required span sits within the rated turndown, is a key part of correct instrument selection.

Ranging in the Field

On a smart or HART transmitter, ranging is a digital configuration done from a handheld communicator or asset-management software - you enter the lower and upper range values directly, without applying physical pressure. Re-ranging is common when a process changes: a new operating window, a different vessel, or a need for finer resolution. A loop check afterward confirms the new range reads correctly end to end.

Ranging is set in the field instrument, and the controller is scaled to match. A cloud SCADA such as Merobix reads the engineering-unit value the controller reports based on that range; it does not range the transmitter. The field ranging defines what the number means, and the SCADA displays and trends it.

A Worked Re-Ranging Example

Numbers make the resolution argument concrete. Say a pressure transmitter has a sensor capable of 0 to 1000 psi, but the separator it serves never operates above 300 psi. Left at the full 0 to 1000 range, the output for any process value follows the standard 4-20 mA mapping: current equals 4 mA plus 16 mA times the measured value divided by the span. At 150 psi that is 4 + 16 x (150 / 1000) = 6.4 mA, and a 10 psi process change moves the output by only 16 x (10 / 1000) = 0.16 mA.

Re-range the same transmitter to 0 to 300 psi and the same operating point sits at 4 + 16 x (150 / 300) = 12 mA, in the middle of the signal, and that same 10 psi change now moves the output 16 x (10 / 300), or about 0.53 mA - more than three times the signal movement for the same process movement. Every downstream consumer of the loop, from the analog input card to the trend display, resolves the process that much more finely. The arithmetic is nothing more than the 4-20 mA convention applied to two different spans, which is exactly why the ranging decision deserves a minute of deliberate thought instead of defaulting to the sensor's full capability.

Zero Suppression and Elevation

Ranging is not always a simple zero-to-something. On differential-pressure level measurements the transmitter often does not sit level with the bottom tap: mounted below the vessel, it sees a constant extra head of fluid in the impulse line, and with a wet reference leg it sees a constant negative offset. Ranging absorbs these offsets by shifting the lower range value away from zero - a suppressed-zero range starts above zero to cancel added head, and an elevated-zero range starts below zero, with a negative lower range value, to cancel a wet leg. The transmitter then reads true level even though the raw pressure it senses never crosses zero at an empty vessel.

The offsets are pure geometry and fluid density, so they are calculated per installation rather than looked up. Getting them wrong shows up as a level that reads plausibly but sits shifted across its whole range, which is why the working procedure in setting the 4-20 mA range on a level transmitter walks through the head calculation before any values are entered.

Ranging Is Not Calibration

The two get conflated because both involve a communicator and both end with the transmitter reading differently. They are separate operations. Ranging changes which process values map to 4 and 20 mA; it moves the goalposts but trusts the sensor's measurement. Calibration - more precisely, trim - corrects the measurement itself against a reference standard: a sensor trim aligns the transmitter's digital reading with a known applied input, and an output trim aligns the mA output with what the digital value says it should be. Re-ranging a transmitter whose sensor has drifted does not fix the drift; it just re-maps a wrong number onto a different span.

The practical rule: if the transmitter disagrees with a trusted reference, trim it, as described in trimming a transmitter with a HART communicator. If the process operating window changed, re-range it. If both apply, trim first against the reference and then range, so the new span is built on a corrected measurement.

After a Re-Range: Keeping the Rest of the Loop Honest

A re-range done only in the field instrument quietly breaks everything scaled to the old span. Before closing the work order:

1. Update the analog input scaling in the controller so raw counts convert to engineering units using the new lower and upper range values.
2. Review alarm and trip setpoints - setpoints defined in engineering units in the controller usually survive, but anything defined in raw counts or percent of span is now wrong.
3. Update the SCADA tag scaling and any calculations built on it.
4. Correct the loop sheet and instrument database so the next person finds the truth.
5. Run an end-to-end loop check to prove the displayed value tracks the process across the new range.

The failure mode this prevents is nasty precisely because it is quiet. If the transmitter moves from a wide span to a narrow one and the controller still divides by the old span, every reading downstream is scaled wrong by the ratio of the spans while looking perfectly healthy. Treat a re-range as a loop change under management of change, not an instrument tweak.

Frequently Asked Questions