PCB manufacturing PCB manufacturing
Home > Blog

VNA Port Extension: Move the Plane, Check the Result

November 17th, 2026

VNA port extension moves the electrical reference plane past a section of transmission line. Use it when the section behaves like a nearly matched line with predictable delay. A flat phase trace after correction tells you that the fitted slope is gone. It does not tell you that the connector launch, fixture ripple or loss has been removed. If the two test ports cannot mate to establish the initial two-port calibration, see the VNA Unknown Thru calibration guide before making any port-extension correction.

For a two-port PCB fixture, enter the one-way delay at each port, not the round-trip delay measured on S11 or S22. Then measure a standard you did not use to fit the correction. If that check fails the phase or amplitude budget, stop and change the measurement method before signing off the DUT.

VNA Port Extension: What Actually Moves?

A reference plane is where the instrument reports the incident and reflected waves. If you calibrate at the coax connectors, a PCB launch and its feed line normally lie inside the measured network. If you want the response at the component pads instead, define the new planes at those pads. Moving the planes changes which electrical length you report; nothing physically moves. If the production spec is defined at the board’s connector, keep that connector in the result.

RF PCB test fixture with two coaxial launches and a device position between them
RF fixture illustration. Identify the connector planes and device planes separately on the actual fixture drawing.

For reflection, the wave goes down the test section and back along the same path. For transmission, it passes once through the section at each end. This is why one entry on port 1 affects S11 by twice its delay but S21 by only its one-way contribution. Compare data at the same planes and reference impedance; otherwise raw and corrected traces describe different networks.

VNA Port Extension Calculation: One-Way vs. Round-Trip Delay

If the unwrapped S11 phase falls by 64.8° over a 1 GHz interval, the reflection takes 180 ps round trip and the port extension entry is 90 ps one way. This is a calculated example for a smooth, nearly matched fixture with a suitable reflection standard. Use several clean points across the intended band, rather than fitting two noisy endpoints.

Use one-way delay = −Δφ/(720 × Δf) for a reflection phase fit, with Δφ in unwrapped degrees and Δf in hertz; the result is seconds. At 3 GHz, removing 180 ps of round-trip delay adds 194.4° of phase to S11 before wrapping. If port 2 has a 110 ps one-way delay, S21 crosses 90 + 110 = 200 ps of fixtures and its correction at 3 GHz is +216°. Neither correction changes magnitude in delay-only mode.

PCB fixture showing 90 ps one-way delay at port 1, 110 ps at port 2, 180 ps round-trip reflection and 200 ps forward delay
In this calculated example S11 returns through the left fixture; S21 crosses both fixture sections. The instrument entries are 90 ps and 110 ps.

A useful sanity check: entering 180 ps for port 1 leaves 180 ps of excess round-trip correction. That is +64.8° per GHz of residual S11 slope in the example. If the corrected slope changes sign and is close to the original size, check for a factor-of-two error before changing the fixture.

VNA Electrical Delay vs. Port Extension vs. De-Embedding

Choose according to what must be measured. A display delay is useful for inspecting a trace; a port extension is a plane correction based on a line model; network de-embedding can remove fixture behavior that the line model cannot describe. They are not interchangeable.

Method When to use it When to switch
Electrical delay Check one trace for non-linear phase. You need to move a shared reference plane.
Port extension Move the plane along a matched line. The check short ripples or the phase slope varies sharply.
Network de-embedding Use validated fixture networks to remove mismatch, loss and delay. The model is unreliable or you can calibrate at the DUT plane.

Validate at the same device plane regardless of method. For a simulation deliverable, too much delay removal can make the response arrive before its defined time origin. See the S-parameter causality guide for how to tell an origin error from finite-band ringing or time wrap.

Manual Port Extension: Verify the Phase Slope First

  1. Define the measurement first. Mark the coax calibration planes and DUT planes on the fixture drawing. Keep the sweep band, cable position, calibration settings and raw traces in the record.
  2. Measure a known reflection at the intended DUT plane. Unwrap the phase over usable points and account for the standard’s own phase if the manual method supports it. Do not fit across an unexplained notch, wrap or abruptly changing slope.
  3. Set the one-way delay on the correct port. Use the actual unit, such as ps rather than ns. If converting a physical length, use the line’s propagation velocity, not the speed of light in air; for a dispersive line, check that a constant delay is acceptable over the band.
  4. Start with delay only. Compare raw and corrected phase and magnitude at identical sweep settings. If magnitude moved, check whether loss compensation or another operation is enabled. Then verify with a different standard.

Automatic Port Extensions: When an Open or Short Is Good Enough

On the applicable Keysight implementation, the automatic function estimates delay from an open, a short or both, with an optional loss fit. It assumes an ideal standard in this operation. A populated footprint is not an open. Even an unpopulated footprint can have fringing capacitance; a short with a long return loop adds inductance. A seemingly clean fit can include the electrical length of the standard itself.

Use standards with reproducible geometry at the intended device plane. Record the open and short estimates before averaging or accepting the result. If they differ enough to exceed your phase error allowance, inspect the termination geometry and launch mismatch, or change the fit band with justification and verify across the full required band. Do not use the same open both to fit and independently approve the correction.

Loss Compensation: What the VNA Can and Cannot Correct

For an ideal matched-line example with 0.18 dB one-way fixture loss at port 1 and 0.25 dB at port 2 at 3 GHz, the correction is +0.43 dB to S21 and +0.36 dB to S11. Those sums explain a line loss adjustment; they are not fixture specifications. A mismatched launch can interact with the DUT reflection. A smooth loss curve cannot cancel that interaction, even if it makes the average amplitude look right.

Keep the loss fit disabled unless you can verify its improvement separately. If the corrected open or short shows substantial magnitude ripple around its expected response, investigate the fixture mismatch, standard and calibration before using the data. Avoid accepting a trace simply because an instrument option shifted every sample below 0 dB. That does not show that the two-port network is physically correct.

VNA System Verification: A Check Standard You Did Not Fit

Use the following worksheet after changing a reference plane. Fill in the band, known standard, separate limits for phase and amplitude, and the measured residual for each. Use an independent check short or load for reflection and a characterized verification line or through for transmission, as appropriate. A load can check reflection magnitude and residual match; its small reflection makes it a poor phase reference. A nonzero-length through must be compared against its known delay, not a flat zero-degree trace.

Corrected short phase comparison showing an example in-budget trace and a residual ramp that exceeds the example phase budget
Illustrative phase residual comparison, not measured data. Judge the corrected trace against an independent reference and the applicable budget.
Field Example Decision
Band and test 1–10 GHz; independent short at port 1 DUT plane. Save raw and corrected S11 and the short model.
Phase residual Example limit: ±5°. Example result: +7° at 10 GHz. Hold data. Refit or change method and verify again.
Other checks Enter magnitude error and reconnection spread. Do not accept on phase alone.

If the entire ±5° phase allowance at 10 GHz were assigned to a pure delay error, S21 would permit only 1.39 ps of total delay error; S11 would permit 0.694 ps of one-way error. In a real budget, allocate part of the allowance to the calibration, standard and repeatability as well. The example is not an IPC acceptance limit; use the applicable drawing or agreed measurement procedure.

PCB Test Fixture: Where Port Extension Is Useful

Filter coupon: preserve the filter, remove the feeds

Put the DUT planes at the filter’s port pads when comparing against a pad-referenced model. Determine the one-way delay of both feed sections. Verify with a known through or line before installing the filter. Accept the result only if the reference agrees with phase and loss budgets and the measured filter passband, stopband and group delay meet the project limits. Do not fit the fixture correction on the filter passband and then use the same fit as proof of filter delay.

PCB antenna: report at the feed you intended to tune

If the matching network is specified at its antenna feed, set the port 1 plane there, leaving the antenna and intended matching elements in the measured network. Verify with a separate short or load on a matching coupon, then check the frequency and depth of S11 minima and the usable band against the antenna requirement. A delay-only correction rotates the impedance display but cannot improve return-loss magnitude. If the connector is the specified product test plane, measure and report there instead.

Mismatched connector launch: distinguish the two failure modes

If the launch is itself the product feature under test, leave it inside the DUT boundary and compare to the connector-plane mask. If it is only a fixture and its ripple dominates the error budget, validate a fixture model or calibrate at a closer plane. In both cases retain raw and processed files, calibration identifiers, port directions and the verification result. If there is no check standard or equivalent validation, label the trace as diagnostic instead of releasing it as verified device data.

VNA Port Extension FAQs

Is port extension a replacement for SOLT calibration?

No. Calibrate first at an accessible plane. The extension then moves the reference through a section modeled separately; it does not solve the same systematic error terms as calibration.

Does port extension improve S11?

Delay-only correction changes phase, not magnitude. A reported magnitude change may come from enabled loss compensation or a different processing step, not an improvement of the hardware.

Can port 1 and port 2 use different delays?

Yes. Fit and record each separately. S21 and S12 cross both sections; each reflection uses its own section twice.

Why did my open and short give different delays?

The standards may be nonideal or located at different planes, or fixture mismatch may change the fit. Inspect the geometry and compare the estimates against the phase budget.

Can I use the delay shown by a NanoVNA directly?

Check the software and firmware manual for whether the displayed value or setting represents one-way line delay, round-trip delay or a trace-level phase correction. Verify it on a known length before transferring settings between instruments.

Should I average delay across a wide band?

Only where the fixture behaves as the assumed model and the independent reference meets the required full-band residual. A narrower fitting band does not by itself validate operation outside it.

Does time gating solve the same problem?

No. Gating suppresses selected time events in the processed response. Port extension moves the reporting plane; it does not selectively remove an echo. Keep the unprocessed data either way.

What goes into the Touchstone delivery notes?

Include the original and output planes, port order and reference impedance, sweep band, one-way delay by port, loss and other processing settings, and the verification evidence.

Technical References

Custom RF PCBs With Stackup and Test Coupon Review

Ordering an RF PCB or a separate test coupon? Send EBest Circuit your intended stackup, controlled-impedance targets, launch drawing and test-plane locations before releasing the fabrication data. An early review gives your fabrication and lab teams the same geometry to reference when they compare board and coupon results.

Request an RF PCB quote from EBest Circuit with your Gerbers or ODB++, quantity and required delivery date.

S-Parameter Causality: Is the Early Pulse in Your Model Real?

November 17th, 2026

If a PCB channel model seems to respond before the input, check the reference plane, measured band and frequency step before repairing the file. A real transmission response cannot precede its excitation, but a finite-band plot can show small oscillations around a valid arrival. A late echo can also fold into negative time on a centred display. Change one setting at a time and confirm the result on an independent reference before deciding the model is noncausal.

An RF PCB coupon with coaxial connections in front of a network analyzer
Capture the measurement setup and reference planes before comparing transformed or fitted time-domain data.

What Is S-Parameter Causality?

A causal network does not respond to a future input. For a correctly referenced linear time-invariant model, the physical impulse response is zero before the excitation at the input reference plane. For a transmission path a known physical delay can give a more specific expected onset, although estimating it requires the actual path, propagation model and reference planes. A reflection at the calibrated input plane can legitimately begin near zero.

Passivity and reciprocity test different properties. The S-parameter passivity check examines whether a passive model creates net power, not whether it responds too early. A small negative group delay over a limited band is likewise not, by itself, proof of noncausality. Use the full measurement and modelling context, rather than one plot attribute.

S-Parameter Impulse Response: Why a Causal Path Can Show Pre-Ringing

An inverse Fourier transform of a measured sweep works with finite bandwidth. Limiting the spectrum multiplies it by a frequency-domain window; in time this convolves the actual impulse with the window’s time response. A sharp truncation can create sidelobes before and after a causal pulse. A softer window often suppresses sidelobes but broadens the main pulse, so nearby features become harder to separate.

