Hey Sarge - Thanks for circling. DJI have gone silent on me - especially after I detailed the KML files and the GPS showed the flight went from Australia to China to Africa and then back to Australia.Any updates on what the final outcome was?
I don't think it has gotten that far up honestly. I had a supervisor call at one point. But I've consistently asked for escalation and received no significant response. Any recommends on position title I should ask for?I'm rather baffled by their stance on this one - how far up the chain has this been escalated?
Aa°°°°AaazaaaaAO1&
I don't think it has gotten that far up honestly. I had a supervisor call at one point. But I've consistently asked for escalation and received no significant response. Any recommends on position title I should ask for?
sar104 is the man when it comes to looking at data, if he is baffled than I can bet dji is also. I do agree with him though that you should try to post on the dji forums and I would definitely be pushing the issue with this. Btw...off topic but your user name also belongs to one of my favorite drummers of all time. sar, do you think this could be some kind of weird gps issue? Same as when my phone tell's me I'm in Seattle when I'm actually in Portland.
I think that @BudWalker summed it up in post #23. It's an unusual case but the direct cause of the crash seems clear - the FC confused simulator mode with flight mode. I don't see any GPS problem - the GPS data all look fine.
Any reason you think the GPS shows coordinates: N 22º 32' 15", E 114º 57' 13" in the log? Along with others that place it near Africa etc...? Any thoughts on why the KML data shows the wild trip from Brisbane to China?
Or am I missing something here?
Update:
I have been able to come to a resolution with DJI and a replacement is being sent in the coming days - of which I am incredibly grateful.
We still did not come to a wider conclusion on the situation and there are still plenty of questions as to why this occurred. While this matter is closed, I am still curious as to why this happened and hope DJI continue to look into it.
Yes, they are. Which is what I initially asked for - now... what's the overall cost that I've expended with my time on this? It'd likely be comparable to paying for repair - but it was the principle of the matter with this clear glitch.So they are replacing it free of charge - yes?
Yes, they are. Which is what I initially asked for - now... what's the overall cost that I've expended with my time on this? It'd likely be comparable to paying for repair - but it was the principle of the matter with this clear glitch.
I'm just hoping they will truly review and determine the issue, rather than insisting the AC never even took off.
Glad they eventually came to the conclusion it was their fault. Amazing it took them so long, as they anticipated they would remove the useless flight simulator recently, meaning they might have already come to the conclusion that it was buggy (or buggier than the rest of their software).Yes, they are. Which is what I initially asked for - now... what's the overall cost that I've expended with my time on this? It'd likely be comparable to paying for repair - but it was the principle of the matter with this clear glitch.
I'm just hoping they will truly review and determine the issue, rather than insisting the AC never even took off.
Outstanding!!! That is great news!! I do agree that a definitive outcome on what caused it would be nice to get also.Update:
I have been able to come to a resolution with DJI and a replacement is being sent in the coming days - of which I am incredibly grateful.
We still did not come to a wider conclusion on the situation and there are still plenty of questions as to why this occurred. While this matter is closed, I am still curious as to why this happened and hope DJI continue to look into it.
We use essential cookies to make this site work, and optional cookies to enhance your experience.