IMDTouchKnowledge BaseShop main store

Explainer

Why a USB HMI transfer cable cannot be hand built

HMI and touchscreens Published 6 min read

Short answer

There is no pin map to copy: the cable is an active USB device whose bridge IC and firmware descriptors do the work, so a soldered copy enumerates as nothing. Buy the documented accessory for the tool-port path, or move the project by Ethernet or USB memory.

On this page
  1. What the accessory actually is
  2. Why wiring alone cannot work
  3. The numbers behind the interface
  4. Transfer paths that do work
  5. Transferring over the accessory
  6. When the transfer fails
  7. The decision
  8. Questions asked

There is no pin map to copy, because the part of the cable that does the work is not wiring. A USB HMI transfer cable such as the Pro-face CA3-USBCB-01 is an active USB device: a bridge IC and its firmware descriptors live inside the connector shell, and they, not the copper, are what the PC and the panel talk to. A soldered copy of the connector pinning enumerates as nothing on the PC and never reaches the panel. For the tool-port path, buy the documented accessory; if Ethernet or USB memory is available on the panel, transfer that way and skip the cable entirely.

What the accessory actually is #

The CA3-USBCB-01 is a 2 m (6.5 ft) USB transfer cable for moving screen data between a PC and the panel; the same accessory also carries the order code PFXZC3CBUSA1. It is listed for the GP3000, ST3000(W) and LT3000 series, which covers a bench panel such as the AST3401-T1-D24 (24 VDC supply) downloading a project from GP-Pro EX. Do not confuse it with the ordinary peripheral USB cable the same manufacturer lists for printers and storage (FP-US00, 5 m): that one serves the panel's host port for peripherals and moves no projects from a PC.

Why wiring alone cannot work #

USB is not a pin-for-pin interface. Under the USB 2.0 specification, a full-speed device announces itself by pulling the D+ line up through a 1.5 kΩ resistor; the host then resets the line, and the device must answer with its descriptors — vendor ID, product ID, endpoints — before one byte of project data moves. The driver binds to those descriptors. None of that lives in a wire map.

A passive serial lead is a different animal, and the contrast is the whole answer:

Attribute Passive serial lead USB transfer accessory
Electrical function Point-to-point conductors, optional shield tie Bridge IC plus level conversion
PC-side interface UART levels on a COM port USB; enumeration required first
Driver None Supplied with the development software
Reproducible from a pin map Yes No — the wiring carries none of the function

That is why a shop that routinely builds its own serial leads — see How to Build the HMI Cable for an A1S Programming Port and Building the RS-232 Modbus cable between an HMI and a controller — still has to buy this one. Those jobs copy conductor maps; this accessory has no conductor map that matters.

The numbers behind the interface #

Full-speed USB runs at 12 Mbit/s: one bit every 1 ÷ 12,000,000 s ≈ 83.3 ns. A 115.2 kbaud serial link moves one bit every 1 ÷ 115,200 s ≈ 8.68 µs. The ratio is 12,000,000 ÷ 115,200 ≈ 104, which is why the transceiver and its timing, not the copper, are the functional content of the assembly.

Illustrative check, 5 MiB runtime project, protocol overhead ignored:

  • Serial at 115,200 bit/s with 10 bits per frame (start, 8 data, stop): 115,200 ÷ 10 = 11,520 B/s. 5 MiB = 5 × 1,048,576 = 5,242,880 B. 5,242,880 ÷ 11,520 ≈ 455 s ≈ 7.6 min.
  • Full-speed USB at its raw ceiling: 12,000,000 ÷ 8 = 1,500,000 B/s. 5,242,880 ÷ 1,500,000 ≈ 3.5 s.

Those are interface ceilings, not measured throughput for this cable, but they frame the decision: the bridge earns its place, and soldering cannot reproduce it. The same specification caps a cable segment at 5 m; the documented 2 m accessory leaves 5 − 2 = 3 m of margin, so a long passive extension inside one segment is already outside the arithmetic.

Transfer paths that do work #

Path Hardware Use when Watch-out
Tool port over USB CA3-USBCB-01 plus its driver Panel has no Ethernet, or the LAN is not commissioned Accessory and driver install are both required
Ethernet Patch cable or switch to the panel LAN port Panel has an assigned IP address PC and panel must share a subnet; the firewall must allow the transfer service
External memory CF or USB storage in the panel's slot No PC can reach the panel Export the runtime package, not the source project
Panel USB device port Standard A-to-B cable, if the port is fitted The model exposes a device (slave) port Verify it is a device port, not the host port for peripherals

Confirm which of these the exact model physically carries before choosing; the connector complement varies within a series.

