123 Main Street, New York, NY 10001

Classic 3-Op-Amp Instrumentation Amplifier (INA)

← Back to:Instrumentation Amplifiers (INA)

Classic 3-op-amp instrumentation amplifiers are the go-to front end for bridge sensors because they keep input loading low and maintain real-world CMRR even when cable/lead resistance and wiring symmetry are imperfect. This page shows how to set gain with one resistor, protect and bias the inputs, plan CM/REF/headroom, and verify stability/noise with repeatable checks that translate directly into weighing/pressure resolution.

What a Classic 3-Op-Amp INA Is (and Is Not)

Decision: when this architecture is the “right default”

A classic 3-op-amp instrumentation amplifier (INA) is a differential front-end that delivers high input impedance, gain largely set by one external resistor, and high CMRR that remains more robust when the two input source impedances are not perfectly matched. It is a strong default for bridge sensors where a tiny differential signal rides on a large, noisy common-mode environment.

Mechanism: what problem it solves in real wiring
1) Tiny bridge signal without loading the sensor

Bridge outputs are commonly specified in mV/V. High input impedance keeps the bridge transfer function intact and prevents the front-end from becoming a hidden “shunt” that changes sensitivity and linearity.

2) Common-mode noise and ground movement

Long leads and industrial grounds inject common-mode disturbances (mains pickup, ground bounce, RF). The 3-op-amp structure targets rejection of that common-mode content before it becomes a false differential reading.

3) Source-impedance mismatch immunity (field reality)

Cable resistance, connector contact variation, and bridge imbalance make Rs+ and Rs− unequal. That imbalance converts common-mode interference into differential error (CM→DM conversion). Classic 3-op-amp INAs tend to remain more tolerant of this mismatch than simpler topologies.

Verify: quick checks that confirm the “bridge + wiring” failure mode
  • Touch / move cable test: if readings jump when the cable is moved, suspect CM pickup + CM→DM conversion (wiring asymmetry, shielding termination, leakage paths).
  • Lead resistance symmetry: measure each lead (or connector contact) DC resistance; large asymmetry often correlates with apparent “poor CMRR” in the field.
  • Common-mode step probe: inject a controlled common-mode disturbance (e.g., capacitively couple a small square-wave to both leads together) and observe if a differential output appears; a differential response indicates conversion mechanisms outside the ideal model.
Not the right choice when…
  • Ultra-low drift dominates: minute/hour stability pushes toward zero-drift/chopper INAs (architecture-specific ripple and demodulation artifacts belong to that page).
  • Very fast dynamics matter: wide bandwidth, high slew, and fast overload recovery push toward high-speed / low-latency INAs.
  • Very high common-mode voltage or isolation is required: bus/high-side or reinforced isolation pushes toward high-voltage / isolated INA solutions.
Scope guard (stay inside this page boundary)

This page focuses on the classic 3-op-amp topology: signal flow, gain-by-one-resistor intuition, real-world CMRR under source mismatch, input bias/leakage implications, and bridge-friendly wiring hooks. Detailed content for 2-op-amp INA behavior, chopper ripple mechanisms, PGA switching/mux, IEC surge/ESD network sizing, and full ADC-drive/AAF design belongs to their dedicated sibling pages.

Problem to solution map for bridge sensors using a classic 3-op-amp INA Block diagram showing a bridge sensor with long leads feeding a 3-op-amp INA and then an ADC or MCU. Tags highlight high CMRR, single-resistor gain, and high input impedance. Bridge Sensor Classic 3-Op-Amp INA A1 A2 Diff RG ADC/MCU Codes High CMRR High-Z Input Single-R Gain Bridge mV/V + noisy wiring → amplify DM, reject CM, stay tolerant to mismatch.

Topology Deep Dive: Three-Amplifier Signal Flow

Decision: what must be true for “high CMRR” to be real

The classic 3-op-amp INA achieves strong common-mode rejection only when the two input paths remain symmetric and the internal/feedback networks maintain matching. In practice, the most common CMRR failures are caused by external imbalance (lead resistance, connector contact, leakage paths), not by the idealized topology itself.

Mechanism: how the three amplifiers separate “DM gain” from “CM rejection”
Stage 1 (A1, A2): high input impedance + controlled front-end gain

A1 and A2 buffer each input with very small input current demand, so the bridge is not “loaded” by the amplifier. The external RG primarily sets how much differential component is developed between the two stage-1 outputs. High input impedance reduces sensor loading, but it also means bias current and leakage paths become dominant error sources when source impedance is high.

Stage 2 (Diff Amp): subtract stage-1 outputs to reject common-mode

The final differential amplifier subtracts the two stage-1 outputs. If both paths respond equally to common-mode changes, those common-mode components cancel during subtraction. Any path mismatch turns a portion of common-mode into a false differential signal (CM→DM conversion).

Where it breaks first (the three most common “first failures”)
  • Input-stage window violation: input common-mode or differential swing pushes A1/A2 out of linear range, creating distortion or clipping before the diff stage can cancel CM.
  • Output headroom / load stress: near-rail swing limits or capacitive loads cause nonlinearity, ringing, or slow settling that looks like “mysterious drift.”
  • Overload recovery: cable plug events, ESD clamps, or large transients saturate internal nodes; recovery time becomes a hidden latency and can dominate measurement stability.
Verify: simple tests that map symptoms to the internal stages
  • Stage saturation check: sweep input common-mode while keeping differential near zero; if output suddenly bends or clips, the system is hitting an input/output window limit rather than a “CMRR spec issue.”
  • CM injection symmetry check: apply the same coupled interference to both leads; a nonzero differential output indicates mismatch/leakage conversion mechanisms outside the ideal cancel model.
  • Overload recovery timing: apply a controlled step/plug-like transient and measure time-to-within-band; recovery time is often the real bottleneck for stable readings after disturbances.
Scope guard

This section builds the signal-flow model and the conditions for cancellation. Detailed frequency-dependent CMRR modeling, chopper modulation artifacts, IEC transient compliance networks, and full ADC-drive/AAF design are intentionally out of scope here.

Three-amplifier signal flow in a classic 3-op-amp INA Diagram showing A1 and A2 front-end amplifiers feeding a differential amplifier. Differential signal is highlighted in blue, common-mode in gray, with visual cancellation at the subtract stage. VIN+ / VIN− CM A1 A2 RG Diff Amp CM cancels* OUT DM path (signal) CM path (disturbance) *Only if input paths stay symmetric.

Gain Set by One Resistor: What It Really Controls

Decision: pick gain from an end-to-end mapping, then derive RG

Gain should be chosen by mapping the sensor’s full-scale differential output into the ADC’s usable input range with headroom for offsets and transients. Once the target gain is defined, RG becomes the gain “set knob” in the classic 3-op-amp INA. Most devices use a simple relationship of the form G ≈ 1 + K/RG (where K is set by the internal resistor network), so a smaller RG generally increases gain.

Mechanism: RG controls more than gain (accuracy, speed, recovery)
1) Gain setpoint vs gain accuracy

RG primarily sets the gain target, but gain accuracy is the combination of RG tolerance, RG tempco, and the INA’s internal network matching. A tight RG does not guarantee tight system gain if internal matching, temperature gradients, or leakage paths dominate in the field.

2) Bandwidth and phase margin (why high gain often “slows down”)

Higher gain usually reduces small-signal bandwidth and can reduce stability margin when real-world parasitics appear (cable capacitance, input RC, protection networks). If the measurement needs fast settling, gain selection must be checked against step response, not only against a headline bandwidth number.

3) Overload and recovery (the hidden latency at high gain)

High gain makes it easier for internal nodes to saturate during plug events, ESD clamp action, or large common-mode disturbances. Once saturated, the INA may show a long “tail” while internal stages recover, which appears as delayed stability after disturbances.

4) Leakage and humidity: the gain drift that RG never explains on paper

RG is often connected to high-impedance nodes. Flux residue, contamination films, and humidity can create a parallel leakage path that effectively changes RG. If gain drift correlates with cleaning, coating, or moisture exposure, the dominant mechanism is usually leakage rather than resistor tempco.

Verify: isolate the cause of “wrong gain” before changing parts
Case A — gain error is constant at room temperature
  • Quick check: measure RG in-circuit (or lift one side) and compare to BOM value.
  • Interpretation: if RG is correct but gain is not, suspect internal network tolerance, wiring mistakes, or output loading effects.
  • Minimal fix: confirm RG value/placement, then remove unexpected parallel paths (test points, contamination, solder bridges).
Case B — gain changes with temperature or humidity
  • Quick check: compare drift before/after cleaning, drying, or conformal coating.
  • Interpretation: a strong moisture correlation points to leakage across high-impedance RG nodes or input protection paths.
  • Minimal fix: shorten high-impedance traces, improve cleaning/coating, and keep RG away from contamination-prone areas.
Case C — higher gain causes slow settling or post-event “tails”
  • Quick check: observe a step or plug-like event and measure time-to-within-band of the output.
  • Interpretation: long recovery indicates internal saturation or reduced stability margin under real parasitics.
  • Minimal fix: add headroom, reduce gain, or adjust input/output networks that increase phase shift (details belong to the dynamics section).
Scope guard

This section explains how RG influences gain, gain error/drift, bandwidth, and overload recovery inside a classic 3-op-amp INA. Full ADC-drive/anti-alias network design and detailed stability compensation belong to the later dynamics and co-design sections.

RG parameter map for a classic 3-op-amp INA Centered RG block with arrows showing gain increase and bandwidth and recovery reduction, plus error source blocks for tolerance, tempco, leakage and load effects. RG Gain ↑ BW ↓ Recovery ↓ Error Sources Tolerance Tempco Leakage Load / Headroom RG sets gain, but accuracy, speed, and recovery are constrained by tolerance, tempco, leakage, and load headroom.

Real-World CMRR: Why 3-Op-Amp Is More Mismatch-Tolerant

Decision: when to suspect external imbalance before blaming the datasheet

If apparent “CMRR” collapses when cables move, connectors warm up, or humidity changes, the dominant mechanism is usually external imbalance that converts common-mode disturbance into differential error (CM→DM conversion), not the INA core itself.

Mechanism: ideal cancellation vs real wiring conversion
Ideal model (what the datasheet assumes)

In the ideal model, both inputs see the same common-mode disturbance through perfectly symmetric paths. The INA amplifies the differential component and cancels the common-mode component during subtraction.

Real wiring (what bridges actually look like)

Cable lead resistance, connector contact variation, and bridge imbalance create Rs+ ≠ Rs−. That asymmetry makes the two inputs respond differently to the same common-mode disturbance, producing an effective differential error (CM→DM conversion) that looks like “poor CMRR.”

One-line comparison (do not expand here)

2-op-amp INA topologies are typically more sensitive to source-impedance matching; classic 3-op-amp INAs often remain more tolerant in bridges because input loading is better isolated.

Verify: three quick experiments that identify mismatch-dominated CMRR collapse
Test 1 — swap the input leads (sign flip check)
  • Action: swap VIN+ and VIN− (or swap the two bridge sense leads).
  • Observe: does the error change sign while magnitude stays similar?
  • Interpret: a sign flip strongly indicates external conversion mechanisms rather than a fixed internal offset.
