As noted above, the gimbal is alligned with the front of the aircraft. Yes, you can upload the data from this flight, and when I get the chance I will try and sync it with the video to form a better conclusion, if possible.Can I upload the flight log from this video and can you please take a look at it. To see if the camera is straight
@blong10 ... For notation, the first .txt file you posted, shows an IMU Positioning error at ~80 seconds and remained fro the entire flight. That being said, the second .txt file you posted ( DJIFlightRecord_2019-10-24_[17-29-27].txt ) does not show this error and that flight matches up with FLY489.
I am not seeing much of a deviation in the angles.
Below is the first .txt log that shows the positioning error in shaded pink.
View attachment 115227
Your flight profile looks straight and even to me.
View attachment 115228
The gimbal YAW matches the aircraft YAW so I would dought that this is related to the gimbal.
View attachment 115229
As noted above, the gimbal is alligned with the front of the aircraft. Yes, you can upload the data from this flight, and when I get the chance I will try and sync it with the video to form a better conclusion, if possible.
There is another way to do this as well. If it were me, I would fly a Waypoint Mission, either with GO4 or Litchi. That way you eliminate the variable of the RC. If the drift is there ( more than a few degrees ) then you know it is an aircraft issue.Please see the video I posted and the times I referenced and see if I'm crazwa
As noted above, the gimbal is alligned with the front of the aircraft. Yes, you can upload the data from this flight, and when I get the chance I will try and sync it with the video to form a better conclusion, if possible.
There is another way to do this as well. If it were me, I would fly a Waypoint Mission, either with GO4 or Litchi. That way you eliminate the variable of the RC. If the drift is there ( more than a few degrees ) then you know it is an aircraft issue.
The only issue there is, if I am not mistaken, tap to fly is only "Auto-Takeoff". The aircraft will only lift off and hover. What you need is a long straight run. The road by your launch point certainly looks straight enough as a bearing point. If you look at this quick sample from Litchi, you will see what I mean. From Waypoint 2 to Waypoint 3 is ~ .4miles. That should be plenty of distance to notate any drifting.I could also try tap to fly cant I. That would make it fly straight and see if it's a RC issue. Because if it flys straight under this and not using the RC I would say the RC is the culprit.
@blong10 Before going too much farther with testing, I'd like to have @sar104 and/or @BudWalker take a look at your logs if they have the time. They are much better in diagnosing an IMU issue ( If there is one ) than myself.
I was watching the thread, as it happens. I'd like to see the DAT file (mobile device or aircraft) for the flight shown in post #25.
So I took it out and I forgot to let the drone fly itself using the DJI Go app anyway I tried to fly it straight multiple times on this run and it was way off in my opinion. I would really like if you guys can look at this log.
FLY497.DAT
drive.google.com
![]()
DJIFlightRecord_2019-10-25_[17-59-42].txt
drive.google.com
Maybe, but the last Dat I saw was.....FLY489.......Will see what the OP says.Is that the log from the video above?
Is that the log from the video above?
We use essential cookies to make this site work, and optional cookies to enhance your experience.