How 987419640/firmware works
Project Type & Purpose
• PX4 is an embedded flight‐control firmware for drones.
• It comprises:
• A hardware abstraction layer (board & platform drivers)
• A publish-subscribe middleware (“uORB”)
• A suite of modules (flight control, estimation, navigation, communications)
• Communication bridges (MAVLink, UAVCAN, micro-RTPS)
• Build/deployment for both bare-metal (NuttX) and simulation (POSIX SITL)
High-Level Component Breakdown
a. Hardware Abstraction
• Boards/Platform directories → board-specific init, bus drivers (I²C, SPI, UART)
• src/drivers → sensor, actuator, telemetry drivers
• RTOS ports: platforms/nuttx & platforms/posix & platforms/qurt
b. Core Middleware
• uORB → publish/subscribe bus (src/modules/uORB)
• Work queue / scheduled tasks (px4_work_queue)
• Parameter server (flashparams, parameters_injected.xml)
• Logging (modules/logger + log_writer)
• Build system & scripts (CMakeLists.txt, Tools/docker_run.sh, .ci, Travis, Jenkins)
c. Application Modules
• Estimation (ekf2, attitude_estimator_q)
• Flight control
– mc_att_control & mc_pos_control (multirotor)
– fw_att_control & fw_pos_control (fixed wing)
– vtol_att_control
• Vehicle management (modules/commander, navigator, dataman)
• Safety & watchdog (circuit_breaker, commander/failure_detector)
d. Communications & External Interfaces
• MAVLink bridge (modules/mavlink) → telemetry links to ground station (e.g. QGroundControl)
• UAVCAN nodes & ESC servers (drivers/uavcan, drivers/uavcanesc)
• micro-RTPS bridge (modules/micrortps_bridge) → ROS2 / PX4-Fmw link
• POSIX SITL launch scripts & simulators (launch/, Tools/sitl_*.sh)
Relationships & Data Flow
• Modules subscribe to uORB topics, process data, and publish control outputs
• Actuator drivers consume control outputs (PWM, CAN)
• Communication modules (MAVLink/UAVCAN/RTPS) tap into uORB to forward telemetry/commands
• Scheduler/WorkQueue governs module run timing (rate, priorities)
• Parameter subsystem configures modules at startup and on-the-fly
Architectural Patterns & Principles
• Layered architecture: Drivers → Middleware → Modules → External
• Pub/Sub decoupling (uORB) ensures modular, testable modules
• Platform‐abstraction via CMake and “platforms/…” enables NuttX vs. POSIX builds
• Plugin‐style modules auto‐registered via CMake (px4_add_module)
• CI/CD pipelines target SITL tests, hardware builds, code coverage