Heidenhain codes
HeidenhainCommunicationIntermediate30-120 minutes

236-A101

HEIDENHAIN 236-A101 - No contact to ProfiNet end device

No contact to ProfiNet end device

This TNC7/TNC 640 system error indicates The ProfiNet end device does not respond. Possible causes. The control has detected an abnormal state that requires attention.

Root Cause Summary

HEIDENHAIN alarm 236-A101 occurs when the TNC control loses communication with a configured ProfiNet end device. This typically results from network configuration mismatches, physical connection issues, or device naming conflicts in the ProfiNet topology.

Safety

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

Causes and Fixes

  1. 1

    Access ProfiNet Configuration

    Navigate to MOD function → Setup → ProfiNet → Device Configuration to view configured device names.

    Document all device names before making changes for easy rollback.

  2. 2

    Verify End Device Name

    Check the physical device label or use ProfiNet diagnostic tools to confirm the actual device name matches the TNC configuration.

    Ensure the machine is in a safe state before accessing physical devices.

  3. 3

    Update Configuration

    Correct the device name in the TNC ProfiNet configuration or rename the end device to match the TNC setup using appropriate device configuration software.

  4. 4

    Restart ProfiNet Communication

    Execute PLC program restart or cycle TNC power to reinitialize ProfiNet communication with corrected device names.

DIY Feasiblehigh confidence

Call a technician if:

  • ·End device requires firmware update
  • ·ProfiNet project requires complete redesign
  • ·Multiple devices showing similar communication failures

Prevention

  • Regularly backup ProfiNet configurations
  • Use cable strain relief to prevent connection damage
  • Monitor ProfiNet diagnostic counters for early failure detection
  • Keep spare Ethernet cables and end devices in inventory

Common Mistakes

  • Assuming cable is good without testing
  • Forgetting to restart ProfiNet after configuration changes
  • Using incorrect GSDML files for device firmware version
  • Not documenting original device names before changes

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.