-
Notifications
You must be signed in to change notification settings - Fork 13.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Robustify mission upload/download (take 2) #8794
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 4e008fe.
The mission items need to be requested one by one by a ground station. This is a "pull" protocol and we should not retry to "push" the mission items down. If we do this we can trigger the situation where the autopilot keeps retrying and the ground station does not time out because it keeps receiving items (even though the items are the wrong ones).
When actively re-requesting lost mission items, we can be more agressive and therefore lose less time when a mission item is lost on the way.
LorenzMeier
approved these changes
Feb 1, 2018
Jenkins failed. |
@LorenzMeier not sure how that is related:
|
It might be one of the remaining intermittent failure cases. Keep track of the failure link and I'll restart the job. Update: this one is new, there's not even a ulg. |
dagar
approved these changes
Feb 1, 2018
Stifael
pushed a commit
to Stifael/Firmware
that referenced
this pull request
Apr 3, 2018
* Revert "mavlink_mission: don't retransmit automatically" This reverts commit 4e008fe. * mavlink_mission: don't retry to send mission item The mission items need to be requested one by one by a ground station. This is a "pull" protocol and we should not retry to "push" the mission items down. If we do this we can trigger the situation where the autopilot keeps retrying and the ground station does not time out because it keeps receiving items (even though the items are the wrong ones). * mavlink_mission: reduce retry timeout When actively re-requesting lost mission items, we can be more agressive and therefore lose less time when a mission item is lost on the way.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a follow up to #8750.
This fixes #8791.
For more info and to review, please check the commit messages.
Tested with QGC release, and QGC from mavlink/qgroundcontrol#6059, and DroneCore mavlink/MAVSDK#230.