I wont worry too much about it as long as there is no gimbal overload warning. This is my M2P which has some slight tendency to point to the right as well.
You may want to reconsider whether to go down the path of using log profile. The reports I have seen plus my own experience says that there is little to gain. Here is one of the reports : Mavic 2 Pro Normal vs DLOG
Exactly the same problem has been reported for Air 1 before but I cannot recall the same being reported for other models. May be this is the characteristics of Air 1's battery ?
https://mavicpilots.com/threads/mavic-went-from-96-battery-at-takeoff-to-0.103526/...
It is possible that the drone hit the boundary of a no-fly zone or altitude-limited zone. If it's the latter, you should be able to fly it back once it's altitude is below the limit
Very likely due to the cooling fan not working. My M2P had the same problem and it came just suddenly. The sound of the fan spinning could not be heard. It was still under warranty so DJI replaced it free.
The TXT file looks fine on the PhantomHelp interface but not in CsvView. The same amount of data loss is seen in the "verbose csv" file downloaded from PhantomHelp. The csv file is OK but it contains too little information.
You are right. I was rushing through the flight log data in my previous post and after taking a second more careful look, It can be confirmed that the prop on the right-front motor came off immediately after the collision. The time was so close that I misidentified the cause and result in my...
This is what I saw from the flight log DJIFlightRecord_2021-02-14_[11-45-10].txt . The corresponding .DAT file is not provided so the depth of analysis is limited .
The marked time point in the chart below is 1 second before the collision. Full left aileron was applied but the craft kept banked...
I know the gimbal has it's own IMU. In calibrating the IMU of the craft, it is required to position the craft in different orientations in order to load the accelerometers of different axes in turns. Just don't understand why this is not required when calibrating the IMU of the gimbal.
Seems that the propeller on the right-front motor suddenly came off because the speed of that motor maxed out but the current drawn dropped to almost zero indicating that there was no load.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.