123 Main Street, New York, NY 10001

Reconstruction & Anti-Image Filters for DAC Outputs

← Back to:Digital-to-Analog Converters (DACs)

A reconstruction / anti-image filter is a system-level contract: it must suppress DAC images and keep amplitude/phase (and group delay) predictable under the real driver, load, and layout conditions. The goal is not a “pretty” schematic curve, but repeatable SFDR/EVM/THD improvement that survives measurement setups and production variation.

What this page solves

This page focuses on the DAC reconstruction / anti-image filter: the analog stage that converts discrete updates into a clean continuous-time waveform by controlling images, ZOH roll-off, stopband leakage, and group delay. The goal is to turn “my waveform looks bad” into numeric filter requirements, a buildable topology, and a repeatable test plan.

Typical symptoms this page fixes
  • Images / spurs too high near Fs − BW, failing SFDR/ACPR/EVM targets even when the DAC datasheet looks fine.
  • Stair-step “roughness”, overshoot, ringing, or long settling after large code changes (major-carry events).
  • Passband amplitude/phase not flat, causing waveform distortion, pulse smearing, or modulation quality loss.
  • THD worse than expected because the external network (filter + driver + load + parasitics) dominates system distortion.
Deliverables (what to leave with)
  1. Requirement set: BW, transition band, passband ripple, stopband attenuation at the first image, group-delay ripple, and allowed phase error.
  2. Topology choice: LP vs BP, passive vs active, differential implementation path, and realistic order/complexity range.
  3. Interaction checklist: driver stability, load impedance, parasitics, and measurement fixture sensitivity.
  4. Verification plan: frequency response + time response + “system metrics before/after” (SFDR/ACPR/EVM/THD/group delay).
  5. Debug routing: symptom → likely root cause → fastest confirmation measurement → corrective action.
Out of scope (linked, not expanded here)
DAC reconstruction filter scope map Block diagram showing DAC, output driver, reconstruction filter, and load with key concerns: images, ZOH zeros, stopband, and group delay, plus measurement outcomes. Images ZOH zeros Stopband Group delay DAC Output Driver Reconstruction LP / BP Filter Load / Next Measure outcomes SFDR ACPR EVM THD Group delay

The spectrum reality: ZOH, images, and why reconstruction matters

A DAC updates discrete codes at Fs. That sampling action unavoidably creates spectral images around k·Fs. In addition, the output is typically held between updates (zero-order hold), which applies a sinc-shaped amplitude envelope and introduces zeros at specific frequencies. The reconstruction filter exists to keep the desired band clean and to suppress what sampling must create.

A) Images are inevitable (sampling replicates the spectrum)
  • What appears: a copy of the baseband shows up around k·Fs (k = 1, 2, 3…); the first image is usually the closest and most harmful.
  • Why it matters: if the first image is not attenuated, it can dominate SFDR, break ACPR, or raise EVM even when the in-band tone looks fine.
  • Design handle: the filter must guarantee a numeric attenuation at the image region (not just “a low-pass exists”).
B) ZOH adds a sinc envelope (flatness and phase are part of “clean”)
  • What changes: the held output behaves like a sample-and-hold, causing a sinc roll-off and zeros at predictable frequencies.
  • System consequence: near the band edge (especially closer to Nyquist), “steeper filtering” can trade stopband for worse group delay, distorting pulses and degrading modulation.
  • Design handle: define passband ripple and group-delay ripple targets early, then choose a family/topology that can actually meet them.
Why “DAC datasheet only” is not enough

Many real-world failures are set by the external network (driver + reconstruction filter + load + parasitics), not by the DAC core. The next step is to convert bandwidth and waveform quality goals into numeric filter requirements: transition band, stopband targets at the first image, and allowed group-delay ripple.

Spectrum images and ZOH sinc envelope Simplified spectrum plot showing baseband, first image near Fs, axis ticks at 0, Fs/2, Fs, and 3Fs/2, plus a ZOH sinc envelope and a highlighted stopband region. 0 Fs/2 Fs 3Fs/2 Baseband 1st image ZOH sinc Stopband Images come from sampling; ZOH adds sinc roll-off; reconstruction filters define what the load finally sees.

Requirements first: turning “clean waveform” into numeric filter specs

“Clean” must become a verifiable contract. A reconstruction / anti-image filter is specified by numeric limits on passband flatness, phase / group delay, transition difficulty, stopband suppression, and time-domain settling. Without these numbers, filter order, topology, and test results will not converge.

