-
Notifications
You must be signed in to change notification settings - Fork 1
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
No error when tcpros is not compiled, but yarp node is being used to publish to ROS topic #9
Comments
Hi, Tobias, thank you for reporting this issue. Please note that similar problems may happen also if you have not properly set the ip addresses of the machines in your /etc/hosts files or if yarp is bound to 127.0.1.1 instead of the ip address of your network interface. This is another issue frequently reported by users. |
Related to robotology/yarp#722 and robotology/yarp#1679 . |
Hi @Nicogene, EDIT: |
Hi @Tobias-Fischer !
Yes it could be a nice idea! My only concern is that the overhead introduced by the call of |
Related issue on the nature of |
@Tobias-Fischer: On the client should not be necessary. Each carrier is searched for as a plugin, and if the plugin is not found an error is already printed.
or if I try to use a non existing carrier:
So that check is already implemented at the connection level. |
Hi @barbalberto, |
This could be a good idea, but |
I don't think this is a big issue, since |
👍 |
This is strongly related to the issues with the known issues of the I'd start adding a property to the An alternative could be adding some specific command to the nameserver protocol... i.e. in node init This check could also replace all the ROS configuration in the |
@Tobias-Fischer The example was just to have a simple test. |
Hi,
We were playing around today to set up the joint state publisher using the
ControlBoardWrapper
as described in http://www.yarp.it/classyarp_1_1dev_1_1ControlBoardWrapper.htmlIt took us a while to realize that we did not get an output on the ROS topic because we did not have the
ENABLE_yarpcar_tcpros
flag enabled. The ROS topic was created just fine, androstopic info
showed the proper type etc.; there was just no output.It would be great if there was a warning / error message somewhere if that happens.
Best, Tobi
The text was updated successfully, but these errors were encountered: