123 Main Street, New York, NY 10001

2-Op-Amp Instrumentation Amplifier (INA): Practical Guide

← Back to:Instrumentation Amplifiers (INA)

A 2-op-amp INA is the most cost- and power-efficient way to build multi-channel differential front-ends—when source impedance and wiring symmetry are controlled. This page shows how to prevent CMRR collapse (CM→DM conversion), budget headroom, and verify stability/settling so the “cheap” architecture stays reliable on real boards.

What is a 2-Op-Amp INA and when it wins

A 2-op-amp instrumentation amplifier is a cost- and power-efficient differential front-end that can perform extremely well when source impedance and wiring symmetry are controlled—but its real CMRR is strongly shaped by the sensor + PCB, not just the datasheet.

Positioning
  • Primary value: lower cost, lower power, and scalable multi-channel measurement.
  • Primary constraint: common-mode rejection depends heavily on external symmetry (source impedance, protection network, and layout).
  • Best fit: cost-driven DAQ/process channels where sensor wiring and input networks can be kept consistent.
When it wins
A 2-op-amp INA is usually the best choice when all three conditions below are true:
  1. Source impedance is controlled: Rs+ ≈ Rs− and stays stable across temperature, connectors, and cable motion.
  2. Input symmetry is enforceable: matching RC/protection components and truly symmetric routing are practical.
  3. Common-mode environment is manageable: CM amplitude and spectrum can be reduced with shielding/return paths/filters.
Pass criteria (field-ready)
  • Common-mode injection produces only a small, repeatable residual differential output (no large variation across channels).
  • Cable touch/motion does not create step-like output shifts beyond the system noise envelope.
Red flags (typical failure signals)
  • CMRR collapses on the PCB: datasheet looks great, but real CMRR degrades sharply once wiring and protection are added.
  • Cable motion changes the reading: touching/moving the cable shifts output (classic CM→DM conversion symptom).
  • Channel-to-channel drift mismatch: identical channels drift differently due to small asymmetries (leakage, protection paths, connector contact).
Quick check (fast isolation)
  • Force both inputs to the same node (no differential signal), then inject a small common-mode step; measure residual output change.
  • Swap the two input wires; if the error polarity changes, the dominant path is asymmetry (Rs mismatch / protection mismatch / routing).
When to route away (do not force 2-op-amp)
  • Source impedance is unknown or variable (long leads, multiple connectors, changing contact resistance, large bridge imbalance).
  • Input protection must be asymmetric due to real-world constraints (different clamp paths, different series resistors, different RC).
  • Common-mode disturbance is large and broadband, and wiring symmetry cannot be guaranteed.
Recommended next page
Use a 3-op-amp INA when real wiring and source resistance mismatch are unavoidable: Classic 3-Op-Amp INA.
2-Op-Amp INA page scope map Block diagram showing what this page covers versus related sibling pages: 3-op-amp, chopper, PGA, high-voltage and isolated solutions. Page scope (2-op-amp INA) Keep the page focused: cover only what the 2-op-amp topology owns This page covers Related pages CMRR vs source-R mismatch CM→DM conversion mechanisms Gain setting & resistor strategy Ratio, tolerance, bandwidth impact Multi-channel wiring & verification Layout symmetry and CM tests Classic 3-Op-Amp INA Zero-Drift / Chopper INA PGA / Programmable INA High-Voltage / Wide-CM INA Isolated INA / Isolated ΣΔ

Diagram: A scope map to keep content vertical and non-overlapping—coverage stays inside 2-op-amp INA boundaries, while deeper topics route to sibling pages.

Core topology: how the 2-op-amp INA actually works

The 2-op-amp INA relies on two amplifier paths and a resistor network to amplify differential signal while canceling common-mode. In practice, any asymmetry in what each input “sees” (source resistance, protection parts, or routing) turns common-mode into residual differential error.

Topology in one glance
  • Two paths: each input is amplified through its own loop, then combined through a resistor network.
  • Ideal behavior: equal response to common-mode on both paths → subtraction cancels it.
  • Real behavior: unequal path impedance or gain → cancellation is incomplete → residual differential output appears.
Minimal gain relationship (engineering usable)
Gain is set primarily by resistor ratios and the gain element (often named Rg). Exact forms vary by implementation, but two rules hold across designs:
  • Ratio dominates: matching between paired resistors is typically more important than absolute accuracy.
  • Higher gain tightens margins: bandwidth, output swing, and recovery become the first limits in single-supply systems.
Quick check
Verify gain with a small differential stimulus at the intended common-mode level; repeat across channels to confirm ratio consistency and avoid “looks fine at mid-CM only” traps.
Where common-mode leaks into differential error
  • Source impedance mismatch: Rs+ ≠ Rs− creates unequal input drops and phase shifts, especially when filters/protection are present.
  • Protection asymmetry: different series resistors, clamp leakage, or RC values produce unequal transfer under CM disturbance.
  • Routing asymmetry: different parasitic capacitance to aggressors/planes causes frequency-dependent CM→DM conversion.
Pass criteria
Under a controlled common-mode stimulus, residual differential output should be stable across repeated tests and should not jump with cable motion or probe placement.
Error paths that map directly to system problems
Resistor ratio mismatch
Converts CM cancellation error into CMRR loss and gain error; worsens with frequency when parasitics differ.
Input bias current × source-R
Appears as offset that drifts with temperature and leakage; becomes dominant in high-impedance sensors or contaminated boards.
Output swing / headroom
Near-rail nonlinearity and saturation recovery distort readings and can create slow “settling tails” in multi-channel scans.
Protection leakage asymmetry
Clamp diodes and TVS leakage can create temperature- and humidity-dependent offsets if the two inputs do not leak equally.
2-op-amp INA simplified topology schematic Simplified block schematic with two op-amp blocks, resistor network labels R1 R2 Rg, differential inputs Vin+ Vin-, common-mode label Vcm, and output Vout. Simplified 2-op-amp INA topology (concept view) Key nodes only: Vin+, Vin−, Vcm, Vout, and resistor ratios Vin+ Vin− Vcm A1 Input path A2 Input path Resistor network R1 R2 Rg Vout Gain ≈ k(R1/R2, Rg) · ratio matching matters Asymmetry (Rs / RC / routing) → CM leaks into DM

