Currently I'm having some trouble with my kinect senor.
I installed the following libraries via homebrew:
libusb +universal (1.0.9)
sensor-kinect (0.91-5.1.0.25)
openni (stable-1.5.2.23)
NITE (1.5.2.21)
When I try to run the example Sample-NiSimpleRead located at sample/Bin/x64-Release from the openni framework the following error occurs after about 20 seconds:
UpdateData failed: A timeout has occurred when waiting for new data!
My kinect is model 1473.
I tried the steps in this post Kinect hangs up suddenly after working pretty well a few seconds. How can I fix it?
But my libfreenect library says that it found one device but couldn't open it.
Does anybody know how to fix this?
Since you mentioned you're not using an USB extension, this shouldn't be the issue.
I had issues with 10m ones. 5 and 7m active USB extensions worked fine though.
I was looking at the order of install, which is important: should be OpenNI/Nite then Sensor.
Also, for a Kinect with OpenNI you should use Avin's modified SensorKinect driver.
In conclusion try this:
Install OpenNI 1.5.4.0
Install Nite 1.5.2.21
Install Avin's SensorKinect
After you insall the above in that order, connect your sensor
and try to run of the samples(like NiSimpleViewer).
This should work(famous last words). If not, try to access another computer for a few minutes to test the same. This way you should have the sensor running at least on one computer and work out if the issue could be with the sensor or with the computer( and it's usb port/internal usb bus).
You shouldn't need libfreenect/libusb, but on osx you can use both at the same if you want, as long as you don't access the same sensor resources (so you can get accelerometer values from libfreenect and scene segmentation from openni)
Related
I wonder why every once in a while, Intel RealSense 3D camera fails to start? I have re-installed the drivers and SDK as well as the DCM but still it is whacky and very unpredictable. Any idea what the source of the problem could be? It should be able to run the examples in the SDK in a normal working situation.
Well, previously that it couldn't init problem was that only two of the its drivers could be recognized (not the virtual driver) like the following but now all of its driver are recognized and still it can't init.
so I am receiving an init failed message when running the SDK examples.
Any pointer for fixing is really appreciated.
If you are also showing an integrated webcam (other than the 3 RealSense listings), try disabling that so the RS camera can be seen as the primary.
Actually you can select the device you want to run the sample on in the menu "Device". If you installed the RealSense correctly and if the latest DCM is running (the current version is 1.4 if I remember), you should be able to select the RealSense device there and then run the sample.
Sometimes the DCM Service fails to start (e.g. if you force-restarted your machine recently). Then you just need to make the service restart and it should work.
Hope this helps.
I’m also facing the same problem (on windows 10), and found a way that solved it for me: search “Scanners and Cameras” in Control Panel, choose “Add Device”, under “Manufacturer” choose “Intel” and under “Model” choose “Intel(R) RealSense(TM) Camera SR300 Virtual Driver” or the version you use, and continue to install.
Have you installed the right drivers? There are two versions of the real sense cameras. The Windows 10 works with Intel Real Sense R3 which has completely different architecture than its predecessor.
I am having trouble loading a game app on genymotion. The game is Star Wars Force Collection. I can load the game, get the splash screens, then it crashes.
I have done some research before I posted here. The possible problems found in the genymotion logcat file:
There was a line noting Google services was out of date, "Google Play services out of date. Requires 4030500 but found 3225136"
Fatal signal 11 (SIGSEGV) at 0x00000364 (code=1), thread 1796 (RefQueueWorker#)
W/NetworkManagementSocketTagger( 280): setKernelCountSet(10040, 1) failed with errno -1
Some have pointed out ARM Translator problem and OpenGL.
Then again I'm really not sure the problem, and I want to post the logcat file here but I don't know how to attach it.
For problem 1, I have seen other thread here that may have fixed it with code, I'm not savvy enough for that and my Google is not updating itself.
That's about it. A few details about genymotion and the VM. I am running the latest version of genymotion and virtualbox. I am using the downloaded Custom image 4.3 as provided by Genymotion. I flashed the ARM Translation v1.1. I flashed the Gapps onto it, (I tried a higher version of Gapps to try and solve the problem, but that just made it crash) and then Star Wars Force Collection, most up to date version.
Also, worth noting that the app was running fine for v2.++, until an update to v3.++ made the game crash. I updated my graphics drivers to try and mend any graphics issues.
So there it is, any suggestions will be appreciated.
I am using Kinect for Windows (not for XBOX) on Apple iMac 3GHz 4GB 10.8.3. The Kinect is connected with USB cable to iMac and with power supply.
Software: I have installed XCode, XQuartz, MaxPorts, CMake, then libtool, libusb, OpenNI SDK v1.5.4.0, SensorKinect, and NiTE v1.5.2.21.
I am running Processing 2.0.8 with SimpleOpenNI 0.27 library.
Any example from SimpleOpenNI runs, but after approximatly 20sec Kinect stops working and freezes.
(I need to say that the green led is blinking constantly but Kinect is still working, since at least for short period time I can get e.g. the depth image etc.)
Any ideas why is not working constantly? Maybe I need Kinect for Xbox in the end? Is there any power supply issues with Apple computer? (I have tested the same Kinect device on PC and it worked fine)
This is a bit late, but for others finding this problem that I also found, try installing OpenKinect within Processing and running one of the sample sketches (like Average Point Tracking) for a moment, closing, then trying your Simple OpenNI sketch. I'm also using .27 (because I couldn't get later versions to work) and this fixes the problem, but you have to do it every time you plug the camera back in or restart the OS. Hope this helps someone else.
I am trying to run some of the examples with running Kinect and Processing together
http://www.shiffman.net/p5/kinect/
I have installed everything in the directions. However, when I run the processing code, it says "Kinect not found". I have done nothing except for:
1. install processing
2. install relevant libraries
3. connect kinect to computer
I have a feeling I am missing something obvious here. I am just confused because this particular library only works on Macs, but the Kinect generally works on Windows. Any guidance towards making my Mac recognize there is a kinect connected to it would be great. Thanks!
You can use a Kinect on OSX, Windows or Linux depending on the drivers/SDK (e.g. Kinect for Windows will only run on Windows 7 and up, but OpenKinect/libreenect or OpenNI will run on the above mentioned).
I'm not sure if you need to install the libusb-devel driver or not, but you should give that a go using MacPorts for example:
sudo port install git-core
sudo port install libtool
sudo port install libusb-devel
Also the Processing OpenKinect wrapper is a bit limited. You can't get accelerometer data for example. Other than the depth,RGB,IR streams with OpenNI also supplies, motor control is the only extra feature. On the other hand OpenNI also comes with hand tracking, gestures, skeleton and scene detection, etc. I recommend giving SimpleOpenNI a go.
I've faced a problem getting my libusb-w32 based program to detect devices.
The program has to detect digital cameras, and I need to automatically install driver filter for any new camera to be detected without any manual work.
I've used install-filter i --class={6BDD1FC6-810F-11D0-BEC7-08002BE2092F} , i. e. installing filter for MTP devices, and it seemed to work. But today I tried it on a clean machine and found out it actually only seemed that way. Tried install-filter with different parameters - no luck.
The only way I was able to detect devices at all was to use the inf-wizard.exe. It installed the driver, enabling my program to detect devices, but also disrupting the original Windows functionality for digital cameras. Then, I've uninstalled the libusb driver, installed the original windows driver back, executed install-filter i --class={6BDD1FC6-810F-11D0-BEC7-08002BE2092F} - and the program is still able to detect devices.
The question is: how to automate the process so that any new camera is detected without any work required from a user?
Update:
I'll shorten the question. It seems that when I install a driver with inf-wizard.exe, it does something besides installing the driver itself. I need to know what, exactly.
Thanks in advance.
In case someone has similar problem - the answer is here:
https://sourceforge.net/mailarchive/forum.php?thread_name=749401313049992%40web78.yandex.ru&forum_name=libusb-win32-devel