Dave's profile - activity

Thanks, I appreciate the fix! Rosbridge is a great tool!

Hi, I'm having a problem where rosbridge.py closes websocket connections immediately on Fuerte. This may be related to changes in the timing functions. Originally ROSProxy.py used roslib.rostime, which no longer seems to exist on Fuerte. Perhaps the rospy.rostime behavior is not the same in some important way? The related compile question is available here:

http://answers.ros.org/question/33825/rosbridge-error-in-rosproxypy-on-fuerte-with

rosbridge.py fails on Fuerte after trying to import roslib.rostime. It seems like this problem can be fixed by replacing all 3 instances of "roslib.rostime" in the code with "rospy.rostime" (although I haven't thoroughly tested this yet). I don't have any experience with the patching process, but I wanted to get this fix out there, and I would appreciate it if someone could update the code. Here was the original error:

Traceback (most recent call last): File "/opt/ros/fuerte/stacks/brown_remotelab/rosbridge/bin/rosbridge.py", line 2, in <module> from ROSProxy import ROSProxy File "/opt/ros/fuerte/stacks/brown_remotelab/rosbridge/bin/ROSProxy/__init__.py", line 1, in <module> from ROSProxy import ROSProxy File "/opt/ros/fuerte/stacks/brown_remotelab/rosbridge/bin/ROSProxy/ROSProxy.py", line 6, in <module> import roslib.rostime ImportError: No module named rostime

I just had the same issue. I fixed it by editing the .rviz/display_config file that rviz was using by default. I basically just deleted most of it, and then rviz launched sucessfully.