CFC Parameter Readback: Safety, Feasibility, and Consistency Rules When Offline Charts Are Uncompiled

Yes, CFC Readback (Chart > Readback) is not only safe but strictly recommended when offline charts differ from the online AS due to uncompiled logic or missing software updates. Because CFC compilation has not occurred, the offline database structure (instance DB numbers, parameter byte offsets, and variable types) matches the running CPU exactly. Readback queries the online instance DBs and writes live setpoints, operator parameters, and tuned PID values directly into the offline CFC charts. Executing readback prior to installing updates (like CFC SP1 Upd4) ensures that operator tuning made from WinCC is preserved and not overwritten during subsequent recompilations.

Mechanics of CFC Readback in Continuous Process Automation

During plant operation, operators and process engineers continuously tune controllers from WinCC faceplates: adjusting PID gains (Gain, TI, TD), updating alarm limits (SP_HiLim, SP_LoLim), modifying batch setpoints, and altering interlock bypass states. These changes write directly to the online instance data blocks (DBs) inside the S7-400 or CPU 410-5H work memory.

If an engineer subsequently makes offline logic edits in Continuous Function Chart (CFC), compiles, and downloads without performing a Readback, the compiler writes the default values stored in the offline chart database back into the controller, erasing weeks or months of operational tuning. The CFC Readback utility extracts current values from the online PLC and updates the offline CFC chart parameters.

Why Uncompiled Offline Projects Guarantee Safe Readback

A common concern arises when an engineer encounters an engineering roadblock (e.g., compilation is blocked due to an unapplied CFC service pack, such as CFC V8.2 SP1 Upd4), and wonders whether readback is valid while the offline project is 'uncompiled'.

In fact, uncompiled state is the ideal condition for readback:

Identical Memory Layout: The offline CFC database currently retains the exact instance DB structure, variable order, and block addresses generated during the previous successful compile. This corresponds 1-to-1 with the memory layout in the AS.
Safety Against Type Skew: If the project had been compiled with modified block types or shifted parameters, readback would detect address mismatches and abort. Because compilation was withheld, the readback engine matches each online DB byte to its corresponding offline CFC block pin with zero discrepancy.

Readback Scope: 'All Parameters' vs 'OCM-Capable Parameters Only'

When initiating readback, the CFC dialog prompts for the extraction scope:

OCM-Capable Parameters Only (Operator Control and Monitoring): Reads back only parameters marked with the system attribute s7_m_c = 'true' (parameters accessible via WinCC faceplates, such as setpoints, control parameters, and modes). This is the recommended standard practice for 95% of industrial applications.
All Parameters: Reads back every writable input pin, including internal interconnected logic pins. Caution: this can capture temporary simulation overrides or transient calculation states as permanent initial values.

Step-by-Step Parameter Readback Procedure in PCS 7

Follow this procedure to safely read back operational parameters prior to software patching or compilation:

Create an Offline Backup: In SIMATIC Manager, select File > Archive to create a baseline ZIP backup of the project.
Open CFC Editor: Open any CFC chart in the target AS program.
Launch Readback: Select Chart > Readback (or click the Readback icon on the toolbar).
Configure Scope: In the Readback dialog, select:
- Scope: 'OCM-capable parameters only'
- Source: 'Online AS'
Execute Readback: Click OK. CFC connects to the automation station via the active PG/PC interface, queries the DBs, and updates the offline chart database. Review the readback log upon completion.
Install Software Updates: Install the required updates (e.g., CFC SP1 Upd4). Re-open the project, compile charts, and verify that all tuned operational values are retained.

Readback Parameter Selection Matrix

The following table compares readback scopes and their impact on offline project data:

Readback ModeAttributes ScannedTarget VariablesRisk ProfileRecommended ScenarioOCM Parameters Onlys7_m_c = 'true'Faceplate setpoints, tuning, alarm limitsVery Low (Preserves operator entries)Standard pre-compile workflowAll ParametersAll writable inputsAll configurable pins (including non-OCM)Moderate (May lock temporary debug values)Complete unit clone or disaster recoverySelected Charts OnlySpecified chart folderOnly blocks in selected chart hierarchyVery LowLocal loop re-tuningNone (Compile Directly)NoneOffline defaults overwrite AS memoryHigh (Erases all online tuning)Strictly prohibited on running plants

Verification

Verify readback success and parameter preservation through the following steps:

Check the CFC Readback Log (Options > Logs > Readback). Confirm '0 Errors' and inspect the list of updated parameters.
Open a critical PID controller chart (e.g., PIDConL). Inspect the Gain and TI parameters in the CFC object properties. Confirm they match the live values currently displayed on the WinCC OS faceplate.
Perform a test CFC compilation (Changes only). Confirm that compilation finishes without errors.
Compare the offline project against the archived baseline to verify that only operational values were updated.

Limitations and Operational Precautions

Consider these operational rules when executing readback:

Never Perform Readback After Modifying Block Types: If you update block types in the library or alter block interfaces before readback, the structural mapping breaks, making readback impossible without risking corrupted parameter assignment.
Redundant H-System Readback: In redundant S7-400H or CPU 410-5H systems, execute readback from the master CPU (Rack 0 or Rack 1) that is actively controlling the plant.
Online Connection Reliability: Ensure the ES network connection to the Plant Bus is stable; a dropped link during readback can leave a subset of charts updated while others retain obsolete defaults.

Engineer FAQ

Can I perform Readback while the plant is actively producing product?

Yes, Readback is a completely non-intrusive read-only query of instance data blocks. It has zero impact on controller execution cycle or plant operation.

Where can I see which parameters were modified by Readback?

Open SIMATIC Manager and view the Readback log file under Options > Logs > Readback, which lists every block parameter and its before-and-after value.