This project has moved and is read-only. For the latest updates, please go here.




we are currently testing OpendPdc.
We are encountering some issues that we would like to undergone you in order to establish if this tool could be integrated in our WAMS.
The first investigated issue is the "Power Calculations".
I’m following the procedure reported in the pdf file at the link
either by inserting the connection string:
inputMeasurementKeys={example PPA:5; PPA:6; PPA:9;PPA:10};
outputMeasurements={example PPA:77;PPA:78};
FramesPerSecond= example 50;
LagTime=example 3.0;
LeadTime=example 1.0
Or by directly using the mask with “Parameters” and “Value”. In this case I found this situation: the quantities tag is replaced (I guess wronlgy) with a text string different form the usual one above (es. PPA:num). Attached you can find the described situation.

Furthermore I would like to tell you that also the “Manage Power Calculations” from “Action” in the toolbar has been used for the purpose but unsuccessfully.
Could you give us support to overcome the issue?

file attachments

Closed May 10, 2016 at 6:55 PM by staphen


cosimopis wrote May 3, 2016 at 3:16 PM


Exception Source: GSF.TimeSeries
Exception Type: System.InvalidCastException
Exception Message: Impossibile eseguire il cast di oggetti di tipo 'PowerCalculations.PowerCalculator' sul tipo 'GSF.TimeSeries.Adapters.IOutputAdapter'.
Exception Target Site: TryCreateAdapter

---- Stack Trace ----
GSF.TimeSeries.Adapters.AdapterCollectionBase`1.TryCreateAdapter(adapterRow As DataRow, adapter As T&)
   openPDC.exe: N 00483

(Outer Exception)
Date and Time: 5/3/2016 3:56:50 PM
Machine Name: NTB200872
Machine IP: ::1
Machine OS: Microsoft Windows NT 6.1.7601 Service Pack 1
Current User ID: NT SERVICE\openPDC
Current User Name:
Current User Phone:
Current User Email:

Application Domain: openPDC.exe
Assembly Codebase: C:/Program Files/openPDC/openPDC.exe
Assembly Full Name: openPDC, Version=, Culture=neutral, PublicKeyToken=null
Assembly Version:
Assembly Build Date: 4/28/2016 12:17:50 AM
.Net Runtime Version: 4.0.30319.42000

Exception Source:
Exception Type: System.InvalidOperationException
Exception Message: Failed to load adapter "POWER_CALC" [PowerCalculations.PowerCalculator] from "C:\Program Files\openPDC\PowerCalculations.dll": Impossibile eseguire il cast di oggetti di tipo 'PowerCalculations.PowerCalculator' sul tipo 'GSF.TimeSeries.Adapters.IOutputAdapter'.

staphen wrote May 3, 2016 at 7:28 PM

Hello cosimopis,

Regarding your error, the PowerCalculator adapter is an action adapter, not an output adapter. There seems to have been a bug introduced at the beginning of April that caused all the custom adapter pages to display only action adapters in the type dropdown. You should be able to work around this issue by editing the "Search directory" text box to point to different directory, then change it back. This will repopulate the type dropdown with the correct adapter types. A fix has been implemented and will be available in the next nightly build version (v2.2.35).

The "Manage Power Calculations" tab is the recommended approach for creating power calculations. I don't know what issues you had with it, and I don't know what database engine you're using, but I fixed an issue today which I suspect would have inhibited its functionality when using a database engine other than SQL Server. This fix will also be included in the next nightly build version (v2.2.35).

As for your observations regarding the InputMeasurementKeys on the adapter screen, it is working as expected. The InputMeasurementKeys field in the connection string can be specified as a list of measurement IDs, a list of measurement point tags, a list of signal IDs (GUIDs), or a filter expression. The checkboxes on that screen generate a list of signal IDs, which is what you are seeing in your screenshot. What you may also notice is the order in which the signal IDs appear in the list is fixed; it is not based on the order in which you clicked on the checkboxes. This can be inconvenient in cases like the PowerCalculator which requires them to be defined in a specific order. However, if you enter text directly into the Filter Expression field, it will copy that straight into the connection string so it's not entirely unusable.

Finally, as a side note, I wanted to let you know that our codebase has been moved to GitHub. As part of the transition, we would like to begin using the GitHub issue tracker to track future issues.


cosimopis wrote May 6, 2016 at 8:50 AM

Hi Stephen,
first of all many thanks!!!
I will follow you suggestions to fix the issue.
Let's keep in contact.


cosimopis wrote May 6, 2016 at 9:22 AM


when will version v2.2.35 be available for download?



staphen wrote May 6, 2016 at 1:17 PM


The nightly build process runs once per day at 12 AM Eastern. It automatically increments the version numbers and posts a build with the latest changes which can be downloaded from the following page.

The latest nightly build version is currently v2.2.38.


cosimopis wrote May 6, 2016 at 3:02 PM

Thanks again Stephen!!!

wrote May 10, 2016 at 6:55 PM