Lost connection and crashed

[Thomas B]

How is your experience with DJI Care how fast can they replace the AC?

I had an encounter with a tree branch in an early flight. From the time I contacted DJI to use my DJIRefresh until an apparently new drone, with SN already registered to me, arrived at my door was 8 days counting the weekend. No hassles and it saved me enough money to pay for the DJICare on my other 2drones.

 

[Waliaf]

The description of your incident is confusing.
Did the drone fly off somewhere and crash into an obstacle, or did it just stop flying and fall from the sky?

If it lost signal while still powered, it could only have continued flying for three seconds before RTH would initiate.

I suspect that it just stopped flying because either the battery was dislodged or the drone just shut down.
If that's the case, you would have found it close to the last point in the recorded flight data.
And if so, the disconnected message was because the drone had lost power.
That would also explain why it did not come back.

More information is required to be able to be certain of any more.

The drone did not fall out of the sky, on the RC I lost the connection, in my situation, the AC should have hovered until the connection was back, this worked before for me, but this time instead of hovering, the AC did fly away and lost the hight and crashed somewhere to a building 300m from the home point. attached the log files hope this gives more info so that we know what happened.

 

[Waliaf]

I had an encounter with a tree branch in an early flight. From the time I contacted DJI to use my DJIRefresh until an apparently new drone, with SN already registered to me, arrived at my door was 8 days counting the weekend. No hassles and it saved me enough money to pay for the DJI Care on my other 2drones.

should I directly go for DJI Care or let it first be investigated by DJ to see if it can be covered by Warranty... what happens to DJI care if the drone is replaced under Warranty? Do you need to buy new DJI care?

 

[Thomas B]

should I directly go for DJI Care or let it first be investigated by DJ to see if it can be covered by Warranty... what happens to DJI care if the drone is replaced under Warranty? Do you need to buy new DJI care?

DJICare covers 2 loss events. If you use warranty DJIC is unused.

 

[runeOfRune]

I took a brief look at the logs aaand I believe that aircraft had it coming anyway... multiple IMU convergence errors, battery errors, sensor errors. What the hell am I looking at? Is this even a real log?

Okay, this one highlight out of all that mess is hilarious:

[L-BATTERY][ERROR] BATTERY_STATE_ABSENT

Those logs, I don't even.

 

[Waliaf]

I took a brief look at the logs aaand I believe that aircraft had it coming anyway... multiple IMU convergence errors, battery errors, sensor errors. What the hell am I looking at? Is this even a real log?

Okay, this one highlight out of all that mess is hilarious:


Those logs, I don't even.

apparently, some of them are the data from after crash, my battery is broken but still working, sensors are damaged (left and under) and I am getting an error now when I run the drone one.

FLY087.DAT is from 21.34 so this should give some useable information?

 

[runeOfRune]

Your usable flight data ends abruptly 304 seconds into flight 89. Prior to the crash, even during your previous successful flight, your aircraft experienced multiple IMU convergence errors, multiple instances of horizontal and vertical drift, multiple disconnects, multiple vision system errors, multiple ultrasonic system errors, eram write errors (???), battery API errors, accelerometer errors... Unless I'm reading the logs wrong, I have never seen anything like this.

As to the actual reason of the crash, I cannot help you as the logs did not record the final event. But I guess some of those listed had at least a partial impact.

Where did you get that aircraft from...? What did you do to it?

 

[Meta4]

FLY087.DAT is from 21.34 so this should give some useable information?

I don't do .dat files but if you can post the .txt file from the app flight records, I might be able to make some sense from that.

 

[runeOfRune]

@Meta4 I mean, well, you can, but just look at this...

231.724 : 24471 [L-NS][ext ns] too LATE! delay_idx:21 imu_local:491697 fusion:491645
231.729 : 24471 [L-NS][comm] ext ns disconnect2
231.775 : 24474 [L-FDI]NS(0) FUSION(1): fault on , disconnect
231.775 : 24474 [L-IMU]

state: drift
232.115 : 24491 [L-FMU/LED]action changed. no atti:not converged(2)​

