Heidenhain codes
HeidenhainCommunicationIntermediate30-120 minutes

236-A103

HEIDENHAIN 236-A103 - Contact lost to ProfiNet end device

Contact lost to ProfiNet end device

This TNC7/TNC 640 system error indicates Interrupted communication between TNC and a ProfiNet end device. Possible causes. The control has detected an abnormal state that requires attention.

Root Cause Summary

HEIDENHAIN alarm 236-A103 indicates a communication failure between the TNC control and a ProfiNet end device configured in the network topology. This alarm typically occurs when the TNC's ProfiNet master loses cyclic data exchange with a configured slave device, triggering the communication watchdog timeout.

Safety

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

Causes and Fixes

  1. 1

    Check physical cable connections

    Inspect all ProfiNet cables between TNC and the affected end device. Look for loose RJ45 connectors, damaged cables, or disconnected network switches.

    Power down the TNC before disconnecting any ProfiNet cables to prevent data corruption.

  2. 2

    Verify cable integrity

    Use a network cable tester to check continuity of all 8 wires in the ProfiNet cable. Replace any damaged cables with industrial-grade Cat5e or Cat6 cables.

    ProfiNet requires industrial-grade cables - standard office network cables may cause intermittent faults.

  3. 3

    Check network topology

    Access MOD function → Setup → ProfiNet configuration to verify the network topology matches the physical installation and all devices show 'Connected' status.

  4. 4

    Reset ProfiNet communication

    In Setup → ProfiNet, disable and re-enable the ProfiNet master to reinitialize communication with all end devices.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Multiple end devices failing simultaneously
  • ·TNC ProfiNet master hardware failure suspected
  • ·Complex network topology with managed switches requiring configuration

Prevention

  • Use industrial-grade ProfiNet cables with proper shielding
  • Implement regular ProfiNet diagnostics monitoring
  • Maintain spare end devices for critical applications
  • Document network topology and IP addressing scheme

Common Mistakes

  • Using office-grade network cables instead of industrial ProfiNet cables
  • Connecting ProfiNet shields at both ends creating ground loops
  • Mixing ProfiNet with standard Ethernet traffic on same network
  • Not updating GSD files when replacing end devices

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.