BudWalker
First Officer
Flight distance : 5966247 ft
United States
Offline
|
In summary, the Flight Controller mistakenly thought the Avata was moving North and rolled it CW to compensate. This can be seen by looking at North velocity from two different perspectives. OSD:xSpeed is computed by the FC. ImuCalcs:velN is not computed by the FC and derived by time differentiating the Lat/Long provided by the FC. Usually, these values are in close agreement.
The incorrect velocity and position is shown in green curve and trajectory. The actual velocity and position is shown in red.
From the OP's description it seems clear that OSD:xSpeed is incorrect and the location solution provided by the FC is correct. This could be caused by incorrect magnetometer or accelerometer data.
Also possible would be incorrect GPS velocity data which is derived from the Doppler effect on the recieved GPS signals. GPS location would be correct, just the GPS velocity would be incorrect. A bit unusual; velocity is more often correct.
Finally, the vision system may be being used to determine OSD:xSpeed. This would be my guess.
More could be learned if the .DAT could be provided. If you had the mobile device connectd to the goggles and the Fly App is set to not synch with DJI that .DAT will exist on the Fly App. Take a look here
https://mavicpilots.com/threads/mavic-flight-log-retrieval-and-analysis-guide.78627/
to see how to retrieve the .DAT from the Fly App. If the mobile device was not connected to the goggles during the flight the .DAT can first be moved from the goggles to the Fly App
using the method described here
https://fpvdronepilots.com/threads/dat-available.4225/#post-35016
|
|