Eye Tracker keeps Disconnecting

Forum to report issues and bugs on Windows 7, 8, and 10.

Eye Tracker keeps Disconnecting

Postby Samleo » 01 Jun 2014, 09:35

The EyeTribe eye tracker continuously disconnects for some strange reason.

I tried both the 0.9.27 and 0.9.35 SDKs where I have never faced such a problem before (In fact, it was just working yesterday!), but to no avail.

Still, the eye tracker seems to momentarily disconnect and the eye tribe server sometimes crashes for no apparent reason. Is it because the eye tracker is overheating?

How to fix this problem (I am trying the latest SDK, but I doubt the SDKs are the cause of the problem)?
Samleo
 
Posts: 7
Joined: 01 Mar 2014, 11:30

Re: Eye Tracker keeps Disconnecting

Postby Martin » 03 Jun 2014, 14:06

Do you mean that the device disappears and then reappears on the system level, or as reported by the server output log? Please post the output from "C:\Users\USERNAME\AppData\Local\EyeTribe\Logs"

In general, it gets warm but never to the point where it is too hot to handle (limit is somewhere around 50-60c). When I've only seen it overheating when pushing it, for example, placing it on top of a busy Macbook Pro just above the vents. The air coming out of the laptop fans blowing directly onto the device makes it really hot, so not recommended.

I've been running the many devices on many computers now and the primary source of grief is USB3.0 controllers, drivers and the lack of native support for it in Windows 7. In many cases Windows will automatically install a generic USB driver which works so-so. Most chipsets will only work well with the vendor driver. On two computers I need to re-plug the device every couple of hours. These are a 7 year old HP Xeon workstation, the other is a 4 year old Core i7 920, both have a cheap USB3.0 controller PCI add-on cards.

I need to know more about your system configuration to properly diagnose. The weird thing here is that is was working ok then not. What changed? Either way the server should not be crashing. We can probably fix that with the help of the server output logs.
Martin
 
Posts: 567
Joined: 29 Oct 2013, 15:20


Return to Issues and troubleshooting - Windows



cron