You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • Hi,

    Are rally points compatible with the APMRover2 build?

    Thanks

  • It is now gone from the Wiki page. The Wiki page on Flight Modes even points to the page that is gone.

  • Hi Michael, We would love to have your feedback on future wiki projects on the APM Wiki Editors Discuss group. Looking forward to seeing you there!

    Best,

    -Alex

  • Very nice, love this!

  • Hi Michael,

    It seemed to me that it pretty much related to mission planner settable features and so belonged there.

    But I had looked through and didn't see your link under First Flights. 

    I would have thought rally points might be a bit advanced for first flights and they are very much a Mission Planner feature. (Of course I sort of feel that way about Geofencing too.)

    OK to leave it both places for the moment.

    And it is in the Table of Contents (TOC Menu) now too.

    Our subtopic headings aren't always ideal in any case.

    And we don't always agree on what ought to be where.

    In any case, great job on Rally Points, a really excellent and thorough description and illustration of the feature.

    Best Regards,

    Gary

  • Gary,

    I do have permissions to edit menus and I had placed Rally Points in the menu after under First Flight after Geofencing (at Tridge's request) when I originally published the page.

    I see it's now also under Mission Planning and Analysis.  Probably should not be in two places?  I actually like it better under Mission Planning.

    -m

  • MR60

    I want this for arducopter ! That's a great feature.

  • I should have asked this before Michael,

    Do you have menu write permissions.

    Can you in fact access Appearances -> Menu and then edit the Instructions or TOC Menu I know that is a separate authorization step and I would like to know your status on this.

    All you need to do is try to get to either of those menus.

    If you can you can edit them if not then you can't.

    Thank You,

    Gary

  • @Nathaniel:

    I see I neglected to answer you first questions.


    1. For Mission Planner: Uploaded separately, yes.  Currently rally Points are _downloaded_ simultaneously when downloading mission waypoints (so NOT downloaded separately).  MAVProxy's behavior is different: both uploading and downloading are separate operations.

    2. For Mission Planner: Good question.  This actually needs to be addressed in Mission Planner... rally waypoints should be save-able to hard disk to a rally point file (they are NOT saved in the mission plan).  I will submit a request to the Mission Planner maintainer and see what can be done. Rally Points are intended to be saved separately because it is quite conceivable to have fairly static Rally locations at a flying field while the mission waypoints are likely to change often.

    3. Rally points persist in flash memory (no matter their location) until the user deletes them.  The reason for the RALLY_LIMIT_KM parameter is to safely allow Rally Points to remain in flash memory no matter their location (so rally points can be specified for multiple flying fields).

    Hope this helps,

    -m

  • @Nathaniel:

    Good catch on that wiki error.  Should be fixed now.
    On an evacuation route: plans are in the works to

    1. Provide terrain following (PX4/Pixhawk only). APM's memory is not large enough to handle terrain following, though.   This also does not cover the case where the obstacle(s) in question are not terrain.
    2. Allow a Rally Point to loiter a bit and then, if there is no user intervention, proceed to the nearest landing waypoint.  Some path planning logic needs to be added for that to work... not sure when it will be done.

    Allowing user-defined evacuation path planning is therefore probably a good idea... in the future a Rally Point could be configured to proceed to an arbitrary waypoint instead of just a landing waypoint.

    @Gary: Thanks for those pointers.  I will endeavor to improve any future wiki posts.

This reply was deleted.