Firmware · PX4
PX4 firmware development.
Custom modules, drivers, flight modes and control allocation inside the PX4 autopilot — with a ROS 2 path and a simulation harness from day one.
Where we work inside PX4
- Custom uORB modules — new estimators, controllers or mission behaviors as first-class PX4 modules.
- Flight modes — in-firmware modes, or external modes over the ROS 2 / uXRCE-DDS interface when iteration speed matters more than latency.
- Control allocation — effectiveness matrices for tilt-rotor, coaxial, hybrid VTOL and other non-standard configurations.
- Drivers — SPI/I²C/UART/CAN sensor drivers, ESC telemetry, and custom payload interfaces.
- Board support — NuttX board configs for new hardware, bootloader and parameter defaults.
- Estimator configuration — EKF2 tuning and external vision / GPS-denied inputs.
How we keep your fork healthy
A PX4 fork that can't rebase is a liability. We structure customizations as discrete modules and patches, track a named upstream release, and document the rebase procedure so your team can follow PX4 forward without us.
Test before flight
Every PX4 change ships with a Gazebo SITL scenario and, where hardware allows, a HIL configuration. See simulation.
Good fit when
- You need ROS 2 native integration
- Permissive licensing is a requirement
- The airframe is multicopter, fixed-wing or VTOL
- Companion autonomy is the heart of the program