Panasonic Minas A6 Servo Drive (MADLT/MBDLT) Alarm Codes, Step-by-Step Repair & Maintenance Guide

Panasonic Minas A6 Servo Drive (MADLT/MBDLT) Alarm Codes, Step-by-Step Repair & Maintenance Guide

By Jennifer Zhang

Panasonic's MINAS A6 family is one of the most widely installed servo platforms in modern packaging, semiconductor, and assembly machinery. The line spans single-axis pulse/analog A6B drivers such as the MADLT01SM, RTEX network A6N drivers such as the MADLT05SM, EtherCAT variants (A6ME/A6SF), and the multi-axis A6 Multi modules of the MBDLT series. All of them report faults the same way: when a protective function trips, the front-panel LED shows a code in the Er13.0 format — the number before the point is the main code, the digit after it is the sub-code — the ALM output opens, and the driver stops the motor according to Pr5.10 "Sequence at alarm."

Most alarms clear with the alarm clear input (A-CLR) held ON for 120 ms or longer after the cause is removed. Two field quirks matter: Err16.0 (overload) can only be cleared about 10 seconds after it occurs, and absolute-system alarms such as Err40.0 will not clear at all until an Absolute Clear has been performed. Panasonic's free Panaterm software shows the last 14 error factors together with the command and feedback waveforms captured at the trip moment — the fastest way to tell a wiring problem from a genuine hardware failure.

Please check our servo drive collection for tested replacement drivers and motion-control components before you begin.

Main-Circuit Alarms: Err13, Err14, Err16, Err18

Err13.0 / Err13.1 — Main Power Supply Under-voltage

Fault Manifestations: The driver refuses to run or trips during acceleration, showing Err13.0 (DC-bus under-voltage between P and N) or Err13.1 (AC interception detected — a momentary loss of input power).

Root Causes: Low incoming line voltage, one blown fuse or loose phase on a three-phase supply, undersized supply wiring, a failed upstream contactor or filter, or a supply that sags under motor inrush.

Repair Steps:

1. Measure the input voltage at the driver terminals under load and compare with the nameplate range (typically 200–240 VAC +10%/−15%).
2. Check fuses, terminal tightness, and every device ahead of the driver.
3. If the supply sags only during acceleration, increase conductor size or supply capacity.
4. On machines with frequent power dips, enable the momentary-power-loss ride-through option or add a line conditioner.

Err14.0 / Err14.1 — Over-current / IPM Error

Fault Manifestations: Instantaneous trip at power-on or the first motion command. Err14.0 is over-current; Err14.1 is an IPM (intelligent power module) error detected inside the driver.

Root Causes: A short or ground fault in the motor cable (crushed conduit, coolant-wet connectors), a phase-to-phase short in the motor windings, swapped motor phases, or a failed IGBT/IPM output stage in the driver itself.

Repair Steps:

1. Power down, let the bus discharge, then disconnect the motor cable at the driver.
2. Megger the cable phase-to-phase and phase-to-ground (should exceed 10 MΩ) and test the motor windings the same way.
3. Confirm U/V/W wiring order and shield grounding.
4. If cable and motor are clean and Err14 still returns with the motor disconnected, the power module has failed — replace the driver. The Yaskawa SGD7S-470A20A servo drive ($1,360.00) is a popular tested replacement.

Err16.0 / Err16.1 — Overload / Torque Saturation

Fault Manifestations: Trip partway through a cycle after seconds or minutes of running. Err16.0 is electronic overload protection; Err16.1 is torque saturation — the driver has hit its torque limit and cannot follow the command.

Root Causes: Mechanical binding, a brake that never released, gain oscillation, a motor/driver size mismatch, or a genuine duty overload in which effective torque exceeded the overload characteristic. Remember that Err16.0 cannot be cleared until roughly 10 seconds after the trip.

Repair Steps:

1. In Panaterm, watch the load ratio and torque waveform — oscillation points to tuning, a flat high plateau to mechanical load.
2. Rotate the load by hand (power off) to find binding; verify brake voltage on brake-equipped motors.
3. Verify gear ratio and inertia ratio, then re-run auto-gaining.
4. If the machine has outgrown the axis, upsize the motor/driver or lighten the cycle.

Err18.0 — Over-regeneration Load

Fault Manifestations: Trip during rapid deceleration or when a vertical axis lowers its load.

Root Causes: Regenerative energy flowing back into the DC bus exceeds the driver's built-in regeneration absorption — short decel times, high inertia, or high-duty vertical motion.

Repair Steps:

1. Extend deceleration times where the process allows.
2. Reduce the frequency of fast back-and-forth moves, or add/upgrade an external regeneration resistor or regeneration unit.
3. On new builds or upgrades, choose an amplifier with higher built-in regen capacity — for example the Yaskawa SGDH-60AE-P ($1,370.00) — when vertical axes dominate the cycle.

