How to Correct WinCC Runtime Time Display and Synchronization in PCS 7 V9.0 SP3

For a PCS 7 V9.0 SP3 system where WinCC Runtime shows an incorrect or stale date and time, first distinguish the clock source from the display format. A CP 16x3 configured as a time receiver is a slave; a workgroup without a central time source still requires a configured OS-server time-synchronization master. Siemens' PCS 7 V9.0 SP2 manual documents that workgroup arrangement and the CP settings. The ticket's additional symbols require separate message-template verification.

Symptoms and likely cause

The reported system uses PCS 7 V9.0 SP3 and WinCC 7.4, with a CP1623 acting as a time receiver and no central time master defined. In Siemens' V9.0 SP2 time-synchronization model, an OS server can provide cooperative time synchronization on the plant bus when no central master exists. A receiver-only CP does not supply that missing master. Confirm the configured topology before changing clocks.

Configure the time receiver

In the hardware configuration for the applicable CP 16x3, open its properties and select the Options tab. In the Time of day area, enable time-of-day handling and select Slave (time receiver), as documented in the PCS 7 Time Synchronization manual §6.4.1. Keep the adapter and role consistent with the project's existing time-source design; do not set a second master simply to make a display update.

Configure a workgroup without a central time source

For the documented workgroup arrangement, configure an OS server as a cooperative time master on the plant bus using the WinCC Time synchronization editor. Select the network adapter that connects to the intended bus and configure its role as Master, following §6.4.3.2 of the manual. Siemens describes OS clients as time slaves; where clients use a connected WinCC server, configure the client accordingly. The exact adapter names and topology are project-specific. Ensure an OS server is active for synchronization to the AS as described by the manual.

Check the displayed time basis

Time synchronization and date/time presentation are different settings. Before loading the OS, inspect the OS computer object's Parameters in WinCC Explorer and its Time basis for time display in runtime setting (§6.4.2.1). Confirm whether the project expects UTC or local time and check the selected display format. The format changes presentation; it does not establish a time source.

Interpretation of additional symbols

The ticket reply attributes ~X~ to a message without a comment and ~??~ to a BATCH ID when no BATCH process is present. The cited Siemens time-synchronization manual does not document those symbol meanings. Treat them as source-reported clues, not verified WinCC definitions. Inspect the specific runtime text, associated message configuration, and any BATCH-related display mapping before drawing a conclusion; do not assume these symbols share the clock-synchronization cause.

Expected behavior and verification

After configuration and the project's normal compile/load process, verify time on the configured source, OS server, OS client, and relevant AS through approved diagnostics available in that installation. Compare the actual displayed date/time against the intended UTC or local basis and confirm it advances and remains consistent after the synchronization interval. Siemens notes that its synchronization behavior treats deviations up to ±5 seconds differently from larger deviations; a large clock correction can affect timestamp interpretation. Do not use a changed display alone as proof that every system node is synchronized.

Verification

Check the configured time source and the role of each participating node against the PCS 7 V9.0 SP2 manual, then confirm actual time on the server, client, and AS in the deployed topology. Separately verify the runtime time basis and inspect the original message configuration for the reported symbols. The cited procedure is documented for V9.0 SP2; the ticket reports V9.0 SP3, so confirm the applicable SP3 project documentation and installed component behavior before applying changes.

Limitations and Operational Precautions

This guidance is scoped to the Siemens V9.0 SP2 time-synchronization manual and the ticket's PCS 7 V9.0 SP3 / WinCC 7.4 context; it does not establish every SP3-specific detail. Time-source changes can affect event timestamps and sequence-of-events interpretation. Coordinate changes with operations, preserve the project, follow site change control, and plan any OS compile/load for an approved maintenance window. Do not change clocks manually or promote an adapter to master without confirming the plant time architecture. The meanings of ~X~ and ~??~ remain unverified.

Engineer FAQ

Does setting the CP1623 as a time receiver make it the time master? No. In the cited configuration it is a slave (time receiver); the time source must be established elsewhere in the synchronization design.

What should provide time in a workgroup with no central master? The V9.0 SP2 manual documents OS servers as cooperative time masters on the plant bus, with OS clients and AS participating as slaves according to the topology.

Can the runtime date/time format fix an unsynchronized clock? No. The OS computer object's time-basis and format settings control how time is presented; they do not create a synchronization source.

Are ~X~ and ~??~ confirmed clock error codes? No. Their meanings are reported in the discussion but are not established by the cited synchronization manual. Check the corresponding message and display configuration.

Can the V9.0 SP2 procedure be assumed for every PCS 7 V9.0 SP3 installation? The cited manual alone does not prove that. Validate the settings against the installed SP3 components and project topology.

Technical References

Siemens, Time Synchronization (V9.0 SP2), A5E39221891-AC, especially §§3.7, 6.4.1, 6.4.2.1, and 6.4.3.2: https://cache.industry.siemens.com/dl/files/559/109767559/att_985409/v1/ps7tsy_b_en-US.pdf