NAV mode keeps changing to ROL with Non-GPS Avionics
-
@RPGamerous It was from PAWG Wrangell to PAKT Ketchikan. VOR used was mainly Level Island 116.5. Cruise was at 7000 ft. However, It also reverted to ROL when I was on the ILS 11(?) approach into PAKT. Made it interesting with IFR conditions until 500' AGL, lol.
As mentioned above, also got similar behavior in the Duke, where it switched to HDG mode instead.
I tried monitoring some of the BKSQ VOR-Related LVARs in SPAD; I might dig into that a bit more to look for a pattern.
I briefly tried the same flight in the BaE 146, no cutouts, but that was late.
I'll try things again tonight.
@SteveKane said in NAV mode keeps changing to ROL with Non-GPS Avionics:
I tried monitoring some of the BKSQ VOR-Related LVARs in SPAD; I might dig into that a bit more to look for a pattern.
Just trying to save you some time as you're looking into this, the signal degradation system is "for your eyes only" and has nothing to do with the autopilot behavior. You might still find some useful information from the L:Vars, but none of it will be causal. Just trying to help, since you're willing to look into this!
-
@SteveKane said in NAV mode keeps changing to ROL with Non-GPS Avionics:
I tried monitoring some of the BKSQ VOR-Related LVARs in SPAD; I might dig into that a bit more to look for a pattern.
Just trying to save you some time as you're looking into this, the signal degradation system is "for your eyes only" and has nothing to do with the autopilot behavior. You might still find some useful information from the L:Vars, but none of it will be causal. Just trying to help, since you're willing to look into this!
-
@SteveKane said in NAV mode keeps changing to ROL with Non-GPS Avionics:
I tried monitoring some of the BKSQ VOR-Related LVARs in SPAD; I might dig into that a bit more to look for a pattern.
Just trying to save you some time as you're looking into this, the signal degradation system is "for your eyes only" and has nothing to do with the autopilot behavior. You might still find some useful information from the L:Vars, but none of it will be causal. Just trying to help, since you're willing to look into this!
@Black-Square said in NAV mode keeps changing to ROL with Non-GPS Avionics:
Just trying to save you some time as you're looking into this, the signal degradation system is "for your eyes only" and has nothing to do with the autopilot behavior.
Anecdotally, I have seen this. How does/would a real autopilot handle that sort of signal oscillation?
-
@Black-Square Thanks for the 411.
Is there an LVAR I can monitor that'll show whether the KAP140 Autopilot is in "ROL" mode?
@SteveKane You can find all of the relevant SimVars here. For roll mode, I would monitor both
AUTOPILOT BANK HOLDandAUTOPILOT WING LEVELER. I'm not sure exactly when one is activated over the other, so I just monitor both in all my code. -
I've been doing some testing. The plot thickens:
- This behavior happens in either dual KX 155B units, or TDS GTN750/650 when in VLOC mode.
- It happens everywhere, not just Alaska.
- The same behavior happens in the Duke, though it changes from NAV to HDG mode. This behavior is across models, which we know from the Starship thread.
- When in GPS mode, everything works fine, as I'd expect.
- Here's where it gets interesting. I use SPAD for all of my planes. For a test, I restarted the sim, spawned the 208 on the runway, did NOT launch Spad but instead "moused it" for everything. No issues whatsoever, stayed in NAV tracking a VOR, departing KPHX 07L, and simply tracking the nearby PXR VOR to the east for 45+ miles.
- Turned around back to PXR, started Spad, briefly switched from NAV to HDG back to NAV just for kicks, and a couple of minutes later, ROL mode.
- In SPAD, I've tried both the standard "K:AP_xxx" events as well as the "H:KAP140_PUSH_xxx" commands for NAV/HDG/etc., no difference: I get ROL mode using each.
- If I start a test flight using SPAD, eventually get the NAV->ROL, and I turn off SPAD, the NAV->ROL issue still occurs.
It seems that simply starting SPAD (with my rather extensive profile) correlates with this behavior.
I'll look into this some more and report back, perhaps starting with an empty Spad profile and incrementally adding things.
(In the meantime, I also might write some Spad code to detect when it goes from NAV to ROL and have it go back to NAV, though that might have some unintended side effects)
-
I've been doing some testing. The plot thickens:
- This behavior happens in either dual KX 155B units, or TDS GTN750/650 when in VLOC mode.
- It happens everywhere, not just Alaska.
- The same behavior happens in the Duke, though it changes from NAV to HDG mode. This behavior is across models, which we know from the Starship thread.
- When in GPS mode, everything works fine, as I'd expect.
- Here's where it gets interesting. I use SPAD for all of my planes. For a test, I restarted the sim, spawned the 208 on the runway, did NOT launch Spad but instead "moused it" for everything. No issues whatsoever, stayed in NAV tracking a VOR, departing KPHX 07L, and simply tracking the nearby PXR VOR to the east for 45+ miles.
- Turned around back to PXR, started Spad, briefly switched from NAV to HDG back to NAV just for kicks, and a couple of minutes later, ROL mode.
- In SPAD, I've tried both the standard "K:AP_xxx" events as well as the "H:KAP140_PUSH_xxx" commands for NAV/HDG/etc., no difference: I get ROL mode using each.
- If I start a test flight using SPAD, eventually get the NAV->ROL, and I turn off SPAD, the NAV->ROL issue still occurs.
It seems that simply starting SPAD (with my rather extensive profile) correlates with this behavior.
I'll look into this some more and report back, perhaps starting with an empty Spad profile and incrementally adding things.
(In the meantime, I also might write some Spad code to detect when it goes from NAV to ROL and have it go back to NAV, though that might have some unintended side effects)
@SteveKane Very interesting results!! I will eagerly await more testing! This could explain why I have never seen this, since I don't use any 3rd party hardware applications that might be polling the variables or causing whatever hiccup is related to this in MSFS 2024.
-
Yet another update...someone in the Baron/Bonanza thread in the MSFS official forum mentioned that those planes have this issue (using FSUIPC), and someone else mentioned that the Blackbird C310 also has the same NAV -> ROL problem. I was just able to reproduce the issue in the C310. I am using SPAD, and may try flying without it to see if that correlates as well.
Regardless, I'll shortly file a bug report on the offical forum to see where it goes, since it seems like a Sim problem vice an airplane problem.
-
Yet another update...someone in the Baron/Bonanza thread in the MSFS official forum mentioned that those planes have this issue (using FSUIPC), and someone else mentioned that the Blackbird C310 also has the same NAV -> ROL problem. I was just able to reproduce the issue in the C310. I am using SPAD, and may try flying without it to see if that correlates as well.
Regardless, I'll shortly file a bug report on the offical forum to see where it goes, since it seems like a Sim problem vice an airplane problem.
@SteveKane Thank you for keeping me updated! I feel guilty being excited that it doesn't seem to be the fault of my software, but I will be here to help troubleshoot if you guys seen any while looking into FSUIPC. Please keep me posted!
-
Hello, I'm the one who experiences NAV disengagement using FSUIPC.
I want to do some test and switched on logging in FSUIPC to see what's going on when this happens. FSUIPC then logs all events and/or input events occuring in MSFS (not only the ones it by itself triggeres).Soon it happened in the Bonanza and FSUIPC logged a change in Simulator Variable 'AUTOPILOT NAV 1 LOCK' from 1 to 0.
