IMDTouchKnowledge BaseShop main store

Explainer

Why the LogicLab Symbols Converter Expands Array Elements into Tags

HMI and touchscreens Published 6 min read

Short answer

The Symbols converter exports every symbol allocated in DB100 — currently the only LogicLab data block addressable over Modbus — and writes one EasyBuilder tag per array element, with no exclusion option. That is normal output, not a faulty import. Unreferenced tags generate no Modbus traffic, because the panel polls only addresses bound to objects, alarms or data logs the project uses.

On this page
  1. What the Symbols converter exports
  2. Counting the tags for a four-element UINT array at %MW100.16
  3. Why unreferenced tags cost nothing at runtime
  4. Reaching the whole array with one tag
  5. When pruning is worth it, and what it costs
  6. What to check after every re-export
  7. Questions asked

Yes, the expansion is normal, and there is currently no setting that narrows it. The Symbols converter writes one EasyBuilder tag per element for every array it exports, and it exports every symbol LogicLab allocates in DB100 — currently the only data block addressable over Modbus. A tag list far larger than the screens need is expected output, not a faulty import. The surplus tags also cost nothing at runtime: the panel polls only the addresses bound to the objects, alarms and data logs the project actually uses, so an unreferenced tag generates no Modbus request. Import the full list, bind the object that walks the array to the element 0 tag with index-register addressing, and leave the rest unreferenced.

What the Symbols converter exports #

The converter takes every symbol LogicLab allocates in DB100, because DB100 is currently the only data block the panel can address over Modbus. Anything allocated outside that block never reaches the tag file. Within it, each element of an array becomes its own line, and the current version offers no way to exclude individual symbols or to keep an array as a single base-address tag.

This declaration in LogicLab:

VAR_GLOBAL
    MyArray AT %MW100.16 : ARRAY[0..3] OF UINT;
END_VAR

produces four tags in the generated file:

MyArray[0],MyProgram,%MW,40008,,16-bit Unsigned
MyArray[1],MyProgram,%MW,40009,,16-bit Unsigned
MyArray[2],MyProgram,%MW,40010,,16-bit Unsigned
MyArray[3],MyProgram,%MW,40011,,16-bit Unsigned

The tag count therefore scales with the declared array length, not with what the screens display: an array of N elements yields N tags, even when a single object walks the whole array with an index register and only the element 0 tag is ever referenced. The file reaches the EasyBuilder Pro tag library through the same import path as any PLC tag CSV, so the merge rules described for importing a PLC tag CSV into an existing HMI tag database apply unchanged.

Counting the tags for a four-element UINT array at %MW100.16 #

The inputs:

  • Declaration, from the LogicLab project: MyArray AT %MW100.16 : ARRAY[0..3] OF UINT, a global array of four unsigned integers.
  • Element width, from the type: UINT is 16 bits, one %MW word, so each element occupies exactly one Modbus holding register. A UINT fills one word and no more; values wider than 16 bits span several words and become a word-combining exercise of their own, such as combining four UINT words into a ULINT safely.
  • Base address, from the documented converter output: element 0 lands at Modbus address 40008.
  • Runtime references, from the panel design: one screen object walks the array through an index register.

The rule, in words: the converter writes one tag per element, and consecutive elements of a one-word type occupy consecutive holding registers, so element k sits at the base address plus k.

The arithmetic:

  • Element count: 3 - 0 + 1 = 4 elements.
  • Register span: 4 elements × 1 register per element = 4 holding registers.
  • Addresses: 40008 + 0 = 40008, 40008 + 1 = 40009, 40008 + 2 = 40010, 40008 + 3 = 40011.
  • Referenced tags: 1 (the element 0 base); unreferenced tags: 4 - 1 = 3.

Result: four tags in the library, three of which no object, alarm or data log ever points at.

Decision: import all four and leave the three alone — they add no Modbus traffic and no panel load. The number worth verifying is not the tag count but the element 0 address: it must equal the Modbus address of the LogicLab declaration, because every index offset hangs from it. Keep the surplus tags for as long as they are merely unreferenced; prune only when the library is too large to search.

Why unreferenced tags cost nothing at runtime #

The size of the tag library has no effect on communication speed with the PLC or on panel resources. The panel requests only the variables bound to graphic objects the program actually uses, plus the addresses its alarms and data logs reference; a tag nothing points at generates no Modbus request at all. Poll load follows the addresses the active screens reference and the block sizes the driver requests, never the number of tags sitting in the library.