Diagram: A concept schematic that highlights the only labels needed for later chapters—CMRR failures are usually created by asymmetry outside the silicon (source-R, protection, and layout).

Why CMRR collapses: source impedance mismatch is the real enemy

CMRR is the ability to reject common-mode changes so they do not appear as differential output error. In a 2-op-amp INA, real-world asymmetry (source resistance, protection parts, and routing parasitics) converts common-mode disturbance into residual differential error.

The mechanism in three steps (CM → DM conversion)
  1. Common-mode enters both inputs: cable pickup, ground bounce, or coupling injects the same disturbance onto Vin+ and Vin−.
  2. Inputs do not respond equally: Rs+ ≠ Rs− or asymmetric RC/clamps create different drops and phase shifts on each side.
  3. Cancellation becomes incomplete: subtraction/combination inside the INA leaves a residual differential component at Vout.
Practical takeaway
High datasheet CMRR does not guarantee high system CMRR; the dominant loss is often created by external asymmetry, not silicon limits.
What amplifies the problem
Source-R mismatch (Rs+ ≠ Rs−)
Any imbalance converts part of common-mode into differential error, especially when series resistors or RC filters are present.
Protection / RC asymmetry
Different series resistors, clamp leakage, or capacitor values create unequal transfer under common-mode stress.
Routing parasitics
Unequal parasitic capacitance to planes or aggressors causes frequency-dependent CM→DM conversion.
Frequency signatures (how it looks on instruments)
  • Low frequency: behaves like offset/drift; changes with temperature, humidity, contact resistance, and slow cable movement.
  • Higher frequency: looks like spikes, jitter, or noise bursts; worsens with coupling, probe placement, and fast common-mode steps.
  • Key clue: “CM disturbance in → differential residue out” increases with frequency when parasitic imbalance dominates.
Measurable diagnosis (no hand-waving)
Step 1 · Remove differential signal
Force Vin+ and Vin− to the same node (no differential input). Any output movement now is not “real signal”.
Step 2 · Inject a controlled common-mode disturbance
Apply a small CM step or sweep to both inputs through a symmetric coupling path; observe the residual differential at Vout.
Step 3 · Prove source-R sensitivity
Add a small series resistor on only one input (intentional Rs mismatch). If residual error changes strongly, the dominant issue is CM→DM conversion.
Pass criteria (usable form)
  • Residual differential output under CM stimulus is small, repeatable, and consistent across channels.
  • Cable touch/motion does not create step-like output shifts beyond the expected noise envelope.
CMRR error injection model for 2-op-amp INA Model showing sensor source resistances Rs+ and Rs-, common-mode disturbance injection, layout parasitics, and residual differential output at the INA output. CMRR loss mechanism (CM → DM conversion) Asymmetry turns common-mode disturbance into residual differential error Sensor / Bridge Differential source Rs+ Rs− Cp Cp Vcm disturbance 2-Op-Amp INA CM cancel + subtract Vout Residual DM Mismatch Layout asymmetry Frequency dependence

Diagram: Common-mode disturbance becomes differential residue when the two input paths are not symmetric (Rs, RC, clamps, or parasitics).

Input common-mode range & headroom: the hidden limiter in single-supply systems

“Rail-to-rail” does not mean linear to the rails. In single-supply designs, the usable region is bounded simultaneously by input common-mode range, output swing, and gain—violating headroom often looks like drift, distortion, or slow recovery in multi-channel scans.

RRI / RRO: separate “reach” from “linearity”
  • Reach: input/output can approach a rail without immediate saturation.
  • Linearity: distortion and gain error remain small inside a narrower window.
  • Recovery: once saturated, the output may take time to return—this is a dynamic limit, not a DC spec.
Fast clue
If the error appears only near one rail or after a large transient, headroom and recovery are likely the root causes, not CMRR.
The triple constraint (CM range + output swing + gain)
  • Input CM range: the input stage must remain inside its linear window at the intended common-mode level.
  • Output swing: amplified differential signal must fit inside the output linear region with margin.
  • Gain: higher gain compresses available output headroom and can force saturation during spikes or scan transients.
Pass criteria (budget form)
The worst-case common-mode plus amplified differential peak stays away from both rails with defined margin, and saturation recovery time remains below the sampling/scan interval budget.
VMID / Vref planning for single-supply INAs
  1. Define extremes: worst-case common-mode and differential peak (including expected transients).
  2. Center the trajectory: choose VMID/Vref so the amplified output waveform sits inside the linear swing window.
  3. Reserve margin: allocate headroom for drift, RC settling, and ADC kickback (without assuming “rail-to-rail linear”).
Quick check
Sweep input common-mode across the intended range while holding differential amplitude constant; look for gain shift or distortion onset near the rails.
Overload and slow recovery (multi-channel scan impact)
  • Saturation history matters: a large spike can push the output into saturation, creating a slow “tail”.
  • Scan systems amplify the symptom: slow recovery can look like drift or channel memory when channels are multiplexed.
  • Separate cause: recovery-limited behavior is time-dependent; CMRR loss is stimulus-dependent and often frequency-shaped.
Pass criteria
After an intentional overload pulse, the output returns to the expected level before the next sample window; no long tails remain in the measured step response.
Headroom budget chart for single-supply 2-op-amp INA Vertical supply rail bar chart showing input common-mode linear window, output swing window, and margin for signal trajectory under gain. Headroom budget (single-supply) Usable operation is bounded by input CM window, output swing, and gain VDD GND Input CM window Linear region Output swing Linear window Signal Gain Margin (top) Margin (bottom) Vcm Vout swing Near-rail distortion

