What causes FANUC alarm 136?

SPOS command in the same block as an axis movement when simultaneous execution is not permitted. Spindle positioning attempted while another SPOS or SPOSA is already active. M19 spindle orient and SPOS commanded together in a conflicting sequence. SPOS not allowed in current spindle mode (speed mode vs. position mode).

How do I fix FANUC alarm 136?

1. Separate the SPOS command into its own block. 2. Ensure no other spindle positioning or orient commands are active before issuing SPOS. 3. Verify spindle is in position control mode (SPOS requires position control mode active). 4. Review the Fanuc programming manual for SPOS usage restrictions on this series.

axismd.ai

FANUC Controller

Program/G-code · Advanced · 30-60 minutes

Alarm 136

Fanuc Alarm 136 - SPOS AXIS - OTHER AXIS SAME TIME

Alarm 136 occurs when a spindle positioning M code (typically M19 or user-defined spindle orientation) is commanded in the same NC block with other axis movement commands (X, Y, Z, etc.). The Fanuc control does not allow simultaneous spindle positioning and linear/rotary axis motion in a single block because spindle positioning requires the spindle to operate in position mode rather than speed mode.

FANUCProgram/G-codeAdvanced30-60 minutes

136

Fanuc Alarm 136 - SPOS AXIS - OTHER AXIS SAME TIME

SPOS AXIS - OTHER AXIS SAME TIME

Root Cause Summary

Alarm 136 occurs when a spindle positioning M code (typically M19 or user-defined spindle orientation) is commanded in the same NC block with other axis movement commands (X, Y, Z, etc.). The Fanuc control does not allow simultaneous spindle positioning and linear/rotary axis motion in a single block because spindle positioning requires the spindle to operate in position mode rather than speed mode.

Safety

Communication lost

Causes and Fixes

1
Review the NC program at the alarm occurrence point. Check for M19 or custom spindle positioning M codes (defined in parameters 4960-4962) in the same block as X, Y, Z, A, B, or C axis commands.
2
Separate the spindle positioning command into its own block. Example: Change 'G00 X100. M19' to two blocks: 'M19' followed by 'G00 X100.' on the next line.
3
Verify parameter 4960 (Spindle Positioning M code) and check if bit 0 of parameter 3704 (Spindle positioning selection) is properly configured for your spindle orientation requirements.
4
Add a dwell command G04 P1000 (1 second) after M19 if needed to ensure spindle positioning completes before subsequent axis motion, particularly for heavy or high-inertia spindles.

DIY Feasiblehigh confidence

Call a technician if:

·Parameter backup corruption
·Multi-spindle hardware configuration changes needed
·Encoder feedback issues during spindle positioning

Prevention

Always separate M19 commands from linear axis moves
Verify spindle positioning parameters after any axis configuration changes
Use proper spindle selection in multi-spindle programs

Common Mistakes

Programming M19 X__ Y__ on same line
Forgetting to cancel coordinate transformations before spindle positioning
Incorrect parameter 4077 settings after machine modifications

Related Alarms

135 137 410 411

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.