Beta-testing new firmware tool

[Martin]

I have started a limited beta-testing group for our new firmware flasher tool. The new firmware that addresses the stream-stopped issue found on some systems (particularly old or non-Intel USB controllers).

There might be a couple of bugs in the beta version so this thread is dedicated to feedback on the new software.

If you can handle windows configuration and want to participate in the beta test, please send me a PM.

Once we have a stable tool it will go public.

[Joe G]

Unfortunately, the firmware flashing has failed on the first try. It seems to have corrupted the bootloader and the device cannot be recognized now.
- On first load, it saw the firmware 293 and device ID
- When I initiated flashing, a couple of error messages came up, including one about the bootloader
- Now the device shows up in Device Manager as WestBridge, but when I try to update the driver to cyusb3.inf, it cannot install it. The following error is shown: "Cypress USB BootLoader The system cannot find the file specified."

[Martin]

Could be Windows 8.1 specific as reported by Rafael

We proceeded to upgrade the WestBridge driver using Cyusb3.inf (the default option was "Cypress USB BootLoader"). Windows says it "located the device driver, but found an error when trying to install it".

Then we tried to do the same on Windows 7 Pro 64 bits and it found the Cypress driver through Windows Update and the firmware was upgraded successfully.

We have another EyeTribe (both with the same problem we described on the forum), and we upgraded both, and they are working fine now.

- No word on Linux tool yet.

[Martin]

If Cyusb3.inf wouldn't install here's an archive with xp, vista, 7 & 8 versions.

[Joe G]

Okay, got it running with firmware 203. Testing it out now to check stability.

If Cyusb3.inf wouldn't install here's an archive with xp, vista, 7 & 8 versions.

Thanks! I switched to a Windows 7 x86 machine and updated the driver using what you provided.

**Finished testing. Unfortunately, I had the same problem on the Intel NUC as with firmware 293. I timed it the past couple of times the lockup issue occurred and it takes up to 2 minutes to happen. Here's the log output using firmware 203:

Code: Select all

2015-03-04 17:31:30.324|510465103|I|Creating new log file
2015-03-04 17:31:30.325|510465103|I|Initializing environment
2015-03-04 17:31:30.325|510465103|I|Detecting primary screen
2015-03-04 17:31:30.328|510465103|I|Register control handler
2015-03-04 17:31:30.328|510465103|I|Initializing config system
2015-03-04 17:31:30.328|510465103|I|TCP port: 6555
2015-03-04 17:31:30.328|510465103|I|Connections: local only
2015-03-04 17:31:30.328|510465103|I|Framerate: 30
2015-03-04 17:31:30.339|510465103|I|Initializing the Eye Tribe Server (v0.9.49)
2015-03-04 17:31:30.342|510465103|I|Initializing network
2015-03-04 17:31:30.344|510465103|I|Initializing dispatcher
2015-03-04 17:31:30.344|510465103|I|Initializing Network
2015-03-04 17:31:30.344|510465103|I|Setting network connection port
2015-03-04 17:31:30.344|510465103|I|Setting max network connections
2015-03-04 17:31:30.344|510465103|I|Setting connection timeout
2015-03-04 17:31:30.344|510465103|I|Starting Network
2015-03-04 17:31:30.344|510465103|I|Checking for running instances
2015-03-04 17:31:30.345|510465103|I|Creating Tracker Manager
2015-03-04 17:31:30.345|510465103|I|Creating Camera Manager
2015-03-04 17:31:30.345|510465103|I|Initializing COM library
2015-03-04 17:31:30.346|510465103|I|Initialized COM library
2015-03-04 17:31:30.346|510465103|I|Starting Device Monitor
2015-03-04 17:31:30.355|1210739288|I|Video capturing device Found: Intel(R) RealSense(TM) 3D Camera Virtual Driver
2015-03-04 17:31:30.355|1210739288|I|Video capturing device Found: TheEyeTribe
2015-03-04 17:31:30.361|1210739288|I|Registering the device
2015-03-04 17:31:30.361|1210739288|I|Device registered
2015-03-04 17:31:30.361|1210739288|I|Validating camera device
2015-03-04 17:31:30.361|1210739288|I|Initializing tracker device
2015-03-04 17:31:30.361|1210739288|I|Starting Direct Show device
2015-03-04 17:31:30.387|1210739288|I|Building Direct Show render graph
2015-03-04 17:31:30.421|1210739288|I|Setting up device properties
2015-03-04 17:31:30.427|1210739288|I|Setting chosen video format
2015-03-04 17:31:30.430|1210739288|I|Validate camera firmware
2015-03-04 17:31:30.431|1210739288|I|Eye Tribe Tracker firmware revision is 203
2015-03-04 17:31:30.434|1210739288|I|Validate USB3 host
2015-03-04 17:31:30.434|1210739288|I|Validate camera device stream
2015-03-04 17:31:32.532|1210739288|I|The Eye Tribe Tracker stands ready
2015-03-04 17:31:32.532|1210739288|I|The tracker device has been connected
2015-03-04 17:31:32.533|510465103|I|Creating Detection Manager
2015-03-04 17:31:32.546|510465103|I|Creating Calibration Manager
2015-03-04 17:31:32.546|510465103|I|Validating number of camera devices
2015-03-04 17:31:32.546|510465103|I|Validating config chosen device
2015-03-04 17:31:37.766|660635948|I|New connection detected [176093691904]
2015-03-04 17:31:38.539|1210739288|I|The device stream has started
2015-03-04 17:31:38.539|660635948|I|Tracker started
2015-03-04 17:31:38.540|660635948|I|Creating new connection [176093691904]
2015-03-04 17:33:20.492|1210739288|W|The device stream has paused
2015-03-04 17:33:21.491|1210739288|E|The device stream has stopped


