Heidenhain codes
HeidenhainServo/AxisIntermediate30-120 minutes

260-020E

Heidenhain 260-020E - Compilation of PLC error table failed

Compilation of PLC error table failed

This alarm occurs when the Heidenhain control's PLC compiler cannot successfully compile the PLC error table (PLCE.TAB or error handling structures) during system startup or after PLC program modifications. The PLC error table defines custom error messages and handling routines for machine-specific conditions. Compilation failure prevents proper PLC error message display and handling.

Root Cause Summary

The PLC compiler has encountered errors while attempting to compile the error table definitions, preventing the control from properly establishing PLC-based error handling. This is typically caused by syntax errors, file corruption, or format incompatibility in the PLCE.TAB file. The control cannot continue with PLC operations until the error table compiles successfully.

Safety

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

Causes and Fixes

  1. 1

    Access PLC programming environment

    Press MOD key, select 'PLC Programming' or access via Settings → General → MOD functions → PLC. Enter service password if required for your control generation.

    On iTNC 530 and TNC 620/640, you can access PLC files directly through the File Manager in PLC operating mode.

  2. 2

    Review compilation error log

    Check the PLC compiler output window or error log for specific error messages indicating line numbers, syntax issues, or invalid error number ranges. Note any E-number conflicts or format violations.

    Heidenhain PLC error numbers must be in the range E1000-E9999 for user-defined errors.

  3. 3

    Open and inspect PLCE.TAB

    Navigate to TNC:\plc\ directory and open PLCE.TAB file. Verify proper format: error number, language identifier, error text in quotes, proper delimiters. Check for special characters, missing quotes, or incorrect line termination.

    Each error definition must follow format: E#### "Error text in English" or E#### DE "Fehlertext" for German. No semicolon needed at line end.

  4. 4

    Validate error number ranges

    Ensure all error numbers are within valid ranges and not duplicated. User PLC errors must use E1000-E9999 range. Remove any conflicting or out-of-range definitions.

    Do not use error numbers E0001-E0999 as these are reserved for Heidenhain system errors.

  5. 5

    Recompile and test

    Save corrections to PLCE.TAB, then manually trigger PLC compilation via 'Compile All' in PLC programming mode. Verify compilation completes without errors before exiting.

    Always keep a backup of working PLCE.TAB file on external media before making changes.

DIY Feasiblemedium confidence

Call a technician if:

  • ·PLC file restoration fails
  • ·Custom PLC code requires extensive modification
  • ·Memory issues persist after optimization

Prevention

  • Maintain regular PLC file backups
  • Test PLC modifications in simulation before deployment
  • Monitor PLC memory usage during code development

Common Mistakes

  • Modifying system PLC files without backup
  • Ignoring PLC compilation warnings
  • Using invalid error number ranges in custom code

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.