How We Built a Flight Controller Configurator for a UAV Client

The context: firmware work that revealed a usability gap

Tykho Electronics develops electronics and UAVs, from flight controllers and flight stacks to complete drone platforms. Our cooperation began when Tykho needed firmware expertise to accelerate flight-controller development: we produced technical documentation, developed the electronics architecture and handled low-level firmware tasks.

Supporting the firmware gave us a close view of how people actually set up the product. Once the core deliverables were in place, we proposed, on our own initiative, a tool that would make that setup easier for Tykho's users, especially those new to drones.

Why drone setup is hard for beginners

A drone is not ready to fly when the hardware is built and the firmware is flashed. Every unit still needs configuration: flight modes, sensor calibration, motor parameters and safety limits all have to be set before a stable flight is possible.

Open-source configurators such as Betaflight and INAV are the standard for experienced pilots and engineers. They expose a great many settings, which is exactly what makes them overwhelming for newcomers and for businesses that only need a few essential steps.

The approach: a companion tool, not a competitor

The goal was not to replace full-scale configurators but to build a companion product for Tykho hardware. Taking inspiration from Betaflight, we kept only the essential setup steps and added presets tuned for Tykho's flight stacks, so users start from stable, tested defaults instead of a blank configuration.

The configurator is built on the foundations of Betaflight and is also compatible with INAV firmware, which widens the range of drone applications it can serve.

Behind the interface: a browser talking directly to the flight controller

We built the configurator with Angular, a framework usually used for web front ends. Here there is no client-server model: the app runs locally and communicates with the flight controller directly over a serial port from the browser. That makes it independent of the operating system and driver setup, and it works without an internet connection, in a field, on a farm or at a remote site where last-minute calibration is needed.

The flight controller speaks MSP (MultiWii Serial Protocol), a compact binary protocol used by Betaflight and INAV. Our engineers wrote custom byte-level encoders and decoders so the browser could build each command and parse each response. To match the firmware exactly, the team studied Betaflight's open-source code to see how commands are structured and executed, then adapted those mechanisms to Tykho's firmware.

// MSP v1 request frame: '$' 'M' '<' | size | command | payload | checksum
// The checksum is the XOR of the size, command and payload bytes.
function encodeMspV1(command: number, payload: Uint8Array = new Uint8Array()): Uint8Array {
  const frame = new Uint8Array(6 + payload.length);
  frame.set([0x24, 0x4d, 0x3c, payload.length, command]);
  frame.set(payload, 5);
  let checksum = payload.length ^ command;
  for (const b of payload) checksum ^= b;
  frame[frame.length - 1] = checksum;
  return frame;
}

Responses come back with a '$M>' header, or '$M!' for an error, and have to be reassembled from a byte stream that may arrive in fragments. Getting this reliable took patience, experimentation and some reverse engineering, but it moves the complexity from the user to the tool.

What this changes for a drone hardware maker

For a company that sells and maintains its own flight electronics, setup is part of the product. A configurator tuned to the hardware becomes a support and marketing instrument: fewer users stuck at first setup, consistent defaults across units, and a direct channel to the people flying the hardware. Partners testing the tool have already sent requests for enhancements, and it is expected to evolve alongside Tykho's flight systems.

If you are planning a configurator for your own hardware