Caravan Autopilot - won't disarm?
-
@ultradianguy said in Caravan Autopilot - won't disarm?:
Hello - I am now utterly confused about what changes are needed to make the BS Caravan AP work correctly with the GNS avionics. I had given up on flying it altogether after trying suggested changes to the GNS code. @jmarkows pointed me here which I much appreciate. But I'm unclear which of the many suggested above were confirmed as a solution.
I've seen the original changes to the 530 and 430 files, possible changes to the KAP140 js, and also a change in systems.cfg. As well as keeping or not keeping the WT content manager mods.
@Black-Square can you please provide a single, comprehensive set of instructions in one place for the needed changes to fix the issues? My experience seems to be quite similar to that of @jmarkows .
- You DO need the marketplace mod installed. Without it, the plane calls the original Asobo GNS units and autopilot and things like NAV won't capture and follow
- You DO need to set "flight_director_available" to 1 in the systems.cfg in the Analog Caravan folder
- You do NOT need to make the change to the KAP140.js file; the AP shouldn't display any modes when disconnected, and that code change fixes that, but it's not critical to the fix so you can wait if you don't want to make that change yourself.
- You do NOT need to make changes to the WT530.js and WT430.js to fix the hot swapping issue with the latest WT avionics, but an official fix is likely not coming until SU15 and you run the risk of the AP not working if the state saving doesn't load you into something with the 530/430 already set. I DO recommend you make this fix.
They're not complicated fixes and all that's required is some copy and pasting. You should make a copy of the original file before making the changes, that way you can easily go back if you don't do it right.
-
Thanks - not worried about making the edits - no big deal - just wasn't clear on which were determined to be helpful.
The way people are discussing this is a bit confusing - as saying that the WT avionics are now incorporated into the core sim implies (to me) that no addin is needed in Content Manager. (In my mind, anything I see in Content Manager is not Core - but maybe that's just mistaken).
Anyway, regarding bullet 1 above - there are two GNS files listed in CM - a bigger one with no thumbnail and a smaller one with a thumbnail. I'm understanding the most recent replies to mean BOTH should be loaded.
Confirm?
(And thank you) -
@ultradianguy said in Caravan Autopilot - won't disarm?:
Thanks - not worried about making the edits - no big deal - just wasn't clear on which were determined to be helpful.
The way people are discussing this is a bit confusing - as saying that the WT avionics are now incorporated into the core sim implies (to me) that no addin is needed in Content Manager. (In my mind, anything I see in Content Manager is not Core - but maybe that's just mistaken).
Anyway, regarding bullet 1 above - there are two GNS files listed in CM - a bigger one with no thumbnail and a smaller one with a thumbnail. I'm understanding the most recent replies to mean BOTH should be loaded.
Confirm?
(And thank you)Confirmed, yes. The one without the thumbnail is the core avionics and to my knowledge actually can't be uninstalled. The one with the color thumbnail is the pointer, which can be removed, but you want it installed.
Just to give you a warning to something that tripped me up making the KAP140 edits, Black Square gives four lines that the provided code snipped needs to go after: those are functions and that should be the first line in each function. My first attempt, I misread it as putting it after the block of four functions, and that bricked my avionics. The rest are super simple.
-
@jmarkows Ah, thank you. So I'm adding the same code snippet as the first line of each of those 4 functions?
I usually do this sort of thing in notepad++ which will recognize the file as js and give me some indication where a block begins and ends. Not a full-fledged development environment but helpful.
-
@ultradianguy Correct.
I think a little below that are snippets from my file and Black Squares that should illustrate it a little better, as I said my first attempt didn't go quite right 😂
-
Cool, thanks. (Tried to just like your response but I guess you can't do that here?)
-
Thank you for your post, @jmarkows. That's exactly the current situation. Sorry that this reminds so confusing right now.
I heard through yet another grapevine yesterday that Working Title will not address this until SU15, which is rather upsetting to me and my support team, as you might imagine. I'm sure that it's not by choice, though. Despite the ability to make instantaneous changes at no cost, software development can still be a slow moving machine.
-
-
@Black-Square I think one or more of these fixes might have had unintended consequences.
I noticed flying the Caravan this morning that the AP will now adjust the held altitude based on the cockpit altimeter and not its own. I was holding at 7000ft with a setting of 30.23 (or so, the Kollsman window is impossible to read), when I pulled a local altimeter of 29.94 and adjusted the cockpit one first.
The plane began climbing back to 7000ft as soon as I touched the altimeter but the KAP140 was still set up 30.23. Adjusting that had no effect, but I did discover that playing with the KAP140 Baro setting is still doing something under the hood because you will get all Alt warning beep if you set it differently enough; about .3 in either direction, which IIRC is roughly 300ft.
-
I suspect that's because the Working Title autopilot is missing some features of the native one. For example, it has no bank angle limiter. I added this in my modifications I sent them, so hopefully it will be added in SU15. The KAP140 is my only autopilot with a separate barometer, so I'm not surprised I haven't noticed, given that the Caravan was released well before the WT GNS. I'll take a look next time I have the sim running and see if I can spot a mistake or improve their code.
-
I really appreciate the offer, but please take my word for it that it's extremely unlikely that any of our changes would have resulted in that change. I just don't want to waste your time after you were so willing to help my troubleshoot the bigger problem. I will give this a test run on my side later. It's very easy for me to roll back those changes, because I keep a copy of every version of my aircraft exactly as they were released to the public. If I need any further testing, I will let you know, but I will also do my best to spare you the trouble. Thank you!
-
I did just do a clean install, and it did not work as I thought it did; my apologies. Normally the altimeter change hasn't been as wild as it was during today's flight, so when I adjusted it I saw a small wiggle in the VSI and thought it was adjusting.
I'm not really surprised that the changes wouldn't have done it, but I was sure (so much for that) that it was working previously. You said it's missing some features of the native one? Maybe I had seen it in action when using the stock Asobo avionics.
-
@Black-Square Yes I can also verify in the BKSQ Analog Caravan, the KAP140 Baro setting doesn't have any effect on the altitude hold, only changing the altimeter Kohlsman does.
-
I just confirmed that this doesn't work with the default C172 with Asobo's implementation of a KAP140 either. When I looked in the code, it's using the SimVar "INDICATED ALTITUDE" directly, which will only look at the main altimeter, not a secondary barometer. It's deeper in the code than I usually like to make modifications to, but I will look at the documentation and see if there is an easy addition I can make and suggest to Working Title.
-
@Black-Square Always appreciate your quick response on these forums, by the way I also had the "AP will not shut off" issue (in WTT mode) and your suggested fix (change Flight Director =1) resolved the problem, though I had to map a key to toggle FD on/off since there is no such clickable button in the actual Analog Caravan visual cockpit model.
-
@nomadrc said in Caravan Autopilot - won't disarm?:
@Black-Square Always appreciate your quick response on these forums, by the way I also had the "AP will not shut off" issue (in WTT mode) and your suggested fix (change Flight Director =1) resolved the problem, though I had to map a key to toggle FD on/off since there is no such clickable button in the actual Analog Caravan visual cockpit model.
You shouldn't need to do this, the normal Autopilot Off/Disconnect has been working fine, both bound and clicking the yoke button.
-
@Black-Square said in Caravan Autopilot - won't disarm?:
I just confirmed that this doesn't work with the default C172 with Asobo's implementation of a KAP140 either. When I looked in the code, it's using the SimVar "INDICATED ALTITUDE" directly, which will only look at the main altimeter, not a secondary barometer. It's deeper in the code than I usually like to make modifications to, but I will look at the documentation and see if there is an easy addition I can make and suggest to Working Title.
Now I feel really bad for the bum steer!
