KRC0493

Common Causes

• Accessing $POS_INT or other interrupt variables in the main program flow rather than within an interrupt handler
• Reading global variables before initialization code has executed during program startup
• Using conditional logic that attempts to read a variable that may not have been assigned in all code paths
• Accessing array elements with an index that exceeds the declared array bounds or is uninitialized
• Referencing a variable that was declared but never assigned a value before first use

Troubleshooting Steps

1. 1Identify the exact variable and line number reported in the alarm message using the program editor
2. 2Verify that the variable is properly initialized with a valid value before any read operations occur
3. 3Check if the variable is context-specific (such as $POS_INT for interrupts) and ensure it is only accessed in appropriate execution contexts
4. 4Review all code paths leading to the problematic read operation to confirm initialization occurs in every path
5. 5Add explicit initialization statements or defensive null/zero checks before reading potentially uninitialized variables
6. 6Test the program with the KUKA smartPAD debugger to monitor variable states and identify the point where initialization fails