JJB*
Core User of DJI
Flight distance : 13811834 ft
Netherlands
Offline
|
Sean-bumble-bee Posted at 2-13 15:41
I think you had a problem with a prop or motor or perhaps a bird strike causing those, the logs report an impact but that could be a blade breaking and hitting the drone. I think what JJB is looking for in the DAT is motor data, which might gives clues as to what went wrong e.g. speeds, current drawn, voltages etc. If you can post the DAT we can maybe see if it is readable. The DAT is in a folder with a a name that starts MCDat...... you can post the file directly to here I think.
Did you recover the drone? If so were the props intact? Do the motors turn freely? Any feathers or blood on the drone?
If you recovered the drone is it smashed? if a prop was missing check inside the motor for any broken of prop mounting lugs, I pranged a M2P/Z in the house (my fault) and it broke a mounting lug off the prop's base, have a look at an intact prop to see what I mean and for comparison.
Hi,
...the logs report an impact....
Not sure if the original log shows that kind of information.
Recently AirData shows general messages about impacts in pitch and/or roll direction....
I think they add by themselves, checking the sudden pitch and roll angles, speed ect.
Impact messages are not written in PH or AirData CSV files.
"Problem" with the decrypers is that we do not know if they share all information from the log into their CSV file.
Uhm i know they don`t show all decrypted data into their CSV, just check headers in AirData CSV and the info on the site of a flight.....
cheers
JJB
|
|