Davros007
Well-Known Member
Or we can say the left rear prop is the most squashed one when stored...So, we can say, that this is problem of software, not props. Okay, let's see what happens next.
Or we can say the left rear prop is the most squashed one when stored...So, we can say, that this is problem of software, not props. Okay, let's see what happens next.
It might though. Pure speculation on my part but what if the IMU error was below the threshold triggering an IMU recalibration message. So up we go. IMU reports in-flight out of trim, FMC responds, gunning one or more motors. No effect so it increases power until motor overspeed threshold is reached and triggers the warning message.
Somewhat supportive of this scenario are the are reports of the overspeed error occuring after a prop change, if I'm not misremembering that.
It could also be just a bad case of wind upsetting the trim. There are so many permutations it's hard to nail down without so much as a system diagram, let alone the code. Could be a combination of several errors, in fact I'd bet good money on that, the swiss cheese model strikes again. As a result I'm not expecting a fix anytime soon.
Gotcha.
But we know the prop blades are likely under spec to be driven beyond some limit,TBD. Perhaps that limit is set too high (e.g. a hard-coded literal buried in the code, etc).
We know the motors are capable of it, that doesn't make it the correct thing to do if the hardware can't handle it.
Cause or effect?
I'm proposing to try it, you have nothing to lose and a lot to gain. It worked for me and I'm using the latest firmware without any issues at allBut what are you proposing the IMU has to do with this? The IMU data are what show that the problem is occurring, so that doesn't make any sense to me.
I'm not trying to argue that it's down to something else. I'm not knowledge enough in the technology and how it works to put forward a good argument. What I am proposing is that you at least try what worked for me because you have nothing to lose and lots to gain. Why not just try it and prove that it's another way that doesn't/or does fix the problem?It's been hypothesized, including by me, that the props might deform dynamically at high rotation rates, or at least be additionally deformed enough to lose their profile in flight. I replicated that, albeit not conclusively, in one of the tests. Interestingly, in the new firmware, DJI introduced the motor speed error but didn't reduce the maximum permitted motor speed. But either way - even if it is exacerbated by too high a motor speed limit in the firmware - it doesn't appear to have anything to do with the IMU.
I'm not trying to argue that it's down to something else. I'm not knowledge enough in the technology and how it works to put forward a good argument. What I am proposing is that you at least try what worked for me because you have nothing to lose and lots to gain. Why not just try it and prove that it's another way that doesn't/or does fix the problem?
Good feedback @Buzzfledderjohn - I think it's pretty obvious now that the Mavic Mini will do these crazy uncommanded descents no matter what firmware it's running. DJI's firmware 'enhancement' simply gives you a warning about motor overspeed - which - now we know why! - will give you the heads-up that you have a problem with your props.Hello all. I am new to the forum due to having my first uncontrolled decent yesterday with motor error message. I purchased my MM in December, before Christmas. I was one of the lucky ones who was able to snag a Fly More kit from my local Apple Store. I have done about 30 flights without incident until yesterday. The drone spends an equal amount of time in the case vs sitting open on my desk, so what I'm saying is, it spends a fair amount of time in the case as I do not fly that often. The big piece of evidence I will share is that I have not updated the firmware since purchase. I was on the original firmware for controller, MM and batteries and while flying yesterday I received the max motor warning message for the first time. Tried to return to landing but MM would not respond to my direction commands and then began its decent into 100 foot oaks that border my property. I got lucky as I was about to fly out over the wetlands which I have done on many occasions. It weed-wacked several groups of leaves (no branches) which absorbed the fall to soft leaf-covered ground. Not a scratch and only the smallest abrasion on 2 props.
After reading here and other forums I looked at my propellers and the back are definitely deformed. Not from the crash, they are bent in the manner consistent with what has been shown here. No IMU or GPS warnings and to reiterate, on original firmware from product launch. For me, it seems the likely culprit is prop deformation, most likely caused by storage. I rarely fly in sport mode or high wind. There was no wind yesterday. I have ordered a full set of new props and have completely updated all firmware including batteries via the desktop app as per the instructions outlined in this thread. I will report back when props are installed.
Good feedback @Buzzfledderjohn - I think it's pretty obvious now that the Mavic Mini will do these crazy uncommanded descents no matter what firmware it's running. DJI's firmware 'enhancement' simply gives you a warning about motor overspeed - which - now we know why! - will give you the heads-up that you have a problem with your props.
I also forgot to mention, after the crash I started the MM back up to make sure it was still functional and after hovering at 6 feet for a minute with no issues, I got overspeed and prop replacement warning for the left rear beeping esc after landing.
We use essential cookies to make this site work, and optional cookies to enhance your experience.