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

DO_SET_ROI modification request (saving complexity, waypoint space) #969

Closed
AndKe opened this issue Apr 11, 2014 · 3 comments
Closed

DO_SET_ROI modification request (saving complexity, waypoint space) #969

AndKe opened this issue Apr 11, 2014 · 3 comments

Comments

@AndKe
Copy link
Contributor

AndKe commented Apr 11, 2014

Please make DO_SET_ROI stay valid until new DO_SET_ROI or DO_END_ROI

Currently, DO_SET_ROI needs to be set for every single WP, effectively doubling the mission items, and making it a mess to manage/change ROI.
(user may need to change altitude/position of lots ROI points in case a correction is needed.
Please see:
http://ardupilot.com/forum/viewtopic.php?f=12&t=7179

There are no drawbacks, only advantages.

@AndKe
Copy link
Contributor Author

AndKe commented Apr 11, 2014

Additional bonus: Creators of flight planning software would have a much easier life.

@jmachuca77
Copy link
Contributor

I believe Randy already changed this for 3.2. It's a duplicate of issue #569.

Jaime

On Apr 11, 2014, at 3:12 PM, AndKe notifications@github.com wrote:

Additional bonus: Creators of flight planning software would have a much easier life.


Reply to this email directly or view it on GitHub.

@rmackay9
Copy link
Contributor

Yes, already done in master. It'll be available for testing around the end of April when the first AC3.2 release candiate goes out.
thanks for the report in any case.

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

No branches or pull requests

3 participants