TestBench.tools
GitHub

Measurement Accuracy Calculator

Turn an instrument’s ±(% of reading + % of range) spec into an absolute error.

Accuracy specification

±(0.0035 % of reading + 0.0005 % of range)

Uncertainty (±)
0.0002145 V
Interval
4.69979 … 4.70021 V
As % of reading
0.004564 %
As ppm of reading
45.64 ppm
Where the uncertainty comes from
TermContributionShare
0.0035 % of reading0.0001645 V
77 %
0.0005 % of rangedoes not shrink with the reading0.00005 V
23 %

Reading is 47 % of full scale. · terms cross over at 1.42857 V

Terms are added, not root-sum-squared, because a published accuracy specification is a single guaranteed limit of error rather than a set of independent random contributions. It also assumes the instrument is inside its stated calibration interval and temperature window.

This calculator turns a published instrument accuracy specification into the absolute uncertainty of one specific reading. Enter the reading, the range you were on, and the spec in whichever form your manual states it — % of reading, % of range, ppm, counts or digits, or a fixed offset — and it returns the ± value, the interval that implies, the error as a percentage of the reading, and a breakdown of how much each published term contributed. Reference: ±(0.0035 % of reading + 0.0005 % of range) at 4.7 V on a 10 V range is ±214.5 µV, or 0.00456 % of reading.

An accuracy spec is not one number

Almost every specification worth quoting has at least two terms, and they behave completely differently. The first is proportional to what you measured — % of reading, % rdg, ppm of reading, sometimes % of measured value. It tracks the signal: halve the reading and that error halves with it. The second is proportional to the range, or to the size of a display step, and it does not move at all when the reading changes. Manufacturers write it as % of range, % FS, ppm of range, counts, digits, or LSD.

The headline number in a marketing table is nearly always the first term alone. Quoting it as “the accuracy” is correct only near full scale, where the second term is a small share of the budget. Everywhere else it understates the error, and it understates it worst exactly where people trust it most: on a small signal read on a comfortable, generous range. Adding the terms up by hand is not difficult, which is precisely why it usually does not get done.

Because the units differ between the two halves of the expression, neither term can be compared to the other until both are converted into the unit you are actually measuring in. That conversion is what this tool does, and the breakdown it prints is the point of it: it shows in absolute volts, amps or ohms which half of the specification is in charge of your result.

Worked example — the same instrument, two readings

spec ±(0.0035 % of reading + 0.0005 % of range) · range 10 V

reading 4.7 V
  reading term 0.0035 % × 4.7 = 164.5 µV (77 %)
  range term   0.0005 % × 10  = 50.0 µV (23 %)
  total → ±214.5 µV · 4.6997855 … 4.7002145 V · 0.00456 % of reading

reading 0.1 V, same range
  reading term 0.0035 % × 0.1 = 3.5 µV (6.5 %)
  range term   0.0005 % × 10  = 50.0 µV (93.5 %)
  total → ±53.5 µV · 0.0535 % of reading

same 0.1 V moved to the 1 V range → ±8.5 µV · 0.0085 % of reading
  6.3× better, same meter, one button

Nothing about the instrument changed between those three lines. The 0.0035 % headline is honest at 4.7 V and off by a factor of fifteen at 0.1 V, and the fix is a range change, not a better meter.

The crossover reading

There is a single reading at which the two halves of a specification are exactly equal, and it is worth knowing because it divides the range into two regimes. Below it the fixed terms dominate and your error as a percentage of reading climbs steeply as the signal falls; above it the proportional term takes over and the percentage error settles down to roughly the headline figure. The calculator reports it for every spec you enter.

It is found by setting the two sides equal. With a % of reading term of a and a fixed part F (the range, counts and offset terms added together, already converted into measurement units), the terms cross at reading = F ÷ (a/100). For the example above that is 50 µV ÷ 0.000035 = 1.43 V on a 10 V range, so anything below about 14 % of full scale is in the regime where the range term is calling the shots.

Handheld meters land in a more uncomfortable place. A spec of ±(0.05 % + 3 counts) on a 6000-count meter puts three counts at 3 mV on the 6 V range, and 3 mV ÷ 0.0005 = 6 V — the crossover sits exactly at full scale. On that range the counts term is never the smaller of the two, no matter where in the range you read. That is not a defect; it is what a three-and-a-half to four-digit display costs, and knowing it stops you from chasing a specification the display cannot deliver.

Counts, digits and resolution

Counts terms are the ones most often left uncomputed, because the specification never tells you what a count is worth. It cannot: a count is one step of the least significant digit, and that step changes with every range. Three pieces of information will pin it down, and any one of them is enough.

The meter's rated count is the usual one — 2000, 4000, 6000, 20 000 — and one count is then the range divided by that number. A 6000-count meter on the 60 V range steps by 60 ÷ 6000 = 10 mV. The digit count works the same way with a different convention: n½ digits means n digits running 0 to 9 plus a leading digit that can only be 0 or 1, so the display resolves the nominal range into 10ⁿ steps and can over-range to 2·10ⁿ − 1 counts. A 5½-digit meter on the 10 V range steps by 100 µV and reads up to 19.9999 V. The third option is simply to read the resolution off the display: if the last digit is worth 0.001 V, enter 0.001 and skip the arithmetic.

Enter the nominal range, not the over-range ceiling. The 10 V range is 10 V even though the display will happily show 19.9999 V, and using 19.9999 as the range would inflate both the % of range term and the count size. The calculator prints the over-range ceiling separately so the two never get confused.

What the number is, and what it is not

The result is a limit of error. It is the band the manufacturer guarantees, and it comes with conditions attached that the specification page states and the specification line does not: a calibration interval (24 hour, 90 day and 1 year figures differ, sometimes by more than a factor of two), a temperature window around the calibration temperature with a separate coefficient outside it, a warm-up time, and frequently a minimum percentage of range below which a different row of the table applies. A number computed here inherits every one of those conditions. If the instrument is out of calibration, cold, or being used below its stated floor, the arithmetic is still right and the guarantee is gone.

It is also not, on its own, a measurement uncertainty in the sense of the GUM. To feed it into a formal budget you would treat a limit with no stated distribution as rectangular and divide by √3 to get a standard uncertainty, combine that in quadrature with your other independent contributions — reference standard, thermal emf, loading, repeatability — and then multiply by a coverage factor for the confidence level you need. This tool stops one step short of that on purpose, because the assumptions in that step belong to whoever is signing the certificate, not to a web page.

The one place the two views meet is the test uncertainty ratio. Calibration procedures commonly require the accuracy of the reference to be several times better than that of the unit under test — a 4:1 ratio is the usual threshold — and that comparison has to be made in absolute units at the actual test point, not between two headline percentages. Computing both instruments' specs at the same reading, on the ranges each one will actually be on, is the only honest way to check it.

Specification forms this calculator reads

ParameterValueNotes
% of readinga % × |reading|also % rdg, % of measured value
% of rangeb % × rangealso % FS, % of full scale
ppm of reading1 ppm = 1e-4 %calibrators, 8½-digit DMMs
ppm of range1 ppm = 1e-4 %same conversion
countsn × (range ÷ counts)also digits, LSD, d
digitsn½ → 10ⁿ stepsover-ranges to 2·10ⁿ − 1 counts
fixed offsetabsolute unitsa floor stated in V, A, Ω…
Combinationarithmetic sumnot RSS — see above

Manual entry is the primary mode: type the terms exactly as your manual prints them and leave empty any your spec does not have.

The instruments that are built in

Six DC voltage specifications are included as presets. Each one was read out of the manufacturer's own PDF, and each carries the document number, the revision date, and the conditions the figures are valid under, so a number on screen can always be traced back to a page in a manual. Only the 1-year column is included; the 24-hour, 90-day and 2-year columns, the temperature coefficients and the AC, resistance and current functions are all left to manual entry, because every additional column multiplies the transcription surface by the number of models and a preset holding the wrong row is worse than no preset at all.

ParameterValueNotes
Keysight 34461A±(0.0035 + 0.0005) at 10 V1 year, TCAL ± 5 °C · 5991-1983EN
Keysight 34401A±(0.0035 + 0.0005) at 10 V1 year, 23 ± 5 °C · 5968-0162EN
Keithley DMM6500±(0.0025 + 0.0005) at 10 V1 year, TCAL ± 5 °C · SPEC-DMM6500 Rev. A
Siglent SDM3055±(0.015 + 0.004) at 20 V1 year, 23 ± 5 °C · DataSheet-2021.05
Fluke 289±(0.025 % + 2 counts) at 5 V1 year, 18–28 °C · Users Manual Rev. 2
Fluke 87V±(0.05 % + 1 count) at 6 V1 year, 18–28 °C · 80 Series V Rev.2

Reading 4.7 V on each of those instruments, on the range each one would actually select, gives ±0.2145 mV, ±0.2145 mV, ±0.1675 mV, ±1.505 mV, ±1.375 mV and ±3.35 mV respectively — a twentyfold spread for the same measurement. Notice that the Siglent lands in the middle despite a % of reading term six times looser than the Keithley's: on the 20 V range its 0.004 % of range term contributes more than its reading term does, which is the small-value-on-a-large-range effect appearing purely because 4.7 V sits low in a 20 V range.

Handheld presets quote the resolution printed in the manual's own resolution column rather than dividing the range by a display count. The Fluke 289 manual, for instance, never prints a count figure at all; 50 000 counts can be derived from its ranges and resolutions, but a derived number is not a published one and does not belong in a preset table.

FAQ

What does ±(0.0035 % of reading + 0.0005 % of range) actually mean?

It means two errors are added. The first scales with what you measured: 0.0035 % of 4.7 V is 164.5 µV. The second scales with the range you are on and not with the reading at all: 0.0005 % of a 10 V range is 50 µV whether the meter shows 4.7 V or 0.1 V. The instrument is guaranteed to be inside ±214.5 µV of the true value at 4.7 V on that range, so the reading brackets 4.6997855 V to 4.7002145 V.

Why is my error so much worse when I measure a small voltage?

Because the second term does not shrink. On the 10 V range the range term is a fixed 50 µV, so at 4.7 V it is a quarter of the budget and at 0.1 V it is 93 % of it — the error rises from 0.0046 % of reading to 0.0535 %, an eleven-fold loss, with no change to the instrument. Moving the same 0.1 V measurement to the 1 V range cuts the range term by ten and the total uncertainty by about six. This is the single most common way engineers lose accuracy they already paid for.

What is a count, and how do I convert counts to volts?

A count is one step of the least significant digit on the display, so its size depends on the range. A 6000-count meter on its 6 V range shows up to 6.000 V, which is 6000 steps of 0.001 V, so one count is 1 mV and a '+3 counts' term is 3 mV. Give the calculator either the meter's rated count, its digit count, or the resolution read straight off the display, and it does that conversion for you. 'Digits', 'LSD' and 'd' in a specification all mean the same thing as counts.

How do 5½ digits relate to counts?

n½ digits means n digits that run 0 to 9 plus one leading digit limited to 0 or 1. So a 5½-digit meter resolves its nominal range into 10⁵ steps — 100 µV on the 10 V range — and can keep counting to 199 999 before it has to change range. Enter the nominal range, 10 V, not the 19.9999 V over-range ceiling; the calculator reports the ceiling separately because it is display capability, not resolution.

Should the terms be added or root-sum-squared?

Added. A published accuracy specification is a limit of error: the manufacturer asserts the instrument stays inside that band over the stated calibration interval and temperature window, and the band is the arithmetic sum of its terms. Root-sum-square is the right combination one level up, when you build an uncertainty budget out of several independent sources — meter, reference, fixturing, operator. Applying RSS inside one vendor expression quietly shrinks the manufacturer's own guarantee, so this calculator never does it.

Is this the same as measurement uncertainty in the GUM sense?

No, it is one input to it. The result here is a limit of error taken straight from the specification. To use it in a formal budget you normally treat a limit with no stated distribution as rectangular and divide by √3 to get a standard uncertainty, then combine it in quadrature with your other sources and multiply by a coverage factor. This tool deliberately stops before that step, because the division depends on assumptions only you can make.

Does the spec still apply if I am outside the calibration interval?

No. Accuracy specifications are always qualified — 24 hour, 90 day or 1 year since calibration, within a temperature window around the calibration temperature, after a stated warm-up, and often only above a minimum percentage of range. Outside any of those, the published numbers are not a guarantee and a temperature coefficient or a different table applies. Read the qualifier line under the table in your manual before trusting the number this calculator gives you.

Where do the instrument presets come from?

Six instruments are built in — Keysight 34461A and 34401A, Keithley DMM6500, Siglent SDM3055, Fluke 87V and Fluke 289 — and every figure was read out of the manufacturer's own PDF, not from memory or a secondary site. Each preset names the document number and revision it came from, and the tool shows the calibration interval and temperature window the numbers are valid under. Only DC voltage and only the 1-year column are included, because each extra column multiplies the chance of a transcription error. Everything else is typed in from your manual.

My instrument is not in the list. Is that a problem?

No — manual entry is the primary mode and the presets are a convenience. Type the terms exactly as your manual prints them: the percentage that goes with 'of reading', the one that goes with 'of range', the number of counts or digits, and any fixed offset. Leave a box empty if your spec does not have that term. A preset would only save you reading the same table you already have open.

Is my data uploaded?

No. Every calculation runs in your browser.

Related tools