Passband Amplitude / Phase
Spec fields
  • Fp (passband edge) and desired bandwidth (BW).
  • Ap ripple (dB, peak-to-peak) across 0…Fp.
  • Δτg group-delay ripple (peak-to-peak) across 0…Fp.
  • Multi-channel: ΔGain and ΔPhase mismatch across channels.
Impact
  • Amplitude ripple becomes in-band gain error and waveform shaping error.
  • Group-delay ripple distorts pulses, increases ISI risk, and rotates modulation phase (EVM).
  • Channel mismatch breaks phase coherence (arrays / synchronized control).
How to verify
  • Frequency sweep (VNA or swept-tone) to capture amplitude and phase.
  • Compute group delay from phase slope across the passband.
  • For multi-channel, measure relative gain/phase under the same stimulus.
Common pitfalls
  • Probe/fixture capacitance changes the passband and “creates” ripple.
  • Load impedance mismatch hides the intended response.
  • Wideband noise/jitter issues are misread as filter flatness problems.
Transition Order / Realizability
Spec fields
  • Fp (end of passband) and Fs1 (start of stopband).
  • Implied difficulty: transition width (Fs1 − Fp).
  • Implementation constraint: max practical order or allowed insertion loss.
Impact
  • Narrow transition demands high order, increasing sensitivity to parasitics and tolerances.
  • Over-aggressive transition targets often force unstable driver + filter interactions.
How to verify
  • Measure the response slope near Fp and the actual attenuation at Fs1.
  • Confirm the response under real load and with expected component tolerances.
Common pitfalls
  • Only stating “60 dB stopband” without frequency boundaries.
  • Spec assumes ideal components; real SRF/Q shifts the knee and slope.
Stopband Images / Masks
Spec fields
  • Define a target attenuation band around the 1st image: As over (Fs − BW … Fs + BW).
  • If required, add external constraints: ACPR mask or regulatory out-of-band limits.
  • State whether broadband noise above Fp must be reduced or only image tones.
Impact
  • Insufficient attenuation near Fs leaks images into the load and dominates SFDR/ACPR/EVM.
  • Over-optimizing stopband without phase limits can harm time-domain fidelity and EVM.
How to verify
  • Measure attenuation in the defined image band under the real output path.
  • Confirm with spectrum measurements: image level before/after filtering.
Common pitfalls
  • Stopband “looks good” due to FFT windowing or insufficient RBW, not actual suppression.
  • Transformers/baluns/fixtures add their own filtering and confuse attribution.
Time-domain Step / Settling
Spec fields
  • Overshoot limit (%) and ringing tolerance.
  • Settling time to X% (or to a ppm target) for small-step and large-step events.
  • Define an allowable “disturbance window” for code-change artifacts (glitch propagation).
Impact
  • Ringing and slow settling show up as visible waveform errors and control-loop disturbances.
  • Phase-oriented filters can meet frequency specs yet fail time-domain requirements.
How to verify
  • Step tests at representative code sizes (small step and major carry).
  • Measure under the final load and with realistic bandwidth probes.
Common pitfalls
  • Scope/probe bandwidth and grounding inflate overshoot and hide true settling.
  • Load changes alter Q and settling, invalidating lab-only results.
Application-to-spec priorities (keep the page non-overlapping)
Instrumentation / Measurement
  • Prioritize Δτg (group-delay ripple) and passband flatness for waveform fidelity.
  • Specify settling behavior for step-driven setpoints and calibration sequences.
  • Stopband targets focus on the first image region to protect downstream measurement bandwidth.
Hi-Fi / Audio
  • Prioritize phase consistency (low Δτg) and system THD at the output.
  • Stopband planning targets images and out-of-band noise that fold into audible artifacts in the next stage.
  • Time-domain overshoot/ringing limits prevent transient coloration.
Comms / Modulation
  • Start from the ACPR/EVM mask, then back-derive stopband requirements around the first image.
  • Keep passband amplitude/phase within limits to avoid EVM penalties from group-delay distortion.
  • Use realistic transition bands to keep order practical and stable in hardware.
