123 Main Street, New York, NY 10001

MFB LP/HP Active Filters: High-Q Design & Verification

← Back to:Active Filters & Signal Conditioning

MFB LP/HP filters are a production-friendly 2nd-order active filter block that delivers predictable fc and controllable Q for audio and measurement bandwidth shaping. This page turns specs into values and real-world pass/fail checks—covering tolerance, op-amp limits, noise/THD, source/load interaction, and verification from bench to production.

Intent Choose MFB confidently for a target fc / Q without drifting into other topologies.

What is MFB LP/HP (and when to use it)

Definition in one sentence

MFB (Multiple-Feedback) is an inverting, 2nd-order active filter where multiple feedback paths (R/C networks) shape a pair of poles, enabling practical control of cutoff frequency (fc) and quality factor (Q) using resistor ratios and RC scaling.

Where it sits in a signal chain

  • Bandwidth shaping: limit noise bandwidth, suppress out-of-band interferers, and stabilize downstream dynamic range utilization.
  • Selective emphasis: create controlled peaking around the corner when a mild resonance (higher Q) improves response or SNR in-band.
  • 2nd-order building block: used as a repeatable stage in anti-alias/reconstruction interfaces and measurement front ends.

Use MFB when

  • The design needs Q control (peaking/selection) beyond a purely “flat” 2nd-order response, while keeping component ratios practical.
  • The corner is in a region where op-amp phase margin and linearity can be met with an appropriate amplifier choice.
  • The system can accept an inverting stage (sign inversion is either irrelevant or compensated elsewhere).
  • Audio/measurement chains need predictable shaping with clear bench verification hooks (magnitude/phase, step response, THD/noise).

Avoid (or isolate first) when

  • The source has high or uncertain source impedance and cannot be buffered; source-Z interacts with the inverting input network and shifts fc/Q.
  • The load is variable/capacitive and must be driven directly; plan for output isolation or a buffer to avoid peaking/instability.
  • The application requires multiple simultaneous responses (LP/HP/BP/notch at once) or wide tuning range; that belongs on the multi-response/tunable pages.

Quick decision rules (fast, practical)

  • Need higher Q (controlled peaking / narrower transition) → choose MFB.
  • Need the simplest unity-like active filter and Q is modest → use the simplest topology page (link below).
  • Need tunable/multi-output behavior → use the state-variable/tunable pages (link below).
  • Need higher order response shaping → use cascaded biquad staging (link below).
MFB LP/HP family Two side-by-side block-style schematics showing MFB low-pass and high-pass variants with labeled nodes and key components. MFB 2nd-Order Family: LP and HP share the same “inverting + multiple feedback” core Labels kept minimal: Vin, Vout, Rin, Rf, C1/C2, Vref MFB Low-Pass (LP) MFB High-Pass (HP) op-amp + op-amp + Vin Rin Vref Vout Rf C1 C2 Vin Rin Vref Vout Rf C1 C2 Next: treat fc as an RC scale, and Q as a feedback ratio “knob”.
Diagram: LP and HP variants share the same core; only key labels are used to keep mobile readability.
Intent Build an intuition for Q as a controllable knob, and recognize the cost of pushing it higher.

Intuition: why MFB gives better Q control

Q in practice (what can be observed on the bench)

  • Frequency domain: higher Q produces a stronger corner peaking or a sharper transition.
  • Time domain: higher Q tends to increase ringing and lengthen settling after a step.
  • Sensitivity: higher Q amplifies the effect of tolerances, parasitics, and op-amp phase delay.

Why MFB feels “ratio-friendly”

MFB value picking naturally separates into two knobs:

Knob #1: fc (scale)

fc is largely set by the RC time-constant scale. Choose capacitor families (C0G/NP0) and a practical R magnitude first.

Knob #2: Q (ratio)

Q is mainly controlled by feedback ratios. Adjusting ratios is typically easier than forcing extreme absolute values.

When it is more robust (and what the cost looks like)

MFB often behaves better than simpler alternatives when Q must be intentionally higher and component ratios must remain realistic. However, higher Q is never free:

  • Phase margin becomes a limiter: op-amp delay near fc shifts the effective Q and can trigger peaking/oscillation.
  • Noise gain matters: resistor noise and op-amp input noise can be amplified around the corner.
  • Distortion concentrates: peaking increases internal swings at specific frequencies, stressing linearity under real loads.

Practical next step (keeps the page “engineering-first”)

  • Lock fc by choosing a stable capacitor family and a resistor magnitude that balances noise vs bias/leakage sensitivity.
  • Dial Q by ratios, then validate with AC response + step settling (both reveal Q errors quickly).
  • Reserve headroom in GBW/phase margin and THD at the target swing and load (bench conditions must match reality).
MFB knobs: fc scale vs Q ratio Two large knobs labeled fc and Q point to highlighted RC scale group and feedback ratio group in a simplified MFB diagram. Two practical knobs: fc is an RC scale, Q is a feedback ratio Keep values realistic; verify with AC + step settling at real swing/load Control panel fc scale (R×C) Q ratio (R/R) Simplified MFB core (groups highlighted) op-amp + Vin fc group RC scale Rin C Vref Vout Q group feedback ratios Rf C Higher Q increases sensitivity: verify phase margin, noise gain, and distortion near the corner.
Diagram: treat fc as a scale (RC), and Q as a ratio (feedback). Keep labels minimal for mobile readability.
Intent Align spec knobs (fc, Q, gain) with the 2nd-order template (ω0, Q, H0) and avoid sign mistakes.

Transfer function map: fc, Q, gain and sign conventions

The 2nd-order “language” used in design and verification

A practical MFB LP/HP stage is a 2nd-order block described by three parameters: ω0 (corner location), Q (peaking/ringing), and H0 (midband gain magnitude). Treat them as the bridge between system specs and component values.

ω0 (corner location)

Set by the stage’s effective RC scale. In measurement, it anchors the magnitude/phase transition region.

Q (shape + settling)

Controls corner peaking and step-response ringing. Higher Q increases tolerance and phase-delay sensitivity.

H0 (midband gain magnitude)

