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

Revision history [back]

Thank you for your response, we are trying to reset properly our network since. I will keep you in touch but it should work properly after that.

Thank you Hello, Sorry for your response, the long time to answer. So, we are trying manage to reset properly set up the vpn through the base station. The robot is now connected in wifi to the building's network and our network since. I will keep you in touch but computer connects it should work properly after that. through the building's network

From the base station, everything is working fine but from another computer messages are not received. We tried to publish a topic from the robot and to suscribe from our computers and the base station: we can see that our computer has subscribed to the node on the robot, but we get nothing ( whereas no problem from the base station).

Our ROS_MASTER_URI is pointing on c1's IP through the base station (PRx1 from 14.1.3 of the manual ), no ROS_IP nor ROS_HOSTNAME is set.

We can ping the robot and connect it with ssh from our computer.

We are wondering if it is a ROS configuration problem or still a network problem.

(edited) Hello, Sorry for the long time to answer. So, we manage to set up the vpn through the base station. The robot is now connected in wifi to the building's network and our computer connects it through the building's network

From the base station, everything is working fine but from another computer messages are not received. We tried to publish a topic from the robot and to suscribe from our computers and the base station: we can see that our computer has subscribed to the node on the robot, but we get nothing ( whereas no problem from the base station).

Our ROS_MASTER_URI is pointing on c1's IP through the base station (PRx1 from 14.1.3 of the manual ), no ROS_IP nor ROS_HOSTNAME is set.

We can ping the robot and connect it with ssh from our computer.

We are wondering if it is a ROS configuration problem or still a network problem.