What causes KUKA Robot alarm KRC0627?

Attempting to create a SUB module with an identical name to an existing SCR module in the same project. Importing or copying modules that create duplicate names between different module types. Manual file system edits that created conflicting module names without updating project references. Using WorkVisual to add modules without checking for existing names across all module types. Project merge or integration that introduced duplicate module names from different branches.

How do I fix KUKA Robot alarm KRC0627?

1. Open the project in WorkVisual and review the module list to identify the conflicting SCR and SUB modules 2. Check the file system under the project directory to confirm which modules exist with duplicate names 3. Rename the SUB module or SCR module to a unique identifier that does not conflict with existing modules 4. Verify that all program calls and references to the renamed module are updated throughout the project 5. Clean and rebuild the project in WorkVisual to ensure the module name change is properly compiled 6. Test the application on the KUKA smartPAD to confirm the naming conflict has been resolved

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0627

KUKA Robot KRC0627 - <Name> already exists

A module name conflict has occurred in the KRL project structure. The system cannot create a SUB module when an SCR module with the same name already exists, or vice versa. This naming conflict must be resolved before compilation can proceed.

KUKA RobotSystemBasic

KRC0627

KUKA Robot KRC0627 - <Name> already exists

<Name> already exists

Common Causes

Attempting to create a SUB module with an identical name to an existing SCR module in the same project
Importing or copying modules that create duplicate names between different module types
Manual file system edits that created conflicting module names without updating project references
Using WorkVisual to add modules without checking for existing names across all module types
Project merge or integration that introduced duplicate module names from different branches

Troubleshooting Steps

1Open the project in WorkVisual and review the module list to identify the conflicting SCR and SUB modules
2Check the file system under the project directory to confirm which modules exist with duplicate names
3Rename the SUB module or SCR module to a unique identifier that does not conflict with existing modules
4Verify that all program calls and references to the renamed module are updated throughout the project
5Clean and rebuild the project in WorkVisual to ensure the module name change is properly compiled
6Test the application on the KUKA smartPAD to confirm the naming conflict has been resolved

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.