FANUC SRVO-043 DCAL Alarm: Regenerative Discharge Overload and the Hidden Cost of an Aggressive Cycle

The robot is running a tight cycle, the line is loaded, and SRVO-043 SERVO DCAL on G1 A2 takes it down. You reset, it runs, it drops again twenty minutes later. The alarm is not random. The amplifier is telling you it cannot dump heat fast enough into the regenerative resistor, and the cycle is asking for more than the hardware can deliver. We see this several times a quarter on R-30iA Mate and R-30iB welders, palletizers, and tending cells running close to their thermal ceiling.

This post is written for technicians dealing with SRVO-043 on R-J3, R-J3iB, R-30iA Mate, and R-30iB cabinets. The diagnostic logic is the same regardless of cabinet, but the hardware on the bigger arms tolerates more cycle abuse before the alarm shows.

What this error actually means

SRVO-043 is the alarm raised when an axis amplifier dissipates too much regenerated energy into its discharge resistor. The FANUC error code manual references it as: “SRVO-043 SERVO DCAL alarm(Group:%d Axis:%d).” The PNT1-109 echo on page 1027 of the R-30iB error code manual confirms that this is a discharge-current alarm tied directly to the affected group and axis. The remedy line on the same page points back to the SRVO-043 entry itself, which is the manual’s way of saying the fix lives in the cycle and the cooling, not in the alarm name.

Mechanically, every time the arm decelerates a heavy joint, the motor acts as a generator. That energy has to go somewhere. The amplifier dumps it through a regenerative resistor, which gets hot. If decelerations come too close together, or the joint is being braked harder than the spec, the resistor exceeds its thermal budget, and the amp posts SRVO-043 before something blows.

Most common causes, in order of probability

What we actually find on the cell floor:

1. Payload data does not match real tooling. When the robot does not know the real mass and center of gravity, its motion planner picks decelerations that overload the resistor on heavier joints. Often surfaces on the J2 axis of a palletizer or J3 of a long-reach welder. The DIY Robotics forum thread on this alarm starts the conversation around payload and acceleration tuning for exactly this reason (reference thread).
2. Acceleration override or program duty cycle too aggressive. Programs that brake hard between every move generate more heat than programs that flow through with CNT100. A tightened cycle that recently moved from CNT0 to higher overrides is a classic SRVO-043 source.
3. Cabinet fans clogged or amplifier exhaust restricted. A cabinet filter that has not been changed in a year drops fan output enough to push the amp over its limit on a hot day. Same alarm code as a program problem, completely different fix. A Reddit user troubleshooting an LR Mate 200iC documented checking the amp variant first, then chasing thermal causes (reddit thread).
4. Regenerative discharge resistor degraded. Resistors do age. They open partially, they shift value, and the amp stops being able to dump energy where it expects to. Usually only suspect after the cycle and the cooling are confirmed clean.
5. Servo amplifier itself failing. Last on the list because it is the most expensive guess. A Robot-Forum poster only reached this conclusion after returning the controller to a vendor, which is the kind of escalation you should not start with (robot-forum thread).

How to diagnose in under 10 minutes

Step 1. Note which group and axis the alarm calls out. SRVO-043 always names G: A:. Take the axis number to the program before you go to the cabinet.

Step 2. Single-step the program and watch where the alarm fires. If it always trips at the same move, you have a payload or deceleration problem at that point. If it trips randomly, lean toward thermal causes (fans, resistor, ambient).

Step 3. Open MENU > SYSTEM > Motion > Payload and confirm the active payload schedule. Cross-check the mass, CoG, and inertia against the real tooling. If anyone has changed grippers in the last month, you likely just found your fix.

Step 4. Pull the cabinet door, check the filters and the amp exhaust path. A cabinet that runs 5 degrees hotter than the spec sheet will throw SRVO-043 on duty cycles it used to tolerate.

Step 5. If everything checks out and the alarm persists, plan a swap of the suspect axis amplifier. Match the amp model exactly, including the variant, since R-30iA Mate cabinets come in fewer flavors than R-30iB but the wrong variant will misbehave silently (LR Mate thread).

How to fix it

Match the fix to what you found.

If the payload schedule is wrong: run PAYLOAD ID with the actual tooling installed, save the result to the schedule, and re-test. PAYLOAD ID measures dynamic response and is the only reliable way to set this number on robots that did not ship from a known integration.

If the cycle is hammering one axis: insert CNT values between aggressive moves so the controller blends instead of stopping cold. On welding cells, a short WAIT or an unattended air-blow step on the right joint can drop the duty cycle below the SRVO-043 threshold without losing throughput.

If the cabinet is hot: change the filters, clean the amp exhaust path, and recheck after the next full shift. On older R-30iA Mate cabinets, an aging fan can pull air without moving the volume the spec calls for, and that needs swapping.

If only one joint trips repeatedly with payload and cooling correct: reseat the amplifier connectors and the brake/encoder cables on the affected axis. If it still trips, plan an amp swap on the next outage and order the exact variant.

A note from the DIY Robotics thread that comes up often: do not assume an SRVO-043 is the amp’s fault until you have confirmed the move that triggers it (forum reference). The shop floor is full of replaced amps that did not fix the problem.

When to call a specialist

Call us when the cycle is tuned correctly, payload is correct, cooling is in spec, and SRVO-043 still drops on the same axis. At that point the conversation is about a controlled amp swap, mastering backup verification, and a thermal audit of the cabinet, which is the kind of half-day intervention that wants to be planned, not improvised at 2am.

contact us for an on-site service call, or set up a maintenance preventive contract so cabinet filters, amplifier connectors, and cycle thermal margins get reviewed before a production cell starts dropping DCAL alarms.

Related errors to check

• SRVO-046 OVC alarm: overcurrent on the same axis. If SRVO-046 logs alongside SRVO-043, you have a current problem that the amp is also flagging thermally.
• SRVO-044 HVAL: high voltage on the servo amp. Different trigger, but if it fires alongside SRVO-043 the regenerative path itself is suspect.
• SRVO-050 Collision Detect: separate alarm, but often shows up together when payload is wrong. Both clear together once payload data is fixed.

Probot Systems is a FANUC integrator based in Lévis, Quebec. We commission palletizers and welders and maintain them across Canada and the US, and SRVO-043 is one of the alarms we see most often on cells that have outgrown their original cycle plan. If you want a thermal and cycle audit before the next heat wave, that is a contact us conversation.