OOhs! It seems as if the manual needs an update. Once upon a time there was a pause button, but we decided to remove it due to its limitations.
However, you can try to insert the “Stop” RAPID instruction in your program and see if that can be a workaround for you.
From the RAPID Reference manual: 'Stop is used to stop the program execution. Any movement performed at the time will be finished before the Stop instruction is ready.’
Thanks for your answer!
I couldnA’t make it work. If I insert the “Stop” instruction and then run the simulation until it stops and then saves the current state the simulation still starts from the beginning when I try to start from the new state.
When you have long simulations I think it would be to great help if you can pause and save different states. Otherwise you will have to run through the whole simulation when you want to check something at the end.
The possibility of saving different states is somewhat hampered by the missing pause-button.
Is the idea behind the ability to save states that you should only be able to save states from the start of simulations?
If you would like to start and stop the program execution without “destroy the program pointer”, you should start the rapid execution from the offline editor:
To stop the execution in a specific instruction, you can use a “break point”:
If you use Smart Components that require the simulation to be running, you must uncheck the robot system(s) from the simulation setup before you press simulation play. Otherwise you can’t control the system from the offline editor:
What I was looking for was a way to save a “state” with both the simulation status as well as keeping the program pointer at the right position. This would be good for debugging purposes. Is it possible to achive in any way?
For example, if you have a FOR-instruction with “i From 1 To 20” and you want to examine the behaviour at i=18, the ability to save a “complete” state at the end of “i=17” and running from there would be time saving when debugging.