**Update: Also have the same problem on the Surface Pro 2 with firmware 203. The problem only took about 30 seconds to manifest. Example log:

Code: Select all

2015-03-04 17:37:12.311|2086069414|I|Creating new log file
2015-03-04 17:37:12.311|2086069414|I|Initializing environment
2015-03-04 17:37:12.311|2086069414|I|Detecting primary screen
2015-03-04 17:37:12.311|2086069414|I|Register control handler
2015-03-04 17:37:12.311|2086069414|I|Initializing config system
2015-03-04 17:37:12.311|2086069414|I|TCP port: 6555
2015-03-04 17:37:12.311|2086069414|I|Connections: local only
2015-03-04 17:37:12.311|2086069414|I|Framerate: 30
2015-03-04 17:37:12.326|2086069414|I|Initializing the Eye Tribe Server (v0.9.49)
2015-03-04 17:37:12.326|2086069414|I|Initializing network
2015-03-04 17:37:12.326|2086069414|I|Initializing dispatcher
2015-03-04 17:37:12.326|2086069414|I|Initializing Network
2015-03-04 17:37:12.326|2086069414|I|Setting network connection port
2015-03-04 17:37:12.326|2086069414|I|Setting max network connections
2015-03-04 17:37:12.326|2086069414|I|Setting connection timeout
2015-03-04 17:37:12.326|2086069414|I|Starting Network
2015-03-04 17:37:12.326|2086069414|I|Checking for running instances
2015-03-04 17:37:12.326|2086069414|I|Creating Tracker Manager
2015-03-04 17:37:12.326|2086069414|I|Creating Camera Manager
2015-03-04 17:37:12.326|2086069414|I|Initializing COM library
2015-03-04 17:37:12.326|2086069414|I|Initialized COM library
2015-03-04 17:37:12.326|2086069414|I|Starting Device Monitor
2015-03-04 17:37:12.357|2922841770|I|Video capturing device Found: Microsoft LifeCam Front
2015-03-04 17:37:12.357|2922841770|I|Video capturing device Found: Microsoft LifeCam Rear
2015-03-04 17:37:12.357|2922841770|I|Video capturing device Found: PS3Eye Camera
2015-03-04 17:37:13.342|2086069414|I|Creating Detection Manager
2015-03-04 17:37:13.342|2086069414|I|Creating Calibration Manager
2015-03-04 17:37:13.342|2086069414|I|Validating number of camera devices
2015-03-04 17:37:13.342|2086069414|W|Waiting for the tracker device to be connected
2015-03-04 17:37:17.343|2922841770|I|Video capturing device Found: TheEyeTribe
2015-03-04 17:37:17.405|2922841770|I|Registering the device
2015-03-04 17:37:17.405|2922841770|I|Device registered
2015-03-04 17:37:17.405|2922841770|I|Validating camera device
2015-03-04 17:37:17.405|2922841770|I|Initializing tracker device
2015-03-04 17:37:17.405|2922841770|I|Starting Direct Show device
2015-03-04 17:37:17.452|2922841770|I|Building Direct Show render graph
2015-03-04 17:37:17.535|2922841770|I|Setting up device properties
2015-03-04 17:37:17.535|2922841770|I|Setting chosen video format
2015-03-04 17:37:17.535|2922841770|I|Validate camera firmware
2015-03-04 17:37:17.535|2922841770|I|Eye Tribe Tracker firmware revision is 203
2015-03-04 17:37:17.550|2922841770|I|Validate USB3 host
2015-03-04 17:37:17.550|2922841770|I|Validate camera device stream
2015-03-04 17:37:19.651|2922841770|I|The Eye Tribe Tracker stands ready
2015-03-04 17:37:19.651|2922841770|I|The tracker device has been connected
2015-03-04 17:37:25.948|3840228335|I|New connection detected [176093691904]
2015-03-04 17:37:26.675|2922841770|I|The device stream has started
2015-03-04 17:37:26.675|3840228335|I|Tracker started
2015-03-04 17:37:26.675|3840228335|I|Creating new connection [176093691904]
2015-03-04 17:37:52.671|2922841770|W|The device stream has paused
2015-03-04 17:37:53.670|2922841770|E|The device stream has stopped


