kdfw__

LPV guidance not showing using GPS500

Recommended Posts

issue: when using GPS500, not getting the LPV guidance, GNS530 shows the LPV guidance.

this one is easy to replicate, go to KTKI rwy17 and tune to ILS, should see the loc/gs needles and activate RNAV17, should also see LPV needles sitting at the end of rwy.

using GPS500, no gs when ILS is tuned, regardless of the nav/gps switch if LinkVor = true.  if LinkVor=false, then ILS gs needle appears.  RNAV needle does not show up regardless of nav/gps switch or LinkVor setting.

using the GNS530, if CDI=gps and RNAV is activated, gs shows up.  If CDI=vloc and ILS is tuned, gs shows up.  this is with CDI button connected to the nav/gps switch setting = true (if false, the CDI and nav/gps switch doesn't sync).  

It looks like the nav variables are not overwritten by the GPS500 to animate the gs/loc.

 

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

in addition to the issue above, i'm not able to change the bezel brightness.  according to the manual on p6, the bezel brightness can be adjusted independently from screen brightness (screen brightness slider works).

right now, the bezel is full bright emmissive at night when the gauge is placed in the vc (not pop up but on the panel surface).  ideally, the bezel should be pretty much black with button backlight (used to be green on the original rxp gauge but now white?).

thanks.

 

 

 

 

Share this post


Link to post
Share on other sites

Hi, thank you for your feedback.

We're reviewing the 'VOR' variables since the 2.3.1 release to make sure we didn't introduce a 'logic' error in how we manage them. 

As for the 'brightness', the issue you are having looks like it is a 3D model polygon surface type, which might be configured as 'emissive' (or similar). Otherwise, the gauge bezel integral lighting should be working fine and the bezel shouldn't be lit up, only the buttons and knobs integral lighting, which is green.

Speaking of the lighting, you might want to first assess it is working properly in a 2D popup window, and you might also notice thanks to our rendering technology the green lighting is barely visible during daylight, and lettering appears more white, while it is progressively becoming visible as night fall, while progressively appearing more green!

Share this post


Link to post
Share on other sites

Hi, a quick update on the 'needle' issue: we've had no time to test this specifically today, because we've corrected other code related to the VOR needle (in fact, related to all our variable overrides):

It might be the issue you are having is directly related to this as well, so just keep tight, we'll test this specifically tomorrow and report.

Share this post


Link to post
Share on other sites

HI Jean-Luc,

thanks for looking into the needle issue.  

regarding the bezel lighting, this is what i'm seeing:

at night with panel/guague lights on (not the vc flood lights), the light maps turn on and i get the 1st one with the button brightness=100.  the bezel rendered on the vc is bright, 2d popup is not particularly dark (i recall the rxp v1 pop up looked darker at night).

rxp1.jpg

the 2nd one here is with brightness=0, maybe button brightness changed but the bezel itself didn't change.  the vc gauge is unchanged as well, bright gray bezel.
rxp2.jpg

 

Share this post


Link to post
Share on other sites

A picture is worth a 1000 words!

First, the "Buttons" brightness is only for adjusting the integral lighting, that is the amount of light glowing though the buttons which allow to read the labels at night.

The bezel is only lit up by the panel lights.

Now there are two different cases: 2D panel/popup and VC.

2D panel: what controls the bezel lighting is a combination of panel.cfg "light" section settings, as well as popup window "light" settings. The gauge is designed to be almost agnostic to these, at least as much as possible, and renders dark like in your screenshots in most situations.

VC: what controls the bezel lighting is the polygon materials as defined by the aircraft 3D model. There is nothing we can do about this, because it is the 3D material, not the gauge, which controls this (the gauge only has limited possibilities in the VC).

I see nothing wrong in the popup window on your screenshots. At night, it properly gives the illusion of slight lighting on the edges of the screen by the screen itself, other shadows and highlights are moderate. At daylight, the same bezel looks correct as well, because these shadows and highlights are slightly but effectively accentuated by FS.

However, the VC is definitely not good looking. What about trying in another aircraft VC to compare?

Share this post


Link to post
Share on other sites

Hi Jean-Luc,

The VC gauge--if you look at the standard fsx lear jet pfd gauge construction in Lear_45_XML.cab (or p3d's Maule_M7_260C.cab), you'll find bitmaps with "_night.bmp" suffix.  this forces the sim to render the "_night.bmp" at night time automatically.  So at night, a dark bezel/gauges can be displayed and during day time, the standard bezel/gauges can be displayed. 

I'm sure your bezel/button .bmps in the rxp.dll contains the daytime .bmp but i think you should be able to add a night version of the bezel/buttons like it's done on the xml gauges here.  the sim may not automatically select the day/night texture for a dll gauge but if you can conditionally select the .bmp off the simulator's time (dawn/day/dusk/night variables), this should be doable.  

mdf_nightmap.jpg

 

Share this post


Link to post
Share on other sites

Hi Jean-Luc,

just tried v2.3.3 but behavior is the same for gps500.  gns530 is working the same as before, properly see gs for lpv and nav. 

as for the bezel suggestion i made above, hope you can give it some thought.  perhaps easiest route is to have a bezel xml gauge which has the day/night .bmp with click spots and display the gns530 as screen only.

Share this post


Link to post
Share on other sites

Strangely, the RXP GPS500 I use in the RealAir B60, shows the LPV glidepath just fine..

Share this post


Link to post
Share on other sites

Hi Bert,

i tried using the realair tduke v1.2 and i'm not seeing the LPV needle with the gps500.  nav1 gs needle works if 'connect to cdi mode to nav/gps=false' but regardless of this and the other settings, no luck on LPV here...

 

Share this post


Link to post
Share on other sites

I wonder if the GPS500 is controlling the autopilot in your setup..

Is the GPS/NAV switch in the panel set to GPS?

When you first power it up, on the initial "Testpage", do the HSI needles deflect correctly?

 

 

Share this post


Link to post
Share on other sites

gps500 is coupling to the ap, i see the needles deflect at power on if i set 'connect gps to vor indicator.'  vcdi/hcdi halfway as it should.

gps nav is working, follows track and procedures fine.  just no LPV with the 500.  

gns530 on the other hand is working perfectly fine.

 

i checked the win event log and see two errors each time the gps is turned on and off, always with exception codes 05 and 41d:

turn on/off first error

Faulting application name: G530SIM.exe, version: 0.0.0.0, time stamp: 0x4bff0a69
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x2370
Faulting application start time: 0x01d335755c43fb69
Faulting application path: C:\Program Files (x86)\Garmin\GNS Trainer\GNS\G530SIM.exe
Faulting module path: unknown
Report Id: 3de96b48-5c10-4a80-8c35-96cb739c1377
Faulting package full name: 
Faulting package-relative application ID: 

turn on/off 2nd error

Faulting application name: G530SIM.exe, version: 0.0.0.0, time stamp: 0x4bff0a69
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x6a17c1ed
Faulting process id: 0x2370
Faulting application start time: 0x01d335755c43fb69
Faulting application path: C:\Program Files (x86)\Garmin\GNS Trainer\GNS\G530SIM.exe
Faulting module path: unknown
Report Id: fe76743c-f351-4244-8a74-1d31912cbc22
Faulting package full name: 
Faulting package-relative application ID: turn on/off 2nd error

 

Share this post


Link to post
Share on other sites
28 minutes ago, kdfw__ said:

gps nav is working, follows track and procedures fine.  just no LPV with the 500.  

Hi, just to make sure I understand: the needles work, the A/P works, the only thing not working as 'LPV' is what?

1) there is no vertical indication on the HSI?

2) there is a vertical indication on the HSI but the A/P is not following it?

 

