Debug, Verification & Compliance Convergence

Every block passes and the product still fails

Which requirement, on which complete product configuration, did those passing block tests actually cover?

The node’s transmitter passes its nominal conducted test. The gateway receives a weak wanted signal when its backhaul is quiet. The application delivers 995 of 1000 messages in one unobstructed setup. Then the node supply falls to 2.7 V and its adjacent-band power rises. Enable the gateway’s backhaul and the receiver needs more wanted input. Rotate the node and thirty requests miss their deadline. The earlier observations can all be correct.

Subsystem tests isolate useful questions by controlling what surrounds a block. Integration deliberately exposes interactions that those controls excluded: supply impedance can modulate PA behavior, an aggressor can enter a receiver through RF or shared power paths, and an antenna pattern can move energy away from the service direction. A product claim therefore needs an explicit intersection of requirement, complete configuration, sample, method and environment. Adding passing labels cannot supply that intersection.

We continue teaching-node-v1, the fictional condition-monitoring node and gateway. Its 2.450 GHz QPSK waveform is generic: 20 kbit/s information, 10 ksymbol/s and RRC roll-off .35. It is not automatically Bluetooth, Wi-Fi or an authorized transmission. The four configurations below are declared test variants, not a claim to cover every mode combination.

Bring 10.4’s staged bring-up record, 08.6’s hypothesis and evidence workflow and Path 09’s compliance foundations. This lesson owns integrated verification and review readiness. Measurement theory remains in Path 08; real market decisions remain in Path 09.

Freeze the question, specimen and evidence scope

Could another engineer reconstruct both the specimen and the claim from the record?

A configuration is the complete node/gateway pair under test, including the state of an aggressor. “Latest firmware” or “standard antenna” cannot identify it. A report also needs the sample population it actually represents. Here the supplied specimen is SYN-N01-FR-01 paired with SYN-G02-FR-01; repeating a trial on that pair does not create another independent product sample.

The requirements inherit 10.1’s service definition. A timely success is a unique complete 32-byte payload at gateway D0, with latency plus its expanded timing uncertainty at or below 1 s. Requests occur 60 s apart, with at most one retry at +200 ms. The predetermined denominator is 1000. Late, missing and ambiguous-timing messages count as unsuccessful; the radio’s packet counter or a cloud acknowledgement cannot silently replace this boundary.

Every variant fixes stationary, dry 25±2 °C conditions; synthetic unobstructed S0 separation 100 m; antenna reference points 1.5 m high; gateway vertical polarization and azimuth 0°. P0-GW is a separate 5.0±.05 V gateway supply. The values define this exercise and supply no component safety rating. The four full child manifests below include hardware, BOM, stackup, firmware, calibration, cable and user state.

Verify interfaces before expensive sequences

Are the instruments, application logs and budgets answering the same question?

An environmental or formal test sequence multiplies the cost of a setup mistake. First reconcile the named interfaces from 10.2, the physical test access from 10.3, and the controlled activation from 10.4. A receiver RF input is R1-RX, a local alias of R1. R3 is where the receiver makes decisions. Moving a generator calibration to the antenna connector without accounting for the intervening path changes the input-level claim.

Q-TX is a carrier-relative power ratio in dBc, not an absolute output in dBm. Its numerator is integrated adjacent-band on-time power, and its denominator is the named on-time carrier band. Changing detector, gating, integration bandwidth or carrier normalization changes the statistic. The inherited B-FEED allocation stays one 2 dB matched loss: +10 dBm at R1 becomes +8 dBm at R2. That allocation is neither a measured correction nor Q-TX’s carrier denominator.

Q-RX is a paired difference at the same gateway RF input: aggressor-on required level minus aggressor-off level, with the wanted waveform, receiver criterion, fixture, power and environment unchanged. Positive dB means degraded sensitivity. In the concurrent example, −97.2−(−100.0)=+2.8 dB. Its supplied U already includes common corrections and covariance. Adding two copies of that U would count the paired uncertainty again.

Port correction does not freeze a test system forever. Keysight’s error guidance distinguishes drift and other residual errors; a changed cable or thermal condition must be considered before comparing corrected results. Use 08.4’s calibration and fixture model for the method, and the RF Tools bench for supporting port and power calculations.

