So, the only application failing at establishing a connection would be Citect.
This implies ModNET TCP/IP is a legitimate and VirtualBox supported feature. The Citect software at this point time outs on this port 502.Īt the same time, I used another monitor application and I can read and write ModNET data in a perfect way, both using NAT and host interface modes (PCnet-FAST III net card emulation). I created one guest machine and made a very simple 'hello world' application reading one value over ModNET thru port 502. The application would run a basically vanilla Windows XP SP3 guest (and same Win XP SP3 host), the only apparent need is to read and write over port 502 (ModNET TCP/IP) which in turn is the PLC communication conduit (see it as a remote TCP/IP server). Two versions of the application cannot be installed on the same computer so I decided to create several Citect 6.10 platforms to do my tests and then port the conversion in the development machine with version 7. Here's the site of the application / IDE (freely available, goes in demo mode which is plenty enough to see the effects) My company tasked me with migrating our current SCADA appliances from Citect 6.10 to Citect 7.
