Parameters often fail to transfer with QGroundControl #2

New Issue

Open

opened 2020-09-25 12:08:30 -06:00 by jebba · 1 comment

jebba commented

2020-09-25 12:08:30 -06:00

Collaborator

The SkyViper by default uses UDP 14550 for MAVLink.

With QGroundControl connected to the drone, there is way too high message loss rate, often over 50%.

If QGroundControl is not running, and MAVProxy is connected to the drone, the parameters all download, with around 3% message loss (acceptable).

If MAVProxy receives UDP 14550 from the drone, and proxies it to QGroundControl on port 16550, QGroundControl still has very high message loss.

This has been tested using the drone in Wifi host mode (default) and also with the drone as a client to a TP-Link base station.

TCP/IP connection to the drone has been very reliable. Ping is 100%. Using the drone web server is fast and responsive. So it isn't a wifi issue, in general.

The SkyViper by default uses UDP 14550 for MAVLink. With QGroundControl connected to the drone, there is way too high message loss rate, often over 50%. If QGroundControl is not running, and MAVProxy is connected to the drone, the parameters all download, with around 3% message loss (acceptable). If MAVProxy receives UDP 14550 from the drone, and proxies it to QGroundControl on port 16550, QGroundControl still has very high message loss. This has been tested using the drone in Wifi host mode (default) and also with the drone as a client to a TP-Link base station. TCP/IP connection to the drone has been very reliable. Ping is 100%. Using the drone web server is fast and responsive. So it isn't a wifi issue, in general.