The intended passband gain magnitude used in budgets. Keep sign/phase separate from gain magnitude.

Sign conventions (why “simulation matches, bench looks inverted”)

MFB LP/HP stages are typically inverting. The system spec often states a gain magnitude, while instruments may display phase and complex gain. This page uses a consistent rule:

  • H0 is reported as magnitude (positive number).
  • Inversion is handled via phase (≈180°) and wiring polarity checks.
  • On single-supply designs, small-signal measurements are taken around Vref, not around ground.
Fast debug checklist (bench)
  • Confirm scope channel polarity and reference (CH1/CH2 sign, probe ground, differential vs single-ended).
  • Confirm the source output impedance and coupling (50Ω source or coupling capacitor can shift the effective input network).
  • Confirm Vref bias alignment (input/output centered at the same reference when using single-supply).

LP vs HP mapping (same knobs, different passband)

Spec / knob Low-pass (LP) High-pass (HP)
H0 (passband gain magnitude) Defined in the low-frequency passband. Verify ripple/flatness well below fc. Defined in the high-frequency passband. Verify ripple/flatness well above fc.
fc / ω0 (corner region) The transition from passband to attenuation. For Q ≠ 0.707, -3 dB may not coincide with ω0. The transition from attenuation to passband. Do not judge “gain” using DC behavior; use high-frequency passband.
Q (peaking / ringing) Higher Q can create corner peaking; confirm step overshoot and settling match system tolerance. Higher Q can cause “transition ringing” and sensitivity to parasitics; verify with AC sweep and step response.
Practical reading on plots Use magnitude + phase together: peaking reveals Q errors; phase slope hints at delay/PM issues. Use magnitude + phase together: corner depth/shape and phase transition reveal bias and loading issues.

Next, the workflow section turns these knobs into a repeatable value-picking process: pick a stable capacitor scale for fc, then tune ratios for Q and gain.

2nd-order template mapping Left block shows ω0, Q, H0; right block shows MFB component groups; arrows map ω0, Q, H0 between them. Parameter map: ω0, Q, H0 are the shared “language” between specs and an MFB stage H0 is a magnitude; inversion belongs to phase and polarity checks 2nd-order template (s-domain) ω0 corner location Reads on magnitude/phase transition region Q peaking / ringing Revealed by peaking + step settling H0 midband gain magnitude Keep sign separate (phase / polarity) map ω0 Q H0 MFB stage (component groups) RC scale group sets ω0 (corner location) Feedback ratio group shapes Q (peaking/settling) Gain definition sets H0 (magnitude) + phase separately Use ω0/Q/H0 to keep specs, simulation, and bench verification aligned.
Diagram: a minimal mapping between the 2nd-order template and MFB component groups, keeping sign/phase separate from gain magnitude.
Intent Turn specs into values + checks + pass criteria with a repeatable workflow.

Step-by-step design workflow (spec → values)

Step 1 — Define the spec boundary (inputs that cannot be guessed)

  • Filter type: LP or HP; single-supply vs dual-supply; Vref definition if biased.
  • Targets: fc, Q (or ripple/atten translated to stage targets), and H0 gain magnitude.
  • Budgets: allowed in-band noise and/or THD at the target frequency and output swing.
  • Environment: source impedance (Rs) and load (Rl/Cl), plus expected temperature range.
Output of this step

A one-page boundary sheet that lists fc/Q/H0, noise/THD limits, Rs/Rl/Cl, and Vref/supply assumptions.

Step 2 — Feasibility (confirm the target window is realistic)

  • High Q raises sensitivity: phase delay, tolerances, and parasitics shift Q and can cause peaking/instability.
  • Gain + Q increase internal swings: distortion risk rises near the corner frequency under real load.
  • Rs/Rl/Cl matter: source and load interactions can move fc/Q unless buffered or isolated.
If feasibility fails
  • Reduce Q or split gain into stages; add buffering/isolation where Rs/Rl dominates.
  • Adjust fc or choose a different topology (comparison pages are linked in H2-1 boundary).

Step 3 — Choose capacitor scale first (stability + practicality)

Capacitor choice sets both stability and how extreme resistor values must become. Use stable dielectric (C0G/NP0) for corners that must hold across temperature and production.

  • C too small → R becomes large: higher thermal noise, higher bias/leakage sensitivity, stronger parasitic effects.
  • C too large → R becomes small: heavier drive, higher current demand, stronger loading interactions.
Output of this step

A capacitor family and a target resistor magnitude window that balances noise, bias sensitivity, and loading.

Step 4 — Solve resistor ratios (fc by scale, Q by ratios, H0 by definition)

  • Start from the mapped targets (ω0/Q/H0) and compute an ideal set of ratios.
  • Quantize to E24/E96 while preserving ratios (Q is ratio-sensitive) and keeping R magnitudes in the window from Step 3.
  • Record the ratio error and expected impact (used directly in Monte-Carlo and guardband decisions).
Output of this step

A purchasable BOM (R/C values) plus a short “ratio error” note for Q and midband gain.

Step 5 — Op-amp check (pass/fail before spending time on layout)

Dynamic behavior
  • GBW and phase margin at/above the corner (Q magnifies phase delay errors).
  • Slew rate and output settling at the target swing and frequency.
Noise + bias sensitivity
  • Input noise (en/in) vs the resistor magnitude window.
  • Input bias current and drift vs expected offsets when biased at Vref.
Linearity under real load
  • THD at the target frequency, swing, and load (not a convenient datasheet condition).
  • Output drive and headroom on the chosen supply and Vref.
Output of this step

A short amplifier shortlist with “must meet” conditions tied to the boundary sheet.

Step 6 — Simulate, layout, verify, and guardband (close the loop)

Simulation set
  • AC magnitude/phase (read ω0/Q behavior).
  • Noise (in-band integrated noise tied to the budget).
  • Transient (step overshoot/settling reveals Q errors).
  • Monte-Carlo (fc/Q distribution for production viability).
Bench verification (same as production intent)
  • Magnitude/phase vs frequency (corner shape + phase slope).
  • Step response (overshoot + settling time).
  • THD/IMD at target frequency and swing under real load.
  • Noise measurement with defined bandwidth integration.
