- 4-port USB 3.0 self powered hub with robust 20W (5V, 4A) UL certified power adapter (US AC wall outlet plug options, 100-240V 50/60Hz)
- Compatible with most Windows 8.1, 8, 7, Vista, XP, Mac OS X, Linux (kernels 3.0 and later), and Unix systems
- Fully plug and play, no drivers required (individual devices / USB 3.0 host controller may require drivers), devices can be hot-plugged
- Features single VIA VL811+ hub chipset with the latest v9095 firmware for maximum compatibility and performance with most USB 3.0 host controllers along with additional BC1.2 smart charging on all 4 ports. This firmware also allows the hub to be a stand-alone (not connected to host computer) smart 4-port USB charger able to select the best charging mechanism for the attached device.
- Sleek piano black glossy finish with all 4 ports on one side to minimize cable clutter and maximize accessibility
- Individual LED status indicators for each USB port and USB over-current protection supporting up to 900mA per port (up to 1.5A for BC 1.2 devices)
- Supports USB 3.0 SuperSpeed transfer rates up to 5Gbps (640MBps – transfer rates are device and USB host controller dependent)
- Backwards compatible with USB 2.0 Hi-Speed devices (rates up to 480Mbps), and USB 1.1 Full/Low Speed devices (rates 12/1.5 Mbps)
- Mac OS X iPad Charging Error with iPads on BC 1.2 Charging Hubs
- Plugable USB 3.0 Hub Firmware History Mid-2014 Update
- Device Charging Rates
- Plugable USB 3.0 Hub Firmware Upgrades
- Plugable’s USB 3 Hubs and OS X
- VIA VL811 USB 3.0 Hub Firmware Upgrade
- OS X Mid-2012 MacBook USB and Graphics update
- The Windows RT and Surface USB Device Compatibility Story
- New USB 3.0 Support Built-In to Windows 8
- Windows 8 Consumer Preview Support
Expand USB connectivity by connecting up to four USB 3.0, 2.0, or 1.1 devices to any USB 2.0 or 3.0 capable desktop, laptop, or tablet computer. The hub supports USB 3.0 transfer rates up to 5Gbps (640MBps) to allow data to move quickly between devices, ideal for high-throughput devices such as USB hard drives, flash drives, and USB video adapters.
USB has become more than a way of connecting devices to a computer with plug and play ease and high performance, it has also become the method of choice to power and charge a range of battery-powered devices from headsets and controllers to phones and tablets. Some of those mobile devices have adopted proprietary mechanisms to draw more power than USB 3.0 was designed to allow, which has caused confusion about charging.
That is being solved by the Battery Charging (BC 1.2) Standard – when both the device and the hub/charger are BC Standard compliant, it can charge at a faster rate (up to 1.5A) in a standard way.
The Plugable USB3-HUB81X4 is among the first of USB 3.0 hubs that does everything existing USB hubs do, plus has support for the Battery Charging Standard (BC 1.2). So it’s a no-compromise solution for both gaining extra USB ports and for charging the newer generation of BC 1.2 compliant devices. Both charge and sync (CDP) and dedicated charging (DCP) are supported along with support for other proprietary charging signals when being used as a stand-alone charger if the phone or tablet also supports these modes.
- Microsoft Windows systems should install latest manufacturer USB 3.0 host controller drivers and Windows Updates for best results. Apple Mac OS X and Linux / Unix systems require latest operating system updates for best compatibility.
- Not recommended for use with older Texas Instruments, Fresco Logic, Etron, or Wistron USB 3.0 host controllers.
- This hub can act as a standalone charger and can charge phones and tablets as it has special charging functionality for charging iPads, iPhones, and other tablets and smartphone devices. It is also BC 1.1 / 1.2 compatible.
- Some devices such as the Apple SuperDrive look for Apple-specific signaling and will not work when connected through any USB hub.
- We do not recommended this hub for use with USB 3.0 PCI-e add-on cards for older Apple Mac Pro systems because of limitations in their software support for USB 3.0 hubs.
- 2.4Ghz wireless devices such as wireless keyboard/mouse receivers, Bluetooth and WiFi adapters, may not work in close proximity to USB 3.0 devices or hubs. Connecting wireless devices to a USB 2.0 port is recommended for best results.
USB ChargingBattery charging over USB has become a standard practice but the actual charging behavior of different devices is often unpredictable and sometimes disappointing. The devices themselves decide how much current to draw and manufacturers haven’t settled on a single standard. We constantly test our products with as many different devices as possible and publish the results so it’s easy to determine the charging behavior to expect from your device on each of our USB products. These are the results for the devices we’ve tested on this charger so far.
For hubs, "Hosted" means the hub is attached to a host computer that is powered on. "Unhosted" means just the opposite, that the hub isn't attached to a host computer, or that the host computer is turned off. This doesn't apply to stand-alone chargers that only plug in to a wall outlet.
The "Estimated Charging Time" column is the minimum amount of time that the device would take to charge if it was fully drained. This is just an estimate! We provided this to give a general idea of the expected charge time. If this column is blank for a device, that means that the device indicated that it wasn't charging. In this case, even if the device is drawing power, it will likely either "tread water" keeping the battery at a constant level, or slowly lose ground.
Q: Do I need a firmware update for my hub?
A: See our firmware update page here.
Q: Is the AC power adapter required?
A: Yes. The hub is not capable of running in bus power mode (from the host PC).
Q: What do the green LED lights indicate?
A: There is a green led for each of the downstream USB ports on the hub. The LEDs turn on when a USB device is connected and recognized by the operating system. These lights may turn off even though a device is connected when the host computer operating system puts the device to sleep to conserve power. There is no master light to indicate the hub is receiving power.
Q: Can the hub charge and sync iPods/iPads and other smartphones?
A: Only Apple devices that use the Lightning connector support BC 1.2 charge and sync. Apple 30-pin dock connector devices that require special signaling such as the original iPad go into data only (sync) mode when attached to this hub. Most Android and Windows phones and tablets support charge and sync functionality.
Q: Can the hub support 4 devices which charge at the full BC 1.2 CDP 1.5A rate?
A: Technically no (if including four 1.5A BC 1.2 devices), the supplied power adapter delivers 4A of available current across all USB ports which leaves us 2A short (4 * 1.5A = 6A). If using four 900mA non BC 1.2 devices the hub can easily power them with power left to spare (4 * 900mA = 3.6A) . In the real world however, it will be hard to find 4 USB devices that will use the full 900mA+. So you can be confident that you can use all the 4 available ports at the same time.
Q: Does the power supply switch for different regions or is it tied to US voltage and frequency?
A: The switching power adapter with our 4-port hub supports inputs of 100-240V at 50/60 Hz. Output is at 5V 4A.
Q: Is this hub a good match for my Raspberry Pi?
A: Because the Raspberry Pi is a USB 2.0 device and can’t take advantage of USB 3.0 functionality as well as mixed results from users, we do not recommend this hub for use the Raspberry Pi. The hub we do recommend is our 7 port USB 2.0 hub
Here’s a link with more details: A USB Hub that Works Well with the Raspberry Pi.
In The Box
USB 3.0 4-port Hub, 5V 4A 20W UL certified AC power adapter with 6 foot cord and 3 foot USB 3.0 cable.
Where to Buy
Either we got no JSON from the API. Or the basenode-parameter is not ok.
Switch on the Debugmode of the Plugin!
Switch to gutenberg-Blocks!
There the JSON Content Importer Block gives an easier way to use the JSON-APIs.
Or: Switch on the Debugmode by adding "debugmode=10" in the Shortcode.
If all is without success: Open ticket at wordpress.org please