How to Troubleshoot Faceplate Block Jumps (SelFp1, SelFp2, BLK_Jump) in PCS 7 APL

In SIMATIC PCS 7 APL, faceplate block jumps (using SelFp1, SelFp2, or interconnected BLK_Jump attributes on Interlock blocks) fail to open target faceplates when WinCC OS Clients lack a configured Standard Server for Split Screen Manager (SSM) and Tags, when server data packages are missing, or when the project is run directly on an Engineering Station where target OS computer paths cause server prefix resolution errors. Furthermore, on Interlock blocks (Intlk0x), the 'OS additional text' parameter at In01 only configures jump button tooltips; to display custom text next to inputs inside the faceplate, engineers must configure the 'Identifier' property of the corresponding AV01.value parameter in CFC.

Mechanics of APL Faceplate Block Jumps and Text References

The SIMATIC PCS 7 Advanced Process Library (APL) incorporates a powerful navigational feature allowing operators to jump seamlessly between related technological faceplates.

Common operational use cases include:
* Interlock to Cause: In an interlock faceplate (Intlk02, Intlk04, Intlk08), clicking an input row opens the faceplate of the upstream transmitter or motor that triggered the interlock.
* Auxiliary Equipment Jumps: Using parameters SelFp1 and SelFp2 on drive blocks (MotL, VlvL) to provide direct jump buttons in the faceplate header to associated lubrication pumps, temperature monitors, or variable frequency drives.

The Text Reference Mechanism

Block jumps do not rely on hardcoded script paths. Instead:
1. When CFC compiles the OS, it creates a Text Reference in the WinCC Text Library formatted as:
[ServerPrefix]::[ChartName]\[BlockName]
2. In the faceplate, standard C scripts (APL_OpenFaceplate) resolve the text reference, extract the server prefix and tag name, and pass them to the Split Screen Manager to open the target window.

Root Cause Analysis for Failed Faceplate Jumps

Engineers frequently encounter scenarios where clicking the jump button produces no response, displays a 'Server down' warning in the WinCC message banner, or shows missing text errors.

Primary Failure Modes

Missing Standard Server on OS Clients: In client-server configurations, the client workstation must know which server processes Split Screen Manager requests. If Standard Server is not assigned for SSM and Tags in WinCC Explorer, the client script cannot resolve the server prefix, causing the jump to fail silently.
Running Server Projects Directly on the ES: If an engineer opens and activates an OS Server project directly on the Engineering Station (rather than using the proper OS Simulation utility), the target path configured in the OS properties points to the physical server. The server prefix resolution fails, reporting communication drops.
Text Library Language Desynchronization: If a jump is configured while one display language is active in SIMATIC Manager, and the runtime language is switched to an unpopulated language, the text reference resolves to an empty string, disabling the jump button.

Configuring Input Labels vs Block Jump Texts on Interlock Blocks

A widespread misunderstanding among automation engineers involves configuring text labels on APL Interlock blocks (Intlk02, Intlk04, Intlk08):

The Misunderstanding: `In01` 'OS Additional Text'

Engineers often enter descriptive labels (e.g., 'High High Level Trip') into the 'OS additional text' field of the binary input In01 in CFC. They expect this text to appear next to the input indicator inside the interlock faceplate.
* Why it does not appear: The 'OS additional text' on In01 is linked to the BLK_Jump attribute. It is used only as a tooltip / text reference for the block jump button. Because the button in the interlock faceplate is small, the text is not rendered as an on-screen label.

The Proper Method: Configuring `Identifier` on `AV01.value`

To display a descriptive text string next to the input in the interlock faceplate:
1. In CFC Editor, expand the interlock block to view its analog value inputs (AV01, AV02, etc.) or internal structures.
2. Locate the parameter AV01.value (or In01 structural identifier depending on APL version).
3. Open its Object Properties and configure the 'Identifier' field (e.g., 'Tank 101 High Level').
4. Compile the OS. The text configured in the Identifier field will now appear clearly beside the interlock input in the faceplate Standard View!

Block Jump Parameters and Configuration Reference Matrix

The following table outlines the configuration parameters and system settings governing APL faceplate block jumps:

Feature / ParameterBlock TypeConfiguration LocationOperational FunctionSelFp1 / SelFp2MotL, VlvL, PIDConLCFC Block InputsInterconnect to technological block or specify tag nameIn01#OS_TextIntlk02 through Intlk16CFC Input In01 (OS Add. Text)Configures jump button tooltip referenceIdentifierIntlk0x (AV01.value)CFC Parameter Object PropertiesDisplays descriptive text label in faceplateStandard Server SSMOS Client StationWinCC Explorer -> Server DataEnables Split Screen Manager jump resolution on clientStandard Server TagsOS Client StationWinCC Explorer -> Server DataResolves tag prefixes for jumped faceplatesGenerate Server DataOS Server StationSIMATIC Manager -> OS -> OptionsGenerates .pck package containing text references

Proper configuration across both CFC parameters and WinCC server assignments guarantees 100% reliable faceplate navigation.

Verification

To verify that faceplate block jumps are working properly:
1. On an OS Client in WinCC Runtime, open the faceplate of the drive block or interlock block.
2. For Interlock blocks: Verify that the descriptive label configured in Identifier is visible next to the input status indicator.
3. Click the block jump button (or the input line of an active interlock).
4. Verify that the target faceplate (e.g., the upstream level transmitter or auxiliary oil pump) opens immediately centered on the operator display.
5. Confirm that the target faceplate shows live process data with zero 'Server down' or 'Tag not found' warnings.
6. Click the back arrow in the faceplate navigation history to return to the original block.

Limitations and Operational Precautions

Do not run OS Server projects directly on an ES station in production networks; use Options -> OS Simulation to prevent network node address conflicts with real servers.
If a target block is deleted or renamed in CFC, the text reference in the Text Library will become orphaned until an OS compilation with 'Tags and messages' is executed.
Avoid modifying standard APL faceplate scripts (@PG_Intlk0x_Standard.pdl) to bypass standard text references, as updates will overwrite manual changes.
Ensure all server data packages (.pck) are updated and reloaded on clients whenever plant hierarchy structures change.

Engineer FAQ

Why does clicking a block jump report 'Server down' in runtime on my ES?

Because the OS project properties contain the target path to the physical production server. When running locally on the ES, the server prefix cannot resolve its own hostname. Use OS Simulation instead.

How do I assign a Standard Server on an OS Client?

In WinCC Explorer on the OS Client, expand the project tree, right-click Server Data, select Standard Server..., and select the primary OS Server for both 'SSM' and 'Tags'.

Can I use `SelFp1` to jump to a non-APL process picture instead of a faceplate?

No. SelFp1 is designed to invoke APL faceplates. To open an arbitrary process picture, use a standard graphic button configured with the SSMOpenPicture() function.

Technical References

Related Tags

APL_Faceplates
Block_Jump
SelFp1
Intlk0x
Standard_Server

6 respuestas

How to Troubleshoot Faceplate Block Jumps (SelFp1, SelFp2, BLK_Jump) in PCS 7 APL