Troubleshooting
Why an HMI Is Detected but Project Download Fails
Short answer
Automatic LAN detection proves the panel answers on the network, not that the transfer function works. When USB and LAN both end in "failed to connect to the display unit", work the shared conditions in order: the exact system error code, supply voltage measured during the transfer, transfer settings in the engineering software, and the software version against the project target.
On this page
- What LAN detection proves, and what it does not
- Capture the system error before changing anything
- Measure the supply while the transfer runs
- Check the transfer settings at both ends
- Match editor version, firmware and project target
- The order that closes the fault
- What counts as fixed, and what to hand over
- Questions asked
The panel shows up in LAN discovery and the download still ends with "failed to connect to the display unit" — those are two different results, not a contradiction. Discovery proves the network interface answers on your subnet; the transfer then depends on the panel's transfer function, a supply that holds up under the write, matching settings on both ends, and an editor and firmware pair that accepts the project. When USB and LAN fail with the same message — the pattern reported on old-stock panels like the Pro-face GP 5401-TADW — the cable is almost never the cause. Work the shared conditions in order: system error code first, supply voltage during the transfer, transfer settings in GP-Pro EX, then editor version and project target.
What LAN detection proves, and what it does not #
Auto-detection sends a query out on the subnet and the panel answers it. That is one service on the panel. Project transfer is a different function, with its own settings, its own power demand at the moment the flash write begins, and its own version requirements. A panel can pass the first and fail the second all day.
| Result on the bench | What it establishes | What it does not establish |
|---|---|---|
| USB download fails | the USB path is not completing | anything about the LAN path |
| LAN: panel detected, download fails | the panel's interface answers discovery | that settings, power and runtime state allow a transfer |
| Both paths, one message | a condition shared by both paths | a cable fault |
Two independent physical paths producing one identical message points at what they share: the panel itself, its power, the software talking to it, or the project configuration. A ping or a discovery listing is evidence of life, not of transfer capability — the same distinction behind why an HMI transfer fails in initial start mode despite ping, a different documented pattern with a similar symptom.
Capture the system error before changing anything #
The transfer window on the PC gives you one sentence; the panel gives you the detail. Open the system error information screen on the unit and copy the text exactly, code first. Treat that code as the branch point for everything that follows.
One documented branch closes the case on its own: system error RAAA203. Pro-face's connection key documentation states that when RAAA203 appears, you perform a forced transfer using external storage, and transfer by other methods will not complete. If that is your code, stop chasing USB and LAN — put the project on the storage medium the panel reads, run the forced transfer, and the fault is closed.
Every other code goes to the checks below.
Measure the supply while the transfer runs #
The input rating printed on the unit's nameplate is the authority — read it off the panel rather than assuming a value. What kills old-stock units is not idle voltage but the sag at the instant the transfer starts, when the write to flash stacks on top of full display draw. A marginal supply passes every static check and drops out at exactly that moment, and the editor reports it as a connection failure.
Worked example with illustrative inputs — substitute your nameplate values. Say the nameplate reads 24 VDC at 0.8 A, the supply is set to 24.0 V, and the panel is fed through 15 m of 0.5 mm² copper one way, so the loop is 30 m of conductor:
- Loop resistance: R = 0.0172 Ω·mm²/m × 30 m ÷ 0.5 mm² = 1.032 Ω
- Drop at load: V = 0.8 A × 1.032 Ω = 0.83 V
- Voltage at the panel: 24.0 V − 0.83 V = 23.2 V
- With an example allowable band of ±10 %, the limit is 21.6 V, and 23.2 V clears it
Decision rule: measure DC volts at the panel's terminal block at idle and again while a download is running. If the reading falls below the printed minimum exactly at transfer start, the supply path is your fault — shorten the run, go up a conductor size, or fix the supply. If it holds inside the band, power is exonerated and you move on. On a unit that sat in storage, reseat the power connector and check terminal screw torque before trusting any reading.
One safety note: never raise the supply above the printed upper limit to "give it more power" — overvoltage destroys the panel; fix the drop in the path instead.
Check the transfer settings at both ends #
On the PC side, the transfer method in the project must match the connection you are actually using, USB or LAN. For LAN, do not trust the auto-detected target blindly: on a shared subnet, discovery can latch onto a different panel or a stale address. Confirm the target is the GP 5401-TADW on your bench, or enter its IP manually and retry.
For USB and RS-422/485 paths, Pro-face's troubleshooting for settings common to all display models (T.7.1) names one documented cause of connection errors: incorrect flow control on the USB/SIO port. The check is the [Port] settings in GP-Pro EX's [Device/PLC] configuration — make the flow control match what the connection uses and retry.
On the panel side, its offline menu holds which transfer methods it accepts at all. That kind of setting lives where how to enter configuration mode on a touch HMI shows you, and an old unit still configured to refuse the method you are trying will fail exactly this way. If USB never enumerates on the PC at all — no detection, nothing — the cable itself becomes the suspect, and how to upload an HMI program without the right cable pinout covers that pinout problem.
Match editor version, firmware and project target #
Version drift between an aging panel and a newer editor is a documented failure class, not a theory. Pro-face's September 2021 notification describes a transfer symptom solved by downloading GP-Pro EX V4.09.300, installing it, and transferring the project again. If your editor is older than that, update first and retry before touching anything else.
Then check the project's display target: it must be the exact model, GP 5401-TADW, options included — the suffix is part of the hardware definition. If the model does not appear in the software's target list at all, start with when an HMI model is missing from the programming software.
The order that closes the fault #
- Copy the system error information from the panel exactly, code first.
- RAAA203: run the documented forced transfer from external storage; no other method completes. Done.
- Measure the supply at the panel terminals at idle and during a download; compare with the nameplate.
- Below the printed minimum during transfer: fix the supply path, then retest.
- Verify the port flow-control settings under the device configuration for the USB/serial path, the LAN target address for the network path, and that the transfer method matches the connection in use.
- Record the editor version and the project's display target; update the editor if it predates the documented fix release, and set the target to the exact model.
- Retry USB and LAN separately, noting for each whether detection succeeds and when the failure appears.
- Still failing: escalate rather than guess.
What counts as fixed, and what to hand over #
Success is the download completing end to end and the panel booting the new project — a discovery listing is not success. After any change, repeat the same transfer and confirm the connection error is gone and the project runs.
If the fault survives the full sequence, hand support the complete data set: full model designation, the exact PC-side message, the readable system error text, editor version, panel firmware or runtime information, the selected project target, the measured terminal voltage during transfer, and the separate USB and LAN results. That package is what separates a power fault from a compatibility or configuration fault without parts-swapping.
Questions asked
Why does LAN discovery find my HMI but the download still fails to connect?
Discovery and transfer are different functions on the panel. Being listed proves the network interface answers on your subnet; the download then depends on the transfer function, its settings, a supply that holds up during the write, and an editor and firmware pair that accepts the project. Any one of those failing produces the same final message.
Can insufficient power cause failed to connect to the display unit?
Yes. Supply sag at the moment a transfer starts is a common shared cause when USB and LAN both fail. Measure at the panel's power terminals while a download runs and compare with the input range printed on the nameplate. In a 24 V example with 15 m of 0.5 mm2 cable at 0.8 A, the loop drops 0.83 V and the panel sees 23.2 V; treat power as the fault only if the measured value falls below the printed minimum.
What does system error RAAA203 mean on the panel?
Pro-face documents RAAA203 as a condition where normal transfer methods will not complete. The documented recovery is a forced transfer using external storage: put the project on the medium the panel reads, trigger the forced transfer, and let it rewrite from there. Until then, USB and LAN attempts keep ending in the same connection failure.
Both USB and LAN fail with the same message. Is the cable the problem?
Unlikely. Two physically independent paths failing with one identical message points at a condition shared by both: panel power, transfer settings, a software or firmware mismatch, or the panel's internal state. Check the port flow-control settings in the device configuration for the serial path and the LAN target address before replacing any cable.
Which GP-Pro EX version fixed a transfer failure on older panels?
A documented Pro-face notification from September 2021 ties a transfer symptom on these units to editor version drift, with recovery consisting of installing the then-current editor release and transferring the project again. The exact version and steps are given in the version-matching section below; the principle is to rule out version drift before changing hardware.