Telemetry Delayed
Native App version 2.3.0 (150) Mavic Air 2 with iPad Mini 5.
Flew a few mission on Wednesday without any issues about a mile away from house. Everything worked perfectly. Drove home and tried another mission about 20 minutes later. Started the mission and it hovers at about 3 feet. Tries executing the mission and eventually fails with the infamous “Telemetry Delayed.” Seemed like it was taking a longer time trying to execute then usual. I tried several times, restarted drone and controller. Deleted and reinstalled the App and Shut down and restarted my iPad. Still same failure another couple times. Calibrated the IMU and Compass but still same issue after about 5 or 6 attempts total. I Tried again today and same issue.
I already read about 8 or more other Forum post about Telemetry Delayed errors. None of those issue appear to be my situation. I live in a very rural area and I was literally about 6 feet from drone with 15 Satellites, full signal bars and all indicating in the green.
Not sure what else I can do on my end but I’m always open to any suggestions. No issues with the DJI Fly app if it makes any difference. I have a screen receding if wanted.
Thanks for any help.
Mike……….
Comments
24 comments
Were the missions on Wednesday in build 150? If not, can you install a previous build from TestFlight and see if 150 is indeed the issue.
Yes it was (150) I can a try Beta build (149) and let you know.
Updated: Just worked with Beta build 2.3.0 (149)
😀
Hello,
We have been having serious issues with telemtry delayed on mutliple flights. We are also have extremely long wait times where our drones just hover for minutes.
What mobile device are you using?
iPads with sim cards. Newest dronelink version.
The critical thing is which iPad (model / year).
Mine is iPad mini (5th generation) and the colleauge who had 3 "telemety delayed"s today in the field has a iPad Pro several years old (he's not sure). We can try using our phones next time. They're all quite new.
I assume you haven't had issues with this device?
I Just looked at the log. I had a "telemetry delayed" and "device running too slow" on the iPad Mini.
Also, the other thread you suggested we discuss here was a separate issue:
I mentioned the "telemtry delayed" problem but that has nothing to do with the prolonged mission execution process at the beginning of flight or after each battery change. It's the wierdest thing. I've been flying phantoms for 4 years with a couple of different mission planning apps and have never had them take off and just sit there for a minute or two before capture begins.
I disagree, I think they are related (and probably the same issue). I suspect that your mobile device is suffering from a performance issue which is manifesting itself in both of these problems. Please post links to the missions that have the errors.
Sure. A few links below:
Every mission I've conducted suffers from the extended hovering issue so posting everything won't help. These flights all had errors ranging from "telemtry delayed" to "Unable to Take Off: There was an error executing the command.(code:-1008)" to "Camera Start Capture Failed". This is on devices ranging from iPad to smart controller.
To summarize, try breaking up the missions into smaller chunks, especially if you want to run them on older devices, and attempt to isolate hardware issues by comparing the same mission on different drones. For what it's worth, we are looking at making performance optimizations to handle longer missions, but that body of work is still unprioritized on the product roadmap. The current architecture is optimized for missions that take 3 or less batteries.
By the way, your Growth account comes with email support if you would prefer to move this conversation to a private channel: support@dronelink.com.
Great feedback, Jim. Thanks! We have discussed the length of maps as a potential issue. I'll break one of the larger missions close to home into chuncks and fly with the newest iPhone or tablet I can find. I'll report back here so the findings can be shared with the community at large.
With respect to the question:
The issues do not seem to be drone specific or drone model specific. I've also noticed the Southeast region suffers less overall (but their locs are generally smaller). The Midwest fields are quite remote.
Moving forward I will use email support. Thanks, again.
Following up on this, breaking large mapping missions into smaller mapping missions drastically improved performance by eliminating "telemetry delayed" errors and painfully slow mission initiation times. I strongly encourage anyone collecting over 1000 images to break your missions into chunks. We average missions at about 2000 images with P4Pro at GSDs ranging from 0.6cm/pix to 1 cm/pix. Recent testing indicates to us that single mapping missions should not be larger than about 1000 images or 45 minutes of flight time. Our procedure moving forward will be to string several missions together to handle these large area tasks.
Glad to hear things are working better now! One other thing to remain cautious of is ambient temps and direct sunlight (as we move into summer), especially on older devices.
Understand and agree about heat on devices. However, in my situation it wasn’t hot. I had another issue the other day with my IPad Mini 5. It was 75° In my house and I went outside and it had the same failure with a very cool IPad. I upgraded to the newest Beta 2.3.1 (152) and it worked on several missions. Seems like it’s hit and miss for me lately depending on what version I was using. Whether the Regular Native App or one of the Beta’s. So far the newest Beta (152) is working. First time this failure has ever happen to me in about 6 to 7 months. If it is my iPad Mini 5 I would be surprised but anything is possible. Hopefully I’m not having an issue with it. Only about 7 months old and I only use it for my drones. Ill keep running missions and see how it goes.
Could it possibly be a DL version issue ? If not then I’ll need to figure out what it is on My end.
Thanks, Mike…
Sorry, that part was mainly directed at Will.
Anything is possible. Let me know if you see it crop up again, especially if it is in a production version (all bets are off for beta builds).
Understood Jim. Just some additional info about my situation. I’ll keep pushing forward and see if it continues or not. Everything overall has been great and this is the first issue for me in quite awhile. No worries.
Thanks Jim.
Hi Jim. Just an update and some info. I’ve Only flown a few missions lately with Beta versions and it’s working without the Telemetry Delay error. There have been many Beta updates since the first Telemetry Delay problem I had about three weeks ago. I can’t remember all the ones I used but I know two of them which worked great were Beta 2.3.1 (152) and 2.4.0 (153) I haven’t tried going back to the Production Native app to see if it would work now.
Until I see the Production Native app updated in the App Store I’ll continue to use Beta versions. As long as it’s working with Beta versions it doesn’t matter to me. Just updated to Beta 2.4.0 (155) and will be trying it in next few days. Keep up the great work. Your fantastic support is Always appreciated.
Thanks, Mike……. 👌🏻😀
I also see this behavior using the latest beta versions. I am guessing it is because of a perceived long mission though I have seen it on a 20 minute long with only 2 batteries being used. I have had to cancel my last 2 requests because I couldn't get anything completed.
I will try breaking up the mission into multiple missions but that is not always easy. It must not be only time related since the last mission had a 20 minute estimate though it did have a lot of waypoints (217).
Is there a parameter available that allows it to do all the calculations it needs without having the aircraft hover during the initial part of the flight? It wouldn't be as big of deal if I was not burning batteries the entire time.
I usually fly with a 4 year old iPad but it doesn't get much better with my iPhone 12 Pro Max.
Thanks, Morris
What is the time difference between the legacy iPad and the iPhone 12?
The iPad is from 2017 iPad Pro (10.5-inch). I get similar results with the iPhone 12 where I got the telemetry delayed and had to cancel the flight. The mission was only supposed to take 20 minutes but after spending 30-45 minutes trying to get it going, I had to quit.
How much does spotty cell coverage impact this initial flight delay where it hovers for a long time before starting the actual mission? I don't know what it is doing during this delay so not sure if there is a lot of network traffic.
None at all, it is pre-computing most of the necessary calculations to perform the virtual stick commands. It front-loads it as an optimization to support slower devices (which would otherwise get a bunch of disengagements with Device Running Too Slow error messages).
Again, what is the time difference between your iPad and the iPhone 12.
I misunderstood your question about time. I didn't measure the time difference. I will have to do some testing to get you those numbers. Thanks.
Please sign in to leave a comment.