CDU: Fly-By vs. Fly-Over waypoints

[pdpo]

Hans,

the working you described is the same I see in the airbus PM suite.
However I have complained about this to Enrico and send him the
needed screenshots to prove my point. When flying on autopilot
this behaviour is acceptable but once you fly an approach manually
and the MCDU cycles to the next waypoint dropping the wayopint from the
ND ... you loose the reference to it.... worse even when you have defined
several waypoints somewhat close to eachother and when the MCDU cycles
all the waypoints are removed from the ND and you loose all references to fly
unless you revert to traditional VOR/NDB navigation.....

PS : at least for airbus I know that the calculated path of the MCDU includes
the projected turn and the planes follows this path perfectly. When the
MCDU cycles to the next waypoint the previous one does not disappear
unless its outside of the range of the ND.

Greetz Peter

[mauriceb]

""....do you set your cost index? That entry is required to calculate the magenta path correctly...""

By the way what are the usual values for it.
In some doc I have seen that it goes from 0 to 999 but apparently PM does not accept over 400 or so..
Anyone has precise info on that?

Everything I read about this only mentions values of 0 to 100, with 100 being the least economical way (fastest performance). So I don't think that there is any point in putting in anything over 100 even if the CDU accepts it. I could be wrong though

Maurice

[Jackpilot]

0 to 100 would make sense... sort of percentage ...because why 500?

Any "lifesize" CDU specialist on that?

[stefanloss]

PS : at least for airbus I know that the calculated path of the MCDU includes
the projected turn and the planes follows this path perfectly. When the
MCDU cycles to the next waypoint the previous one does not disappear
unless its outside of the range of the ND.

Greetz Peter

That´s exactly how it should be in the 737 as well.