Bulid openhistorian from source code

wagebro · April 28, 2020, 10:05am

Hi,
When I bulid openhistorian from source code ,it shows problems like the screenshot.

How could I solve these errors?
Thank you very much!

clackner-gpa · April 28, 2020, 1:58pm

It looks like the class ‘AlarmDeviceStateView’ is defined in two places. Possibly because you copied the definition or created your own class with the same name.
Based on your screenshot it also looks like you have an outdated version of the source code that might have this issues. I would suggest getting the latest version from Github.

Good Luck,
Christoph

wagebro · April 29, 2020, 2:31am

Hello ,Christoph
Thanks for your reply.I have downloaded the latest version of the source code ,but it shows the same problem .

And I notice that they are located in the same folder except for the first error.

Maybe there’s something wrong but I haven’t found it yet .

Thank you !
wagebro

clackner-gpa · April 29, 2020, 2:08pm

So there is a couple of things going on that is causing these errors. Because there are duplicate definitions for AlarmDeviceStateView Visual Studio is unable to compile openHistorian.Adapter.Model.

This results in a .dll file missing for the openHistorian to properly build which results in all the other errors.

Essentially if you fix the issue with AlarmDeviceStateView everything else should resolve itself.

wagebro · April 30, 2020, 2:06am

Hi,Chirstoph
After I rebuilt the solution ,the error about AlarmDeviceStateView disappeared ,but the other errors remained.So I am not sure if AlarmDeviceStateView caused the other errors.
thank you !

StephenCWills · April 30, 2020, 2:19am

Can you try moving the solution to a path comprised only of ASCII characters to see if that helps?

wagebro · April 30, 2020, 2:24am

Hi,Stephen,
oh,it rebuilt successfully!
There may be some compatibility issues with Chinese.
Thank you very much!

StephenCWills · April 30, 2020, 3:22am

While I’m not 100% sure what the cause of the incompatibility is, I have read that NTFS supports all Unicode characters in file names with just a few exceptions, but batch scripts only support the current ANSI codepage. ASCII is generally a good bet when it comes to compatibility. I’m glad that it’s working for you.

wagebro · May 7, 2020, 1:43am

Hi，Stephen
I have one more question .In our team ,we use a modified protocol based on IEEE Std C37.118 to transfer data.What should I do to add this protocol into openhistorian ?Or could you give me some advice?
Thank you very much!
wagebro

StephenCWills · May 7, 2020, 1:07pm

You should create an input adapter, then add a record to the Protocol table referencing your custom input adapter.