Test 2 — common-mode injection (does CM create DM?)
  • Action: couple the same small disturbance into both leads together (capacitive coupling is enough).
  • Observe: is there a measurable differential output response?
  • Interpret: a differential response indicates CM→DM conversion driven by asymmetry/leakage/shield termination.
Test 3 — deliberate ΔR asymmetry (linearity check)
  • Action: temporarily add a small series resistance to only one input lead.
  • Observe: does the error change roughly proportionally with ΔR?
  • Interpret: proportional behavior indicates mismatch-dominated performance; non-proportional drift points toward leakage or headroom issues.
Fix direction: lowest-cost actions first
  1. Restore symmetry: keep input pair routing and connector paths matched; eliminate one-sided series parts and uneven contact resistance.
  2. Control leakage: clean residues, shorten high-impedance nodes, and prevent moisture films that create parallel paths.
  3. Stabilize shielding strategy: use a consistent shield termination method for the installation (details belong to the protection/immunity page).
  4. Only then change the INA: if mismatch/leakage is controlled and CMRR is still insufficient, upgrade core specs or move to specialized parts.
Scope guard

This section focuses on real-world CMRR collapse from source-impedance mismatch, lead resistance variation, and bridge imbalance. Full EMI/IEC network sizing and shield-grounding design rules belong to the protection and immunity page.

Source-impedance mismatch causing apparent CMRR collapse Vin+ and Vin- each include a series resistance Rs+ and Rs-. A common-mode disturbance couples into both leads. When Rs+ differs from Rs-, an effective differential error appears at the INA input, shown as CM to DM conversion. Bridge / Leads Rs+ Rs− Rs+ ≠ Rs− CM noise INA Input VIN+ VIN− DM error CM→DM Lead R / Connector / Imbalance External asymmetry makes CM disturbances look like a differential signal, dominating “real” CMRR in the field.

Input Stage Engineering: Bias Current, Leakage, Protection Side-Effects

Decision: classify the symptom before changing the INA

Input-stage errors are usually driven by “invisible currents.” The same board can appear perfect on a bench yet fail in the field because bias current, leakage, and protection networks convert wiring realities into offset, drift, or long settling tails. Treat the symptom as one of these three buckets: offset shift, drift with temperature/humidity, or settling tail after events.

Mechanism: translate hidden currents into an error budget (Verror ≈ I × R)
1) Input bias current × source impedance → offset error

Any input bias current flowing through source resistance produces an input-referred error: Verror ≈ Ib × Rsource. In bridges and long-lead systems, Rs+ and Rs− are rarely identical, so the two input currents create an effective differential offset even when the sensor is “at zero.” If the error scales when source resistance is increased, bias/leakage currents are the dominant mechanism.

2) Protection parts leak, and leakage is temperature dependent

Clamp diodes, TVS devices, and even “harmless” input networks can introduce leakage current that changes with temperature and bias conditions. The same budget rule applies: Verror ≈ Ileak × Rsource. In practice, leakage is often asymmetric (one input sees a different bias or contamination path), which converts common-mode disturbances into differential error.

3) “High input impedance” is not infinite: humidity films create parallel paths

Flux residue, dust, and moisture can form a conductive film across high-impedance nodes. That film behaves like a parallel resistance and creates an effective leakage current path to ground or rails. If offset or gain changes after cleaning, drying, or conformal coating, the dominant mechanism is typically contamination-driven leakage rather than the INA’s core specs.

4) Input capacitance + long cables → transient currents, ringing, and tails

Even with tiny DC input current, any voltage step or common-mode disturbance drives transient current through input and cable capacitance. That current can create ringing or a long settling tail, especially when combined with series resistance and protection networks. A stable “DC” reading can still be corrupted immediately after plug events, cable motion, or common-mode steps.

Verify: three fast experiments to separate core specs from board leakage
Test 1 — short the differential input (leakage vs downstream)
  • Action: short VIN+ and VIN− together at the connector or closest entry point.
  • Observe: does the output still drift or jump?
  • Interpret: persistent drift suggests REF/output/headroom issues; large improvement suggests input leakage or wiring conversion.
Test 2 — dry/clean comparison (humidity film signature)
  • Action: compare readings before/after controlled drying or cleaning (repeatable procedure).
  • Observe: does offset or drift change noticeably?
  • Interpret: strong sensitivity indicates contamination-driven leakage across high-impedance nodes and protection parts.
Test 3 — deliberate source resistance change (I×R linearity check)
  • Action: add a known series resistance on one lead or swap to a higher source impedance.
  • Observe: does the error scale roughly with added resistance?
  • Interpret: scaling behavior points to bias/leakage currents as the dominant error mechanism.
Scope guard

This section explains bias/leakage mechanisms and their side-effects on offset, drift, and settling tails. IEC transient levels and full protection-network sizing belong to the protection and immunity page.

Leakage budget paths at the INA input stage Block diagram of VIN+ and VIN- entering protection elements (series resistor, RC, clamp diodes, TVS) with leakage arrows to AVDD and GND. Output symptom tags show offset shift, drift with temperature, and settling tail. AVDD GND VIN+ VIN− R R RC C R Clamp TVS Leakage Offset shift Drift (temp) Settling tail Model input errors as Verror ≈ I × R, then check leakage paths and transient currents through cable capacitance.

Input CM Range, REF Pin, and Output Headroom Planning

Decision: treat common-mode and headroom as one “valid window”

In single-supply bridge systems, many “mystery” problems are window violations: the input common-mode leaves the valid region or the output swing hits headroom limits. Either violation can look like drift, distortion, or poor rejection. The correct approach is to check a combined CM window + output swing window for the chosen gain and reference offset.

