C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Troubleshooting and Confining Cannot Write the Tag Runtime Errors in SIMATIC PCS 7

Troubleshooting and Confining Cannot Write the Tag Runtime Errors in SIMATIC PCS 7

In SIMATIC PCS 7 and CEMAT installations, the runtime error prompt 'Cannot write the tag ' occurs when an operator command, C-script, or faceplate action attempts to modify an unresolvable tag, an unparameterized tag prefix, a read-only tag, or an address for which the logged-in user lacks authorization. To isolate and resolve the root cause, execute a structured three-step confinement procedure: (1) inspect the WinCC Operator and Chronicle alarm lists to determine the exact timestamp and preceding operator action; (2) launch the application diagnostic tool 'apdiag.exe' (located in C:\Program Files (x86)\Siemens\WinCC\uTools) to monitor the Output Window for script syntax errors and missing tag paths; and (3) verify user authorization levels in WinCC User Administrator and check the block's OS_Perm parameter in CFC.

Table of Contents

Executive Summary

During plant operations and commissioning across SIMATIC PCS 7 and industry-specific add-ons such as CEMAT, operators frequently encounter generic error popups stating: 'Cannot write the tag '. Because this notification provides no direct link to the underlying graphic file, script subroutine, or logic chart, troubleshooting can quickly consume valuable engineering hours.

This error typically arises when an operator clicks a setpoint field, commands an operating mode switch, or presses an action button. If the runtime cannot write to the target tag, it aborts the operation and displays the warning. Most tag write failures stem from broken tag prefix evaluations (TagPrefix), obsolete C-script routines leftover from incomplete project migrations, lack of operator authorization in WinCC User Administrator, or restrictive controller-side permission masks (OS_Perm). This technical guide outlines the systematic confinement strategy recommended by Siemens automation specialists, details how to capture script traces using apdiag.exe, and provides a verified checklist to eliminate tag writing faults.

Architecture and Fundamental Mechanics

The tag writing mechanism in SIMATIC PCS 7 WinCC involves multiple validation boundaries between the user interface and the controller:
1. Tag Prefix Concatenation Mechanics:
* Standard APL and CEMAT faceplates are generic containers (@PG_*.pdl). When opened, the parent block icon passes its hierarchical tag path via the TagPrefix property (e.g., Plant/Unit/Motor101.).
* Internal scripts execute functions like SetTagBit(GetTagPrefix() + "AutModLi", 1).
* If TagPrefix is empty, truncated, or incorrectly formatted (e.g., missing the trailing period), the script attempts to write to an isolated string (e.g., AutModLi). WinCC Tag Management evaluates this tag, cannot find it in the project database, and generates the error: 'Cannot write the tag (unknown)'.
2. Security and Authorization Gatekeeping:
* WinCC User Administrator enforces operational permissions: Authorization 5 (Process controlling) and Authorization 6 (Higher process controlling).
* In addition, modern APL blocks utilize the controller input parameter OS_Perm (Operator Permission, a 32-bit DWORD).
* If an operator attempts an action that is disallowed by OS_Perm (e.g., attempting manual mode switch while interlocked), the faceplate script detects the disallowed bit and blocks tag writing.
3. Application Diagnostics Engine (apdiag.exe):
* WinCC includes a low-level diagnostic utility (apdiag.exe) that attaches to the C-script engine (CScriptRT.exe) and Basic Process Control runtime.
* By listening to standard output and printf streams, apdiag captures exact script execution failures, including line numbers, failing tag names, and picture window paths.

Step-by-Step Implementation Procedure

Step 1: Correlate Timestamps in Operator and Chronicle Alarm Lists

  1. In WinCC Runtime, open the Alarm Logging view.
  2. Select the Operator Messages list and the Chronicle list.
  3. Identify the exact time the 'Cannot write the tag' popup occurred.
  4. Review the preceding messages: identify which motor, valve, or controller was clicked, which screen was active, and what parameter was being modified.

Step 2: Attach apdiag.exe Application Diagnostics

  1. On the affected OS client or server, navigate to:
    C:\Program Files (x86)\Siemens\WinCC\uTools\
  2. Right-click apdiag.exe and select Run as administrator.
  3. In apdiag, click Output > Output Window.
  4. Keep the Output Window visible and return to WinCC Runtime.
  5. Re-create the operator action that triggered the error (e.g., clicking the button or entering a setpoint).
  6. Observe the apdiag Output Window: review the diagnostic printout to identify the failing picture name (e.g., @PG_APL_OA_Real.pdl), the object name, and the unresolvable tag string.

Step 3: Verify User Authorization and OS_Perm

  1. Open WinCC Explorer on the Engineering Station and open User Administrator.
  2. Verify that the logged-in user group has Authorization 5 and Authorization 6 enabled for the target plant area.
  3. Open the target CFC chart in SIMATIC Manager: inspect the technological block's OS_Perm parameter. Verify that the relevant permission bit has not been forced to 0 by upstream logic.

Step 4: Verify Tag Configuration and Read-Only Properties

  1. In WinCC Explorer, open Tag Management.
  2. Search for the tag identified by apdiag.
  3. Verify that the tag exists and that its 'Read-only' property is UNCHECKED.
  4. Open WinCC Channel Diagnosis: confirm that communication to the AS controller is 'Ready' with active read/write frames.

Step 5: Restore Standard Faceplate Pictures via OS Project Editor

If the fault stems from corrupted faceplate scripts following an upgrade:
1. In WinCC Explorer, open OS Project Editor.
2. On the Basic Data tab, ensure system pictures are selected for update.
3. Click OK to redeploy original factory faceplate scripts, compile OS, and download to runtime stations.

Verification

  1. In WinCC Runtime, log in with operator credentials.
  2. Open the affected faceplate and execute the command or setpoint modification.
  3. Confirm that the value writes smoothly without error popups.
  4. Confirm that the AS controller reflects the updated value in CFC test mode.
  5. Inspect the apdiag Output Window: verify that zero script errors or unhandled tag write exceptions are logged.

Limitations and Operational Precautions

  1. Do not leave apdiag tracing enabled with high debug levels during normal plant operations, as heavy logging can consume system resources.
  2. Custom C-scripts that modify standard APL faceplate logic will be overwritten when running the OS Project Editor; always back up custom scripts beforehand.
  3. In CEMAT installations, ensure that the CEMAT block library version on the AS matches the installed CEMAT WinCC faceplate version.
  4. Channel write failures occurring during network disconnects should be diagnosed via WinCC Channel Diagnosis rather than script editing.

Engineer FAQ

What is the first tool I should use when 'Cannot write the tag' appears?

Use apdiag.exe (located in C:\Program Files (x86)\Siemens\WinCC\uTools\). The Output Window reveals the exact script line, picture name, and tag that failed.

Why does the error message say the tag is unknown?

It typically means the faceplate's TagPrefix was missing or truncated, causing the script to attempt to write to an isolated parameter name that does not exist in Tag Management.

Can controller logic cause a tag write failure in WinCC?

Yes. If the controller block's OS_Perm (Operator Permission) bits disallow the operation, or if the parameter is locked by an active interlock, the write will be rejected.

Does this error occur in CEMAT projects as well as standard PCS 7?

Yes. CEMAT utilizes specialized faceplates built upon WinCC scripting, and missing tag prefixes or permission mismatches trigger the identical error prompt.

How do I fix faceplates that were broken after a PCS 7 upgrade?

Run the OS Project Editor in WinCC Explorer to deploy updated, consistent system faceplate pictures (@PG_...) from the global library.

Technical References

Related Articles

Related Tags

  • apdiag
  • Cannot Write Tag
  • WinCC Scripting
  • CEMAT
  • Tag Management
20 respuestas