FellowWithLaptop / TwinCAT_ExecutionPoint

In TwinCAT there are some functions available for debugging. The best known is probably the breakpoint. But this is used with caution, because it stops a running machine immediately. Therefore it is often avoided by programmers by using counters or flags to check the sequence of a control. In addition to the breakpoint, there is also the execution point, which does not stop the machine. I suspect that many are not aware of this feature and so I would like to share it briefly.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

TwinCAT_ExecutionPoint

In TwinCAT there are some functions available for debugging. The best known is probably the breakpoint. But this is used with caution, because it stops a running machine immediately. Therefore it is often avoided by programmers by using counters or flags to check the sequence of a control. In addition to the breakpoint, there is also the execution point, which does not stop the machine. I suspect that many are not aware of this feature and so I would like to share it briefly.

The breakpoint is normally added with the F9 key or via the context menu. The breakpoint is red and an arrow appears when the code is stopped.

alt text

The execution point is added via the Debug tab, New Breakpoint. alt text

In the dialog that opens, select the "Execution point settings" tab and click on the "Execution Point". With the "Activate breakpoint immediately" option, the execution point is activated automatically. alt text

Unlike the breakpoint, the execution point is green and the code is not stopped. alt text

Whether and how often the execution point has already been called, you can see in the Breakpoints window. You can find the window under the tab PLC->Windows->Breakpoints. alt text

alt text

In the Breakpoint Properties window you can find some other useful functions, which I will not go into here. If you are looking for the documentation of this function from Beckhoff you will find it here.

About

In TwinCAT there are some functions available for debugging. The best known is probably the breakpoint. But this is used with caution, because it stops a running machine immediately. Therefore it is often avoided by programmers by using counters or flags to check the sequence of a control. In addition to the breakpoint, there is also the execution point, which does not stop the machine. I suspect that many are not aware of this feature and so I would like to share it briefly.