What causes KUKA Robot alarm KRC0743?

Signal name in KRL code does not match the predefined signal name in the signal definition file. Typo or case sensitivity mismatch in signal naming (e.g., 'Signal_1' vs 'signal_1'). Signal was renamed in the configuration but the KRL program still references the old name. Multiple conflicting signal definitions with similar but not identical names exist in the project. Signal imported from external library has a different name than expected in the current program scope.

How do I fix KUKA Robot alarm KRC0743?

1. Check the KRL source code for the exact signal name referenced near the error location 2. Verify the signal definition in the signal configuration file (*.src or signal table) matches the KRL reference exactly 3. Review the system configuration to ensure predefined signals are properly imported and accessible to the current program 4. Compare signal names for case sensitivity and special character differences between declaration and usage 5. Clear any cached compilation data and recompile the entire KRL program from scratch 6. If using signal aliases or imports, verify that the signal mapping is correctly configured and there are no duplicate or conflicting definitions

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0743

KUKA Robot KRC0743 - IDENTICAL PREDEFINED SIGNAL NAMES EXPECTED 2079

This alarm occurs when predefined signal names in a KRL program are not identical or do not match the expected naming convention defined in the system configuration. The compiler or runtime environment detected a mismatch between signal declarations and their predefined definitions, indicating a naming consistency violation.

KUKA RobotSystemBasic

KRC0743

KUKA Robot KRC0743 - IDENTICAL PREDEFINED SIGNAL NAMES EXPECTED 2079

IDENTICAL PREDEFINED SIGNAL NAMES EXPECTED 2079

Common Causes

Signal name in KRL code does not match the predefined signal name in the signal definition file
Typo or case sensitivity mismatch in signal naming (e.g., 'Signal_1' vs 'signal_1')
Signal was renamed in the configuration but the KRL program still references the old name
Multiple conflicting signal definitions with similar but not identical names exist in the project
Signal imported from external library has a different name than expected in the current program scope

Troubleshooting Steps

1Check the KRL source code for the exact signal name referenced near the error location
2Verify the signal definition in the signal configuration file (*.src or signal table) matches the KRL reference exactly
3Review the system configuration to ensure predefined signals are properly imported and accessible to the current program
4Compare signal names for case sensitivity and special character differences between declaration and usage
5Clear any cached compilation data and recompile the entire KRL program from scratch
6If using signal aliases or imports, verify that the signal mapping is correctly configured and there are no duplicate or conflicting definitions

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.