Heidenhain codes
HeidenhainCommunicationIntermediate30-120 minutes

235-0090

HEIDENHAIN 235-0090 - No original HEIDENHAIN driver software

No original HEIDENHAIN driver software

Third-party manufacturer software has been loaded via IOconfig but is not original HEIDENHAIN software. The control has not activated this software.

Root Cause Summary

This alarm specifically detects that drive interface drivers loaded in the TNC system lack HEIDENHAIN's digital signature or have been modified. The control's security architecture prevents operation with unverified drivers to maintain real-time performance guarantees and prevent incompatible software from compromising motion control integrity. Resolution requires reinstalling genuine HEIDENHAIN software from authorized sources.

Safety

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

Causes and Fixes

  1. 1

    Access system information

    Press MOD key, select 'System Information' to document current software version, build number, and installation date. Record this information for comparison after reinstallation.

    Screenshot the system information display or note the exact build date - this helps identify if mixed versions were installed.

  2. 2

    Obtain original HEIDENHAIN software

    Locate the original TNC software installation DVD/USB media matching your control model (TNC 320/530/620/640). If unavailable, contact HEIDENHAIN Service with your control serial number to receive authorized installation media. Never use software from unofficial sources.

    Using software from non-HEIDENHAIN sources may contain incompatible drivers and will trigger this alarm repeatedly.

  3. 3

    Perform clean NC software installation

    Boot from the original HEIDENHAIN installation media. Select 'Complete Installation' option (not 'Update') to ensure all driver components are replaced with genuine versions. Follow on-screen prompts and allow the process to complete fully without interruption.

    Ensure UPS backup power is available - power loss during installation will corrupt the system and require complete reinstallation.

  4. 4

    Verify driver authenticity post-installation

    After installation completes and system reboots, check that alarm 235-0090 no longer appears. Access MOD > Service > System Status to verify all drive modules show 'OK' status with version numbers matching the installed software release.

    Document the driver versions shown in System Status for future reference if similar issues arise.

DIY Feasiblemedium confidence

Call a technician if:

  • ·License activation fails after multiple attempts
  • ·IOconfig modifications cause system instability
  • ·TNC software update required

Prevention

  • Maintain current third-party software licenses
  • Verify driver compatibility before TNC updates
  • Regular backup of IOconfig and third-party software

Common Mistakes

  • Installing incompatible driver versions
  • Modifying IOconfig without proper licensing
  • Ignoring software expiration notifications

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.