Web-based Management 2:
Diagnostics → ESM statistics

Valid from firmware release 2026.0 LTS

On this WBM 2 page, users can check the utilization of running tasks in the ESM DATA tab, and occurring exceptions and their origin in the EXCEPTIONS tab.

Note: Access to the specific pages in the WBM 2 depends on user roles and their rights - see WBM 2: Accessibility for details.

ESM DATA tab

By default, all currently executed tasks are displayed in a bar graph, grouped by ESM core and in the order provided by the corresponding online variables.

↓ ESM DATA tab with default selection

Data selection filters

To adapt the bar graph for your needs, this section provides three filter options, and changed selections become visible at the bar graph:

  • which ESM(s) to be shown (visible and at the y-axis of the bar graph) 
  • choose the maximum or the minimum values of delay and execution time (visible at the top of the bar graph)
  • choose the linear or the logarithmic scaling of the time axis (visible athe x-axis, along with the scale unit) 

Usually the scale unit is µs, unless the task with the smallest delay and execution time surpasses 500 µs:
Then all time values will switch to ms, and the scale unit of the graph visible at the x-axis changes.

The default selection for this page is:

  • All selected 
  • Maximum
  • Linear

ESM statistics

All data in the bar graph will be updated periodically in a 1 s cycle.

Each two-color bar represents a single task, showing the crucial information at a glance. The color coding on the execution time section tells how close to the defined threshold it already has been during execution (hovering over the info icon icon in the WBM 2 page shows a short explanation): 

  •  Delay time 
  •  Execution time OK  
    The execution time section of the bar is green if the threshold has never been overrun, the counter is 0.
  •  Execution time close to watchdog  
    If the execution section of the bar has become orange, then the execution time threshold has been overrun once at minimum, the counter is larger than 0, the execution time is close to triggering a watchdog.
  •  Execution time + delay time > threshold: watchdog occurred   
    If the execution section of the bar has become red, then a watchdog has already occurred.
  • The configured watchdog time threshold is marked by a red vertical line | in each bar row. If it's invisible, then the scale of the bar graph is to small to show the number where the threshold would be. 
    Because the threshold line is a little longer than the height of a bar, even if already overrun you can detect to what extent the bar has exceeded the threshold.

Each bar is labeled with the delay time and, respectively, the execution time. The number in brackets at the execution section tells the task priority. If a number is invisible then the bar section is just too short; it will show up once the section grows longer.

On hovering over a bar end, a large tooltip shows all data for that task:

↓ Example of a task data tooltip

EXCEPTIONS

If exceptions have occurred, the table in this page shows them.

↓ Example of the Exceptions table

The table contains the following information:

  • Type
    • ARP Exception
    • STD Exception
    • Unknown Exception
    • Signal
    • Task Watchdog
  • Sub Type, which is the subtype of the exception (for example: ARP::System::Commons::ArgumentException)
  • ARP Sub Type, providing details for
    • ARP exception
    • PLC exception
    • PLC division by zero exception
    • PLC index out of range exception
    • PLC stack overflow exception
    • PLC string error exception
  • Task Name, which is the name of the task in which the exception occurred
  • Program Name, which is the name of the program instance in which the exception occurred
  • Information, which is additional information on the exception that occurred

 

 

• Published/reviewed: 2026-03-24  ☃  Revision 091 •