OK, on to the next minor problem. Still loving the plane, but also still trying to sort out a few glitches.I have the Reality XP GNS 530 WAAS installed and configured and everything seemed to integrate well until the first time I flew a GPS/LPV approach in the 337. I've since tried several different approaches (locations that is), with the same results each time. All but one thing works - the GPS displays the LPV flag, the autopilot couples well in both axes and the HSI properly displays horizontal deflection, but I can never get it to display glideslope. The "barber pole" on the left side of the HSI stays on every time with no glideslope indicator displayed, though the autopilot will follow the virtual glideslope with great stability (and I assume accuracy based on how things look) right down to the runway.Note that ILS glideslope indication works gangbusters. The net result is that "Otto" can fly an LPV approach very well indeed, but I can't, and letting "Otto" do it blindly is spooky and absolutely no fun!.The same 530 configuration in the Carenado 210 works perfectly. Both were installed with their respective Carenado Reality XP integration tools, and configured with identical options through the Reality XP GNS WAAS config tool.Have any other 337 Reality XP users tried this? I'm hoping I've just missed flipping that one magic bit.Scott

There is hope! It works on my system..From the rxpgns.ini file:[GNS530]Popup=794AutoPilotMode=2Radios=1LinkCdiKey=OnAutoApproach=OffLinkToVor=On

Edited January 4, 201214 yr by Bert Pieke

LinkToVor=On

This appears to be the missing piece. Interesting that the Reality XP config utility doesn't generate this setting (and no option I've tried with it seems to) and that it doesn't appear to be needed on the 210. In the single approach I've tried, the AP also didn't capture the glideslope, though that's probably just coincidence. In any case, I'll gladly take the option of display with no AP over AP with no indicator.My FSX learning continues and there's more experimentation to come, but thanks once again for your guidance Bert. Brilliant!Scott

In the configurator, it is called Link Vor.. same thing..

In the configurator, it is called Link Vor.. same thing..

This appears to generate LinkVor=1 (or 2) or nothing if set to off, and links available CDI's. In the 210, I have this set to LinkVor=1 for the GNS 430 to link it to the CDI, but set to "off" for the 530 on both the 337 and 210 as I want to drive the HSI with the 530, not the CDI.I've flown several LPV approaches now and confirmed that LinkToVor=On does enable LPV glideslope on the HSI, but has somehow disrupted glideslope capture on the AP.I'll keep experimenting...Scott

Edited January 5, 201214 yr by tttocs

Not sure I understand the ins and outs, but linking the GNS to the VOR1 gauge(which in this case is the HSI) makes sense to me..So, LinkVor=1 or LinktoVor=On, same thing, seems to be the right setting.The older GNS versions used LinktoVor and it is still supported by the newer release..

my setting is[GNS530]Popup=15531AutoPilotMode=2Radios=1LinkCdiKey=OnAutoCdiMode=0AutoApproach=OffLinkVor=1For the GPS approach, I wonder if this is the correct procedure (it works fine):1. fly to IA in GPS mode (NAV), ALT hold2. When vertical guidance turns on, GA/GS turns on3. then press VOR/LOC to extinguish NAV, ALT still holding4. When "GS" is captured, ALT extinguishes and follows vertical guidance5. all the way downstep 3 is kinda like pressing "APP" on the Boeing AP.

Edited January 6, 201214 yr by kdfw__

LinkVor=1

Following my last exchange with Bert, I regenerated the file with the config tool and this is what I ended up with. And it works too... that is, it allows glideslope to be displayed. This still seems odd to my twisted mind, as it seems like this ought to couple to the 1st (only) CDI, and in fact that's how it seem to work in my 210 where I have LinkVor=1 set on the 430 (second) GPS.In any case:

4. When "GS" is captured, ALT extinguishes and follows vertical guidance

