New CDU and GC build avaible

[touwersl]

I made a few test flights with the 'd' release of the CDU software last week. Of both testflights I have send an comprehensive report to Enrico and Thomas of PM.
I heard from them that there MIGHT be an issue with the Navigraph data and the best thing to do is to test with the NAV cycle available from the PM latest webpage.
Meanwhile they are investigating this issue but we could perform perhaps some tests with this NAV data cycle to get more insight information for Enrico to troubleshoot.
Just my thoughts.

Regards,

Theo

[michelmvd]

Enrico advised me to use the beta navdate set on his updates webpage, and with this I don't have the problems anymore.
I hope Navigraph will quickly find this problem, as lot's of data has changed over Europe last month.
B. Rgds
Michel

[Jan Pemöller]

pls confirm using the betadata from PM webpage (also from NAVIGRAPH) and not latest PM-Data (http://www.projectmagenta.com/downloads/navdata.html)
And having no problems after selecting a SID and during departure selecting a direct to waypoint inside the SID ...

on my system it delates the whole SID!

Thanks for your comment.
Best regards
Jan

[Jan Pemöller]

Hi Thomas,

and can you confirm that SID and STAR problems are gone with beta navdata? I will try it this afternoon.

Thanks
Jan

[mauriceb]

I did several flights with the latest beta releases from PM and PM Navdata. Although things seem better, I had at least one flight when adding a STAR totally messed up the route. What it did was add all the waypoints that had already gone by. I was able to recover by removing the extra waypoints, but it was a real pain. The other flights were OK after I added STARs.

Much more serious issues though are the calculations re. the VNAV path. if you don't mess with the initial route, VNAV seems reliable. But as soon as you add a STAR, everything goes to ****. Top of descent does not re-calculate (& does not change) and the altitudes & speeds are all messed up. You also get erroneous top of descent announcements at various times.

Having said that, it could well be I'm doing something wrong. I have just started playing with STARs & route modifications, so I'm not that experienced. But I have a strong feeling that there is something wrong with the way the path is re-calculated when adding or removing waypoints & certainly very wrong when adding STARs.

Have any of you had any success with altitude & speed calculations after modifying initial routes? Is there any way to force re-calculation of altitudes & speeds after modifying initial route waypoints? Seems to me this is or should be a basic function of the FMC and these re-calculations should be dynamic every time you change a waypoint. Am I just dreaming here

Thanks,
Maurice

[NicD]

You're right - recalculation should be automatic after your press EXEC.

On the legs page make sure you've got no route discontinuities and that all waypoints seem logical as far as distance and heading are concerned. If all looks ok there then TOD and VNAV should caclulate fine. If not it could well be a CDU bug.

[mauriceb]

You're right - recalculation should be automatic after your press EXEC.

On the legs page make sure you've got no route discontinuities and that all waypoints seem logical as far as distance and heading are concerned. If all looks ok there then TOD and VNAV should caclulate fine. If not it could well be a CDU bug.

All the waypoints look OK and no discos. If that works for you, then I wonder what I'm doing wrong . This isn't a new bug, if it is in fact a bug. I have never been able to get the right descent path (& T.O.D. indicator) on the CDU after I modified any route (even with previous releases). Distances are OK, heading is OK, but altitudes & speeds are way off.

Am I the only one with this problem. I would like to know before I start pestering PM support

Maurice

[Tom Stian Bjerk]

There is now a new testnavdata dated 07 may.

I havent tested it.

checkout:
http://www.projectmagenta.com/downlo...stnavdata0704/

[NicD]

Hmm.. what about other performance factors... weight, cost index etc. ... check that all parameters are entered into the various CDU pages.

Do you get a TOD calculated on your DES page?

[mauriceb]

Well, at least part of my problem was self induced. I was entering STARs when I was already descending & lower than the altitude specified in some of the early waypoints in the STAR. So I guess the CDU was totally baffled by that.

But I still think there is something else not quite right with the way the FMC calculates the top of descent if I just modify some of the originally calculated values such as specifying a new altitude or speed target for a certain waypoint. But who knows? I may be doing something else wrong here. So, I'll play some more & try to learn the right way to program the CDU .

Thanks,
Maurice