Repository Summary
Checkout URI | https://github.com/PX4/px4_msgs.git |
VCS Type | git |
VCS Version | ros1 |
Last Updated | 2023-09-20 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
px4_msgs | 1.0.0 |
README
px4_msgs
This package contains the ROS(1) message definitions of the PX4 Pro ecosystem. Building this package generates all the required interfaces to interface ROS nodes with the PX4 autopilot internals, which use the uORB messaging API. Currently the messages of this package represent a dependency to px4_ros_com
package ros1
branch. The interface with PX4 is only possible using the ros1_bridge
and px4_ros_com
, which bridges the ROS topics with the ROS2 topics.
uORB message definitions
The uORB message definitions, which represent the counter-part of these ROS messages found in this package, can be found on the PX4 Firmware repository.
How are these messsage definitions generated?
The PX4 Firmware Jenkins-based CI/CD deploys new messages or modifications to the current definitions with each build of the master branch of the PX4 Firmware. A future improvement will also include tagging and releasing this repository according to the tags/releases of the PX4 Firmware, for a more tide coupling between the message definitions.
Install, build and usage
Check this section of the ROS tutorials in order to understand how to create and build msg and srv files. Check the RTPS/ROS2 Interface section on the PX4 Devguide for further details on how this integrates with the px4_ros_com
package.
Bug tracking and feature requests
Use the Issues section to create a new issue. Report your issue or feature request here.
Questions and troubleshooting
Reach the PX4 development team on the #messaging
PX4 Slack channel:
CONTRIBUTING
Contributing
Do not commit changes directly to this repository that change the message definitions. All the message definitions are directly generated from the uORB msg definitions on the PX4 Firmware repository. Any fixes or improvements one finds suitable to apply to the message definitions should be directly done on the uORB message files. The deployment of these are taken care by a Jenkins CI/CD stage.
Contributing to the PX4 Firmware repository (or to this repository, not including message definitions)
Follow the Contributing
guide from the PX4 Firmware repo.