-
Notifications
You must be signed in to change notification settings - Fork 2
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
Some problems I had testing connectivity with the ros1 framework #4
Comments
Thanks for the detailed write-up! I never intended this as a drop in replacement (more to bridge custom tools to the ROS world eg. for visualization).
I might help to have RUST_LOG=DEBUG in the core for standard ros tooling compatibility (rostopic echo chatter,...) |
Thank you for your reply, I will take a serious look. |
Hi @jackyliu16, I know it's been a year, but if this is still of interest to you, could you check again with the current version? I had similar issues with rosbag, and it turned out the bug was fixed in one of ros-core-rs's dependencies a while ago. The current git main version of ros-core-rs does pull in that fix now. |
As lack of activity and trusting @jobafr explanation, this issue seems to be resolved. |
I was trying to simple use ros-core-rs as a kind of standalone software, unlike sync application you provide, I using the publisher subscriber example of rosrust.
Environment:
Ubuntu 22.04
nix-ros-overlay noetic
=====
publisher.rs
subscriber.rs
When I'm trying to use this kind of packages, connect with local rospy package talker_listern from beginner_learnning, using cargo run as a kind of master. I found rosrust example is capable to connection to master and send message to rospy packages though topic.
These are a few questions I had during my brief test, and I would appreciate it if anyone could answer them or helpping in it.
The text was updated successfully, but these errors were encountered: