IMDTouchKnowledge BaseShop main store

Troubleshooting

Why GP-Pro EX imported tags stay UNDEFINED with an S7-1500

HMI and touchscreens Published 6 min read

Short answer

The addresses stay UNDEFINED because the device SERIES is set to TIA PORTAL ETHERNET, which cannot resolve absolute S7 DB addresses from a CSV. Change the series to SIMATIC S7 ETHERNET, keep the TIA Portal V14 project, and re-import: variables then resolve as [PLC1]DB00051.DBW00012.

On this page
  1. The fix: set the SERIES to SIMATIC S7 ETHERNET
  2. Why one series resolves addresses and the other does not
  3. Keep the TIA Portal V14 project
  4. Build the address CSV from an editor export
  5. Worked example: resolving DB51.DBW12 on a GP4501T
  6. If the address still shows UNDEFINED
  7. Questions asked

Tags that import with names, types and addresses in the right columns but UNDEFINED in the address field are a device-series problem, not a CSV problem. This case ran GP-Pro EX Ver. 4.07 on a GP4501T talking to an S7-1500 in TIA Portal V14, with the device SERIES set to TIA PORTAL ETHERNET. Changing that one selection to SIMATIC S7 ETHERNET let the editor resolve absolute DB addresses: DB51.DBW0 displays as [PLC1]DB00051.DBW00012. The TIA Portal project stays at V14, and no downgrade is needed to make tags resolve.

The fix: set the SERIES to SIMATIC S7 ETHERNET #

  1. Back up the HMI project before changing any communication configuration.
  2. Open the Device/PLC settings for the panel and find the SERIES selection for the controller; it read TIA PORTAL ETHERNET.
  3. Select SIMATIC S7 ETHERNET. The series decides which addressing model the editor offers, and the connection settings belong to the driver, so re-enter the controller IP address and the remaining settings exactly as the driver's Device/PLC Connection Manual lists them.
  4. Verify the driver is installed. The Version dialog under the Help function lists installed drivers with their versions, and SIMATIC S7 Ethernet Driver Ver. 1.19.12 applies to GP-Pro EX Ver. 2.10.000 and later, so 4.07 is covered.
  5. Create one variable by hand at a known address such as DB51.DBW0 and confirm the address field shows a resolved form instead of UNDEFINED.
  6. Re-import the CSV. The rows that already parsed keep their names and types, and the address column resolves.

Why one series resolves addresses and the other does not #

Two things happen between the CSV file and the panel. At engineering time the editor interprets the address text against the addressing model of the selected series; at runtime the panel requests that address from the controller over Ethernet. A successful parse proves only the first half of the first step. Here the summary table showed every column in place — names, types, addresses — while the address field stayed UNDEFINED, because TIA PORTAL ETHERNET offers no S7 absolute address format to map the text into.

The series is not wrong for the controller. The TIA Portal Ethernet driver's documentation lists the S7-1200 and S7-1500 series as supported devices, with the S7-1200 G2 series excluded. It is the wrong series for an absolute-address variable list, and its companion route, the direct import of the TIA project, is documented for TIA Portal V11 through V13.

SERIES selection Addressing model Result with a TIA Portal V14 project
TIA PORTAL ETHERNET Tag access built on the direct TIA project import, documented for TIA Portal V11 through V13 Names and types import; addresses stay UNDEFINED
SIMATIC S7 ETHERNET Absolute S7 DB addresses, entered by hand or read from CSV Address field resolves, e.g. [PLC1]DB00051.DBW00012

For absolute DB addressing, select SIMATIC S7 ETHERNET regardless of which engineering software built the controller project.

Keep the TIA Portal V14 project #

The V11 through V13 limit is a file-format dependency of the direct import path, not a communication dependency. Direct import opens the TIA project and extracts its tag table; absolute addressing never opens it, because the addresses live in the HMI project and the CSV. With SIMATIC S7 ETHERNET selected there is nothing a V13 migration would add to variable definition. Treat a migration as its own engineering change — controller hardware, firmware and every tool that touches the project — done for its own reasons, never to make tags resolve.

Build the address CSV from an editor export #

The dependable template is an export GP-Pro EX makes itself: it shows the header names, delimiter, field order and the address spelling the import expects.

  1. With SIMATIC S7 ETHERNET selected, create one variable by hand at a valid address.
  2. Export the variable table to CSV from the editor, and check where the file lands — why GP-Pro EX CSV export writes to the simulation folder is the path surprise to rule out first.
  3. Map the TIA export's columns into that structure, keeping the device association and the address syntax the editor's own export showed.
  4. Import a small test set and compare every row against the controller declaration before converting the full list — the same end-to-end check described for importing a PLC tag CSV into an existing HMI tag database.

