Have you noticed that Kinect or AsusXtionPro under ROS appears to have a stochastic behavior? In other words, do you have problem that sometimes you are able to launch the driver of the sensor but sometimes you cannot, although you have not changed anything in your system-environment? Then the following hint may come in very handy.
Solution
Here' s a quick thing you can try and see if you have any better chance after. The following command may cause NO new problems whatsoever, so try this in your terminal:
kill $(ps aux | grep Xn | awk '{print $2}')
This command will try to kill any processes with a name that includes "Xn", which in our case aims at killing XnSensorServer and XnVSceneServer that may run already and prevent ROS to take control of the sensor.
If you want to see whether you have already these two processes running you can try this:
ps aux | grep Xn
For example, in my terminal the output looked something like this:
If NONE of these two processes appear in your output while you are trying to use the sensor through ROS, then your problem is different and the solution proposed here will not apply to your case.
But if you DO see, one, or both of these processes already running, then if you kill these two processes with the first command that i gave in the beginning you can be sure that YOU WILL NOT GET the error message:
"....enumerating image nodes failed. Reason: One or more of the following nodes could not be enumerated:
Image: PrimeSense/SensorV2/(your_sensor_verison): Failed to set USB interface!..."
through ROS.
Now try to initiate the sensor through the ROS wrapper (roslaunch openni_launch openni_launch) and see if you are more lucky.
Note: i arrived to this solution by reading this post:
