dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separatorTesting and Debugging dl-breadcrumb-item__separatorUsing Breakpoints
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Using Breakpoints dl-permalink__symbolPermalink

Breakpoints are commonly used for debugging programs. CODESYS supports breakpoints in all IEC editors.

You can set breakpoints at specific positions in the program to force an execution stop and to monitor variable values. You can set special "data breakpoints" to halt program execution when the value of a specific variable changes.

The halt at a breakpoint or data breakpoint can be linked to additional conditions. You can also redefine breakpoints and data breakpoints as "execution points" where specific code is executed instead of stopping the program.

The “Breakpoints” view provides an overview of all defined breakpoints. It also includes additional commands for processing batch changes to multiple breakpoints.

In the editor, the following symbols identify the status of a breakpoint or execution point:

  • _cds_icon_breakpoint_activated.png: The breakpoint is enabled.

  • _cds_icon_breakpoint_deactivated.png: The breakpoint is disabled.

  • _cds_icon_breakpoint_in_other_instance.png: The breakpoint is set in another instance of the POU open in the editor.

  • _cds_icon_breakpoint_halt.png: The program halts at the breakpoint.

  • _cds_icon_breakpoint_conditional_activated.png: The breakpoint with condition is enabled.

  • _cds_icon_breakpoint_conditional_deactivated.png: The breakpoint with condition is disabled.

  • _cds_icon_executionpoint_activated.png: The execution point is enabled.

  • _cds_icon_executionpoint_deactivated.png: The execution point is disabled.

  • _cds_icon_executionpoint_conditional_activated.png: The execution point with condition is enabled.

  • _cds_icon_executionpoint_conditional_deactivated.png: The execution point with condition is disabled.

  • _cds_icon_data_breakpoint_activated.png: The data breakpoint is enabled.

  • _cds_icon_data_breakpoint_disabled.png: The data breakpoint is disabled.

  • _cds_icon_data_breakpoint_halt.png: The program halts at the data breakpoint.

  • _cds_icon_data_execution_point_enabled.png: The data execution point is enabled.

  • _cds_icon_data_execution_point_disabled.png: The data execution point is disabled.

  • _cds_icon_data_executionpoint_halt.png: The program halts at the data execution point.

  • _cds_icon_data_executionpoint_cond_activated.png: The data execution point with condition is enabled.

  • _cds_icon_data_breakpoint_cond_activated.png: The data breakpoint with condition is enabled.

For more information, see: ⮫ “Commands: Breakpoints ”

  • Data breakpoints
  • Breakpoints in applications with multiple tasks
  • Setting a single breakpoint (example in ST editor)
  • Defining a breakpoint condition (example in ST editor)
  • Defining an execution point (example in ST editor)
  • Setting a data breakpoint