Heidenhain codes
HeidenhainCommunicationIntermediate30-120 minutes

236-A123

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

Error during access to ProfiNet end device

An error occurred while initializing a ProfiNet end device. More drive objects are logged for cyclic data exchange than available on the ProfiNet interface.

Root Cause Summary

The TNC control cannot establish or maintain communication with a specific ProfiNet IO device on the industrial Ethernet network. This is most commonly caused by physical connection failures, device power issues, configuration mismatches between the control's ProfiNet setup and actual hardware, or network infrastructure problems. The alarm protects against undefined I/O states by halting operations when fieldbus communication integrity is compromised.

Safety

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

Causes and Fixes

  1. 1

    Identify Failed Device

    Read the complete alarm text to identify which ProfiNet device number is referenced in %1. Cross-reference this with MOD > System Configuration > ProfiNet to determine the device name and location.

    The device number in %1 corresponds to the sequence order in the ProfiNet configuration tree, not necessarily the station address.

  2. 2

    Verify Device Power

    Physically inspect the identified ProfiNet device for power LED indicators. Check 24VDC supply voltage at the device terminals and verify circuit breakers or fuses in the power distribution system are intact.

    Use appropriate electrical safety procedures and lockout/tagout when checking power circuits.

  3. 3

    Check Network Connection

    Verify Ethernet cable is securely connected to both the ProfiNet device and the network switch/control. Look for link LED activity on the device's Ethernet port. Replace cable if damaged or uncertain.

    ProfiNet requires industrial-grade shielded cables with proper grounding on both ends. Standard office Ethernet cables can cause intermittent errors.

  4. 4

    Test Device Isolation

    Temporarily remove the suspect device from the ProfiNet configuration in MOD > System Configuration > ProfiNet to verify if the control operates normally without it. This confirms whether the device itself is faulty.

    Before removing from configuration, document all device parameters and slot assignments for later restoration.

DIY Feasiblemedium confidence

Call a technician if:

  • ·Hardware replacement required
  • ·Multiple drive failures detected
  • ·GSD file issues persist

Prevention

  • Regular ProfiNet cable inspection
  • Maintain current parameter backups
  • Monitor drive diagnostics weekly

Common Mistakes

  • Modifying configuration without backup
  • Ignoring ProfiNet diagnostic warnings
  • Mixing incompatible drive firmware versions

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.