ABeardedItalian
Second Officer
Flight distance : 1063107 ft
United States
Offline
|
It isn't incorrect. It is just a 4th observation that deepens the mystery. People have been replacing props with new props and the error goes away. Not switching. Replacing.
Explain to me how switching isn't the same as replacing? You replace the bad props with the props from a good motor, if the error doesn't come back then replacing the props fixed the issue. What was the issue then if the bad props on a new motor don't trigger the error? Were the original error'ing props actually bad or is this a fw bug?
They have been working on this patch since the last patch, and testing it a lot.
lol that's funny, were the test dummies here. Half the people here wait for the other half to do testing before they update because issues like these are found and were never addressed by DJI. They could of but a disclaimer, new update might cause X error because Y reason. Do they, will they, nahhh.
Oh, one other thing, MASS ISSUE is overused here.
I've been on this forum since December, you think my "mass" claim is exaggerated some how? There have been over 50 lost mini threads since it's release, the majority of those from uncommanded descents. I myself have used your very argument against users here and I'll repeat it for you, this is DJI's official forum. It's a focused group of users reporting problems, when looking at the forums the mini looks like a failure but when you consider that the traffic here is maybe 1.5% of the MM owners you understand these issues aren't as pandemic as people would like to make out.
Posting fake news is really not the best way to get the right people looking at your problem.
What fake news is that? That from reading the forums anyone with half a brain can see that there's an issue with props, be it a bad batch, storing issues, something but DJI felt the need to address it with the latest fw. DJI hasn't come out and publicly said "Were aware of these recent issues and have released a fix in an attempt tt solve it." That would mean they have claimed responsibility for knowing about an issue, it's the same as GM/FORD,DODGE, they know about issues that need to be recalled but when you can silently "Patch" it without recalling the entire fleet they will do that a hundred times then own there screw up and do a recall. IF DJI really understands that they have prop issues they would issues ALL MAVIC MINI owners FREE prop replacements. Have they? Will they?
2. Possibly, the performance envelope is even narrower with the MM. Really, no. Take a look back a week or two in the forums, there is a nice thread that talks about the narrow performance of the mavic mini.
3. The original firmware (prior to this release) drastically auto descended at some point when there were too many max power errors. Are you a DJI Engineer? How do you know those drops were related to those errors and not props?
4. This release (hopefully) does not auto descend, but informs the user which prop(s) are causing the max power errors. We've been hoping for DJI to address these issues since fw 1.03.
@120ccpm Ty for repeating the same thing without being attacked.
DJI is not telling us whether there's a batch of bad props around or whether props eventually lose their shape if stored improperly (the rear props are obviously more at risk, as they end up under the AC when the arms are folded in), but this new addition to the firmware really seems to give us a early warning that something is not right.
There are reports of uncommanded descents, and the theory is that they could be related to props. DJI never acknowledged the problem, but here on the forum they always recommended to replace the props in those situations.
Like I said in my original conspiracy theory, DJI could have the detection rate at 90% to force the hand of its users to change props knowing that there's an issue and if everyone as a whole has to change props then the likely hood of more uncommanded descents could go down. Why do a recall or give customers replacement props, lets not say anything and see if we can't sweep this under the rug with a fw patch. That is the part I don't like, they have everyone's flight logs and the internal information exists that they developed this error to catch under performing props, THEY KNOW SOMETHING IS A MISS AND ARE NOT SAYING ANYTHING. This is what makes them shady, don't hide from it, own it. It helps improve the companies public image by acknowledging the issue and taking a stance to resolve it properly.
|
|