Troubleshooting Missing BatchCC Toolbar Icon in PCS 7 OS Client Runtime and Custom Button PDLs

The BatchCC shortcut icon in the PCS 7 OS bottom toolbar (@Buttons11.pdl / @Buttons12.pdl) fails to appear if the station is not configured as a Batch Client, or if custom button picture files lack the dynamic registry evaluation script. During runtime startup, WinCC executes a C-script on the BatchCC button that queries the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\AUTSW\BATCH (or 32-bit WOW6432Node). If the Batch Client package is not installed or the registry key is missing, the button's Visible property is set to FALSE. Furthermore, when engineers customize @Buttons12.pdl without copying the internal script logic, or overwrite it during an unmanaged OS Project Editor pass, the icon disappears. Restoring the script logic and verifying Batch Client registration restores the icon.

Executive Summary

The bottom button navigation strip in SIMATIC PCS 7 WinCC OS runtime provides plant operators with immediate access to core supervisory tools, including SFC Visualization, Alarm Logging, Trend Systems, and SIMATIC BATCH Control Center (BatchCC). A frequent commissioning issue occurs when the BatchCC shortcut button displays correctly when using factory template pictures (@Buttons11.pdl / @Buttons12.pdl), but completely disappears when custom button pictures are deployed or when migrating OS Client stations. This article analyzes the dynamic Windows registry inspection mechanisms governing toolbar button visibility, explains OS Project Editor template management, and provides step-by-step instructions to restore the BatchCC icon in customized OS layouts.

Architecture and Fundamental Mechanics

WinCC Toolbar Button Architecture and Dynamic Visibility Mechanics:

Toolbar Structure: @Buttons11.pdl and @Buttons12.pdl:
In PCS 7 OS runtime, the bottom navigation bar is divided into picture banks. @Buttons11.pdl contains primary system functions (alarm acknowledgment, horn silencing, screen navigation), while @Buttons12.pdl hosts secondary tools (BatchCC, SFC Visualization, Maintenance Station, PDM).
Operators switch between button banks using arrow toggles on the right side of the toolbar.
Registry-Driven Dynamic Visibility Logic:
The BatchCC button in @Buttons12.pdl is not statically visible. It contains a dynamic C-script assigned to the Visible (Display) property of the button object.
On picture open, the C-script invokes Windows API functions to inspect the local registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\AUTSW\BATCH (or SOFTWARE\WOW6432Node\Siemens\AUTSW\BATCH on 64-bit operating systems).
If the registry key exists and indicates an active Batch Client installation, the script returns 1 (Visible = TRUE).
If the key is absent (such as on standard OS Clients where SIMATIC BATCH Client was omitted, or on OS Servers where operator launchers are suppressed by design), the script returns 0 (Visible = FALSE), hiding the button.
Custom Button PDL Breakages:
When engineers customize @Buttons12.pdl (e.g. adding company logos, re-ordering buttons, or altering screen resolutions), they frequently paste standard button graphics while failing to copy the internal C-action or omitting necessary global header inclusions (#include 'apdefap.h').
Additionally, running OS Project Editor with default settings can overwrite customized PDL files with standard factory templates, or leave custom button pictures disconnected from the screen layout hierarchy.

Step-by-Step Implementation Procedure

Verify Local SIMATIC BATCH Client Installation and Registry Key:
* Log on to the target OS Client station with administrative privileges.
* Open the Windows Registry Editor (regedit.exe).
* Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Siemens\AUTSW\BATCH.
* Verify that the key exists and contains valid path values pointing to the Batch installation folder (e.g. C:\Program Files (x86)\Siemens\Batch).
* If the key is missing, run the SIMATIC PCS 7 installation media on the client and install the 'SIMATIC BATCH Client' software package.
Inspect Custom Button Picture in Graphics Designer:
* Open WinCC Explorer on the Engineering Station (or OS Client project).
* Open your active button picture file (e.g. @Buttons12.pdl or custom MyButtons12.pdl) in Graphics Designer.
* Select the BatchCC button object and open its Object Properties dialog.
* In the Properties tree, navigate to Miscellaneous -> Display (or Visible).
* Check the dynamic column: confirm that a dynamic C-action is present and configured to execute on picture load.
Restore Standard Dynamic C-Script Logic:
* If the dynamic script is missing or corrupt, open the factory template @Buttons12.pdl located in the WinCC installation pool:
<Siemens_Dir>\WinCC\Options\PDL\Base_Data_Pool\@Buttons12.pdl.
* Copy the dynamic C-script from the factory BatchCC button's Display property and paste it into your custom button object.
* Verify that the button's Mouse Click event contains the standard execution call: PCS7_OpenBatchCC(); or ProgramExecute('BatchCC.exe');.
Configure OS Project Editor Protection Settings:
* Open OS Project Editor from WinCC Explorer.
* Select the Basic Data tab.
* In the list of system PDL files, locate @Buttons12.pdl.
* If maintaining custom modifications, select Do not overwrite (or use a dedicated custom layout name) to prevent future OS Project Editor runs from overwriting your custom script.
* Click OK to apply.
Validate Runtime Operation on OS Client:
* Activate WinCC Runtime on the OS Client.
* Navigate to button bank 2 using the bottom toolbar navigation arrows.
* Confirm that the BatchCC button is clearly visible and that clicking it successfully opens BatchCC.

Verification

Verify BatchCC Launcher Visibility and Execution:
1. In WinCC Runtime on the OS Client, confirm that the BatchCC icon is displayed in the bottom button strip.
2. Click the BatchCC icon; verify that SIMATIC BATCH Control Center launches without Windows error dialogs.
3. Open the WinCC diagnostic viewer (apdiag.exe -> Output Window) and confirm that 0 script compilation or execution errors are reported when loading @Buttons12.pdl.

Limitations and Operational Precautions

Operational Precautions and Role Restrictions:
- By Siemens architectural design, BatchCC is an operator client application. It should not be forced into the toolbar of dedicated OS Servers, which should run headless or restricted to engineering diagnostics.
- Never modify original template files in the Base_Data_Pool directory; always copy files into the local project GraCS folder before customizing.
- Ensure that operator Windows user accounts belong to the local Windows user group SIMATIC BATCH to prevent access-denied errors upon launching BatchCC.

Engineer FAQ

Why does the BatchCC icon show in @Buttons12.pdl but disappear in my custom PDL?

Custom button PDLs frequently omit the dynamic C-script attached to the button's Display property, which queries the Windows registry for an installed Batch Client before setting visibility to TRUE.

Is the BatchCC icon supposed to appear on the OS Server runtime toolbar?

No. By product design, OS Servers do not display operator client launchers like BatchCC in their toolbar, even if the OS Server also acts as the SIMATIC BATCH Server.

What registry key controls BatchCC button visibility?

The button script queries HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Siemens\AUTSW\BATCH. If this key is missing, the button remains invisible.

What happens if OS Project Editor runs with default settings?

OS Project Editor will overwrite modified system PDL files (like @Buttons12.pdl) with factory defaults unless the file is marked as 'Do not overwrite' on the Basic Data tab.