Applies To:
  • CitectSCADA 5.xx

Since daylight savings ended, my Events and Reports are running an hour earlier than scheduled and my device files are rolling over an hour early. Why, and how do I fix this?

Due to a windows 'design flaw' Citect's time Scheduling will be one hour out after a daylight saving time adjustment. This is because windows does not send a time change message when it does the adjustment as it correctly thinks that the underlying UTC has not changed. Since Citect does not get this message it does not change any of its time Scheduling meaning that reports, events, device rollovers and cicode timing will all be one hour out (which way depends on which changeover but for us going to daylight saving at the end of the month a 3:00am report will run at 4:00am and keep running at 4:00am). A simple method to get Citect back on correct scheduling would be to send the time change message to it. There is a command line application TimeChange.exe that will do this. This can be run anytime after the changeover to fix the problem. You can download TimeChange.exe from the Utilities area in the Citect Toolbox on our website

or contact your local support office for a copy.

If you discover this problem only after the changeover has occurred then you can run this to get Citect in correct schedule now without restarting. For customers who will be having a changeover at the end of the month I would advise using the NT scheduler to schedule TimeChange to run at say 3:00:00 am and 3:00:01am to make sure it gets done.

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