IMDTouchKnowledge BaseShop main store

How-to

Importing a PLC Tag CSV into an Existing HMI Tag Database

HMI and touchscreens Published 6 min read

Short answer

A PLC tag CSV imports only when its columns match the format your HMI software documents — .csv for one package, .xlsx for another. Never import into the production project: run it on a copy, use the tag count to tell merge from replace, spot-check one revised address, and confirm each affected tag against live PLC values before download.

On this page
  1. Check the documented import format first
  2. Copy the project and record the baseline
  3. What the tag count tells you
  4. Merging a 120-row PLC export into a 300-tag database
  5. Verify every changed tag against live PLC values
  6. Keep the rollback and escalate with evidence
  7. Questions asked

A PLC tag CSV that the HMI refuses to accept almost always fails on format, not content: the file's columns do not match the layout the HMI software documents for tag import, so re-exporting the same PLC data changes nothing. Once the format matches, the real risk is behavior — one importer merges into the existing tag database, another replaces it outright, a third appends duplicates. The procedure below gets the file into the documented shape, runs the import on a project copy, uses the resulting tag count to identify which importer you have, and verifies every changed tag against live PLC values before the project downloads.

Check the documented import format first #

A .csv extension names a container, not a layout, and each HMI package documents its own. C-more's help specifies an Import Tag Name Database command that accepts a properly formatted .csv file, with .xls and L5K files listed among the accepted source types. The tag import documented for STEP 7 and WinCC Unified requires .xlsx instead, structured to the columns and rules those manuals define. InTouch applications move tag data between projects as .csv. The same tag rows therefore travel in three different containers, and a PLC description export is portable to an HMI only after its columns match that HMI's documented layout.

The check is fast: open the rejected file in a text editor, read its header row, and compare each column — tag name, PLC address, data type, description — against the documented import layout, including column order and file encoding. If they differ, reshape the file into the documented columns rather than renaming the extension; a rename changes nothing the importer reads. Keep the original export untouched and work on a copy of the file too.

If the tag base arrived with a whole-project conversion from an older panel, the screens and tags came in together — importing legacy HMI screens when migrating to a new panel covers that route. The steps below are for layering a revised PLC export on top of a tag base the project already has.

Copy the project and record the baseline #

Never import into the production project first; the copy gives you a clean rollback if the import replaces or pollutes the tag base.

  1. Save a copy of the production project under a new name and leave the original untouched until every check passes.
  2. Export the current HMI tag database if the software offers an export. That file is both your merge source and your record of what every tag said before the import.
  3. Count the data rows in the PLC export, excluding the header row, and count the tags in the project copy. Call the export total N and the tag total B.
  4. Import the PLC export into the copy through the documented import command.
  5. Count the tags in the copy again.
  6. Open one tag whose PLC address the program revision changed, and read its address field in the copy.

What the tag count tells you #

Compare the post-import count against B, N and D, where D is the number of tag names that appear in both the PLC export and the existing base. The count sorts the importer into one of four behaviors:

  • Unchanged at B: the import either updated existing entries in place or did nothing. The step 6 spot-check decides — a revised address means in-place update; the old address means the import was a no-op and the file was never really read.
  • B + (N − D): the import added only new names and kept the old definitions for every overlapping name, so revised addresses on existing tags were never applied.
  • B + N: the import appended every row, duplicates included. The copy now holds two definitions for each overlapping name, so restore it rather than untangle it.
  • N: the import replaced the whole base. Restore the copy, merge the exported old tags with the PLC export outside the tool, and import the merged file.

Two of these four outcomes call for a merge before import, not another import of the same file.

Merging a 120-row PLC export into a 300-tag database #

This worked example uses round illustrative counts; read your own B, N and D from your two files and the same arithmetic applies.

The inputs, each read from a file: the project copy holds B = 300 tags, counted in its tag list. The PLC description export holds N = 120 data rows, counted with the header excluded. Comparing name columns gives D = 96 names present in both files, so the export carries 96 revised definitions for existing tags and 24 new names, since 96 + 24 = 120.

The rule in words: the post-import tag count identifies the importer's behavior, and only the in-place-update outcome leaves the revised addresses in place. The arithmetic: replacement would leave exactly N = 120 tags; appending every row would give 300 + 120 = 420 tags; adding only new names gives 300 + (120 − 96) = 300 + 24 = 324; an in-place update stays at 300.

