TW202349222A - Automatic usb 3 hub for detecting and changing link speed - Google Patents

Abstract

A USB control method comprising: counting errors encountered by a USB connection; comparing a number of counted errors to an error count threshold within a set time frame; identifying a port speed configuration for the USB connection; and changing the port speed configuration for the USB connection to a slower port speed configuration than the identified port speed configuration.

Description

Automatic USB 3 hub for detecting and changing link speed

This application relates to USB 3 link operations, and specifically, to systems and methods for detecting marginal USB 3 link operations and changing the link connection speed to improve overall performance.

The Universal Serial Bus (USB) 1.0 specification was originally developed in the 1990s to provide a bus and interface to standardize communications between computers and peripheral devices such as keyboards, printers, cursor pointing devices, external drives, etc. . USB 1.0 supports speeds up to 1.5Mbps, while USB 1.1 supports speeds up to 12Mbps. Since then, USB has progressed to versions 2.0 and 3.0 and is ubiquitous in computers and portable devices such as smartphones, tablets and MP3 players. USB 2.0 supports speeds up to 480Mbps. Later, USB 3.0 became the universal standard and supported speeds up to 5Gbps. USB 3.0 and/or USB 3.1 begin to have Gen 1 and Gen 2 capabilities. The difference between USB 3.1 Gen 1 and USB 3.1 Gen 2 is only in speed. USB 3.1 Gen 1 supports speeds up to 5Gbps, while USB 3.1 Gen 2 supports speeds up to 10Gbps. Later, USB 3.2 became the universal standard. Again, the difference between USB 3.2 Gen 1 and USB 3.2 Gen 2 is simply speed. USB 3.2 Gen 1 supports speeds up to 5 Gbps, while USB 3.2 Gen 2 supports speeds up to 10 Gbps.

Usually, in USB communication, there is a host, and another peripheral device is a device connected to the host through the bus. The host powers the bus, issues commands and overall maintains control of its connections. Peripheral devices typically do not initiate activity for any bus control. For example, a personal computer acts as a host for a USB "thumb drive" device. A USB hub is a device that expands a single USB port into several USB ports so that more ports can be used to connect multiple devices to the host.

The USB Type-C connector has been developed to help enable thinner and more elegant product designs, enhance usability, and provide a growth path for future versions of USB with enhanced performance. Type-C connectors are built based on existing USB 3.1 and USB 2.0 technologies. USB Type-C is a 24-pin USB connector system with rotationally symmetrical connections. The designation C refers only to the connector's physical configuration or form factor and should not be confused with the connector's specific capabilities as indicated by its transport specification.

When a USB device is connected to a host via a USB cable, it sometimes encounters poor quality communication. The current USB specification does not provide a solution for poor quality connections and assumes that USB devices and hosts will take actions to mitigate data loss issues. Current USB devices, hosts and hubs can barely handle poor data transfers. Specifically, the current USB specification does not envision USB hubs playing a proactive role in error detection and mitigation. No mechanism currently exists, and this type of functionality has not been observed in currently available USB hubs.

There is a need for a USB hub, host or device that can automatically detect significant or critical data loss in a USB connection and take corrective actions to reduce the impact on end users.

A device includes non-transitory machine-readable media containing instructions. When loaded and executed by the processor, these instructions cause the processor to perform automatic USB hub bad link quality detection and speed roll-back. A USB host may force individual USB hub ports to a specified USB speed (i.e., force a USB port operating at Gen 2 speed to switch to Gen 1 speed due to excessive errors detected while operating at Gen 2 speed) .

According to one aspect, a method is provided, including: counting errors encountered by a USB connection; comparing the number of counted errors with an error threshold within a set time frame; identifying an error number used for the USB connection. a port speed configuration; and, changing the port speed configuration for the USB connection to a port speed configuration that is slower than the identified port speed configuration.

