Third flight of new Mavic Mini. Flight starts out fine with GPS warning, but warning clears after a few seconds. When yawing at about 0:25 drone starts to loose altitude and controls behave in reverse. Video and connection to controller cuts out at 29secs in. Drone continues on path crashing into trees. Recovered in very bad shape about 2-300m from where it lost connection. You can see from flight logs that it thinks it is flying backwards. Flight logs uploaded.
Here is the video captured from device: https://youtu.be/CNQeuAabFiI
Flight logs uploaded to DJI, here is a video of replay: https://youtu.be/r_oot5_JwCg
I have returned the unit to dealer. There is no stock in the country so I won't be playing with this toy at Christmas
Speed reported @ 72 km/h.
Could it reach that speed in still air?
I guess that since as far as I know, speed is only derived from changes in gps readings, and with gps intermittent/lost , it could report any speed imaginable.
Bright Spark Posted at 12-3 04:10
Speed reported @ 72 km/h.
Could it reach that speed in still air?
I guess that since as far as I know, speed is only derived from changes in gps readings, and with gps intermittent/lost , it could report any speed imaginable.
Hiya,
Afaik speed is calculated from the inertia changes in the x and y axis., not from GPS readings.
Fly in your house with no GPS reception (OPTI mode) and notice that speed is still indicating.
If IMU gets the correct data and does a good calculation the result is equal to GPS speed calculation.
GPS data is almost always available; even in a forced into ATTI mode (due to other than gps errors) .When GPS speed and XY speed differs a lot than thats`s an indication of some errors in the drone. With errors the speed indication in the GoApp is not always correct.
Thanks for info. I gather airliners use inertia changes as one method of determining speed nd poition . No doubt those much more knowledgable than me will know.
Could it also be found by ground mapping?
I can't remember if tello gives speed - no gps anyway.
If a mm can do say 50 km/hr in still air, then to get 70 groundspeed on the clock it would be in a 20 kh tail wind.
But if it turns round, then ground speed becomes 30kh.,
implying inertial measurement can account for ( varying) windspeed.
Not saying it can't, but find it interesting!
Hello and good day gwaja. I am sorry to read and to know what happened to your DJI Mavic Mini. Since this unfortunate incident happened. I would highly recommend to contact our DJI support team at https://www.dji.com/support?site=brandsite&from=nav for us to be able to assist you further with regards to this issue and to analyze what happened on that said flight. We have the team who would do their best to find out the reason of the said incident and then the corresponding resolution would be provided. Again I am sorry and thank for your support.
Afaik speed is calculated from the inertia changes in the x and y axis., not from GPS readings.
I'm not sure that's correct. Inertia changes only measure changes in acceleration, not speed. Imagine being in a plane flying at a constant 600 km/h. Providing there are no changes to acceleration/deceleration, there is nothing to affect the gyro meters. You certainly wouldn't get a reading of 600 km/h.
This is interesting.
There must have been inertia reading when it accelerated to 600. So it would know the status quo and that speed.
And a constant headwind/tailwind on take off would, and could also be accounted for.
Any susequent change in wind would give a reading too, albeit small.
I'm more or less guessing of course.
I believe these incredibly sensitive instruments are the last resort for navigation in the air when all else has failed!
Sorry to hear of your experience. I also had a fly away where mine got up to about 65mph (104km/h) before it eventually recovered itself.
I'd be interested in checking out your logs to see if there is anything useful in there to help understand what happened.
Can you upload the flight record from your phone to the following site? Directions are on the page, of course substitute DJI Fly in place of Go 4 in the directions.
I was doing a short line of sight flight. It didn't require GPS. In any case. It said 7 sats at take off, but the error cleared before I got over the water so I assumed all was ok. I think the little thing freaked out when it could not reconcile the GPS and IMU data.
gwaja Posted at 12-3 10:56
Conditions were perfect and there was almost no wind. Cannot confirm 72km/h, but when it decided to fly backwards at top speed it was going very fast.
Bright Spark Posted at 12-3 04:10
Speed reported @ 72 km/h.
Could it reach that speed in still air?
I guess that since as far as I know, speed is only derived from changes in gps readings, and with gps intermittent/lost , it could report any speed imaginable.
I concur with your reasoning. It looks like a bogus speed calculation due to an anonymous GPS data point.
gwaja Posted at 12-3 10:58
There is a video showing stick position. Controls show forward and up, it is going backwards hard and loosing altitude.
Wondering if there is anything in drone's Log file around 0:25 that might give a clue as to why.
Phantomhelp provides a human readable version of log file in two forms; basic and additional.
DJI has way to look at far more.
Yawing at 25 seconds is not seen in the flightlog, craft heading remains at approx. 221 degrees.
Yaw input starts at 14 secs (about 27% right max) upto 34 seconds. Guess your drone did actually yaws right but this is not seen in the log. Only the last few seconds in that period YAW heading is changing. If you flew a 180 turn right (guess you did so) than the mini still thinks that its heading 221.Ofcourse after that all goes wrong!
Flight started in OPTI mode, after 17 seconds in Cinematic mode.
There is no distance recorded in the file.
HomePoint has not been recorded, so satellite number and reception too weak for that.
Could have had impact on drone positioning too.
Not sure what happend, but start of the flight wasn`t oke. Why the heading data remains steady at 221 and not following your yawing; good question for DJI to answer.
EDIT see post #33 above is wrong as the OP did use mode2.
cheers
JJB
Mode 2. 00:25 is in the video footage (https://youtu.be/CNQeuAabFiI) where everything starts to go wrong. You can see for the first 20secs I am flying happily straight with no yaw on the sticks. Does your program tell when camera is started? I think it is somewhere around 12secs in the logs.
gwaja Posted at 12-4 06:29
Mode 2. 00:25 is in the video footage () where everything starts to go wrong. You can see for the first 20secs I am flying happily straight with no yaw on the sticks. Does your program tell when camera is started? I think it is somewhere around 12secs in the logs.
Hi gwaja,
So my chart is wrong as i thought you didn`t use mode2.
Thanks to your video i spot the time in the log where is goes wrong.
Your started video at 11.4secs in flight, plus 20 seconds...i see now what imo happend; at this point VPS height stopped indicating, before that steady 3.3 meters.
Guess your were flying that low height in OPTI mode, not a GPS mode (8 sats + 3 for reception), curious to know what mode you see in the app, can you replay the flight in the FlyApp as in the GoApp ?
Once missing the VPS bottem sensor Mini cannot hold its ground reference, any RC input will speed up the Mini. (as in ATTI mode)In CineSmooth 100% fwd stick gives low speed, but 100% fwd stick in a non GPS mode gives full speed. (same for all 4 direction inputs)
Red thin line under the black flight mode line is the video recording line.
So starting to fly in OPTI mode wasn`t a good idea!
So my chart is wrong as i thought you didn`t use mode2.
Here is the video of roughly what I saw on the controller. It started off with a GPS warning, but that cleared after getting out from under the trees and just said "In Flight". It was in cinematic mode which is effectively slow and steady mode.
Apart from the GPS warning at the start which cleared, there was no indication that anything was wrong until it started behaving badly, then comms cut off.
Also video cut off way before the crash which is weird.
This is my first drone. My third test flight was today. When I got above 50m it suddenly flew away and crashed into the trees. I think it's the same error that's described here. I have no idea how to check logs or what that data would mean anyway. Any advice for a beginner? Thank you.
djiuser_Yf90lf4FnfaI Posted at 12-6 20:26
This is my first drone. My third test flight was today. When I got above 50m it suddenly flew away and crashed into the trees. I think it's the same error that's described here. I have no idea how to check logs or what that data would mean anyway. Any advice for a beginner? Thank you.
I have the same issue I took my mavic mini on an open field and the drone lost reception and it flew away over 1.5 km away from me with no attempt to return home. DJi looked at my records and told me it was my fault so offered a 15% discount on a new drone which I found poor. I have flown over 250km with dji drones and this is the first time any of my drones take off within eye range from me. They are blaming it on the winds. Please people do not buy this drone dji are aware there is a problem and do nothing about it. I have raised a complaint and this will be shared all over my social media. Why sell a drone and advertise it as an outdoor one and then have the guts to say it was the pilots fault. Even if it was my fault the RH function should have helped the drone come back as a home pont was set. It is ridiculous and I am utterly disappointed with DJI. They are about to lose many customers over this drone.
Patron14 Posted at 12-18 05:31
I have the same issue I took my mavic mini on an open field and the drone lost reception and it flew away over 1.5 km away from me with no attempt to return home. DJi looked at my records and told me it was my fault so offered a 15% discount on a new drone which I found poor. I have flown over 250km with dji drones and this is the first time any of my drones take off within eye range from me. They are blaming it on the winds. Please people do not buy this drone dji are aware there is a problem and do nothing about it. I have raised a complaint and this will be shared all over my social media. Why sell a drone and advertise it as an outdoor one and then have the guts to say it was the pilots fault. Even if it was my fault the RH function should have helped the drone come back as a home pont was set. It is ridiculous and I am utterly disappointed with DJI. They are about to lose many customers over this drone.
Hello and sorry for your issue.
Have you posted fly logs here in the forum?
Some users can really look at the info and tell you exactly what happened.
Did you recover it?
Again I hope this issue is solved for you asap.
Your mini may I suppose be one of the first, if not the first, really to be at fault, but it's ridiculous to suggest thousands have failed when a brief reading of initial difficulties reported here have turned out, upon examination, to be completely pilot error.
This happened to me today. I had the drone for two days. Had a nice sunset so went down to the beach to fly, had a perfect line of sight no houses in front of me. It first had no GPS. Then it had GPS the home point was updated so I raised it to about 45 meters recorded for about 15 seconds then the drone shot over behind me in reverse and went into a cliff with dense bush. No chance of recovery, It went flat out and responded to nothing when I tried to control it. I have lodged a job with them so see what happens. Just gutted!
Cannot paste txt files here, but here is a here to dropbox.
https://www.dropbox.com/s/675glxjmejirsxv/DJIFlightRecord_2019-11-29_%5B12-25-14%5D.txt?dl=0