Android app

[aBUGSworstnightmare]

[Patnet]

Appears to have corrected issue where AQ only flies to WP1 and then yaw indefinitely. Still shows yellow line to Equatorial Africa.

[Patnet]

Actually, I'm still having the yaw issue. Any ideas on how to correct? The AQ M4 goes to Waypoints OK but often it just yaws at a WP and doesn't proceed. I've made the target radius 4.0 and I have 200 meters between WPs. Any ideas?

[chschmid]

[Patnet]

[chschmid]

[Patnet]

Hi Christof, thanks. Are you saying that removing the -0.0 heading removes the infinite yawing on lost WP, and thus lets the AQ find the WP?

[chschmid]

[Patnet]

Hi Christof, thanks. I don't really understand why if my hACC is, say, 0.79 (as it is right now) or even 1.25, say, and my target radius is 4m, or even 2m, why it can't find the WP.

If the WP default bearing is changed to, say, 45 degrees, does the camera then not point forward anymore? It's always pointing north east along with the nose?

Thanks for pointing me to the document. Does the following text apply?: "When I command my AQ to navigate to a waypoint, it overshoots/undershoots the target position. Increase your navigation speed I slightly." There isn't any reference to my particular issue of the AQ yawing infinitely

Thanks so much, I'm sorry that I'm slow to understand what you're saying.

[LPR]

Pat

Your hACC is high. If you have an open sky, a good GPS antenna with the right size ground plane you should be getting a hACC that is under .500.

You need to have the speed to the next WP set.

If you use a -0 for the heading, your multicopter will fly with it's front pointing toward the next WP.

You can use -50 degrees and your copter will fly with it's front turned 50 degrees off the heading to the next WP.

Keep playing with missions. I've used mission for years and I'm still learning.

Larry