FAQ: How to address Logic service cycle overflows?
In some cases, Logic Service may not respect the configured cycle time of the Logic application. When this happens consider the following:
- Check Windows Event Logs - System Event ID = 37: The speed of processor x in group y is being limited by system firmware. The processor has been in this reduced performance state for zzz seconds since the last report.
This message suggests CPU frequency is decreased for some reason. Make sure there are no BIOS/UEFI or Operating System settings causing this. Power saving settings are common the source of this event, that decrease CPU power in case computer is idle from human or process operation.
- Make sure you have a CPU that can handle the Logic application and other processes running simultaneously.
Consider to revise your Logic application so that the actual calculation time of the Logic Service is reduced:
- There are no long loops or other statements can block Logic Service calculation cycle.
- Reducing Logic project.
- Splitting the Logic project in multiple Logic applications.
- To clean the Project by looking and removing unused items.
- Change the compiling method from Debug to Release.
- Split the load of the application units across through different Logic cycles, by defining different periods and phases for the POUs.
We recommend to backup your project before implementing any change.
If you have any question for this FAQ please leave a feedback.
If you would like to know more about Historian please contact your local COPA-DATA Representative.