Excessive MAVLink Message Loss in QGroundControl #3

New Issue

Closed

opened 2020-09-25 12:15:14 -06:00 by jebba · 2 comments

jebba commented

2020-09-25 12:15:14 -06:00

Collaborator

This is probably the cause of #2.

QGroundControl has over 50% MAVLink message loss to the drone.

MAVProxy has around 3% MAVLink message loss to the drone (acceptable).

Using MAVProxy as a proxy for QGroundControl doesn't appear to help.

Checking "High Latency" in the Link Configuration doesn't help.

Using the drone as the access point helps marginally, but doesn't solve problem. Using drone as wifi client is marginally worse.

This is probably the cause of #2. QGroundControl has over 50% MAVLink message loss to the drone. MAVProxy has around 3% MAVLink message loss to the drone (acceptable). Using MAVProxy as a proxy for QGroundControl doesn't appear to help. Checking "High Latency" in the Link Configuration doesn't help. Using the drone as the access point helps marginally, but doesn't solve problem. Using drone as wifi client is marginally worse.

jebba added the

bug

qgroundcontrol

labels 2020-09-25 12:15:14 -06:00

jebba referenced this issue

2020-09-25 12:15:33 -06:00

Parameters often fail to transfer with QGroundControl #2

jebba commented

2020-09-25 12:20:34 -06:00

Poster

Collaborator

The default is checked, default settings below:

All Streams Controlled by Vehicle Settings

Raw Sensors	2 hz
Extended Status	2 hz
RC Channel	2 hz
Position	3 hz
Extra 1		10 hz
Extra 2		10 hz
Extra 3		3 hz

The default is checked, default settings below: ``` All Streams Controlled by Vehicle Settings Raw Sensors 2 hz Extended Status 2 hz RC Channel 2 hz Position 3 hz Extra 1 10 hz Extra 2 10 hz Extra 3 3 hz ```

jebba commented

2020-10-13 17:07:26 -06:00

Poster

Collaborator

Newer versions of qgroundcontrol may be doing it better. This process works:

Start qgroundcontrol, but don't start communication.
Start drone, and wait for it to fully boot.
Start communication in in qgroundcontrol. This should download the parameters happily now.

Newer versions of `qgroundcontrol` may be doing it better. This process works: * Start `qgroundcontrol`, but don't start communication. * Start drone, and wait for it to fully boot. * Start communication in in `qgroundcontrol`. This should download the parameters happily now.

jebba closed this issue

2020-10-13 17:07:30 -06:00