-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve documentation on integration #42
Comments
Hi @fsteff, My plan is to add in this repo some examples of Zenoh applications that are compatible with some of the ROS 2 demos (e.g. |
Thanks, that would be very useful. Maybe I can support the community by releasing the library I'm working on as open source (don't have greenlight from my employer for this yet, but we talked about doing so once it's stable). |
That would be great! Are you aware of the incoming rmw_zenoh ? Once done, it will be useable via |
For now we don't plan to implement it in other languages, though maybe we'll need to support C++ as well (for future projects).
The whole point of building our own library is that it will be lightweight and easy to use. For now we'll only support ROS actions (and maybe services/topics). In the zenoh-to-zenoh usecase (without ROS) the encoding is JSON, which also reduces complexity. |
Improve documentation on integration
I want to build a zenoh-native application that uses this plugin for compatibility with ROS2, but I could not find any documentation on how exactly the ROS2 services and actions are mapped to Zenoh Queryables.
More specifically, I plan to build a python library for using ROS actions from "outside" of a ROS environment. AFAIK this plugin does exactly what I need for that purpose, but unfortunately am having difficulties finding the required details details in the code.
(as mentioned in "Easier integration with Zenoh native applications (services and actions are mapped to Zenoh Queryables)"
e.g. are parameters (such as goal_id) of the actions mapped to the Zenoh Selector, or are they just appended to the query as a value?
The text was updated successfully, but these errors were encountered: