Troubleshooting
Why an HMI Fails USB Transfer From a USB 1.0 PC
Short answer
The panel never receives the project because Weintek terminals expose a USB 2.0 client for direct download, and a PC with only USB 1.0 falls outside that boundary. Load the compiled xob file from a FAT32 pen drive on the panel's USB host port, from SD card where fitted, or over Ethernet, and leave the DIP switches alone: boot loader mode updates firmware, it does not load projects.
On this page
- The boundary is the controller generation
- Why the pen drive works when the cable does not
- Fixes that cannot work
- Read the symptom before you act
- Load the project from a pen drive or SD card
- Working the transfer time for a 32 MB xob package from a USB 1.0 PC
- Ethernet for routine programming
- Leave the DIP switches out of boot loader mode
- Confirm the load before you call it done
- Questions asked
The download never starts because of the USB controller generation inside the PC, not the cable, not Windows XP, and not a setting in the engineering tool. Weintek operator terminals present a USB 2.0 client interface for direct project download, so a PC whose controllers are all USB 1.0 cannot carry the xob file across that link at all. Compile the project to an xob file, copy it to a FAT32 pen drive, and load it from the terminal's USB host port — or from SD card where the model has a reader — or use the Ethernet port, the dependable path for routine programming. Leave the DIP switches alone: boot loader mode updates panel firmware and has nothing to do with application download.
The boundary is the controller generation #
Weintek documents the direct PC connection as the terminal's USB 2.0 client joined to the PC's USB interface, and the compatibility line for that link is USB 2.0 only. A USB 1.0 controller sits outside the boundary, and no software change moves it: the controller is hardware on the board. A connector that fits proves only that the plug is the right shape.
Windows XP is not the deciding condition. Machines of that era often shipped with USB 1.x controllers, and some boards mixed generations across ports, so read the controller behind the specific port you use, in the PC's device information under the USB controllers, before judging any port by its looks. Check each port separately; one USB 2.0 controller anywhere on the machine still supports a direct download from the ports it serves.
Why the pen drive works when the cable does not #
The panel's USB host port is a host: it controls storage, reading a pen drive the way a PC reads one. The PC is also a host. Direct programming uses the panel's other USB role, its client port, with the PC acting as host, and that is the path the USB 2.0 requirement lands on. Loading from a pen drive never crosses the PC's controllers, which is exactly why the panel can read a project from storage while the cable transfer from the same PC refuses to start.
Do not bridge the two host ports with an A-plug to A-plug cable. Two hosts have no device between them and nothing to negotiate, and the connection is not a compliant USB arrangement in the first place.
Fixes that cannot work #
- Swapping USB cables. A good cable cannot change the controller generation; a damaged cable would misbehave with other devices too.
- Reinstalling the engineering software. Software cannot add a controller the board does not have.
- Changing Windows XP settings or service packs. Operating-system settings leave the hardware generation untouched.
- Setting the DIP switches to boot loader mode. That is the firmware maintenance path, not a project loader.
- Host-to-host cabling. It pairs two hosts with no download path between them.
Not every failed USB download is a PC-generation problem. A download that starts and then leaves the touch layer dead is a panel-side fault with its own causes, which is the subject of why HMI USB downloads fail and touch stops responding.
Read the symptom before you act #
| Symptom | Real cause | First move |
|---|---|---|
| Cable download never starts from the old PC | PC controller is USB 1.x; the terminal's client link is USB 2.0 | Switch to pen drive, SD card or Ethernet |
| Pen drive loads fine but the cable never does | Host storage path versus client programming path | Stop troubleshooting the cable |
| Panel sits in a loader screen after a DIP change | Boot loader mode was entered | Restore the switches and restart before anything else |
| Panel ignores the pen drive | Wrong port, wrong format or wrong folder layout | Check the host port, FAT32 and the manual's layout |
Load the project from a pen drive or SD card #
- Compile or export the application as an xob file in EasyBuilder8000.
- Format a Hi-Speed USB 2.0 pen drive, 4 to 16 GB, as FAT32, the file system these terminals read and write.
- Copy the xob to the drive following the folder layout in the EasyBuilder8000 User's Manual, renaming nothing.
- Eject the drive, then re-read it on the PC and confirm the xob carries a real size. A 0-byte file means the export or the copy failed before the panel ever saw it; MT6070iH upload errors and 0-byte XOB files start at that same check.
- Insert the drive into the panel's USB host port, or the card into the fitted SD reader where the model has one.
- Run the panel's documented download function with the DIP switches in their normal positions.
- Let the load finish and the panel restart before removing the media.
If the panel does not recognize the drive, check three things in order: you used the host port, the drive still re-reads on the PC, and the layout matches the manual. Rebuilding the application will not fix media the panel cannot mount.
Working the transfer time for a 32 MB xob package from a USB 1.0 PC #
Inputs:
- Compiled package: 32 MB, an illustrative mid-size screen set — an example input, not a panel specification.
- PC controllers: USB 1.x, 12 Mbit/s full-speed signalling, with no other ports.
- Terminal client link: USB 2.0, 480 Mbit/s High-Speed signalling, the documented requirement.
- Ethernet link used in this example: 100 Mbit/s negotiated.
The rule in words: wire time equals the file's bit count divided by the link's bit rate, and protocol overhead only adds to the result, so the quotient is a floor.
The arithmetic:
- 32 MB × 8 bit/byte = 256 Mbit.
- Ethernet at 100 Mbit/s: 256 Mbit ÷ 100 Mbit/s = 2.56 s.
- USB 2.0 at 480 Mbit/s: 256 Mbit ÷ 480 Mbit/s = 0.53 s.
- USB 1.x at 12 Mbit/s: 256 Mbit ÷ 12 Mbit/s ≈ 21 s — and irrelevant, because the terminal's USB 2.0 client never comes up behind a 1.x controller. The honest figure for the cable path is not 21 seconds; it is never.
Decision: file size is not what stops this transfer, so no smaller project rescues the cable. The moment every controller on the PC reads USB 1.x, direct USB is out for a small project as surely as a large one. Use Ethernet when the panel has the port, and the pen-drive load when it does not.
Ethernet for routine programming #
If the panel has an Ethernet port, make it the default for every programming operation: it crosses no USB boundary and needs no USB driver on the PC. Do not infer the port from the family name — look at the connectors or the model's documentation. Read the panel's current address from its own system settings rather than guessing, and put the PC on a reachable network before starting the download. If the panel answers ping yet the transfer still refuses, the next check is the panel's runtime state, the subject of why an HMI transfer fails in initial start mode despite ping.
Leave the DIP switches out of boot loader mode #
Setting the switches to boot loader mode restarts the panel into its maintenance loader, which expects a firmware package on a pen drive or SD card. The application is untouched, but it will not run until the panel boots normally again, so the mode cannot load a project and takes the panel away from production while it is entered. It is a recovery boundary, not a stronger download function; treat a firmware update as a deliberate service step with the documented package. How a bootloader acts as a recovery boundary covers what that layer is and is not for.
Confirm the load before you call it done #
An error-free finish is not proof. Confirm the intended startup screen appears, move through several of the changed screens, and check a revision marker if the application carries one, then exercise the communications and operator actions the revision touched. If the old application still runs, recheck which xob you selected and which load command you issued. If the panel cannot read the media at all, return to the port, format and layout checks before touching firmware.
Questions asked
How do I tell in Windows which USB controller generation a port has?
Open the PC's device information, expand the USB controllers, and read the entries on the path your port uses: a controller listed as an Enhanced host controller is USB 2.0, while OpenHCD and Universal host controller entries are the USB 1.x generation. Ports on different entries can be different generations on the same board, so check the specific port you plug into.
What are the pen drive rules beyond FAT32?
Use a Hi-Speed USB 2.0 drive in the 4 to 16 GB range. These terminals read and write both FAT and FAT32, but FAT32 is the documented file system, so build the load media as FAT32. If you attach a hub at the host port to handle two drives, each drive must be FAT32 as well.
The panel is sitting in boot loader mode. How do I get out?
Restore the DIP switches to their normal operating positions and restart the panel; the loader leaves the application untouched, so it should boot back into the project. If the panel will not return to normal operation after the switches are restored, stop and escalate to the vendor's support rather than experimenting further.
Is Windows XP the reason the download fails?
No, the controller generation is. The panel fails from any PC whose controllers are all USB 1.x and succeeds from an XP machine that carries a USB 2.0 controller or card. XP only correlates because machines of that era often shipped with USB 1.x boards, which is why the check belongs on the controller, not on the operating system.