IMDTouchKnowledge BaseShop main store

Troubleshooting

Separating HMI Transfer Method From PLC Driver Selection

HMI and touchscreens Published 6 min read

Short answer

The application download (Ethernet, or USB with the XBTZG935 cable) and the PLC driver (Uni-Telway) are two independent selections in a Vijeo Designer project. A driver missing from the transfer screen is a configuration-location problem, not proof that Vijeo Designer 6.2 is required.

On this page
  1. Two connections, two selections
  2. Set the replacement target first
  3. The download connection: Ethernet or USB
  4. The PLC connection: where Uni-Telway is selected
  5. Cable, serial settings, and equipment addressing
  6. Confirm live PLC data
  7. Symptom-to-check list
  8. Questions asked

The Uni-Telway driver for PLC communication and the transfer method for the application download are two separate selections made in two different configuration windows, and confusing those windows is what makes the driver look missing. The driver is chosen in the target's PLC communication configuration; the download method — Ethernet, or USB with the XBTZG935 cable — is chosen in the transfer settings. Neither selection implies the other. For a replacement HMIGTO6310 programmed in Vijeo Designer 6.1 in place of an XBTGT6330, that separation also settles the version question: a Vijeo Designer 6.2 upgrade is justified only when documentation for the target, driver and version together names it, never by a driver absent from a transfer dialog.

Two connections, two selections #

Commissioning a replacement panel configures exactly two connections. Keep them separate and verify them separately:

  1. Engineering PC to HMI: downloads the compiled application. Selected in the transfer settings as Ethernet, or USB with the XBTZG935 cable.
  2. HMI to PLC: exchanges process values and commands. Selected as a driver — Uni-Telway — in the target's PLC communication configuration, with the PLC added as equipment under that driver.
Connection Purpose Selected in What proves it works
PC to HMI Application download Transfer settings: Ethernet or USB (XBTZG935) Transfer completes; panel starts the application
HMI to PLC Process data Driver list in the target's PLC communication configuration A live value matches the PLC and updates

Driver availability belongs to the selected target. Schneider Electric publishes driver support per HMI family — one example qualifies a Siemens TIA Ethernet driver for HMISCU, HMIGTO, HMIGTU and iPC — so the compatibility check is always target plus driver plus software version. The transfer screen is never part of that check, and selecting Ethernet or USB does not select, replace or exclude any PLC driver.

Set the replacement target first #

Fix the target before touching communication. Save a separate copy of the working project and record the old panel's driver, equipment settings, serial configuration and variable addressing. In that copy, select HMIGTO6310 as the target in place of the XBTGT6330, read the conversion messages, and validate the application. A transfer cannot correct a project configured for the wrong hardware.

Changing the target changes which communication resources and driver choices the editor presents, because each target carries its own hardware environment including its PLC devices. Treat the old project as the record of the PLC connection you must recreate, not as proof that every setting carries over. If a whole family is absent from the target catalog, that is a different fault with its own recovery, the same class of problem as getting the HMIGXO family into the Vijeo Designer catalog.

The download connection: Ethernet or USB #

For an Ethernet transfer, establish the panel's network settings first. Read its configured address, confirm the engineering PC has a valid route to it, check for duplicate addresses, and confirm the address entered in the transfer configuration is the intended panel rather than another HMI on the network.

Worked example with illustrative addresses:

  • Panel: 192.168.1.10 with mask 255.255.255.0
  • Engineering PC: 192.168.1.50 with mask 255.255.255.0
  • PC network: 192.168.1.50 AND 255.255.255.0 = 192.168.1.0
  • Panel network: 192.168.1.10 AND 255.255.255.0 = 192.168.1.0

Both ends compute to 192.168.1.0, so the PC delivers directly and the transfer configuration points at 192.168.1.10 with no gateway. If the PC were 192.168.0.50, its network would be 192.168.0.50 AND 255.255.255.0 = 192.168.0.0, which does not equal 192.168.1.0: correct the PC address or add a route before suspecting the software. When the panel sits behind a router or VPN, run this same reachability check first, as covered in downloading a Vijeo Designer project to a remote HMI over VPN.

For a USB transfer, use the XBTZG935 cable, confirm the PC recognizes the connection, then select USB as the transfer method. Resolve device-recognition problems before troubleshooting the project itself.

Download only after target validation succeeds. Read the transfer result and separate a connection failure — no route, unrecognized cable, wrong address — from a target or runtime compatibility failure reported by the software. A completed download proves the transfer path only, never PLC communication.

The PLC connection: where Uni-Telway is selected #

The transfer dialog lists transfer methods; it never lists PLC drivers. Uni-Telway is selected from the driver list inside the target's PLC communication configuration, and the PLC is then configured as equipment belonging to that driver — the same driver-plus-equipment pattern as adding a Modbus RTU driver and external variables in Vijeo Designer.