Mechanism: the CM range is not a single number; it depends on gain and output level
1) Input CM “window” shrinks when headroom is consumed

Internal stages require voltage headroom from the supply rails. Higher gain and larger output swings consume that headroom and can reduce the usable input common-mode region. As a result, the valid CM region must be checked at the intended gain and output bias, not as a standalone spec.

2) REF pin sets the output center and protects headroom

The REF pin shifts the output baseline so the amplified differential signal swings around a chosen center (often the ADC midscale). A well-chosen REF keeps the output away from rails and preserves linearity. A poorly chosen REF pushes the output into headroom limits and creates distortion or clipping during transients.

3) Output load and near-rail behavior set real distortion and settling

The usable output swing is affected by load conditions. Driving an ADC input network or a filter can pull the output toward stability limits and can increase settling time. Near-rail operation often collapses linearity first, even if the output appears to “fit” within the voltage range.

4) Overload and recovery become a production metric

Bridge startup imbalance, plug events, and shocks can saturate internal nodes or push the output into rails. The important metric is time-to-within-band after a defined disturbance. If recovery time is long, “stable readings” will be delayed even when noise density looks excellent.

Verify: quick checks that expose window violations
Check 1 — sweep input common-mode while holding differential near zero

If the output bends, clips, or becomes nonlinear at certain CM levels, the system is leaving the valid CM region. This is a window problem, not a “CMRR spec” problem.

Check 2 — adjust REF center and watch headroom margin

Move REF to re-center the output. If distortion or clipping disappears with a better center, headroom was the limiting factor. Ensure REF is low-impedance and quiet to avoid injecting baseline noise.

Check 3 — define a disturbance and measure time-to-within-band

Apply a repeatable plug/step event and measure recovery time to a defined tolerance band. Long recovery indicates overload or rail hits and must be handled by gain/headroom/REF planning.

Scope guard

This section focuses on CM window, REF usage, and output headroom planning for single-supply bridge systems. Detailed ADC-drive/AAF compensation belongs to the co-design and dynamics sections.

Common-mode window and output headroom planning with REF A simplified window diagram showing valid common-mode region, output swing limits near rails, and REF setting the output center within the allowed region. AVDD GND Valid CM region Headroom Headroom REF OUT swing CM Output limits Valid window REF centers Plan a valid CM + OUT window at the target gain, then place REF to keep headroom and recovery margin.

Noise & Drift: Turning Datasheet Numbers into Bridge Resolution

Vocabulary: three datasheet numbers map to three user experiences
Noise density (nV/√Hz) → short-term jitter

Noise density predicts how much the reading “moves” over short time windows. Wider measurement bandwidth integrates more noise, so the apparent jitter increases even when the sensor is perfectly static.

0.1–10 Hz noise (µVpp) → low-frequency stability

This number is a practical predictor for “minute-scale stability” in weighing and pressure measurement. A design can have excellent wideband density yet still look unstable at low frequency if the 1/f region dominates the operating band.

Offset & drift (µV, nV/°C) → thermal/long-term movement

Offset is the baseline error at a given condition; drift describes how that baseline changes with temperature. In bridges, drift often appears as slow movement after warm-up, airflow changes, or temperature gradients across the PCB.

Why 1/f corner matters: wideband specs do not guarantee low-frequency steadiness
Low-frequency bridges operate in a narrow band

Many weighing/pressure systems only need a few Hz of signal bandwidth. In that region, 1/f noise can dominate the integrated noise. A “great” noise density number can still lead to an unstable readout if the low-frequency region is not controlled.

Practical takeaway: use the right metric for the right time scale

Use noise density to predict short-window jitter, and use 0.1–10 Hz noise to predict low-frequency stability. Use offset drift to predict thermal movement across minutes to hours.

Mapping workflow: convert INA noise into bridge resolution (g / Pa)
Step 1 — input-referred noise → input noise within the measurement band
  • Wideband jitter: integrate noise density across the effective bandwidth (set by analog + digital filtering).
  • Low-frequency stability: use the 0.1–10 Hz number as a stability predictor if the signal bandwidth lives in that region.
Step 2 — apply gain: input noise → output noise

Output noise is the input-referred noise scaled by gain. If headroom is violated, additional distortion and tails can appear and must be fixed as a window problem.

Step 3 — output volts → ADC codes (or LSB fractions)

Convert output noise voltage into ADC code noise using the ADC input range and LSB size. This creates a consistent “code jitter” representation for both wideband and low-frequency behavior.

Step 4 — ADC codes → physical units using sensor sensitivity and excitation

Bridge sensitivity (mV/V) and excitation voltage convert volts into physical units. Once the chain is in volts or codes, the final step is a direct scaling into g or Pa, giving a resolution number that matches the user’s expectation.

When to consider zero-drift (decision rules only)
  • If 0.1–10 Hz noise mapped into physical units exceeds the stability target, low-frequency noise is the limiter.
  • If drift mapped into physical units exceeds the thermal stability target, temperature movement is the limiter.
  • If humidity/cleaning strongly changes the result, leakage and gradients must be fixed before changing architecture.
Noise mapping chain from INA input noise to bridge resolution Block diagram showing input-referred noise through output noise and ADC codes to physical units, with LF and WB tags and a sensor sensitivity block. Input noise INA (RTI) Output noise ADC codes g / Pa Resolution LF 0.1–10 Hz WB density Sensitivity Map RTI noise to output, convert to ADC codes, then scale by bridge sensitivity into g / Pa.

Bandwidth, Step Response, and Stability with Real Sensors and Cables

Constraint: gain increases reduce bandwidth, which shows up as settling time

In a classic 3-op-amp INA, higher gain typically reduces usable bandwidth. In weighing and pressure systems, the key performance metric is not “bandwidth” alone, but time-to-within-band for real step-like events such as load changes, cable motion, and plug disturbances.

Two failure modes: small-signal ringing vs large-signal tails
Small-signal stability: phase margin loss → ringing or persistent jitter

Cable capacitance and input RC networks add phase shift and can reduce stability margin. The result is overshoot and ringing, or a “never quite settled” jittery output even when the sensor is static.

Large-signal dynamics: slew / saturation / recovery → long settling tails

Plug events, shocks, or bridge imbalance can push internal nodes into saturation or drive the output into headroom limits. The waveform may show a long single-direction tail while stages recover, even if small-signal stability looks fine.

Input RC / RFI filtering: suppress RF without breaking settling and stability
Principle 1 — keep the differential input path symmetric

Asymmetry converts common-mode disturbances into differential error. Use matched series elements and matched shunt capacitors when filtering both inputs.

Principle 2 — cable capacitance multiplies the effect of series resistance

A long cable adds capacitance. Series resistance and total capacitance create poles that slow steps and can reduce phase margin. If “adding RC” makes the output worse, the cable is often the missing capacitor in the model.

Principle 3 — separate stability issues from headroom/recovery issues

Ringing indicates stability margin loss; long tails indicate overload recovery or headroom violation. Fixing the wrong mechanism (for example, only changing RC values) can hide the true limiter and waste iterations.

Symptom → priority debug path (fast triage)
Ringing / overshoot

First check cable capacitance, input RC symmetry, and output load. Ringing is usually a phase margin problem.

Slow settling tail after plug/step

First check headroom and REF centering, then check clamp action and overload recovery. A tail is usually a large-signal recovery problem.

Touching the cable changes the reading

First check asymmetry and leakage paths at the input. Cable motion often changes coupling and leakage, creating CM→DM conversion.

“RC made it worse”

Check whether added series resistance increased I×R errors (bias/leakage), or whether the cable capacitance shifted poles into an unstable region. Then re-evaluate the combined CM + OUT window to ensure recovery margin.

Scope guard

This section covers INA-side principles for cables, RC networks, and stability/settling behaviors. IEC transient levels and detailed network sizing belong to the protection and immunity page.

Cable capacitance, RC filtering, and INA stability outcomes Block diagram with cable capacitance, series resistor, filter capacitor, and INA input. On the right, small waveforms illustrate ringing versus settled response. Cable C Rseries Cfilter INA Input OUT Response Ringing Settled Phase margin Settling Overload Cable C plus RC can reduce phase margin (ringing) or increase recovery/settling time (tails).

Layout & Wiring for Bridges: Kelvin, Sense Routing, and Thermal Gradients

Bridge wiring blueprint: separate excitation, sense, and signal responsibilities
Excitation delivers power; sense measures the true bridge voltage at the load

In real harnesses, lead resistance and connector contact resistance change with temperature and stress. A sense pair returns the actual bridge-side voltage to the controller/reference domain, preventing line loss from becoming gain error or drift. If sense is treated as “optional,” long-term stability usually degrades first.

4-wire vs 6-wire is a stability decision, not a feature checkbox

4-wire works when the harness is short and contact variation is small. 6-wire becomes the practical choice when the system must remain accurate under cable length changes, connector aging, and ambient temperature swing. The decision is driven by how much line loss and contact variation can be tolerated.

Kelvin points must be at the bridge, not only at the PCB

The Kelvin concept only works when the sense measurement “touches” the bridge terminals. Sensing at the PCB while the harness and connector sit in between does not remove the dominant series errors. Keep differential pairs symmetric to avoid converting common-mode disturbances into differential error.

Ground, shield, and guard: control leakage and prevent CM→DM conversion
Shielding is only useful with a predictable return path

Shield currents must not share impedance with the measurement reference. If shield return paths wander across sensitive nodes, cable motion and environmental coupling turn into apparent sensor signal changes.

Guard rings belong around high-impedance nodes

Guarding reduces the impact of surface leakage films on inputs, REF-related nodes, and gain-setting networks. The purpose is to steer leakage current into a controlled potential, preventing it from appearing as input offset or slow drift.

Thermal gradients: why “same PCB temperature” is not enough
Gradients create drift through leakage, networks, and contact physics

Low-frequency bridge systems translate tiny voltage changes into meaningful physical units. A small temperature difference across the front end can change leakage, bias-related I×R errors, and connector resistance, appearing as slow drift even when the average PCB temperature seems constant.

Practical layout moves that reduce gradient-driven drift
  • Keep the bridge front-end away from hot regulators, CPUs, and power resistors.
  • Use symmetrical copper and component placement around differential paths to avoid one-sided heating.
  • Validate with repeatable disturbances (airflow, touch, warm-up) and measure time-to-within-band.
Connector and harness effects: contact variation becomes measurement error

Connector resistance changes and lead resistance imbalance can reduce real-world common-mode rejection and create slow drift. If readings change when the harness is lightly moved, verify symmetry and contact stability before blaming the INA core CMRR.

Bridge wiring blueprint with excitation, sense, and signal pairs Diagram showing a bridge sensor with excitation, signal, and optional sense wire pairs routed to an instrumentation amplifier, marking Kelvin points and emphasizing pair symmetry. Bridge Kelvin INA VIN+/VIN− Pair symmetry Excitation Signal Sense 4-wire 6-wire Use excitation, signal, and (when needed) sense pairs, place Kelvin points at the bridge, and keep pair symmetry to protect real-world CMRR.

Application Blueprint: Bridge Strain/Pressure/Weighing

Ratiometric concept: share excitation and reference to cancel drift paths

If the bridge excitation and the ADC reference share the same source, excitation variation appears in both the signal and the reference, so a ratio-based measurement becomes less sensitive to excitation drift. This improves long-term stability without changing the INA architecture.

