dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference: User Interface dl-breadcrumb-item__separatorMenu Commands dl-breadcrumb-item__separatorView dl-breadcrumb-item__separatorCommands: Breakpoints
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Commands: Breakpoints dl-permalink__symbolPermalink

Symbol: _cds_icon_breakpoints.png

Function: The command opens the “Breakpoints” view.

Call: “View” menu

The view shows an overview of all defined breakpoints for an application. You have access to all breakpoint commands within the view.

Table 600: Table of current breakpoints

“Application”

Select the required application from the list.

“POU”

Name of the POU which will get the breakpoint

“Position”

Location of the breakpoint in the POU

  • Text editor: Line number and column number

  • Graphical editor: Network number or element number

"(Impl)" indicates that the breakpoint is located in the implementation of the function block, not in an instance.

“Instance Path”

Full object path of the breakpoint location

“Tasks”

Names of tasks which should become effective when the breakpoint is executed

If there are no restrictions, then "(all)" is displayed here.

“Condition”

  • “Break always”: No additional activation condition defined

    The breakpoint is always active.

  • Boolean expression

    The expression has to yield ‎TRUE‎ for the breakpoint to be active.

“Hit Count Condition”

Specifies when the breakpoint should become effective (depending on the hit count)

“Current Hit Count”

Specifies how often the breakpoint has already been reached up to now during the execution ("hit")

Table 601: Toolbar
_cds_icon_breakpoint_new.png

_cds_icon_breakpoint_activated.png “New Breakpoint”

The command opens the “Breakpoint Properties” dialog.

_cds_icon_data_breakpoint_activated.png “New Data Breakpoint”

The command opens the “Breakpoint Properties” dialog.

_cds_icon_breakpoint_delete.png

“Clear breakpoint”

Removes the breakpoint

Do not confuse this with disabling.

_cds_icon_breakpoint_activated_deactivate.png

“Enable/disable breakpoint”

Toggles the status of the breakpoint or execution point between "enabled" and "disabled"

  • _cds_icon_breakpoint_activated.png: The breakpoint is enabled.

  • _cds_icon_breakpoint_deactivated.png: The breakpoint is disabled.

  • _cds_icon_executionpoint_activated.png: The execution point is enabled.

  • _cds_icon_executionpoint_deactivated.png: The execution point 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_execution_point_enabled.png: The data execution point is enabled.

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

Different from “Clear Breakpoint”, a disabled breakpoint remains in the list and can be enabled again.

_cds_icon_breakpoint_properties.png

“Properties”

The “Breakpoint Properties” dialog opens for editing the breakpoint parameters. The dialog corresponds to the “New Breakpoint” dialog. In online mode, you can convert the breakpoint into an execution point.

_cds_icon_breakpoint_goto_source_position.png

“Go to source position”

Opens the online view of the relevant POU

The cursor is set at the breakpoint location.

cds_icon_breakpoint_delete_all_breakpoints.png

“Clear all breakpoints”

Deletes all breakpoints and execution points in the application

The list is cleared. Do not confuse this with disabling.

_cds_icon_breakpoint_activate_all.png

“Enable all breakpoints”

Enables all breakpoints and execution points which are currently disabled

_cds_icon_breakpoint_deactivate_all.png

“Disable all breakpoints”

Disables all breakpoints and execution points which are currently enabled

The points remain in the list and can be enabled again.

For more information, see: ⮫ “Using Breakpoints ”