We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
docs: MAVLink serial autodetection with the pinning variables Configuration and Build describe the blank-path serial scan that locks onto MAVLink traffic and the MAVLINK_SERIAL_PATH pin for the TELEM2 UART.
docs: MAVLink serial variables and the TELEM2 UART hookup Configuration lists MAVLINK_SERIAL_PATH and MAVLINK_BAUD, and Build describes the three-wire TELEM2 hookup with the FC parameters for ArduPilot and PX4.
docs(build): alternative modems, SIM and eSIM options, tested-config note The Build page covers cellular HATs like Waveshare on a Pi or a Compute Module 4 or 5 carrier, public-IP and eSIM data plans, XBStation as a closed alternative that runs its own firmware, and a note that testing covers SITL and the reference PX4 and ArduCopter build.
Deployment: production pulls the published image
Build: describe the Betaflight rig and its companion computer
Deployment: production pulls the published multi-arch image; up with build flag builds from source
Build: the Betaflight stack is its own aircraft, and the reference Pixhawk flies on both PX4 and ArduPilot
Document the NOTAM notices feature and its /api/notams endpoint
Architecture: link-up message intervals, GCS heartbeat, and the vehicle snapshot. Home: lost-operator failsafe capability
Configuration: lost-operator failsafe section
Configuration: full variable table plus MSP link, camera source, and email sections. Firmware: board identity in detect and catalog target autodetect
Remove the leading page-name heading that GitHub already renders as the page title
Deployment: nginx serves the app on port 80, persistent database volume
Configuration: app config passed via compose environment with defaults
Configuration: single root .env.example for compose and the app
Correct wiki drift: per-stack go-to and speed, real page list, SSE telemetry, profile count, MSP stacks
Detached compose bring-up commands
Development: full SITL vehicles table with per-variation run commands Lists the copter, rover, boat, plane, and sub commands on the development profile (via SITL_VEHICLE and SITL_MODEL) plus the PX4, Betaflight, and INAV profiles, with the MAVLink 5760 / MSP 5761 ports and the one-app-at-a-time note.
Document set_depth endpoint and vehicle-class dashboard controls HTTP-API lists the reconnect, manual_control, set_origin, and set_depth MAVLink routes. Autopilot-Support describes how the go-to control adapts per vehicle class: altitude for air, depth for submarines (ALT_HOLD depth hold via SET_POSITION_TARGET_GLOBAL_INT), and none for rovers and boats.
Firmware: station arms an MSP craft over its own receiver
Firmware: INAV flies its own onboard mission over MSP INAV runs a waypoint mission the same as a MAVLink autopilot. The station uploads the mission, arms, and engages NAV WP by reading the mode ranges and holding the arm and NAV WP aux channels active with MSP RC override while INAV navigates onboard. Companion guidance covers Betaflight, which has no waypoint engine. Documents the mode-range engage, the MSP v2 box-table read, and the MSP-RC-override prerequisite.
docs: per-autopilot capability matrix and MSP calibration, gamepad, crash alerts
docs: MSP mission upload, Betaflight companion guidance, mission bracketing Firmware covers the INAV waypoint upload and the companion guidance loop that flies a Betaflight craft over RC override. Mission planning notes the auto return-to-launch that closes a plan and the grouped airspace warnings. Autopilot support lists the position-control intent mode.
Add the drone build photo for the build guide
Document the HGLRC XJB Betaflight stack in the build guide The station connects to an HGLRC XJB Betaflight flight-controller stack over MSP alongside the Pixhawk over MAVLink, so the build guide records it and points to the firmware and configuration pages for the MSP link.
Document new patterns, import formats, AI tuning, and MAVLink signing Mission-Planning covers the corridor, search, and structure-scan generators and the KML, KMZ, and CSV import readers. Configuration adds the MAVLink signing and AI assistant settings with their env fallbacks. HTTP-API documents the pid-tune endpoint.
Add the hardware Build guide Documents the reference build: a Raspberry Pi 4B companion, a Holybro quadcopter airframe with a Pixhawk 6C, an Arducam day/night camera, and a 4G modem on a public-IP SIM, with the USB link to the flight controller and the CG-NAT reachability rationale. Carries a drone-photo placeholder and a sidebar entry.
Document ArduPilot/PX4 serial-bootloader flashing and Betaflight cloud build
Document mission patterns, gamepad flight sessions, and plan-header grouping
Document mission editing from every interactive map window