WinCC PCS 7 Block Icon Orientation: Vertical to Horizontal

In a PCS 7 process picture, a single automation block (VlvL, VlvAn, Mot, PIDCtrl) can be represented by several visual variants. The most common split is horizontal versus vertical, driven by the piping layout drawn on the P&ID. The challenge with PCS 7 is that the AS-OS transfer mechanism is designed to instantiate one canonical block icon per (tag, type) tuple, while field engineers routinely need the same tag drawn on multiple pictures (overview plus detail) with different orientations on each. This reference documents the supported workflows for changing block icon orientation, the role of the @ symbol convention in opting icons out of automatic management, the Type assignment on CFC blocks, and the field-proven verification steps.

Overview

PCS 7 separates automation logic (CFC/SFC in the AS) from HMI graphics (WinCC Explorer on the OS). During an AS-OS transfer, the OS compile reads the block icon Type assigned in each CFC block's Object Properties, opens the corresponding typicals picture (@PCS7TypicalsAPLVx.pdl or @TemplateAPLVx.pdl), and instantiates the matching block icon into the process picture that corresponds to the plant hierarchy folder holding the CFC chart.

By default, this mechanism is destructive: if more than one icon of the same (tag, type) exists across the OS server, all but one are removed during the next transfer. The @ symbol prefix is the lever that determines whether a particular icon is system-managed or user-managed.

Three supported paths exist for handling multiple orientations of the same tag:

1. Method 1: Re-derive via CFC and AS-OS transfer — used when the project follows the plant hierarchy and the process picture is auto-generated.
2. Method 2: Manual copy from @PCS7TypicalsAPLVx.pdl or @TemplateAPLVx.pdl — used for pictures outside the plant hierarchy (custom overview, composite graphics, or duplicate visual representations).
3. Method 3: TIA Portal WinCC object rotation — for projects on the TIA Portal platform (Unified, Comfort Panels, RT Advanced, RT Professional), where PCS 7's typicals library is not in use.

Method Selection Flowchart

Prerequisites

Understanding the @ Symbol Convention in PCS 7 Block Icons

PCS 7 distinguishes between system-managed and user-managed block icons through the leading @ character in the icon's Type field. This single character controls whether the AS-OS transfer regenerates, replaces, or leaves the icon alone.

The implication for orientation changes: a manually placed icon whose Type does not match the block icon property of any CFC chart will survive the next AS-OS transfer. Removing the @ from the Type field, or changing the suffix number, are both valid ways to opt out of automatic management.

For valves, the CFC block icon property uses an integer suffix to control the visual orientation:

The setting is made on the block's Object Properties dialog: right-click the block in the CFC editor, select Object Properties…, switch to the Block Icon tab, and pick the value from the Block icon drop-down.

Method 1: Re-derive the Block Icon via CFC and AS-OS Transfer

This is the canonical PCS 7 workflow when the project follows the plant hierarchy and the process picture is auto-generated. The OS compile reads the block icon property from the CFC and re-draws the icon accordingly.

1. Open the CFC chart containing the valve block in the CFC Editor.
2. Right-click the block and choose Object Properties….
3. Switch to the Block Icon tab.
4. Change the Block icon drop-down to the desired orientation. For example, change from 1 (horizontal) to 2 (vertical).
5. Click OK to apply, then save the CFC chart.
6. In WinCC Explorer, select the OS server project.
7. Choose OS → Compile OS… (or AS-OS Transfer depending on PCS 7 version).
8. In the compile dialog, ensure both Pictures and Block icons are enabled.
9. Click Compile/Transfer.
10. Open the process picture bound to the hierarchy folder of the CFC chart. The block icon will be redrawn with the new orientation in the same coordinates.

If the same tag also appears on a different picture (e.g., a unit overview in addition to the area detail) and that picture needs the other orientation, two options exist:

• Place a second CFC chart instance of the same S7 block in a separate hierarchy folder, each with its own block icon property assignment. Each instance will get its own canonical icon during the AS-OS transfer.
• Use Method 2 to manually place the alternate orientation and opt the icon out of auto-management via the @ rename.