Keep the time origin and original data fixed. Compare the early response with a known line or thru using the same processing and record how it changes under reasonable windows and measured spans. Small features near the main arrival that vary as expected with the window are consistent with truncation. Do not call them real PCB events or declare the file good solely because one strong window hides them.

Illustrative impulse showing sidelobes on both sides of the expected main arrival after band limiting
Schematic only, not measured data. Finite-band processing can put sidelobes ahead of the main arrival without making the real device noncausal.

Frequency Step Size: A Late Echo Can Appear at Negative Time

On a uniformly spaced frequency grid, the inverse-transform time record repeats with period T = 1 ÷ Δf. Span and step do different jobs: a larger measured bandwidth can separate closer events, while a smaller frequency step extends the record. Zero-padding or interpolating the same measured samples does not supply independent frequency points or prove that a late event is inside the measured record. If your solver needs a different frequency grid, use this S-parameter interpolation guide to compare Cartesian and polar methods against withheld measured points.

Worked example: assume a delayed echo at +8.8 ns. With a 100 MHz step, T is 10 ns and a centred display covers −5 ns up to +5 ns. The echo appears at 8.8 − 10 = −1.2 ns in that period. Re-measure the same band on a 25 MHz grid and T becomes 40 ns; the centred record goes from −20 ns up to +20 ns and can show the echo at +8.8 ns. These times illustrate ideal periodic mapping, not measured results.

A plus 8.8 nanosecond example echo appears at minus 1.2 nanoseconds in a 10 nanosecond centred period and at its positive time in a 40 nanosecond period
Keep bandwidth comparable and physically reacquire the finer grid. Do not infer additional measured time range from display interpolation.

VNA Time Domain: Three Lookalike Faults and Their Checks

Put separate tests around three questions: does the feature track the frequency window, does it move with the record period, or does it first appear during model processing? Perform the changes on a saved copy and verify instrument calibration on the actual sweep grid. Every new data record needs an identifiable setup and reference.

What you see Check that separates it What the result supports
Small features clustered either side of the main arrival Compare two reasonable windows and a known line at the same reference planes. A change in spacing or sidelobe amplitude consistent with the reference supports a finite-band artifact.
Isolated early pulse Re-measure at the same span with a finer frequency step, keeping the setup comparable. A feature moving by an amount consistent with the repeat period supports a folded response.
Entire response moves after port extension or fixture removal Compare raw and processed stages against a known path and check removed delay and sign. Hold the processed model until time origin and fixture assignment agree.
Early feature persists in a physically implausible location after controlled changes Compare independent reference measurements and validate the model method and settings. Do not dismiss it as ringing; isolate the first failing stage and do not release unverified data.

S-Parameter Reference Plane: Check the Delay You Removed

Keep a sketch from the VNA calibration planes to the DUT planes, with port numbers and the fixture on each side. Compare the untouched sweep with each processed file. On a transmission path a simple delay correction changes phase slope and shifts time. If the applied correction removes more delay than the physical fixture contributes, a correctly measured arrival can appear too early in that processed file.

For example, if an arrival is 1.4 ns from the raw reference and the documented combined fixture delay is 0.6 ns, a delay-only correction would leave about 0.8 ns in this illustrative case. Removing 1.6 ns instead would place it at about −0.2 ns. Real de-embedding can also change amplitude and reflections, so do not treat every fixture as a pure delay. Verify on a reference, and check units and port extensions before editing the DUT model.

If the delay was removed at the instrument, use the VNA port extension guide to check each port’s one-way delay and verify the shifted plane with an independent standard before judging a time-domain arrival.

DC Extrapolation: Use the Physical Low-Frequency Path

A sweep starting above DC does not establish what happens at DC. A through connection with a resistive path and an otherwise isolated series-capacitor path have different low-frequency limits. Use the schematic, DC resistance when relevant, and a suitable low-frequency reference to constrain the extrapolation. Do not assume S21 = 1 or extend the first sample flat for every PCB network.

For a serial interconnect, compare transient results under justified low- and high-frequency continuations, including any actual coupling components. For a DC-blocking filter, use a low-frequency model that preserves the open series path; a convenient flat extrapolation can create a misleading step baseline. In both cases, report which bands were measured and which were estimated. If the outcome changes beyond the project tolerance within plausible assumptions, limit what the model may be used for or remeasure.

Vector Fitting S-Parameters: Compare the Fit With Original Measurements

A well-formed stable, proper rational model with a physically appropriate nonnegative delay can be a useful causal representation. But a fit forces structure on the data. It cannot prove the real PCB matches the result, especially outside the measured band. Do not “fix” a large early pulse by zeroing the response before an arbitrary time; changing the time waveform also changes the frequency response.

For a backplane or cable launch, verify the fit against complex S-parameters, expected delay, and the transient or eye metric used by the system team. For a narrowband RF filter, preserve the wanted passband transmission and phase as well as the stopband range your fixture can establish. For a passive channel, run a separate passivity check on the resulting model and inspect the errors after any enforcement. Reject or limit a fit that meets numerical criteria only by losing a response the application depends on.

S-Parameter Quality Check: What to Sign Off Before Handoff

Use this worksheet when sending a model to a designer or accepting it from a vendor. Fill in the measured band, actual point spacing, reference planes, expected arrival, and the early-time interval used for review. State how acquisition, repeatability and processing affect the decision. There is no universal percentage of pre-arrival energy that applies regardless of bandwidth and window.

Record Evidence to include Action if missing or inconsistent
Measured sweep and origin Device and fixture IDs, planes, grid, settings, and reference device trace. Hold timing comparisons until another engineer can reproduce the origin and band.
Early feature example 100 MHz grid shows −1.2 ns; a qualified 25 MHz remeasurement confirms a corresponding echo at +8.8 ns. Record the original reading as a display wrap candidate. Confirm the actual echo on the extended record before releasing the original timing claim.
Processing and intended use Window, extrapolation, fixture removal, fit method, residuals and intended application and band. Do not generalize the fit to unqualified conditions. Refit, remeasure or set limits on use.

IEEE 370-2020 covers electrical characterization and measured-data quality for printed circuit boards and related interconnects up to 50 GHz. If invoked, apply the agreed method and derived acceptance criteria; the case values above are teaching examples, not IEEE thresholds or PCB workmanship limits.

S-Parameter Causality FAQs

Does every sample before time zero mean a noncausal PCB?

No. Check finite bandwidth, record wrap, reference plane and the measurements before judging the model.

How do I tell ringing from time wrap?

Compare windows on a fixed data set for ringing. Re-measure with a finer frequency step and similar span to test whether an event moves as a folded echo should.

Does a wider span always increase time range?

No. Time-record period is set by frequency step. At fixed point count, a wider span generally increases the step and shortens the record.

Does zero-padding fix missing measurements?

No. It may increase displayed sample density, but does not add information or replace actual low-frequency or finer-grid measurements.

Can a wrong port extension make a response appear early?

Yes. Excess delay removal can shift an arrival too far left. Recheck the fixture map and a known reference before judging the network.

Must the file contain a measured DC sample?

No, but a simulation sensitive to the DC limit needs a physically justified low-frequency continuation and a stated range of validity.

Does a causal fit prove a passive channel model is acceptable?

No. Separately check passivity, complex in-band error, physical delay and performance in the intended circuit.

Should I trim all pre-arrival samples before simulation?

Not as a first step. Find the cause before changing the waveform and verify any processed result against the original complex data.

Technical References

Custom High-Speed PCBs With Stackup and Coupon Review

Have a high-speed PCB build that depends on a trustworthy channel model? Send EBest Circuit your layout files, stackup, target impedance, connector or fixture assumptions and the coupon requirements. Request a fabrication quote and stackup review to define the build and verification scope before ordering.

S21 vs. S12: Why Your VNA Traces Disagree on an RF PCB

November 16th, 2026

If a passive PCB coupon expected to be reciprocal gives you different S21 and S12, compare the complex transmission coefficients, not just the two dB traces. Then put a known reciprocal verification device at the same calibration planes and measure it in both directions. If the reference shows the same mismatch, fix the setup before blaming the board. If the VNA agrees but the exported file does not, inspect the file and processing chain before measuring again.

Two-port RF PCB test coupon with connectors at opposite ends on a workbench
A two-port PCB coupon has a forward and reverse transmission path. Confirm both directions at the same reference planes.

S21 vs. S12: Which Direction Is Each Trace?

The first index is the response port; the second is the driven port. S21 is the outgoing wave at port 2 divided by the incident wave at port 1, with no incident wave from port 2. S12 reverses the drive and response with the same port numbers. The other port is terminated in the measurement reference impedance for the coefficient definition. Changing the drive direction does not mean renumbering the connectors on the board.

Both coefficients have magnitude and phase. Displaying 20 log10 of their magnitudes answers how much the signal is attenuated or amplified, not whether their complex values agree. Keep a port map showing the board end, cable and VNA port so another engineer can reproduce the setup after a reconnect.

Two-port diagram showing S21 from port 1 to port 2 and S12 from port 2 to port 1
Keep port labels fixed. Drive each port in turn and measure the opposite port.

Reciprocal Network: What Should and Should Not Match?

For an ordinary reciprocal two-port measured with equal real reference impedances and consistent power-wave normalization, S21 = S12 at the same frequency and reference planes. This is equality of the full complex values. The two reflections, S11 and S22, need not match: a board can have a different connector launch on each end and still transmit reciprocally. For a compatible multiport basis, the comparison is against the plain matrix transpose, not its complex conjugate.

Reciprocity is separate from passivity. A correctly specified ferrite isolator, for example, can be passive while intentionally attenuating reverse transmission more than forward transmission. A biased active stage can also be direction-dependent. Check the intended function, terminations, bias and power setting before applying a reciprocal-coupon release rule. Use the S-parameter passivity check separately if the model must also satisfy a passive power bound.

S21 and S12: Equal dB Can Still Hide a Phase Error

Illustrative values at 5 GHz: S21 = 0.50 at 0° and S12 = 0.50 at +10°. Both magnitude readings are −6.02 dB. In rectangular form, S21 is 0.5000 + j0 and S12 is about 0.4924 + j0.0868. Their complex difference has magnitude 0.0872. If you subtract only their dB values, you find zero and miss the disagreement.

Plot the absolute residual |S21 − S12| versus frequency using linear complex values. For two equal magnitudes A and phase difference Δφ its value is 2A × |sin(Δφ/2)|. Do not use a large phase swing at a very small signal level as stand-alone evidence; first establish that both measurements are above the usable noise and leakage limits. The residual is dimensionless, not dB.

Illustrative complex-plane sketch of equal 0.50 magnitudes at zero and positive ten degrees with a residual of 0.0872
Same magnitude, different phase. The chord between the two endpoints is the complex residual, not a subtraction of dB values.

VNA Calibration: Verify Forward and Reverse Before Reconnecting

  1. State the reference planes. Record cable orientation, adapters, fixture, connector condition, calibration method, sweep grid, source power and IF bandwidth. Use an applicable full two-port correction at the agreed planes, such as SOLT for appropriate coaxial standards or a qualified TRL setup for a fixture.
  2. Measure an independent reciprocal reference at those planes. An appropriate verification thru, line or attenuator should be independent of the solve and suit the band and loss of interest. A low-loss thru alone does not qualify a deep stopband. Record both phase and magnitude.
  3. Repeat the DUT without an avoidable setup change. First capture both VNA directions without physically swapping the cables. If a reversal check is needed, keep the calibrated cables and adapters fixed as far as practical, document which board end goes to which port, and recheck the reference after reconnecting. Do not interpret a reversed setup as a clean confirmation if a cable had to move substantially.

Keysight describes distinct forward and reverse terms in full two-port error correction. A good trace in one direction does not validate the other. A mismatch that appears on the reference is a reason to check the instrument path, not proof that a particular receiver or switch failed.

