Sub-Second Tag Logging on S7-1200: WinCC Cycle Limits

Problem Statement and Application Constraints

The S7-1214C DC/DC/DC CPU is a compact controller widely deployed in machine-level applications where a small panel or mid-tier SCADA provides operator visibility. When process diagnostics demand a tag-to-disk cadence faster than the canonical one-second HMI polling cycle, the architecture that worked for trend displays and shift reports quickly collapses. A typical requirement—25–30 process tags logged at 10–20 ms intervals—produces data volumes and timing budgets that exceed the native capabilities of every Comfort, Advanced, and Unified Comfort Panel. The following reference decomposes the constraint, then maps each Siemens visualization product to the achievable minimum logging cycle, the storage envelope, and the engineering workarounds that bridge the remaining gap.

The decision path is not linear. Three independent limits stack on top of each other:

1. Acquisition rate – how often the visualization layer can request a tag value from the S7-1200 PROFINET interface.
2. Logging rate – how often the resulting value is committed to the archive store (CSV on the panel, SQL Server in the SCADA, or the internal database in WinCC Unified).
3. Storage rate – how much data can be retained before a ring buffer or rollover policy discards history.

Misalignment of any one of these produces either a missed sample, a frozen trend, or a disk-fill alarm. Engineers sizing a logging system must evaluate all three simultaneously.

S7-1200 Communication Architecture for HMI/SCADA Logging

The S7-1214C DC/DC/DC (catalog number 6ES7214-1AG40-0XB0, firmware V4.4 or later) exposes one integrated PROFINET interface for HMI and SCADA traffic. The interface is shared with programming, PUT/GET, and (from firmware 4.4) the OPC UA server, so bandwidth must be budgeted against all consumers.

The PROFINET connection is the bottleneck for any fast-cyclic acquisition. At 100 Mbps the wire itself is not the limiting factor, but the OPC UA / S7-communication stack on the controller side services a finite number of read requests per millisecond. Each read of a 32-bit tag occupies one PDU slot; bulk reads via the Put/Get protocol amortize the cost. Comfort and Advanced Panels use the proprietary S7-communication protocol and can read a configured tag block in a single fetch, while OPC UA subscribers require individual read or subscription requests.

WinCC Comfort and Advanced Panel Logging Limits

WinCC Comfort, WinCC Advanced, and the WinCC Unified Comfort Panel family share a common data logging subsystem that is hard-limited to a 1-second minimum logging cycle for continuous acquisition. This applies to:

• KTP1200 Basic / KTP1200 Basic DP (2nd generation, e.g., 6AV2123-1MB02-0AX0)
• TP1200 Comfort (6AV2124-1MC01-0AX0)
• TP1900 Comfort, TP2200 Comfort
• Unified Comfort Panels (MTP/MTP Unified)

The constraint is documented in the TIA Portal help for the "Logs" editor. When a log's acquisition cycle is configured below 1 s in any panel target, TIA Portal issues a warning and the runtime enforces the lower bound regardless.

Verification in TIA Portal: In the project tree, expand the HMI device → "Logs" → select the log → open "Properties" → "General". The "Acquisition cycle" dropdown enumerates the supported values; if the smallest value is 1 s, the device falls into the category above.

WinCC Professional (TIA Portal) Logging Capabilities

WinCC Professional, the PC-based runtime bundled with TIA Portal (V17, V18, V19, V20), replaces the panel-class 1 s limit with a configurable cycle down to 500 ms for tag logging. The runtime uses a SQL Server (or SQL Server Express for smaller systems) instance to persist the archive; tag values are committed via the SQL Server bulk-insert path, which is why 500 ms is the practical floor: each write transaction has measurable overhead on a general-purpose database engine.

Below 500 ms, WinCC Professional exposes the Tag Logging Fast add-in (introduced with V14 SP1, refined through V17/V18, still present in V20). Tag Logging Fast writes through a proprietary high-performance store and can achieve cycles in the 100–250 ms range, but it requires:

• A separate runtime license for Tag Logging Fast on the target PC.
• A 64-bit Windows 10/11 / Server 2019+ host (Tag Logging Fast is not available on WinCC Runtime 32-bit).
• Sufficient disk bandwidth—write-cache SSD recommended; spinning media will saturate below 1 GB/s of write throughput and stall the logger.

WinCC Classic V7.x and Fast Tag Logging

WinCC V7.0 through V7.5 SP2 (the "Classic" line, sold separately from TIA Portal Professional) was the de-facto sub-second logger for two decades. The product distinguishes between two logging subsystems:

