What causes FANUC alarm 245?

Incorrect G-code programming in the same block as a T-code. Mixing G-codes that are not allowed to be used together in the same block. Attempting to use a G04, G10, G28, G29, G30, G50, or G53 command in the same block as a T-code.

How do I fix FANUC alarm 245?

1. Review the program block where the alarm occurred and identify the G-code and T-code that are being used together. 2. Separate the G-code and T-code commands into different program blocks, ensuring they are not used in the same block. 3. Verify that the G-codes being used are compatible with the T-code command and make any necessary corrections to the program. 4. If the issue persists, check the CNC program for any other instances where G-codes and T-codes may be used together incorrectly.

axismd.ai

FANUC Controller

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

Alarm 245

Fanuc Alarm 245 - T-CODE NOT ALLOWED IN THIS BLOCK

Fanuc Alarm 245 occurs when a T-code (tool call) is programmed in the same block as one of the restricted G-codes: G04 (dwell), G10 (programmable data input), G28 (return to reference position), G29 (return from reference position), G30 (return to 2nd/3rd/4th reference position), G50 (coordinate system setting/max spindle speed), or G53 (machine coordinate system selection). These G-codes require independent execution and cannot share a block with tool change commands due to motion control and sequence timing conflicts.

FANUCProgram/G-codeIntermediate15-30 minutes

245

Fanuc Alarm 245 - T-CODE NOT ALLOWED IN THIS BLOCK

PROGRAM ALARM 245

Root Cause Summary

Fanuc Alarm 245 occurs when a T-code (tool call) is programmed in the same block as one of the restricted G-codes: G04 (dwell), G10 (programmable data input), G28 (return to reference position), G29 (return from reference position), G30 (return to 2nd/3rd/4th reference position), G50 (coordinate system setting/max spindle speed), or G53 (machine coordinate system selection). These G-codes require independent execution and cannot share a block with tool change commands due to motion control and sequence timing conflicts.

Causes and Fixes

1
Press PRGRM key and review the alarmed program block displayed on the screen. Identify which restricted G-code (G04/G10/G28/G29/G30/G50/G53) is combined with the T-code.
2
Separate the T-code and restricted G-code into individual blocks. Example: Change 'G28 U0 W0 T0101;' to two blocks: 'G28 U0 W0;' followed by 'T0101;' on the next line.
3
Reset the alarm by pressing RESET key, return to program start or safe position, and re-execute the corrected program to verify proper operation.

DIY Feasiblehigh confidence

Call a technician if:

·Parameter corruption suspected
·Repeated alarms after program correction
·Tool changer mechanical issues

Prevention

Always separate T-codes from restricted G-codes into different program blocks
Use program verification tools before running production
Establish standard tool change sequences in programming guidelines

Common Mistakes

Combining multiple functions in single block for efficiency
Copy-pasting code blocks without checking G-code compatibility
Not understanding Fanuc block execution sequence requirements

Related Alarms

074 244 246 400

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.