I’ve recently been running into VNAV issues with the PMS GTN750. As you can see i have a waypoint altitude set to 1000’ at waypoint 4. VNAV should use this constraint to calculate VNAV descent and TOD.
However as you can see for some reason it’s selecting waypoint 3 as its active VNAV constraint and putting the altitude at 0’ even though waypoint 3 has no constraint at all.
How can you choose which waypoint to use to calculate TOD and VNAV? I’ve used the GTN 750 many times in the past to calculate these values without issue, however recently it’s started behaving oddly. Thanks for any help
I have also noticed this, would be nice to have especially when flying more complex SID/STAR procedures that have a lot of altitude constraints.
i know, right? it seems to be behaving strangely
It used to have it, I know I was able.to put in an altitude constraint and have it show a TOD marker. Then one day it didn’t anymore, not sure if I did something or something changed in sim
now that we know it’s behaving differently than it used to (and as it should) guess the next step is to bring it up with PMS directly and see if they’re aware
I’m flying the Aerostar 600 with GTN PMS 750. I’m following the usual steps by entering a lower altitude constraint and enabling VNAV. Everything works fine and the T.O.D. and VS Required fields are correctly calculated.
About 6 seconds later all the fields go black and vnav becomes disabled. I can reenable it but the same things happens, over and over. I’ve never run into this issue before. Anyone know whats going on?
not sure why these got combined, they are two different issues. this latest one is a really bad one and I can’t find anyone else mention it.
Anyone run into this issue as well?
