What causes Siemens SINUMERIK alarm 21614?

Axis overtravel beyond the physical limit switch position due to a program error, manual jog mistake, or loss of position reference after a power cycle, causing the drive to detect the switch activation.. Defective or misadjusted hardware limit switch that is triggering prematurely or intermittently, often caused by mechanical wear, contamination with coolant or chips, or a cam that has shifted out of position.. Loose or broken wiring in the limit switch circuit, including the signal wire, common ground, or shield connection, causing the controller to see a false trip signal even when the axis is not at the travel boundary.. Incorrect machine data or software limit settings that allow the CNC to command the axis into a position where the hardware limit is reachable before the software overtravel protection intervenes.. Encoder or feedback system fault causing the controller to lose accurate position tracking, which can result in the axis being driven physically past the intended boundary while the controller believes it is still in a safe position.. Faulty NCU or I/O module input card where the limit switch input channel has developed a fault, causing it to read the switch as active regardless of the actual switch state.. Mechanical obstruction or fixture collision that stopped the axis short of its intended position, causing the axis to be physically located at or near the limit switch without an obvious program cause..

How do I fix Siemens SINUMERIK alarm 21614?

1. Step 1: Do not attempt to jog the axis further in the same direction. Identify which axis triggered the alarm by checking the alarm details in the Siemens diagnostics screen, then determine the direction of travel that caused the trip before moving anything. 2. Step 2: Visually inspect the axis and the limit switch cam or dog to confirm the switch actuator is actually making contact with the switch. If the axis is clearly not at the physical boundary, suspect a wiring or input card fault rather than a true overtravel. 3. Step 3: With the control in a safe state, use a multimeter to measure continuity and voltage at the limit switch terminals. A normally closed limit switch should read closed circuit under normal conditions. Check the signal at both the switch itself and at the corresponding I/O terminal strip in the cabinet to isolate whether the fault is in the switch or in the wiring run. 4. Step 4: Inspect the limit switch body, mounting bracket, and cam for physical damage, coolant ingress, corrosion, or debris. Actuate the switch manually by hand and confirm it clicks and releases cleanly. A switch that does not release or feels spongy needs replacement. 5. Step 5: Check the limit switch cable for chafing, pinching, or broken conductors, especially at flex points in the cable track or where the cable exits a connector. Wiggle the cable while watching the input status in the Siemens I/O diagnostic screen to catch intermittent faults. 6. Step 6: If the switch and wiring check out, navigate to the machine data parameters for that axis and verify the software overtravel limits (MD36100 POS_LIMIT_MINUS and MD36110 POS_LIMIT_PLUS) are set correctly and are positioned inside the hardware limit switch locations by a safe margin. 7. Step 7: If the axis did genuinely travel to the hardware limit, you need to retract it in the opposite direction using the overtravel release function. On Siemens SINUMERIK controls, enable the overtravel key (typically a dedicated key or softkey in JOG mode), then carefully jog the axis away from the limit switch until the alarm clears, then perform a reference point return. 8. Step 8: After clearing the alarm and re-homing the axis, run the relevant program section slowly in single block mode while watching the actual position value against the software limit boundary to confirm the software limits will catch the axis before it can reach the hardware limit again in normal operation.

axismd.ai

Siemens SINUMERIK Controller

Spindle · Intermediate · 10-30 minutes

Alarm 21614

Siemens Alarm 21614 - Hardware Limit Switch Reached

SINUMERIK alarm 21614 occurs when the hardware limit switch input signal for a drive axis becomes active, indicating the axis has reached its physical travel boundary. This safety mechanism immediately stops axis movement to prevent mechanical damage, but can also be triggered by faulty limit switches, wiring issues, or incorrect parameter settings in the drive configuration.

Siemens SINUMERIKSpindleIntermediate10-30 minutes

21614

Siemens Alarm 21614 - Hardware Limit Switch Reached

Hardware Limit Switch

Root Cause Summary

SINUMERIK alarm 21614 occurs when the hardware limit switch input signal for a drive axis becomes active, indicating the axis has reached its physical travel boundary. This safety mechanism immediately stops axis movement to prevent mechanical damage, but can also be triggered by faulty limit switches, wiring issues, or incorrect parameter settings in the drive configuration.

Safety

Check for collision damage
Move axis carefully away from limit
Be aware of potential pinch points and moving parts when working near the axis.
Ensure the machine is properly grounded to prevent electrical shock.
If electrical troubleshooting is required, disconnect power to the machine and follow proper lockout/tagout procedures.
High voltage may be present in the drive cabinet. Only qualified personnel should access the drive cabinet.
Before re-referencing the axis, ensure the work area is clear of obstructions and personnel.

Causes and Fixes

1
Check Current Axis Position
Navigate to Diagnostics > Drive > Actual Values and verify the current position against the machine's physical travel limits defined in MD36100 (POS_LIMIT_MINUS) and MD36110 (POS_LIMIT_PLUS).
Compare machine coordinates with the actual physical position using a measuring device to confirm accuracy.
2
Manually Retract Axis
Use Machine > Manual > JOG mode to carefully move the axis away from the limit switch in the opposite direction at reduced feedrate (10% override recommended).
Ensure the limit switch is mechanically clear before attempting movement to avoid damage.
3
Reset Alarm and Verify Operation
Press RESET key to clear alarm 21614, then test axis movement within normal working envelope to ensure proper operation.
Check the alarm log in Diagnostics > Alarms > Archive to identify what program or operation caused the overtravel.

DIY Feasiblehigh confidence

Call a technician if:

·Multiple limit switches failing simultaneously
·Drive module hardware suspected
·Safety circuit modifications required

Prevention

Regular limit switch inspection and cleaning
Proper cable routing away from interference sources
Periodic verification of limit switch operation during PM
Monitor alarm frequency in service logs

Common Mistakes

Ignoring intermittent limit switch behavior
Incorrect switch polarity configuration
Bypassing hardware limits without proper safety analysis
Not checking cable shield grounding

Related Alarms

21615 25050 25051 380xx

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.