jetdillo's profile - activity

Thanks! That looks like it might be helpful. I'll check it out and let you know what happens.

Modeling Conditional Constraints in MoveIt! I'm working with a custom robot arm that has some mechanical constraints tha

Okay, so I finally know enough about ROS to totally tie myself up in knots here. I've got my Neato laser up and running and pumping but data to the /scan topic but not seeing anything in rviz.

I'm running Groovy on a Beaglebone w/ Precise LTS (12.04).

I'm running rviz remotely on a separate laptop, also running Groovy on Precise LTS.

I have a Neato LIDAR hooked up to it, running the cwru-ros-pkg XV11 laser driver. rostopic shows the laser successfully publishing to a topic called "/scan":

ubuntu@arm:~$ rostopic list
/rosout
/rosout_agg
/scan
ubuntu@arm:~$

I'm getting data from rostopic echo on both the Beaglebone and the laptop I'm running rviz on:

armadilo@talon:~$ rostopic echo /scan
header: 
  seq: 15555
  stamp: 
    secs: 1367714272
    nsecs: 996305089
  frame_id: neato_laser
angle_min: 0.0
angle_max: 6.28318548203
angle_increment: 0.0174532923847
time_increment: 0.000163100005011
scan_time: 0.0
range_min: 0.0599999986589
range_max: 5.0
ranges: [0.2980000078678131, 0.3059999942779541, 0.3140000104904175, 0.3240000009536743, 0.3330000042915344, 0.34200000762939453, 0.35100001096725464, 0.3610000014305115

But nothing is showing up in rviz.

I'm using the cwru-ros-pkg xv11_laser_driver which publishes to the /scan topic, not sensor_msgs/LaserScan. I'm sure I'm missing a big chunk of something here but am not exactly sure what.

Any help from those who've been able to get data from their XV11 laser into rviz or other parts of the ROS stack would be appreciated.

Thanks! 'dillo

I ran into this as well and fixed it by looking at the list of held-back packages:

The following packages have been kept back:

  ros-groovy-actionlib ros-groovy-common-msgs ros-groovy-geometry
  ros-groovy-nodelet-core ros-groovy-pluginlib ros-groovy-ros
  ros-groovy-ros-comm ros-groovy-ros-tutorials ros-groovy-rosgraph
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
ubuntu@arm:~/catkin_ws$

I did a manual 'apt-get install ros-groovy-actionlib', which succeeded. That apparently released all the others except ros-groovy-rosgraph, because now apt-get upgrade reported:

The following packages have been kept back:
  ros-groovy-rosgraph
The following packages will be upgraded:
  ros-groovy-common-msgs ros-groovy-geometry ros-groovy-nodelet-core
  ros-groovy-pluginlib ros-groovy-ros ros-groovy-ros-comm
  ros-groovy-ros-tutorials
7 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 42.3 kB of archives.
After this operation, 66.6 kB of additional disk space will be used.
Do you want to continue [Y/n]? Y

Now I could apt-get install ros-groovy-rosgraph to finish the job. I was able to get roscore running successfully after this.

So there are a couple points here I guess:

1. I was able to get my Groovy install to a point where it could run roscore using the above procedure.

2. I didn't have to do a 'dist-upgrade' to get this all working.

3. Fixing install order dependencies for individual packages (if they occur) is preferable to breaking your whole OS install if a dist-upgrade goes bad for some reason.

Indeed, 'apt-get dist upgrade' should be a last resort.