The following pages are intended to be printed as a Quick Reference Card (QRC) for operators when time or field conditions limit access to the full manual. The QRC is designed to print two pages per sheet, front and back, forming a single foldable card that can be laminated and carried into the field. Print in landscape orientation with 1-inch margins to maximize readability.

Note

Field Reference Card — abbreviated procedures for trained operators. For full procedures, refer to the Horizon End-User Manual, Ch. 5 (Normal) and Ch. 6 (Abnormal & Emergency). Print front/back, laminate, and carry in the field.

Connection Reference

Item	Value
GCS UDP — Remote IP	127.0.0.1
GCS UDP — Remote port	14550
Aircraft UDP Port (Add New Aircraft)	14550 (auto-increments per aircraft)
Flight controller baud (SERIAL1)	57600

Mode A — BLOS-Only Startup

Use when connecting to an aircraft already airborne or preparing for launch, with no LOS from the GCS. Prerequisite: Aircraft unit configured, powered, and transmitting over BLOS.

1. Ensure the GCS computer has internet.
2. Confirm Beam is running (tray: Server running), then Open Horizon Manager.
3. Open Fleet View → Add Aircraft.
4. Set Device, Name, UDP Port (14550) → Add Aircraft.
5. In the GCS application, add a UDP connection: 127.0.0.1 : 14550.
6. Wait for the card to turn Active and POS/telemetry to update before issuing commands.

Command delivery: watch the card’s Flight Log — entries advance Pending → Sending → Delivered. Use Clear Queue to cancel pending commands.

Mode B — LOS + BLOS Startup

1. Power on the aircraft and flight controller, then the Aircraft Hardware Unit.
2. Confirm the Aircraft unit STATUS LED is solid green.
3. Connect the GCS unit via USB-C and power it from the AC wall adapter (USB-C does not power it).
4. Confirm the LINK LED on both units is fast-blinking green (LOS closed).
5. Confirm Beam running → Open Horizon Manager.
6. In Preferences, confirm 127.0.0.1 : 14550 and Connected GCS; Status: Connected.
7. Fleet View → Add Aircraft (Device, Name, UDP Port 14550).
8. In the GCS application, add a UDP connection 127.0.0.1 : 14550; confirm live telemetry.

BLOS fallback: if no LOS MAVLink packet arrives for >3 s, Beam routes supported commands/telemetry over BLOS automatically, and reverts when LOS returns.

Pre-Flight BLOS Ground Test

1. Establish a full LOS + BLOS connection.
2. Upload a mission plan via LOS and read it back.
3. Move outside with a clear view of the sky.
4. Confirm the aircraft appears/updates on the Beam web map (somewear.app → Map).
5. Disconnect USB-C, wait ≥3 s (triggers BLOS fallback); push a modified plan; watch the Flight Log reach Delivered.
6. Reconnect USB-C; read the plan back and confirm.

System Shutdown

1. Land and disarm the aircraft.
2. In the GCS application, disconnect from the aircraft.
3. Beam tray → Stop Server.
4. Power off the GCS Hardware Unit.
5. Power off the aircraft and Aircraft Hardware Unit.
6. Disconnect all cables and store equipment per Handling, Storage, and Transport.

Note

Field Reference Card — abnormal & emergency procedures. For full procedures, refer to the Horizon End-User Manual, Ch. 6.

LED Quick Reference

LED Behavior	STATUS LED	LINK LED
🔴 Blinking Red	Bootloader mode (abnormal during op)	LOS Link Lost
🟢 Solid Green	Power good (normal)	—
🟢 Blinking Green	—	LOS Link Closed
🟡 Flashing Amber	Firmware update in progress - do not unplug	—

Horizon UI Displays “Missing API Key”

1. Verify the GCS computer has internet; if it was offline, restart the Beam server after reconnecting.
2. Open Diagnostics → Config.
3. Confirm an api-key is present; add/enter it if missing.

LOS Link Cannot Be Established

1. Confirm both units share matching Radio Settings ranges and the radio is enabled (Connected Device).
2. Confirm both units have a unique Name (no name → no LOS encryption keys → link will not close).
3. Confirm the LINK LED on both units is fast-blinking green.
4. Verify flight controller serial config (Flight Controller Configuration) and power.
5. Confirm the GCS UDP connection is 127.0.0.1 : 14550. No COM-port selection is required.

No Telemetry Over BLOS

1. Verify the SAT antenna is connected to the Aircraft unit’s SAT port.
2. Ensure a clear, unobstructed view of the sky.
3. Confirm the satellite data plan is active.
4. Verify flight controller config (Flight Controller Configuration) and power.
5. If on the Beam web map but not in the GCS app: confirm the correct aircraft in Fleet View; verify GCS internet.

BLOS Commands Not Clearing the Flight Log

1. If telemetry is also missing, troubleshoot No Telemetry Over BLOS first.
2. If telemetry is present but tasks are not clearing, select Clear Queue on the card and re-issue.

GCS Hardware Unit Not Detected

1. Reseat the USB-C cable at both ends; confirm it is data-capable; try another cable.
2. Confirm the unit is powered (USB-C does not power it — use the AC wall adapter).
3. Confirm STATUS LED solid green.
4. Check Device Manager and install any required USB serial drivers.

Beam or Horizon UI In-App Update Fails

1. Uninstall Beam (Control Panel → Programs → Uninstall Somewear Local).
2. Download the latest client: https://somewear.app/app/settings/downloads
3. Reinstall cleanly and confirm Beam starts.

Total Loss of Link — GCS Crew Actions

1. Verify GCS Hardware Unit power and USB-C connection.
2. Verify GCS internet.
3. Reposition GCS antennas to restore LOS.
4. If equipped with RTL failsafe, allow it to execute.
5. If BLOS was recently active, allow several minutes for satellite re-connection before issuing commands.

Horizon UI or Beam Crash During Mission

1. Relaunch: Beam tray → confirm Server running → Open Horizon Manager.
2. Confirm the aircraft returns to Active; re-add the UDP connection (127.0.0.1 : 14550).
3. BLOS routing is unavailable while the server is down — rely on the aircraft failsafe (RTL) until restored.

Critical Limits & Cautions

• Power: VSUPP 6–13 V DC recommended; absolute max 16 V. USB-C cannot power the Hardware Unit — supply via VSUPP/GND on the I/O connector, or use the AC wall adapter at the GCS.
• Environment: Ambient operating −20 to 85 °C. Max altitude 4,500 m geometric. Not IP-rated — protect from precipitation and immersion.
• LOS frequency separation: The two programmed LOS channels must differ by ≥ 2 MHz. Closer spacing degrades performance.
• BLOS antenna: Requires unobstructed view of the sky. Real-time radio control is not available over BLOS.
• Device naming: Both Hardware Units must be assigned a unique name, or LOS encryption keys are not set and the link will not form.