Heidenhain codes
HeidenhainCommunicationIntermediate30-120 minutes

236-A122

HEIDENHAIN 236-A122 - Error during access to ProfiNet end device

Error during access to ProfiNet end device

Initialization failed for a ProfiNet end device because it lacks support for the TNC-compatible ProfiDrive profile version.

Root Cause Summary

This alarm is fundamentally a ProfiNet network communication failure where the TNC cannot access a configured I/O device. The root cause is typically either physical layer issues (cabling, power, hardware failure) or configuration layer mismatches between the TNC's expected ProfiNet topology and the actual installed devices. The TNC monitors cyclic communication with all configured ProfiNet slaves and raises this alarm when a device becomes unreachable or non-responsive.

Safety

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

Causes and Fixes

  1. 1

    Identify the Affected Device

    Note the device name/number shown in the %1 parameter of the alarm message. Cross-reference this with your machine documentation or the ProfiNet configuration to identify the physical module location.

    The %1 identifier typically matches the device name configured in the TNC's ProfiNet setup, which may be a descriptive name like 'IO_Module_3' or 'EncoderInterface_2'.

  2. 2

    Verify Device Power and Status

    Locate the physical ProfiNet device in the cabinet. Check that power supply to the device is present (typically 24VDC) and verify status LEDs indicate normal operation. Most ProfiNet devices have dedicated LEDs for power, network status, and bus fault.

    Observe proper lockout/tagout procedures when accessing electrical cabinets. Verify power measurements with appropriate safety equipment.

  3. 3

    Inspect Device Network Indicators

    Check the ProfiNet-specific LEDs on the device. A green link LED indicates physical connection; a flashing green ProfiNet status LED typically indicates active cyclic communication. No activity or red LEDs indicate communication failure.

    Refer to the specific device manufacturer's LED pattern documentation—ProfiNet devices from different vendors use varying LED codes.

  4. 4

    Replace or Swap Device if Faulty

    If the device shows no signs of power or network activity despite verified power supply, the module may have failed. Replace with a known-good identical module, ensuring firmware versions are compatible with the TNC configuration.

    After replacing a ProfiNet device, you may need to assign the IP address and device name using the manufacturer's configuration tool before the TNC will recognize it.

DIY Feasiblemedium confidence

Call a technician if:

  • ·TNC software update required
  • ·ProfiNet hardware replacement needed
  • ·Multiple ProfiNet devices affected simultaneously

Prevention

  • Maintain ProfiNet device firmware compatibility matrix
  • Regular ProfiNet network diagnostics checks
  • Document ProfiDrive profile versions during commissioning

Common Mistakes

  • Mixing incompatible ProfiDrive profile versions
  • Incorrect ProfiNet device slot configuration
  • Ignoring ProfiNet timing parameter optimization

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.