Diagram: Budget headroom explicitly—input CM linear window and output swing must both contain the amplified trajectory with margin, or distortion and slow recovery will dominate.

Gain setting & resistor strategy: accuracy, bandwidth, and tolerance mapping

In a 2-op-amp INA, gain is primarily set by resistor ratios. Ratio mismatch does not only create gain error—it also degrades cancellation paths and can reduce real, board-level CMRR. A good resistor strategy converges accuracy, bandwidth, and multi-channel consistency with predictable cost.

Rule #1: ratio dominates, absolute value follows
  • Gain accuracy: ratio tolerance is usually the first-order term in gain error.
  • CMRR risk: ratio mismatch and asymmetric input networks reduce common-mode cancellation margin.
  • Practical implication: matched pairs and symmetric placement often outperform “high-precision single resistors” scattered across the board.
Quick check
Compare channel-to-channel gain using the same differential stimulus and the same common-mode level; a wide spread is often ratio/matching or asymmetry, not “random silicon”.
Tolerance and tempco mapping (how specs become errors)
Ratio tolerance → gain error
The relative mismatch between paired resistors shifts the effective ratio and directly moves gain from its intended value.
Ratio drift → gain drift
What matters most is matching of tempco tracking, not the smallest individual TCR number.
Asymmetry → CMRR degradation
Unequal resistor placement, return paths, or parasitics introduce frequency-shaped CM→DM residue.
Pass criteria
  • Gain at the intended common-mode is repeatable across temperature points.
  • Channel-to-channel gain spread stays inside the calibration or trimming budget.
High gain reduces usable bandwidth (verify both small and large signal)
  • Small-signal bandwidth: verify flatness and roll-off against sensor dynamics and filter targets.
  • Large-signal behavior: verify step settling and overload recovery; “slow tails” often dominate scan systems.
  • Single-supply trap: high gain reduces headroom and increases the chance of clipping during spikes and channel switching.
Quick check
Apply a differential step at the intended common-mode level; confirm the output settles before the sampling window closes and does not exhibit long recovery tails.
Multi-channel consistency: why resistor networks win
  • Better ratio matching: shared substrate processes improve tracking versus discrete parts spread over the PCB.
  • Better temp tracking: ratio drift is tighter, so temperature sweeps produce more consistent channel slopes.
  • More consistent parasitics: geometry symmetry reduces frequency-shaped CM→DM differences across channels.
Selection guideline (usable)
For many channels and repeated builds, prioritize matched arrays for the ratio-defining resistors; use discrete resistors only where absolute value or power handling is the actual constraint.
Mapping table: parameter → symptom → action → pass criteria
Parameter Symptom Action Pass criteria
Ratio tolerance Channel gain spread Use matched pair/array; symmetric placement Spread fits calibration budget
Ratio drift (tracking) Temp sweep slope mismatch Prefer arrays; reduce gradients Slopes converge
High gain BW loss, slow settling Verify step + sweep at target CM Settling fits window
Tradeoff map for gain, bandwidth, matching and cost in a 2-op-amp INA Tradeoff map showing gain versus bandwidth, matching versus CMRR, and cost impact, with block elements representing resistor arrays, discrete resistors, tolerance, and tempco. Tradeoff map (resistor strategy) Converge Gain, BW, CMRR and Cost by controlling ratio matching Gain Bandwidth Matching / CMRR Gain ↑ BW ↓ Matching ↑ CMRR ↑ Rg Ratio Small-signal Step / settle Array Tolerance Tempco Cost ↑ (if over-specified)

Diagram: Drive the design by ratio matching and symmetry—gain, bandwidth, and real CMRR can be converged without runaway cost when the tradeoffs are made explicit.

Noise & DC accuracy in real sensors: what dominates depends on source impedance

The same INA can look excellent with low-impedance sensors and fail with high-impedance sensors. As source impedance increases, current-related terms (input current noise and bias/leakage) grow and can dominate both noise and DC accuracy.

Three dominant terms (source impedance decides who wins)
  • Voltage noise (en): often dominant at low source impedance.
  • Current noise (in·Rs): grows with Rs and becomes important as impedance rises.
  • Bias/leakage (Ib·Rs): converts directly into offset error and is highly sensitive to asymmetry and contamination at high Rs.
Practical takeaway
Improving en alone does not fix high-impedance systems; bias/leakage symmetry and surface cleanliness often become the real accuracy limit.
Bias current × Rs: the “hidden offset amplifier”
  • Offset creation: Ib through source resistance produces a differential-equivalent offset at the input.
  • Drift behavior: temperature, humidity, and board contamination change leakage and make the offset look like drift.
  • Asymmetry matters: unequal leakage on the two inputs creates large errors even when Ib is “typical small”.
Quick check
  • Swap Vin+ and Vin−; if the offset polarity flips, a dominant asymmetry path exists.
  • Compare “as-built” and “cleaned/dried” boards; large changes indicate leakage-driven error.
0.1–10 Hz vs wideband noise: map to usable resolution
  1. Define bandwidth: use the sensor bandwidth or the post-filter effective bandwidth.
  2. Estimate short-term RMS: convert wideband density into RMS within the effective bandwidth.
  3. Bound long-term stability: use 0.1–10 Hz peak-to-peak as a guardband for slow noise and drift-like behavior.
  4. Convert to system units: map input-referred terms through gain into ADC codes or sensor engineering units.
Pass criteria
Short-term averaged RMS meets the resolution target, and long-term readings remain bounded without slow wander beyond the low-frequency noise budget.
When to route to chopper or high-Z solutions (conditions only)
Choose zero-drift / chopper
When µV-level DC stability and low-frequency noise are the primary requirements and calibration cannot remove slow error.
Choose high-Z / FET-input INA
When source impedance is high and leakage/bias-driven offset dominates even with careful symmetry and cleanliness controls.
Field-ready budget steps (source impedance anchored)
  1. Estimate effective Rs: include sensor Rs plus any series resistors and filter components seen by each input.
  2. Pick dominant terms: compare en, in·Rs, and Ib/leakage·Rs using the expected operating temperature and humidity.
  3. Separate time scales: use wideband terms for short-term RMS and 0.1–10 Hz for long-term stability bounds.
  4. Map to system units: convert input-referred noise/offset through gain to ADC codes or engineering units.
  5. Route if needed: if the dominant term cannot be reduced without major system changes, choose the architecture that owns that limit.
