14 minutes ago, rasander said:

...

Connect GPS to HSI (pilot): checked

...

Connect GPS to VOR1 indicator: checked

...

 

 

How did you do that, can that be done at the same time? I could not do it with the RXP 530 afaik.

Edited March 18, 20215 yr by PeterBremer

7 minutes ago, PeterBremer said:

I could not do it with the RXP 530 afaik.

All our GPS (750, 650, 530, 430) are all implemented with the same functionality regarding these. If you can fly an approach with one, they all will fly the approach the same (except if the GNS and the GTN navigation logic is different of course, and it might be possible it is for anything pertaining to PBN because the GTN is more recent).

By the same token, it also means if you can configure the GTN a certain way for example, but can't configure the GNS the same way, it is bug in our product, and I've very much like to know precisely in this case so that we can make the correction!

1 hour ago, RXP said:

All our GPS (750, 650, 530, 430) are all implemented with the same functionality regarding these. If you can fly an approach with one, they all will fly the approach the same (except if the GNS and the GTN navigation logic is different of course, and it might be possible it is for anything pertaining to PBN because the GTN is more recent).

By the same token, it also means if you can configure the GTN a certain way for example, but can't configure the GNS the same way, it is bug in our product, and I've very much like to know precisely in this case so that we can make the correction!

I meant I can not set RXP GNS530 to both VOR1 and HSI at the same time, which is by itself logical. But it looks like Rasander was able to set it that way.

@rasander can you please post the content of the RealityXP.GTN.ini file ?

@PeterBremer I believe I understood you! I'm just explaining there shouldn't be any plugin different between the 4 types of devices with regard to the "Panel" settings but the devices might produce different results due to their sole generational differences. Otherwise it is a bug in our product.

NB: the same code runs in the same family (750 and 650, 530 and 430). In other words, if this is working with a 750 it is supposed to be working exactly the same with a 650.

Let's try getting to the bottom of this!

Edited March 18, 20215 yr by RXP

I’d be happy to, but please let me know the procedure to post an attachment to this forum. “Insert image from URL didn’t open a browser to locate a file.

 

I also need to know where to find the RealityXP.GTN.ini file.

PS - "Notify me of replies" does not work.  I don't receive any emails alerting me of new posts.

 

Reality XP Keyboard Shortcuts Configuration File v2.0 (XPlane)
 

@rasander I'm referring to the .ini file located in the aircraft folder.

I determined the GTN 750 GPSS and GS work properly when the Plane Maker\Systems\General Autopilot HNAV course is set to either the default of HDG or to GPS/OC

The .ini file in the aircraft folder follows.  I was able to cut and paste it.

Spoiler

 

[GTN]
; comma separated list of gauges
gauges = GTN_750_1

