FANUC Mastering Lost After Battery Replacement: Recovering Encoder Zero Without Re-Touching Every Position

The robot was stored over the holidays, the controller was powered off, and when you came back in January every Cartesian move throws BZAL or the robot lands meters away from where the program expects. You replaced the backup batteries, restarted the controller, and now you are staring at an unmastered robot with two days of production scheduled. This is one of the most common ways to lose half a week of production in a small shop, and the recovery depends entirely on what you have in your last AOA backup.

This post is for maintenance technicians and integrators recovering mastering on R-30iB and R-30iB Plus controllers across the FANUC range, with specific attention to CRX-10iA, M-10iA, and LR Mate 200iD where mastering recovery is a common service call.

How FANUC mastering actually works

Every FANUC robot tracks its joint positions with absolute encoders. “Absolute” means the encoder remembers where it is between power cycles, as long as the encoder’s backup battery holds voltage. Mastering is the procedure that ties the encoder’s raw value (a pulse count) to a known physical orientation of the joint (the “zero” position).

When the battery voltage drops below a threshold, the encoder loses its absolute reference and reports an alarm called BZAL (Battery Alarm) or BLAL (Battery Low Alarm). After BZAL, the encoder counts up from wherever it powered on, not from the true mastering position. Cartesian moves become unsafe because the controller does not know where the joints actually are.

The official FANUC alarm code manual entry for INTP-106 reads: “Program cannot be resumed. Remedy: Refer to the error cause code. Use MENU to display the Alarm Log screen.” That alarm fires when you try to start a Cartesian program against an unmastered robot. Below it in the log you will usually find an MCTL-003 or a SYST-212 telling you the deeper cause.

For SYST-212: “Mastering data or robot parameters are changed, but they are not applied to the DCS parameter. Remedy: Press F3(APPLY) in the DCS menu.” That alarm shows up after you re-master, because the DCS subsystem holds a separate copy of the mastering offset and needs to be told to sync.

Most common pitfalls

1. Controller stored powered off for months. Backup batteries drain at a rate that depends on the encoder type and temperature. Storing for 6+ months without power means the batteries are almost certainly flat by the time you come back. The BZAL Alarm on CRX-10iA/L thread describes this exact pattern.
2. Batteries replaced with controller powered off. Pulling the batteries while the controller is dead loses the encoder counts immediately, no grace period. Every FANUC controller maintenance manual specifies battery replacement with controller ON for this reason.
3. No recent AOA backup. Without an AOA that contains SYSMAST.SV, you cannot Quick Master and have to fall back to Single Axis Mastering at the casting marks. The INTP-106 Continue request failed, MCTL-003 system is in error status thread documents this scenario.
4. Quick Master Reference position not set. Even with an AOA, if no one ever pressed “Set Quick Master Ref” while the robot was well-mastered, the Quick Master shortcut does not have a reference position to recover to. Single Axis Master is the only path.
5. Mastered from someone else’s backup. A backup from a different robot will work mechanically, but the TCP will be measurably offset because mastering is unit-specific. The Incorrect robot movement after battery replacement thread shows the symptoms clearly.

How to recover mastering

Scenario A: You have a recent AOA backup from this exact robot, and Quick Master Ref was set before the loss.

This is the fastest recovery, usually under 30 minutes.

Step 1. Boot the robot. Acknowledge BZAL by pressing RESET (it will probably come right back).

Step 2. Restore SYSMAST.SV from your AOA backup. MENU > FILE > F1 LOAD > navigate to USB1: > select SYSMAST.SV > F4 LOAD. Confirm overwrite.

Step 3. Cold start. The robot should boot with valid mastering. The TP should now show actual joint angles that match the physical orientation.

Step 4. Press F3 APPLY in MENU > SYSTEM > DCS to clear any SYST-212.

Step 5. Run a slow test program against a known fixture point. TCP repeatability should be within 0.5mm of the original.

Scenario B: You have an AOA but Quick Master Ref was not previously set.

Same as Scenario A through Step 3, then verify by jogging the robot to its known visual zero position (all axis marks aligned with the casting witness marks). If the TP joint readout shows zero, the restore worked. If it shows non-zero, the backup mastering was from a different state and you need to Quick Master to the current visual zero.

Scenario C: No backup at all, robot needs full re-mastering.

This is the painful one, but it is recoverable.

Step 1. Manually drive each axis (joint mode, slow) to the painted mastering marks on the robot casting. Every joint has a witness mark milled into the casting and a matching mark on the rotating element. Align them.

Step 2. From MENU > 0 NEXT > SYSTEM > F1 TYPE > Master/Cal, select “Single Axis Master”.

Step 3. For each axis in turn, press F2 EXEC, then verify the new master position. Repeat for all 6 (or 7) axes.

Step 4. Press F2 SET QMR (Set Quick Master Reference) so the next battery event is faster to recover from.

Step 5. F3 APPLY in DCS.

Step 6. Verify TCP repeatability against a known fixture. Expect 1-2mm offsets from the original cell calibration because hand-aligning casting marks is not precision work. Re-teach UFRAMEs against any fixture that needs sub-millimeter accuracy.

The I’ve messed up our CRX10i thread is a sobering case where a tool frame edit triggered a chain reaction that looked like mastering loss but was actually a frame discipline problem. Worth reading to recognize when you are dealing with mastering versus when you are dealing with frames.

How to prevent this from happening again

Replace batteries with controller ON. The FANUC maintenance manual says this clearly. The hot-swap is brief: one battery at a time, replace within 30 seconds while controller is energized, encoder counts survive.

Take an AOA every quarter. Schedule it. Different USB stick per robot per quarter. Store at least one off-site.

Set Quick Master Reference after every mastering event. Press F2 SET QMR in the Master/Cal menu. This is the cheapest insurance against the next battery event.

Monitor battery state. MENU > 4 STATUS > Battery shows battery health on R-30iB Plus. Replace before you see BLAL warnings, not after BZAL.

Schedule preventive battery replacement. Lithium backup batteries are spec’d for 4-5 years. Replace at 3 to be safe.

When to call a specialist

If you have no backup, no Quick Master Ref, and the cell relies on sub-millimeter accuracy (welding, dispensing, vision-guided pick), the Single Axis Master at the casting marks will not get you back to where you were. You need a specialist with a laser tracker or a calibrated fixture to verify the mastering match, then a frame-by-frame UFRAME re-teach.

For shops without a strong backup discipline, the right move is to set one up before the next event. contact us for an emergency mastering recovery, or set up a maintenance preventive contract that includes battery scheduling and verified quarterly AOA backups.

Related errors to check

• SRVO-062 BZAL: the canonical battery alarm. The trigger for everything in this post.
• SRVO-064 BLAL: low battery warning. Replace batteries before BZAL hits.
• INTP-106 Continue request failed: program will not resume because the controller does not trust the joint positions.
• SYST-212 Need to apply to DCS param: appears after re-mastering. Press F3 APPLY in the DCS menu.
• MCTL-003 system is in error status: companion alarm that often shows up with INTP-106 when mastering is lost.

Probot Systems is a FANUC integrator based in Lévis, Quebec. We do mastering recovery and preventive battery service across Canadian and US plants, including on shop floors where the only viable recovery is laser-tracker verification. If your robot has lost mastering and your backup is months old, that is a contact us conversation.