Kloo Gee
First Officer
Flight distance : 16783757 ft
United States
Offline
|
DJI Thor Posted at 2017-11-11 03:00
Thank you for your reply, I had checked your case log, the aircraft was controlled by the pilot in GPS mode, and responded to pilot command well. Then, the flight record ended without any sign of abnormality, please refer to the pic below, we're not able to verify what happened afterwards. If you have further files could be provided, please send them back to us and we are pleased to let the engineers review. For now, considering this special situation, we've provided you with the best offer based on after-sales policy. Hope your kind understanding.[view_image]
DJI Thor,
If possible, can you please look at passing along a suggestion for your engineering team for future consideration?
I have been a part of this DJI forum for a few months and quite regularly look through people's Flight Records from DJI Go 4 when they have had an incident. Quite frequently, as in this case, the log file just ends abruptly with nothing at all to indicate anything had happened. In my opinion, the only time the Flight Record should end abruptly without any indication of a problem is if the DJI Go 4 app itself crashes.
I also see in flight logs quite frequently where this is a missing time gap in the logs followed by a message saying "Downlink Restored (after XX seconds)"
This is an example from a different person's log file (not associated with this particular thread). Note the normal entry, followed by a gap of over 11 seconds, then an entry saying the connection was restored.
835 103 1m 43s 59.33852963 17.92177735 P-GPS 156.8 47.8 0 0 0 0 64.8 19.7 59.33856437 17.92143597 21 82 11.692 0 3.897 3.897 3.897 0 0 0 3.7 -5.1 27 1024 1024 1024 1024 1024
836 114.5 1m 54.5s 59.33852902 17.92177296 P-GPS 156.5 47.7 0 0 0 0 64 19.5 59.33856437 17.92143597 20 82 11.692 0 3.897 3.897 3.897 0 0 0 2.6 -3.7 27.1 1024 1024 1024 1024 1024 Downlink Restored (after 0m 11.5s)
In my opinion, there should be at least 3 log entries in this time period. At the 1m 43s mark is a normal log entry under normal behavior. There should be an additional log entry at 1m 43.1s with null or empty values for most of the flight data with a message that the connection to the aircraft was lost. Then there should be the follow up later indicating "Downlink Restored (after XX seconds) as it does now. Also, I might suggest that if the connection isn't re-acquired within 10 seconds, it should log again that the connection to the aircraft is lost and repeat this log entry every 10 seconds for up to a certain period of time where it logs a final message saying connection was lost and the logging will end.
By adding these additional logs, it will make it much clearer to both DJI and the user what is going on. At the moment, the log just ends and neither DJI or the user knows for sure if it just ended because it became disconnect or the app just crashed or what happened.
Please pass along this request to the DJI engineering team for consideration. It seems like such a simple thing to implement and would provide considerable insight for DJI and their customers when things go awry.
Thanks much!
|
|