User Manual
Chapter 12
GFK-1742F
Jan 2020
Local Logic Language Syntax
301
Watchdog Timeout Warning / Error
Local Logic programs are constrained to complete execution within 300 microseconds in
the Logic Engine. This is to allow sufficient processing time in the module for Path
Generation and other tasks. Refer to Appendix E for a detailed listing of the execution times
for all valid Local Logic operations. The user can compute the execution time required for a
given program using the data tables supplied in Appendix E. The Logic Engine reports a
warning (Status Only) error code if the execution time takes more than 275 microseconds
but less than 300 microseconds. A Fast Stop error is generated if the program execution
time exceeds 300 microseconds. Refer to Table 63 for a list of the runtime warnings and
error codes.
Note:
Local Logic execution is halted if there are any Local Logic Fast Stop errors (see Table 61) and all
Digital Outputs, Control bits (Jog, Feedhold, Strobe Resets, Follower Enable) and CTL bits that are
under the control of Local Logic are disabled. Local Logic execution resumes from the start when
the user clears the error (via the error clear %Q bit).
12.8
Local Logic Error Messages
12.8.1
Local Logic Build Error Messages
The local logic program build process communicates the build status through the local
logic, editor error log window. In the event an error occurs, the build process reports the
error and attempts to continue the build process.
Error messages generated by the local logic build process fall into three categories; syntax
errors, parse errors, and parse warnings.
Parser error messages have several common elements.
Filename (Line): [Severity] [error message]
Filename is the filename of the current file being built.
Line is the line number in the file that the error was detected on.
Severity describes error severity. Errors prevent a binary creation. Warnings are
informational.
Error Message is a short, general description of the error