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
A GPS Black Hole?
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="joeke3el" data-source="post: 94741" data-attributes="member: 17909"><p>Jim, thanks for your reply. Since posting this I've learned a few more things. ATTI mode happened once while flying manually with the controller and the DJI GO 4 app and also on another day flying autonomously with a Litchi mission. So far I've dived into the Litchi mission issue and have come up with the following:</p><p></p><p>1. The crazy gimbal activity was due to flight plan gimbal control not executing because the drone was out of RC range. I initially did not know you can't program gimbal movement in areas where there is no RC contact. As a result, when the drone got back into range, all the gimbal commands were pushed through and you can see in the footage all the commands executing in rapid fashion to catch up. </p><p>2. I uploaded the Litchi flight log to Airdata.com and looked at the Kp Index at the time of the fight. It was 3-1/3 which is still in the "generally safe" zone but also considered "unsettled" on the chart. I do recall the Spark taking longer than usual to get a lock so in retrospect I probably should have called off the mission. The logs show 15 sats at the moment ATTI kicked in but a Kp of 3-1/3 seems close enough where there may have been a brief moment where it bumped to 5 or 6 and momentarily knocked the drone off. After a few moments of ATTI it did return to GPS which really helped me pilot it home. </p><p></p><p>Conclusion of the Litchi Mission: My UAV Forecast app only showed 9 sats and even though the Spark had 12 before launch, I should have taken heed to this and waited for better conditions as usually my iPhone app would show at least 12. So things were probably marginal when I launched. I think it all was my fault.</p><p></p><p>As for the manual flight, I was using the controller, was 143 feet up and about 150 feet from home when it occurred. I have not uploaded that log yet but I was even less experienced on that day and chances are I was flying again when maybe I shouldn't have. The only uncertainty is I was 143 feet above a residential satellite dish when it happened. Not sure if they have internet through that or just TV. Not sure if internet transmission could cause a problem since it's not sharing the same bands as drones. But radio waves have done crazier things to electronics. We'll see. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>Joe</p></blockquote><p></p>
[QUOTE="joeke3el, post: 94741, member: 17909"] Jim, thanks for your reply. Since posting this I've learned a few more things. ATTI mode happened once while flying manually with the controller and the DJI GO 4 app and also on another day flying autonomously with a Litchi mission. So far I've dived into the Litchi mission issue and have come up with the following: 1. The crazy gimbal activity was due to flight plan gimbal control not executing because the drone was out of RC range. I initially did not know you can't program gimbal movement in areas where there is no RC contact. As a result, when the drone got back into range, all the gimbal commands were pushed through and you can see in the footage all the commands executing in rapid fashion to catch up. 2. I uploaded the Litchi flight log to Airdata.com and looked at the Kp Index at the time of the fight. It was 3-1/3 which is still in the "generally safe" zone but also considered "unsettled" on the chart. I do recall the Spark taking longer than usual to get a lock so in retrospect I probably should have called off the mission. The logs show 15 sats at the moment ATTI kicked in but a Kp of 3-1/3 seems close enough where there may have been a brief moment where it bumped to 5 or 6 and momentarily knocked the drone off. After a few moments of ATTI it did return to GPS which really helped me pilot it home. Conclusion of the Litchi Mission: My UAV Forecast app only showed 9 sats and even though the Spark had 12 before launch, I should have taken heed to this and waited for better conditions as usually my iPhone app would show at least 12. So things were probably marginal when I launched. I think it all was my fault. As for the manual flight, I was using the controller, was 143 feet up and about 150 feet from home when it occurred. I have not uploaded that log yet but I was even less experienced on that day and chances are I was flying again when maybe I shouldn't have. The only uncertainty is I was 143 feet above a residential satellite dish when it happened. Not sure if they have internet through that or just TV. Not sure if internet transmission could cause a problem since it's not sharing the same bands as drones. But radio waves have done crazier things to electronics. We'll see. :-) Joe [/QUOTE]
Verification
Post reply
Forums
General Forums
General Discussions
A GPS Black Hole?