Method 2: Manual Copy from @PCS7TypicalsAPLVx.pdl or @TemplateAPLVx.pdl

Use Method 2 when the target process picture is not generated by the plant hierarchy — typical for custom overview screens, composite area graphics, or projects where the OS compile is intentionally bypassed for selected pictures.

1. In WinCC Explorer, open the Graphics Designer for the OS project.
2. Open the picture @PCS7TypicalsAPLVx.pdl (e.g., APLV8 for PCS 7 V8.x, APLV9 for V9). The file is normally read-only.
3. Locate the desired valve block icon variant. Typical names: @VlvL/1 (horizontal), @VlvL/2 (vertical), @VlvAn/1, @VlvAn/2.
4. Select the icon and press Ctrl+C to copy.
5. Close @PCS7TypicalsAPLVx.pdl without saving.
6. Open the target process picture.
7. Press Ctrl+V to paste the icon at the cursor position.
8. Select the pasted icon and open its Object Properties → Miscellaneous. Inspect the Type field — it should read @VlvL/2 (or the variant you copied).
9. To prevent the AS-OS transfer from deleting the manual copy, change the Type field to one of:
   • Remove the leading @ (becomes VlvL/2 — user-managed, never touched).
   • Add a second @ (becomes @@VlvL/2 — system-managed in a different namespace).
   • Append a unique suffix (becomes @VlvL/2_overview — no match in the CFC chart's block icon property).
10. Close the Object Properties dialog. The icon is now opt-out of the auto-management for the next AS-OS transfer.
11. With the icon still selected, open the Standard Dynamics tab in the Dynamic Wizard.
12. Launch the wizard Connect picture block to tag structure.
13. Browse to the S7 program → chart folder → block (e.g., S7 Program(1)/Plant/Unit1/Valve_CFC/Vlv001).
14. Confirm. The icon is now bound to the same S7 tag as the AS-generated icon.
15. Verify faceplate calls: right-click the icon and confirm the faceplate opens with live values.

Alternative: copy from @TemplateAPLVx.pdl instead of @PCS7TypicalsAPLVx.pdl. The Template picture is identical to the typicals picture except the @ prefix has already been removed from all block icons. Pasting an icon from the Template picture requires no further renaming of the Type field.

Method 3: TIA Portal WinCC Object Rotation (Alternative Platform)

For engineers working in TIA Portal WinCC (Unified, Comfort Panels, RT Advanced, or RT Professional) rather than PCS 7, the rotation mechanism is built into the editor and does not require the typicals library or CFC/AS-OS workflow.

1. Open the screen in the TIA Portal editor.
2. Select the object (icon, shape, or graphic) to be rotated.
3. From the menu, choose Edit → Rotate, or use the rotation handles on the object.
4. Objects that support rotation can be turned clockwise or counter-clockwise in 90° steps around their center axis.
5. Save the screen.

Method 3 is not a substitute for Methods 1 and 2 in PCS 7. The PCS 7 typicals library is not used in TIA Portal projects, and the @ symbol mechanism is not relevant there. For PCS 7 projects, always use Methods 1 or 2.

Reference: Rotating objects – TIA Portal V20 documentation.

Block Icon Type Mapping and S7 Block Assignment

The CFC block icon Type is a composite string: <Symbol-prefix><BlockFB>/<Orientation>. The orientation is the suffix integer. The symbol prefix is the namespace indicator (@ or @@).

Plant Hierarchy, Overview Area, and OS Compilation Workflow

PCS 7 organizes the plant as a hierarchy of folders under the S7 program. Each folder may contain CFC charts, SFC charts, and (through OS compilation) one or more process pictures:

• A chart placed in Hierarchy/Unit1/Reactor becomes a CFC instance in the Reactor folder.
• An OS compile generates a picture @Reactor.pdl automatically.
• The Overview button on the parent unit picture (e.g., @Unit1.pdl) navigates to @Reactor.pdl.

For projects that use the plant hierarchy as the process picture tree, Method 1 is the only fully supported path. For projects where the plant hierarchy folder structure is not used as the process picture layout (e.g., the hierarchy is administrative only, and the OS uses a custom picture tree), Method 2 is the standard work-around.

The picture @Overview1.pdl is the standard top-level area overview. Subordinate area overviews follow the naming pattern @Overview<n>.pdl (e.g., @Overview2.pdl). Each overview can carry block icons that are independent of the per-unit detail pictures, and the @ rename is required to keep them after an AS-OS transfer.

Common Pitfalls and Field-Proven Caveats

1. Manual icon disappears after OS compile. The Type field still matches a CFC block's Block icon property. Rename the type (remove or add @, or append a unique suffix) and recompile.
2. Faceplate opens but values are wrong or static. The block icon was pasted but not bound via the Dynamic Wizard. Re-run Connect picture block to tag structure.
3. Permission levels don't match the operator's group. PCS 7 enforces authorization on the tag connection, not on the picture object. Verify in the User Administrator that the operator's group has rights on the underlying tag.
4. Two identical icons with the same Type are placed; only one remains. The AS-OS mechanism keeps exactly one icon per (tag, type) tuple across the OS server. This is by design. Use Method 2 with distinct Type strings to have multiple visible copies.
5. Rotation looks wrong on screen. Horizontal vs vertical is a 90° rotation; PCS 7 typicals are designed for a specific pipe-flow direction. Validate the orientation against the P&ID before commissioning.
6. The wrong typicals picture is referenced. The APLVx suffix in @PCS7TypicalsAPLVx.pdl is version-specific. A V8.x project running on a V9 OS will misbehave. Always match the major version.
7. Text inside the icon is mirrored or inverted. Some typicals include an embedded text field. The orientation change does not flip embedded text. Adjust the embedded label manually or use a different block variant.
8. Project migrated from V8 to V9 loses the orientation. Re-run OS compile after migration to regenerate the typicals. Verify the APLVx suffix on the typicals picture has updated.
9. @ symbol vs @@ symbol behavior confusion. A single @ makes the icon system-managed and matched against the symbol name without @. A double @@ makes the icon system-managed and matched against the literal @@<name>. Pick the convention that fits your process picture naming and stays consistent across the project.
10. Plant hierarchy picture is deleted but the icon is still expected. The picture file in the hierarchy is generated; deleting it does not affect the CFC. Regenerate via OS compile rather than authoring a replacement by hand.
11. Trend view opens on the wrong tag. The block icon's tag connection was made on a different connection point (e.g., PV vs SP). Open Object Properties → tag connection and re-bind the correct input.
12. Multi-client OS shows only one orientation. The redundant OS server has its own picture copies. The manual paste and @ rename must be repeated on each redundant server's picture, then synchronized via the OS project duplicator or by re-running the OS compile with Generate all selected.

Verification and Acceptance Test

After applying Method 1, 2, or 3, perform the following checks before sign-off:

1. Open the target process picture. Confirm the block icon is visible at the correct coordinates, with the correct orientation, and at the correct scale.
2. Click the icon and verify the faceplate opens, with live process values populating.
3. Force a value in the S7 block (e.g., via PLCSIM or the test mode in the CFC). Confirm the icon's color/animation tracks the value.
4. Trigger an OS compile. Verify the manually placed icons survive the compile and remain in the same coordinates.
5. Trigger a full AS-OS transfer. Verify again.
6. On the operator station, log in as a standard operator and as a maintenance engineer. Confirm the faceplate and trend view are reachable from the new icon, with the correct authorization level.
7. Check the picture's printout (if used) to ensure the icon is not clipped by page margins.
8. Document the icon's Type string and the corresponding CFC chart for future maintenance. Store the documentation alongside the plant hierarchy export.
9. Verify trend and message configuration: open the message configuration in WinCC Explorer and confirm the new icon's tag carries the expected message classes and priorities.
10. Test the loss-of-connection behavior: pull the AS connection and verify the icon turns gray or shows the configured "no response" state without crashing the picture.

Frequently Asked Questions