This autopilot is not recommended because some versions of the board are not compatible with the official ArduPilot software despite multiple efforts to work with the manufacturer to make them compatible. The manufacturer is also apparently not abiding by the GPLv3 license which requires releasing the modified source code to its customers. “V1.0” and “V1.2” probably work, “V1.0 II” and “V1.1” definitely do not work.
The RadioLink CrossFlight is not supported by ArduPilot. As far as the ArduPilot Development Team is aware, RadioLink are in violation of ArduPilot’s GPLv3 license in that they refuse to release the source code for their modifications to ArduPilot. The Development Team recommend you do not purchase this product, and instead select from one of our many other supported boards.
This hardware comes preflashed with a RadioLink-branded version of ArduCopter and an ArduPilot-compatible bootloader. To use non-branded ChibiOS-based ArduPilot firmware versions, download the required vehicle firmware .apj file from https://firmware.ardupilot.org/ and flash your board using MissionPlanner’s “custom firmware” option.
In case a bootloader re-installation is required, you can boot your board to DFU-mode using the following solder-points:
Then follow the instructions on how to load firmware onto ChibiOS boards.
The flightcontroller’s plastic case shows the telemetry ports’ numbers reversed compared to the board’s PCB imprints and the
firmware’s SERIALn assignments, this requires additional attention!
MiniPix voltage and current sensing pins use Pixhawk standard ( BATT_VOLT_PIN = 2, BATT_CURR_PIN = 3).
The additional ADC pin can be used for either RSSI or analog airspeed. Set required option to PIN = 11.