Noise dominance versus source impedance for instrumentation amplifiers Chart showing how voltage noise en, current noise in times source impedance, and bias/leakage times source impedance dominate as source impedance increases, with low, mid and high impedance zones. Noise dominance vs source impedance As Rs increases, current-related terms and leakage become the limiting factors Source impedance (low → high) Error contribution Low Rs Mid Rs High Rs en in·Rs Ib·Rs Leakage Chopper High-Z INA Bias / leakage control

Diagram: As source impedance rises, current-related and leakage-related terms dominate; architecture choice and symmetry/leakage control become the primary levers.

Output drive, ADC interface & stability: the multi-channel trap zone

Multi-channel, cost-driven systems often fail at the output interface: capacitive loading, RC filters, and ADC sampling transients can steal phase margin, create kickback-induced glitches, and produce scan “memory” across channels. The goal is to make stability and settling predictable under real sampling conditions.

Load types and stability zones (R-load is not C-load)
  • Resistive load: mainly affects output current, swing, and distortion; it does not necessarily cause oscillation.
  • Capacitive load: adds phase lag and can collapse phase margin; it is the common root of ringing, overshoot, and burst oscillation.
  • Real interface: the output sees a mixed load (RC + ADC input behavior), so the whole chain must be verified as a unit.
Quick check
Compare step response with (1) R only, (2) C added, and (3) RC + ADC attached; ringing that appears only when C/ADC is present indicates phase-margin loss at the interface.
ADC kickback: sampling transients reflected into the driver
  • What happens: sampling switches connect an input capacitor; charge transfer creates a short, repetitive transient current demand.
  • What is observed: output spikes, steps, or bursts synchronized with sampling edges; those can convert into code errors if settling is incomplete.
  • Why it worsens in multi-channel: repeated switching plus insufficient recovery time produces a deterministic “memory” pattern from one channel to the next.
Diagnostic signature
If the output disturbance shifts when sampling rate or acquisition window changes, the dominant driver is sampling transient behavior, not random noise.
Riso / RC filters: stabilization lever with settling penalties
  • Riso purpose: decouple the INA output from the sampling transient current, reducing direct kickback injection into the output node.
  • RC purpose: shape high-frequency content and provide a local charge reservoir, reducing edge-driven disturbances.
  • Primary tradeoff: larger R and C slow settling; if the sample window arrives early, deterministic gain/offset errors appear.
Tuning sequence (field-safe)
  1. Stabilize first: remove ringing and burst oscillation under worst-case sampling edges.
  2. Then recover speed: reduce time constant until settling fits the acquisition window with margin.
  3. Re-check scan: confirm that channel-to-channel dependence disappears at the final values.
Multi-channel “memory effect”: why scanning fails even when single-channel looks fine
Incomplete settling
The RC/network is still converging when the next acquisition begins, so the previous channel leaves a deterministic residue.
Overload recovery tail
Large steps or near-rail events push the output or internal nodes into non-linear recovery that lasts longer than a scan period.
Shared-path coupling
Kickback energy couples through shared routing, supplies, or returns, so a disturbance appears simultaneously on other channels.
Pass criteria
  • Under worst-case sampling edges, the output does not ring or burst-oscillate.
  • At the sampling instant, the output is inside the noise envelope and shows no systematic tail.
  • Channel order and dwell time do not materially change the measured value beyond the error budget.
10-minute isolation workflow: locate the interface failure mode
  1. R-only test: remove C/ADC; confirm the driver is stable with resistive loading.
  2. C-only test: add the intended Cfilter without ADC; if ringing appears, the driver is C-load sensitive.
  3. ADC test: attach ADC; change sampling rate/window; disturbances that track sampling confirm kickback dominance.
INA to ADC interface chain with RC isolation, kickback and settling annotations Block diagram showing INA output, isolation resistor, filter capacitor to ground, and ADC sampling input with hold capacitor and kickback arrow, plus labels for settling and stability. INA → RC / AAF → ADC drive chain Kickback, settling, and stability determine multi-channel success INA Output driver Riso Cfilter RC shaping ADC Sampling input SW CHOLD kickback stability settling scan memory

Diagram: Use Riso and Cfilter to control kickback and stabilize the driver, then validate settling against the acquisition window to remove channel-to-channel memory.

Layout & wiring rules that decide CMRR in the field

In a 2-op-amp INA, field CMRR is often determined by symmetry and return paths, not by the datasheet number. The objective is to prevent common-mode interference from converting into differential residue through asymmetric impedance, parasitics, and leakage paths.

Input symmetry checklist (geometry + electrical + parasitic)
  • Geometry: route Vin+ and Vin− as a tight pair with equal length, same layer, and the same reference plane.
  • Electrical: mirror series resistors, RC filters, and protection parts so both inputs see the same impedance profile.
  • Parasitics: keep both inputs equally distant from noisy copper, planes, and shields to avoid unequal capacitance to aggressors.
Pass criteria
With a controlled common-mode injection, the residual differential output is stable across touch/move tests and does not shift with cable motion beyond the budget.
Return paths and “no split” rule (avoid hidden asymmetry)
  • Continuous reference: the differential pair needs a continuous return path under the traces.
  • No plane gaps: avoid routing across slots/splits; a detoured return increases loop area and creates unequal coupling.
  • Boundary control: define the reference at the connector so common-mode current does not enter the board uncontrolled.
Quick check
If the pair crosses a split and the measurement changes when the cable is moved, return-path discontinuity is a prime suspect.
Cable, connector, and shield strategy (keep CM outside)
  • Connector pinout: place Vin+ and Vin− adjacent; place a solid return reference pin nearby.
  • Shield intent: ensure shield connections define a repeatable common-mode return path instead of letting it couple into the signal pair.
  • Mechanical stability: strain relief and consistent cable routing reduce motion-driven changes in coupling and impedance.
