Menu
Forums
New posts
Search forums
What's new
New posts
New media
New media comments
New profile posts
Latest activity
Media
New media
New comments
Search media
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Search
Search titles only
By:
Search titles only
By:
Menu
Welcome DJI Spark Pilot!
Jump in and join our free Spark community today!
Sign up
Forums
General Forums
General Discussions
AutoPilot and the Spark
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Chrislaf" data-source="post: 52771" data-attributes="member: 3317"><p>Today I went out again to try shooting a mapping mission. I used my same mission as before but just changed a few things and tested each time. I flew 4 missions (all 4 of my batteries). I had SUCCESS on my 3rd mission - the Spark took photos! Finally! The 4th mission flew the path but again no pictures were taken.</p><p></p><p>Here's what I did for the successful mission: I set the gimbal to the default -84º, Ground Sample Reference to 'Capture Angle' (not sure if this makes any difference), and height to 22m. Once I started the motors I went into the photo menu (interval is automatically chosen for mapping) and set the interval to 2s and the number of shots to 150. I then engaged the mission and once the Spark got to the first boundary point the interval shooting began (the camera button changed from white to red) and the Spark flew noticeably different. It flew ahead a bit tilted down quickly then flew ahead again, rotated a bit, tilted down again, etc. I am sure glad I had my battery clip on because the movements are fast and sharp so if the battery was not snug this would certainly jiggle it free. When the mission completed the Spark was still taking some interval shots so I manually stopped it. The Spark took 143 images and 7 more while idling at the end point.</p><p></p><p>The fourth mission was not successful likely because I changed the interval to 4s and 60 shots. When I looked up the Spark Specs it only supports intervals at 2/3/5/7/10/15/20/30/60s, so my setting to 4s is likely why it didn't work.</p><p></p><p>What I have observed about AutoPilot is that the settings in any mode must match what the AC is capable of. I had a similar problem with panos not working initially because the defaults are for Aircraft with 3 axis gimbals that can tilt down 90º. I still have lots of trial and error left to do to figure out exactly what works for the mapping missions.</p><p></p><p>Regardless, it's pretty amazing what can be done with this software. It adds many features that are not supported on the GO4 app. This is similar to what Litchi does for the Phantom 3 Standard. Thank God for 3rd party developers!</p><p></p><p>Chris</p></blockquote><p></p>
[QUOTE="Chrislaf, post: 52771, member: 3317"] Today I went out again to try shooting a mapping mission. I used my same mission as before but just changed a few things and tested each time. I flew 4 missions (all 4 of my batteries). I had SUCCESS on my 3rd mission - the Spark took photos! Finally! The 4th mission flew the path but again no pictures were taken. Here's what I did for the successful mission: I set the gimbal to the default -84º, Ground Sample Reference to 'Capture Angle' (not sure if this makes any difference), and height to 22m. Once I started the motors I went into the photo menu (interval is automatically chosen for mapping) and set the interval to 2s and the number of shots to 150. I then engaged the mission and once the Spark got to the first boundary point the interval shooting began (the camera button changed from white to red) and the Spark flew noticeably different. It flew ahead a bit tilted down quickly then flew ahead again, rotated a bit, tilted down again, etc. I am sure glad I had my battery clip on because the movements are fast and sharp so if the battery was not snug this would certainly jiggle it free. When the mission completed the Spark was still taking some interval shots so I manually stopped it. The Spark took 143 images and 7 more while idling at the end point. The fourth mission was not successful likely because I changed the interval to 4s and 60 shots. When I looked up the Spark Specs it only supports intervals at 2/3/5/7/10/15/20/30/60s, so my setting to 4s is likely why it didn't work. What I have observed about AutoPilot is that the settings in any mode must match what the AC is capable of. I had a similar problem with panos not working initially because the defaults are for Aircraft with 3 axis gimbals that can tilt down 90º. I still have lots of trial and error left to do to figure out exactly what works for the mapping missions. Regardless, it's pretty amazing what can be done with this software. It adds many features that are not supported on the GO4 app. This is similar to what Litchi does for the Phantom 3 Standard. Thank God for 3rd party developers! Chris [/QUOTE]
Verification
Post reply
Forums
General Forums
General Discussions
AutoPilot and the Spark