Fanuc 7115 Alarm -
: Ensure the auxiliary contacts on the switching contactors are sending the correct confirmation signals back to the CNC. A missing feedback signal will trigger the 7115 alarm. Test Wiring
: Use the robot's "Ping" utility ( [ MENU ] → Setup → Host Comm ) to see if the robot can see the PLC/remote device on the network.
While a dead battery is the most common culprit, several other variables can trigger this specific fault code:
Contactor tips can weld together due to high current. fanuc 7115 alarm
Manually jog the affected axis to its physical reference position (using alignment marks or a dial indicator). Change (bit 4) from 0 to 1 for that axis.
The robot was commanded by the software program to move to a position outside its allowable physical workspace.
Conclusion The Fanuc 7115 alarm points to critical issues in the servo feedback loop or drive system. Systematic troubleshooting — starting with contextual data, inspection, signal monitoring, parameter checks, and component isolation — identifies the root cause while minimizing unnecessary replacements. Repairs typically involve restoring reliable feedback (encoders/cables), addressing amplifier or motor faults, correcting mechanical binding, or fixing parameter/tuning mismatches. Preventative measures such as proper cable routing, grounding, routine inspections, and thermal management reduce recurrence and help maintain consistent CNC performance. : Ensure the auxiliary contacts on the switching
Once you resolve alarm 7115, take these steps to ensure it never returns.
When the FANUC 7115 alarm occurs, you may notice the following symptoms:
Ensure that the spindle switching timers and confirmation parameters are set correctly according to the machine tool builder's (MTB) specifications. Cable Continuity: While a dead battery is the most common
Use the FANUC and Diagnostic screens to monitor critical I/O signals that are prone to causing alarm 7115. An unexpected change in a signal’s state (e.g., a clamp switch that intermittently drops out) can be caught early before it leads to a full alarm.
Only after you have verified the code is 100% correct according to your machine’s option sheet. If the code is perfect but the alarm persists, you may have a corrupted parameter or a failing PMC, but that is rare.