IMDTouchKnowledge BaseShop main store

Troubleshooting

When an HMI Model Is Missing From the Programming Software

HMI and touchscreens Published 6 min read

Short answer

The model-selection list in HMI programming software contains only the panels whose definitions are installed on that workstation, so a missing model means missing model support. Run the editor's model-support setup utility from its own installation directory, or get the software upgrade from the vendor, and never substitute the nearest similar model number.

On this page
  1. Why is the model missing from the programming software?
  2. Can you select the closest similar model instead?
  3. How do you tell which editor you actually have?
  4. How do you run the model-support setup utility?
  5. When is the vendor upgrade the only fix?
  6. How do you verify the target model before downloading?
  7. What if the panel answers ping but the editor still lists nothing?
  8. Questions asked

The model-selection list in HMI programming software contains only the panels whose model definitions are installed on that workstation, so a model that does not appear is missing model support, not a defective panel. The fix is to add the support: run the editor's model-support setup utility from its own installation directory, or obtain the newer software version from the panel's manufacturer. Selecting the nearest similar model number is never part of the fix. The documented case behind this article: two installed editors listed only the GP-4401 series while the panel was a GP-4402WW, and the utility that adds the missing support ships inside the GP-Pro EX installation's OP folder as YTSetup.exe.

Why is the model missing from the programming software? #

Because the model-selection list is built from the model definitions installed on that workstation, not from a live query of the panel or of any catalog: no installed definition, no list entry, whatever hardware sits on the bench.

Editors gain target models through the definitions their installer and support components register on the PC. An editor version released before the panel existed cannot list it, and an installation missing a support component lists only part of a family. Two editor products from the same vendor keep separate lists, so both being present proves nothing about either.

Worked example from the documented case: search both installations for the exact designation GP-4402WW. GX Pro V4.07.101 returns the GP-4401 series only. V4.06.300 returns the GP-4401 series only. That is 0 of 2 installations listing the panel (0 ÷ 2 = 0), so the fault sits in the workstation's software setup, not in the panel and not in any transfer setting. The behavior is not unique to one platform; target information that depends on installed definitions reads the same way across vendors.

Can you select the closest similar model instead? #

No: the project targets exactly what you select, so choosing the GP-4401 series for a GP-4402WW compiles a project aimed at hardware you do not have, and family resemblance is not a compatibility basis.

The suffix is part of the model. Editors treat each designation as a distinct target with its own screen geometry, memory map and option set, and everything downstream of the selection compiles against that target. A clean build proves the editor accepted its own target, not that the target matches your panel. The substitution also hides the real fault, because a list entry that "works" removes the pressure to install the definitions. Decision: never substitute; add the model support.

How do you tell which editor you actually have? #

Read the product name and version from the editor's own splash or About screen, then confirm its installation directory, because the setup utility lives in one specific product's folder and a similarly named product is a different program.

In the documented case the workstations carried GX Pro V4.07.101 and V4.06.300, while the utility procedure is documented for GP-Pro EX. A differently named editor is not evidence that the same folder and file exist in it, and running a similarly named installer found elsewhere is how workstations end up with mismatched components. Before you act, record:

  • the product name exactly as displayed
  • the version exactly as displayed
  • the installation directory path
  • the exact designation you searched for, and the list result

How do you run the model-support setup utility? #

Show hidden files, open the GP-Pro EX installation directory, open its OP folder, run YTSetup.exe from there, then reopen the editor and search the model list for the exact designation again.

  1. Enable display of hidden files in the file manager.
  2. Browse to the GP-Pro EX installation directory.
  3. Open the OP folder.
  4. Run YTSetup.exe, the copy from this installation, never a copy from another computer or a download site.
  5. Reopen the editor and search the list for the exact designation.
  6. Still absent? Stop here and take the vendor path below rather than picking a near match.

One caution, in place: if the utility offers choices that do not clearly correspond to adding model support, or offers to remove components, stop and confirm with the vendor before clicking through, and take installer files only from the manufacturer or its distributors.

When is the vendor upgrade the only fix? #

