FANUC codes
FANUCProgram/G-codeIntermediate30-60 minutes

1100

Fanuc Alarm 1100 - CANCEL WITHOUT MODAL CALL

Canned Cycle Error

Fanuc program alarm 1100: Canned Cycle Error. The part program contains an error or illegal condition that the Fanuc control cannot execute. Correct the program to clear this alarm.

Root Cause Summary

Alarm 1100 occurs when a G67 (modal call cancel) command is executed without an active G66 (macro modal call) being in effect. This is a programming logic error where the cancel command is issued either without a preceding G66, after a G66 has already been canceled, or in incorrect program structure. The CNC detects the mismatch between the cancel instruction and the actual macro call state.

Safety

  • Verify cycle before running
  • VERIFY cycle parameters before executing program
  • Before making any changes to the G-code program or machine parameters, ensure that you understand the potential consequences. Incorrect changes can lead to machine damage, workpiece damage, or personal injury.
  • Always verify the G-code program in a safe environment, such as a simulator, before running it on the machine. This will help identify potential errors and prevent accidents.
  • Be aware of the machine's emergency stop button and be prepared to use it if necessary. If the machine is behaving erratically, immediately press the emergency stop button to prevent further damage or injury.
  • Ensure that the workpiece is securely clamped and that the machine's safety interlocks are functioning correctly before running any G-code program.
  • Electrical Hazard: Never attempt to repair or modify the machine's electrical system unless you are a qualified electrician. High voltages are present inside the machine's control cabinet, which can cause serious injury or death.
  • Mechanical Hazard: Keep hands and other body parts away from moving parts of the machine during operation. The machine's cutting tools and other moving components can cause serious injury.
  • Wear appropriate personal protective equipment (PPE), such as safety glasses, gloves, and hearing protection, when operating the machine.
  • Ensure proper personal protective equipment (PPE) is worn during troubleshooting

Causes and Fixes

  1. 1

    Review the active NC program on the PROGRAM screen. Search backward from the alarm point for any G66 command that should have activated modal macro call before the G67.

  2. 2

    Check for duplicate G67 commands in the program. The first G67 cancels the G66 modal call, and any subsequent G67 without a new G66 will trigger alarm 1100.

  3. 3

    Verify program logic including conditional statements (IF/GOTO) or subprogram calls that may cause the G66 to be skipped while G67 is still executed. Trace program flow from start to alarm point.

  4. 4

    Correct the program by either removing the erroneous G67, adding the missing G66 before the G67, or restructuring conditional logic to ensure G66/G67 pairing is maintained. Reset alarm and test program.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Parameter corruption suspected
  • ·System continues to alarm after program corrections
  • ·Macro memory allocation issues persist

Prevention

  • Always pair G66 with G67 in program structure
  • Use program initialization blocks to establish known modal states
  • Implement proper program restart procedures
  • Regular backup of programs and parameters

Common Mistakes

  • Copying program segments without complete G66/G67 pairs
  • Using block restart without considering modal state context
  • Assuming G67 is always safe to execute
  • Not verifying macro program existence before G66 call

Related Alarms

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.