Which operating systems are these plugs compatible with?
The drivers are currently only available for Windows 7, 8, 10, 11 and 2008 Server (in 32bit and 64bit).
Linux with kernel releases 2.6.31 or higher are supported, when used with BurnInTest for Linux v3.1 (or later). libusb 1.0 is also required. (This is standard Linux library supplied with almost all Linux distributions).
Slax Linux (7.0.8) is not supported as it appears there is a possible device driver bug that prevents the USB3 plug from entering loopback mode correctly, other live systems tested (Kubuntu 12.04, Fedora 18, Porteus 3.0.1) do not seem to be affected by the same bug.
Do I need a device driver to use these plugs?
Are the device drivers compatible with all versions of BurnInTest and USB3Test?
Does the PassMark USB 3.0 loop back plug appear in my Device Manager as a new USB Device?
Can the plugs also be used on PCs with older USB 2.0 ports?
How can USB 2.0 functionality be tested on USB 3.0 ports?
What is the meaning of the 4 LEDs on the device?
Can I run multiple copies of USB3Test at the same time?
Can I run USB3Test at the same time as BurnInTest?
Can the USB3 plugs be used to test bus powered USB hubs?
I get an error message "This device cannot start (code 10)" what does this mean?
What type of USB data transfer type does the USB 3.0 loopback plug use?
USB3 plug shows "Fatal Error. Update software and reconnect the plug". What does this error message mean?
The red Error LED goes on. What does this mean?
It means the USB 3.0 loopback plug has flagged a Device transceiver error. Device transceiver errors are triggered when the USB transceiver on the USB 3.0 loopback plug detects what it considers to be an error. These are events at a low level that may lead to the packet being retransmitted. They do not represent data errors at the application level. These errors are normally not visible to the user, but are displayed to help identify potential problems, for example, poor quality cables, cables that are too long, or system internals with insufficient electrical shielding with high electrical interference on the bus. Errors that may cause a device transceiver error are divided into two groups:
Physical layer errors:
Link layer errors:
For additional details of each error, please refer to the pages referenced of the USB3.0 specification, Revision 1.0.
It should be noted that device transceiver errors are not an indication that the USB port does not comply with the USB Specification.
What maximum speed should I expect from my USB port?
USB3.0 Super-speed is normally quoted as 5Gb/Sec. Data rates will never reach these speeds on a real device because of 8b/10b encoding, protocol overhead and host and device latency. In theory, the maximum bandwidth of USB port is limited to the following speeds:
There are also other factors which further decrease the USB port speed in practice:
Table 1 and 2 show the result of our test for actual throughput of USB port on different systems using USB3 Loopback plug (Firmware version 2.3). We limited our analysis to a single USB3 loopback plug that is directly attached to the host.
|PC Information||Host Controller||Operating System||Throughput (Mb/s)|
|Intel® Core™ i5-6600K, 3.50 GHz, 16 GB RAM||Intel® USB 3.0 eXtensible Host Controller||Windows 10 64-bit||3472|
|Intel® Core™ i5-4210U, 1.7 GHz, 16 GB RAM||Intel® USB 3.0 eXtensible Host Controller||Windows 10 64-bit||3469|
|Intel® Core™ i5-6600K, 3.50 GHz, 16 GB RAM||Welland UP-314C PCIe USB3 card (Renesas USB 3.0 eXtensible Host Controller)||Windows 10 64-bit||2973|
|AMD A6-3670 APU, 2.70 GHz, 8 GB RAM||AMD USB 3.0 Host Controller (Driver Ver 22.214.171.124)||Windows 7 64-bit||2903|
|AMD A10-7850K Radeon R7, 3.70 GHz, 4 GB RAM||ASMEDIA USB3.0 eXtensible Host Controller (Driver Ver 126.96.36.199)||Windows 10 64-bit||2896|
|Intel Core i5-2540M CPU, 2.60 GHz, 4 GB RAM||NEC Electronics USB 3.0 Host Controller (Driver Ver 188.8.131.52)||Windows 7 64-bit||2401|
*Table 1: SuperSpeed USB throughput comparison
|PC Information||Host Controller||Operating System||Full Speed Throughput (Mb/s)||High Speed Throughput (Mb/s)|
|Intel® Core™ i5-6600K, 3.50 GHz, 16 GB RAM||Intel® USB 3.0 eXtensible Host Controller||Windows 10 64-bit||374||9.3|
|Intel® Core™ i5-4210U, 1.7 GHz, 16 GB RAM||Intel® USB 3.0 eXtensible Host Controller||Windows 7 64-bit||374||9.3|
|AMD FX™-8150 Elight-Core 3.6 GHz. 4GB RAM||ASMEDIA USB3.0 eXtensible Host Controller (Driver Ver 184.108.40.206)||Windows 7 64-bit||368||9.3|
|AMD A10-7850K Radeon R7, 3.70 GHz, 4 GB RAM||ASMEDIA USB3.0 eXtensible Host Controller (Driver Ver 220.127.116.11)||Windows 10 64-bit||365||9.2|
|Intel® Core™ i5-6600K, 3.50 GHz, 16 GB RAM||Welland UP-314C PCIe USB3 card (Renesas USB 3.0 eXtensible Host Controller)||Windows 10 64-bit||330||8.4|
*Table 2: High Speed and Full Speed USB throughput comparison
I'm getting frequent errors in benchmark mode with USB3Test
We have observed many errors can occur on front panel ports, particularly in benchmark mode, the errors messages that can be logged include;
These errors will often cause the USB3 loopback plug to disconnect/reconnect. Testing the back panel ports on the same machine does not show any similair errors which seem to indicates that the front port panels have inferior wiring and shielding in place, very similar to the USB2 issues that could occur on front panel ports.
"Device not recognised" error displayed after power on with USB3 attached.
We have seen some cases where if the system is powered on with the USB3 plug attached then Windows will display a "Device not recognised" error and the USB3 plug may only display that it is connected at USB2 speed (480Mb/s).
In BIOS there is often a “xHCI mode” BIOS setting. Sometimes this is also called a "xHCI Pre-Boot Driver". This option controls if the physical USB3 ports are handled via the USB2.0 EHCI controller or the xHCI USB3.0 controller. In particular having it set to “Auto”, “Smart Auto” or EHCI can cause a problem for the USB3.0 loopback plugs on a few motherboards. Auto which will emulate a USB2 port during the boot process until the USB3 driver is loaded once Windows starts. This can cause the plug to connect first at 480Mb/s and not refresh the display correctly when the link changes to 5Gb/s.
In our testing we saw the USB3 test would still run correctly and at 5Gb/s but the display could still indicate 480Mb/s, but it has been reported that in some cases the device will remain as "unrecognised" and require disconnected and reconnected in order to work.
If you have a problem, we would recommend changing the "xHCI Pre-Boot Driver" to Enabled and xHCI mode to "Enabled" rather than any “Auto” setting for testing purposes. We suspect the underlying cause is a BIOS bug in the effected motherboards & this workaround avoids the bug.
However there are also other cases of buggy BIOS implementations causing USB3 devices not be recognised, while in xHCI mode, unless they are plugged in when the machine is powered on. A BIOS update is required in this case.
My USB3 device is becoming disconnected or not enumerating at SuperSpeed (5Gb/s) during a resume from a sleep or hibernate.
"I'm getting Benchmark read/write failed or blue screen errors in isochronous mode when device enumerated as Full Speed or High Speed.
Is there an Application Programming Interface available?
How do I find the device Hardware Revision and what are the differences between hardware revision 1 and revision 2?
The hardware revision is printed on the product label on the back of the device. The below table summarizes the main differences across revisions.
|Rev 1||Rev 2|
|Clock||19.2Mhz (crystal)||19.2Mhz (oscillator)|
|ESD Protection on VBUS||ESD, IEC 61000-4-2, 8kV contact, 5kV air discharge||ESD, IEC 61000-4-2, ±30kV contact, ±30kV air discharge
EFT, IEC 61000-4-4, 40A (5/50ns)
|ESD Protection on USB2 lines||ESD, IEC61000-4-2 level 3A, ± 6kV contact, ±8-kV air discharge
ESD, IEC61000-4-2 level 4C, ± 8kV contact, ±15-kV air discharge
|ESD, IEC 61000-4-2, ±20kV contact, ±30kV air discharge
EFT, IEC 61000-4-4, 40A (5/50ns)
|ESD Protection on USB3 lines||ESD, IEC61000-4-2, ±20kV contact, ±20kV air discharge||ESD, IEC 61000-4-2 Level 4, ±12kV contact, ±15-kV air discharge
EFT, IEC 61000-4-4, 80 A (5/50 ns)
|Voltage Protection (+5V & GND)||±28V||±26V|
|On board voltage regulators||1.2 (linear regulator), 3.3 (linear regulator)||1.2 (switching regulator), 3.3 (linear regulator)|
|Power Consumption||115mA (Typical USB 2.0 operation)
170mA (Typical USB 3.0 operation)
|75mA (Typical USB 2.0 operation)
90mA (Typical USB 3.0 operation)
In addition to the above-mentioned differences, in the new revision:
Does USB3 Loopback plug incorporate ESD and overvoltage protection circuits?
Can the USB3 plug be used for USB port auditing? (Detecting juice jacking)
What are the common failure modes of the USB3 plugs?
"Update software and reconnect the plug" error displayed on the device LCD after plugging to USB port.