Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.altnautica.com/llms.txt

Use this file to discover all available pages before exploring further.

Hardware Tab in Mission Control

The Hardware tab is a top-level tab in ADOS Mission Control. It gives you a browser control surface for the connected Ground Agent: status, network, physical UI, controllers, peripherals, distributed receive, and mesh.
Mission Control Hardware tab showing ground station overview with link health and connected clients

Where to find it

The Hardware tab sits in the top navigation bar of Mission Control, after Command and before Plan. It appears when Mission Control is connected to an Agent running in the ground-station profile.

Current sub-views

Overview

The landing page for the Hardware tab. It shows:
  • Ground station profile, board, uptime, and paired-drone state
  • Link health, including RSSI, bitrate, channel, and FEC counters when available
  • Uplink summary and current role
  • Pairing action for the drone link
  • PIC widget showing who currently has pilot-in-command authority

Network

Full network configuration:
  • WiFi AP enable, SSID, passphrase, and band settings
  • WiFi client scan, join, and leave
  • Ethernet status and configuration
  • Cellular modem status and APN settings
  • Uplink priority order
  • Share-uplink toggle for local clients

Physical UI

OLED and device UI settings:
  • OLED brightness
  • Auto-dim behavior
  • Screen timing and screen settings where supported
  • Factory reset with typed confirmation
Button remapping and screen reorder controls are present as configuration surfaces, but remain limited until the matching Agent endpoints are fully supported.

Controllers

Gamepad and pilot-control management:
  • Connected gamepad list
  • Primary gamepad selection
  • PIC claim, release, confirm, and heartbeat state
  • Bluetooth scan, pair, and forget actions where available

Peripherals

Connected accessory management:
  • Enumerated USB, Bluetooth, and Agent-discovered devices
  • Per-device health and status
  • Device configuration and supported action buttons

Distributed RX

Shown on mesh-capable nodes. The page is role-aware:
  • Direct: shows that distributed receive is off and offers role change.
  • Relay: shows receiver reachability, relay status, and fragment forwarding stats.
  • Receiver: shows paired relays, pending join requests, pairing-window state, revoke actions, and combined-stream stats.
This page polls the role and distributed-receive endpoints while visible. It can change role, open and close the receiver pairing window, approve pending relays, and revoke relays.

Mesh

Shown on mesh-capable nodes. The page shows:
  • Mesh health, mesh id, peer count, partition indicator, and selected gateway
  • Neighbor table with link quality and last-seen age
  • Gateway table with advertised gateways and pin action
  • Mesh event toasts for partitions, gateway failover, receiver unreachable, relay revoked, and relay disconnected
  • Disabled log-aggregation action until the Agent log bundle endpoint ships
The page polls mesh health, neighbors, routes, and gateways while visible. Live mesh deltas arrive through the mesh WebSocket stream.

Planned sub-views

Two sub-views are planned but are not separate pages in the current Mission Control route tree:
Sub-viewPlanned coverage
RadioChannel, bitrate, FEC, diversity, and recording controls
Storage and LogsSD usage, recording downloads, log bundles, and cleanup policy
Today, drone pairing and link health live in Overview, while mesh log aggregation is shown as a disabled action in Mesh.

Data flow

The Hardware tab communicates with the Ground Agent through:
ChannelPath
REST APIhttp://<ground-node>:8080/api/v1/ground-station/*
Uplink eventsws://<ground-node>:8080/api/v1/ground-station/ws/uplink
Mesh eventsws://<ground-node>:8080/api/v1/ground-station/ws/mesh
PIC eventsws://<ground-node>:8080/api/v1/ground-station/pic/events
For ground stations on the local network, the browser connects directly over WiFi AP, USB tether, or Ethernet. Hosted Mission Control cannot open local http:// or ws:// endpoints from an HTTPS page, so local Ground Agent control should use a local Mission Control build or the Ground Agent-hosted build.

State behavior

  • Overview status polls at a short cadence while the page is visible.
  • Distributed RX polls every few seconds while visible.
  • Mesh polls every few seconds while visible.
  • Polling pauses when the browser tab is hidden.
  • Last-known state is retained when a node goes offline, then refreshed when it reconnects.

Using Hardware tab offline

The Hardware tab works offline as long as your browser can reach the Ground Agent over the local network. Cloud features are additive. Local video, telemetry, role management, and network setup do not require internet.

What is next