What causes KUKA Robot alarm KRC0798?

Variable declared with wrong data type (e.g., REAL instead of POS). Passing a CHAR, INT, or BOOL variable where POS/FRAME/AXIS is required. Incorrect function call syntax with mismatched parameter types. Using an uninitialized or incorrectly structured variable in function arguments. Type mismatch between function definition and actual argument passed at runtime.

How do I fix KUKA Robot alarm KRC0798?

1. Review the KRL program line where alarm KRC0798 occurs and identify which function or instruction triggered it 2. Check the function/instruction documentation to verify the required parameter type (POS, FRAME, or AXIS) 3. Verify that all variables passed as arguments are declared with the correct data types matching function requirements 4. Declare variables using proper KUKA data types: AXIS, POS, FRAME, or use TYPE declarations for custom structures 5. Compare variable initialization and assignment to ensure type consistency throughout the program logic 6. Recompile the KRL program and test execution after correcting the data type mismatch

KUKA Robot codes

axismd.ai

KUKA Robot Controller

Servo/Axis · Basic

Alarm KRC0798

KUKA Robot KRC0798 - TYPE MUST BE “POS”,“FRAME”,“AXIS” 2134

This alarm indicates that an invalid data type was passed to a function or instruction that requires a specific parameter type. The function expects one of three valid types: POS (position), FRAME (coordinate frame), or AXIS (axis specification), but received a different data type instead.

KUKA RobotServo/AxisBasic

KRC0798

KUKA Robot KRC0798 - TYPE MUST BE “POS”,“FRAME”,“AXIS” 2134

TYPE MUST BE “POS”,“FRAME”,“AXIS” 2134

Common Causes

Variable declared with wrong data type (e.g., REAL instead of POS)
Passing a CHAR, INT, or BOOL variable where POS/FRAME/AXIS is required
Incorrect function call syntax with mismatched parameter types
Using an uninitialized or incorrectly structured variable in function arguments
Type mismatch between function definition and actual argument passed at runtime

Troubleshooting Steps

1Review the KRL program line where alarm KRC0798 occurs and identify which function or instruction triggered it
2Check the function/instruction documentation to verify the required parameter type (POS, FRAME, or AXIS)
3Verify that all variables passed as arguments are declared with the correct data types matching function requirements
4Declare variables using proper KUKA data types: AXIS, POS, FRAME, or use TYPE declarations for custom structures
5Compare variable initialization and assignment to ensure type consistency throughout the program logic
6Recompile the KRL program and test execution after correcting the data type mismatch

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.