Quick Answer / Summary: Programmable hubs (Ykush, Acroname class): per-port VBUS switching and data-line control via USB command interface (CLI/API/SDK) – scripts power-cycle devices under test, gate data lines, read per-port current on metered builds. Lab duty: automated test fixtures, DUT power cycling, CI device farms. Price $60-300 per the class. Consumer hubs can’t do this – the class boundary is the SDK.
The programmable hub is the lab class: per-port power and data switching under script control – the test bench’s ability to power-cycle a device under test without touching the rack. This guide covers the class the consumer market never sees.
What ‘Programmable’ Actually Means
The class’s definition: a command interface over the hub’s controller – per-port power on/off (VBUS switching, the same cut the manual switches perform, now scripted), per-port data gating (the port electrically isolated from data – the device invisible to the host without losing power), and on metered builds, per-port current telemetry (the device’s draw read in mA over the API). The interfaces: CLI tools (the test script shells out), Python/C SDKs (the fixture integrates), some builds add network control (the rack managed remotely). The class boundary: consumer hubs’ switches are manual; the programmable class’s switches answer to software – the SDK’s presence is the definition, and the price delta ($60-300 versus $25) prices it.
The SDK Test
‘Programmable’ listings without an SDK/CLI download are consumer hubs in lab clothing. The SDK’s existence – downloadable, documented, versioned – is the class’s entrance exam.
The Lab Duties
DUT power cycling: the device under test (phone, board, dongle) power-cycled by the test script between runs – the fixture’s core loop, thousands of cycles without a hand on the rack. Device farms: the CI system’s phone farm – devices reset remotely, ports gated to isolate failures. Test-bench discipline: metered builds log each device’s current draw across the test (the regression the current curve catches). Embedded manufacturing: fixture control of board programming ports – power, flash, power-off, next. The class’s value: the bench’s automation percentage – every manual power-cycle the script absorbs is a labor-hour saved and a variance removed.
The Cycle-Count Argument
A test suite cycling a DUT 200 times nightly: manual switching is 200 rack touches; the scripted hub is zero. The cycle count prices the class on one fixture.
The Buying Lines for the Lab
The lines: SDK quality (documented, maintained, versioned – the entrance exam again), switching class (VBUS only, or data-gating too – the isolation duty needs the latter), current telemetry (metered builds for the draw-logging duty), port count and per-port ratings (the DUT population’s amps), and the stack support (Linux CLI for CI runners – the driver story that consumer silicon fails). The industrial cousins: DIN-rail programmable hubs with wide-temperature ratings (the plant-floor class). The verification: the SDK’s demo script cycles every port under observation – the class’s acceptance test is the script itself.
The CI Runner Line
The CI’s Linux runner needs the hub’s CLI to exist there – driver support for headless Linux is the lab class’s silent spec. Consumer silicon fails it; the lab class publishes it.
Programmable Hub Classes
| Class | Switching | Telemetry | Price | Duty |
|---|---|---|---|---|
| Entry programmable | VBUS per port | No | $60-90 | Fixtures, hobby labs |
| Metered | VBUS + data gate | Per-port mA | $100-180 | Test benches, draw logging |
| Multi-TT managed | Full control | Yes | $180-300 | Device farms |
| Industrial DIN | VBUS, wide temp | Varies | $150-400 | Plant fixtures |
Real-World Application Scenarios
A firmware team’s fixture cycles test boards 500 times nightly – the scripted hub absorbed 500 rack touches per run. A device farm’s CI resets flaky phones remotely; the metered log caught the regression that drained batteries 30% faster. A manufacturing line’s programming fixture runs power-flash-verify on every board – the class’s industrial duty.
Recommended Internal Resources
(1) Product cluster – https://zh-zong.com/productlist/ (anchor: programmable and industrial hub classes, SDK-documented); (2) FAQ – https://zh-zong.com/faq/ (anchor: SDK, switching and telemetry questions); (3) Contact – https://zh-zong.com/contact/ (anchor: describe the fixture, get the class recommendation).
- programmable and industrial hub classes, SDK-documented
- SDK, switching and telemetry questions
- describe the fixture, get the class recommendation
Related Reading in This Series
- 4-Port USB 3.2 Hub: Gen 1 vs Gen 2 and What the Names Change
- Hub Micro USB: The Micro-B Legacy Port Multiplier, Mapped
- USB Hub Mounting: Fixed Installations, from Desk Clamps to DIN Rails
Frequently Asked Questions (FAQ)
Q: What makes a hub ‘programmable’?
A: A command interface: CLI/API/SDK controlling per-port power and data switching. Consumer hubs’ switches are manual – the SDK is the class boundary.
Q: Can I power-cycle devices under test automatically?
A: Yes – the class’s flagship duty: the script cuts and restores VBUS per port. Metered builds log the current draw across every cycle.
Q: Why do these hubs cost $100+?
A: The controller’s command firmware, the SDK’s maintenance, and the switching silicon’s ratings. The cycle-count arithmetic pays it back on any automated bench.