Eyetracker Disconnection Error while LED's are still on

[tq32804]

The eyetracker worked on the first time but since then the server app keeps reporting an error "The Eye Tribe Tracker has been disconnected!" while the two side LED clusters are still illuminated. When this happens, I notice the USB 3.0 Hub controller in Windows 7 Device Manager disappears and will come back if I unplug the eyetracker USB 3.0 cable. I tried two different kinds of USB 3.0 Express Card adapters and encounter the same error. I am running this on a HP Elitebook 8440W i5 2.67GHz 8GB RAM. Any ideas?

Thanks,
Tan

[Murray]

I got the same type of crash. (Device disconnected and LEDs stay on.) It happened when I attempted a recalibration. I captured the following:

---------------------------
Calibration Failed
---------------------------
Failed to calibrate. Please try again. System.NullReferenceException: Object reference not set to an instance of an object.
at TETControls.Calibration.CalibrationRunner.<DoCalibrate>b__3(Object param0, EventArgs param1)
at System.Windows.Threading.DispatcherTimer.FireTick(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)
at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.MessageBox(HandleRef hWnd, String text, String caption, Int32 type)
at System.Windows.MessageBox.ShowCore(IntPtr owner, String messageBoxText, String caption, MessageBoxButton button, MessageBoxImage icon, MessageBoxResult defaultResult, MessageBoxOptions options)
at System.Windows.MessageBox.Show(String messageBoxText)
at TETControls.Calibration.CalibrationRunner.DoCalibrate(Boolean& userAbort)
at TETControls.Calibration.CalibrationRunner.Start()
---------------------------
OK

[Martin]

Thanks Murray.
We'll have this sorted out a.s.a.p, I've opened a bug-ticket and will get back to you when it's taken care of.

[tq32804]

Some more observations on this problem: I was able to get past the calibration steps. As soon as the process complete it reports that device not connected. Then the Eyetribe disapprears from the image devices under device manager and the USB3.0 controller disappears as well. So something must be triggering the eye cameras in the Eyetracker bar and USB 3.0 controller to shut off. Is it because the tracker bar drawing more power than the USB3.0 port can supply? What is the current draw from the eyetracker?

Tan

[Martin]

Tan,

Could it be that the computer goes into power-saving mode and shuts down the USB ports? If so, try disabling it.

Power consumption is limited to stay below the USB3.0 ratings which is 900mA.

[tq32804]

Hi Martin,
It was not caused by the Power Save Mode. My computer does not go in Power Save mode until in 15 minutes. The problem usually occurs after the first successful calibration cycle. Is there a debug log/setting that can be turned on to help troubleshoot this problem?

Tan

[tq32804]

Update on this problem - I have tried two new cables and had the same results. LED's are on but the Eyetribe UI reports the device not connected. So the problem appears to be with the eyetracker bar. Please let me know how I should proceed with this or need to test with more cables.

Tan

[Martin]

Hi Tan,

I think this could be caused by the drivers for USB 3.0 controller. We had a similar error with a Lenovo laptop and it was resolved by updating the drivers.

Could you please:
- Check that you have the latest version for the USB controller drivers.
- Update to the latest eye tracking software and see if that changes anything.
- Report the brand and model of the USB 3.0 Express Cards you are using so we could buy them and test.

Thanks.

[Martin]

A new version is out that has some changes related to device connectivity. Could you please install it and check if it resolves the issue for you.

Thanks