That inverts the usual tidy-up instinct. Deleting the surplus array tags buys nothing in cycle time or update rate, and it costs rework, because the converter regenerates the complete list on the next run.

Reaching the whole array with one tag #

In EasyBuilder Pro, bind the object that walks the array to the element 0 tag and enable index-register addressing. The object uses that tag's address as its base and adds the index register value as an offset, so elements 1 through 3 are reached through the same object without their own tags.

Two checks prove the setup before you call it done:

  • From the PLC, write distinct known values into element 0 and the highest element. Step the index register from 0 to 3 and confirm the object shows each value at the matching index.
  • Confirm that no object, alarm or data log references MyArray[1] or later. Those tags stay in the library unused, which is exactly the intended state.

When pruning is worth it, and what it costs #

Your options, in the order that serves you best:

  • Import the full list and leave unused tags in place: no runtime effect, and a later re-export and re-import needs no rework.
  • Delete unused tags in EasyBuilder Pro after import: no runtime gain, and the next import brings every tag back, so the pruning repeats each cycle.
  • Edit the generated file before import: same outcome, plus a manual step outside the converter that must be repeated and checked every time.
  • Reduce what is allocated in DB100: shrinks the list at the source, but moves PLC memory and Modbus addresses, which touches every tag already bound.

Prune only when the library has grown so large that finding a tag by name slows you down. That is the one real cost of a large library: search time in the engineering tool, not performance on the machine.

What to check after every re-export #

  • Missing symbols: only DB100 allocations are exported. A variable in another block will not appear; move it into DB100 and run the converter again.
  • Address drift: tag addresses derive from the LogicLab declaration. Move or resize an array and the converter must run again — stale tags keep reading the old registers while the link still reports healthy.
  • Element count: an ARRAY[0..3] must produce four lines at consecutive addresses in the file. If it does not, the declaration changed under you.
  • Index range: the index register can exceed the declared array length without raising any tag error, and the panel then reads whatever register follows in DB100. Limit the index in the PLC or on the object.

If an address typed by hand is rejected while the imported tags validate, the fault sits in address entry rather than in the converter; work through fixing invalid bit address errors when adding HMI tags.

Questions asked

Why does the Symbols converter create one tag per array element?

The converter expands every array allocated in DB100 into one tag per element, so an array of N elements yields N tags at consecutive addresses. The current version has no setting to exclude symbols and no option to collapse an array to a single base-address tag, so the full expansion is expected output. The tag names keep the element index in brackets, so searching the library for the array's base name finds the whole set at once.

Why is my LogicLab variable missing from the exported tag file?

The converter exports only the symbols LogicLab allocates in DB100, currently the only data block addressable over Modbus, so a variable placed in any other block never reaches the file. Check the symbol's allocation in LogicLab before you export, move the variable into DB100 if the panel must see it, then run the converter again.

Do unused tags slow down communication with the PLC?

No. The panel polls only the variables bound to graphic objects the project actually uses, plus the addresses its alarms and data logs reference, so an unreferenced tag generates no request and consumes nothing. If communication is slow, count the distinct addresses on the active screens and their background objects: that set, and the block sizes the driver requests, is what loads the link, not the size of the tag library.

Why is the element 0 tag enough to display the whole array?

With index-register addressing the object takes the element 0 tag as its base address and adds the index register value as an offset, so elements 1 and above are reached without their own tags. Keep the index inside the declared bounds, set in the PLC or on the object: an index past the array end raises no tag error, it simply reads the next register in the block.

Why do tags I deleted come back after re-running the converter?

The converter regenerates the complete tag list from the DB100 symbols on every run, including every array element, so manual pruning is undone at the next import. Since pruning buys no runtime improvement, keep the full list and re-import it as-is; prune only when the library is hard to navigate, and note what you removed so the loss is no surprise.

Keep reading

  • Troubleshooting

    Why EasyBuilder Pro Replaces Siemens Tags With a Question Mark

    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.

    HMI and touchscreens

  • Explainer

    Can a Weintek HMI Command Siemens CPU Run and Stop

    A Weintek panel can command a Siemens CPU between run and stop only when the EasyBuilder Pro driver for that CPU family documents an operating-state operation; Siemens documents that GET/PUT data access works in either state, so working tags prove nothing. If the operation is absent from your driver, mode changes stay on TIA Portal, a Siemens operator panel or the S7-1200's built-in web server, which offers stop and run and no restart command.

    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