Parameters often fail to transfer with QGroundControl #2
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
spacecruft/skyviper-journey#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Probably caused by #3.