Pass criteria template (fill from the system budget)
  • Corner: fc within ±X% and peaking within ±Y dB.
  • Time domain: overshoot < Z% and settling < T ms.
  • Distortion: THD < A dB at ftest and Vout swing.
  • Noise: in-band RMS < N (defined BW and weighting).

Production guardband should feed back into the boundary sheet: adjust ratios, choose tighter components, or reduce Q/gain to keep the distribution inside pass limits.

Spec to verification workflow A one-page flowchart with blocks from Spec to Production guardband, including simulation and bench verification, with a feedback loop. Repeatable workflow: Spec → C scale → R ratios → Op-amp check → Sim → Layout → Bench → Production guardband Each block produces an artifact: boundary sheet, BOM, shortlist, plots, review checklist, pass report, and guardband Spec boundary sheet Choose C scale C family + R window Solve R ratios BOM + ratio notes Op-amp check shortlist Sim AC / noise / MC Layout review checklist Bench verify plots + report Production guardband feedback: update boundary sheet A workflow is only complete when guardband closes the loop back into the spec assumptions.
Diagram: the workflow produces concrete artifacts (boundary sheet, BOM, shortlist, plots, checklist, pass report) and closes the loop with production guardband.
Intent Keep fc and Q stable across tolerance, temperature, and build variation—especially at higher Q.

Component scaling & tolerance: keeping Q and fc stable

Why higher Q “amplifies” component error

Q is a shape parameter. When Q is higher, small ratio drift in the feedback network translates into larger changes in peaking, ringing, and the phase transition region. The stage becomes more sensitive to parasitics and thermal gradients that slightly disturb ratios.

Ratio error → shape error

fc mostly follows RC scale, while Q mostly follows ratios. Ratio drift shows up as corner peaking changes and longer settling.

Parasitics become “visible”

In high-Q designs, small capacitance at the inverting node and asymmetry in routing can shift Q and peak gain even when nominal values are correct.

Temperature changes ratios, not only fc

Different materials, packages, and placement create mismatch in drift. The result is Q and peaking dispersion across units and temperature.

Part choices and layout tactics that hold Q

Capacitors first (stability matters)
  • Use C0G/NP0 where corner stability is required.
  • Prefer consistent dielectric and package for matched pairs.
  • Keep inverting-node capacitance low and predictable.
Ratios next (matching beats “tight everywhere”)
  • Use resistor networks for ratio-critical parts when possible.
  • Use thin-film/precision resistors for key ratio legs.
  • Spend tolerance budget on ratio-critical components, not on every part.
Thermal and symmetry layout
  • Place ratio parts close together to share the same thermal environment.
  • Route the inverting-node network compactly; avoid long stubs and layer changes.
  • Keep sensitive nodes away from switching edges and guard with a quiet reference plane.

Monte-Carlo checklist: what distributions actually matter

Focus on spread and tails, not only averages. A stable design is one where the worst-case units remain inside the system’s shape and settling budgets.

fc drift (mean + spread)

Track shift direction and 3σ range; confirm the corner remains inside the allocated budget window.

Q distribution (shape + tails)

Inspect whether Q is skewed and whether tails create excessive peaking or slow settling in a small fraction of units.

Peaking and phase corner

Track peak gain and the phase-transition region. These reveal ratio sensitivity and parasitic-driven instability risk.

Fast isolation tactic

Run a baseline Monte-Carlo, then repeat with one critical ratio leg exaggerated. The dominant contributor becomes obvious without requiring long derivations.

Guardband: converting “target Q” into “production Q”

First choice: design for margin

When the system allows, reduce Q or split gain so the distribution stays inside peaking and settling budgets under tolerance and temperature.

If high Q is required: match before tightening everything

Use matched networks and thermal co-location to shrink random ratio spread. This usually beats pushing every part to the tightest tolerance.

When needed: add calibration hooks

Provide a trim point (digital pot / resistor strap / stored coefficients) so production can re-center peaking and corner location without over-costing passive components.

Pass criteria template (fill from the system budget)
  • Corner: fc stays within ±X% across tolerance and temperature.
  • Shape: peaking stays within ±Y dB and step ringing settles within T.
  • Phase: the transition region shift stays below Z for the system’s timing/latency goal.
Tolerance to Q and fc distribution funnel Left shows tolerance inputs; middle shows simplified distributions for fc and Q; right shows recommended actions: matching, calibration, or lowering Q. Tolerance funnel: small input variations spread fc/Q, high-Q makes the spread more visible Focus on distribution tails: peaking and settling failures usually live there Inputs Distributions Strategies R tolerance / ratio Q is ratio-sensitive C tolerance / drift fc scale stability Parasitics / layout inverting node risk Thermal gradient ratio drift across T fc spread check mean + tails Q spread watch peaking tail Match networks + thermal co-location Calibrate trim / straps / coefficients Lower Q split gain / add stage margin shrink tails
Diagram: tolerance and parasitics spread fc/Q; stable designs minimize tails through matching, calibration hooks, or margin (lower Q / split gain).
Intent Prevent the classic MFB failure mode: values compute fine, but the op-amp is the limiting factor.

Op-amp requirements for MFB (GBW, noise, distortion, headroom)

GBW and phase margin (high Q magnifies phase delay)

In MFB, the corner region is where phase behavior matters most. Higher Q increases sensitivity to phase delay and can turn small loop-margin loss into visible peaking or ringing. Use the corner shape and phase slope as stability indicators, not only a single GBW number.

“Not enough” symptoms
  • Corner peaking higher than expected; Q appears inflated on the bench.
  • Step response rings longer or settles late near the corner target.
  • Some boards behave differently: parasitic variation moves loop margin.

Noise: why swapping op-amps changes the noise floor

The inverting node “sees” an effective impedance set by the MFB network. Input voltage noise (en) and input current noise (in) convert through that impedance and the noise-gain path into output noise. Resistor magnitude decisions from the component-scaling step directly affect how much in and bias terms matter.

When resistor magnitudes are larger

Current noise and bias/leakage conversion become more visible; drift and low-frequency terms can dominate.

