Could anyone get the camera data from the Kinect using a Raspberry Pi ?
We would like to make a wireless Kinect connecting it using Ethernet or WiFi. Otherwise, let me know if you have a working alternative.
To answer your question, yes it is possible to get Image and depth on the raspberry pi!
Here is how to.
If you want to use just video (color, not depth) there is already a driver in the kernel! You can load it like this:
modprobe videodev
modprobe gspca_main
modprobe gspca_kinect
You get a new /dev/videoX and can use it like any other webcam!
If you need depth (which is why you want a kinect), but have a kernel older than 3.17, you need another driver that can be found here: https://github.com/xxorde/librekinect. If you have 3.17 or newer, then librekinect functionality is enabled by toggling the gspca_kinect module's command-line depth_mode flag:
modprobe gspca_kinect depth_mode=1
Both work well on the current Raspbian.
If you can manage to plug your kinect camera to the raspberry Pi, install guvcview first to see if it does works.
sudo apt-get install guvcview
Then, typeguvcview in the terminal and it should open an option panel and the camera control view. If all of that does works and that you want to get the RAW data to do some image treatments, you will need to compile OpenCV (it takes 4 hour of compiling) and after that, you just will need to program whatever you want. To compile it, just search on Google, there are lots of tutorial.
Well, as far as I know there are no successful stories about getting images from Kinect on RaspberryPi.
On github there is an issue in libfreenect repository about such problem. In this comment user zarvox say that RPi haven't enough power to handle data from Kinect.
Personally I tried to connect Kinect with RPi using OpenNI2 and Sensor, but have no success. And that was not a clever decision because it's impossible to work with Microsoft Kinect on Linux using OpenNI2 due to licensing restrictions (Well, actually it is not so impossible. You can use OpenNI2-FreenectDriver + OpenNI2 on Linux to hookup Kinect. But anyway this workaround is not suitable for RaspberryPi, because OpenNI2-FreenectDriver uses libfreenect).
But anyway there are some good tutorials about how to connect ASUS Xtion Live Pro to RaspberryPi: one, two. And how to connect Kinect to more powerfull arm-based CubieBoard2: three.
If you intend to do robotics the simplest thing is to use the Kinect library on ROS Here
Oderwise you can try OpenKinect, They provide the libfreenect library that let you acess to the accelerometers the image & much more
OpenKinect on Github here
OpenKinect Wiki here
Here is a good exemple with code & all the details you need to connect to the Kinect & operate the motors using libfreenect.
You will need a powered USB hub to power the Kinect & to install libusb.
A second possiblity is to use the OpenNI library which provides a SDK to develop midleware libraries to interface to your application there is even an OpenNi lib for processing here.
yes, you can use Kinect with raspberry pi in a small robotic project.
I have done this work with the openkinect library.
my experience is you should check your raspberry pi and monitoring pi voltage, not time does to low voltage.
you should accuracy your coding to use lower processing and run your code faster.
because if your code had got a problem, your image processing would be the slower response to the objects.
https://github.com/OpenKinect/libfreenect https://github.com/OpenKinect/libfreenect/blob/master/wrappers/python/demo_cv2_threshold.py
Related
I'm trying to emulate STM32F429I discovery board using qemu & eclipse IDE. I got the blinky example running with the led turning on and off on the graphics screen but I have tried an example to run the on-board screen and it doesn't seem to be running, Is it supported? Also, many drivers fail when simulated with qemu (sdram, rcc, ...) How can I know exactly what peripherals that are fully supported?
Here's the part of documentation about the board, What is meant by "FP not emulated" anyway?
Note: Why this question is not off-topic
Some people seem to think this question is off-topic, and it would be better suited for Super User. Please give me a chance to explain why that's not the case.
The question is not about "general computing hardware" but about "embedded software". In the topic of "embedded software", there are tons of questions on StackOverflow related to OpenOCD, a popular open-source tool to connect your computer to embedded software development boards. All these questions are considered totally okay for StackOverflow. My question on this page is about PyOCD - an emerging OpenOCD alternative. So if you vote to close this question, then please also vote to close the 565 (!) other questions about OpenOCD too ;-)
I've got a NuMaker-M032SE V1.3 board from Nuvoton that I'm trying to flash/debug with PyOCD. It's my first time I'm experimenting with PyOCD and with Nuvoton chips. Unfortunately, PyOCD cannot find the device. I'll go step-by-step through the whole procedure. Please tell me what I did wrong.
1. My system
I'm running 64-bit Windows 10 on my desktop computer. I've got Python 3.8 and recently installed the latest PyOCD development version from a cloned GitHub repository (see https://github.com/mbedmicro/pyOCD).
2 Install Microcontroller board
Note: this paragraph is simply to show you the background situation, before I move on to explain the actual problem I got with PyOCD
I've got a Nuvoton NuMaker-M032SE V1.3 microcontroller board:
This board has a Nu-Link2-Me V1.0 probe on the right side. The first time I connect my board to my computer nothing really happened. So I figured out I had to install the Nuvoton ICP tool that comes with the Nu-Link USB Driver 1.6:
You can download the Nuvoton ICP tool here: https://www.nuvoton.com/hq/support/tool-and-software/development-tool-hardware/programmer/
When I first start the sofware, I see this:
And I get a request to update the firmware on the Nu-Link2-Me V1.0 probe:
I click OK and wait for the firmware update to complete. I plug out and back in the board. Windows clearly notices the device:
I can also see the device in my Control Panel > Device Manager. It's listed under Universal Serial Bus Controllers as Nuvoton Nu-Link2 USB:
3 Prepare PyOCD
PyOCD has a few built-in targets. But not the Nuvoton chip I got. So I consulted the documentation at https://github.com/mbedmicro/pyOCD/blob/master/docs/target_support.md and learn that I need to download a pack from http://www.keil.com/dd2/pack/ . That's where I download the Nuvoton ARM Cortex-M NuMicro Family Device Support pack:
Because I downloaded the pack manually, I know that I'll have to add the parameter --pack="C:/path/to/pack/Nuvoton.NuMicro_DFP.1.3.5.pack" to every PyOCD command, to ensure that PyOCD can access this pack whenever it needs to.
4. Connect PyOCD with Nuvoton board
I believe my microcontroller board is properly installed to go on to the final step: connect PyOCD to the Nuvoton microcontroller board.
First I want PyOCD to find the board. I issue the following command in a Windows console:
$ pyocd list --pack="C:/path/to/pack/Nuvoton.NuMicro_DFP.1.3.5.pack"
Unfortunately, I get the response:
No available debug probes are connected
I tried a few times, both with and without the --pack parameter. I always get the same error message.
Note:
I had expected to see something like:
# Probe Unique ID
---------------------------------------------------------------------------
0 ARM CMSIS-DAP v1 000000800a0c882800000000000000000000000097969902
That's the output I get when I issue the $ pyocd list command and I have my SWDAP probe connected to my computer. The SWDAP is the official probe from ARM (see https://os.mbed.com/components/SWDAP-LPC11U35/) that runs the DAPLink firmware (see https://github.com/ARMmbed/DAPLink).
I got a reply from Nuvoton. Apparently the NuMaker-M032SE V1.3 board is not yet supported in PyOCD at the time of writing (02 Dec 2019). At the moment, only NuMaker M252/M263 boards are supported.
Nuvoton will make efforts to support these boards in PyOCD too, in the future.
I want to use my Kinect v2 as a webcam for some tools which requires a webcam as an input device as example cheese.
However, I am able to start protonect from libfreenect2 like described at the bottom of this page: https://github.com/OpenKinect/libfreenect2/blob/master/README.md#linux
Protonect will display 4 streams, which is fine, but cheese and other tools tell me there is no device found. The same is true for different other tools I tested like VLC media player.
I read the different guide but most I found seems only to be true for Kinect v1.
According to the openkinect FAQ, the Kinect should be able to use as the webcam with a Kernel above 3.0. Mine is 4.10 while Ubuntu is 17.04 and I use an AMD GPU with newest Pro driver.
Thank you in advance for your help.
As we know,the OpenNI and openni.org have been closed. But I need to use Kinect or Xtion to make a 3D scanner. what should I use now? I find that structure.io provides OpenNI 2, but I am not sure if it is compatible with those codes or driver using OpenNI.
Just use Kinect SDKs provided by Microsoft. You can definitely access all the functionality and there are many resources out there to get a quick start. I did a virtual dressing room project using only Kinect SDKs and XNA.
I have the same problem with this post: MSDN Post. It seems nobody answered with a working solution on that thread.
The symptoms:
Kinect SDK 1.5 installed.
The Kinect device is recognized and drivers seem to be loaded correctly.The speech demo works correctly.
Skeleton Viewer shows "Could not enable Skeleton Tracking".
Shape Game starts, but does not track anything.
Kinect Explorer starts the small windows only showing that it has connected to the Kinect, the black window does not open. If I close the white window, the kinect explorer is still running I have to quit it through the task manager.
When I unplug and plug the USB after I open Kinect explorer; it says insufficient bandwith.
I tried:
Updated BIOS.
Updated motherboard software. (ASUS Maximus IV Gene-Z, Gen3)
Removed all USB's and plugged them all.
Restarted windows. (several million times)
I uninstalled and re installed. Kinect SDK 1.0. (but everything is the same)
My OS: Windows 7 64 bit Ultimate.
I have been struggling with this for 1 complete day. Any suggestions will be greatly appreciated.
EDIT: I tried my Kinect device on another computer (laptop), and it works.
If the Kinect shares a USB Controller with other devices, a problem such as yours can happen easily.
Try the following: Unplug all USB devices, then connect only the Kinect to your computer. If you have USB mouse and/or keyboard, plug those into a different set of ports (for example front usb ports if you have the Kinect plugged into the back of the computer). Then, try running the SDK's sample applications.
Should this approach fail, something might be wrong with your USB controller(s).
One more option: Try running the sample applications on a different Windows computer, preferably a laptop of some type, since you won't need to plug in any additional USB devices.
If this approach fails, your Kinect is most likely defective. In which case you can get a replacement or refund from your retailer, if the purchase didn't happen too long ago.
Best of luck to you!
I finally was able to made my kinect work. This MSDN Discussion helped me to do that.
The solution:
Uninstall all Kinect Drivers from Control Panel.
Reinstall Kinect SDK.
(IMPORTANT) Make sure to skip getting drivers from windows update during driver installation.
And yay! It works beautifuly ..
The same happened with me; I noticed a windows update related to Kinect, installed it. Kinect stopped working. Installing SDK from May 2d 2012 didn't fix the problem. Rolling back to February 2010 SDK didn't fix it either. At first I guessed that Microsoft doesn't want us to use Kinect for Xbox any more, and this is their way of telling us to buy Kinect for Windows... well, may be - but in my case Kinect Camera driver was somehow updated to Version 1.5 (May 2, 2012), while everything else was on version 1.0. Installing original driver fixed the problem.