IMDTouchKnowledge BaseShop main store

Troubleshooting

Why EasyBuilder Pro Replaces Siemens Tags With a Question Mark

HMI and touchscreens Published 7 min read

Short answer

Get tags from a Siemens PLC made EasyBuilder Pro 6.08.01.350 replace every HMI object's tag reference with a question mark, even where the name matched. Remap each object by selecting localhmi, then reselecting the PLC device and tag, and prevent a repeat by updating tags with the same acquisition method that built the tag set, proven first in a copy.

On this page
  1. Why do HMI objects show a question mark after a Siemens tag update?
  2. What is actually lost when the reference becomes a question mark?
  3. Was Get tags the wrong way to update Siemens tags?
  4. How do I remap an object whose tag shows a question mark?
  5. How do I prove the repair and the next update safely?
  6. How do I keep the next PLC update from breaking the HMI?
  7. When should this go to the vendor?
  8. Questions asked

After a Get tags update from a Siemens PLC, EasyBuilder Pro 6.08.01.350 replaced every HMI object's tag reference with a question mark, even on tags whose name had not changed. The objects still displayed the tag name, but each one had to be remapped by selecting localhmi, then reselecting the PLC device and the tag. Treat this as a tag-binding fault in the project database, not as a PLC communication fault, and repair it in the editor. This article gives the remap sequence, the acquisition-method rule that stops a repeat, and what to send the vendor when you can reproduce the fault.

Why do HMI objects show a question mark after a Siemens tag update? #

Because Get tags replaced each object's qualified tag reference, not just the tag list: the refreshed entries are new database entries, so every object bound to the old entries shows a question mark, even when the visible tag name is unchanged. The verified case is EasyBuilder Pro 6.08.01.350 with a Siemens PLC, refreshing tags through Get tags; every reference in the project turned into a ? at once.

Two conditions produce exactly this picture, and the working diagnosis is one of them:

  • The acquisition path differed from the one that built the tag set: Get tags run against a set that was originally imported, or the reverse.
  • The protocol or device configuration differed from the original project.

Either condition changes how the editor represents a reference — the device context plus any prefix or suffix in the complete name — so the refreshed entries no longer match the stored bindings and the editor drops them to ?.

What is actually lost when the reference becomes a question mark? #

The object loses its device-and-tag association inside the project database; the tag text still displayed on the object is only a label, so a visible name proves nothing about whether the object still reads or writes a valid PLC tag. A binding is the association between an HMI object and its data source: the selected device plus the tag reference, and the question mark means that association is gone.

The consequence is that the object resolves to nothing until it is rebound. Reconnecting the PLC, power-cycling the panel, or re-downloading the project will not restore it, because the broken state is saved in the project itself.

Was Get tags the wrong way to update Siemens tags? #

In the verified case, yes: Get tags was the operation that broke the bindings, and the working diagnosis is that the acquisition path or protocol differed from the one that originally built the tag set, so the complete references stopped matching.

Weintek's PLC connect guides document two acquisition paths for its drivers: a file import and an online read from the connected PLC. On the Rockwell EtherNet/IP guide the buttons read "Import Tags…" for .L5X or .CSV files and "Get Tag Info…" for the online read; Get tags is that online-read path. The Siemens side offers the same two shapes: an import from the TIA Portal project — the editor refuses it with "Compile TIA Portal Project before importing" until the project is compiled — and an online read from the connected PLC. For the file-import path in general, importing a PLC tag CSV into an existing HMI tag database covers the mechanics, and which paths a driver offers varies, which is also why EasyBuilder asks for a tag CSV for a Mitsubishi Q PLC.

The rule this case leaves you with: update tags through the same path that built the tag set. A set built by a TIA Portal project import gets refreshed by importing the updated, compiled project; a set built online gets refreshed online. Mixing paths, or changing protocol between updates, is what drops the bindings. The failure shape is general — an import whose keys no longer match stored references breaks the bindings — and one parallel walkthrough is fixing EDE imports with changed keys.

How do I remap an object whose tag shows a question mark? #

Open the object's tag selector, select localhmi first, then reselect the Siemens PLC device and the tag: that sequence rebuilds the association and clears the question mark, and it is the repair that worked in the verified case.

  1. Save a copy of the affected project and work in it; keep the broken original for comparison.
  2. Build the inventory first: screen, device, displayed tag name, and whether the object displays data or issues commands.
  3. Open one affected object's properties and go to its tag selector.
  4. Select localhmi. This is an intermediate step that releases the stale association; it is not the intended data source.
  5. Reselect the Siemens PLC device, then the current tag.
  6. Check that the tag's data type and its read or write function match what the object did before the update.
  7. Close the properties and reopen them: both selections must persist.
  8. Repeat across the inventory, then save, close and reopen the project, and confirm no question marks remain.

The editor's find-and-replace for tags, documented in Weintek's tutorials, finds every object using a given reference faster than walking screens; whether its replace action rebuilds a binding lost this way was not tested in the verified case, so treat step-by-step reselection as the repair. One caution: a command object remapped to the wrong tag can write to real equipment, so verify every write object against the PLC program, not against a similar name.

