I’ve had similar problems with my Oculus Rift DK2 tracker
and found a solution that I’d like to share, since there seems to be very
little advice about this on the internet. It boiled down to a problem with the USB
My hardware set-up is:
Windows 7, 64-bit
Intel Xeon E5520 (4 cores, 8 threads, 2.26 GHz) – below minimum
spec, I think
NVIDIA GTX970 – just meets minimum spec
Oculus SDK 0.5.0.1 (also got it working with SDK 0.8.0.0)
To begin with, I had only USB 2.0 ports on my PC. The HMD
device was working fine, but the tracker was not working at all. The Oculus
Configuration Utility failed to detect it: ‘Oculus Rift DK2 Attached; No
Tracker Attached’. The blue tracker LED was off.
I fitted a USB 3.0 card (with 2 ports) into a spare PCIe
slot and plugged both the tracker and the HMD into it. This made no difference:
the tracker was still not working and the Oculus Configuration Utility still
said ‘Oculus Rift DK2 Attached; No Tracker Attached’. I did notice, though,
that the tracker was being recognised by Device Manager. It was listed under ‘Oculus
VR Devices’ > ‘Oculus Video Camera’, was reported to be working and had the correct
driver installed. The HMD was listed separately as an HID device.
At this point, I decided to try updating to Oculus SDK
0.8.0.0, which includes newer drivers for the tracker and the HMD. This didn’t
solve the problem, but it did give me some useful error messages which enabled
me to find a solution. The error messages I got were the same as the ones
reported by earlier posts in this thread. The Oculus Configuration Utility
periodically alternated, apparently at random, between two sets of error
1) Oculus Configuration Utility alternates between ‘Oculus
Ridt DK2 Attached; No Tracker Attached’ and ‘Oculus Rift DK2: Ready’. Also,
there is a warning message saying ‘! Tracker can not get USB bandwidth’. The
blue tracker LED flashes on and off.
2) Oculus Configuration Utility reports ‘Oculus Rift DK2:
Ready’. But there is also a warning message saying ‘! Tracker synch cable
disconnected’. The blue tracker LED is on continuously.
The bandwidth error message suggested that the tracker
was not getting a sufficient data rate through the USB 3.0 port. Some PCIe
slots share their bandwidth with other slots on the motherboard, so I tried
fitting a second USB 3.0 card (which I happened to have) to another free PCIe
This almost worked. Now the Oculus Configuration Utility continuously
reported ‘Oculus Rift DK2: Ready’, the blue LED was on continuously, and there
were no warning messages most of the time. However, a new warning occasionally
appeared: ‘! Tracker truncated a higher than acceptable number of frames in the
last time period (expected <= 1, got 2)’. Also, when viewing the demo
program, the image being viewed would occasionally jump to a new position.
This warning about frames being dropped suggested that
there was still a problem with the data rate. This was because the tracker and
HMD were plugged into ports on the same USB 3.0 card and were sharing
bandwidth. The problem was solved by plugging the HMD into a port elsewhere
(either on the other USB 3.0 card or one of my USB 2.0 ports – it didn’t matter
which), so that the tracker no longer had to share bandwidth. Finally, the
tracker worked with no error messages.
Having got the tracker working, I rolled back to Oculus
SDK 0.5.0.1 and found that the tracker worked just as well with this Oculus SDK
version. So the problem had to do entirely with the USB ports.