Sean-newbie
Core User of DJI
Flight distance : 15997 ft
United Kingdom
Offline
|
Ok I see you have formatted the card but the following is worth a try.
Put that new card in the drone, boot the drone and let it sit for maybe a minute or so then switch the drone off and remove the card.
There may be readable logs on the card,. Put the card in a reader and connect the reader to a computer. DO NOT read the card via the drone.
If you have a Windows computer then, I think you need to have "show hidden files" or words to that effect, switched on or active/ Likewise "show extensions" needs to be on.
Open the card via the following path or folder tree.
Computer->card's name->MISC->LOG->flylog
Open flylog and you will see fc_log.log
Copy fc_log.log to your computer, note that is COPY not move, leave the original where it is.
Change the extension of the copy from log to DAT, so fc_log.log becomes fc_log.DAT you will get at least one warning or question about changing the file type, click whatever is necessary to change the file name to fc_log.DAT
That file i.e. fc_log.DAT is now likely to be readable by the free software DatCon and may contain messages giving an indication of what the problem is. DatCon outputs the processed file as a csv which can be opened as a spreadsheet.
This works for me and the log seems to cover several switch the drone on / switch teh drone off sessions of the drone. I saw this in the mavic pilots forum and I think one of the posters said thay might have had a full log.
If one of the log people in here would perhaps play with the idea other logs might be found.
With regards to the original now formatted card, if you have not overwritten the old data it might be recoverable. Whether the naming of any recovered files will make sense I have no Idea.
I use ZarX for photo recovery but do not know if it can recover data files. I have also seen mention of recuva
|
|