May 11, 20188 yr Hello, System: P3D v 4.2 on Win 10 machine. I have the GNS 430w V2.1, and successfully installed it into the Alabeo PA32. I can use the GPS to navigate enroute (it drives the HSI needle), but the problem arises when I activate a GPS approach: the 430w continues to provide lateral guidance, but I get no glideslope (the 430w does change to LPV mode). Whereas in my Alabeo C404, I can fly a full LPV approach to minimums. The stock PA32 has both a 530 and a 430. I replaced the 430 with the Reality XP 430w using the Addon wizard, and again, it works fine for everything but APP. Might this have something to do with the stock 530 being present? I tried "installing" the Reality XP 530 (which I don't have), such that the 530 panel is dark, but same result. I could not find any avionics switch setting in the PA-32 cockpit that might route things differently. I looked at the configuration settings menu, but left it default as the HSI was working...did I miss ticking a box there? Something else? Thanks! Scott
May 12, 20188 yr Make sure that the 430 is set to NAV1 / COM1. You may have to disable the 530 if it wants to be NAV1 as well. Bert
May 12, 20188 yr Author 1 hour ago, Bert Pieke said: Make sure that the 430 is set to NAV1 / COM1. You may have to disable the 530 if it wants to be NAV1 as well. I did set it to Nav1, but didn’t disable the 530. By this you mean commenting it out in the panel.cfg file?
May 12, 20188 yr That is what I would do, but I do not have the airplane.. Maybe the HSI does not expect a vertical signal when driven by a GPS.. Bert
May 15, 20188 yr Author Solved! While surfing some other posts about GS issues I found his tidbit: Quote Have you tried "Connect GPS to VOR indicator" option? I hadn’t, since the HSI was the instrument in question, but apparently Alabeo didn’t code this quite right. Once I enabled this option - voila - a working GS 😄!
Archived
This topic is now archived and is closed to further replies.