As for the errors reported, we'll further look into this. What is puzzling is the 'offset' value in the error report, which leads me to believe there might be something going on with an anti-virus, or another process/module/gauge interacting somehow. Ideally, you'd try on an aircraft with no other gauge than default FS gauges to compare if you still get the error reports.

Also, I fail to find in the discussion: what is your Fsim version?

Share this post


Link to post
Share on other sites

Not sure what the error messages mean.. but try this test and report back.

GPS500 in the RealAir Duke.. KTPA, load and activate the RNAV 01L LPV approach via PIE.

Fly the approach on autopilot at 2000 ft AGL in NAV mode.

After the FITPA teardrop hold, and onto final, the TERM indication on the GPS should switch to LPV.

The Glideslope indicators on the HSI should come on.

Then you press APR, and wait for the airplane to intercept the glidepath and pitch down..

At what point does this sequence fail?

  • Upvote 1

Share this post


Link to post
Share on other sites
3 hours ago, RXP said:

Hi, just to make sure I understand: the needles work, the A/P works, the only thing not working as 'LPV' is what?

1) there is no vertical indication on the HSI?

2) there is a vertical indication on the HSI but the A/P is not following it?

 

As for the errors reported, we'll further look into this. What is puzzling is the 'offset' value in the error report, which leads me to believe there might be something going on with an anti-virus, or another process/module/gauge interacting somehow. Ideally, you'd try on an aircraft with no other gauge than default FS gauges to compare if you still get the error reports.

