What causes FANUC alarm 310?

Program number or file path in M198 or file access command does not exist on the device. External storage device (USB, CF card) not inserted or not recognized by the control. File was deleted or moved from the device since the program was created. Incorrect drive designation or subdirectory path in the file access command. Data server connection lost or the specified file does not exist on the server.

How do I fix FANUC alarm 310?

1. Verify the file name and path in the program against the actual files on the device. 2. Check that the external storage device is inserted and recognized by the CNC. 3. Navigate the file directory on the control to confirm the file exists. 4. Check the data server connection if using network file access. 5. Correct the file path or program number in the M198 or file access command.

axismd.ai

FANUC Controller

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

Alarm 310

Fanuc Alarm 310 - FILE NOT FOUND

Fanuc Alarm 310 FILE NOT FOUND occurs when the control attempts to execute a subprogram call (M98, G65, or macro call) but cannot locate the specified program number in memory or on the active storage device. This is typically caused by incorrect program numbering, missing programs in memory, or incorrect file path parameters when using external memory devices.

FANUCProgram/G-codeAdvanced30-120 minutes

310

Fanuc Alarm 310 - FILE NOT FOUND

FILE NOT FOUND

Root Cause Summary

Fanuc Alarm 310 FILE NOT FOUND occurs when the control attempts to execute a subprogram call (M98, G65, or macro call) but cannot locate the specified program number in memory or on the active storage device. This is typically caused by incorrect program numbering, missing programs in memory, or incorrect file path parameters when using external memory devices.

Safety

CRITICAL SAFETY ALARM

Causes and Fixes

1
Identify the called program number from the alarm screen or check the main program line where execution stopped (look for M98 P[number] or G65 P[number]).
2
Press PROG key, select directory/list mode, and verify the subprogram exists in memory with the exact O-number being called (e.g., if calling M98 P1234, verify O1234 exists).
3
If program is missing, transfer the subprogram to CNC memory via RS232, USB, CF card, or network depending on configured I/O device in Parameters 20 (I/O channel).
4
Check parameter 3204#0 (OHD) and 3204#4 (O8D) - if set to 1, these require 4-digit or 8-digit program numbers respectively. Verify program numbering format matches parameter settings.

DIY Feasiblehigh confidence

Call a technician if:

·Memory hardware failure suspected
·Parameter corruption requiring system restore
·Repeated alarms after all troubleshooting steps

Prevention

Maintain organized program numbering system
Regular backup of all programs and parameters
Verify subprogram existence before main program execution
Use consistent O-number formatting

Common Mistakes

Confusing O1 with O0001 in program calls
Forgetting to load subprograms after main program
Incorrect P-address format in M98 calls
Not checking macro option availability before G65 calls

Related Alarms

078 079 311 312

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.