IMDTouchKnowledge BaseShop main store

How-to

Open a legacy Vijeo Designer project in version 6.2

HMI and touchscreens Published 7 min read

Short answer

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.

On this page
  1. Read the refusal before you click anything
  2. Back up the original before the first conversion
  3. Convert one release at a time
  4. Worked example: converting a Vijeo Designer 4.6 project to 6.2
  5. Change the target to HMIGTO6310
  6. Configure Unitelway before you touch the transfer
  7. Pick one transfer route from the documentation
  8. Gate list before you download
  9. Questions asked

Open the project in the release the refusal message names — Vijeo Designer 4.7 in your case — compile and save it there, then walk the file up one release at a time until 6.2 opens it and builds it with no unresolved errors. Installing 6.2 converts nothing; the format conversion happens inside the intermediate editors. Only after 6.2 holds the project do you change the target to HMIGTO6310, configure Unitelway, and pick one documented transfer route for the download. The steps below keep that order and put a checkpoint at every stage.

Read the refusal before you click anything #

The error names the release the file must be opened in first, and that message is the only authoritative statement of where your project stands. The folder saying 6.1 and an operator remembering 6.1 do not establish which release saved the file. Your captured message routes the project through 4.7, so the file sits below the level 6.2 accepts directly.

Launch the editor explicitly from the installed programs, never by double-clicking the project file. With several Vijeo Designer releases installed on one station, the file association regularly hands an old project to a different release than the one you think you opened. Confirm the release in the editor's own version information, then write down the full refusal text before moving on.

Back up the original before the first conversion #

Copy the complete project folder or its existing archive to a separate working location and leave the original untouched from here on. Every completed conversion stage gets its own saved checkpoint, so a failure at any stage costs you one stage, not the project. If the file turns out to be damaged rather than merely old, the job changes: Magelis HMI project recovery in Vijeo Designer covers that path.

Convert one release at a time #

  1. Record the exact refusal text from 6.2, including the release it names — 4.7 for this project.
  2. Obtain that release from Schneider Electric or an authorized distributor, with the licensing it requires, and install the base release before any of its service packs; the install order matters, as install the HMI base software before the service pack shows for this editor family.
  3. Launch 4.7 explicitly and open the working copy. Confirm the whole tree loads — application, screens, variables, and the original XBTGT6310 target — before you save anything.
  4. Compile, then save the project under a new checkpoint name. Close it and reopen it in the same release to prove the checkpoint reads back.
  5. Open that checkpoint in the next release upward. If it opens, repeat the compile-save-reopen cycle there. If it refuses, its message names the release you still have to pass through — insert that release and repeat the cycle in it.
  6. Stop when 6.2 opens the project and a full build completes with no unresolved errors. Log conversion warnings separately from warnings that already existed in the application.

The manufacturer's upgrade guidance for this kind of move documents the pattern: a 4.6 project is imported into 6.1, compiled, exported, then imported into 6.2 — some chains carry an export between imports, not just opens and saves. Record the exact update level you run at every stage; 6.2 alone has service packs, one of them integrated into SoMachine v4.3, and an update nobody can name is a step nobody can repeat.

Worked example: converting a Vijeo Designer 4.6 project to 6.2 #

Inputs:

  • Starting release: 4.6, from the manufacturer's upgrade guidance for exactly this conversion.
  • Goal release: 6.2, the editor the HMIGTO6310 retarget needs.
  • Documented intermediate: 6.1.
  • Archive rule: one untouched original plus one checkpoint per completed stage.

Rule in words: one conversion stage is one import of the project into the next release in the chain, and the documented 4.6 chain adds a compile and an export at 6.1 before the final import.

Arithmetic:

  • Stages: 4.6 to 6.1 is 1 stage, 6.1 to 6.2 is 1 stage, 1 + 1 = 2 stages.
  • Imports: 1 into 6.1 + 1 into 6.2 = 2 imports.
  • Compiles and exports at 6.1: 1 compile, 1 export.
  • Archives: 1 original + 2 stage checkpoints = 3 archives on disk.

Result: two conversion stages, two imports, one compile-and-export at the intermediate, three archives.

Decision: with fewer than 2 stages the file never reaches the 6.2 format, and with fewer than 3 archives a failure in the second stage takes the whole conversion with it. At 2 stages and 3 archives, the conversion is safe to run and the target change can follow.

Change the target to HMIGTO6310 #

Format conversion and retargeting are two separate jobs. Keep the converted, original-target checkpoint untouched and make a copy for the HMIGTO6310 adaptation.

In the installed 6.2, look for HMIGTO6310 in the target selection. If it is not there, the release or update level does not carry it — fix that before substituting a near model. Target families in this editor sometimes have to be activated in the release before they appear; activating the XBTOT target family in Vijeo Designer 6.2 is the same class of problem. Then run the editor's target-change workflow and confirm the project properties show the new model.

