PDA

View Full Version : New CDU and GC build avaible



Tom Stian Bjerk
04-20-2007, 08:21 PM
check http://www.projectmagenta.com/downloads/builds/latest/?M=D

lets hope that the CDU bugs are fixed

Best Regards
Tom Stian Bjerk

NicD
04-21-2007, 12:28 AM
Good to see something is happening, but looks like another Beta release and not alot fixed yet ? ...

CDU 389
- some minor changes for route generation
- update for engravity legs page SPD/ALT display

I've emailed them a few times now to find out about what's happening with the CDU and I'm not getting any replies (altho I did get replies on some other things) ... hmm ..

stefanloss
04-21-2007, 07:02 PM
Hi,
unfortunately I still have the route bug with the new build. Went back to 382.
:-(

Best regards,
Stefan.

Tom Stian Bjerk
04-21-2007, 08:55 PM
There is new buildt again for the CDU .. buildt 389d .. But nothing new in the changes.txt ...

michelmvd
04-24-2007, 08:23 AM
I did some flights with the latest builds installed. My general impression is a very smooth operation.

CDU : problem with disappearing runway centreline when activating route, is solved.
The drawing accuraty of magenta route is a lot smoother and also without interruptions.

Unfortunately all other reported bugs by me and other members are still there. Also on B744 approach page the flap 25 / 30 indications are not visual. Adding a STAR in route or after activation, still make a mess of the route and also a go direct to a X waypoint makes returning the aircraft to the beginning.

Ciao
Michel

touwersl
04-25-2007, 05:45 AM
Hi All,

I just installed the latest version CDU and made a short flight from EDDM to LOWI. I saw that the CDU didn't display the selected RWY at the departure airport and furthermore I seem to be unable to load my existing flightplans into the CDU. It does load the Departure and the Arrival airports but it doesn't load the waypoints in between. I spotted this problem already in an earlier release but reverting back to version 380 Solves this problem. The latest revisions of the CDU have a different way to load flightplans I saw.
Maybe I'm doing something wrong here?

I didn't see any other major issues in this release however.

Regards,

Theo Ouwersloot

stefanloss
05-01-2007, 05:02 PM
Hi,

there are new intermediate builds available again. I did a quick test flight and everything was working as it should (no route/runway bug).
:p

Have fun!

touwersl
05-01-2007, 05:53 PM
Hi Stefan,

Well i hope it will work for me too, I will test it tomorrow.

Thanks

michelmvd
05-03-2007, 10:34 AM
Hi Stefan
Does that mean you don't have any problems with the route going crazy when selecting STARS during flight or go direct to problems ?
As Enrico thinks it has something to do with the Navigraph data.
B. Rgds
Michel

stefanloss
05-03-2007, 03:52 PM
Well,

I only could do one flight so far, and during that the FMC worked fine, including the selection of a takeoff- and landing-runway and inserting new waypoints during flight. I am using the latest Navigraph navdata cycle.

EDIT:
What actually did happen is that after altering the route inflight, it shortly disappeared, but then was displayed as it should (white dashed line until "EXEC").


The only problem I have is that several Navaids are displayed twice (as the "KBO"-VOR at EDDK), but this actually seems to be a Navigraph-issue, as it also appears outside of Project Magenta (also in FlightsimCommander, for example).

I´ll report as soon as I get time to do another flight.

touwersl
05-03-2007, 04:01 PM
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
05-04-2007, 05:02 AM
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
05-04-2007, 08:39 AM
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
05-05-2007, 02:49 AM
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
05-06-2007, 08:25 PM
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 :roll:

Thanks,
Maurice

NicD
05-07-2007, 12:43 AM
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
05-07-2007, 07:23 AM
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 :mrgreen:

Maurice

Tom Stian Bjerk
05-07-2007, 09:29 AM
There is now a new testnavdata dated 07 may.

I havent tested it.

checkout:
http://www.projectmagenta.com/downloads/builds/latest/testnavdata0704/

NicD
05-07-2007, 07:47 PM
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
05-07-2007, 08:13 PM
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