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

I have several reports configured and I report information from various PLCs that Citect is communicating with.  Sometimes these triggered reports do not get run.  When I tried using a button or keyboard command to execute one of these reports, the report ran okay.  What is the problem?

By default triggered reports will run providing there is no communication problem affecting the report trigger.  This is controlled by the [Report]ComBreak parameter.  By default mode 1 is used and the way this works is that all the report triggers are checked each report WatchTime.  Each report is executed when their time is due provided the trigger can be read and the result is true.  See [Report]Watchtime for more information.  If the trigger cannot be read then all subsequent triggered reports in the reports database will not run even if their trigger is on an IO device which is communicating.

CIT have confirmed this to be a problem in Citect for Windows versions 3.X to 5.X. We are researching this problem and will post new information here as it becomes available.