Autopilot modes
-
It's possible that the HDG indicator not lighting up is just a momentary issue with the GPS hotswapping. I've seen that happen in rare occasions when switching units a lot while testing. If it's more persistent, just make sure that you have the most up-to-date versions of all of your GPS software, regardless of whether you're using it at the time or not.
As for the GS annunciator, that's all it is, actually. Despite appearances, it is not a button. It will illuminate when the GS has been captured in approach mode.
-
@Black-Square Yeah the HDG isn't just momentary, it's always dark. I had a potientially old free version of the PMS GTN installed, I disabled that for now and will re-test. But I never swapped GPS units, it defaulted to the TDS and I left it there from the beginning.
And I looked at the manual mysticfm posted, LOL that thing is as old as me :) But it talks about manual GS coupling by pressing the button, one scenario is GS interception from above. Page 32, step 2.
-
The PMS GTN was the cause, approach mode engaged and HDG wasn't dark during flight.
Quick other question @Black-Square, I looked at the pitch trim knob L-var from the manual and used that in my miniFCU profile and that worked fine so far. I adjusted it by incrementing and decrementing the number in the lvar from Mobiflight. I was working on a refinement today and might have gotten that value out of the -15 to +15 range. Looks like the aircraft didn't like that. The ATT pitch control of the auto pilot stopped working completely and I had to hand fly the last half hour :)
Is there a K:PITCH_KNOB_DEC and INC event defined that's not in the manual? Otherwise I have to limit the value, but the syntax for that is a nightmare tbh and I'm not sure what other side-effects changing the value of Lvar directly might have.
-
Ok more testing, just dumping this all in here to help diagnose. Did another test flight for my mobiflight profile, limiting it did the trick so that's working fine.
But the APPR mode wouldn't work again, also HDG not lighting up again. So I guess not caused by the PMS GTN after all. Not sure if it matters if the tds application is set to auto-start in the exe.xml file. I removed it from there as it uses quite a bit of resources, even if you don't load an aircraft with it equipped. So it could be the timing of when I'm remembering to start it.
I was approaching an ILS with it not working, so I tried quickly swapping to the WT 530/430 ... also not working. Then I swapped to the KNS (I believe, sorry can't remember, the two top-most options). With them selected the approach mode worked and HDG illuminated again.
All this was a level approach segment before the FAF already aligned with the LOC, so the easiest possible APPR engage/coupling possible. The glide came in just as I activated the last config and it coupled immediately.
-
I went with these to make sure to keep them within limits, and for me down was +
Down:
(L:var_AP_PitchKnob) 0.5 + 14.5 min (>L:var_AP_PitchKnob)
Up:
(L:var_AP_PitchKnob) 0.5 - -14.5 max (>L:var_AP_PitchKnob)I gave it some extra margin to the 15 limit stated in the manual, even though I saw it working outside that range. Once I scrolled way past and it broke the auto-pilot :)
-
-
Firstly, props to BlackSquare. Your twin-piston and turboprops are just dripping with immersion. Your products are usually the first I consider using when flying the MSFS world.
I do question how the GA mode is working, or at least how to cancel or exit this mode. It seems I've found the only way is by using the GA binding in MSFS to cancel or exit this mode. Pushing ATT mode doesn't work, and at least to a safety standpoint should. Yes initially pitching up a set attitude sounds correct, but the pilot should be able to change modes by a button press on the AP mode panel. Any insight on this would be welcome.
-
Sorry. "Dripping" is not the word I meant to use. I meant to say oozing immersion.