Leakage and contamination control (INA-input only)
  • High impedance sensitivity: moisture and residues create leakage paths that translate into offset and CMRR loss.
  • Guarding: use guard rings and spacing around high-impedance input nodes to intercept leakage currents.
  • Symmetry requirement: treat both inputs identically; asymmetric contamination is effectively a built-in mismatch source.
Quick check
Compare offset and touch sensitivity before and after cleaning/drying; strong changes indicate leakage-driven error dominance.
Field checklist (short, executable)
  • Vin+ / Vin− routed as a tight pair, same layer, same plane reference.
  • No split/slot crossing under the pair; return path remains continuous.
  • Series parts (R/RC/protection) are mirrored and placed symmetrically.
  • Connector pinout keeps the pair adjacent with a nearby return reference.
  • High-impedance nodes use spacing/guarding; both inputs are treated identically.
  • Cable move/touch test does not shift the reading beyond the budget.
Symmetry and return-path diagram showing good versus bad routing for field CMRR Side-by-side diagram: good differential routing with continuous return plane versus bad routing crossing a split plane and coupling to an aggressor, illustrating return path discontinuity and asymmetry. Symmetry & return-path (GOOD vs BAD) Field CMRR is preserved by symmetry and continuous return paths GOOD BAD CONN tight pair solid plane return path CONN split cross split detoured return SW aggressor

Diagram: Preserve field CMRR by routing the differential pair over a continuous plane with symmetric parasitics; avoid split crossings and uncontrolled return detours that convert common-mode into differential residue.

Engineering checklist: build, debug, and verify (no hand-waving)

This section turns the page into a review-and-test package: requirements, schematic checks, PCB checks, and bring-up verification with measurable pass criteria. Every checklist item maps to an observable failure mode and a repeatable test hook.

A) Before design: lock the boundary conditions
Source impedance envelope
Define Rs_min, Rs_max, and allowable ΔRs (mismatch). This is the primary driver for field CMRR and bias·Rs error.
Common-mode envelope
Define Vcm_min/Vcm_max, including disturbance steps and cable-coupled common-mode. Headroom failures often hide here.
Bandwidth / settling objective
Specify target bandwidth or step response and the sampling window that must be met in scan-and-sample systems.
Multi-channel metrics
Define channel-to-channel limits: gain delta, offset delta, scan memory tolerance, and drift consistency across temperature and humidity.
Red flags (do not proceed without mitigation)
unbounded ΔRs unknown Vcm no settling margin cable not controlled
B) Schematic review: remove structural failure modes early
Resistor strategy / matching
  • Prioritize ratio matching over absolute values; treat unmatched ratios as built-in gain error.
  • Use matched networks where channel consistency matters; mirror placement intent in the schematic.
  • Keep both inputs electrically symmetric (same elements, same order, same values).
Input protection vs bias/leakage
  • Protection parts must be symmetric; asymmetric leakage converts common-mode into differential residue.
  • Series resistors and clamps must be checked for offset drift via bias·Rs and leakage paths.
Output interface chain
  • Reserve locations for Riso and Cfilter; plan for sampling transients and capacitive loading.
  • Define the settling window and verify the RC choices do not violate it during scanning.
Headroom plan (single-supply)
  • Confirm Vref/VMID gives margin for input common-mode and output swing at the selected gain.
  • Overload recovery must be compatible with the scan period; slow recovery produces scan memory.
C) PCB review: symmetry and return paths decide field CMRR
  • Route Vin+ / Vin− as a tight pair, same layer, same plane reference.
  • Do not cross splits/slots; keep the return path continuous under the pair.
  • Mirror series parts (R/RC/protection) and place them symmetrically.
  • Connector pinout keeps the pair adjacent with a nearby return reference pin.
  • High-impedance nodes use spacing/guarding; treat both inputs identically.
D) Bring-up verification: inject, measure residual, change one variable, re-test
1) Common-mode injection
Inject a controlled Vcm step or sweep and measure the residual differential at the output.
Pass criteria
Residual DM < X (under specified Vcm)
2) Rs mismatch sweep
Intentionally introduce ΔRs and observe how residual DM scales; strong scaling indicates mismatch-dominated CMRR collapse.
Pass criteria
ΔDM/ΔRs < Y (linearity under control)
3) Scan order & dwell sensitivity
Change channel order and dwell time; if the result depends on sequence, scan memory or incomplete settling is dominant.
Pass criteria
Channel delta < Z (order independent)
4) Temperature / humidity sensitivity
Run a controlled soak and compare drift and touch sensitivity; large deltas usually indicate leakage/bias·Rs dominance.
Pass criteria
Drift shift < W (after soak/clean)
Test flow and pass criteria ladder for 2-op-amp INA bring-up and verification Flowchart showing common-mode injection, residual measurement, Rs mismatch sweep, scan order test, and temperature/humidity checks, with a right-side ladder listing pass criteria placeholders. Test flow & pass criteria ladder Inject → measure residual → change one variable → re-test Inject CM (step / sweep) CM Measure residual (DM out) residual Change ΔRs (mismatch) ΔRs Re-test (scan / drift) scan drift Pass criteria residual DM < X slope vs ΔRs < Y ch. delta < Z drift shift < W

Diagram: Use a controlled common-mode injection and ΔRs sweep to expose mismatch-driven CMRR collapse, then validate scan order sensitivity and environmental drift with pass criteria placeholders.

Application patterns: cost-driven multi-channel measurement (within this page)

These patterns describe when a 2-op-amp INA is the most economical and stable choice in multi-channel systems. The focus is on source-impedance control, wiring symmetry, scan settling, and predictable common-mode behavior—without expanding into domain-specific application deep dives.

