IMDTouchKnowledge BaseShop main store

Troubleshooting

Which Vijeo Designer version edits an XBTG5230 project

HMI and touchscreens Published 5 min read

Short answer

Edit an XBTG5230 application with a licensed Vijeo Designer release from 4.5 through V5.0 SP2 — V5.0, all service packs included, is the last line supporting the XBTG series (Schneider Electric FAQ FA280491). Version 4.2.2 cannot load a 4.5 project and releases after V5.0 cannot select the target, so the fix is the release window, not a cable or terminal fault.

On this page
  1. The support boundary sits at V5.0
  2. Why 4.2.2 fails before the terminal is involved
  3. The version interval, with the arithmetic
  4. Install the release, keep the license legitimate
  5. Protect the source before you edit
  6. When the terminal itself is the end-of-life item
  7. Decision summary
  8. Questions asked

An XBTG5230 application is edited with a licensed Vijeo Designer release from 4.5 through V5.0 SP2. V5.0, including every service pack in its line, is the last release that supports the XBTG series, per Schneider Electric's compatibility entry FAQ FA280491 — so nothing newer can select the target, and a 4.2.2 workstation cannot load a project built in 4.5 at all. The fix is the software release window, not a cable, a driver or the terminal.

The support boundary sits at V5.0 #

Schneider Electric's compatibility entry FAQ FA280491 names Vijeo Designer V5.0, all service packs included, as the last version that supports the XBTG series. What that boundary means in practice:

  • Every release that carried XBTG targets still carries them through the V5.0 line, service packs included.
  • The V5.0 service pack line ends at SP2, which makes V5.0 SP2 the newest corrected build that compiles for this terminal.
  • Every release after V5.0 drops the family from its target catalog — that is why the XBTG5230 entry is missing from 6.2.
  • Release 6.2 catalogs newer families instead; XBTOT is one of them, and activating the XBTOT target family in Vijeo Designer 6.2 is the procedure for those panels, not a route back to XBTG.

The family-by-family rule holds across every manufacturer's HMI catalog; the same question is answered panel family by panel family in which HMI software works with which HMI panel hardware.

Why 4.2.2 fails before the terminal is involved #

A Vijeo Designer project opens in the release that created it or in a newer release, never in an older one. A project built in 4.5 therefore fails to load on 4.2.2 before any transfer is attempted, so the cable, the transfer interface and the terminal are not where this fault lives. Separate the failure stages before touching hardware:

  • A saved project will not open on the computer: release or project-file compatibility.
  • The project opens but the terminal cannot be reached: transfer interface, cable, connection settings or workstation driver.
  • The terminal answers but its content will not come off: retrieval capability and what the application stored.
  • The terminal is absent from the target list: engineering release too new for the family.

Your case fails at the first stage, and the version interval below is the fix for it.

The version interval, with the arithmetic #

Set the two bounds, then test every candidate against both:

  • Floor — the release the project was built in: 4.5. A tool below the floor cannot load the file.
  • Ceiling — the last release that still offers the XBTG target: V5.0 SP2.
  • Usable interval — 4.5 through V5.0 SP2: releases 4.5 and 4.6, and the V5.0 line with any service pack through SP2.

Worked check on the two candidates that fail, for opposite reasons. The installed 4.2.2 sits below the floor by 4.5 − 4.2.2 = 0.28 release units, so the project file will not load. The newer 6.2 clears the floor but sits beyond the ceiling by 6.2 − 5.0 = 1.2 major versions, so the XBTG5230 target cannot be selected at all. Both are version facts, not transfer faults.

Release Floor: loads a 4.5 project Ceiling: offers the XBTG target Verdict
4.2.2 No, 0.28 below the floor Yes Reject
4.5 Yes, matches the build release Yes Accept
4.6 Yes Yes Accept
V5.0 SP2 Yes Yes, the last release that does Accept, preferred
6.2 Yes No, 1.2 major versions past Reject

The decision from the numbers: standardize the maintenance workstation on licensed V5.0 SP2 — the newest release inside the interval — or on 4.5 where that environment already exists with a valid license.

Install the release, keep the license legitimate #

  • Ask Schneider Electric or an authorized distributor for the release that supports XBTG, together with its service packs; the current package cannot help this terminal.
  • Check the operating system and the transfer drivers the chosen release documents, and prepare the workstation to match — tooling of this era expects the environment it was built for.
  • One compliance rule: V5.0 being old does not put it in the public domain. Media passed around informally grants no use rights, and an unlicensed engineering tool on a production machine is an exposure at any release age.

