Peter, thanks for the tips on the Garmin visual approach.  I understand I need to be at or below the glideslope as I intercept it.

After a week of trying different settings, I now have both the GTN 750 (GPS 1) and 650 (GPS 2) working.  They are both capable of tracking waypoints in GPSS mode, and intercepting, tracking and following the localizer and glideslope.

I had tried hovering over the Com Freq/Push NAV dial before, but after your note, I tried again and found the "sweet spot" where the cursor changes to a hand, so that is working.

Regards,

Rich

 

On 3/21/2021 at 6:51 AM, PeterBremer said:

And even gives when flying unexpeted GS flag results. E.g. When flying the LPV the flag was not there, but a temporary switch to VLOC and back to GPS showed the flag. Also during VOR operations the GS flag was not visible. Afaik the GS flag should be in view uring VOR operations.

So changed it back to _mech

XP11 SDK is very much limited to providing the complete set of overriding. You can for example override the needles, but not the flags?! Therefore it is their own internal logic which like you've found out, is controlling the flag if you're tuned to a station regardless of the plugin setting override_nav#_needles.

In these cases, you can change the _mech dataref with the following (RXP User's Manual, "Simulation Datarefs" chapter):

RXP/radios/indicators/hsi_flag_glideslope_1

NB: dataref suffix can be _1, _2 or _pilot (respectively any GPS #1 (GTN or GNS V2), any GPS #2 and any Reality XP Master Device)

@rasander

I'm glad you've sorted this out!

Can you please share you configuration tips and findings for this, so that it helps others searching for solutions in the forum in the future?

Here are my configuration settings to enable the GTN 650 and 750 to command the S-Tec 55 Autopilot with Altitude Preselector enabled (using a Logitech Multi Panel) in X-Plane 11. Both GPS units are capable of tracking waypoints in GPSS mode, and intercepting, tracking and following the localizer and glideslope.

The key to enabling the GTN 650 as a GPS2 Master Device is to assign VLOC Source to NAV1 and GPS Source to GPS1.

Settings not listed are default.

GTN 750 (GPS 1) Settings for X-Plane 11

Panel Instruments

☒Master Device

☒Connect GPS to Autopilot

☒Connect GPS to HIS (pilot)

☒Connect HIS/CRS (auto-slew)

☒Connect HIS/OBS (course in)

☒Connect GPS to VOR1 indicator

☒Connect CDI Mode to NAV/GPS Switch

        Sync Mode GPS==SIM (both ways, last option

Gauge Options

Cockpit Side               Pilot

Radios                           COM1 / NAV1

VLOC Source              Auto (NAV1)

GPS Source                 Auto (GPS1)

 GTN 650 (GPS 2) Settings for X-Plane 11

Panel Instruments

☒Master Device

☒Connect GPS to Autopilot

☒Connect GPS to HIS (pilot)

☒Connect HIS/CRS (auto-slew)

☒Connect HIS/OBS (course in)

☒Connect GPS to VOR1 indicator

☒Connect CDI Mode to NAV/GPS Switch

        Sync Mode GPS==SIM (both ways, last option

Gauge Options

Cockpit Side               Pilot

Radios                           COM1 / NAV1

VLOC Source              NAV1

GPS Source                 GPS1

 

 

How can you connect GPS1 both to HSI and VOR1 indicator. I think that is not possible, at least not for 430/530, then it is one at the same time.

I should add these settings are for a Cessna 172.  

Since there is no HSI in the 172, it doesn’t matter what the HSI setting is, but it worked, so I left it.

even though there is no HSI gauge in the panel, there is still an HSI system in XP11 internals, and this HSI system data is used by the autopilot system internally in order to determine the navigation data source (it uses the HSI source selector for this). This is why enabling the connection between the RXP GPS and the HSI is helping in this case, because it changes the nav data source selector based on the GPS/VLOC mode.

10 hours ago, RXP said:

even though there is no HSI gauge in the panel, there is still an HSI system in XP11 internals, and this HSI system data is used by the autopilot system internally in order to determine the navigation data source (it uses the HSI source selector for this). This is why enabling the connection between the RXP GPS and the HSI is helping in this case, because it changes the nav data source selector based on the GPS/VLOC mode.

Yes I found that as well (for RNAV vertical guidance, for lateral guidance with the AP connnecting to the HSI is not required), but afaik I can not at the same time as connecting GPS to HSI, connect it to VOR1/OBS, correct?

For my training VOR1/OBS is more important than have the GPS coupled for RNAV vertical guidance. For my training handflying and OBS is more relevant than full AP flying. OBS mainly for circling approaches and holdings which are not in the database.

 

Edited March 24, 20215 yr by PeterBremer

3 hours ago, PeterBremer said:

for lateral guidance with the AP connnecting to the HSI is not required), but afaik I can not at the same time as connecting GPS to HSI, connect it to VOR1/OBS, correct?

There was a reason we're connecting the HSI OBS if you're also enabling connecting to the HSI but I  don't remember which right now (my notes are not helping either). I have a vague feeling it was because otherwise, the VOR OBS was tied in some way and not working. But honestly if both are decoupled in more recent X-Plane versions, it is easy code-wise to lift the restriction and allow connecting it to one or the other. I'll have to further try this.

A further update on the GTN 650 and 750:

- They both continue to work nicely.  They are capable of tracking in GPSS mode, as well as intercepting and tracking the localizer and glideslope.  Upon intercepting the glideslope the GTN begins the descent smoothly and gradually, as opposed the abrupt start of descent in the G530.

- One issue is that on final approach the GTN 650 places the aircraft too high and to the right of the runway centerline, even though the CDI shows the airplane is on track with the localizer and glideslope.  The PAPI lights indicate correctly, so on short final I need to disconnect the AP and fly the airplane.  

- In X-Plane 11 I prefer the GTN 650 over the GTN 750 because its rectangular format fits nicely above the left window without blocking the outside view in a three-monitor setup.

- It took me a day to figure out that the GTN folder installed in the Plug-in folder renders the default X-Plane G530 non-functional.  The G530 appears to work, but after entering a flight plan with an approach I often don’t obtain a magenta line.  In addition, with the GTN folder in the Plugin folder the G530 went off on a journey of its own at the FAC waypoint.  Removing the GTN and GNS folders from the Plugin folder when using the G530 resolves these issues.  I imagine I could also change the settings in the GTN units to disable them, but removing them is easier.

- Overall I am very happy with the GTN GPS units, especially since it is good training for the actual aircraft I have been training in, which has a GTN 650.