SYNC CLOCKS / Practical resources
Clock System Troubleshooting: Time Mismatch Checks
Check synchronized clock time differences by affected area, power, time source and network status. Use a symptom checklist before contacting support.
In this guide
What should be recorded before changing anything?
Start by recording the symptom, affected locations and the time reference used for comparison. This preserves useful evidence and helps distinguish a display setting from a source, communication or power problem before anyone changes the system.
Note when the issue was first seen, whether it followed a power interruption or approved network change, and whether every affected clock shows the same difference. Photograph the display and any visible indicator. Record labels exactly as shown rather than translating them into an assumed fault code. This guide organizes observations; reset sequences, configuration changes and repair instructions must come from the applicable device documentation.
Are all clocks affected or only one area?
The affected pattern helps identify where to begin investigating, but it does not establish a cause by itself. Compare a working location with an affected location and record which reference, distribution segment and power arrangement they share.
| Observed pattern | First information to collect |
|---|---|
| All displays show the same difference | Common reference status, intended time zone and recent system-wide changes |
| One building or floor differs | Shared network segment, distribution equipment and power conditions |
| One clock differs | Model, visible state, location and comparison with a nearby working clock |
| Only one display type differs | Configuration and receiving method used by that group |
Do not assume that the nearest working clock uses the same source. Mixed installations can contain several distribution methods. The equipment inventory is more useful than physical proximity alone.
Is the time difference fixed or growing?
A stable offset and a changing difference deserve different investigations. Record repeated observations against the same reference, with the date, local time zone and observation time included, before concluding that the clock is drifting.
A whole-hour difference can point toward a time-zone or daylight-saving setting, but the actual configuration must be checked. A growing difference can justify reviewing the last successful synchronization and source availability. Neither pattern proves a particular component has failed. If the discrepancy involves only analog hands or part of a digital display, include a clear photograph and seek model-specific guidance.
A web clock can support an ordinary time-of-day observation, but it is not proof of precision performance. NIST explicitly distinguishes its time.gov display from a traceable measurement service. Use an appropriate measurement method if the project’s tolerance is smaller than the observation method can resolve.
What can the responsible staff check without changing settings?
Use visible status information and existing records to check power, reference availability and the intended communication path. Network observations should be performed by the responsible IT team using approved access, without opening broad firewall rules or replacing configuration as a first response.
- Confirm whether the clock and relevant distribution equipment appear powered.
- Record the selected time source and its visible state, where this information is available.
- Ask IT whether an affected network segment has a known incident or recent change.
- Record last synchronization or connection information only if the installed model exposes it.
- Compare affected and unaffected groups without assuming their settings are identical.
For architecture background, see network synchronized clock systems. Do not interpret a connection indicator alone as proof that valid time is being received.
What should be checked after a power interruption?
After an interruption, document the sequence of equipment recovery and the displayed behavior before attempting a restart. A clock, network switch and reference server may regain service at different times, so the order of events can help support understand the symptom.
Record when power returned, which devices were available and whether the display later changed without intervention. Recovery behavior and synchronization intervals vary by model and configuration. Do not apply another manufacturer’s waiting time, reset button sequence or default credentials to the installed equipment.
When should troubleshooting stop and support take over?
Stop before opening enclosures, working at height, changing electrical connections or performing an undocumented reset. Escalate when safe observation cannot explain the issue, a fault persists, or further testing would interrupt a working installation.
Prepare a support record containing the location, model and firmware if visible, affected quantity, onset time, photographs, observed difference, comparison reference and recent approved changes. Include the exact visible status text and any available last-sync record. Keep passwords, access tokens and sensitive network details out of public enquiry fields.
Use technical enquiry support to share the symptom summary. Find available documents in the download center, or consult the synchronized clock FAQ for general operating questions. A useful escalation preserves observations instead of concealing them behind repeated resets.
Discuss your clock system requirements
Send your clock locations, quantities, available infrastructure and required timing performance to HC Electronics.