Another aspect provides an apparatus including: a connection detector circuit that counts errors encountered by a USB connection operating at an initial speed and compares the number of counted errors to a preset error threshold , and identify a port speed configuration for the USB connection; and, a control circuit that changes the port speed configuration for the USB connection to a speed slower than the initial speed.

According to another aspect, a system is provided, including: a USB hub having an upstream port, a downstream port and a switch in electrical communication with the upstream port and the downstream port; a USB host through a first A USB connection for electrical communication with the upstream port; a USB device for electrical communication with the downstream port through a second USB connection; a connection detector circuit for the first USB connection or the second USB counting errors encountered by the connection, comparing the number of counted errors to a preset error threshold, and identifying a port speed configuration for the first USB connection or the second USB connection; and, a control circuit, It changes the port speed configuration for the first USB connection or the second USB connection to a slower speed.

The figures illustrate example processes and systems for detecting marginal USB 3 link operations and adjusting connection speed to improve overall performance and prevent disconnections. Various error counters can be employed for each port, and when a counter exceeds a configured threshold, specific actions can be taken to regulate the connection speed. The element symbols for any illustrated element appearing in multiple different drawings have the same meaning in the multiple figures, and, if any, no reference is made herein to any illustrated element in the context of any particular drawing. References or discussions of , also apply to every other drawing showing the same illustrative element.

Automated USB hosts, automated USB hubs, and automated USB devices for poor link quality detection and speed roll-back are described here. When a user plugs a USB device into a USB host or USB hub, an automatic connection is established and multiple ports and speeds are configured based on policy settings. Furthermore, automatic USB hosts, automatic USB hubs, and automatic USB devices can be used with Type-C capabilities by implementing various error counters for each port and taking specific actions to regulate the connection speed when a counter exceeds a configured threshold. USB 3 interface. For example, a USB hub can allow a poor-quality device connected to a poor-quality cable to operate at a reduced signal rate to prevent complete failure. USB hubs can fine-tune their functionality to meet custom specifications. USB hubs are compatible with USB devices and cables to operate together. Of course, the USB hub function can be implemented using the USB hub's firmware and may not have a new hardware design, but various hardware implementations are still possible and can reduce the burden on the firmware and improve reliability.

One aspect may allow poor quality devices or devices connected to poor quality cables to operate at reduced signal rates in order to prevent complete failure. Bad quality means that the transmission rate has more than a critical number of errors within a given period of time. A USB hub can fine-tune its functionality to meet the specifications/needs of the host/hub/device environment. Devices and cables that are unable to operate at a set signal rate can be configured to operate at a slower signal rate using connection detector circuitry as disclosed herein. Examples may be implemented within the firmware of the host, hub, or device, and may not feature new hardware designs. Alternatively, if implemented in hardware, hardware implementation can also reduce the burden of firmware development and improve reliability.

When connecting a USB device via a USB cable, you sometimes experience poor quality communication. For example, a USB 3.2 device, that is, a device that conforms to the USB 3.2 standard published by the USB Implementers Forum (USB-IF), may be connected to a USB hub port with a low-quality USB cable. More specifically, a 10Gbit/s capable USB 3 Gen 2 device with a poor-quality cable may have a lower overall data throughput than the same device and cable when connected to a 5Gbit/s capable USB 3 Gen 1 port. quantity. Bad data communication can also occur on the USB hub's upstream port, for example, between the USB hub and the USB host, causing connectivity to all devices on the downstream port to be affected. In this case, there may be three possible data loss scenarios: (1) minimal to moderate data loss with occasional corrupted packets; (2) massive data loss with frequent corrupted packets and USB 3 link recovery startup ; (3) Key data is lost, among which three packets failed consecutively. The average user is unlikely to notice the first scenario, which is minimal to moderate data loss. However, average users may notice the second scenario as the overall data throughput will be lower. In the third scenario, the average user will definitely notice the connection problem because the USB host may take action by turning off the USB device.