Characterize corners without inventing yield

How far can one corner result legitimately travel?

Design corners deliberately probe mechanisms. A repeated trial probes repeatability under declared conditions. A set of independently selected units can support a population inference only with its sampling and statistical model. These are different experiments. Our single sample pair and four deliberately selected states do not estimate production yield, field reliability or a universal worst case.

Uncertainty addresses knowledge of a declared measurement result; it is not the spread of future manufactured units. Expanded U is related to combined standard uncertainty by a stated coverage factor, while its probability interpretation needs more information. NIST TN 1297 §6 explains that distinction. Here U is a supplied k=2 premise for the named statistic; no population confidence is calculated.

The decision model uses integer tenths of dB and integer counts. It never rounds a display and then decides. A 0.1 dB nominal margin is a difference between two numbers, not a quantified yield guarantee. JCGM 106 separates measurement information from decision policy; an actual standard may prescribe a different rule that its owner must apply.

Debug with eligible evidence and competing hypotheses

What observation would distinguish the leading explanation from a plausible alternative?

Debug begins with an eligible symptom, not a preferred repair. First confirm the configuration and method; then list competing mechanisms and write a discriminating prediction before intervention. A test that improves the scalar result may still be ambiguous if it changes supply, firmware and load together. Preserve the intervention, untouched controls, countertest and corrective verification as different records.

The three stories below share a product but need different experiments. Low-supply adjacent power points toward PA/supply behavior. Paired gateway desense asks about a particular aggressor and receiver state. Orientation-dependent service asks about radiation, polarization, mounting and the application deadline. They are not automatically three versions of a matching fault.

A common timing cluster can prioritize work: PA current and spectral regrowth may share a supply mechanism; concurrent packet losses and backhaul activity may share a coupled path. It cannot establish causation by itself. Likewise, one remaining cause in a bounded hypothesis catalogue only says the other listed explanations were excluded under the model. An unlisted cause, an ineligible control or a wrong measurement model can remain.

Correlate measurements across domains

Are coincident timestamps actually coincident physical events?

A spectrum, current waveform, protocol log and thermal image observe different quantities through different bandwidths and delays. Align the timestamp reference and capture window before interpreting their order. A 1 Hz thermal record can show the slower case-temperature context but cannot resolve a 20 ms burst. A log written after a software task may timestamp the write rather than the RF event.

The three aligned intervals are [9960,10040] µs. None lies strictly before another. To establish order at this resolution, one interval’s upper endpoint must be below the other’s lower endpoint after justified latency correction. Even established order is only one causal condition; a controlled intervention and countertest are still needed.

Keep the spectrum’s on-time window tied to the same burst state, with the specified detector/statistic and bandwidth. The R&S gated-FFT discussion explains how selecting a time window changes the spectral comparison. A sample excluded by the gate cannot become evidence for that omitted interval. Probe position and cable geometry also belong to a repeatable comparison.

Prepare the pre-compliance and formal handoff

What exactly should the laboratory be able to reproduce?

Pre-compliance work is valuable because it exposes design and setup problems early. It becomes misleading when the team labels an engineering scan as a formal report or assumes that a report-shaped document covers the present product. Freeze the intended radio/modes, representative rationale, firmware, antenna, cable, mount and supply before requesting a method-specific formal sequence.

A good handoff explains why test firmware represents production behavior: channel and power control, duty, concurrency, calibration tables, state timing and restrictions must be traceable. It names source and method revision, specimen identity, fixture/calibration and uncertainty or prescribed decision rule. The laboratory and Path 09 owner need explicit deviation questions and permitted configuration changes, not a generic instruction to “make it pass.”

The table above is the static BASELINE dossier example. M-A and M-B are supplied formal-scope review premises for the four baseline manifests; they are not real report or approval identifiers. M-C has no package. The live matrix later keeps its own current formal table aligned with the selected snapshot. No dossier row fills an engineering cell.

As a separate real-source example, ACMA’s testing guidance ties the evidence route to applicable standards and equipment classification. This Australian example is not a mapping of M-A, M-B or M-C and does not add Australia to the inherited product scope. It illustrates the source question the Path 09 owner must answer for an actual product.

