Why an Active PCS 7 SFC May Restart After a Jump-Topology Change

Adding a jump changes the SFC topology. Siemens documents that topology changes take effect in instances after the SFC type is compiled and downloaded; active sequencers may need their instances disabled during the download and then restarted after operator confirmation. The resumed point depends on the instance's process state and configured start conditions, so a return to the beginning is not enough by itself to prove an SFC defect.

Topology changes and active instances

A jump changes the step/transition sequence and jump destination in the SFC type. Siemens' SFC V9.0 SP7 manual states that inactive sequencers can be downloaded after topology changes at any time; active sequencers require the instances to be disabled before download. When disabled for download, instances are restarted after confirmation, and their execution depends on process state and start conditions.

Why the sequence can appear to start over

The ticket reports that after adding one jump and downloading, the SFC stops and starts from the beginning. If the instance was disabled and restarted, configured start conditions can select an initial sequencer. Review the SFC type topology, instance start conditions, operating mode and download log to determine whether this was expected restart behavior or a configuration issue.

Plan a topology change safely

Identify which SFC instances of the modified type are active and what process state they represent.
Review start conditions and recovery behavior before applying the changed jump topology.
Schedule the download when affected instances are inactive where possible. If active instance download is required, use the documented disable/restart workflow and obtain operator confirmation.
Avoid using SIMATIC Manager “Compile and download objects” if the required SFC disable step would not be performed by that workflow; the SFC manual warns such downloads may be skipped and logged.
After download, verify sequencer state and actual process conditions before resuming operation.

Operational risk

During a download requiring SFC disablement, the instances cannot be processed in the automation system and their CFC interconnections cannot access them. If the sequence controls a critical process, assess safe state, hold/abort behavior and restart preconditions with operations before changing the type.

Verification

Review the load log for whether each instance was disabled, downloaded and restarted. Confirm the current active step, jump target and start condition, then verify the process is in a state where the resumed sequence is safe.

Limitations and Operational Precautions

The ticket does not identify PCS 7/SFC version or show the download log. This article uses Siemens SFC V9.0 SP7 behavior as a documented reference; verify the matching version before applying the exact workflow.

Technical References

Siemens, SFC for SIMATIC S7 V9.0 SP7, Programming and Operating Manual, section 8.5.3 “Configuration changes in the SFC type”: https://support.industry.siemens.com/cs/attachments/109805980/s7sfcs7b_en-US.pdf

PCS 7 SFC topology changes
SFC instance restart conditions

Engineer FAQ

Does adding one jump necessarily stop every process? Not necessarily. The effect depends on whether affected SFC instances are active and on the download workflow. Active instances may need to be disabled during the topology download.

Why did the SFC return to the beginning? After restart, execution depends on the instance process state and configured start conditions. Inspect those settings and the load log.

Can an inactive sequencer receive topology changes? The cited SFC V9.0 SP7 manual says inactive sequencers can be downloaded after topology changes at any time.

Can an active sequencer receive a topology change while remaining active? The cited manual says active instances must be disabled before downloading topology changes.

What happens while an SFC instance is disabled for download? The instance is not processed in the automation system and cannot be accessed through its CFC interconnections during the download.

Will SIMATIC Manager automatically disable SFCs in every compile/download workflow? No. The manual warns the “Compile and download objects” function does not disable SFCs when required; download may be skipped and logged.

What should be reviewed before modifying a critical sequence? Review safe state, active step, start conditions, process interlocks and approved restart procedure with operations.

Do step or transition parameter changes have the same rules as topology changes? No. Siemens distinguishes topology and step/transition configuration changes from interface modifications; check the applicable manual section.

Does this behavior prove the SFC type is defective? No. A restart can follow the documented disable/download/restart behavior. Logs and start conditions are needed to determine the specific cause.

Which version does the cited behavior describe? The cited programming manual is SFC for SIMATIC S7 V9.0 SP7; validate against the installed PCS 7/SFC release.

Why an Active PCS 7 SFC May Restart After a Jump-Topology Change