dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorCODESYS Development Systemdl-breadcrumb-item__separatorReference, User Interfacedl-breadcrumb-item__separatorDialogsdl-breadcrumb-item__separatorDialog 'New Breakpoint'
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Dialog 'New Breakpoint'dl-permalink__symbolPermalink

Function: In the dialog, you define the settings for a new breakpoint or data breakpoint. It is identical to the “Breakpoint Properties” dialog which is used in the “Breakpoints” view.

Call:

  • “Debug  New Breakpoint”

  • “Debug  New Data Breakpoint”

Requirement: The application is in online mode.

Tab 'Condition'

The dialog defines the requirements for which program processing should halt at a breakpoint.

NOTICE

NOTICE
NOTICE
NOTICE

NOTICE

NOTICE

Using conditional breakpoints slows down code execution, even when the condition does not yield ‎TRUE‎.

Conditional breakpoints required a CODESYS runtime >= V3.5.4.0.

Table 555: “Tasks”

“Break only when the breakpoint is hit in one of the following tasks”

_cds_icon_option_activated: CODESYS evaluates the breakpoint only if it is reached by specific tasks. The required tasks must be activated.

For example, you can define a single debug task and also prevent other tasks that use the same block from being affected when debugging.

Table 556: “Hit Count”

“Hit Count”

“Break always”: The program always halts at this breakpoint.

Alternative: The program halts at the breakpoint when the breakpoint has been hit as often as defined in the following (type in the required hit count or select it from the number list):

  • “Break when the hit count is equal to”

  • “Break when the hit count is a multiple of ”

  • “Break when the hit count is greater than or equal to”
Table 557: “Condition”

“Break, when true”

_cds_icon_option_activated: CODESYS evaluates the specified condition and halts the program at the breakpoint only when the result yields ‎TRUE‎. You can define a condition as a valid Boolean expression. Examples: ‎x>100‎, ‎x[y]=z‎, ‎a AND b‎, ‎boolVar‎.

Tab 'Data'

Requirement: This is used for the properties of a data breakpoint.

The function of data breakpoints depends on the target system. Currently, data breakpoints are possible only with the CODESYS Control Win V3.

On the tab, the variable or memory address is specified for which the data breakpoint is set or will be set.

“Break execution when the value of the variable or address changes”

  • Input of a qualified variable name

  • _cds_icon_input_assistent: Selection of a variable in the “Input Assistant” dialog, in the “Watch Variables” category

Examples: variable: ‎PLC_PRG.fb_DoSth.dwVariable‎; address: ‎16#12A‎, ‎0x12A‎, ‎129‎

“Size”

Number of bytes of the specified variable or memory address above which should be monitored for changes. When a new variable or memory address is specified, a value that matches the data type or memory is set automatically at first.

Note: The “Size” and quantity depend on the target system. For the CODESYS Control Win V3, a maximum of four data breakpoints with a maximum size of 8 bytes can be defined.

Example: ‎4‎ for data type ‎DWORD‎

Example: ‎2‎ for data type ‎DWORD‎: Only the two first bytes of the variable are monitored.

Tab 'Execution Point Settings'

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: The breakpoint becomes an execution point. Processing does not halt at this point and the given code is executed.

  • Execution point of a breakpoint: activated: _cds_icon_executionpoint_activated; deactivated: _cds_icon_executionpoint_deactivated

  • Execution point of a data breakpoint: activated: _cds_icon_data_execution_point_enabled; deactivated: _cds_icon_data_execution_point_disabled

“Execute the following code”

Code that 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 print variables with the placeholder {variable name} in the message text.

Tab 'Location'

Requirement: The command “New breakpoint” was selected.

“POU”

POU of the active application where the breakpoint is placed.

“Position”

Position of the breakpoint in the POU. Entry as row and column numbers (text editor) or as network or element numbers.

“Instances”

In the case of function blocks, you have to define whether the breakpoint should be set in the implementation or in an instance.

_cds_icon_option_activated CODESYS sets the breakpoint in the instance. For this option, select “Instance Path”.

_cds_icon_option_deactivated CODESYS sets the breakpoint in the implementation.

“Enable breakpoint immediately”

_cds_icon_option_activated: The breakpoint is activated.

_cds_icon_option_deactivated: The breakpoint is not activated. To activate later, click the _cds_icon_breakpoint_activated_deactivate button in the “Breakpoints” view.