Heidenhain codes
HeidenhainSafetyIntermediate30-120 minutes

239-0273

HEIDENHAIN 239-0273 - 273 UM-FSUC: cyclic communication inconsistent CC

273 UM-FSUC: cyclic communication inconsistent CC

The FS microcontroller detected inconsistent cyclic communication with the PAE module. Data exchange is not functioning correctly.

Root Cause Summary

Alarm 239-0273 indicates the FS (Functional Safety) microcontroller has detected inconsistent cyclic communication with the PAE (Position and Axis Electronics) module. This typically occurs due to communication timing issues, hardware faults in the PAE module, or configuration mismatches between the TNC control and axis electronics.

Safety

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

Causes and Fixes

  1. 1

    Check PAE Module Status LEDs

    Examine the PAE module status indicators. Green LED should be solid, red LED should be off during normal operation.

    Ensure machine is in emergency stop before opening electrical cabinet

  2. 2

    Verify EnDat Cable Connections

    Check all EnDat encoder cables between PAE module and motor encoders for secure connections and proper shielding continuity.

    Use a multimeter to verify shield continuity - resistance should be less than 1 ohm

  3. 3

    Monitor Cycle Time in MOD Function

    Access MOD > System Info > Communication and check PAE communication cycle times for values exceeding 4ms.

    Normal cycle times should be 2-3ms consistently

  4. 4

    Reset PAE Module

    Power cycle the PAE module by removing 24V supply for 10 seconds, then restore power and monitor alarm status.

DIY Feasiblemedium confidence

Call a technician if:

  • ·PAE module hardware failure confirmed
  • ·Multiple encoder failures detected
  • ·Parameter corruption requiring factory reset

Prevention

  • Perform monthly encoder signal quality checks
  • Maintain proper cable management and shielding
  • Keep PAE modules clean and well-ventilated
  • Regular parameter backup schedule

Common Mistakes

  • Ignoring encoder cable bend radius requirements
  • Mixing encoder cable types in same installation
  • Incorrect axis parameter mapping during setup
  • Failing to verify shield continuity after cable installation

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.