PLC SCADA timestamp clock synchronization faults - PLC Playground troubleshooting guide

PLC and SCADA Blame Different Events First? Align the Clocks Before the Timeline

Two event logs can disagree about cause and effect when their clocks differ. Before ordering faults by timestamp, establish what each timestamp represents and whether the devices share a trustworthy time reference. Millisecond-looking precision does not guarantee millisecond accuracy.

Original event-correlation framework; clock configuration depends on the installed system.

What is happening?

A source timestamp, server receipt time, and HMI display time describe different moments. Clock offset, time-zone presentation, daylight-saving conversion, and buffering add further differences. Correlating logs requires both synchronized clocks and an understanding of where each event was stamped.

Check these five things

  1. Record the clock source and synchronization status for the PLC, server, HMI, and relevant devices.

  2. Identify whether each log uses UTC, local time, or a converted display value.

  3. Determine whether timestamps originate at the event source or when a collector receives the data.

  4. Compare a known test event across logs without assuming network arrival order equals physical event order.

  5. Document remaining timing uncertainty before drawing a root-cause conclusion.

Worked example

A PLC clock is two seconds ahead of the SCADA server. A PLC stop appears to occur after a server communication alarm even when the physical sequence was the reverse. Correcting the interpretation requires clock evidence, not rearranging the narrative to fit the displayed order.

Quick diagnostic reference

Timestamp property Question
Origin Where was it assigned?
Reference Which clock and time zone?
Uncertainty How precise is the ordering?

The mistake to avoid

Changing a production clock can affect logs and time-based behavior. Time corrections belong to the approved synchronization procedure.

How to verify the fix

Capture a controlled event and show that the logs agree within the required uncertainty, including the documented display-time conversion.

Field-work boundary: These are educational diagnostic guides. Use the exact equipment manuals and approved site procedures. Electrical testing and machinery changes belong to qualified, authorized personnel; control hazardous energy and validate affected functions before release.

Technical reference

OPC Foundation: source and server timestamp semantics. The examples and diagnostic tables above are original teaching material; they do not replace the product manual.

Continue troubleshooting

Previous Post Next Post