What causes KUKA Robot alarm KRC0691?

Function parameter count differs between external declaration and actual definition. Parameter data types mismatch between declaration and implementation. Return type mismatch for function declarations. External declaration uses different naming convention or spelling than actual object. Mixing of DECL and DEF declarations with incompatible signatures across program modules.

How do I fix KUKA Robot alarm KRC0691?

1. Locate the external declaration of @P1@ and verify the parameter list, data types, and return type match exactly 2. Check the actual function/subroutine definition in the .src or .sub file and compare signatures side-by-side 3. Ensure parameter order, names, and IN/OUT/INOUT modifiers are identical in both declaration and definition 4. Verify the data types of all parameters match precisely (e.g., REAL vs INT, CHAR vs STRING) 5. Remove and re-declare the external function to ensure no typos or formatting inconsistencies exist 6. Recompile the program in the KUKA IDE and check for any additional related compilation errors

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0691

KUKA Robot KRC0691 - EXTERNAL AND SR/FCT DECLARATIONS DO NOT MATCH 2027

This alarm indicates a mismatch between the external declaration and the SR/FCT (subroutine/function) declaration for object @P1@ in your KRL program. The function or subroutine signature defined externally does not match the actual implementation, causing a compilation or linking error.

KUKA RobotSystemBasic

KRC0691

KUKA Robot KRC0691 - EXTERNAL AND SR/FCT DECLARATIONS DO NOT MATCH 2027

EXTERNAL AND SR/FCT DECLARATIONS DO NOT MATCH 2027

Common Causes

Function parameter count differs between external declaration and actual definition
Parameter data types mismatch between declaration and implementation
Return type mismatch for function declarations
External declaration uses different naming convention or spelling than actual object
Mixing of DECL and DEF declarations with incompatible signatures across program modules

Troubleshooting Steps

1Locate the external declaration of @P1@ and verify the parameter list, data types, and return type match exactly
2Check the actual function/subroutine definition in the .src or .sub file and compare signatures side-by-side
3Ensure parameter order, names, and IN/OUT/INOUT modifiers are identical in both declaration and definition
4Verify the data types of all parameters match precisely (e.g., REAL vs INT, CHAR vs STRING)
5Remove and re-declare the external function to ensure no typos or formatting inconsistencies exist
6Recompile the program in the KUKA IDE and check for any additional related compilation errors

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.