# Check pmu sync with OPENPDC

**URL:** <http://discussions.gridprotectionalliance.org/t/check-pmu-sync-with-openpdc/305>\
**Category:** openPDC\
**Created:** [April 3, 2018, 11:10am UTC](http://discussions.gridprotectionalliance.org/t/check-pmu-sync-with-openpdc/305 "2018-04-03T11:10:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pietropau](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/pietropau/32/217_2.png) [@pietropau](http://discussions.gridprotectionalliance.org/u/pietropau)\
**Post date:** [April 3, 2018, 11:10am UTC](http://discussions.gridprotectionalliance.org/t/check-pmu-sync-with-openpdc/305/1 "2018-04-03T11:10:31Z")

</div>

Hi,  
Is there any way to find pmu with wrong timestamp or clock failure ?

Regards  
Pietro

---

<div class="post-metadata">

**Author:** ![ritchiecarroll](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/ritchiecarroll/32/2_2.png) [@ritchiecarroll](http://discussions.gridprotectionalliance.org/u/ritchiecarroll)\
**Post date:** [April 3, 2018, 1:28pm UTC](http://discussions.gridprotectionalliance.org/t/check-pmu-sync-with-openpdc/305/2 "2018-04-03T13:28:29Z")

</div>

The easiest way is to navigate to the `Monitoring > Stream Statistics` screen in the openPDC Manager. Here you can check on the statistics for latency, e.g., `Average Latency`, which is an indication of timestamp deviation on the PMU data stream as compared to the local system clock. This value is reported in milliseconds, very good values (with an accurate local clock) will report numbers less than 1,000. Very high numbers usually indicate a bad timestamp. Additionally, the `Time Quality Errors` statistic reports the total number of encountered bad time flags during the last reporting interval, i.e., every 10 seconds.