VNA Dynamic Range: Find Where the Comparison Stops Being Useful

In a deep stopband, the reverse trace may be dominated by instrument noise or residual leakage rather than transmission through the filter. Check a suitable terminated or isolated reference under the same sweep settings, then repeat both traces at a verified lower IF bandwidth. Noise can decrease while systematic leakage stays. If either direction remains too close to the established floor, flag the band as inconclusive rather than publishing a direction-specific isolation number.

If a stable residual remains after the noise check, use the VNA isolation calibration guide to decide whether to use the optional correction and verify it against an independent attenuator before comparing the two directions.

Observed pattern Next discriminating check Decision
Same dB, phase split in the passband Compare raw complex traces with an independent reciprocal reference at unchanged planes. If the reference shows the split, requalify the setup; do not reject the PCB.
Difference mainly near the stopband floor Check residual leakage and repeat both directions with verified measurement settings. If acceptable uncertainty cannot be shown, report the band as inconclusive.
Raw traces agree; processed file does not Re-import the raw export, then apply reference corrections and transforms one step at a time. Fix the step that introduced the mismatch rather than hiding it by copying a column.
Difference persists with a clean reference Check expected directionality, fixture removal, port maps and stimulus-dependent behavior; repeat independently. Escalate before declaring nonreciprocity on an ordinary PCB coupon.

Touchstone File: Compare Each Processing Stage

Save the instrument traces and the untouched file before renormalization, de-embedding, port extension or mixed-mode conversion. Check the frequency units, data format (RI, MA or DB), port map and real reference resistance. In conventional two-port Version 1 data the file lists S11, S21, S12, S22. Touchstone 2.1 allows an explicit [Two-Port Data Order]. Read it rather than imposing an order. Check [Matrix Format] too: a triangular file format can encode assumed symmetry and cannot independently prove that both directions were measured.

Re-import with a compatible reader and compare known complex samples against the instrument first. Then replay each processing step. A plain exchange of S21 and S12 by itself changes the sign of S21 − S12 but not its magnitude; a new nonzero residual points to another mismatch, such as a wrong column, inconsistent reference correction, grid alignment, or asymmetric processing. Never replace the reverse trace with the forward trace to make an undiagnosed problem vanish.

S-Parameter Reciprocity in Three PCB Measurement Tasks

PCB interconnect coupon

Use the raw two-direction data to qualify a passive trace and its launches. For a representative verification condition, compare trace residual over the required band and recheck the references if the ports have been disturbed. Release only if the residual meets the agreed data-quality limit and the coupon meets its own insertion-loss and reflection requirements. Different S11 and S22 can still matter to the system even if reciprocity passes.

RF filter on an assembled board

Compare the two transmission directions in the passband and establish usable measurement range in the stopband. Keep fixture terminations and any bias networks in the defined configuration. Report measurable bands separately from floor-limited bands; do not accept a stopband number simply because forward and reverse both look flat at the instrument floor.

PCB with an isolator or active RF chain

The design may intentionally have unequal transmissions. Verify the expected forward direction and reverse isolation against its specification at the specified bias, power and termination. Reversing a connectorized fixture still requires a defined port map. For a three-port device report the unused-port termination and do not infer the complete multiport behavior from a two-port subset.

VNA Measurement Uncertainty: What Goes in the Release Report?

Use this worksheet to review a new S2P file. The test plan must define frequency bands, expected network class, reporting metric, validation reference and evidence for the decision limit. A set of repeat sweeps estimates repeatability but does not by itself bound systematic errors. Have the lab include validated calibration, fixture, dynamic-range and reference-check contributions appropriate to the band.

Required evidence What to record If missing
Comparable data Port mapping, same planes, impedances, operating state and frequency grid; two measured directions. Hold the comparison. A symmetrical export is not independent evidence.
Uncertainty and usable band Calibration and independent checks, residual repeatability, receiver limits and decision rule. Flag measurements outside the validated band or level as inconclusive.
Illustrative decision at 5 GHz |S21 − S12| = 0.0872; assume a project-specific review trigger of 0.0200 for this example. 0.0872 exceeds 0.0200. Hold the file and localize the cause; this alone does not establish a faulty PCB.

The example trigger is not an IPC threshold or an instrument specification. If the report cannot show how the setup supports a limit, request the missing evidence before qualifying the file or changing the fixture.

S21 vs. S12 FAQs

Do S21 and S12 have to be the same on every passive PCB?

No. Confirm the network is expected to be reciprocal and the two measurements have comparable references. A passive isolator is a counterexample.

Can S11 and S22 differ on a reciprocal board?

Yes. Reciprocity relates exchanged transmission terms. Different launches or impedances at the two ends can give different reflections.

Why can the two traces match in dB but disagree in the file?

A dB plot omits phase. Compare the real and imaginary components, or reconstruct them from magnitude and phase before subtracting.

Does swapping the two VNA cables prove the PCB is directional?

No. You may also change cable shape, contact repeatability or calibration planes. Keep a board-end map and verify the calibrated paths.

Can a lower IF bandwidth fix S21 and S12 disagreement?

It can reduce random receiver noise. It does not undo a wrong reference plane, fixture model, or stable leakage path.

Can I use a reciprocal thru to validate reverse isolation?

A thru is a useful basic check but normally does not establish the uncertainty at the much lower transmission level of an isolation measurement.

Does a symmetric Touchstone file prove the two directions were measured?

No. A reader can fill missing entries from triangular storage. Ask for the measured full two-direction data and the export settings.

Should I average S21 and S12 to repair a file?

Keep the raw data independent. Use symmetry constraints only as a documented model decision after establishing that the network is reciprocal and understanding the original discrepancy.

Technical References

Custom RF PCB Fabrication With Stackup and Launch Review

Send EBest Circuit your RF PCB files, required impedance, connector footprint and operating band to flag stackup and launch constraints before the prototype build. Include coupon or report requirements if they are part of acceptance. Request an RF PCB quote and DFM review to agree on the build and verification scope before ordering.

S-Parameter Passivity Check: Why S21 Alone Can Miss It

November 16th, 2026

To check a passive PCB interconnect, compute the largest singular value of its full complex S matrix at each frequency, using a consistent power-normalized port basis. A value above 1 means the data predicts more outgoing power than incoming for at least one combination of incident waves. Looking only at S21—or even at every S entry separately—can miss it. Find the first file or processing step that shows the problem before using passivity enforcement.

Passive RF PCB through-line coupon with two coaxial ports for interconnect measurements
A PCB coupon is expected to be passive, but its exported data or fitted model may not preserve that property.

What Is an S-Parameter Passivity Check?

For a linear passive interconnect, no incident-wave combination can produce more total outgoing power than the incoming waves provide. In a power-normalized representation, the complex outgoing vector b equals the full matrix S times the incident vector a. The sum of squared wave magnitudes gives power in that basis. The upper bound is therefore on the ratio of the two vector norms, not on one plotted transmission trace.

With positive real reference resistances and the corresponding power normalization, check that the largest singular value σmax(S) is at most 1. Equivalently, the largest eigenvalue of SHS, where H denotes complex conjugate transpose, is at most 1. A value equal to 1 can be legitimate for a lossless mode. This article assumes positive real port references; if your tool uses complex impedances or a different wave definition, use the correct power metric or validated conversion before applying this test.

Singular Value Decomposition: A Two-Port Example You Can Check

At one frequency, take a real-valued example with S11 = S22 = 0.12 and S21 = S12 = 0.92. For a unit input at either port alone with the other port matched, total outgoing normalized power is 0.12² + 0.92² = 0.8608. That single-port test passes in either direction, and every element magnitude is below 1.

Now drive the ports in phase, sharing one unit of total incident power equally. Each incident wave has amplitude 1/√2. The two outgoing amplitudes are each (0.12 + 0.92)/√2. Their total normalized outgoing power is 1.0816. The largest singular value is 1.04, and its square gives the worst-case power ratio. The opposite-phase mode has singular value 0.80. The numbers are a deliberately nonpassive example, not measured coupon data.

Normalized outgoing power of 0.8608 for one driven port and 1.0816 for two equally driven in-phase ports
Both excitations use one unit of total incident power. An entry-by-entry screen misses the in-phase power excess.

Touchstone File: Verify the Basis Before Doing the Math

Read the actual complex values, not an S21 magnitude plot or an export with phase removed. Verify units, data encoding, file version, port order, reference resistances and whether the data is single-ended or mixed mode. A four-port file is not automatically a differential file. Do not assemble a matrix by copying an assumed order of S11, S12, S21 and S22 from text: use a compatible Touchstone reader and confirm the imported matrix against known values.

Run the check before and after any required conversion. The S-parameter renormalization guide explains how to carry the full matrix to a new reference. Correct renormalization of a passive network into another positive real power-normalized basis should not invent physical gain. A warning that first appears after import or conversion deserves a check on wave definitions, numerical conditioning and metadata.

S-Parameter Passivity vs. Causality and Reciprocity

These checks answer different questions. A file can pass one and fail another. Use only the checks relevant to the network and its intended model: an active amplifier is not a passive coupon, and a passive network need not be reciprocal.

If the separate reciprocity check fails on a coupon expected to be reciprocal, compare the original complex transmission traces before changing or averaging the file. The S21 vs. S12 troubleshooting procedure explains how to distinguish a direction-dependent setup error from a discrepancy introduced during export or processing.

If a time-domain plot shows a pulse before the expected arrival, keep the passivity result separate. Use the S-parameter causality guide to distinguish finite-band ringing, a folded late echo and an incorrect reference-plane correction before modifying the model.

Check Question it answers What a pass does not prove
Passivity Does any incident-wave combination yield excess outgoing power? Correct port mapping, fit accuracy or causality
Causality Is the response zero before excitation, with the defined planes? Power consistency; finite-band transforms can also create apparent early ringing
Reciprocity Do exchanged transmission terms agree where reciprocity is expected? Passivity or identical reflections at both ports

Nonpassive S-Parameters: Find Which Data Step Introduced the Warning

Keep three versions: the raw measurement, the de-embedded or converted data, and the fitted model. Plot or record the worst singular value against frequency for each. If the raw passive witness itself fails, recheck VNA calibration, cable stability, connection repeatability and raw data import. If only the result after fixture removal fails, review reference planes, fixture equivalence and residuals; small errors can become more significant around low-transmission or poorly conditioned regions.

If the imported samples pass but the fitted model fails, examine the fit over its intended use range, not just at the measured points. A sparse grid can miss a violation between samples, and a small average fit error does not prove passivity. For an actual PCB interconnect measurement, use the agreed verification method. IEEE Std 370-2020 concerns high-frequency electrical interconnect characterization up to 50 GHz; its public scope is not a blanket acceptance rule for every model or a numerical tolerance for this calculation.

Diagnostic flow comparing raw measurement, fixture-removed data, and the final fitted model
Start with the first stage that fails. A model-only warning is not evidence that the measured board was active.

Passivity Enforcement: Correct a Model Without Hiding Bad Data

Use enforcement only after reviewing the measurement and identifying the model problem. Save the unmodified dataset. Apply the tool’s appropriate passive fitting or model-repair method and preserve it separately from the measurement. Do not independently set every term above 0 dB to 0 dB; entries that individually pass can still violate the joint power constraint.

Check the repaired model continuously with an applicable model-level test when available, and compare insertion loss, return loss, coupled terms and response timing against the original in the decision band. Quantify the change where the design has the least margin, not just a global residual. If the correction changes a notch or consumes the error budget, refit or remeasure instead of calling it a successful repair. A software tolerance handles numerical or QA decisions; it does not change the physical bound of 1.

S-Parameter Applications: What to Check Before Releasing the File

