OPCUA Plugin 64 bit clash with 32 bit libuv dll

[silenroc1]

Situation:

I use the build191121 version and work on a 64 bit windows machine. The OPC-UA plugin requires the libuv dll. This dll appears to be available only in a 32 bit version. It looks like this results in a 32/64-bit mismatch, given the error code shown below.

How should I get around this? I browsed some stackoverflow, but all suggestion require changes to the actual C#-project, should they work. E.g.,

Expected results:
I expect the OPC-UA plugin to correctly start.

Actual Results:
When starting the OPC-UA Plugin the following error message is returned in the log:

[1] Could not load HTTPS Stack Listener. An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) AggregateException 'One or more errors occurred.' -

[mySCHOTT]

Try to replace libuv.dll by the 64bit version. Just goolge e.g. "libuv.1.10.0.nupkg" or download directly from https://www.nuget.org/packages/Libuv/.

Please have look in issue #31 too. https://github.com/admin-shell/aasx-package-explorer/issues/31

[silenroc1]

@mySCHOTT Thank you, indeed I had to take the 64-bit libuv.dll from the libuv-package and put it in the folder with AasxPackageExplorer.exe.

However, the plugin still does not seem to function completely correct for build191121. When in builds/build191121/public-release-with-browser I run the following command:
.\AasxPacakgeExplorer.exe -dll <absolute-path-to>\Net46AasxServerPlugin\Net46AasxServerPlugin.dll

After opening an .aasx-file compatible with that build, the OPC-UA plugin starts as follows:

Do you know why it doesn't start? Feels like I may be missing something simple.

[mySCHOTT]

Please try to connect via an OPC Client to the server. You will find the right opc connection string in Net46AasxServerPlugin.Config.xml. Please try opc.tcp://localhost:51210/UA/SampleServer as anoymous in your OPC Client.

Please make sure, that no firewall is blocking the OPC port(s).

[silenroc1]

Thanks a lot, I can indeed inspect the AAS opened in the Package Explorer via UaExpert.

When it is opened, a steady stream of '[2]IsReadyToPublish [1] FALSE' is printed in the AAS Explorer log, reaching several thousand in a few minutes. Is that something to be bothered about? It does make the Package Explorer quite slow eventually.

[mySCHOTT]

I'm glad that someone is doing a PoC how the aasx things could implement and work. In my opinion, this is more and less an education. Could be a product later, but it's hard work. Currently, the opc implementation is more and less a nightmare and not usable for a demonstrator inside - too fast to many questions.

But again, I'm really glad that someone is releasing some aasx solutions. That is one reason why I support as much as possible on issues in order to move forward.