How-to
Sharing One USB Host Port With a Powered Hub on an HMI
Short answer
Yes: a four-port USB hub on the CMT-FHDX-820's single host port carries the touchscreen interface and the 32 GB DataLog stick together. Use an independently powered hub — two devices budgeted at 500 mA each draw 5.0 W, more than the 4.5 W a bus-powered hub shares — then commission touch and logging one at a time through the hub before accepting the shared link.
On this page
Yes. A four-port hub on the panel's single host USB port carries the touchscreen interface and the 32 GB DataLog stick at the same time: the Weintek host interface is documented for project upload and download and for data storage, and a hub behind that port is a supported way to add sockets. Commit to one decision before anything is bought: the hub is independently powered. Budgeted at their USB class maximum, the two devices draw 5.0 W against the 4.5 W a bus-powered hub can share, so the powered hub is the arrangement that closes the budget, not merely the cautious one. Then commission touch first, storage second, and accept the link only when both run together.
What the hub adds — and what it does not #
The Weintek CMT-FHDX-820 in this application exposes one host USB port, and the question is whether four sockets behind it are real. They are, with one limit: a hub expands one port into a shared branch; it does not create independent host ports. Touch input and the memory stick both travel the single upstream cable, so pulling that cable or dropping hub power removes both functions in the same instant. Four sockets for two devices settles the count question on its own, with two to spare. What remains is electrical — who supplies the current — plus one cabling rule about the monitor's picture.
Why the hub needs its own supply #
A bus-powered hub runs its own electronics and everything plugged into it from the panel's upstream 5 V supply, and that supply is typically 4.5 W shared across all ports — 0.9 A at 5 V. On the other side of the ledger, USB 2.0 permits a high-power device up to 500 mA from a port, which is 2.5 W at 5 V, and that is the number to budget for a device whose documented draw is not in front of you.
Budget for this pair, both devices at the class maximum:
- touchscreen interface: 500 mA
- 32 GB memory stick: 500 mA
- pair total: 0.5 A + 0.5 A = 1.0 A, and 1.0 A × 5 V = 5.0 W
- branch budget: 4.5 W
- shortfall: 5.0 W − 4.5 W = 0.5 W, before the hub's own electronics take anything
The decision follows from the arithmetic: do not commission this pair on a bus-powered hub. A self-powered hub closes it with room. The documented example — a 12 V, 5 A supply with 36 W of port capacity — runs the 5.0 W pair at 14 percent (5.0 W ÷ 36 W = 0.139), and a hub supply capped at 3.0 A total leaves the 1.0 A pair 2.0 A of headroom. Self-powered sockets also carry a higher rating: 500 mA each on USB 2.0, 900 mA each where the hub is built to the USB 3.x rating.
One warning: a hub with a power socket is not independently powered until that supply is connected and switched on. An unconnected supply lets the hub fall back onto the panel, and the bus-power arithmetic above applies again.
Keep the video cable off the hub #
A touchscreen monitor is two signal paths in one housing: a video path to the display input and a USB path for the touch digitizer. The hub belongs to the second path only. Route video on its own cable from the panel's display output, and route the monitor's USB touch cable to a hub socket — the hub is never a substitute for the video connection. Keep the diagnosis split the same way: a live picture proves nothing about touch, which is the exact split behind why HDMI video works while USB touch does not. Where the video link is an adapter rather than a native cable, the same one-function-at-a-time discipline applies, as shown in commissioning USB-VGA video and touch for a native HMI. If the screen for the position beside the controller is still to be chosen, compare industrial touchscreen monitors for that spot.
Commission one device at a time #
Make every change with the machine in a safe state: from the moment the upstream cable leaves the panel, the operator has no touch input, and an interrupted write can damage the stick's file system.
- Collect the governing numbers: the hub supply's rating and each device's documented draw, budgeting the USB class maximum for anything without a stated draw.
- Connect and switch on the hub's external supply first, and confirm the hub is alive before anything upstream.
- Connect the hub's upstream port to the panel's host port.
- Plug the monitor's USB touch cable into a downstream socket, leave video on its own cable, and work the real screen objects until touch responds on every one the operator will use.
- Insert the 32 GB stick into a second socket and confirm the panel recognizes the storage before touching the DataLog configuration.
- Start the DataLog with both devices present and force test records by triggering the conditions that write a row.
- While logging runs, keep operating the screen: touch must stay responsive and the log must gain rows with advancing timestamps.
- Restart the panel once with everything connected, then repeat steps 6 and 7 — boot-time enumeration is part of acceptance, not an afterthought.
- Stop recording and use the panel's documented removal step before pulling the stick; never disconnect storage during a write.
When the shared branch drops out #
Symptoms after commissioning separate cleanly along the same lines:
| Symptom on the machine | First check | Why it points there |
|---|---|---|
| Picture present, touch dead | Touch USB cable, hub supply | Video and touch are separate paths |
| Touch alive, no log file | Stick recognition, DataLog destination | Input and storage are separate functions |
| Touch and storage die together | Hub supply, upstream cable | Both sit on the one shared branch |
| Touch alive, values stale | Tag address, controller link | Process data never travels this hub |
A device that works plugged straight into the panel but fails through the hub convicts the hub, its supply or its cable — swap those, not the panel. Stale values are never a hub symptom on this arrangement: the branch carries input and storage only, while process values arrive over the controller link, so a frozen number is a tag or driver fault with its own path to chase.
Questions asked
Can a bus-powered hub ever work for these two devices?
Only with documented draws in hand. If the touch interface and the stick are each documented at 200 mA, the pair needs 0.2 A + 0.2 A = 0.4 A, which is 2.0 W at 5 V — inside what a bus-powered branch shares, leaving 2.5 W for the hub's own electronics. Without those numbers on paper, use the powered hub.
How does the panel tell two USB drives apart behind one hub?
EasyBuilder Pro, Weintek's engineering software, lets a project designate which physical drive is "USB disk 1" and which is "USB disk 2" when a hub presents more than one storage device. With a single stick and a touch interface there is nothing to designate; the feature matters the day a second drive joins the branch.
Is a 32 GB stick within what the host port accepts?
The panel's documented removable-storage support sets the ceiling, not the hub — the hub is electrically transparent and adds no capacity limit of its own. Where a maximum size or a required format is documented for the port, that governs, and the insertion test during commissioning proves the actual stick on the actual port.
Can a printer share the same hub?
Yes — the host interface is documented to connect printers directly, so a printer can take a third downstream socket. Add its documented draw to the branch budget the same way: a 500 mA printer beside the touch pair brings the branch to 1.5 A, still half of a 3.0 A hub supply.