"The device stream has stopped" lockup across computers
Posted: 04 Mar 2015, 22:03
I have an Eye Tribe tracker with firmware 293 and SDK 0.9.49 x86. I have tested this on three different Windows 8.1 Pro x64 computers, including a mini-ITX Intel computer, Intel NUC, and Surface Pro 2. Each computer experiences a lockup of the eye tracker after approximately 3-5 minutes.
Symptoms:
There's no particular usage that causes the lockup. The Eye Tribe server may simply be running with TET tracker connected or I may attempt or complete calibration before the lockup occurs. A symptom of the lockup is that the red LEDs will not turn off and the Eye Tribe server will not notice if the device is subsequently disconnected. The log shows "The device stream has paused" followed by "The device stream has stopped". If I exit the Eye Tribe server (clicking the x in the console window), there is nothing more added to the log.
I believe this issue may be more prevalent than described in the Known Issues post (viewtopic.php?f=9&t=232). It also seems similar to the post on Issues with the 0.9.49 Windows SDK (viewtopic.php?f=9&t=398), although I have reproduced the issue on three computers every time without any success running TET tracker for longer than a few minutes.
Here are the specific devices I tested on. These all use integrated USB 3.0 connections on the motherboards. I have tested on all USB 3.0 ports possible with no other USB 3.0 devices connected.
- ASUS H87I-PLUS motherboard
- Intel NUC D54250WYKH (D54250WYB board)
- Surface Pro 2
Please advise on possible workarounds. Thanks!
Symptoms:
There's no particular usage that causes the lockup. The Eye Tribe server may simply be running with TET tracker connected or I may attempt or complete calibration before the lockup occurs. A symptom of the lockup is that the red LEDs will not turn off and the Eye Tribe server will not notice if the device is subsequently disconnected. The log shows "The device stream has paused" followed by "The device stream has stopped". If I exit the Eye Tribe server (clicking the x in the console window), there is nothing more added to the log.
I believe this issue may be more prevalent than described in the Known Issues post (viewtopic.php?f=9&t=232). It also seems similar to the post on Issues with the 0.9.49 Windows SDK (viewtopic.php?f=9&t=398), although I have reproduced the issue on three computers every time without any success running TET tracker for longer than a few minutes.
Here are the specific devices I tested on. These all use integrated USB 3.0 connections on the motherboards. I have tested on all USB 3.0 ports possible with no other USB 3.0 devices connected.
- ASUS H87I-PLUS motherboard
- Intel NUC D54250WYKH (D54250WYB board)
- Surface Pro 2
Please advise on possible workarounds. Thanks!