Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with Kinect using standalone OpenNI only after installing openni_launch for ROS too #61

Open
130s opened this issue Jan 6, 2018 · 1 comment

Comments

@130s
Copy link
Member

130s commented Jan 6, 2018

Issue by lynncodd
Thursday Nov 07, 2013 at 18:06 GMT
Originally opened as ros-drivers/openni_launch#12


32 bit Ubuntu 12.04 LTS

Installed OpenNI v1.5.4.0
Installed NITE v1.5.2.21
Installed Sensor Kinect v5.1.2.1

Once done, I was able to run NiViewer just fine. I was also able to run other utilities that use the standalone OpenNI.

Because I also wanted to run some ROS groovy packages, I installed ros-groovy-openni-launch. When I go back to run ./NiViewer using the standalone OpenNI, I get the following error:

Open failed: Device Protocol: Bad Parameter sent!
Press any key to continue . . .

Even if I remove ros-groovy-openni-launch, ./NiViewer still no longer works. What did installing that package do that is causing the standalone OpenNI or my Kinect Sensor to not be recognized?

@130s
Copy link
Member Author

130s commented Jan 6, 2018

Comment by piyushk
Thursday Nov 14, 2013 at 21:34 GMT


@lynncodd I have never tested the Kinect driver with a 32 bit system, so I cannot comment if the groovy driver ever worked correctly on it or if my answer below is correct.

There were problems with the earlier versions of openni-dev and nite-dev. The ROS repos now contained updated packages libopenni-dev and libopenni-sensor-primesense-dev which were pulled in when you installed ros-groovy-openni-launch. Furthermore these packages would have remove your previous openni packages. It may be possible that these packages do not work on a 32 bit system.

Try removing these packages from your system and reinstall the original OpenNI drivers that worked for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant