axismd.ai
FANUC Controller
Program/G-code · Basic · 15-30 minutes
Fanuc Alarm 160 - MISMATCH WAITING M-CODE
Alarm 160 occurs in multi-path (synchronized) machining systems when different waiting M-codes are commanded simultaneously in Path 1 and Path 2. The CNC expects identical waiting M-codes (M-codes with third auxiliary function signals) to be executed synchronously across paths, but detects a mismatch in the commanded codes.
160
Fanuc Alarm 160 - MISMATCH WAITING M-CODE
SYSTEM ALARM 160
Fanuc alarm 160: SYSTEM ALARM 160. This alarm indicates a fault condition detected by the Fanuc control. Refer to the alarm number and name to identify the specific system or function involved.
Root Cause Summary
Alarm 160 occurs in multi-path (synchronized) machining systems when different waiting M-codes are commanded simultaneously in Path 1 and Path 2. The CNC expects identical waiting M-codes (M-codes with third auxiliary function signals) to be executed synchronously across paths, but detects a mismatch in the commanded codes.
Causes and Fixes
- 1
Check SYSTEM > PARAM > search parameter 3411 through 3420 to identify which M-codes are designated as waiting M-codes (third auxiliary function). Note all active waiting M-code numbers.
- 2
Review the NC programs for both Path 1 and Path 2 at the line where alarm occurred. Verify that both paths specify the exact same waiting M-code number at synchronized execution points.
- 3
Correct the program by ensuring identical waiting M-codes are programmed in both paths (e.g., if Path 1 has M100, Path 2 must also have M100 at that synchronization point).
- 4
Reset alarm, rewind programs for both paths, and re-execute in single block mode to verify synchronization.
In synchronized mode, both paths must reach the waiting M-code before either can proceed.
Call a technician if:
- ·Parameter 3407 changes don't resolve issue
- ·Persistent alarm after program corrections
- ·Suspected hardware synchronization failure
Prevention
- Always use identical waiting M-codes at synchronization points
- Validate multi-path programs in single block mode first
- Maintain consistent program structure between paths
Common Mistakes
- Using different M-codes for synchronization
- Ignoring G04 dwell timing effects
- Not resetting after program changes
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 freeWas this guide helpful?
Always verify with your machine manual or a certified technician before performing service procedures.