When resistor magnitudes are smaller

Output drive and distortion often become the limiter; noise may drop but linearity can degrade under load.

Verification hook

Compare integrated in-band noise across the intended bandwidth using the same source impedance and biasing conditions.

Distortion: where THD tends to worsen in MFB stages

The corner region can stress internal nodes more than expected, especially with gain and higher Q. Under real loads, headroom limits and output current demand produce frequency-dependent distortion that does not appear under “easy” datasheet conditions.

Output swing + load

Near headroom boundaries, compression and odd-order rise can appear first around the corner and under capacitive loads.

Capacitive feedback effects

Nonlinear output stages interacting with capacitive paths can produce corner-linked distortion and unexpected peaking.

Condition mismatch traps

THD must be verified at the target frequency, swing, and load. “Great typical THD” under light load is not transferable.

Headroom and common-mode boundaries (single-supply + Vref)

On single-supply designs, signals are centered around a reference (Vref). The op-amp input common-mode range and output swing must accommodate the corner-region dynamics without clipping or asymmetric distortion. Treat Vref integrity as a signal-quality input.

Field symptoms
  • Looks fine at no-load, fails when driving an ADC or a long cable: output drive/headroom and stability under load are limiting.
  • Corner behavior changes with bias: input CM range and Vref routing/noise are coupling into the stage.

One-page op-amp checklist (MFB-specific)

Capability What to verify “Not enough” symptom
GBW / PM Corner shape, peaking, and phase slope under the intended network and load. Extra peaking; longer ringing; unit-to-unit variation tied to parasitics.
Noise (en/in) Integrated in-band noise using the real source impedance and bias conditions. Noise floor rises when swapping op-amps; drift-like behavior when R magnitude is high.
THD / linearity THD at target frequency, swing, and load (not a convenient datasheet condition). Corner-linked distortion jump; compression near headroom; sensitivity to capacitive loads.
Swing / CM range Single-supply margin around Vref; verify both input CM and output swing in the intended bias. Looks fine no-load, fails with ADC/cable; bias-dependent shape changes.
Bias / drift Input bias and drift impact with the chosen resistor magnitude window; confirm offset stability vs temperature. Offset shifts with part swaps; warm-up dependence; corner behavior changes over temperature.
Op-amp capability quadrant for MFB Four quadrants around a central op-amp block: GBW/PM, Noise, THD, Swing/Headroom. Each quadrant includes a short symptom tag for insufficient capability. Op-amp capability map (MFB): each weakness shows up as a specific bench symptom Use symptom tags to prioritize which spec is the true limiter Op-amp (real conditions) corner behavior GBW / Phase margin stability at the corner symptom: peaking / ringing Noise (en / in) set by effective node impedance symptom: noise floor up THD / Linearity swing + load + corner stress symptom: THD jump Swing / Headroom single-supply + Vref margins symptom: clip / bias shift
Diagram: a box-diagram “capability map” that links each op-amp requirement to a concrete bench symptom in MFB stages.
Intent Explain why bandwidth shaping can improve or worsen total in-band noise, and how to control the dominant contributors.

Noise budget: from resistors to total in-band noise

Noise sources that appear at Vout (stage-only view)

This section treats the MFB stage as the boundary. Only contributors that couple into this stage output are listed here. System-level ADC quantization and downstream reference budgets should be handled on their dedicated pages.

Resistor thermal noise

Every resistor produces noise; the MFB topology weights each resistor differently through the noise-gain path.

Op-amp input voltage noise (en)

en injects at the input pair and is shaped by the stage noise gain and the frequency response around the corner region.

Op-amp input current noise (in)

in converts through the inverting-node effective impedance. Larger resistor magnitudes make in and bias/leakage more visible.

Reference / bias noise (Vref/Vbias)

In single-supply biasing, Vref integrity behaves like a signal input. Poor reference filtering can dominate low-frequency output noise.

What MFB amplifies: noise gain and the inverting-node impedance

In MFB stages, some resistor noise terms are multiplied by the noise-gain path, and the inverting node behaves like a frequency-dependent impedance. As Q increases, corner-region weighting becomes stronger, so small changes in ratios and parasitics can shift which term becomes dominant.

Dominant pattern at higher R magnitudes
  • in and bias/leakage conversion rise at the inverting node.
  • Reference/bias noise coupling becomes easier to notice.
  • Low-frequency noise terms become harder to average away.
Dominant pattern at lower R magnitudes
  • Resistor thermal noise can drop, but output-drive stress can increase.
  • Linearity and stability under load may become the limiter.
  • en can become the main term when in conversion is reduced.
Practical takeaway

The same spot-noise number can lead to very different in-band results. The real metric is the integrated noise over the intended passband.

In-band integrated noise vs spot noise (how to measure correctly)

Spot noise answers “noise density here”

A single frequency point can look great while total integrated noise increases due to wider bandwidth or corner peaking.

In-band integrated noise answers “total noise in the passband”

Integrate the measured spectrum across the target bandwidth. Use consistent RBW, windowing, and averaging settings.

Measurement hook (repeatable)
  1. Hold gain, bias (Vref), source impedance, and load constant.
  2. Measure output noise spectrum with FFT and sufficient averaging.
  3. Integrate over the intended passband; compare configurations using the same bandwidth definition.
Common traps
  • Changing bandwidth (or RBW) between measurements and comparing results directly.
  • Letting Vref noise couple into the stage and misattributing it to the op-amp.
  • Using insufficient low-frequency resolution and masking 1/f or bias-related noise behavior.

Design actions that move the noise needle (in priority order)

Reduce effective impedance (R magnitude window)

Lower impedance reduces in conversion and resistor noise weighting, but verify output drive, distortion, and load stability.

Choose op-amp noise that matches the impedance

Smaller R often favors low en; larger R makes in and bias terms more important. Verify noise under the real corner conditions.

Control passband gain and corner peaking

Excess gain or high Q increases corner weighting and can raise in-band noise even when spot noise looks unchanged.

Treat Vref as a signal-quality input

Filter, decouple, and route Vref/Vbias to avoid injecting low-frequency noise into the MFB output.

