Deucalion
lvl.4
Flight distance : 103091 ft
United States
Offline
|
thE29 Posted at 4-27 02:12
Hard to say if people are just lying to prove their point or if they are telling the truth..
I mean look at some answers "I went back to previous firmware and error is gone". Yeah, well this function didnt exist at the previous firmware..
The rear and front props have different geometries, look at the angles they make with the ground. That is probably why the issue shows up with the rear first. That also explains why switching front and rear props has worked as well. Why the left rear more, I don't know.
The main reason for the 2 steps of making sure the FW is upgraded and then if that doesn't work then replace the props, is that it fixes the error. We are not saying we know WHY, just that it fixes it, usually. That came just from watching a lot of users fix the issue. Those are the steps they took. Obviously, the DJI Assistant step should go first and replacing the props second.
There is no evidence (in all of the user cases) that storing the drone in the case caused this. Whatever the issue is with the props, they came that way from the factory.
I do believe that there is something marginally different with a handful of drones, probably with the props. Prior to this FW update, a handful of drones did exhibit the behavior of having max power errors and a handful of those did have uncommanded descents. All the rest had neither symptom. I do believe that this FW update was supposed to address this issue by not doing an uncommanded descent and instead warning the user of the troublesome prop(s). But then the update was botched so much, probably because it involved the drone, the RC and the batteries all at once, that a whole lot of users got the prop errors.
That last paragraph is all conjecture. |
|