Testing with breakpoints
With this test option, you set breakpoints in your program, establish an online connection,
and enable the breakpoints on the CPU. You then execute a program from one breakpoint to
another.
Requirements:
● Setting breakpoints is possible in the programming language SCL or STL.
Testing with breakpoints provides you with the following advantages:
● Localization of logic errors step by step
● Simple and quick analysis of complex programs prior to actual commissioning
● Recording of current values within individual executed loops
● Use of breakpoints for program validation also possible in SCL/STL networks within
LAD/FBD blocks
Note
Restriction during testing with breakpoints
• When you test with breakpoints, there is a risk of overwriting the cycle time of the CPU.
• If you are using technology objects and test them with breakpoints, the CPU switches to
STOP.
Note
F-System SIMATIC Safety
Setting breakpoints in the standard user program results in errors in the
security program:
• Sequence of F cycle time monitoring
• Error in communication with the fail-safe I/O
• Error during safety-oriented CPU-CPU communication
• internal CPU error
If you still wish to use breakpoints for testing, you must deactivate
the safety mode beforehand. This will result in the following errors:
• Error in communication with the fail-safe I/O
• Error during safety-oriented CPU-CPU communication
SIMATIC Drive Controller
System Manual, 11/2019, A5E46600094-AA
Test and service functions
14.1 Test functions
261