RF PCB filter or test coupon: Apply the matrix test at the specified DUT planes across the required band. Compare the raw and fixture-removed versions, and verify that the filter’s wanted passband loss and stopband features were not moved by a correction beyond the agreed error budget.

Differential serial channel: Confirm all four physical port assignments, the pairing and the power normalization before converting to mixed mode. Test the whole represented network, not just the differential transmission block. For transient use, also check causality, the intended delay and any material regression in the channel response.

Vendor model handoff: Keep the original Touchstone file and any fitted model as separate artifacts. Reopen both in the recipient’s tool, confirm the frequency range and reference resistances, and rerun the checks used to make the release decision. Do not present a repaired fit as raw VNA data.

S-Parameter Passivity Check Report: Record the First Failure

Keep a short record of each stage and the band the model is intended to cover. The example below shows how to make a hold decision without inventing a universal limit for measurement uncertainty.

Record field What to check or write
Files, port map, planes and reference basis List raw, processed and model versions; record frequency units, ports and real reference resistances
Worst sample or failing frequency band Illustrative sample: 1.04 at 5 GHz in the processed file; power ratio 1.0816. Keep the complex matrix and identify which stage first shows the excess
Disposition and evidence Hold the suspect file for review; include raw witness, correction delta in the critical band, fit coverage and verification rerun before release

S-Parameter Passivity Check FAQs

Can negative S21 in dB still come from a nonpassive file?

Yes. S21 measures one path under one drive and termination condition. Other outgoing waves and combined input modes can make the full matrix fail.

Is a singular value of 1 automatically bad?

No. A lossless mode can legitimately have a value of 1. Small excesses near the bound require checking the full measurement and numerical uncertainty before drawing a conclusion.

Can I check passivity without phase?

Not generally. The worst-case input depends on the complex relationships among the matrix entries. Magnitudes alone do not preserve those relationships.

Does a 50 Ω reference mean all test loads must be exactly 50 Ω?

The reference determines the wave normalization, not the actual impedance of every connected load. Keep the physical termination and mathematical reference documented separately.

Why can a fit fail when all measured points pass?

The fit is a different mathematical model. It may overshoot between samples or become nonpassive in an unmeasured range despite matching the table closely at its sample frequencies.

Can an active amplifier legitimately fail this test?

Yes. An amplifier can supply energy from its bias source. Do not force its intended active model to meet an unconditional passive network constraint.

Is a successful transient simulation enough to accept the model?

No. One setup may not excite modes or frequencies that reveal a problem. Check the model, its applicable bandwidth and the actual transient response against the intended use.

Should I overwrite a vendor file after enforcing passivity?

No. Retain the original and save the corrected version separately, with a processing record and comparison at the frequencies that matter to the design.

Technical References

Custom RF PCBs With Stackup and Coupon Review Before Fabrication

Send EBest Circuit your fabrication files, stackup and transmission-line requirements before ordering. Mark your port locations, controlled-impedance targets and any coupon or measurement handoff you need so those requirements can be reviewed with the build. Email sales@bestpcbs.com to request a custom RF PCB quote.

VNA Power Sweep: Is Your DUT or Receiver Compressing?

November 16th, 2026

If the gain falls during a VNA power sweep, do not report the first 1 dB drop as amplifier compression until you check the receiver. Repeat the sweep at the same calibrated DUT input powers with a different, characterized receiver-path attenuation. If the corrected compression point stays put within the uncertainty budget, it is evidence of DUT compression. If it moves, check receiver linearity, output loading and calibration before you accept either result.

Vector network analyzer and a small RF circuit board with coaxial ports
Mark the DUT input, DUT output and analyzer input as separate power reference planes before testing.

What Is a VNA Power Sweep?

A VNA power sweep changes drive level at one frequency while measuring how the response changes. A frequency sweep changes frequency at a specified stimulus level. Use the power sweep to find where fundamental gain stops being constant; repeat it at the frequencies where the product must meet its specification. A pass at one frequency does not establish compression across the band.

For a same-frequency amplifier, record calibrated incident input power and fundamental output power at the agreed DUT planes. With consistent wave/reference definitions, gain in dB is output dBm minus input dBm. A ratio trace can show the gain trend, but an ordinary small-signal S-parameter file does not establish absolute input power or describe a nonlinear amplifier at arbitrary drive levels.

Source Power Calibration: Put the Input Level at the DUT

Calibrate or verify source power at the DUT input plane, after input cables, adapters or a bias network that the test includes. The analyzer’s programmed output power is not necessarily the incident power at that plane. For a simple matched example, a −6 dBm source setting through 2 dB of input-path loss gives −8 dBm at the DUT. Use measured or calibrated power rather than applying a fixed loss correction over a range where loss, source leveling or mismatch is significant.

Use the instrument’s specified power-calibration method and verify the relevant range and frequency. Scalar power calibration establishes levels; vector error correction addresses systematic measurement errors such as match and tracking. Changing pads or reference planes may require a different calibration. Save the settings and reference planes with each sweep. Do not treat a single unchecked power-cal point or a changed cable as proof that the full sweep axis is correct.

Receiver Compression Point: Set a Safe Power Budget

Pick attenuation and receiver range before applying RF. The analyzer’s damage limit and its linear measurement limit are different, and the lower usable power can depend on frequency, receiver range and test configuration. Check the source, both analyzer ports, the DUT, bias hardware, attenuators and any power sensor against their own RF and DC limits. Check reverse excitation as well: a full two-port measurement can drive the DUT output unless the instrument and setup are configured appropriately.

For a first estimate, suppose the maximum DUT-plane input is −6 dBm and the maximum credible gain for this example is 18 dB. The estimated DUT output is +12 dBm. If the selected receiver configuration has an illustrative linear ceiling of −2 dBm and you reserve 3 dB, aim for −5 dBm or lower at the receiver. The minimum estimated path loss is then 17 dB. With 20 dB of characterized loss, the estimated receiver input is −8 dBm. These values are arithmetic examples, not analyzer specifications. Check real maximum outputs, startup transients, attenuator rating, power dependence, and the lower noise limit before approving the setup.

Signal chain marking the DUT input, DUT output and VNA receiver input on either side of the output attenuator
Correct receiver-path loss back to the DUT output plane. For the comparison, keep the calibrated DUT input drive unchanged.

Gain Compression Measurement: Establish a Linear Reference

Find several low-drive points with repeatable gain above the measurement floor, and use the reference method required by the test plan. Starting at the sweep’s lowest point is not enough if that point is noisy. Define compression as the amount the measured fundamental gain falls below the specified linear reference. Record any gain expansion rather than silently choosing the peak gain as a new reference; peak-gain and linear-gain definitions can give different crossings.

Stabilize bias, supply and temperature. Record bias current and wait conditions when changes in gain could come from self-heating or supply sag. A reverse sweep or a repeated low-drive checkpoint can reveal a history-dependent result, but it cannot identify temperature as the sole cause. If the product calls for pulsed rather than continuous-wave drive, use the specified regime and report pulse conditions separately.

1 dB Gain Compression Point: Calculate Input and Output

With 18.0 dB linear reference gain, target a measured gain of 17.0 dB. Suppose a valid calibrated sweep reads 17.2 dB at −9.0 dBm input and 16.8 dB at −8.0 dBm. Linear interpolation between those two points places the input crossing at −8.5 dBm; the corresponding output is +8.5 dBm, not +9.5 dBm. The latter is the output extrapolated from 18.0 dB of uncompressed gain. The values are illustrative, not measured amplifier specifications.

Take finer steps near the crossing before reporting a result close to a limit. Report whether P1dB is input-referred or output-referred, along with frequency, bias, temperature or stabilization conditions, and the applicable uncertainty. If the drive range never reaches the crossing under valid measurement conditions, report the verified bound rather than extrapolating a P1dB value beyond the sweep.

Illustrative gain crossing 17 dB at minus 8.5 dBm input between steps of minus 9 and minus 8 dBm
For an 18 dB linear reference, the 1 dB crossing is at 17 dB measured gain. The interpolation is valid only for an adequately resolved, verified sweep.

DUT Compression vs. Receiver Compression

Change receiver input power without intentionally changing the DUT input. Check that the alternate path neither changes the load materially nor shifts the reference planes; where possible use a verified downstream receiver attenuator arrangement. Recalibrate or correct each path, and verify both at low drive. If the additional attenuation reduces measurement margin, it can create a different error at the low-drive end. The two useful datasets need an overlapping region that is both above noise and below receiver nonlinearity.

Observation Likely problem Check next
Same corrected crossing at the same DUT drive after an independent receiver-level change Consistent with DUT compression Verify the expected gain at low drive, comparable DUT load, and sufficient margin in both sweeps
Droop starts earlier only with the higher receiver level Possible receiver compression Confirm receiver linearity and path corrections with a suitable reference at comparable receiver powers
Low-drive baseline changes with the pad even though both receiver levels are verified linear Load mismatch, changed reference plane or path loss Verify pad response, load seen by the DUT, connector repeatability and correction state
Gain wanders at the low-drive end, worse with more attenuation Weak-signal uncertainty Check noise and repeatability before changing the reference gain

If low-level gain has no flat, repeatable region, use the VNA IF bandwidth and noise-floor checks before collecting the compression sweep. Narrowing IF bandwidth may help a noisy baseline; it does not fix an overloaded receiver.

VNA Power Sweep Setup for Amplifiers, Filters and Fixtures

RF amplifier board: Place both DUT planes at the agreed RF interfaces. Check bias under drive, measure at the required frequencies, and verify the crossing using a second corrected receiver level. Accept when its position is repeatable under the specified bias and drive regime and meets the product limit after applying the agreed decision rule.

Passive RF filter: When checking whether insertion loss changes with drive, choose frequencies inside the passband and separately check stopband measurement margin. Keep incident power within the product’s conditions. Accept only if repeatable changes stay inside the allowed variation over the stated level range. A stable low-power sweep does not qualify the component for higher-power service.

Test fixture or path: Use a characterized linear thru or attenuator with adequate rating to check the chain over the levels it must measure. Match receiver levels as well as practical; replacing a high-gain amplifier with a bare thru at the same source level alone does not exercise the receiver at the same power. Require stable corrected response in the overlap region before blaming the board.

Gain Compression Test Report: Log the Evidence

Fill one row per frequency and test condition, then check that the conclusion survives the second setup. The example below shows what a complete record should contain. The illustrated crossing is not a passing result unless the product requirement and uncertainty rule agree.

Record What to write and verify
Test conditions Frequency, sweep direction and steps, bias and current, CW or pulse settings, DUT serial and both physical reference planes
Baseline and bracket Example: 18.0 dB linear reference; −9.0 dBm/17.2 dB and −8.0 dBm/16.8 dB; input −8.5 dBm and output +8.5 dBm by local interpolation
Independent setup check Two corrected receiver-path configurations; actual linear range and noise margin; record the corrected crossing from both, not just the selected trace
Disposition Applicable limit and whether it is input or output, uncertainty or guard band, power margin checks and any untested frequency or condition

VNA Power Sweep FAQs

Should I keep the same source setting when I change the output pad?

Keep the same verified DUT input power, which is the quantity that matters. Also confirm the alternate path has not changed DUT output loading enough to alter the amplifier’s actual behavior.

Why does the measured compression point move when I add an attenuator?

Possible causes include analyzer nonlinearity, an uncorrected pad response, changed load match or a different usable signal range. Check a characterized reference and compare at the same DUT input powers before interpreting the shift.

Does a 1 dB gain drop mean a 1 dBm output power?

No. One dB is the difference from reference gain. P1dB can be any absolute input or output power in dBm within the specified test conditions.

Can I measure P1dB from a frequency sweep at one power?

Not generally. You need a valid gain reference and enough drive levels at the frequency to bracket the crossing, or an instrument mode that performs this sweep at each selected frequency.

