Troubleshooting
Getting the HMIGXO Family Into the Vijeo Designer Catalog
Short answer
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.
On this page
The GXO family is missing from your target list because Vijeo Designer 6.2 ships its HMIGXO targets behind a license activation, not because the HMIGXO3501 is unsupported: Schneider Electric's FAQ FA283377 states that HMIGXO is compatible with Vijeo Designer 6.2. The documented fix is a license upgrade — launch Vijeo Designer as Administrator and apply the GXO activation code through Help > About > License > Upgrade, with the license registered first. Installing SoMachine 4.1 for the Modicon M238 (TM238LFDC24DT) changes nothing on the HMI side, because controller software never installs HMI targets. Afterwards, select the exact HMIGXO3501 and prove the M238 link with one register before building screens.
Why the GXO targets are hidden #
A full Vijeo Designer 6.2 installation does not display every family it can program. The GXO targets are released through an activation applied to the license, and until that activation exists, a catalog search for GXO returns nothing at all — no family, no models.
Two of the manufacturer's FAQ entries cover exactly this case. FA283377 confirms HMIGXO compatibility with Vijeo Designer 6.2 and names the prerequisite: the Vijeo Designer license must be registered first. FA365003 gives the procedure — run as Administrator, then the license upgrade path. The mechanism is the same one used when activating the XBTOT target family in Vijeo Designer 6.2: target families join the catalog through license upgrades, not through the base installer.
The activation, step by step #
- Read the panel nameplate and record the complete model — here HMIGXO3501. The catalog search uses that exact identifier.
- Confirm the Vijeo Designer license is registered on the engineering station; the manufacturer lists this as the prerequisite for the upgrade.
- Close Vijeo Designer and relaunch it as Administrator in Windows, as the documented procedure requires.
- Open Help > About > License > Upgrade.
- Enter the GXO upgrade code published in the manufacturer's FAQ FA365003 and confirm the upgrade.
- Restart Vijeo Designer, start the project, and search the target list for HMIGXO3501.
Proceed only when the exact model is selectable. If GXO appears after step 5, the catalog problem is closed and nothing else about the installation was wrong.
Why SoMachine 4.1 does not add the GXO targets #
SoMachine 4.1 is in this project for one job: configuring and programming the M238. The HMI target catalog belongs to Vijeo Designer and is governed by its license, so no SoMachine installation — 4.1 or any other — adds or removes HMI targets on the HMI side. GXO panels are programmed in Vijeo Designer, not in SoMachine.
If you also cannot see the GXO3501 inside a SoMachine HMI list, that is a different catalog with its own documented fix, covered in separate correction for HMIGXO3501 missing from a SoMachine Magelis HMI list.
What each catalog result calls for #
- No GXO models at all. This is the license-gating case above. Apply the activation; the family is documented as supported on 6.2, so there is no reason to reinstall anything else first.
- GXO family listed, HMIGXO3501 not. Do not substitute a GXU or GTO target: the downloaded runtime would be built for different hardware. Confirm the exact model against the installed release in the manufacturer's compatibility data, and if you rebuild the station, install the HMI base software before the service pack.
- Exact HMIGXO3501 listed. Create the target with that model and move to the link test below.
For any other family, the general diagnosis is when an HMI model is missing from the programming software; the GXO case is the one where the documented answer is a license activation.
Prove the M238 link with one register #
Worked example, illustrative values on the Modicon Modbus convention. In SoMachine 4.1, add one line to the M238 task: %MW20 := %MW20 + 1, executed once per second. Modicon controllers map %MW0 to Modbus holding register 40001, so the test register sits at 40001 + 20 = 40021. On the HMI side, add the Modbus driver that matches the medium wired between panel and M238 — the steps are in adding a Modbus RTU driver and external variables in Vijeo Designer — and bind one numeric variable to holding register 40021, typing 20 instead if that driver's address field is 0-based. The driver setting decides which number you type, not the panel.
Download and watch the panel. A value climbing by one each second proves target, driver and physical link together; a static value means the fault is now in driver or port configuration, never in the catalog. Prove this read path first, and test your first HMI write against a spare register before any write reaches real M238 outputs.
Where the GXO programming guide lives #
There is no separate GXO programming package to find. The GXO family is programmed in Vijeo Designer, so the documentation is the Vijeo Designer user documentation plus the panel's own hardware manual, both from the manufacturer's site. Take the software itself the same way: the official Vijeo Designer 6.2 base download, with any service pack applied after it.
Questions asked
Is the HMIGXO3501 supported by Vijeo Designer 6.2?
Yes. Schneider Electric's FAQ FA283377 states HMIGXO is compatible with Vijeo Designer 6.2. The family is license-gated, not unsupported: once the GXO activation is applied, the targets appear and you search for the exact nameplate model.
Which software programs the HMIGXO3502?
The same environment. The GXO upgrade code activates the family's targets, so the GXO3502 joins the catalog together with the GXO3501 once the license upgrade is applied in Vijeo Designer 6.2. Search for and select the exact model printed on the nameplate.
Where does the GXO upgrade code come from?
From Schneider Electric's own support entry FA365003, which publishes the code together with the Administrator procedure and the registered-license prerequisite. It is applied through Help > About > License > Upgrade. Take the code from the manufacturer's page so it matches your release.
Why didn't installing SoMachine 4.1 make the GXO appear?
Because it never could. SoMachine 4.1 configures and programs the Modicon M238; HMI target catalogs belong to Vijeo Designer and open under its license. No controller-side installation adds HMI targets, so the GXO family stays hidden until the HMI-side activation is done.
Can I use a GXU or GTO target until GXO appears?
No. A different family's target builds a runtime for different hardware and communication behavior, which the GXO3501 may reject or run incorrectly on the M238 link. The documented fix is the license activation, so there is no engineering case for a substitute target.