What causes KUKA Robot alarm KRC0589?

Array parameter declared in the function definition but not initialized with actual data before the function is called. Array passed as callbyvalue (DECL INT my_array[10]) instead of callbyreference (DECL INT my_array[]) in the function signature. Function call attempts to pass a multi-dimensional array without proper bracket notation or dimension specification. Array variable name spelled differently between the calling code and the function parameter declaration causing mismatch. Function parameter list includes an array that exceeds the maximum size limits allowed by the KRC4 memory allocation.

How do I fix KUKA Robot alarm KRC0589?

1. Examine the function definition in the KRL program and verify the array parameter is declared using callbyreference syntax with empty brackets 2. Check that the array variable is declared and initialized with actual elements before the function call is executed 3. Verify the array variable name in the function call exactly matches the parameter name in the function definition, including correct spelling and case sensitivity 4. Review the array dimension declaration and confirm it does not exceed the KRC4 system memory limits for the data type being used 5. Use WorkVisual syntax highlighting to identify any red-underlined array references indicating undefined or improperly scoped variables 6. Recompile the complete KRL program and test the function call using single block mode on the KUKA smartPAD to verify the alarm no longer occurs

KUKA Robot codes

axismd.ai

KUKA Robot Controller

Parameter · Advanced

Alarm KRC0589

KUKA Robot KRC0589 - Array parameter inadmissible

An array parameter passed to a function is either undefined or declared as complete callbyvalue instead of using callbyreference. The KRC4 controller cannot process arrays that are passed by complete value or that have not been properly initialized before the function call.

KUKA RobotParameterAdvanced

KRC0589

KUKA Robot KRC0589 - Array parameter inadmissible

Array parameter inadmissible

Common Causes

Array parameter declared in the function definition but not initialized with actual data before the function is called
Array passed as callbyvalue (DECL INT my_array[10]) instead of callbyreference (DECL INT my_array[]) in the function signature
Function call attempts to pass a multi-dimensional array without proper bracket notation or dimension specification
Array variable name spelled differently between the calling code and the function parameter declaration causing mismatch
Function parameter list includes an array that exceeds the maximum size limits allowed by the KRC4 memory allocation

Troubleshooting Steps

1Examine the function definition in the KRL program and verify the array parameter is declared using callbyreference syntax with empty brackets
2Check that the array variable is declared and initialized with actual elements before the function call is executed
3Verify the array variable name in the function call exactly matches the parameter name in the function definition, including correct spelling and case sensitivity
4Review the array dimension declaration and confirm it does not exceed the KRC4 system memory limits for the data type being used
5Use WorkVisual syntax highlighting to identify any red-underlined array references indicating undefined or improperly scoped variables
6Recompile the complete KRL program and test the function call using single block mode on the KUKA smartPAD to 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.