This on VirtualBox 2.1.2.
My company tasked me with migrating our current SCADA appliances from Citect 6.10 to Citect 7.
Here's the site of the application / IDE (freely available, goes in demo mode which is plenty enough to see the effects)
http://www.citect.com/
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.
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).
I created one guest machine and made a very simple "hello world" application reading one value over ModNET thru port 502.
The Citect software at this point time outs on this port 502.
At 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). This implies ModNET TCP/IP is a legitimate and VirtualBox supported feature.
So, the only application failing at establishing a connection would be Citect.
What I'd like to ask is if someone else succeeded at running such application with a TCP/IP connection to an external PLC / device or hints at something to detect what eventual undocumented ports Citect is trying (and failing) to open.
Of course asking Citect about this operation leads to "ask Virtualbox, the product itself connects perfectly on a "true" computer (indeed, running Citect 6.10 directly on the host works perfectly).
I don't even hope being given a resolutive solution as the software is very specialistic, I'd just like to see if there are pointers to tools / documentation to help me out at this.
Best regards
Anyone succeeded at VirtualBoxing Citect?
-
- Posts: 2
- Joined: 27. Jan 2009, 16:31