USB devices failed (or disconnected?)
Posted: Tue Jun 11, 2013 8:51 pm
From time to time, the computer running TrackingTools makes the sound indicating that a USB device has disconnected ("BA dup"), sometimes more than once, and then shortly after that the reconnection sound ("ba DUP"). A few seconds later, some number of cameras in the 3D perspective view move to the X-axis.
Sometimes after this happens I get an error from Windows, "USB device has failed" or similar.
It's not always the same cameras that "fail", and the first time it fails it's almost always 6 cameras -- but NOT all from the same hub.
This results, obviously, in greatly reduced tracking success and accuracy within my volume. (I run experiments with mobile robots.)
I have figured out that I can simply reload the Calibration file to get it working properly again (rather than restarting), but if this occurs during an experiment I then have bad (or missing) tracking data until I reload the cal.
My setup:
Dell Precision T5500
Dual Intel Xeon quad-core E5504 2.00GHz
24GB RAM
Win7 Pro 64 SP1
TrackingTools 2.3.3 for the last two years or so.
Just installed TrackingTools 2.3.4 Beta1 (my license expired 1 day before 2.4.0 Beta1 64) today, problem still occurs but possibly less frequently (can say that conclusively though)
22 x V100:R2 cameras
4 x OptiHubs
one hub w/ 4 cameras + hw key has powered 5m USB extension
other 3 hubs have 6 cameras
tracking volume is ~4m x 3.3m x 2.5m (W L H)
I will likely be re-upping my license and eventually migrating to Motive, but I am constrained to versions pre-2.4.0 for the time being (until I can get funding approved) and I need to get this round of experiments done.
Any help please? Thanks!!
Sometimes after this happens I get an error from Windows, "USB device has failed" or similar.
It's not always the same cameras that "fail", and the first time it fails it's almost always 6 cameras -- but NOT all from the same hub.
This results, obviously, in greatly reduced tracking success and accuracy within my volume. (I run experiments with mobile robots.)
I have figured out that I can simply reload the Calibration file to get it working properly again (rather than restarting), but if this occurs during an experiment I then have bad (or missing) tracking data until I reload the cal.
My setup:
Dell Precision T5500
Dual Intel Xeon quad-core E5504 2.00GHz
24GB RAM
Win7 Pro 64 SP1
TrackingTools 2.3.3 for the last two years or so.
Just installed TrackingTools 2.3.4 Beta1 (my license expired 1 day before 2.4.0 Beta1 64) today, problem still occurs but possibly less frequently (can say that conclusively though)
22 x V100:R2 cameras
4 x OptiHubs
one hub w/ 4 cameras + hw key has powered 5m USB extension
other 3 hubs have 6 cameras
tracking volume is ~4m x 3.3m x 2.5m (W L H)
I will likely be re-upping my license and eventually migrating to Motive, but I am constrained to versions pre-2.4.0 for the time being (until I can get funding approved) and I need to get this round of experiments done.
Any help please? Thanks!!