When an HMI panel does nothing when you plug in a thumb drive, suspect the drive first. Panels read only the file systems their manuals list, and they reject some drive controllers outright. Format a small spare drive FAT32, check the panel's transfer screen sees it, and only then chase the project, the port or the naming.
You plug a thumb drive into the HMI panel and nothing happens: no media icon, no transfer screen, no error. Before you re-export the project or suspect the port, test the media. A panel reads only the file systems its manual lists, and it rejects some drive controllers outright even when the same drive works in a laptop. Some drives simply never work in some panels, which is why some panel vendors sell a drive of their own for this. The practice that ends the argument is a small spare drive formatted FAT32, checked once on the panel's own transfer screen, and kept with that panel's spares. This page gives the symptoms to tell apart, the format numbers that matter, and the order to check things in when a known-good drive still fails.
Start with the drive, not the project
A USB plug fitting the panel's host port says nothing about what is behind the plug. Flash drives differ in their controllers, and two drives from the same shop shelf can behave differently in the same panel. When the panel stays silent, the media path is the first suspect, the port the second, and the project the last, because the project is not involved until a transfer screen opens.
Make the first move physical. Pull the unrecognized drive, check it for damage, and set it aside unchanged, since reformatting it now destroys the evidence support may ask for later. Then take a second drive that has already worked on a panel of the same model. If none exists, format a small spare as FAT32 and test it at the bench before the field visit, because cycling through unknown drives at a live machine wastes trips.
Symptoms and what each points to
Match what the panel does to the fault before you touch anything:
- Nothing at all on insert. Wrong file system for that panel, or a drive controller the panel's firmware never recognizes. The most common cause, and the one a spare FAT32 drive clears first.
- Works on the laptop, dead in the panel. File system mismatch. The laptop reads exFAT and NTFS happily; a panel whose manual lists FAT32 only does not.
- Media icon appears, transfer screen lists no file. The drive is accepted, so naming or folder placement is the miss. Match the manual's expected name and location exactly.
- Transfer starts, then stops partway. Project and firmware are now in play. Check the panel's firmware revision before you rebuild the export.
- Every drive silent and the panel otherwise odd. Port damage or a panel fault. Stop testing drives and check the panel itself.
Format the drive so the panel can read it
File system is the first documented gate, and the panel manual prints the list on its storage page. One widely deployed current panel family documents FAT32, NTFS and exFAT on its USB ports. Older graphic and text panels often document FAT32 alone, and panels old enough to document FAT16 top out at 2 GB volumes, because FAT16 addresses 65,536 clusters and 65,536 × 32 KiB = 2,147,483,648 bytes. FAT32 is the common denominator, which is why the shop spare is a FAT32 drive.
FAT32 carries two numbers worth knowing. A single file cannot exceed 4,294,967,295 bytes, the largest value a 32-bit file-size field stores, so a bigger export must be split or carried on a file system the manual lists for large files. And Windows' formatting dialog stops offering FAT32 on volumes larger than 32 GB, so the practical spare is 16 GB or smaller, where the dialog does the whole job. Size the spare under both limits and format questions disappear.
Prove the panel sees the drive before you load anything
Work the checks in this order:
- Format the 16 GB spare FAT32 on your PC.
- Copy the project export onto it under the exact file name the manual's transfer procedure expects, in the folder it names.
- Insert the drive into the panel's USB host port and wait a few seconds for the panel's media response.
- Open the panel's transfer or backup screen and check that the drive and the file are both listed. This is the gate: past it, every fault is a project fault, not a media fault.
- Start the copy and wait for the completion message before pulling the drive. Interrupting power mid-write is one way a panel loses its stored project.
Run the load and the verification with the machine in the site's approved safe state, since a new project can drive outputs the moment its screens go live. Test writes against the PLC link before motion is enabled, and when the archive has to come off the panel instead, getting the project from the panel back to your PC has its own procedure.
Example: a 16 GB spare drive on a field panel
Scenario: a packaging line panel is two states away, a new screen set has to go on today, and the current archive has to come off on the same visit. You format a 16 GB spare at the office; the dialog offers FAT32 directly because its FAT32 option ends at 32 GB volumes. The project export is 12 MB, far inside FAT32's single-file cap: 4,294,967,295 bytes ÷ 12,000,000 bytes ≈ 358, so the cap is about 358 times this export.
You copy the file across under the manual's expected name, walk up to the panel, and insert the drive. The transfer screen lists the drive and the file within seconds, the copy runs to its completion message, and the archive comes off on the same drive. Media cleared, project loaded, archive in hand, one trip. Had the screen stayed dark at the listing step, the next test is a second known-good drive: if it lists, the first drive was the fault; if it also stays silent, the port or the panel is, and the visit becomes a support call with the model number and the behavior written down.
When a known-good drive still fails
Work down this list:
- Port. Look into the connector for a bent or folded tongue and for debris, and never force a drive that meets resistance.
- Second known-good drive. A drive known good on a panel of the same model splits the fault: if it lists, blame the first drive; if it stays silent too, the panel side is the suspect.
- Panel health. Check that the panel boots to its normal screens and that its power wiring is sound before condemning the port.
- Naming and firmware. If the drive lists but the export is missing or a transfer aborts, the panel's firmware revision is the next check. A transfer that stops for a missing firmware file is its own failure with its own fix.
When two known-good drives produce no response and the port looks clean, stop experimenting at the machine. Take the model number and the exact observed behavior to the panel vendor's support channel.
Recommendation: Keep one USB drive of 16 GB or smaller, formatted FAT32, with the spares for each panel model you service. Format it once, check it on that model's transfer screen, and label it for the model. When a field transfer comes up, that drive is the first thing you plug in. Reformat or swap media only after the known-good drive also fails, because the fault has then moved off the drive, and the record of two silent known-good drives is exactly what support will ask for.
Questions
Why does a thumb drive that works in a laptop fail in the panel?
A laptop's operating system reads a long list of file systems and tolerates many drive controllers. A panel's transfer firmware reads the short list its manual prints, often FAT32 alone and sometimes NTFS or exFAT as well. A drive formatted exFAT mounts on the laptop and stays invisible to a panel that documents FAT32 only. Format the spare to the panel's documented list and check it once on the transfer screen.
What if a project export grows past FAT32's single-file limit?
FAT32 cannot hold a single file larger than 4,294,967,295 bytes, so an oversized export fails no matter how empty the drive is. Split the export into smaller files if the panel's procedure accepts them, or move that one file on a file system the manual lists for large files, such as NTFS on panels that document it.
The panel lists the drive but not the project file. What now?
Media is cleared at that point, so the miss is in naming or placement. Check the manual's transfer page for the folder it names and the exact file name and extension, then re-copy to match. Some transfer procedures expect the file in a specific folder, and some are particular about names. If the manual prints no path, ask the panel vendor for the documented transfer procedure instead of guessing names.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.