tiny-wb/docs/sources.md

4.6 KiB

Upstream source catalogue

This catalogue records the authoritative references used to build the local guide. It was last checked on 2026-10-04. Prefer these primary sources over retailer listings, reposted manuals, videos, and forum recollections.

Official overview and model data

Architecture, limitations, and operation

  • Ultra technical description — mixer, IF, filter, detector, generator, and calibration-source signal paths.
  • Ultra mode — low-pass bypass, mirror/spur elimination, sensitivity and bandwidth limitations, LO leakage, and unlock behavior.
  • Ultra limitations — RBW, speed, images, low-frequency sensitivity, LNA overload, and 48 MHz MCU radiation.
  • Ultra menu tree — front-panel settings, presets, SD, sweep controls, calibration, expert settings, and generator modes.
  • Ultra best-performance settings — recommended automatic expert controls and cautions.
  • RBW — coverage, noise-floor, resolution, and sweep-time trade-offs.
  • Attenuation — protection and overload/spur diagnosis.

Safety, first use, and maintenance

  • Safe operation — current DC-block, transmitter attenuation, and static precautions.
  • First use — charging, authenticity, self-test, calibration, and connection warnings.
  • Safe transmitter measurement — dBm examples and external attenuation strategy.
  • Firmware update — correct download trees, DFU tools/modes, recovery, and post-update steps.
  • Ultra battery guidance — charging current and the voltage needed for best RF performance.

USB protocol and firmware implementation

Source-conflict policy

When sources disagree:

  1. protect hardware using the most conservative official safety value;
  2. use the comparison/specification page for the exact physical revision;
  3. use on-device version, info, and help for the installed build;
  4. use source at the matching firmware revision for byte-level behavior;
  5. verify ambiguous scan semantics with a low-level known signal and preserve the transcript as a regression fixture.

The local docs intentionally record two known conflicts: the wiki's textual “MSB LSB” description versus firmware's little-endian byte writes, and endpoint-inclusive intuition versus the reviewed firmware's span / points scanraw step. Both are explained in the protocol guide.