Heidenhain codes
HeidenhainServo/AxisIntermediate30-120 minutes

1A0-008B

HEIDENHAIN 1A0-008B - Incorrect axis index for FN18

Incorrect axis index for FN18

The Q-parameter function FN18 was applied to an axis index that does not correspond to a main axis. Coordinate transformations through FN18 are restricted to X, Y, and Z only.

Root Cause Summary

The alarm is triggered when an NC program attempts to read axis-specific system data using FN18 with an axis index that does not correspond to any configured axis in the machine. This is typically a programming error where the axis index value is out of bounds, improperly calculated, or references an axis configuration that no longer exists on the machine.

Safety

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

Causes and Fixes

  1. 1

    Locate the problematic FN18 call

    In MANUAL mode, press the PROGRAM TEST key and review the error location. Note the exact line number and FN18 syntax. The alarm typically shows which block triggered the error.

    Use Test Run with single-block mode to step through the program and see Q-parameter values in the calculator before the FN18 executes.

  2. 2

    Check machine axis configuration

    Access MOD function, select 'Machine Parameters', and review MP120 (number of axes) and the axis assignment table. Note the total number of controlled axes (typically 3-5 axes).

    Valid axis indices typically range from 1 to the value in MP120. Some FN18 implementations use 0-based indexing.

  3. 3

    Verify FN18 syntax and index value

    Review the FN18 call structure: FN18: SYSREAD Q-parameter ID-number IDX-parameter. Check that the IDX value (axis index) is within the valid range 1 to MP120 value. If using a Q-parameter for the index, verify its calculated value.

    Add a temporary programming line before FN18 like 'FN16: F-PRINT Q-par/text' to output the axis index value to verify calculation.

  4. 4

    Correct the axis index or program logic

    Either change the hardcoded axis index to a valid value, or if using Q-parameters, correct the calculation logic. For portable programs, add conditional logic to check MP120 value first before calling FN18 with axis-specific IDs.

    Use FN18 ID10 to read MP120 into a Q-parameter, then use conditional jumps (FN9/FN10) to skip axis reads that would exceed the configured axis count.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Machine parameter access denied
  • ·Kinematic configuration errors persist
  • ·Axis assignment changes required

Prevention

  • Always use X, Y, Z axes only in FN18 functions
  • Document active transformations before programming
  • Verify axis assignments in machine parameters
  • Use PLANE function for rotary axis operations

Common Mistakes

  • Including A, B, C axes in FN18 syntax
  • Mixing kinematic and coordinate transformations
  • Not resetting previous transformations
  • Incorrect machine parameter axis definitions

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.