Heidenhain codes
HeidenhainCommunicationIntermediate30-120 minutes

220-001B

HEIDENHAIN 220-001B - Cannot close queue

Cannot close queue

The control could not close an internal system queue. This is a system-level communication fault that may leave resources in an inconsistent state.

Root Cause Summary

HEIDENHAIN alarm 220-001B occurs when the TNC control cannot properly close an internal communication queue, typically due to network interface problems, PLC communication errors, or system resource conflicts. This alarm indicates a breakdown in the control's internal message handling system that manages data flow between different system components.

Safety

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

Causes and Fixes

  1. 1

    Check Network Interface Status

    Navigate to MOD function → System Info → Network Status and verify Ethernet interface X116 shows 'Connected' status with valid IP configuration.

    Look for packet loss counters or error statistics in the network diagnostics

  2. 2

    Reset Network Interface

    Access Setup → General → Network Settings, disable and re-enable the Ethernet interface, then restart the TNC control completely.

    Save all active programs before restarting the control

  3. 3

    Verify Cable Connections

    Check physical Ethernet cable connection at X116 connector and verify network switch/router connectivity with ping test from TNC terminal.

    Use TNC's built-in ping utility in MOD function → System → Network Tools

  4. 4

    Check Network Parameters

    Verify MP7200 (Network Configuration) parameters match your network requirements and MP7210 (IP Address) is not conflicting with other devices.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Alarm persists after network and PLC resets
  • ·Multiple communication alarms occur simultaneously
  • ·System memory consistently shows critical levels

Prevention

  • Regularly monitor network interface statistics
  • Implement proper LSV2 connection management in external software
  • Schedule periodic PLC cycle time monitoring
  • Maintain adequate free disk space for system operations

Common Mistakes

  • Ignoring network cable quality and connections
  • Not properly configuring LSV2 timeout parameters
  • Running too many simultaneous external connections
  • Clearing the alarm without addressing the underlying communication issue

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.