Files
heltec-repeater/docs/FIELD_TEST_2026-09-01.md
T

9.9 KiB

Field test — first onsite standalone deployment (2026-09-01, afternoon)

Setting: the repeater and the HIL laptop (with the Nooelec SDR) moved from the development bench to a real site. Goal: run the repeater standalone (no USB host) and verify it over RF alone. This log records what happened, because the sequence of wrong theories is itself a finding.

Timeline of evidence

Setup LED (TxDone) RF at SDR Verdict at the time
Laptop USB, board on table (~16:07) double-blinks 7/7 TX clock-aligned, median +37 dB over floor baseline: transmits
Power bank (USB-C, then USB-A) went dark after seconds none bank auto-off at ~60 mA idle load
UGREEN 100 W GaN wall charger, C-to-C double-blinks "sometimes" none in 4 captures (~8 min) wrongly blamed supply sag
LiPo pack attached blinks, 2-4 double-pulses/90 s none supply theory started cracking
LiPo + dangling USB cable (no host) ~9 double-pulses/90 s none RX rate recovered; TX still invisible
Mid-capture unplug (laptop -> LiPo, position frozen) blinks throughout none in either phase laptop connection alone does NOT explain it: power theories all dead
Wall power, board hanging free, no LiPo blinks none at prior SDR-antenna position placement of the DUT alone is not it either
SDR antenna moved to ~20 cm from the hanging board blinks same-duration burst pairs at 50-54 ms: 10-10, 17-17, 16-16 ms repeater IS repeating standalone; radiated/received level is simply far lower than the laptop-connected reference

What was actually established

  1. The repeater works standalone. On wall power, hanging free, its RX->50 ms->TX cycle runs (LED) and its repeats are observable at RF (same-duration pairs at the configured delay) once the observer antenna is close enough.
  2. The laptop-connected "+37 dB at 50 cm" reference was not a pure radiated-field measurement. With the board on the host's USB, the cable shield and shared ground with the SDR dongle add counterpoise and possibly conducted common-mode coupling. Standalone, at a similar claimed distance, the same transmitter was invisible; at ~20 cm it shows up at +14..+24 dB. The gap between those numbers is the combined effect of geometry, orientation, antenna environment and the lost cable/ground contribution -- not a firmware or supply fault.
  3. Every power-source theory failed when tested properly.
    • Power bank: real failure, but trivial (auto-off). The LED found it in one glance.
    • Wall-adapter "sag during PA burst": WITHDRAWN. The adapter is a 100 W GaN unit, and the frozen-position unplug test showed the laptop connection failing at the same spot too. The earlier conviction (committed to FINDINGS.md at the time) was wrong.
    • LiPo (stiffest possible rail): same invisibility -> supply exonerated entirely.
  4. TxDone still proves nothing about radiated power. The task spec's warning (§36: "TX successful is not evidence") extends beyond FEM configuration to antenna geometry: the SX1262 completes its packet into a mismatched/shadowed antenna exactly as happily as into a good one. The LED inherits this limit: double-blink = chip-level TX, not RF.
  5. The observer's antenna position is as much a variable as the DUT's. Half of today's captures compared "device moved" against "SDR antenna wherever it happened to be". The decisive experiments were the ones that froze one side: mid-capture unplug (DUT frozen) and antenna-close (DUT untouched, observer moved).
  6. Neighbour-meter fingerprint (for future correlation at this site): 23-24 ms bursts in trains at ~28-32 ms spacing, plus 10-17 ms singles up to +42 dB that rail the dongle and produce no rtl-wmbus output. Their rate is invariant across our firmware versions, reboots and power sources -- definitively not the repeater.

Field lessons for the Solenos gateway

  • A conducted RF test port would have ended this in minutes. Half a day of over-the-air inference replaced one attenuated SMA measurement. Already in devboard_signals.csv; priority upgraded.
  • Antenna system design is not optional polish. The stock whip against a tiny PCB ground radiates so poorly, and so directionally, that deployment placement dominates link budget. The gateway needs a real antenna with a defined counterpoise, and the battery pack must be kept mechanically away from the radiator.
  • On-device persistent telemetry (NVS counters, VBAT) is still the missing piece. The LED collapsed "is it powered/alive/repeating" from four SDR captures to one glance, but every RF question still required the laptop. Retained counters would have separated "not receiving" from "not transmitting" instantly.
  • LED patterns earned their place and should carry to the gateway (with the FUTURE_UI.md caveat: an LED can only report chip state, never radiated RF).

