All projects

02 / NASA Space Apps / Human-centred systems

A clearer picture of Mars.

Team Beacon

Prototype & integration

Connecting terrain, mission state and astronaut interfaces in a collaborative Mars navigation and safety demonstrator.

A little closer
to Mars.
Mars mission / Concept illustration · illustrative, not project hardware
MY ROLE

Headset & Quest applications · repository attribution: CJ

TOOLS & TECHNOLOGIES
Quest 3Unity / OpenXRWebXRShared telemetry
EVIDENCE STATUS

Public repository reviewed

01 / CONTEXT

Overview

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.

The engineering problem

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

My role & responsibilities

  • The repository ownership table assigns apps/headset and apps/quest to CJ.
  • This case study focuses my contribution on the astronaut-facing headset and Quest applications.
  • The Rust engine, relay/integration, hub and firmware are team components, not presented as my individual work.
  • A more detailed account of my authored changes and design decisions can be added alongside selected commits.

Requirements & constraints

  • Distinguish real terrain data from synthetic route or mission fixtures used in particular demo configurations.
  • Keep shared state, units and connection status consistent across interfaces.
  • Separate desktop simulation from passthrough, tracking, readability and hardware validation.
  • Treat the Earth Mission Control concept separately from the implemented laptop-hosted demonstration.

03 / THE SYSTEM

Architecture

01

Terrain & planning

Team Rust engine · terrain and route exports

02

Shared mission state

Node relay · WebSocket interfaces

03

Astronaut & base views

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

Hardware, software & interfaces

Headset interfaces

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.

Team integration

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.

Ideas beyond the demo

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

Decisions & trade-offs

01

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

Separate visual context from navigation evidence

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.

03

A staged validation approach

Desktop rehearsal can exercise UI state and synchronization. Headset comfort, tracking, controller input and physical presentation require separate hardware checks.

Challenges & lessons

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

Testing & verification

What is known, what remains to be demonstrated.

  • The repository includes model, pathfinding, terrain and relay test files.
  • The Quest acceptance document records version-specific software and hardware checks, along with remaining limitations.
  • I have inspected the public source and documentation for this portfolio; the project’s full test suite has not been independently rerun here.
  • No competition result, mission readiness or independently verified performance figure is claimed.

07 / WORK IN PROGRESS

Current status & next steps

Prototype & integration

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.

  1. Add approved screenshots from the actual hub and headset.
  2. Link selected authored commits and explain personal design iterations.
  3. Publish a concise validation summary tied to a specific revision.
  4. Keep planned sensing and voice features separate from the implemented demo.

KEEP EXPLORING

REXUS / MEDLDiscuss my work