Ros already provides a network transparent communication protocol based on sockets. Normally, you write nodes that directly communicate with the Robot's hardware and publish the data directly via topics.
If your robot data is provided on a socket, I suggest to create a ROS node that uses whatever you are used to, e.g. libc's socket functions, to communicate with your robot. Your ros node then needs to decode the data from the socket, put it into a ros message and publish it. I don't know about any generic way for implementing such a bridge since it is highly specific for your socket based protocol and the ros messages to be published.
Correct me if I'm wrong, but ROS uses TCP underneath right? In that case, wouldn't there be a chance of a port clash?
Lorenz - many thanks for that. Just what I was asking - couldn't tell from the tut's if there was something I was missing or for this piece it was a roll my own with in a publishing node.
Mark
(For some reason I couldn't comment on your answer - apologies for using answer.)
Asked: 2012-04-23 05:19:43 -0600
Seen: 258 times
Last updated: Apr 23 '12
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