The result: after the test import, the copy reads 324 tags.

The decision: the importer added the 24 new names and kept the old definitions for the overlapping tags, so none of the revised addresses was applied, and reimporting the same file will not change that. Merge before import instead: combine the exported current tag list with the PLC export in a spreadsheet, keep the newer address for each overlapping name deliberately, and import the merged file into a fresh copy. Had the count read 420, the copy would hold duplicate definitions — restore it and de-duplicate first. Had it read 120, the base was replaced — restore it and pre-merge the same way.

Verify every changed tag against live PLC values #

A completed import is a data-transfer result, not proof of runtime. Before download, compare each changed tag's name, PLC address, data type and read/write direction against the revised PLC program — a mismatch leaves the tag present in the base but pointed at the wrong data. Download the project, then prove the tags that matter: pick a PLC value that changes under a known, controlled condition and confirm the HMI display follows it, across representative tags in the changed set, including different data types and address patterns.

If a value stays static, the definition or the link is at fault: check the tag's address and data type first, then the communication link's status and diagnostics. Reimporting the same file repairs neither. If an imported address is both wrong and greyed out so no hand edit can reach it, why C-More shows tag addresses you cannot set in Productivity documents that locked-address case.

Writable tags carry one more rule: test writes to setpoints or commands only under the machine's approved operating procedure with the process owner's sign-off, never against live production without it.

Keep the rollback and escalate with evidence #

Keep the original project and the pre-import tag export on hand until operators have confirmed the affected screens on the downloaded project. If the file matches the documented format but the count points one way and the spot-check another, or the import silently changes tags it should not touch, stop re-running it. Capture the software version, the project copy, a sample of the CSV and one failing tag name, and take those to the vendor's official support channel rather than importing into the production project on the chance of a different result.

Questions asked

Is there a shorter path than building the import file by hand?

Often, yes. Some controller packages ship a dedicated export for their own HMI line: ABB, for example, documents exporting AC500 controller tags directly for Panel Builder. Before you hand-build columns, look in the PLC programming software for a symbol or description export aimed at an HMI target; a vendor-matched pair tends to keep names, addresses and data types aligned, which removes most of the format work.

When is manual editing the better choice?

When the change list is short. Under roughly ten changed tags, editing each one in the HMI software is faster than exporting, reshaping, importing and validating a file, and it cannot disturb the other 290 definitions in a 300-tag base. The import starts paying for itself once revisions touch dozens of tags or repeat at every program revision. Below that line, hand edits are the lower-risk procedure.

What if the HMI software documents no tag import at all?

Then the merge happens outside the tool or not at all. Export the existing tag database if an export exists, combine it with the PLC descriptions in a spreadsheet, and check whether the vendor's project- or screen-conversion path carries tags with it. Where none of that exists, the remaining options are hand entry in the tag editor or a documented scripting interface.

Do imported tags reach the panel without a download?

No. An import changes the tag database inside the editor project; the panel keeps running the definitions in its downloaded runtime until you save and download the project again. Most HMI editors cannot hot-swap a changed tag base onto a running panel, so plan the download for a window when the affected screens can be offline, then run the live-value checks before returning the machine to production.

Keep reading

  • Troubleshooting

    HMI Screen Goes Blank for Seconds Then Recovers

    A blank of a few seconds that recovers on its own, and survives a project reload, points first at a PLC-controlled backlight, screen-saver or visibility tag being overwritten at runtime. Separate backlight loss from a panel restart by checking the rear status LEDs and tracing the tags the Reset action writes before swapping hardware.

    HMI and touchscreens

  • Troubleshooting

    Fixing Invalid Bit Address Errors When Adding HMI Tags

    When the tag editor throws GUI-024: Invalid Address on a slash-form bit address like IO4/05 after a software upgrade, the fault is in the tag-entry dialog, not in the PLC point. Export the tag database, restore the full bit address in a spreadsheet, re-import, and verify the object against the intended output before the screen returns to service.

    HMI and touchscreens

  • How-to

    How to import HMI images with a transparent background

    On an EA9 panel running version 6.8 of the C-More software, image import takes BMP, so PNG is out; the transparent-color key removes every pixel of one chosen color, which is why a QR code sharing the background black gets destroyed. Separate the code on its own layer in an image editor, rebuild the background as a solid color that matches the screen, and export a real BMP.

    HMI and touchscreens

Why the LogicLab Symbols Converter Expands Array Elements into Tags