for Taguilo - Request for KAP 140 support
Posted: Mon Jan 14, 2019 12:59 am
From the outset since I started logging hours in the 310R Redux I have had trouble with the KAP 140 autopilot disengaging at what appeared to be at random. For several flights early on a year or so ago, it appeared to occur about two hours into flights. This past week I closely watched some Youtube KAP 140 video tutorials and noted that changing some avionics settings or applying some control inputs can cause the real world KAP 140 to first enunciate an issue, providing time to react. Then if not overridden, to disengage. That raised my curiosity, so I logged some fresh hours in the Redux to observe.
On a relatively short flight from Bloomington, Indiana (kBMG), to Aurora, Illinois (KARR), I experienced two times when the KAP 140 disengaged. I did not catch it until after the fact in both instances as I heard no warning tone. So I will ask for specific support for that issue. The audible annunciation, or warning tone, is unusually low in volume. I compared it to the level of the AP warning in the Milviz B55 and the Redux volume is only a fraction of that in the B55, and in the original Milviz 310 as well.
The next day I completed my return flight. During the return flight I did at a turn in my route notice the KAP 140 begin a flashing annunciation, then disconnect. I had made no changes to my flight plan or autopilot button selections, but I noted that I had bumped the yoke with my left hand. Upon that I started to experiment and believe I found my issue.
I am using a Saitek Pro Cessna Yoke. The yoke has a 4 way rocker switch on the left handle, under the left thumb location. I use the L to R function of that rocker switch to pan views in and out, mostly in the virtual cockpit. I use the vertical or up/down rocker of that switch in the 301C Redux to apply pitch-trim. That rocker switch is not super tight and does not reliably separate the functions of its two axis, especially when at rest at the mid point position for both axis. That four-way rocker is sloppy in the middle. It is not through wear, just the way it is made.
What I found was that unless I was very very careful when using the L to R function of that four way rocker switch to zoom view, I could inadvertently signal the other axis: elevator trim. It appears that even the shortest signal to the trim axis causes the KAP 140 to initiate a disengage. I understand that applying trim in the real world will cause this from a KAP 140, but I would think it should take more than an inadvertent micro-second bump.
There is no way I can find to adjust the sensitivity or null zone of the hat switch. I need the trim rocker to be functional during maneuvering flight and during landing, so I do not wish to disable it. So what I would like to inquire about is if there is some other method within the KAP 140 coding to reduce the sensitivity; require a longer signal; or for lack of that, a user-configurable lock out of trim switch as an influence to the KAP 140?
Finally, on the issue of not catching these disengage annunciations as they occur, another issue I noted is that in the Redux the audible warning from the KAP 140 that it is encountering an exception is very low volume compared to engine and environmental sound thresholds. I spent about an hour flying around, adjusting my various FSX sound levels, trying to get a more significant disengage warning from the KAP 140. I was able to gain some, but I do not believe enough. Are you able to provide an increase in the warning's sound level? The current warning level is a fraction of that for your BE55 and original 310R, and a fraction of the level of all of my other payware aircraft.
Best regards,
Frank (fppilot)
On a relatively short flight from Bloomington, Indiana (kBMG), to Aurora, Illinois (KARR), I experienced two times when the KAP 140 disengaged. I did not catch it until after the fact in both instances as I heard no warning tone. So I will ask for specific support for that issue. The audible annunciation, or warning tone, is unusually low in volume. I compared it to the level of the AP warning in the Milviz B55 and the Redux volume is only a fraction of that in the B55, and in the original Milviz 310 as well.
The next day I completed my return flight. During the return flight I did at a turn in my route notice the KAP 140 begin a flashing annunciation, then disconnect. I had made no changes to my flight plan or autopilot button selections, but I noted that I had bumped the yoke with my left hand. Upon that I started to experiment and believe I found my issue.
I am using a Saitek Pro Cessna Yoke. The yoke has a 4 way rocker switch on the left handle, under the left thumb location. I use the L to R function of that rocker switch to pan views in and out, mostly in the virtual cockpit. I use the vertical or up/down rocker of that switch in the 301C Redux to apply pitch-trim. That rocker switch is not super tight and does not reliably separate the functions of its two axis, especially when at rest at the mid point position for both axis. That four-way rocker is sloppy in the middle. It is not through wear, just the way it is made.
What I found was that unless I was very very careful when using the L to R function of that four way rocker switch to zoom view, I could inadvertently signal the other axis: elevator trim. It appears that even the shortest signal to the trim axis causes the KAP 140 to initiate a disengage. I understand that applying trim in the real world will cause this from a KAP 140, but I would think it should take more than an inadvertent micro-second bump.
There is no way I can find to adjust the sensitivity or null zone of the hat switch. I need the trim rocker to be functional during maneuvering flight and during landing, so I do not wish to disable it. So what I would like to inquire about is if there is some other method within the KAP 140 coding to reduce the sensitivity; require a longer signal; or for lack of that, a user-configurable lock out of trim switch as an influence to the KAP 140?
Finally, on the issue of not catching these disengage annunciations as they occur, another issue I noted is that in the Redux the audible warning from the KAP 140 that it is encountering an exception is very low volume compared to engine and environmental sound thresholds. I spent about an hour flying around, adjusting my various FSX sound levels, trying to get a more significant disengage warning from the KAP 140. I was able to gain some, but I do not believe enough. Are you able to provide an increase in the warning's sound level? The current warning level is a fraction of that for your BE55 and original 310R, and a fraction of the level of all of my other payware aircraft.
Best regards,
Frank (fppilot)