From numeric requirements to topology selection Decision flow diagram mapping inputs like bandwidth, sample rate, image suppression, ACPR/EVM mask, and group delay limit to outputs like LP or BP choice, order range, passive or active, and need for equalization. Inputs BW / Fp Fs Image target ACPR / EVM mask Δτg limit Decisions Baseband? or IF Phase critical? Stopband extreme? Outputs LP or BP Order range Passive / Active Equalize? LP BP

LP vs BP vs multistage: choosing the right reconstruction strategy

Strategy selection should happen before component selection. A low-pass solution is natural for baseband waveforms, a band-pass solution is natural for narrowband IF synthesis, and a multi-stage approach avoids forcing a single analog filter to satisfy an extreme combination of steep stopband and low group-delay ripple.

LP Baseband
Advantages
  • Natural choice for DC-to-BW waveforms and arbitrary waveform synthesis.
  • Targets the first image near Fs with straightforward stopband placement.
  • Passband flatness and group delay can be shaped for waveform fidelity.
Risks
  • Too-narrow transition bands push order high and increase parasitic sensitivity.
  • High-Q sections can stress driver stability and worsen time-domain ringing.
  • Near-Nyquist use cases face stronger ZOH roll-off and phase tradeoffs.
What to measure
  • Passband ripple and group delay across 0…Fp.
  • Attenuation across the 1st image region (Fs − BW … Fs + BW).
  • Step response (overshoot/ringing/settling) under the real load.
BP IF / Narrowband
Advantages
  • Well-suited when the desired band is centered at a known f0 away from DC.
  • Can provide strong selectivity around the IF band without forcing a DC-to-BW passband.
  • Often simplifies meeting out-of-band masks around a narrow allocation.
Risks
  • Not a universal solution for arbitrary waveforms that require DC or very low frequency content.
  • Center frequency and Q are sensitive to tolerances and layout parasitics.
  • Phase/group delay through the band still matters for modulation fidelity.
What to measure
  • Amplitude/phase within the intended band (around f0).
  • Suppression of nearby images and mask-critical bands.
  • Center frequency shift across temperature and tolerance corners.
Multi-stage Split the burden
Advantages
  • Uses a gentle analog stage to protect stability and reduce the most harmful energy early.
  • Allows tighter masks with less phase damage by distributing selectivity across stages.
  • Improves robustness against tolerances by avoiding extreme single-stage Q/order.
Risks
  • Requires a clear “who owns what” allocation between stages to avoid spec gaps.
  • More interfaces mean more impedance interactions if boundaries are not controlled.
  • Measurement attribution becomes harder without a staged verification plan.
What to measure
  • Stage-by-stage response to confirm responsibility split.
  • System ACPR/EVM/SFDR before and after each stage.
  • Driver stability margin with the first (gentle) stage connected.
Reconstruction strategy comparison: LP vs BP vs multi-stage Three-lane block diagram comparing low-pass, band-pass, and multi-stage reconstruction strategies from DAC to load, with minimal labels for what each emphasizes. LP BP Multi-stage DAC LP Filter Load Flatness Images DAC BP Filter f0 Load IF band Select. DAC Gentle LP Selective stage Load Phase Mask

Filter families: amplitude flatness vs phase linearity vs stopband

Filter family choice is a priority decision: passband flatness, phase / group delay quality, and stopband steepness cannot be maximized at the same time. The most robust designs start by picking the family “personality” that matches the system goal, then selecting an implementable topology in the next step.

Butterworth
  • Personality: smooth passband amplitude; moderate phase/group delay behavior.
  • Use when: flatness matters and transition band is not extreme.
  • Watch-outs: pushing order for stronger stopband can increase ringing and sensitivity.
Chebyshev
  • Personality: steeper transition for a given order; passband ripple is the trade.
  • Use when: tighter transition/stopband goals are needed and ripple is acceptable.
  • Watch-outs: ripple becomes deterministic amplitude error and can penalize EVM/precision.
Elliptic
  • Personality: strongest stopband / steepest transition at low order; phase is often the cost.
  • Use when: mask/image suppression dominates and time-domain shape is less critical.
  • Watch-outs: phase/group delay distortion can degrade pulses and modulation quality.
Bessel
  • Personality: best phase/group delay; weakest stopband for a given order.
  • Use when: time-domain fidelity and low ringing are the primary goals.
  • Watch-outs: strong stopband targets may require higher order or staged strategies.
