What causes KUKA Robot alarm KRC0677?

Subroutine source file is missing or deleted from the project directory. Incorrect subroutine name or reference in the calling program. Source file corruption or syntax errors preventing proper compilation. File path or library reference is broken or pointing to wrong location. Version mismatch between subroutine declaration and implementation.

How do I fix KUKA Robot alarm KRC0677?

1. Verify that the subroutine source file exists in the correct project directory and has not been deleted 2. Check the subroutine call syntax and confirm the name matches exactly with the source file definition 3. Review the source file for syntax errors by opening it in the KUKA IDE and attempting recompilation 4. Verify all library paths and file references are correct and point to valid locations 5. Delete all generated object files and perform a clean full rebuild of the entire project 6. If using external libraries or modules, ensure they are properly registered and accessible to the linking process

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0677

KUKA Robot KRC0677 - SUB CANNOT BE LINKED TO SRC 2013

This alarm occurs during program compilation when a subroutine cannot be successfully linked to its source file or object reference. The linker failed to resolve the subroutine dependency, typically due to missing, incompatible, or incorrectly referenced program modules.

KUKA RobotSystemBasic

KRC0677

KUKA Robot KRC0677 - SUB CANNOT BE LINKED TO SRC 2013

SUB CANNOT BE LINKED TO SRC 2013

Common Causes

Subroutine source file is missing or deleted from the project directory
Incorrect subroutine name or reference in the calling program
Source file corruption or syntax errors preventing proper compilation
File path or library reference is broken or pointing to wrong location
Version mismatch between subroutine declaration and implementation

Troubleshooting Steps

1Verify that the subroutine source file exists in the correct project directory and has not been deleted
2Check the subroutine call syntax and confirm the name matches exactly with the source file definition
3Review the source file for syntax errors by opening it in the KUKA IDE and attempting recompilation
4Verify all library paths and file references are correct and point to valid locations
5Delete all generated object files and perform a clean full rebuild of the entire project
6If using external libraries or modules, ensure they are properly registered and accessible to the linking process

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.