Noise flow map (MFB stage) Multiple noise sources inject into a simplified MFB network and the inverting node; arrows show how noise reaches Vout and which term can dominate. Noise flow map: sources → nodes → Vout (dominant terms depend on impedance, gain, and Q) Use this map to identify which source becomes dominant before changing parts Vin source impedance MFB network Op-amp en / in Vout inverting node R_in R_f R_g C_1 C_2 Vref bias R noise R noise en / in Vref noise dominant: high R → in dominant: high Q → corner weight dominant: noisy Vref → LF rise
Diagram: noise sources inject through specific nodes; dominance shifts with impedance window, Q/peaking, and Vref quality.
Intent Address the real audio/measurement concern: THD/SFDR under real swing and real loads, not only the AC response.

Linearity & distortion: THD/SFDR under real loads

Distortion drivers to diagnose (before changing the topology)

Output swing headroom

As the output approaches headroom limits, compression and odd-order products rise rapidly, often first near the corner region.

Load impedance and output current

Low resistive loads increase output current demand; THD can worsen sharply with amplitude even if small-signal AC looks perfect.

Capacitive loads and stability margin

ADC inputs, long cables, and input capacitances reduce phase margin. The result can be corner-linked peaking and distortion bumps.

Why corner peaking can amplify THD risk (high Q effect)

Higher Q introduces magnitude peaking near the corner. At those frequencies, the stage (and sometimes internal nodes) sees larger effective swing for the same input level. This increases headroom stress and output-current demand exactly where loop margin is also most sensitive.

Design rule of thumb (engineering form)

Set maximum swing using the peak region, not the flat passband. Use the worst-case peaking condition as the linearity guardband anchor.

Test hooks that reveal the real limiter (THD/SFDR/IMD)

Single-tone THD sweep

Measure across frequency and amplitude, focusing on the corner and the peaking region where risk concentrates.

Two-tone IMD

Use two tones that stress the corner region; inspect intermod products for load-driven nonlinearity.

Real-load verification

Repeat with the actual load (ADC input, cable, or specified R||C). Small-signal lab conditions are not transferable.

Pass criteria template (fill with system targets)
  • Load: R||C = ___ ; bias = ___ ; swing = ___
  • THD < X dB across ___ to ___, including the peaking region.
  • No distortion “bump” larger than Y dB around the corner/peak zone.

Practical actions to reduce THD risk (in priority order)

Reduce peaking (lower Q) or re-balance gain

The fastest lever: reduce peak-region swing demand and keep the stage inside its linear envelope.

Add buffer or isolation (Riso) for capacitive loads

Isolation often stabilizes the load interface and reduces distortion bumps triggered by phase-margin loss.

Select a more linear op-amp under real conditions

Screen parts using the intended swing, frequency, and load; avoid relying on “typical THD” under light-load conditions.

Guardband using the peak region

Set amplitude limits and validation around the peaking region to prevent late-stage THD surprises.

Peaking region to THD risk map A simplified frequency response shows peaking near the corner; a highlighted risk zone marks where THD often worsens; three factor cards point to the risk zone. Peaking amplifies THD risk: a narrow frequency region often becomes the limiter under real loads Use the peak region as the guardband anchor for swing and load validation Gain f peaking region THD risk zone passband roll-off Swing margin clip / compression Load current THD rises fast Capacitive load PM loss / bump
Diagram: the peaking region is highlighted as the THD risk zone; swing margin, load current, and capacitive load commonly amplify distortion there.
Intent Explain why a clean simulation can become ringing, peaking, or oscillation on the PCB, and how to localize the injection point quickly.

Stability & interaction: source-Z, load-Z, and parasitics

Source impedance interaction (how source-Z reshapes effective Q)

In an MFB stage, the source is not “outside” the loop. Source impedance couples into the inverting-node effective impedance, which can shift the corner behavior and reshape peaking. A different generator, fixture, or series resistance can change Q-like behavior without changing the nominal R/C values.

Symptoms (signature)
  • Peaking height/position changes with source or series resistance.
  • Step overshoot changes even when the PCB stays the same.
  • Corner-region phase behavior shifts unexpectedly.
Practical actions
  • Model source-Z as a window (min/max) in simulation.
  • Validate peaking and step response across that window.
  • Use a controlled series element only when needed, and verify its side effects on noise/distortion elsewhere.

Load impedance and isolation (when Riso / buffer becomes mandatory)

Real loads are rarely purely resistive. ADC inputs, cables, protection devices, and probing hardware often behave like R||C. That load can reduce phase margin and create a narrowband bump near the corner. Isolation is a controlled way to decouple the loop from the load without redesigning the filter.

Trigger conditions
  • Downstream behaves like R||C (ADC, cable, clamp network).
  • Response changes with probe type or cable length.
  • Ringing frequency is stable and repeats across boards.
Priority fixes
  • Add Riso near the output pin and sweep its value as an A/B diagnostic.
  • Use a buffer stage when load variation is unavoidable.
  • Re-check peaking and step response in the real load corner case.
Quick diagnostic rule

If peaking/ringing changes strongly with Riso, the load interface is the dominant coupling path.

PCB parasitics: four injection points that rewrite phase margin

Cin at the inverting node

Sensitive-node capacitance adds an extra pole/zero interaction near the corner and can increase peaking.

Cout at the output / load

Output capacitance reduces phase margin and can create sustained ringing or intermittent oscillation.

Trace inductance (Ltrace)

Ltrace with capacitive nodes forms a resonant bump that shows up as a narrowband peak and repeatable ringing frequency.

Ground impedance (Zgnd)

Shared return paths convert output currents into a reference shift, effectively injecting phase error into the loop.

Fast localization (A/B tests: change one variable, read the signature)

Riso sweep

Large change in ringing/peaking points to load-C coupling and phase-margin loss at the output interface.

Source series change

Peaking height/position changes point to source-Z coupling into the inverting-node effective impedance.

Probe and grounding change

A visible response change indicates measurement injection or ground impedance coupling through the return path.

What to record (minimal)

Peak height, ringing frequency, and settling time constant under each A/B condition.

