What causes KUKA Robot alarm KRC0949?

Missing or incomplete object name after a declaration keyword (DEF, DECL, VAR, etc.). Typo or syntax error in the component name definition. Incorrect use of reserved keywords where a custom name is required. Missing or misplaced punctuation (colons, parentheses, brackets) around the expected name. Attempting to use an empty or whitespace-only identifier where a named component is required.

How do I fix KUKA Robot alarm KRC0949?

1. Review the KRL source code at the line number indicated in the error message 2. Verify that all function definitions (DEF), variable declarations (DECL, VAR), and module names have valid identifiers following the keyword 3. Check that component names follow KUKA naming conventions (alphanumeric characters and underscores, not starting with a number) 4. Ensure no reserved keywords are used as component names without proper context 5. Look for missing or extra whitespace, brackets, or parentheses around the expected name location 6. Compile the program again after corrections to confirm the error is resolved

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0949

KUKA Robot KRC0949 - COMPONENT NAME EXPECTED 2286

This alarm indicates that the KRL compiler expected a component name at a specific location in the source code but did not find one. The error typically occurs during program compilation when a required object identifier (module, function, or variable name) is missing or malformed in the syntax.

KUKA RobotSystemBasic

KRC0949

KUKA Robot KRC0949 - COMPONENT NAME EXPECTED 2286

COMPONENT NAME EXPECTED 2286

Common Causes

Missing or incomplete object name after a declaration keyword (DEF, DECL, VAR, etc.)
Typo or syntax error in the component name definition
Incorrect use of reserved keywords where a custom name is required
Missing or misplaced punctuation (colons, parentheses, brackets) around the expected name
Attempting to use an empty or whitespace-only identifier where a named component is required

Troubleshooting Steps

1Review the KRL source code at the line number indicated in the error message
2Verify that all function definitions (DEF), variable declarations (DECL, VAR), and module names have valid identifiers following the keyword
3Check that component names follow KUKA naming conventions (alphanumeric characters and underscores, not starting with a number)
4Ensure no reserved keywords are used as component names without proper context
5Look for missing or extra whitespace, brackets, or parentheses around the expected name location
6Compile the program again after corrections to confirm the error is resolved

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.