I was flying my ALTA on a shooting today, flew 4-5 flight without problem, then suddenly lost control, the copter started making very stragne noise (high vibration) and then started to yaw left and roll left and in a spiral it crashed. Temperature was 4 celsius, the gros weight was 12.5 kg. After crashing I could stop the motors, only when I teared off the batteries. Tried to contact Freefly, but no response yet. Is there any way to check the log files?
Hi Adam: Sorry to hear about this. Today is a national holiday here in the USA (Thanksgiving), so FF is closed until the morning of Tuesday December 1st. Can you please remove the microSD card from the GPS unit (it's under the small rubber cover). You should see a .csv (Comma Separate Values) file that corresponds to the flight. Post it on the forum or email it directly to me at ajohnsonlaird AT me DOT com and I'll have a look at it. Certainly send an email to support@freeflysystems.com. Send the .csv file as an attachment if you can. If the .csv file is very large (e.g. > 2 megabytes) your email software may object. In that case use a Web based file transfer service like wetransfer.com (it's free) to email the file to me -- I can then get it to FF. Andy.
Adam: Afterthought: Could you create a compressed ZIP file of *all* of the .csv files on the microSD card please and send that ZIP file to me. I'd like to be able to see if there was any evidence of an impending problem *before* the mishap flight. Thanks Andy
Hy, It's uploading. There is one file that is damaged and can't copy or upload it. You can download the files from here: https://www.dropbox.com/sh/e1y6v55gtq3v8sj/AADH7yLv0HvA4LL_iiysrb9Ta?dl=0
OK. Got the ZIP file. Thanks. Is this damaged file the most recently created? If so, that will be the one for the mishap flight, I'm afraid. If it is the mishap flight's file, then there is a chance that the data is on the microSD card, but just not in an easily accessible form. Let me know and we'll work from there. Andy
It is the last big one, there is only 1 file after this, but thats only 613 KB.Any idea how to recover/send this file?
Sorry to hear about your issues. Based on the logs, do you have the UTC time of the incident? Makes it a little easier. All the logs look normal so Im guessing that the corrupted log is the one that contains the culprit.
I think it was UTC 7am 58 min. In my time zone it was 8 am 58 min. Any idea how to send the damaged file?
Second to last log is at 08:57:41 and then jumps to 08:58:45 almost a full minute of no logs. Hmmmm. What were you powering with??
Are you running a Mac or PC? We might be able to get you to create a forensic "image" of the entire microSD card and send that... Andy.
There is two 10.000 6S TATTU batteries. They survived, the motors were still running before I disconnected the batteries.
The last log fiile, SYNLog-08-58-50.csv, shows a status of "Fail" going from 0 to 1 in data row 14. What I'm trying to figure out is whether the last two files, SYNLog-08-55-15.csv and SYNLog-08-58-50.csv are really from the same flight? There is data corruption in the first few rows of file SYNLog-08-58-50.csv that suggests that this file is a "continuation" of SYNLog-08-55-15.csv -- but that's something I've never seen before. Andy.
I can make a video of how I copy and upload the files, or even let someone use remote desktop to check them. I really just want to figure out what happened. And by the way I really need this copter to work.