Gain selection flow: from mV/V bridge output to ADC range (no long derivations)
Step 1 — translate full-scale physical input into bridge differential volts

Use bridge sensitivity (mV/V) and excitation voltage to predict the maximum differential output. This establishes the true electrical full-scale before selecting any gain.

Step 2 — reserve headroom and choose REF center

Plan a safety margin for overload, warm-up drift, and plug events. Place REF to center the output within the valid CM + OUT window, so the amplified signal does not approach rails during real disturbances.

Step 3 — choose gain so the effective output uses the ADC range without clipping

The gain should be high enough to use the ADC range for resolution, but low enough to avoid saturation and long recovery tails. After selecting gain, re-check the valid window at that gain and the intended output center.

Low-frequency strategy: reduce perceived instability without over-designing the chain
Control the true limiter: 0.1–10 Hz noise, leakage, and thermal gradients

In weighing, improving wideband noise alone does not guarantee a stable reading. Stability is usually limited by low-frequency noise and drift mechanisms that appear as slow movement.

Sampling and averaging reduce jitter, but do not remove drift

Averaging reduces random jitter and improves short-term repeatability. Drift from temperature, leakage, and contact variation must be reduced by wiring, layout, and window planning; it cannot be averaged away.

Common failure modes: symptom → first checks
Warm-up drift after power-up

First check thermal gradients and REF centering. Then check leakage paths near high-impedance nodes and input protection behavior under bias.

Airflow or touch causes slow movement

First check gradient-driven drift and humidity-related leakage. Validate with repeatable airflow tests and compare before/after cleaning or guarding.

Touching or moving the harness changes the reading

First check pair symmetry, shield return path, and connector contact stability. Cable motion often changes coupling and contact conditions, converting common-mode disturbance into differential error.

Temperature change causes slow wandering

First map drift into physical units using the noise/drift workflow, then decide whether layout/harness fixes, calibration, or a different architecture is required.

Ratiometric bridge chain with shared excitation and ADC reference Block diagram showing bridge excitation feeding the bridge and also feeding the ADC reference, with INA amplification and ADC conversion to physical units. Vexc Source Bridge INA Gain ADC Codes g Pa Vref (shared) Share bridge excitation with ADC reference to reduce excitation-driven drift, then set gain and headroom from mV/V full-scale.

IC Selection Logic & Production-Ready Engineering Checklist

Use this section as a decision framework: translate system constraints into the exact datasheet lines to request, then confirm with a minimal bench plan that is repeatable in production.

A) Selection flow (gate-by-gate logic)

1) CM window & supply domain
  • System input: bridge excitation, expected input common-mode, REF target, single/dual-supply limits.
  • Must-ask datasheet lines: input CM range vs gain/output, output swing vs load, REF behavior.
  • Bench hook: apply a common-mode step and check output stays linear and recovers without long tails.
2) Target gain & dynamic needs
  • System input: bridge sensitivity (mV/V), full-scale physical range, settling time target.
  • Must-ask datasheet lines: gain equation/range, bandwidth vs gain, overload recovery.
  • Bench hook: step response to “within-band” threshold (ringing vs slow tail indicates different root causes).
3) Low-frequency stability (offset / drift / 0.1–10 Hz)
  • System input: stability target in physical units (g/Pa), warm-up allowance, ambient temperature swing.
  • Must-ask datasheet lines: offset, offset drift, 0.1–10 Hz noise, 1/f corner notes (if provided).
  • Bench hook: short-window jitter + minute-scale drift + 2-point temperature sample (screening-level).
4) Input bias, leakage, and source-R sensitivity
  • System input: bridge equivalent source resistance, harness contamination risk, input protection presence.
  • Must-ask datasheet lines: input bias vs temperature, input offset vs source resistance notes.
  • Bench hook: inject a controlled leakage path and check offset/drift sensitivity (repeatable stress test).
5) Output drive & ADC interface constraints
  • System input: ADC input structure (sampling cap / RC), required settling per sample, load capacitance.
  • Must-ask datasheet lines: output current, stability with capacitive load, settling behavior (if specified).
  • Bench hook: test with real ADC (or equivalent sampled load) to confirm settling to the error band.
6) Robustness requirements (EMI/ESD as “filters and checks”)
  • System input: cable length, field disturbance likelihood, survivability expectation.
  • Must-ask datasheet lines: CMRR vs frequency, input overvoltage notes, recovery after overload.
  • Bench hook: common-mode injection + harness touch/move test; confirm output does not “double-step” or latch into a tail.
Must-ask datasheet lines (copy/paste list)
Input CM range vs gain/output
Input bias current vs temperature
0.1–10 Hz noise + offset drift
Output swing vs load (headroom)
Overload recovery / settling
CMRR vs frequency (real cables)
Selection decision tree and must-ask datasheet lines Flow from requirements to constraints, candidates, verification, and shortlist. A right column lists must-ask datasheet lines such as CM range, bias current, 0.1–10 Hz noise, output swing, recovery, and CMRR versus frequency. Requirements Constraints Candidates Verify Shortlist Decision gates CM window Gain & BW LF stability Bias & leakage ADC drive Recovery & CMRR(f) Must-ask lines CMR vs Vout Ib vs temp 0.1–10 Hz Swing vs load Recovery CMRR vs f Convert constraints into must-ask datasheet lines, then validate with a minimal, repeatable bench plan.

B) Production-ready engineering checklist (layout → budget → test)

