Notes and Information

Observe the following instructions when using the Profiler.

Notice

Changed time behavior of the PLC program and potential watchdog exceptions when using the Profiler functionalities

The Profiler measurements change (slow down) the runtime behavior of the PLC program. The effects depend on the PLC program architecture and the profiler configuration.
Watchdog exceptions can occur due to the changed behavior.

  • You should only use the profiler functions in a secure test environment.
Notes and Information 1:

Change Profiler settings via download

Switching the profiling function on and off and changing the Profiler configuration will force a download. It is not possible to load these changes to the controller using Online Change.

Notes and Information 2:

Libraries

By default, only calls to the application code of the current PLC project are recorded. Library function blocks can be added via the library whitelist in the profiler configuration (see Window Configuration).

  • Add library function blocks to the library whitelist via the Input Assistant or by drag and drop from the Library Manager.
  • Alternatively, you can encapsulate calls from libraries within the application code into actions and record those actions.
Notes and Information 3:

Function blocks for implicit checks

Simultaneous use of the PLC Profiler and function blocks for implicit checks (e.g. bound checks, pointer checks, see also Object POUs for implicit checks) can lead to distorted measurement results. The implicit checks generate additional runtime overhead, which is included in the measured values. For meaningful profiling results, it is recommended to deactivate function blocks for implicit checks during the measurement.