Test Flights

This page may be out of date

The latest version can be found here.

Test flights are important for quality assurance. The Dronecode test team can help review (test flight) your pull requests and provide feedback and logs.

How to Request Test Flights

  • Add a complete and thorough description of your changes in the pull request

  • Tag the test team in a comment using @PX4/testflight

  • Wait for feedback from the test team

Response Times

  • Multi-Copter: up to 48 hours (typically within 24 hours)

  • VTOL, Fixed Wing: up to 4 days (typically 2 days)

Test Cards

The tests performed for each platform are linked below:

Test Vehicles/Autopilots

Multicopter

FrameFlight ControllerUUID

002400283335510A33373538 (f450-v3)

000100000000363533353336510900500021 (f450-v3)

Cube (Pixhawk 2.1)

00010000000033343537313751050040001c (F450 Pixhawk v2 cube)

00010000000037373430333551170037002a (F450-Pixracer)

000100000000303236353136510500180036 (Pixhawk pro)

003200293036511638363834 (f450-v5-m)

000200000000383339333038510700320016 (F450-v5)

0002000000003432333830385115003a0033 (F450-v5-m)

000200000000323634353237511800200021 (F450-Pixhawk4)

Holybro QAV250

000200000000343233383038511500420032 (f450-v5-m)

NXP Semiconductor KIT-HGDRONEK66 ("Hovergames")

00030016ffffffffffff4e45362050130029

Fixed Wing

FrameFlight ControllerUUID

0001000000003035333330365104003c0020 (f450-v2)

VTOL

FrameFlight ControllerUUID

000200000000343233383038511500350039 (vtol-v5-m)

0001000000003437393931375114004c0042 (delta-v2)

Last updated