EdisonW1979
First Officer
Flight distance : 1535679 ft
Canada
Offline
|
DJI Susan Posted at 2018-7-13 01:40
Hi Edison, thanks for bringing this to attention. Firstly, we sincerely apologize for the late response. I have a quick look at all posts you mentioned and understand your concerns about the current firmware, but there are some points need to be clarified and confirmed:
1. Motor Current Error: This is a known error and the misinformation will not affect the normal flight, our engineers will fix it in the next update.
2. Transmission issue: The transmission issue might appear in various conditions. Not sure it is the firmware issue, so we suggest doing troubleshooting to narrow down the scope and see whether it can be fixed remotely. We appreciate your cooperation on this.
Hello Susan,
I'm glad that someone from DJI has FINALLY acknowledged this thread after all the weeks it has been up. However I would like some further clarifications on your posting:
- "Motor Current Error: This is a known error and the misinformation will not affect the normal flight, our engineers will fix it in the next update" <- This is not the case, as some MA pilots have reported loss of control, or drone instability (the issue I experienced) when this message appears during certain flight scenarios, and DJI has been told this repeatedly, but just puts out this canned response to concerns. When GO 4 was at 4.2.16 on iOS, DJI stated this was an issue with the app and that they're working on a fix; we're now at 4.2.22 on iOS, and I just got this error AGAIN the other day, so this REMAINS an issue!
- "Transmission issue: The transmission issue might appear in various conditions. Not sure it is the firmware issue, so we suggest doing troubleshooting to narrow down the scope and see whether it can be fixed remotely. We appreciate your cooperation on this." <- Again, another DJI admin here as put out a VERY different response, stating this issue was identified by DJI engineers as a known bug, and it was supposed to be fixed by 4.2.20, and then later acknowledged publicly that it was still not fixed by 4.2.22. If this is true, why are you putting out a statement which will cause pilots just to waste more of their time doing pointless troubleshooting when DJI already knows this is a GO 4 app issue?
- "For the raw and drift issue, we're collecting the samples videos and corresponding flight logs for further analysis. Also, some issues you mentioned appeared before this firmware, I'm afraid that it is a little misguided for collecting here for attention." <- I personally find this statement an attempt to quell public outcry about the yaw and drift issue, as they are VERY much a concern to those pilots here who are affected by it, and making a statement such as this infers DJI doesn't want negative publicity on a bug, which you just admitted, goes beyond 0400 firmware, which if true, is TOTALLY UNACCEPTABLE! It has been 2 months since 0400's release, and yet you've just admitted a potentially serious flaw has gone un-fixed for even more time than that???
And what about the statements put out by DJI employee Ken Booth, referenced by forum user Brantel on the linked thread below in posts #205 and #239:
https://forum.dji.com/forum.php?mod=viewthread&tid=147912&extra=page%3D1%26filter%3Dtypeid%26typeid%3D534&page=6
Are the DJI admins serving this forum not made aware of these official statements by representatives / engineers of DJI, or are trying to deny those statements were in fact official?
I think after so many months of pilots having to deal with NO action or any real fixes from DJI on this matter, and only receiving scripted responses from DJI staff, we deserve a DETAILED explanation of what is going on, what DJI is doing to fix it, and when we can expect the much needed firmware update!
I await your detailed response.
|
|