How hyp-ed/hyped-2027 works
HYPED combines STM32 pod control and sensing with a base-station telemetry system for monitoring, visualisation, logging, and operator commands. The principal workflow runs from pod measurements over CAN and MQTT into telemetry ingestion and storage, then to live or historical views; control commands travel back through the server to the pod. The map preserves the documented control, localisation, and fault capabilities. Some pod and telemetry subsystem connections are based on README descriptions and the file tree, not sampled implementation source.
Main entry points: boards Navigation and telemetry board · can.rs CAN and MQTT tasks · MqttIngestion.service.ts MQTT ingestion · App.tsx Telemetry operations UI
Components 25
Pod firmware
- Navigation and telemetry board
boards/stm32f767zi/src/bin/boards - Levitation boards
boards/stm32l432kc/src/bin/levitation.rs - Sensor acquisition tasks
boards/stm32f767zi/src/tasks/sensors.rs - Motor control tasks
boards/stm32f767zi/src/tasks/motor_control.rs - CAN and MQTT tasks
boards/stm32f767zi/src/tasks/can.rs
Shared Rust libraries
- Message and event model
lib/communications/src/lib.rs - Sensor drivers
lib/sensors/src/lib.rs - Localisation
lib/localisation/src/lib.rs - Control algorithms
lib/control/src/lib.rs - Pod state machine
lib/state_machine/src/lib.rs
Telemetry server
- Telemetry server
telemetry/packages/server/src/app.module.ts - MQTT ingestion
telemetry/packages/server/src/modules/mqtt/ingestion/MqttIngestion.service.ts - Measurement service
telemetry/packages/server/src/modules/telemetry/Measurement.service.ts - State service
telemetry/packages/server/src/modules/state/State.service.ts - Public data API
telemetry/packages/server/src/modules/public-data/PublicData.controller.ts - Historical telemetry API
telemetry/packages/server/src/modules/openmct/data/historical/HistoricalTelemetryData.service.ts - Pod controls API
telemetry/packages/server/src/modules/controls/PodControls.controller.ts - Fault monitoring
telemetry/packages/server/src/modules/openmct/faults/Fault.service.ts - Remote and live logs
telemetry/packages/server/src/modules/remote-logs/RemoteLogs.service.ts
Telemetry interfaces
- Telemetry operations UI
telemetry/packages/ui/app/App.tsx - OpenMCT dashboards
telemetry/packages/ui/openmct/main.ts - Public pod dashboard
telemetry/packages/public-app/app/page.tsx
External systems
- MQTT broker
- InfluxDB
Other components
- Operator
Connections 28
- Operator → Telemetry operations UI: uses controls
- Operator → OpenMCT dashboards: views telemetry
- Operator → Public pod dashboard: views status
- Sensor acquisition tasks → Sensor drivers: reads sensors
- Navigation and telemetry board → Sensor acquisition tasks: runs tasks
- Navigation and telemetry board → Motor control tasks: runs tasks
- Navigation and telemetry board → CAN and MQTT tasks: runs tasks
- CAN and MQTT tasks → Message and event model: encodes messages
- Levitation boards → CAN and MQTT tasks: communicates CAN
- Navigation and telemetry board → Levitation boards: communicates CAN
- Motor control tasks → Control algorithms: uses control
- Navigation and telemetry board → Localisation: uses localisation
- Navigation and telemetry board → Pod state machine: uses state machine
- CAN and MQTT tasks → MQTT broker: relays MQTT
- MQTT broker → MQTT ingestion: delivers messages
- MQTT ingestion → Measurement service: adds readings
- MQTT ingestion → State service: adds state
- Measurement service → InfluxDB: stores readings
- State service → InfluxDB: stores state
- Public data API → Historical telemetry API: requests readings
- Historical telemetry API → InfluxDB: queries history
- Telemetry operations UI → Pod controls API: sends commands
- Pod controls API → MQTT broker: publishes commands
- MQTT broker → CAN and MQTT tasks: delivers commands
- OpenMCT dashboards → Telemetry server: requests telemetry
- Public pod dashboard → Public data API: requests pod data
- OpenMCT dashboards → Fault monitoring: uses fault data
- Telemetry operations UI → Remote and live logs: submits logs