Premium Garmin G5 question MSFS

[jph]

Now I'm confused Do you want a refund or not?
I'm not saying never. But I have to get Tony's panels online first, and then have to finish the administration of 2021 (and 2022 Q4) before the end of January. Those are my priorities at the moment.

This is our financial deparment.

So, you tidied up since last year ?
Looks 'normal' to me, a bit like my workbench....

[MatthewS2077]

There has to be something that works because the generic KI525A HSI in the community store will display the glidepath indicator for RNAV approaches.

Are you certain of this because at one point nothing was working for RNAV vertical deviation. I haven’t checked for a few weeks though. Have you seen this work out of beta for instance? For info there are 2 525’s but one is named after the whole compass system.

I tried the generic KI525A HSI earlier today and it wasn't displaying the glidepath for RNAV.

[Crunchmeister]

There has to be something that works because the generic KI525A HSI in the community store will display the glidepath indicator for RNAV approaches.

Are you certain of this because at one point nothing was working for RNAV vertical deviation. I haven’t checked for a few weeks though. Have you seen this work out of beta for instance? For info there are 2 525’s but one is named after the whole compass system.

A few weeks back (pre-AAU I), I created a full steam gauge C414 panel with GNS units, in which I used the Generic - Bendix/King KI525A HSI (by J.ZAHAR based on original by MacnFly) from the community store. And I noticed RNAV GSI was showing as I was coming in on an RNAV approach. This was new to me as well, as I typically used the GSI on the PMS50 GTN750 as my GSI until that point, and no longer had it available in this panel. I was rather pleased to see it actually.

[Ralph]

@MatthewS2077 the way to determine if there's a glideslope in MSFS is a bit wonky.
The G5 is looking at 'NAV GS FLAG:1'. You can monitor this in the Viewer on the Create/Edit tab. When the flag is true (weird), it shows the GSI. I suspect that with RNAV this is false.
I might have to use VOR1_CODE. I think I cannot subscribe to this one at the moment, I can't find a working type.

Code: Select all

The VOR 1/2 code flags:

BIT0:[index] 1= DME available
BIT1:[index] 1 = TACAN available
BIT2:[index] 1= voice available
BIT3:[index] 1= no nav signal available
BIT4:[index] 1= DME transmitter at glide slope transmitter
BIT5:[index] 1= no localizer backcourse
BIT6:[index] 1= glideslope available
BIT7:[index] 0= VOR, 1= Localizer

[SimPassion]

Or this one @Ralph ? And perhaps in conjunction with another one !?

Code: Select all

NAV HAS GLIDE SLOPE 	Flag if tuned station has a glideslope. 	Bool

https://docs.flightsimulator.com/html/P ... es.htm#nav

So, if ILS is not set and glideslope still available :

Code: Select all

NAV RAW GLIDE SLOPE 	The glide slope angle. 	Degrees

[Ralph]

I've used that one, mainly because it was used with FSX, but it did not give the correct output. Maybe this has been fixed, it is probably almost 2 years ago.
Maybe @MatthewS2077 can monitor that one as well in the Viewer.

[SimPassion]

@MatthewS2077 the way to determine if there's a glideslope in MSFS is a bit wonky.
The G5 is looking at 'NAV GS FLAG:1'. You can monitor this in the Viewer on the Create/Edit tab. When the flag is true (weird), it shows the GSI. I suspect that with RNAV this is false.
I might have to use VOR1_CODE. I think I cannot subscribe to this one at the moment, I can't find a working type.

Code: Select all

The VOR 1/2 code flags:

BIT0:[index] 1= DME available
BIT1:[index] 1 = TACAN available
BIT2:[index] 1= voice available
BIT3:[index] 1= no nav signal available
BIT4:[index] 1= DME transmitter at glide slope transmitter
BIT5:[index] 1= no localizer backcourse
BIT6:[index] 1= glideslope available
BIT7:[index] 0= VOR, 1= Localizer

Is there Binary able inside AM ?
It looks like there's f (FLAGS) requirement for type, though I didn't guess what they meant

Code: Select all

VOR1_CODE

VOR2_CODE
	f (FLAGS) 	

The VOR 1/2 code flags:

    BIT0:[index] 1= DME available
    BIT1:[index] 1 = TACAN available
    BIT2:[index] 1= voice available
    BIT3:[index] 1= no nav signal available
    BIT4:[index] 1= DME transmitter at glide slope transmitter
    BIT5:[index] 1= no localizer backcourse
    BIT6:[index] 1= glideslope available
    BIT7:[index] 0= VOR, 1= Localizer

https://docs.flightsimulator.com/html/P ... #VOR1_CODE
 

[Ralph]

I can't find a type that subscribes correct. We'll have to look into that.

[SimPassion]

In any case it looks like I'm not able to read these values either in AM Beta 4.2.6 or in AM Final 4.1.6

Code: Select all

function pr_values(
					-- vor1code,
					gsraw,
					gsavail,
					locavail,
					locheading,
					locrwdesignhdg,
					locrwdesign
					)
	-- print("VOR1FLAGS : "..vor1code)
	print("GS_DEGREES : "..gsraw)
	print("GS_AVAILABLE : "..tostring(gsavail))
	print("LOC_AVAILABLE : "..tostring(locavail))
	print("LOC_HEADING : "..locheading)
	print("LOC_RW_DESIGNATOR_FULLID : "..locrwdesignhdg..locrwdesign)
	-- print("LOC_RW_DESIGNATOR : "..locrwdesign)
end

fs2020_variable_subscribe(
							-- "VOR1_CODE", "FLAGS",
							"NAV RAW GLIDE SLOPE", "number",
							"NAV HAS GLIDE SLOPE", "BOOL",
							"NAV HAS LOCALIZER", "BOOL",
							"NAV LOCALIZER", "number",
							"NAV LOC RUNWAY NUMBER", "string",
							"NAV LOC RUNWAY DESIGNATOR", "string",
							pr_values)

 

[Ralph]

I'm not sure about those, but the VOR1_CODE variable returns a couple of SimConnect exceptions.