Siemens SINUMERIK codes
Siemens SINUMERIKOvertravel/LimitBasic5 - 15 minutes

10620

Siemens 10620 - Block axis at software limit switch

Block axis at software limit switch

During the traversing motion, the system detected that the software limit switch would be traversed in the direction indicated. Exceeding the traversing range was not detected during block preparation because there has either been a motion overlay or a zero offset has been executed or a coordinate transformation is active Control reaction: Local alarm reaction. NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm at block end.

Root Cause Summary

SINUMERIK alarm 10620 occurs when the NC kernel encounters a feed-interpolated motion command (G01, G02, G03) without a valid positive feedrate value. This typically results from missing F-word programming, modal feedrate loss during mode transitions, or feedrate override conditions reducing the effective rate to zero.

Safety

  • Only qualified personnel should diagnose and clear control alarms; follow the machine builder's safety procedures and lockout/tagout where hardware work is required.

Causes and Fixes

  1. 1

    Check Current NC Block

    In SINUMERIK Operate, navigate to Program > Editor and examine the NC block where alarm occurred. Look for missing F-word before any G01/G02/G03 commands.

    Use the cursor position indicator in the NC editor to identify the exact block that triggered the alarm.

  2. 2

    Verify Modal Feedrate Status

    Press Machine > Diagnostics > Service > Variables and check $AA_MODAL[F] to see current modal feedrate value. Zero indicates no feedrate is active.

    Modal feedrate is lost after M02/M30 or when switching between feed modes.

  3. 3

    Add Valid F-Word

    Edit the NC program to include appropriate F-word (e.g., F1000 for mm/min) before the motion command. Ensure F-value matches units set in MD20150 (AXCONF_MACHAX_USED).

    Always verify feedrate units - G94 (mm/min) vs G95 (mm/rev) to prevent excessive speeds.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Machine data modifications required
  • ·PLC interface issues with override signals
  • ·Persistent alarm after program corrections

Prevention

  • Always initialize R-parameters used in feedrate calculations
  • Program F-word explicitly after mode changes (G94/G95 switches)
  • Use feedrate validation subroutines in complex programs
  • Verify override switch positions before program start

Common Mistakes

  • Assuming modal feedrate persists through all mode changes
  • Using uninitialized variables in F-word expressions
  • Programming G95 moves without active spindle
  • Setting feedrate override to 0% during setup

Related Alarms

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.