Applies To:
  • CitectSCADA 3.xx, 4.xx, 5.00

I have been running Citect for a while and the clock has stopped updating. However, the Windows clock is fine. What has happened? 

Currently there is a problem with Citect where its internal second clock may stop counting after running for 50 days. This is due to the rollover of the Windows tick counter. Citect will still work as the millisecond counter is unaffected so Kernel scheduling will still continue. However anything relying on the second counter, like alarms and trends, will show whatever time the second counter stopped at.

CIT has confirmed this to be a problem in Citect for Windows versions 3.XX to 5.00. This problem has been fixed in versions 3.40/4.20 Service Pack H and 5.01.