Jump to content

Archived

This topic is now archived and is closed to further replies.

ernie274

600/700 VNAV Climb

Recommended Posts

Since I got the 600/700 add on, I have noticed that during VNAV climb, the airplane starts an overspeed at around 30,000 feet. It just stays on 315 knots instead of switching to .80. I didn't have this problem with the base package. Am I doing something wrong? Also, I also find that the VNAV descent is a little more agressive than the 800/900. Is this normal?Thanks!

Share this post


Link to post
Share on other sites

just flying the 700 now from ybbn to ybcs just climbed thru fl 300 ft and it changed to .79 so no problem here so far


I7-800k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,    2  ssd 500gb 970 drive, gtx 1080ti Card,  RM850 power supply

 

Peter kelberg

Share this post


Link to post
Share on other sites

Hi Ernie (don't forget to sign your full name to posts smile.png )I certainly haven't encountered the climb issue. Are you using real weather? If so, what is the outside air temperature?Descent is quite different for each of the models, so provided everything is within limits, you're all good.


Mark Adeane - NZWN
Boeing777_Banner_BetaTeam.jpg

Share this post


Link to post
Share on other sites

I had the same issue sometimes with pre-sp1 base pack (HF4 installed). At FL300 the bird came into overspeed and didn't climb anymore. Had to reduce the speed manually at the CLB-Page in CDU, after that it worked fine. I use ASE for weather.


Robin Harazim

 

System:

CPU: AMD Phenom II X4 940 @ 3,4GHz

Motherboard: MSI DKA790GX Platinum

RAM: 8GB GeIL DDR2 @ 1066MHz

GPU: Gainward HD4870 GS with 1024MB VRAM

HID: Logitech G15 Blue, Logitech G500, Logitech Force 3D Pro

OS: Windows 7 64Bit

FSX: Acc-Pack, REX 2.0 OD, UTX, GEX, FSG2010, ASE SP3, PMDG 737NGX v2987, WoAI, a lot of scenery

Share this post


Link to post
Share on other sites

Robin, every now and then ASE (a wonderful program, I might add) will inject an erroneous air temperature into FSX, usually WAY warmer than normal. This significantly affects a number of things in the NGX, and could also cause issues with the IAS/Mach changeover.If this happens to anyone, I suggest you first look at the air temperature figure on the upper EICAS screen. If it is much higher than normal, then that would be your prime suspect.Otherwise, I'd be looking at the CLB page and verifying that everything there looks as it should.As a side note, it's worth remembering that you should NEVER let VNAV or LNAV (or ANY automatics for that matter) take you someplace you didn't want to go in the first instance. If anything goes odd-shaped, don't hesitate to disengage the autopilot and put your handflying skills to the test to recover the situation.


Mark Adeane - NZWN
Boeing777_Banner_BetaTeam.jpg

Share this post


Link to post
Share on other sites

Hi Mark,thanks for the fast reply. Now, as you talk about air temperature, it comes into my mind, that often the temperature was really much warmer than reported from ASE. At the briefing page in ASE it reported temperatures between -50 to -60°C, but in FSX the upper DU reportet something around -25°C. I'm sure this would cause the problem but somewhere I've read, that ASE reports only OAT/SAT but the NGX shows TAT, could this be a reason for the differences?Is there any known fix or workaround for the wrong temperature injection from ASE?(Sorry for grammatically mistakes, my last english lessons was some years ago :))


Robin Harazim

 

System:

CPU: AMD Phenom II X4 940 @ 3,4GHz

Motherboard: MSI DKA790GX Platinum

RAM: 8GB GeIL DDR2 @ 1066MHz

GPU: Gainward HD4870 GS with 1024MB VRAM

HID: Logitech G15 Blue, Logitech G500, Logitech Force 3D Pro

OS: Windows 7 64Bit

FSX: Acc-Pack, REX 2.0 OD, UTX, GEX, FSG2010, ASE SP3, PMDG 737NGX v2987, WoAI, a lot of scenery

Share this post


Link to post
Share on other sites

Robin, you'd have to take a look over at hifisim's forum for help on that.The issue has affected me only once, during early beta of the 737, and never since, so I'm not familiar with any fix for this.


Mark Adeane - NZWN
Boeing777_Banner_BetaTeam.jpg

Share this post


Link to post
Share on other sites

Refreshing the weather on the ASE interface often helps...Andrew


Andrew Entwistle

Share this post


Link to post
Share on other sites

Robin, the upper DU shows TAT, and as you say, ASE gives OAT/SAT. Have a look at the FMS CDU Progress page 2. It has SAT there and also how far off ISA.Ernie, certainly, as the lads state above, weather values injected into FSX can affect aircraft performance, but non changeover from IAS to MACH at FL300 sounds wrong. I would imagine changeover would occur well before that. Anybody got an explanation?


Best Regards,

Philip M Wafer

EIWT

Share this post


Link to post
Share on other sites

I thought the change occurs around FL260?Andrew


Andrew Entwistle

Share this post


Link to post
Share on other sites

I am not using ASE. The only weather change I make at times is wind direction. I have incurred this problem with the changeover of IAS/Mach with both changing default wind direction and leaving it alone.Ernie

Share this post


Link to post
Share on other sites

I think I found my problem. I was using the ECON setting on climb. The default settings are 320/.803. While climbing, the Climb page shows ACT315 CLB with 315 on the PFD. The target speed from the ECON settings is still 320/.803. I think this difference is the problem. I reset the target speed before takeoff to 315/.802. I got the switch from IAS to MACH between FL280 and FL290 with no overspeed. I'm not sure why there is a difference when using ECON setting, but at least I know how to fix it.Thanks,Ernie

Share this post


Link to post
Share on other sites

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    43%
    $10,985.00 of $25,000.00 Donate Now
×
×
  • Create New...