dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorCODESYS Development Systemdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference, User Interfacedl-breadcrumb-item__separatorMenu Commandsdl-breadcrumb-item__separatorMenu 'View'dl-breadcrumb-item__separatorCommand 'Breakpoints'
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Command 'Breakpoints'dl-permalink__symbolPermalink

Symbol: _cds_icon_breakpoints

Function: This command opens the “Breakpoints” view.

Call: Menu bar: “View”.

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

Table 504: Table of current breakpoints

“Application”

Select the required application from the list.

“POU”

Name of the function block that will receive the breakpoint

“Location”

Location of the breakpoint in the POU

  • Text editor: Line number and column number

  • Graphical editor: Network number or element number

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

“Instance Path”

Complete object path of the breakpoint location.

“Tasks”

Names of tasks that will be effective when the breakpoint is executed. If there are no restrictions, then "(all)" is displayed here.

“Condition”

  • “Break always”: No additional enable condition defined; the breakpoint is always enabled.

  • Boolean expression. The expression must yield ‎TRUE‎ for the breakpoint to be enabled.

“Hit Count Condition”

When the breakpoint should be in effect (depending on the hit count)

“Current Hit Count”

How often the breakpoint has already been reached up to now during the execution
Table 505: Toolbar
_cds_icon_breakpoint_new

_cds_icon_breakpoint_activated“New Breakpoint”

This command opens the “Breakpoint Properties” dialog.

_cds_icon_data_breakpoint_activated“New Data Breakpoint”

This command opens the “New Breakpoint” dialog.
_cds_icon_breakpoint_delete

“Clear Breakpoint”

Removes the breakpoint (not the same as disable)
_cds_icon_breakpoint_activated_deactivate

“Enable/Disable Breakpoint”

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

  • _cds_icon_breakpoint_activated Breakpoint enabled

  • _cds_icon_breakpoint_deactivated Breakpoint disabled

  • _cds_icon_executionpoint_activated Execution point enabled

  • _cds_icon_executionpoint_deactivated Execution point disabled

  • _cds_icon_data_breakpoint_activated Data breakpoint enabled

  • _cds_icon_data_breakpoint_disabled Data breakpoint disabled

  • _cds_icon_data_execution_point_enabled Data execution point enabled

  • _cds_icon_data_execution_point_disabled Data execution point disabled

As opposed to "Clear breakpoint", a disabled breakpoint remains in the list and can be enabled again.
_cds_icon_breakpoint_properties

“Properties”

The “Breakpoint Properties” dialog opens for editing the breakpoint parameters. This dialog is the same as “New Breakpoint”. In online mode, you can change the breakpoint into an execution point.
_cds_icon_breakpoint_goto_source_position

“Go to Source Position”

Opens the online view of the affected block. The cursor is set at the breakpoint location.
cds_icon_breakpoint_delete_all_breakpoints

“Clear All Breakpoints”

Deletes all breakpoints and execution points in the application. The list is cleared. Not to be confused with "deactivate".
_cds_icon_breakpoint_activate_all

“Enable All Breakpoints”

Enables all currently disabled breakpoints and execution points.
_cds_icon_breakpoint_deactivate_all

“Disable All Breakpoints”

Disables all currently enabled breakpoints and execution points. The points remain in the list and can be enabled again.