- Aug 12, 2017
-
-
DonLakeFlyer authored
-
- Aug 11, 2017
-
-
Don Gagne authored
-
- Aug 03, 2017
-
-
Jacob Walser authored
-
- Jul 31, 2017
-
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
Switch only to MAVLink 2 on first connected link. Fall back to v1 if two links to the same vehicle are connected and one can only do v1
-
Lorenz Meier authored
This extension introduces a complete version handshake mechanism which will detect wether the vehicle AND the complete link / routing infrastructure support MAVLink 2. If they do, QGC will switch to the highest protocol version supported by all connected vehicles. If a new vehicle connects, it will re-negotiate the highest possible version. This means that we error on the side of compatibility, which later can be easily changed.
-
- Jul 25, 2017
-
-
Jacob Walser authored
-
- Jul 21, 2017
-
-
Don Gagne authored
-
DonLakeFlyer authored
-
- Jul 19, 2017
-
-
DonLakeFlyer authored
-
Don Gagne authored
-
- Jul 17, 2017
-
-
Don Gagne authored
-
- Jul 15, 2017
-
-
DonLakeFlyer authored
-
- Jul 08, 2017
-
-
Lorenz Meier authored
-
- Jul 04, 2017
-
-
DonLakeFlyer authored
-
- Jul 01, 2017
-
-
DonLakeFlyer authored
-
- Jun 29, 2017
-
-
Don Gagne authored
-
- Jun 11, 2017
-
-
DonLakeFlyer authored
-
- Jun 09, 2017
-
-
DonLakeFlyer authored
-
- Jun 07, 2017
-
-
Jacob Walser authored
-
Jacob Walser authored
-
Jacob Walser authored
-
Jacob Walser authored
-
Jacob Walser authored
-
- May 14, 2017
-
-
Don Gagne authored
-
- May 13, 2017
-
-
DonLakeFlyer authored
-
DonLakeFlyer authored
-
DonLakeFlyer authored
-
- May 12, 2017
-
-
Mohammed Kabir authored
-
Jacob Walser authored
-
- May 08, 2017
-
-
Don Gagne authored
-
- May 06, 2017
-
-
DonLakeFlyer authored
-
- May 05, 2017
-
-
Gus Grubba authored
-
Don Gagne authored
-
- May 03, 2017
-
-
Jacob Walser authored
-
- May 02, 2017
-
-
DonLakeFlyer authored
-
DonLakeFlyer authored
-
- May 01, 2017
-
-
DonLakeFlyer authored
-
DonLakeFlyer authored
-