Merge pull request #19 from Valar-Systems/feat/space-firmware

Spacescope: a third firmware product (live space-data desk monitor)

Author: daniel-frenkel

.github/workflows/firmware.yml

@@ -29,6 +29,9 @@ jobs:
           # FEATURE_EAM product: same boards, EAM monitor firmware, own OTA channel
           # (firmware-eam-<slug>.bin -- the slug must match FW_OTA_PREFIX + variant::SLUG).
           - { env: blipscope-eam-s3-146, slug: eam-s3-146 }
+          # FEATURE_SPACE product: same boards, Spacescope firmware, own OTA channel
+          # (firmware-space-<slug>.bin -- the slug must match FW_OTA_PREFIX + variant::SLUG).
+          - { env: blipscope-space-s3-146, slug: space-s3-146 }
           # - { env: blipscope-lite-s3-128,       slug: s3-128 }
           # - { env: blipscope-pro-s3-175-amoled, slug: s3-175-amoled }
     steps:

CLAUDE.md

@@ -39,6 +39,10 @@ The radar SKUs are all S3: `blipscope-s3-146` (Waveshare ESP32-S3-Touch-LCD-1.46
 - **OTA channel:** `-DFW_OTA_PREFIX="eam-"` makes [OtaUpdater](src/OtaUpdater.cpp) fetch `firmware-eam-<slug>.bin`, so an EAM device never pulls a radar image for the same board. The shared `version.txt` gate is unchanged.
 - The config web page is feature-gated in [ConfigurationWebServer.cpp](src/ConfigurationWebServer.cpp) (`#ifdef FEATURE_EAM`): the EAM form + its NVS keys instead of the radar form; the shell (mDNS, `/reset-wifi`, save flag, secret masking) is shared. Adding an EAM SKU = a variant header + an `[env:*]` (with `-DFEATURE_EAM`, the `build_src_filter`, and `FW_OTA_PREFIX`) + a CI row whose slug is `eam-<board>`.
 
+## FEATURE_SPACE — a third product (Spacescope)
+
+`-DFEATURE_SPACE` (set on the `blipscope-space-*` envs) swaps the radar app for **Spacescope** — a desk window onto live space data (ISS, rocket launches, space weather, deep-space probes) — built from the same boards and the same shared infra as the radar and EAM. It compiles **no** radar/aircraft or EAM code: the SPACE env's `build_src_filter` drops the radar-only TUs **and** `src/eam/`, `[common]` drops `src/space/` from the radar builds (and the EAM env drops it too), and [main.cpp](src/main.cpp) picks `SpaceManager` vs `EamManager` vs `AircraftManager` at compile time (same `Initialise/Update/Draw` surface). Everything Spacescope lives in [src/space/](src/space/). The config page gains a `#elif defined(FEATURE_SPACE)` branch alongside the EAM one in [ConfigurationWebServer.cpp](src/ConfigurationWebServer.cpp). OTA channel: `-DFW_OTA_PREFIX="space-"` (its own `firmware-space-<slug>.bin`). It pulls directly from free public space APIs and **bakes in no backend**; the optional `valar-space-feed` backend is the runtime `space-base-url` config (default empty, from the `SPACE_FEED_BASE` flag). **Status: Stage-1 skeleton** — the product gate, config form, OTA channel, and the rotation/touch/brightness shell with a splash + UTC clock are in; the feed client + data screens land in later stages (each = a feed + a `DrawX()` + a `HasData()` case).
+
 ## The C3's three hard constraints — read before changing memory, networking, or touch
 
 These applied to the now-**retired C3 Kit** SKU: a **single-core RISC-V** chip with a tight, fragmenting heap — most non-obvious shared code exists to live within that. The board is gone, but its guards stay in the tree (inert on S3, gated by capability flags), so this section stays as reference and a C3 could be revived: **don't "simplify" the guards away.** The S3 SKUs (dual-core + PSRAM) relax all three (full framebuffer, enrichment always-on, touch and network on separate cores) via the variant's capability flags rather than by deleting the guards:

RELEASING.md

@@ -51,6 +51,18 @@ These ride the **same** `version.txt` gate (one `FW_VERSION` bump releases radar
 and a device only ever downloads its own `<prefix><slug>` binary. Releasing is otherwise identical
 — the matrix rows are already in [.github/workflows/firmware.yml](.github/workflows/firmware.yml).
 
+## Spacescope builds — another separate OTA channel
+
+The `blipscope-space-*` envs build a third **product** (Spacescope, `-DFEATURE_SPACE`; see
+[CLAUDE.md](CLAUDE.md)) from the same boards. Same arrangement as EAM: `-DFW_OTA_PREFIX="space-"`,
+and a CI slug prefixed to match so a Spacescope device never pulls a radar or EAM image:
+
+| env | slug (CI + OTA asset) |
+| --- | --- |
+| `blipscope-space-s3-146` | `space-s3-146` → `firmware-space-s3-146.bin` |
+
+Same `version.txt` gate (one `FW_VERSION` bump releases radar, EAM, and Spacescope together).
+
 ## Legacy note: the retired C3
 
 The original ESP32-C3 Kit is retired — Blipscope is S3-only going forward. The workflow no

platformio.ini

@@ -25,10 +25,10 @@ build_flags =
     ; Shrink ESPAsyncWebServer's per-send buffer from 2x TCP_MSS (2872 B) to 1 KB so it
     ; fits a fragmented heap on the tightest board; roomier boards are unaffected.
     -DASYNC_RESPONCE_BUFF_SIZE=1024
-; Default source set: the radar app. The FEATURE_EAM cluster (src/eam/) is a separate
-; compile-time product, so it's excluded here; the EAM envs below override this filter to
-; pull in src/eam/ and drop the radar-only sources instead.
-build_src_filter = +<*> -<eam/>
+; Default source set: the radar app. The FEATURE_EAM (src/eam/) and FEATURE_SPACE (src/space/)
+; clusters are separate compile-time products, so they're excluded here; the EAM / SPACE envs
+; below override this filter to pull in their dir and drop the radar-only sources instead.
+build_src_filter = +<*> -<eam/> -<space/>
 board_build.partitions = min_spiffs.csv
 lib_deps =
     lovyan03/LovyanGFX @ 1.2.21
@@ -121,6 +121,41 @@ build_src_filter =
     -<AircraftInfoFields.cpp>
     -<Logbook.cpp>
     -<models/>
+    -<space/>
+
+; ===================== Spacescope (live space-data monitor) ===========
+; A third compile-time PRODUCT from the same repo and boards: -DFEATURE_SPACE swaps the radar app
+; for Spacescope (src/space/) -- a desk window onto ISS / launches / space weather / deep-space
+; probes. Reuses all the shared infra (display, Wi-Fi, web config, storage, HTTP/TLS, OTA, ntfy)
+; but NOT the radar/aircraft/ADS-B code or the EAM cluster, which build_src_filter strips.
+; FW_OTA_PREFIX puts it on its own OTA channel (firmware-space-<slug>.bin). It pulls directly from
+; free public space APIs and bakes in NO backend; the optional valar-space-feed backend (Phase 3)
+; is the runtime "space-base-url" config, defaulting to the SPACE_FEED_BASE flag (empty by default).
+; Runs on the S3 1.46" AMOLED.
+[env:blipscope-space-s3-146]
+extends = common
+board = esp32-s3-devkitc-1
+board_build.arduino.memory_type = qio_opi
+board_build.flash_size = 16MB
+board_upload.flash_size = 16MB
+board_build.partitions = default_16MB.csv
+build_flags =
+    ${common.build_flags}
+    -DBLIPSCOPE_VARIANT_S3_146
+    -DFEATURE_SPACE
+    -DFW_OTA_PREFIX=\"space-\"
+    -DBOARD_HAS_PSRAM
+    -DARDUINO_USB_MODE=1
+    -DARDUINO_USB_CDC_ON_BOOT=1   ; native USB-CDC: upload + monitor over the USB-C port
+build_src_filter =
+    +<*>
+    -<AircraftManager.cpp>
+    -<MqttPublisher.cpp>
+    -<SpecialAircraft.cpp>
+    -<AircraftInfoFields.cpp>
+    -<Logbook.cpp>
+    -<models/>
+    -<eam/>
 
 ; ===================== Assembled S3 tiers (TODO) ======================
 ; Added at hardware bring-up: each needs a variant header in include/variants/