-
Notifications
You must be signed in to change notification settings - Fork 8
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
How to use this repo to solve the bug in ros2-web-bridge #2
Comments
Is there any progress with this issue? |
Hi all, has there been any progress on this issue? @sunshengjin @SomaGallai @AndrewJSchoen |
Hi all, sorry for the lack of response (I haven't been using ROS2 lately). Let me try it out and see what happens on my end. |
Sounds good, thanks for the quick reply @AndrewJSchoen :) On my end, I am running into similar issues mentioned above with getting pointclouds to populate using ros3djs and tf2_web_republisher. |
@brockpatchin If you have a minimal example workspace that might help me determine the issue. |
Sure. I am following this tutorial (https://github.com/RobotWebTools/ros3djs/blob/develop/examples/pointcloud2.html) except I am using a realsense d435i. An error keeps popping up on my rosbridge_server terminal that says something along the lines of "[rosbridge_websocket-1] [ERROR] [1678311323.546637795] [rosbridge_websocket]: [Client 4281e172-6c6c-4cb4-8bec-2dd41321b535] [id: advertise:/tf2_web_republisher/goal:2] advertise: Unable to import msg class TFSubscriptionActionGoal from package tf2_web_republisher. Caused by module 'tf2_web_republisher.msg' has no attribute 'TFSubscriptionActionGoal'" This is nothing to populate on the viewer object, but the pointcloud is showing on rViz. Thank you for your help in advance :) |
Still working on an issue getting a setup working on my machine. However, as I work through that, I thought I would mention a possible alternative, based on my own experiences with some aspects of the RobotWebTools materials. I generally had a lot of issues with getting the default tools working, hence why I made this repo (as part of that exploration). However, the thing I was trying to do was actually to create an interface for users, and found that while their In terms of usage, you could write a subscriber to broadcast the data from the backend as a json string, and then parse on the front-end, and populate the data in the scene yourself. An example of setting up subscribers in that way can be found here and an example of updating the scene can be found here (last example doesn't use ROS, and instead uses a separate backend, but it gives the idea). Long story short, still working out the issues with this (but I may be a bit sparse in responding because I am going to be away), but this other thing may work for you, depending on what exactly you are trying to accomplish, and how you are doing it. Let me know if you have any questions on any of that! |
Thank you very much @AndrewJSchoen for the in-depth response :) I will try out the robot-scene library that you mentioned above! I am trying to also build a user interface for a robot currently with a group of students for our senior project (undergraduate) so we are still relatively new to all of this stuff! It is truly appreciated that you took the time to respond to help us out! |
Hi Andrew!
I am also developing ros2 and ros2-web-bridge related applications, and I also facing some problems related to tf2-web-republisher. Here is log:
I think the problem with tf2-web-republisher messages has caused me to be unable to use ros2djs or ros3djs to display all tfClient-related widgets, such as pose, laserscan, etc.
When I searched for the solution to this problem, I found that you are also tracking similar problems and found this repo. I copied this repo to my ros2 workspace and compiled it. Then recompiled ros2-web-bridge. But the problem has not been solved. Because of the lack of documentation, I don’t know if what I did is correct.
Do you have any progress now? Or the correct use of this branch to solve the problem of tf2-web-bridge?
Looking forward to your reply!
Thanks again!
The text was updated successfully, but these errors were encountered: