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

Problem with kinect

asked 2012-05-07 22:35:14 -0500

Giu gravatar image

updated 2016-10-24 08:34:36 -0500

ngrennan gravatar image

Hello, I hope you can help me.I have a problem with kinect. I open a terminal and write "roscore" then I open a new terminal for lunch my kinect. I open a new terminal for a make and after I open a new terminal for run my ros node. The first time I always get my results, but if I want to repeat the acquisition kinect, because I want to redo the run of the node (because I made the changes), the kinect disconnects. When I try to restart it no longer connects and I have to restart the PC to make it work. I use ros electric in ubuntu 11.10. This is the message when the kinect disconnects: [camera_nodelet_manager-1] process has died [pid 2623, exit code -6].

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2013-03-12 05:00:03 -0500

updated 2013-03-12 05:01:05 -0500

With the information provided, I'm not entirely sure what the problem is. However, here are a couple of tips for debugging. First you don't need a separate roscore; using roslaunch on openni.launch will automatically start a core (this will just save you a step).

You very likely do not have to restart your entire computer if the openni.launch process does crash. Often, I have found that reloading the udev service is enough to get the Kinect restarted. So if openni.launch is failing to start the Kinect, or failing to publish any data, try unplugging the Kinect and running the command

sudo service udev reload

Then try again.

Launching the openni.launch with debugging turned on will allow you to get a backtrace of the error. This could possibly lead to the cause of your problem. Run

roslaunch openni_launch openni.launch debug:=true

a separate xterm window running gdb will pop up. In that window type run, and the node will start running. Then if the node crashes, you can type bt in the gdb window to generate a backtrace of the error.

edit flag offensive delete link more


Wow... I did not realize how old the question was. Maybe @Giu still cares?

jarvisschultz gravatar image jarvisschultz  ( 2013-03-12 05:02:09 -0500 )edit

Neither did I, I just was looking at unanswered questions.

Oier gravatar image Oier  ( 2013-03-12 05:20:38 -0500 )edit

answered 2013-03-12 02:06:53 -0500

Oier gravatar image

Could you paste the whole error log please? From what you tell, it seems like the old Kinect bug, which has been fixed in groovy.

edit flag offensive delete link more

Question Tools


Asked: 2012-05-07 22:35:14 -0500

Seen: 593 times

Last updated: Mar 12 '13