IMDTouchKnowledge BaseShop main store

Troubleshooting

When VNC works but HMI project upload fails over Ethernet

HMI and touchscreens Published 7 min read

Short answer

A VNC session proves only an IP path to the panel's viewer service; it says nothing about the engineering transfer service the upload tool needs. Read the panel's real address, put the PC in that subnet, test LAN1 and LAN2 separately, then check adapter selection and the panel-side transfer enable. Copy the project to USB before any firmware recovery.

On this page
  1. What the VNC session proves, and what it does not
  2. Read the panel's real address first
  3. Worked example: PC addressing for a panel at 192.168.1.10, mask 255.255.255.0
  4. Test LAN1 and LAN2 as separate interfaces
  5. Separate workstation faults from panel-service faults
  6. Back the project up over USB before recovery
  7. The firmware recovery branch, in order
  8. The decision for each case
  9. Questions asked

VNC reaches the panel, the upload tool does not: those two results are not contradictory. A VNC session proves an IP path to the panel's viewer service; an HMI project upload needs a separate engineering transfer service with its own enable state and its own session. Work the fault in this order: read the panel's real address from its own screen, put the engineering PC in that subnet, test LAN1 and LAN2 as separate interfaces, then separate workstation faults from panel-service faults. Before any firmware recovery, copy the project to USB — in the reported DOP-W127B case the flash-drive copy worked even though Ethernet transfer returned "ethernet can't be opened" every time.

What the VNC session proves, and what it does not #

The viewer talks to the panel's VNC service; the upload tool has to open an engineering session the panel can refuse independently. Reachability of one service is not connectivity to the device's other services — the same distinction behind why a WAN ping proves reachability, not LAN connectivity.

Observed result What it proves What it does not prove Next check
VNC shows the panel's live screen an IP path reaches the panel's viewer service that the transfer service is enabled or reachable compare the VNC target address with the address typed into the tool
the PLC program uploads over the same switch the workstation has a path to the PLC that the panel shares that address, subnet or port test the panel's recorded address directly
automatic search finds no device discovery received no usable answer that the panel is offline select the wired adapter in the tool, then enter the panel address manually
a static address returns "ethernet can't be opened" the tool cannot open its Ethernet session that the address itself is wrong split path failure from service failure with a ping

Do not spend time proving the panel is alive; it is. Spend it on the path between the upload tool and the transfer service. VNC is also the accepted workaround when the touch layer dies — using a mouse and VNC when an HMI touchscreen fails keeps the machine operable — but it never restores the engineering path.

Read the panel's real address first #

  • Walk to the panel and open its network page; the address it displays is the only one that counts, not the one the PLC project or a cabinet drawing suggests.
  • Record the address, the subnet mask, the gateway and which physical port — LAN1 or LAN2 — the cable enters.
  • Note the link indication at the panel port and at the switch port.
  • Write down the address the working VNC viewer targets, and confirm it is the same one you type into the upload tool.

Those recorded values are the inputs for the addressing step below; nothing else is trusted until it matches them.

Worked example: PC addressing for a panel at 192.168.1.10, mask 255.255.255.0 #