B1) Wiring & layout
  • Symmetry: route VIN+/VIN− as a matched environment pair; avoid asymmetry that converts CM to DM.
  • Kelvin/sense: place sense points at the bridge terminals for long cables; do not “sense” only at the PCB end.
  • Guarding: guard high-impedance nodes (inputs / REF-related nodes / gain-setting network) to control surface leakage.
  • Return paths: keep shield/return currents away from the measurement reference impedance.
B2) Error budget (own the dominant term)
  • Bias/leakage term: error ≈ (Ib + leakage) × Rs (map into physical units).
  • Gain term: RG tolerance/tempco + internal network drift → gain error vs temperature.
  • Thermal term: gradients across the front-end and connectors → slow drift (not removable by averaging).
  • Contact term: connector/harness resistance variation → excitation loss and CM→DM conversion.
B3) Production tests (minimal set that catches real field issues)
  • Fast spot-check: offset and gain at one or two points (screening).
  • CMRR spot-check: inject a known common-mode change and measure the equivalent differential output.
  • Temp sample: two-temperature drift sample using a stability threshold (not a fixed soak time).
  • Harness stress: repeatable connector/harness wiggle test; log reading change band and recovery time.

Reference examples (part numbers; starting points only)

These part numbers are provided to speed up datasheet lookup and lab screening. Final selection must follow the flow above and pass the bench hooks.

Texas Instruments
INA826, INA828, INA818, INA118, INA128, INA129
Analog Devices
AD620, AD8221, AD623
Use-case tags (quick filter)
Precision bridge screening • Single-resistor gain • Long-cable realism checks • Recovery-tail sensitivity

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

FAQs (Classic 3-Op-Amp INA for Bridges)

Short, actionable troubleshooting answers only. Each item includes a ranked cause list, one quick check, a pass/fail rule, a minimum fix, and a scope guard.

Why does CMRR look great on paper but the bridge still drifts with cable resistance changes?
Symptom
Reading changes slowly after cable length/temperature/connector conditions change.
Likely cause (ranked)
  1. Rs+ ≠ Rs− causes CM→DM conversion (cable/connector asymmetry dominates).
  2. Excitation line loss changes (no true Kelvin/sense at the bridge terminals).
  3. Contact resistance drift under stress/thermal gradients.
Quick check
Add a known small series resistor to only one input lead (simulate mismatch), then log output shift versus added resistance.
Pass/Fail threshold
Fail if the induced output shift consumes more than the allowed drift band (or > 25% of the total drift budget) for the same mismatch level expected from the harness/connector.
Fix (minimum change)
  • Restore pair symmetry (routing + harness) and stabilize connectors/mechanics.
  • Add true bridge-terminal Kelvin/sense when cable loss variation is non-negligible.
Scope guard
Deeper protection/standards sizing belongs to the Protection page. Full ratiometric/remote-sense system design belongs to the Excitation & ADC Co-Design page.
How to quickly tell “source-impedance mismatch” vs “true INA limitation”?
Symptom
CMRR-driven error is suspected, but root cause is unclear.
Likely cause (ranked)
  1. External mismatch (Rs+, Rs−, connector contact, asymmetric shielding return).
  2. Window violation (CM range / output headroom near rails).
  3. Overload/recovery tails masked as “poor CMRR”.
Quick check
Swap VIN+ and VIN− (or swap the left/right harness ends) while keeping the same sensor stimulus, then observe whether the error polarity follows the swap.
Pass/Fail threshold
If the error flips sign or changes significantly after swapping, external mismatch dominates. If the error stays nearly unchanged, suspect window/headroom or recovery limits.
Fix (minimum change)
  • Fix harness symmetry and shield return path first; then re-test.
  • If window/recovery is the limiter, adjust REF center and headroom before changing ICs.
Scope guard
Sensitivity differences between 2-op-amp and 3-op-amp INAs belong to the 2-Op-Amp INA page.
What RG tolerance/tempco is worth paying for in weighing systems?
Symptom
Gain-related drift or channel-to-channel spread is observed across temperature and time.
Likely cause (ranked)
  1. RG tolerance/tempco dominates the gain budget.
  2. Surface leakage around RG and high-impedance nodes shifts effective RG.
  3. Thermal gradients change local conditions, creating apparent gain drift.
Quick check
Convert the allowed physical drift band into an allowed gain drift band, then back-solve the maximum acceptable RG drift contribution.
Pass/Fail threshold
Upgrade RG if its drift contribution exceeds ~30–50% of the total drift budget (or is the largest single contributor).
Fix (minimum change)
  • Use a lower-tempco, tighter-tolerance RG only after confirming RG dominates the drift budget.
  • Place RG away from contamination and add guarding/cleanliness controls to prevent leakage-driven “effective RG” drift.
Scope guard
Calibration strategy beyond “screening-level” belongs to the production/calibration pages, not this architecture page.
Why does touching the cable change the reading even with a 3-op-amp INA?
Symptom
Light cable touch/motion creates a measurable output shift or slow drift.
Likely cause (ranked)
  1. Shield/return path impedance changes → CM disturbance converts to DM error.
  2. Connector contact micro-motion changes resistance and asymmetry.
  3. Humidity/contamination changes leakage and electrostatic coupling behavior.
Quick check
Perform a repeatable touch/move test at a fixed location and force, and log both the peak shift and the recovery time back into the stability band.
Pass/Fail threshold
Fail if the repeatable disturbance produces a shift larger than the allowed stability band, or if recovery time exceeds the system update interval.
Fix (minimum change)
  • Enforce pair symmetry and a controlled shield return path; avoid shield current sharing measurement reference impedance.
  • Mechanically stabilize the connector/harness to reduce contact micro-motion.
