Dialog ‘New breakpoint’¶
Function: In the dialog, you define the settings for a new breakpoint or data breakpoint.
Call:
- Menu bar:
- Menu bar:
- Drop-down list:
New in the Breakpoints view
Requirement:
- The application is in online mode.
- In order to use data breakpoints, the device description file must include target entries that correspond to your controller.
Tasks | |
Only break if the breakpoint is hit in one of the following tasks: |
For example, you can define a single debug task and also prevent other tasks |
Hit Count | |
Break always | Break always: The program always halts at this breakpoint. |
Break when the hit count is equal to | The program halts at the breakpoint if the breakpoint has been reached as often as you have selected or specified here. |
Break when the hit count is a multiple of | |
Break when the hit count is greater than or equal to | |
Condition | |
Break, if true | ![]() TRUE . You can define a condition as a valid Boolean expression. Examples: x>100 , x[y]=z , a AND b , boolVar . |
Requirement: The command New data breakpoint was selected. | |
Interrupt execution if the value of the specified variable changes: | Variable for which the data breakpoint is set
|
Requirement: The command New breakpoint was selected. | |
Location |
|
Instances | In the case of function blocks, you must define whether the breakpoint should be set in the implementation or in an instance.
|
Execution point (execution does not stop at breakpoint) |
|
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 check box in . CODESYS can print variables with the placeholder {variable name} in the message text. |
Enable breakpoint immediately |
|
See also