Skip to main content

ANT61 Beacon integration

Command and receive telemetry over the ANT61 Beacon API instead of a UDP ground station.

How it works​

AutoSat reaches your satellites through Beacon's API instead of a ground-station pass. Enabling the integration runs an always-on Beacon ground station for this workspace, so there are no pass windows to wait for.

Install the Beacon subsystem on a satellite and set the Beacon ID that ANT61 assigns it. Commands sent through the Beacon ground station are delivered over the API, and telemetry returns the same way into the console — just like a normal pass.

Setup​

  1. Enable the integration in the workspace's integration settings. This creates a Beacon ground station for the workspace — it's always connected, with no passes.
  2. Set the workspace API token. Tokens are generated in ANT61 Beacon, one per workspace, and stored write-only — the token is never shown again after saving.
  3. Install Beacon on each satellite and give it the Beacon ID (uid) that ANT61 assigned. One install per satellite.

Telemetry​

Beacon telemetry arrives as subsystem-scoped fields under the beacon. namespace, including location (beacon.location.latitude, beacon.location.longitude, beacon.location.altitude), signal quality, battery state (beacon.battery.remaining, beacon.battery.charging), raw IMU and orientation readings, and the reported firmware version. Link latency is mapped to the shared satellite-level autosat.link.ping_ms field.