The problem is that OpenPDC (historian) changes the data format of the timestamp, to a format different from those output by PMUs. We get the proper time frame when we check it using both pmu tester and OpenPDC graph visualizer, but when we get the values from the historian (MySQL database) the timestamp value does not relate to any time format.
To clarify the problem:
Our data samples (Ado output adapter-Mysql database) looks like below.
PMU ID TIMESTAMP Value (angle)
6dbfb2e6-4f1d-4e5e-ae60-eefd5fe81c15 636268434320000000 -91.08
The value in your TIMESTAMP column looks like it’s in ticks, which is 100-nanosecond intervals since midnight on 01-01-0001. The adapter is designed to use ticks if you specify
timestampFormat=null in the connection string for the adapter.
You can also specify other formats.
Standard formats: https://msdn.microsoft.com/en-us/library/az4se3k1(v=vs.110).aspx
Custom formats: https://msdn.microsoft.com/en-us/library/8kb3ddd4(v=vs.110).aspx
The default format, if you do not specify anything for the timestampFormat in the connection string, is a custom format of
dd-MMM-yyyy HH:mm:ss.fff which should produce timestamps like “05-Apr-2017 18:37:50.164”.