What causes KUKA Robot alarm KRC0755?

Attempting to pass a multi-dimensional character array where a one-dimensional CHAR[] is required. Using a STRING variable instead of CHAR[] array in a function or parameter declaration. Declaring a character array with incorrect dimensions (e.g., CHAR[5][10] instead of CHAR[50]). Passing a scalar CHAR variable to a function expecting CHAR[] array parameter. Type mismatch in array initialization or assignment operation involving character data.

How do I fix KUKA Robot alarm KRC0755?

1. Locate the exact line number referenced in the alarm message in your KRL source file 2. Verify the data type being used matches CHAR[] (one-dimensional character array) requirement 3. Check function or variable declarations to ensure dimensional consistency with caller expectations 4. If using STRING type, convert to CHAR[] array using appropriate string conversion functions 5. Review parameter passing at the flagged location and confirm argument types match function signature 6. Recompile the program after corrections and verify the alarm no longer occurs

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0755

KUKA Robot KRC0755 - ONE DIMENSIONAL CHAR FIELD EXPECTED 2091

This alarm occurs when the KRL compiler expects a one-dimensional character array (CHAR[]) but receives a different data type or dimensional structure at the specified location in the program. The @P1@ parameter indicates where in the source code the type mismatch was detected during compilation.

KUKA RobotSystemBasic

KRC0755

KUKA Robot KRC0755 - ONE DIMENSIONAL CHAR FIELD EXPECTED 2091

ONE DIMENSIONAL CHAR FIELD EXPECTED 2091

Common Causes

Attempting to pass a multi-dimensional character array where a one-dimensional CHAR[] is required
Using a STRING variable instead of CHAR[] array in a function or parameter declaration
Declaring a character array with incorrect dimensions (e.g., CHAR[5][10] instead of CHAR[50])
Passing a scalar CHAR variable to a function expecting CHAR[] array parameter
Type mismatch in array initialization or assignment operation involving character data

Troubleshooting Steps

1Locate the exact line number referenced in the alarm message in your KRL source file
2Verify the data type being used matches CHAR[] (one-dimensional character array) requirement
3Check function or variable declarations to ensure dimensional consistency with caller expectations
4If using STRING type, convert to CHAR[] array using appropriate string conversion functions
5Review parameter passing at the flagged location and confirm argument types match function signature
6Recompile the program after corrections and verify the alarm no longer occurs

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.