Applies To:
  • CitectSCADA 5.xx, 6.XX
  • CitectHMI 5.xx, 6.XX

If an alarm log device is located on a remote machine and the machine is taken off the network, e.g. the network card is unplugged or the remote machine is turned off, Citect will lock up for about 30 seconds every time it tries to write data to the alarm logging device.

If Citect needs to open a network file on a computer that it cannot find, Citect will pause for the designated time determined by Windows. Windows will search for the remote machine across the network until it times out. This timeout is fairly large since a search is conducted over the network. During this timeout period Citect will lock up or pause and Trend Gaps may also appear.

This problem can be alleviated in V6.1 by assigning each processor to a separate Citect Server task i.e. Alarms Server to one Processor and Trend Server to another processor. In this case only the server running the alarms would lock up and hence related issues like trend gaps should disappear.

Citect has confirmed this to be a problem in Citect for Windows. We are researching this problem and will post new information here as it becomes available.

Citect Lock Up, Device