-
Notifications
You must be signed in to change notification settings - Fork 387
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
Issue with ROS2 bridges and roslibjs services/actions #395
Comments
I don't know anything about integration/compatibility of ROS2. Maybe @RobotWebTools/ros2-0 can help you out. |
ROS 1 uses topics for action but ROS 2 uses a combination of services and topics. roslibjs uses a topic implementation ie, ROS 1. I am also looking for a fix but am unable to find it. I currently use a ROS 2 action client with the subscriber in python which listens to roslibjs and sends the goal. If you have found a fix please let me know. I also tried ros 2 branch but the implementation is the same. |
Hi guys, any news on this matter? we have been developing a bunch of actions and when trying to connect to the web interface we run into this problem.. any advances? if not, @mypsybot could you give some more detail of your workaround solution please? |
Hi all, I am getting below messages.
also roslibsj core trying to use this like below;
|
Is there any update on this? I am trying to call some actions from my websitem but get similar error as above: Is |
I will repeat myself: "I don't know anything about integration/compatibility of ROS2. Maybe @RobotWebTools/ros2-0 can help you out." |
Sure, i am just asking whom ever is familiar since it seems it got lost. :) |
We recently merged official ROS 2 action support in both rosbridge_suite and this repo: There are tests and examples with these changes. If this is still applicable for people in this thread, I hope you get to try these out! |
I have same error , and i try to update ros_bridge for ros2 Humble , codevar ActionClient = new ROSLIB.ActionClient ({ I am getting below messages: |
Hi all. I have been posting a number of issues across the org lately trying to decipher exactly where an issue is occurring with ROS2 versions of many of these libraries. I think, based on some of the errors and feedback in the following issues that it come down to the roslibjs library.
Existing Issues:
rosbridge_suite:552
ros2-web-bridge:#171
Basically, it seems that when roslibjs attempts to create anything other than a publisher/subscriber connection, it looks for the wrong message type (i.e., the ROS1 version instead of the ROS2 version):
(from the rosbridge_suite issue):
For exhaustion of links, it seems like there is some discussion of this parity issue: ros2-web-bridge:148
Is there any interest in remedying this?
In the meantime, we might be able to co-opt the fact that roslibjs just ends up expecting "topics" regardless of it being a topic, service, or action (from what I see). Might I just be able to create a bunch of messages and topics that mirror what roslibjs is expecting? Am I right in this understanding?
The text was updated successfully, but these errors were encountered: