ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

The problem here is that the serial_node.py is trying to get the configuration information of what topics you are publishing/subscribing from the "client". Thus, if you wanted a two-way tunnel, on each machine you would have to run the serial_node.py AND an instance of a "client", which would be a program built on one of rosserial_arduino or more likely rosserial_embeddedlinux. The program does need to know what topics are going to be pub/sub, so that it can negotiate the channels being used for each topic.

The problem here is that the serial_node.py is trying to get the configuration information of what topics you are publishing/subscribing from the "client". Thus, if you wanted a two-way tunnel, on each machine you would have to run the serial_node.py AND an instance of a "client", which would be a program built on one of rosserial_arduino or more likely rosserial_embeddedlinux. The program does need to know what topics are going to be pub/sub, so that it can negotiate the channels being used for each topic.

EDIT: this has a further complication, that the client and serial_node really can't both open the same serial port. So I'm guessing that serial_node will need to be revised in order to have it basically act as a client internally.