Bad quality USB connections can be detected through various firmware- or hardware-based error counters. Types of errors counted may include: number of link recovery entries; number of warm resets received; number of retries detected; and, LBAD (link bad) link commands received quantity. For example, if you count fifteen errors in one second for any of these types of errors, you can determine that the USB connection is of poor quality. The configurable parameters of the terminal system integrator may include: mask operation for error types; error counter thresholds (one threshold for each error type), where the user can set the threshold to define "excessive" Meaning; mode selection, infinite error count persistence mode or rolling window mode (rolling window mode); and, rolling window timing. The threshold used to detect error conditions indicating a bad USB connection can be based on a single error type, can be based on a combination of error types, and can also be based on the number of errors counted per unit time. For a combined example, one threshold can be preset for the first error type, another threshold for the second error type, and both thresholds met before determining that the USB connection is of poor quality. New hardware or USB devices can be run in the port to implement error counters. Connection quality can be detected/adjusted by USB hub, USB host or USB device.

Referring to the drawings, with particular attention to FIG. 1 , a schematic diagram illustrating an exemplary USB hub environment is shown according to an example. As shown, system 100 includes USB hub 102, USB host 112, and USB device 114. The USB hub 102 has one upstream port 108 and four downstream ports 110a, 110b, 110c, and 110d. Switching hub 104 switches between downstream ports 110a, 110b, 110c, 110d. The control circuit 105 is used to receive and process signals through the USB port and control the switching hub 104 . The control circuit 105 may be executed by processor instructions, functions, library calls, subroutines, shared libraries, software as a service, analog circuits, digital circuits, control logic, through hardware Description language programmed digital logic circuits, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), or any suitable combination thereof or any other suitable mechanism, regardless of Whether implemented in a single device or distributed across multiple devices. Connection detector circuit 106 detects errors per unit time and identifies the port speed. Speed circuit 103 changes the port to a slower speed configuration. Both the connection detector circuit 106 and the speed circuit 103 can be executed by instructions, functions, library calls, subroutines, shared libraries, software as a service, analog circuits, digital circuits, control logic, etc. in the media executed by the processor. Hardware description language programmed digital logic circuits, application specific integrated circuits (ASIC), field programmable gate arrays (FPGA), programmable logic devices (PLD), or any suitable combination thereof or any other suitable mechanism , whether implemented in a single device or distributed across multiple devices.

A USB46x4 hub available from Microchip Technology Incorporated of Chandler, Arizona can be implemented as USB hub 102 if modified to include connection detector circuit 106 and speed circuit 103 as described herein. In this example, USB host 112 is connected to USB hub 102 through cable 109 . The USB device 114 can also be connected to the hub 102 through one of the downstream ports 110a, 110b, 110c, and 110d, where a Type-C connector can be used for the connection. In Figure 1, USB hub 102 has connection detector circuitry 106, which includes hardware-based error counters, firmware, or both, to regulate connections. The connection detector circuit 106 may be implemented by processor-executed instructions, functions, library calls, subroutines, shared libraries, software as a service, analog circuits, digital circuits, control logic, through hardware description language programs ionized digital logic circuits, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), or any suitable combination thereof or any other suitable mechanism, whether in a single device or distributed across multiple devices.

