IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing a Vijeo Designer Runtime Installer Target-Not-Found Error

HMI and touchscreens Published 6 min read

Short answer

When ping succeeds and a standalone runtime install completes but the application download fails at the runtime-installation stage, the fault is the launch path: close the Vijeo Designer session started through SoMachine and launch Vijeo Designer directly, then download over the same Ethernet connection. That single change fixed the reported XBTGT6330 installation. Treat the USB flash-full message as a separate storage branch.

On this page
  1. Two errors, two different faults
  2. Why the launch path is the thing to change
  3. The fix, step by step
  4. What ping and a standalone runtime install actually prove
  5. The flash-memory-full branch, with numbers
  6. What to record if the direct launch still fails
  7. Questions asked

Close the Vijeo Designer session you launched through SoMachine, start Vijeo Designer on its own, and download the application again over the same Ethernet cable and address. On the installation described here — Vijeo Designer 5.1 downloading to a Magelis XBTGT6330 — the panel answered ping and had just accepted a standalone runtime install over Ethernet, yet the application download stopped at the runtime-installation stage with a Runtime Installer error reporting the target machine as not found. Launching the editor directly made the identical transfer succeed, with no change to firmware, cable or terminal. The flash-memory-full message seen on a USB transfer is a separate branch: a storage question, not this fault.

Two errors, two different faults #

The panel in this case produced two different "target not found" messages under two different conditions.

  • Runtime Installer error, [Target] [XBTGT6330]: the transfer window showed connection in progress, switched to runtime installation in progress after several tens of seconds, then reported the target machine as not found and abandoned the transfer as a Runtime Installer error. Ping still worked, and a standalone runtime install had completed over the same cable shortly before.
  • Error 1800, connection error: with the Ethernet cable unplugged or a wrong destination address, the download failed immediately, reporting the defined target machine as not found and abandoning the transfer as a connection error.

Error 1800 is a reachability fault: restore the cable and the address, and the transfer proceeds. The Runtime Installer error with ping passing is not a reachability fault — it appears at the stage where the editor hands the built package to its runtime-installation workflow. That is the launch-path fault, and it is the one to fix first.

Why the launch path is the thing to change #

The SoMachine installation includes Vijeo Designer, but that software is independent of SoMachine and can be installed or updated on its own, as the SoMachine compatibility and migration documentation states. The editor reached through SoMachine and the editor started directly are therefore not guaranteed to be the same installation in the same state, and the runtime-installation stage is where the difference surfaced here.

Nothing in this symptom justifies a firmware change, a bootloader rewrite or a different cable: the panel had already proved it could receive and install a runtime over Ethernet. Change the one thing that differed — how the editor was started — before touching the terminal. If the project was created inside SoMachine, keep a .VDZ archive of it; that archive is the documented interchange format for moving a Vijeo Designer project between the integrated and standalone environments.

The fix, step by step #

A successful download restarts the panel, so put the machine in a state that tolerates the HMI going down for a minute before you start.

  1. Close the Vijeo Designer session opened through SoMachine.
  2. Launch Vijeo Designer directly from its own shortcut, and open the project — from its .VDZ archive if it lived inside SoMachine.
  3. Confirm the project target matches the physical panel, the XBTGT6330 here, and that the download destination is the panel address that answered ping.
  4. Build the project and clear build errors first, so a compilation fault cannot masquerade as a transfer fault.
  5. Download over Ethernet and watch the whole status sequence: connection in progress, runtime installation in progress, application transfer, panel restart.
  6. Confirm the application is on the panel after the restart. A closed transfer window is not success; the panel running the application is.

In the reported case, the first two steps alone were the fix: the same project, the same panel and the same cable then transferred and ran.

What ping and a standalone runtime install actually prove #

A ping reply proves IP reachability from the PC to the panel, and nothing above it. A completed standalone runtime install proves that one transfer workflow can reach the panel and write to it. Neither exercises the editor's full application-download sequence, which is why both can pass while the download fails.

Use those results as discriminators, not as clearance. The pattern of a panel that passes network checks while the transfer fails shows up on other platforms as well. Why an HMI transfer fails in initial start mode despite ping works through the same fault on another vendor's terminal. An HMI that is detected while the project download still fails shows the shape from the detection side. If the panel sits behind a router or VPN, the successful ping and runtime install have already cleared that path; where they have not, downloading a Vijeo Designer project to a remote HMI over VPN covers what the routing needs.