252.737 : 25524 [L-NS][AHRS] Bad sample tick measure or recapture signal: 21.080000
415.341 : 33670 [L-NS][AHRS] Bad sample tick measure or recapture signal: 0.010000
495.849 : 37704 [L-NS][AHRS] Bad sample tick measure or recapture signal: 13.580000

471.395 : 36479 [L-FDI]NS(0) VO(0): fault on, height_consist
471.415 : 36480 [L-FDI]fatal error: no ns with level < 4 !!!
472.433 : 36531 [L-FMU/LED]action changed. imu error:ns_abnormal(3)

525.686 : 39199 [L-RC]craft ctrl failed!!!
527.702 : 39300 [L-RC]craft ctrl failed!!!
529.718 : 39401 [L-RC]craft ctrl failed!!!
531.734 : 39502 [L-RC]craft ctrl failed!!!
533.750 : 39603 [L-RC]craft ctrl failed!!!

300.477 : 18475 [L-NS][ext ns] too LATE! delay_idx:20 imu_local:371784 fusion:371734
300.482 : 18476 [L-NS][comm] ext ns disconnect2
300.537 : 18479 [L-FDI]NS(0) FUSION(1): fault on , disconnect
300.537 : 18479 [L-FDI]ns req:fdi,1to0,reason:imu.disconnect,result:succeed
300.537 : 18479 [L-FDI][SWITCH] req:2,1->0,result:6,serr:1000617,derr:5
300.537 : 18479 [L-IMU]

state: drift
300.677 : 18486 [L-FDI]NS(0) VO(0): fault on, disconnect
300.730 : {IRQ153}INFO:AP reboot!!!||
300.797 : 18492 [L-FDI]ULTRASONIC(0): fault on, disconnect
​

302.174 : 18561 [L-FMU/LED]action changed. no atti:not converged(2)
308.522 : 18879 [L-GEO][nfz_flight_monitor]flight connect changed! 1 -> 0|
308.522 : 18879 [L-GEO][set_flight_err]err:NONE=>FLIGHT_ERR|
308.542 : 18880 [L-GEO][update_fc_db_handle]update fc db num:0|
309.919 : 18949 [L-GEO][nfz_flight_monitor]flight connect changed! 0 -> 1|
309.919 : 18949 [L-GEO][clr_flight_err]clear err:FLIGHT_ERR|

573.610 : 32160 [L-IMU]

state: drift
573.610 : 32160 [L-FMU/DM]Busy Device Changed. Type:imu1_ext_ns, <ID:7 idx:0-->ID:15 idx:1>, change ti
574.409 : 32200 [L-FDI]ns switch app warning!
574.628 : 32211 [L-IMU]

state: fixed
578.700 : 32415 [L-BATTERY]battery_device_info_process
578.702 : 32415 [L-BATTERY]battery app version: 2.74.7.12
592.863 : {task_e}INFO:i2c3 core recovery||
592.863 : 33124 [L-BATTERY][ERROR] smbus_read CMD_POWER_STATE error||​

2.209 : 5486 [L-N_MIS]req abort all for assit takeoff finished
3.353 : 5544 [L-FMU/MOTOR]safe_near_grd:false
3.393 : 5546 [L-FMU/LED]action changed. set home(0)
3.953 : 5574 [L-VISION][VIO]receive vio data befor current ts||
4.271 : 5590 [L-FDI]NS(0) GPS(0): fault on , conformity

...​

 

[RayOZ]

I need the AC by end of July I am not sure how fast DJ is, so should I go direct for the DJI Care or not ? :/

It depends. If they can diagnose quickly, they can send you another one pretty quickly. Also, depends on where it's being sent. Do it soon, the longer the wait the longer it'll take.
If there's a lot of error messages, it could be a covered under warranty and DJI will send you a replacement for free. They will update the DJI Care Refresh SN, so you don't have to do anything.

 

[Waliaf]

Your usable flight data ends abruptly 304 seconds into flight 89. Prior to the crash, even during your previous successful flight, your aircraft experienced multiple IMU convergence errors, multiple instances of horizontal and vertical drift, multiple disconnects, multiple vision system errors, multiple ultrasonic system errors, eram write errors (???), battery API errors, accelerometer errors... Unless I'm reading the logs wrong, I have never seen anything like this.

