What serial connection means for your flight controller
A serial connection is a direct line between your PX4 flight controller and your computer, one piece of data at a time. Unlike wireless connections that send many signals at once, serial talks to the board in a single stream. This matters because it lets you upload new firmware, read what the board is thinking in real time, and troubleshoot problems without needing a radio link or internet.
The PX4 autopilot runs on boards like the Pixhawk, Pixhawk 4, or Cube Orange. All of them have a serial port — usually labeled TELEM1, TELEM2, or Debug — that your computer can reach through a USB cable or a dedicated serial adapter. When you plug in, your computer sees the board as a new device and can start sending commands.
You will use serial connection for three main things: flashing firmware updates to the board, reading live sensor data and diagnostics, and configuring parameters that change how the autopilot behaves. Most people do this once or twice, but if you are building or testing a drone, you may do it many times.
Key Takeaways
- Serial connection requires a USB cable or serial adapter plugged into your flight controller's TELEM or Debug port, and a ground station process like QGroundControl on your computer.
- Your computer must recognize the board as a COM port (Windows) or /dev/ttyUSB device (Linux and Mac) before you can communicate with it.
- Firmware upload, parameter tuning, and live telemetry all happen over the same serial link, so you only need one cable to do all three.
- If your board does not appear as a device, the most common fixes are installing the correct USB driver, trying a different USB port, or checking that the cable is not damaged.
Choosing the right cable or adapter for your board
Most modern PX4 boards come with a USB port built in, usually a micro-USB or USB-C connector on the board itself. If your board has one, you can plug a standard USB cable directly into it and into your computer — no adapter needed. The Pixhawk 4 and Cube Orange both have this setup.
Older boards like the original Pixhawk or some custom builds may only have a serial port with exposed pins. In that case, you need a USB-to-serial adapter — a small device that converts USB on one end to serial pins on the other. Common adapters use the FTDI chip or the CH340 chip. You solder or connect the adapter's TX, RX, and GND pins to the matching pins on your flight controller, then plug the USB end into your computer.
Check your board's documentation to find which port to use. TELEM1 and TELEM2 are usually for telemetry radios, but they also work for serial connection. The Debug port is often the fastest and most direct route for firmware upload. If you are unsure, start with the Debug port or the built-in USB connector.
Installing drivers so your computer recognizes the board
When you plug in your flight controller for the first time, your computer needs a driver — a small piece of software that tells the operating system how to talk to the board. Without it, the board will not show up as a usable device.
On Windows, the board usually appears as a COM port (COM3, COM4, and so on). If it does not, you may need to install the FTDI driver or the CH340 driver, depending on which chip your adapter or board uses. read the driver from the chip maker's website — FTDI.com for FTDI chips, or WCH.cn for CH340 chips — and run the installer. Then unplug and replug the board. Windows should now list it in Device Manager under Ports.
On Mac, modern boards often work without a driver. If yours does not, read the FTDI or CH340 driver from the same sources, install it, and restart your Mac. The board will appear as /dev/tty.usbserial-XXXXX in the terminal.
On Linux, drivers are usually built in. Plug in the board and open a terminal. Type ls /dev/ttyUSB* to see if the board appears. If it does not, you may need to install the driver package for your chip — search your package manager for ftdi or ch340 — or add your user to the dialout group so you have permission to access the port.
Connecting with QGroundControl, the standard ground station
QGroundControl is the most common process for talking to PX4 boards over serial. It runs on Windows, Mac, and Linux, and it handles firmware upload, parameter tuning, and live telemetry all in one place. read it from qgroundcontrol.com.
After you install QGroundControl and plug in your board, open the process. In the top left corner, you will see a button that says "Vehicle Setup" or shows a connection icon. Click it. QGroundControl will scan for available serial ports and show you a list. Select the port your board is on — it will usually be labeled with the board name or a COM number — and click Connect.
If the connection works, the main window will fill with data: your board's firmware version, sensor readings, battery voltage, and GPS status if you have a GPS module. You are now talking to the board over serial. From here, you can upload new firmware by going to Firmware in the left menu, or tune parameters by clicking Parameters.
If QGroundControl does not find your port, go back and check that the driver is installed and the board shows up in Device Manager (Windows) or the terminal (Mac and Linux). If the port appears but QGroundControl will not connect, try unplugging the board, waiting five seconds, and plugging it back in.
Uploading firmware to your flight controller
Firmware is the software that runs on your PX4 board. Updates add features, fix bugs, and improve stability. You upload new firmware over the serial connection using QGroundControl.
Plug in your board and open QGroundControl. Make sure it is connected — you should see sensor data in the main window. Then click the Firmware icon in the left menu. QGroundControl will ask you to select a vehicle type (Quadrotor, Plane, Rover, and so on) and a board type. Choose the correct ones for your hardware.
Next, QGroundControl will read the latest stable firmware from the internet and show you a progress bar. Do not unplug the board or close the process while this is happening. The upload usually takes one to three minutes. When it finishes, the board will reboot and QGroundControl will reconnect automatically.
If the upload fails, the most common reason is that the board lost power or the cable was unplugged mid-upload. Unplug the board, wait ten seconds, plug it back in, and try again. If it keeps failing, check that you selected the correct board type — uploading the wrong firmware can brick the board, though it is usually recoverable by uploading the correct firmware again.
Reading live data and troubleshooting with the console
Once your board is connected, you can watch what it is doing in real time. This is useful for checking that sensors are working, seeing what the autopilot is thinking, and finding problems before they cause a crash.
In QGroundControl, click the Analyze icon in the left menu. You will see several tabs: Messages shows text output from the board, Mavlink Console lets you type commands, and Graphs plots sensor data over time. The Messages tab is the most useful for beginners — it shows warnings, errors, and status updates as they happen.
If a sensor is not working, you will usually see a message like "Compass 1 not detected" or "GPS not found". If the board is not arming (spinning up the motors), the Messages tab will tell you why — maybe the compass needs calibration, or the GPS does not have a lock yet. Read the messages, fix the problem, and watch the messages change.
You can also plot sensor data by clicking the Graphs tab and selecting what you want to see — gyroscope readings, accelerometer data, battery voltage, and dozens of other values. This is most useful after a test flight, when you want to know if the board was stable or if something went wrong.
Configuring parameters over serial
Parameters are settings that change how your autopilot behaves — things like how fast it responds to stick input, how high it climbs, and how it handles wind. You change parameters over the serial connection using QGroundControl.
With your board connected, click the Parameters icon in the left menu. You will see a long list of settings, organized by category: MC (multicopter), FW (fixed wing), VT (vertical takeoff), and so on. Each parameter has a name, a current value, and a description.
To change a parameter, click on its value, type the new number, and press Enter. QGroundControl will send the new value to the board and save it in the board's memory. Some parameters take effect when ready; others require a reboot. If you are not sure what a parameter does, hover over its name to read the description.
Be careful when changing parameters — wrong values can make your drone unstable or unsafe to fly. If you break something, you can always reset to defaults by clicking the Tools menu and selecting Reset to Defaults, then re-upload your firmware.
Frequently Asked Questions
Why does my board not show up as a COM port or /dev/ttyUSB device?
The driver is usually missing or the cable is bad. First, try a different USB port on your computer — sometimes one port is broken. Then check Device Manager (Windows) or the terminal (Mac and Linux) to see if the board appears at all, even with a warning symbol. If it does, the driver is missing — read and install it from the chip maker's website. If it does not appear anywhere, the cable may be damaged or the board may not have power.
Can I use serial connection while the drone is flying?
No. The USB cable will get in the way and pull on the board. Serial connection is for setup, testing, and troubleshooting on the ground. Once you unplug the cable, the board will reboot and you can arm and fly normally. If you want to see data while flying, use a telemetry radio instead — it sends the same information wirelessly.
What if QGroundControl connects but then disconnects after a few seconds?
This usually means the board is rebooting or the connection is unstable. Try a different USB cable — cheap or damaged cables often cause this. If you are using a serial adapter, make sure the TX and RX pins are soldered correctly and not touching anything else. You can also try a slower baud rate in QGroundControl's connection settings, though the default usually works.
Can I upload firmware to two boards at the same time?
Not with one computer and one USB port. You can only connect one board at a time. If you have two boards, upload to the first one, unplug it, plug in the second one, and upload again. If you have many boards to flash, some people use a Raspberry Pi or a dedicated flashing station, but that is beyond the scope of a serial connection.
What is the difference between TELEM1, TELEM2, and the Debug port?
All three are serial ports, but they run at different speeds and are meant for different things. TELEM1 and TELEM2 usually run at 57600 baud and are meant for telemetry radios. The Debug port usually runs at 115200 baud and is faster, making it better for firmware upload and live data. If you are connecting to your computer, use the Debug port if your board has one. If you only have TELEM ports, either one works, but upload will be slower.