What causes KUKA Robot alarm KRC0674?

Attempting to rename a global subroutine or function that is referenced in other program modules. Trying to rename a global object that is already declared or used in the active program workspace. Global SR/FCT name conflicts with existing reserved function or subroutine names in the KUKA system. Attempting to rename a global subroutine/function while it is actively being executed or called by other tasks. File or module permissions preventing modification of globally-scoped program objects.

How do I fix KUKA Robot alarm KRC0674?

1. Verify the global SR/FCT name does not conflict with KUKA system reserved names or existing program objects 2. Check all program modules and cross-references to identify where the global subroutine/function is being called 3. Ensure the object is not currently in use or being referenced by active tasks before attempting to rename 4. Create a new global subroutine/function with the desired name and migrate all references instead of renaming the existing object 5. Save and reload the entire project workspace to refresh the symbol table and clear potential naming conflicts 6. If necessary, delete all references to the original object, remove it, then recreate it with the new name and update all call references

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0674

KUKA Robot KRC0674 - GLOBAL SR/FCT CANNOT BE RENAMED 2010

This alarm indicates that a global subroutine (SR) or function (FCT) cannot be renamed during program compilation or editing. The system prevents renaming of globally-scoped program objects that are already defined or referenced elsewhere in the project to maintain code integrity and prevent broken references.

KUKA RobotSystemBasic

KRC0674

KUKA Robot KRC0674 - GLOBAL SR/FCT CANNOT BE RENAMED 2010

GLOBAL SR/FCT CANNOT BE RENAMED 2010

Common Causes

Attempting to rename a global subroutine or function that is referenced in other program modules
Trying to rename a global object that is already declared or used in the active program workspace
Global SR/FCT name conflicts with existing reserved function or subroutine names in the KUKA system
Attempting to rename a global subroutine/function while it is actively being executed or called by other tasks
File or module permissions preventing modification of globally-scoped program objects

Troubleshooting Steps

1Verify the global SR/FCT name does not conflict with KUKA system reserved names or existing program objects
2Check all program modules and cross-references to identify where the global subroutine/function is being called
3Ensure the object is not currently in use or being referenced by active tasks before attempting to rename
4Create a new global subroutine/function with the desired name and migrate all references instead of renaming the existing object
5Save and reload the entire project workspace to refresh the symbol table and clear potential naming conflicts
6If necessary, delete all references to the original object, remove it, then recreate it with the new name and update all call references

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.