David Megginson said:
Ampere K. Hardraade wrote:
One explanation for the violent maneuvers that I thought of is this: as the
distance between the plane and the waypoint decreases, the accuracy required
in the course calculations increases. Since it takes time for the autopilot
to
My observations are similar to this. However, I don't think that it's a
problem with the accuracy of the calculations as such. The route manager code
is relatively old and tries to set a straight course to it's next waypoint.
It doesn't consider the wind blowing the aircraft off its lateral
All these issues are a matter of adjusting the autopilot coefficients to
specific aircraft dynamic characteristics.
In order to avoid the spiral into waypoint problem, you should try and
implement something like this: compute a track to the waypoint from the
present position, memorize it, and
Ampere K. Hardraade wrote:
I think it will probably be a good idea to increase the distance that triggers
the poping of waypoints. Right now, the plane practically gets on top of the
way point before switching to the next, which is causing some awfully violent
maneuvers.
The best way to do
Ampere K. Hardraade wrote:
I think it will probably be a good idea to increase the distance that triggers
the poping of waypoints. Right now, the plane practically gets on top of the
way point before switching to the next, which is causing some awfully violent
maneuvers.
Regards,
Ampere
On
Josh Babcock wrote:
How do real life FMS's do it? Does this generally vary? If so maybe it
would make sense to pick this number up from the autopilot XML with a
default defined in preferences.xml.
At any given speed, the same bank angle will give you the same turn rate
(for a coordinated
On Friday 04 June 2004 15:37, David Megginson wrote:
Josh Babcock wrote:
How do real life FMS's do it? Does this generally vary? If so maybe it
would make sense to pick this number up from the autopilot XML with a
default defined in preferences.xml.
At any given speed, the same bank
Lee Elliott wrote:
If I understand the problem correctly, changing the distance at which the turn
is initiated won't make any difference - it's the way that the pid controller
reacts to the jump in input as the waypoint is popped that's causing the
abrupt change.
For example, if there are two
On Friday 04 June 2004 23:30, David Megginson wrote:
Lee Elliott wrote:
If I understand the problem correctly, changing the distance at which the
turn is initiated won't make any difference - it's the way that the pid
controller reacts to the jump in input as the waypoint is popped that's
The violent maneuvers I was describing occur when the plane is a few
kilometers away from the waypoint. Therefore, it should have little to do
with the way that pid controller reacts to the jump in waypoints.
One explanation for the violent maneuvers that I thought of is this: as the
distance
I think it will probably be a good idea to increase the distance that triggers
the poping of waypoints. Right now, the plane practically gets on top of the
way point before switching to the next, which is causing some awfully violent
maneuvers.
Regards,
Ampere
On June 3, 2004 11:23 am, Durk
11 matches
Mail list logo
