How do I set up Honeycomb Bravo for PMDG 737 in MSFS 2020?

Create a dedicated Honeycomb Bravo control preset in Microsoft Flight Simulator 2020, remove conflicting default assignments, and bind separate 0–100% axes for PMDG 737 throttles 1 and 2. Add spoiler and flap axes, reverse-thrust buttons, trim and gear controls; use PMDG-specific events for MCP buttons and PMDG-aware output logic for annunciators.

Set up a clean PMDG 737 control preset first

A separate Bravo preset prevents general-aviation throttle, propeller and mixture assignments from interfering with the PMDG 737. MSFS 2020 does not automatically select the correct device preset for each aircraft, so remember to choose it before loading or flying the 737.

1. Confirm that MSFS detects the Bravo. Move every lever and press several buttons in Controls Options. Basic axes and buttons do not require the annunciator-light bridge.
2. Create a dedicated preset. Select the Bravo, duplicate its default preset through the preset manager, and give the copy a clear PMDG 737 name. Starting blank is cleaner when troubleshooting, but duplicating the default retains useful gear, trim and autopilot assignments.
3. Remove conflicting controls. Use the assigned-input filter to clear combined throttle, propeller, mixture and unwanted engine bindings. An axis must not be assigned to both a combined throttle and an individual engine throttle.
4. Check each input by movement. Use input scanning rather than copying button numbers from somebody else’s configuration; Bravo revisions, profiles and handle arrangements can produce different numbers.

If the hardware is not detected or you need the underlying MSFS preset procedure, follow our clean Alpha and Bravo control-preset workflow before adding PMDG-specific mappings.

Which Bravo axes should the PMDG 737 use?

The PMDG 737 works best with separate forward-thrust axes and button-operated reversers. The commercial handles are convenient but not required; arrange the physical levers in whichever order feels natural, then bind them as follows.

Begin with a linear response and the smallest dead zone that prevents jitter. Use the binding’s reverse-axis option if a lever moves backwards; do not distort the sensitivity curve merely to invert it. Confirm that each throttle reaches idle and full forward travel independently.

If the flap handle jumps between detents, first remove duplicate flap assignments. If it still hunts, add a small dead zone or use increment and decrement commands through a custom profile. A speed-brake lever that will not stay in ARM can be handled with a PMDG-specific arm command while retaining the axis for the rest of its travel.

How do you configure reverse thrust?

Bind each Bravo reverser input to the corresponding throttle-decrease command, with the forward throttle axes left at 0–100%. This lets each PMDG engine enter reverse only after its thrust lever has reached idle.

1. Place both thrust levers at idle.
2. Lift the left reverser and scan its input, then assign THROTTLE 1 DECREASE.
3. Lift the right reverser and assign THROTTLE 2 DECREASE.
4. Test with the engines running. The virtual reverse levers should deploy independently and increase reverse thrust while the inputs remain active.

Do not assign both decrease-throttle and toggle-reverse commands to the same lever. Toggle commands can leave reverse latched after the physical lever is released. If reverse only flickers, confirm that the input remains active while the reverser is lifted and that the main axis has fully reached idle.

How should the Bravo autopilot panel map to the PMDG 737?

The rotary controls can use standard simulator increment and decrement commands, but several Bravo button labels do not correspond directly to Boeing MCP modes. A generic MSFS command may change the simulator’s hidden autopilot state without pressing the expected PMDG cockpit button.

• IAS: adjust the MCP speed value.
• CRS: adjust the captain’s course selector; controlling both sides requires additional custom logic.
• HDG: adjust the MCP heading.
• VS: adjust the selected vertical speed.
• ALT: adjust the MCP altitude.

For the mode buttons, a PMDG-aware profile would normally treat Bravo HDG as HDG SEL, NAV as LNAV, APR as APP, ALT as ALT HOLD, VS as V/S, IAS as LVL CHG and AP as CMD A. Leave REV unused unless you have assigned it a deliberate custom function. NAV HOLD is not the same thing as LNAV, and the Bravo has no dedicated VNAV key.

Test every mode against the 737’s flight-mode annunciator, not just the lamp on the Bravo. Our explanation of how the PMDG MCP, flight directors and autothrottle work together covers the cockpit logic behind those assignments.

What should the gear lever, trim wheel and switches control?

The gear lever should have separate gear-up and gear-down bindings, while the trim wheel should send elevator-trim-up and elevator-trim-down commands. The Bravo cannot represent the 737’s middle gear-lever OFF position, so move the cockpit lever to OFF with the mouse after retraction if you are following the full procedure.

Avoid assigning the Bravo switches to generic mixture commands for the PMDG fuel-control levers. Those levers and many overhead switches use PMDG-specific controls; either operate them in the cockpit or map the corresponding custom events through a PMDG-aware hardware profile.

Why do the throttles jump when autothrottle disconnects?

The Bravo is not motorised, so its physical levers do not follow the PMDG 737’s moving virtual thrust levers. When autothrottle releases and the hardware axis is moved, thrust can jump to the physical lever position.

Keep the Bravo levers still while autothrottle is controlling thrust, then match them to the virtual levers when your procedure calls for manual thrust. If minor axis noise fights the autothrottle, add only enough dead zone to stop the jitter and check the PMDG option governing manual throttle override. Duplicate throttle bindings are the other common cause.

Why are the Bravo annunciator lights not working?

Working axes do not prove that the annunciator-light software is installed or active. MSFS bindings handle inputs, while the Honeycomb bridge and output profile drive the LEDs; the PMDG 737’s custom system variables may also require aircraft-specific output logic.

Use our Bravo driver, profile and annunciator-light setup to install the bridge and distinguish the Honeycomb Configurator profile from the MSFS control preset. If generic aircraft lights work but PMDG indications do not, the missing component is usually the PMDG-aware output profile rather than the USB connection.

Common PMDG 737 Bravo setup faults

Does the same setup work on Xbox?

The axis and basic-button principles are the same when the Bravo is connected through compatible Xbox hardware, but the Windows Honeycomb Configurator and AFC bridge are PC tools. Advanced PMDG event mappings and custom annunciator outputs therefore may not be available on Xbox; use the simulator’s native bindings and operate unsupported controls in the cockpit.

How do you check the finished profile?

Validate the profile one system at a time before attempting a complete flight.

1. Move each thrust lever separately from idle to maximum and confirm that only its own engine responds.
2. Check speed-brake DOWN, ARM and deployed positions, followed by every flap detent.
3. With both throttles at idle and the engines running, test each reverser independently.
4. Operate gear and trim while watching the cockpit controls for repeated or conflicting inputs.
5. Test MCP selectors and buttons in a safe airborne situation, using the 737’s flight-mode annunciator as the final indication of what is engaged.