Add branching feature #26
Open
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
kibidev
force-pushed
the
pr_branch_selector
branch
2 times, most recently
from
592abe3 to
305eaf0
Compare
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 the solution for branching waypoints with no changes required on the PX4 side. This will also preserve backward compatibility with QGC.
The feature allows using multiple Jump to items (MAV_CMD_DO_JUMP) as a branching waypoint.
Usually Jump to items are used when a certain condition is reached to activate to jump to a predefined waypoint.
If multiple Jump to items are put one after another only the first one will be used from the PX4 side.
This solution adds the option for the pilot to manually select one of all predefined Jump to items.
Link to the video with the feature in action:
https://youtu.be/wyUkNFZhwGI