I’m using the GTN750 in Xplane with Carrenado 182.  I have AIr Manager G5 panel emulation connected to Xplane.

Settings for GTN are as master, with GPS->SIM sync.

The problem I have is the gps bearing pointer on the g5 is not updating correctly.

I believe it is driven off xplane dataref gps_bearing_deg_mag

This variable is not being updated correctly. If I use the G1000 in the 182 it is. As soon as I make GTN master and drive the G1000 from that, the variable stops being updated.

any ideas?

thanks.

 

21 hours ago, uptimist1 said:

As soon as I make GTN master and drive the G1000 from that, the variable stops being updated.

any ideas?

I believe you've got the answer already:

The XP11 G1000 is a first-class citizen in the X-Plane world and doesn't play nicely with XP11 "override gps" feature. In other words, 3rd party plugins can't override the G1000.

Having said this, the dataref XP11 is expecting plugins to override is:

"sim/cockpit/radios/gps_dir_degt"

 

Thanks for responding.   I did a little more investigation, it's not actually specific to the G1000.  The problem is the same using the stock Xplane 172 with the GPS which looks like a 530.

I think the issue is this:  it appears the Air Manager G5 is using "gps_bearing_deg_mag" to set the G5 GPS bearing pointer.  That dataref is being updated by Xplane with a good bearing, when using Xplane 530 or G1000 style GPS.  When the RXP GTN is enabled, it is being set to due north (actually 359.9 or something close).  I don't know if you are setting it to that value, or it reverts to that value when master GPS is the RXP.  The dataref you point out "gps_dir_degt" is a bearing relative to track.  So for example if track is 060 and gps bearing is 020, the dataref value will be -40.  You can use that to get the GPS bearing (060-040 = 020), but the Air Manager G5 is relying on the default Xplane behaviour of doing that calculation and writing the result to gps_bearing_deg_mag.

That's what I observe anyway.

Any chance you could update the GTN to write the actual bearing to gps_bearing_deg_mag? 

Unfortunately we can't override this dataref, like I've said:

The dataref XP11 is expecting plugins to override is: "sim/cockpit/radios/gps_dir_degt"

Now I agree this could be seen as a bug in XP11 in which they don't change their computations based on the override.

On one hand XP11 should update gps_bearing_deg_mag taking in account any 3rd party override writing gps_dir_degt.

On the other hand, the G5 should use the lowest level data, not the pre-computed data for display purposes, which "sim/cockpit2/radios/indicators/gps_bearing_deg_mag" is along with any other dataref in the "indicators" path.

This is the main point in my opinion: such gauges should use the low level datarefs only. Indicators/actuators datarefs are mostly for the 3D model. They could also use the specific RXP datarefs directly (details in the RXP manual) and decide which datarefs to use based on detecting whether there is any RXP 'master device' active.

Edited November 22, 20205 yr by RXP

I'm having the same problem using the GTN 650, but noticed that it doesn't happen if the GTN CDI is in VLOC mode. To test, put two VORs (that are in range) in NAV1 and STBY. Switch CDI to GPS. Enable VLOC on Bearing Pointer 2 on the G5 (XPlane 11.5, Air Manager). Now switch the NAV1 and STBY on the GTN 650; the G5 bearing pointer doesn't move.

Now, switch the CDI to VLOC and do the same thing. HSI in Air Manager switches to VLOC mode (green), and Bearing Pointer 2 points to NAV1 source. Switch NAV1 and STBY, and the Bearing Pointer moves also.

So, the RXP unit is certainly capable of driving the G5. Any thoughts on what might cause the issue I just described?