When the utility is absent from your installation, or the model still fails to appear after it runs, the definitions you need are not on that workstation and the newer software or support package has to come from the panel manufacturer.

Manufacturers publish editor upgrades and support packages on their own download pages, and legacy lines often sit behind an account or an authorization request, the same discipline as obtaining manuals for an installed system; request the access rather than sourcing the software elsewhere. Attach the four recorded items from the section above to the request. Which editor version first carried a given model definition is vendor information, not something to guess; your proof is the model list after the upgrade installs. If the vendor has retired the editor family, the decision becomes a supported panel, and planning an HMI terminal replacement from an older operator panel walks through that choice.

How do you verify the target model before downloading? #

The exact designation, suffix included, must appear in the model-selection list and again as the project's target in its own settings, two places and one string, before anything compiles or transfers.

Open the project's target or device settings and read the model string back character by character; GP-4402WW is not GP-4401. Compile only after the string is right, because a successful build against a wrong target proves nothing. Transfer questions come after, never before: why an HMI transfer fails in initial start mode despite ping is the next read, and if the cable is the unknown, uploading an HMI program without the right cable pinout covers the wiring.

What if the panel answers ping but the editor still lists nothing? #

Then the panel is healthy and the problem stays on the engineering workstation: a live ethernet link proves connectivity, not installed model definitions, so keep working the editor's model support and leave the network alone.

Nothing done at the panel end adds a list entry on the PC, because the list is a workstation artifact. Work the definitions until the exact model appears and is selected, then move on. The decisions, in order:

  • Exact designation in the list: set it as the project target and proceed to transfer.
  • GP-Pro EX installed and YTSetup.exe present: run it from the OP folder, then re-check the list.
  • Different editor product, or the model still missing: vendor upgrade path, with your recorded details attached.
  • Vendor support retired: plan a supported panel instead of forcing an unsupported target.

Questions asked

Will reinstalling the same editor version bring the missing model back?

No. The same installer writes the same model definitions, so the list comes back unchanged. The list changes only when the definitions change: run the model-support setup utility inside that installation, or install the newer software version the vendor supplies.

Can YTSetup.exe be copied from another computer or a download site?

No. Use the copy inside the GP-Pro EX installation you are fixing, and take full installers only from the manufacturer or its distributors. Executables from shared folders and mirror sites are a common way to land a mismatched or tampered setup on an engineering workstation.

The model now appears with several suffixes, so which one do I pick?

The exact designation printed on the panel, suffix included. Editors treat each suffix as a distinct model with its own screen size, memory and options, so a near match compiles a project aimed at the wrong hardware. If the exact suffix never appears, the definition is still not installed.

Does a successful transfer prove the target model was right?

No. A completed download proves the cable and the connection, not the target: depending on the platform, the runtime refuses a mismatched project or runs it with wrong geometry. Read the model string back in the project settings before calling the job finished.

Keep reading

  • Troubleshooting

    Fixing TwinCAT HMI publish failures after a NuGet update

    The publish task fails with every symbol unresolved because TF2000, TE2000 and the HMI NuGet packages are at mixed versions after a partial TcPkg upgrade. Update all three groups together on the engineering PC and the IPC, redeploy an empty project to prove the path, then republish: the failure sits in the environment, not the project.

    HMI and touchscreens

  • How-to

    How to Upload an HMI Program Without the Right Cable Pinout

    Upload an HG3F with the documented programming cable HG9Z-XCM1A, which runs from a 9-pin RS-232 port on the PC to Serial Interface 2 on the panel. Do not fabricate a pinout, and confirm the installed WindOI-NV2 version permits upload before you connect.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Macro PLC Tag Is Missing From the PLC Program

    Only the second quoted string in a macro line is a candidate PLC tag, and it resolves against the HMI Address Tag Library, which maps the name to a controller address. Unquoted names are macro-local variables that never reach the controller. If no HMI unit sits in the data path, trace the real consumer from the controller's cross-reference and Ethernet client list.

    HMI and touchscreens

Why your HMI software reports a missing installed font