What causes FANUC alarm 010?

G-code number does not exist in the Fanuc alarm list for this series (e.g., value outside valid range). G-code requires an option that is not enabled on this control (e.g., G96 requires constant surface speed option). Typo in the part program — G1O (letter O) instead of G10, or similar character substitution. G-code not valid in the current modal state or in combination with other active G-codes. Program post-processed for a different Fanuc series with different G-code support.

How do I fix FANUC alarm 010?

1. Note the block number shown on the Fanuc alarm screen and locate that block in the program. 2. Verify the G-code number is correct — check for typos, especially O vs 0 confusion. 3. Consult the Fanuc programming manual G-code list for this series to confirm the code is valid. 4. Check if the G-code requires a machine option that may not be installed on this control. 5. If the program was CAM-generated, verify the post-processor is configured for this specific Fanuc series.

axismd.ai

FANUC Controller

Program/G-code · Basic · 15-30 minutes

Alarm 010

Fanuc Alarm 010 - IMPROPER G-CODE

Fanuc Alarm 010 IMPROPER G-CODE occurs when the CNC system encounters a G-code that is either not supported by the current control model/series, is syntactically incorrect, or conflicts with active system parameters that disable certain G-code functions. This is a program validation error detected during block execution or pre-read.

FANUCProgram/G-codeBasic15-30 minutes

010

Fanuc Alarm 010 - IMPROPER G-CODE

G-Code Not Allowed

Root Cause Summary

Fanuc Alarm 010 IMPROPER G-CODE occurs when the CNC system encounters a G-code that is either not supported by the current control model/series, is syntactically incorrect, or conflicts with active system parameters that disable certain G-code functions. This is a program validation error detected during block execution or pre-read.

Safety

Verify machine is in proper state before testing G-codes - ensure all axes are homed and within travel limits
Use caution when testing unknown G-codes in AUTO mode - prefer MDI with reduced feedrates
Ensure machine is homed and within travel limits before testing G-codes
Use MDI mode with reduced feedrates when testing unknown G-codes - avoid AUTO mode
Be aware of potential rapid or unexpected machine movements when testing G-codes. Keep a hand on the emergency stop button.
Ensure all safety interlocks and guards are in place and functioning correctly before operating the machine.
If the alarm occurs during program loading, ensure the machine is properly grounded to prevent electrostatic discharge, which could damage the control.
Before making any changes to machine parameters, back up the existing parameters to prevent data loss.
Keep emergency stop button accessible during G-code testing
Verify all safety interlocks and guards are functioning before operation
Back up existing parameters before making any changes

Causes and Fixes

1
Identify the exact G-code causing the alarm by reviewing the program line number displayed with alarm 010 on the CNC screen. Note the G-code and block number.
2
Navigate to SYSTEM > PARAM and check parameter 3401-3410 (G-code system selection) to verify the active G-code system (A/B/C). Cross-reference the flagged G-code against the Fanuc programming manual for your specific control series to confirm if it is valid.
3
Check parameters 3450-3490 (valid G-code range settings) to ensure the G-code number falls within enabled ranges. Some controls use these parameters to restrict available G-codes based on machine configuration.
4
If the G-code is unsupported, modify the NC program to use an equivalent valid G-code for the control series, or contact the machine builder to confirm if parameter changes or software options are required to enable the function.
Changing G-code system parameters can affect all existing programs. Backup parameters before modification.

DIY Feasiblehigh confidence

Call a technician if:

·Parameter changes require machine tool builder approval
·Software option purchase and installation needed
·Custom macro conflicts affecting multiple programs

Prevention

Always verify G-code compatibility with your specific control model before programming
Maintain documentation of enabled/disabled G-codes and custom macro assignments
Use program verification tools before running new programs

Common Mistakes

Assuming all G-codes work on all FANUC controls
Enabling G-codes without understanding their safety implications
Not checking software option requirements before programming

Related Alarms

011 012 020 021

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.