- Joined
- Aug 17, 2020
- Messages
- 327
- Reaction score
- 212
My Phantom 3 S had been on the shelf for a few weeks so I decided to send it on a couple of beyond-signal-range Litchi missions since such missions are perfectly legal in my remote Third World backwater. Reviewing the video footage from the first flight, I was alarmed to see a couple of instances when the drone yawed violently enough for the camera to pick up a glimpse of one of the front motor housings, which I have never seen happen in over 2,200 miles of Litchi flights.
I reviewed my pre-set camera orientations along the flight path, and there simply weren't any abrupt changes in my assigned camera directions that could account for those two uncommanded and drastic yawing motions. I would be grateful if anyone could shed some light on this drastic and uncommanded yaw that I have seen this Phantom3S perform for the first time ever today.
The second odd behavior that I observed occurred when I launched the drone on a 22-minute duration Litchi flight plan mission right as the sun was about to set, at twilight. Now I do realize that most of the footage filmed at dusk would have been too dark to be of much use, but I intended to edit out all footage that was recorded after sunset. The drone was still within signal range when Litchi announced that the mission was being terminated and an RTH was about to be triggered. The drone rose to the RTH height and sure enough headed right back to base without any input from me whatsoever.
Because I'd never in the past launched the drone quite that late in the day, it occurred to me that perhaps Phantom drones are hard-wired to RTH when light sensors indicate that lighting will be insufficient for filming by the time the drone reaches its destination, but this is mere speculation. I sure would be grateful for any opinions that can be offered as to why this unexpected RTH occurred on this particular flight. I haven't calibrated the GPS for a while now, so maybe that might be a factor.
I reviewed my pre-set camera orientations along the flight path, and there simply weren't any abrupt changes in my assigned camera directions that could account for those two uncommanded and drastic yawing motions. I would be grateful if anyone could shed some light on this drastic and uncommanded yaw that I have seen this Phantom3S perform for the first time ever today.
The second odd behavior that I observed occurred when I launched the drone on a 22-minute duration Litchi flight plan mission right as the sun was about to set, at twilight. Now I do realize that most of the footage filmed at dusk would have been too dark to be of much use, but I intended to edit out all footage that was recorded after sunset. The drone was still within signal range when Litchi announced that the mission was being terminated and an RTH was about to be triggered. The drone rose to the RTH height and sure enough headed right back to base without any input from me whatsoever.
Because I'd never in the past launched the drone quite that late in the day, it occurred to me that perhaps Phantom drones are hard-wired to RTH when light sensors indicate that lighting will be insufficient for filming by the time the drone reaches its destination, but this is mere speculation. I sure would be grateful for any opinions that can be offered as to why this unexpected RTH occurred on this particular flight. I haven't calibrated the GPS for a while now, so maybe that might be a factor.