FIG. 2 shows an algorithm flow diagram for the connection detector circuit 106 of FIG. 1 , whereby the USB hub 102 detects a poor quality USB connection and adjusts the connection to improve performance. In this case, the USB hub 102 monitors the USB connection through the upstream port 108 and cable 109 together with the downstream ports 110a to 110d, and checks whether it is connected to a USB host or a USB device. The algorithm starts by clearing (202) all error counters. The errors are then counted (204) and it is determined whether the number of errors has exceeded the error threshold within the set time frame. If the error count threshold is not exceeded within the set time frame, the algorithm waits (206), clears (202) the error counter, and starts another count of errors again within the new set time frame (204). If the error threshold is exceeded within the set time frame, the algorithm then determines the port speed (208) for the connection that exceeds the error threshold within the set time frame: for example, USB 3.2 Gen 2 (10G) or USB 3.2 Gen 1(5G). In both cases, the algorithm then determines (210A and 210B) the port type: (1) upstream (eg, connected to USB host 112); or (2) downstream (eg, connected to USB device 114). If the error threshold (204) is exceeded within the setup time frame which may indicate a bad connection on the upstream port configured for USB 3.2 Gen 2 (10G) speed, then connection detector circuit 106 or control circuit 105 or both Temporarily disconnect (212) the upstream port USB 3 interface and reconnect it with Gen 2 functionality blocked, thereby forcing a lower data speed, i.e. USB 3 Gen 1 throughput. This action causes the upstream connection to drop to a USB 3 Gen 1 (5G) port speed connection through corresponding actions by the USB host 112. If a port that exceeds the error threshold within a set time frame is detected on an upstream port configured for USB 3 Gen 1 (5G) speed (eg, connected to the USB host 112 ), the connection detector circuit 106 disconnects (214) upstream port USB 3 interface, and issues a USB 3 warm reset to all downstream ports with attached USB 3 devices, and then disconnects/disables all downstream USB 3 interfaces. This action causes the downstream connection to be reconfigured for USB 2. If the port that exceeds the error threshold within the setup time frame is a downstream port configured for USB 3.2 Gen 2 (10G) speed, then connection detector circuit 106 or control circuit 105 or both issue a warm reset (216) to downstream port and mask the Gen 2 capability bits, then reconnect the port with the Gen 2 capability bits masked. This action causes its connection to be reconfigured for USB 3 Gen 1 (5G) speeds. If the port that exceeds the error threshold during the setup time frame is on a downstream port configured for USB 3.2 Gen 1 (5G) speed, then connection detector circuit 106 or control circuit 105 or both issue a warm reset to that port. port, and disconnect/disable the USB 3 interface. This action causes its connection to be reconfigured for USB 2 speeds.

For connection quality detection using a USB hub, when the number of errors rises above a certain threshold within a set time frame, one or more routines provided in Table 1 can be initiated. Table 1 error condition reaction final result Too many errors on upstream port at USB 3.2 Gen 2 speed Temporarily disconnect the upstream USB 3 interface and reconnect it with Gen 2 functionality blocked. Upstream/device connections will reconnect as USB 3 Gen 1 Too many errors on upstream port at USB 3.2 Gen 1 speed Disconnecting the upstream USB 3 interface issues a USB 3 warm reset to all downstream ports with USB 3 devices attached, and disconnects/disables downstream USB 3 interfaces The device will reconnect via USB 2 Too many errors for downstream ports at USB 3.2 Gen 2 speeds Issue a USB 3 warm reset and reconnect with Gen 2 functionality blocked. The device will reconnect with USB 3 Gen 1 Too many errors on downstream ports at USB 3.2 Gen 1 speed Issues a USB 3 warm reset to the port and disconnects/disables the downstream USB 3 interface The device will reconnect via USB 2 This feature can be implemented in the USB hub's firmware or hardware.

FIG. 3 shows a schematic diagram of an example USB hub environment similar to that shown in FIG. 1 , except that the connection detector circuit 106 and the speed circuit 103 are located in the USB host 112 . USB host 112 has connection detector circuit 106, which may include hardware-based error counters or firmware, or both, to determine the quality of throughput, and speed circuit 103, which may include hardware or firmware, or both. or to regulate its connection. USB host 112 is connected to hub 102 via upstream port 108 via cable 109 . In an example, connection detector circuit 106 may be in USB host 112 and speed circuit 103 may be in USB hub 102 . In an example, connection detector circuit 106 may be in USB hub 102 and speed circuit 103 may be in USB host 112 .

Figure 4 shows an algorithm flow diagram for the connection detector circuit 106 of Figure 3, whereby the USB host 112 detects poor quality USB connections (cable 109 and upstream port 108) and adjusts their connections to improve performance. Connection detector circuit 106 begins by clearing (402) all error counters. Errors are then counted (404) and it is determined whether the number of errors has exceeded the error threshold within the set time frame. If the error number threshold is not exceeded in the set time frame, the algorithm waits (406), clears the error counter (402), and starts error processing in the set time frame, that is, in the next set time frame. Another count of (404). If the error threshold is exceeded within the setup time frame, the algorithm then determines (408) the port speed of the connection: USB 3.2 Gen 2 (10G) or USB 3.2 Gen 1 (5G). If the error threshold is exceeded for the USB connection 109 within the set time frame, the algorithm of the speed circuit 103 is configured for USB3 Gen 2 (10G) speed, where the speed circuit 103 issues a USB 3 warm reset to its port, and Reconnect with Gen 2 capability bits obscured. This action causes its connection to be reconfigured for USB 3 Gen 1 (5G) speeds. If the error threshold is exceeded within the setup timeframe for a USB connection 109 configured for USB 3.2 Gen 1 (5G) speed, the speed circuit 103 issues a USB 3 Warm Reset (414) to the port and disconnects/disables USB 3 interface. This action causes its connection to be reconfigured for USB 2 speeds because USB 3 functionality has been disconnected/deactivated.

For connection quality detection using a USB host, one or more routines provided in Table 2 can be initiated when the number of errors rises above a certain threshold within a set time frame. Table 2 error condition reaction final result Too many errors for downstream ports at USB 3.2 Gen 2 speeds Issues a USB 3 warm reset and masks the Gen 2 capability bits on the USB 3 interface The connection will reconnect as USB 3 Gen 1 Too many errors on downstream ports at USB 3.2 Gen 1 speed Issues a USB 3 warm reset and disconnects/disables the USB 3 interface. The connection will reconnect as USB 2 This feature can be implemented in the USB host's firmware or hardware.

FIG. 5 shows a schematic diagram of connection detector circuit 106 in USB device 114 within an example USB hub environment. As shown in the figure, the system 100 includes a hub 102, one or more control circuits 105, a USB host 112 and a USB device 114, wherein a plurality of USB devices 114 can be connected to the hub 102 via downstream ports 110a to 110d. The USB device 114 has a connection detector circuit 116 including a hardware-based error counter or a firmware-based error counter or both, and a speed circuit 103 for regulating the connection.

FIG. 6 shows an algorithm flow diagram for the connection detector circuit 106 and the speed circuit 103 of FIG. 5 , whereby the USB device 114 detects a poor quality USB connection and adjusts the connection to improve performance. In this case, USB device 114 monitors the USB connection. Connection detector circuit 106 begins by clearing (602) all error counters. The errors are then counted (604) and it is determined whether the number of errors has exceeded the error threshold within the set time frame. If the error threshold is not exceeded within the set time frame, the algorithm waits (606), clears the error counter (602), and starts erroring again in the set time frame (i.e., in a subsequent set time frame). A count (604). If the error threshold is exceeded within the setup time frame, the algorithm then determines (608) the port speed of the connection: USB 3 Gen 2 (10G) or USB 3 Gen 1 (5G). If the error threshold is exceeded within the setup time frame when the USB connection is configured for USB 3.2 Gen 2 (10G) speed, the speed circuit 103 temporarily disconnects (612) the USB 3 interface and blocks the Reconnect without Gen 2 capable bits. This action causes its connection to drop to a USB 3 Gen 1 (5G) port speed connection. If the error threshold is exceeded within the setup time frame when the USB connection is configured for USB 3.2 Gen 1 (5G) speed, speed circuit 103 disconnects/disables (614) the USB 3 interface and issues a USB 3 Warm reset to this port. This action causes the connection to be reconfigured for USB 2.

