Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

VNAV altitudes not copied to the Laminar G1000 (resolved)

Featured Replies

I've been flying the RWDesigns Citation Mustang with the RXP 750. Not integrated into the panel, just as a pop-out. The Mustang has the full Laminar G1000 including VNAV support. When I create a flight plan with an approach on the 750, I can see all the fixes and their altitudes, but the altitudes don't show up in the flight plan on the G1000, just the fixes with a blank altitude. Since there are no VNAV references, the Mustang's AP can't descend to the correct altitude at each fix so VNAV doesn't work.

Am I doing something wrong or is there a setting I'm missing? The 750 is so much easier to create flight plans on, I'd rather use it than the G1000. Perhaps coping of the VNAV altitudes isn't supported, but it would be great if it was.

Thanks for any help!

 

Hi,

This is expected for at least the following reasons:

- The G1000 is not just an EFIS, it is also a GPS and it has a special status in XP11 in that no plugin can override it. This means it is not meant to be adjoined with a GTN or a GNS.

- The XP11 SDK doesn't offer any mean to output the waypoints but their LAT/LON. We're using some tricks and workaround the SDK to try having as much of the waypoints ICAO showing up in 3rd party EFIS,

- The GTN VNAV doesn't provide any coupling nor guidance. It is just a reference for the pilot. It might be possible some specific Garmin Autopilot models are capable of using some of this information in the real world though.

 

  • Author

Ahhh...ok, that makes sense. Too bad, the RXP 750 is so much better for entering flight plans and managing routes than the G1000. Entering a long plan with a rotating knob is tiresome. I didn't realize the real 750 only provides VNAV guidance and doesn't couple to the AP for the most of them. I thought it controlled everything like the G1000 can.

Do you know of any light jets for XP that will allow the GTN to control the AP for a VNAV glidepath? I thought I remembered reading that it works on some of them. I know it doesn't work on the Eclipse 550 as it's AP has no VNAV function. I have the Carenado Phenom 100, but I haven't tried it in there yet.

Thanks for your help and for the awesome product! I get to play with a GTN 750 without having to spend the big $$$ to install a real one! 🙂

 

Thank you for your kind words!

Vertical coupling engages only for approaches with the GTN.

  • Author

Do the GTN 750 RNAV approaches work with the Carenado Phenom 100 autopilot? I was able to navigate to an airport on a GTN flight plan, but when I got to the IAF and armed approach mode on the AP, no glideslope ever appeared on the PFD and the plane did not head down to the runway. I was even able to fly a SID with no issues, but the RNAV approach didn't seem to work.

Thanks!

 

Is this aircraft equipped with a G1000....

  • Author
1 hour ago, RXP said:

Is this aircraft equipped with a G1000....

It is, but it's not the one from Laminar. It's one that was written by Carenado.

 

Sure, but whichever G1000 is is from, any G1000 is supposed to be both EFIS + GPS therefore it is doing its own "override" to any other GPS and has priority.

I also believe the Carenado G1000 is a layer atop the default but I might be wrong with this one.

  • Author

I was able to use the GTN as a GPS source for the AP. I was even able to fly a SID and to other waypoints. The G1000's flight plan remained blank during this even though the AP tracked all the fixes properly. The PFD just never showed a glideslope indicator and there was no vertical guidance when I got to the approach. It's supposedly able to fly an ILS approach if you tune the NAV radio, but it doesn't natively support RNAV approaches according to their documentation. I was hoping the GTN would allow it to.

Thanks!

 

Hi all:  I have a somewhat similar problem with the latest release SW release 5.27. I have integrated this with the Carendao F33A Bonanza, (which includes their KFC 150 autopilot including KI525A HSI and KG258 Vertical Gyro).  I have a 1978 A36 Bonanza, with similar configuration (I have a KFC-200, driven by a GTN 750 - very similar). I bought the simulator and the Carendao and Reality products so I could practice my IFR skills at home. I must say, I am amazed at the realism of these products. Everything is just like in the real plane, and my sim sessions are improving my flying skills. Great products!!!!

