And yes, there are ways to put hidden ILS's into every airport and make the default autopilot track them.

Yes, but are they accurate WAAS approaches and updateable as the F1 Mustang is?

I just want to iterate... the point to my posts is this: It's easily doable, not really that complex.

I just want to iterate... the point to my posts is this: It's easily doable, not really that complex.

OK, Ed, I'll take the bait....Can I take an XML coded autopilot and change the coding so thatwith GPS selected, rather than NAV, the APPR button would make it follow the vertical guidance that shows up on the HSI(in this case provided by the GNS530W) just as it would do if following an ILS glideslope?

OK, Ed, I'll take the bait....Can I take an XML coded autopilot and change the coding so thatwith GPS selected, rather than NAV, the APPR button would make it follow the vertical guidance that shows up on the HSI(in this case provided by the GNS530W) just as it would do if following an ILS glideslope?

That's actually what one would call a 'loaded question'.I have no idea what variable(s) RXP is using to 'drive' anything so I can't answer your question.

That's actually what one would call a 'loaded question'.I have no idea what variable(s) RXP is using to 'drive' anything so I can't answer your question.

OK... the GNS530W will drive the "glideslope indicator" on the default FSX Baron HSI... when the autopilot is set to NAV and the NAV/GPS switch is set to GPS.That looks like standard FSX variables to me. (Way out on a limb here..) If that is indeed true, what would be the answer?

Bert, I don't have the 530W but what you describe sounds like Nav Mode is being used with an ILS Freq and the 530W is displaying GS but not actually "driving" anything despite the NAV/GPS Switch.

OK... the GNS530W will drive the "glideslope indicator" on the default FSX Baron HSI... when the autopilot is set to NAV and the NAV/GPS switch is set to GPS.That looks like standard FSX variables to me. (Way out on a limb here..) If that is indeed true, what would be the answer?

Ed is correct, its doable with the FS autopilot , its not all that complicated. Everything you need to make it happen is in the SDK.Regards.Ernie.

OK... the GNS530W will drive the "glideslope indicator" on the default FSX Baron HSI... when the autopilot is set to NAV and the NAV/GPS switch is set to GPS.That looks like standard FSX variables to me. (Way out on a limb here..) If that is indeed true, what would be the answer?

The answer would be based on assumptions... but, here goes: If it's driving the default GS needle indication, then RXP has hacked into FS and is forcing the value.I just flew a flight and let the VNAV in the Citation X fly the aircraft down to 50ft above the runway... while the math for VNAV isn't part of FS... it's something RXP has to already be doing (see next paragraph) to calculate the WAAS glideslope. It doesn't take much more effort to implement the vertical aspect of WAAS in FS without having to write a custom autopilot.Now, since I'm making assumptions... I'm willing to assume the real reason it wasn't done is because there's absolutely zero code written by RXP aside from the gauge interface for the Garmin trainer.

Ed is correct, its doable with the FS autopilot , its not all that complicated. Everything you need to make it happen is in the SDK.Regards.Ernie.

OK, time to move this to the Panel Design Forum.Hopefully I'll see you gents over there :( I'm going to try to take the same signal that drives the Glideslope needleand feed it to the autopilot as the ILS glideslope input and see what happens.

Actually, it's already been done ;)Last fall I prototyped a gauge that adds an LPV lock to FSX

The Eaglesoft Citation X uses the default FS autopilot interface to control a vertical decent path. No hack needed. No PID required either, in fact... controlling a vertical descent path is so simple a PID controller is like using a nuclear bomb to kill a common housefly (in my opinion).If RXP is driving the default FS glideslope needle... there's a hack involved in that. I know of no way to legitimately override it's value.

Actually, it's already been done ;)Last fall I prototyped a gauge that adds an LPV lock to FSX’s autopilot.Possibly not exactly as you describe…a custom PID controller is needed and it simply overrides FSX’s AP pitch control.It works great…just doesn’t have a lot of polish…or hard testing yet…but it will fly right to the threshold (if you like).The PID was written as part of an autopilot for a commercial aircraft add-on (VANS RV7).But, the intention has always been to release the WAAS LPV gauge itself as freeware.I think an LPV solution is imminent one way or the other…but I'd be happy to share my work to date.The gauge is written in XML...but I'd like it translated to C...with a data file to store tuning parameters.DannyBTW, RXP GNS isn’t bundled with an autopilot…if it was, I’m sure Jean-Luc would have include an LPV lock.But, patching FSX's AP like above is "hacky" and not exactly to RXP's standards...IMO.

I'm definitely going to need help with this - have sent you a PM.PS. Over to the Panel Design forum..The thing is: RXP actually has a nice STEC55X autopilot packaged with their FLN gauges,but it does not have LPV capability.

...PID controller is like using a nuclear bomb to kill a common housefly (in my opinion).

...but it's three lines of math :(

Actually our CX2.0 has an FMS. :(

I don