Review deviations and control corrective action

Did the corrective work change only the failed measurement, or the claims supported by other evidence too?

A laboratory may correctly measure a specimen that differs from the intended release configuration. The report remains an authentic account of that test, but its use for a changed antenna, firmware or operating mode needs a separate applicability decision. Do not edit the old report’s identity to make it current. Record the deviation, retain the result, and identify the changed claim and next evidence.

A PA/control correction can affect spectral regrowth in all four states, gateway reception during concurrency and every service sequence through RF or timing behavior. The declared CH-PA graph therefore marks nine engineering uses stale. It also asks the Path 09 owner to review M-A and M-B against the new manifest. These are formal applicability questions; graph reachability is not a prescribed test suite.

Q-RX@V-NOM and Q-RX@V-LOW are outside the combined ten-cell set under the supplied graph’s explicit rationale. That says which evidence use was reviewed as unaffected here. It does not prove every unconnected physical mechanism is harmless. An unknown change, missing edge or different graph version requires impact discovery rather than a no-impact badge.

In its separate Australian context, ACMA’s change guidance calls for a retained statement describing a product change and its materiality. Its testing page also directs retesting after changes to a tested product. An actual retest disposition must use those current rules and the product’s facts; this local teaching graph grants no exemption.

Close requirements without hiding restrictions

Can the review see what is still failed after the scope is narrowed?

Closure is a supported current claim under a declared rule. It is not a checkbox the owner can flip. The matrix checks identity and graph integrity, then evidence compatibility, result/uncertainty eligibility and the decision rule. An invalid draft has no new evaluation. A valid record with unknown U remains uncovered, with its nominal value identified as provisional.

REST-ROT-v1 proposes keyed mounting and installation controls, with a firmware orientation check only if its implementation is supportable. The antenna/mechanical and firmware owners must determine whether users can defeat or misunderstand the control and how the installed state is verified. Selecting the proposal below does not implement it. A controlled requirement revision would need a new identity, rationale and review history.

Work through the convergence sequence

1. Begin with BASELINE and inspect each blocker. Distinguish measured-shaped illustrative failure, interval overlap and missing evidence.
2. Load BOUNDARY: twelve engineering cells close at the supplied equality cases. M-C remains missing. These are independent complete VM-BOUND-v1 premises, including M-A-BOUND and M-B-BOUND.
3. Return to BASELINE; propose V-ROT restriction. The baseline stays twelve, with the original rotated service failure retained.
4. Load PA-CHANGE: nine uses become stale under VM-PA-v2. Inspect the preserved original failure in evidence history.
5. Select Q-TX@V-LOW and apply SINGLE-RETEST-PA-v1. The compatible −43±1 dBc packet produces exactly four closed and eight uncovered. Both formal applicability reviews remain open.
6. Load FULL-REGRESSION: all nine affected uses get supporting records, with explicit retention of the other three. All twelve close; M-A/M-B applicability and M-C evidence still need review.
7. Compare M-B-PRESCAN and M-B-WRONG-SCOPE, then M-C-RESOLVED. None changes engineering cells. Reset restores the canonical case and keeps keyboard focus.

Chair a release-readiness review

What can each decision owner defend, and what must stay open?

Chairing the review means making the evidence boundary clear enough that people can disagree productively. Ask the RF lead to defend the failed and overlapping cells, the verification lead to defend sample and regression coverage, the installation owner to defend restrictions, and the Path 09 owner to identify formal gaps. A complete document set can coexist with technical failure; a fully closed engineering matrix can coexist with a missing formal package.

The current release-readiness draft in the workbench states the exact manifest, counts and blocker IDs. It does not implement a signature, approval, release service or legal authorization. Even after selecting an M-C-resolved premise, actual market placement and operation require current source and product-specific decisions outside this teaching fixture. There is no global green release badge.

IEEE 149-2021 remains the antenna-measurement reference identified in Path 06: the official catalogue lists it active, but its full procedure text was not accessible for this lesson. Do not infer an unseen clause. Use 06.3’s configuration reasoning and commission the actual scoped method review before claiming antenna acceptance.