Auto WP - Grid and Gridv2 variable command.

[GoogleCodeExporter]

Currently, Auto WP - 'grid' and 'gridV2' generates a waypoint-based search 
grid. Would there be a possibility to select what command type can be defined 
inside the grid? Such as a relay or a servo command?

This would be useful for users that require more finer control with camera 
shutter command being actuated by APM.

Original issue reported on code.google.com by jmgam...@gmail.com on 23 Sep 2012 at 10:05

[GoogleCodeExporter]

not currently. what did you have in mind?

Original comment by Meee...@gmail.com on 25 Sep 2012 at 7:58

[GoogleCodeExporter]

Original comment by Meee...@gmail.com on 25 Sep 2012 at 10:24

[GoogleCodeExporter]

Hi,

Thanks for responding. What I had in mind was. After defining a polygon. Then 
selecting Auto WP -> Grid. You will be asked.

- Relative Altitude
- Distance between lines
- Put a WP every x distance (-1 for none)
- Enter the line direction

I was thinking of maybe adding another popup called "Command". And one can 
enter a command -- such as DO_DIGICAM_CONTROL to actuate the camera at every 
waypoint.

thanks in advance. ;)

Original comment by jmgam...@gmail.com on 27 Sep 2012 at 5:17

[GoogleCodeExporter]

Original comment by Meee...@gmail.com on 11 Nov 2012 at 1:28

• Changed state: Accepted

[GoogleCodeExporter]

Hi,

I just joined DIY Drones last night, and this is my first post, so please 
forgive me if I inadvertantly rehash a topic that's already been resolved.

The Grid and GridV2 functions appear to have missed two important features 
which render them almost useless in their current form for grid-based aerial 
imaging. First, there is no way to generate a grid of anything other than 
default WAYPOINT waypoints. This means a user who wants to do something like 
trigger a camera must manually change each one of these to a DO_DIGICAM_CONTROL 
command - not a pleasant task if one has many waypoints. Second, since 
apparently all DO_<whatever> commands require a dummy waypoint after the 
command to "close" it, the user must manually add a dummy waypoint after each 
grid position. This will greatly clutter the flight profile with irrelevant 
waypoints.

Can a better method be developed to accomplish this? What about simple 
distance-based camera triggering that is toggled on and off using a DO_ type 
command? The user enters a distance, and for as long as the distance-based 
triggering is toggled ON, the shutter control is triggered every time the UAV 
has gone that distance from the last trigger point. The user just has to lay 
out the flight profile with the proper line spacing - no intermediate grid 
points are needed. I can think of a couple of enhancements for this, but I 
won't pile on unless there's interest in developing this functionality, which 
would be extremely useful to the aerial mappers like me.

Thanks for an otherwise fantastic gizmo!

Original comment by airborne...@gmail.com on 24 Dec 2012 at 12:55