Work the cases in order:

  • You were looking in the transfer settings. That is the entire fault. Open the PLC communication configuration for the HMIGTO6310 target and select Uni-Telway from its driver list. No software change is justified.
  • The target is still the XBTGT6330. The driver list you are reading reflects the old target. Reselect HMIGTO6310, revalidate, and read the list again.
  • HMIGTO6310 is selected and Uni-Telway is genuinely absent from the PLC communication driver list. Record the installed version and service pack, then verify the HMIGTO, Uni-Telway and version combination against Schneider Electric's documentation or support. Move to Vijeo Designer 6.2 only when that documentation names it as the required minimum, and obtain it from Schneider Electric or an authorized distributor.

A higher version number alone is not the fix: target families have needed explicit activation even inside 6.2, as in activating the XBTOT target family in Vijeo Designer 6.2. Decide from documented compatibility, not from a missing entry in the wrong window.

Cable, serial settings, and equipment addressing #

With the driver selected, match the physical and logical link. A protocol name does not define the connector pinout, the electrical interface, the station addressing or the communication parameters.

  • Read the connection documentation for both the HMIGTO6310 and the PLC port; verify the interface, connector assignments and cable wiring. Reuse the old panel's cable only after those details match, because a connector that fits is not a wiring check.
  • Assign the driver to the HMI port that is physically wired to the PLC, and clear any conflicting assignment.
  • Match baud rate, parity, data bits and stop bits against the PLC port and the saved project settings — the values the devices require, not guessed defaults.
  • Match the Uni-Telway equipment configuration to the PLC's configured communication identity, and confirm the application variables reference that equipment.

Compile, download again, and confirm the panel starts with the revised communication configuration before judging runtime behavior.

Confirm live PLC data #

  • Start with a read-only variable you know, and compare the HMI value against the PLC programming tool, including its data interpretation.
  • Confirm the value updates with a normal process change or a controlled test condition; a plausible static number can be a retained value rather than live communication.
  • Check the panel's runtime communication indication for the PLC equipment.

Before testing any write from the replacement panel, put the machine in a state where an unexpected command cannot start motion or a process.

Symptom-to-check list #

  • Application will not download: transfer method, destination address, PC route or USB cable recognition, target compatibility.
  • Application runs but PLC values fail: driver selection, port assignment, cable wiring, serial settings, equipment address.
  • Only some variables fail: the variable's equipment reference, address and data type against the actual PLC value.

Questions asked

Do I need Vijeo Designer 6.2 to use Uni-Telway with an HMIGTO6310?

Not because of the transfer method. Ethernet and USB transfers with the XBTZG935 cable are transfer settings, fully independent of the PLC driver. Upgrade only if Schneider Electric's documentation for the HMIGTO target with the Uni-Telway driver names a minimum version above your installed 6.1, and obtain that release from Schneider Electric or an authorized distributor.

Why does Uni-Telway not appear in my download window?

Because the download window lists transfer methods — Ethernet or USB — never PLC drivers. Uni-Telway is selected from the driver list in the target's PLC communication configuration, where the PLC is added as equipment under that driver. If it is missing from that list as well, confirm HMIGTO6310 is still the selected target before questioning the software version.

The download completed but the panel shows no PLC values. Is that a transfer problem?

No. A completed download proves the engineering transfer path works; it says nothing about PLC communication. Work the second connection instead: driver selection, port assignment, cable wiring checked against both devices' documentation, serial settings, and the Uni-Telway equipment address versus the PLC's configured identity.

Can the panel download over Ethernet while talking Uni-Telway to the PLC?

Yes. The two connections are independent: the PC reaches the panel over the network for the transfer while the panel exchanges data with the PLC through the Uni-Telway driver. Before each transfer, confirm the panel's address is unique on the network and the PC still has a route to it.

Can I reuse the cable from the old XBTGT6330?

Only after comparing wiring, not connectors. Check the electrical interface and pin assignments in the documentation for both the HMIGTO6310 and the PLC port, then match baud rate, parity, data bits and stop bits to the PLC. A connector that fits the new panel is not evidence the wiring matches.

Keep reading

  • Troubleshooting

    Why HMI Programming Software Needs a Ping Reply to Download

    The programming software sends an ICMP echo request to the panel and aborts the download when the reply is blocked, even while remote viewing still works. Ask for one scoped firewall rule: the echo request from your authorized source to the panel address, with its stateful reply. Do not disable the firewall or fake the reply.

    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

  • Selection guide

    Selecting a Modbus TCP HMI Panel for an Existing Controller

    A replacement HMI qualifies when its Modbus TCP client driver reproduces the working panel's tag map exactly: data area, raw address, word order and write behavior. A connection that polls proves reachability, not correctness — prove one known tag and one supervised write before rebuilding the screens.

    HMI and touchscreens