What causes KUKA Robot alarm KRC0391?

External files created by non-KUKA tools or third-party software lacking proper KRL module headers and metadata. Corrupted file data transmitted during network transfer resulting in invalid or incomplete module information headers. KUKA system version mismatch between source and destination, causing incompatible module format or descriptor structures. Module files with incorrect encoding or character set that causes parsing failure in the KRC4 file evaluation process. Custom or legacy KRL code with non-standard comments or formatting that interferes with module information extraction.

How do I fix KUKA Robot alarm KRC0391?

1. Verify the source file is a valid KUKA KRL module by opening it in WorkVisual and confirming proper syntax highlighting and structure 2. Confirm the file was created or last modified within the same KUKA system version as the target KRC4 controller 3. Re-transfer the file using a reliable connection method, such as WorkVisual direct upload or KUKA smartPAD file manager to prevent data corruption 4. Check the file encoding in WorkVisual (typically UTF-8 or system default) and ensure it matches the KRC4 system locale settings 5. Create a new module in WorkVisual and manually copy the program logic to establish proper metadata and descriptor structure 6. Contact KUKA support if the issue persists and provide the problematic module file for analysis of non-standard format characteristics

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0391

KUKA Robot KRC0391 - FILE DESCRIPTION CANNOT BE PROCESSED

This alarm indicates that module metadata or file descriptors received during a COPY operation from an external source cannot be properly parsed or evaluated by the KRC4 controller. The file information structure does not conform to expected KRL module format specifications, preventing successful integration into the system.

KUKA RobotSystemBasic

KRC0391

KUKA Robot KRC0391 - FILE DESCRIPTION CANNOT BE PROCESSED

FILE DESCRIPTION CANNOT BE PROCESSED

Common Causes

External files created by non-KUKA tools or third-party software lacking proper KRL module headers and metadata
Corrupted file data transmitted during network transfer resulting in invalid or incomplete module information headers
KUKA system version mismatch between source and destination, causing incompatible module format or descriptor structures
Module files with incorrect encoding or character set that causes parsing failure in the KRC4 file evaluation process
Custom or legacy KRL code with non-standard comments or formatting that interferes with module information extraction

Troubleshooting Steps

1Verify the source file is a valid KUKA KRL module by opening it in WorkVisual and confirming proper syntax highlighting and structure
2Confirm the file was created or last modified within the same KUKA system version as the target KRC4 controller
3Re-transfer the file using a reliable connection method, such as WorkVisual direct upload or KUKA smartPAD file manager to prevent data corruption
4Check the file encoding in WorkVisual (typically UTF-8 or system default) and ensure it matches the KRC4 system locale settings
5Create a new module in WorkVisual and manually copy the program logic to establish proper metadata and descriptor structure
6Contact KUKA support if the issue persists and provide the problematic module file for analysis of non-standard format characteristics

Seeing Multiple Alarms?

Seeing another alarm with this one? Enter the code.

Get machine-aware diagnosis

AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.

Start free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.