Are these problems particular to Windows 8.1 Pro 64-bit?

[Joe G]

I have tested my Eye Tribe tracker (with firmware 203) on Windows 7 Pro 64-bit for 10 minutes and there were no problems. Unfortunately, this is not a workaround for me, as I must use Windows 8.1 Pro 64-bit in my research. See example log below:

Code: Select all

2015-03-05 08:26:50.475|1488074855|I|Creating new log file
2015-03-05 08:26:50.475|1488074855|I|Initializing environment
2015-03-05 08:26:50.475|1488074855|I|Detecting primary screen
2015-03-05 08:26:50.487|1488074855|I|Register control handler
2015-03-05 08:26:50.487|1488074855|I|Initializing config system
2015-03-05 08:26:50.487|1488074855|I|TCP port: 6555
2015-03-05 08:26:50.487|1488074855|I|Connections: local only
2015-03-05 08:26:50.487|1488074855|I|Framerate: 30
2015-03-05 08:26:50.488|1488074855|I|Initializing the Eye Tribe Server (v0.9.49)
2015-03-05 08:26:50.488|1488074855|I|Initializing network
2015-03-05 08:26:50.488|1488074855|I|Initializing dispatcher
2015-03-05 08:26:50.488|1488074855|I|Initializing Network
2015-03-05 08:26:50.488|1488074855|I|Setting network connection port
2015-03-05 08:26:50.488|1488074855|I|Setting max network connections
2015-03-05 08:26:50.488|1488074855|I|Setting connection timeout
2015-03-05 08:26:50.488|1488074855|I|Starting Network
2015-03-05 08:26:50.488|1488074855|I|Checking for running instances
2015-03-05 08:26:50.498|1488074855|I|Creating Tracker Manager
2015-03-05 08:26:50.498|1488074855|I|Creating Camera Manager
2015-03-05 08:26:50.498|1488074855|I|Initializing COM library
2015-03-05 08:26:50.498|1488074855|I|Initialized COM library
2015-03-05 08:26:50.498|1488074855|I|Starting Device Monitor
2015-03-05 08:26:50.508|4262128536|I|Video capturing device Found: ManyCam Virtual Webcam
2015-03-05 08:26:50.508|4262128536|I|Video capturing device Found: ManyCam Video Source
2015-03-05 08:26:50.508|4262128536|I|Video capturing device Found: PS3Eye Camera
2015-03-05 08:26:51.498|1488074855|I|Creating Detection Manager
2015-03-05 08:26:51.498|1488074855|I|Creating Calibration Manager
2015-03-05 08:26:51.498|1488074855|I|Validating number of camera devices
2015-03-05 08:26:51.498|1488074855|W|Waiting for the tracker device to be connected
2015-03-05 08:26:54.781|4098513586|I|New connection detected [176093691904]
2015-03-05 08:26:54.781|4098513586|E|Could not start tracker
2015-03-05 08:26:54.781|4098513586|I|Creating new connection [176093691904]
2015-03-05 08:31:21.452|4262128536|I|Video capturing device Found: TheEyeTribe
2015-03-05 08:31:21.458|4262128536|I|Registering the device
2015-03-05 08:31:21.458|4262128536|I|Device registered
2015-03-05 08:31:21.458|4262128536|I|Validating camera device
2015-03-05 08:31:21.458|4262128536|I|Initializing tracker device
2015-03-05 08:31:21.458|4262128536|I|Starting Direct Show device
2015-03-05 08:31:21.465|4262128536|I|Building Direct Show render graph
2015-03-05 08:31:21.592|4262128536|I|Setting up device properties
2015-03-05 08:31:21.613|4262128536|I|Setting chosen video format
2015-03-05 08:31:21.623|4262128536|I|Validate camera firmware
2015-03-05 08:31:21.625|4262128536|I|Eye Tribe Tracker firmware revision is 203
2015-03-05 08:31:21.629|4262128536|I|Validate USB3 host
2015-03-05 08:31:21.629|4262128536|I|Validate camera device stream
2015-03-05 08:31:23.758|4262128536|I|The Eye Tribe Tracker stands ready
2015-03-05 08:31:23.768|4262128536|I|The device stream has started
2015-03-05 08:31:23.768|4262128536|I|Tracker started
2015-03-05 08:31:23.768|4262128536|I|The tracker device has been connected
2015-03-05 08:41:11.805|4098513586|I|Connection removed [176093691904]
2015-03-05 08:41:12.370|4262128536|I|The device stream has stopped
2015-03-05 08:41:12.370|4098513586|I|Tracker stopped
2015-03-05 08:41:14.915|1488074855|I|Shutting down Tracker Manager
2015-03-05 08:41:14.915|1488074855|I|Shutting down Camera Manager
2015-03-05 08:41:14.915|1488074855|I|Stopping Device Monitor
2015-03-05 08:41:15.241|4262128536|I|Stopping Direct Show device
2015-03-05 08:41:15.349|1488074855|I|Uninitializing COM library
2015-03-05 08:41:15.349|1488074855|I|Uninitialized COM library
2015-03-05 08:41:15.349|1488074855|I|Shutting down Detection Manager
2015-03-05 08:41:15.369|1488074855|I|Shutting down Calibration Manager
2015-03-05 08:41:15.369|1488074855|I|Deinitializing dispatcher
2015-03-05 08:41:15.369|1488074855|I|Deinitializing Network Manager
2015-03-05 08:41:15.369|1488074855|I|Network Manager Deinitialized


