KRC0215

Common Causes

• Safety program or SafeOperation module has enabled output blocking to protect against unintended actuator activation
• $BLK_IO_AUT was set to TRUE during system startup or power initialization and was not reset
• Active safety interlock or protective device status requires output blocking for operator or equipment protection
• Program logic intentionally blocks outputs during certain operational phases and the operation was attempted during a blocked state
• Incorrect user permissions or access level prevents manual output control in the current system mode

Troubleshooting Steps

1. 1Check the KRC4 system variable $BLK_IO_AUT using the diagnostics menu and note if it is TRUE or FALSE
2. 2Verify that all safety interlocks and protective devices are properly closed and in correct operational state
3. 3Review the running safety program or SafeOperation configuration to understand why output blocking was activated
4. 4If output blocking is not needed, reset $BLK_IO_AUT to FALSE using the KRC4 variable editor or through the applicable safety program
5. 5Confirm that the current user has appropriate access level and permissions to control outputs in the active robot mode
6. 6After disabling the blocking condition, retry the output control command through the KUKA smartPAD or KRL program