Lenze PLC Designer PLC Designer (R3-1) - Manual (Page 130)

L-force | PLC Designer
Concepts and Base Components
128 DMS 4.1 EN 03/2011 TD29

3.14 Debugging
To evaluate programming errors you can use the »PLC Designer« debugging
functionality in online mode. In this context regard the possibility to check an
application in simulation mode, i.e. without the need of connecting to a real hardware
target device.
Breakpoints can be set at certain positions to force an execution break. Certain
conditions, such as which tasks are concerned and in which cycles the breakpoint
should be effective, can be set for each breakpoint. Stepping functions are available to
get a program executed in controlled steps. At each break the current values of the
variables can be examined. A call stack can be viewed for the currently reached step
position.
Breakpoints
A breakpoint, set in an application program, will cause a break during the execution of
the program. The possible breakpoint positions depend on the editor. In each case
there is a breakpoint at the end of a POU.
A main facility is the Breakpoints dialog providing an overview on all breakpoints,
allowing adding, removing and modifying breakpoints.
New: Conditional breakpoints; the halt at a breakpoint can be made dependant on the
number of run through cycles or on which task is currently processed.
Symbols:
breakpoint enabled
breakpoint disabled
halt on breakpoint in online mode
Stepping
Stepping allows a controlled execution of an application program, e.g. for debugging
purposes. Basically you step from one instruction to the next one by repeated use of
the key , but also you can step over POUs which are called or ....
...New in contrast to »PLC Designer« V2.3:
• The next statement to be executed can be explicitly defined ('Set next statement').
• The next execution break can be defined simply by placing the cursor there ('Run to
cursor').
• 'Step Out' steps back to the previous caller.