Encoder and Positioning Alarms: Err21, Err23, Err24, Err29

Err21.0 / Err21.1 / Err23.0 — Encoder Communication Errors

Fault Manifestations: Trip at power-up or intermittent trips with axis vibration. Err21.0 is encoder communication disconnection, Err21.1 a communication error, Err23.0 a communication data (frame) error.

Root Causes: Damaged encoder cable, contaminated or bent-pin connectors, noise from power cables routed in parallel, or a failing encoder inside the motor.

Repair Steps:

1. Power off and reseat both encoder connectors; inspect for bent pins.
2. Inspect the cable for sharp bends, staples, and drag-chain wear; reroute at least 30 cm from motor power lines.
3. Verify shield/FG grounding (ground at one end only).
4. Swap in a known-good cable: if the fault follows the cable, replace it; if it stays with the axis, suspect the encoder.
5. Repeated Err23.0 with clean wiring points to the encoder head — replace the motor or send the encoder for factory repair.

Err24.0 / Err29.0 — Position Deviation Excess / Deviation Counter Overflow

Fault Manifestations: The axis faults during motion because commanded position and feedback position diverge beyond the set limit (Err24.0), or the internal deviation counter overflows (Err29.0).

Root Causes: The motor stalled or slipped — mechanical jam, brake still engaged — gains set far too low, acceleration beyond available torque, or a command pulse frequency above the driver limit (pulse errors carry their own code, Err27.0).

Repair Steps:

1. Check whether the motor actually rotated when commanded; a stalled axis is a mechanical problem, not a tuning problem.
2. Verify torque limits and accel times; increase margins.
3. Re-tune gains and confirm the electronic gear ratio matches the machine specification.
4. Inspect the coupling for slippage or a sheared key.

System and Memory Alarms: Err36/37, Err40

Err36.0–1 / Err37.0–2 — EEPROM Parameter Errors

Fault Manifestations: Trip at power-up with an EEPROM parameter error (Err36.x) or EEPROM check-code error (Err37.x).

Root Causes: Corrupted parameter memory — typically after years of vibration, repeated brownouts, or a parameter save interrupted by a power cut.

Repair Steps:

1. Recover the parameter list from your Panaterm backup file.
2. Re-initialize the driver to factory defaults, reload the backup, and power-cycle.
3. If the error returns immediately after reload, the control-board EEPROM is failing — replace the driver or its control board.

Err40.0 — Absolute System Down

Fault Manifestations: On machines using the absolute system, the driver faults at power-up with Err40.0: encoder backup power and internal capacitor both discharged, so multi-turn data is lost.

Root Causes: Dead or disconnected absolute battery, a broken battery cable, or a machine left unpowered longer than the backup specification.

Repair Steps:

1. With control power ON, connect the fresh battery before removing the old one — never let the encoder lose backup mid-swap.
2. Power-cycle, then perform Absolute Clear and re-home the machine; this alarm cannot clear until Absolute Clear is done.
3. Add battery checks to the PM schedule. If the axis runs as incremental instead, no battery alarms will occur.

Preventive Maintenance for MINAS A6 Drives

• Monthly: blow dust from heatsink fins and fan intakes with dry air; confirm the fan spins freely (a seized fan eventually produces Err15.0 over-heat).
• Quarterly: reseat and inspect encoder and power connectors on vibrating machines; check absolute-battery voltage.
• Semi-annually: verify DC-bus terminal and ground-bond tightness; record no-load current and compare with earlier readings.
• Continuously: export a Panaterm parameter backup after every tuning change, and review the 14-entry error history at each service visit — recurring sub-codes reveal developing faults early.

FAQ

Q: The panel shows Er27.0 on a pulse-train machine. Is the driver faulty?
A: Usually not — Err27.0 is a command pulse input frequency error. Compare the controller's output pulse frequency with the driver's maximum input frequency and your electronic gear setting.

Q: Can I swap an A6B driver for an A6N (RTEX) unit?
A: Not directly. A6B accepts pulse/analog commands while A6N communicates over the RTEX network; the motion controller must match the interface type; cabling and parameters differ.

Q: Which alarms usually mean real hardware damage?
A: Err14.x, Err36–37.x, Err70.x (U/W-phase current detector errors) and encoder alarms that persist with clean wiring indicate failed hardware. Err13.0, Err16.0, Err18.0 and Err24.0 usually reflect operating conditions.

Q: Where can I get tested replacement drivers and encoders?
A: Browse our encoder collection or send us the exact model code (MADLT01SM, MADLT05SM, or your MBDLT module number) and we will quote a tested replacement with a 12-month warranty.