What causes KUKA Robot alarm KRC0980?

Attempting to create a file with a period in the filename (e.g., 'program.test.src'). Copying or importing a file from an external source that contains periods in its name. Manually editing project files or configuration that inadvertently introduces periods in object names. Using legacy or improperly formatted filenames when migrating programs between systems. Incorrect naming convention applied to subroutines, functions, or module definitions within KRL code.

How do I fix KUKA Robot alarm KRC0980?

1. Identify the problematic filename or object name that triggered alarm 2317 2. Remove all period (.) characters from the filename, replacing them with underscores (_) or other allowed characters if needed 3. Rename the affected KRL file or object to comply with KUKA naming conventions (alphanumeric and underscore characters only) 4. Update any references to the renamed object throughout the program and project structure 5. Reload or recompile the affected KRL program to ensure the new naming is recognized by the system 6. Verify the alarm clears and the program executes without the KRC0980 error

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0980

KUKA Robot KRC0980 - FILE NAME MAY NOT CONTAIN “.” 2317

This alarm occurs when attempting to create or reference a KRL program object (module, function, or variable) with a filename containing a period (dot) character. The KUKA KRC system does not permit periods in object names as they are reserved for internal syntax purposes.

KUKA RobotSystemBasic

KRC0980

KUKA Robot KRC0980 - FILE NAME MAY NOT CONTAIN “.” 2317

FILE NAME MAY NOT CONTAIN “.” 2317

Common Causes

Attempting to create a file with a period in the filename (e.g., 'program.test.src')
Copying or importing a file from an external source that contains periods in its name
Manually editing project files or configuration that inadvertently introduces periods in object names
Using legacy or improperly formatted filenames when migrating programs between systems
Incorrect naming convention applied to subroutines, functions, or module definitions within KRL code

Troubleshooting Steps

1Identify the problematic filename or object name that triggered alarm 2317
2Remove all period (.) characters from the filename, replacing them with underscores (_) or other allowed characters if needed
3Rename the affected KRL file or object to comply with KUKA naming conventions (alphanumeric and underscore characters only)
4Update any references to the renamed object throughout the program and project structure
5Reload or recompile the affected KRL program to ensure the new naming is recognized by the system
6Verify the alarm clears and the program executes without the KRC0980 error

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.