Keep Custom APL Block Icon Pictures After PCS 7 OS Compilation

If OS compilation changes an APL block icon's custom picture folder to PCS7CustomPictures, check whether the folder attribute is configured on the generated APL block-icon instances. Siemens documents that the default is inserted when the instance has no folder value. Store custom images under the OS project's GraCS tree and verify the instance attribute after block-icon generation; a setting only in a @PCS7Typicals template may not be the value used at compile time.

Why the folder value can change

The symptom matches documented PCS 7 behavior for custom APL block-icon pictures: when the Directory for pictures attribute is not configured for an APL block-icon instance, OS compilation writes the default PCS7CustomPictures value. A custom typical file may exist while the process-picture instance still lacks the explicit folder assignment. Confirm the setting on generated block-icon instances, not only in the typical template.

Configure the custom-picture folder

Siemens' Operator Station V10.0 Configuration Manual says PCS7CustomPictures is the default custom-picture folder under the OS project's GraCS directory, additional subfolders may be created there, and the folder attribute determines which picture folder the APL icon uses. For the reported MotorSpdCL folder, confirm that the folder exists within GraCS or a subfolder and set the desired folder name in the APL block icon's configuration attribute for the actual generated instances. The exact label may vary by PCS 7 release (Directory for pictures/Folder for pictures).

Check the template and generated instances

Back up the OS project. 2. Confirm the custom images are stored in GraCS\MotorSpdCL (or the actual intended subfolder) and retain the picture filenames expected by the APL block icon. 3. In the process picture, inspect a generated APL motor block icon's configuration and check whether the custom-picture folder attribute is empty or explicitly set. 4. Compare the value in the @PCS7Typicals-based source with the value on the generated instance. 5. Regenerate block icons and compile the OS in a test copy, then inspect whether the custom folder assignment persists.

Why setting the template alone may not be enough

PCS 7 generates block icons from typified templates and instance attributes. The V10.0 manual describes the compile-time default specifically when no folder value is configured for the APL block-icon instances. If MotorSpdCL is set only in a template but not carried into the relevant instance configuration, the default can replace it. Verify the exact generation procedure for the installed PCS 7 version before changing @PCS7Typicals files.

Verification

After test compilation, inspect the instance property again and verify the intended images are loaded from the expected GraCS subfolder in process mode. Test the server and transferred OS client copies as applicable. Confirm that re-running the supported generation/compile workflow does not reset the setting.

Limitations and Operational Precautions

The source does not state the PCS 7/WinCC/APL version or whether MotorSpdCL exists inside the OS project's GraCS tree. The opened detailed manual is V10.0, while the exact Directory for pictures wording also appears in Siemens' V9.0 manual result; confirm the matching release. Do not edit or replace standard @@PCS7Typicals files directly: Siemens Operator Station documentation warns that original typicals are overwritten by updates and instructs users to create a separate @PCS7Typicals... file.

Engineer FAQ

Why does the field become PCS7CustomPictures during OS compile? Siemens documents that this default is entered when no custom-picture folder is configured for APL block-icon instances.

Where should MotorSpdCL be located? In the OS project's GraCS folder or a subfolder under it, according to the Operator Station guidance.

Is setting the folder in @PCS7Typicals always sufficient? Not necessarily; compare the actual generated APL block-icon instance property because compile defaults can be applied at instance level.

Can I modify the original typical file? Siemens advises against modifying originals because updates can overwrite them; use a separate custom @PCS7Typicals file.

How can I prove the fix survives compilation? Recreate/update block icons and compile a backed-up test OS, then inspect both the assigned folder value and the displayed images.

Technical References

SIMATIC PCS 7 Operator Station V10.0 Configuration Manual, section “Displaying custom pictures in APL block icons” (p. 158); describes PCS7CustomPictures as the default and says compile inserts it when an APL instance has no configured folder value.
SIMATIC PCS 7 Operator Station V9.0 Configuration Manual, search-indexed section “Displaying custom pictures in APL block icons”; uses the Directory for pictures attribute terminology. The PDF was blocked during direct retrieval.
Operator Station V8.0 SP1 Configuration Manual, section 7.2.3; says use a separate file whose name begins @PCS7Typicals for custom icons rather than changing the original file.

Keep Custom APL Block Icon Pictures After PCS 7 OS Compilation