Troubleshooting Interlock Jump Navigation from APL Faceplates in PCS 7

When the 'Interlock Jump' button on an Advanced Process Library (APL) technological faceplate (e.g., 'MotL' or 'VlvL') fails to open the associated interlock block faceplate ('Intlk02', 'Intlk04', or 'Intlk08'), the issue typically stems from: missing OS compilation of the interlock block, missing block icon generation for the interlock in the plant hierarchy, unconfigured 'OS Area' assignment, or operating in a Single Station without proper server data mapping. To fix this, verify that the interlock block has 'S7_m_c := true', compile the OS with 'Create/update block icons' enabled, and verify that the interlock block resides in an assigned plant hierarchy folder.

Executive Summary

The PCS 7 Advanced Process Library (APL) provides a powerful operator feature known as 'Interlock Jump'—allowing control room operators to click the padlock interlock icon on a motor or valve faceplate and immediately open the detailed logic view of the upstream interlock block (Intlk02, Intlk04, Intlk08). When this jump fails, the button appears grayed out or clicking it produces no response, leaving operators blind during process trips. This article explains the internal WinCC script mechanics of APL interlock jumps, prerequisite plant hierarchy settings, and step-by-step diagnostic procedures.

Architecture and Fundamental Mechanics

APL Interlock Jump Architecture and Faceplate Script Mechanics:

Technological Interlock Interconnection in CFC:
Technological blocks (e.g., MotL) connect to interlock blocks (e.g., Intlk02 / Intlk04) via standard structure pins (Permit, Protect, Intlock).
The APL compiler evaluates these connections during OS compilation, exporting interconnection metadata into WinCC Tag Management.
WinCC Interlock Jump Mechanics:
When an operator opens the MotL faceplate and clicks the interlock button, WinCC executes the standard C-script APL_OpenInterlockFaceplate.
The script reads the tag name connected to the motor's interlock input (e.g., Plant/Unit/Intlk_Pump101).
It searches the WinCC project for the block icon or picture containing that interlock object.
Failure Modes:
1. Interlock Block Missing S7_m_c: If the interlock block in CFC does not have Operator Control and Monitoring (OCM / S7_m_c = true) enabled, no WinCC tags are created.
2. Interlock Block Icon Missing: If 'Create/update block icons' was not run, WinCC cannot locate the screen coordinates for the interlock faceplate anchor.
3. Hierarchy Assignment: If the interlock chart resides in an unassigned hierarchy folder, the navigation system rejects the call.

Step-by-Step Implementation Procedure

Step-by-Step Procedure to Enable and Fix APL Interlock Jumps:

Verify OCM Properties of the Interlock Block in CFC:
- Open the CFC chart containing the interlock block (Intlk02, Intlk04, or Intlk08).
- Open the block's Object Properties.
- Ensure that 'Operator Control and Monitoring' (OCM) is checked (S7_m_c := 'true').
- Verify that 'Create block icon' is checked.
Verify Interconnection to Technological Block:
- In CFC, ensure the output Out of the interlock block connects to Permit, Protect, or Intlock on the technological block (e.g., MotL).
- Ensure the connection is a direct CFC structural connection, not an indirect word transfer.
Verify Plant Hierarchy Placement:
- In SIMATIC Manager Plant View, ensure both the motor chart and the interlock chart reside within a hierarchy folder assigned to an active OS Area.
Perform OS Compile with Block Icon Generation:
- In SIMATIC Manager, right-click the OS -> Compile.
- Check Create/update block icons.
- Complete compilation and verify that WinCC Tag Management contains the interlock block tags.
Test in WinCC Runtime:
- Open the motor faceplate in WinCC Runtime.
- Verify that the padlock icon illuminates (green/yellow/red) and is clickable.
- Click the icon; verify that the Intlk faceplate opens immediately with live input states.

Verification

To verify interlock jump functionality:
1. In WinCC Runtime, locate the technological block icon (e.g., motor).
2. Open the faceplate -> click the 'Standard' view.
3. Hover over the interlock status icon; verify the cursor turns into a hand pointer and displays the tooltip with the interlock tag name.
4. Click the icon; confirm the interlock faceplate appears centered over the screen displaying all individual bypass and signal status flags.

Limitations and Operational Precautions

Operational precautions:
- If an interlock input is driven by raw boolean bit logic or an elementary gate (And02) rather than an APL Intlk block, the interlock jump feature is disabled because raw gates lack faceplates.
- In multi-client configurations, ensure the server package containing the interlock block is loaded onto the client.
- Do not disable block icon generation on interlock blocks if interlock jump navigation is required.

Engineer FAQ

Why is the interlock jump button disabled on my motor faceplate?

The technological block's interlock input is not connected to an APL Interlock block (Intlk02/04/08), the interlock block lacks S7_m_c, or the OS has not been compiled with block icons.

Can I jump to an interlock if I used an elementary AND gate in CFC?

No. Interlock jumps require an APL technological interlock block (Intlk02, Intlk04, Intlk08) which possesses a WinCC faceplate.

What script executes the interlock jump in WinCC?

The standard APL C-script APL_OpenInterlockFaceplate or internal WinCC script triggers.

Does the interlock block need its own block icon in a process graphic?

Yes, or at least be registered in the project typicals so the OS Project Editor can locate its faceplate call structure.

Does an Intlk block consume an extra Process Object?

Yes, APL Intlk blocks with S7_m_c enabled consume standard AS/OS Process Objects.

Technical References

Related Tags

Interlock Jump
APL Faceplates
Intlk04
MotL
Plant Hierarchy

20 respuestas

Troubleshooting Interlock Jump Navigation from APL Faceplates in PCS 7