Pattern A) Multi-channel DAQ / process measurement (density + power sweet spot)
  • Why it fits: channel density and low power matter, while source impedance and wiring can be standardized.
  • What decides success: symmetric input networks, controlled return paths, and scan settling verified under real acquisition windows.
  • Typical failure sign: a few channels drift or move with cable motion—usually wiring asymmetry or ΔRs variation, not random noise.
Pattern B) Economic bridge / pressure / weighing front-ends (only when conditions are controlled)
  • Use when: lead resistance and mismatch are controlled, and cable symmetry is maintained end-to-end.
  • Upgrade trigger: uncontrolled cable/connector mismatch or wide ΔRs drift—field CMRR becomes unpredictable.
  • Validation hook: common-mode injection plus cable move/touch test confirms whether residual DM stays within budget.
Pattern C) Scan-and-sample systems (settling and memory dominate)
  • Critical metric: the output must settle within the acquisition window after each channel switch.
  • Primary trap: sampling kickback and RC time constants produce deterministic scan “memory” if recovery is incomplete.
  • Practical strategy: stabilize first (no ringing), then tune RC for settling margin, and re-check order dependence.
Typical failure patterns and first checks
Cable mismatch (ΔRs)
First check: compare residual DM before/after intentional ΔRs insertion and under cable motion.
Uncontrolled return path
First check: verify the pair does not cross plane splits and return current is not detoured.
Scan memory / incomplete settling
First check: change scan order and dwell time; strong order dependence indicates memory dominance.
Leakage / contamination sensitivity
First check: compare offset and touch sensitivity before/after cleaning/drying and during humidity soak.
When to move up (links only, no deep dive)
  • Uncontrolled ΔRs / cable variability: move to a topology less sensitive to input mismatch (3-op-amp INA page).
  • µV-level DC stability and 0.1–10 Hz dominance: move to zero-drift/chopper INA page.
  • Very high source impedance and leakage-driven errors: move to high-Z / electrochemistry INA page.
Multi-channel front-end block diagram using a 2-op-amp INA bank and ADC Block diagram showing multiple sensors, optional multiplexer, a bank of 2-op-amp INA channels, and an ADC, with labels for channel matching, scan settling, and wiring symmetry. Multi-channel front-end pattern Sensor bank → (optional) MUX → 2-op-amp INA bank → ADC Sensor bank CH1 CH2 CH3 CHn MUX optional 2-op-amp INA bank INA1 INA2 INA3 INAn ADC sample channel matching scan settling wiring symmetry

Diagram: The multi-channel pattern is economical when wiring symmetry and source impedance control are repeatable, and when scan settling is verified under the real acquisition window.

IC selection logic: fields → risks → shortlist (2-op-amp INA page)

The selection method below prevents “datasheet shopping” mistakes. It maps required datasheet fields to field failure risks, and produces a shortlist based on source impedance control, wiring symmetry, bandwidth/settling, and ADC-drive stability.

A) Required datasheet fields (fill these before comparing parts)
Field table (what to check → bench hook → red flag)
CMRR vs frequency (not DC-only)
Check: curve conditions (gain, source impedance assumptions, frequency range).
Bench hook: inject common-mode step/sweep, measure residual differential at output.
Red flag: large residual grows strongly with ΔRs or cable motion.
Input CM range (gain + swing dependent)
Check: input CM limits under intended gain and output swing constraints.
Bench hook: sweep Vcm with a fixed differential signal, watch linearity and recovery.
Red flag: near-rail distortion or slow overload recovery breaks scan stability.
Input bias & drift Ib, temp drift
Check: Ib vs temperature and how protection networks affect leakage paths.
Bench hook: offset change after humidity/cleaning; touch/cable motion sensitivity.
Red flag: offset behaves like “humidity amplifier” (leakage-dominated).
Noise (en / in) maps with Rs
Check: wideband density and low-frequency behavior relevant to the bandwidth of interest.
Bench hook: measure noise with representative Rs and cabling (not a lab short).
Red flag: high-Rs channels show disproportionate noise/offset wander.
BW / settling small + large signal
Check: settling specs under realistic step size and load conditions.
Bench hook: step response with the real RC/ADC interface; measure error at the sampling instant.
Red flag: scan order dependence (memory) indicates incomplete settling.
Output swing & stability load / C stability
Check: capacitive load stability region and recommended isolation resistance practices.
Bench hook: observe ringing/overshoot with RC/ADC load; confirm margin across channels.
Red flag: “stable on one channel” but unstable on others (layout + load variability).
Iq / temperature range system constraints
Check: Iq vs supply/temperature and shutdown behavior in multi-channel deployments.
Bench hook: thermal soak while monitoring offset/gain consistency across channels.
Red flag: drift mismatch across channels after soak indicates mismatch/leakage sensitivity.
Gate condition (must pass before a shortlist is trusted)
Rs mismatch budget + CM injection residual test + headroom budget + ADC settling window
B) Risk mapping: observed symptom → likely cause → quick check → fix
Symptom: CMRR collapses on the board
Likely cause: Rs+ ≠ Rs−, resistor ratio mismatch, layout asymmetry converts CM into DM.
Quick check: inject common-mode step/sweep and measure residual DM; repeat with intentional ΔRs.
Fix: enforce symmetry (network + routing + connector), then re-run the residual test.
Symptom: reading drifts or changes when cables are touched / humidity changes
Likely cause: bias·Rs and leakage paths dominate; protection networks or contamination create asymmetry.
Quick check: compare offsets before/after cleaning/drying; repeat under a controlled humidity soak.
Fix: make input protection symmetric, add guarding/spacing on high-impedance nodes, control contamination.
Symptom: multi-channel scanning is unstable (memory / crosstalk / order dependence)
Likely cause: incomplete settling, overload recovery too slow, or output instability into RC/ADC loads.
Quick check: change channel order and dwell; measure error at the sampling instant; look for ringing.
Fix: stabilize first (Riso/RC), then tune for settling margin, and re-validate order independence.
Symptom: distortion or slow recovery near supply rails in single-supply systems
Likely cause: headroom is consumed by (Vcm + signal swing + gain), pushing the amplifier out of linear range.
Quick check: sweep Vcm and output swing with the target gain; measure recovery time after overload.
Fix: re-plan VMID/Vref, keep margin for both CM and differential swing, then re-check recovery.
C) Shortlist buckets (starting points) by Rs / channels / BW / CM environment