Quick score board (higher is better)
Family
Flatness
Phase
Steepness
Butter
Cheby
Elliptic
Bessel
Filter family trade-off map Quadrant plot with stopband steepness on x-axis and phase/group delay quality on y-axis, showing Butterworth, Chebyshev, Elliptic, and Bessel as labeled points. Stopband steepness → Phase / group delay quality ↑ Butter Cheby Ellip Bessel Phase-first Mask-first

Topologies that actually build: passive RLC vs active vs differential

After the family “personality” is selected, the next decision is how to build it in hardware. Passive networks maximize linearity but demand strong drive and stable loads; active filters make higher order practical but introduce amplifier limits; differential implementations improve immunity and even-order suppression but require symmetry and common-mode control.

Passive RLC ladder
Works when
  • Linearity and low added distortion dominate the system target.
  • The driver can supply the required current and remains stable into reactive impedance.
  • The load is known or isolated so the response does not drift with connection changes.
Three common failure modes
  • Load pulling: the cutoff/flatness changes when the load impedance changes.
  • Drive stress: distortion rises at high frequency or large amplitude due to current demand.
  • Parasitic drift: high-order/high-Q responses shift due to SRF/Q and layout parasitics.
What to check early
  • Driver output impedance and current margin across the intended band.
  • Inductor/capacitor SRF/Q and tolerance grade at the target frequency.
  • Response verification under the final load and cable/connector conditions.
Active MFB / Sallen-Key
Works when
  • Higher order is needed without a large passive network and tight L tolerances.
  • Buffering is required to reduce sensitivity to the following load.
  • The amplifier has adequate bandwidth, linearity, and stable behavior for the target band.
Three common failure modes
  • GBW shortfall: amplitude/phase deviates from the intended design near the band edge.
  • Large-signal limits: THD rises due to slew rate and output swing/current constraints.
  • Stability loss: ringing/oscillation appears with capacitive loads or cascaded stages.
What to check early
  • GBW and phase margin for the chosen topology and component ratios.
  • THD vs frequency/amplitude, and output drive margin into expected impedance.
  • Noise contribution and whether it erodes the system noise target.
Differential FDA + RC
Works when
  • Common-mode control and even-order suppression are needed for robust system performance.
  • Immunity to interference and clean return paths are required across boards/cables.
  • Multi-channel coherence benefits from symmetric differential signal paths.
Three common failure modes
  • Common-mode drift: headroom or distortion degrades because VCM is not controlled.
  • Asymmetry: mismatch and layout imbalance raises even-order distortion and IMD.
  • Return-path issues: differential pairs still need clean return paths; poor grounding raises spurs.
What to check early
  • Symmetry: matched R/C networks, mirrored routing, and controlled common-mode reference.
  • FDA stability with the RC network and the expected output load/cable.
  • Even-order distortion and IMD sensitivity vs mismatch and layout.
Buildable topology map for reconstruction filters Three-lane circuit-level block diagrams: passive differential RLC ladder, active cascaded 2nd-order MFB sections, and differential FDA with RC network and common-mode control. Passive Active Differential DAC RLC ladder L C L C Load DAC MFB (2nd) R C MFB (2nd) R C Load DAC FDA VCM RC network R C Load

Group delay and amplitude/phase matching: what matters and how to budget it

“Clean reconstruction” is often limited by group-delay ripple and channel-to-channel amplitude/phase mismatch, even when the magnitude response looks acceptable. This section turns those effects into measurable budgets and shows practical design levers and tests.

Phenomena
  • Time-domain shape: edge smear, tailing, or overshoot changes with frequency content.
  • Modulation quality: phase distortion and ISI raise EVM even if magnitude is flat enough.
  • Coherence: mismatch across channels reduces coherent combining and shifts phase alignment.
Metrics
  • Group delay ripple (Δτg p-p): specify the exact evaluation band (baseband or around f0).
  • Phase error φ(f): limit at critical band edges or sensitive regions of the spectrum.
  • Channel mismatch: ΔG(f) and Δφ(f) over frequency (not only single-point trim).
Design levers
  • Choose priorities: phase-first families/topologies trade stopband steepness for lower Δτg.
  • Stage the problem: split “stopband mask” and “low ripple” across stages to avoid extreme Q.
  • Symmetry matters: matched networks and mirrored routing often beat single-channel perfection.
