mavlink: add message spacing for AVAILABLE_MODES, for low bandwidth#25428
mavlink: add message spacing for AVAILABLE_MODES, for low bandwidth#25428
Conversation
There was a problem hiding this comment.
maybe @bkueng could also help. The rest seem ok to me.
|
Curious why the existing "Mav Rate" param is not sufficient to prevent TX overflows ? Can MAVLINK_MODE_LOW_BANDWIDTH and/or LOW_BANDWIDTH_DELAY_US be inferred from the "Mav Rate" ? |
|
FWIW only - The GCS should re-request specific modes it doesn't get first time. It still makes sense to manage the bandwidth of course. |
|
@jsm09a: Yes good point. Logic now respects the rate |
0632490 to
8f50a4c
Compare
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 88 byte (0 %)]px4_fmu-v6x [Total VM Diff: 80 byte (0 %)]Updated: 2025-08-18T15:20:36 |
0f5bf27 to
e9591b8
Compare
Solved Problem
PX4 sends all of the available modes at once via mavlink, this can overflow the TX buffer of low bandwidth radios, causing the ground station to not receive most of them.
Solution
Test coverage