IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing invalid PLC type in Vijeo Designer 6.2 SP12

HMI and touchscreens Published 5 min read

Short answer

When Vijeo Designer 6.2 SP12 leaves %M and %MW exchanging but kills %I and %Q with Invalid PLC Family/Model/Type (ModbusEquipment01), the fault is the software build, not the addressing. Request the SP12 hotfix from Schneider Electric technical support — HF5, build 6.2.12.2056, or the earlier HF3, build 6.2.12.2052 — then rebuild, download, and verify each address class separately.

On this page
  1. What the surviving %M and %MW objects tell you
  2. The fix is the hotfix, not the addressing
  3. What to record before you call
  4. Install, confirm the build, download again
  5. Verify by address class, and size the retest
  6. If the error survives the hotfix
  7. Questions asked

An HMISTU855 talking to a TM221CE40T stopped exchanging %I and %Q objects the moment its project was rebuilt and downloaded under Vijeo Designer V6.2 SP12, while %M and %MW kept working; every download ends with Invalid PLC Family/Model/Type (ModbusEquipment01). That split is a software-build fault in the SP12 installation, not an addressing fault in your project. The fix is the applicable SP12 hotfix from Schneider Electric technical support — HF5, build 6.2.12.2056, or the earlier HF3, build 6.2.12.2052 — followed by a rebuild, a fresh download, and a class-by-class verification. Leave the PLC addressing alone.

What the surviving %M and %MW objects tell you #

The failure is selective by address class, not by connection. %M bits and %MW words, which are internal memory, still cycle between the panel and the PLC. %I and %Q, the physical input and output images, are silent. Both classes ride the same equipment, ModbusEquipment01, so the link is up; the error text says the driver can no longer resolve which controller family, model, or type that equipment points at after the update. The reported installation string was Vijeo Designer V6.2.24 SP12 24-210, and nothing on the machine or in the PLC program changed with it.

One documented cause of this exact error text is cheaper than a hotfix, so clear it first. Schneider's published FAQ for this message names a Modbus Unit ID mismatch — the server device's Unit ID differing from the value configured in the HMI equipment — as its most common cause. Open the equipment properties, compare the Unit ID against the PLC's, and re-download if they differ. When the IDs match and the fault arrived with the SP12 update, the build is the cause and the hotfix is the fix.

A panel gone quiet on all four classes is a connection problem, not this one; that diagnosis path starts with fixing an HMI PLC communication timeout over serial.

The fix is the hotfix, not the addressing #

Request the SP12 hotfix from Schneider Electric technical support and ask for the newest one your installation can take: HF5, build 6.2.12.2056. HF3, build 6.2.12.2052, is the earlier hotfix for the same service pack; if support directs that build for your installation, install it, but the later build is the default ask. Take the package only from the support channel — links shared around the internet for these builds have already gone dead, and an uncontrolled copy cannot be tied to the build it claims to be.

Do not re-address the project. The %I and %Q addresses were valid before the update, the PLC program did not change, and the failing classes share the equipment and connection with the working ones. Re-addressing would bury the driver fault and break the PLC's I/O mapping at the same time.

A hotfix installs on top of the full base product plus SP12, in that order — the same order that matters when installing the HMI base software before the service pack. Close open projects, run the package on the engineering station, and let it finish without errors before you rebuild anything.

What to record before you call #

  • The installed version string exactly as reported — in this case Vijeo Designer V6.2.24 SP12 24-210.
  • The HMI model: HMISTU855 in the reported case.
  • The PLC model: TM221CE40T, with its Modbus Unit ID.
  • The equipment name from the error, verbatim: ModbusEquipment01.
  • The class split: %M and %MW working, %I and %Q not communicating.
  • The exact error text: Invalid PLC Family/Model/Type (ModbusEquipment01).

Then ask one direct question: which SP12 hotfix applies to this build for this fault, HF5 6.2.12.2056 or HF3 6.2.12.2052?

Install, confirm the build, download again #

