KRC0104

Common Causes

• Damaged or loose X31 communication cable between KRC and DSE-IBS module causing signal dropout
• DSE board hardware failure or corrupted firmware preventing proper cyclic data exchange
• Timing violation in PROFIBUS or EtherCAT network cycle due to excessive external axis load or configuration mismatch
• Incorrect $ETH_ASYNC or drive bus configuration parameters in machine data causing communication timeout
• EMI interference on fieldbus cables disrupting synchronization signals between controller and drive modules

Troubleshooting Steps

1. 1Step 1: Acknowledge alarm and check for visible damage on X31 cable and DSE module connector, reseat connections firmly
2. 2Step 2: Verify LED status on DSE-IBS board - green steady indicates normal operation, red or flashing indicates communication error or board fault
3. 3Step 3: Access Diagnosis -> PROFIBUS/EtherCAT in smartPAD and verify all configured drive nodes show green status with no timeout errors
4. 4Step 4: Check machine data file $ROBCOR.DAT and $ETH_ASYNC.DAT for correct bus cycle time and DSE addressing matching physical hardware configuration
5. 5Step 5: Test with external axes disconnected from motion program - if alarm clears, investigate external axis drive parameterization and mechanical binding
6. 6Step 6: Replace DSE-IBS module if above checks pass but alarm persists, then perform complete bus scan and drive reinitialization in WorkVisual