— Compatibility
Fly what you already own.
TacLink C2 is hardware-agnostic by design. ArduPilot and PX4 native, MAVLink 2.0 throughout, open adapter architecture for everything else. The matrix below tracks tested hardware as it comes online during the closed alpha.
— Autopilots
Autopilot stacks.
Active testing list is being published as boards come up on the bench. ArduPilot 4.5+ and PX4 1.14+ on Pixhawk-class hardware are the canonical targets and the first stacks on the bench.
— Boards
Flight controller hardware.
Active testing list is being published as boards come up on the bench. Pixhawk 6X, Cube Orange, Cube Orange+, Holybro Durandal, and matek H743-class boards are the initial bring-up targets.
— Telemetry
Radio links.
Active testing list is being published as boards come up on the bench. SiK-firmware 915 MHz radios, RFD900-family long-range modules, and Herelink integrated links are the first telemetry targets, with MAVLink 2.0 message signing where the hardware permits.
— Airframes
Tested airframes.
Because TacLink C2 talks to the autopilot, not the airframe, any aircraft running a supported autopilot on supported boards inherits the same compatibility. Specific airframe call-outs (commercial platforms, Blue UAS-listed builds, custom domestic builds) will be published as the bring-up program covers them.
— Adapter
Do not see your hardware?
The architecture is built around an open adapter layer. Adding a new autopilot or transport is the path we want, not an exception. If you run hardware that is not on the matrix yet, tell us about it.