Recent content by slup

Just a heads-up in case you plan to use the Goggles 3 with your Air 2S... Goggles 3 are only compatible with Air 3 & Mini 4 Pro in the "photo drone segment"... not the Air 2S.

Check out --> OpenAthena

Here you have a guy that measure this in the proper way & what equipment he uses...

Can't you use the waypoint mode for this... just design a path with attached waypoint actions like taking a photo & then re-run it as many times you want. Introduction to Waypoint Flight Mode of DJI Fly

Those aren't in any of the logs generated by DJI drones... you need a test stand with a thrust & torque sensor to measure these.

That the cell voltage was that low indicate that the chemistry is LiIon, not LiPo that have the lowest voltage level at 3.0V before permanent damage occur. LiIon have a lowest level at 2.5V... but being as low as 2.6V once landed doesn't give much margin considering the major voltage drop that...

Very much agree with your threads heading... and as batteries are very different than amplifiers, you also should consider reading this post --> Disable forced landing

Think you've misunderstood the intent with the "Fake GPS hack"... it's used to make the firmware switch over to the FCC transmission mode (higher transmission power) if you're flying in a CE mode (lower transmission power) country. Once the "hack" have allowed you to switch to FCC, you can...

As per post #7... no. And that also include the beta version of Litchi Pilot as no SDK is released yet.

You don't have the possibility to stack waypoint actions on the same WP? For instance when arriving to the WP videoing... 1 Stop videoing 2 Timed delay to stabilize the drone (do you have a similar action with DJI WP? Litchi have it...) 3 Take photo 4 Timed delay (give some time to finalize...

The video seems to show the very end of the flight, approx. the yellow circled area... the motor error & what's described in the chart in post #10 happens in the white circled area.

If looking into the moment where you get the "Motor unable to rotate" error, we see several uncommanded movements that could point to a loss of thrust (for instance, the motor can't rotate as fast as it's commanded). The error come at 890sec into the flight... have in below chart placed a chart...

The waypoint mission, as far as you let it execute, looked to be very much in the vertical plane... with a pretty steep ascent until approaching the second pier, then a rapid descent down behind the pier. This reminds me of another case we had here on the forum back in February during similar...

The loss of connection was most probably not the root cause, instead a consequence of the incident. All attitude telemetry + battery data doesn't indicate anything abnormal just there in the end of the log, you had just started to apply a full command for forward flight (stick mode 3)... & then...

A Mavic 2 Pro & several others with Go4 as the original app, only go to the RTH height if below the set height... if above it that will be the height the drone will return on, it will not descend.