Can I use only an RF generator and a power meter?

Yes, if you establish the incident drive and the relevant output with suitable calibrated equipment. If the output sensor sums harmonics but the specification concerns only fundamental power, use a validated frequency-selective method or filtering.

Does the VNA receiver always compress right before it is damaged?

No. The input may remain undamaged while measurement errors are already unacceptable. Consult the linearity and protection limits for the exact receiver path and instrument configuration, and check both.

What if no compression appears in the validated sweep?

Report that the crossing was not reached within the verified range and state its upper tested drive. Confirm that the reference gain and power readings remain valid at the highest tested point.

Can lower IF bandwidth replace output attenuation?

No. It can improve repeatability near the noise floor but does not lower incoming RF power. Select attenuation and range to maintain receiver linearity, then choose bandwidth for the resulting signal level.

Technical References

Custom RF PCBs With Stackup and Test Access Review

Send EBest Circuit your fabrication files, target stackup and controlled-impedance requirements. Flag the connector interfaces, any de-embedding or coupon arrangement, and the test access you need before fabrication. The more clearly your files define those interfaces, the easier it is to agree on a build and verification scope before ordering. Email sales@bestpcbs.com to request a custom RF PCB quote.

S-Parameter Renormalization: From 50 Ω to 75 Ω

November 16th, 2026

To compare a 50 Ω VNA file with a 75 Ω specification, renormalize the complex S-parameters to the required impedance at the same reference planes. Do not change only the Touchstone header. Renormalization changes how the same electrical network is described. It does not change the actual VNA ports, remove a launch, or repair a poor measurement.

This guide uses linear networks and positive real reference resistances. For complex reference impedances or mixed-mode ports, use a documented method that handles the applicable wave definitions and port mapping.

Illustrative RF PCB transmission coupon with coax connectors at both ends
An RF test coupon can be described using different wave references without changing its connectors or the copper geometry.

What Is S-Parameter Renormalization?

S-parameter renormalization expresses the same network at the same physical ports using a different impedance basis for the incident and reflected waves. The voltage-current relationships of the network stay the same; the S-parameter values need not. This is why the same measured circuit can have different return loss under two standards that specify different reference impedances.

Start by recording the original impedance at each port, the port order, the reference plane and the target specification. If the specification calls for a 75 Ω connector-to-connector measurement, a 75 Ω result at the pads is not automatically comparable. Agree on the plane first, not only the impedance number.

Reference Impedance vs. the Physical Termination

The reference impedance is part of the wave definition; a termination is a physical component or a load in a simulation. Changing the reference of a recorded file does not replace the coaxial hardware or change how the source drove the original measurement. If you connect an external load in a simulator, set that load explicitly even when the file is already in the desired reporting basis.

In a two-port S11 reading, the other port is matched to its reference for that S-parameter definition. When you renormalize both ports, that matched condition is different. That is one reason a one-port conversion on S11 alone does not generally reproduce the correct two-port result.

Reflection Coefficient Formula: Check a Known Load First

A known ideal 75 Ω load produces a reflection coefficient of +0.20 in a 50 Ω reference system and zero in a 75 Ω reference system. For a positive real reference resistance R and a load impedance Z, Γ = (Z − R)/(Z + R). The magnitude in dB is 20 log10|Γ|; the positive return-loss convention takes the opposite sign.

One unchanged ideal 75 ohm load evaluated at 50 and 75 ohm references
In this ideal example the load stays 75 Ω. The reference changes, so the reported reflection changes.

The +0.20 result is −13.98 dB in S11 magnitude, or 13.98 dB return loss. From the original complex Γ, recover the load as Z = R(1 + Γ)/(1 − Γ), then apply the new reference to that same Z. Do not do this from magnitude alone: positive and negative reflections of the same magnitude do not give the same impedance. An ideal open, Γ = +1, makes the finite-Z form singular; use a supported conversion or its limit. A real measured 75 Ω standard will not read exactly zero after conversion.

S21 Measurement: Recalculate the Whole Two-Port

Use a full-matrix renormalization in a tool that supports the file’s wave definition and new per-port values. Do not change only S11 or S22 and leave transmission terms untouched. The result at one port depends on what happens at the other, and complex phase information is part of the data.

Take an ideal 25 Ω series resistor as a check, with the same reference resistance R at both ports. The series current and voltage drop give S11 = 25/(2R + 25) and S21 = 2R/(2R + 25). At 50 Ω, S11 = 0.20 and S21 = 0.80 (−1.94 dB). At 75 Ω, S11 = 1/7 and S21 = 6/7 (−1.34 dB). The reported transmission changed by about 0.60 dB; the resistor did not change. This is an ideal lumped example, not a prediction for a frequency-dependent PCB launch or an uneven pair of port references.

50 Ohm vs. 75 Ohm: Choose the Right Kind of Change

Change the reporting basis only if that is what the problem requires. If the data include a fixture that is not part of the specification, solve the reference-plane problem separately. If the measurement itself cannot resolve the device, improve or verify the physical setup.

What needs to change? Operation What to verify
Wave reference, with the same physical planes Renormalize the full complex network. Correct original and new references; known-load or known-network check.
Location of the reference planes Use a qualified calibration at the new planes or remove a characterized fixture. Which launches remain, and whether the fixture model is valid in band.
Hardware mismatch or usable range Adapt and calibrate the measurement setup as appropriate. Hardware compatibility, matching, repeatability and residual noise.

VNA Port Extension vs. a Reference Impedance Change

Port extension typically compensates for electrical delay and may include loss correction on some instruments. It is not a generic correction for fixture mismatch, and changing R does not move a calibration plane. Verify the instrument’s implementation. If the fixture has appreciable discontinuities or coupling, use an appropriate fixture characterization instead of treating it as a uniform delay.

Conceptual measurement path with connectors, launches and distinct connector and pad reference planes
Renormalizing at the connector planes leaves the launches inside the measurement. Moving the planes changes which structure the result describes.

VNA Calibration: Check What the Physical Setup Can Prove

Keep the instrument’s physical ports and its software impedance setting separate. For example, Keysight’s E5080A system-impedance guidance distinguishes its nominally 50 Ω physical ports from a mathematical 75 Ω display reference. It gives a 75 Ω measurement workflow using suitable matching pads and 75 Ω calibration standards. Apply the supported method for your actual analyzer, calibration kit and rated adapters.

If you have a suitable 50 Ω linear measurement, you can convert it mathematically, but conversion does not restore a response missing below the floor or remove unstable coupling. When weak S21 limits the claim, use the VNA IF bandwidth guide to verify receiver noise and fixture leakage before converting or releasing the result.

Touchstone File: Check the Export Before Sending It

Save the original raw file, export a separate converted copy, and reopen it in the receiver’s tool. In Touchstone 2.0 and 2.1, the optional [Reference] keyword supplies port-ordered real reference resistances and overrides the option-line default when present. Touchstone 1.0 uses a single shared reference on the option line; 1.1 has its own per-port syntax. Check importer support rather than relying on the file extension alone.

For a passive PCB channel, use the full-matrix S-parameter passivity check on both versions. Exporting the expected reference values and matching a single transmission trace does not prove the converted data is safe to use in a passive channel model.

Record to check Example entry Pass condition
Physical planes and port order Connector planes; P1 input, P2 output Both versions have the same plane and mapping unless a separate change is documented.
Original and export reference 50/50 Ω → 75/75 Ω Reopened file reports the intended values and transformed complex data.
Known-network check Ideal series 25 Ω: S21 ≈ 0.857 at 75 Ω Use the complex value and expected tolerance, not just the marker after rounding.
Round-trip check Convert the reopened copy back to 50/50 Ω Original complex data are recovered within declared numerical tolerance; this tests software and data handling only.

Use this table for a vendor data handoff. For example, if the exported resistor check still shows S21 = 0.80 while the file shows 75/75 Ω, do not release it: verify that the complex matrix was changed and that the reader recognized the reference format. For a coaxial filter, compare the required return loss and transmission in the specified band at the defined planes. For simulation correlation, verify using the same file reference, frequency grid and actual load definitions. If a change in reference moves the margin around a limit, verify again rather than calling it a physical redesign benefit.

S-Parameter Renormalization FAQs

Can I edit only R 50 to R 75?

No. That changes the metadata without computing the new wave values. Use a valid full-complex conversion and keep the original file.

Can I convert a screenshot that shows S11 in dB?

Not uniquely. You generally need the complex data or both magnitude and phase. Ask for the original file or remeasure.

Does selecting 75 Ω make VNA hardware 75 Ω?

No. A software setting cannot change the physical port construction. Use the instrument’s supported hardware and calibration method when the physical measurement needs to be adapted.

Can ports have different reference resistances?

Yes, when the format and tool support them. Enter the values in the correct port order and verify what the importing program actually applies.

Should I use a different number on the Smith chart after conversion?

Use the chart reference that matches the data and task. A shifted point with a new reference is not evidence that the measured load physically changed.

Does a round trip prove accuracy?

No. It checks conversion and data handling. A measurement can round-trip faithfully and still carry calibration error, noise or fixture leakage.

Can I remove an SMA launch by changing references?

No. Identify the intended plane and use suitable calibration or characterized de-embedding for the launch, independently of the impedance basis.

Do these examples apply to mixed-mode or complex reference data?

Not directly. Define modes, port order and the scattering-wave convention, then use an appropriate documented transformation. This guide uses positive real single-ended references.

Technical References

Custom RF PCBs With Stackup and Test Coupon Review

Send EBest Circuit your stackup, RF connector footprints and test band before release. Reviewing the trace geometry and test coupon together lets your team state which line construction the fabrication check covers and which launches or device responses need separate validation.

Request an RF PCB fabrication quote at sales@bestpcbs.com. Include your released fabrication files, quantity, target impedance by structure, and the required reference planes and reporting conditions.

VNA IF Bandwidth: Is Your Filter Stopband Real?

November 16th, 2026

If a PCB filter’s S21 flattens in the stopband, narrow the VNA IF bandwidth and measure the baseline in the same setup. In a receiver limited by white noise, reducing the bandwidth from 1 kHz to 100 Hz should lower the random noise floor by about 10 dB. If a repeatable plateau remains near the fixture’s isolation baseline, a narrower setting alone will not prove the filter meets its rejection target.

The useful result is not the deepest number the screen displays. It is a reading that can be separated from noise and leakage well enough to decide whether the PCB meets the requirement across the specified band.

Illustrative two-port vector network analyzer connected to an enclosed RF filter fixture
Illustration of a two-port test arrangement. Keep the physical setup stable while changing receiver settings.

What Is VNA IF Bandwidth?

VNA IF bandwidth is the width of the receiver filter used after the RF signal has been translated to an intermediate frequency. It controls how much noise reaches each measurement point. It is not the RF sweep span, the spacing between frequency points, or the physical bandwidth of the filter under test.

For approximately white receiver noise, noise power is proportional to effective bandwidth. The ideal change is 10 log10(new bandwidth ÷ old bandwidth) dB, so a change from 1 kHz to 100 Hz gives −10 dB. Keysight documents the trend experimentally for one class of instruments. It does not predict the sweep time or lower a signal leaking coherently around the device.

VNA Noise Floor: Check Two Baselines

Separate the receiver-and-cable baseline from leakage through the full fixture. A documented isolation check with the two cable ends independently terminated in appropriate matched loads, with no intended through path, shows what the receiver and external setup report under that condition. A representative isolation witness with the relevant fixture retained can reveal coupling that the separately terminated cables missed.

Two independent VNA ports connected to separate matched loads without a through path
Independent terminations are useful for the receiver-and-cable check. Removing the fixture means this check does not capture all of its leakage.