Scope guard
Detailed EMI/ESD protection network sizing belongs to the Protection page.
How can input protection increase offset over temperature?
Symptom
Offset drift worsens at higher temperature after adding clamps/series parts/RC.
Likely cause (ranked)
  1. Protection device leakage increases with temperature and creates Ib/leakage × Rs error.
  2. Surface contamination/humidity creates a temperature-dependent leakage path around high-Z nodes.
  3. Clamp conduction during transients leaves a recovery tail (appears as “drift”).
Quick check
Compare input-short offset at room temperature versus a hot condition, with the same wiring and bias state, and compute Δoffset.
Pass/Fail threshold
Fail if Δoffset mapped into physical units exceeds the stability budget, and changes when protection parts are removed/relocated/cleaned.
Fix (minimum change)
  • Move leakage-sensitive protection away from high-impedance nodes, and add guarding/cleanliness controls.
  • Re-check Ib/leakage × Rs error after changes (same quick check).
Scope guard
Protection device selection and IEC-level survivability belong to the Protection page.
How close to the rails can the input common-mode be before distortion appears?
Symptom
Linearity degrades or recovery slows when the bridge CM shifts toward supply rails.
Likely cause (ranked)
  1. Input CM window collapses with gain/output level (real “window” is smaller than a headline spec).
  2. Output headroom is insufficient under load at the chosen REF center.
  3. Overload behavior triggers slow recovery tails near rails.
Quick check
Sweep common-mode in small steps at the intended gain and REF center, and log where distortion or recovery time increases sharply.
Pass/Fail threshold
Fail if the valid operating region does not cover the expected CM range plus a guardband, or if time-to-within-band exceeds system timing targets near rails.
Fix (minimum change)
  • Shift REF to re-center output swing and restore headroom.
  • Reduce gain or increase supply/headroom if the CM window collapses at the required output level.
Scope guard
Detailed window planning is covered in this page’s CM/REF/Headroom section; device families with wide CM belong to the Wide-CM/HV pages.
Why does the output take long to recover after overload or plugging the sensor?
Symptom
After a plug event or a large transient, readings stay “stuck” or drift back slowly.
Likely cause (ranked)
  1. Input/output saturation due to insufficient headroom at the chosen gain/REF.
  2. Clamp/protection conduction creates a discharge path and a recovery tail.
  3. Cable + RC time constants produce a long settling tail even after the transient ends.
Quick check
Create a controlled overload (repeatable step/plug simulation) and measure time-to-within-band at the output.
Pass/Fail threshold
Fail if recovery time exceeds the system’s allowed “back-in-spec” time or update interval after a repeatable overload.
Fix (minimum change)
  • Increase headroom (REF re-center, gain reduction, or supply margin) to prevent saturation.
  • Reduce tail-causing RC/time constants while keeping input robustness.
Scope guard
Protection clamp selection and recovery behavior under IEC events belong to the Protection page.
Does adding an input RC always improve stability? When can it worsen ringing?
Symptom
After adding RC, response gets slower, rings more, or becomes touch-sensitive.
Likely cause (ranked)
  1. RC + cable capacitance creates an underdamped pole/zero pair.
  2. RC placement is not at the input, leaving the cable “inside” the loop.
  3. Excess series resistance increases Ib/leakage × Rs error or slows settling.
Quick check
Compare step response across three builds: no RC, small RC, larger RC (same cable). Record ringing amplitude and time-to-within-band.
Pass/Fail threshold
Fail if RC increases ringing or increases time-to-within-band beyond the system target compared to the no-RC baseline.
Fix (minimum change)
  • Place the RC at the INA input so the cable is outside the filtered node.
  • Reduce series R if it slows settling or inflates Ib/leakage × Rs error.
Scope guard
Full filter/ADC-drive co-design belongs to the Excitation & ADC Co-Design page.
How to estimate resolution impact from 0.1–10 Hz noise vs wideband noise?
Symptom
Short-term jitter may be small, but long-term stability looks worse (or the opposite).
Likely cause (ranked)
  1. Wideband noise dominates short-window RMS (“jittery” but not drifting).
  2. 0.1–10 Hz noise and drift dominate long-window peak-to-peak (“slow wander”).
  3. Thermal/leakage/contact drift masquerades as “noise” over long windows.
Quick check
Measure two windows: short-window RMS (captures wideband) and long-window peak-to-peak (captures low-frequency). Map both into physical units using sensor sensitivity and gain.
Pass/Fail threshold
Fail the wideband target if short-window RMS exceeds the resolution requirement. Fail the stability target if long-window peak-to-peak exceeds the allowed stability band.
Fix (minimum change)
  • If wideband-limited: tighten bandwidth/averaging and verify settling constraints.
  • If low-frequency-limited: reduce leakage/thermal gradients and avoid saturation/recovery tails.
Scope guard
Detailed noise-to-resolution mapping and drift mechanisms are covered in this page’s Noise & Drift section.
What quick production tests catch wiring/connector-induced errors early?
Symptom
Good boards fail in the field due to harness/connector variability and handling.
Likely cause (ranked)
  1. Connector contact resistance variation and asymmetry (CM→DM conversion).
  2. Shield return path inconsistency (handling-sensitive CM injection).
  3. Leakage sensitivity that only shows up under humidity/temperature.
Quick check
Run a minimal three-test set: (1) offset/gain spot-check, (2) common-mode injection spot-check, (3) repeatable harness/connector wiggle test with recovery-time logging.
Pass/Fail threshold
Pass only if all three tests remain inside the same defined stability band, and recovery time after the wiggle test is within the production spec.
Fix (minimum change)
  • Standardize harness symmetry and connector mechanics; verify with the same wiggle script.
  • Adjust routing/guarding to reduce leakage sensitivity before increasing test complexity.
Scope guard
A full production reporting schema and binning strategy belongs to the Production Reporting & Failure Analysis page.