Applies To:
  • CitectSCADA 7.0
  • CitectHMI 7.0


When running the CitectSCADA Cicode debugging feature the Debugger seams to take a long time to execute from previous versions used. It was noticed that the Cicode debug takes 3-10 seconds to step to the next instruction, even when simple instructions are executed, and the Stack window is refreshing very slowly as it takes seconds to refresh the values in the stack window after the debug stops on a break or the next step is reached when stepping thru the code.



It was noticed that the servers in question have a dual or quad core CPU and if Citect32.exe is running on CPU-1 while the development uses CPU-0 the debugger is extremely slow. When the CPU-0 was selected for Citect32.exe the Cicode debugger was reasonable fast.

This is currently being investigated and expected to be corrected in future releases.