KRL (KUKA Robot Language) is a proprietary, Pascal-like industrial programming language. Because the KUKA parser handles source code differently than standard PC languages, using a code formatter requires understanding specific constraints to maintain syntax compliance while achieving clean, readable code.
When formatting KUKA KRL code, you must keep in mind three critical technical constraints:
Single-Line Limits: KRL does not support line breaks within function calls, logic assignments, or inline forms.
No VOID Type: Subroutines cannot return a VOID type; they must be clearly defined as DEF for subroutines or DEFFCT for functions with specific return types.
Semicolon Comments: Every comment line must begin with a semicolon ;.
If you are just getting started with writing, editing, and formatting KRL scripts, here is how you can use a source code formatter and structure your code effectively. 1. The Right Tools for Formatting & Editing
You typically write KRL files with the .src (source code) and .dat (data) extensions. Formatting is usually done offline in dedicated IDEs to prevent breaking the KUKA parser on the physical controller: Basic Program that moves robot in a rectangle – UT Wikis
Leave a Reply