Match source level, receiver mode, frequency grid and IF bandwidth to the device run. Document where calibration ends and whether the analyzer uses isolation correction. An isolation-corrected baseline is not an independent witness if the same trace was used to derive the correction. Follow instrument instructions for appropriate loads and connections. With the real fixture in use, the isolation witness must preserve the geometry and relevant coupling paths; if it cannot, report that limitation.

VNA Dynamic Range: Check the Weakest Part of the Band

Usable dynamic range is set by the actual setup at the frequencies of interest. Check the separation between the device and a relevant baseline point by point, or at the weakest locations under a justified sampling plan. A single best-case dynamic-range number from the front page of an instrument datasheet can miss an in-band leakage spur or a noisier frequency region.

Higher source power can improve a weak reading only while the board and receiver still behave as intended. If the observed gain begins to fall as you raise the drive, use the VNA power sweep guide to check whether the board or the receiver is compressing.

A separation in dB is a screening number, not a measurement uncertainty by itself. Coherent leakage can add or cancel, and receiver noise varies from sweep to sweep. Compare repeats including a reference, and apply the project’s agreed uncertainty and decision rule. If the limit lies within the unverified region, record the measurement limitation instead of assigning a precise stopband value.

S21 Measurement: Record a Wide and a Narrow Sweep

First record the wider-bandwidth baseline, the device and an appropriate reference response. Repeat at a narrower bandwidth with the same grid, test power, fixture geometry and gain settings. Some analyzers adjust operating ranges automatically; verify and record the actual state. Preserve raw sweeps without smoothing. A baseline that drops while the device feature remains repeatable supports a real response. A device trace that drops with the baseline may still be unresolved.

Illustrative S21 plot showing a wide-bandwidth floor partly masking the DUT stopband and a lower narrow-bandwidth floor
Conceptual sketch, not a measurement. Narrowing the receiver bandwidth can separate a DUT response from random noise, but the fixture floor still needs its own check.

Keep the cables still between runs. If a repeatable phase or magnitude change tracks cable pose rather than IF bandwidth, use the VNA cable movement guide to distinguish flex from connector remating. Changing the setting and reconnecting at the same time would obscure which variable caused the difference.

VNA Averaging vs. Narrower IF Bandwidth

Try a narrower IF bandwidth first if the receiver noise is the problem and the sweep budget allows it. Use vector averaging for stable repeated sweeps when you still need better repeatability. Do not substitute trace smoothing for either. Smoothing blends neighboring frequencies and can hide a narrow leak in the stopband.

Control What it changes When to use it
Narrower IF bandwidth Restricts receiver noise per frequency point; usually takes longer to sweep Weak transmission with a baseline that falls when bandwidth is reduced
Vector averaging Combines repeated complex samples; coherent leakage can remain A stable setup where repeated sweeps still show uncorrelated noise
Trace smoothing Combines neighboring frequency points in the displayed response Only for a labeled overview if appropriate; use raw resolution for a narrow-feature limit

For ten independent, equal-weight samples of zero-mean noise, the averaged noise power falls by a factor of ten, or 10 dB. The actual instrument averaging algorithm, settling and drift determine whether its “10” setting behaves that way. Time the completed result, not only the first visible sweep.

VNA Calibration: Recheck It Before Comparing Settings

Set the measurement conditions first where practical, then calibrate to the required reference planes. After an IF bandwidth change, follow the procedure for the specific analyzer. In one Keysight M9485A mode, changing it after calibration can trigger a C-delta status indicating uncertain correction accuracy. Do not assume all instruments handle that change the same way.

Check a suitable reference after the change and recalibrate if the method requires it. Save the correction state, calibration plane, frequency grid, source level and time. If a new calibration changes the reference itself beyond your repeatability allowance, fix or explain that discrepancy before claiming the bandwidth experiment isolated noise.

When comparing a 50 Ω measurement with a 75 Ω requirement, settle the reference basis before interpreting a changed trace. The S-parameter renormalization guide separates mathematical conversion from moving the calibration plane or changing the test hardware.

VNA Sweep Time: Spend Time Where It Changes the Decision

The narrowest setting is not automatically best. Choose the widest validated IF bandwidth that separates the signal from the floor and meets the repeatability needed for your decision. Measure the actual sweep time. Instrument overhead, source changes and filter implementation mean a tenfold reduction in IF bandwidth does not imply exactly ten times the total duration.

On analyzers that support segment sweeps, narrow the receiver bandwidth in the stopband while keeping a suitable frequency grid near narrow features. Keep the rest of the band as fast as the test allows, but verify the full production recipe against a reference. Changing segment boundaries or omitting points to save time must not skip a frequency region covered by the requirement.

Filter Stopband Attenuation: Decide What You Can Report

Use the worksheet below at a defined frequency where a result may be limited by the setup. Enter the absolute S21 display levels at the same conditions and subtract the baseline from the DUT reading. Then decide whether you have sufficient independent evidence for a numerical result. These are teaching numbers; they are not PCB measurements or instrument specifications.

Example condition DUT / baseline, dB Observed separation
1 kHz versus independently terminated baseline −75 / −82 7 dB
100 Hz versus independently terminated baseline −77 / −92 15 dB
100 Hz versus separate fixture isolation witness −77 / −86 9 dB

How to use the third row: subtract −86 dB from −77 dB to get 9 dB. If the contract calls for S21 no higher than −70 dB, the indicated value is 7 dB below that boundary. Neither 7 dB nor 9 dB is the error bound. Check the repeatability, leakage behavior and decision rule before claiming pass. If the isolation witness limits confidence, improve or characterize the fixture rather than reporting extra decimal places.

For a filter stopband, verify frequency coverage, weakest rejection and comparison to the isolation witness. For adjacent PCB paths, retain the relevant routing, launches and return geometry when checking unwanted coupling. For rapid production screening, validate the fastest acceptable setup against a suitable reference and keep a path for retesting borderline samples. Each use case makes a different claim; do not transfer the filter’s measured baseline to a different fixture or board.

VNA IF Bandwidth FAQs

Does IF bandwidth set the spacing between VNA points?

No. Frequency point spacing describes where the response is sampled. IF bandwidth changes the receiver bandwidth at those points. You still need enough points to resolve a narrow feature.

Is averaging dB values the same as vector averaging?

No. Vector averaging works on complex measurements before display; averaging the displayed decibel magnitudes is a different calculation. Use the analyzer’s documented mode and save what it does.

Why does a stable plateau stay at the same level?

It may be real transmission, or it may be repeatable coupling through the setup. Compare the plateau with a suitable isolation witness and change one setup condition at a time.

Can a peak above the baseline still be measurement error?

Yes. A coherent leakage path can add to or cancel real transmission. A repeatable separation supports further measurement, but the setup and the decision rule still determine what can be claimed.

Will changing source power give me more usable range?

It may help in a linear setup limited by receiver noise, but not if the source-to-receiver leakage rises with it or the device enters compression. Stay within equipment and device limits and repeat the baselines.

Can I use a lower IF bandwidth to remove fixture mismatch?

No. It does not correct the impedance discontinuity. Verify the calibration references and treat fixture mismatch separately from receiver noise.

Is the strongest stopband marker enough for a qualification report?

No. Report the weakest relevant rejection across the specified band and any regions where the setup could not establish the requested claim. Keep the original traces and settings.

Should I quote stopband rejection as positive or negative decibels?

Label the convention. An S21 reading of −70 dB corresponds to 70 dB attenuation using the same reference and transmission definition. The direction of the acceptance inequality changes with the convention.

Technical References

Custom RF PCBs With Stackup and Test Coupon Review

Before releasing an RF PCB order, ask EBest Circuit to review the proposed stackup and test coupon requirements together. State the band, target impedances and RF features that must be reproduced so the quote can distinguish board fabrication evidence from the device-level test you plan to run.

For an RF PCB fabrication quote, send your Gerber or ODB++ data, drawing revision, stackup, quantity and test requirements to sales@bestpcbs.com.

PCB Copper Density: Why Matching Traces Measure Differently

November 16th, 2026

Two PCB traces can have the same width in the artwork and still measure different impedances. If the difference follows a boundary between dense and sparse copper, compare the finished trace geometry and pressed dielectric thickness in both regions. A passing panel-rail coupon can confirm its own construction; it cannot settle that comparison unless it represents the same local conditions.

The practical test is to compare two accessible lines with the same intended geometry and return path, then section both locations. Check the return path first: a missing reference plane changes the electrical structure even if lamination was perfect.

Illustrated bare PCB showing sparse routed copper alongside a dense copper area
Illustration: sparse routing and a dense copper region can share one PCB without sharing the same local lamination conditions.

What Is PCB Copper Density Near a Trace?

For this check, PCB copper density is the percentage of a defined area occupied by copper on a specified layer. It is not copper weight, the density of the metal, or the amount of current a trace carries. Use the released fabrication artwork, including approved fill, and report the size and location of each measurement window. Comparing a small cutout on one layer with a whole-board average on another will hide the difference you want to see.

Start with identical windows around the two trace regions, using the same window dimensions and the same layer. In an illustrative 10 mm by 10 mm window, 80 mm² of copper gives 80% coverage and 25 mm² gives 25%: a difference of 55 percentage points. That window size is for arithmetic, not a process rule. Ask the fabricator what scale reflects the construction; retain wider context if the nearby copper boundary is large or irregular.

Two equal-sized copper coverage windows with different proportions of solid copper
Compare equal-size windows on the same layer. The patterns are schematic, not the 80% and 25% examples above. Keep the full artwork with your annotated windows so that a nearby boundary is not lost.

Why Pressed Prepreg Thickness Can Change Locally

Prepreg contains glass reinforcement and partially cured resin. Under heat and pressure, some resin moves into spaces beside the copper before curing. A wide sparse region and a dense region therefore need not press to the same local thickness. The glass reinforcement, available resin, copper height, fill pattern and layup affect the result; the copper-area percentage alone does not predict a pressed thickness.

Gary Brist’s published four-layer Partial POOL example reported a roughly 20–25% thickness reduction for the dielectric associated with the lines inset on layer 3. The study also observed a different thickness response on another layer pair. That is a measured result for that construction, not a general adjustment to put into a PCB stackup. In a new design, establish the direction and size from the actual layer pair.

PCB Stackup: Separate Lamination From Return-Path Changes

Compare the reference geometry before attributing a low or high reading to resin movement. A plane split directly under a route changes the return path; unmodeled copper beside a route can change coupling; a change in pressed spacing changes the cross-section even when the plane remains solid. More than one can occur at the same location.

What changed? First useful evidence What to do next
Pressed signal-to-plane spacing Same-layer sections show different spacing, comparable finished width and the same reference geometry Use measured spacing in separate models. Repeat sections if one cut may not represent the region.
Finished trace geometry Sections show different top or base width or copper thickness Compare process and artwork before changing the prepreg specification.
Return or lateral coupling Artwork shows a plane gap, unmodeled nearby copper, or a changed pair spacing Model that geometry separately or change the route. A uniform-line calculation will not explain a transition.

PCB Impedance Calculator: Compare Finished Cross Sections

Use a field solver to compare the two measured cross sections. Hold material assumptions and signal/return topology constant for the first run; vary only the measured signal-to-plane gap. Then add the measured conductor sizes, differential spacing, solder mask and adjacent copper where relevant. For an ordinary microstrip with unchanged width, copper thickness and dielectric properties, moving the reference plane closer tends to lower impedance. When those other inputs also change, the size and even the net direction of the measured change cannot be inferred from copper density alone.

Compare the direction and approximate magnitude with your measurements, and write down what the model omits. If a uniform cross-section model does not explain an abrupt feature, do not tune a single dielectric constant until it fits. Check the artwork for a transition, then use a suitable discontinuity model or a purpose-built sample.

Impedance Test Coupon vs. a Region-Matched Witness Line