The flash-memory-full branch, with numbers #

On a USB transfer, the panel began loading from the stick and then reported flash memory full. The reported figures were 32 MB of panel flash, a 4 MB application and a 9 MB runtime.

The arithmetic says the message is not about nominal capacity. The install needs 4 MB + 9 MB = 13 MB, of the roughly 13 to 14 MB the case estimated, against 32 MB of flash: 32 − 13 = 19 MB of nominal headroom. A minimal one-page application, about 11 MB with its runtime, installed over the same route. The space actually free at install time therefore sat below 13 MB and at or above 11 MB, which means the flash already held data — an earlier application or runtime image — that the nominal figure hides.

Treat this branch as storage occupancy, not as a broken panel. Prove it the way this case did: install a minimal package to measure what fits, then clear or overwrite the stored application before loading the full one. The branch is independent of the Runtime Installer fault — the minimal package installed over USB while the full application later installed over Ethernet after the launch-path fix alone.

For a USB-equipped XBTGT, the documented file-system route is: plug an empty USB key into the PC, choose "File system" as the transfer medium, run Generate -> Transfer All to write the package to the key, then plug the key directly into the panel's port.

What to record if the direct launch still fails #

  • The full error text and the last stage shown in the transfer window, connection or runtime installation. The stage separates a network fault from an installer fault.
  • How the editor was launched, its exact version, and the panel's runtime revision. A documented cause of runtime faults is the development software version differing from the runtime version on the Magelis target, so both versions belong in the record.
  • The destination address and a ping result taken from the same PC at the same moment.
  • The package size, and whether a minimal package installs — the discriminator for the storage branch.

Those four readings split the next failure into network, version or storage, and each branch above carries its own decision.

Questions asked

Is it normal for the panel to return to its initial start page after a standalone runtime install?

Yes. A runtime-only installation puts system software on the panel but no application, so after the reboot the terminal waits in initial start mode with nothing to run. The page clears as soon as an application download completes and the panel restarts into it. If the panel still shows that page after a transfer the PC reported as successful, record it as a separate fault rather than repeating the download.

Do I need to run the standalone Runtime Installer before every application download?

No. The application download itself runs a runtime-installation stage when the panel needs it, and that is the stage where this fault appeared. The standalone Runtime Installer is for first setup or for recovering a panel with no usable runtime. It also works as a diagnostic: completing over Ethernet proves the path and the panel's installer, which is what pointed the fault at the editor session in this case.

The USB transfer reported flash memory full on a 32 MB panel. Does the panel need replacing?

Not on that evidence. A 4 MB application plus a 9 MB runtime needs 13 MB against 32 MB of nominal flash, so the message reflects the space actually free at install time, not the nominal figure. The reported case put the real limit between an 11 MB minimal package that installed and a 13 MB full package that did not. Clear or overwrite the stored application and retest before condemning the hardware.

Will launching the editor directly break the project's link to SoMachine?

No, provided you keep an archive. The .VDZ archive is the documented format for carrying a Vijeo Designer project between the SoMachine-integrated and standalone environments, so archive the project before you switch and import it again when you need the integrated setup. The download to the panel does not depend on the project staying embedded in SoMachine.

Could a version mismatch between the editor and the panel runtime cause this error?

It causes a related but different fault. A documented cause of runtime faults is the Vijeo Designer development version differing from the runtime version on the Magelis target, which shows up as a runtime mismatch rather than a missing target. If the direct launch does not clear your error, record both versions and align the panel runtime with the editor version using the vendor's runtime installer before downloading again.

Keep reading

  • Troubleshooting

    Fixing Vijeo Designer Error 1850 Secondary Drive Not Found

    Error 1850 on an HMIG3U appears because the project assigns a data file to a Secondary or Optional drive this target does not define; it supports only the Main drive with an SD card. Move the data file's location to Main, rebuild, and the download completes. No hardware switch enables the missing locations.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Transfer Fails in Initial Start Mode Despite Ping

    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.

    HMI and touchscreens

  • Troubleshooting

    Why a TP700 Comfort download fails 0132:000002 despite ping

    Error 0132:000002 with ping and Flash LED working means discovery succeeds but the transfer connection does not. Select the PG/PC interface entry for your adapter that ends in TCPIP rather than ISO, put the TP700 in transfer mode or allow remote transfer, give the PC a unique static address, and confirm no second device answers at 192.168.226.140. Those four checks clear the error in almost every case.

    HMI and touchscreens