basti_an_uno 0 Posted December 22, 2020 Share Posted December 22, 2020 Good evening, I would like to configure my Bravo Throttle Quadrant for use with aerosoft's A3XX-Family. I found the LVars-Files, but I am not able to bind the autopilot-section. The aircraft simply doesn't react to any action (or it reacts in the wrong way), e.g. if I try to input the heading or altitude. There is no problem with the hardware. I found the videos with explenations how to configure the quadrant in general, but in this case they do not help me. Is it possible to get a manual or tutorial with all necessary information? Thanks for your help. Best wishes and stay healthy! Link to comment Share on other sites More sharing options...
Aerosoft BenBaron 287 Posted December 22, 2020 Aerosoft Share Posted December 22, 2020 Hi Basti, there might be still some limitations in place, so that you cannot actually interact with every variable. Unfortunately, there is simply too many possible variations out there, to cover all of them on initial release. As you might have already noticed, we have this channel which already contains some videos supposed to helping you configure things. Other than that, you can also attach the .json file to this thread, so I can take a look as to whether this should work, or might simply not be supported, just yet. Link to comment Share on other sites More sharing options...
basti_an_uno 0 Posted December 25, 2020 Author Share Posted December 25, 2020 Hi Ben, thank you for your answer. The last days I tryed a few configurations. Now I'm able to engage SPD, HDG and ALT in managed mode, but I'm not able to disengange it. Also I was able to bind the AP-Button with AP1, but if I want to activate the autopilot during flight, it disconnects immediately after pushing the button. So there are some open questions. I attache my .json-Profile to my answer. Again, thank you very much! NeuMeins.json Link to comment Share on other sites More sharing options...
Aerosoft BenBaron 287 Posted December 27, 2020 Aerosoft Share Posted December 27, 2020 Hi Basti, as I am not with my development environment I cannot delve in too deeply into your profile. But what I can tell you is that I've already identified a bug in the interfacing module which might prevent you from actually interacting with LVars like "L:AB_AP_HDGmode". So, if this does not work for you right now, it is not your fault and will get fixed in the foreseeable future. Link to comment Share on other sites More sharing options...
basti_an_uno 0 Posted December 29, 2020 Author Share Posted December 29, 2020 Hi Ben, is it a bug in the airbus interface or in honeycomb's? I only ask because I tried to configure my QW787 and had some problems... but I should say I tried it late at night and I was a little tired, so it could have been my fault. Next week I will give it a second chance with better preperation. Otherwise I will wait for the bugfix. Thank you very much for your help so far! I wish you (and everyone else at aerosoft) a happy new year. Link to comment Share on other sites More sharing options...
Aerosoft BenBaron 287 Posted December 30, 2020 Aerosoft Share Posted December 30, 2020 Hi Basti, it is just that the variable landscape is quite heterogenous so it is difficult to get each and every variable type interfaced correctly. While we tried, there are some snags here an there which will just show up over time. We are working on improving this in the future. For now, I am also wishing you a good new Year's. Link to comment Share on other sites More sharing options...
Dan Bonenfant 0 Posted January 2, 2021 Share Posted January 2, 2021 I understand it is not easy. Until I have a workable profile available I'll be leaving the A32xx Pro as well as the CRJ Pro in the hangar. I have tried unsuccessfully with the CRJ using all of the information available, what meager info there is. Not wasting any more time until there is something useable to start with. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.