• Tag Logging – SQL Server backed; minimum cycle is 500 ms.
• Tag Logging Fast – in-process binary store; documented minimum cycle is 250 ms, with field deployments reaching 100 ms on Windows Server 2016+ with local SSD storage. Fast Tag Logging bypasses SQL Server entirely and writes directly to its own segmented files.

The S7-1200 connects to WinCC V7.x via either the SIMATIC S7-Protocol Suite channel (PROFINET, MPI/DP via gateway) or the OPC channel against the S7-1200's built-in OPC UA server (firmware 4.4+). For 30-tag logging at sub-second rates, the SIMATIC S7-Protocol Suite with the "raw data tag" group and a single named connection outperforms OPC UA by roughly 3–5× in PDU throughput.

WinCC Unified RT Logging

From TIA Portal V17 onward, WinCC Unified (RT Unified) and the WinCC Unified Comfort Panels share a SQLite-backed logging subsystem. The Unified PC Runtime's logging cycle is configurable down to 100 ms for tag logging when the runtime is installed on a PC-class host, and down to 1 s on a Unified Comfort Panel.

Reference documentation for the underlying configuration is published in the TIA Portal V20 help – Basics of data logging (RT Unified). Key points that the official documentation makes explicit:

• Logging cycles below 1 s require the "Logging" license on the Unified PC Runtime, distinct from the basic RT license.
• Each log can hold a configurable number of entries; default 500 000; minimum storage ring is enforced at 100 000.
• Tags can be configured for "logging on change" (dead-band) or at a fixed cycle; on-change logging can produce sub-millisecond effective resolution when process values change rapidly.
• The runtime writes asynchronously to a per-log SQLite file; loss of the file system (power loss, network share outage) can lose up to one second of in-flight data unless a UPS is fitted.

Data Storage Sizing Calculation

Logging feasibility is inseparable from storage sizing. Engineers frequently discover that a 25-tag, 50 Hz acquisition does not fit on the panel's internal flash and cannot be streamed continuously to a network share.

The cadence rule for the requirement in the source (25–30 tags × 50 acquisitions/s ≈ 50 samples/s for the slowest feasible 20 ms cycle):

N_per_hour = N_tags × (3600 / t_cycle)
        = 30 × (3600 / 0.020)
        = 30 × 180 000
        = 5 400 000 samples/h

Assuming 8 bytes per sample (timestamp + 32-bit value + status byte + alignment), the hourly payload is:

Bytes_per_hour = 5 400 000 × 8
             ≈ 43.2 MB/h
             ≈ 1.04 GB/day

This exceeds the entire internal storage of every Comfort Panel in one hour. WinCC Advanced Runtime (500 000 entries per log) holds roughly 8 minutes of the same dataset. WinCC V7.x Tag Logging Fast (segmented files, no fixed cap) is the only architecture in the Siemens product line that scales linearly with storage hardware, provided the underlying disk subsystem sustains write throughput.

PLC-Side Pre-Buffering Architecture

When the visualization layer cannot acquire at the required cadence, the recommended architecture is to buffer the high-rate samples in the S7-1200 itself and push the burst to the SCADA only on demand or on event. The S7-1200 firmware provides two complementary mechanisms:

Data Log files (file-system-based)

From firmware 4.0 onward, the S7-1200 supports the DataLog instruction family (DataLogCreate, DataLogOpen, DataLogWrite, DataLogClose, DataLogDelete). Data Logs are CSV files stored on the optional SIMATIC memory card (SMC, up to 32 GB). The PLC can write to the log at OB1 cycle time (1 ms minimum, typically 5–10 ms in user code) without consuming PROFINET bandwidth for the logging operation itself.

Field-proven parameters:

• Write throughput on a Class 10 SMC: ~5 000 entries/s sustained, ~50 000 entries/s burst for short windows.
• Maximum file size: limited by the SMC capacity; recommended 4 MB per file to keep Web server downloads manageable.
• Web server integration: from firmware 4.4, the standard Web server exposes Data Logs as downloadable CSV, removing the need for OPC UA or S7-comm reads to retrieve them.

OPC UA Publish on event

From firmware 4.4, the S7-1200 OPC UA server can publish a data set when a configured event (boolean tag rising edge, threshold crossed, alarm acknowledged) triggers a subscription. The SCADA pulls the burst only when the trigger fires, keeping the steady-state acquisition cost at the SCADA's native cycle (1 s on a Comfort Panel, 500 ms on WinCC Professional) and pushing only the diagnostically relevant window.

Recipe-style DB snapshot

