PS010

At the alarm screen, note the exact G-code and line number (N-number) causing PS010. Press RESET and use EDIT mode to navigate to the flagged block.

Navigate to SYSTEM > PARAMETER and check parameter 3106#0-#7 and 3107#0-#7 (G-code system selection bits) to verify which G-codes are enabled. Cross-reference with your control's programming manual for the specific series.

Press SYSTEM > OPTION and verify installed software options. Look for options like High-Speed Machining (bit 2), AI Contour Control, 5-Axis Machining, or Smooth TCP depending on the G-code in question.

If the option is missing, either modify the post-processor to exclude unsupported G-codes or contact Fanuc/machine builder for option enablement. If the option is present, verify parameter 19500-19699 series for G-code specific enable/disable settings.

Enabling software options requires proper licensing and may need Fanuc service involvement

Review the program block at the alarm location. Common syntax errors include: G-codes with invalid decimal formats (G2.1 instead of G02.1), missing required axis words (G02/G03 without I, J, K or R), or conflicting modal groups in the same block.

Check parameter 3404#0 (Decimal Point Input) to verify if your program matches the control's decimal point setting. If bit=0, leading zero format is required (G01 not G1). If bit=1, decimal point programming is active.

Verify parameter 0000 (Input Unit) is correctly set: 0=metric (mm), 1=inch. Program G-code format must match, especially for feeds, coordinates, and G20/G21 usage.

Cross-check the G-code against the Fanuc Programming Manual for your specific control series (0i-F, 30i-B, 31i-B5, etc.) as syntax requirements vary between generations. Edit and correct the program block accordingly.

Always perform a dry run after program edits to verify corrected syntax

Navigate to SYSTEM > PARAMETER and check parameters 6050-6059 (G-code group assignment). Verify if the problematic G-code has been reassigned or disabled. Also check parameter 3450#0-#7 for G-code input inhibit settings.

If Custom Macro option is installed, check parameters 6050-6099 for user-defined G-code assignments. User G-codes (typically G65, or G codes defined in 6050-6059) may conflict with program expectations.

Review parameters 11000-11255 (Macro Compiler/Custom Macro) if specific G-codes execute macro programs. Verify O-number programs exist in memory if G-codes call macros. Use EDIT > PROGRAM to list all programs.

Changing G-code group parameters can affect all programs on the machine

If a G-code was intentionally disabled for safety, consult with process engineering before re-enabling. If disabled in error, set the appropriate parameter bit and perform a control power cycle (not just reset) to activate the change.

Parameter changes at level 7 or 8 protection require parameter write enable (PWE) switch or password