With the earlier version of the Reality product both ILS and GPS approaches brought up the GS on the HSI, and worked exactly like the real plane. I would get the GS indicator on the HIS as soon as I had a valid ILS signal, and the CDI was on VLOC. For GPS approaches that give vertical guidance, such as LPVs, The GPS would switch to the appropriate approach mode (such as LPV) as soon as it crossed the last fix before the IAF, and again the GS needle on the HSI would come alive. 

On the latest version 5.27, it all works great for the ILS approaches, but for GPS approaches the HSI never shows the GS needle. I have tried intercepts below the GS (standard practice), and even some above.  What is interesting is that even with no GS indicator on the HSI, the KFC-150 autopilot will still track the GS. So, if I fly a coupled approach, no problem, but I can’t hand fly an approach with vertical guidance.

I suspect I have some configuration wrong, The following is a link to the RealityXP.GTN.ini file: https://drive.google.com/file/d/1UunG2a93ltGs_9yw9WJgR-4Htqyi-x9c/view?usp=sharing

Anyone have an idea here?

Thanks

Charlie

  • 3 weeks later...

As long as we're on the subject of VNAV, is there some way to disable VNAV altogether? I fly a C-177B equipped with a GTN-750 in real life, but we don't have a baro-corrected altitude source on board (yet...I'm hoping we'll install G5s or GI-275s at some future time) . 

It would be nice if the 750 in the sim behaved like it does in the airplane.   

Edited by MaggieL
turn on reply notify

  • 2 weeks later...

@charlesrothschild Hi, I'm sorry for the delay.

If I understand correctly GTN versions prior 1.5.27 where 'driving' the needles on the Carenado KI525A.

But no longer when using the same X-Plane version?

Or did it change since you've update to X-Plane 11.50?

Are the needles showing correct deflection during POST though?

NB: the autopilot override takes place at the F/D level regardless of the needles and this is why it is flying the approach even if there is no G/S needle displaying. The needles however depend on XP11 override system and these are selectively overriding the HSI and/or NAV datarefs depending on your RXP settings (Connect HSI, Connect VOR).

@MaggieL Are you using Shadin Air Data in the RXP? What about disabling it? Are you sure VNAV is not deactivated during installation instead because the aircraft doesn't have a baro source?

 

Hi Jean Luc: To answer your questions, I am 95% certain that the GS indicator was working on the previous  GTN version. (I can't go back and try it now). I recently bought the Reality XP GTN750  (from my notes, I bought on Aug 20), used it a few times (was utterly blown away at how great it is). Then I got the latest upgrade, which I applied and the GS indicator stopped working on GPS approaches.

 

I'm a  new user to XPlane 11, having bought the original version in May, along with the Carennado F33 Bonanza.  Within a few weeks I got a XPlane notice that there was a new Beta version available, so I upgraded to it 11.5b14  (I am running on a brand new Dell Windows 10 desktop). After that upgrade I had to adjust the licensing on the Carennado product, so decided I wouldn't do any more Beta upgrades. I then got the Reality GTN 750.  So I've been using 11.5b14 the entire time I've had the GTN750,

 

Unfortunately I don't know the acronym POST, but the VOR and LOC Deviation Bar (D-Bar) on the KI525A has always worked through all phases. Just now I went into the configuration and enabled the following, which had not been enabled: Connect HSI/CRS (auto-slew), Connect HSI/OBS (course in), and Connect GPS to VOR. I then tried it out, and the results were the same: The GS did not show up for an LPV approach, however it tracked it perfectly with the autopilot. Also, the DBar worked perfectly throughout the entire flight. Any other suggestions would be appreciated.

 

POST = Power On Self Test. The last page during this process is showing expected deviations and flags and these shall reflect in the HSI (provided you've enabled "Connect HSI". Is this matching?

Archived

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.