I think a lesson learnt here would be to extract the logs immediately after it all goes wrong rather than mess with it because they soon get over written and also in the effort of syncing the flight logs to view them on air data also removes them from the phone itself :rolleyes: it's almost like...
Think your right about it not deleting some old data files I bet the one we were looking for had been over written because I had flown it after the incident plus messed around with turning it on and off. I've deleted all but the most recent logs and will see how it behaves now. Is there a rtc...
Ah well we may never know I have flown it a few times since from the same place even and thrown it around in sports mode and not had any errors again. I have downloaded all of the flight logs individually via dji assistant and checked them in csv view but cannot find 113. Weirdly there are some...
OK only fly117.dat is avaliable on my phone so trying the aircraft itself the mounted disc method doesn't work I can see 2 disc drives but neither do anything and this is what I can see on my list of available logs
Is it the flight logs off the aircraft you want? I plugged it in the pc and it all looks different than what it used to the lost of logs doesn't include the day when it happened. Altho the date could be wrong in the mavic as I saw flight logs for September when it was packed away. I will look at...
I've checked through my logs and true there are absolutely no compass errors in any other flight taking off at the same location before or today after very odd maybe I had something in my hand when I turned it on. Also it's not the first time I had used it since the motor replacement I have...
I saw those too on the air data but none appeared while I was actually flying plus I took off where I normally take off for flying round the back garden it's a large bit of concrete with no reinforcement but there is a scrap pile I flew over on the way into the garden but not normally an issue...
So first proper flight after replacing a motor on my mavic and it being layed up for almost a year it all seemed to be working fine so decided to take a panoramic from abut 200 ft and that's where it all went wrong. From looking at the logs it shows an imu error and yaw errors not sure what...
Yep calibrated gimbal, IMU, compass and the controller sticks factory reset the drone and latest firmware still the same. Recalibrated the IMU again too after the latest update as it was saying IMU error in the go app but not on the controller or the flashing light and it flew fine still. And...
I've had the same issue since an update around August. I also have a terrible yaw drift on the gimbal I can hover in front of myself and actually see the gimbal slowly drifting to the right. I have recalibrated everything, replaced gimbal cable and redone the firmware to no avail. Currently on...
It's just a cheep dc to dc boost converter really it has a mutch higher input range than the standard mavic charger so I can charge off a 12v solar array when the sun goes behind a cloud
Had a cessna come over my house and Garden the other day less than 200 ft for sure because it went right through the point where I was hovering my mavic at 150 ft taking a panoramic earlier that morning!
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.