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.

waypoint trigger.jpg

transect lines.jpg

AIR_1.txt

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

Join diydrones

Email me when people reply –

Activity

DIY Robocars via Twitter
How to use the new @donkey_car graphical UI to edit driving data for better training https://www.youtube.com/watch?v=J5-zHNeNebQ
13 hours ago
DIY Robocars via Twitter
RT @SmallpixelCar: Wrote a program to find the light positions at @circuitlaunch. Here is the hypothesis of the light locations updating ba…
Saturday
DIY Robocars via Twitter
RT @SmallpixelCar: Broke my @HokuyoUsa Lidar today. Luckily the non-cone localization, based on @a1k0n LightSLAM idea, works. It will help…
Thursday
DIY Robocars via Twitter
@gclue_akira CC @NVIDIAEmbedded
Wednesday
DIY Robocars via Twitter
RT @luxonis: OAK-D PoE Autonomous Vehicle (Courtesy of zonyl in our Discord: https://discord.gg/EPsZHkg9Nx) https://t.co/PNDewvJdrb
Wednesday
DIY Robocars via Twitter
RT @f1tenth: It is getting dark and rainy on the F1TENTH racetrack in the @LGSVLSimulator. Testing out the new flood lights for the racetra…
Wednesday
DIY Robocars via Twitter
RT @JoeSpeeds: Live Now! Alex of @IndyAChallenge winning @TU_Muenchen team talking about their racing strategy and open source @OpenRobotic…
Nov 20
DIY Robocars via Twitter
RT @DAVGtech: Live NOW! Alexander Wischnewski of Indy Autonomous Challenge winning TUM team talking racing @diyrobocars @Heavy02011 @Ottawa…
Nov 20
DIY Robocars via Twitter
Incredible training performance with Donkeycar https://www.youtube.com/watch?v=9yy7ASttw04
Nov 9
DIY Robocars via Twitter
RT @JoeSpeeds: Sat Nov 6 Virtual DonkeyCar (and other cars, too) Race. So bring any car? @diyrobocars @IndyAChallenge https://t.co/nZQTff5…
Oct 31
DIY Robocars via Twitter
RT @JoeSpeeds: @chr1sa awesomely scary to see in person as our $1M robot almost clipped the walls as it spun at 140mph. But it was also awe…
Oct 29
DIY Robocars via Twitter
RT @chr1sa: Hey, @a1k0n's amazing "localize by the ceiling lights" @diyrobocars made @hackaday! It's consistently been the fastest in our…
Oct 25
DIY Robocars via Twitter
RT @IMS: It’s only fitting that @BostonDynamics Spot is waving the green flag for today’s @IndyAChallenge! Watch LIVE 👉 https://t.co/NtKnO…
Oct 23
DIY Robocars via Twitter
RT @IndyAChallenge: Congratulations to @TU_Muenchen the winners of the historic @IndyAChallenge and $1M. The first autonomous racecar comp…
Oct 23
DIY Robocars via Twitter
RT @JoeSpeeds: 🏎@TU_Muenchen #ROS 2 @EclipseCyclone #DDS #Zenoh 137mph. Saturday 10am EDT @IndyAChallenge @Twitch http://indyautonomouschallenge.com/stream
Oct 23
DIY Robocars via Twitter
RT @DAVGtech: Another incident: https://t.co/G1pTxQug6B
Oct 23
More…