HMI panels in this class document FAT32 first, some newer unified families also take NTFS and exFAT, and a FAT32 file stops at 4,294,967,295 bytes. Format one stick FAT32, test it plugged straight into the panel port on a cable under the 5 m USB 2.0 limit, then buy spares. The shared switch and the long cable cause most of the failures blamed on drives.
A panel that logs batches, trends or alarms asks one narrow question of a USB stick: will this panel mount this drive and write to it? The answer rarely comes from the price tag or the color of the shell. It comes from three things you can check in an afternoon: the file system on the drive, the length and switching of the cable path between the drive and the panel, and the storage list in the exact panel model's documentation. This article gives the numbers for all three, a test order that separates a bad stick from a bad path, and a worked example that shows when the FAT32 file-size ceiling ends a logging job on schedule rather than as a surprise.
Which USB flash drives work with an HMI panel?
Format a drive FAT32, plug it straight into the panel's host port, and run one real export before you buy spares, because FAT32 is the file system small panel documentation most often names, and the cable and switch in the path cause more failures than the drive's brand does.
Documentation for panels in this class names FAT32 first, and at least one unified-panel family documents FAT32, NTFS and exFAT side by side. The stories of four identical sticks where only two mount are real, and the cause is usually the path, the format or the model's media list, all of which the test below separates in minutes. Start from FAT32 as the default, treat the first stick that passes the direct port test as your reference, and buy spares only in that exact capacity and format.
What file system should the drive use?
Use FAT32 unless the exact panel's documentation says otherwise, because small industrial panels most commonly document FAT32, some newer unified panel families also list NTFS and exFAT, and no FAT32 file can ever pass 4,294,967,295 bytes.
FAT32 is the common denominator, and the documented procedure for formatting a thumb device for HMI software says exactly that: format the stick FAT32. A FAT32 stick then opens on any PC at the end of a shift. Newer unified panel families add NTFS and exFAT to the supported list, so read the exact model's storage documentation before reformatting anything.
The number that decides single-file jobs is the FAT32 ceiling. The directory entry stores the file size in a 32-bit field, so no file can pass 4,294,967,295 bytes, beside the much higher NTFS and exFAT limits. The ceiling applies per file, not per stick, which is why a logger that appends to one growing CSV dies partway through while the same job with one file per day runs for years on the same stick.
Is there a capacity or brand limit on HMI panel USB drives?
The exact panel model's documentation is the only capacity limit worth quoting, because manufacturers publish tested media in the model list where they publish it at all, and the shop-floor story that smaller and cheaper sticks mount more often is anecdote, not a specification you can buy against.
Field reports cut both ways. Sticks of 2 GB have run for years at one plant with a dozen in service, while another site watched two of four identical new sticks fail to mount. Both patterns fit the same two causes, variance in stick quality and faults in the path, and neither report is something to buy against. The workable rule is to keep the stick that passes the direct port test below as your reference and buy spares only in its exact capacity and format. For capture jobs, commit to 8 to 32 GB formatted FAT32: it holds years of logs at the rates in the example, and a PC's format dialog stops offering FAT32 above 32 GB, so every spare stays reformattable without special tools.
What does each symptom point to?
Match the symptom to the part of the path before buying anything: a drive that mounts on the PC but not the panel points at the cable or the switch, a drive nothing mounts points at formatting, and a mounted drive with no new files points at the logging setup.
- Mounts on the PC, never on the panel. A path fault: cable past the USB 2.0 limit, a switch still held by the PC, or a format the model's documentation does not list. Run the direct port test.
- Mounts on one panel, fails on another. Different cable lengths or switch states behind each panel. Carry the stick and a short cable between them before judging either panel.
- No computer mounts it. Damaged file system or partition table. Back the files up on a PC that still reads the stick, reformat FAT32 and retest.
- Mounts, then vanishes mid-transfer. Marginal signal on a long cable or a worn switch contact. Shorten the run and retest at the port.
- Mounts, but no new files appear. The stick is fine; check the project's logging or export configuration and the destination path.
A stick that mounts is not proof the logger writes to it, so run one real export before declaring the media healthy. When a panel refuses to mount anything at all, the checks in the USB drive not recognized test sequence take the port side apart step by step.
Does a shared USB switch or long cable cause the fault?
Yes: USB 2.0 high speed, at 480 Mb/s, is specified for cable runs up to 5 m, USB 3.2 Gen 1 cables stay at 2 to 3 m, and a shared switch adds a second host that can hold the drive when the panel needs it.
A sharing switch hands one device to one host at a time. If the PC side holds the stick, the panel sees nothing at that moment, and a switch flip during a write can leave the file system damaged, which then looks exactly like a rejected drive. Two habits remove the whole class of fault: eject the stick cleanly on the PC before moving the switch, and test the panel with the stick plugged straight into its port, no switch and no hub, before blaming the media.
Cable length has published numbers, one per USB generation, so measure the actual run before blaming the stick. A run out to a locked cabinet that sits past the USB 2.0 limit produces intermittent mounting on its own. Keep the whole run from panel port to stick inside the limit for the generation in use, or fit an active extension rated for that same generation.
How do I test a stick on the panel before buying spares?
Test one known-good stick on the shortest path first, because if a drive formats FAT32, ejects cleanly from the PC, and mounts when plugged straight into the panel's host port, the media is fine and the fault lives in the switch, the long cable or the project's logging settings.
- Write down the exact panel model, the USB port used, the stick's capacity and file system, and the cable path in metres.
- Back the stick up on a PC and eject it cleanly. If it carries a panel project backup, confirm how that backup restores first, because the USB restore without programming software procedure is the fallback when the programming laptop is out of reach.
- Format the stick FAT32, or the file system the model's documentation names, with the default allocation size.
- Plug it straight into the panel's host port: shortest cable in the drawer, no hub, no switch.
- Run one real export with a test record, remove the stick by the panel's own eject procedure, and open the file on the PC. If a project backup file will not open, the file-type filter fix is the usual reason.
- Rebuild the installed path one piece at a time, switch first, then the long cable, running an export at each step. The step that breaks the mount is the fault, and the stick goes back in the drawer as the known-good reference.
If the panel's menus offer no port-configuration screen, that is normal for this class: the project software assigns the port its role, transfer or logging, and port questions go to the model documentation first and the manufacturer's support channel second.
Recommendation: format one stick FAT32, plug it straight into the panel's host port on the shortest cable in the drawer, run one real export and open the file on the PC, and order spares only in that stick's exact capacity and format. If the cabinet run is longer than the USB 2.0 limit, shorten the run or fit an active extension before blaming a single drive.
What does an example decision look like with real numbers?
A trend logger appending 40 MB per day to one CSV hits the FAT32 file ceiling of 4,294,967,295 bytes in about 102 days, so that job needs daily files, while a 16 GB stick formatted FAT32 holds about 400 daily files under the same per-file limit.
Scenario: an autoclave in a restricted area logs to a stick locked in a cabinet, 8 m of USB 2.0 cable from the panel's host port, and the project appends every reading to one CSV at 40 MB per day. Run the two numbers.
The file ceiling. FAT32 stores file sizes in a 32-bit field, so the CSV stops accepting writes at 4,294,967,295 bytes. One day of data is 40 × 1,048,576 = 41,943,040 bytes, and 4,294,967,295 ÷ 41,943,040 ≈ 102.4, so the single-file job hits the ceiling on about day 102 while the stick still shows free space. One file per day instead leaves each file at about 41 MB, a hundred times under the ceiling, and a 16 GB stick, 16,384 MB, holds 16,384 ÷ 41 ≈ 400 daily files before the oldest roll off or the stick swaps out. The oldest-file rollover check then matters, because a full stick is a different fault from a full file.
The cable. The 8 m run sits 3 m past the 5 m USB 2.0 limit, so intermittent mounting is expected on that path alone. Bring the stick inside 5 m of the panel or fit an active USB 2.0-rated extension, and retest at the port.
| Item | Number | What it decides |
|---|---|---|
| FAT32 file ceiling | 4,294,967,295 bytes | Single-file logging stops near day 102 |
| One day of data | 41,943,040 bytes (40 MB) | Daily files sit 100 times under the ceiling |
| Stick | 16 GB = 16,384 MB | About 400 daily files per pass |
| Cable run | 8 m vs the 5 m limit | Intermittent mounting until the run is shortened |
The decision: FAT32, one file per day, a 16 GB stick and a run inside the 5 m limit. The capture runs past a year per pass, every spare reformats in any PC, and nothing in the setup depends on stick luck.
Should the panel send the data instead of a thumb drive?
If the area rule bans removable media, have the panel send the records by its FTP or email function and drop the stick entirely, but run the network path alongside the existing capture and check file content and timestamps before you retire the working method.
The functions to look for are FTP and email in the model's communication documentation: the panel sends the files to a server or a mailbox, and no removable media crosses the restricted area. A common configured job mails the day's trend files and the alarm log shortly after midnight, so the previous day's data is off the floor before the first shift starts. Check that the exact model supports the function and that the receiving system can hold the files, then compare the two paths record by record for a week. Keep the stick as the fallback until a full week of network records checks out, and retire the media only then.
Questions
If the panel documentation lists both FAT32 and exFAT, which should I format?
Format exFAT only when a single export file will grow past 4,294,967,295 bytes, because exFAT removes the FAT32 per-file ceiling. For every other job stay on FAT32: it is the file system this class of documentation names first, it opens on any PC at the end of a shift, and a spare stick formatted FAT32 behaves the same in every panel on the floor.
Can a USB hub share one stick between the panel and the PC?
No. A hub leaves both hosts seeing the same device, and each will try to own it, which produces the intermittent recognition you are already chasing. A sharing switch is the arrangement that works, because it hands the stick to one host at a time: eject cleanly on the PC, move the switch, then let the panel mount.
Do I need a fast USB 3.x stick for log capture?
No. USB 2.0 high speed is rated 480 Mb/s, which works out to tens of MB/s in practice, while the example's full day of trend data is 41,943,040 bytes, about 40 MB. A USB 3.x stick in a 2.0-class port runs at 2.0 speed, so buy spares on capacity and build quality, and spend nothing extra for speed.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.