Parasitic injection point map A simplified MFB block shows four parasitic injection points: Cin, Cout, trace inductance, and ground impedance; arrows link each to ringing, peaking, or oscillation symptoms. Parasitic injection map: identify where the loop is being disturbed on the PCB Cin / Cout / Ltrace / Zgnd → ringing / peaking / oscillation Vin MFB stage Op-amp Vout inverting node Cin Cout Ltrace Zgnd ringing peaking oscillation
Diagram: four common parasitic injection points and the symptom signatures they tend to produce in MFB stages.
Intent Provide a reusable engineering checklist that links bench tests to failure modes and sets up production-ready hooks.

Engineering checklist & verification hooks (bench → production)

Layout checklist (highest impact first)

Feedback and sensitive node discipline
  • Keep the inverting node short with minimal copper area and minimal vias.
  • Minimize feedback loop area; place R/C elements tightly around the op-amp pins.
  • Use guard/keepout around high-impedance nodes to reduce Cin and leakage pickup.
Return path and ground impedance control
  • Maintain continuous return paths; avoid crossing splits for the output current return.
  • Separate high-current loops from sensitive references; prevent Zgnd injection into the loop.
  • Place decoupling close; keep current loops compact and predictable.
Symmetry and parasitic matching (when applicable)
  • Match trace environments for repeatability across channels.
  • Place critical parts with consistent orientation and proximity to reduce drift mismatch.
  • Control routing inductance for output and feedback paths.

Bench checklist (what to measure and what it catches)

AC magnitude/phase

Detects peaking shifts and phase anomalies caused by source/load interaction and parasitics.

Step response

Reveals ringing frequency, overshoot, and settling behavior tied to phase-margin loss and resonances.

Noise (in-band)

Validates integrated noise across the intended bandwidth and catches Vref injection and impedance-window sensitivity.

THD/SFDR under real load

Captures load-driven distortion bumps near the corner/peaking region that do not appear in small-signal AC checks.

Pass criteria placeholders (fill with system targets)
  • Peaking < X ; overshoot < Y% ; settle < T
  • In-band noise < N ; THD < D across band (including peak region)

Production hooks (test points, loopback, calibration slots, reject bins)

Minimum test points
  • Vin, Vout, Vref (bias), and a clean reference ground point.
  • Optional: Riso option pads to select isolation window in production.
Bypass / loopback hooks
  • Bypass the downstream load for isolation diagnosis.
  • Loopback fixtures to reproduce AC/step behavior consistently.
Calibration slots (serviceability)
  • Digipot or resistor options for gain/threshold tuning.
  • EEPROM parameter slot to track calibration revision and guardband windows.
Reject-bin template (placeholders)
  • Peaking > X → bin “peaking”
  • Ringing / oscillation beyond T → bin “stability”
  • THD bump > Y in peak region → bin “linearity”
  • In-band noise > N → bin “noise”
Verification matrix: tests vs failure modes A matrix links bench tests (AC, step, noise, THD, temp) to failure modes (Q drift, peaking, osc, THD high, noise high) using icons to show coverage. Verification matrix: connect tests to failure modes (bench → production bins) Use this to choose the smallest test set that still catches the dominant failures Q drift peaking osc THD high noise AC step noise THD temp ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ✅ strong coverage ⚠️ partial / condition-dependent Fill targets with placeholders: X, Y, T, N, D (system-defined)
Diagram: a compact matrix to select the smallest verification set that still catches peaking, oscillation, THD, and noise failures.

H2-11. Applications (audio & measurement bandwidth shaping)

MFB LP/HP is most valuable as a repeatable 2nd-order building block: predictable bandwidth shaping, controllable peaking (Q), and easy reuse across audio and measurement front-ends. The goal in each application is the same: set fc, limit peak gain, and verify with time-domain + distortion + noise checks.

A) Audio: LP/HP bandwidth shaping (clean, low peaking)

  • Starter recipe: choose Q near “no peaking” (avoid resonant emphasis unless intentionally voiced).
  • Where it shines: rumble removal (HP), bandwidth limiting (LP), anti-RF “cleanup” before ADC or codec.
  • Common trap: high-Q audio shaping can create hidden peak gain → headroom loss and THD rise at the peak.
Verify (template)
  • Passband peaking ≤ +0.5 dB (or per voicing target)
  • Step response overshoot ≤ 10% (or per transient spec)
  • THD+N at worst-case peak frequency meets system target under real load

B) Measurement: bandwidth shaping for noise control and settling

  • Starter recipe: set fc from required signal bandwidth + settling margin; keep Q modest to avoid ringing.
  • Why MFB fits: stable shaping with component ratios that are practical for production.
  • Common trap: “AC looks perfect” but step settling fails because parasitics and source/load interaction shift Q.
Verify (template)
  • Step settling to ±0.1% within the measurement window
  • In-band noise (integrated) stays below the SNR budget margin
  • Peaking/phase shift stays stable across temp and tolerances (Monte-Carlo correlation)

C) “2nd-order AAF cell” in front of ADC/DAQ

  • Role: provide a predictable 2nd-order roll-off block that can be cascaded if more attenuation is needed.
  • Key trade: attenuation vs group delay/settling; avoid excessive Q that creates a peaking “alias injector”.
  • Common trap: clamp/protection or ADC kickback changes effective loading → Q shifts and ring/osc appears.
Verify (template)
  • Aliased tone/spur improvement is measurable at the sampling rate used
  • Driver remains stable with ADC input network (kickback + input capacitance)
  • Full-scale THD/SFDR meets target at the peak-gain frequency region
MFB LP/HP applications block diagrams Three common chains highlighting where an MFB low-pass/high-pass block is inserted for audio, measurement, and ADC anti-alias front-ends. Applications: place MFB as a reusable 2nd-order block Audio chain Measurement chain ADC/DAQ AAF front Source Preamp/Buffer MFB LP/HP fc / Q Codec/ADC Sensor Gain Stage MFB LP/HP noise/settle DAQ/ADC Input Protection MFB LP AA cell ADC Keep Q modest unless peaking is intentional; verify peak-gain headroom and stability with real source/load.
Three common patterns. The MFB block is highlighted because it is the repeatable “2nd-order knob” for fc/Q, noise, and peaking control.

