Manual VIPA System 300S SPEED7 Chapter 4 Deployment CPU 313SC/DPM
HB140E - CPU SC - RE_313-6CF03 - Rev. 07/45 4-27
The CPU offers up to 4 breakpoints to be defined for program diagnosis.
Setting and deletion of breakpoints happens in your programming
environment. As soon as a breakpoint is reached, you may process your
program step by step and in- and outputs can be activated.
For the usage of breakpoints, the following preconditions have to be
fulfilled:
• Testing in single step mode is only possible with STL. If necessary
switch the view via View > STL to STL.
• The block must be opened online and must not be protected.
• The open block must not be altered in the editor.
• Activate View > Breakpoint Bar.
• Set the cursor to the command line where you want to insert a
breakpoint.
• Set the breakpoint with Debug > Set Breakpoint. The according
command line is marked with a circle.
• To activate the breakpoint click on Debug > Breakpoints Active. The
circle is changed to a filled circle.
• 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.
• 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.
• Delete (all) breakpoints with the option Debug > Delete All Breakpoints.
• The LED RUN blinks and the LED STOP is on.
• The execution of the code is stopped. No level is further executed.
• All times are frozen.
• The real-time clock runs on.
• The outputs are closed, but may be released for test purposes.
• Passive CP communication is possible.
Note!
The usage of breakpoints is always possible. Switching to the operating
mode test operation is not necessary.
With more than 3 breakpoints, a single step execution is not possible.
Operating mode
HOLD
Precondition
Approach for
working with
breakpoints
Behavior in
operating state
HOLD
To Next Page
Loading...
