We have been using Arducopter 3.2.1 and log bitmask set to 4100 to just get cam triggers and GPS locations.
Has been working great since last year.
We are now running Pixhawk 1 with v3.5.1 Octaquad with same 4100 and it only recorded CAM values one flight out of 4 different missions.
We flew multiple flights after this to try to get it to log CAM every time, changing to the listed values in MP full parameter tree and only ALL-AC315 would log the CAM. Problem is that these are big files for just a 15 minute flight and they fail when trying to download via data radio.
Data radio works fine on the smaller file we would get with value 4100.
Any ideas?
Another question:
We are also getting a delay of sorts for our triggering. In attached picture the dots represent trigger locations.
They should be straight lines running west-east on the polygon with CAM trigger starting and stopping at beginning and end of line. The trigger stops too soon and then starts while turning to line up for next transect line.
Looking at the flight path it flew the mission perfectly just didn't trigger correctly.
We are flying at 9 m/s and have distance triggering set for 9 meters.
We have set cam trigger distance at 9 as it flies west-east across the polygon and set to zero at the next waypoint on end of transect line. It then turns and flies north to next waypoint and we set distance to 9 again as it flies to the end of the next transect line east-west where it is again set to Zero. This pattern repeats the whole mission.
Waypoint radius is set to 3 meters. If we go larger than that it seems to always cut the corners as it turns.
Result is shown in the picture.
Is there a method to get it to start and stop the triggering right on the waypoint rather than in middle of the turn?
Mission file attached as well.
Any help would be great.
Thanks.
Replies