Test methods
  • Sweep phase → compute τg: measure phase vs frequency with correct fixturing and loads.
  • Time-domain A/B: compare step/pulse responses for “flat τg” vs “rippled τg” behavior.
  • Relative channel tests: measure ΔG/Δφ with shared stimulus to reduce absolute reference error.
Budget workflow (from waveform requirement to filter constraints)
  1. Define the observation band: baseband span or around f0, including band-edge sensitivity.
  2. Define acceptable distortion: allowable tail/overshoot, EVM contribution, or coherent loss.
  3. Translate to limits: set Δτg and φ(f) limits across that band and between channels.
  4. Constrain the build: choose family/topology/staging that can meet Δτg without extreme Q.
Group delay ripple vs time-domain distortion Two-row comparison showing flat versus rippled group delay curves and corresponding time-domain waveforms, illustrating tailing and overshoot changes. Flat τg Rippled τg τg f τg f Vout t Vout t tail / overshoot

Interactions: DAC output, driver stability, load impedance, and parasitics

A reconstruction filter is not an isolated block. The most common “it simulates fine but measures poorly” failures come from interactions between DAC output impedance, driver stability, filter Q, load / fixture, and measurement injection.

Interaction matrix (what can go wrong and where to look first)
Block
Amplitude
Phase / τg
Stability
Spurs
DAC
Zout / compliance
phase vs load
edge drive
code feedthrough
Driver
gain flatness
phase margin
C-load risk
IMD / slewing
Filter
tolerance / Q
Δτg ripple
ringing
leak path
Load
impedance drift
group delay shift
reflection
standing waves
Measurement
fixture loss
probe C
injection
mixing paths
Failure pattern 1
  • Symptom: magnitude looks fine, but step response rings badly.
  • Interaction: driver phase margin × filter Q × load/probe capacitance.
  • Check: swap loads/probes and add isolation to see if ringing collapses.
Failure pattern 2
  • Symptom: image/spur suppression fails despite a clean simulation.
  • Interaction: fixture/transformer paths and load impedance not matching the assumed network.
  • Check: measure stage-by-stage (driver out / filter out) with the final fixture.
Failure pattern 3
  • Symptom: a spur appears/disappears with cable/hand proximity changes.
  • Interaction: parasitic coupling and return-path sensitivity causing unintended mixing paths.
  • Check: change grounding/shielding and routing to see if the spur tracks the return path.
Interaction loop around the reconstruction filter Block diagram showing DAC, driver, filter, load, and measurement with dashed arrows indicating reflection, parasitic coupling, and probe injection paths. DAC Driver Filter Load Measurement reflection parasitic probe C phase margin Q / tolerance impedance

Layout & grounding for filters: keep images down in real hardware

A reconstruction filter can meet every schematic target and still fail on the PCB due to return-path mistakes, parasitics, and coupling paths that bypass the intended transfer function. The checklist below focuses on actions that directly reduce image/spur leakage in real hardware.

Checklist: return paths & loop area
  • Minimize the high-frequency loop: DAC/driver out → filter → connector/load → return path.
  • Keep the reference plane continuous: avoid routing across plane gaps that force return detours.
  • Maintain differential symmetry: mirrored geometry, equal via count, equal reference plane.
  • Localize current return: provide a clear, close return corridor under the signal path.
Checklist: RLC parasitics & high-Q realism
  • Prevent inductor coupling: separate inductors and rotate orientations to reduce mutual inductance.
  • Keep high-impedance nodes tiny: short traces, minimal copper, no large pads around sensitive nodes.
  • Avoid SRF proximity: keep L/C operation well below self-resonance to prevent response warping.
  • Control via/stack transitions: unnecessary layer jumps add inductance and create extra resonances.
Checklist: shielding & coupling control
  • Enforce keep-out zones: keep clocks and fast digital lines away from high-Q/high-Z nodes.
  • Prevent “bypass” coupling: avoid parallelism between digital aggressors and filter nodes.
  • Use guard/ground fences where needed: create controlled E-field paths around sensitive nodes.
  • Connector return continuity: ensure shield/ground returns are adjacent to signal transitions.
Checklist: thermal gradients & multi-channel matching
  • Keep matched networks in the same thermal environment: symmetric placement and airflow exposure.
  • Separate heat sources: keep DC-DC, FPGA, and clocks away from filter matching clusters.
  • Match parts and orientation: use the same packages/tolerances and mirrored layout for pairs.
  • Plan for drift verification: re-check ΔG/Δφ after warm-up and across temperature changes.
