What causes KUKA Robot alarm KRC0946?

Attempting to redeclare a constant with a different data type than the original declaration. Using the same constant name in multiple program sections with incompatible type definitions. Copying constant definitions from different program versions with conflicting type specifications. Mixing constant declarations across included files or libraries with incompatible type assignments. Syntax error in constant definition causing the compiler to interpret the type differently than intended.

How do I fix KUKA Robot alarm KRC0946?

1. Locate the constant declaration referenced in the alarm message and verify its initial data type definition 2. Search the entire KRL program for all instances where this constant name appears to identify conflicting redeclarations 3. Review the first constant definition and ensure all subsequent uses maintain the same data type throughout the program 4. Check included files, libraries, and global program sections for duplicate constant declarations with different types 5. Rename one of the conflicting constants to use a unique identifier if both declarations are necessary with different types 6. Recompile the KRL program after resolving the type mismatch to confirm the alarm is cleared

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0946

KUKA Robot KRC0946 - FIRST CONSTANT INCOMPATIBLE WITH THIS CONSTANT 2283

This alarm indicates a type incompatibility error in KRL program code where a constant declaration uses a data type that conflicts with a previously declared constant of the same name. The compiler detected that the first constant definition is incompatible with the redeclaration attempt, preventing program compilation and execution.

KUKA RobotSystemBasic

KRC0946

KUKA Robot KRC0946 - FIRST CONSTANT INCOMPATIBLE WITH THIS CONSTANT 2283

FIRST CONSTANT INCOMPATIBLE WITH THIS CONSTANT 2283

Common Causes

Attempting to redeclare a constant with a different data type than the original declaration
Using the same constant name in multiple program sections with incompatible type definitions
Copying constant definitions from different program versions with conflicting type specifications
Mixing constant declarations across included files or libraries with incompatible type assignments
Syntax error in constant definition causing the compiler to interpret the type differently than intended

Troubleshooting Steps

1Locate the constant declaration referenced in the alarm message and verify its initial data type definition
2Search the entire KRL program for all instances where this constant name appears to identify conflicting redeclarations
3Review the first constant definition and ensure all subsequent uses maintain the same data type throughout the program
4Check included files, libraries, and global program sections for duplicate constant declarations with different types
5Rename one of the conflicting constants to use a unique identifier if both declarations are necessary with different types
6Recompile the KRL program after resolving the type mismatch to confirm the alarm is cleared

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.