ProTool Tag Address Modification Across Multiple HMI Screens

Overview of the ProTool Tag Modification Problem

ProTool is the legacy Siemens configuration software used to program SIMATIC Operator Panels (OP), Touch Panels (TP), and early Multi Panels (MP) before the product line was succeeded by WinCC Flexible (2004) and later TIA Portal WinCC (2010). A common engineering task when commissioning, retrofitting, or migrating SIMATIC systems is the need to modify a tag address that is referenced by several screens, scripts, alarms, and recipes inside the same ProTool project.

ProTool projects are not global search-and-replace friendly: a tag instance bound to a screen object (a numeric I/O field, a bar, a trend view, a status display, an event-driven change) holds an internal pointer to a tag definition located in the central tag list. Modifying the address column of that tag definition will automatically propagate the change to every consumer of the tag — provided the data type is preserved, the connection remains valid, and the new address is reachable over the configured logical connection.

This article documents the supported, supported-with-caveat, and unsupported approaches for modifying a tag address in ProTool, the role of the Cross Reference tool, the data type preservation rule, and the recommended verification workflow before downloading the revised project to the panel.

Prerequisites

Before performing a tag address modification in ProTool, verify the following:

• ProTool installation: ProTool V6.0 SP2 or ProTool V6.0 SP3 is installed on the engineering workstation. ProTool CS (Configuration Software) is the design-time environment. ProTool/Pro RT is the runtime that executes on the panel itself.
• Project backup: A complete .pdb or .pba backup of the active ProTool project has been archived. ProTool does not provide project versioning comparable to TIA Portal; manual snapshots are the only safe rollback path.
• PLC program symbol table: A current export of the STEP 7 symbol table (S7-300/400) or the local symbol table of Micro/WIN (S7-200) is available so the new tag address can be validated against the PLC truth source.
• Online connection to the panel: A serial, MPI, PROFIBUS, or Ethernet path exists between the engineering PC and the target OP/TP/MP so the compiled project can be downloaded and the runtime tested.
• Original tag definition recorded: Note the original tag name, data type, PLC connection, and address. This information is required for cross-reference reconciliation and rollback if the new address proves incorrect.

ProTool Tag Architecture: Internal, External, and System Tags

ProTool classifies every variable in a project into one of three categories. The address-modification rules differ between them.

Speed references that drive setpoint inputs, actual-value displays, and trend archives on a machine HMI are almost always external tags pointing into a STEP 7 data block or a Micro/WIN V-memory area. This is the tag class where address modification is meaningful.

Supported PLCs and Communication Drivers

ProTool V6.0 ships with a fixed set of PLC drivers. The tag address syntax accepted in the address column depends on which driver is bound to the logical connection.

The communication driver is selected under Project > Connections in ProTool. Once the driver is set, the address field in the tag list validates the entered string against that driver's grammar.

Step-by-Step: Modifying an Existing Tag Address

This is the preferred approach when the tag name should be preserved (e.g. it is used as a script variable, in a recipe, or in a multi-language export) but the underlying PLC address must change — for example when an S7 program has been refactored and the data block layout has shifted.

1. Open the project in ProTool CS. From the project tree, expand Tags and select Tag List. The tag list editor opens in the working area.
2. Locate the target tag by name (e.g. Speed_Setpoint or SP_Motor1). Sorting by the Name column accelerates the search; the Filter button (funnel icon) supports substring filtering.
3. Record the original values of Connection, Data type, Length (for STRING), Acquisition cycle, and Limit value monitoring. These must remain identical after the change.
4. Edit the Address column of the tag in place. Type the new absolute address in the syntax required by the configured connection (for example DB12.DBD12 or VW220). Press Enter to commit. ProTool performs a syntax check; an invalid address displays a red field background and a tooltip describing the parse error.
5. Confirm data type preservation. ProTool does not warn if you change the data type by accident — it only validates address syntax. The engineer must manually verify the new address has the same physical width as the original (e.g. DBD = DWORD 32 bits; the replacement must point at a DWORD, not at a WORD or a BOOL).
6. Save the project with File > Save or Ctrl+S. The project tree updates the modification timestamp on the Tags node.
7. Compile with Project > Compile > All. Any unresolved cross-reference errors appear in the Output window.
8. Download the compiled runtime to the panel using File > Transfer > to Panel…. For a recipe-only change, a partial transfer (transfer only the tag database) may be selected under Settings > Transfer.

Step-by-Step: Creating a New Tag and Bulk Reassignment

When the existing tag must be retired — for example because its data type must change (INT → REAL), because its acquisition cycle must change, or because the old address will continue to be used by another consumer — ProTool requires the engineer to create a new tag and reassign it to each screen object.

