Checklist
Checking HMI engineering software before a panel replacement
Short answer
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.
On this page
- What is the latest version of Vijeo Designer?
- Is Vijeo Designer 6.2 still supported?
- Can a newer HMI panel be added to Vijeo Designer 6.2?
- How do I check the installed engineering software version?
- How do I confirm the replacement panel works with my software?
- What should I verify before staying on Vijeo Designer 6.2?
- What does migrating to Operator Terminal Expert involve?
- What is the final checklist before ordering the replacement?
- Questions asked
Vijeo Designer's current line is version 6.2, and its newest service pack is SP12 — version 6.2.12, released 26 January 2024. The line is still maintained, but the newer HMI hardware generation is engineered in Operator Terminal Expert (OTE) and cannot be added to Vijeo Designer by installing an update. That split is the whole compatibility question when a panel fails or ages out: your installed engineering software decides which replacement panels you can build for, not the other way round. This checklist walks the check in the order you meet it — current version, support status, target availability, the replacement's documented software requirement, and the scope of a migration if OTE is what the new panel requires.
What is the latest version of Vijeo Designer? #
Version 6.2 is the current line, and its newest service pack is SP12, version 6.2.12, released on 26 January 2024, so any workstation still on an earlier service pack is behind by a countable number of updates. The number comes from the vendor's release listing for the 6.2 line. Service packs are cumulative and install over the 6.2 base: you must have 6.2 installed first, and you can go straight from any earlier service pack to the latest without installing the ones in between.
Worked example. A workstation found running 6.2 SP4 (example input) is 12 − 4 = 8 service packs behind. The cumulative rule makes that a single update, SP4 straight to SP12, not eight installs. Decision: bring the engineering station to SP12 before any panel work begins, and archive the project exactly as SP4 built it before the update, so the pre-update state survives whatever happens next.
Is Vijeo Designer 6.2 still supported? #
Yes, for now: the 6.2 line is still maintained, but the vendor expects it to become obsolete, and the newest HMI models support only Operator Terminal Expert, so there is no future Vijeo Designer release to wait for. Maintained means downloadable and serviceable, not growing — no service pack of the 6.2 line will add the OTE hardware generation. The vendor's compatibility FAQ adds a second fact worth planning on: version 6.3 no longer supports certain legacy HMI models that version 6.2 supports, so even inside the same software family a newer release can remove targets instead of adding them. Decision: treat 6.2 SP12 as the working release for existing targets, keep the hardware refresh and the engineering-software maintenance as separate planned activities, and expect every new panel model to arrive as an OTE target only.
Can a newer HMI panel be added to Vijeo Designer 6.2? #
No, not by updating: a target panel can be built only when the engineering tool ships a target definition for it, and the newer hardware generation that requires Operator Terminal Expert will not appear in Vijeo Designer 6.2 at any service pack. The target definition carries more than screen size — it fixes runtime capabilities, communications resources, memory assumptions and the objects the project may use. Selecting a look-alike target to force a compile gives you either build failures or, worse, a project that builds and still misrepresents the hardware. Some target families must be activated in the tool before they can be selected at all; activating the XBTOT target family in Vijeo Designer 6.2 is the documented example. Decision: when the replacement's documentation names Operator Terminal Expert, its target is not in Vijeo Designer, full stop.
How do I check the installed engineering software version? #
Read the full version and service pack from the software's product-information display, write it down before opening the production project, and expect 6.2 with a service pack when the station is current. Then protect the project before you touch anything:
- Record the displayed version and service pack verbatim, before opening or saving the production project.
- Work on a controlled duplicate: opening and saving a project in a newer release moves its format forward, and the tool has no save-back to an older release.
- Keep the original archive untouched, and note which software version last produced a successful download to the terminal.
- If no source project exists any more, the fallback is reading the old HMI program before panel replacement, not a rebuild from screenshots and memory.
How do I confirm the replacement panel works with my software? #
Read the replacement panel's own documentation: it must name Vijeo Designer compatibility for your exact target, or it names Operator Terminal Expert, and that single statement decides whether you are buying a drop-in replacement or a migration. The documentation, not the catalogue photo, is the compatibility statement. Check it this way:
- Match the target designation in the project against the terminal nameplate, character for character; a mismatch means the project is not a verified backup of what actually runs.
- Documentation names Vijeo Designer and lists your exact target: drop-in path, proceed to the stay-and-verify checks.
- Documentation names Operator Terminal Expert: a migration — count the re-engineering work, not just the panel swap.
- Documentation names neither: obtain the compatibility statement in writing before ordering, and do not substitute on appearance.
The general rule — each manufacturer's panels build only in that manufacturer's matching tool generation — is laid out in which HMI software works with which HMI panel hardware.
What should I verify before staying on Vijeo Designer 6.2? #
Compile a controlled copy of the project with no functional edits and expect a clean build for the exact target: that clean build, plus a communications check on the terminal, is your evidence the Vijeo Designer path still holds. Do it in this order:
- Build the duplicate in the release you will keep, and compare the diagnostics against the last accepted build record.
- Record the target, controller communications settings, tag sources, alarm configuration, recipes, scripts, security behaviour and any removable-storage dependency.
- Verify representative operator functions and communications with the machine in a safe state: a verification download can write to the process, so treat it as a controlled intervention, not a file transfer.
Decision: staying on 6.2 is the correct maintenance choice while your target is in the supported list, and it stops being one the day the only replacement panel you can buy is no longer a 6.2 target.
What does migrating to Operator Terminal Expert involve? #
A full re-engineering check: OTE is a separate environment, not a new version of Vijeo Designer, so installing it converts nothing by itself and every function in the running application needs a mapped destination and a test. Inventory before you rebuild:
- Screens: navigation, pop-ups, numeric entry, status indication, alarms, trends, recipes, user access and the maintenance pages actually used.
- Communications: controller endpoints, tag addressing, data types, read/write direction, scaling and loss-of-communications indication — validating HMI variables during a software migration covers the field-level checks.
- Runtime-dependent behaviour: scripts, macros, alarm acknowledgement, retained values, startup actions and security state.
- Import or recreate only through documented paths, and treat a completed import as the start of validation, never as proof of equivalence.
Accept the migration on data semantics, not screen appearance: a value can display correctly while writing to the wrong address, with the wrong scaling, or under the wrong access level. Where the rebuild outweighs the application, the same decision point allows replacing the terminal with industrial panel PCs running PC-based HMI software instead.
What is the final checklist before ordering the replacement? #
Six items, all confirmed before the order: current software version recorded, target matched character for character, the replacement's software requirement named in its documentation, a clean unedited build, communications verified, and a migration scope counted if OTE is required.
- Version recorded: 6.2 plus service pack, SP12 (6.2.12) if the station is current.
- Target matched: project designation equals the nameplate designation, character for character.
- Requirement named: the replacement's documentation names Vijeo Designer with your exact target, or names Operator Terminal Expert.
- Build proven: the controlled duplicate compiles clean in the release you keep.
- Communications proven: representative functions verified against the controller on the terminal.
- Scope counted, OTE path: screens, tags and scripts inventoried, each with a mapped destination and a test.
Ordering before these six are confirmed is how a panel replacement turns into an unplanned application rebuild. For the part-number side of the same decision, work through how to verify an obsolete HMI replacement before ordering.
Questions asked
Which Windows versions run Vijeo Designer 6.2?
The vendor's release page lists Windows 10 and Windows 8 for the 6.2 line. Windows 10 has been supported officially since service pack SP6, and SP6.1 improved that support for both 32-bit and 64-bit Windows 10 Pro. A workstation stuck on an older service pack is therefore an operating-system question as much as a software-version question.
Can I save a project back to an older service pack after testing it?
No. The tool does not save a project back to an older release, so once the project has been opened and saved under SP12 it will not reopen on a workstation still running an earlier service pack. Keep the pre-update archive untouched, run the test on a controlled duplicate, and record which software version last produced a successful download.
What is the XBTOT target family?
XBTOT is a target family inside Vijeo Designer 6.2 that must be activated in the engineering tool before those panels can be selected as a project target. If your replacement is in that family, activation in the installed software, not a version update, is what makes it selectable in the target list.
Will upgrading Vijeo Designer drop support for my old panel?
Possibly, and it is documented: the vendor's compatibility FAQ states that version 6.3 no longer supports certain legacy HMI models that version 6.2 supports. Before any upgrade, confirm your exact target is still in the supported list of the release you are moving to, and keep the installation that builds your target today.
How do I protect the project while I test the update?
Vijeo Designer 6.2 includes an auto backup feature that copies the project automatically, and configuring it before any update work means every save leaves a recoverable copy. Combine that with a controlled duplicate of the whole project folder and an original archive kept read-only, so a failed test costs time rather than the application.