H2-12. IC selection logic (op-amp choices + component strategy)

For MFB LP/HP, “works in simulation” is not enough. Selection must be driven by peak-gain headroom, phase/GBW margin, and noise & distortion under real load. The workflow below turns selection into a field checklist and provides example MPNs (op-amps + passives) for fast datasheet lookup.

A) Selection funnel (Must-have → Nice-to-have)

  • Must-have: THD/SFDR at target frequency & swing, GBW/phase margin at the chosen Q, and a noise profile that fits the budget.
  • Then: output drive into the real load (including cable/ADC input), supply headroom, and EMI robustness.
  • Finally: Iq/cost, package/assembly constraints, and production stability (temp/tolerance sensitivity).

B) Must-have fields to request / verify (datasheet → bench)

Field Why it matters in MFB What to check
THD/SFDR @ target Peak gain can push swing/loop stress at one frequency. THD vs frequency, swing, and load; not only “1 kHz, 2 Vrms”.
GBW & phase margin Higher Q amplifies phase sensitivity and peaking. Margin across temp/process; stability with feedback capacitors.
en / in noise Inverting node impedance shapes how noise is amplified. Noise at low-f (1/f) and in-band; match with resistor scale.
Output drive & capacitive load Load can shift phase and cause ringing/osc. Stable drive into worst-case Cload; consider Riso/buffer policy.
Swing / headroom Peak gain consumes headroom; clipping is frequency selective. Output swing vs load; input common-mode constraints (if single-supply).
Pass criteria (starter template)
  • No unexpected peaking shift beyond production tolerance expectation
  • Step overshoot/settling meets window across worst-case source/load
  • THD/SFDR meets target at the peak-gain frequency region
  • Integrated noise meets SNR margin with the chosen resistor scale

C) Example MPNs (fast lookup) — op-amps + passives

Op-amps (audio/measurement focus)
  • Low-noise / low-THD (dual): TI OPA1612AIDR, TI OPA1602AIDR, TI OPA1678IDR
  • FET/JFET input (good when resistor values are higher): TI OPA1652IDR (dual), TI OPA1656IDR (single), TI OPA1642AIDR (dual)
  • High-speed / wideband option: ADI ADA4898-2YRDZ-R7 (dual; check supplies & headroom policy)
  • Precision (DC/low-frequency measurement): TI OPA189IDR (single; validate distortion if used in audio band)
  • Reference-grade “general precision”: ADI ADA4077-2ARZ-R7 (dual; confirm bandwidth/Q feasibility)
Tip: choose resistor scale to match input type—bipolar-input parts like lower impedance; FET/JFET parts tolerate higher impedance with lower bias impact.
Resistors (thin-film, production-friendly)
  • Vishay Dale 0805 0.1%: TNPW080510K0BEEA (example value 10 kΩ; match values per design)
  • SUSUMU 0805 0.1%: RG2012P-103-B-T5 (10 kΩ; stable ratio networks for Q control)
For high Q, matched ratios matter more than absolute. Keep related R parts close for thermal tracking.
Capacitors (C0G/NP0 for fc/Q stability)
  • Murata C0G 0603 1 nF 50 V 1%: GRM1885C1H102FA01D
  • Murata C0G 0603 10 nF 50 V 5%: GRM1885C1H103JA01D
  • TDK C0G 0603 10 nF 50 V 5%: CGA3E2C0G1H103J080AA
Avoid high-K dielectrics for the timing caps in the core network; Q and fc stability degrade with voltage/temp.
Op-amp selection funnel for MFB LP/HP A must-have to nice-to-have funnel showing the order of checks: THD/SFDR, GBW/phase margin, noise budget, swing/headroom, then power/cost/packaging. Selection funnel: lock “must-have” first Must-have: THD/SFDR @ target + real load Must-have: GBW / phase margin at chosen Q Must-have: noise budget (en/in + resistor scale) Nice-to-have: swing, Iq, EMI, package, cost Order matters: peaking creates hidden headroom and distortion risk.
The funnel prevents “datasheet cherry-picking”: lock THD/SFDR and stability first, then optimize power/cost.

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

H2-13. FAQs (MFB LP/HP) — troubleshooting & production criteria

These FAQs close common “simulation vs bench” gaps for MFB low-pass/high-pass filters. Each answer is fixed to a 4-line, measurable structure: Likely cause / Quick check / Fix / Pass criteria.

