Wouldn't that disrupt the connection and recording as well? (also would the log show a voltage drop if it maintained recording/connection during the whole fall?)you could have a problem with the battery connection in the drone, this would be inline with what is happening
Finally managed to get the log file uploaded (internet connection here sucks for upload)As this was a Mini 1 we still have a possibility to see what the motors actually was doing ...
The Mavic Mini maintains the most recent DAT file named fc_log.log on the removable SD card in hidden folder: MISC » LOG » flylog.
Check if you have that fc_log.log file ... if you have, share it. It might be rather large so you perhaps need to put it on some personal cloud service like Dropbox & share a link to it.
Can unfortunately only find these flights in the fc_log.log file ...Finally managed to get the log file uploaded...
That was a test flight from much later in the day (3:30 - 4:00 ish), the mess of red in the middle is where I was experimenting as I had noticed it wasn't reacting to the ground consistently, lots of takeoffs and landings, bits of logs I have looked at from them show vps height indicating negative numbers, locked at 5.9 feet throughout a flight (including takeoff & landing) or seemingly normal.Can unfortunately only find these flights in the fc_log.log file ...
View attachment 148343
And this is the incident flight from your earlier shared log ...
View attachment 148345
But also get below when trying to convert in DatCon ... so have a feeling that it's more in there, maybe @BudWalker can figure out how to get hold of it.
View attachment 148346
The trick is to tell DatCon to not use Smart Time Axis processing.Can unfortunately only find these flights in the fc_log.log file ...
View attachment 148343
And this is the incident flight from your earlier shared log ...
View attachment 148345
But also get below when trying to convert in DatCon ... so have a feeling that it's more in there, maybe @BudWalker can figure out how to get hold of it.
View attachment 148346
Crash flights looks to be in there (green line)...
@BudWalker ... have to leave this over to you, can't get this massif log to open directly from Csvview, haven't enough free space on my C: drive for the .csv creation ... tried directly with DatCon with .csv saving towards another hard drive with more free space ... but jeez, it takes time to open a 44 gig file in Csvview & then it mainly adds huge waiting times for every action in there.Looks to me like the flight shown in post #1 was over written in the fc_log.log by a subsequent flight . Bummer.
The flight shown in post #1 looks like this.Crash flights looks to be in there (green line), blue line is immediately after.
I don't think I have overflown that area since the crash.
View attachment 148397
Yes, the CsvView/DatCon architecture makes processing the fc_log.DAT quite the machine eater.@BudWalker ... have to leave this over to you, can't get this massif log to open directly from Csvview, haven't enough free space on my C: drive for the .csv creation ... tried directly with DatCon with .csv saving towards another hard drive with more free space ... but jeez, it takes time to open a 44 gig file in Csvview & then it mainly adds huge waiting times for every action in there.
Hope you have a better computer than I have ...
7050 [L-ESC]ESC3 link down||| 7051 [L-FMU/MOTOR]esc err. status:0| 7051 [L-FMU/MOTOR]fault on . esc(4) is disconnect| 7051 [L-ESC]ESC0 link down||| 7051 [L-ESC]ESC1 link down||| 7051 [L-ESC]ESC2 link down||| 7052 [L-FMU/MOTOR]fault on . esc(1) is disconnect |
7052 [L-FMU/MOTOR]fault on . esc(2) is disconnect| 7052 [L-FMU/MOTOR]fault on . esc(3) is disconnect |
We use essential cookies to make this site work, and optional cookies to enhance your experience.