Heidenhain codes
HeidenhainSystemIntermediate30-120 minutes

900-0BB9

HEIDENHAIN 900-0BB9 - Failed to send internal message

Failed to send internal message

This error condition indicates failed to send internal message. The control has detected an issue that requires attention before normal operation can resume.

Root Cause Summary

Alarm 900-0BB9 indicates a breakdown in internal communication between TNC system components, typically involving the NC kernel, PLC, or hardware interface modules. This communication failure prevents proper data exchange between critical system processes, often triggered by software conflicts, hardware interface issues, or system resource exhaustion.

Safety

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

Causes and Fixes

  1. 1

    Check PLC Status

    Navigate to MOD > System Info > PLC and verify PLC cycle time is within normal range (<10ms). Check for PLC error messages in the error log.

    PLC cycle times over 15ms often indicate communication bottlenecks

  2. 2

    Reset PLC Communication

    Access MOD > Machine Parameters > General > MP7200 (PLC Interface) and toggle bit 0 to restart PLC communication interface.

    This will temporarily halt all PLC functions - ensure machine is in safe state

  3. 3

    Verify Message Queue Status

    Check MOD > Diagnostics > System Messages for message queue overflow. Clear queue if buffer shows >90% utilization.

    Message queue issues often correlate with high-frequency I/O operations

  4. 4

    Restart NC Software

    Perform controlled NC restart via MOD > System > Restart NC to reinitialize communication channels.

    Save all active programs and tool data before restart

DIY Feasiblemedium confidence

Call a technician if:

  • ·Hardware interface modules show persistent errors after reset
  • ·System resource issues persist after optimization
  • ·Software updates fail or cause additional errors

Prevention

  • Monitor system resources regularly via MOD diagnostics
  • Maintain clean network configurations
  • Perform regular system maintenance and cache clearing
  • Keep software versions synchronized across all components

Common Mistakes

  • Ignoring gradual resource usage increases
  • Mixing incompatible software versions during updates
  • Overlooking loose hardware interface connections
  • Not clearing system cache during regular maintenance

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.