Your discussion on the limits of the Honeycomb Bravo throttle quadrant bring clarity to my frustration as to why the beta and reverse capabilities did not seem to work. I mostly fly the Cirrus SR22 TN but also fly the Hot Start TBM900. Currently I am not able to have the throttle work at all let alone the beta and reverse modes. I am learning that this is an issue between the TBM900 and the Honeycomb. Perhaps your Arduino can resolve this additional limitation. Appreciate any comments on this.
Hi William, I love Cirrus SR22 😃. There may be several issues with not being able to use the Bravo quadrant apart from its inability to send the analog data below the detent (unless you modify it as I did with mine). Arduino definitely helped me to overcome some issues when flying default KingAir C90, but in some other planes the issue may be a bit more tricky to resolve. What I realized, the trouble is that there is no unified system of data variables in X Plane that can be controlled by external controllers. Every plane developer adds more variables (which can be found through DataRef plugin, and through looking at script files in plane directories). Then you have to send data to those variables from your controller (Honeycomb partially solved it with their profiling tool 👏). For instance, despite the fact that all my Arduino-based axes work perfectly, I still cannot control mixture in Zebo B737 with them since the variables that control mixture for both engines are not standard (such as "Mixture1" and "Mixture2") 🤷♂️. Having the ability to create your own planes and modify existing ones is great, but each plane may require a completely different software profile of your controller, which is a mess I am afraid. As for the Arduino, I started creating a video of how to modify the Bravo quadrant, but was set behind due to other work.
@@kiralema Thanks for this update. My issue is all about the Hot Start TBM900 (a very well designed and performing sim aircraft) that uses the Pratt Whitney PT6A turboprop engine. However, the TBM900 now has just a throttle control that serves as a condition lever to bring the engine to flight idle and actually moves the single lever to the left for normal throttle Alpha and beta mode. There is no separate condition level or prop control. My old CH Pro yoke with a throttle quadrant would work fine but with a separate condition lever and throttle control. The Honeycomb bravo does not activate the throttle control in the TBM900 at all in Xplane. I would like to think the new Xplane12 when it comes out down the road will work with Honeycomb to resolve this sort of thing. That may be awhile. I will watch for your Arduino video to understand more. May have to acquire this system I really want to fly the TBM900. The Cirrus SR22 TN works fine with the Honeycomb. Bill
Hi John, apologies for the long time to reply. I was working on compiling the video where I describe how to fix the issue with an additional controller board. Here's the link to part 2: ua-cam.com/video/Lv1fQ-lLvUA/v-deo.html
Unfortunately, I don't really know what version of the firmware of the Bravo quadrant the Honeycomb Aeronautical is using at the moment. There's no mentioning anything on their website, so one may assume that the issue is still there. What I ended up doing is to adding an Arduino board inside the Bravo quadrant, which would utilise the full potential of all 6 potentiometers, and would let me to add other buttons and switches if I wanted. I hope to post a video on that sometime.
Thank you *so* much! Your solution is brilliant! Wow! You've enhanced my X-Plane 11 experience tremendously. 😀
I glad it helped! :)
Your discussion on the limits of the Honeycomb Bravo throttle quadrant bring clarity to my frustration as to why the beta and reverse capabilities did not seem to work. I mostly fly the Cirrus SR22 TN but also fly the Hot Start TBM900. Currently I am not able to have the throttle work at all let alone the beta and reverse modes. I am learning that this is an issue between the TBM900 and the Honeycomb. Perhaps your Arduino can resolve this additional limitation. Appreciate any comments on this.
Hi William, I love Cirrus SR22 😃. There may be several issues with not being able to use the Bravo quadrant apart from its inability to send the analog data below the detent (unless you modify it as I did with mine). Arduino definitely helped me to overcome some issues when flying default KingAir C90, but in some other planes the issue may be a bit more tricky to resolve. What I realized, the trouble is that there is no unified system of data variables in X Plane that can be controlled by external controllers. Every plane developer adds more variables (which can be found through DataRef plugin, and through looking at script files in plane directories). Then you have to send data to those variables from your controller (Honeycomb partially solved it with their profiling tool 👏). For instance, despite the fact that all my Arduino-based axes work perfectly, I still cannot control mixture in Zebo B737 with them since the variables that control mixture for both engines are not standard (such as "Mixture1" and "Mixture2") 🤷♂️. Having the ability to create your own planes and modify existing ones is great, but each plane may require a completely different software profile of your controller, which is a mess I am afraid. As for the Arduino, I started creating a video of how to modify the Bravo quadrant, but was set behind due to other work.
@@kiralema Thanks for this update. My issue is all about the Hot Start TBM900 (a very well designed and performing sim aircraft) that uses the Pratt Whitney PT6A turboprop engine. However, the TBM900 now has just a throttle control that serves as a condition lever to bring the engine to flight idle and actually moves the single lever to the left for normal throttle Alpha and beta mode. There is no separate condition level or prop control. My old CH Pro yoke with a throttle quadrant would work fine but with a separate condition lever and throttle control. The Honeycomb bravo does not activate the throttle control in the TBM900 at all in Xplane. I would like to think the new Xplane12 when it comes out down the road will work with Honeycomb to resolve this sort of thing. That may be awhile. I will watch for your Arduino video to understand more. May have to acquire this system I really want to fly the TBM900. The Cirrus SR22 TN works fine with the Honeycomb. Bill
looks like a good idea to me has any upgrade been released yet how did you get your to respond to the beta mode?
Hi John, apologies for the long time to reply. I was working on compiling the video where I describe how to fix the issue with an additional controller board. Here's the link to part 2: ua-cam.com/video/Lv1fQ-lLvUA/v-deo.html
Is that issue still the case, as of the date of this post? What firmware is that, that you have?Thanks.
Unfortunately, I don't really know what version of the firmware of the Bravo quadrant the Honeycomb Aeronautical is using at the moment. There's no mentioning anything on their website, so one may assume that the issue is still there. What I ended up doing is to adding an Arduino board inside the Bravo quadrant, which would utilise the full potential of all 6 potentiometers, and would let me to add other buttons and switches if I wanted. I hope to post a video on that sometime.
Can't understand a thing you said , good god man speak clearly
I am sorry if my voice wasn't clear enough.