Once I've set LinkVor=1, this is the step which no longer works. I seem to get either the AP able to capture glideslope but no display (no LinkVOR) or display but no AP glideslope capture (LinkVor=1, or LinkToVor=ON). Again, curiously with either configuration, ILS approaches work flawlessly. Just shot the relatively new ILS 16 at Nanaimo, BC (ORBX PNW scenery and June 2011 nav data) in both modes without any problems. Doing the RNAV (GNSS) 16? Either/or.At this point I'm ready to just let it go and fly for a while. :-)Scott

Edited January 6, 201214 yr by tttocs

At this point I'm ready to just let it go and fly for a while. :-)

And so I did. Took a break, flew other planes or flew this one without LPV approaches and let it go. When I got back in the mood to bang my head against the wall again, I deleted the 337's RXPGNS.ini, ran the Reality XP integration tool to set things back to the default 530, and brought up the airplane in this mode to confirm that everything was back to defaults. I also deleted the 530's non vol mem file, just to be doubly sure. I then started from scratch, building a new .ini (with LinkVor=1 set), then ran the Reality XP integration tool and loaded up a flight plan with LPV approach.And... <insert appropriate drum roll or whatever>, it all worked perfectly.The moral of the story is one that I've really begun to internalize after several similar episodes in my short time flight simming: when all else fails, get rid of all existing config files completely, get everything back to defaults and start fresh.Onward to the next mystery,Scott

And... , it all worked perfectly.

And did so for about 4 approaches before reverting right back to previous behavior. I'm outa ideas.Arrgggh! :-(Scott

Do you possibly have two ini files... one in the panel folder and one in the aircraft folder?If so, the one in the panel folder will take over.

Do you possibly have two ini files... one in the panel folder and one in the aircraft folder?

Good question, as I had exactly this dueling .ini problem with my RealAir Duke, due to the Duke's integration app creating the file in the panel folder. After discovering this, deleting the one in the aircraft folder and integrating what I'd done there with what RealAir's config had done in the panel folder, some minor issues I was having with the Duke cleared up nicely.With the 337, however, the only one I have is the one in the aircraft folder. The last few LPV approaches I've tried have worked just fine again (and ILS approaches continue to work without any issues). Still trying to understand why things sometimes fall apart, but thanks for the excellent suggestion. With each of these exchanges, I learn a little more.Scott

Hey folks,

I know this is an old, and still unresolved thread...but, I'm interested in the concept of the coupled LPV approach.  Flying the Lancair Reality, I can couple the ILS without problems, but not LPV using the RXP 530.  It shows the glideslope, but the autopilot won't couple to it.  Strangely with the default MSFS GPS in the panel, you can couple and fly the GPS approach down the GS.  Any ideas?  I've also been flying a Carenado A36 that demonstrates strange/inconsistant behavior when coupled to the RXP 430.  Sometimes it will descend on the ILS GS.  Sometimes it won;t. It never descends on GPS LPV,and infact never gives a GS display on the AI gage. It just hangs at intercept alt.  Thanks in advance for your ideas.  Bob

Bob,

 

Actually my problem has long since been resolved, it just never got reflected in this old thread.  The key for flying a coupled LPV approach with the RXP 430/530 is generally simple - don't engage approach mode on the autopilot until after you see the glideslope come alive.  Depending on how you intercept, this will often occur after you've turned on to the final approach course, usually sometime after the IF.  Many will engage approach mode too early - if you do so, the autopilot will never capture the virtual glideslope.

 

Scott

Hi Bob,

 

The RealAir Lancair will fly LPV approaches, for sure.

 

Try flying out of KTPA.. stay at 2000 ft, select and activate the RNAV approach

to runway 36L (or 01L if you have newer navdata).  Use PIE as the transition point.

 

With the autopilot coupled in NAV and ALT modes, just sit back and watch..

 

When the glideslope activates on the HSI, push the APR button on the autopilot - that is it!

 

Regarding the A36, I've got a mod to get the Aspen avionics to support LPV approaches.

Send me a PM with your email address if you would like a copy.