For connection quality detection using USB devices, when the number of errors rises above a certain threshold within a set time frame, one or more routines provided in Table 3 can be initiated. table 3 error condition reaction final result Too many errors on upstream port at USB 3.2 Gen 2 speed Temporarily disconnect/disable the upstream port USB 3 interface and reconnect it while blocking Gen 2 capabilities Upstream/device connections will drop to USB 3 Gen 1 Too many errors on upstream port at USB 3.2 Gen 1 speed Issue a USB 3 warm reset to the port and then disconnect/disable the upstream port USB 3 interface Connection will drop to USB 2 This functionality may be implemented in the USB device 114's firmware or hardware.

The connection detector circuit 106 or the speed circuit 103 disclosed herein can be implemented in USB 3 hubs, USB hosts and USB devices designed for the automotive industry. In particular, the automotive industry almost universally adopts USB Type-C with USB power delivery. port.

FIG. 7 shows a schematic diagram of a connection detector and speed circuit 706 , which may be an example of the connection detector circuit 106 or the speed circuit 103 . See Figures 1, 3 and 5. An example of connection detector and speed circuit 706 has processor 702 and non-transitory machine-readable medium 704 including instructions 708 . Instructions 708, when loaded and executed by processor 702, cause processor 702 to perform automatic USB hub bad link quality detection and speed rollback. The instructions include: counting errors encountered by the USB connection; comparing the number of counted errors with a preset critical number of errors; identifying the port speed configuration of the USB connection; and changing the port speed configuration of the USB connection to a higher slow speed. These functions may also be programmed to be performed by the speed circuit 103. See Figures 1, 3 and 5.

Figure 8 shows a schematic diagram for detecting poor quality USB connections and adjusting the connection to improve performance, including a connection detector circuit 806 and a speed circuit 803.

Although examples have been described above, other variations and examples may be made from this disclosure without departing from the spirit and scope of these disclosed examples.

Related Patent Applications: This application claims priority from generally owned U.S. Patent Application No. 63/319,002, filed on March 11, 2022, the entire contents of which are hereby incorporated by reference.

100:System 102: (USB) hub 103: Speed circuit 104:Switching hub 105:Control circuit 106: Connect the detector circuit 108: Upstream port 109: Cable; USB connection 110a: Downstream port 110b: Downstream port 110c: Downstream port 110d: Downstream port 112: USB host 114: USB device 202, 204, 206, 208, 210A, 210B, 212, 214, 216, 218: (algorithm) steps 402, 404, 406, 408, 414, 416: (algorithm) steps 602, 604, 606, 608, 612, 614: (algorithm) steps 702: Processor 704: Non-transitory machine-readable media 706: Connect the detector and speed circuit 708:Command 803: Speed circuit 806: Connect detector circuit

FIG. 1 is a schematic diagram illustrating an example USB environment including a USB hub with connection detector circuitry and speed circuitry, a USB host, and a USB device. Figure 2 shows an algorithm flow diagram for the connection detector circuit and speed circuit of Figure 1, whereby the USB hub can detect poor quality USB connections and adjust the connection to improve performance. Figure 3 is a schematic diagram illustrating an example USB environment including a hub, a USB host with connection detector circuitry, and a USB device with a USB hub having speed circuitry. Figure 4 shows an algorithm flow chart for the connection detector circuit and speed circuit of Figure 3, whereby the USB host can detect poor quality USB connections and adjust the connection to improve performance. Figure 5 is a schematic diagram illustrating an example USB environment including a hub, a USB host, and a USB device with connection detector circuitry and a USB hub with speed circuitry. Figure 6 shows an algorithm flow diagram for the connection detector circuit and the speed circuit of Figure 5, whereby the USB device can detect poor quality USB connections and the speed circuit can adjust the connection to improve performance. Figure 7 shows a schematic diagram of the software implementation used to connect the detector circuit. Figure 8 shows a schematic diagram for detecting poor quality USB connections and adjusting the connection to improve performance, including a connection detector circuit and a speed circuit.