Review everything the old terminal owned: screen layout, fonts, touch objects, scripts, alarms, and functions tied to terminal hardware. A clean format conversion proves nothing about feature equivalents on the new panel. Build until no target-related error remains, and leave the communication settings for the next section so any new error traces to a single change.

Configure Unitelway before you touch the transfer #

Two connections are involved and they are not the same one. Unitelway is the link between the terminal and the controller, configured inside the project; the transfer is the link between your engineering station and the terminal. Set the driver first.

Record from the working project and the controller configuration: driver, equipment, station addressing, serial settings, and the port assignment. Confirm Unitelway appears for the HMIGTO target in your installed release; if it does not, the release level is what you fix, not the wiring. Check the HMIGTO6310 documentation for which port carries that driver and what electrical interface it needs — a connector's shape tells you nothing about its function. Configure the equipment and terminal port, confirm the variables reference that equipment and the intended addresses, and preserve the working values unless the new hardware requires a documented change.

Pick one transfer route from the documentation #

Three candidates exist for this terminal: the XBTZG935 adapter, Ethernet over the RJ45 jack, and a file-system transfer from USB storage. The documentation decides between them, not the connectors. Verify what the XBTZG935 connects and which transfer mode expects it before you plug it in; do not pick USB because an accessory has a USB plug, or Ethernet because the jack is RJ45.

Configure exactly one route. For Ethernet, read the terminal's network settings and set a reachable destination in the editor. For the adapter or a direct cable, use the documented cable and workstation driver. For removable media, follow the editor's file-system deployment and the terminal's load procedure. One safety note: schedule the download for a moment when the machine is safe without a live display, because the terminal's screens go away while the transfer runs. And a terminal that answers on the cable is not the same as a terminal accepting the project — why an HMI is detected but the project download fails is the document to have open if the download stalls.

Gate list before you download #

  • 6.2 opens the project and a full build finishes with no unresolved errors.
  • The untouched original, the converted checkpoint, and the HMIGTO6310 copy all exist as separate archives.
  • The target selection reads HMIGTO6310 exactly, and every warning from the target change has been read, not suppressed.
  • The Unitelway driver, equipment, addressing, and port match the controller side, and the variables point at that equipment.
  • One transfer route is chosen from the terminal documentation, with its cable or media prepared.
  • The machine is in a state that tolerates the display going blank for the transfer.

Run the download only when all six hold.

Questions asked

The project folder says 6.1. Why did 6.2 refuse to open it?

Because the folder name and anyone's memory of the release are not evidence of the saved format. The refusal message is: it states the earliest release the file can be opened in, and 6.2 pointing you at 4.7 means the file was saved below what 6.2 reads directly. Act on the message and ignore the label.

Can I go straight from the named release to 6.2 and skip everything between?

Try it, but let the editor decide rather than a guess. One field report has a 4.5-era project, updated and saved in 4.7, opening straight into 6.2 afterwards, while the documented 4.6 chain runs through 6.1 with a compile and an export between the two imports. If 6.2 refuses your saved file, its message names the release you still have to pass through.

Where does an old release like 4.7 come from today?

Discontinued releases disappear from public download portals, and the documented route in that case is the vendor's support organization, which can supply the installer for a conversion like this. Keep the installer and its update level on record with the project archive, because a conversion you cannot reproduce is worthless at the next migration.

How do I confirm what the XBTZG935 adapter is for?

The terminal's hardware documentation and the transfer chapter of the editor documentation state the adapter's purpose and the transfer mode that expects it. Read both before connecting anything, and match the editor's transfer setting to the mode the documentation names for that adapter. The part marking alone never settles it.

Do I configure Unitelway to download the project?

No. Unitelway runs between the terminal and the controller; the download runs between your engineering station and the terminal. A converted project with a correctly configured driver still fails over the wrong transfer route, and that failure often looks like a Unitelway problem because it appears at the same moment. Configure the driver, then the route, and never edit both at once.

The application predates Vijeo Designer. Is there still a ladder?

An XBTL1000 application is a different conversion problem with its own route: the vendor ran a dedicated conversion program for migrating those applications to Vijeo Designer. Ask Schneider Electric or its distributors what the current route is, instead of pointing Vijeo Designer releases at an XBTL1000 file.

Keep reading

  • 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

  • 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

  • Troubleshooting

    When an HMI project fails to open: recovery and backup

    A Vijeo Designer project that no longer opens is recovered from the editor's local project storage on the PC, not from the panel. Save never creates a portable backup: close the project in the manager, export it and keep that export as a zip after every working session, then prove the zip by importing it into a clean editor and building.

    HMI and touchscreens

Converting a version 5.10 MER file for FactoryTalk View 7.0