Use a conventional rail coupon for agreed production checks and a region-matched witness line when the board has an electrically important density transition that the rail does not reproduce. A useful witness line keeps the same signal and reference layers, line geometry, material construction and local copper surroundings. Agree with the fabricator how to make it accessible, sufficiently long for measurement, and representative of its intended location. The witness line does not replace an actual channel test.

For a controlled comparison, use equivalent launches, the same instrument calibration and rise-time setting, and a comparable stable measurement region. Repeat the contact and capture the raw traces. If the observed difference appears only around the launch or shifts on reconnect, investigate the setup first. The production measurement method IPC-TM-650 2.5.5.7, Rev A (March 2004), discusses representative specimens in §§3.1.1–3.1.3 and describes limits on positional profiling in §1.2(f). Apply the revision and acceptance criteria required by your order; do not take an arbitrary dip on a diagnostic TDR plot as an acceptance measurement. For record-level checks, use the PCB impedance test report guide.

PCB Cross Section: Use a Paired Measurement Record

Choose marked locations in both regions, measure the witness lines first, and take cross sections from agreed sacrificial samples. Record the board or panel ID, region coordinates and layer pair. On each section, record the signal-to-reference spacing, the trace’s top and base widths and its copper thickness. For stripline, record the distances to both reference planes. A single overall board-thickness measurement cannot substitute for these readings.

Two simplified microstrip sections with the dielectric distance bracketed from the trace underside to the reference plane
For this microstrip comparison, measure the dielectric from the underside of the trace to the facing surface of the reference plane. Sections are schematic and not to scale.

Use the worksheet below when a repeatable impedance difference remains after the fixture check. Replace the example columns with readings from a matched pair, calculate B minus A, and ask whether the evidence justifies a lamination, geometry or electrical investigation. All entries below are hypothetical and independent; the dielectric column was not calculated from copper coverage, and impedance was not calculated from dielectric thickness.

Input A: dense B: sparse B minus A
Same-layer copper coverage 80% 25% −55 percentage points
Finished dielectric spacing 100 µm 80 µm −20 µm (−20% relative to A)
Stable TDR reading 50.2 Ω 46.7 Ω −3.5 Ω

How to use the last row: if the agreed 50 Ω ±5% range applies to these witness lines, its limits are 47.5–52.5 Ω. A is inside; B reads 0.8 Ω below the lower limit. Check the agreed decision rule and measurement uncertainty before disposition. If repeat measurements and sections support the difference, verify that finished geometry and return paths really match, then test whether the spacing difference explains enough of the shift. If the setup varies by an amount comparable with the 3.5 Ω separation, fix the measurement before asking the fabricator to change the layup.

When PCB Copper Thieving Helps—and When It Does Not

Filling a sparse region can help with some manufacturing nonuniformity, but added copper close to an impedance-controlled route can also change the electric field. Before releasing CAM edits, distinguish off-board fill for panel processing from copper inside the finished outline. Mark controlled routes and structures that require a keepout, then agree the boundary with the fabricator and confirm it in the model. There is no one clearance suitable for every stackup.

Do not blanket-fill a plane opening reserved by the electrical design. If local fill is not allowed, compare moving the route, changing the reference arrangement or adjusting the layup. Keep changes separate on the qualification panel so they can be evaluated rather than hidden in a global trace-width change.

PCB Copper Balance: How to Verify the Next Build

Repeat the same regional comparison after an approved change. For a memory bus next to a copper boundary, check selected lines in both neighborhoods instead of averaging every line on the panel. For an RF route next to proposed fill, confirm the same measurement planes and compare the response across the specified frequency band; a coupon reading alone will miss a launch or a local coupling change. For routine lot release, use the approved sampling plan and the limits stated on the drawing or order, not the example numbers above.

Record which artwork and stackup were actually built, where each sample came from, the instrument settings and what changed in CAM. Close the investigation when the region-specific evidence meets the agreed criteria and can be repeated. A smaller A/B difference is not enough if both regions are still out of tolerance.

PCB Copper Density and Impedance FAQs

Does doubling the copper coverage halve the impedance?

No. Coverage is an area ratio, while impedance depends on the finished transmission-line geometry and dielectric properties. Two layouts with the same percentage can place copper at very different distances from a route.

Can I use the same percentage target on every layer?

Do not assume that. A mostly solid reference plane and a routing layer have different functions. Document the neighborhood of the controlled line and ask which areas the fabricator wants to balance for that stackup.

Is a nominal prepreg thickness enough for a quote?

It is useful for discussion, but review the proposed finished dielectric spacing for each critical layer pair and how it will be verified. A prepreg style or catalog value does not establish that spacing in two very different copper environments.

Can a coupon from the panel edge stand in for the center?

Only for the conditions it has been shown to represent. Record the positions of the rail coupon and product regions, then compare them on a qualification build if the correlation is material to acceptance.

Do I need to cut every production panel?

No general rule requires that. Use agreed sacrificial specimens for engineering comparisons and retain the sampling frequency defined for production. Do not use one successful comparison to remove a contractual control.

What if the dielectric spacing is the same but the TDR readings differ?

Look at the finished top and base widths, copper thickness, mask, pair gap and adjacent copper. Then repeat the measurements with equivalent launches. Matching thickness removes one candidate explanation, not all of them.

What if the trace is too short to give a stable TDR region?

Design a longer accessible representative line or use an appropriate characterized fixture. Do not average a region dominated by the launch and termination just to obtain an impedance number.

Can an A/B cross section prove my finished assembly will work?

No. It can show a geometric difference and help interpret a matched transmission-line measurement. An assembled channel still needs its own verification for losses, reflections and the requirements of the interface.

Technical References

Custom Controlled-Impedance PCBs With Stackup Review

Get the production stackup and impedance test plan aligned before releasing your PCB order. EBest Circuit can review your fabrication drawings and proposed stackup, and discuss which coupon structures and reports should be included in your quote. That gives your engineering and quality teams the same layer-by-layer record before the boards are built.

Send your Gerbers or ODB++ files, the drawing revision, target impedances and tolerances, and any locations where copper fill or plane clearance is restricted to sales@bestpcbs.com. Ask for a controlled-impedance PCB quote with the proposed stackup and agreed test evidence listed.

VNA Cable Movement: Is Your PCB Measurement Real?

November 16th, 2026

If a VNA curve changes when you move a cable, repeat the movement on a known reference before changing the PCB. Keep the connectors mated for that first experiment. Then put the cable back in its original position and run a separate remating check. If both changes happen together, the trace cannot tell you which one caused the difference.

A calibration corrects the setup as it was characterized. It does not make a bent cable, loose connector or moving antenna feed behave like the original setup. The question is whether the shift over your actual frequency band is small enough for the decision you are about to make.

Illustrative coaxial test cable supported with a clamp and connected to an RF PCB coupon
A fixed cable route gives the reference and PCB a better chance of seeing the same mechanical setup. Illustrative, not a production test record.

VNA Cable Testing: Change One Variable at a Time

Start with a suitable verification standard at the intended reference plane. Take repeat sweeps with nothing moved, then sweep again after the approved range of cable motion without disconnecting anything. Return the cable to its starting pose and compare the trace again. For transmission use a suitable through reference; for reflection use a suitable characterized reflection reference as called for by your procedure.

Keep the device, adapter orientation, test settings and temperature stable. If a shift appears on the reference, do not attribute the equivalent shift on the product to its layout. If the reference returns to baseline only in one cable pose, clamp the cable there and reverify rather than assuming the post-calibration movement is harmless.

If the cables and reference are stable but a weak S21 trace appears to flatten, check whether receiver noise or fixture leakage limits the reading. The VNA IF bandwidth guide shows how to tell the two effects apart.

VNA Calibration: Keep the Reference Plane and Cable Pose Consistent

Identify which connectors define the calibration plane and which adapters remain outside it. Photograph the cable path, support the connector instead of loading it sideways, and use the specified mating procedure. If your verification standard is at the coax plane but the release claim is at the PCB trace plane, any intervening launch or fixture still needs its own error treatment.

Keep raw data before port extension, smoothing or gating. These options can support a valid procedure; they do not replace a stable path. For edge alignment during time-domain tests, see the differential TDR deskew guide. Its source and receive corrections solve a different problem from post-calibration VNA cable movement.

Three comparison steps from undisturbed reference to cable motion and then separate remating
Keep one change per comparison. Repeat the fixed reference between the movement and mating trials.

Phase Stable Cables: Compare the Flex Specification With Your Test

Choose a cable using the specified band, length, connector, bend radius and magnitude/phase stability under the documented flex condition. Phase-stable is not a universal error figure. A repeated sweep with a cable clamped in one place does not qualify a production fixture that needs to move through several positions.

Option Best fit What to verify
Test cable held in a fixed route Repeated boards with consistent connector location. Stationary baseline and repeatability after normal mating.
Qualified phase-stable flexible cable The test requires a defined range of movement. Magnitude and phase at the positions and over the band used in the test.
Board-specific pigtail or adapter Physical access requires a nonstandard connection. Repeatability of the complete path; do not transfer a bench cable rating to the pigtail.

Follow the cable manufacturer’s bend and handling limits. Do not force a tighter bend just to make a trial more sensitive, or assume an adapter has the same mechanical limits as the main test cable.

S21 Phase: Turn a Delay Shift Into Degrees

For a pure added delay Δt in one transmission path, the magnitude of phase change at frequency f is 360° × fΔt, before phase wrapping. At 10 GHz, 2 ps corresponds to 7.2°. For an ideal reflection that traverses that same changed section on both the outgoing and return path, the corresponding phase change would be 14.4°. That factor of two is not a rule for every S11 feature or a mismatched fixture.

Calculate phase differences consistently across the same frequency grid and handle wraparound. A linear phase change can be consistent with delay; ripple, an amplitude shift or a changed notch shape means delay alone does not explain everything. Inspect raw magnitude as well as phase before applying a correction.

Schematic showing one pass through a changed cable section for transmission and a return pass for reflection
The illustration assumes one changed section before the reflector. Real mismatches may produce additional responses.

S11 Measurement: Separate Cable Error From Antenna Interaction

For a matched load, reflection phase can be too noisy to serve as the sole stability check because very little signal returns. Check complex reflection or its magnitude as appropriate, and choose a characterized reference suitable for the phase question. Do not judge a phase jump at a deep reflection null in isolation.

For a small antenna, cable routing can also change the system being measured by interacting with its ground or field. If a reference is stable but the antenna response still moves, repeat with the use-representative feed geometry, body or enclosure. Verify the actual acceptance metric, such as the agreed S11 limit and frequency range, in that defined configuration.

VNA Measurement Uncertainty: Budget the Motion Separately

Set a setup repeatability budget tighter than the differences you need to distinguish, and separate stationary variation, motion and connector remating. The example below is a hypothetical 6–10 GHz PCB coupon test. The project allocates at most 0.10 dB and 5° to the observed change during permitted setup motion. These are example limits, not instrument specifications.

Change from fixed reference Worst magnitude / phase change in band Example action
Nothing moved 0.02 dB / 1.0° Record the stationary comparison.
Cable moved, connectors not opened 0.13 dB / 7.2° Exceeds both allocations; stabilize or change cable setup before use.
Fixed route, reference remated 0.04 dB / 4.8° Inside the example limits, but phase has only 0.2° of margin; repeat under the approved rule.

Enter separate rows for each condition, and report the frequency of each worst change. The worst magnitude and phase changes need not occur at the same point. These observed changes are repeatability evidence, not a complete uncertainty statement or values that may always be added or root-sum-squared.

VNA System Verification: Confirm the Reference After a Change

After changing the cable route, replacing an adapter or tightening a loose clamp, verify the reference again under the intended conditions. Recalibrate when the approved procedure requires it. Use the same sweep settings, plane and reference type, then repeat the motion or connection sequence that the test actually needs.