Inputs (illustrative values in the RFC 1918 private range; your own values come from the panel's network page):

  • Panel address 192.168.1.10, subnet mask 255.255.255.0, read at the panel.
  • One engineering PC, wired adapter, one cable — to the same switch path the working VNC session uses, or direct to the identified LAN port.
  • Known busy addresses on that network: the panel's .10 and the PLC's address.

Rule in words: with mask 255.255.255.0, the first three octets form the network. Two hosts exchange frames directly only when their first three octets match; anything else needs a router between them. A network of this size holds 256 addresses, two of which are reserved.

Arithmetic:

  • Panel network: 192.168.1.10 with mask 255.255.255.0 gives network 192.168.1.0 and broadcast 192.168.1.255.
  • Usable addresses: 256 − 2 = 254, the range 192.168.1.1 through 192.168.1.254.
  • Choose 192.168.1.50 for the PC: its first three octets, 192.168.1, match the panel's, so both sit on 192.168.1.0/24 with no router in between. Leave the gateway field empty.

Result: PC at 192.168.1.50, mask 255.255.255.0, gateway blank, is a valid same-subnet setting for a panel at 192.168.1.10.

Decision: ping 192.168.1.10 from that setting. Four replies while the upload still returns "ethernet can't be opened" means addressing is not the fault — move to the adapter and panel-service branches. Zero replies keeps you in the physical and addressing branch. Committing to that split is what stops the loop of retyping addresses.

Test LAN1 and LAN2 as separate interfaces #

A two-port panel runs LAN1 and LAN2 as independent interfaces: each can hold its own address, and moving the cable does not carry the configuration with it.

  • Use one known-good cable and one PC adapter for the whole test.
  • Check the link indication at both ends; no link sends you to cable, connector or a disabled port before any software.
  • Shine a bright light into the panel's RJ45 socket and look for bent pins before blaming software.
  • Repeat the addressing test against the port you are actually plugged into, using that port's recorded address.

In the reported case the procedure ran on both ports and no address was discovered on either, so port swapping alone was not the repair; the fault lived above the physical layer or on the panel-service side.

Separate workstation faults from panel-service faults #

On the PC:

  • Disable VPN clients and virtual adapters so the subnet has exactly one route.
  • Select the wired adapter inside the upload tool, not only in the operating system.
  • Allow the tool through the local firewall.
  • Try a second PC built the same way. In the reported case a second PC with fresh addresses still failed, which rules out one damaged installation and points at a cause both machines share: the same wrong target, the same policy, or the panel's transfer service.

The reported split — VNC worked from Linux, not from Windows — is a viewer-side difference, not a panel fault. When a VNC viewer connects from some machines and not others, the address the viewer targets is the first suspect; a remote VNC viewer that targets the wrong address fails exactly this way.

On the panel, transfer is often gated on purpose. One vendor's HMIs show a tick labeled "Allow Ethernet Download & Upload" that must be set before Ethernet transfer is accepted; on others the channel is enabled from a control menu reached during boot. Ping, runtime and VNC all work with that permission off, and the upload alone refuses — which matches the signature in the reported case.

Back the project up over USB before recovery #

The reported case recovered the project to a flash drive even though Ethernet transfer never opened. Do that before anything else touches the panel.

  1. Insert the USB flash drive in the panel.
  2. Use the panel's own copy or transfer function to write the project to the drive.
  3. Wait for the panel to report completion, then remove the drive.
  4. Open the recovered project in the engineering software and confirm it loads.
  5. Keep one untouched copy and work only on copies.

The USB path is local storage on the panel: it uses neither the LAN configuration nor the transfer service, so it proves nothing about Ethernet. It is still the copy that saves the application if a recovery goes wrong.

The firmware recovery branch, in order #

Firmware recovery is the last branch, and it has conditions:

  • the project exists on USB and opens in the engineering software;
  • both LAN ports failed with controlled addressing;
  • a second PC failed the same way;
  • the panel-side transfer permission was verified on.

Then build the automatic update package from the project in the engineering software, copy it to the flash drive in the structure the software generated — no renamed or rearranged files — and apply it from the panel's USB update function. A failed update can leave the panel without a running application, which is exactly why the untouched USB backup comes first.

The decision for each case #

  • Ping fails after the worked-example addressing: physical layer — cable, bent pins in the RJ45 socket, switch port, disabled interface. Fix link before software.
  • Ping answers, automatic search still empty: tool side — wrong adapter selected, a VPN or virtual adapter routing the subnet, firewall.
  • Ping answers, the manual address still returns "ethernet can't be opened": panel transfer service — verify the Ethernet transfer permission, then run the USB firmware recovery after the backup.
  • VNC connects from some computers only: workstation difference on the failing machines; do not condemn the panel for it.
  • Project already copied to USB: it is the authoritative backup; verify it opens before any further change.

When the tool does connect and the transfer aborts mid-session, the fault has moved to the session layer: an HMI project upload that reports Communication failed is a different failure from the discovery failure traced here.

Questions asked

Why does VNC show the HMI screen while the upload tool reports ethernet can't be opened?

VNC and the project transfer are separate services on the panel. The viewer path can be healthy while the engineering service is disabled, filtered or crashed, so the tool cannot open its Ethernet session even though the screen renders. Compare the two addresses character by character, then check the panel-side transfer permission, before suspecting hardware.

Does copying the project to USB mean Ethernet transfer should also work?

No. The flash-drive copy runs through the panel's local storage and never touches the LAN configuration, the workstation route or the transfer service. Keep it as the recovery copy, verify it opens in the engineering software, and treat the Ethernet fault as still live until an upload actually succeeds.

Should I update the panel firmware to fix the failed upload?

Only after the project is backed up and both LAN ports, a controlled same-subnet PC and a second workstation have all failed, and the panel-side transfer permission is confirmed on. Build the automatic update package from the project and apply it from the panel's USB update function.

Does reaching the PLC over the same switch prove the HMI is reachable?

No. The PLC answers on its own address; the panel may sit on another address, subnet or physical port behind the same switch. Test the panel's recorded address directly instead of inferring reachability from the PLC, and repeat the test on LAN1 and LAN2 separately.

Why would VNC connect from the Linux machine but not from Windows?

The viewer side differs between machines: adapter selection, routing and firewall policy on the Windows computer can block the same session Linux opens. Fix the Windows path, or keep using the Linux viewer, but treat it as a workstation difference rather than evidence of a panel fault.

Keep reading

  • How-to

    Replacing an old HMI when no project files exist

    There is no free configuration software for a legacy Magelis or PanelMate panel that arrived without it, so choose one of three licensed routes: buy the matching engineering package, hire an integrator who owns it, or have a distributor upload and print. If no editable project can be recovered, capture the running application, map every tag against the live controller, and rebuild on confirmed writes.

    HMI and touchscreens

  • Troubleshooting

    Fixing an HMI Project Upload That Reports Communication Failed

    Treat a failed HMI project upload as three separate branches: the installer's parallel-port dongle driver message is a licensing fault, a "communication failed" report before any progress is a transfer-path mismatch, and a "file system error" after the panel answers is a storage or destination fault. Identify the layer from the message and the moment it appears, fix that layer only, and retest. A dongle fault never blocks the cable, and a successful ping never proves the transfer service is up.

    HMI and touchscreens

  • Troubleshooting

    When the HMI Software Has No Driver for Your PLC

    If the Device/PLC list in your HMI software has no driver for the controller family, that project cannot open a native connection — no cable, baud rate or tag edit adds one. Confirm the list for the exact software version, then either move the project to software that documents the driver with a panel it supports, or replace the panel side. In the GP2500 case, the count comes to 3 of 4 required matches, which fails.

    HMI and touchscreens