- Joined
- Mar 24, 2015
- Messages
- 312
- Reaction score
- 138
Running DJI GO in the background should not affect the flight performance. The usual effect will be that you can't get connected to the aircraft in autopilot. I think this issue is actually just the same thing as the next issue. You should terminate GO when using Autopilot though.I didn't have DJI GO closed, the phantom would take off and do a wide orbit type flight no where near the first waypoint.
The most likely explanation is that the curves are too tight for the programmed speed and Movement Responsiveness setting, and the aircraft is overshooting. You either need to widen the turn, lower the speed, or decrease the Movement Responsiveness setting.at each waypoint it would stop, then fly back the way it came about 25ft or so, pause again, then continue on to the next waypoint.
Taking off first is definitely safer, but Autopilot does have Altitude Priority to help make auto-takeoff safer than most other apps. In a nutshell, Altitude Priority will cause the aircraft to rise straight up after take-off until it reaches an altitude that is close enough to the target altitude (per the setting) before performing lateral motion.all the missions I flew today I "engaged" with the phantom on the ground, letting Autopilot do an auto take off. I have seen several people say they only engage after they are in flight, should I switch to doing that?
To be clear, all Modes are affected, but probably what you mean is none of the other Modes encourage long-range flight?The only way to really relax, is to not use Autopilot in waypoint mode, and stick to other modes with Autopilot or stick with DJI GO, until DJI releases a firmware that corrects the SDK issue.
It will head to the first waypoint after respecting Altitude Priority.The drone will proceed straight to the first waypoint and may not reach a safe altitude (obstacle clearance, including humans) on its vertical path to this waypoint.