View Full Version : Pm Cdu 394
excalibur67
03-07-2008, 01:20 PM
Hi at all, someone tried this new version of CDU ? They fixed all our problems ? I can't try to myself because i stay in holiday and then not near at my B737.
Regards,
Giuseppe Reda
Its hard to know what's been worked on because the changes.txt file says very little. If we knew the issues that had been worked on then we'd know what to test and could provide more accurate and helpful feedback to PM.
There is also a MCP423a in intermediate builds, but changes.txt is for MCP424 which appears not to be released yet. I assume (from PMs posts here) that the VNAV and speed issues were being worked on, but it's unclear whether these new builds cover this or not.
Can we have some more information PM ? thanks
rob747
03-08-2008, 04:09 AM
Good news - the new MCP build seems to behave a lot better - did a flight from EGKK to LSZH last night (747-4)and the MCP behaved well - no hissey fits at all. Can't say the new CDU build has made any difference... hope we see a GC update soon also.
jrphcien
03-09-2008, 09:14 AM
Hello, for the CDU: unfortunately while in flight if you change via dep/arr the destination runway, then the aircraft will quit its flight route (LNAV and VNAV engaged) until you press execute !
MCP: having the MCP and EFIS from CP flight, using the new build, baro altimeter was difficult to adjust (change only by increments of 3: 29.71,29.74 etc
test flight: cyul cyyz
route: kanur tukir
cyul: rnway 06r sid kanur1
cyyz: ILS rnway 05 star simcoe transition yso
while in flight (with Vatsim) instructed to change to runway 33R
then i did change the star to wasie with transition YSO
Jean-louis
Peter Dowson
03-09-2008, 01:05 PM
Hello, for the CDU: unfortunately while in flight if you change via dep/arr the destination runway, then the aircraft will quit its flight route (LNAV and VNAV engaged) until you press execute !
This sounds like the same bug which has been in the CDU for many versions -- if you change pretty much anything -- cruise altitude, waypoint, etc, whilst the A/P is following an LNAV path, it starts diverging from the correct path quite badly until you press EXEC to finalise the change. The it struggles back on course. It seems not merely to forget to control the flight, but actually positively to turn to a new course. Weird.
This has been reported and confirmed many times before. I've not noticed whether it affects VNAV so badly, though. Shame -- it sounds like it hasn't received attention yet.
Regards
Pete
RGroebl
03-09-2008, 04:10 PM
Hi,
same here. When insert an STAR or an Waypoint and LNAV VNAV is active sometimes the A/P loss the route and fly a turn to the right.
But this happens not at all STARīs or Waypoints inserted. The A/P goes back to course when the Route discontinue on the legs page is deleted.
At example in EDDM NAPSA3M arrival this happend.
Greets
Roland
Ray Proudfoot
03-09-2008, 07:53 PM
Hello, for the CDU: unfortunately while in flight if you change via dep/arr the destination runway, then the aircraft will quit its flight route (LNAV and VNAV engaged) until you press execute!
This is a very frustrating bug and as Pete says has been present for many months. Either Enrico can't reproduce it or he has more important changes.
As Jonathan visits here on a semi-regular basis it would be apprciated if this problem could be bumped up the priority list. Even a reply saying whether it's reproducable would be appreciated.
Frustrating indeed. I can't imagine why this embaressing bug would not be high on the list, and not reproducible.
JonathanRichardson
03-10-2008, 03:19 AM
Frustrating indeed. I can't imagine why this embaressing bug would not be high on the list, and not reproducible.
Hi
Actually this was fixed prior to release, if it is coming back as a problem now it is because several other major changes were made to accomidate other things - somehow that old one has crept back in it seems. It will be looked at of course.
Regards
Jonathan Richardson
RGroebl
03-10-2008, 07:00 AM
Hi,
thanks for your reply Jonathan.
Itīs time to say that the software isnīt so bad, for me, it has been written here in the forum.
I use the software about 6 Monthīs and I am happy. Surely there are some Bugīs, but show me another software which is bug free. I didnīt know software who is perfect.
So I will wait for the next build and hope the bug is erased. For me PM was a new big step to bring my homecockpit to another level of realism.
Greets
Roland
Ok, thanks Jonathon. I haven't had time to do much testing yet but wil do later this week, and will report back.
michelmvd
03-11-2008, 02:33 PM
I did this week some test with the latest pm builds, available on the site (MCP423a and CDU 394 full -released version ).
Route building on the displays looks more smoother and also the CDU gives me a general feeling of smoother operation. Still some overshoots of waypoint with high crosswinds.
The MCP didn't give me any problems but also no addional functionally for B744.
First I did some test with short routes EBOS/EGLL/EBOS and operation was ok.
I furthermore tested a route EBOS/LSZH (Zurich), still a very short route for a B744 ;)
EBOS RWY 26 KOK2M - UL607 REMBA UM624 DIK UN852 LIMGO R7 SUTAL UN852 LASAT UL851 TRA TRA 1Z RWY16
Airac cycle 0802
Big was my surprice, when I saw all the same major bugs as reported here and to PM already for more than a year, were still there. When selecting the STAR (TRA1Z), a major part of the routing disappeared again! The part between DIK and TRA simply vanished from the LEGS page. (UN852 R7 UN852 UL851.) I selected the STAR during preflight, but also at the end of the route , it gave the same result (plus returning).
After waiting so long for an patch or update to the CDU394 this is extermely frustrating. Maybe Jonathan can inform us what was fixed then and what not.
Would be good I think if some forum members are checking this route and see if the same behavior can be reproduced.
I send mail with routing the usual support adresses aswell.
This is really a very unpleasant situation.
B. Rgds
Michel
Trevor Hale
03-11-2008, 02:38 PM
Hi Michel,
I am hoping to get back into the pit this weekend. I am looking to upgrade the builds and have a slash.
First on my Addenda is to get my Epic unit installed and replace my existing interface.
Following that, I will see what happens to the route during a couple vatsim flights.
Best regards,
Trev
I'll do some testing as well.
Strange that the bugs are still there while PM claims that it has been fixed earlier (although that claim may not have been acknowledged by the users here). And how the h%## can it "come back"? Makes you wonder why it did not pop up during the tests PM will surely have performed before they released this version.
JWS
Ray Proudfoot
03-11-2008, 03:15 PM
Hi
Actually this was fixed prior to release, if it is coming back as a problem now it is because several other major changes were made to accomidate other things - somehow that old one has crept back in it seems. It will be looked at of course.
Regards
Jonathan Richardson
Hi Jonathan,
It would be useful if the notes that accompany each release (beta or full) gave details of what has been fixed. Nowhere in Enrico's release notes here does it mention this particular problem has been fixed. http://www.projectmagenta.com/downloads/builds/MCPchanges.txt
We would all appreciate an early fix to this annoying problem - thanks.
Trevor Hale
03-11-2008, 03:29 PM
Guys..
I must reiterate the fact that PM does not regularly monitor these forums.
Please send your comments and support requests via email to: PMSUPPORT (support@projectmagenta.com)
Best regards,
Trevor Hale
Mycockpit.org - Admin
David Withers
03-12-2008, 03:14 AM
well trevor, tell johnathan to stop peeping then!!!...these issues are our secret!!...not.
JonathanRichardson
03-12-2008, 04:44 AM
>
well trevor, tell johnathan to stop peeping then!!!...these issues are our secret!!...not.
Hi
You want me to stop - .... LOL
The status is simple, we do not monitor the forum "all the time" it could be that you post something here and we do not see it at all, or only after several days or weeks. So, as Trevor says - issues like this that you post are just for yourselves, which is fine - if you post to support you can be sure that they are seen. Do not expect a reply all the time though, the more you send to support the more the issue is logged in our brains - here you can post as much as you like but Enrico will never see it of course...
Regards
Jonathan Richardson
michelmvd
03-12-2008, 05:18 AM
Hi Jonathan,
I have send the complete detailed report of course to support too. I hope you received it and can at least confirm you are able to reproduce the problem. By posting the routing here I hope others will be able to reproduce this well know bug also, which maybe will give finally some clues to resolve the problem after a year.
I normally enter the route, as its done according the ops manuals, when entering manually.
- RTE page EBOS - LSZH + RWY of origin (B744 procedure)
- DEP/ARR sid (KOK2M)
- RTE page routing (UL607 REMBA UM624 DIK UN852 LIMGO R7 SUTAL UN852 LASAT UL851 TRA )
- DEP/ARR expected RWY and STAR
- Activate
- EXEC
Already immediately after entering the STAR, the route between NIK and TRA was vanisched.
Many thanks
Michel
JonathanRichardson
03-12-2008, 07:02 AM
Hi
As I already stated before - you probably need to enter all routes via the legs page, even if this means a lot of data entry, this is not something we omitted - it is the current status. The current update has been an entire re-write of the lower level code and many things have been improved that perhaps are not obvious on the first level. Your post to support was received (as others) and has been seen. In the course of time the RTE page entry is being looked at - but it was not promised by us re this update.
Regards
Jonathan Richardson
michelmvd
03-12-2008, 10:33 AM
Hi Jonathan,
Many thanks for your quick reponse via the forum.
I will enter the route this evening via the legs page waypoint by waypoint and report the results back.
As I reported in my previous message, I have indeed the feeling the CDU is operating much more smoother than in the past. This will certainly be the results of the lower level program work from which the results are indeed maybe not clearly visual, but is most important.
Once more a good communication, explain a lot.
As you know the way of entering you suggest, if of course far from what is commonly done in real, certainly if you have to do a 7 or 10 page routing ;)
B. Rgds
Michel
JonathanRichardson
03-12-2008, 11:13 AM
>As you know the way of entering you suggest, if of course far from what is commonly done in real, certainly if you have to do a 7 or 10 page routing ;)
Yes I know, but there is nothing which can be done about that at this stage - I hope via the legs page it works for you.
Regards
Jonathan Richardson
JonathanRichardson
03-12-2008, 11:23 AM
>Strange that the bugs are still there while PM claims that it has been fixed earlier (although that claim may not have been acknowledged by the users here). And how the h%## can it "come back"? Makes you wonder why it did not pop up during the tests PM will surely have performed before they released this version.
Hi
We did not claim any such thing.... We are slowly dealing with very long lists of software changes - right across the board not just Boeing.
After further testing today, the error that was fixed *is* fixed - certainly I could not recreate the original error. To be specific, the original error was that any change in the route would cause the a/c to turn left or right whilst in LNAV. This was fixed and remains so. There is only one issue that remains outstanding with regard to this, but it was not fixed in *this* update and perhaps the original post is refering to when there is a break in the route directly after the active waypoint. In this situation the AP should command to fly present heading, but at the moment it turns back to last known waypoint. That is a different issue to the one fixed - just to avoid confusion. This will be addressed. But it is a different issue to the first one.
Regards
Jonathan Richardson
hercules
03-12-2008, 03:03 PM
hi all, hi Jonathan,
is the bug with the slow TO/GA accelaration fixed?
Regards
Thomas
Ray Proudfoot
03-12-2008, 03:12 PM
After further testing today, the error that was fixed *is* fixed - certainly I could not recreate the original error. To be specific, the original error was that any change in the route would cause the a/c to turn left or right whilst in LNAV. This was fixed and remains so.
Jonathan,
Just so I and others can be clear about which version of the CDU has this fix implemented can you please advise the version number. Do the notes in the readme include this fix?
I can certainly reproduce this bug so if you wish me to send any information to the support address I will certainly do so.
My flying is with FS9 and I run the GC/CDU on a separate PC via WideFS.
JonathanRichardson
03-12-2008, 03:36 PM
>Just so I and others can be clear about which version of the CDU has this fix implemented can you please advise the version number. Do the notes in the readme include this fix?
Hi
Certainly...
MCP423a
CDU394
>I can certainly reproduce this bug so if you wish me to send any information to the support address I will certainly do so.
You mean with the above builds, and you change your routing whilst in LNAV the a/c begins to turn left or right? I specifically re-tested this today, I even downloaded the above builds to make 100% sure I was not ahead of you guys with other betas. The problem did not show up. If it is happening with the above builds - then I am wondering what else is going on. . . please let me know.
Regards
Jonathan Richardson
Ray Proudfoot
03-12-2008, 07:32 PM
Hi
Certainly...
MCP423a
CDU394
>I can certainly reproduce this bug so if you wish me to send any information to the support address I will certainly do so.
You mean with the above builds, and you change your routing whilst in LNAV the a/c begins to turn left or right? I specifically re-tested this today, I even downloaded the above builds to make 100% sure I was not ahead of you guys with other betas. The problem did not show up. If it is happening with the above builds - then I am wondering what else is going on. . . please let me know.
Regards
Jonathan Richardson
Hi Jonathan,
I'll need to check my build numbers and it's a little late now. I'll try a flight tomorrow evening and report back here.
Thanks for your quick response. :D
RGroebl
03-13-2008, 01:48 AM
Hi Jonathan,
I can confirm that the problem shows up with CDU 394 and MCP 423a. They run together on a WIN XP SP2 machine connected over Wideserver to FS9.
Several routes tested and alway the problems show up. When entering STAR the plane leaves his route and turn left or right.
Sometimes the route is erased completely after execute, sometimes all overflown waypoints from the beginning of the route are reentered in the CDU.
This evening I will make another flight and enter the route over the legīs page.
Greets
Roland
JonathanRichardson
03-13-2008, 03:24 AM
>Several routes tested and alway the problems show up. When entering STAR the plane leaves his route and turn left or right.
Sometimes the route is erased completely after execute, sometimes all overflown waypoints from the beginning of the route are reentered in the CDU.
This evening I will make another flight and enter the route over the legīs page.
Just to confirm - if you use anything other than the Legs page for changes - then that is something different / different issue. I am only refering to the Leg page basic route planning facility of the CDU nothing more which has been fixed.
Regards
Jonathan Richardson
Greets
Roland[/QUOTE]
Ray Proudfoot
03-13-2008, 01:29 PM
>Just to confirm - if you use anything other than the Legs page for changes - then that is something different / different issue. I am only refering to the Leg page basic route planning facility of the CDU nothing more which has been fixed.
Hi Jonathan,
I am in the middle of a flight now and can confirm this bug is still there with the CDU and MCP builds mentioned.
Once at Cruise if I go to the CRZ screen and enter a different flight level for CRZ ALT the aircraft turns left until EXEC is pressed. It then resumes the original heading.
Again, whilst at cruise if I then go to the DES screen and alter the Target Speed that again causes the aircraft to deviate left until EXEC is pressed.
I'm sure there are other scenarios that will cause this heading change problem but those will do for now. If you are able to confirm those then hopefully we can have them fixed soon.
Thanks.
JonathanRichardson
03-13-2008, 03:06 PM
Hi
Thanks for the info. Will check it and see what we can do.....
Regards
Jonathan Richardson
Hi Jonathan,
I am in the middle of a flight now and can confirm this bug is still there with the CDU and MCP builds mentioned.
Once at Cruise if I go to the CRZ screen and enter a different flight level for CRZ ALT the aircraft turns left until EXEC is pressed. It then resumes the original heading.
Again, whilst at cruise if I then go to the DES screen and alter the Target Speed that again causes the aircraft to deviate left until EXEC is pressed.
I'm sure there are other scenarios that will cause this heading change problem but those will do for now. If you are able to confirm those then hopefully we can have them fixed soon.
Thanks.
michelmvd
03-14-2008, 09:13 AM
As suggested by Jonathan, I have redone the testflight EBOS/LSZH by entering all the waypoint via the legpage .
My routing was as follow : EBOS KOK2M FERDI BUPAL REMBA RITAX DEMUL DIK LIMGO SUTAL GTQ POGOL LASAT BEGAR TRA TRA1Z LSZH
The most recent Navigraph Airaccycle 0803 was used.
I entered via the RTE page Origin and Destination - then via DEP/ARR the EBOS sid KOK2M and finally via the legpage all the waypoints.
After entering the waypoints, I reopened the DEP/ARR page and entered the TRA1Z for RWY 14 in Zurich.
The good news is, all when smooth and the complete routing was remaining in the box, after entering the LSZH star TRA1Z
Also during the flight "go directs" to DIK and GTQ was completed without any problems or returns.
I changed the STAR of LSZH after GTQ, by first deleting the previous one in the DEP/ARR and then selecting a new RWY (16) and its star.
All went very smoothly after deleting the DIS lines.
Until now, I only had the time to do this route, but it looks that this part is working correctly and smooth. Let's hope the rewriting of the RTE-age code will come up now soon too.
With the latest builds, operations certainly went a lot smoother. Writing low level software is certainly a lot of work and time consuming and not always visual, but sometime even more important.
I think PM is on the good track, just a pitty we heard so litle from the team passing year, which sometimes brings a lot of frustration.
Regards
Michel
Ray Proudfoot
05-05-2008, 08:35 AM
Hi
Thanks for the info. Will check it and see what we can do.....
Regards
Jonathan Richardson
Jonathan,
Is there any news on this problem? It's been seven weeks since you promised to look into it. There is a release of the CDU dated 3 March but the release notes make no mention of what has been fixed. Do we have to install it and find out for ourselves?