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

"ImportError: No module named deserialize" when launching ur5_bringup.launch

asked 2014-10-27 09:02:22 -0500

rkeatin3 gravatar image

updated 2014-10-27 10:47:11 -0500

When I attempt to run the command roslaunch ur_bringup ur5_bringup.launch robot_ip:=172.22.22.2, I get the following output:

... logging to /home/rkeatin3/.ros/log/5d470f28-5de0-11e4-aa81-fc4dd43d9838/roslaunch-dscl-rosstation-02-13666.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://dscl-rosstation-02:45140/

SUMMARY
========

PARAMETERS
 * /robot_description
 * /robot_ip_address
 * /rosdistro
 * /rosversion
 * /tf2_buffer_server/buffer_size

NODES
  /
    robot_state_publisher (robot_state_publisher/state_publisher)
    tf2_buffer_server (tf2_ros/buffer_server)
    ur_driver (ur_driver/driver.py)

auto-starting new master
process[master]: started with pid [13683]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 5d470f28-5de0-11e4-aa81-fc4dd43d9838
process[rosout-1]: started with pid [13696]
started core service [/rosout]
process[robot_state_publisher-2]: started with pid [13708]
process[ur_driver-3]: started with pid [13726]
process[tf2_buffer_server-4]: started with pid [13727]
Traceback (most recent call last):
  File "/opt/ros/hydro/lib/ur_driver/driver.py", line 19, in <module>
    from deserialize import RobotState, RobotMode
ImportError: No module named deserialize
[ur_driver-3] process has died [pid 13726, exit code 1, cmd /opt/ros/hydro/lib/ur_driver/driver.py 172.22.22.2 __name:=ur_driver __log:=/home/rkeatin3/.ros/log/5d470f28-5de0-11e4-aa81-fc4dd43d9838/ur_driver-3.log].
log file: /home/rkeatin3/.ros/log/5d470f28-5de0-11e4-aa81-fc4dd43d9838/ur_driver-3*.log

I've been unable to find any posts with the same answer. I checked the roslaunch log file, but it doesn't have any more useful information. Any ideas?

Edit: I'm using hydro, installed from debs.

edit retag flag offensive close merge delete

Comments

ROS version, driver version, from source, from debs, etc (I know some of it is visible in your console copy/paste, but still).

gvdhoorn gravatar image gvdhoorn  ( 2014-10-27 10:25:26 -0500 )edit

I'm not sure what you mean by driver version, but all of my packages should be up-to-date.

rkeatin3 gravatar image rkeatin3  ( 2014-10-27 10:48:01 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2014-10-27 12:47:23 -0500

gvdhoorn gravatar image

updated 2014-10-28 04:26:19 -0500

I can't give you any solution right now, but I've created an issue at the universal_robot repository. See universal_robot/issues/134.


Edit: just proxying for the Github issue:

this is a known issue with the currently released (v1.0.3) Hydro debs and will be fixed in the next release. The hydro-devel branch already contains the fix, so if you build the universal_robot repository from source, things should start working again for you.

Alternatively, you could temporarily add the ur_driver directory to your $PYTHONPATH:

export PYTHONPATH=$PYTHONPATH:/opt/ros/hydro/lib/python2.7/dist-packages/ur_driver/

after sourcing your setup.bash (don't forget to remove this once fixed debs have been released).

edit flag offensive delete link more

Question Tools

Stats

Asked: 2014-10-27 09:02:22 -0500

Seen: 474 times

Last updated: Oct 28 '14