KRC0373

Common Causes

• Incorrect parity bit configuration in the serial port or fieldbus communication settings (should typically be set to EVEN, ODD, or NONE depending on device specification)
• Loose or damaged communication cable between the KRC controller and peripheral device causing signal degradation
• Mismatched baud rate or parity settings between the KRC controller and the connected external device
• EMI/RFI interference on the communication line corrupting transmitted data packets
• Faulty serial communication card or fieldbus interface module in the KRC controller

Troubleshooting Steps

1. 1Verify the parity setting in the KRC controller's serial port configuration matches the connected device specification (check device manual for correct parity: EVEN, ODD, or NONE)
2. 2Inspect and test the serial communication cable for physical damage, proper shielding, and secure connections at both ends
3. 3Confirm that baud rate and data bits (typically 8) are correctly configured and match between the KRC controller and the external device
4. 4Move the communication cable away from high-voltage power lines and motor cables; consider adding ferrite clamps to reduce EMI interference
5. 5Power cycle the KRC controller and the connected peripheral device, then re-establish communication to allow proper handshake
6. 6If the alarm persists after verification, replace the serial communication cable and test; if still present, contact KUKA service to diagnose potential hardware failure in the communication interface