Eddie & Kinect -- kinect not reconized after running 'Eddie' from DDS Cmd

tux

Hi guys,

I just got my hands on an Eddie robot. I've followed the documentation with the setup steps and after encountering some Kinect driver problems and unblocking the parallax .ddls I have managed to start the robot dashboard. Soon after the UI was started (1-2 sec.) I got a message from Windows telling me that there was an "Unrecognized USB Device") and I've noticed that the Kinect stopped blinking.

I thought at first that this is a Windows problem and rebooted it. The behaviour is the same related to the driver part (unreconized after running 'Eddie' from the DDS cmd) and now the dashboard starts partially, only some sliders are visible but not buttons or the 2 Kinect image windows. I even tried installing the latest Kinect SDK (which also contains the drivers) but no luck. Also, in the DDS CMD prompt I see a message something about getting no response and giving a timeout.

My setup is:
Windows 7 Pro (32 bit)
MS Robotics Studio 4
Kinect SDK (1.8, also tried 1.0)
.NET 4

Any ideas are appreciated!

Thank you!

bomber

Welcome to the forums, tux! I originally had some problems with the kinect as well, initially. Do you have the kinect drivers? There are some bare-bones demo's made by microsoft that may help, I got them pre-installed with the drivers. Another issue I had was that some of the USB ports on my computer would just flat out not work with the kinect. Switching to another port helped.

tux

Hi bomber,

Thanks for the tips but it still doesn't work. After I start 'Eddie' from DDS command prompt, or by running a project from VPL or by flashing Eddie with the Propeller tool the Kinect becomes unrecongized (Windows sounds of unplugging/plugging a device and the "USB device not recognized" pop-up).

What I've tried is the following:
- Kinect SDK 1.0 -- the most unstable vpl + code does work correctly
- Kinect SDK 1.5.2 -- a bit more stable (doesn't crash every time, only 70% of the time ) ) code does work correctly --> sticking to this version for now.
- Kinect SDK 1.6 -- same behavior + vpl code doesn't work correctly even if recompiled the samples
- Kinect SDK 1.8 -- same behavior + vpl code doesn't work correctly even if recompiled the samples
- tried a different USB port -- same behaviour -- later edit: (should also check the other 1-2 ports available on the right side of my laptop).

I've verified that Kinect is working by using the samples provided in the Toolkit -- sometimes they work and sometimes they don't but at least I know the Kinect isn't broken (I guess).

Do you have any other ideas?

Thanks in advance!