PA-28R Turbo Arrow III/IV

@Mark Thanks for your reply. From that I gleaned that the AP disconnect is not a feature of the aircraft so perhaps something might be wrong on my end.

I did a long testflight during which I unplugged my yoke and throttle quadrant and that seemed to cure the AP disconnect. After reconnecting the AP disconnected again after a while.

I checked the yoke sensivity setting in MSFS and noticed there was a "reactivity" setting I have never touched before. It showed 100 so I changed that to 98, on a hunch that this might filter out these spikes.

I did a long test flight with this setting and did not have a AP disconnect. The funny thing is, when I set it back to 100 I also did not have these AP disconnects anymore.

When I later checked for spikes using VKB Joytester I noticed that the yoke was indeed sending spikes once in a while, very short bursts but off the scale.
These did not lead to AP disconnects since I already touched the reactivity setting in MSFS.

Even after a very, very long flight the AP disconnect did not return except once when I changed GPS instruments on the tablet during a flight.

Perhaps the original value of the reactivity setting was not set properly in MSFS internally so setting it to 98 and then back to 100 reset something in MSFS.
Sorry for the long reply but hopefully someone else with a similar issue might benefit from this.

@jonah9000 We have received reports across multiple aircraft (from multiple developers) of autopilot issues following some changes that were made to the default Working Title GNS530 in MSFS SIm Update 14. We are hopeful that some changes that are due to be released with MSFS Sim Update 15 should improve this.

In the meantime, if you could kindly contact Just Flight support, they may be able to assist with some short-term troubleshooting steps: https://www.justflight.com/support

Mark - Just Flight

@Mark

maybe an open-source approach could make sense?

https://www.fsdeveloper.com/forum/threads/msfs-kln-90b-integration.457361/

Worth contacting Just Flight support. They should be able to help with this kind of thing:

https://community.justflight.com/topic/2/product-support

I believe the turbocharger simulation was something that was improved in the latest MSFS Sim Update and may have fixed this issue, but the Turbo Arrow III/IV will still be using the turbo simulation from prior to that Sim Update, as we haven't got around to investigating any of that new logic just yet.

We do have this noted on our internal bugs/feature requests tracker and we'll investigate what is possible in a future update to the Turbo Arrow.

Mark - Just Flight

@mad_x

I have checked my software :
1 Checked that there is no Garmin in the Community folder
2 Deleted GNS Garmin 430/530 in content manager, only 1 standard ( non remove able ) remained.
3 Restarted MSFS
4 Loaded the GNS 430/530 from market place
5 Restarted MSFS
6 Loaded PA28 Turbo Arrow III at parking 1 in EDLV in Cold & Dark mode, After few moments I selected " Ready for Start. NOW I can select frequency 121.705 !
7 Restarted MSFS
8 Loaded PA28 Turbo Arrow III t runway with running engine : Bingo! now I can make frequency steps of 25 only!
=> this problem is sometimes in PMDG DC6B, but never in Fenix A320 or PMDG B737-800
So Back to FS9 ; always start up in the right way......

@martyn
Hi Martyn, further to your last reply, I'm afraid the latest update did not resolve the issue re the heading bug in the Turbo arrow III.

However a workaround has got it working. I noticed on the Black Square Baron 58 Controls options, that the heading bug could be moved via the Increase/Decrease knob on the right side of the Honeycomb Bravo. This was in spite of the binding settings for the Increase and Decease having disappeared, leaving only the Select Heading Bug . I removed those 2 bindings from Controls Options on the Turbo Arrow III, and the heading bug can now be Incr/Decr by using the right hand control knob.
Andy

Thanks once again for support guys. I installed the latest version of gtn750, and everything ok. I haven't thought of that, because I thought, that gps unit pops up notification, that update is available and so I was thinking that I have the latest version of gps....

it must have been something on my end then, deleted and reinstalled now works fine :crossed_fingers_medium-light_skin_tone:


@jlheyden works again thanks to update to version 2.1.98

@ecoleshill false alarm. It was hidden off the secondary screen.