Phuong Do
lvl.4
Flight distance : 29800 ft
Vietnam
Offline
|
Dear all,
After give a thorough thought, and try to imagine a big picture here, I come to a theory, or better to say an assumption. I would like to emphasize this is all my theory and please believe me, I do really hope I am wrong, and hope DJI can prove me wrong. Other users can curse, use bad words on me, I do not care as long as DJI can give a satisfying answer, I will take them all.
First of all, who am I and why my background would make this thread a bit more convincing. I got my bachelor in mecha-tronics, where I have knowledge in mechanics such as motor, actuators as well as programming for embedded systems, circuits. To speak in English: I understand about both hardware and software. Furthermore, I also got master degree in project management, therefore, I do understand how you should manage stakeholders, in this case: users.
And I would like to involve in this thread the users (who are using Spark), Mr. Captain Hallmark (Who has been very helpful to us and would be un-biased in this discussion since he got many experience with DJI product) and our supportive mod DJI Thor and Natalia.
OK, to start with, we are all happy with Spark in terms of its functionalities, convenience and entertainment. However, recently, we are all aware of cases about Spark shut-down in the middle of the flight. I am aware that Mr. Hallmark did said those cases are just small number (which involved both user error and AC error), however, you must admit that there are cases with AC error, DJI did confirm "it is not pilot error" to those users (and I believe this is another way to say "it is AC error", DJI just trying to playing with words). Anyway, the threat is there, I have not yet had that issue, many of us not, but again, the threat is there.
I will analyze my theory, again, this is totally my theory, other users if you think I am right, please back me up and give pressure on DJI since we are paying for the product and we have that rights, if you think I am wrong, please feel free to prove it, and even better, please prove it by releasing the fix "right now" rather than saying "will be released soon". And please believe me, I am very happy to be wrong in this case:
1. Let assume those errors until now is software matter, coding is quite easy to debug if problems happen, since these days, codes following the object-orientation style where they have 3 characteristics: encapsulation, inheritance and polymorphism. The modules are encapsulated, for example, if you have issue with dronie code, it should be encapsulated in a module call dronie, and programmer just need to focus on debug that module, and that will not take so much time. So, if it is really software matter, DJI should be able to debug and have already released the fix already by now. I remember Mr. Hallmark also kept saying in few threads that he himself also does not understand why DJI is a bit slow in answering Spark issues. My guess is that because there is no issue in their code at all, and they do not know what to fix since the code is correct.
Again, Mr. Hallmark did say error with software is quite common by looking at Inspire, Mavic in their first days of release. However, I do believe Spark is not so much different from those model, they should have already learnt from those mistake and with the "inheritance" characteristic, they should be able to fix Spark from those mistake rather than learning the mistakes again.
Oh, and quickshots issues, don't worry, programming matter can be fixed, and they maybe fixed already. But, I think they have not yet released because they still do not know what is going on with the the falling cases and the release would not be so useful without fixing it. And as my assumption, the code overall might be already optimized and correct by learning from other previous drone model, so does not really need minor firmware to fix.And the test firmware for the remote control, come on, I think DJI can do better than that. And don't treat users as kid. First of all, the issue in the aircraft, what will a firmware for remote control do about the power matter of Spark. Secondly, if that is really a beta test, I don't think you will simply send that to any users who provide you their account like that. My assumption again is that, since users are craving for some firmware, you just basically use a current firmware, edit a little bit here and there, to calm us down. Let's ask all the tester if they see any real improvement. Because actually the current firmware is working well already, if it is the signal issue, you cannot just boost the signal range by programming, and the wifi nature, itself, is vulnerable to interference. I am actually happy with the OTG method. The matter to be concerned now is the fall-off cases.
2. Then, this will come to the second assumption that the issues in hardware. And to answer why some users have issues, some don't, I think because maybe matter will only trigger after a certain period of flying (obviously, some of us fly more than other), Or the issue in quality control during manufacturing that only some units got issue some don't, that is why only a few got issues while other not (again, please note all is my guess). And DJI cannot announce that because it would be hard to know now how many units got matter and it will create an outbreak if they accept the matter with hardware...But DJI slowness in answering the question, and quietness in answering the issue ... this assumption sounds more convincing to me.
Anyway, whoever your project manager is, I think quiet is not the way, I believe we are high importance and high influence stakeholders, you need to keep us update, not promise. only. Please again, prove me wrong and release a fix, or at least let us know what is your research so far about the fall-off cases. We do not really want to play with a ticking bomb which can fall whenever that we do not know.
I do understand Mr. Hallmark will have a say here and again, to explain that the cases until now is small and related both user's error and AC error, and do not panic. However, not yet happened doesn not mean no will never happen, especially there are cases that DJI admitted "It is not pilot error" already. So, in other words, Spark is like a timing bomb to me now...
You have different idea, please say, but again, the best way to say I am wrong is that DJI release a fix.
Ah, I also want to add that, I remember some guy in the forum said: "If you bought the drone, you have already take the risk". Sorry, I do not agree. If DJI, in there website, and their commercial Video, official says: "Please note that there is a chance that our drone will shut-down midflight, buy it at your own risk", I will agree with him. But, since DJI did not warn anything like that mean the Drone should not shutoff. And if the drone shut-off, no matter it is still in warranty or not, they have to fix / or replace at DJI's own cost. That is called ethical business.
|
|