CDU build 390 issues

[rippey]

Issue with new CDU build 390. When selecting an approach at the destination airport I get a windows error message that says 'stop command encountered' and then the CDU software shuts down. Also, not as big of a problem, but the selected star does not appear in the RTE pages...ie DKK.YOUTH2...the proper waypoints do appear in the LEGS page. Anyone else get a chance to try the new build out yet? I am using the first set of test navdata 1206, could that be the problem, is the new build designed to work with the newer test data?

[Bob Reed]

Issue with new CDU build 390. When selecting an approach at the destination airport I get a windows error message that says 'stop command encountered' and then the CDU software shuts down. Also, not as big of a problem, but the selected star does not appear in the RTE pages...ie DKK.YOUTH2...the proper waypoints do appear in the LEGS page. Anyone else get a chance to try the new build out yet? I am using the first set of test navdata 1206, could that be the problem, is the new build designed to work with the newer test data?

This is a programing error make sure to report this to PM at support@projectmagenta.com.

[oal331]

Issue with new CDU build 390. When selecting an approach at the destination airport I get a windows error message that says 'stop command encountered' and then the CDU software shuts down.

Me also have the same error :(
Yesterday I downloaded latest builds with test navadata from PM's site and when selected the VORDME approach at LGSR (Santorini Airport) i got the same error.
When i choosed only the rwy and the STAR without the VORDME it worked.


Another issue i had in my previous version, (that i have to check it in current) was that when modifying a route during the flight, in example a rwy change, until press the EXEC button the aircraft forgets that had already fly the previous legs and turns back to the first flightplan's leg as starting all the rout from the beggining having active all the points again.


Best regards


Eddie

[frans]

I have been using PM for a few years now but the CDU part is not working very good at the moment to say the least.
The Q is ofcourse is it the CDU or is it the navdata??
I am using the latest Navigraph data.
We have paid a lot of money for PM, at least they should keep us better informed.

Regards

Frans Spruit EHAM

ps even Bob must agree with me this time;)

[oal331]

The Q is ofcourse is it the CDU or is it the navdata??
I am using the latest Navigraph data

So we can try the latest builds with old navdata,
or old builds with current navdata to see where is the problem.

This is a s/w approach for troubleshooting ;) !!!


Eddie Armaos

[oal331]

I made the tests i said above and here are the results

With Build CDU390 and old navdata 0610 the same error and cdu closing
With Build CDU380 and current navdata no error, but many problems with fixes, flightplan route, waypoints, fuels remaing, magenta line in GC.

I will return to by previous situation from backup :(

That's why many people remaing in old versions, because they feel that new version have 90% new problems, trying to fix other older.

Eddie

[Jackpilot]

What about CDU390 with latest navigraph?

[oal331]

As i wrote above in the same thread, i have problems also with latest navdata downloaded from PM's site (PM_CDUNAV_0704.zip) with this error message and CDU termination


I will not install other navdata from navigraph, as they will also have them in the same format. As i can understand the problem is both latest in CDU and navadata, so i will flash back some months ago to previous buils and navdata :(


Eddie

[Peter Dowson]

What about CDU390 with latest navigraph?

What about CDU391, I see in the intermediate files folder today?

Pete

[mattford1]

I'm having the same problems as well.

Matt

[oal331]

What about CDU391, I see in the intermediate files folder today?

Pete

I miss the old forum days :-(

[Peter Dowson]

Issue with new CDU build 390. When selecting an approach at the destination airport I get a windows error message that says 'stop command encountered' and then the CDU software shuts down.

The changes files accompanying CDU391 says that the stop statement is removed in that build. It's in the intermediate files folder.

Pete

[oal331]

The changes files accompanying CDU391 says that the stop statement is removed in that build. It's in the intermediate files folder.

Pete


Yes with 391 build i don't have the stop error message.
But i have some issues i noticed also in this build.

First starting the CDU it knows my position and has already the airport where my aircraft is. Before some builds i had to manually type the airport then copy the position so to have ND. Is something new, has to do something with page No2?

Then i re-type the origin (before it was remaining in scratchpad) and trying to fill my flighplan. Choose DEST airport, then Departure rwy and SID, then back on route page to insert first leg.
In example LGAV to LGSR, dep from rwy21L with SOREV 1F then A10.MIL
When typing A10.MIL and move it to Left LSK5, then i press the Right LSK 6
to avtivate. I get a message in scratvhpad ROUTE NOT FOUND


Regards


Eddie