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__separatorDialogs dl-breadcrumb-item__separatorDialog: New Breakpoint dl-breadcrumb-item__separatorTab: Execution Point Settings
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Tab: Execution Point Settings dl-permalink__symbolPermalink

Here, an existing breakpoint or data breakpoint can be converted into an execution point.

“Execution point (execution does not stop at breakpoint)”

_cds_icon_option_activated_copy.png: The breakpoint becomes an execution point. Processing does not halt at this point and the given code is executed.

  • Execution point of a breakpoint: _cds_icon_executionpoint_activated.png enabled, _cds_icon_executionpoint_deactivated.png disabled

  • Execution point of a data breakpoint: _cds_icon_data_execution_point_enabled.png enabled, _cds_icon_data_execution_point_disabled.png disabled

“Execute the following code”

Code which is executed when the execution point is reached

Looping structures (For, While) and IF or CASE expressions are not possible.

“Print a message in the device log”

This option is available only when you select the “Enable logging in breakpoints” option in “Project Settings  Compile options”.

CODESYS can output variables with the ‎{variable name}‎ placeholder in the message text.