R
Member
Group delay is one of those specs that looks simple on a datasheet and turns messy on the bench. I spent last week characterizing a bandpass filter for a receiver front end, and the measured group delay ripple was twice the datasheet number until I fixed my own setup. Notes from that session.
First, pick the right aperture. Group delay is a derivative of phase, so the aperture (frequency step) you choose directly sets the trade-off between noise and resolution. Too narrow an aperture and the trace turns into noise; too wide and you smooth away real ripple. For a filter with ~100 MHz bandwidth, I found a 1-2 MHz aperture a reasonable starting point, then I tighten it until the ripple stops changing. If the ripple keeps shrinking as you widen the aperture, you are measuring your own smoothing, not the device.
Second, calibration matters more than people expect. A full 2-port cal is the baseline, but for group delay the real trap is cable movement between calibration and measurement. I re-ran the same sweep after re-routing the test cable and got a 0.3 ns shift - larger than the ripple I was trying to measure. Fix the cables in place, use a torque wrench on the connectors, and re-check with a thru standard before trusting small numbers.
Third, know what the ripple is telling you. Periodic ripple in group delay usually means a reflection somewhere in the chain: a mismatched connector, an adapter, or the filter's own return loss interacting with the source match. I traced one stubborn 0.5 ns peak-to-peak ripple to a single adapter with 14 dB return loss; swapping it for a 20 dB part cut the ripple in half. The filter was fine - the fixture was the problem.
Fourth, separate device ripple from fixture ripple. Measure the fixture alone (thru + adapters, no DUT) and record its group delay ripple as a baseline. Anything in the DUT measurement that matches the baseline's period is suspect.
What aperture do you typically use for narrowband filter measurements, and how do you decide when ripple is real versus a setup artifact?
First, pick the right aperture. Group delay is a derivative of phase, so the aperture (frequency step) you choose directly sets the trade-off between noise and resolution. Too narrow an aperture and the trace turns into noise; too wide and you smooth away real ripple. For a filter with ~100 MHz bandwidth, I found a 1-2 MHz aperture a reasonable starting point, then I tighten it until the ripple stops changing. If the ripple keeps shrinking as you widen the aperture, you are measuring your own smoothing, not the device.
Second, calibration matters more than people expect. A full 2-port cal is the baseline, but for group delay the real trap is cable movement between calibration and measurement. I re-ran the same sweep after re-routing the test cable and got a 0.3 ns shift - larger than the ripple I was trying to measure. Fix the cables in place, use a torque wrench on the connectors, and re-check with a thru standard before trusting small numbers.
Third, know what the ripple is telling you. Periodic ripple in group delay usually means a reflection somewhere in the chain: a mismatched connector, an adapter, or the filter's own return loss interacting with the source match. I traced one stubborn 0.5 ns peak-to-peak ripple to a single adapter with 14 dB return loss; swapping it for a 20 dB part cut the ripple in half. The filter was fine - the fixture was the problem.
Fourth, separate device ripple from fixture ripple. Measure the fixture alone (thru + adapters, no DUT) and record its group delay ripple as a baseline. Anything in the DUT measurement that matches the baseline's period is suspect.
What aperture do you typically use for narrowband filter measurements, and how do you decide when ripple is real versus a setup artifact?
