Century IV autopilot, altitude capture questions
-
Just want to add: the "Control AP Pitch with Hardware events" option is not described in the manual and I had the same experience. If it is enabled, I can't adjust the pitch angle for ATT mode using external software and hardware such as spad.next and my Honeycomb Alpha. If it is disabled, I was able to (and it took several hours of debugging to figure this out!) It seems the behaviour of this option is reversed to what one would expect. Hope this helps someone...
-
Just want to add: the "Control AP Pitch with Hardware events" option is not described in the manual and I had the same experience. If it is enabled, I can't adjust the pitch angle for ATT mode using external software and hardware such as spad.next and my Honeycomb Alpha. If it is disabled, I was able to (and it took several hours of debugging to figure this out!) It seems the behaviour of this option is reversed to what one would expect. Hope this helps someone...
@PAStime For my reference more than anyone else's, here is what it currently says in the manual:
An option has been added to control the autopilot pitch knob with hardware controls. When “Control AP Pitch with Hardware Events” is selected on the options page of the tablet interface, “AP_PITCH_REF_INC_DN”, “AP_PITCH_REF_INC_UP”, and “AP_PITCH_REF_SET” can be used to adjust the autopilot’s pitch holding reference.
If you would like to suggest a way to clarify this statement, or change the name of the option for better clarity, I would really appreciate it. This wouldn't be the first time I have accepted a much better description from a user on this forum.
-
@PAStime For my reference more than anyone else's, here is what it currently says in the manual:
An option has been added to control the autopilot pitch knob with hardware controls. When “Control AP Pitch with Hardware Events” is selected on the options page of the tablet interface, “AP_PITCH_REF_INC_DN”, “AP_PITCH_REF_INC_UP”, and “AP_PITCH_REF_SET” can be used to adjust the autopilot’s pitch holding reference.
If you would like to suggest a way to clarify this statement, or change the name of the option for better clarity, I would really appreciate it. This wouldn't be the first time I have accepted a much better description from a user on this forum.
@Black-Square said in Century IV autopilot, altitude capture questions:
AP_PITCH_REF_INC_UP
Aha, I misssed it, thanks. That text is in the Change Log, which I did not assume was something I needed to read.
The behaviour which I found non-intuitive regarding the tablet's "Control AP Pitch with Hardware events" setting, is as follows:
- With this option enabled, I am unable to make changes to L:var_AP_PitchKnob (page 143 of the Duke Turbine manual)
- With this option disabled, I am able to make changes to the this variable and see it change in the cockpit
Well, at least after a few hours of trying stuff, this seemed to be the fix to make my spad.next configuration able to set the desired pitch for ATT mode. Should I instead use these: AP_PITCH_REF_INC_DN”, “AP_PITCH_REF_INC_UP”, and “AP_PITCH_REF_SET”?
Thanks and have a great weekend.
-
Another altitude related question.
At 1:27 of this video https://www.twitch.tv/videos/2699364673 , AP switches to GS mode despite APP mode isn't armed. It is a LOC/DME approach. I'm unable to see glideslope indications on the panel.
What may be noteworthy is that the GS capture could coincide with a 3 degree glideslope if it was there.
I'm using the CWS script for ATT mode here.
You can probably ignore that start of the vid as I'm trying to intercept the localizer in APPR mode.
I've tried to find out from the real manual if I misconfigured the plane in this scenario. Did I?
-
Another altitude related question.
At 1:27 of this video https://www.twitch.tv/videos/2699364673 , AP switches to GS mode despite APP mode isn't armed. It is a LOC/DME approach. I'm unable to see glideslope indications on the panel.
What may be noteworthy is that the GS capture could coincide with a 3 degree glideslope if it was there.
I'm using the CWS script for ATT mode here.
You can probably ignore that start of the vid as I'm trying to intercept the localizer in APPR mode.
I've tried to find out from the real manual if I misconfigured the plane in this scenario. Did I?
-
@Black-Square said in Century IV autopilot, altitude capture questions:
AP_PITCH_REF_INC_UP
Aha, I misssed it, thanks. That text is in the Change Log, which I did not assume was something I needed to read.
The behaviour which I found non-intuitive regarding the tablet's "Control AP Pitch with Hardware events" setting, is as follows:
- With this option enabled, I am unable to make changes to L:var_AP_PitchKnob (page 143 of the Duke Turbine manual)
- With this option disabled, I am able to make changes to the this variable and see it change in the cockpit
Well, at least after a few hours of trying stuff, this seemed to be the fix to make my spad.next configuration able to set the desired pitch for ATT mode. Should I instead use these: AP_PITCH_REF_INC_DN”, “AP_PITCH_REF_INC_UP”, and “AP_PITCH_REF_SET”?
Thanks and have a great weekend.
Also, but likely unrelated, I am finding the state of my Turbine Duke is not being saved from session to session, despite completed flights and orderly shutdown of the sim. This "Control AP Pitch with Hardware events" tablet setting always needs to be changed, and the fuel levels of my previous flight are not what I left the plane at.
Still a great plane to fly!
-
Also, but likely unrelated, I am finding the state of my Turbine Duke is not being saved from session to session, despite completed flights and orderly shutdown of the sim. This "Control AP Pitch with Hardware events" tablet setting always needs to be changed, and the fuel levels of my previous flight are not what I left the plane at.
Still a great plane to fly!
@PAStime Unfortunately, it's almost daily now that I have to refer a user to one of the many threads here or on the MSFS Official Forums about how Asobo completely bugged state saving with SU4. Thankfully we have been told that it will be fixed for SU5.
-
@vliah There are unfortunately some strange bugs that are currently linked with the kln90B and pms750 gps units since SU4. I have removed both and had no issues since.
@SadBucket Roger that. If this clip helps to narrow the bug down, it happened at VORDME zone of confusion at this time https://www.twitch.tv/videos/2705523736
-
@SadBucket Roger that. If this clip helps to narrow the bug down, it happened at VORDME zone of confusion at this time https://www.twitch.tv/videos/2705523736
@vliah Same thing happened to me recently, I posted it here: https://community.justflight.com/topic/10047/finally-got-an-ils-issue/5. It hasn't reproduced since I uninstalled the kln90B, tho I did not have it loaded into the aircraft and I don't understand why having the unit installed would cause this issue... It is also generally good practice to enter HDG mode before intercepting a localizer.
