Telemetry Delay Error & Corkscrew Orbits
IPad Mimi 5, Mavic Air 2. Very rural area with usually 15 to 21 Satellites. Never any lose of signal bars or connection.
Two questions.
1. Just an update regarding the Telemetry Delay errors. Until recent couple of months I never had this issue. Seems like several others have been bringing this issue up. It’s not a big deal with my situations since it happens at the start when executing the mission. It hovers at about 4 feet while executing the plan and sometimes will fail to start with the “Telemetry Delay” Error. If it happens All I do is wait for about 15 seconds and hit the start button again and it runs mission fine. Not sure if it’s something in the software or not. All but one time when the Error happened it was at the start of mission while it was executing while hovering. I’m only about 8 feet away with 13 to 17 Satellites. Just letting you know incase it may be fixable in the future.
2. I’ve been trying some light painting lately. Trying to run a Corkscrew Orbit at different diameters to record long exposure night shots. Three different separate short missions at 20, 30 and 40 foot diameters. I’ve ran Corkscrew Orbits before but it’s been awhile. The drones heading starts going off center. Since I’m not needing to record any video or photos on the drone in this situation it doesn’t really matter at this point. I ran these missions during the daytime to test out before actual running them at nighttime so I know it’s not a nighttime, low light situation which I don’t believe would make a difference anyway. These are fairly basic corkscrew orbits. I Slowed it down a bit but still doesn’t keep drones heading to the center all the way through the mission.
The mission preview shows it performing correctly which I understand can be different than the actual real time flight. You can see at the end of mission the drones heading goes off center. It does seem the tighter the orbit the sooner and more drastic it goes off center. Sending a screen recording of a 40’ and 20’ mission. I just started the second 20’ mission from the ending point of the 40’ but I know that won’t make a difference. I ran them separately a couple times and same issue. Possible I’m expecting too much on a very tight orbit and this is why. You can see the gimbal is trying to stay on centered but drones heading is off.
Everything else overall has been working great. I’ve seen a lot of added features/functions and changes since December of 2020. Your team is doing a great job. Keep it up and thanks.
Mike………
Comments
10 comments
Hi Jim. I forgot to mention the version I’m using. It’s the regular production version from the Apple store, 2.5.0 (164) which is obviously the same as the last Beta. I haven’t t tried any older beta versions. I noticed the new DJI SDK version 4.15 for IOS was added with this version. Just some additional info.
Thanks again, Mike…….
1. Does it happen on all missions or just larger ones?
2. This is a known issue.
August 15th was the Latest Telemetry delay error mission which was about 12 minutes. All my missions within the last few months were all less then 15 minutes. I usually keep mine just under 15 minutes so I don’t need to swap batteries. For my hobbyist purposes I usually don’t make them too long. As I stated it works if I wait about 15 seconds or so then start from it hovering position instead of restarting and it always works.
I always shutdown and restart my iPad just prior to flying with either DJI Fly or DL app so it’s fresh with no other apps running. Generally I download the missions for offline usage prior to going out to fly since it’s a WiFi only IPad just to make sure. It may not make a difference but I figure better to do it anyway.
On number 2 question I’m assuming it’s being looked into.
None of these at this point are critical for my purposes but, I figured if these are issues and aren’t reported then they can’t be looked into and fixed.
Thanks Jim.
https://app.dronelink.com/wyldwestaz/home-missions/plan/JnCe3vG8BUdxDoj1CZ8I/JSD8H0AtINujbTQqHPIa
Is there a specific version number you can say when it started happening?
Yes, and not prioritized for a fix right now.
I looked all the way back in my missions to November 2020 when I started using DL and no issues until early June and there have been several. I’m fairly sure they all have been regular Production versions. Doesn’t happen all the time and I’m only guessing about 20 to 30% of the time at start of missions while executing the plan.
Only once has it happened during a mission at about 1500 feet away but still had full Signal bars with plenty of Satellites. I waited about 15 seconds or so and then resumed mission and it completed. Maybe this info will help. Wish I could help more.
Mike…..
Hi Jim. I just remembered the first time this happened. I sent a post about it and I’m putting a link to the post I sent about 2 months ago.
Hopefully this will help. Mike…..
https://support.dronelink.com/hc/en-us/community/posts/1500001289922-Telemetry-Delayed
Thanks, that helped a lot!
Since we don't have an active 2.5.2 beta yet, I put a kernel update on 2.5.0. Can you install that version from TestFlight (under previous builds) and measure the time it takes to estimate for you on mission plans that are causing the issue. Then upgrade back to 2.5.1 and compare the times?
Glad it helped and it may be fixed. I just tried both versions as you asked. It’s the Same mission I shared with you which is about a 12 minute mission.
First I did the Beta 2.5.0 (164) and it took about 5 seconds to load the mission which is about as quick as it used to be. Once I hit the start button it took about 12 seconds while executing the mission. Seems about what it took before these issues. I tried twice with the same approximate time and no Telemetry Delay errors and the mission started.
Second I tried the Regular production version 2.5.1 (165) and it took about 10 seconds to load the mission. Once I hit the start button it took about 17 seconds while it was executing the mission. First time was no error and it started the mission. Second attempt took about the same amount of time on both loading and executing mission but I got the Telemetry Delayed error again.
Time will tell but looks like maybe you may have hit the nail on the head. I’ll stick with the Beta version for now and see how it goes. Once I see an updated regular production version I’ll switch over.
Thanks for the help and quick responses as always.
Mike……
Just remembered one other issue. It’s not a big deal for my purposes but the Distance at take-off and landings has always been off by about 50 to 60 feet. Altitude has always been at zero at take-of and really close at landing. If it can be locked into that would be great. I’m sure it’s not a priority but I figured I’d bring it up.
Thanks again.
I promoted the fix to production.
Great. 👍🏼
Please sign in to leave a comment.