USB Connection Diagram: Host Controller, Hub Architecture and Device Enumeration
This is a free printable usb connection diagram: download the diagram as SVG or open it and print to paper or PDF.
A USB connection diagram illustrates how a host controller communicates with devices through a tiered-star topology, showing bus segments, hub repeaters, and the enumeration process that assigns addresses and negotiates power for each connected device.
Diagram checks and scope
- Components
- 5
- Wired connections
- 9
- Automated check
- Automated pin, route, source, and topology checks passed; this is not a safety certification.
USB employs a strict host-centric, tiered-star topology where a single host controller manages all bus traffic. No USB device can initiate a transfer — all communication is scheduled and directed by the host controller, which polls devices and allocates bus time in predetermined frames of 1 ms duration for USB 2.0 or 125 µs microframes for USB 3.0. The host controller resides in the PC chipset or SoC and presents one or more root hub ports. Each root hub port connects either directly to a device or to an external hub, which acts as a repeater to multiply port count. Up to five hub tiers can be cascaded between host and device, with each tier adding one hub-to-hub latency of approximately 200 ns. The maximum depth including the root hub is seven tiers, and the maximum total number of devices on a single USB bus is 127, each assigned a unique 7-bit address by the host during enumeration. When a device is plugged into a port, the hub detects the D+ or D− pull-up resistor in the device — D+ pull-up signals a Full-Speed or Hi-Speed device, D− pull-up signals a Low-Speed device — and notifies the host of a port connect event. The host then resets the port, causing the device to present its default device descriptor at address zero. The host reads the device descriptor, assigns a unique address using a Set_Address request, then reads configuration, interface, and endpoint descriptors to understand the device capabilities. This sequence, called enumeration, typically completes within 100–500 ms. Power distribution follows the same topology: each hub port supplies up to 500 mA at 5 V for USB 2.0 or 900 mA for USB 3.0 from its own power supply or from its upstream port if it is a bus-powered hub. Bus-powered hubs are limited to 500 mA total for all their downstream ports, making them unsuitable for power-hungry devices. Self-powered hubs draw their own supply from an external adapter, providing full per-port power regardless of upstream bus load.
How to wire usb connection diagram
- Map the USB topology Enumerate all USB hosts, hubs, and devices in the system using the operating system device manager or a USB tree viewer application. Identify which hub tier each device occupies to verify the five-tier maximum is not exceeded.
- Calculate power budget per port Sum the current requirements of all devices on each hub. Compare to hub port current limit. For bus-powered hubs, sum all device currents and verify total is below 500 mA. Add a self-powered hub if budget is exceeded.
- Verify cable segments Measure cable length for each segment in the daisy chain. Confirm total cable length between host and any device does not exceed 5 m per USB 2.0 segment or 3 m per USB 3.0 segment, multiplied by the number of hub stages.
- Check enumeration in device manager Open device manager and inspect USB devices for error codes. Code 43 indicates a device-reported error. Code 28 indicates a driver not installed. Code 10 indicates the device failed to start — these point to power, cable, or driver issues respectively.
- Use a protocol analyser for deep debugging Connect a USB protocol analyser between the host port and the device under test. Capture the enumeration sequence. Verify device descriptors are returned correctly and the host completes Set_Configuration without error.
Specifications
| Maximum devices per host | 127 (7-bit address space, addresses 1–127) |
|---|---|
| Maximum hub tier depth | 5 tiers between host root hub and device |
| USB 2.0 Hi-Speed frame period | 1 ms (1000 frames/second) |
| USB 3.0 SuperSpeed microframe | 125 µs (8000 microframes/second) |
Safety warnings
- Do not connect more than 500 mA total load across all ports of a bus-powered hub — overloading causes the upstream port protection to activate, disconnecting all devices on the hub.
- Avoid using generic USB hubs with no over-current protection — a fault in one port can collapse the VBUS supply for all other ports simultaneously.
- Keep USB cables away from fluorescent light ballasts and switch-mode power supply cables — conducted and radiated interference causes enumeration failures and data errors.
Tools needed
- USB protocol analyser (hardware or software) for enumeration descriptor capture
- USB power meter (VBUS voltage and current monitor) for port power budgeting
- Digital multimeter for cable and connection resistance checks
- USB hub with per-port power switching for controlled device testing
Common mistakes
- Using bus-powered hubs to connect high-current devices such as external hard drives, causing under-voltage and data corruption.
- Cascading more than five hub tiers between host and device, exceeding USB specification and causing unreliable enumeration.
- Plugging USB 3.0 devices into USB 2.0 ports and expecting SuperSpeed performance — the bus speed is limited by the lowest-capability link in the chain.
Troubleshooting
- Device not recognised on hub but works directly on host port
- Cause: Hub current limit exceeded or hub tier depth exceeds specification Fix: Calculate total hub port current consumption and compare to hub rating. Replace bus-powered hub with self-powered hub. Count hub tiers and reduce if more than five between host and device.
- USB SuperSpeed device enumerates at Hi-Speed only
- Cause: USB 3.0 cable or hub link failing SuperSpeed negotiation; device falls back to USB 2.0 Fix: Replace USB 3.0 cable with a verified USB 3.0 certified cable. Verify the hub is USB 3.0 rated. Test directly on a USB 3.0 root hub port bypassing any intermediate hubs.
- Multiple devices disconnect simultaneously
- Cause: VBUS voltage collapse on hub due to overloaded bus-powered hub port Fix: Monitor VBUS voltage on the hub with a USB power meter during the event. Reduce connected device current load or replace with a self-powered hub.
Frequently asked questions
How many devices can one USB host support?
The USB specification allows a maximum of 127 simultaneously connected devices per host controller, each identified by a unique 7-bit address (1 through 127, with address 0 reserved for enumeration). Modern hosts often have multiple host controllers, each supporting 127 devices independently. Practical limits are usually set by power budget and hub tier depth before address space is exhausted.
What is USB enumeration?
Enumeration is the process by which the host discovers and configures a newly connected USB device. The host resets the port, reads the device descriptor at address 0, assigns a unique address, then reads configuration and interface descriptors to determine the device class, endpoints, and power requirements. The operating system uses this information to load the appropriate driver and allocate resources.
What is the difference between bus-powered and self-powered hubs?
A bus-powered hub draws all its power from the upstream USB port, limiting total downstream port power to 500 mA for USB 2.0. A self-powered hub uses an external power adapter, providing full per-port current (500–900 mA each) regardless of upstream bus load. Self-powered hubs are essential for connecting devices with high power requirements such as external hard drives or charging mobile devices.
Why does my USB device work on some ports but not others?
Port capability varies: USB 2.0 ports cannot enumerate USB 3.0 SuperSpeed devices in SuperSpeed mode. Some ports may have lower power limits due to being behind bus-powered hubs. BIOS settings may disable specific ports. Test the device on a direct root hub port rather than a cascaded hub to rule out hub-related issues, then check if the device operates in USB 2.0 compatibility mode.
How does USB handle multiple devices on one bus simultaneously?
The host controller uses time-division multiplexing, scheduling transfers in 1 ms frames. Interrupt and isochronous transfers receive guaranteed bandwidth allocations each frame. Bulk transfers use remaining frame time in round-robin priority. Control transfers use a reserved portion of each frame. The hub acts as a transparent repeater — it does not arbitrate between devices but forwards all packets in both directions between host and the addressed device.
Sources and verification
Review status: Not independently reviewed. Automated topology checks confirm stored terminals and routes, not the correctness of manufacturer pin assignments, ratings, regional codes, or installation decisions. Verify those claims against the current primary documentation before use.
- IEC 61082-1:2014 — Rules for electrotechnical documents — International Electrotechnical Commission. Supports: General diagram, drawing, table, and reference-designation presentation conventions. Checked 2026-07-15.
- USB 2.0 Specification — USB Implementers Forum. Supports: USB 2.0 interface, cable, electrical, signal, protocol, and connector requirements. Checked 2026-07-15.
Related diagrams
- female usb pinout
- micro usb cable wiring diagram
- micro usb diagram
- micro usb pinout diagram
- mini usb wiring diagram
- usb 2.0 wiring diagram