Skip to content
inksong edited this page Nov 9, 2026 · 2 revisions

Safety

ANet Relay flies real aircraft.

  • Fly only inside a netted area with a padded floor, with propeller guards fitted.
  • Keep an operator at the Relay window. Possession, Stop (Esc) and Stop all (Ctrl+. / ⌘.) override every agent and program at any time.
  • Verify stick directions with the propellers removed before the first flight of each aircraft.
  • Preflight blocks arming until link, battery, prearm checks and GCS input parameters are in order; arming a real aircraft needs the confirm word ARM.
  • In STABILIZE there is no altitude or position hold: an aircraft without a controller keeps its last throttle until the autopilot's failsafe acts. Prefer altitude hold.
  • Releasing possession stops stick input. On PX4 Relay stops sending manual control instead of sending zero throttle.
  • Onboard programs on a real aircraft need Allow programs on this aircraft (confirm word PROGRAM), and a program's fire output is ignored there. An emergency stop ends a dogfight's control of that aircraft for good.
  • The API listens on the loopback interface only. The LAN arena socket carries no control: nothing received from the network reaches sticks, arming, claims, parameters, skills or plans.
  • Hardware in the loop (PX4 only) needs the propellers removed, the confirm word HITL, a disarmed aircraft and the operator's possession. Relay backs up every parameter first, changes only SYS_HITL and SYS_AUTOSTART, and restores and verifies them afterwards, also on the next connection if Relay quit during a session. Copilot asks for every HITL start and stop, even with Allow all on.
  • Hazardous device-level operations (motor tests, calibration, flight termination, reboot) need a confirm word and have hard limits.

Clone this wiki locally