As to the actual reason of the crash, I cannot help you as the logs did not record the final event. But I guess some of those listed had at least a partial impact.

Where did you get that aircraft from...? What did you do to it?

I got it from a well-known shop in the Netherlands, apparently I have misused the poor drone :/ attached the complete flight record map, hope this gives more insights?

FlightRecord.zip

 

[Waliaf]

I don't do .dat files but if you can post the .txt file from the app flight records, I might be able to make some sense from that.

I have here the full txt files. the crash happened yesterday between 21.00 - 22.00 CET.


FlightRecordTxT.zip

 

[Meta4]

I have here the full txt files. the crash happened yesterday between 21.00 - 22.00 CET.

There are lots of files going back a month in that zip archive but none of them make any sense.
There are nine from within a 17 minute period on the last day.
They are just full of garbage numbers - even the older ones.

Try this for just the most recent flight:
Go to DJI Flight Log Viewer | Phantom Help
Follow the instructions there to upload your flight record from your phone or tablet.
That will give you a detailed report of the flight.
Come back and post a link to the report it gives you.

 

[sar104]

I'm not really sure what happened here. The txt file is DJIFlightRecord_2019-06-09_[22-17-01].txt and the DAT file is FLY089.DAT.



The DAT log event stream contains a number of errors at the end of the flight. My guess would be that the FC crashed.

296.030 : 20207 [L-NS][AHRS] Bad sample tick measure or recapture signal: 11.085000
296.030 : 20207 [L-NS][AHRS] connect vo :1
296.046 : 20208 [L-FDI]NS(0) VO(0): fault off, disconnect
299.014 : 20356 [L-NS][comm] ext ns connect2
299.020 : 20357 [L-FDI]NS(0) FUSION(1): fault off, disconnect
299.503 : 20381 [L-NS][comm] ext ns disconnect2
299.559 : 20384 [L-FDI]NS(0) FUSION(1): fault on , disconnect
299.598 : 20385 [L-NS][AHRS] connect us :0
299.739 : 20393 [L-FDI]NS(0) VO(0): fault on, disconnect
299.839 : 20398 [L-FDI]ULTRASONIC(0): fault on, disconnect
299.971 : {IRQ153}INFO:AP reboot!!!||
300.376 : 20424 [L-NS][AHRS] connect vo :0
300.937 : 20453 [L-FDI]NS(0) TOF(0): fault on, disconnect
303.193 : {IRQ153}INFO:AP reboot!!!||

 

[RayOZ]

Someone pointing some sort of microwave gun at the drone to bring it down?
Looking at the map, it doesn't look like a good place to be flying a drone in the first place. Too many buildings, too many source of interference.

 

[Meta4]

I'm not really sure what happened here. The txt file is DJIFlightRecord_2019-06-09_[22-17-01].txt

That was my guess but it's all garbage just like the rest.
I can't see a single line that means anything here:

DJI Flight Log Viewer | Phantom Help

Upload and view DJI Phantom, Mavic, and Spark flight logs online

www.phantomhelp.com

 

[sar104]

That was my guess but it's all garbage just like the rest.
I can't see a single line that means anything here:

DJI Flight Log Viewer | Phantom Help

Upload and view DJI Phantom, Mavic, and Spark flight logs online

www.phantomhelp.com

I'm not sure what you mean by garbage - it does have an extra line of data on the end that is spurious, but the rest of the file is fine.

 

[Meta4]

I'm not sure what you mean by garbage - it does have an extra line of data on the end that is spurious, but the rest of the file is fine.

Sounds like it's displaying differently for you.
This is what it looks like here:


Not one line that makes any sense

 

[sar104]

Sounds like it's displaying differently for you.
This is what it looks like here:
View attachment 75193

Not one line that makes any sense

I didn't try running it through the Phantomhelp site - that may be unable to read it with the extra data on the end. Try this:

DJI Flight Log Viewer | Phantom Help

Upload and view flight logs from your DJI drones

www.phantomhelp.com

 

[BudWalker]

I didn't try running it through the Phantomhelp site - that may be unable to read it with the extra data on the end. Try this:

DJI Flight Log Viewer | Phantom Help

Upload and view flight logs from your DJI drones

www.phantomhelp.com

Yikes!!!