-
Notifications
You must be signed in to change notification settings - Fork 18
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
ROS Dart Subscriber cannot listen to topic under some situation #4
Comments
Sure I could look into it :D |
@jeff214103 It should be fixed now. |
It works well when the code run alone, but it currently leads to some related flutter works not working. Edit 29/4: After a day of test, even the code running alone the problem happened in random (Sometimes okay sometimes failed) |
Just discover something wrong with the dart publisher. The dart subscriber works pretty fine, but the dart publisher is not able to publish data to the topic right now. Can you please take a look for that? Edit: Using the dart publisher and python simple subscriber. The setting stay the same (ROS melodic, python3.6) |
Ye, sorry about that one. I changed ROS publisher to accept whenever it should start publishing when started, but made the default false 🤦♂️. It's going to work like intended now. Also if you're going to change publishing rate (publishInterval) you'll need to call startPublishing to start sending data again |
Hi I am using the ROS nodes, and I discovered an issue in Dart Subscriber.
I am using ROS melodic, ubuntu 18.04, python3.6 for publisher, and Dart for subscriber.
Usually in ROS, a simple listener can listen to the topic even it is one time pub or re-run the publisher code (Following the tutorial ROS wiki - Simple python publisher and subscriber)
However, I notice that this subscriber is not able to that.
As long as the publisher code running in ROS, it works fine. However, once I would like to re-run the publisher, it would require me to re-subscribe (unsubscribe then subscribe) to listen to publisher again. One time pub cannot even listen the msg.
Is it possible to give a fix for that? Thank you so much
The text was updated successfully, but these errors were encountered: