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

Problems with network setup involving Sawyer robot arms

asked 2019-06-21 11:40:53 -0500

tkrane gravatar image

I was working on a Sawyer robot arm (specifically, two of them plugged into the same router, but I'm just trying to get one started now). The cables got unplugged and then replugged, but the settings had been changed so the arm's weren't functioning properly. I'm a research assistant and the grad students who have been working on the robot before are on vacation, so there's a lot of stuff in the file structure that I'm not quite clear about. (Also networking really isn't my strong suit, hopefully I'll learn something here.)

So far: rebooted the robot ran "source" the contents of which are:

export ROS_MASTER_URI=http://crlSawyerRighty.local:11311
export ROS_IP=
source ~/ros_ws/devel/setup.bash

ifconfig shows as the IP of the computer, /etc/hosts has CRLSawyerRighty.local. This IP can be pinged successfully.

At this point: rostopic list showed all of the topics associated with the robot, but did not publish data on the subject. Attempting to enable the robot caused a hang and timeout because it couldn't get /robot/state. roswtf was telling me 'connection refused', so I tried rosnode cleanup and rebooting the robot. At this point, rostopic list does not show anything. Attempting to run roscore completes, but says "ROS_MASTER_URI [http://crlSawyerRighty.local:11311] host is not set to this machine" and runs the master on the computer ( I've gone through various tutorials and support questions and nothing seems to be working. Thanks for any advice.

edit retag flag offensive close merge delete


For the record, I'm working with a Barrett hand on the same system, and rostopic has previously and still works fine with it, and it's functioning correctly.

tkrane gravatar image tkrane  ( 2019-06-21 13:35:01 -0500 )edit

From a fully 'source'd terminal on your computer, while attached to the robot, can you please update your question with the output of the following:
$ env | grep ROS
$ rosnode list -a
This should help us see if there's a disagreement on ROS environment variables between your computer and robot.

imcmahon gravatar image imcmahon  ( 2019-06-22 09:36:54 -0500 )edit

Also, you seem to be a pretty advanced ROS user, but the file was created to simplify the ROS networking experience with the robot. Just modify the top environment variables and execute the script to enter a (hopefully correctly configured) ROS shell

imcmahon gravatar image imcmahon  ( 2019-06-22 09:51:41 -0500 )edit

env|grep ROS returns nothing but i think thats an installation issue. printenv|grep ROS works and it gives


and rosnode list -a gives   /bhand_node

(with the barrett hand running)

tkrane gravatar image tkrane  ( 2019-06-22 17:33:34 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2019-06-25 09:50:43 -0500

tkrane gravatar image

updated 2019-06-25 09:53:52 -0500

Fixed the problem. The robots were not properly set on static IP's and thus weren't connecting correctly. We rebooted the arms and used the Field Service Menu to set the IP to static (in this case, for the IP, for the mask, for the gateway). Once rebooted the computer recognized the robot.

FSM help:

Obviously only directly applicable to Sawyer but the static IP problem might be helpful to other people.

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2019-06-21 11:40:53 -0500

Seen: 1,650 times

Last updated: Jun 25 '19