For deterministic event capture (the field report's "30 s before and 30 s after a fault" pattern), the recommended pattern is:

1. Configure a 30-tag FIFO data block of ARRAY[0..N] in the S7-1200, depth N chosen to span 30 s at the OB1 cycle.
2. On fault trigger, freeze the FIFO and copy its tail to a non-retentive snapshot DB.
3. Use the snapshot DB as the data source for the SCADA log; it can be read at any rate the SCADA supports because the values are static until reset.

This approach decouples acquisition rate from logging rate entirely and is the most common workaround for "20 ms but the panel only does 1 s" deployments.

Selection Matrix: HMI vs SCADA vs PLC-Side

Configuration Procedure: WinCC Professional with S7-1214C at 500 ms

The following step-by-step establishes a 30-tag, 500 ms logging link between the S7-1214C DC/DC/DC and a WinCC Professional V20 runtime. The procedure is identical for V17/V18/V19 with menu relocations.

Prerequisites

• TIA Portal V20 installed (any edition from Professional upward).
• WinCC Professional V20 RT license on the target PC.
• S7-1214C project compiled and downloaded; firmware V4.4 or later.
• HMI connection between the panel/PC and the PLC already configured (PROFINET, IP in same subnet, S7 connection activated in PLC properties → "Permit access with PUT/GET").

Step 1 — Enable the S7 connection on the PLC side

1. In TIA Portal, open the S7-1214C device configuration.
2. Select the PROFINET interface → "Properties" → "Connection mechanisms".
3. Check "Permit access with PUT/GET communication from remote partner".
4. Compile (Hardware) and download to the PLC.

Step 2 — Add an HMI connection in the project

1. In the project tree, right-click the WinCC Professional RT device → "Add new connection" → select the S7-1214C.
2. Confirm the connection name (default HMI_Connection_1). Verify the partner IP matches the PLC's PROFINET IP.

Step 3 — Create the tag list

1. Open the HMI device → "HMI tags" → create 30 tags of data type Real (or Int, Bool per process requirement).
2. For each tag, set the PLC tag connection to the S7-1214C and the address (e.g., %DB5.DBD0, %DB5.DBD4, …).
3. Set the acquisition mode to "Cyclic in operation" and the cycle to 500 ms.

Step 4 — Create the tag log

1. HMI device → "Logs" → "Add new log".
2. In the log's "Properties" → "General":
3. Name: ProcessLog_500ms.
4. Storage location: SQL Server (default).
5. Acquisition cycle: 500 ms (lowest selectable in WinCC Professional without Tag Logging Fast).
6. Number of entries: configure to retention target (default 500 000; expand if disk permits).

Step 5 — Add tags to the log

1. Drag each of the 30 HMI tags from the tag list into the log's "Logged tags" table.
2. For each logged tag, set the "Logging" column to "On change" or "Cyclic" as required. For 500 ms continuous capture, leave at default "Cyclic".

Step 6 — Compile and download to runtime

1. Right-click the WinCC Professional RT device → "Compile" → "Software (full)".
2. Download to the target PC via "Online" → "Download to device".
3. Start the runtime; verify the log fills by inspecting the configured SQL database (WINCC default instance, table ArchiveLog_ProcessLog_500ms via SSMS).

Step 7 — Configure the trend view

1. Insert a "Trend view" on the process screen.
2. Bind to the log and to the 30 tags.
3. Set the time axis to a 5-minute window; the trend will refresh at the SQL polling rate (default 1 s; configurable in the trend properties).

Verification and Commissioning Checks

After commissioning, execute the following verification matrix to confirm the system meets the 500 ms or 100 ms target before declaring the system production-ready.

Common Fault Modes and Field-Proven Remedies

Summary and Recommendation

For an S7-1214C DC/DC/DC and a 25–30 tag, 10–20 ms logging requirement, the panel-class Comfort/Advanced/Unified Comfort HMI products cannot satisfy the requirement directly. The minimum cycle for any Siemens panel-based runtime is 1 s. Engineers have three legitimate paths:

1. Accept 500 ms logging by deploying WinCC Professional (or WinCC Unified PC Runtime with the Logging license) and accepting that the original 20 ms target will not be met.
2. Use Tag Logging Fast in WinCC Professional or WinCC V7.5 SP2 to reach 100–250 ms, satisfying a relaxed version of the original target.
3. Pre-buffer on the S7-1200 using Data Logs or a FIFO data block, and push only the diagnostically relevant window to the SCADA. This is the only architecture in the Siemens portfolio that natively supports 20 ms acquisition for 30 tags without compromise.

Storage sizing, time synchronization, and PROFINET bandwidth must all be engineered together. The minimum cycle is not a single number but a system-wide constraint, and the right architecture is the one that aligns cycle, capacity, and acquisition cost against the operational use case rather than against an isolated specification target.