# Frequency data with wrong numbers

**URL:** <http://discussions.gridprotectionalliance.org/t/frequency-data-with-wrong-numbers/1371>\
**Category:** openHistorian\
**Created:** [February 6, 2025, 7:35pm UTC](http://discussions.gridprotectionalliance.org/t/frequency-data-with-wrong-numbers/1371 "2025-02-06T19:35:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![leticia\_acs](http://discussions.gridprotectionalliance.org/letter_avatar_proxy/v4/letter/l/3ec8ea/32.png) [@leticia\_acs](http://discussions.gridprotectionalliance.org/u/leticia_acs)\
**Post date:** [February 6, 2025, 7:35pm UTC](http://discussions.gridprotectionalliance.org/t/frequency-data-with-wrong-numbers/1371/1 "2025-02-06T19:35:40Z")

</div>

Hi!

So, I have an openPDC that is sending data to openHistorian and I am using CSV\_EXPORT adapter. When I get the files from this adapter or when I go to the web interface and export the data to csv, the frequency numbers are a little weird… The right number is suppose to be 60Hz, burt sometimes it appears like 600, not 60. Any idea why that’s happening?

 ![image](http://discussions.gridprotectionalliance.org/uploads/default/original/2X/6/6190de6e4a4617835d11ba9d30b48435d781aa26.png)

Thank You!

---

<div class="post-metadata">

**Author:** ![StephenCWills](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/stephencwills/32/20_2.png) [@StephenCWills](http://discussions.gridprotectionalliance.org/u/StephenCWills)\
**Post date:** [February 7, 2025, 2:30pm UTC](http://discussions.gridprotectionalliance.org/t/frequency-data-with-wrong-numbers/1371/2 "2025-02-07T14:30:11Z")

</div>

Hi leticia\_acs,

Those numbers don’t look like 60 Hz to me. They look more like 60-trillion Hz. Can you explain where the data is coming from? If there is a PMU sending data to openPDC, you should try connecting directly to the PMU using PMU Connection Tester and creating a debug capture to determine whether that’s just what the PMU is sending you.

Thanks,  
Stephen