Still open after this session

  • Clock-aligned close-antenna run (device on laptop serial + SDR antenna at 20 cm) to attribute bursts per TX event and put a number on the standalone radiated level. Protocol ready; not yet executed.
  • Quantify laptop-cable contribution: repeat the alignment run twice at identical geometry, cable in vs out (LiPo), antenna close.
  • Proper antenna A/B (e.g. quarter-wave with radials vs stock whip) -- directly relevant to the gateway RF architecture.

Location 3 (evening session) -- the beacon, and the real fault

Coordinating physical actions with an async agent kept failing (missed timestamps, tuner deaths mid-capture), so we changed instruments: a firmware beacon mode (set beacon_period_ms N) transmits a synthetic OMS frame (manufacturer SLN, ID 00000001, access_nr = sequence) every N ms. No meter traffic, no serial coordination, dense uniform sampling.

The beacon caught what two days of repeat-chasing could not:

  • TX radiated power is intermittent at minute scale. One 90 s window: 0/25 beacons produced ANY RF (max +0.5 dB over floor) while 27 ambient meter frames in the same IQ showed median +26.8 dB (observer healthy) and the chip reported TX_DONE, mode 6, device_errors 0 for every beacon. Thirty minutes later, same boot, same config: repeats, test_tx and beacons all radiated at a constant ~+10 dB.
  • RX stayed healthy through dead TX windows. Chip-side diagnostics are identical in dead and live states. The fault therefore sits between the SX1262 PA output and the antenna: KCT8103L PA path (CPS/DIO2, CTX, PA supply) or a mechanical/thermal TX-chain fault. Firmware cannot observe it -- exactly the RADIO_VDD_SENSE / conducted-test-port gap in docs/devboard_signals.csv.
  • Methodology bug found and fixed: verify_repeats_iq's single-burst clock fit can lock at -repeat_delay and "confirm" every repeat with its own original's burst. The "7/7 at +37 dB" laptop confirmations were this artifact. Trustworthy methods: structural same-duration pairs at the configured delay, content decodes (duplicate payloads), and hil/meter_anchored.py (clock fitted on strong meter receptions; ambient meter levels double as per-capture observer health).
  • Positive control: with a healthy observer, 30 structural pairs at 137 ms and 35 duplicate decoded payloads in 90 s -- the repeater function itself is solid whenever the TX chain is in its live state.

Location 3, late evening -- soak verdict and physical isolation attempt

Antenna swap + IPEX reseat performed (TX disabled during swap). Immediate post-swap check: 74/74 TX events radiating. Beacon soak started to look for recurrence (2-min segments, meter-anchored verdicts, observer health gating, dongle auto-recovery).

Soak result: the fault recurred post-swap.

  • Segments 1-8 (~16 min usable): alive, TX median +7.0..+8.8 dB.
  • Segment 9: marginal (median +5.9) -- levels visibly sagging.
  • Segment 13: dead -- 106 TX attempts, median +0.5 dB, observer independently verified healthy (56/60 meter anchors at 2.2 ms clock error, meters at +21.8 dB). Airtight.
  • The decay pattern (+8 -> +7 -> +6 -> dead over ~10 min of sustained ~50 TX/min) suggests but does not prove a thermal mechanism.

Conclusion: the old antenna and pigtail are acquitted. The intermittent TX-kill is on the board itself, in the chain between SX1262 PA output and the antenna connector (KCT8103L FEM prime suspect), invisible to every chip-level diagnostic.

Live provocation session (35 s verdict cadence):

  • Baseline: marginal-alive (+5.2), died to +2.0 within ~2 min (pressure state during death window not recorded).
  • ~90 s of breath-cooling the FEM area: no recovery (+3). Weak cooling, so thermal is not acquitted -- merely unconfirmed.
  • Pressure test: not completed; session ended.

Instrument attrition tonight: the RTL-SDR dongle required one physical replug, dropped off the USB bus once more, produced four short/empty captures and two deaf windows. Roughly a third of tonight's wall time went to working around the observer rather than observing the DUT.

Where this leaves the project

  1. Repeater firmware: fully functional and standards-shaped -- structural pairs, duplicate decodes, duty accounting (modulo ring saturation, see OPEN_QUESTIONS), recovery ladder, LED patterns, beacon mode.
  2. This particular board: not deployable unattended until the TX-chain fault is fixed or understood. Next diagnostic steps in order of value: a) proper cooling/heating provocation (freezer spray / hot-air at low temp) with the live monitor; b) pressure/flex mapping; c) conducted measurement through an attenuator to split FEM vs antenna-port; all need bench equipment or at least controlled temperature, not breath.
  3. The observer (NESDR SMArt v5) is end-of-life for serious use: replace before the next HIL session.
  4. Every hard-won methodology upgrade is now in the repo: beacon mode in firmware, hil/meter_anchored.py (borrow-immune verification + observer health), hil/beacon_soak.sh (unattended state mapping).