What causes KUKA Robot alarm KRC0928?

Variable or expression declared with incorrect data type instead of MODUS_T. Type mismatch in function parameter passing where MODUS_T is expected. Attempting to assign a non-MODUS_T value to a MODUS_T variable. Incorrect structure initialization or casting of mode-related data. Using wrong variable name or referencing undefined MODUS_T object in expression.

How do I fix KUKA Robot alarm KRC0928?

1. Review the KRL source code at the line indicated by the alarm to identify the problematic expression 2. Verify that all variables used in the expression are declared with the correct MODUS_T data type 3. Check function signatures and ensure parameters match expected MODUS_T types 4. Confirm that any type conversions or assignments involving mode data are explicitly cast to MODUS_T 5. Cross-reference variable definitions in included files or libraries to ensure consistent typing 6. Recompile the program after corrections and verify the alarm code no longer appears

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0928

KUKA Robot KRC0928 - EXPRESSION TYPE NOT “MODUS_T” 2265

This alarm indicates that an expression used in the KRL program does not have the required MODUS_T (mode structure) type. The compiler expected a MODUS_T data type but encountered a different type instead, preventing proper program compilation or execution.

KUKA RobotSystemBasic

KRC0928

KUKA Robot KRC0928 - EXPRESSION TYPE NOT “MODUS_T” 2265

EXPRESSION TYPE NOT “MODUS_T” 2265

Common Causes

Variable or expression declared with incorrect data type instead of MODUS_T
Type mismatch in function parameter passing where MODUS_T is expected
Attempting to assign a non-MODUS_T value to a MODUS_T variable
Incorrect structure initialization or casting of mode-related data
Using wrong variable name or referencing undefined MODUS_T object in expression

Troubleshooting Steps

1Review the KRL source code at the line indicated by the alarm to identify the problematic expression
2Verify that all variables used in the expression are declared with the correct MODUS_T data type
3Check function signatures and ensure parameters match expected MODUS_T types
4Confirm that any type conversions or assignments involving mode data are explicitly cast to MODUS_T
5Cross-reference variable definitions in included files or libraries to ensure consistent typing
6Recompile the program after corrections and verify the alarm code no longer appears

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.