mavlink/c_uart_interface_example

Simple MAVLink to UART interface example for *nix systems

Hosted by Linux Foundation

View on GitHub ↗Jump to charts ↓

mavlink/c_uart_interface_example has 300+ stars and 250+ forks on GitHub, is written in C++, and was last pushed on Apr 1, 2024. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 25 minutes ago
Added to GitGenius on October 15th, 2026
Created on August 18th, 2012
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 258
Total Stargazers: 308 (+0)
Total Subscribers: 31 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.3 hours
Mean response time: 6.3 hours
90th percentile: 6.3 hours
Tracked items: 1

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

C-UART Interface Example is a reference implementation for MAVLink communication over UART on Unix-like systems that enables offboard computers to interact with Pixhawk autopilots.

The tool addresses the need to establish reliable serial communication between a Pixhawk flight controller and an external computer. It demonstrates how to receive and send individual MAVLink messages over a UART connection, which is preferred over USB for flight-critical operations due to the simpler and more trusted driver implementation. The example handles port detection, message serialization, and the basic send-receive loop required for autopilot communication.

This project suits developers building offboard control systems, companion computer applications, or learning MAVLink protocol integration. It works with Pixhawk hardware connected via USB programming cable, Telemetry Radio on TELEM1 or TELEM2 ports, or FTDI developer cables on various serial ports. The example is intentionally minimal, showing only one receive and one send operation, making it suitable as a starting point for custom applications rather than a complete communication framework. Developers can extend it by modifying message types or adding additional send-receive cycles.

The project maintains a straightforward, focused codebase with clear documentation of hardware setup and port mappings for different Pixhawk UART configurations. The README provides specific guidance on device enumeration, connection options including Telemetry Radio and FTDI cable alternatives, and integration with the PX4 simulator. The exploration section outlines concrete next steps for extending the example, such as modifying message data types or adding NuttX shell debugging output.