Use Breakpoints With LD and FBD Languages
Breakpoints work the same way in both LD and FBD languages; in order to set a new breakpoint, move to the line where you want to halt the program execution, then choose Debug>Set/Remove breakpoint.On the header of the line, the gray raised button with the line number on it, will now apper a red circle, meaning that there’s a breakpoint on that line.
When a breakpoint is hit (which means that the code execution has reached the line where the breakpoint is set), the header is highlighted to indicate that the program is waiting to execute that instruction.Also the program execution state will change, in the far bottom-right corner, it will change from running to halted.
Note that, as shown with the textual languages, when a breakpoint is hit, the program execution is halted before that instruction took place.Selecting Debug>Run the program execution will be resumed until another breakpoint is hit, or the same breakpoint will be hit again after an entire cicle has took place.Selecting Debug>Run the line where the program execution has halted, will be executed, but the program will halt on the very next instruction. In other words, the result is the same as setting a new virtual breakpoint to the next instruction and then resume the execution.
When a breakpoint is hit (which means that the code execution has reached the line where the breakpoint is set), the header is highlighted to indicate that the program is waiting to execute that instruction.Also the program execution state will change, in the far bottom-right corner, it will change from running to halted.
Note that, as shown with the textual languages, when a breakpoint is hit, the program execution is halted before that instruction took place.Selecting Debug>Run the program execution will be resumed until another breakpoint is hit, or the same breakpoint will be hit again after an entire cicle has took place.Selecting Debug>Run the line where the program execution has halted, will be executed, but the program will halt on the very next instruction. In other words, the result is the same as setting a new virtual breakpoint to the next instruction and then resume the execution.