IMDTouchKnowledge BaseShop main store

Troubleshooting

How to get Vijeo Designer Basic 1.1 from the official source

HMI and touchscreens Published 8 min read

Short answer

The shared address is cut off where the file name should continue, so it cannot fetch anything. Recover the package from Schneider Electric's download area by searching "Vijeo Designer Basic" and opening the V1.1 entry, an EXE of about 370.8 MB documented in SEVD-2020-133-02, then confirm the exact HMIGXU target and PLC driver before installing.

On this page
  1. Why does the shared Vijeo Designer Basic 1.1 link not work?
  2. Where do you download Vijeo Designer Basic 1.1 officially?
  3. How do you check the package before you install it?
  4. What stops the download even from the right page?
  5. Which HMI models does Vijeo Designer Basic 1.1 support?
  6. Which PLC protocols should you verify before building a project?
  7. How do you install it without breaking existing projects?
  8. What if version 1.1 is no longer on the download page?
  9. Questions asked

The link passed around for Vijeo Designer Basic 1.1 is cut short: the value that names the file ends in an ellipsis, so the vendor's file service cannot resolve a package and the page fails no matter how often it is opened. The fix is to go to Schneider Electric's download area on se.com, search the exact product name, and open the V1.1 release entry there. Before installing, confirm the exact HMIGXU terminal and the PLC driver the project needs, because the editor's protocol list is capability, not proof of a working connection.

The address in the shared message is cut short: the query value that names the file ends in an ellipsis, so the vendor's file service cannot resolve a package and the page returns nothing usable.

The address points at the released-software file service with two query values: p_enDocType=Software - Released and a p_File_Name whose visible text stops at VijeoDesig.... The three dots are a truncation, not part of the address, so every copy of it requests a file name that does not exist. The service answers with an error page, a search page, or silence.

Decision: do not repair the address character by character. A file name you reconstructed can point at a build you did not choose, and a matching file name alone proves nothing about the bytes behind it. Treat any address ending in ... as a pointer to the portal, never as a download.

Where do you download Vijeo Designer Basic 1.1 officially? #

Search Schneider Electric's download area on se.com for the exact text "Vijeo Designer Basic" and open the V1.1 release entry; the package is an EXE of about 370.8 MB, with a companion release document, SEVD-2020-133-02.

Work the portal, not the copied address:

  • Open se.com, go to the Downloads area, and use its search; the product range page for Vijeo Designer HMI software indexes the software family.
  • Search the exact name "Vijeo Designer Basic" rather than the family name alone.
  • Open the V1.1 entry and read the listing fields: name, version, format EXE, size about 370.8 MB.
  • Download the release document SEVD-2020-133-02 (PDF, 247.7 KB) and read the supported targets and notes before the installer runs.

Take the package only from this area. Third-party pages offering the same file name on request are not the vendor's channel, and a matching file name is not evidence of matching content. One source, the vendor's download area; everything else is a copy of unknown integrity.

How do you check the package before you install it? #

Confirm four things on the release entry and the downloaded file: the name contains Basic, the version reads 1.1, the format is EXE, and the size is close to the published 370.8 MB.

The checks, in order:

  • Name: "Vijeo Designer Basic" in full; a similarly named editor is not interchangeable with this one.
  • Version: 1.1; target availability and project compatibility follow the release.
  • Format and size: EXE, about 370.8 MB as the listing states it.
  • Authenticity: where the vendor publishes a checksum or signs the package, validate it with the stated method before running anything.

Worked size check, with illustrative local numbers. The listing states decimal megabytes, so the expected count is 370.8 MB × 1,000,000 B/MB = 370,800,000 bytes. Windows properties reports mebibytes, so a file showing 272 MB there is 272 MiB × 1,048,576 B/MiB = 285,208,704 bytes, about 285.2 MB decimal. The ratio is 285.2 ÷ 370.8 = 0.77, a transfer that stopped at 77 percent. Delete that file and download it again from the same entry; do not resume or hand-patch a package of this size.

Decision: compare byte counts, not the "MB" labels, and treat any file well short of the listed count as a broken transfer.

What stops the download even from the right page? #

Once the address is right, four local layers can still break the transfer: session and browser settings, proxy or inspection, endpoint security, and write permissions; the failing layer decides the fix.

Symptom Likely stage Decisive check
The page does not open Address or network path Open the vendor's software area directly and search by name.
The page opens but no file starts Session, redirect, browser controls Sign in, allow the site's required functions, watch the download panel.
The transfer starts then stops Proxy or security inspection Compare the local byte count with the listing.
The file disappears after landing Endpoint security Read the security product's quarantine record for the event.
The installer will not launch Package, rights, or OS support Re-check size and publisher, then the release's OS requirements.

The sequence that separates the layers:

  1. Record the terminal's full catalog number and the editor version on the workstation before changing anything.
  2. Open the vendor's download area directly, not through the truncated address.
  3. Download in a normal signed-in browser session, with the site's required functions allowed.
  4. Watch the browser's download panel for a blocked redirect or a transfer error.
  5. Save to a folder the signed-in user can write to, not a browser cache or a network share.
  6. Compare the finished byte count with the listing and validate the checksum or signature where one is published.
  7. If security software removed the file, use that logged event to request an approved exception instead of re-downloading on repeat.

Changing browsers cannot fix a truncated address, and downloading again cannot fix an operating-system mismatch: match the fix to the layer that failed.

Which HMI models does Vijeo Designer Basic 1.1 support? #

Vijeo Designer Basic 1.1 serves the low-end GXU terminals; the models listed with the release are HMIGXU3500, HMIGXU3512, HMIGXU5500 and HMIGXU5512, so read the full catalog number from the nameplate before you commit.

