Glenn,
You’re understanding is right on the mark.
Basically we don’t support the nav-takeoff command in guided mode, it’s only supported as part of a mission and we also require that the throttle be raised to start the mission (or guided mode) and this must be done through an rc-override.
Both are on the to-do list and are discussed in this particular issue:
https://github.com/diydrones/ardupilot/issues/656
I’m pretty sure I will get to these over the next few months but if anyone wants to take a crack at supporting the take-off as part of guided I’m happy to provide advice. It’s actually not that difficult to add because as part of the AVC balloon popper I added the “guided-mode” variable and structure to support guided mode doing various things besides just flying to a point.
Sorting out the RC override thing is a much bigger job because I think it will involve rewriting the RC_Channel library and supporting multiple input devices at the same time (i.e. TX and tablet input). I imagine we will model this on how we’ve added support for dual GPS, dual compass, etc.
-Randy
--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Glenn,
Yes, I think clearing the rc-override will work. At that point I would expect the throttle failsafe to trigger but if it’s already in AUTO mode and the FS_THR_ENABLE is set to 2 it will continue with the mission. When it came home it would see both the low throttle and the failsafe and it would disarm automatically. This all only applies to Auto mode though, if it was in guided mode the moment the rc-override was cleared the throttle failsafe would cause it to RTL.