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
DJI Spark Forums
Spark Help
Nearly had a flyaway today
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="Saigondroner" data-source="post: 92243" data-attributes="member: 17363"><p>Here are 4 log files: </p><p></p><p>1st one is the 1st flight, using Litchi, with iOS. This is when things started to go awry, and I engaged RTH</p><p>2nd one is the same flight, but I extracted the log from the Spark itself, using DJI Assistant 2</p><p>3rd one is the 2nd flight, that was totally out of control. I used Go4.</p><p>The final log is the same 2nd flight, but I extracted using DJI Assistant 2.</p><p></p><p>I used Phantomhelp to read the DJI .txt & Litchi .csv file, and DatCon to read the DJI .dat files I extracted from the Spark itself. I think a much of the 2nd flight's log are not 100% valid. The Spark was reporting a FORBIN error with the compass problems. My guess is that means 'forbidden'.</p><p></p><p>It looks like a combination of very poor GPS coverage, and serious interference, for both the controller and the compass.</p><p></p><p>As far as the CSC stick abort goes, I am sure that is what I did in Flight #1. I'm happy to re-test another time. I kicked a prop 2nd flight....as it appeared the Spark was headed back toward water.</p><p></p><p>Over the weekend, in a very rural area, the Spark performed almost perfectly. Wifey says it's because she wrapped it well ;-)</p><p></p><p>Thanks for any insight!</p><p></p><p>[ATTACH=full]10330[/ATTACH]</p></blockquote><p></p>
[QUOTE="Saigondroner, post: 92243, member: 17363"] Here are 4 log files: 1st one is the 1st flight, using Litchi, with iOS. This is when things started to go awry, and I engaged RTH 2nd one is the same flight, but I extracted the log from the Spark itself, using DJI Assistant 2 3rd one is the 2nd flight, that was totally out of control. I used Go4. The final log is the same 2nd flight, but I extracted using DJI Assistant 2. I used Phantomhelp to read the DJI .txt & Litchi .csv file, and DatCon to read the DJI .dat files I extracted from the Spark itself. I think a much of the 2nd flight's log are not 100% valid. The Spark was reporting a FORBIN error with the compass problems. My guess is that means 'forbidden'. It looks like a combination of very poor GPS coverage, and serious interference, for both the controller and the compass. As far as the CSC stick abort goes, I am sure that is what I did in Flight #1. I'm happy to re-test another time. I kicked a prop 2nd flight....as it appeared the Spark was headed back toward water. Over the weekend, in a very rural area, the Spark performed almost perfectly. Wifey says it's because she wrapped it well ;-) Thanks for any insight! [ATTACH type="full" alt="10330"]10330[/ATTACH] [/QUOTE]
Verification
Post reply
Forums
DJI Spark Forums
Spark Help
Nearly had a flyaway today