Skip to content

Automatic scanning — planned

Automatic spectrum scanning is deferred, not an available session mode. Phase 4 was deferred by the operator on 2026-08-27 and remains open. Current source implements manual receiver lanes, detection, candidate analysis and explicit activation, but no automatic scan-plan scheduler, scan state machine or scan-results history. A route's scan purpose is policy metadata, not proof of a working scanner. Phase 5 mobile scan interactions and Phase 7 native broker actions remain separate future work.

This chapter preserves the design requirements formerly detailed in the opening WEBSDR overview. It is not a tutorial for controls that do not exist. The original Phase 4 checklist remains the acceptance ledger.

Scan types

  • Visible-window scan: inspect the current captured passband without a hardware retune; several simultaneous signals may share that window.
  • Band sweep: retune across configured ranges with overlap to avoid losing signals at FFT edges.
  • Channel-list scan: visit explicit frequencies, names, modes and settings.
  • Priority scan: revisit important ranges/channels more often while still covering the rest of the plan.

Configurable scan plan

A plan must preserve these requested choices:

  • Automatic use of all eligible routes, or a compatible receiver/path pin.
  • One or several bands, arbitrary ranges or saved channel lists.
  • Included and excluded frequency ranges.
  • Receiver/transverter/upconverter translation.
  • Center-frequency step or automatic overlap.
  • Sample rate and usable bandwidth per step.
  • Scan speed and fast/balanced/thorough presets.
  • Tuner settling after a hardware retune, distinct from observation/dwell time.
  • Minimum SNR above local noise.
  • Minimum and maximum occupied bandwidth.
  • Minimum persistence or burst count before acceptance.
  • Desired modulation, protocol or service families.
  • Whether known spurs, stations or dismissed signals are ignored.
  • Stop, temporary hold or continue after detection.
  • Resume delay after a hold or operator action.

Validate ranges and complete passbands against route translation and hardware capabilities. An HF upconverter's displayed RF must not be treated as the tuner frequency. Keep frequency coordinates and source evidence explicit.

Cooperative scheduling

One logical plan partitions windows/channels across every eligible, available receiver route. Distinct receivers operate concurrently where they contribute coverage; detections retain receiver serial and route, and progress/results aggregate into that plan. Avoid duplicate coverage unless redundancy is requested, rebalance around unavailable receivers and never seize a receiver pinned to incompatible manual work. Manual listening on one receiver and scanning on another must remain valid. Release a finished receiver independently even while other assignments continue.

Local manual, scan and decoder consumers need explicit references to their owning lane/session. Reuse its IQ and shared decoder manager/admission controls; do not open another SDR connection, create a scan-only decoder path or treat today's gateway 0/1 consumer_count as an implemented multi-consumer scheduler.

State and operator handoff

The intended state machine is:

flowchart TB
    IDLE[Idle] --> TUNE[Tuning]
    TUNE --> SETTLE[Settling]
    SETTLE --> OBSERVE[Observing]
    OBSERVE --> DETECT{Accepted detection?}
    DETECT -->|no| NEXT[Next window/channel]
    NEXT --> TUNE
    DETECT -->|yes| ACTION{Configured action}
    ACTION --> ASK[Hold and ask]
    ACTION --> CONTINUE[Run actions and continue]
    CONTINUE --> NEXT
    ACTION --> STOP[Stop and hand control to operator]
    ACTION --> HOLD[Temporary hold]
    HOLD -->|resume delay| NEXT

Display state, range, frequency, progress, dwell and next action continuously. Manual dialing pauses or ends the scan through an explicit transition, never fights the controller. This diagram specifies future behavior, not a current runtime implementation.

Multiple signals and actions

Keep confirmed candidates highlighted and rank by operator interests, SNR, persistence, supported confidence and novelty. Allow one or several selections and individual/batch actions while continuing to track the remaining signals inside the capture. Internal ranking scores must not masquerade as calibrated probabilities. One audible focus is the initial requirement; multiple VFOs and decoders within one captured passband remain subject to later performance work.

Per-plan and per-signal action rules must support:

  • Highlight/information only, or stop and ask.
  • Tune/listen automatically, or listen for a configured hold then resume.
  • Start a compatible manifested decoder through the shared job manager.
  • Record demodulated audio.
  • Record a bounded pre/post-detection IQ interval using the rolling buffer.
  • Save spectrum/waterfall snapshots and bookmarks with source metadata.
  • Add/update results and notify the operator.
  • Ignore, dismiss once, or maintain a local ignore/spur list.

An action must respect pins, explicit automation policy, cancellation and decoder input/validation requirements. Browser storage/download is the recording default. Any future Pi recording needs explicit enable, time/space bounds and SD-wear controls. DVR is not already a durable recording/export service.

Results and export

Retain detection/last-seen times, receiver/plan, RF and scan-window center, supported mode/protocol/service assessments, SNR, bandwidth, duration, duty and drift, repeated-detection count and actions. Include recording, snapshot, bookmark and decoder-result links plus operator classification, notes and dismissed/interesting state. Preserve evidence behind confidence labels and export enough acquisition/plan metadata to reproduce the scan and use selected captures in decoder/classifier tests. None of these requirements is fulfilled merely by exporting a current detector snapshot.

Receiver ownership and power

Every participating receiver uses its existing serial-keyed lane lease and public sdr-demandd port, counting as an active client. Never interrupt an existing SDR++ or WebSDR controller. Stop/cancel releases each receiver when its assignment and other authorized local consumers are finished; demand idle shutdown still owns clean backend close and logical USB disable.

Distinct receivers may scan concurrently while a pinned receiver stays manual. A future trunking mode may use one control-channel receiver and another traffic receiver, but must preserve serial-keyed isolation; it is not implemented by this documentation. Show elapsed scan time and the power consequence: scanning intentionally keeps receivers awake longer. Battery operation makes that cost especially relevant, but battery power is not assumed for every appliance.

Qualification boundary

The full Phase 4 gate includes cooperative scans and independent manual use, busy/fault rebalancing, no-steal/duplicate-coverage rules, history/export, disconnect/cancellation, power/idle paths and manifested decoder integration. Source inspection and a docs build do not close any item. Phase 5 mobile navigation and Phase 7 native workers need their own acceptance.

See receiver ownership, explicit activation and the roadmap/source map.