Hello,

I played around with mission planner and today wanted to do my first camera mission. Unfortunately I clicked to update the apm software yesterday, which radically changed the functionality, so I had to think in the field...

Before I used GridV2 to plan a mission. I'm using what used to be called a relay, but is actually pin A9 on the APM. That is connected to an opto isolator, which triggers the Canon camera through CHDK.

Now, in the new version, I just clicked "survey (Grid)" in the mission planner and this seemed to work. I could load my camera there, input the altitude and it would (apparently) make a nice mission. What I did not notice is that the MP didn't actually insert action waypoints to trigger the camera. *sigh*. So no pics were taken.

Right now I noticed there's a checkbox "Advanced options", which makes some tabs appear. In one of the tabs the actual camera parameters can be verified. In the last one you can make changes to the type of the trigger. Looks like the default is a "camera distance trigger", which I actually used before when set to 40 meters or so, which then generated a valid mission. When I use that, I don't see any waypoints appearing.

I can also set this to "DO_DIGICAM_CONTROL", but I don't know if that's the same as "DO_SET_RELAY". Can anyone confirm it's acting on pin A9 and just pulses that for the set duration in the CAM_DURATION settings in the parameters?  I expect this to be up 100ms or so.

So... the new functionality does seem to work better and offloads a lot of the internal calculations that otherwise need to take place. In terms of user friendliness, I'm not sure if people would find the trigger type so easily and whether the default is the best type of trigger to use (considering APM should know about how the board is configured, since it loads all the parameters. So why not use that?).

On the up-side... the mission itself was executed beautifully without any glitch. And the ground station allowed us to follow that from a telemetry perspective.

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

Join diydrones

Email me when people reply –

Replies

  • If you use the CAMERA_TRIG_DISTANCE option it doesn't set any waypoints because it uses the GPS data to trigger the camera at the set distance, it saves the waypoints for navigation.

    You seem to have done everything correctly, after you created and written your mission to the APM using survey(grid) did you check in the advance parameters list that the distance variable for CAMERA_TRIG_DISTANCE had been automatically generated by the survey(grid) function.

    Also did you set a servo output  for your camera trigger, I set servo out for channel 7 in the parameters list to "camera trigger" and connected my gentwire to it and walked my APM along the ground and it triggered the camera at the my chosen trigger distance(38m)

    Hope this helps

    Martin : )

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @TinkerGen_: "The Tinkergen MARK ($199) is my new favorite starter robocar. It’s got everything — computer vision, deep learning, sensor…
yesterday
DIY Robocars via Twitter
yesterday
DIY Robocars via Twitter
RT @roboton_io: Join our FREE Sumo Competition 🤖🏆 👉 https://roboton.io/ranking/vsc2020 #sumo #robot #edtech #competition #games4ed https://t.co/WOx…
Nov 16
DIY Drones via Twitter
First impressions of Tinkergen MARK robocar https://ift.tt/36IeZHc
Nov 16
DIY Robocars via Twitter
Our review of the @TinkerGen_ MARK robocar, which is the best on the market right now https://diyrobocars.com/2020/11/15/first-impressions-of-tinkergen-mark-robocar/ https://t.co/ENIlU5SfZ2
Nov 15
DIY Robocars via Twitter
RT @Ingmar_Stapel: I have now explained the OpenBot project in great detail on my blog with 12 articles step by step. I hope you enjoy read…
Nov 15
DIY Robocars via Twitter
RT @DAVGtech: This is a must attend. Click the link, follow link to read the story, sign up. #chaos2020 #digitalconnection #digitalworld ht…
Nov 15
DIY Robocars via Twitter
RT @a1k0n: Got a new chassis for outdoor races (hobbyking Quantum Vandal) but I totally didn't expect that it might cause problems for my g…
Nov 11
DIY Drones via Twitter
First impressions of the Intel OpenBot https://ift.tt/36qkVV4
Nov 10
DIY Robocars via Twitter
Nov 9
DIY Robocars via Twitter
Excellent use of cardboard instead of 3D printing! https://twitter.com/Ingmar_Stapel/status/1324960595318333441
Nov 7
DIY Robocars via Twitter
RT @chr1sa: We've got a record 50 teams competing in this month's @DIYRobocars @donkey_car virtual AI car race. Starting today at 10:00am…
Nov 7
DIY Robocars via Twitter
Nov 6
DIY Robocars via Twitter
RT @a1k0n: Car's view, using a fisheye camera. The ceiling light tracking algorithm gave me some ideas to improve ConeSLAM, and having grou…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: To get ground truth I measured the rug, found the pixel coordinates of its corners, calibrated my phone camera with my standard…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: @DIYRobocars is back in December, but outside. Time to reinvestigate ConeSLAM! I rigged up a quick and dirty ground-truth captur…
Nov 5
More…