Looks like device data is coming in out of order - the 1.0 historian that is built-in to openPDC does not support out of order measurements. You might want to check your PMU time source.
Otherwise, just use the openHistorian 2.0 to archive the data - this newer archive tool does support out of order insertions. Also, you can just use an STTP subscription to directly connect to you openPDC from openHistorian to start immediately archiving data. To do this:
Install openHistorian
Open the openHistorian Manager (UI tool from Start Menu - not web UI)
Go to Inputs > Subscription Based Inputs > Create Internal Subscription
Enter:
a. Acronym: OPENPDC
b. Name: openPDC System
c. Hostname: IP of openPDC (or localhost if installed on same system)
d. Port: 7165
e. Select: STTP
f. Uncheck Use Source Prefix "OPENPDC!"
g. Click Next the click Save
Wait a few seconds, then go to Monitoring > Graph Measurements
Data will be successfully archived into openHistorian
Hi,Ritchie
Thanks for your reply.I followed the steps above.And I didn’t see that error any more.but have a question that why the light in front of the PMU is grey…
It looks like the full-resolution subscription that provides data to the graph is returning data for those points when you select them, but the throttled subscription that provides 2-second updates to the treeview is not. How do the timestamps of the 1212 device compare to those of SHELBY? You may need to adjust time zones, fix time slew, disable SHELBY, or adjust the lag/lead time of the display under Display Settings above the graph.
Assuming you followed my instructions, data should be stored in the openHistorian even if it is coming in out of order. Open a browser and go to this link: