Printable View
Hello Cockpitbuilders,
I just saw that there are are lot of new updates from PM on their website. New versions of GC, MCP, CDU for both Boeing and Airbus are ready for download (also new updates for pmsystems, Instructor Station and RJ GC).
Anybody tested it already?
Maybe it's possible now to put in the airways now?
I hope that a lot of bugs are fixed!
Unfortunately I have to wait until weekend but I'm curious about it!
Greetings
Norbert
oooooooopppppppppppppppssssssss
An AFT Overhead for the 737 at pmsystems 112 and at least 20..30 new offsets.
I see a lot of forum activity in the next weeks.
Now we have to buy an AFT overhead?
Well, I did 2 flights last night after updating all the software. This is what I found so far.
First flight was a short flight (TJSJ-TNCM) with 2 waypoints and it was a total disaster. The ND was still showing that the Top of climb was quite far away while the CDU showed I should be descending. Basically ND was way off but I may have done something wrong somewhere because the next longer flight between New York & Toronto was much better.
BUT, there are still some unresolved issues as far as I could see. The airplane still wants to turn towards the next waypoint as it gets closer. It seems **** bent on overflying the next waypoint exactly before it finally starts the next leg. It seems a bit better than before, but still not quite right. I don't think this is a big issue though although the passengers may not like it :D
When within 50 miles of TOD, the Descend now option should be available in the DES page, but it isn't. Sometimes later it became available, but I wasn't checking closely, so don't know at what distance it became available (it was available when I checked about 25 miles from TOD).
Most importantly though, VNAV descent is unable to properly control speed & by that I mean, you will never reach the 250 knots target at 10,000ft or even much below without manual intervention. The initial descent works fine and when reaching 10,000 ft, the throttle finally came back to idle, but I was still way above 250 knots and stayed that way until I took over manually. I don't recall seeing a drag required message on the CDU when approaching 10,000 ft.
I didn't not get a chance to test whether the route gets messed up if you select a different STAR but it did not get messed up when I selected a different landing runway.
I'm not at all discounting the fact that I may not be following correct procedures or that some of my settings in the various ini file may have got changed as I was experimenting earlier, so I'm not rushing to pass any judgement. Much more testing needed by many people, so looking forward to read about other people's findings.
Maurice
Achilles,
Where do you see any AFT overhead on PMSys 112?
Peter
Quote:
Originally Posted by AchillesP
Maurice,
Do U use FSX for your tests?
Hi Peter,
in the "sysvar.txt" you can find some new Offets:
And in the "pmsys737.lgc" it says:Quote:
5710 1 IRSSelector1
5711 1 IRSSelector2
5712 1 IRSSelector3
5714 1 IRSStatus //this can be used to set the various conditions
5715 .0 IRSNotAligned //will disable GC
Maybe that's what has been mentioned by Achilles!Quote:
////AFT
if aftPanel then
if noirs then
sixpackirs = 0
else
SixPackIRS = IRSDCL or IRSDCR
endif
if flapstest <> 0 then flapstest = 0 [2]
if flapstest = 0 then
LETransit = LEFlapsTransit
LEExtended = LEFlapsExtended
SlatTransit = LEFlapsTransit or ((FlapsPosL > 2050) and (FlapsPosL < 4090))
SlatExtended = (FlapsPosL > 10) and (FlapsPosL < 4090)
SlatFull = (FlapsPosL > 4090)
else
LETransit = 1
LEExtended = 1
SlatTransit = 1
SlatExtended = 1
SlatFull = 1
endif
//--
if IRSSelector1 = 0 then
DCTestL = 1
IRSTestL = 1
IRSOff1 = 1
IRSDCL = 0
IRSLAlign = 0
ATT1 = 0
IRSAlignedL = 1
endif
if IRSSelector2 = 0 then
DCTestR = 1
IRSTestR = 1
IRSOff2 = 1
IRSDCR = 0
IRSRAlign = 0
ATT2 = 0
IRSAlignedR = 1
endif
if (IRSSelector1 <> 0) then
DCTestL = 0 [2]
IRSTestL = 0 [12]
IRSDCL = DCTestL
if DCTestL = 0 then
IRSLAlign = IRSTestL or AlignL
endif
if (IRSSelector1 < 3) and (ATT1 = 0) then IRSOff1 = IRSNotAlignedCDU
if (DCTestL = 0) and (IRSTestL = 0) then
IRSAlignedL = IRSOff1
else
IRSAlignedL = 1
endif
endif
if (IRSSelector2 <> 0) then
DCTestR = 0 [2]
IRSTestR = 0 [12]
IRSDCR = DCTestR
if DCTestR = 0 then
IRSRAlign = IRSTestR or AlignR
endif
if (IRSSelector2 < 3) and (ATT2 = 0) then IRSOff2 = IRSNotAlignedCDU
if (DCTestR = 0) and (IRSTestR = 0) then
IRSAlignedR = IRSOff2
else
IRSAlignedR = 1
endif
endif
if IRSNotAlignedCDU and (IRSTestL = 0) then AlignL = blink
if IRSNotAlignedCDU and (IRSTestR = 0) then AlignR = blink
if (IRSSelector1 <> 0) or (IRSSelector2 <> 0) then
IRSNotAligned = (IRSAlignedL and IRSAlignedR) or ((IRSSource < 1) and IRSAlignedL) or ((IRSSource > 1) and IRSAlignedR)
else
IRSNotAligned = 1
endif
if (IRSSelector1 = 3) or IRSNotAlignedCDU then
IRSOff1 = 1
ATT1 = 1
endif
if (IRSSelector2 = 3) or IRSNotAlignedCDU then
IRSOff2 = 1
ATT2 = 1
endif
//-----------
Cheers
Quote:
Originally Posted by Jackpilot
That's all I ever use now ;)
Maurice
Guess I have to purchase more sys-boards then. New functions need more interfacing:D
I installed the updates yesterday and did a quick test flight. Unfortunately the plane still tried to turn back after I'd selected a STAR / RWY on the APPDEP page, while the EXEC light was lit. Once I pressed EXEC it resumed LNAV track. I've reported this to PM support and they are looking into it. If anyone else still sees this bug please report it here and to PM support.
Hello Nick,Quote:
Originally Posted by NicD
I confirm this bug, the same effect for me. I'll send a message to PM support now.