One type detail from the case: rows addressed through the "word address" field only displayed correctly once their type read Word instead of Int. That change is needed for a consistent row, and it is not a resolution fix — width and interpretation are separate from whether the address exists.

Worked example: resolving DB51.DBW12 on a GP4501T #

Inputs:

  • Editor GP-Pro EX Ver. 4.07, panel GP4501T, controller S7-1500, project TIA Portal V14 — the commissioning case.
  • One variable to resolve: a word at DB51.DBW12, type Word.
  • Driver on the checklist: SIMATIC S7 Ethernet Driver Ver. 1.19.12, applicable from GP-Pro EX Ver. 2.10.000, per the driver download page.

Rule in words: the SIMATIC S7 ETHERNET series writes a word address as [device]DBxxxxx.DBWxxxxx, with the DB number and the word offset each padded to five digits.

Arithmetic:

  • Version gate: 4.07 is later than 2.10.000, so the driver version applies.
  • DB number: 51 padded to five digits is 00051.
  • Word offset: 12 padded to five digits is 00012.
  • Logical device: PLC1.
  • Assembled: [PLC1]DB00051.DBW00012.

Result: the address field displays [PLC1]DB00051.DBW00012, and the summary table shows the name, Word and the address in the right column.

Decision: import the full CSV only after this test row resolves. One UNDEFINED row after the series change means the series or the address string is still wrong, so fix that and never carry an UNDEFINED row into a project that will download. For the runtime read, the target DB must be a standard-access block on the S7-1500, because optimized blocks cannot be addressed absolutely. Prove the link with reads from a scratch address before writing anywhere that drives machine outputs.

If the address still shows UNDEFINED #

  • SERIES is still on TIA PORTAL ETHERNET — re-check that one setting before touching any column.
  • The address text does not match the driver's syntax: DBW for words, DBX for bits, spelled exactly as the editor's own export shows. A refused address at entry is its own format problem, worked in fixing invalid bit address errors when adding HMI tags.
  • The type column disagrees with the address class, as with the "word address" rows that needed Word rather than Int.
  • The driver is missing: the Version dialog under the Help function shows what is installed; add the driver package if SIMATIC S7 Ethernet Driver is absent.
  • The address resolves but the value never arrives: that is the runtime half — check the controller IP and the connection settings the driver's manual specifies, plus the standard-access property of the DB, before suspecting the import again.

Questions asked

Do I need to move the TIA Portal project back to V13?

No. The V11 through V13 limit applies to the direct project-import path, which reads the TIA project file itself. Absolute addressing through SIMATIC S7 ETHERNET never opens the TIA project; the addresses live in the HMI project and the CSV. Keep V14, and treat any migration as a separate engineering change with its own compatibility review.

Why did the names and types import but the addresses stayed UNDEFINED?

Because parsing and address resolution are separate steps. The CSV reader placed every column correctly, which the summary table showed, but the selected series offered no S7 absolute address format to map the address text into, so the editor left it UNDEFINED. Once the series provides absolute DB addressing, the same file resolves.

Where do I check which drivers GP-Pro EX has installed?

Open the Version dialog from the Help function; it lists the installed communication drivers with their versions. SIMATIC S7 Ethernet Driver Ver. 1.19.12 applies to GP-Pro EX Ver. 2.10.000 and later, so a 4.07 installation qualifies. If the series does not appear in the selection, install the driver package first.

Does the TIA PORTAL ETHERNET series have a use at all?

Yes. Its driver documentation lists the S7-1200 and S7-1500 series as supported devices, with the S7-1200 G2 series excluded, and it is the series tied to the direct TIA project import path. For a variable strategy based on absolute DB addresses, entered by hand or from CSV, SIMATIC S7 ETHERNET is the series to select.

Why did changing the type from Int to Word not fix the import?

It fixed a different problem. Rows using the "word address" field only displayed correctly once their type column read Word, so the change was needed for a consistent row. But the type only says how the sixteen bits are interpreted; the series selection decides whether the address exists at all. Resolution came from changing the series.

Keep reading

  • 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

  • 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

  • How-to

    How to Address S7 PLC Outputs in a WinCC Flexible Tag

    A WinCC flexible tag must carry the address of the real PLC operand: Bool tags on Q0.1, Q0.2 and Q0.3 for the line, delta and star outputs. DB1.DBX0.0 is bit 0 of byte 0 in data block 1 and follows an output only if the PLC program copies it there — and the S7-200 CPU family has no data blocks at all.

    HMI and touchscreens