Set up Honeycomb Alpha and Bravo in MSFS with correct yoke, throttle, trim, flap and switch bindings, plus profile and conflict fixes.
Connect the Honeycomb Alpha and Bravo as separate USB devices, create a dedicated preset for each in Microsoft Flight Simulator, bind the Alpha only to pitch and roll axes, and map the Bravo levers by aircraft type. Remove duplicate assignments, calibrate each axis, then test trim, reversers, gear and switches before flight.
Set up the Alpha and Bravo as separate MSFS controllers
The reliable method is to treat the Alpha and Bravo as two independent controllers that happen to form one cockpit setup.
- Mount and connect both units. Plug each controller into USB and confirm that Windows and Microsoft Flight Simulator detect two separate devices. Avoid an unpowered USB hub while diagnosing connection problems.
- Install the Bravo support software if required. Its axes and buttons should work as standard controller inputs, but the annunciator lights normally depend on the appropriate Honeycomb bridge or companion package. Our Bravo detection, driver and profile checks cover this part without repeating it here.
- Create individual presets. Create or duplicate one preset under the Alpha device and another under the Bravo. Names such as
GA Single - AlphaandGA Single - Bravomake it clear which pair belongs together. - Remove conflicting defaults. Check every connected joystick, gamepad and throttle for duplicate pitch, roll and throttle axes. Use the input-search function to find assignments triggered by a particular control.
- Bind the Alpha axes. Assign 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, so pedals or another controller must provide yaw. For the remaining switches and magneto positions, use our detailed Alpha axis and switch mapping. - Bind the Bravo for the aircraft type. Use separate engine axes when each physical lever controls one engine; use a combined throttle only when one lever should move every engine.
- Test before taxi. Watch the control indicators while moving every axis slowly from stop to stop. In the cockpit, verify the direction of the yoke, throttles, propeller controls, mixture or condition levers, flaps, spoilers and trim.
Which Honeycomb Bravo axis bindings should I use?
The correct Bravo bindings depend on the number and type of engines, so separate presets for piston singles, twins, turboprops and jets prevent most conflicts.
| Aircraft profile | Typical lever assignments | Binding rule |
|---|---|---|
| Piston single | Throttle, propeller, mixture | Use the engine 1 throttle, propeller and mixture 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 usually uses throttle 1 and propeller uses propeller 1. The condition lever often uses a mixture axis, but aircraft-specific calibration takes priority. |
| Twin-engine jet | Spoilers, throttle 1/2, flaps | Use separate throttle axes plus the spoiler and flap axes. |
| Four-engine jet | Spoilers, throttle 1–4, flaps | Assign four individual throttle axes rather than one combined axis. |
Where MSFS offers both full-range and 0 to 100% throttle commands, the Bravo's normal lever travel generally suits the 0-to-100 option because its reverser handles are buttons rather than negative axis travel. An aircraft with its own cockpit or tablet calibration may require a different choice.
Never bind the same lever to both Throttle Axis and Throttle 1 Axis. Our combined and per-engine throttle binding explanation shows when each command is appropriate.
How should I map trim, reversers and switches?
The Bravo's trim wheel, reverse handles and selectors are button inputs, even though some of them resemble analogue controls.
- Trim wheel: bind it to elevator trim up and elevator trim down. Do not assign it to an elevator trim axis. Turn the wheel both ways and confirm that nose-up movement changes the cockpit trim indicator in the correct direction.
- Reverse handles: generic aircraft commonly use a throttle-decrease command while each handle is held. Other aircraft use a reverse-thrust toggle or their own calibration system. Test from idle because the correct behaviour varies by aircraft.
- Gear lever: assign its two positions to explicit gear-up and gear-down commands rather than one gear-toggle command.
- Flaps and spoilers: use axis commands when the aircraft supports them. Airliners with fixed detents may also need calibration in the aircraft's cockpit or tablet settings.
- Master and light switches: prefer explicit on and off commands over toggle commands. Maintained hardware switches can otherwise become opposite to the cockpit state.
- Autopilot controls: the rotary selector chooses the parameter and the increase/decrease knob changes it. If the knob alters heading while altitude is selected, the selector positions are missing, duplicated or unsupported by that aircraft.
What sensitivity settings should the Alpha and Bravo use?
Start with linear response curves, minimal dead zones and unchanged endpoint settings, then adjust only to correct an observed problem.
The Alpha needs a small centre dead zone only if the on-screen elevator or aileron input jitters while untouched. Reducing sensitivity can soften handling, but excessive curve changes make the centre vague and the ends abrupt.
Bravo lever axes should reach both endpoints without a large dead zone. If a cockpit lever moves backwards, use the axis-reverse option. If it stops short of idle or full travel, check the selected axis command and endpoint adjustment before changing sensitivity.
Why are the Honeycomb controls moving incorrectly?
Incorrect movement is usually caused by a duplicate binding, the wrong axis range or the wrong active preset.
- Both throttles move together: remove the combined throttle assignment and keep only throttle 1 and throttle 2.
- A control moves by itself: search every connected device for the same axis, then check that an assistance feature is not controlling the aircraft.
- Reverse thrust starts before idle: use the 0-to-100 throttle axis where appropriate and map the reverse handle separately.
- The lever never reaches an endpoint: verify its physical input range, then use the simulator or aircraft calibration rather than compensating with a large dead zone.
- Bravo lights remain dark: confirm the bridge software is installed and that the aircraft's electrical buses are powered. Dark annunciators do not necessarily mean the axes have failed.
- Switches keep changing back: replace toggle bindings with explicit on/off events and remove duplicate switch assignments.
- An add-on ignores autopilot buttons: some complex aircraft use custom events instead of standard MSFS commands. Their axes may work while particular buttons and annunciators do not.
Do MSFS 2020 and MSFS 2024 use the same profiles?
The binding principles are the same in MSFS 2020 and MSFS 2024, but presets should be checked or rebuilt rather than assumed to transfer perfectly.
Both simulators present the Alpha and Bravo as separate devices, although control-screen layout and command wording can differ. Confirm the active preset after changing aircraft or simulator version, and repeat any aircraft-specific throttle calibration.
These instructions primarily apply to PC. Xbox Series X|S requires an Xbox-compatible Alpha setup and the appropriate connection hardware for the Bravo; PC bridge software cannot be installed on the console. On PlayStation 5, use only peripherals explicitly supported by the console and simulator rather than assuming that PC USB compatibility carries across.