djiuser_jJFRKC7baMLo
Captain
Flight distance : 27713973 ft
Germany
Offline
|
Perhaps one of the users can give a hint or a moderator of this forum forwards the problems to the software development ... I tried to clarify these issues with DJI Support (German), but their answers seem to have been given to me without any expert knowledge at the moment.
First, very briefly (exact analysis was only at home by evaluating the flight data):
Our Mavic Mini crashed after a short flight time (approx. 4m 50s) and a last known charge level of 80%. Distance between starting point (Pstart) and crash point (Pcrash) approx. 430m (1.400 ft).
Phew!
Now the "Find My Drone" is called up immediately and the position (Pdrone) is shown (as an icon on the map and - in white letters - at the bottom left of the smartphone display):
What's this?
Supposedly another 1,400m (4,560 ft) distance to the Mavic Mini, between Pcrash and Pdrone.
OK. Unfortunately, this position (Pdrone) is on the other side of the (wide) river and we had to drive about 40km (about 25 miles) because we needed a bridge.
Unfortunately the Mavic Mini could not be found. The terrain at this indicated position (Pdrone) was very "simple", but there was also no radio connection to the Mavic Mini.
We searched for about 3 hours, but then we drove home to further consider.
With the help of the website "AIRDATA" came insights that did not want to match the displays of the Fly app:
There is no indication in the flight data of the position shown in the "Find My Drone" function (Pdrone)!
All the data sent from the Mavic Mini to the RC are saved in the flight data, right?
How can the Fly app display such a position (Pdrone) that was not sent by the Mavic Mini at all ???
That is the crucial point for me!
Is there a "big" bug in the RC software, along with the Fly app?
At the time of this incident, the software was the current one: 1.0.4 (both for the Mavic Mini, for all batteries, for the Android smartphone, and for the RC, of course).
The next day the weather was not so good. Because it had to be assumed that the battery had been drained in the meantime, i.e. no radio connection to the crashed Mavic Mini could be established, a new search no longer made sense.
The terrain at the crash site is much more difficult and without the help of the Mavic Mini (by beeping and blinking) the search now seemed hopeless ...
The German customer service of DJI, which received all the data (flight data in particular), confirmed the crash at position Pcrash, but said in summary (quote):
"... the chief engineer temporarily determined that the aircraft's GPS module could be damaged by the aircraft accident, and for this reason transferred the wrong GPS coordinate back to the app."
With little attention you could "believe" this, but then this position - caused by a defective GPS module - would have to be stored in the flight data, right?
Any attempt by me to contact DJI's software developers and discuss the issue with them will be blocked.
Too bad, very sad!
One should think that any concrete reference to software problems is gratefully received ...
Perhaps it will now be possible to contact the developers via this forum and provide them with all the information (data) again so that they can find out the reason for these errors and remedy them.
I would be very happy and grateful if this path could lead to success here ...
Frank
|
|