The part numbers below are practical starting points for datasheet lookup and bench validation. Final selection must follow the gate condition and the verification ladder.

Bucket 1) Integrated INA candidates for cost-driven multi-channel front-ends
TI INA122 TI INA126 TI INA2126 (dual) ADI AD627 ADI AD622
Use when: Rs and ΔRs are controlled, wiring symmetry is enforceable, and common-mode injection residual meets the budget.
Check first: CMRR vs frequency, CM range at target gain, output stability into RC/ADC loads, and scan settling.
Bucket 2) Discrete 2-op-amp implementations (dual op-amps + matched resistor networks)
ADI OP284 (dual) ADI OP297 (dual) ADI OP227 (dual) ADI / LT LT1002 (dual) TI OPA2192 (dual) TI OPA2188 (dual, zero-drift)
Use when: channel count is high and matched resistor networks can be placed symmetrically near the op-amps.
Design priority: resistor ratio matching + layout symmetry beat “higher specs” if ΔRs and return paths are uncontrolled.
Bench focus: CM injection residual, scan settling with the real RC/ADC interface, and humidity/leakage sensitivity.
Upgrade triggers (routing-only guidance; no deep dive here)
uncontrolled ΔRs → go 3-op-amp INA µV DC stability dominates → go chopper INA very high Rs / leakage dominates → go high-Z INA
D) Vendor / FAE inquiry template (copy-paste fields)
Provide these conditions and request curves / limits under the same conditions
  • Operating point: Gain = [ ], Vcm range = [ ] to [ ], supply = [ ], VMID/Vref = [ ].
  • Source impedance: Rs_min = [ ], Rs_max = [ ], allowable ΔRs = [ ].
  • CMRR vs frequency: provide curve with stated gain and source assumptions.
  • Input CM range: confirm linear range at target gain and output swing (near-rail behavior included).
  • Noise: en/in or input-referred noise under the intended bandwidth and source impedance.
  • Bias/leakage: Ib vs temperature; guidance for symmetric protection networks and leakage budgeting.
  • Settling: settling to [0.1% / 0.01%] under step = [ ] within window = [ ].
  • Output stability: stable region for Cload/RC/ADC loads; recommended Riso practices.
  • Overload recovery: recovery time after saturation; impact on scan period = [ ].
  • Multi-channel consistency: channel-to-channel gain/offset/drift matching recommendation and test method.
Request a simple bench confirmation plan
CM injection residual test + ΔRs sweep + scan order test + humidity/cleaning A/B test. Pass criteria: residual < X, slope < Y, channel delta < Z, drift shift < W.
Short decision tree for selecting a 2-op-amp INA versus alternative INA families Decision tree that starts with source impedance and mismatch likelihood, then checks wiring symmetry and bandwidth/settling needs, and outputs a routing choice: 2-op-amp OK or move to 3-op-amp, chopper, or high-Z INA pages. Decision tree (short) Source-R → symmetry → BW/settling → shortlist route Source-R high? or ΔRs likely NO Wiring symmetry controllable? YES BW / settling tight? scan window critical NO Go 3-op-amp INA page YES Very high Rs? leakage dominates YES Go high-Z INA page NO Go chopper INA page NO 2-op-amp OK validate residual YES 2-op-amp OK prove settling

Diagram: A short decision tree that routes selection based on source impedance/mismatch likelihood, wiring symmetry control, and scan settling constraints.

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

FAQs (2-Op-Amp INA): fast diagnostics & pass/fail criteria

Each answer is intentionally short and executable. Use the “Pass criteria” placeholders (X/Y/Z/…) to plug in system-level budgets.

