KRC0393

Common Causes

• ANALYSE or DEBUG commands invoked with file extension (e.g., analyse otto.src) instead of using module name without extension
• CALL or CALLPROG statements that include .src extension when the command expects only the module identifier
• LOAD or UNLOAD commands referencing files with extensions when the system expects project-relative module paths without extensions
• Custom program logic attempting to process module names containing extension suffixes in commands that strip or expect bare names
• Generated KRL code from external tools appending extensions to module references in contexts where they should be omitted

Troubleshooting Steps

1. 1Review the KRL command syntax in KUKA documentation and identify whether the specific command accepts or prohibits file extensions
2. 2Remove all file extensions from module references in problematic commands, using only the module name or identifier
3. 3Check for pattern consistency across the program to ensure all similar commands use the same naming convention without extensions
4. 4Use WorkVisual syntax validation and code completion features to automatically correct command syntax with proper module reference formatting
5. 5Search the entire KRL program for similar command patterns and apply the corrected syntax to all instances to prevent recurrence
6. 6Test the corrected program in offline mode by compiling in WorkVisual before uploading to the KRC4 controller to verify the alarm is resolved