Heidenhain codes
HeidenhainCommunicationIntermediate30-120 minutes

235-0079

HEIDENHAIN 235-0079 - No contact to ProfiNet terminal

No contact to ProfiNet terminal

Communication with a ProfiNet terminal has been lost. The control cannot maintain contact with the networked device.

Root Cause Summary

HEIDENHAIN alarm 235-0079 indicates a complete loss of communication between the TNC control and a configured ProfiNet terminal device. This typically occurs due to physical network disconnection, IP configuration conflicts, or ProfiNet device failure preventing proper cyclic data exchange.

Safety

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

Causes and Fixes

  1. 1

    Check Physical Connections

    Inspect all Ethernet cables connected to the TNC's ProfiNet interface (typically X116 connector). Verify secure connection and check for visible damage to cable jackets.

    Power down connected devices before disconnecting cables to prevent damage

  2. 2

    Test Cable Continuity

    Use a network cable tester or multimeter to verify continuity on all 8 conductors. Replace cable if any pairs show open circuit or short conditions.

    Cat5e minimum required for ProfiNet - Cat6 recommended for industrial environments

  3. 3

    Verify Link Status

    Check the Ethernet port LEDs on both TNC control and ProfiNet switch. Green/amber activity lights should be present when properly connected.

    TNC ProfiNet interface typically shows link status in MOD function under network diagnostics

  4. 4

    Reconnect and Test

    Reconnect all cables ensuring proper seating. Clear alarm using CE key and monitor for alarm recurrence during normal operation cycles.

DIY Feasiblehigh confidence

Call a technician if:

  • ·ProfiNet configuration requires specialized software
  • ·Multiple network devices affected simultaneously
  • ·TNC control network interface hardware suspected

Prevention

  • Use industrial-grade Ethernet cables with proper strain relief
  • Implement regular ProfiNet network diagnostics checks
  • Maintain spare ProfiNet devices for critical applications
  • Document all IP configurations and network topology

Common Mistakes

  • Ignoring ProfiNet cable category requirements
  • Using consumer-grade network switches in industrial environment
  • Not verifying IP address uniqueness before configuration
  • Mixing ProfiNet with standard Ethernet protocols on same network

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.