Mission "pausing" for 12 seconds? No errors.
This mission: https://app.dronelink.com/2672/roamer105/plan/Ff1gWZ6eq6ebG2f7mqjZ/aHzAB2calWGpeCBT2rtu
paused for a full 12 seconds (no significant movement) at WP B also Marker 3. After 12 seconds, it proceeded as expected. No errors. Drone was in VLOS (although to far away to see). There was a bit of gusty winds (5-10MPH) and the drone was at 1288 feet altitude. I wonder if it just had to fight to be in the right position? What else could it be?
If so, I very much would advocate for a set of parameters that would allow to relax positional accuracy especially for missions like this where the drone does not get anywhere near an obstacle.
Comments
9 comments
Are you flying this on a Mavic? Winds aloft can be much higher than at ground level, and even at 20 mph you aren't leaving much room for the drone to compensate. The only other explanation would be that the downlink was slow, but that usually results in a Mission Stopped: Telemetry Delayed warning. If it was due to wind, the only solution is to just slow it down even further.
Yes an M2P. Agreed about the winds. I was just surprised not to see any apparent movement for a whole 12 seconds. I was just about to abort the mission... and it took off again before I acted. It was rather unnerving.
That is why I would love to be able to analyze the logs. It would help a lot!
If you connect the device to your computer, you should see a folder called SDK_logs in the application's directory. These are standard DJI GO format logs which you should be able to manually upload to Airdata.
Since I managed to upload this mission to AIRDATA here is the link: https://app.airdata.com/share/ZZjTEA
Note that at 2:48.01 to 3:58.01 the drone is effectively staying in place. It was only 10 seconds not 12 as I had determined from looking at the video.
The winds at that point were: below 5mph!! So absolutely no issue there.
Details:
03m 46.5s Joystick 15 1213.9ft 34.1ft 13.1mph 3292.9ft 84% 16.07V 4.024V 4.015V 4.017V 4.018V 0.002V 100%
03m 46.9s Joystick 15 1214.2ft 34.1ft 10.8mph 3300.2ft 84% 15.97V 4.023V 3.999V 3.976V 3.976V 0 100%
03m 47.3s Joystick 15 1213.6ft 34.1ft 6.8mph 3305.4ft 84% 15.97V 4.023V 3.999V 3.976V 3.976V 0 100%
03m 47.7s Joystick 16 1214.2ft 34.1ft 3.4mph 3308.3ft 84% 15.97V 4.023V 3.999V 3.976V 3.976V 0 100%
03m 48.1s Joystick 16 1214.6ft 34.1ft 1.1mph 3309.3ft 84% 16.30V 4.088V 4.077V 4.069V 4.063V 0.006V 100%
03m 48.5s Joystick 16 1214.9ft 34.1ft 0mph 3309.3ft 84% 16.30V 4.088V 4.077V 4.069V 4.063V 0.006V 100%
03m 48.9s Joystick 16 1214.6ft 34.1ft 0.3mph 3308.8ft 84% 16.21V 4.061V 4.052V 4.048V 4.045V 0.003V 100%
03m 49.3s Joystick 16 1214.2ft 34.1ft 0.2mph 3308.2ft 84% 16.21V 4.061V 4.052V 4.048V 4.045V 0.003V 100%
03m 49.7s Joystick 16 1214.2ft 34.1ft 0mph 3307.9ft 84% 16.21V 4.061V 4.052V 4.048V 4.045V 0.003V 100%
03m 50.1s Joystick 16 1214.2ft 34.1ft 0mph 3307.8ft 84% 16.17V 4.054V 4.043V 4.038V 4.037V 0.001V 100%
03m 50.5s Joystick 16 1214.2ft 34.1ft 0.2mph 3307.7ft 84% 16.17V 4.054V 4.043V 4.038V 4.037V 0.001V 100%
03m 50.9s Joystick 16 1213.9ft 34.1ft 0.2mph 3307.8ft 84% 16.21V 4.057V 4.051V 4.051V 4.053V 0 100%
03m 51.3s Joystick 16 1213.6ft 34.1ft 0mph 3307.9ft 84% 16.21V 4.057V 4.051V 4.051V 4.053V 0 100%
03m 51.7s Joystick 16 1213.6ft 34.1ft 0.2mph 3308.0ft 84% 16.21V 4.057V 4.051V 4.051V 4.053V 0 100%
03m 52.1s Joystick 16 1213.3ft 34.1ft 0.2mph 3308.1ft 84% 16.24V 4.066V 4.060V 4.058V 4.059V 0.001V 100%
03m 52.5s Joystick 16 1213.6ft 34.1ft 0mph 3308.3ft 84% 16.24V 4.066V 4.060V 4.058V 4.059V 0.001V 100%
03m 52.9s Joystick 16 1213.9ft 34.1ft 0mph 3308.4ft 84% 16.24V 4.066V 4.060V 4.058V 4.059V 0.001V 100%
03m 53.3s Joystick 16 1214.2ft 34.1ft 0mph 3308.5ft 84% 16.23V 4.068V 4.060V 4.053V 4.054V 0.001V 100%
03m 53.7s Joystick 16 1214.2ft 34.1ft 0mph 3308.6ft 84% 16.23V 4.068V 4.060V 4.053V 4.054V 0.001V 100%
03m 54.1s Joystick 16 1214.6ft 34.1ft 0mph 3308.6ft 84% 16.25V 4.069V 4.060V 4.059V 4.063V 0.001V 100%
03m 54.5s Joystick 16 1214.6ft 34.1ft 0mph 3308.7ft 84% 16.25V 4.069V 4.060V 4.059V 4.063V 0.001V 100%
03m 54.9s Joystick 16 1214.2ft 34.1ft 0mph 3308.7ft 84% 16.25V 4.069V 4.060V 4.059V 4.063V 0.001V 100%
03m 55.3s Joystick 16 1214.6ft 34.1ft 0mph 3308.8ft 84% 16.28V 4.076V 4.068V 4.066V 4.066V 0 100%
03m 55.7s Joystick 16 1214.6ft 34.1ft 0mph 3308.8ft 84% 16.28V 4.076V 4.068V 4.066V 4.066V 0 100%
03m 56.1s Joystick 16 1214.2ft 34.1ft 0mph 3308.8ft 84% 16.27V 4.075V 4.067V 4.064V 4.063V 0.001V 100%
03m 56.5s Joystick 16 1214.2ft 34.1ft 0mph 3308.7ft 84% 16.27V 4.075V 4.067V 4.064V 4.063V 0.001V 100%
03m 56.9s Joystick 16 1214.2ft 34.1ft 0mph 3308.7ft 84% 16.27V 4.075V 4.067V 4.064V 4.063V 0.001V 100%
03m 57.3s Joystick 16 1214.2ft 34.1ft 0mph 3308.6ft 84% 16.27V 4.076V 4.066V 4.062V 4.062V 0 100%
03m 57.7s Joystick 16 1214.2ft 34.1ft 0mph 3308.6ft 84% 16.27V 4.076V 4.066V 4.062V 4.062V 0 100%
03m 58.1s Joystick 16 1214.6ft 34.1ft 2.1mph 3309.0ft 83% 16.27V 4.076V 4.066V 4.062V 4.062V 0 100%
03m 58.5s Joystick 16 1217.2ft 34.1ft 5.6mph 3311.4ft 83% 16.25V 4.068V 4.061V 4.061V 4.063V 0 100%
03m 58.9s Joystick 16 1220.8ft 34.1ft 10.4mph 3316.0ft 83% 16.25V 4.068V 4.061V 4.061V 4.063V 0 100%
03m 59.3s Joystick 16 1225.4ft 34.1ft 13.3mph 3322.9ft 83% 15.96V 4.006V 3.989V 3.983V 3.980V 0.003V 100%
The only other thing I can think of is that the downlink was solid (receiving telemetry) but the uplink was sketchy (sending commands). Can you send a link to the updated plan so I can try flying it again?
Here is the link:
XndTZM7HdKgQ5sJd28ww
Regarding “roll” too many moving parts on a drone 😃
i differentiate using Roll for the Gimbal and Yaw for the aircraft. Since the Gimbal can be moved “sideways” independently of the aircraft yaw position I was referring to the Gimbal “center forward” position as 0 degrees “roll”. That is what appears to move off center in this mission. It is mostly visible during the last couple of legs.
The 100% value refers to communication in this case. The AC was in VLOS position less than a mile away in open country. No com errors were recorded.
Can you post the full mission plan url?
I flew the mission and it went off flawlessly. I am going to create a support ticket out of this if you want to dig deeper.
Please sign in to leave a comment.