Do you have more logfiles or any hints where the build process is stopping? 

If you want to connect it with hardware you need to use a websocket based protocol. For Beckhoff PLCs you could use Twincat HMI (https://doc.realvirtual.io/components-and-scripts/interfaces/twincat-hmi) or you could use MQTT (which is also working over websocket: https://doc.realvirtual.io/components-and-scripts/interfaces/mqtt) or what we will release in the next 2 weeks is our own standard Websocket protocol (https://doc.realvirtual.io/components-and-scripts/interfaces/websocket).

Hi, the deactivated components are in this case correct. We want to prevent the signal update method, which is not needed in this case. Are you maybe writing on PLC inputs which are also available in hardware. In this case you can't force or even set it from realvirtual because the real physical input value can't be changed.

It is technically impossible to communicate with Webbrowsers with non Websocket based protocols - which is the case for most of the industrial plcs protocols. There is no way making OPCUA communication directly working with a WebGL application.

Hi,

it seems that you are using an old version. This issue has been solved. Some interfaces need to be deactivated before compiling because they are using functions which are not available in WebGL.

You should upgrade to the latest version or delete the interfaces (the full folder of it) which are not supported in WebGL. You can check the table on this page here: https://doc.realvirtual.io/advanced-topics/supported-platforms

Hi, can you somehow share your OPCUA server so that we can debug it on our PCs?

you can check the the table here for a feature comparison:
https://realvirtual.io/en/buy/

no, this connection is only in professional

Hi,