uORB Messaging
Last updated
Last updated
The uORB is an asynchronous publish() / subscribe() messaging API used for inter-thread/inter-process communication.
Look at the tutorial to learn how to use it in C++.
uORB is automatically started early on bootup as many applications depend on it. It is started with uorb start. Unit tests can be started with uorb_tests.
New uORB topics can be added either within the main PX4/PX4-Autopilot repository, or can be added in an out-of-tree message definitions. For information on adding out-of-tree uORB message definitions, please see .
To add a new topic, you need to create a new .msg file in the msg/ directory and add the file name to the msg/CMakeLists.txt list. From this, the needed C/C++ code is automatically generated.
Have a look at the existing msg files for supported types. A message can also be used nested in other messages.
To each generated C/C++ struct, a field uint64_t timestamp will be added. This is used for the logger, so make sure to fill it in when publishing the message.
To use the topic in the code, include the header:
By adding a line like the following in the .msg file, a single message definition can be used for multiple independent topics:
Then in the code, use them as topic id: ORB_ID(offboard_mission).
Publishing a topic can be done from anywhere in the system, including interrupt context (functions called by the hrt_call API). However, the topic needs to be advertised and published outside of an interrupt context (at least once) before it can be published in an interrupt context.
:::note The listener command is only available on Pixracer (FMUv4) and Linux / OS X. :::
To list all topics, list the file handles:
To listen to the content of one topic for 5 messages, run the listener:
The output is n-times the content of the topic:
:::tip On NuttX-based systems (Pixhawk, Pixracer, etc) the listener command can be called from within the QGroundControl MAVLink Console to inspect the values of sensors and other topics. This is a powerful debugging tool because it can be used even when QGC is connected over a wireless link (e.g. when the vehicle is flying). For more information see: Sensor/Topic Debugging. :::
The command uorb top shows the publishing frequency of each topic in real-time:
The columns are: topic name, multi-instance index, number of subscribers, publishing frequency in Hz, number of lost messages per second (for all subscribers combined), and queue size.
uORB provides a mechanism to publish multiple independent instances of the same topic through orb_advertise_multi. It will return an instance index to the publisher. A subscriber will then have to choose to which instance to subscribe to using orb_subscribe_multi (orb_subscribe subscribes to the first instance). Having multiple instances is useful for example if the system has several sensors of the same type.
Make sure not to mix orb_advertise_multi and orb_advertise for the same topic.
The full API is documented in platforms/common/uORB/uORBManager.hpp.
As there are external tools using uORB messages from log files, such as Flight Review, certain aspects need to be considered when updating existing messages:
Changing existing fields or messages that external tools rely on is generally acceptable if there are good reasons for the update. In particular for breaking changes to Flight Review, Flight Review must be updated before code is merged to master.
In order for external tools to reliably distinguish between two message versions, the following steps must be followed:
Removed or renamed messages must be added to the deprecated_msgs list in msg/CMakeLists.txt and the .msg file needs to be deleted.
Removed or renamed fields must be commented and marked as deprecated. For example uint8 quat_reset_counter would become # DEPRECATED: uint8 quat_reset_counter. This is to ensure that removed fields (or messages) are not re-added in future.
In case of a semantic change (e.g. the unit changes from degrees to radians), the field must be renamed as well and the previous one marked as deprecated as above.