[GTN_750_1]
; comma separated list of render targets.
drawto = WINDOW, PANELS
; is the master device if true.
MasterDevice = true
; aviation db: 0: nav_db2_grm, 1: nav_db2, 2: nav_heli_db2_grmn, 3: nav_heli_db2
NavDbType = 1
; connects to: 'PFC_GTN' or any '#PID' (#D067 for PFC_GTN)
; no value connects to first found, 'OFF' disables connection.
HardwareDevice = 
; hardware selector number or -1 to disable.
HardwareIdx = -1
PowerSource = BUS_2
LinkObs = true
LinkCrs = true
LinkVor = true

[GTN_750_1.WINDOW]
; display window if true.
visible = true 
; show screen only gauge if true.
nobezel = false
; display type: WINDOW,PANEL2D,PANEL3D,PANELS
frame.type = WINDOW
; display position and dimension (left,top,width,height)
frame.rect = 1443,1076,463,440
; screen only border size (pixels).
border.size = 0
; screen only border color (#RGB or #RGBA).
border.rgba = #000000
; enable mouse clickspots if true, disable if false (use SHIFT to override)
usemouse = true 
; left mouse button on the screen toggles popup window if true (requires SHIFT+left mouse button).
popleft = false
; right mouse button on the screen toggles popup window if true (requires XP11.1).
popright = true 
; VR mode position and dimension (left,top,width,height) (requires XP11.20)
vrmode.rect = 0,395,415,395
; display as popout window if true (requires XP11.1).
undocked = false
; display mouse tooltips if true.
tooltips = false
; freeze display position if true.
locked = false
; auto hide in external view if true.
autohide = false

[GTN_750_1.PANELS]
; display window if true.
visible = false
; show screen only gauge if true.
nobezel = true
; display type: WINDOW,PANEL2D,PANEL3D,PANELS
frame.type = PANELS
; display position and dimension (left,top,width,height)
frame.rect = 0,0,0,0
; screen only border size (pixels).
border.size = 0
; screen only border color (#RGB or #RGBA).
border.rgba = #000000
; enable mouse clickspots if true, disable if false (use SHIFT to override)
usemouse = true
; left mouse button on the screen toggles popup window if true (requires SHIFT+left mouse button).
popleft = false
; right mouse button on the screen toggles popup window if true (requires XP11.1).
popright = true

 

 

Edited March 18, 20215 yr by RXP

@rasander Thank you for sharing the ini file. LinkHsi is true by default therefore the OBS input comes from the HSI OBS (which doesn't exists in the C172).

I'm looking at the C172 in PlaneMaker right now. Mine, which is supposed to be unaltered default is already Autopilot:ST55 and HNAV Course: HDG

Do you mean if you change HNAV Course source to GPS/LOC, the GS flag in the VOR indicator is working as expected instead?

Because otherwise I don't think there is any problem with the autopilot coupling itself (the coupling directly overrides the flight director).

Edited March 19, 20215 yr by RXP

X-Plane 11 changed the autopilot to the S-Tec 55, which has no altitude pre-selector, in a recent update, so it is now the default AP.  That deactivated my altitude preselector on my Logitech Multi Panel, until I figured out I had to re-enable the altitude pre-selector that is in the S-Tec 55 X.

Anyway, there is no need to change the HNAV Course from HDG to GPS/LOC.  The GTN 750 glideslope works properly either way.

There is one issue.  The GPS/NAV switch must be set in the GTN 750. If I try to change it from the cockpit it gets overridden by the GTN 750.

ATTN: I've written "55X" but it is "55". I've edited my post now!

As for the CDI mode, you can select which "sync" mode you prefer right under the option.

By default it is GTN -> SIM but you can change this to GTN <=> SIM

Edited March 19, 20215 yr by RXP

Yes, there is no 55X available, but if a Logitech Multi Panel is connected and the S-Tec 55 is selected, the altitude preselector on the Multi Panel works.

Thanks for the clarification on the CDI mode.  I switched to GTN <=> SIM and it now syncs either way.

I was wondering if you would be kind enough to offer a reduced price for the GTN 650 as a return for the information I've provided,

Sincerely,

Rich 

9 hours ago, RXP said:

@rasander Thank you for sharing the ini file. LinkHsi is true by default therefore the OBS input comes from the HSI OBS (which doesn't exists in the C172).

I'm looking at the C172 in PlaneMaker right now. Mine, which is supposed to be unaltered default is already Autopilot:ST55 and HNAV Course: HDG

Do you mean if you change HNAV Course source to GPS/LOC, the GS flag in the VOR indicator is working as expected instead?

Because otherwise I don't think there is any problem with the autopilot coupling itself (the coupling directly overrides the flight director).

And be careful when testing the GS flag: If a valid ILS signal is received while GPS is in GPS mode and not in VLOC mode, the GS flag follows the ILS. So be sure first to select a ILS frequency which is not used in the neighborhood of your test.

When that is done, easiest is to switch off/on the GTN/GNS with the power button. Then carefully follow/check what it indicates on the check screen, the GS flag should be out of view.

3 hours ago, PeterBremer said:

If a valid ILS signal is received while GPS is in GPS mode and not in VLOC mode, the GS flag follows the ILS. So be sure first to select a ILS frequency which is not used in the neighborhood of your test.

I confirm this is the case but it might just be on the _mech dataref variant.

Which would match the description of the dataref as well:

Quote

 

sim/cockpit2/radios/indicators/nav1_flag_glideslope_mech

Glide slope flag, nav1 – mechanical instrument flag that shows whenever no glideslope signal is received

 

Should you manually edit the .obj file to use the following instead, I'm pretty certain it will work as intended:

sim/cockpit2/radios/indicators/nav1_flag_glideslope

Glide slope flag, nav1 – EFIS style flag that shows when glideslope is expected, but not received

 

The problem is the first one (_mech) is not honoring the override_nav#_needles datarefs...

Edited March 19, 20215 yr by RXP

On 3/18/2021 at 6:43 PM, RXP said:

The problem is that XP11 internals are just ignoring the fact there is a plugin overriding the gps data signals and this doesn't count as a "glideslope signal received" for removing the flag from view.

This is most likely due to the 172 VOR gauge using the new dataref introduced since XP11.30 I'm mentioning above:

sim/cockpit2/radios/indicators/nav1_flag_glideslope_mech

Glide slope flag, nav1 – mechanical instrument flag that shows whenever no glideslope signal is received

 

Should you manually edit the .obj file to use the following instead, I'm pretty certain it will work as intended:

sim/cockpit2/radios/indicators/nav1_flag_glideslope

Glide slope flag, nav1 – EFIS style flag that shows when glideslope is expected, but not received

 

 

 

Does not work, at least not when in the "instrument panel self-test" screen of the 530, should be out of view according "VFLG" but it is not.

Need to test while flying, but that will not be before tomorrow.

Edited March 19, 20215 yr by PeterBremer

@PeterBremer thank you for the report. I was hoping it would, but since they first introduced the new _mech datarefs, they have also changed the internal logic regarding "override_nav1_needles" and we can't do anything more for now. I've never found a combination of Plane Maker items and datarefs which would make it work as before so far either, but I don't loose hope. You can still manually change the datarefs using the RXP ones though (see user's manual for the equivalent datarefs), but I'd like the stock datarefs to work as well.