CXA_ModbusTCP Communication from Virtual Core to external device

[Lauri]

Hello.

Is it possible to communicate from Virtual Core as Client with CXA_ModbusTCP to external device, for example physical Core?

For some reason I end up with some sort of socket error. Could it be some setting that needs to put correctly?

[CodeShepherd · Accepted solution]

See online documentation for general information about CXA_ModbusTCP.

See "How to communicate between a ctrlX COREvirtual and other applications" for general communication setup.

There are at least two possible ways:

1. Start ctrlX COREvirtual in network adapter mode and set IP (e.g. 192.168.1.2) to the same subnet as the real ctrlX CORE (e.g. 192.168.1.1) connected to your PC. Then bridge in your Windows network connections, the virtual network adapter with the real one, so data is routed between both correctly. To get access to the devices again enter a IPv4 address to the network bridge in the same subnet as your devices e.g. 192.168.1.3.
   
   
2. If 1st is not possible e.g. because of company restrictions, start ctrlX COREvirtual in port forwarding mode and set IP (e.g. 192.168.2.2) to a different subnet as the real ctrlX CORE (e.g. 192.168.1.1) connected to your PC, so data is routed correctly via the standard gateway in ctrlX COREvirtual.
   1. Send from real to virtual control:
      ctrlX PLC Engineering ModbusTCP connection ctrlx CORE to ctrlX CORE virtual
      
      
   2. Send from virtual to real control:
      You will have to forward the port you want to use for communication in the ctrlX CORE in port forwarding mode and also add an inbound rule to your windows firewall for that port to let the data path through.