[Solved] Error when run Kinect example

[Veerachart]

Hi,

I'm trying to control Crazyflie by the Kinect, so I started with the example in this Wiki page.

However, I got the following error:

Code: Select all

send_cmd: Bad magic 00 7a
freenect_fetch_reg_pad_info: send_cmd read -1 bytes (expected 8)
freenect_camera_init(): Failed to fetch registration pad info for device
Error: Invalid index [0]
Error: Can't open device. 1.) is it plugged in? 2.) Read the README
send_cmd: Bad len 0004 != 001c
freenect_fetch_reg_pad_info: send_cmd read -1 bytes (expected 8)
freenect_camera_init(): Failed to fetch registration pad info for device
Error: Invalid index [0]
Error: Can't open device. 1.) is it plugged in? 2.) Read the README
Traceback (most recent call last):
  File "./cfkinect", line 85, in <module>
    cfkinect.main()
  File "/home/veerachart/Research/Crazyflie/CFKinect/crazyflie-pc-client/lib/cfkinect.py", line 171, in main
    kinect_pilot.control(args.dry)
  File "/home/veerachart/Research/Crazyflie/CFKinect/crazyflie-pc-client/lib/cfkinect.py", line 97, in control
    (x,y,depth) = self.kinect.find_position()
  File "/home/veerachart/Research/Crazyflie/CFKinect/crazyflie-pc-client/lib/kinect/kinect.py", line 159, in find_position
    (kinect_depth,_), (rgb,_) = get_depth(), get_video()
TypeError: 'NoneType' object is not iterable

It seems like the Kinect is not working properly, so no data is obtained from get_depth() and get_video. However, I tried glview and both depth image and RGB image are shown.

I'm running on Ubuntu 12.04, with Xbox360 Kinect on USB3 port. Is this a problem with USB3?

Any suggestion for solution is appreciated.

Thanks.

[Veerachart]

Well, I got it flying after updated to Ubuntu 13.10 (which actually destroyed my dual boot and took me some time to reinstall the whole system.)

PS. Should I change this to SOLVED? I think it is better if someone can solve it without upgrading Ubuntu.

[marcus]

Hi,

Ouch, sorry to hear that ran into so much problems. I recognize the situation and I think that this xkcd describes it pretty well...

Since the device won't even open I'm worried that there's some incompatibility on a lower level that we can't control. I think that we can mark this as solved and I've created an issue for this to investigate.