#ros #websocket #json #async


An library for interfacing with the ROS's rosbridge_server

9 releases (breaking)

0.9.0 May 13, 2024
0.8.0 Oct 4, 2023
0.7.0 Mar 13, 2023
0.6.0 Dec 16, 2022
0.5.2 Oct 31, 2022

#8 in Robotics

Download history 15/week @ 2024-01-29 28/week @ 2024-02-12 13/week @ 2024-02-19 41/week @ 2024-02-26 122/week @ 2024-03-04 38/week @ 2024-03-11 16/week @ 2024-03-18 7/week @ 2024-03-25 46/week @ 2024-04-01 2/week @ 2024-04-08 7/week @ 2024-04-22 10/week @ 2024-04-29 31/week @ 2024-05-06 166/week @ 2024-05-13

214 downloads per month
Used in geist_common

MIT license



Noetic Galactic Humble Iron License:MIT

This package aims to provide a convenient intermediary between ROS1's rosbridge and Rust similar to roslibpy and roslibjs.

Information about the protocol can be found here.

Note on documentation: All information about the crate itself (examples, documentation, tutorials, etc.) lives in the source code and can be viewed on docs.rs. This readme is for "Meta" information about developing for the crate.

Fully Supported via rosbridge: Noetic, Galactic, Humble.

Code Generation of ROS Messages

The crates roslibrust_codegen and roslibrust_codegen_macro support code generation in Rust for ROS1 and ROS2 message, service, and action files. Many of the examples use the macro for convenience. find_and_generate_ros_messages is a macro which accepts an optional list of paths relative to the project workspace directory and will additionally check the ROS_PACKAGE_PATH environment variable for paths to ROS packages.

It's used like this:


Code generation can also be done with a script using the same code generation backend called by the macro. See the contents of example_package for a detailed example of how this can be done. While the proc_macros are extremely convenient for getting started there is currently no (good) way for a proc_macro to inform the compiler that it needs to be re-generated when an external file changes. Using a build script requires more setup, but can correctly handling re-building when message files are edited.

Experimental Support for ROS1 Native

If built with the ros1 feature, roslibrust exports some experimental support for implementing nodes which talk to other ROS1 nodes using the TCPROS protocol without the need for the rosbridge as an intermediary. See ros1_talker.rs and ros1_listener.rs under roslibrust/examples to see usage. This implementation is relatively new, incomplete, and untested. Filing issues on bugs encountered is very appreciated!

See this issue filter for known issues: https://github.com/Carter12s/roslibrust/labels/ros1


Rough overview of the features planned to built for this crate in what order:

Feature rosbridge ROS1 ROS2
examples x
advertise / publish x
unadvertise x x
subscribe x
unsubscribe x x
services x x
rosapi ✅ (ROS1 only for now) N/A N/A
TLS / wss:// Should be working, untested N/A N/A
ROS2 msgs length limits Planned N/A x
cbor Planned N/A N/A
rosbridge status access Planned N/A N/A
rosout logger Planned x x
auth Planned N/A N/A
fragment / png Uncertain if this package will support x N/A
cbor-raw Uncertain if this package will support N/A N/A


Contribution through reporting of issues encountered and implementation in PRs is welcome! Before landing a large PR with lots of code implemented, please open an issue if there isn't a relevant one already available and chat with a maintainer to make sure the design fits well with all supported platforms and any in-progress implementation efforts.

Rust Version for Development

Due to cargo 1.72 enabling "doctest-in-workspace" by default it is reccomended to use Rust 1.72+ for develop. Previous rust versions are support but will require some incantations when executing doctests.

Running Tests

There are various unit tests and integration tests behind feature flags. For tests with ROS1, both through rosbridge and native clients, you'll need a locally running rosbridge_websocket node and rosmaster. Then run with cargo test --features "ros1_test ros1". For tests with ROS2, you'll need a running rosbridge server, then run with cargo test --features "ros2_test". You can find relevant Dockerfiles and docker compose configurations udner the docker directory.


~358K SLoC