Below you will find the configuration for the Honeycomb Bravo Throttle Quadrant for the Airbus A32NX by FlyByWire. The configuration relies on settings in the MSFS Interface, Spad.Next (if you own it is an advantage) and other free and paid tools (e.g. Better Bravo Lights). You can find the full keyboard layout of the Honeycomb Bravo Throttle Quadrant in Read the Honeycomb Bravo Throttle Quadrant Keymap.
The configuration is divided into several parts: autopilot, switch and thrust control. First, however, I would like to give you an overview of the programs used and useful.
Software
Spad.Next
Spad.Next is software that allows the configuration of different panels and input devices. Among other things, the Honeycomb Bravo Throttle Quadrant is also supported (without prepared profiles). With Spad.Next, variables (e.g. A32NX variables) can be read out and KeyEvents and parameters can be transferred via the SimConnect interface. There is also the option to create local variables and conditions. This is required to use the Honeycomb Bravo Throttle Quadrant autopilot function with the A32NX.
In Spad.Next you then have to add the key events for the A32NX as a CustomClientEvent. To do this, you can use the Use the XML file from FlyByWire and copy it to the AppData/Roaming/SPAD.neXT\Conf\Clientevents folder. This is necessary so that you can use all events afterwards.
The complete You can download the configuration for the FlyByWire here and then import into Spad.Next. You may have to change your DeviceSerial (line 4 in the XML file).
Better Bravo Lights
Better Bravo Lights (BBL) is an alternative “better” replacement for the Aerosoft Honeycomb Bravo Throttle Lights Tool (aka “AFC Bridge”). Better Bravo Lights is completely self-contained and therefore does not require the original Honeycomb Bravo Lights driver. The tool is available for free download at Flightsim.to or on Github.
I recommend using the tool because you can assign all the LEDs as you wish. For example, you can use the “Vacuum” event to display “Seatbelts”. I also use the “REV” display to activate / deactivate the A/THR. You don’t have to configure anything in the first step (unless you want to misuse something), because a standard configuration for the A32NX from FlyByWire is already included.
You can download and apply the following configuration file config.ini (note: due to the file extension, you have to confirm this file twice). You can exchange the file in the Microsoft Flight Simulator 2020 community folder (\Community\BetterBravoLights). Alternatively, you can change the lines listed below for the FBW A32NX manually (e.g. change them with NotePad) in the file path \Community\BetterBravoLights\Config.ini
;; FlyByWire A320
[Aircraft.FlyByWire_A320_NEO]
; A320 FBW has two autopilots, specific to FBW
AUTOPILOT = L:A32NX_AUTOPILOT_1_ACTIVE == 1 OR L:A32NX_AUTOPILOT_2_ACTIVE == 1
; On the A320 the starter switch is 'TURB ENG IGNITION SWITCH EX1:n' (the master engine switches are 'GENERAL ENG STARTER:n')
StarterEngaged = A:TURB ENG IGNITION SWITCH EX1:1, bool == 2
; Don't check for APU GENERATOR SWITCH. It always reports '1'
APU = A:APU GENERATOR ACTIVE, bool == 1
; FBW provides custom LVARS for the 3 hydraulic systems
LowHydPressure = L:A32NX_HYD_BLUE_PRESSURE < 2000 OR L:A32NX_HYD_GREEN_PRESSURE < 2000 OR L:A32NX_HYD_YELLOW_PRESSURE < 2000
; FBW does not set A:BRAKE PARKING POSITION
ParkingBrake = L:A32NX_PARK_BRAKE_LEVER_POS == 1
; From flybywire-aircraft-a320-neo\html_ui\Pages\VCockpit\Instruments\NavSystems\A320_Neo\A32NX_NavSystem.js
LowVolts = A:ELECTRICAL MAIN BUS VOLTAGE, volts < 24
LowFuelPressure = A:GENERAL ENG FUEL PRESSURE:1, psi <= 10 OR A:GENERAL ENG FUEL PRESSURE:2, psi <= 10
; From flybywire-aircraft-a320-neo\html_ui\Pages\VCockpit\Instruments\NavSystems\A320_Neo\A32NX_NavSystem.js
LowOilPressure = A:ENG OIL PRESSURE:1, psi <= 60 OR A:ENG OIL PRESSURE:2, psi <= 60
; Monitor front and rear and cargo doors
; From flybywire-aircraft-a320-neo\html_ui\Pages\A32NX_Core\A32NX_LocalVarUpdater.js
Door = A:CANOPY OPEN, percent > 0 OR A:EXIT OPEN:0, percent > 0 OR A:INTERACTIVE POINT OPEN:3, percent > 0 OR A:INTERACTIVE POINT OPEN:5, percent > 0
; Equivalent of stock A320 but with A:PITOT HEAT, bool replaced with L:A32NX_MAN_PITOT_HEAT
AntiIce = A:STRUCTURAL DEICE SWITCH, bool == 0 AND A:ENG ANTI ICE:1, bool == 0 AND A:ENG ANTI ICE:2, bool == 0 AND L:A32NX_MAN_PITOT_HEAT == 0
; HDG
HDG = L:A32NX_FCU_HDG_MANAGED_DOT == 0
; NAV
NAV = L:A32NX_FCU_HDG_MANAGED_DOT == 1
; APR
; REV for Auto Thrust Mode
REV = L:A32NX_AUTOTHRUST_MODE != 0
; ALT
ALT = L:A32NX_FCU_ALT_MANAGED == 0
; VS
VS = L:A32NX_FCU_VS_MANAGED == 0
; IAS for Speed
IAS = L:A32NX_FCU_SPD_MANAGED_DOT == 0
; SeatBelts
Vacuum = A:CABIN SEATBELTS ALERT SWITCH, bool == 1
Honeycomb Bravo configuration for the FBW A32NX
Below you will find the configuration settings for the Honeycomb Bravo Throttle Quadrant for the FlyByWire A32NX. There are often links to detailed articles, since you often have different options for configuring the throttle. Also, you may not own all of the software.
Autopilot (FBW A32NX – Honeycomb)
In this section we will look at configuring the FlyByWire A32NX autopilot with the Honeycomb Bravo Throttle Quadrant.
- Button 1 – HDG Mode – Heading – HDG and TRK/FPA
- Button 2 – NAV Mode – Navigation – NAV and LOC
- Button 3 – APR Mode – Approach – APPR and activation of second autopilot
- Button 4 – REV Mode – Back Course / Reverse => Misuse for A/THR
- Button 5 – ALT Mode – Altitude – ALT and 100/1000ft Selector
- Button 6 – VS Mode – Vertical Speed – VS
- Button 7 – IAS Mode – Indicated Airspeed – IAS and SPD/MARCH
- Button 8 – Autopilot mode
- Button 13 – INCR Knob – Clockwise
- Button 14 – DECR Knob – Anticlockwise
- Button 17 – IAS Selector – Indicated Airspeed
- Button 18 – CRS Selector – Course => Misuse for AutoBrakes
- Button 19 – HDG Selector – Heading
- Button 20 – VS Selector – Vertical Speed
- Button 21 – ALT Selector – Altitude
Switches (FBW A32NX – Honeycomb)
This section represents freely programmable switches for the FlyByWire A32NX in the Honeycomb Bravo Throttle quadrant. Things that either have to be done regularly or are difficult to access are useful. Examples of somewhat frequently used processes (or processes under stress) are Taxi Lights, Landing Lights, Seat Belts, APU Start, Anti Ice. Other processes such as switching on ADIRS or NAV Light are only required once and should be done with the mouse / keyboard during the cockpit prep.
- Button 34 / Button 35 – Switch 1 – Seat Belts
- Button 36 / Button 37 – Switch 2 – External Taxi Lights
- Button 38 / Button 39 – Switch 3 – External Landing Lights
- Button 40 / Button 41 – Switch 4 – APU
- Button 42 / Button 43 – Switch 5
- Button 44 / Button 45 – Switch 6
- Button 46 / Button 47 – Switch 7
Thrust Control (FBW A32NX – Honeycomb)
The final chapter covers thrust control in the A32NX, controlled by the Honeycomb Bravo Throttle Quadrant.
- Button 9 – not in use (thrust reversal with 4-engine engine)
- Button 10 – thrust reverser engine 1
- Button 11 – thrust reverser engine 2
- Button 12 – not in use (thrust reversal with 4-engine engine)
- Button 15 – Flaps increase
- Button 16 – Flaps decrease
- Button 22 – Trim Nose Down
- Button 23 – Trim Nose Up
- Button 24 – not in use (thrust reverser button, axis 1)
- Button 25 – not in use (thrust reverser button, axis 2)
- Button 26 – Thrust Reverser Engine 1 (Axis 3)
- Button 27 – thrust reverser engine 2 (axis 4)
- Button 28 – not in use (thrust reverse button, axis 5)
- Button 29 – not in use (red TO/GA button engine 1 (with four-engine engine))
- Button 30 – TO/GA
- Button 31 – Gear Up
- Button 32 – Gear Down
- Button 33 – not in use (thrust reverse button, axis 6)
- Button 48 – not in use (red TO/GA button engine 3)
- Axis 1 – (L-AXIS Y) – Air Brakes / Spoilers
- Axis 2 – (L-AXIS X) – not in used
- Axis 3 – (R-AXIS Z) – Engine 1
- Axis 4 – (R-AXIS Y) – Engine 2
- Axis 5 – (R-AXIS X) not in use
- Axis 6 – (L-AXIS Z) – Landing Flaps (Flaps / Slats)
More configurations
- Configure the autopilot
- Configuration for SeatBelts
- Configuration for AutoBrakes
- Configuration for the APU
- Configure A/THR
- Configure for taxi lights
- Configure for landing lights
- Configuring flaps & spoilers
- Configuration in MSFS
- To the overview page of the configuration of the A32NX
- Key Map / Button Map Honeycomb Bravo
More about the Honeycomb Bravo Throttle Quadrant
More about the Honeycomb Bravo Throttle Quadrant can be found on the Honeycomb Bravo Throttle Quadrant Overview Page, the Configuration page of the Honeycomb Bravo Throttle Quadrant for many other aircraft and the Honeycomb Bravo Throttle Quadrant Test and Recommendation.
2 thoughts on “Honeycomb Bravo Throttle Quadrant – A32NX FlyByWire configuration”
Comments are closed.