Protect the source before you edit #

  • Recover the original project archive from the machine documentation, maintenance backups or the machine builder before any software is installed.
  • Keep one untouched copy in its original format: opening and saving in a different release can update the project's storage format, so a converted file must never become the only copy.
  • Work on a full copy — screens, images, fonts and communication configuration together — and record every conversion prompt the tool raises.
  • Do not download to the terminal until a documented way back to the application now running on it exists.
  • If no archive exists anywhere, recovering a Magelis HMI project with Vijeo Designer with a release from the interval is the fallback path.

When the terminal itself is the end-of-life item #

XBTG-era tooling dates to the mid-2000s, and at some point the station, not the software, is what holds the machine back. Three honest paths:

  • Maintain as built: licensed V5.0 SP2 on a prepared workstation, editing the 4.5-era application for as long as the terminal runs.
  • Migrate the application: the project must be re-targeted to a family a current release supports, and opening a legacy Vijeo Designer project in version 6.2 is where that path starts.
  • Replace the station: the operator interface moves to industrial panel PCs at the machine, with the control logic untouched.

Decision summary #

  • Workstation at 4.2.2, project at 4.5: 4.2.2 is below the floor and cannot load the file; install a licensed release inside the interval, V5.0 SP2 preferred.
  • A licensed 4.5 environment already exists: use it, because it matches the release the project was built in.
  • Only a release newer than V5.0 is available: it is past the ceiling and cannot select XBTG5230; re-targeting a working project just to edit it is the wrong trade.
  • No editable source exists anywhere: chase the archive and the machine builder first, then documented retrieval with an in-interval release.
  • The terminal is the end-of-life item: migrate the application to a current target or to a PC-based station, and treat it as a hardware project rather than a version choice.

Questions asked

Why is the XBTG5230 target missing from Vijeo Designer 6.2?

XBTG support ended at V5.0, so every later release drops the family from its target catalog. Release 6.2 lists newer families instead — XBTOT is one, and it must be activated there before use. No service pack or activation option puts XBTG back into 6.2; editing this terminal belongs to the 4.5-through-V5.0 SP2 window.

Is XBTGT5230 the same terminal as XBTG5230?

No. XBTG and XBTGT are different Magelis series, and XBTGT5230 is a separate reference, not a spelling variant. Select the exact designation from the terminal's identification label as the engineering target; a project compiled for the wrong series produces a download the hardware will not run.

Can I use a copy of V5.0 from another site?

Only if that copy carries a valid license for your workstation. Media passed around informally, by email or from unofficial downloads, grants no use rights whatever the release's age. Get the installation files, the service packs and the license through the manufacturer or an authorized distributor.

Will installing V5.0 recover the project if we never saved it?

Not by itself. What runs on the terminal is a runtime application, and a backup pulled from the terminal is not automatically editable source. Search the machine documentation and ask the machine builder first; documented retrieval with a compatible release yields source only if source was stored on the panel.

Which service pack should the V5.0 installation carry?

SP2. Every V5.0 service pack keeps XBTG support, so the base release works too, but SP2 is the final corrected build of the last XBTG-capable release, and it is the one to standardize the maintenance workstation on.

Keep reading

  • How-to

    Open a legacy Vijeo Designer project in version 6.2

    Open the project in the release the error names — Vijeo Designer 4.7 in this case — compile and save it there, then climb release by release until 6.2 opens and builds it. Only then change the target to HMIGTO6310, configure Unitelway, and choose one documented transfer route.

    HMI and touchscreens

  • Checklist

    Checking HMI engineering software before a panel replacement

    Vijeo Designer's current line is 6.2, ending at service pack SP12 (version 6.2.12, 26 January 2024). Newer HMI panels are engineered only in Operator Terminal Expert and cannot be added to Vijeo Designer by updating it. Before ordering a replacement, record your installed version, match the target designation exactly, and let the replacement's documentation decide between a drop-in and a migration.

    HMI and touchscreens

  • How-to

    Activating the XBTOT Target Family in Vijeo Designer 6.2

    Enter upgrade code VJDHTGTOPV62M in the full Vijeo Designer 6.2 edition under Help > About > License > Upgrade, restart the software, and XBT OT appears in the new-project target list. Vijeo Designer Lite 1.2 or 1.3 cannot list or unlock the family.

    HMI and touchscreens

Which SoMachine version configures an HMISCU controller and HMI