HMIGXUxxxx in a datasheet or a forum post is a family placeholder, not a target. Read the complete catalog number from the terminal's nameplate or from the existing project, then prove the target inside the editor: create a throwaway project and select that exact catalog number. If the exact number is not offered, stop; this editor does not serve that terminal, and no download effort changes that.

Decision: target first, download second. An editor release is only correct for the terminals its target list actually contains.

Which PLC protocols should you verify before building a project? #

Treat EIP, S7 TCP, Profibus, Modbus and Modbus TCP as the protocol families commonly cited for this editor, then verify the one you need in the installed editor's driver list for your exact target before building the project.

That list is an editor-level capability claim, not proof that a given terminal exposes the port or that a given PLC variation is covered. Check three layers:

  • Physical: the terminal has the Ethernet, serial or fieldbus interface the driver needs.
  • Protocol: the driver list for your exact target contains the protocol and the PLC family.
  • Application: addresses, data types, station identifiers, byte order and access rights match the PLC configuration.

Profibus is not implied by the presence of Ethernet protocols; a fieldbus driver needs its own physical interface. Test the link before engineering the screens, following the same flow as simulating a Basic HMI against a real TM172 HVAC controller, so a driver problem surfaces before it is buried under graphics.

Decision: if any of the three layers fails, this editor is the wrong choice for that controller, and the answer is a different target or driver path, not persistence.

How do you install it without breaking existing projects? #

Back up the application and any exported archive first, then install the base software before any service pack, because opening a project in a different editor or release can start a conversion the older installation cannot reverse.

  • Close other engineering applications and back up the HMI application plus any exported archive.
  • Read the release entry's operating-system support and prerequisites before running the EXE.
  • Where a release includes a service pack, follow the rule of installing the HMI base software before the service pack; the pack upgrades a base, it does not stand alone.
  • Run the installer with the rights your site's workstation policy requires.
  • Launch the editor and read the about screen: it must identify Vijeo Designer Basic and version 1.1.
  • Record the installed release and keep the installer with the project backup so the workstation can be rebuilt unchanged.

Decision: do not open an existing project until the about screen reads correctly; a conversion started by the wrong release cannot be undone from the old installation.

What if version 1.1 is no longer on the download page? #

Ask Schneider Electric's support channel for the archived release or the documented migration path, and do not install a different version on the engineering station until project and target compatibility are confirmed.

Decide by the state of your installation:

  • Terminals and projects current: use the release the catalog lists now, after confirming your exact target is in its supported list.
  • Old projects that must stay on 1.1: request the archived release through the vendor's support channel, and keep a dedicated workstation image for 1.1 so those projects never depend on a catalog change.
  • Terminal line winding down and the editor path closing: move the visualization to industrial panel PCs and touchscreen computers, choosing a PC-based HMI runtime for a Modbus TCP PLC.

Installing an unverified different version trades a download problem for a compatibility problem, and on an engineering station that trade is wrong.

Questions asked

Can I just type the missing characters into the truncated address?

No. The cut-off value is a file name you would be guessing, and a wrong guess can return a different build or nothing at all while looking legitimate. Use the address only as a pointer to the vendor's download area, then search for Vijeo Designer Basic and open the V1.1 entry by name. That route needs no reconstructed query string.

Why does a complete download look smaller in Windows than the listed 370.8 MB?

The vendor lists decimal megabytes while Windows properties shows mebibytes. A complete file converts as 370.8 MB times 1,000,000 equals 370,800,000 bytes, and 370,800,000 divided by 1,048,576 equals 353.6 MiB, so Windows displays roughly 354 MB. Compare byte counts when in doubt; a genuinely partial file lands far below that figure.

Does Vijeo Designer Basic also cover the GXO panel family?

No. Basic is the editor tied to the low-end GXU targets such as HMIGXU3500, HMIGXU3512, HMIGXU5500 and HMIGXU5512. The GXO family is managed in the full Vijeo Designer environment, where the target family must be present in the software catalog before a project can be built for it.

What is document SEVD-2020-133-02?

It is the vendor's release documentation for Vijeo Designer and Vijeo Designer Basic software version 1.1, published as a PDF of about 247.7 KB. Read it before installing: it states the supported targets, package details and release notes for V1.1, and it is the reference to quote if you later need the archived release from support.

Keep reading

  • How-to

    Simulating a Basic HMI against a real TM172 HVAC controller

    Yes, but only with the physical TM172 present: the Windows simulation replaces the HMI panel, never the controller. Run the HMI application in simulation as a Modbus TCP client to the controller's port 15797, or as a Modbus RTU master with the PC's RS-485 converter assigned to COM2. Without the physical controller there is no live application data to test against.

    HMI and touchscreens

  • How-to

    Reading Modbus discrete input 10001 in a Vijeo HMI

    Yes, you can read it: 10001 is the first Modbus discrete input, and %M10001 points at internal coil 10001 instead. Uncheck IEC61131 Syntax on the Modbus/TCP driver and enter 100001 in the 1x family, which equals %I1; copy the input to a %M bit only if the driver cannot reach the input table.

    HMI and touchscreens

  • Troubleshooting

    Getting the HMIGXO Family Into the Vijeo Designer Catalog

    The GXO family is missing because Vijeo Designer 6.2 gates the HMIGXO targets behind a license upgrade, not because the panel is unsupported: Schneider Electric documents HMIGXO as compatible with 6.2. Launch Vijeo Designer as Administrator, apply the GXO upgrade code through Help > About > License > Upgrade with a registered license, then select the exact HMIGXO3501 target. SoMachine 4.1 never adds HMI targets, and the M238 link is proven afterwards with one register test.

    HMI and touchscreens