Codesys Profiler ^{CODESYS Forge talk (Thread)}
Codesys Profiler
Last updated: 2019-11-27

Codesys Profiler ^{CODESYS Forge talk (Thread)}
Codesys Profiler
Last updated: 2019-11-14

Profiler Doesn't work? ^{CODESYS Forge talk (Thread)}
Profiler Doesn't work?
Last updated: 2022-08-13

temperature profiler ^{CODESYS Forge talk (Thread)}
temperature profiler
Last updated: 2010-08-13

Test manager and profiler ^{CODESYS Forge talk (Thread)}
Test manager and profiler
Last updated: 2019-11-29

Profiler memory usage, application memory exceed ^{CODESYS Forge talk (Thread)}
Profiler memory usage, application memory exceed
Last updated: 2020-07-24

codesys "profiler" object reference not set to an instance of an object ^{CODESYS Forge talk (Thread)}
codesys "profiler" object reference not set to an instance of an object
Last updated: 2023-01-11

Post by rcanfield on Code Coverage and Test Manager ^{CODESYS Forge talk (Post)}
I am exploring the possibility of measuring test coverage using the Test Manager and Profiler tools. It appears there are some significant limitations. Has anyone been successful trying to use these tools? Here are my observed limitations. Am I misunderstanding anything? * Profiler only works for one "run cycle". Even warm resets will clear the coverage calculations. Thus, all tests would have to manually reset values when complete to prevent contamination to other tests. * It is not possible to see which statements were/weren't executed. One would have to use the flow control tool which cannot be used in conjunction with the Profiler, and must be viewed in realtime. * The profiler control cannot be automated and therefore must be executed through a manual procedure. Thank you!
Last updated: 2024-07-11

Post by rcanfield on Code Coverage and Test Manager ^{CODESYS Forge talk (Post)}
I am exploring the possibility of measuring test coverage using the Test Manager and Profiler tools. It appears there are some significant limitations. Has anyone been successful trying to use these tools? Here are my observed limitations. Am I misunderstanding anything? * Profiler only works for one "run cycle". Even warm resets will clear the coverage calculations. Thus, all tests would have to manually reset values when complete to prevent contamination to other tests. * It is not possible to see which statements were/weren't executed. One would have to use the flow control tool which cannot be used in conjunction with the Profiler, and must be viewed in realtime. * The profiler control cannot be automated and therefore must be executed through a manual procedure. Thank you!
Last updated: 2024-07-11

Post by acc00 on Main Task cycle too long leading to PLC Fail ^{CODESYS Forge talk (Post)}
I have 2 Wago PFC200 PLC, running with Runtime SP19 Patch 5, with the Redundant application. The PLC communicates as Modbus Master with at this moment 15 Modbus Slaves -later there will be 28 in total- (Drives, Power management units,...). These devices are connected in 2 rings (1 ring of Drives, 1 ring of Power Management units), with 2 Managed Moxa Switches being part of the ring. Each PLC is connected to one of these switches. The issue I'm encountering is that the Cycle time of the Active PLC goes very high when I'm closing the Drive ring (simulating an issue on one Cabinet supply, resulting in that one Drive shut down, which can happen on field quite often). As a result of this long cycle, the PLC fails and goes to Exception, and the Passive PLC does not take control of the system. A normal cycle is around 30ms for the Main task, and a few ms for the Ethercat task. When I monitor with Profiler, I see that in this Maximum Cycle, the main Task is only taking 13ms, so I'm not sure where the PLC is hanging for so long. Is the remaining cycle time the Redundant management/sync or something else? Thank you in advance.
Last updated: 2024-03-08

Sort by relevance or date