Resolving SFC Type Technological Action Failures and SetNumP Execution Inconsistencies in PCS 7

In SIMATIC PCS 7 V9.0 SP2, SFC Type technological actions (such as SetNumP, SetBitP, and ChkBitP used in Equipment Phases and Equipment Modules) failing to execute during step processing—resulting in numerical setpoints (_AI) remaining unassigned—is caused by outdated or un-synchronized command/status definitions in the Master Data Library or known execution defects in early ES V9.0 SP2 updates. In PCS 7 technological engineering, SFC Type actions rely on global function templates. If the project library was not synchronized across both the 'Commands' and 'Status' tabs, or if ES V9.0 SP2 UC02 was installed without cumulative engineering hotfixes, SetNumP is ignored by the runtime engine. To resolve this, upgrade to ES V9.0.5.4 (PCS 7 V9.0 SP2 UC04 or V9.0 SP3), synchronize the Master Data Library using 'PlantType > Synchronize', execute 'Options > Charts > Update Block Types' on the SFC Type FB, and recompile the S7 program.

Executive Summary

Implementing ISA-88 modular batch automation using SIMATIC PCS 7 Equipment Modules (EMT) and Equipment Phases (EPH) relies heavily on SFC Types. A powerful feature of SFC Types is Technological Actions, allowing engineers to write readable commands—such as SetNumP to assign recipe setpoints or SetBitP to assert control bits—directly inside SFC steps without raw parameter linking. However, engineers working on PCS 7 V9.0 SP2 frequently encounter situations where SetNumP steps execute without setting the target setpoint, while traditional direct assignment (CV = PV) functions normally. This failure stems from desynchronization between the project's technological command catalog and the underlying SFC library, combined with software defects resolved in later Engineering Station service packs.

Architecture and Fundamental Mechanics

The technological action architecture in SIMATIC PCS 7 SFC Types bridges high-level process commands with low-level CFC machine code:

Technological Commands and Statuses Architecture:
* In PCS 7 V9.0, technological engineering allows abstracting control actions into formal library objects: Commands (e.g., SetNumP, SetBitP, RampP) and Statuses (e.g., ChkBitP, ChkNumP).
* These commands are managed centrally within the Master Data Library under Technological Types.
* When an engineer inserts SetNumP into an SFC Type step, the SFC compiler does not generate hardcoded assembly; it inserts a call to an underlying technological interface function that translates the setpoint parameter into the target block's input register.
The Library Desynchronization Problem:
* When library elements are created, modified, or updated between engineering workstations, the internal database IDs of commands can diverge.
* If an engineer synchronizes only the Commands tab in the Plant Type editor while neglecting the Status tab (or vice versa), the relational binding breaks.
* When the SFC Type FB compiles, the compiler encounters mismatched function signatures. Instead of throwing a fatal error, the compiler generates empty execution stubs, causing SetNumP to be skipped silently at runtime.
Product Hotfix Requirements (ES V9.0.5.x):
* In early builds of PCS 7 V9.0 SP2 (including Update Collection 2), a known software defect prevented the SFC runtime engine from executing SetNumP functions assigned to specific parameter categories.
* Siemens corrected this in ES V9.0.5.4 (PCS 7 V9.0 SP2 UC04) and permanently integrated the fix into PCS 7 V9.0 SP3.

Step-by-Step Implementation Procedure

Follow these procedures to restore proper execution of SetNumP and technological actions in SFC Types:

Verify and Update Installed ES Software Version:
* In SIMATIC Manager, select Help > About... > Display > Products.
* Locate Engineering System (ES) and SFC.
* If running an unpatched version of PCS 7 V9.0 SP2, download and install PCS 7 V9.0 SP2 Update Collection 4 (UC04) or upgrade to PCS 7 V9.0 SP3 to ensure the engineering engine is at version V9.0.5.4 or higher.
Synchronize Master Data Library Commands and Statuses:
* In SIMATIC Manager, select the Master Data Library.
* Navigate to Technological Types.
* Right-click and select PlantType > Synchronize....
* In the synchronization wizard:
- Open the Commands tab: Select all technological commands and click Update in Project.
- Open the Status tab: Select all statuses and click Update in Project.
- Ensure synchronization is completed for both tabs.
Update SFC Library Elements:
* In the Master Data Library, open File > Open > Libraries and open the SFC Library.
* Copy clean, official versions of the technological function blocks and commands (SetNumP, SetBitP) into the Master Data Library Blocks folder.
Update Block Types for SFC Type Instances:
* In the Master Data Library, select the Blocks folder.
* Select Options > Charts > Update Block Types....
* Select the S7 Program containers hosting the SFC Types and EPH/EMT instances.
* Execute the update to synchronize all offline charts.
Recompile the S7 Program and SFC Types:
* Open the SFC Type editor for the affected phase.
* Save and compile the SFC Type.
* In SIMATIC Manager, select the S7 Program and execute PLC > Compile and Download Objects (Scope: Changes only or Entire program).
* Download changes to the AS controller.

Verification

In SIMATIC Manager or SFC Visualization on the OS, open the SFC Type instance in online monitoring mode. Trigger the execution step containing the SetNumP action. Verify that the destination parameter (e.g., analog setpoint _AI) immediately reflects the configured numerical value. Confirm that the transition condition evaluating the setpoint satisfies cleanly and the phase progresses to subsequent steps.

Limitations and Operational Precautions

Always perform a complete multiproject backup (File > Archive) before updating block types or synchronizing technological types. If manual script modifications were made to technological command functions, re-importing clean library elements will overwrite those changes.

Engineer FAQ

Why did CV = PV work when SetNumP failed?

Direct assignment (CV = PV) compiles directly into native SFC microcode, whereas SetNumP calls the modular technological command library. If the technological library is corrupted or desynchronized, only SetNumP fails.

What does SetNumP specifically do in an SFC step?

SetNumP (Set Number Parameter) writes a numerical floating-point value to an analog technological setpoint parameter (_AI) of a target equipment module.