0)
I'm not quite sure what to make of this. The aircraft GPS does appear to have worked mostly normally throughout the recorded flight. Appending the full GPS data (the black trace) to the previous plot:
View attachment 69641
The flight path late on is strange, because the aircraft was in ATTI mode with few stick inputs. I'd expect a more steady drift on the wind unless the wind conditions really were that variable.
Looking on Google Earth:
View attachment 69639
The final flight path was south, but at variable speed. The battery depletion rate indicates that the aircraft would have continued for a further 370 seconds before initiating autoland:
View attachment 69642
If the track and speed were somewhat constant that would permit an estimate of where it would have landed, but speed, in particular, was all over the place:
View attachment 69640
As a result I can't extrapolate from position or velocity. You could take a look in the vicinity of the last position shown above, but it's a long shot.
To address the question of what happened, the event stream indicates that height control failed early in the flight:
5.864 : 5141 [L-FMU/LED]action changed. set home
6.964 : 5196 [L-FMU/FSM]not near ground
7.179 : 5207 [L-FMU/FSM]near ground
13.763 : 5536 [L-RC]mode switch changed!
13.763 : 5536 [L-FLYMODE][RC] mode switch changed
13.763 : 5536 [L-FLYMODE]CTRL reset all by rc mode switch
21.983 : 5947 [L-CFG][handle_plant_gain] save(&(FMU_CFG_GET(CFG_MR_CTRL, mr_ctrl_para_cfg_t)->plant_
21.983 : 5947 [L-CTRL]Uncertainty gain adjust SUCCESS
27.484 : 6222 [L-FMU/FSM]not near ground
27.822 : 6239 [L-NS][AHRS] yaw aligned 1
31.685 : 6432 [L-FDI][CTRL]: fault on , height_ctrl_fail
31.701 : 6433 [L-RC]craft ctrl failed!!!
That was followed by a period of apparently normal flight, and then it went pear-shaped again:
155.840 : 12640 [L-WL][LOG]wl_cur_info.is_pos_available:1=>0
156.047 : 12650 [L-NS][AHRS] yaw aligned 0
157.262 : 12711 [L-WL][LOG]wl_cur_info.is_pos_available:0=>1
159.624 : 12829 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
After a couple of switches back and forth between P-GPS and ATTI the FC gave up on P mode. There are other anomalies in the logs - for example the aircraft type and other details were not properly recorded. How old was this aircraft. I'm guessing not particularly new from the flight index number, but if it was within the warranty period I'd say that you have a chance of getting DJI to replace it.
@BudWalker - any thoughts?
I think you probably used the middle .DAT. I.e. 19-04-15_08-28-21-872FLY493.DAT. This is one of those cases where the .DAT got split and it needs to be put back together. I did that by concatenating the three .DATs. It's attached.I'm not quite sure what to make of this. The aircraft GPS does appear to have worked mostly normally throughout the recorded flight. Appending the full GPS data (the black trace) to the previous plot:
View attachment 69641
The flight path late on is strange, because the aircraft was in ATTI mode with few stick inputs. I'd expect a more steady drift on the wind unless the wind conditions really were that variable.
Looking on Google Earth:
View attachment 69639
The final flight path was south, but at variable speed. The battery depletion rate indicates that the aircraft would have continued for a further 370 seconds before initiating autoland:
View attachment 69642
If the track and speed were somewhat constant that would permit an estimate of where it would have landed, but speed, in particular, was all over the place:
View attachment 69640
As a result I can't extrapolate from position or velocity. You could take a look in the vicinity of the last position shown above, but it's a long shot.
To address the question of what happened, the event stream indicates that height control failed early in the flight:
5.864 : 5141 [L-FMU/LED]action changed. set home
6.964 : 5196 [L-FMU/FSM]not near ground
7.179 : 5207 [L-FMU/FSM]near ground
13.763 : 5536 [L-RC]mode switch changed!
13.763 : 5536 [L-FLYMODE][RC] mode switch changed
13.763 : 5536 [L-FLYMODE]CTRL reset all by rc mode switch
21.983 : 5947 [L-CFG][handle_plant_gain] save(&(FMU_CFG_GET(CFG_MR_CTRL, mr_ctrl_para_cfg_t)->plant_
21.983 : 5947 [L-CTRL]Uncertainty gain adjust SUCCESS
27.484 : 6222 [L-FMU/FSM]not near ground
27.822 : 6239 [L-NS][AHRS] yaw aligned 1
31.685 : 6432 [L-FDI][CTRL]: fault on , height_ctrl_fail
31.701 : 6433 [L-RC]craft ctrl failed!!!
That was followed by a period of apparently normal flight, and then it went pear-shaped again:
155.840 : 12640 [L-WL][LOG]wl_cur_info.is_pos_available:1=>0
156.047 : 12650 [L-NS][AHRS] yaw aligned 0
157.262 : 12711 [L-WL][LOG]wl_cur_info.is_pos_available:0=>1
159.624 : 12829 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
After a couple of switches back and forth between P-GPS and ATTI the FC gave up on P mode. There are other anomalies in the logs - for example the aircraft type and other details were not properly recorded. How old was this aircraft. I'm guessing not particularly new from the flight index number, but if it was within the warranty period I'd say that you have a chance of getting DJI to replace it.
@BudWalker - any thoughts?
Neither the FAA nor DJI will give out personal information based on registration or serial number. If your aircraft (including drones) has a regular FAA "N-number" registration, owner information is publically available on the FAA website. As many posts have pointed out, putting your contact info on your drone is a good idea for improving the chances of getting a lost drone returned.