100:System

102: (USB) hub

103: Speed circuit

104:Switching hub

105:Control circuit

106: Connect the detector circuit

108: Upstream port

109: Cable; USB connection

110a: Downstream port

110b: Downstream port

110c: Downstream port

110d: Downstream port

112:USB host

114: USB device

Claims (20)

A method that includes: Count errors encountered on a USB connection; Comparing the number of counted errors with an error number threshold within a set time frame; Identify the port speed configuration used for the USB connection; and The port speed configuration used for the USB connection is changed to a slower port speed configuration compared to the identified port speed configuration. The method of claim 1, wherein counting errors includes counting one type of errors selected from: link recovery items, received warm resets, detected retries, and received Bad link command. The method of claim 1, wherein the step of counting errors includes counting two or more types of errors selected from: items of link recovery, warm resets received, detected Retries, and received link bad commands. The method of claim 3, wherein the comparing step includes: comparing respective numbers of counted errors regarding the two or more types of errors with respective numbers of counted errors regarding the two or more types of errors. The error number threshold is compared. The method of claim 1, wherein the step of identifying the port speed configuration for the USB connection includes: identifying a port speed configuration selected from 10Gbps and 5Gbps. The method of claim 1 includes: determining whether the USB connection is through an upstream port or a downstream port. The method of claim 1, wherein the step of changing the port speed used for the USB connection to a slower speed includes: changing from 10Gbps to 5Gbps. The method of claim 1, wherein the step of changing the port speed used for the USB connection to a slower speed includes: changing from 5Gbps to 480Mbps. A device consisting of: A connection detector circuit, wherein the connection detector circuit counts errors encountered by a USB connection, wherein the connection detector circuit compares the counted number of errors with a set time frame An error threshold is compared, wherein the connection detector circuit identifies a port speed configuration for the USB connection; and A speed circuit changes the port speed configuration of the USB connection to a slower port speed configuration compared to the identified port speed configuration. The apparatus of claim 9, wherein the connection detector circuit counts one type of error selected from: link recovery entries, received warm resets, detected retries, and received Bad link command. The apparatus of claim 9, wherein the connection detector circuit counts two or more types of errors selected from: link recovery entries, warm resets received, detected Retries, and received link bad commands. The device of claim 9, wherein the connection detector circuit compares respective numbers of counted errors with respect to the two or more types of errors to The respective error number thresholds are compared. The device of claim 9, wherein the connection detector circuit identifies a port speed configuration selected from 10Gbps and 5Gbps for the USB connection. The device of claim 9, wherein the connection detector circuit determines whether the USB connection is through an upstream port or a downstream port. The device of claim 9, wherein the speed circuit reduces the port speed used for the USB connection from 10Gbps to 5Gbps. The device of claim 9, wherein the speed circuit reduces the port speed used for the USB connection from 5Gbps to 480Mbps. A system that includes: A USB hub including an upstream port, at least one downstream port, and a switch in electrical communication with the upstream port and the at least one downstream port; a USB host electrically communicating with the USB hub upstream port through a first USB connection; a USB device in electrical communication with the at least one USB hub downstream port through a second USB connection; A connection detector circuit, wherein the connection detector circuit counts errors encountered by the first or second USB connection, wherein the connection detector circuit counts the counted errors within a set time frame comparing the number of errors to an error threshold, wherein the connection detector circuit identifies a port speed configuration for the first or second USB connection; and A speed circuit that changes the port speed configuration of the first or second USB connection to a slower port speed configuration compared to the identified port speed configuration in response to a greater than error in the setup time frame The number of errors counted for the critical value. The system of claim 17, wherein the USB hub includes the connection detector circuit. The system of claim 17, wherein the USB host includes the connection detector circuit. The system of claim 17, wherein the USB device includes the connection detector circuit.