What causes KUKA Robot alarm KRC0950?

Variable declared twice in the same function or program section. Function or subroutine defined multiple times with identical name. Module or component included/imported more than once causing duplicate symbols. Copy-paste error resulting in duplicate object declarations. Incorrect use of GLOBAL or PUBLIC declarations creating namespace conflicts.

How do I fix KUKA Robot alarm KRC0950?

1. Review the KRL source file and locate all instances of the object name mentioned in 2. Identify which declarations or definitions are duplicates and determine which one should be retained 3. Remove or rename the duplicate declaration, ensuring only one definition exists per scope 4. Check for accidental includes or imports of the same file/module multiple times in your program 5. Verify namespace scope (local, GLOBAL, PUBLIC) to ensure objects don't conflict across modules 6. Recompile the KRL program and verify the alarm no longer appears in the diagnostics

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0950

KUKA Robot KRC0950 - COMPONENT SPECIFIED TWICE 2287

This alarm indicates that a KRL program object (variable, function, or module) has been declared or defined more than once within the same scope or compilation unit. The compiler detected a duplicate declaration of <object name> which violates KRL's unique naming requirements within a scope. This prevents ambiguity in program execution and ensures proper code compilation.

KUKA RobotSystemBasic

KRC0950

KUKA Robot KRC0950 - COMPONENT SPECIFIED TWICE 2287

COMPONENT SPECIFIED TWICE 2287

Common Causes

Variable declared twice in the same function or program section
Function or subroutine defined multiple times with identical name
Module or component included/imported more than once causing duplicate symbols
Copy-paste error resulting in duplicate object declarations
Incorrect use of GLOBAL or PUBLIC declarations creating namespace conflicts

Troubleshooting Steps

1Review the KRL source file and locate all instances of the object name mentioned in <object name>
2Identify which declarations or definitions are duplicates and determine which one should be retained
3Remove or rename the duplicate declaration, ensuring only one definition exists per scope
4Check for accidental includes or imports of the same file/module multiple times in your program
5Verify namespace scope (local, GLOBAL, PUBLIC) to ensure objects don't conflict across modules
6Recompile the KRL program and verify the alarm no longer appears in the diagnostics

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.