What causes KUKA Robot alarm KRC0852?

Passing a non-string variable or literal to a function that expects a STRING parameter. Attempting to assign a numeric, boolean, or other non-string type to a STRING variable. Incorrect parameter type in a function call or method invocation. Missing quotes around a string literal or using unquoted text where a string is required. Using an incompatible data type in string concatenation or string comparison operations.

How do I fix KUKA Robot alarm KRC0852?

1. Locate the line number and code section referenced in the error message where the STRING type is expected 2. Review the function or operation definition to confirm the required parameter data type is STRING 3. Verify that all variables being passed as arguments are declared and initialized as STRING type 4. Check for missing quotation marks around string literals and ensure proper string formatting 5. Convert non-string variables to STRING type using appropriate conversion functions if needed 6. Recompile the KRL program and verify the syntax correction resolves the alarm

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0852

KUKA Robot KRC0852 - STRING EXPECTED 2188

This alarm indicates a type mismatch error where a STRING data type was expected but a different data type was provided in the KRL program. The error occurs during program parsing or execution when an argument, assignment, or operation requires a string value at the specified location.

KUKA RobotSystemBasic

KRC0852

KUKA Robot KRC0852 - STRING EXPECTED 2188

STRING EXPECTED 2188

Common Causes

Passing a non-string variable or literal to a function that expects a STRING parameter
Attempting to assign a numeric, boolean, or other non-string type to a STRING variable
Incorrect parameter type in a function call or method invocation
Missing quotes around a string literal or using unquoted text where a string is required
Using an incompatible data type in string concatenation or string comparison operations

Troubleshooting Steps

1Locate the line number and code section referenced in the error message where the STRING type is expected
2Review the function or operation definition to confirm the required parameter data type is STRING
3Verify that all variables being passed as arguments are declared and initialized as STRING type
4Check for missing quotation marks around string literals and ensure proper string formatting
5Convert non-string variables to STRING type using appropriate conversion functions if needed
6Recompile the KRL program and verify the syntax correction resolves the alarm

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.