For a transmission coupon, compare phase and insertion-loss change across the full band. For an antenna, confirm the reference and then repeat the device with the controlled feed geometry. For a near-limit production result, do not release on a narrower graph scale or a new cable pose chosen after the test. Use the agreed repeatability, uncertainty and disposition rules.

VNA Test Data: Record Which Setup Produced the Result

Record cable and adapter IDs, reference plane, frequency band, sweep settings, mechanical route, reference standard, test timestamp and the raw results for fixed, moved and remated conditions. Keep the before and after traces on a common axis. One sample entry might be: “Fixture A, 6–10 GHz; fixed 0.02 dB/1.0°; flex 0.13 dB/7.2°; hold until cable restraint is verified.”

When the reference repeatability is comparable to the difference between two PCB revisions, report the comparison as inconclusive. If repeatability is validated and the result follows the board on the same setup, investigate the board construction or launch with the same controlled evidence.

VNA Cable Movement FAQs

Can flexing change the S21 phase without much loss change?

Yes. Changes in electrical delay can shift phase without a comparable change in magnitude. Measure both quantities and compare them with separate limits.

Do I need to recalibrate after every small movement?

Follow the approved procedure and validated motion envelope. If the known reference no longer reproduces, correct the setup and recalibrate or reverify as required.

Will a shorter test cable always be more stable?

No. Construction, connector support, bend radius and how the cable is moved matter. A shorter cable forced into a tight bend can be a poor choice.

Can port extension remove cable motion?

It can account for an appropriate fixed delay. It cannot restore repeatability when the cable changes shape or remove an unstable connector mismatch.

How do I separate cable movement from a loose connector?

First move the cable within the approved range without disturbing the connector. Then deliberately remate in the same supported pose under the specified procedure, and compare both results.

Why can a reference look stable while a small antenna still changes?

The cable can interact with the antenna or its ground in ways that do not occur with a coaxial reference. Verify antenna geometry separately.

Is 5° an acceptable phase change for any PCB test?

No. It is an example budget. Use the actual frequency band, test uncertainty and decision margin to set the allowed change.

Should I compare only one frequency?

Only when the acceptance requirement is at that frequency. Otherwise compare across the complete required band and record where the worst change occurs.

Technical References

Custom RF PCBs With Stackup and Test Coupon Review

Send EBest Circuit your stackup, RF test geometry, connector-launch drawings, target band, and the quantities you need. A pre-fabrication review can help define which structures to include on a coupon and where to place the measurement reference plane in your test plan. Request a quotation at sales@bestpcbs.com.

Differential TDR Deskew: Is the Skew on the Board?

November 16th, 2026

If a differential TDR trace shows a bump near the launch, put a known reference on the fixture before changing the board. Align when the instrument sees each edge and when the two stimulus edges reach the board. A display shift can line up two saved traces, but it cannot change what was launched into the board.

The practical check is simple: save the acquisition and launch baselines, verify them after reconnecting, and compare the residual on a known reference with the smallest board effect the test needs to resolve. If the reference cannot pass that check, the result is inconclusive, not a board failure.

Illustrative RF PCB coupon fed by two coaxial cables through edge-launch connectors
A two-path TDR setup. Paths that look equally long can differ in electrical delay and step response. This is an illustration, not a calibration fixture specification.

Differential TDR: Check the Setup Before the Board

Differential time-domain reflectometry (TDR) drives the two conductors with nominally equal, opposite steps and observes reflections. In a symmetric system, those opposite changes cancel in the common-mode average. If one edge arrives early, the cancellation is incomplete while the edges are changing, even if both paths settle to the expected voltage.

Keep the raw positive and negative leg traces, not just the derived impedance plot. Use the same bandwidth, rise-time setting, fixture, cable orientation and calibration reference for the baseline and board. A stable difference on a board can matter; one already present on a known reference is not evidence against that board.

TDR Calibration: Separate Three Different Corrections

Timing alignment, impedance calibration, and fixture removal solve different problems. Follow the instrument procedure for their order and confirm where its reference plane ends. In a connectorized setup, the end of the test cables and the start of the PCB traces are not necessarily the same plane.

Correction What changes What it cannot prove
Acquisition deskew Accounts for a relative time offset in how the two receive paths record a common timing reference. Does not make incident edges arrive together at the device under test.
Incident step deskew Changes relative launch timing where the instrument supports actual source delay adjustment. Does not correct gain mismatch or remove fixture discontinuities.
Impedance calibration or fixture removal Establishes the reference for impedance conversion or removes modeled fixture response, as applicable. Does not independently prove source and receive timing are matched.

IPC-TM-650 2.5.5.7A (March 2004) describes characteristic impedance measurement, including a differential measurement process in §5.3. It is not a universal picosecond limit for differential deskew. Use the product test plan and the instrument’s supported alignment routines.

Oscilloscope Deskew: Align the Acquisition Paths

Apply an approved common timing reference to both receive paths at the intended plane. A characterized splitter or a manufacturer’s alignment fixture is useful because an unequal reference cable would otherwise be counted as an instrument error. Keep compatible terminations and reference hardware; do not improvise a connection between independent active outputs.

Measure the same fractional crossing on both edges; use consistent polarity and local amplitudes so offset or amplitude error does not masquerade as time shift. Record the signed difference, channel mapping, reference components, edge setting and repeat spread. If the delay noticeably varies with crossing level, investigate step-shape or bandwidth mismatch; one offset is unlikely to correct the entire edge.

Schematic showing one timing reference applied through a matched split to two receive paths
One characterized timing reference lets you compare what the two receive paths record. Use an arrangement approved for the instrument.

TDR Step Deskew: Align the Incident Edges

With acquisition timing checked, apply the instrument’s incident-step alignment procedure using its approved reference configuration at the selected plane. Set or verify relative launch delay, then save a second baseline. A Keysight FlexDCA system, for example, distinguishes hardware step skew from shifting a waveform on the screen; other instruments can use different procedures or may lack independent launch control.

Do not interpret an open-reference return-time difference as one-way skew unless the instrument method defines that conversion. A reflected edge travels out and back, and the displayed timing can include both acquisition and source corrections. If the instrument cannot align or demonstrate coincident launches, document that limitation rather than tuning the board result into agreement.

Common Mode Voltage: Quantify a Timing Artifact

For equal and opposite steps, the common-mode voltage is the average of the two measured legs. If the only error is a small delay Δt and the edges have similar shape, the magnitude of a local timing artifact is approximately |slope| × |Δt| ÷ 2. This follows from subtracting an edge from a delayed copy before taking the average.

In an illustrative near-linear interval, each leg changes by 0.50 V over 50 ps, a slope of 10 mV/ps. An 8 ps mismatch gives roughly 40 mV of apparent common mode. Reducing the residual mismatch to 2 ps brings the estimate to about 10 mV. That is an edge-window estimate, not a peak guaranteed by the instrument, an impedance in ohms, or a frequency-domain conversion metric. Unequal step heights, baseline error or different edge shapes can leave a residual even at zero timing offset.

Schematic of opposite edges offset in time, with the resulting common-mode pulse shown below
Schematic only. The unmatched part of two opposite edges can create an apparent pulse in their average without any asymmetry on the board.

TDR Test Fixture: Read the Reference Before Repeating on the Board

Reconnect a suitable known reference after alignment and take enough readings to characterize the setup repeatability. Preserve the same reference plane, attenuation, edge setting and fixture configuration. If changing an adapter changes the timing offset, repeat alignment for that configuration rather than comparing it against the old baseline.

Observation What to check next
Offset appears on the common timing reference. Check receiving paths, reference split, and crossing definitions before adjusting source launch timing.
Acquisition reference passes, but the known differential reference shows an edge pulse. Check incident step timing, leg amplitude and shape, and physical fixture symmetry.
Known reference passes; the feature repeats only on the board at the same board-referenced location. Investigate the PCB transition. Record the baseline and attach both raw leg traces before changing the layout.

A controlled path swap can help: if the apparent difference follows a channel or cable on the reference, the apparatus still contributes. If it follows the same physical board leg after channel identities are restored, investigate that leg. Use documented reconnections; a swap that changes geometry or connector loading is not a clean control.

If the setup is stable and the impedance changes where an otherwise matching route enters a dense or sparse copper region, use the PCB copper density and impedance guide to compare finished trace widths, dielectric spacing and the return path before changing the layout.

If you are verifying the same interconnect in the frequency domain, do not mistake a changed cable pose for a board effect. The VNA cable movement guide separates cable flex from connector remating using a fixed reference.

Differential Pair Skew: Separate Board Delay From Setup Error

For a connector launch, verify the launch reference first, then check that the PCB-only feature stays put when you repeat the setup. For a via transition, hold the edge speed and reference plane constant; a local impedance feature can remain after both channels are aligned. See the PCB via impedance guide for the separate task of identifying that transition.

For incoming coupon reports, ask which reference condition, mode, and measurement window were used before comparing numbers from two labs; the PCB impedance test report checklist covers lot-level traceability. If you actually need board-leg propagation delay from end to end, use a suitable transmission-delay measurement and reference plane. Do not convert every reflection timing difference into a routed length offset.

TDR Measurement Setup: Record a Repeatable Acceptance Check

Start with the smallest relevant board signal and decide how much setup error the measurement can tolerate. For example, if the test plan allows 15 mV of residual edge artifact in a defined window and the relevant slope is 10 mV/ps, a first-order timing budget is about 3 ps, assuming skew is the only contributor. Verify the actual baseline amplitude with the same window; the calculated budget does not cover gain error or ringing.

Use a log with reference ID, both channel/cable IDs, plane, edge setting, raw and corrected offsets, repeat spread and actual baseline residual. Example entry: “Ref A; same launch plane; 8 ps before, 2 ps after; 10 mV baseline measured in the defined window against a 15 mV limit.” This is a hypothetical report entry. Record the offset and residual on each reconnect required by the plan. Hold the judgment if repeatability or the residual is too close to the limit to support it.

Differential TDR Deskew FAQs

Does oscilloscope probe compensation also deskew a channel?

No. Compensation adjusts the probe’s response; deskew corrects relative timing. Both may affect what you see at the edge, so record which procedure was applied.

Can identical cables be assumed to have identical delay?

No. Part tolerances, adapters and routing affect the complete path. Verify the actual pair with the reference connected where you need the alignment.

Is display alignment enough for a true differential launch?

No. Aligning captured traces cannot make the two sources reach the board at the same instant. Verify incident timing separately with the supported procedure.

Does a flat common-mode trace prove the setup is calibrated?

No. It is useful evidence under a defined reference and window. It does not prove absolute impedance accuracy, equal gain at all frequencies, or valid fixture removal.

Should I deskew again after moving a cable?

Recheck the baseline after reconnecting, changing a cable or adapter, or changing settings that affect timing. Repeat formal alignment if the verified residual no longer meets the plan.

Does every differential TDR need 3 ps accuracy?

No. That is an illustrative estimate from a specified slope and voltage budget. Derive your limit from the measured edge and the task’s tolerable artifact.

Can I infer cable length from a TDR time difference?

Only with the propagation velocity and the correct time convention for the setup. A reflected signal generally includes both outbound and return travel.

What if the baseline still shows ringing after alignment?

Check connection quality, reference response, bandwidth, fixture symmetry and termination before adjusting delay further. Do not use time shift to hide a repeatable reference artifact.

Technical References

Custom High-Speed PCBs With Stackup and Coupon Review

Before fabrication, send EBest Circuit your layer stackup, differential trace groups, target impedances and test evidence requirements. Reviewing these together lets you specify which structures the fabrication coupon should represent and which board features need separate measurement. Request a quote at sales@bestpcbs.com with your fabrication files, quantities and approval requirements.