Revision history [back]

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.

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 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 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.