KRC0379 indicates that a peripheral device or interface is not responding or is unavailable to the KUKA KRC controller. This alarm occurs when the controller attempts to communicate with an external device (such as an I/O module, safety device, or communication interface) but fails to establish or maintain the connection. The device may be physically disconnected, powered off, or experiencing communication protocol failures.
KUKA RobotSystemBasic
KRC0379
KUKA Robot KRC0379 - DEVICE NOT READY
DEVICE NOT READY
KRC0379 indicates that a peripheral device or interface is not responding or is unavailable to the KUKA KRC controller. This alarm occurs when the controller attempts to communicate with an external device (such as an I/O module, safety device, or communication interface) but fails to establish or maintain the connection. The device may be physically disconnected, powered off, or experiencing communication protocol failures.
Common Causes
Cable disconnected or unseated from the connector port on the controller or peripheral device
Damaged or defective communication cable (frayed wires, pinch damage, or internal conductor breaks)
Peripheral device powered off or not receiving adequate power supply
Incorrect or incompatible device configured in the KRC controller software configuration files
Communication protocol mismatch or outdated firmware on the connected peripheral device
Troubleshooting Steps
1Power cycle the KUKA KRC controller and all connected peripheral devices; wait 30 seconds between power-off and power-on
2Visually inspect all data and power cables for physical damage, corrosion, or loose connections; reseat all connectors firmly until they click
3Verify that the peripheral device is powered on and displaying normal status indicators or LED signals
4Check the KRC controller's device configuration in the system files (typically in the robot's configuration database) to ensure the device type and communication parameters are correctly specified
5Test the cable with a multimeter or cable tester to verify continuity and proper pin connections; replace the cable if defects are found
6If the issue persists, access the controller's diagnostic menu to check the device communication status and error logs; contact KUKA technical support with the diagnostic report if the device remains unresponsive
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.