An illustrative scope check: 3 screens with 14 affected objects — 10 displays and 4 command objects — at about 1 minute per remap is 14 × 1 min = 14 minutes, plus reopening properties on a few objects and the project once, so budget roughly 20 minutes of editor work. That is the cost of one mismatched acquisition path.

How do I prove the repair and the next update safely? #

Copy the project, repeat the intended tag update in the copy, then count question marks: zero confirms both the repair and the method, while any repeat means the method is wrong for this project and the tag set needs rebuilding through the import path.

  1. Copy the repaired project.
  2. Repeat the tag update you intend to run, using the path that built the original tag set.
  3. Count the question marks: zero means the repair and the method hold.
  4. Any repeat means the method is wrong for this project: rebuild the tag set once through the import path, rebind, and stay on that path for every later update.

Compare a representative group before editing everything: a couple of display objects and one command object, from different PLC structures where present, comparing the old and current complete reference wherever the selector exposes it. Keep any pre-update project separate and work on copies.

How do I keep the next PLC update from breaking the HMI? #

Hold the PLC-to-HMI interface stable — tag names, data types, the HMI's device association, and the acquisition method — and review deliberate PLC-side changes before refreshing the HMI tag database; finishing the PLC program before starting the HMI is discipline, not a requirement. Concretely: freeze names, types and device associations once objects bind to them; add new tags freely; when the PLC side must change a name or type that is already in use, list the change and check the affected HMI objects before refreshing the database; and never alternate acquisition paths on one project.

When should this go to the vendor? #

When you can reproduce it on demand: note the editor version, PLC type, the acquisition method that built the original tag set, the method that broke it, and attach a project copy showing bindings before and after, then send it through Weintek's official support channel or the supplying distributor. A reproducible case is worth reporting; a one-off on a project with unknown history usually is not. The reporting matters because a successful manual remap does not prove the next update keeps its bindings — if the editor drops references again in a controlled test, that is behavior the vendor needs to see, not operator error.

Questions asked

Does a question mark on the tag mean the HMI has lost the PLC connection?

No. This fault sits in the project's tag database, not in the link: the object still shows the tag name, and the question mark survives with the PLC online and communicating. A connection problem would hit objects regardless of which tag update ran, and reselecting a tag would not clear it. Remap first; chase communications only if a verified remap leaves the object broken.

Will downloading the project to the panel clear the question marks?

No. The broken references are stored in the edited project, so a download carries the same broken state to the panel. The repair happens in EasyBuilder Pro: select localhmi, reselect the device and tag for each affected object, save, then download. Downloading first only puts the fault on the machine.

Do I have to finish the PLC program before writing the HMI screens?

No, that is not a rule. What protects the HMI is a controlled interface: once a tag name, data type and device association are in use by HMI objects, treat them as frozen, or review a deliberate change before refreshing the HMI tag database. If PLC work is still moving, build screens in a separate test project and merge them once the interface settles.

Is this fault specific to Siemens PLCs?

The verified case is EasyBuilder Pro 6.08.01.350 with a Siemens PLC updated through Get tags. The mechanism, a refreshed tag set whose complete references no longer match the stored bindings, is not Siemens-specific, and Weintek documents the same two acquisition paths for its Rockwell driver. Treat every driver the same: prove the update path in a copy before touching a live project.

What does selecting localhmi actually do to the object?

It is an intermediate editor step that releases the stale device-and-tag association so you can build it again. It is not a data source for the object: if you stop there, the object is left pointing at the local HMI rather than your PLC, so always finish by reselecting the PLC device and the tag before saving.

Keep reading

  • How-to

    Connecting a Weintek MT8050iE to an S7-200 over PPI

    Yes. The MT8050iE talks to an S7-200 CPU 224XP over PPI with the Siemens S7/200 PPI driver in EasyBuilder Pro, assigned to a COM port documented for RS-485 with serial settings matched to the PLC. Project download runs over a USB A-to-mini-B cable or Ethernet and is independent of the PLC driver; confirm the real-time clock in the model datasheet.

    HMI and touchscreens

  • Troubleshooting

    Fixing an HMI Date and Time Tag That Fails Over S7

    When ordinary tags read and write but a Siemens date and time tag returns a communication error, the driver imported the tag but cannot transfer that data type. Copy the clock into ordinary component variables in PLC logic and read and write those from the HMI. The Ethernet side needs no changes.

    HMI and touchscreens

  • Troubleshooting

    EasyBuilder Pro V5 to V6 Upgrade Shows HMI No Response

    Compiling in EasyBuilder Pro V6 changed the Allen-Bradley CompactLogix EtherNet/IP driver from v1.50 to Device ID 156, v1.80, under the same ALLEN_BRADLEY_EIP_COMPACTLOGIX.e30 file name. Remove the copied V5 DLL, restore the V6 driver package, recompile and download, then verify the PLC address and one tag at a time.

    HMI and touchscreens