Table of Contents
Advertisement
VIPA System SLIO
Operating mode HOLD
Precondition
Approach for working with
breakpoints
Behavior in operating
state HOLD
HB300 | CPU | 013-CCF0R00 | en | 19-30
The CPU offers up to 3 breakpoints to be defined for program diagnosis. Setting and
deletion of breakpoints happens in your programming environment. As soon as a break-
point is reached, you may process your program step by step.
For the usage of breakpoints, the following preconditions have to be fulfilled:
Testing in single step mode is possible with STL. If necessary switch the view via
n
'View è STL' to STL.
n
The block must be opened online and must not be protected.
1.
Activate 'View è Breakpoint Bar'.
2.
Set the cursor to the command line where you want to insert a breakpoint.
3.
Set the breakpoint with 'Debug è Set Breakpoint'.
ð The according command line is marked with a circle.
4.
To activate the breakpoint click on 'Debug è Breakpoints Active'.
ð The circle is changed to a filled circle.
5.
Bring your CPU into RUN.
ð When the program reaches the breakpoint, your CPU switches to the state
HOLD, the breakpoint is marked with an arrow and the register contents are
monitored.
6.
Now you may execute the program code step by step via 'Debug
è Execute Next Statement' or run the program until the next breakpoint via 'Debug
è Resume'.
7.
Delete (all) breakpoints with the option 'Debug è Delete All Breakpoints'.
n
The RUN-LED blinks and the STOP-LED is on.
n
The execution of the code is stopped. No level is further executed.
n
All times are frozen.
n
The real-time clock runs is just running.
n
The outputs were disabled (BASP is activated).
n
Configured CP connections remain exist.
The usage of breakpoints is always possible. Switching to the operating
mode test operation is not necessary.
With more than 2 breakpoints, a single step execution is not possible.
Deployment CPU 013-CCF0R00
Operating modes > Overview
103
Advertisement
Table of Contents
