Skip to content
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

add "move and rotate waypoints" mavlink command #1428

Open
tridge opened this issue Oct 1, 2014 · 4 comments
Open

add "move and rotate waypoints" mavlink command #1428

tridge opened this issue Oct 1, 2014 · 4 comments

Comments

@tridge
Copy link
Contributor

tridge commented Oct 1, 2014

add a single atomic command to move a set of waypoints with a rotation

@tridge tridge self-assigned this Oct 1, 2014
@haygood
Copy link

haygood commented Oct 2, 2014

So, take a set of waypoints of a given pattern or shape and scoot the whole pattern over and rotate the pattern?

@tridge
Copy link
Contributor Author

tridge commented Oct 2, 2014

yes. I have that in mavproxy now (I added it for the OBC drop), but it isn't atomic. I'd like it as an atomic command, to prevent packet loss leaving the aircraft with inconsistent mission items (that happened to us in our OBC mission)

@NiqueIt
Copy link

NiqueIt commented Oct 23, 2014

Like this too. My case are takeoff and landing procedures. Like to store a pattern and load it when a mission is planned. first, the approach has to moved to the planned launchpoint (and rotate). Just before the mission starts, we take care of the wind and probably neet to rotate the approach again. The approach is a subset of all WPs. Launch will not be complicate as it seems to be only a takeoff-WP. But the landing approach will contain more WPs

@davidbuzz
Copy link
Collaborator

A side-effect of doing this with on-board lua via the linked pr is that it's not 'lossy'
from the telemetry stream, and lua can easily read an entire mission (or multiple replaceable missions ) from the SD card. sure, there's tiny issue/s with how to handle the transitional state/s between mission loads, but lua doesn't need to 'wipe' mission/s in between, and it can even know which mission item is actively being executed and avoid over-writing the in-use item till it's no-longer-in-use etc... #13685

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants