How to Resolve Text ID Collisions and 'CiR Parameter Assignment Not Successful' Faceplate Texts in PCS 7

In SIMATIC PCS 7, faceplates and block icons displaying inappropriate texts such as 'CiR parameter assignment not successful' are caused by Text ID collisions in the WinCC Text Library. This condition typically occurs when an unsupported regional display language (e.g., English-Malaysia) is added, or when display languages mismatch between Step 7 AS projects and the WinCC OS. During OS compilation, diagnostic driver strings from Basis Library blocks (such as Configuration in RUN diagnostic texts) overwrite Text ID 1 or displace user text pointers. Harmonizing display languages across all AS and OS projects in SIMATIC Manager and rebuilding the Text Library resolves the issue.

Text Library Architecture and Text ID Pointer Mapping

In SIMATIC PCS 7, multi-language visualization across Operator Stations is coordinated by the WinCC Text Library editor. Every text string displayed in runtime—including faceplate labels, block comments, unit designations, and alarm texts—is assigned an internal numeric identifier known as a Text ID.

When an engineer configures technological blocks in CFC:
* Block parameters with text attributes (e.g., s7_m_c, BLK_Jump, Identifier) are assigned a Text ID reference during the OS compilation process.
* The OS compiler exports these strings from the Step 7 project database into the WinCC SQL Server database, generating language-specific columns within the Text Library.
* Graphic elements and C/VBS faceplate scripts dynamically query the Text Library at runtime using functions like GetText(TextID) or GetLinkedText() based on the currently active runtime language.

Root Cause Analysis for Text ID Collisions and CiR Messages

In migrated projects (e.g., upgrading to PCS 7 V8.1 with customer-specific libraries like APL4BASF), engineers often encounter an anomaly where APL drive faceplates or block status texts suddenly display:
'CiR parameter assignment not successful' (or German: 'CiR Parametrierfehler').

Upon inspecting the WinCC Text Library, engineers find that Text ID 1—which normally hosts an empty default string or the primary block identifier—has been populated with this diagnostic message.

Why Text ID 1 Is Overwritten

Basis Library Driver Wizard Diagnostics: When CFC is compiled with 'Generate module drivers', the wizard imports diagnostic blocks into @Charts (e.g., MOD_D1, MOD_D2, CPU_DIAG). These blocks carry pre-packaged system diagnostic messages related to Configuration in RUN (CiR).
Display Language Desynchronization: If a user creates or opens a project using an unaligned regional language dialect (e.g., English (Malaysia) instead of the standard English (United States)), Step 7 treats the language as a custom locale.
Index Shifting in OS Compile: If the default display language in Step 7 (Options -> Language for Display Devices) does not exactly match the WinCC project's Default Language at Runtime, the OS compiler misaligns the internal string allocation index. System diagnostic strings from XML descriptors (AL_CPU.xml, Al_crack.xml) are written into Text ID 1, corrupting all graphical objects referencing that default pointer.

Step-by-Step Remediation Procedure

To resolve the Text ID conflict and restore pristine faceplate labeling:

Step 1: Harmonize Languages for Display Devices in SIMATIC Manager

In SIMATIC Manager, select the root multiproject or the AS project folder.
Navigate to menu Options -> Language for Display Devices....
Inspect the Installed Languages and Default Language:
* Ensure that standard locales are used (e.g., English (United States)).
* If regional variants (e.g., English (Malaysia)) were added, delete them or set English (United States) as the Default Language.
Repeat this check for every AS project and the OS project within the multiproject to ensure 100% uniformity.

Step 2: Align WinCC Computer Runtime Language Settings

Open the OS project in WinCC Explorer.
Right-click the Computer icon in the left pane and select Properties.
Navigate to the Parameters tab.
Verify that:
* Language Setting at Runtime: Configured to match the AS default (e.g., English (United States)).
* Default Language at Runtime: Set to the identical language.
Click OK.

Step 3: Clean and Rebuild the WinCC Text Library

In WinCC Explorer, double-click Text Library.
Search for the text string 'CiR parameter assignment not successful' or inspect Text ID 1.
If Text ID 1 contains the CiR diagnostic string, delete the string text in that row (leaving the cell blank or restoring the original identifier).
In SIMATIC Manager, right-click the OS project and select Compile.
Select Entire OS with 'Tags and messages' checked.
The compiler repopulates the Text Library with aligned language pointers, ensuring system CiR messages are assigned to dedicated high-index IDs rather than Text ID 1.

Language Synchronization and Text Library Reference Matrix

The following table outlines the required configuration settings across SIMATIC Manager and WinCC to prevent text corruption:

Configuration LevelSetting LocationStandard SettingMisconfiguration RiskStep 7 AS ProjectOptions -> Language for Display DevicesEnglish (United States)Mixed dialects cause Text ID shiftingStep 7 OS ProjectOptions -> Language for Display DevicesEnglish (United States)Language mismatch with AS blocksWinCC Computer PropertiesComputer Properties -> ParametersEnglish (United States)Runtime displays missing text markersWinCC Text LibraryWinCC Explorer -> Text LibraryText ID 1 = Empty/BaseText ID 1 overwritten = System-wide display errorDriver Wizard XMLsSiemens\Step7\S7data\DriverCertified Siemens XML filesModifying XMLs forces diagnostic index errors

Maintaining unified display languages guarantees consistent text resolution across all operator faceplates.

Verification

To verify that the text collision has been resolved:
1. In WinCC Explorer, open the Text Library; confirm that Text ID 1 no longer contains the CiR error text.
2. Activate WinCC Runtime.
3. Open the faceplate of any technological drive block (MotL, VlvL, VlvAnL).
4. Verify that block titles, unit designations, and operating modes display clean, intended engineering texts.
5. In CFC Editor, check that block comments and identifiers match the runtime display exactly.
6. Check the WinCC alarm list; verify that system alarms report clear diagnostic descriptions without garbled text.

Limitations and Operational Precautions

Never manually edit Siemens system driver XML files (AL_CPU.xml, Al_crack.xml, Al_rackm.xml) in an attempt to suppress diagnostic texts; doing so will corrupt future Driver Wizard runs.
When adding a new operating language to a PCS 7 plant, always perform the addition in SIMATIC Manager under 'Language for Display Devices' first, never directly in the WinCC Text Library alone.
If multi-language projects are used, all message texts and block comments must be translated and populated across all columns in the Text Library, or switching languages will yield blank labels.
Always back up the multiproject (File -> Archive) before running full OS compilations with memory reset.

Engineer FAQ

Why did the CiR message appear on blocks that have nothing to do with CiR?

Because the CiR error text accidentally captured Text ID 1 during an unaligned OS compile. Any graphical block or faceplate script whose string reference defaulted to ID 1 rendered that string.

Can I delete Text ID 1 completely from the Text Library?

No. Text IDs are relational indices in the WinCC database. You should clear the string contents within the language columns of Text ID 1 rather than attempting to delete the structural row.

What does 'CiR' stand for in SIMATIC PCS 7?

CiR stands for 'Configuration in RUN', a feature enabling engineers to add distributed I/O racks, modules, and field devices to an active S7-400 system without switching the CPU to STOP mode.