Also, I fail to find in the discussion: what is your Fsim version?

first of all, it's p3dv4 hf1.  

i thought other than the lpv mode, gps500 was at least tracking the flt pln but i just tried again and it seems to just point north 360 when nav is engaged (with gps/nav sw=gps).  maybe the behavior changed with the recent updates, i can't tell.

so here's what i'm seeing on my end with the current version:

1) gps500 isn't able to track plan or lpv 

2) gps500 on power up deflects hcdi/vcdi needles on the adi but once out of self test, flag comes down.

3) swap to gns530 on the same aircraft works fine.

tried this on both the tduke and xproto glj25.

g530sim.exe is on the list of excluded processes from the ms av realtime scan.

 

Share this post


Link to post
Share on other sites
8 hours ago, kdfw__ said:

p3dv4 hf1.  

What version is this? Can you cross check the "My Documents\rxpGns.gau.log" file contains something like "oto not supported..." followed with your version?

Share this post


Link to post
Share on other sites
11 hours ago, kdfw__ said:

3) swap to gns530 on the same aircraft works fine.

 

 

Is this a panel.cfg change,  or do you have both installed at the same time?

I have the GPS500 installed in the B60 Duke and it operates exactly like a GNS530 (minus the radios).

 

Share this post


Link to post
Share on other sites
11 hours ago, RXP said:

What version is this? Can you cross check the "My Documents\rxpGns.gau.log" file contains something like "oto not supported..." followed with your version?

p3d is 4.0.28.21686

log file

17/09/25 04:25:41.864 03704 -    ] # rxpGNS2.dll version 2.3.3.0
17/09/25 04:25:41.869 03704 INFO ] 

Share this post


Link to post
Share on other sites
8 hours ago, Bert Pieke said:

Is this a panel.cfg change,  or do you have both installed at the same time?

I have the GPS500 installed in the B60 Duke and it operates exactly like a GNS530 (minus the radios).

 

panel.cfg change.  

i guess when you operate the gps500, you'll not have the vloc button so using the gps/nav switch, right?  

Share this post


Link to post
Share on other sites

Correct...

When I power up the Duke and move to the test page on the GPS500, the HSI needles

deflect when the NAV/GPS switch is in the GPS position.  When I move the switch to NAV, the needles

go back.

Share this post


Link to post
Share on other sites

likewise, i see the gs/loc needles deflect in self test when the gps/nav=gps, no deflection when gps/nav=nav.  

Share this post


Link to post
Share on other sites
49 minutes ago, kdfw__ said:

likewise, i see the gs/loc needles deflect in self test when the gps/nav=gps, no deflection when gps/nav=nav.  

In that case, the GPS should drive the autopilot in GPS mode.. I am puzzled that it would not work for you..

Share this post


Link to post
Share on other sites

Unfortunately, I'm at a loss here as well for now. It there any difference whether or not you try with a DTO only, or a flight plan (for example an activated approach to an airport)?

Share this post


Link to post
Share on other sites
On 9/26/2017 at 6:31 AM, RXP said:

Unfortunately, I'm at a loss here as well for now. It there any difference whether or not you try with a DTO only, or a flight plan (for example an activated approach to an airport)?

Jean-Luc, Bert,

reran the 'setup aircraft' from 'addons' pulldown on the tduke and for some reason the tduke is now able to fully function with the gps500.  i didn't save off the pre-edit rxp config file so not sure what exactly changed to make it work.  

so that's good news.

now, regarding the bezel at night--is there some thought as to adding a dark bezel .bmp for gauge placed in the vcockpit section?  please see https://www.avsim.com/forums/topic/520205-lpv-guidance-not-showing-using-gps500/?do=findComment&comment=3713683

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now