1. Document every consumer of the old tag using the Cross Reference tool (Tools > Cross Reference or Ctrl+Alt+F). Export the result to a text file or print it for traceability.
2. Create the replacement tag in the Tag List (Tags > New Tag or right-click in the tag list and choose Append Tag). Assign the new PLC address, set the data type to whatever the new address supports, and configure acquisition / limit monitoring as required.
3. Open each screen that references the old tag. For every object bound to the old tag — typically a numeric I/O field, a slider, a bar, a status display, an animation, or a script event — open the object properties dialog (View > Properties) and select the new tag from the Tag dropdown list.
4. Replace script references by opening the script editor (Tools > Script if scripts are enabled in the project) and renaming every occurrence of the old tag symbol. ProTool does not have a script-level find-and-replace; manual editing or an external text editor on a stripped export is required.
5. Update alarms and recipes. If the old tag was bound to a discrete alarm or used inside a recipe structure, open Alarms > Discrete Alarms and Recipes and re-bind the references to the new tag.
6. Save, compile, and transfer as in the modify-in-place procedure.
7. Leave the old tag in place with a _deprecated suffix until the panel has been observed in production. Removing it prematurely will leave dangling references in compiled scripts that ProTool cannot warn about at runtime.

Cross-Reference Function for Bulk Updates

The Cross Reference tool (Tools > Cross Reference) is the engineer's primary safety net. It enumerates every location in the project — screens, templates, scripts, alarms, recipes, schedules, area pointers — where a given tag is referenced.

The cross-reference list is sorted by location. Right-clicking an entry opens the corresponding editor at the exact line, accelerating manual reassignment.

Data Type Preservation Rules

ProTool stores the data type with the tag definition, and every consumer of the tag relies on it. Changing the data type — even when the new type would physically fit the same memory area — is the single most common cause of "the value reads wrong after the address change" symptoms.

Symbolic vs Absolute Addressing in ProTool

When the ProTool connection is configured as "symbolic" (under Connection > Properties > Mode), the tag address column accepts STEP 7 symbol names rather than absolute addresses. In symbolic mode the address field shows the symbol; in absolute mode it shows DBx.DBWy.

• Symbolic mode advantage: The PLC program can be reorganized (a data block can be renumbered, an area can be moved) without touching the ProTool tag list, because ProTool resolves the symbol to the new absolute address at runtime.
• Symbolic mode disadvantage: The ProTool project must carry a copy of the STEP 7 symbol table, which has to be refreshed whenever the PLC program is recompiled with new symbols.
• Absolute mode advantage: The address is unambiguous and survives STEP 7 symbol-table refactoring as long as the data block layout is preserved.
• Absolute mode disadvantage: Any PLC-side data block renumbering forces a bulk update of every affected ProTool tag.

For projects where the data block layout is volatile (frequent STEP 7 refactoring during commissioning), symbolic mode with periodic symbol-table refresh is the lower-maintenance choice.

Compilation, Project Backup, and Download Procedure

The project compile step translates the tag list, screens, scripts, alarms, and recipes into a runtime image. A clean compile is mandatory before download.

1. Clean rebuild: Project > Compile > All (Rebuild). Incremental compile sometimes hides stale references after a tag modification; the rebuild option regenerates the runtime image from scratch.
2. Review the compile output: The Output window displays errors, warnings, and informational messages. Resolve every error before transfer. Warnings about deprecated tags, unused tags, or duplicate names should be triaged.
3. Stage the project backup: Before download, copy the compiled runtime image (typically *.fwd for OP/TP) to a versioned backup directory such as D:\HMI\Backups\<ProjectName>_<YYYYMMDD_HHMM>\.
4. Initiate transfer: File > Transfer > to Panel…. Configure the channel (MPI address, PROFIBUS address, or IP for Ethernet-based panels such as MP370). Set the transfer mode to "Complete" for tag-database changes — partial transfer does not always update the tag database on legacy OP panels.
5. Confirm on the panel: The OP/TP/MP displays a confirmation prompt ("Receive transfer?"). Accept, then wait for the progress bar to complete without interruption.
6. Allow automatic restart: The panel reboots into the new runtime image. Observe the splash screen and confirm the project name and version string match the expected build.

Verification and Runtime Testing

After download, perform a structured verification sequence before handing the system back to operations.

Migration Path: ProTool to WinCC Flexible / TIA Portal

ProTool V6.0 reached end-of-life when WinCC Flexible 2004 superseded it. ProTool projects can be migrated to WinCC Flexible via Project > Migrate ProTool Project; WinCC Flexible projects can be migrated to TIA Portal WinCC via Migration > Migrate WinCC Flexible project in TIA Portal V13 or later.

The migration preserves the tag list, screen layout, alarms, and recipes — but address syntax may need minor adjustment because TIA Portal accepts symbolic tags using the S7-1500 symbol-table format. The following mapping is typical:

For sites planning repeated tag changes, migrating to TIA Portal is the only durable remediation: TIA Portal supports project-wide tag renames and address changes that propagate to every consumer automatically, with a cross-reference graph that updates in real time.

Troubleshooting Matrix