How do I set up Honeycomb for the DA62 in MSFS 2024?

For the Diamond DA62 in Microsoft Flight Simulator 2024, create separate aircraft-specific presets for the Honeycomb Alpha and Bravo. Bind the Alpha to pitch and roll, map two Bravo levers to Throttle 1 and Throttle 2 (0–100%), leave propeller and mixture axes unassigned, then add trim, flaps, gear and autopilot controls.

Why does the DA62 need a separate Honeycomb profile?

The Diamond DA62 uses FADEC-controlled diesel engines with two power levers, rather than the separate throttle, propeller and mixture controls found in a conventional piston twin. MSFS still treats those power levers as individual throttle axes.

That means a generic twin-engine Bravo preset may assign four unnecessary axes and introduce conflicting inputs. The DA62 also has no reverse thrust, and its engine-master and starter arrangement does not match the Alpha's magneto-style ignition switch.

Recommended DA62 control bindings

The best DA62 configuration uses independent throttle axes while leaving every unused engine-control axis clear.

The physical slots and handle colours do not determine which engine is controlled; the bindings do. Install two adjacent throttle handles where they feel comfortable, then identify each axis by moving it in the controls screen.

How do I create the DA62 profiles in MSFS 2024?

Create and select a DA62-specific preset for each Honeycomb device, because changing the Alpha preset does not automatically change the Bravo preset.

1. Connect every controller. Connect the Alpha, Bravo and any rudder pedals before opening the controls screen. The Alpha and Bravo do not provide a normal rudder axis, so pedals or another controller must supply rudder and toe brakes.
2. Load the DA62. Begin on a runway with the aircraft running so that throttle, flap, gear and control-surface movement can be checked immediately. Disable piloting assists while diagnosing inputs.
3. Create separate presets. Select the Alpha, duplicate a usable preset and name it for the DA62. Repeat this for the Bravo and rudder pedals. Our complete Alpha and Bravo profile workflow covers device detection and the general MSFS control-screen process.
4. Assign the Alpha axes. Use input scanning or search to bind elevator and aileron axes. Start with a linear response and the smallest dead zone that prevents unwanted movement; there is no universal sensitivity value that suits every unit.
5. Assign the two power levers. Bind the left lever only to Throttle 1 Axis (0–100%) and the right lever only to Throttle 2 Axis (0–100%). Remove any combined Throttle Axis, propeller, mixture, reverse-thrust or digital throttle bindings from those inputs.
6. Add the secondary controls. Assign trim, flap increase/decrease and explicit gear up/down commands. Map only one physical control to each function unless the duplication is intentional.
7. Check for conflicts. Search by input and inspect every assignment generated by each lever or switch. Default presets often contain an unwanted combined throttle or another axis attached to the same hardware input.
8. Verify the full range. Move each Bravo lever independently from idle to maximum. The corresponding cockpit power lever should travel smoothly from 0 to 100 per cent without moving the other engine's lever.

Why do the DA62 throttles move together or backwards?

DA62 throttle problems usually come from a combined throttle binding, an inverted axis or the wrong device preset being active.

• Both cockpit levers move together: remove Throttle Axis and retain only the individual Throttle 1 and Throttle 2 axes.
• One physical lever moves both engines: search by that input and delete the duplicate assignment.
• Idle produces full power: enable the axis-reversal option for that binding. Do not reverse it by adding extreme sensitivity curves.
• The lever stops short of idle or maximum: confirm that the 0–100% version of the axis is selected, inspect the input meter and recalibrate the hardware only if the input itself fails to reach both ends.
• The lever jumps rather than moving smoothly: remove any Throttle Increase, Throttle Decrease or throttle-set button commands attached to the same control.

For stubborn axis-range problems, follow our steps for diagnosing reversed, duplicated or incomplete MSFS throttle travel.

Can the Alpha ignition switch start the DA62 engines?

The Alpha's rotary ignition switch is not a faithful match for the DA62's FADEC engine-starting system and is best left unassigned for this aircraft.

The DA62 uses electrical and engine-master controls followed by separate starter controls; it does not have conventional magneto positions. Use the cockpit switches, or bind dedicated engine-master and starter commands only after confirming that the stock aircraft responds correctly to them. A generic magneto or starter binding can operate the wrong engine or do nothing.

How should the Bravo autopilot and lights be configured?

The Bravo autopilot panel can operate the DA62's common G1000 autopilot modes, but some labelled Bravo functions do not have an exact one-to-one equivalent.

• Assign the AP button to autopilot master, then map HDG, NAV, APR, ALT and VS to their corresponding modes.
• Use the selector and rotary encoder for heading, course, altitude, vertical speed and airspeed references where the simulator's default Bravo mappings work correctly.
• Assign the Bravo IAS button to flight level change only if that command operates the DA62's FLC mode. Do not map it to autothrottle; the DA62 has no autothrottle.
• Leave REV unassigned unless you specifically use a supported back-course mode.

Bravo annunciator lights are outputs, so working switches do not guarantee that the LEDs will illuminate. PC installations may require the Honeycomb software or bridge component, while individual aircraft may not expose every annunciator state. Our guide to Bravo drivers, aircraft profiles and annunciator-light faults covers that separate layer of the setup.

Final control check

A short ground check catches almost every dangerous Honeycomb mapping error before take-off.

• Move the Alpha through full pitch and roll travel and confirm that every control surface moves in the correct direction.
• Roll the trim wheel forward for nose-down trim and aft for nose-up trim.
• Move each power lever alone and verify that only its corresponding DA62 engine responds.
• Step the flaps through UP, T/O and LDG, then back to UP.
• Confirm that the gear lever commands the expected position while the aircraft is safely on the ground.
• Engage and disconnect the autopilot, then test each mapped mode individually rather than assuming the Bravo labels guarantee the correct function.