Page tree

This watchdog must be activated in the CODESYSControl.cfg configuration file.

The limit is defined in the CmpSchedule section.

Experience has shown that communication problems occur more often in the case of controllers under high loads.


  • Create a "Standard project" and select CODESYS Control Win V3 as the device.
  • Define the target system by means of the Network scan.



  • Edit the PLC_PRG POU as follows:


    Declaration

    VAR
        xToggle   : BOOL;
        xSwitch   : BOOL;
        udiCnt    : UDINT;
    END_VAR

    Implementation

    udiCnt := udiCnt + 1;
    IF xSwitch Then
        WHILE TRUE DO
            xToggle := NOT xToggle;
        END_WHILE
    END_IF

  • Start the project and set the xSwitch variable to TRUE.



    The following entries are located in the log:




With the introduction of multicore support (V3.5.SP13), the processor load is calculated as the average of all CPUs.
This also applies for the runtime license without multicore support.

Therefore, the following situation results in the case of an active infinite loop for an 8-core processor:


To trigger the watchdog, the limit has to be set to approximately 10% in the ini file.

[CmpSchedule]
ProcessorLoad.Maximum=10
  • No labels