The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
As @freadx said, unplugging and replugging the kinect can help.
The openni drivers were also updated a while ago to fix a lot of problems like this. On the turtlebot laptop, run sudo apt-get update && sudo apt-get dist-upgrade to grab all the new packages and see if that helps.
Probably not related to your problem, but it is not a good idea to mix ROS versions.
| | 2 | No.2 Revision |
As @freadx said, unplugging and replugging the kinect can help.
Also, sometimes the XnSensorServer process hangs around after the driver has been killed. You can check if this is happening by running ps aux | grep XnSensorServer. If the process is still there, kill it.
The openni drivers were also updated a while ago to fix a lot of problems like this. On the turtlebot laptop, run sudo apt-get update && sudo apt-get dist-upgrade to grab all the new packages and see if that helps.
Probably not related to your problem, but it is not a good idea to mix ROS versions.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