Transferring over the accessory #

  1. Install GP-Pro EX before plugging the cable in, so the USB driver files are staged on the PC.
  2. Apply 24 VDC and confirm the panel boots to its runtime or offline screen.
  3. Connect from a root USB port on the PC — not an unpowered hub — to the panel's tool port.
  4. Check enumeration in Windows Device Manager: the cable must appear as a virtual COM port or a Pro-face USB transfer device. If it sits under Other devices with a warning, point the driver update wizard at the software's driver folder.
  5. Note the COM number the system assigned.
  6. In the editor's transfer settings, select that USB/COM path rather than Ethernet or memory output.
  7. Send the project. A first download onto different runtime firmware also pushes the system part; let it run to completion.
  8. Confirm the project name and version on the panel's offline or system information screen.

Do not remove panel power while a runtime or system download is running. Before overwriting a bench panel, upload what is already on it; if the right lead for that upload is the missing piece, see How to Upload an HMI Program Without the Right Cable Pinout.

When the transfer fails #

  • Cable absent from Device Manager: try another root port and another PC. The bridge draws bus power, so a dead port or an unpowered hub hides it.
  • Device present with a driver warning: reinstall from the editor's driver folder and confirm a signed driver exists for your Windows version.
  • Editor reports no response or a timeout: re-check the COM number and put the panel in its offline or transfer mode from the system menu.
  • Transfer starts and aborts midway: secure the connector at the tool port and take any extension out of the path.
  • Ethernet pings but the transfer refuses: let the editor's transfer executable through the PC firewall and retry.

A transfer that fails specifically from an old PC has its own documented cause — see Why an HMI Fails USB Transfer From a USB 1.0 PC.

The decision #

Four cases, four answers:

  • You need the PC-to-tool-port path, because the panel has no Ethernet or the LAN is not yet commissioned: buy the CA3-USBCB-01 (order code PFXZC3CBUSA1) and install its driver. No hand-built substitute exists — the bridge is the product, and a pin map cannot carry it.
  • The panel has an Ethernet port with an address: transfer from GP-Pro EX over the LAN and spend nothing on cables.
  • No PC can reach the panel: export the runtime package to CF or USB storage and load it at the panel.
  • You were about to solder one: stop. The copy enumerates as nothing, and the bench hours are the only thing you will transfer.

Questions asked

Will the accessory work on panels outside the GP3000, ST3000 and LT3000 families?

The documented list covers those three families, so an AST3401-T1-D24 sits inside it. Outside that list the combination is untested: check the tool-port designation against the manufacturer's accessory documentation before assuming reuse, and expect earlier serial-only generations to need their own, different download accessories.

Can I extend the 2 m cable to reach a panel further away?

Not with passive wire. The USB 2.0 specification allows one cable segment of up to 5 m, and the documented accessory already uses 2 m of it, leaving 3 m. A longer run needs a powered hub to start a fresh segment, not more copper spliced into the same one.

Why did the COM number change when I replugged the cable?

Windows assigns the COM number per physical USB port, so moving the plug to a different port produces a different number. Re-read the number in Device Manager and re-select it in the editor's transfer settings before blaming the cable.

What happens if power is lost in the middle of a download?

An interrupted project transfer can simply be resent. An interrupted runtime or system download can leave the panel needing a recovery over the same tool-port path, the one situation where neither Ethernet nor memory transfer substitutes, so keep the 24 VDC supply stable until the push completes.

Keep reading

  • Explainer

    Why a USB Joystick Cannot Drive PanelView Tags

    No. PanelView documentation supports USB flash drives, keyboards and mice, and the Plus 7 Performance host ports add removable drives and a printer — no game-controller class and no runtime mechanism that maps an input device to tags. The joystick belongs on PLC inputs or on a PC-based panel.

    HMI and touchscreens

  • How-to

    Adding Flowmeter and Sensor Graphics to an EasyBuilder Pro Screen

    EasyBuilder Pro has no dedicated flowmeter or temperature-sensor object, and it does not need one. Put a picture from the Shape or Picture Library (or your own imported image) on the screen to identify the instrument, then add a separate numeric object bound to the device address for the live measurement — the picture never carries the data connection.

    HMI and touchscreens

  • Troubleshooting

    Why WAV Event Sounds Play in Simulation but Not on an HMI Panel

    The sound plays in simulation because the PC sound card renders the WAV file. The panel stays silent because its buzzer is a tone generator, not an audio output: WAV playback needs a terminal with an audio output or a supported USB sound card feeding powered speakers, with volume set at the speaker.

    HMI and touchscreens