Interconnecting Technological Blocks (CountOh) to SelFp1 on APL Motors in SIMATIC PCS 7

In SIMATIC PCS 7 Advanced Process Library (APL), connecting an auxiliary block like CountOh (Operating Hours) to the SelFp1 input of a motor (MotL) enables a direct 'Block Jump' navigation button on the motor faceplate. Because SelFp1 is an ANY pointer evaluated during OS compilation to resolve the partner block's instance name, any valid technological output pin (such as CountOh.Out or CountOh.HoursOut) can be connected.

The APL Block Jump Concept and Navigation Architecture

In modern process plant operations running SIMATIC PCS 7 Advanced Process Library (APL), operator efficiency depends on seamless navigation between related control objects without cluttering the screen with multiple open windows.

When an operator opens a motor faceplate (e.g. MotL for a pump or compressor), they frequently need access to related operational equipment:
* The Operating Hours and Maintenance Counter (CountOh) to view runtime hours, switching cycle counts, and upcoming maintenance schedules.
* A Dosing or Flow Measurement Block (CountScL or TotalL) tracking accumulated throughput.
* An auxiliary temperature or vibration monitoring block (MonAnL).

To accommodate this, Siemens APL incorporates the Block Jump architecture. Technological blocks provide dedicated input parameters—named SelFp1 and SelFp2 (Select Faceplate 1 and 2)—that generate navigation pushbuttons directly on the standard motor faceplate toolbar in WinCC Runtime. Clicking this button immediately opens the faceplate of the interconnected technological block.

Technical Role of the SelFp1 ANY Pointer Input

Beginner PCS 7 engineers frequently debate which specific output parameter of CountOh must be wired to SelFp1 (e.g., Ms_Release, Out, HoursOut, or DayCntOut):

Evaluation During OS Compilation:
* The parameter SelFp1 has data type ANY in the AS block interface.
* SelFp1 is not used for cyclic mathematical processing inside the controller. The motor block does not calculate operating hours or modify its speed based on this input.
* Instead, during Compile OS, the WinCC OS compiler parses the CFC chart database, traces the textual/block interconnection attached to SelFp1, and extracts the chart name and block instance name of the connected partner.
Any Valid Output Pin Functions Correctly:
* Because the OS compiler extracts the block identity from the pointer structure, any valid technological output pin on the target block satisfies the jump requirement.
* Connecting CountOh.Out, CountOh.HoursOut, or CountOh.Ms_Release to MotL.SelFp1 yields the identical runtime behavior: the motor faceplate generates a jump button leading directly to CountOh.
Engineering Best Practice Recommendation:
* While technically any pin works, standard engineering best practice dictates connecting CountOh.Out or CountOh.HoursOut.
* Connecting the primary technological output maintains visual clarity in CFC charts, making it immediately evident to reviewing engineers that the two blocks are functionally paired.

Step-by-Step Interconnection and OS Compilation Procedure

1. Instantiate the Operating Hours Block in CFC

Open the CFC chart containing your motor block (MotL).
From the APL Library, drag and drop CountOh (FB1864) onto the chart.
Name the instance appropriately (e.g. PMP_101_OH).

2. Connect Motor Run Feedback to CountOh

Connect the motor running feedback signal (MotL.FbkRunOut or drive feedback) to input CountOh.In.
Configure CountOh parameters:
* HoursLimit: Target operating hours threshold for maintenance (e.g., 5000.0 hours).
* Interval: Tracking interval.
* Reset: Connect reset logic or leave available for faceplate operator commands.

3. Wire the Faceplate Jump Connection

In the CFC chart, locate input pin SelFp1 on the MotL block.
If SelFp1 is not visible, select the MotL block, press Alt + Return (Object Properties), navigate to the I/Os tab, find SelFp1, and uncheck the Invisible box.
Draw a connection line from CountOh.Out (or CountOh.HoursOut) to MotL.SelFp1.

4. Execute OS Compilation

In SIMATIC Manager, select the OS station.
Select PLC > Compile and Download Objects.
Choose OS, select Scope: Changes only (or Entire project), and run compilation.
The OS compiler generates the faceplate jump metadata in the WinCC @ internal tag tables.

5. Test in WinCC Runtime

Activate WinCC Runtime.
Click the motor block icon to open the MotL faceplate.
Observe the upper toolbar area of the faceplate: a new button showing the CountOh symbol appears.
Click the button; confirm the CountOh faceplate opens adjacent to the motor faceplate.

Auxiliary Technology Block and Faceplate Jump Matrix

Target BlockFunctionPreferred Output Connected to SelFp1Resulting Motor Faceplate BehaviorCountOhOperating Hours / Maintenance counterCountOh.Out or CountOh.HoursOutButton opens Operating Hours maintenance windowCountScLQuantity and switching cycle counterCountScL.OutButton opens Switching Cycle counter faceplateMonAnLAuxiliary analog monitor (e.g. motor bearing temp)MonAnL.OutButton opens temperature monitoring trend and faceplateTotalLFlow totalizer / Batch accumulatorTotalL.OutButton opens fluid volume totalizer faceplateIntlk02 / Intlk04Interlock logic(Do NOT connect to SelFp1)Dedicated interlock jump buttons are auto-generated via Permit/Intlock inputs

Verification

Open the CFC chart; verify the interconnection line from CountOh.Out to MotL.SelFp1 is solid and active.
Perform an OS compile; confirm compilation finishes with 0 Errors and 0 Warnings.
Open WinCC Runtime on an OS Client or Server.
Click the motor icon to open the standard faceplate.
Verify the Block Jump 1 icon is illuminated in the faceplate header.
Click the Block Jump button; verify the CountOh faceplate opens cleanly, showing accumulated operating hours and cycle counts.

Limitations and Operational Precautions

Interlock Blocks Exception: Never connect interlock blocks (Intlk02, Intlk04, Intlk08) to SelFp1. APL motor blocks have dedicated interlock inputs (Permit, Intlock, Protect) that natively generate dedicated interlock jump buttons. Using SelFp1 for interlocks wastes an auxiliary navigation slot.
Maximum Jump Buttons: Standard APL motor faceplates provide two generic jump inputs: SelFp1 and SelFp2. A maximum of two custom auxiliary faceplates can be linked via this mechanism.
OS Compilation Required: Changes to SelFp1 in CFC do not appear in WinCC Runtime until an OS compilation is executed. Online changes without OS compilation leave the jump button non-functional.

Engineer FAQ

Why is SelFp1 hidden by default on some APL blocks?

To keep CFC block displays compact, secondary parameters like SelFp1 and SelFp2 are set to 'Invisible' by default. You can make them visible via block Object Properties.

Can I connect a block located in a different CFC chart to SelFp1?

Yes. CFC supports inter-chart cross-references. Connecting SelFp1 across charts creates a sheet margin pointer, and the OS compiler will correctly resolve the remote chart and block name.

Can I customize the tooltip or label on the faceplate jump button?

Yes. The button tooltip is automatically derived from the connected block's configured OS comment or technological descriptor in CFC Object Properties.