Why is CMRR great on paper but terrible on my board with a 2-op-amp INA?
Likely cause Source-impedance mismatch and layout asymmetry convert common-mode interference into residual differential error (CM→DM).
Quick check Tie Vin+ and Vin− together at the connector, inject a common-mode step/sine to both, and measure the output residual (Vres). Repeat after adding ΔRs on one side.
Fix Enforce symmetry (matched input series parts, matched resistor networks, symmetric routing/return path, symmetric connector pinout).
Pass criteria With Vcm_step = Y mV (or Vcm_sine = Y mVpp), residual Vres(pp) < X mV and does not change when the cable is moved; CMRR_board = 20·log10(Vcm/Vres) > C dB over [f1..f2].
How much source-impedance mismatch (Rs+ vs Rs−) is “too much”?
Likely cause ΔRs creates an imbalance that turns common-mode into differential error; “too much” is when CM→DM residual exceeds the system error budget.
Quick check Add a known series resistor ΔR on Vin+ (then Vin−), inject the same Vcm, and record Vres; sweep ΔR until Vres hits the allowable limit.
Fix Set a ΔRs budget, then enforce it with symmetric series resistors, matched harness/connector constraints, and matched resistor networks.
Pass criteria Worst-case ΔRs (including cable + protection + PCB) produces Vres(pp) < X mV under Vcm = Y mV and keeps CMRR_board > C dB over [f1..f2].
Cable movement changes the reading—what’s the fastest way to prove it’s CM→DM conversion?
Likely cause Motion changes coupling and return paths, creating a common-mode disturbance that is converted into residual differential by imbalance.
Quick check Short Vin+ and Vin− together at the connector (true zero differential), then move the cable; any output change is CM→DM (not sensor signal). Repeat with intentional ΔRs to amplify sensitivity.
Fix Use twisted pair for inputs, enforce symmetric impedance, define shield termination strategy, and keep a continuous reference plane with symmetric connector pinout.
Pass criteria With Vin+ shorted to Vin− at the connector, cable motion causes output change < X mV (or < Z LSB); CM injection residual remains < X mV across the motion test.
Why does CMRR degrade at higher frequency even when DC looks fine?
Likely cause Parasitic mismatch (Cin, trace capacitance, coupling) becomes dominant and increases CM→DM conversion with frequency.
Quick check Inject a common-mode sine to both inputs and sweep frequency; plot Vres(pp) vs f to identify where mismatch/parasitics take over.
Fix Match input RCs and parasitics, route the pair tightly and symmetrically, avoid stubs, and keep equal coupling to aggressors and to the reference plane.
Pass criteria Vres(pp) stays below X mV up to f = Fmax (or meets CMRR_board > C dB up to Fmax); no frequency region shows abrupt residual spikes caused by coupling.
Which is more important for CMRR: resistor tolerance or resistor matching?
Likely cause Ratio matching between the relevant resistors dominates CMRR; absolute tolerance mainly shifts gain but does not guarantee balance.
Quick check Compare CM injection residual using discrete resistors vs a matched resistor network at the same nominal values and placement.
Fix Use matched resistor networks (ratio/spec matching), place them close together with shared thermal environment, and keep both input paths geometrically symmetric.
Pass criteria Replacing discrete resistors with a matched network improves Vres(pp) by ≥ Δ dB (or raises CMRR_board by ≥ Δ dB) and stabilizes channel-to-channel balance within Z ppm.
How do input protection resistors/diodes create extra offset in high-Rs sensors?
Likely cause Bias current and protection leakage create voltage drops through high source impedance and unbalanced protection networks, appearing as input-referred offset/drift.
Quick check Measure offset change versus temperature and humidity; compare A/B with protection temporarily bypassed or replaced by a symmetric “dummy” network.
Fix Keep protection symmetric, choose low-leakage clamps, limit series values to the minimum required, and provide a defined bias return path to avoid floating nodes.
Pass criteria Protection-induced input-referred offset < X µV and added drift < Y µV/°C across the intended humidity range; A/B bypass does not change offset by more than Z µV.
Why do multi-channel scans show channel-to-channel “memory” or slow settling?
Likely cause The output has not settled to the required error before sampling, or overload recovery is too slow, often worsened by RC/ADC loading.
Quick check Change scan order and dwell time; measure sample error vs time after a channel step; “order dependence” indicates insufficient settling.
Fix Add settling margin (longer dwell, smaller RC, or buffering), and stabilize the output path (Riso/RC placement) before tuning for speed.
Pass criteria For the worst-case channel step, settling error at the sampling instant < X LSB (or < X ppm) and scan-order dependence < Z LSB at dwell = T.
INA output rings only when connected to the ADC—how to isolate stability vs kickback?
Likely cause The ADC sampling network looks like a switched capacitive load (kickback), and/or the amplifier is unstable with the effective capacitance and series impedance.
Quick check Test three cases: (1) ADC disconnected, (2) ADC connected but sampling clock off, (3) ADC sampling active. If ringing appears only in (3), kickback dominates; if (2)/(3), stability dominates.
Fix Add/adjust Riso, move Cfilter to the ADC side of Riso, and validate phase margin with the real load; use a buffer if the settling window is tight.
Pass criteria Overshoot < X% and ringing decays below X mV within T; ADC-connected noise/spurs at fs (and harmonics) stay below the system spur limit.
Near-rail operation causes distortion—how to budget headroom correctly?
Likely cause Single-supply headroom is exhausted by the combination of Vcm + amplified differential swing + output swing limits, causing nonlinearity and slow recovery.
Quick check Sweep Vcm across the expected range while holding a fixed differential input; monitor output error/distortion and overload recovery time near rails.
Fix Re-center VMID/Vref, reduce gain, increase supply headroom, or select a device with wider input CM range and stronger output swing under load.
Pass criteria Across Vcm range, linear error < X ppm (or < X LSB), no clipping at worst-case swing, and overload recovery < τ within the scan window.
Why does temperature/humidity make offset drift worse in high-impedance wiring?
Likely cause Leakage paths (contamination, flux residue, moisture films) create unbalanced input currents; with high Rs this becomes large offset and drift.
Quick check Compare offset before/after cleaning and drying; run a short humidity soak and monitor offset shift; check whether guard traces reduce sensitivity.
Fix Add guarding on high-impedance nodes, increase creepage/clearance, enforce cleaning process, and use conformal coating where required.
Pass criteria After humidity soak, offset shift < X µV and returns within T after drying; cable-touch sensitivity and CM injection residual remain within the same limits.
How to do a quick common-mode injection test without special equipment?
Likely cause A board-level CM injection test reveals CM→DM conversion from mismatch and asymmetry, which is the dominant failure mode for 2-op-amp INAs in the field.
Quick check Use a function generator and two equal resistors (e.g., 10 kΩ) to drive the same signal into Vin+ and Vin− (common-mode). Measure Vres at the output and sweep frequency.
Fix Turn this into a standard bring-up test: repeat with ΔRs sweep, cable configurations, and scan activity to isolate the dominant contributor.
Pass criteria With Vcm = Y mVpp, Vres(pp) < X mV over [f1..f2]; computed CMRR_board > C dB and remains stable across cable and scan conditions.
When should a 2-op-amp INA be replaced by a 3-op-amp or chopper INA?
Likely cause The application violates the assumptions that keep 2-op-amp INAs stable in the field: uncontrolled ΔRs/symmetry, harsh common-mode, or µV-level DC stability requirements.
Quick check If CM injection residual cannot be reduced below X without unrealistic ΔRs constraints, or if humidity/temperature drift dominates even after guarding/cleaning, the architecture is the limiter.
Fix Route selection: uncontrolled mismatch → 3-op-amp INA; µV DC stability → chopper INA; very high Rs/leakage dominated → high-Z INA.
Pass criteria After switching, CM injection residual < X mV over [f1..f2], scan-order dependence < Z LSB, and long-term drift meets the system DC budget (offset shift < W over the environment).