Camera trigger, again

Hi,

I would like to know if there is a ready made solution for configuring the APM2.5 to take photos at fixed distance intervals, by using a voltage based trigger, e.g. as with chdk on canon cameras.

I know this question has been asked here before, (several times), but I am however still not aware of any good answer to the question. So, any help is appreciated.

Cheers!

Jorn

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

Join diydrones

Email me when people reply –

Replies

  • The function 'verify_nav_wp()' lives in the commands_logic ArduPlane sketch. This code runs and verifies that a waypoint has been reached. You could add a flag in that function to trigger a 5V digital output on your APM board. It would run for every single waypoint during your mission though, until you add more code to choose specifically which waypoints you want.

  • Same here. Need a logic signal to trigger my camera at specific waypoints.

  • Jerry, are you firing a camera running CHDK?

    The problem I've had with using the servo command is that it only puts out PWM not solid 5V signals. I haven't tested it in a while but I think CHDK is unable to register anything when you send it PWM. As far as I remember I think it needed to be a 5V pulse on the order or 10ms before it recognized anything. 

  • Hi are you guys still looking into this?

    I did something similar to this with my APM 1.

    Camera: I have an old samsung still camera that I pulled apart and soldered some wires with a connector across the focus/shoot button. The camera still works from the original button or can be triggered through the connector by shorting focus and shoot to ground.

    Camera Control: I'm using 2 NPN transistors (1 for focus, 1 for shoot), controlled by a simple 5V digital outputs from the APM to activate the focus and shoot on the camera.

    APM: I used the 2 expansion ports on the top of the oil pan (A5 and A6 are analog inputs but I configure them as digital outputs). Then in the arduplane code, added a basic function to calculate distance intervals (accumulative or straight line), or time interval, focus and shoot control.  I also modified the dataflash code so that the onboard GPS log has an extra column for 'log camera trigger'. Which writes 'zero' when not shooting and writes '1' when a trigger command is sent. This can be used to geo-locate where the image was taken. It all runs independently of the mission planner though . It's really scrappy in its current form but it got the job done for me.

    Sorry that it isn't the clearest description. The main point I'm trying to get across is that fixed distance or time interval triggering and APM camera control is entirely achievable. It's just that there isn't yet a single neat and tidy solution. If/when I decide to upgrade my camera I'd probably go for a canon with CHDK and use hacked USB control from the APM. And I'd look into the MavLink commands to make it more user friendly from the GCS.

  • I was thinking to use a free port on the MinimOSD ATMega to trigger a CHDK Cannon. If you want to use a timer, that's easy, but then the CHDK alone will do it. What I wanted is an event-based trigger, like when switching from stabilize to loiter, read off the MavLink parameters.

    Maybe someone with a lot more missions then me can answer this: If I program a course with a few waypoints, and instructions to loiter for let's say 10 seconds at each waypoint, what MavLink parameter shall I follow to have the camera snap a picture at every waypoint ?

  • I have simply been using the servo commands in the mission planner to fire the camera at 3 second intervals from launch to land.
  • I second this request. After all this time it's amazing that there still isn't a straight forward set of camera triggering parameters.

This reply was deleted.

Activity

DIY Robocars via Twitter
May 15
DIY Robocars via Twitter
May 14
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…