How-to
Using Vijeo Designer 6.2 to program an HMISTU series HMI
Short answer
HMISTU terminals sit outside the Easy HMI offer that Vijeo Designer Basic programs, and no communication setting adds them. Install regular Vijeo Designer 6.2, take it to the SP12 service pack level, confirm the complete terminal reference appears in the target list, then build and transfer.
On this page
Program an HMISTU terminal with regular Vijeo Designer 6.2, not with Vijeo Designer Basic. Basic is the engineering tool for the Easy HMI offer, and its 1.2 documentation lists exactly two supported families, HMIGXU and HMIET6; the HMISTU series is outside both, and no cable, driver or address setting adds a target to the software. The sequence that works: identify the edition on the engineering PC, install Vijeo Designer 6.2 and take it to the SP12 service pack level, confirm the terminal's complete reference appears in the target list, then build and transfer. One documented trap sits in the middle: 6.2 SP11 hides the HMISTU655 and HMISTU855 targets and raises error 1800, so do not commission on it.
Why Basic cannot program an HMISTU terminal #
Vijeo Designer Basic and regular Vijeo Designer are separate products with separate installers and separate target lists. The Basic 1.2 documentation supports two HMI families: HMIGXU and HMIET6. An HMISTU reference therefore never appears in Basic's target selection, and the software cannot generate an application for hardware it holds no target definition for.
A target definition ships with the engineering software. A reachable panel, a good transfer cable and a correct IP configuration only matter after a valid target is selected, which is why connection troubleshooting inside Basic cannot fix this. The blocker is the edition, not the link.
| What the workstation shows | What it means | What you do |
|---|---|---|
| Vijeo Designer Basic installed | Wrong edition for HMISTU | Install regular Vijeo Designer 6.2 |
| Vijeo Designer 6.2, exact reference missing | Service-pack or release gap | Update the service pack, re-check the list |
| Vijeo Designer 6.2, exact reference listed | Software gate passed | Build and transfer |
Record the terminal's complete reference #
- Read the identification label on the terminal and record the complete product reference. "HMISTU" alone is a family name, not a target.
- Copy every character of the reference. The suffixes carry the display size and hardware variant the target definition is built around.
- Use that string verbatim when you search the target list in the engineering software.
Selecting a near model because it looks close produces a project with the wrong display and hardware assumptions. The complete reference, not the family name, is what the target list matches, and it is what Schneider Electric's own FAQ reads off the back sticker when it discusses these targets.
Install Vijeo Designer 6.2 with the current service pack #
- Get the base 6.2 installer from Schneider Electric or an authorized distributor. The manufacturer and its distributors are the legitimate source for the software and every update to it.
- Install the base release first and the service pack second: installing the HMI base software before the service pack is the order that works, and reversing it leaves you debugging a broken install instead of a panel.
- Bring the line to SP12. Schneider Electric documents, in FAQ FA240229, that 6.2 SP11 does not offer the HMISTU655 and HMISTU855 targets and reports error 1800 when a project references them. At SP12 the targets are available again, so SP12 is the level to commission on.
- Open the product information after installation and read two lines: the version with its service pack, and the license state. If the license reads trial or unactivated, complete the activation through the process documented for that release before you rely on the workstation.
Stay on 6.2 for this terminal. Vijeo Designer 6.3 no longer supports legacy HMI models that 6.2 supported, so a newer major version is not a safer home for an HMISTU project. The 6.2 line has form here too: the XBTGT1130 target disappeared from the Target properties menu after an upgrade to 6.2 SP3.1, so a vanished target after a service pack is a documented pattern, not evidence of a failed panel.
Confirm the target inside the software #
- Start a new project, or open a working copy of an existing one, and go to target selection.
- Search for the complete reference you recorded from the label.
- If it is absent, treat that as a software question first: an HMI model missing from the programming software is a supported-list problem to resolve before you spend time on cables and drivers.
- When the reference is listed, select it and configure the controller driver the project needs, following the target's own documentation.
Build and transfer to the terminal #
A transfer replaces the application the operator is using while the PLC keeps controlling, so schedule the swap rather than interrupting a running shift.
- Keep an untouched copy of any project already running on the terminal.
- Run the build. The build compiles the screens and configuration into the program that executes on the panel; a clean build, with zero blocking errors, is the gate to transfer, not proof that live controller data behaves.
- Configure the transfer interface documented for the target, connect the engineering PC, and start the download from the software.
- Watch the terminal come up on the intended start-up screen, then test navigation and displayed values before anyone issues operator writes from it.
- After any edit, repeat the build and the download: why an HMI edit needs a new runtime download explains what actually has to travel to the panel.
Worked example: an HMISTU855 on the bench #
The label on the back of the terminal reads HMISTU855, and the engineering PC has Vijeo Designer Basic 1.2 installed.
- Basic 1.2 documents 2 supported families: HMIGXU and HMIET6. HMISTU families on that list: 0. Selectable HMISTU855 targets in Basic: 0. Stop, because no setting changes this number.
- Install regular Vijeo Designer 6.2 base, then SP12: 2 installs, in that order.
- On 6.2 SP11, selectable HMISTU855 targets: 0, with error 1800 on any project that references it, a documented software gap rather than a panel fault. On SP12: 1 selectable target.
- Build the project against that target: 0 blocking errors, so transfer proceeds. The terminal boots the new application, and navigation and displayed values are verified before operator writes.
Decision: Basic never programs this terminal. Vijeo Designer 6.2 at SP12 does, with the complete reference selected and a clean build behind the transfer.
Questions asked
Can I make Vijeo Designer Basic see an HMISTU by changing the driver or the IP settings?
No. A target definition ships with the engineering software; communication settings only control how an already selected target talks to the controller. Basic has no HMISTU target to select, so there is nothing for a cable or an address to reach. Install regular Vijeo Designer 6.2 and select the terminal there.
Vijeo Designer 6.2 SP11 reports error 1800 for my HMISTU655. Is the panel faulty?
No, the software level is the issue. Schneider Electric documents that 6.2 SP11 does not offer the HMISTU655 and HMISTU855 targets and raises error 1800 on projects that reference them, matching the part number on the sticker on the back of the panel. Update the 6.2 installation to the SP12 service pack level and reopen the project before you suspect the terminal.
Should I move straight to Vijeo Designer 6.3 instead?
Not for an HMISTU without checking. Schneider Electric documents that 6.3 no longer supports certain legacy HMI models that 6.2 supported. If your complete reference appears in the 6.3 supported list, the move is fine; if it is one of the removed models, 6.2 stays the engineering environment for that terminal. The supported-target list of the exact release decides, not the version number.
Do I need a separate license for regular Vijeo Designer?
Treat Basic and regular Vijeo Designer as separate products with separate entitlements. Get the 6.2 installer and its service pack from Schneider Electric or an authorized distributor and read the licensing terms that ship with that release. After installation, the license state in the product information is what counts: if it reads trial or unactivated, complete the documented activation before commissioning from that workstation.
Can I reuse the screens I built in Basic?
Only through a documented import or conversion path, and only on a working copy with the original kept untouched. Read every conversion message, because opening a project verifies the file, not how objects and communication settings behave on the new target. Where no supported path exists for your content, rebuild the screens in the 6.2 project instead of renaming files.