duduyoyo

There is a HDA solution for Python [here](https://github.com/duduyoyo/WebSocket4OPC). Good luck!

Basically in write() of opcSyncIO.js it passed write.value and write.handle to construct a ComValue, which is wrong. It should pass write.value[0]/write.handle[0] instead. But there is still a glitch in return...

utgard使用J-Interop来作COM通讯，而J-Interop并没有解决DCOM hardening的问题，参见[这里](https://sourceforge.net/p/j-interop/discussion/600729/thread/731d99133f/)。 可以试试这个[方案](https://github.com/duduyoyo/WebSocket4OPC)，这样不用再担心未来的DCOM问题。它更简单直接，不需要COM和DCOM，且支持各种语言如Python、JavaScript、Java、C++、C#等等。用的好别忘加星：-）

Try [this](https://github.com/duduyoyo/WebSocket4OPC) to avoid DCOM hardening issue for your OPC app.

J-Interop can't work properly after Microsoft applied DCOM hardening. You can check [link](https://sourceforge.net/p/j-interop/discussion/600729/thread/731d99133f/) here on this issue. Alternatively, you can try this [solution](https://github.com/duduyoyo/WebSocket4OPC) to retrieve OPC data back in Java....

If you don't want to be bothered by DCOM, you can check this [solution](https://github.com/duduyoyo/WebSocket4OPC). JavaScript/Python is supported natively, and it is a cross-platform solution in client side.

Try [this](https://github.com/duduyoyo/WebSocket4OPC) if you don't want your OPC app affected.

See if [this](https://github.com/duduyoyo/WebSocket4OPC) can help you.

It looks like you don't have 64-bit proxy dll registered properly. Alternatively, if you don't want to deal with win32 API like CoCreateInstanceEx() you can try this 64-bit [solution](https://github.com/duduyoyo/WebSocket4OPC). No...

Check [here](https://github.com/duduyoyo/WebSocket4OPC), it works with classic OPC HDA/DA/AE. Cheers!