PCB layout concept for reconstruction filters Top-down block layout showing DAC, driver, filter, and connector with keep-out zones, differential symmetry, return-path arrows, and digital/clock coupling risk. DAC Driver Filter L C L CONN DIFF SYMMETRY KEEP-OUT RETURN PATH CLOCK / DIGITAL COUPLING

Verification: what to measure (and how) for reconstruction and anti-image filters

Verification should be treated as a measurement menu: each metric needs the right instrument, connection method, pass/fail criteria, and an awareness of setup limits. Comparisons are only meaningful when the test chain and settings are held constant.

Principle 1
Same chain, same settings: only change the DUT insertion point when comparing before/after filtering.
Principle 2
Instrument limits first: confirm noise floor, linearity, and bandwidth margins before blaming the filter.
Frequency-domain
Measure
S21 magnitude/phase, stopband attenuation, image suppression.
Instrument
VNA or equivalent frequency-response setup.
Connection
Define the reference plane; use correct terminations; handle diff-to-SE only if required.
Criteria
Passband ripple, band-edge behavior, minimum stopband suppression over the defined band.
Common pitfall
Fixture/balun phase and termination mismatch can create fake peaks/notches.
Time-domain
Measure
Step/pulse response: overshoot, ringing, settling time.
Instrument
Oscilloscope with adequate bandwidth; differential probe if needed.
Connection
Use short ground; avoid long probe leads; keep termination consistent with the target load.
Criteria
Overshoot %, ring decay, and time to a defined error band (settling).
Common pitfall
Probe capacitance and lead inductance can create “measurement-made” ringing.
System metrics (before vs after)
Measure
SFDR/THD (tone), ACPR/EVM (modulated), and image levels.
Instrument
Spectrum analyzer / VSA, or equivalent FFT receiver chain.
Connection
Keep gain/range identical; compare by moving only the measurement point (pre/post filter).
Criteria
Image reduction, spur changes, and in-band noise/linearity impact at the same settings.
Common pitfall
Instrument noise floor and overload can hide improvements or create false distortion.
FFT settings (principles)
  • Hold settings constant: window, FFT size, averaging, and span must match for comparisons.
  • Control RBW equivalence: FFT-bin width changes the apparent noise floor.
  • Validate the chain: run a known reference tone to confirm linearity and stability before DUT swaps.
Verification connection diagram for reconstruction filters Block diagram showing DAC board feeding reconstruction filter and branching to VNA, spectrum/VSA, and oscilloscope with labels for termination, diff-to-SE conversion, and reference plane. DAC board Reconstruction filter Output Spectrum / VSA VNA Oscilloscope 50Ω termination reference plane diff-to-SE if needed

Production checklist & selection notes (filters, components, and vendor questions)

Production success depends on controlling component variability, parasitics, and change management. This section converts a “good filter design” into RFQ fields, incoming QC actions, and a failure triage flow that keeps image/spur performance stable across lots.

RFQ / vendor questions (copy-paste)
Ask for curves + statistics

Provide the requested evidence for the exact manufacturer PN and package. “Typical” claims without data are not sufficient for production control.

Capacitors (signal path)
  • Dielectric / type: specify (e.g., C0G/NP0 vs X7R) and package size.
  • Tolerance & TCC: provide tolerance bin and temperature coefficient (or curve).
  • ESR/ESL vs frequency: provide curves in the operating band and near band-edge.
  • DC bias / voltage derating: provide C(V) curve if dielectric is bias-sensitive.
  • Lot statistics: provide distribution (mean / sigma) for C and ESR for the production lot.
Inductors (high-Q nodes)
  • L tolerance: provide tolerance bin and measurement conditions.
  • Q vs frequency: provide curve across operating band and transition region.
  • SRF: provide minimum SRF spec and lot-to-lot variation (do not rely on typical).
  • DCR & self-heating: provide thermal rise estimate under expected ripple current.
  • Substitution rules: any alternate must match Q and SRF curves, not only L value.
Resistors (termination / damping / impedance setting)
  • Technology: specify thin-film (preferred for stability) and package size.
  • Tolerance & TCR: provide bins and drift expectations over temperature.
  • Voltage coefficient / noise: provide relevant specs if large signal swing is expected.
  • Lot traceability: require traceable lot codes for critical matched networks.
