Heidenhain codes
HeidenhainCommunicationIntermediate30-120 minutes

231-C690

Heidenhain 231-C690 - C690 DQ communication error

C690 DQ communication error

This alarm indicates a communication error on the DriveQ (DQ) digital drive interface between the Heidenhain TNC control and one or more axis drives. The parameter typically identifies the specific axis or drive module experiencing the communication fault. This is a critical error that prevents proper command transmission to the servo drives over the EnDat or digital interface.

Root Cause Summary

The C690 alarm is fundamentally a breakdown in the digital communication protocol between the TNC control and the drive system. This occurs when the control cannot establish or maintain reliable data exchange with the drive module, preventing proper servo control. The issue is almost always hardware-related, involving cabling, connectors, power supply integrity, or drive electronics failure rather than software configuration.

Safety

  • Refer to Heidenhain service manual
  • Ensure qualified technician performs repairs

Causes and Fixes

  1. 1

    Identify Affected Axis

    Note the axis designation from the %1 parameter in alarm 231-C690. Cross-reference this with the machine's electrical documentation to locate the specific drive module and cable routing.

    The %1 parameter often shows the logical axis name (X, Y, Z, etc.) but may show the physical drive number depending on TNC version.

  2. 2

    Inspect Cable Connections

    Power down the control and check the EnDat/drive communication cable at both ends - X116/X126 connectors on the TNC side and the corresponding connector on the drive module. Look for bent pins, contamination, or loose retention clips.

    Always disconnect main power and wait for DC-Bus discharge (minimum 5 minutes) before handling drive connections.

  3. 3

    Check Cable Routing and Condition

    Inspect the cable along its entire length for pinch points, sharp bends (minimum bend radius 10x cable diameter), or proximity to power cables. Check cable shields are properly terminated at both ends.

    Drive communication cables should never be routed in the same cable tray as motor power cables - maintain minimum 200mm separation.

  4. 4

    Perform Cable Swap Test

    If possible, swap the suspected cable with an identical cable from a functioning axis. If the alarm follows the cable, replace it. Use only Heidenhain-approved shielded cables with correct impedance.

    Always use cables with part numbers specified in the drive system documentation - generic industrial cables often lack the required electrical characteristics.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Multiple drive modules showing faults
  • ·TNC control module replacement needed
  • ·Persistent alarms after cable/connection repairs

Prevention

  • Maintain proper DRIVE-CLiQ cable bend radius
  • Keep spare DRIVE-CLiQ cables in stock
  • Perform quarterly connection inspections
  • Monitor system temperature trends

Common Mistakes

  • Forcing RJ45 connectors causing pin damage
  • Mixing standard Ethernet cables with DRIVE-CLiQ cables
  • Ignoring intermittent alarms until permanent failure
  • Not following proper DRIVE-CLiQ daisy-chain sequence

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.

Start free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.