[Martin]

Hi Joe,

Good to hear that we're making some progress. I'm sure we can figure out the Windows 8.1 as well (I'm running two of my workstations on it). The bulk of issues we've seen has been with USB controller drivers on Windows 7 (no native UBS3.0).

The device will be stopped when the last client disconnects. This is by design so the server doesn't waste resources if no one is listening to the data (e.g TET UI or other 3rd party app).

Considering your log:

Code: Select all

2015-03-05 08:31:23.768|4262128536|I|The tracker device has been connected
2015-03-05 08:41:11.805|4098513586|I|Connection removed [176093691904]
2015-03-05 08:41:12.370|4262128536|I|The device stream has stopped
2015-03-05 08:41:12.370|4098513586|I|Tracker stopped
2015-03-05 08:41:14.915|1488074855|I|Shutting down Tracker Manager


The I before the message means Information, e.g. the event occurred as part of normal operation. Other types are Error and Warnings. So by the looks of it the first (and only?) client disconnects and the server suspends operation.

If we look at the previous logs:

Code: Select all

2015-03-04 17:31:38.540|660635948|I|Creating new connection [176093691904]
2015-03-04 17:33:20.492|1210739288|W|The device stream has paused
2015-03-04 17:33:21.491|1210739288|E|The device stream has stopped


We see one warning that the stream unintentionally paused followed by an error stating that the device has stopped (cannot be reached).

Could you please try running it again leaving the TETUI and/or other clients connected for an extended period.

[Joe G]

Hi Martin,

Yes, I actually manually closed out the Eye Tribe tracker UI after about 10 minutes because I was satisfied that it worked properly on Windows 7 Pro 64-bit.

What would you like me to test on Windows 8.1 Pro 64-bit? So far, it has the "device stream has paused/stopped" error message and lockup when I have the Eye Tribe tracker connected for about 30 seconds to a few minutes (this happens on each of the three Win 8.1 Pro x64 machines). I'll have some time to test again tonight.

Thanks!

[Martin]

Aha, I thought the log you posted before was from the Win 8 64-bit machines. How many do you have?

When it happens, does it ever come back or do you have to reinsert the plug for it to work again?

Tempting to call it a 8.1 64-bit issue.. but I run it on that all day.

I would like to double check that this isn't a software issue, check your inbox for link.

[Joe G]

Thanks, Martin! I'll try it out using the link. I'll reply back within a few hours.

Re: the symptoms, when it locks up, the Eye Tribe Server does not recognize when I unplug or re-plug the device. The output log is "frozen" and no more messages will appear. The device itself becomes stuck with the array of red LEDs lit and they do not turn off if I close whatever application I was using.