findings: withdraw supply-sag conviction; field test record - standalone repeats confirmed, geometry dominates
This commit is contained in:
@@ -0,0 +1,87 @@
|
||||
# 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.
|
||||
Reference in New Issue
Block a user