Q1 Why does the measured Q peak higher than simulation?
Likely cause: tolerance/ESR/parasitics shift poles; finite op-amp phase margin raises peaking.
Quick check: measure actual R/C values; repeat with a low-C 10× probe; compare to Monte-Carlo (same tolerances).
Fix: use C0G/NP0 timing caps (e.g., GRM1885C1H102FA01D) + 0.1% thin-film resistors; reduce Q or resistor impedance; ensure GBW margin.
Pass criteria: peak gain ≤ Spec_peak_dB (starter: ≤ +0.5 dB); |Q−Qtarget| ≤ max(3σQ_MC, UQ_meas).
Q2 Why does Q collapse when I connect a real source (sensor/codec)?
Likely cause: source impedance becomes part of Rin/feedback ratios; loading changes effective pole/Q.
Quick check: buffer the source (low-Z) and re-measure; sweep a series Rs and observe Q/fc sensitivity.
Fix: include Rs in the design equations; lower Rin scale; add an input buffer or defined series/termination network.
Pass criteria: ΔQ from “ideal source” to worst-case Rs ≤ Spec_ΔQ (starter: ≤10%); |fc−fctarget| within guardband.
Q3 Why does THD worsen near cutoff even when passband gain is 0 dB?
Likely cause: peak gain/internal node swing rises near fc; op-amp loop gain drops; output current/headroom limits dominate.
Quick check: compare THD at f≪fc vs f≈fc at the same Vout_rms; reduce input level to see if THD scales with swing.
Fix: cap peaking (reduce Q); reduce resistor impedance; choose op-amps specified for THD at target freq/load (e.g., OPA1612AIDR, OPA1678IDR); add Riso 22–68Ω if driving capacitive loads.
Pass criteria: THD@f_peak ≤ Spec_THD at worst-case Vout/load; no clipping and no THD “bump” beyond limit.
Q4 Why does swapping “same value” capacitors change fc/Q a lot?
Likely cause: dielectric voltage/temp coefficient (high-K), ESR/ESL, tolerance binning, and package parasitics shift poles.
Quick check: replace timing caps with known C0G/NP0; compare fc/Q at the same DC bias and temperature.
Fix: use C0G/NP0 for the core network (e.g., GRM1885C1H102FA01D, CGA3E2C0G1H103J080AA); keep same package/voltage rating; place symmetrically and close to the op-amp pins.
Pass criteria: approved-lot fc/Q variation ≤ guardband; |fc−fctarget| ≤ max(3σfc_MC, Ufc_meas).
Q5 Why does the filter oscillate only with long cables or certain probes?
Likely cause: added capacitive load and ground inductance reduce phase margin; probe capacitance injects an extra pole.
Quick check: remove the cable; switch to low-C 10× probe; add a temporary series output resistor and see if oscillation disappears.
Fix: add Riso 22–100Ω at op-amp output; define a stable load/buffer stage; shorten sensitive nodes; improve return path continuity (no long ground loops).
Pass criteria: no sustained oscillation with worst-case cable/probe; overshoot ≤ Spec_overshoot (starter: ≤10%) and ringing decays within Spec_cycles.
Q6 How do I pick resistor magnitude (noise vs bias current vs loading)?
Likely cause: higher R raises thermal noise and Ib·R errors; lower R increases loading and can stress output drive.
Quick check: prototype two scales (e.g., 2–5 kΩ vs 10–20 kΩ) and compare integrated noise, DC offset, and THD under the same load.
Fix: use low-R scale with bipolar-input parts; use FET/JFET input when higher R is required (e.g., OPA1652IDR, OPA1656IDR); choose 0.1% thin-film resistors (e.g., TNPW080510K0BEEA, RG2012P-103-B-T5).
Pass criteria: Vn_rms(in-band) ≤ Spec_noise; bias-induced offset ≤ Spec_offset; source loading meets input/interface requirement.
Q7 Why does noise increase after “narrowing bandwidth”?
Likely cause: increased Q/peaking raises in-band gain near resonance; noise gain changes; 1/f dominates if fc moved down.
Quick check: measure noise spectrum and integrate over the same bandwidth; check if peak gain > 0 dB after retune.
Fix: cap peaking (starter: ≤ +0.5 dB); reduce resistor impedance; choose lower en/in op-amp; ensure “in-band” definition matches the system budget.
Pass criteria: Vn_rms(in-band) after change ≤ before change (or ≤ Spec_noise) with identical measurement bandwidth and setup.
Q8 Can I raise Q to get better noise rejection—what do I lose?
Likely cause: higher Q increases peaking, ringing, tolerance sensitivity, and headroom demand at resonance.
Quick check: compare step response and peak gain for Q1 vs Q2; run Monte-Carlo for Q spread and peak-gain yield.
Fix: prefer cascading modest-Q stages (controlled peaking) instead of a single high-Q stage; reserve high-Q for cases with proven headroom and stability margin.
Pass criteria: overshoot/settling meets window; peak gain within headroom margin; production yield ≥ Spec_yield under tolerance + temp.
Q9 How do I verify fc/Q quickly on the bench (no VNA)?
Likely cause: the method is missing a repeatable source/load/probe definition; fc/Q extraction is still possible with sweep or step.
Quick check: do a swept-sine with DAQ/audio interface + FFT; estimate Q from peak and bandwidth; cross-check with step damping ratio (ζ).
Fix: standardize fixture (source Z, load, probe); log {fc, peak_dB, BW, ζ}; use the same averaging/windowing across builds.
Pass criteria: repeatability Ufc/UQ within limits (starter: Ufc ≤ 1%, UQ ≤ 5% in same setup); fc/Q within guardband.
Q10 What are robust pass/fail criteria for production (Q/fc/THD/noise)?
Likely cause: criteria are not linked to Monte-Carlo + measurement uncertainty, causing false fails/escapes.
Quick check: define minimum data per unit: fc_meas, Q_meas, peak_dB, THD@f_peak, Vn_rms(in-band), swing_margin; check correlation vs known-good units.
Fix: guardband by max(3σ_MC, U_meas): |fc−target| ≤ max(3σfc, Ufc); |Q−target| ≤ max(3σQ, UQ); add A/B load test when source/load varies in field.
Pass criteria: yield ≥ Spec_yield; drifting lots are detected by fc/Q trend limits; THD/noise stay within Spec across worst-case load/temp.
Q11 Single-supply MFB: why does it clip early even with “RRIO” op-amp?
Likely cause: RRIO swing is load-dependent; resonance peak consumes headroom; output current limit increases distortion near rails.
Quick check: measure Vout at f_peak; compare to output swing vs load curves; repeat with lighter load or added Riso.
Fix: bias around mid-supply (VOCM policy); reduce peaking/Q; increase supply (or add small negative rail); pick parts with proven swing at load (e.g., OPA1656IDR, OPA1678IDR — verify swing curves); add a buffer if needed.
Pass criteria: no clipping at worst-case f_peak and Vout; THD does not spike near rails; swing margin ≥ Spec_margin.
Q12 How do I guardband Q across temperature without overdesigning?
Likely cause: tempco mismatch in R/C + op-amp drift shifts Q/fc; high-Q magnifies small drifts.
Quick check: temp-sweep pilot units; extract Q(T), fc(T); compare to Monte-Carlo + drift assumptions.
Fix: use matched thin-film networks + C0G/NP0; keep critical parts thermally coupled; prefer modest-Q cascades; add trim option pads (parallel resistor footprints) for production centering.
Pass criteria: Q and fc stay within limits across Tmin–Tmax: |Q(T)−Qtarget| ≤ Spec_Q(T); |fc(T)−fctarget| ≤ Spec_fc(T).