Assembly / DFM + change management
  • Package lock: do not change package size or terminal style without re-qualification.
  • PCN/PDN policy: require advance notice and data for any material/process change.
  • Approved alternates: create an alternate list with curve-based acceptance criteria.
  • ESD/surge rating (if output-exposed): require evidence for the intended stress profile.
Production engineering checklist (incoming QC + process control + triage)
Incoming QC (sample & verify)
  • Target parts: prioritize parts that set band-edge behavior and stopband floor (high-Q L/C, matched pairs).
  • Curve-based checks: record S21 magnitude/phase against a golden curve using the same fixture and reference plane.
  • Time-domain check: compare step/pulse response shape (overshoot/ringing/settling) to golden board behavior.
  • Acceptance: use defined frequency points and limits (passband ripple, band-edge, minimum stopband suppression).
Build controls (prevent hidden parasitics)
  • Placement fidelity: enforce orientation and symmetry for matched networks and differential paths.
  • Solder volume control: treat solder geometry as a parasitic element at high frequency.
  • Critical node protection: prevent rework damage and contamination around high-impedance/high-Q nodes.
  • Line audit: run periodic S21 or tone-spur comparison with fixed settings and fixed terminations.
Failure triage (fast root-cause order)
  1. Measurement chain first: termination, fixture, reference plane, and settings consistency (do not compare mismatched setups).
  2. Assembly next: placement offset, wrong value/orientation, solder bridges, rework-induced parasitics.
  3. Component lot next: swap suspect L/C with golden parts and check if S21 and spurs return.
  4. Coupling path last: investigate return-path and near-field sensitivity if behavior depends on cable/hand proximity.
Reference BOM examples (example part numbers)
Sourcing direction

The examples below are starting points for sourcing. Qualification should be based on measured curves and lot statistics for the exact value and package.

C0G/NP0 capacitors (examples)
  • Murata: GRM1555C1H101JA01D
  • Murata: GRM1555C1H220JA01D
  • TDK: C1608C0G1H101J080AA
  • Murata (RF/high-Q family example): GJM0225C1C220GB01L
High-Q inductors (examples)
  • Coilcraft: 0805CS-102
  • Coilcraft: 0603HP-56N
  • Coilcraft: 0402HP-3N9
Thin-film resistors (examples)
  • Vishay: TNPW060349R9BEEA
Alternate approval rule (recommended)
Approve alternates only when Q/SRF and ESR/ESL curves match within defined bands and lot statistics meet the acceptance window.
Production control workflow for reconstruction filters Workflow diagram showing RFQ fields, incoming QC, and failure triage as three connected stages with icons and minimal labels. RFQ fields Incoming QC Failure triage curves + stats golden compare root-cause order

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

FAQs: Reconstruction / Anti-Image Filter

Short, engineering-first answers that keep long-tail questions out of the main text. Each answer follows a consistent structure: symptom → likely causes → fast check → fix.

