![citect logo citect logo](https://cpimg.tistatic.com/06076700/b/4/Schneider-Vijeo-Citect-SCADA.jpg)
Argyle contributed $1 million to the development of Citect for Windows.
![citect logo citect logo](https://demo.pdfslide.net/img/380x512/reader024/reader/2021010413/5b328f917f8b9a81728cadd2/r-2.jpg)
The company was originally intending to use a Honeywell system until a number of Arygle's site engineers talked Argyle around to Citect after highlighting the existing problems they were having with Honeywell systems on site. Citect for Windows was written as a direct response to a request by Argyle Diamonds. The configuration methodology remained similar to Citect for DOS but became more intuitive under MS Windows. It no longer needed the DSI card to run on a PC. This was due to insufficient processing power available in the 286 and 386 PCs available at the time.Ĭitect for Windows Version 1 ĭuring the early 1990s PC computational power had caught up and Microsoft Windows based software was becoming popular, so Citect for Windows was developed and released in 1992.
#Citect logo 32 bit
The runtime software ran on a DSI card a 32 bit co-processor that was inserted into an available ISA slot in the PC.
![citect logo citect logo](https://fiverr-res.cloudinary.com/images/q_auto,f_auto/gigs2/202127098/original/695b177d7cbde2415ce80a6458f895741420e383/be-your-certified-citect-scada-developer.jpg)
#Citect logo drivers
Software drivers were written for many protocols its ability to communicate with a variety of devices - and to have new drivers written when required - became a primary selling point for Citect.
#Citect logo serial
By referencing these tags at animation points using other configuration databases, the user could show the state of equipment such as running, stopped or faulted in real-time.Ĭitect for DOS could communicate with various programmable electronic devices via the various serial links offered by the device some through direct PC serial port connections, others through 3rd party PC based cards designed to communicate with the target programmable electronic device. "Tags" were assigned in the configuration databases, equating to addresses within the programmable electronic devices Citect was communicating with. The user would draw a representation of a facility using the readily available Dr Halo graphical package and placing "Animation Points" in the desired location. Citect for DOS consisted of a configuration database (in dBase format), a bitmap (256 colour raw format) and an animation file. Martin Roberts wrote Citect for DOS, released in 1987, as a response to the limited range of PC-based operator interface software available at the time.