TheOrc.devOregon Radio Company LLC

esp-web-install --chip esp32p4 --channel nightly nightly-df1fd7e

OrcSDR nightly build

Nightly build from main. Includes changes headed for the next release. They've passed testing but haven't had a full release check, so expect the occasional bug. For the tested release, use the regular installer.

OrcSDR nightly-df1fd7e · built 2026-11-11 10:07 PST · 18 merged changes since v0.5.0-beta.1 · 6.4 MB

Nothing newer than v0.6.0 is on main right now, so there is no nightly to install. Use the regular installer.

commit df1fd7e · all changes since v0.5.0-beta.1 · GitHub nightly release · build log

Your saved settings are kept unless you choose to erase. Like the regular installer, this writes only the bootloader, partition table and OrcSDR app and leaves the settings (NVS) area alone. When it asks Erase device, leave the box unticked to keep Wi-Fi, location and rotation.

Reporting a bug

On the Tab5, open Settings → System: the BUILD line shows nightly df1fd7e 2026-11-11 for this build. Put that line in your bug report so the exact commit is known.

Going back to the release

Install the release from the regular installer at any time. If settings act strange afterwards, install again and tick Erase device (you'll re-enter Wi-Fi).

What's new since v0.5.0-beta.1

  • #240 rtl_tcp remote receiver + esp-rtl-sdr driver v0.9.6 pin
    details · 12 lines
    ## Summary This PR now carries two things, at the owner's request: 1. **rtl_tcp remote receiver** (branch `claude/orcsdr-rtl-tcp-interop-f12b5d`, merged in): the Tab5 can take its IQ from a standard `rtl_tcp` server on the network, and can serve its own dongle. 2. **esp-rtl-sdr driver pin v0.9.5 to v0.9.6** (`dabdda1aff6aa196f3c1523d791adf80d2c24ccc`), the original purpose of this PR. Scope against `main`: 106 commits, 81 files, 9,398 lines added and 97 removed. Most rtl_tcp code is in its own modules (`ui/rtl_tcp_*.cpp`, `ui/source_capabilities.cpp`, `ui/settings_remote_source.cpp`); `main.cpp` changes are thin hooks. The full test record is `docs/RTL_TCP_RELEASE_TEST_PLAN.md` (51 iterations, the latest on 2026-11-10). ## rtl_tcp Delivers the request in #235 (rtl_tcp client support). Follow-ups are filed as #243 (review items and untested paths) and #244 (the ESP-Hosted channel to the C6 can stop answering). - **Client:** standard protocol; link-adaptive rate ladder (1.44, 0.96, 0.24 MS/s); reconnects forever (fast attempts, then every 30 s); reports a server whose one client slot is taken as "server busy or silent" and waits up to 2 minutes for it; waits up to 250 ms for a free DSP slot so short stalls cause delay, not lost samples. …
    more on GitHub
  • #241 Fix the Tab5 nightly configure after esp_hosted 3.1.0
    details · 16 lines
    * fix: let the Tab5 nightly configure past esp_hosted 3.1.0 USB rules esp_hosted 3.1.0 gates USB components on promptless Kconfig ints that 3.0.6 does not define. The solver still evaluates 3.1.0 because esp_wifi_remote requires esp_hosted >=2.11, so hosted3 configure fails after the missing-kconfig retry. Define those ints as 0 so the USB rules do not match and the 3.0.6 pin stays in place. Run the nightly Tab5 build on pull requests that change the firmware. * fix: keep the PR Tab5 build id within the 39-character limit The firmware rejects ORCSDR_BUILD_ID longer than 39 characters. A full pull-request SHA exceeded that before configure ran. ---------
  • #239 Prevent Tab5 USB recovery crashes in normal builds
    details · 10 lines
    A receiver disconnect during enumeration recovery can crash the Tab5 inside ESP-IDF's USB host stack. This change tolerates an already-removed device node and preserves root-port state when power-off is rejected, allowing USB events and later retries to continue. Tab5 builds automatically prepare the reviewed USB component in their own build directory before ESP-IDF resolves components. The shared SDK is preserved. Stock ESP-IDF 5.5.4 source hashes and generated sources are verified; unsupported or modified sources fail configuration clearly. Validation: - The full ESP-IDF 5.5.4 integration build at 0c7c2a5d completed all 1686 steps. build.ninja selects the generated patched hub.c and usb_host.c. Application size: 0x41d120 bytes; 31% factory slot free. - At follow-up 9dc5fb44, python tools/test_prepare_usb_recovery.py --idf C:/Espressif/frameworks/esp-idf-v5.5.4 passed generation, reuse, SDK preservation, tamper/source/version rejection, and injected copy/patch/marker failures with cleanup and successful retry. Direct preparation also verified reuse of the integration build override. - .review-usb-check/run-tests.cmd passed the source-extracted MSVC C harness: rejected power-off, event recovery, power cycle, already-off, missing-node recovery and re-enable. Original code reproduced the expected ret == ESP_OK assertion. git diff --check passed. - The follow-up changes preparer error handling and encoding, tests and documentation; the compiled SDK patch is unchanged. …
    more on GitHub
  • #236 docs: clarify P25 import, clock setup, and installation
    details · 7 lines
    * docs: clarify P25 import, clock setup, and installation * docs: omit outdated P25 programming screenshot * docs: address clock and installer review findings * docs: clarify P25 import error wording
  • #233 Show E4000 tuning limits on OrcSDR dashboards
    details · 7 lines
    * Show E4000 tuning limits on OrcSDR dashboards * Show unsupported tuner in the Home waterfall * Document the OrcSDR driver pin and E4000 warning * Address E4000 dashboard warning review findings
  • #232 docs: reconcile native decoder inventory and field-verified OrcSDR capabilities
    details · 40 lines
    * docs: record maintainer RF acceptance and distinguish measurement from interpretation * docs: promote verified reception and clarify E4000/Dead Air capabilities * docs: promote verified reception and clarify E4000/Dead Air capabilities * docs: promote verified reception and clarify E4000/Dead Air capabilities * docs: reconcile detailed dashboard pages with field acceptance * docs: reconcile detailed dashboard pages with field acceptance * docs: reconcile detailed dashboard pages with field acceptance * docs: reconcile detailed dashboard pages with field acceptance * docs: reconcile detailed dashboard pages with field acceptance * docs: reconcile detailed dashboard pages with field acceptance * docs: reconcile detailed dashboard pages with field acceptance * docs: reconcile detailed dashboard pages with field acceptance * docs: reconcile detailed dashboard pages with field acceptance * docs: reconcile detailed dashboard pages with field acceptance * docs: add user-facing Dead Air measurements and VEIL-26 disclosure * docs: update architecture, E4000 UX and Dead Air guide navigation * docs: update architecture, E4000 UX and Dead Air guide navigation * docs: update architecture, E4000 UX and Dead Air guide navigation * docs: update architecture, E4000 UX and Dead Air guide navigation * docs: reconcile roadmap architecture and historical phases with field-verified capabilities …
    more on GitHub
  • #231 docs: refresh OrcSDR feature and receiver status
    details · 36 lines
    * docs: distinguish fully supported receivers from E4000 integration status * docs: distinguish fully supported receivers from E4000 integration status * docs: distinguish fully supported receivers from E4000 integration status * docs: distinguish fully supported receivers from E4000 integration status * docs: distinguish fully supported receivers from E4000 integration status * docs: distinguish fully supported receivers from E4000 integration status * docs: refresh user-facing feature maturity and remove stale route descriptions * docs: refresh user-facing feature maturity and remove stale route descriptions * docs: refresh user-facing feature maturity and remove stale route descriptions * docs: refresh user-facing feature maturity and remove stale route descriptions * docs: refresh user-facing feature maturity and remove stale route descriptions * docs: refresh user-facing feature maturity and remove stale route descriptions * docs: refresh user-facing feature maturity and remove stale route descriptions * docs: refresh user-facing feature maturity and remove stale route descriptions * docs: promote SSTV from stale experiment label using four-dongle conducted evidence * docs: promote SSTV from stale experiment label using four-dongle conducted evidence * docs: promote SSTV from stale experiment label using four-dongle conducted evidence * docs: refresh current release baseline and separate historical accessory evidence …
    more on GitHub
  • #229 Integrate driver 0.9.4 with E4000 gain, identity and offset controls
    details · 9 lines
    * Integrate released SDR driver 0.9.4 and E4000 controls * Update current driver pin documentation to released 0.9.4 * Record clean 0.9.4 integration build and remaining board gates * Address review: E4000 self-check, rate-safe IQ and accurate gain help * Record review-fix build and maintainer merge scope
  • 0b60a16 docs: summarize all dashboards in concise README section
  • d71932b docs: reduce visualization emphasis in README
  • #226 feat: paired OrcDial FT8 preview and SSTV receive controls
    details · 8 lines
    The paired OrcDial can show genuine FT8 decode summaries/text and actual SSTV receive progress, mode and SD archive outcomes. SSTV save, abort, demodulation, gain and tuning reuse receiver handlers with reception guards. Authenticated serial SSTV DETECT AUTO|VIS exposes the existing detection setting for repeatable testing. FT8 preview delivery is negotiated, bounded and tied to the receiver/session/dashboard context. The existing secure protocol, trust storage and C6 firmware are preserved. Matching Dial UI and persistent quick-mute sound controls: https://github.com/hardcoreerik/OrcDial/pull/14. Validation: optimized and sanitizer FT8/state checks, the targeted SSTV host suite, 11 standalone Dial host tests and production Dial/native Tab5 builds passed. Both application-only flashes passed hash verification. Prior live 20 m FT8 tests delivered new matching station records. The final paired internal Robot36 bench passed new receive progress/completion, retune protection and confirmed SD save. A separate two-step abort ended the confirmed session and recorded ABORTED. These SSTV tests use internal synthetic audio, not RF reception. Repeatable automation and exact evidence: [SSTV companion](docs/SSTV_DIAL_IMPLEMENTATION.md), [FT8 device tests](docs/ORCDIAL_FT8_DEVICE_TESTS.md), [FT8 validation](docs/ORCDIAL_FT8_VALIDATION.md), [live FT8 evidence](docs/ORCDIAL_FT8_HARDWARE_2026-10-30.md). Real WAV replay was skipped without a fixture. …
    more on GitHub
  • #227 Add consistent development support links
    details · 10 lines
    Adds GitHub Sponsors, Ko-fi, and PayPal links in the README and GitHub funding configuration. Concise copy explains development time, hardware testing, receiver compatibility, and decoder work across ORC. Validation: YAML parsed with PyYAML; exact funding values and README URLs asserted; git diff --cached --check passed; changed-file scope checked; pushed SHA verified on origin. Documentation/configuration only; application and firmware suites not run. Ready for review. No merge, deployment, payment, account, or tier changes. ## Summary by CodeRabbit * **Documentation** * Added a “Support development” section with links to available contribution options.
  • #220 Dead Air: Environment tab trend charts
    details · 22 lines
    ## Summary - The Environment tab now plots temperature, humidity and pressure as three trend lines (1 H / 6 H / 24 H windows, tap cursor with value and age). - Each point is the mean of accepted ENV III samples in one minute, kept for 24 h (`dead_air_envhistory`, 1440 x 3 x int16 = 8.4 KB inside the PSRAM-resident session state). - A minute with no valid reading is a gap and the line breaks there; nothing is interpolated. Axis ranges are never narrower than 2 C / 10 %RH / 4 hPa. - DEVICE MOTION moved to the left panel. ## Verification - Host tests: new `dead_air_envhistory_tests` and a renderer block (lines per chart, gap breaks, window buttons, cursor, no full-screen clear on repeated updates). All Dead Air host suites I run locally pass. - Native ESP-IDF 5.5.4 Tab5 build clean (0x51c430, 15% app partition free). - Flashed to COM39 and Dead Air opened on the Environment tab over serial. **Not visually checked on the panel**; flicker and layout are unverified. ## Limits - History lives in memory for the session and is not written to SD yet. 🤖 Generated with [Claude Code](https://claude.com/claude-code) ## Summary by CodeRabbit * **New Features** * Added Environment-page trend charts for temperature, humidity, and pressure, with one-minute averages and selectable 1-, 6-, and 24-hour views. * Missing readings appear as gaps. Tap a chart to inspect a historical value, or tap near the selection to clear it. …
    more on GitHub
  • #223 ACARS: native VDL Mode 2, interpreter, SD log tooling
    details · 13 lines
    ## What ACARS on the Tab5: a native VDL Mode 2 receiver on the dashboard, a plain-language interpreter for what used to be raw text, and tooling to work with the SD log. - **VDL Mode 2 (136.725 to 136.975 MHz)** through the existing native D8PSK / Reed-Solomon / AVLC chain; analog ACARS untouched. ACARS inside AVLC frames posts like an analog block; other frames are kept as hex. `main.cpp` net +2 lines (hook signatures only). - **Interpreter** (`acars_interpret.cpp`, pure function, no per-record RAM): squitters, acks, FMC and label 21/22/10/17/32/33 positions, fault displays, Southwest/United/Alaska flight-data headers and rows, ARINC 622 envelopes with CRC, D-ATIS requests with CRC, T1, in-range. A field that is not understood is shown as received. `decoded` is true only when text was understood (honest share of one day: 63%). - **Archive**: 2000 blocks in PSRAM (was 300), 1 MiB of the log read at boot. `SD_GET` of `/orcsdr/acars/*` allowed while receiving. - **Receiver self-heal** when the radio's stream moves to another rate. - **Tools**: offline log analysis (`tools/acars_log`, written by Codex from a brief, lightly reviewed), ADS-B/adsb.lol cross-check scripts (development only; the product needs no accounts). - **Docs**: captures with cross-references (adsb.lol, OpenSky, FAA, OurAirports), `INTERPRETER.md`, format research, info-page text, changelog. ## Verification …
    more on GitHub
  • 72bb486 docs(community): Axeman72 handheld case V1 community hardware
    details · 5 lines
    Design credit: Axeman72, original OrcSDR PR #212, Discussion #202. Import nine original STL files, assembly image and designer README unchanged; update community hardware catalog, documentation, and release attribution guidance. Community-designed prototype. The project's AGPL-3.0 license is the proposed default for these hardware files, pending explicit creator confirmation. No physical print testing claimed.
  • #221 Dead Air: VEIL-26 / ESOTERICA optional symbolic analysis engine
    details · 9 lines
    ## Summary An opt-in analysis engine that turns Dead Air's **measured** tuned frequency and level into **symbols** (letter, dictionary word, gematria) with a fixed, reproducible recipe. It is not a detector: no new acquisition, no new event detector, and it never raises or edits a Dead Air event. Design, algorithm, provenance gaps, bounds and usage are in `docs/dead-air/VEIL26.md`. - `dead_air_veil26`: SHA-256 seed, Python-compatible rounding, both quantization conventions (frequency-log is used for RF; spectral is implemented, unused), 32-bit recurrence, A1Z26 and Pythagorean gematria, and the `Stream` pacing policy (at most one frame a second from a usable observation, one per RF/audio event; retunes and unusable observations are counted breaks, never fabricated frames). - `dead_air_veil26_log`: self-contained JSONL records plus a bounded 16-slot queue. The SD worker writes `veil26_<session>.jsonl` (at most 4 lines per 100 ms), apart from the measured-event journal; every line is `"interpreted":true`. A write failure ends that file only. - Overlay (Overview and Events entry points, six tabs unchanged) with a MEASURED panel and a SYMBOLIC / INTERPRETED panel. Serial: `RTL_DEAD_AIR VEIL`, authenticated `ON|OFF|INTENT <text>`. ## Known gaps (please read) …
    more on GitHub
  • #222 CI: nightly embeds the reviewed world map at orcmaps_world like releases
    details · 10 lines
    Fetch the pinned Natural Earth z0-z4 PMTiles (SHA-256 9aea0877...) from the v0.5.0-beta.1 release, pass it as ORCSDR_WORLD_MAP (same as build-tab5-idf.ps1 -WorldMap), cache it, and fail the build unless the merged image has it at 0x650000. CI and build scripts only; no firmware source changes. ## Summary by CodeRabbit * **Chores** * Tab5 firmware builds now include verified world-map data in the generated image. * Nightly and SSTV build pipelines fetch and reuse the map, and check that it is correctly included in the firmware.
  • #219 Dead Air: ENV III driver and events, PSRAM reclaim, shared replay buffer
    details · 19 lines
    ## What - ENV III (SHT30 + QMP6988) driver on Port A, and temperature / humidity / pressure departures logged as Dead Air events (learned baseline, hold time, hysteresis, per-sensitivity limits). Host tests in `tests/dead_air_envevents_tests.cpp`. - Fixes "no memory" on Play Selected / Start mic: failed PSRAM requests ask registered holders (LoRa IQ, map, SSTV) to release and retry; clip ring retries; audio buffers are freed when the screen is left; each reclaim/refusal is logged. - Replay borrows the mic ring's buffer (saves 1.15 MB). A running mic is stopped for the replay and restarted after; Start mic is refused while a clip plays. - Keyboard probe backs off to once a minute and mutes the expected I2C miss errors. - Reproducible M5GFX-faithful mockups (`tools/dead_air_mockup.py`, `docs/dead-air/mockups/`) for the planned DETECTED banner, night report and tune popup (design only). ## Verification - Host suite (`all.sh`, incl. envevents) passes; firmware builds (0x51b210, 15% free). - Flashed to a Tab5 (COM39): ENV III reads, env events logged, no `i2c.master` errors over 25 s. - NOT verified on hardware: shared-buffer replay with the mic running, free-on-leave PSRAM recovery, whether the LoRa holder releases while on the LoRa band. Expect a trivial conflict in `main/CMakeLists.txt` with #213/#204. ## Summary by CodeRabbit * **New Features** * Added temperature, humidity, and pressure readings, with alerts for sustained environmental changes. …
    more on GitHub

How nightly works

  • Built automatically from main of hardcoreerik/OrcSDR each night (about 3:23 am Pacific), only when main changed and the automated tests pass.
  • Erik only merges to main what he's happy with and plans to ship. It just hasn't had the full release check yet.
  • When main is the same as the latest release, there's no separate nightly. Use the release.
  • Same Web Serial installer as the release: desktop Chrome or Edge, USB-C data cable. See the regular installer for step-by-step and troubleshooting.

Check the file

parts this page writes
0x02000 bootloader          24,032 bytes
  ac5970762e1a5bc81129e1b5f28b11ac
  e9f7416137478235278bca6151cc79e8
0x08000 partition-table      3,072 bytes
  9c5666389dc34dfaa3f7d8539be3d335
  6b9a16b5b1ca4652554bf1e8838d9001
0x10000 factory          5,501,872 bytes
  0fb52f00fd6a0d7b13e1938d6b1bc526
  1d16ecf85317b49cfbf979d1f8a3d231
0x650000 orcmaps_world      871,343 bytes
  9aea08772bacf1f024d1da90cc52aa8f
  cf0b0e37405415dc7c91e75e56596f0f

nightly .bin (complete image, 0x0)
OrcSDR-Tab5-nightly-df1fd7e.bin
size    7,490,479 bytes
sha256
  95b0302f8d338c7596f2df05b49c2107
  735f48011af4a31b0605f8108d3978b1

Source: hardcoreerik/OrcSDR (AGPL-3.0) · nightly prerelease · installer by ESP Web Tools.

You're responsible for operating a radio receiver legally where you live.