Why does my SFDR look worse after adding the reconstruction filter?
Symptom: Spurs rise or the floor shifts after the filter is inserted.
Likely causes: The filter changes the load/impedance environment, pushing the driver into a different linearity region, or the measurement chain (termination/reference plane/range) is no longer identical.
Fast check: Compare pre/post-filter with the same terminations and instrument settings; add a known pad/attenuator or a temporary 50 Ω termination to see whether spur levels track impedance/level.
Fix: Stabilize the impedance seen by the driver (termination, isolation resistor, damping), reduce excessive Q, and lock the measurement reference plane before re-evaluating SFDR.
How much stopband attenuation is “enough” for the first image at Fs−BW?
Quick answer: “Enough” means the first image is below the system mask (ACPR/EVM/SFDR target) with margin, not merely below a filter datasheet line.
Likely drivers: Required margin depends on signal bandwidth, modulation/spectral mask, and the receiver/instrument noise floor that may hide remaining images.
Fast check: Measure the image level at the relevant offset (near Fs−fout) using the final termination/fixture; verify it remains below the required limit across temperature and part tolerance.
Fix: Increase effective attenuation where it matters (higher order, multi-stage, or impedance control) and confirm the stopband does not collapse due to parasitics/fixture limits.
When should group delay flatness be prioritized over a steep stopband?
Quick answer: Prioritize group-delay flatness when waveform shape, modulation quality, or multi-channel coherence is the limiter.
Likely impact: Delay ripple can create ISI/edge distortion and frequency-dependent phase error even when magnitude looks acceptable.
Fast check: Compare EVM (or pulse/step fidelity) for two candidate filters; if EVM/edges worsen without a clear stopband benefit, delay flatness is being violated.
Fix: Use a phase-friendlier family (or a gentler analog stage plus system-level mitigation) and keep the impedance environment stable to preserve delay behavior.
Passive filter vs active filter: which one improves distortion more reliably?
Quick answer: Passive networks do not add active nonlinearity, but they can worsen distortion if the driver is forced into an unfavorable load; active stages can isolate impedances but introduce their own THD and stability constraints.
Fast check: Insert a known isolator (small series resistor/pad/buffer) and re-measure THD/SFDR; if distortion improves, the issue is load interaction more than “filter family.”
Fix: Choose the topology that keeps the driver in a predictable linear region (controlled termination and damping), then qualify the resulting THD with the final fixture and load.
Why does the driver oscillate only with “certain” filter values?
Likely causes: Certain L/C combinations create a higher-Q resonance or a more capacitive input, reducing phase margin only for specific values.
Fast check: Add a small series isolation resistor or a damping element (temporary) and see whether oscillation disappears or shifts in frequency.
Fix: Lower the effective Q, control the seen impedance, and avoid “hidden capacitors” from probing/fixtures that move the poles into instability.
How to measure group delay without a VNA?
Practical approach: Measure phase vs frequency using a swept tone (or chirp) with a two-channel capture referenced to the same clock, then compute delay from the phase slope.
Fast check: Focus on relative delay ripple by comparing against a short “thru” path using the same cables/fixtures.
Fix if results look unstable: Improve reference-plane definition and termination, since fixture drift often dominates delay estimates when a VNA is not used.
Why does the filter response change when probing with an oscilloscope?
Likely causes: Probe capacitance and ground-lead inductance add hidden C/L, shifting poles and increasing ringing in high-Q networks.
Fast check: Switch to a differential probe with short ground, or measure at a low-impedance point (e.g., 50 Ω output) instead of high-impedance nodes.
Fix: Design dedicated test points and keep probing out of sensitive nodes; treat measurement loading as part of the verification plan.
Should the filter be placed before or after the output transformer/balun?
Quick answer: Place the filter where it sees the impedance environment it was designed for, and where conversion elements (transformer/balun) do not dominate amplitude/phase unpredictably.
Fast check: Compare S21 and system spurs for both placements using identical terminations and reference planes.
Fix: Choose the placement that yields stable curves across cable/fixture variation, then lock the chosen termination and layout around it.
How do component tolerances translate into phase mismatch across channels?
Mechanism: L/C tolerance shifts pole/zero locations, changing the phase slope; phase mismatch grows fastest near band edges and around resonances.
Fast check: Measure channel-to-channel S21 phase (or group-delay ripple proxy) under the same termination and fixture.
Fix: Use matched/tighter-tolerance parts on phase-critical nodes, maintain symmetric layout/thermal environment, and qualify with lot statistics rather than nominal values.
What’s a practical way to tune/trim the filter in production?
Practical approach: Reserve DNP pads or split-value footprints on the most sensitive L/C positions, then trim using a small set of frequency points (band edge + a stopband checkpoint).
Fast check: Tune magnitude first (passband/edge), then confirm stopband minimum and phase behavior with the same fixture and reference plane.
Fix: If tuning is unstable, reduce Q sensitivity (damping/impedance control) so small part changes do not create large phase/stopband swings.
Why does passband ripple look worse on the bench than in simulation?
Likely causes: Source/load impedance assumptions are violated, fixture parasitics add extra poles/zeros, or real parts (Q/SRF/ESR/ESL) differ from the ideal model.
Fast check: Measure the passive network alone with controlled terminations and a defined reference plane; compare against a de-embedded (or fixture-consistent) baseline.
Fix: Correct the impedance environment, tighten the parasitic model, and use RF-grade components where SRF/Q are critical to ripple behavior.
Why does the filter “move” when switching between 50 Ω and high-Z loads?
Mechanism: The transfer function depends on the assumed load; changing the load effectively changes damping and pole/zero locations.
Fast check: Lock the termination (or add a fixed shunt/series element) and re-measure to confirm the response stabilizes.
Fix: Design for the intended load or isolate the filter from load variation using controlled termination and buffering where required.