Troubleshooting Frozen Online Values in CFC Test Mode: APL MotL and VlvL Dynamic Monitoring

When input and output values on APL motor (MotL) or valve (VlvL) blocks do not update in CFC Test Mode (remaining grey, blank, or frozen), the failure is caused by inactive dynamic monitoring on block pins, a deactivated runtime group, or an invalid S7 communication handle. In PCS 7 CFC, entering Test Mode (Debug -> Test Mode) establishes controller communication, but parameters only refresh live values if 'Watch On' is active on the block or if pins are registered in the watch list. Furthermore, if the block's runtime group in OB35 is deactivated (EN = 0) or if Set PG/PC Interface is misconfigured, dynamic updates freeze.

CFC Test Mode Architecture: Online Database Handles and Polling Cycles

Continuous Function Chart (CFC) in SIMATIC PCS 7 provides an interactive debugging environment known as Test Mode (accessed via Debug -> Test Mode or pressing the test glasses icon). In Test Mode, the CFC editor establishes an online communication link to the physical S7-400 controller or S7-PLCSIM virtual CPU.

Unlike standard STEP 7 ladder monitoring which polls an entire block unconditionally, CFC relies on selective cyclic polling to conserve controller communication bandwidth. If parameters are not explicitly added to the online monitoring register, the values remain static.

The 'Watch On' Mechanism: Selective vs Global Parameter Monitoring

In CFC, every block and individual parameter has an independent monitoring attribute:

Yellow / Grey Values: When Test Mode is active but dynamic monitoring is off, values appear with a plain grey or static background. They reflect the last compiled offline value, not live controller memory.
Yellow Highlighted Live Values: When 'Watch On' is enabled, the background turns yellow (or designated dynamic color), and values refresh cyclically (typically every 1 to 2 seconds).
Activating Watch: Right-click the block header and select Watch On (or right-click specific pins like Start, FbkRun, Out -> Watch On).

Runtime Group Enable Conditions: The EN/ENO Execution Attribute

A secondary architectural reason for frozen values is that the block is not actually executing in the CPU:

Every block in CFC possesses an implicit EN (Enable) input managed by its parent Runtime Group.
If a programmer conditioned the runtime group with an active enable expression, or if EN is tied to a Boolean condition that evaluates to FALSE (0), the CPU skips block execution during cyclic interrupt OB35.
The instance Data Block remains untouched in CPU RAM, causing outputs to freeze at their last active state.

Communication Diagnostics: S7ONLINE and S7DOS Buffer Saturation

Low-level communication failures can also sever live updates:

PG/PC Interface Binding: The Windows access point S7ONLINE (STEP 7) must point to the active physical network card (or PLCSIM.TCPIP.1). If another software monopolizes the port, CFC loses its S7DOS communication handle (Error 0xFFDF_011E).
Communication Load Throttling: If too many CFC charts are opened in Test Mode simultaneously, the CPU's configured communication slice (default 20%) is saturated, causing S7DOS to drop polling requests.

Comparative Fault Matrix: Frozen Online Values in CFC Test Mode

The following table correlates online monitoring symptoms with their exact technical causes:

Visual Symptom in CFC ChartUnderlying Technical CauseDiagnostic IndicatorDirect Corrective ActionValues plain grey; 'Watch On' button disabledTest mode not engaged or PG/PC interface wrongGlasses icon unlitClick Debug -> Test Mode; verify Set PG/PC InterfaceTest Mode on; values grey and un-updating'Watch On' not activated for the blockGlasses icon lit, block plainRight-click block header -> select 'Watch On'Values yellow but frozen at static stateBlock runtime group disabled (EN = 0)Block skipped in CPU executionOpen Run Sequence; verify runtime group EN = 1Test Mode terminates with popup 0xFFDF_011ES7DOS handle severed / database disconnectedS7DOS Error 286Restart SIMATIC Manager; recompile chartsValues update intermittently (every 10s)Communication queue saturatedCPU communication load at 100%Close unused CFC charts; increase CPU comm load

Step-by-Step Restoration of Online Monitoring in Continuous Function Charts

Follow this sequence to restore dynamic monitoring on motor and valve blocks:

Engage Test Mode: In the CFC menu bar, select Debug -> Test Mode.
Enable Block Watch: Click the header of the MotL or VlvL block. Click the 'Watch On' button on the toolbar (or right-click block -> Watch On).
Register Individual Pins (Optional): If only specific signals are needed, right-click FbkRun or Out -> Watch On. Confirm yellow highlight appears.
Verify Runtime Group Execution: In CFC, select View -> Run Sequence. Locate the chart's runtime group in OB35. Confirm the group is active (Active checkbox enabled).
Check CPU Operating State: Verify the CPU is in RUN (green LED solid on controller or PLCSIM window).
Verify PG/PC Interface: Open Windows Control Panel -> Set PG/PC Interface. Confirm S7ONLINE is set to the valid active adapter.

Verification

Confirm online monitoring health through these tests:

Dynamic Signal Toggle: In the CFC chart, toggle an input (or force an input pin). Verify the value updates to 1 within 1 second in yellow.
Faceplate Synchronization: Open the matching WinCC faceplate. Verify commands issued from the faceplate reflect immediately in CFC Test Mode.
Trend Observation: Open the CFC Trend View (View -> Trend). Confirm dynamic curves plot online values smoothly without dropouts.
Performance Check: Open Windows Task Manager; confirm CPU utilization of s7epa64x.exe remains normal.

Limitations and Operational Precautions

Observe the following engineering precautions:

Close Test Mode When Finished: Leaving multiple CFC charts in Test Mode imposes a continuous communication burden on the CPU; always deactivate Test Mode before concluding engineering sessions.
Caution with Forcing in RUN: Forcing inputs or outputs on running production drives (MotL, VlvL) can cause physical equipment movement; always verify plant safety before modifying values online.
Commercial Accuracy Disclaimer: Software order numbers (MLFBs), package structures, and hardware capacity prerequisites vary across PCS 7 versions and hardware platforms. System integrators must confirm exact software entitlements and licensing requirements against the official Siemens Catalog CA 01 and obtain an authorized Siemens distributor quotation prior to purchasing.

Engineer FAQ

Does activating Watch On on all blocks slow down the S7-400 CPU?

Yes. Monitoring hundreds of blocks simultaneously saturates the CPU communication buffer, increasing communication latency and slowing down WinCC updates.