Recent content by ScrappyMavic

Here is the DAT. Here is the flight record TXT.

Ok, I've analyzed the log and V3 DAT and have some updates. It appears the drone had actually turned off vision / VPS 10 seconds prior to the crash, so we can't blame VPS. Sorry for the false alarm. However we can still blame DJI firmware in it's mode switching between VPS and GPS and pure...

From the OP "With both downward LED and obstacle avoidance turned off, I got into a hover indoors in a room with dim-able lights.". Downward LED == auxiliary lower light. What was behind the Mavic 2? The other wall of the room, about 10 feet back. I'm not sure the forward / backward cam...

Please see OP.

I may be beating a dead or injured horse here, but if you have ever worked in engineering, or designed a system or subsystem, you try really hard to make it not "fail erratically". So if there are serious problems in low light conditions with VPS going wonky, you would try really hard to have...

Hey little life tip for you, throwing out "stupid" quickly and easily on a first post really lowers your class. The bulbs are incandescent and produce extremely low flicker do to the thermal time constant of the filament being much longer than 1/60 seconds. Second, whatever concern you are...

I like to stress test the low light capabilities of the VPS system and so here's what I did. With both downward LED and obstacle avoidance turned off, I got into a hover indoors in a room with dim-able lights. I slowly decreased the brightness in the room until the drone switched to ATTI mode...

Sorry but you are dead wrong, because I see major improvements in v01.03.06 for tilted horizon! I just completed two flights and saw *much* improved horizon performance. However holding the drone and doing a static roll test really shows the improvement. With motors off and gimbal centered...

If you watch the gimbal on v01.03.06 while you do a gimbal cal, there are big changes! You will notice it slowly going through a slow tilt / roll sweep. It never did that on previous revisions... and I've watched it close. Also the calibration takes longer and involves more steps. I'm hoping...

There is a DIY fix for this here.

My personal opinion is that wire twist won't help this particular issue. I've seen this same ATTI / TBE problem when running on the front compass (no noise) and on rear compass after noise fix. A better bet is an absolutely pure compass recalibration.

Based on the data in @Randy 's TXT file, I'd say the second unwanted ATTI event was quite clearly magYaw / Yaw deviation issue leading to TBE. There are roll oscillations present without any stick inputs right before the ATTI event, along with TBE signature in GeoPlayer. Without the magYaw...

I took a look at the RTH ATTI event from @jackgarner and the ATTI event from @storemaster. One thing not mentioned here, and that I'd like to highlight @BudWalker, is that the drop in gpsHealth from 5 to 1 is preceded by > 30 deg magYaw to Yaw separation and roll/pitch oscillations in both...

Thanks for the additional points. Doing several more "sideways" and "nosedown" compass calibrations, I have been unable to repeat my initial results. What I see now, is that no matter how I calibrate, as I yaw through 720 deg as you suggested the max deviation between Yaw and magYaw is less...

Could it just be, @BudWalker , that any type of pitch/roll/TBE oscillations originating from mayYaw mismatch from Yaw will drive the gpsHealth to 1 as it switches to ATTI mode. In this case the GPS data was fine, but the unstable control loop generated large enough errors for flight controller...