Troubleshooting
Why an HMI Transfer Fails in Initial Start Mode Despite Ping
Short answer
Ping success proves only that the panel's IP stack answers. On a new Magelis XBTG in Initial Start Mode, run three checks in order: build in the engineering version that still supports the target (Vijeo Designer 6.2 for XBTG), clear the license so the download command activates, then load runtime and application over one transport at a time.
On this page
- What Initial Start Mode is telling you
- Read the three symptoms separately
- Match the software version to the exact target model
- Clear what holds the download command inactive
- Load the runtime and application, one transport at a time
- What a green ping proves, with numbers
- Confirm the load on the panel and log the run
- Questions asked
A Magelis XBTG taken out of the box sits in Initial Start Mode: a startup page where the only setting you can change is the IP address. That screen is the expected state of a panel with no runtime and no application on it, and a ping reply proves nothing beyond a live IP stack. Work the failed transfer as three independent checks, in this order: the engineering software version against the exact target model, the license and build state that activates the download command, and the runtime-installation path, attempted over one transport at a time.
What Initial Start Mode is telling you #
The startup page is not a fault code. It is the panel's defined empty state — the same state that Runtime Installer's Recovery function deliberately returns a panel to. Two legitimate ways out exist: a project download whose package installs the runtime together with the application, or a separate runtime installation run first. Which path applies is a property of the target's download options in the engineering software, not something to discover by alternating attempts; pick one, run it, and record which you used.
Before the first transfer, set the panel's IP address on that startup page and write it down. If the panel is already wired into a machine that runs, do any Recovery or reload with the machine stopped — the operator interface disappears the moment the runtime reinstalls.
Read the three symptoms separately #
A ping that answers, a download command that stays inactive and a Runtime Installer that refuses the connection are three findings, not one:
| Symptom | What it proves | Where the fault lives |
|---|---|---|
| Panel answers ping | The IP stack on the subnet you configured is alive | Nowhere else |
| Download command inactive | The engineering software is refusing the operation | License condition, unbuilt project, or wrong target |
| Runtime Installer cannot connect | No transfer session was established | Version support, target identity, or transport selection |
A download that succeeded against a different operator terminal model is evidence about your license and your PC, not about this target's configuration. Keep it out of the diagnosis.
Match the software version to the exact target model #
For XBTG-series panels the answer is Vijeo Designer 6.2. The vendor's compatibility documentation states that version 6.3 no longer supports legacy models that 6.2 builds for, and this line is among them, so a 6.3 workstation fails for reasons no cabling can fix.
- Set the project's target machine to the exact physical model, XBTG6330, rather than another operator terminal.
- Build and validate against that target; a build aimed at a different panel does not transfer usefully.
- Run the transfer from 6.2. If only a newer version is installed on the PC, that alone explains a connect failure with ping green.
Decision: version 6.2 installed, target set to XBTG6330, project compiled. Only then move on.
Clear what holds the download command inactive #
Two things gate the command, and only two:
- The project must be compiled; on an unbuilt project the command stays inactive. Compiling is the cheap check, so do it first.
- The license must permit the download operation. In the reported case the grayed-out command traced to a license condition, and clearing it restored downloads immediately.
Adding a Modbus TCP/IP or USB device in the I/O Manager does nothing here. I/O Manager entries describe the runtime's communication with controllers — the failure modes on that side are covered in Why HMI indicators stay off over Modbus RTU polling — while the transfer destination is chosen in the download dialog itself. With the command active and the target right, stop debugging the software and go to the transport.
Load the runtime and application, one transport at a time #
Pick the deployment path deliberately:
- If the target's download options package the runtime with the application, use the project download and finish in one pass.
- If the runtime must be installed separately, run Runtime Installer from the engineering software's Start menu first, then download the application.
Then hold this sequence:
- Set and record the panel IP address on the startup page.
- Confirm the engineering PC reaches that address, then run exactly one transfer with the exact target and the matching destination selected.
- Record the exact error text on a refusal; "fails to connect" is a symptom, and the message names the layer at fault.
- Only then switch transport. USB is a separate test, and a green ping says nothing about it — for a serial or USB upload the cable pinout matters more than the network, as covered in How to upload an HMI program without the right cable pinout.
One change per attempt keeps every result attributable. After the initial download completes, the panel holds its assigned IP address and the download communication type can be changed, so later transfers are not locked to the first transport.
What a green ping proves, with numbers #
Take example addresses: the panel set to 192.168.1.50 with mask 255.255.255.0 on the startup page, the engineering PC at 192.168.1.10 with mask 255.255.255.0.
- PC network: 192.168.1.10 AND 255.255.255.0 = 192.168.1.0
- Panel network: 192.168.1.50 AND 255.255.255.0 = 192.168.1.0
Both hosts sit on 192.168.1.0/24, so an echo request is delivered and the panel's stack replies. That is the full content of a ping result: a working Layer 3 path and a live IP stack. The transfer is an application-layer session between the tool and the panel's download service, and nothing in the ping speaks to it — the same reachability-versus-session distinction behind Diagnosing intermittent HMI to PLC Ethernet comms hangs.
Decision: ping green with transfer red exonerates the network. The fault is in the version, the target, the license or the transport selection, in that order of likelihood on a first commissioning.
Confirm the load on the panel and log the run #
Verification happens on the glass: the startup page must be gone, the runtime must start, and the first project screen must appear. A clean build on the PC proves nothing about what is on the panel, and neither does a transfer log aimed at a different model.
If the panel still shows Initial Start Mode after a reported success, the runtime was not installed by that path. Run Recovery to return the panel to a clean empty state, then take the other deployment path. On a panel already in service, a reload forced by a lockout follows the sequence in Redownloading an HMI project after a user lockout.
Keep a one-line record per attempt: engineering version, target model, transport, destination address, exact result, and the panel's display state afterwards. That is the minimum record that keeps a second failure separable from the first.
Questions asked
Does a successful ping mean Runtime Installer should connect?
No. Ping confirms the panel's IP stack replies to ICMP on the subnet you configured. Runtime Installer needs an application-layer session with the panel's download service, which depends on the software version supporting the target, the exact target model selected, and the transport choice. With ping passing, spend your time on those three, not on cables and switches.
Why is the download command inactive even after the project compiles?
Compiling is necessary but not sufficient. The command also requires a valid license for the download operation; in one reported case the button stayed grayed out until a license condition was cleared, after which a transfer to a different panel model succeeded. Adding a Modbus TCP/IP or USB device in the I/O Manager does not affect it, because that configures runtime controller communication, not the transfer destination.
Can I use a newer engineering software version than 6.2 for an XBTG target?
No. Version 6.3 dropped support for a set of legacy Magelis models that 6.2 still builds for, so a 6.3 installation cannot be treated as an equivalent test bed for an XBTG panel. Install 6.2 for this target, and confirm the project's target machine matches the physical model exactly before transferring.
When do I need Runtime Installer instead of the project download?
Use the project download when the target's transfer options bundle the runtime with the application. Use Runtime Installer, launched from the engineering software's Start menu, when the runtime must go on separately, and use its Recovery function to return a panel to Initial Start Mode after a bad or partial load.
What changes on the panel after the first successful download?
The initial download assigns the panel its IP address; from then on you can change the download communication type in the transfer settings. Verify on the physical panel that the initial start page is gone, the runtime starts, and the first project screen appears. A successful build on the PC proves nothing about what is actually on the panel.