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

Why PCS 7 Faceplate Interlock Buttons Gray Out in Non-English Languages and How to Fix It

Why PCS 7 Faceplate Interlock Buttons Gray Out in Non-English Languages and How to Fix It

In SIMATIC PCS 7 OS runtime, the interlock jump button on equipment faceplates (such as motors and valves) functions normally in English but becomes grayed out and inoperable when the runtime language is switched to German, French, or Spanish. This failure occurs when the target language was added to the WinCC OS project without configuring corresponding multilingual project languages in SIMATIC Manager or without performing a full OS compilation. APL faceplate C-scripts query the WinCC Text Library to verify interlock block type descriptors and permission strings; if the Text Library contains empty records for the active runtime language, the script fails string validation and disables the jump button. To restore functionality, configure the language in SIMATIC Manager, export/import multilingual texts, and execute an Entire OS Compile with memory reset.

Table of Contents

Mechanics of Faceplate Interlock Navigation in PCS 7 APL

In the Advanced Process Library (APL), equipment faceplates (@PG_MotL.pdl, @PG_VlvL.pdl) provide direct navigation buttons to jump to interconnected interlock blocks (Intlk02, Intlk04, Intlk08):
1. When an operator opens a motor faceplate, the APL runtime script reads the interconnected interlock tag from the block's Permit, Intlock, or Protect structure inputs.
2. The script queries the WinCC Text Library and internal system tags to determine:
- Does an interconnected interlock block exist?
- What is the block type and faceplate window designation?
- Does the current operator have authorization to open the interlock faceplate?
3. If all criteria evaluate to true, the navigation button becomes active and clickable. If any check fails, the button remains visually grayed out.

Root Cause: Asymmetric Text Library Population Across Languages

The primary root cause of language-dependent grayed-out buttons is incomplete multilingual synchronization between the Engineering Station (AS project) and the Operator Station (WinCC Text Library):

  • The English Baseline: Most engineering projects are developed initially with English (United States) as the default language. During initial OS compilation, PCS 7 populates the English column of the WinCC Text Library with block comments, units, and internal APL type strings.
  • Adding a Runtime Language in WinCC Only: If an engineer simply opens WinCC Explorer and adds German or French under Computer Properties > Parameters > Language, WinCC creates blank columns in the Text Library.
  • The Missing String Fault: When an operator switches runtime to German, the APL C-script executes GetTextString() to retrieve the interlock jump definition. Because the German column is blank (NULL), the string comparison fails, and the script assumes the interlock block is invalid, graying out the button.

Why ES Simulation Behaves Differently Than Dedicated OS Clients

Engineers often report that interlock jump buttons work in all languages on the Engineering Station during WinCC OS Simulation, but fail when downloaded to dedicated OS Servers and OS Clients.

This discrepancy stems from Server Data Package Generation:
* On the ES, local project files and cross-reference tables are directly accessible.
* On distributed OS Clients, faceplate scripts rely strictly on downloaded Server Data packages (*.pck) and the local Text Library. If server data packages were generated before the multilingual OS compile completed, clients lack the localized block pointers.

Method: Step-by-Step Language Synchronization and Text Compilation

To ensure interlock buttons function across all supported plant languages:

  1. Verify Project Languages in SIMATIC Manager:
    - In SIMATIC Manager, select the top-level project and click Options > Set Project Language.
    - Ensure that all desired plant languages (e.g., English, German, French) appear in the right-hand Languages installed in the project box.
    - If a language is missing, add it and click Set as default temporarily if required.
  2. Synchronize Multilingual Block Texts:
    - In SIMATIC Manager, select Options > Manage Multilingual Texts > Export.
    - Export all block texts, comments, and messages to a comma-separated (*.csv) file.
    - Open the CSV file in Excel. Verify that text columns for the non-English language are populated with valid translated names or cloned from the English column.
    - Import the completed CSV file back via Options > Manage Multilingual Texts > Import.
  3. Configure WinCC Project Editor for Multilingual Support:
    - In WinCC Explorer on the OS Server, open the OS Project Editor.
    - On the Layout tab, verify that your multi-language screen resolution is selected.
    - Click OK to re-apply multilingual system script templates.
  4. Execute Entire OS Compile with Memory Reset:
    - In SIMATIC Manager, right-click the OS project and select Compile OS.
    - In the wizard, select Scope: Entire OS and check the box With memory reset (Urlöschen).
    - Under Select the network connections, verify all active AS connections are checked.
    - Complete compilation. The compiler populates all language columns in the WinCC Text Library.
  5. Update Server Data and Download to Clients:
    - In SIMATIC Manager, right-click the OS Server and select Server Data > Generate.
    - Download the updated OS Server project and OS Client projects.

Verification

To verify that faceplate interlock buttons operate correctly in all languages:

  1. In WinCC Explorer on the OS Server, open Text Library.
  2. Filter the table by Text ID or search for your interlock block names. Verify that every row contains text in both English and the secondary language columns.
  3. Start WinCC Runtime.
  4. Switch the runtime language to the secondary language (e.g., German) using the language selection menu.
  5. Open the motor or valve faceplate.
  6. Verify that:
    - The interlock button is visually enabled (full color, not grayed out).
    - Clicking the button opens the interlock faceplate popup with localized labels.

Limitations and Operational Precautions

  • Entire OS Compile Duration: Executing an 'Entire OS Compile with Memory Reset' on large projects with tens of thousands of tags can take from 30 minutes to over 2 hours. Plan this compile during scheduled engineering windows.
  • Loss of Manual Text Library Edits: Performing an OS compile with memory reset overwrites manual text changes made directly inside the WinCC Text Library. Always maintain multilingual translations in the SIMATIC Manager project using the export/import tool.
  • Faceplate Security Permissions: Even with correct language tables, the interlock button will remain disabled if the logged-in operator lacks the required user authorization level (e.g., Authorization Level 5 'Process controlling' or Level 6 'Higher process controlling').

Engineer FAQ

Why does the interlock button work in English even when texts are unconfigured?
Because PCS 7 block templates and APL faceplates use English as the hardcoded fallback language. If an English string exists, the internal script comparison succeeds.

Can I fix this problem by editing the WinCC Text Library directly on the OS Server?
You can manually fill in the missing translated text in the Text Library as a temporary hotfix. However, the next OS compilation from the Engineering Station will overwrite those manual edits unless they are synchronized in SIMATIC Manager.

Do I need to compile the Automation System (AS) to fix this issue?
No. Language translation tables and faceplate navigation pointers reside entirely on the OS Server and OS Client level; controller logic is language-independent.

Technical References

  • Siemens Industry Online Support Entry ID 109742323: SIMATIC Process Control System PCS 7 Advanced Process Library (APL) Function Manual
  • SIMATIC PCS 7 APL Manual (Document No. A5E03601458)
  • Siemens Industry Online Support Entry ID 56897157: Configuring Multilingual Projects in SIMATIC PCS 7

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=simatic+pcs7
  • https://industrialautomation.net/search?query=advanced-process-library
  • https://industrialautomation.net/search?query=wincc-faceplates
  • https://industrialautomation.net/search?query=text-library
20 respuestas