Problem with kinect

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

Giu
11 ●2 ●2 ●4

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

ngrennan
1 ●1 ●1

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

add a comment

1

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

jarvisschultz

9031 ●58 ●128 ●143 https://www.linkedin.c...

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.