What causes KUKA Robot alarm KRC0789?

Variable name is used in the program but not declared in the DECL section of the data list. Typo or spelling mismatch between variable declaration and usage. Variable declared in wrong scope or in a different module without proper import. Missing DECL statement for global or local variables. Incorrect variable syntax or naming convention that violates KRL rules.

How do I fix KUKA Robot alarm KRC0789?

1. Identify the variable name @P1@ mentioned in the alarm message from the error log 2. Open the KRL program source file and search for all instances where @P1@ is used 3. Verify that @P1@ is declared in the DECL section at the beginning of the program or relevant module 4. Check for spelling mistakes between the variable declaration and its usage throughout the code 5. If the variable is used across multiple modules, ensure it is properly exported/imported or declared as global 6. Recompile the program after correcting the declaration, and verify the alarm clears

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0789

KUKA Robot KRC0789 - VARIABLE NOT DECLARED IN DATA LIST 2125

This alarm indicates that a variable referenced in the KRL program has not been properly declared in the data list (DATLIST) section. The compiler cannot find the declaration for the object @P1@, preventing successful program compilation or execution.

KUKA RobotSystemBasic

KRC0789

KUKA Robot KRC0789 - VARIABLE NOT DECLARED IN DATA LIST 2125

VARIABLE NOT DECLARED IN DATA LIST 2125

Common Causes

Variable name is used in the program but not declared in the DECL section of the data list
Typo or spelling mismatch between variable declaration and usage
Variable declared in wrong scope or in a different module without proper import
Missing DECL statement for global or local variables
Incorrect variable syntax or naming convention that violates KRL rules

Troubleshooting Steps

1Identify the variable name @P1@ mentioned in the alarm message from the error log
2Open the KRL program source file and search for all instances where @P1@ is used
3Verify that @P1@ is declared in the DECL section at the beginning of the program or relevant module
4Check for spelling mistakes between the variable declaration and its usage throughout the code
5If the variable is used across multiple modules, ensure it is properly exported/imported or declared as global
6Recompile the program after correcting the declaration, and verify the alarm clears

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.