597372bec9
On SPM4649T receivers with firmware versions at least 1.1RC9, the serial data will contain an rssi value in dbm, as outlined in the Remote Receiver Interfacing document section 8.3.1. If the value received is greater than or equal to zero, the receiver does not support rssi data, and the incoming value will be ignored. However, if the value is negative, we can use the rssi value. When we have a valid rssi, it gets mapped to a percentage from 0 to 100 as expected by mavlink. This mapping is constructed as a logarithmic function over Spektrum's published minimum and maximum rssi values, -92dBm to -42dBm as 0 to 100: 100 Log10[1 + (x - min) * (9 / (max - min))] This change updates all calls to the dsm input rountes to return the rssi value. Note that one place this doesn't work with the px4io enabled. There is a comment left in the absence of analog rssi that: "we do not actually get digital RSSI regs[PX4IO_P_RAW_RC_NRSSI]". This restriction has been left in place, as removing it exposes a problem where the frequency of the control tick is greater than that of valid dsm frames so the rssi isn't valid every cycle.
PX4 Pro Drone Autopilot
This repository holds the PX4 Pro flight control solution for drones, with the main applications located in the src/modules directory. It also contains the PX4 Drone Middleware Platform, which provides drivers and middleware to run drones.
- Official Website: http://px4.io (License: BSD 3-clause, LICENSE)
- Supported airframes (portfolio):
- Multicopters
- Fixed wing
- VTOL
- many more experimental types (Rovers, Blimps, Boats, Submarines, etc)
- Releases: Downloads
PX4 Users
The PX4 User Guide explains how to assemble supported vehicles and fly drones with PX4. See the forum and chat if you need help!
PX4 Developers
This Developer Guide is for software developers who want to modify the flight stack and middleware (e.g. to add new flight modes), hardware integrators who want to support new flight controller boards and peripherals, and anyone who wants to get PX4 working on a new (unsupported) airframe/vehicle.
Developers should read the Guide for Contributions. See the forum and chat if you need help!
Weekly Dev Call
The PX4 Dev Team syncs up on a weekly dev call.
Note
The dev call is open to all interested developers (not just the core dev team). This is a great opportunity to meet the team and contribute to the ongoing development of the platform. It includes a QA session for newcomers. All regular calls are listed in the Dronecode calendar.
Maintenance Team
- Project: Founder - Lorenz Meier, Architecture: Daniel Agar
- Communication Architecture
- UI / UX
- Multicopter Flight Control
- VTOL Flight Control
- Fixed Wing Flight Control
- Racers - Matthias Grob
- OS / drivers - David Sidrane
- UAVCAN / Industrial - Pavel Kirienko
- State Estimation - James Goppert, Paul Riseborough
- Vision based navigation
- Obstacle Avoidance - Martina Rivizzigno
- Snapdragon
- Intel Aero
- Raspberry Pi / Navio - Beat Kueng
- Airmind MindPX / MindRacer - Henry Zhang
- RTPS/ROS2 Interface - Vicente Monge
See also About Us (px4.io) and the contributors list (Github).
Supported Hardware
This repository contains code supporting these boards:
- Snapdragon Flight
- Intel Aero
- Raspberry PI with Navio 2
- Parrot Bebop 2
- FMUv2.x
- FMUv3.x Pixhawk 2
- FMUv4.x
- FMUv5.x (ARM Cortex M7, future Pixhawk)
- Gumstix AeroCore (only v2)
- Airmind MindPX V2.8
- Airmind MindRacer V1.2
- Bitcraze Crazyflie 2.0
Additional information about supported hardware can be found in PX4 user Guide > Autopilot Hardware.
Project Roadmap
A high level project roadmap is available here.