
axismd.ai
Heidenhain Controller
Servo/Axis · Intermediate · 30-120 minutes
HEIDENHAIN 231-C6B0 - C6B0 DQ init error State= ID= Port=
The 231-C6B0 alarm is triggered when the Heidenhain control's integrated SINAMICS drive system cannot successfully initialize a DRIVE-CLiQ component during the startup sequence. This is typically caused by communication failures, hardware faults, or topology mismatches in the DRIVE-CLiQ network that connects drive modules, motor encoders, and terminal boards.
HEIDENHAIN 231-C6B0 - C6B0 DQ init error State= ID= Port=
C6B0 DQ init error State= ID= Port=
This TNC7/TNC 640 system error indicates DRIVE-CLiQ initialization error. The control has detected an abnormal state that requires attention.
Root Cause Summary
The 231-C6B0 alarm is triggered when the Heidenhain control's integrated SINAMICS drive system cannot successfully initialize a DRIVE-CLiQ component during the startup sequence. This is typically caused by communication failures, hardware faults, or topology mismatches in the DRIVE-CLiQ network that connects drive modules, motor encoders, and terminal boards.
Safety
Causes and Fixes
Power Down System
Completely power down the control and drive system. Ensure all voltage is removed before inspecting connections.
Wait at least 5 minutes after power-down for capacitors to discharge before touching any components.
Inspect DRIVE-CLiQ Cables
Visually inspect all orange DRIVE-CLiQ cables for physical damage, kinks, or pinching. Check cable routing to ensure minimum bend radius is maintained.
DRIVE-CLiQ cables have a minimum bend radius of 10x cable diameter. Excessive bending can cause internal wire breaks while the outer insulation appears intact.
Reseat All Connections
Disconnect and reconnect all DRIVE-CLiQ cable connections at both ends. Ensure you hear/feel the positive click indicating proper seating. Pay special attention to the port number identified in %6 parameter.
Start from the control unit and work outward through the topology. Clean connector contacts with electronic contact cleaner if oxidation is visible.
Test Restart
Power up the system and observe if the alarm clears. If alarm persists with same port/ID, suspect cable failure. If alarm moves to different component, suspect multiple connection issues.
Document the ID=%5 and Port=%6 values before and after reseating to track if the fault location changes.
Call a technician if:
Prevention
Common Mistakes
Seeing Multiple Alarms?
Seeing another alarm with this one? Enter the code.
AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.
Start freeWas this guide helpful?
Always verify with your machine manual or a certified technician before performing service procedures.