You will then see the Restore Complete dialog box and click OK.Ħ You will now see the restored project in the Citect Explorer. You then need to decide if you want it restored to a Current project or a New project.ĥ If the project doesn't exist you will get a dialog box asking you whether you wish to create the folder and select Yes. Select Restore in the menu.Ģ The Restore Project menu appears and click on the Browse button.ģ Navigate to the backup file which with have the ctz file extension and click Open.Ĥ Any associated projects will be listed and select this if as appropriate. This Tech Note walks you through how to restore an application in CitectSCADA.ġ Open the Citect Explorer and Right Click on My Projects. 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.īest regards dfumagalli Posts: 2 Joined: 27.How to Restore an HMI Application in CitectSCADA 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). 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. 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). A name change of the company took place to Ci Technologies, and then to Citect to take advantage of the well known name of its flagship software product, CitectSCADA. The company was then known as Control Instrumentation. 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. Citect began as a subsidiary of Alfa Laval in 1973.
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.
0 kommentar(er)
