GCS_Mavlink: Set a minimum delay for FTP burst read #29326
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
burst_delay_ms is initialized to 0.
In case of using SITL with UDP direct connexion, it will stay to 0, pushing Mavlink packets at full speed. This drive to lost packets.
I made some tests with different receive buffer size (best for me is 512 Bytes) and it works with a minimum value of 4ms, then I putted 5 to get some security.
This introduce a latency arround 350ms for a Copter full parameter ( SITL = 1454 parameters) FTP burst read (70 Mavlink messages) .