One shared mission state
The repository uses shared contracts and relay state to coordinate interfaces. This gives the headset, hub and wrist a common basis for route and alert information.
02 / NASA Space Apps / Human-centred systems
Team Beacon
Connecting terrain, mission state and astronaut interfaces in a collaborative Mars navigation and safety demonstrator.
01 / CONTEXT
Team Beacon was developed for the NASA Space Apps Martian Map challenge. It connects terrain-aware route planning, a base-station interface and astronaut-facing displays. The public repository contains implementation code across these areas; this is a student demonstrator, not an operational astronaut safety system.
An astronaut interface needs to make terrain, route and communications information understandable without separating it from mission context. Beacon explores how a shared state can connect the base station, a wearable interface and an immersive view of the surroundings.
02 / CONTRIBUTION
03 / THE SYSTEM
Team Rust engine · terrain and route exports
Node relay · WebSocket interfaces
Hub · wrist · headset / native Quest · cuff
Simplified view of the repository’s local demo architecture. The broader Earth Mission Control concept is not represented as a deployed remote service.
04 / IMPLEMENTATION
The repository contains a browser headset application and a native Unity/OpenXR Quest project. Documentation describes a mission HUD, emergency shelter requests and AR/VR modes.
A Node relay broadcasts mission state to connected interfaces. The team’s Rust engine computes terrain skyline and derived exposure, sunlight and line-of-sight layers. ESP32 cuff firmware is also present.
Vital-sign and oxygen monitoring, voice interactions, broader environmental risk assessment and a distinct Earth Mission Control service remain concepts unless specific implementation and validation evidence is added.
05 / ENGINEERING REASONING
The repository uses shared contracts and relay state to coordinate interfaces. This gives the headset, hub and wrist a common basis for route and alert information.
Repository notes distinguish terrain scenery, route data and synthetic rehearsal fixtures. That boundary matters: an immersive scene alone does not validate a route or its risk model.
Desktop rehearsal can exercise UI state and synchronization. Headset comfort, tracking, controller input and physical presentation require separate hardware checks.
Connecting several interfaces introduces synchronization, stale-data and coordinate-frame problems. The repository documents these concerns and distinguishes simulation checks from actual headset behaviour; detailed personal reflections can be added with supporting examples.
06 / EVIDENCE
What is known, what remains to be demonstrated.
07 / WORK IN PROGRESS
Implementation code and demo documentation are available publicly. Hardware verification is version-specific, and some demo configurations use synthetic mission data. The wider mission-support vision remains broader than the demonstrated implementation.
08 / PROJECT NOTEBOOK
Space for the actual engineering: diagrams, hardware and evidence. Unfilled slots are labelled explicitly.
Approved capture from the actual Quest app to be added.
Actual hub screenshot and data provenance to be added.
Team-approved cuff or integration photograph to be added.