Honeycomb Bravo Throttle

[Rosmanczyk]

Is there a configuration guide for making Honeycombs Bravo Throttle work with the A32NX? Or is it not possible at all at the moment? I can't seem to make the autopilot modes work, especially following the flight plan in NAV mode.

[tracernz]

For dev version:
You have to decide where you want the detents (since there are no hardware ones on the Bravo); I suggest the back of the lever aligned with each of the marks next to the levers is a good place. Disable reversers on axis (since Bravo doesn't have reverse axis), and calibrate each detent on our EFB, where you decided they should be. For reverse you'll want to bind the reverse "button" to the decrease throttle button in MSFS settings, as for any other aircraft.

[Rosmanczyk]

It is also possible solving this problem in SpadNext! I've seen it in some profiles where there is a retriggerable delay that resets when you stop turning the knob. When you turn it in a certain speed SpadNext (within a certain time range) let's you configure what should happen when you turn it fast.
Check out Les O'Reilly on YouTube, he uses this technique in one of his videos, I think it's on the TBM or so at 3:10:

https://www.youtube.com/watch?v=7U9YPcLAg7Y&t=213s

[cadilhac]

I imagined that there might be a solution like that. Thanks for the link, I'll go check this.

[cadilhac]

Unfortunately, O'Reilly's technique doesn't work well with events (he says so in the comments but for me it works but with the delay I explains below). So I searched a variable, but I only found A32NX_AUTOPILOT_HEADING_SELECTED. It correctly changes the heading on the ND, but not on the FCU although the doc says this variable is "Selected Heading in FCU"...

Also the delay he defines is a true pause (spadnext does nothing during this delay) and not a real timer. This produces a lag (one click produces the increment only after the 200ms delay). Programmatically speaking, there should be a timer that fires 200ms later and if during this delay a click is done again, the timer would be reset and started again. But this feature does not exist in spadnext I guess...

[Rosmanczyk]

I think this is something Honeycomb would need to implement into their encoder or so.
For the ALTITUDE selection to work you need two variables set up:

1. A32NX.FCU_ALT_INC or A32NX.FCU_ALT_DEC and
2. HEADING_BUG_INC or HEADING_BUG_DEC

When both of these are triggered then both will update accordingly in the ND and FCU.

[cadilhac]

Not sure what you mean. These are events, not variables. And you mix heading and alt + default events and custom events.

[Rosmanczyk]

Oh yes sorry my bad I meant A32NX.FCU_HDG_INC or DEC and HEADING_BUG_INC or DEC.
These are two events that are fired on my end when I want to manipulate the heading and in both places it updates correctly.

[cadilhac]

Ah, this makes sense now. But this is an event to increase by 1. Setting a param of 10 does not work.

[Rosmanczyk]

I think you're not gonna like this but just create the event 10 times when triggered. All of this fires so quickly it's not gonna bother your computer anyway. It's not the most elegant of solutions but it works and it still gives you more freedom than MSFS does out of the box.

[cadilhac]

I like everything that is working in the end. ;)
So, it kinda works. But adding 10 events makes the knob increase like crazy! Surprisingly, it would need less to get a good speed pattern.
Thanks anyway for all this.

And if one of the devs wants to explain why the A32NX_AUTOPILOT_HEADING_SELECTED variable does update only the ND and not the FCU, feel free to shed light on this.

[Rosmanczyk]

I guess one of those variables is the custom autopilot they created and the other a build in MSFS function? just guessing here.
Yeah ten times the event is much, I used 3 and that's more than enough, maybe even two could suffice.
You're welcome I hope I could help a bit.

[tracernz]

I like everything that is working in the end. ;) So, it kinda works. But adding 10 events makes the knob increase like crazy! Surprisingly, it would need less to get a good speed pattern. Thanks anyway for all this.

And if one of the devs wants to explain why the A32NX_AUTOPILOT_HEADING_SELECTED variable does update only the ND and not the FCU, feel free to shed light on this.

Because the variable is intended to be read-only (only written by the FCU). You should use K:A32NX.FCU_HDG_INC, K:A32NX.FCU_HDG_DEC, or K:A32NX.FCU_HDG_SET with the desired heading as the param in the latter case.