Feature Request: Terminal Waypoint

Hi Michael,

During our Melbourne meetup and fly today, in which we did several autonomous flights with several quads, we found that there is potential for unusual/unexpected/unwanted behaviour at the conclusion of a mission, if you leave the last waypoint type set to WAYPOINT. Basically the vehicle hits it's target and then doesn't know what to do, so if you're not paying attention, you can get into trouble.

Now, you may already have something built-in to deal with this operator deficiency, but a suggestion (if you don't) would be to run a quick verification on the final waypoint when you press "Write WPs". Checking that it's an unlimited loiter, or land (or some other appropriate choice... and not simply WAYPOINT) and providing a dialog box warning of a non-terminal state for the plan would be good. Here I mean a terminal state is one that is considered stable for all time (so landing, or unlimited loiter). Does this make sense?

Also, is there a simply way to make the plan continuously cyclic... e.g., WP1, WP2,...,WPn, WP1, WP2,..., etc?

Thanks,

Tim

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

Join diydrones

Email me when people reply –

Replies

  • Thanks for the quick reply Michael... I'll need to check what value rtl_alt_final is set at... but my copter definitely didn't loiter at its final point... and it had been okay at loiter within the plan (it had a 10s duration loiter within a 3m circle that it handled serveral times without problem). I'll look into this further. Thanks for the info and advice.

  • Developer

    Hi Tim,

    it is meant to switch into loiter, if the last wp is a WAYPOINT ,depending on what rtl_alt_final is set as. if its set as 0, it will land, if above that it will loiter at that altitude. the default is 2m, so it will go into loiter and ascend/descend to 2m

     

    To make it go around and around you need to use a DO_JUMP, and set the wp target to 1 and count to say 99, or similar.

    Michael

This reply was deleted.

Activity

DIY Robocars via Twitter
May 15
DIY Robocars via Twitter
May 14
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…