Heidenhain codes
HeidenhainCommunicationIntermediate30-120 minutes

235-0064

HEIDENHAIN 235-0064 - Unknown device on the DriveCLiQ interface

Unknown device on the DriveCLiQ interface

An unknown device has been detected on the DriveCLiQ interface. The connected component is not listed in the NC software's device table or is incompatible with the installed version.

Root Cause Summary

This alarm indicates a communication and identification failure within the DRIVE-CLiQ network topology used by Heidenhain controls with integrated Siemens S120 drive systems. The control's drive interface cannot properly recognize a device at a specific topology node, either due to hardware incompatibility, firmware mismatch, configuration errors, or component failure. Resolution requires matching the physical DRIVE-CLiQ topology to the configured device list in the drive parameters.

Safety

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

Causes and Fixes

  1. 1

    Connect STARTER commissioning tool

    Connect a PC with Siemens STARTER software to the X124 service port on the S120 Control Unit. Establish online connection and go online with the project to access drive diagnostics.

    Ensure only qualified personnel access drive parameters. Incorrect drive configuration can cause machine damage.

  2. 2

    Compare topology configuration

    In STARTER, navigate to Drive Object > Topology view. Compare the configured DRIVE-CLiQ device list against the physical installation. Note device at position %1 specifically and verify article number matches installed hardware.

    Use the topology overview graphic in STARTER to visually trace DRIVE-CLiQ connections from Control Unit through Terminal Modules to Sensor/Motor Modules.

  3. 3

    Perform topology scan

    In STARTER, execute 'Topology > Scan for topology' to automatically detect all physically connected DRIVE-CLiQ devices. Compare scan results with configured topology and note any differences at device position indicated in alarm.

    Save topology scan results as reference documentation before making configuration changes.

  4. 4

    Update topology configuration

    If scan reveals different device at alarm position, update topology configuration in STARTER by deleting old device entry and inserting correct device type. Download updated configuration to Control Unit and perform drive power cycle.

    Always create backup of working drive parameters before modifying topology configuration.

  5. 5

    Verify alarm clearance

    After power cycle, monitor startup sequence at TNC control. Alarm 235-0064 should not reappear if topology now matches physical installation. Verify all axes respond correctly in manual mode.

    Check TNC error log (MOD > Service > Error Messages) to confirm no additional DRIVE-CLiQ communication errors during startup.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Software update fails or causes additional alarms
  • ·Multiple DriveCLiQ devices show unknown status
  • ·Memory test indicates hardware failure

Prevention

  • Maintain current TNC software versions
  • Implement regular system backups
  • Use only Heidenhain-approved DriveCLiQ cables
  • Document all hardware changes and part numbers

Common Mistakes

  • Assuming hardware failure without checking software compatibility
  • Mixing DriveCLiQ cable types or lengths
  • Updating drive firmware without verifying TNC compatibility
  • Ignoring EMI sources near DriveCLiQ wiring

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.