Adopting Runtime Setpoints in SFC Types and Operating the TAKESP Control Pin in PCS 7

In SIMATIC PCS 7 Sequential Function Charts (SFC), modifying a setpoint on the 'setpoint automatic input' pin of an SFC Type instance while a batch or sequence is running in Automatic mode does not immediately alter the active operating setpoint because SFC Types latch setpoints at step transitions. To force the SFC Type to dynamically accept a modified automatic setpoint mid-execution without restarting the phase: pulse the control input pin TAKESP (Take Over Setpoints) with a rising edge (0 to 1). In addition, ensure that the setpoint's parameter properties permit dynamic modification and that the active control strategy does not freeze parameter assignments.

Executive Summary

Sequential control logic implemented with SFC Types in SIMATIC PCS 7 coordinates complex procedural phases—such as temperature ramps, agitation speeds, and dosing rates—under the supervision of SIMATIC BATCH or automated plant coordinators. A common source of operational confusion occurs when an engineer or higher-level optimization system modifies a setpoint value on the automatic input interface of an active SFC phase during runtime: the controller appears to completely ignore the new setpoint, continuing to execute with the previous value. This occurs because SFC Types implement deterministic parameter isolation. This article explains the internal setpoint buffering architecture of SFC Types, details the exact operation of the TAKESP control pin, and outlines how to handle dynamic setpoint takeover in continuous batch processing.

Architecture and Fundamental Mechanics

SFC Type Parameter Buffering Architecture, Setpoint Handshake Mechanics, and TAKESP Dynamics:

Parameter Isolation and Latching in SFC Types:
To guarantee recipe repeatability and prevent race conditions, SFC Types enforce a strict separation between External Setpoint Inputs and Active Internal Working Setpoints.
When an SFC Type is instantiated in CFC, each defined setpoint exposes interface parameters:
- <SP>_Op: Operator manual setpoint input.
- <SP>_Ext / <SP>_Aut: Automatic setpoint input (fed from SIMATIC BATCH or supervisory CFC logic).
- <SP>_Act: The actual, currently active working setpoint evaluated by the internal sequencers and step actions.
When a phase transitions from Idle to Starting / Running, the SFC state machine takes a snapshot of <SP>_Aut and transfers it to <SP>_Act. Once the phase is in Running, changes to <SP>_Aut are buffered on the input terminal but are intentionally prevented from altering <SP>_Act.
The Role and Mechanics of the TAKESP Input Pin:
To allow intentional runtime adjustments (e.g. an operator trims a temperature target or SIMATIC BATCH updates a dosing volume), the SFC Type interface includes the control input: TAKESP (Take Over Setpoints).
When TAKESP transitions from 0 -> 1 (positive edge):
1. The SFC Type validates that the new setpoint on <SP>_Aut is within configured high and low limits (<SP>_HL, <SP>_LL).
2. If valid, it copies the value from <SP>_Aut into <SP>_Act immediately during the current execution cycle.
3. The internal sequencer logic and analog control loops instantly begin controlling to the updated value.
The Role of PARAM and Control Strategies:
If setpoints are modified from SIMATIC BATCH, BATCH typically asserts the command PARAM (Parameter transfer) in conjunction with TAKESP to ensure coordinated adoption.
If the parameter property 'Apply setpoint immediately' is checked in the SFC Type characteristics, certain releases adopt setpoints automatically; otherwise, manual or logic-driven pulsing of TAKESP is strictly required.

Step-by-Step Implementation Procedure

Inspect Setpoint Interface Pins in CFC Online Test Mode:
* Open the CFC chart containing the SFC Type instance.
* Switch to Test Mode (Ctrl + F).
* Locate the setpoint input pin (e.g. Temp_Aut or Temp_Ext) and the active working output pin (Temp_Act).
* Observe that modifying Temp_Aut to a new value (e.g. from 60.0 to 75.0) leaves Temp_Act unchanged at 60.0.
Pulse the TAKESP Input Pin:
* Locate input pin TAKESP on the SFC Type block.
* In CFC test mode, force TAKESP = 1 and then return it to 0 (or wire a pulse generator).
* Observe that Temp_Act immediately updates to 75.0, confirming instantaneous setpoint adoption.
Implement Automated Setpoint Takeover in Upstream Logic:
* If setpoints are fed dynamically from continuous CFC calculation blocks (e.g. a master ramp generator or lead controller):
* Insert an R_TRIG (Rising Edge Detector) or delta comparison block monitoring changes on the setpoint signal.
* Connect the output pulse of the edge detector directly to the TAKESP input pin of the SFC Type.
* Every time the external logic calculates a new setpoint step, TAKESP is automatically pulsed, keeping Temp_Act perfectly synchronized.
Configure Setpoint Attributes in the SFC Type Master Library (Optional):
* In the Master Data Library, open the SFC Type definition.
* Navigate to Characteristics -> Setpoints.
* Select the target setpoint; check the attribute Take over setpoint dynamically (or inspect 'Apply during run').
* Save and compile the SFC Type to propagate the behavior.

Verification

In SIMATIC BATCH or CFC, modify the automatic setpoint input during active recipe execution.
Pulse TAKESP; confirm on the SFC online view that the active setpoint (_Act) snaps to the new value within 1 scan cycle.
Confirm that the connected PID loop (PidConL) receives the updated setpoint and adjusts valve output smoothly.

Limitations and Operational Precautions

Pulsing TAKESP while an automatic setpoint value is outside configured limit bounds (<SP>_LL to <SP>_HL) is rejected by the SFC Type, and the block outputs an error status. If the SFC Type is operating in Manual mode (MANUAL), automatic setpoint inputs are locked out; manual setpoints must be modified via <SP>_Op.