BREAKPOINTS Window

The BREAKPOINTS window, located in the Cross Function Area at the lower screen border, lists all set breakpoints and provides a toolbar and context menu for toggling, disabling and removing breakpoints as well as for jumping into a code worksheet, where a breakpoint is set.
If a breakpoint is reached when debugging in debug mode, the same stepping commands are provided (Step into code, Step over code, Step out of code) as in the CALL STACKS window.

You can hide/show the window by clicking the button shown left on the Cross Function Area toolbar.
For closing the window, you can also click the cross icon on the right of the window title bar:
How to pin/unpin the window in the Cross Function Area

You can open several windows in the Cross Function Area at the same time by pinning them. Only if pinned, a window remains visible when another window is opened. If a window is unpinned, it is closed when you open another window.

To pin/unpin a window, click the pin icon in the upper right window corner. Unpinned windows show horizontal pin icon , pinned windows show the icon .

How to undock/dock the window /

By clicking the 'Undock' icon in the window title bar, the window can be undocked from the user interface and placed anywhere on the screen (or on a second screen, if available).

To insert it at its original position, click the 'Dock' icon .

If the controller is connected and at least one new entry is added to the window while it is closed, the icon on the Cross Function Area toolbar is shown with an envelope icon.

Breakpoints are not supported for safety-related variables and code.

Further Info
For detailed information about the BREAKPOINTS window and how to work with it, see the topic "Debugging code: Breakpoints".

Toolbar

Toolbar button Context menu Description

, , , Debug commands which are also available in the CALL STACKS window. Refer to section "CALL STACKS/BREAKPOINTS window: debugging with set breakpoints" for details.

<Ctrl> + <Shift> + <F5> Command: Continue
Program execution is continued until the next set breakpoint is reached.
The command is also available in the CALL STACKS window.

<F11> Command: Step into the code
Program execution is continued at the next line or object and is then halted at this code position.
If a user FB call is reached, the POU code is opened in debug mode and stepped through.
(This behavior applies to user FBs included in the current project as well as in referenced user libraries.)
The command is also available in the CALL STACKS window.

<Ctrl> + <F11> Command: Step over the code
Program execution is continued at the next line or object and is then halted at this code position.
If a user FB call is reached, the call is stepped over and the next line or object is marked.
The command is also available in the CALL STACKS window.

<Shift> + <F11> Command: Step out of the code
This command is relevant while stepping through the code of a user FB POU. This command exits the FB code and returns to the calling POU.
The command is also available in the CALL STACKS window.

Enable Breakpoint Enables the breakpoint(s) selected in the window. The status switches to 'Active' in the window and the symbol in the code changes to
.

Enable All Breakpoints Enables all breakpoints in the window. The status switches to 'Active' in the window and the symbol in the code changes to
.

Disable Breakpoint Disables the breakpoint(s) selected in the window. The status switches to 'Inactive' in the window and the symbol in the code changes to
.

Disable All Breakpoints Disables all breakpoints in the window. The status switches to 'Inactive' in the window and the symbol in the code changes to
.

Remove Breakpoint Removes the breakpoint(s) selected in the window.

Remove All Breakpoints Removes all breakpoints in the window.

Go To Code Opens the code worksheet where the breakpoint is set and marks the breakpoint. If the worksheet is not yet in debug mode, the corresponding instance is opened automatically.

Toolbar button	Context menu	Description
, , ,		Debug commands which are also available in the CALL STACKS window. Refer to section "CALL STACKS/BREAKPOINTS window: debugging with set breakpoints" for details.
	<Ctrl> + <Shift> + <F5>	Command: Continue Program execution is continued until the next set breakpoint is reached. The command is also available in the CALL STACKS window.
	<F11>	Command: Step into the code Program execution is continued at the next line or object and is then halted at this code position. If a user FB call is reached, the POU code is opened in debug mode and stepped through. (This behavior applies to user FBs included in the current project as well as in referenced user libraries.) The command is also available in the CALL STACKS window.
	<Ctrl> + <F11>	Command: Step over the code Program execution is continued at the next line or object and is then halted at this code position. If a user FB call is reached, the call is stepped over and the next line or object is marked. The command is also available in the CALL STACKS window.
	<Shift> + <F11>	Command: Step out of the code This command is relevant while stepping through the code of a user FB POU. This command exits the FB code and returns to the calling POU. The command is also available in the CALL STACKS window.
	Enable Breakpoint	Enables the breakpoint(s) selected in the window. The status switches to 'Active' in the window and the symbol in the code changes to .
	Enable All Breakpoints	Enables all breakpoints in the window. The status switches to 'Active' in the window and the symbol in the code changes to .
	Disable Breakpoint	Disables the breakpoint(s) selected in the window. The status switches to 'Inactive' in the window and the symbol in the code changes to .
	Disable All Breakpoints	Disables all breakpoints in the window. The status switches to 'Inactive' in the window and the symbol in the code changes to .
	Remove Breakpoint	Removes the breakpoint(s) selected in the window.
	Remove All Breakpoints	Removes all breakpoints in the window.
	Go To Code	Opens the code worksheet where the breakpoint is set and marks the breakpoint. If the worksheet is not yet in debug mode, the corresponding instance is opened automatically.