Kinect Sensor stops sending frames RRS feed

  • Question

  • We have been using Kinect One sensors without issues since the dev versions first came out, so a long time now. However recently we have been experiencing random freezing issues. This is happening on one of our dev computers and, of more concern, certain computers that we have deployed in the field. The cameras just seem to stop sending frames. This is occurring both in our software but also just running the Kinect Configuration Verifier, so we do not think it is something we are doing in our software.

    - A camera that has been attached to one of our dev machines for months suddenly will not run for more than a few seconds without stopping. Plugging a different camera into this machine works fine, plugging the same problem camera into another dev machine configured the same works with no problems. This is repeatable and again, just started happening after months of no issues.

    - Our computers in the field are running Windows 10 Embedded images that are identical. However, on certain computers, seemingly at random intervals the cameras will stop sending frames. Unlike the dev machine, this seems to be a more random problem, sometimes happening within a few seconds of starting the camera even after restarts, and sometimes only after hours of running the camera will there be a problem. But we have other identical machines that are running 24/7 and have never had this problem.

    Our software requires the camera to be available 24/7 in a mission-critical monitoring application. We have exhausted our ideas on comparing drivers, cables, USB connections, cameras, and software and can determine no apparent reason for these freezing problems to start occurring.

    Any ideas or suggestions how we can troubleshoot this seemingly random and intermittent problem? 

    Tuesday, June 28, 2016 8:04 PM

All replies

  • Have you noticed any USB reconnection notifications in Win10 when it stops sending frames?

    I've encountered similar situations,where the usb connection fails and gets reset, but unless you've tried to handle this situation specifically, it will not work correctly from that point on and the application will need to restart, because it enters into a kind of deadlock, where you try to get frames from the sensor using the previous instance of the connection(API connection) and while you will get some frames, it will eventually fail again and reset the usb connection. And every time the usb connection fails, you will get a notification from Windows about it. And that's a sign you need to release the sensor somehow.

    Are you cooling the sensors while they work around the clock? Because they overheat easily and it might be that overheating and working around the clock are taking their toll on the sensors.

    Are the machines ,on site, laptops? Is it possible that the power management profile is not High Performance but something else that after a while shuts down the usb links for power efficiency? Check the following link at the end. There's a post about sensor failing frequently.

    Wednesday, June 29, 2016 7:26 AM
  • We seem to have the same issues and we use Windows 10 Home with Shuttle DS81 systems. The camera light turns off while this is happening.
    Wednesday, June 29, 2016 10:49 AM
  • We have noticed this behavior more and more as well. On regular systems (not laptops) with Kinect camera's that are used only a few hours per day.
    Wednesday, June 29, 2016 10:51 AM
  • Doesn't have to be a laptop to have wrong power management profile values. It's just that laptops usually have some defaults towards power efficiency therefore it's a common problem.
    Wednesday, June 29, 2016 10:56 AM
  • @BrianG500, you don't mention anything about trying a separate PCI-E USB card and leaving Kinect the only device using your USB ports. There are known issues when using motherboard's built in USB ports as conflicts arise in resource usage with other devices.

    You may also try a USB 3.1 card which may not only give it more power but also allow use of longer cables. At least so claimed by Newnex:
    Saturday, July 9, 2016 12:07 PM
  • You're right! It's a known issue,also documented by MS, that other usb devices on the same USB controller can degrade Kinect's functionality.

    I doubt though there's need to go that far and add an external USB card, or especially the Newnex stuff(which are suspiciously not showing prices....wondering how high.But since they talk about fiber optics I guess its more than possible as a solution, considering data transfer rates and bandwidths in fibers).

    As long as Kinect can be alone in the controller of the port it's using, its enough. Usually there are two controllers at least. In desktops the ports in the back of the machine are in a different controller than the ports located in the front of the case.

    Saturday, July 9, 2016 2:32 PM