Using parameters on a network

If using CitectSCADA on a network, you can use parameters globally, locally (local to each server and clientA computer that accesses shared network resources provided by another computer called a server. 's client-server based architecture is designed to distribute the processing tasks and optimize performance.), or both globally and locally. Any parameter set in the project database applies to every client unless the parameter is also set in the citect.ini of a Control Client. The value set in the local citect.ini fileA text file that stores information about how each computer (servers and control clients) operates in the configuration and runtime environments. The Citect.INI file stores parameters specific to each computer and therefore cannot be configured as part of the project. takes precedence over the project database for that client only. For example:

Here, a parameter (Parameter x) is set to a value n in the project database (on the file serverA computer with a large data storage capacity dedicated to file storage and accessed by other client computers via a network. On larger networks, the file server runs a special network operating system. On smaller installations, the file server may run a PC operating system supplemented by peer-to-peer networking software.). When the system is running, this value (n) applies to the alarms server and both clients. The same parameter is set to different values for both the I/O ServerA dedicated communications server that exchanges data between I/O devices and control clients. No data processing is performed by the I/O server (except for its local display). Data is collected and passed to the control clients for display, or to another server for further processing. All data sent to an I/O device from any computer is also channelled through the I/O server. If data traffic is heavy, you can use several I/O servers to balance the load. and the trends server (set locally in the respective citect.ini files). When the system is running, the I/O Server uses the value p for the parameter, and the trends server uses the value m.