Ground stations
COSMOS is the primary station. Yamcs is a second station on the same downlink. PlanDev plans; it does not command.Downlink tee
10.5.5.201—
Copies the vehicle's one telemetry stream to both stations.Mission Control
COSMOS Telemetry Viewer, FOGI HOME screen: mode, fuel, deployments, limits and the launch button.
/viewer/ · frameless COSMOS with page buttons 02Telemetry Wall
Saved multi-screen layout: ACS, NAV, IMU, LC and SC side by side for a big display.
/viewer/#wall · also GNC, Mission, cFS, Tools 03Grafana Wall
Time-series mission wall in kiosk mode: rates, fuel, gate counters and event markers.
/grafana/d/draco-wall 04Table Workbench
Build a stored command sequence (RTS) from the COSMOS dictionary or edit an app table field by field, run the structural checks, deliver it to the vehicle by CFDP + Table Services and dump it back to prove it.
/tables/ · Sequences, App tables, Check, Deliver 05Notebooks (Python)
JupyterLab over both archives, read only: find an event, go back two minutes, show the data. Shared notebooks, the draco package preinstalled, nothing can command the vehicle.
Tutorials
Seven hands-on lessons, each a different way to learn: a guided first flight, a scavenger hunt, predict-observe-explain, a fault to diagnose, sequencing puzzles, a recall quiz and a Python notebook. Live checks read the telemetry to tell you it worked.
/tutorials/ · start with 1 First flight 07Training: step by step
What each role is trying to get done and exactly how: run the mission test (everyone), change and debug flight code in VS Code, add a value to a ground page, fly by hand from COSMOS and Yamcs, check the evidence. Printable, with a box to tick per step.
/training/ · start with G, then your role 08Live 3D view
NASA 42 truth dynamics streamed from the virtual display (noVNC). No password prompt: it uses your sign-in.
/42/Presentations
- DRACO7RT Tutorial: How to Use It, by Role · PDF
- DRACO7RT Training: Step by Step · PDF · pages
- Latest for SMA · PDF
- DRACO7RT Full Mission Test · PDF
- DRACO7RT COSMOS Operator Guide · PDF
- DRACO7RT Ground System · PDF
- DRACO7RT Yamcs Operator Guide · PDF
- DRACO7RT CFDP File Transfer · PDF
- DRACO7RT Tables and Stored Commanding · PDF
- DRACO7RT Flight Software: Writing and Debugging Code · PDF
- DRACO7RT Flight Software Security · PDF
- DRACO7RT Ground System Security and Zero Trust · PDF
- DRACO7RT Archive, Events and Notebooks · PDF
- DRACO7RT Ground Systems: Changes to the Baseline Delivery · PDF
Evidence
Operator guide
- COSMOS Operator Guide (deck) · Ground System (deck)
- Guide as PDF · Ground System PDF
- Yamcs Operator Guide (deck) · PDF
- CFDP File Transfer (deck) · PDF
- Ground System Security and Zero Trust (deck) · PDF
- Archive, Events and Notebooks (deck) · PDF · Ground changes (deck)
Sequence for a demo: Start → Fresh vehicle → Launch (or Mission test). Downlink re-enable after any reboot.
Demo control
Actions run on the server one at a time; every request is audited. Only the actions that make sense in the current state are active; hover a button for what it does, or why it is greyed.One commanding station at a time. COSMOS is the primary station and commands by default. Switch to Yamcs only while you command from Yamcs (COSMOS users hold their commands), and switch back when done: both stations reach the same vehicle and share its command counters.
Select an action above. Output appears here live.
Connecting to the console…
The console is the flight computer's UART0 as QEMU logs it: U-Boot, RTEMS and cFS event output. It is read-only; the interactive RTEMS shell on UART1 is disabled on this vehicle by design (root/no_serial_shell). A Fresh vehicle starts a new log.