How do I set up Honeycomb Alpha and Bravo in MSFS 2020 and MSFS 2024?
Set up Honeycomb Alpha and Bravo in MSFS 2020 or 2024 with separate presets, correct axis mappings, aircraft profiles and Bravo LED fixes.
MSFS 2020 and MSFS 2024: connect the Honeycomb Alpha and Bravo as separate devices, give each its own active control preset, map the Alpha to pitch and roll, and build Bravo profiles by aircraft type. After moving between simulators, rebuild or verify both presets, remove duplicate bindings, calibrate the axes and test every control.
Before you begin: Honeycomb drivers, firmware and Configurator
Basic Alpha and Bravo axes and buttons should register in Windows before Microsoft Flight Simulator or Honeycomb companion software is involved.
- Connect each unit separately. Use direct, powered USB connections while diagnosing the setup. Avoid an unpowered hub and confirm that both the Alpha and Bravo appear as distinct controllers.
- Check the raw Windows inputs. Run
joy.cpl, open each device's properties and move every axis, button and switch. If a control is absent here, changing an MSFS binding will not fix it; try another USB port, reconnect the unit and check its support software. - Update firmware only where applicable. Use an updater intended for the exact Honeycomb model and hardware revision. Do not apply unrelated firmware merely because a controller is misconfigured, and never disconnect it during an update.
- Install the correct Bravo support package. The Bravo's levers and buttons normally behave as standard controller inputs, but its gear and annunciator LEDs depend on the compatible Honeycomb bridge, often referred to as
AFC_Bridge, Configurator support or an aircraft-specific integration. Our PC installation, device-detection and Bravo profile checks cover the software side in more detail. - Confirm the bridge is available when MSFS runs. If the package uses Configurator profiles, load the profile intended for the simulator and aircraft. A Configurator profile is not the same thing as an MSFS control preset.
| Configuration layer | What it controls | What to verify |
|---|---|---|
| Windows device input | Raw axes, buttons and switch positions | Both units appear separately in joy.cpl and respond through their full travel. |
| MSFS control preset | Pitch, roll, throttle, switches and other cockpit commands | A separate, active preset exists under each device. |
| Honeycomb bridge or Configurator | Bravo LEDs and some aircraft-specific output events | The compatible package is installed, running as intended and using the correct aircraft support. |
This distinction matters: a Bravo can control the aircraft perfectly while every annunciator remains dark. That usually indicates an output-integration problem, not a failed throttle quadrant.
Honeycomb Alpha configuration and button mapping
A dependable Alpha configuration uses full analogue axes for pitch and roll, explicit commands for maintained switches, and no duplicate yoke assignments on other devices.
- Select the Alpha device. Open the MSFS controls screen, choose the Honeycomb Alpha and create or duplicate a custom preset. Give it a recognisable name such as
Alpha - General Aviation. - Make the preset active. Presets belong to individual devices. Selecting a Bravo profile does not activate the matching Alpha profile, so check both device tabs before loading the aircraft.
- Assign pitch and roll. Bind the yoke to the full-range
Ailerons AxisandElevator Axiscommands. Do not use the digital aileron-left, aileron-right, elevator-up or elevator-down commands. The Alpha has no rudder axis; pedals or another compatible controller must provide yaw. - Remove duplicate axes. Search every connected joystick, gamepad and throttle for additional aileron or elevator assignments. A mistake we see constantly is leaving the same flight-control axis on both the Alpha and an older joystick.
- Check calibration and direction. Centre the yoke, move it slowly to every physical stop and watch the input indicator. Start with a linear response, minimal dead zone and unchanged endpoints. Add a small centre dead zone only if the untouched input jitters. Reverse an axis only when the cockpit control moves in the wrong direction.
- Map the magneto positions. Bind OFF, right, left and both to their matching explicit magneto states, then map the spring-loaded start position to the appropriate starter command. Piston twins may require engine-specific events rather than an all-engine command. Test every detent because a toggle binding cannot reliably represent a multi-position key.
- Map maintained switches explicitly. Battery, alternator, avionics and light switches should use separate on and off commands where MSFS provides them. A toggle command can leave the hardware switch opposite to the virtual cockpit after a mouse click, aircraft reload or electrical-state change.
- Test inside the aircraft. Pulling the yoke back must command nose-up elevator; turning left must command left roll. Check every Alpha button and switch with the aircraft powered as required.
Command labels and available electrical events vary between MSFS 2020, MSFS 2024 and individual aircraft. Our extended Alpha axis, magneto and switch-mapping reference covers the common assignments and their limitations.
Honeycomb Bravo throttle quadrant setup and profiles in MSFS 2020/MSFS 2024
MSFS 2020 and MSFS 2024 Honeycomb Bravo profiles should be organised by engine type and lever layout, then cloned for aircraft that need their own throttle calibration or custom commands.
- Choose the profile's scope. A family profile is suitable when several aircraft use the same standard axes. Use a dedicated aircraft profile when it has custom detents, condition-lever logic, reverse ranges or tablet-based calibration.
- Create and name the Bravo preset. Useful names include
Bravo - Piston Single,Bravo - Piston Twin,Bravo - Twin TurbopropandBravo - Twin Jet. The name should identify both the device and intended aircraft type. - Clear unwanted defaults. Remove throttle, propeller, mixture, flap and spoiler assignments that do not match the fitted lever heads. Never bind one lever to both a combined axis and a per-engine axis.
- Assign the engine axes. Use separate throttle, propeller and mixture or condition commands for each engine when the physical levers are separate. Use a combined throttle axis only when one lever is deliberately controlling every engine.
- Choose the correct throttle range. A
0 to 100%throttle axis is usually the best starting point when the Bravo reverse handles are mapped as buttons. Use a full-range axis only when the aircraft explicitly supports reverse travel through the analogue axis or its own calibration process requires it. - Select and test the preset. Before every first flight with a new profile, verify that the correct Bravo preset is active. Move each lever from stop to stop and compare it with the cockpit control and MSFS input indicator.
Which Honeycomb Bravo axis bindings should I use?
The right axis layout depends on the engine count and how the aircraft models propeller, mixture, condition and reverse controls.
| Aircraft profile | Typical Bravo lever arrangement | Binding rule |
|---|---|---|
| Piston single | Throttle, propeller, mixture | Use throttle 1, propeller 1 and mixture 1 axes. |
| Piston twin | Throttle 1/2, propeller 1/2, mixture 1/2 | Bind all six levers to their matching per-engine axes. |
| Single turboprop | Power, propeller, condition | Power normally uses throttle 1 and propeller uses propeller 1. The condition lever may use mixture 1 or an aircraft-specific command. |
| Twin turboprop | Power 1/2, propeller 1/2, condition 1/2 | Use per-engine axes. Where no standard condition axis exists, follow the aircraft's mixture or custom calibration requirements. |
| Twin-engine jet | Spoilers, throttle 1/2, flaps | Use separate throttle axes plus spoiler and flap axes. Calibrate detents in the aircraft where supported. |
| Four-engine jet | Spoilers, throttle 1–4, flaps | Assign four individual throttle axes rather than one combined throttle. |
Family profiles are starting points, not universal answers. For example, a turboprop condition lever may behave correctly through a mixture axis in one aircraft but require custom events in another. Likewise, an airliner may ignore generic flap detents until they are calibrated through its cockpit or tablet settings.
For a practical twin-engine example, our DA62 Alpha and Bravo profile walkthrough shows how separate device presets, twin throttles, trim, flaps, gear and autopilot assignments fit together.
Bravo switches, autopilot controls and annunciator LEDs
The Bravo combines analogue lever axes, button-style trim and reverser inputs, maintained switches, autopilot controls and output-only LEDs, so these controls cannot all be configured in the same way.
How should I map gear, flaps, spoilers, reversers and switches?
- Gear lever: assign its two positions to explicit gear-up and gear-down commands. Avoid one gear-toggle command because a maintained lever can become opposite to the aircraft state.
- Flaps and spoilers: use analogue axis commands when the aircraft supports them. Airliners with fixed detents may need additional calibration inside the aircraft.
- Reverse handles: these normally register as buttons rather than negative analogue travel. Depending on the aircraft, map them to throttle decrease while held, a hold-reverse command, a reverse toggle or the aircraft's custom event. Test them from idle with the parking brake set.
- Trim wheel: bind the two directions to elevator trim up and down. The wheel sends repeated button inputs; it is not an elevator-trim axis. Confirm that the cockpit trim indication moves in the intended direction.
- Maintained electrical and light switches: use explicit on and off commands. If an aircraft supplies only a toggle event, synchronise the hardware and cockpit before departure and expect mouse interaction to break that synchronisation.
How does the Bravo autopilot selector work?
The rotary selector chooses which autopilot value the increment/decrement knob changes; the selector positions and adjustment knob therefore need separate assignments.
Bind the selector positions to the corresponding heading, course, altitude, vertical-speed or airspeed selection commands, then bind the adjacent knob to increase and decrease. If turning the knob changes heading while altitude is selected, the altitude selector event is missing, duplicated or unsupported.
The AP, HDG, NAV, APR, REV, ALT, VS and IAS buttons use standard simulator commands in many default aircraft. Complex add-ons may use custom events, so their axes can work while certain autopilot buttons do nothing. In that case, use the aircraft's supplied integration rather than layering several generic commands onto the same button.
Why do the Bravo controls work but the annunciator lights stay dark?
Dark Bravo lights usually mean that the output bridge, aircraft support or electrical state is missing; they do not prove that the controller itself has failed.
- Confirm that the compatible Honeycomb bridge or Configurator package is installed and starts as its instructions require.
- Check that any required Configurator or aircraft profile is selected. This profile is separate from the Bravo control preset inside MSFS.
- Power the aircraft's battery, avionics and relevant electrical buses. Many warnings and gear indications remain dark in an unpowered cockpit.
- Test a standard aircraft as well as the add-on. Some complex aircraft do not expose the standard simulator variables expected by generic annunciator profiles.
- Reconnect the Bravo directly to a powered USB port if the lights behave intermittently, while remembering that stable axes do not guarantee that the bridge software is communicating.
If this problem is specific to the newer simulator, use our MSFS 2024 bridge, aircraft-support and annunciator checks.
Why is my Honeycomb setup not working in MSFS 2020 or MSFS 2024?
Most Honeycomb setup faults come from an inactive preset, duplicate command, incorrect axis range or confusion between controller inputs and Bravo LED integration.
| Symptom | Likely cause | What to check |
|---|---|---|
| Both throttles move together | A combined throttle and per-engine axes are assigned at the same time. | Remove the combined assignment and retain only throttle 1 and throttle 2 on their respective levers. |
| An axis moves by itself or fights the hardware | The same axis exists on another controller, or an assistance feature is controlling it. | Use the input-search function across the Alpha, Bravo, pedals, joystick and gamepad, then review active assistance settings. |
| Controls were mapped but do nothing | The wrong preset is active under one device. | Select the Alpha and Bravo separately and confirm the named preset shown for each. Repeat this after changing simulator or aircraft. |
| An axis moves backwards | The axis direction is reversed. | Reverse it in one place only. Do not reverse it in both MSFS and an aircraft calibration page. |
| A lever never reaches idle or full travel | The raw endpoint is missing, the wrong axis command is selected or aircraft calibration is limiting the range. | Check joy.cpl first. If Windows reaches both ends, correct the MSFS endpoint or aircraft calibration rather than adding a large dead zone. |
| Reverse thrust begins before the lever reaches idle | A full-range throttle command or incorrect detent calibration is treating part of the forward range as reverse. | Use a 0-to-100 throttle axis where appropriate, map the reverse handle separately and recalibrate any aircraft-specific idle detent. |
| Alpha buttons or switches do not respond | The button is not mapped in the active Alpha preset, the wrong event type is used or the aircraft needs power or custom events. | Verify the raw button in joy.cpl, search for it by input in MSFS, then replace toggles with explicit commands where available. |
| Bravo annunciators stay dark while axes work | The LED bridge is absent, the aircraft profile is unsupported or the electrical buses are off. | Check bridge operation, Configurator or aircraft support, cockpit power and the same lights in a standard aircraft. |
Can I use the same Honeycomb profiles in MSFS 2020 and MSFS 2024?
The mapping principles are the same, but MSFS 2020 and MSFS 2024 presets should be rebuilt or verified rather than assumed to transfer correctly.
The simulators store and present their control configurations separately, and command names, available events and control-screen layouts can differ. After moving between versions, confirm both devices, activate both presets, inspect every axis for duplicates and repeat any aircraft-specific throttle or detent calibration.
Remember that an MSFS preset and a Honeycomb Configurator profile are separate layers. Recreating the simulator preset does not automatically repair an incompatible LED profile, and changing an LED profile does not remap the Bravo's throttle axes.
These instructions primarily apply to Windows PC. Xbox Series X|S requires an explicitly Xbox-compatible Honeycomb setup and the appropriate connection hardware; it cannot run the Windows bridge software. MSFS 2024 on PlayStation 5 and PS5 Pro likewise requires peripherals supported by the console and simulator. MSFS 2020 was not released on PlayStation.