Pre-Conditions to Set a Breakpoint.

No need for special compilationGF_ProjectVX code debugging tools operate at run-time. Thus, unlike other programming languages such as C++, the compiler does not need to be told whether or not to support break- points: given a PLC code, the compiler’s output is unique, and there is no distinction between debug and release version.Memory availabilityA breakpoint takes a segment in the application code sector, having a well-defined length. Obviously, in order to set a breakpoint, it is necessary that a sufficient amount of memory is available, otherwise an error message appears.Incompatibility with graphic trigger windowsA graphic trigger window takes the whole free space of the application code sector. There- fore, once such a debugging tool has been started, it is not possible to add any break- point, and an error message appears if you attempt to set one. Once the graphic trigger window is eventually closed, breakpoints are enabled again.Note that all the breakpoints existing before the starting of a graphic trigger window will keep working normally. You are simply not allowed to add new ones.