Before rebuilding, confirm the installed version string now reports the hotfix build. If it still reads the old SP12 string, the hotfix did not apply — rerun it rather than wasting a download cycle. Rebuild the project and download it to the panel: a change on the engineering side reaches the HMI only through a new runtime transfer, the same reason why an HMI edit needs a new runtime download. The download should complete with no equipment-type error for ModbusEquipment01.

Verify by address class, and size the retest #

Worked example with illustrative counts — read yours from the variable list. A project holding 26 %I, 31 %Q, 42 %M and 118 %MW variables breaks exactly the way this fault does:

  • Failing scope: 26 + 31 = 57 variables to retest.
  • Whole database: 42 + 118 + 26 + 31 = 217 variables.
  • Share lost to the update: 57 / 217 = 0.26, about 26% of the live tag set.

Because the fault is class-wide rather than point-by-point, one forced %I and one forced %Q confirming on the panel proves the equipment type is resolved. The full 57-point walk still happens before hand-back, since a returning class fault would otherwise hide inside an untested point, and a short %M and %MW spot check confirms nothing regressed. Forcing %Q states drives real outputs: do it with the machine in a safe state and the outputs isolated from the process.

If the error survives the hotfix #

Re-run the Unit ID comparison first; it is the documented most-common cause of this message and costs a minute. Then capture the new version string, the equipment definition, and one-line results for all four classes. That package separates a persistent equipment-definition fault — working %M and %MW, dead %I and %Q, error on download — from total communication loss, and gives support a reproducible case. If the controller has vanished from the software's equipment list rather than being rejected at download, that missing-from-the-list symptom is the different problem covered when an HMI model is missing from the programming software.

Questions asked

Can I get the line running by remapping the failing %I and %Q variables to %MW?

Only as a stopgap, and it costs more than the fix. Copying the physical I/O images into %MW words means a PLC program change, a PLC download, new HMI variables, and a retest of every moved point, while the hotfix restores the project exactly as built. If support confirms a delay in the hotfix, use the remap to keep running and plan its removal.

The SP12 hotfix installer stops because SoMachine is on the same PC. Is there a documented way through?

Yes. The vendor's hotfix-installation FAQ describes renaming the SoMachine software entry in the Windows registry so the installer proceeds, then restoring the original name afterwards. Export the registry first, and take the exact key path from that FAQ or from support rather than improvising one, because a wrong rename breaks the SoMachine installation.

I found a download link for the SP12 hotfix on the internet. Can I use it?

No. Have Schneider Electric technical support supply the hotfix. A link circulating for these builds was already dead when this fault was reported, and an uncontrolled copy cannot be verified as the build it claims to be. Support matches the package to your exact version string, which is what makes the repair reproducible.

Is this SP12 fault limited to the HMISTU855 and TM221CE40T pair?

The reported pair is HMISTU855 and TM221CE40T, but the fault is not tied to it. The same SP12 generation was reported to stop recognizing M221 controllers generally after the update. Treat any SP12 build that rejects a previously working Modbus equipment the same way: confirm the Unit ID, then request the applicable hotfix instead of re-addressing the project.

Keep reading

  • 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

  • Troubleshooting

    Why an HMI Transfer Fails in Initial Start Mode Despite Ping

    Ping success proves only that the panel's IP stack answers. On a new Magelis XBTG in Initial Start Mode, run three checks in order: build in the engineering version that still supports the target (Vijeo Designer 6.2 for XBTG), clear the license so the download command activates, then load runtime and application over one transport at a time.

    HMI and touchscreens

  • Troubleshooting

    Displaying Negative Drive Values and Script Writes in Vijeo Designer

    The reverse readings failed because the Vijeo Designer variables were typed UINT, which cannot show a value below zero; set them to INT and the same drive words display negative. The script write is a separate fault: point the script's write at the setpoint variable the keypad uses, clamp the result to the drive's documented setpoint range, and verify the write on the connected panel, not in the simulator.

    HMI and touchscreens

Upgrading the Crimson 3 L5K Driver to Version 2.00