DRACO7RT · ground systems · 29 October 2026 · site names checked 10 November 2026
What the ground segment looked like on 22 July 2026, what was added, changed and fixed since, and what was deliberately left alone
The baseline delivery was one ground station: COSMOS 7.2.1 with the DRACO plugin, logged into directly. Today the same vehicle feeds two equal stations plus a mission planner, behind one sign-in, with retention, a clean-start rule, an archive, operator tooling and a verification script that proves all of it. Every product is still stock; everything that is ours lives in the repository.
Slides 2 and 3: the baseline and the architecture before and after. Slides 4 to 9: COSMOS, access, the viewer and demo control, hygiene, the tee. Slides 10 to 12: Yamcs, PlanDev, Open MCT and Grafana. Slides 13 to 18: operator additions, verification, what was not changed, gaps, timeline, where to find things.
Baseline
DRACO7RT ground changes · 2 / 18 · git: first commit 2026-07-22 “Baseline: DRACO7 QEMU stack + cFS Draco 7.0 operational app suite”
Architecture
The vehicle still sends one telemetry stream and still accepts commands on one port; the IPs are baked into its boot image and were not touched. Everything new sits on the fogi_net bridge beside COSMOS or behind nginx on the host.
DRACO7RT ground changes · 3 / 18
COSMOS
Bootstrap installs a plugin only when absent. An installed plugin is upgraded by staging the new gem under the installed name (run/upgrade-plugin.sh <dir> <version>, then front door › Demo control › HEALTH › Downlink / map, i.e. --per-boot); installed versions show under Viewer › Tools › Admin, Plugins tab; a plain install of a new version crashes COSMOS’s installer (“targets:AC already exists”) and deletes the old gem.
DRACO7RT ground changes · 4 / 18 · cosmos/openc3-cosmos-draco, cosmos/openc3-fogi-open-source, claude-notes/CMD-AUDIT-2026-10-22.md
Access
COSMOS’s own login page and password, shared by everyone; no record of who did what.
Only /slides/ (decks and PDFs) and the sign-in card are open to outside visitors, plus, since 3 Nov, the static file /yamcs/opi.standalone.js (Yamcs’s open-source display renderer, in a sandboxed frame that gets no cookie; data stays gated). Everything else is gated, COSMOS too since 10 Nov; a new static path needs its own gated location and the exact-match redirect, or it falls through to COSMOS (a 404 there once signed in).
Absolute next URLs after sign-in are allowed only for plan.draco.efsi.com; a sibling host must be added to both the service and the page script.
DRACO7RT ground changes · 5 / 18 · web/control/README.md “Auth model”, run/nginx-draco.efsi.com.conf
Front door
DRACO7RT ground changes · 6 / 18 · web/viewer/, web/control/draco_control.py, run/draco-vehicle.service
Hygiene
Unattended, COSMOS wrote 1 to 3 GB a day: QuestDB rows for the 10 Hz 42 streams, raw packet logs (about 90 MB a day) and 1.2 GB a day of “API data” INFO lines from the wall’s polling and the bridge’s inject calls. Yamcs added about 256 MB a day.
Prunes Docker build cache older than 7 days and dangling images only (never image prune -a: tagged images without a container belong to this and other projects), re-applies the retention settings if lost, archive retention (raw 90 days, Parquet 365 days), reports sizes, warns at 80 % disk.
DRACO7RT ground changes · 7 / 18 · run/clear-data.sh, run/disk-cleanup.sh, run/draco-cleanup.timer
Transport
TO_LAB sends its one telemetry stream to one address. A second station needs a copy of every datagram, and the vehicle’s addresses are baked into its boot image.
The tee is a single point for both stations’ telemetry. It is kept trivial (one Python file), restarts unless stopped, and the verify script watches its counters.
DRACO7RT ground changes · 8 / 18 · run/downlink-tee/, run/compose.yml
Second station
| Piece | What was added | How it touches Yamcs |
|---|---|---|
| Image and instance | Release tarball pinned by sha256, instance draco, UDP telemetry from the tee, packets stamped with reception time (the vehicle clock is not UTC), context path /yamcs behind the gate (front door › Ground stations › Open Yamcs and Viewer › Yamcs › Home open the draco instance’s Home page directly) | documented config keys only |
| Mission database | Generated from the COSMOS definitions by tools/ground/cosmos2xtce.py: 2,139 parameters, 262 commands, 39 containers; --check fails on drift; overlays add Yamcs-only parameters (LC actionpoint states) | XTCE 1.2 |
| Event decoder | DracoEventDecoder: the stock cFS decoder assumes a 12-byte telemetry header, this build’s is 16; flight events become Yamcs events (source = app, type = EVID) | public Java API |
| Alarm auto-acknowledge | DracoAlarmAutoAck: an alarm leaves the active list once the value is back in limits, stays in history (5.13 cannot configure this) | processor service |
| Commanding | Link tc-out to the vehicle, stock cFS post-processor (length, sequence, XOR checksum), disabled at start; switched on the front door, Demo control › COMMANDING STATION › Switch to Yamcs / Switch to COSMOS (badge shows who commands; strip cell Commanding); one commanding station at a time | stock link class |
| CFDP engine | The Yamcs CfdpService (entity 21) is the CFDP engine for both stations; COSMOS drives it through the REST API; Class 1 and 2 both ways (Yamcs › File transfer; Viewer › Mission › File transfer (CFDP)) | stock service |
| Operator aids | 14 displays generated from the COSMOS screens (cosmos2opi.py; Yamcs › Telemetry › Displays, folder DRACO), 7 parameter lists (Telemetry › Parameter lists), 9 command stacks (Stacks, folder DRACO), the mission test as a script activity (Scripts, log on Activities; front door › Demo control › YAMCS › Mission test (Yamcs); 9 of 9 in 177 s, 25 Oct) | buckets, REST |
| Verification | selfcheck.py proves every customization is live; part of --verify | REST |
DRACO7RT ground changes · 9 / 18 · run/yamcs/README.md (the full table and the upgrade procedure)
Planning and views
DRACO7RT ground changes · 10 / 18 · run/plandev/, tools/plandev/, run/openmct/, run/grafana/
Operator tooling
| Addition | Date | What it does, and where it is |
|---|---|---|
| Composite COSMOS pages and walls | Aug to Oct | 13 FOGI pages: mission home, GNC, deployments, propulsion, limits and autonomy, sequences, events, app health, four dense 1920×1080 walls, saved layouts. Viewer (tile Mission Control) groups Home, Wall, GNC, Mission |
| Mission test | Aug | Nine phases from pad check to IMU fault recovery, as a Script Runner procedure and, since Oct, as a Yamcs script activity and stack; records evidence runs. Front door › Demo control › MISSION › Mission test (COSMOS) and YAMCS › Mission test (Yamcs) |
| Decks and the slides site | 30 Sep | Presentations with fixed links (thirteen on 29 Oct, fourteen now), rendered to /slides/ (public) with PDFs. Front door: blue Presentations button (header) or tile Presentations |
| CFDP file transfer | Oct | COSMOS CF/CFDP screen (Viewer › Mission › File transfer (CFDP)) and demo procedure, Yamcs › File transfer, front-door demo with 20 % loss and evidence (Demo control › YAMCS › CFDP file-transfer test) |
| Table Workbench | 27 Oct | RTS editor from the COSMOS dictionary, app-table editors over the compiled layouts, rule checks, delivery by CFDP and Table Services, audited jobs. Tile Table Workbench (/tables/), tabs 01 Sequences, 02 App tables, 03 Check, 04 Deliver |
| Events screen and mute buttons | 29 Oct | Mute a chatty app at the source from COSMOS (Viewer › Mission › Events: Mute SCH slot chatter, Silence app, …) or a Yamcs stack (9-evs-mute); the Events dock under every viewer page and Mission › Event catalog |
| Notebooks | 29 Oct | JupyterLab with the read-only draco package over QuestDB, the Yamcs archive, Parquet and the raw record. Tile Notebooks (Python) (/lab/) or Viewer › Tools › Notebooks (Python) |
| Operator notes | Oct | docs/operator-notes: short written procedures beside the decks |
| Tutorials and Training | 3 Nov | Seven hands-on lessons (tile Tutorials, /tutorials/) and five step-by-step walkthroughs by role (tile Training: step by step, /training/); both also under Viewer › Mission |
DRACO7RT ground changes · 11 / 18
Verification
A pass needs positive evidence the path executed: a counter that moved, a packet timestamp, an event line. The absence of an error is not a pass.
DRACO7RT ground changes · 12 / 18 · run/bootstrap-draco.sh, run/yamcs/selfcheck.py, tools/ground/
Unchanged
DRACO7RT ground changes · 13 / 18
Gaps
DRACO7RT ground changes · 14 / 18 · claude-notes/SECURITY.md has the scored view
Timeline
| Date | Change |
|---|---|
| 2026-07-22 | Baseline: QEMU vehicle, cFS, COSMOS 7.2.1 with the base plugin |
| 2026-08-21 | Mission plugin (ACS, NAV, IMU, GPS42, IMU42, FOGI): composite pages, mission test |
| 2026-09-30 | Front door: landing page, control service, viewer, decks site, Grafana walls |
| 2026-10-20 | Microsoft Entra ID sign-in; retention and the daily cleanup timer; host-reboot recovery |
| 2026-10-22 | Downlink tee; Yamcs live with the generated database; PlanDev public; command audit (28 fixes, base plugin 1.0.8) |
| 2026-10-23 | Yamcs commanding and events; PlanDev mission model and plan-to-flight loop; Open MCT; Yamcs retention |
| 2026-10-25 to 27 | Yamcs displays, operator stacks and script mission test; CFDP; Table Workbench; COSMOS tools without a second login; sign-in record |
| 2026-10-28 | Clean start rule: saved data cleared on every stack start (55 GB freed) |
| 2026-10-29 | Events dock, catalog, mute buttons on both stations; notebooks; raw recorder; Parquet export; these two decks |
| 2026-11-03 | After this deck: training walkthroughs and tutorials (tiles and viewer pages), mission test recorded from both stations, Yamcs display renderer file ungated so displays render |
| 2026-11-10 | COSMOS behind the gate; password sign-in on the front door (throttled); Sessions sign-out; notebook token read-only; sim.efsi.com redirects; CSRF guard; cfdpUp kept on clear; mission plugin 1.2.4 |
DRACO7RT ground changes · 15 / 18 · git log (10 Nov: live, not yet committed)
Where
| Change | Repository path | Live |
|---|---|---|
| COSMOS plugins | cosmos/openc3-cosmos-draco, cosmos/openc3-fogi-open-source | Viewer › Tools › Admin, Plugins tab |
| Front door, viewer, control service | web/site, web/viewer, web/control | https://draco.efsi.com/ (viewer: tile Mission Control, /viewer/) |
| nginx vhosts (reference copies) | run/nginx-draco.efsi.com.conf, run/nginx-plan.draco.efsi.com.conf | /etc/nginx/sites-enabled |
| Tee, compose, bootstrap, clean start, cleanup | run/downlink-tee, run/compose.yml, run/bootstrap-draco.sh, run/clear-data.sh, run/disk-cleanup.sh | docker, systemd timers; front door › Demo control › HEALTH › Verify, Clear saved data |
| Yamcs | run/yamcs (README, etc, ext, mdb, displays, operator) | https://draco.efsi.com/yamcs/ (Open Yamcs: the draco Home page); Viewer › Yamcs |
| PlanDev, Open MCT, Grafana | run/plandev, tools/plandev, run/openmct, run/grafana | plan.draco.efsi.com (Open Plan), /openmct/, /grafana/ (tile Grafana Wall) |
| Generators and drift checks | tools/ground (cosmos2xtce, cosmos2opi, evscat), tools/tables, tools/sc | --check in --verify |
| Notebooks and archive | run/jupyter, tools/archive; data in /home/efsi/draco-archive | https://draco.efsi.com/lab/ (tile Notebooks (Python)) |
| Table Workbench | web/tables, web/control/tables_api.py, tools/tables, tools/sc | /tables/ (tile Table Workbench) |
| Tutorials and Training (3 Nov) | web/tutorials, web/training, tools/tutorials | /tutorials/, /training/ (tiles) |
| Decks | powerpoint/decks (decks.json) | /slides/ (public), tile Presentations |
| Plan and record | claude-notes/GROUND-PLAN.md, CMD-AUDIT-2026-10-22.md, SECURITY.md, claude-notes.md | the engineering record |
DRACO7RT ground changes · 16 / 18
Lessons
The 28 command fixes came from reading the flight binary’s debug information, after months of definitions that looked right. Sizes include tail padding; apps that check length reject silently or with one event.
The Yamcs database, the Yamcs displays, the event catalog, the table catalog and the RTS tables are all generated from one source with a drift check. Hand copies would already have diverged.
Every store that was added got its retention the same day. The one that did not (COSMOS, delivered) filled 51 GB before anyone looked.
Two Java classes through a public API and a pinned commit are the whole of the product-side footprint. Upgrades stay possible, and the diff against the delivery is the change record itself.
DRACO7RT ground changes · 17 / 18
Rules
DRACO7RT ground changes · 18 / 18