Mazak Servo Parameter Error Fix (Matrix, M-Plus, Smooth)

Quick answer

A Mazak servo parameter error (variously labeled “Servo Parameter Error,” Alarm 1280, Alarm 13, “PARAM SET,” or shown as a drive-side AL on the MDS 7-segment with sub-codes 37/38/40-family) means the servo drive received a parameter from the NC that it cannot accept — wrong motor code, wrong encoder code, wrong gain set, wrong axis assignment, or a corrupted parameter file after a board swap or battery loss. This is not a hardware failure — it’s a configuration mismatch, and the fix is almost always restoring from a verified parameter backup.

What a Mazak Servo Parameter Error means

Mazak Matrix, Matrix Nexus, M-Plus, and Smooth controls all share a common architecture: the NC stores servo parameters as a structured block per axis, and on every power-up the NC pushes those parameters to each MDS series drive over the high-speed servo bus (SSCNET on Matrix and Smooth — proprietary serial on older M-Plus). The drive validates every parameter against its own motor/encoder code table. If the NC sends an SV001 (motor type) value the drive doesn’t recognize, or SV017 (encoder code) doesn’t match the encoder actually plugged into CN2, or any rate-of-change limit (SV005, SV007) is set outside the legal range, the drive refuses to enable and reports a parameter alarm back to the NC.

The NC then posts one of several different messages depending on platform:

• Matrix / Matrix Nexus: Alarm 1280 with axis name, or “SV PARAM” in the system message bar
• Smooth (G/X/Ai): Servo Parameter Error with sub-code; drive AL number visible on cabinet drive face
• M-Plus / M-Plus Junior: Alarm 13 “PARAM SET” or NC-side “SERVO PARAM”
• M32: “SERVO PARAM” message with axis indicator

The MDS drive’s 7-segment display shows an AL plus a sub-code that pinpoints which parameter group failed validation. The common sub-codes are:

• AL 37 — motor type mismatch (SV001 / motor code wrong)
• AL 38 — encoder type mismatch (SV017 / encoder code wrong)
• AL 40 — invalid parameter value (typically gain too high or too low)
• AL 36 — parameter checksum failure (parameter memory corrupt)
• AL E3 / E4 — parameter received before initialization complete (timing problem, often after a drive swap)

This alarm is always about software configuration, not hardware. Even AL 36 (checksum failure) — while it can be triggered by failing parameter memory in the drive — is far more often caused by an interrupted parameter write (power glitch during boot, or an aborted parameter download).

Read the alarm history first

This is critical for parameter errors specifically because the alarm history will tell you whether the error appeared after a known event (someone touched the drive, swapped a board, restored parameters) or out of nowhere.

On Matrix and Matrix Nexus:

1. Press Alarm, then Alarm History
2. Find the parameter-error entry. Note the date/time and the axis
3. Look in the same window for any preceding 1041/1042 (battery), 415 (position detector), or system messages about parameter download
4. Press the soft key for Drive Sub-Code — on Matrix firmware after 2015 this displays the drive’s AL sub-code in the alarm detail
5. Cross-reference against your shop’s maintenance log — was anyone in this cabinet recently?

On Smooth:

1. Maintenance → History → Alarm, filter for Servo
2. The detail pane shows drive sub-code
3. Maintenance → Servo → Parameter Compare (on later Smooth) compares NC parameters against drive parameters and highlights mismatches in red

On M-Plus / M32:

1. OPER ALM key, page back through history
2. The MDS-A/B drive’s two-character display shows AL + sub-code — read it directly on the drive face
3. Cross-reference sub-code against the MDS-A/B service manual alarm list

Field insight — the one nugget that traps everyone on Mazak servo parameter errors: when you swap a servo drive (MDS-DH-V2 or similar), the new drive arrives from the spare-parts shelf with factory default parameters, not the parameters this specific machine and axis need. On a healthy machine, the NC pushes the correct parameters to the drive on power-up and overwrites the defaults — that’s how the system is designed. But on Matrix firmware before service pack rev D (approximately 2014), there’s a race condition where the drive sometimes finishes its boot before the NC has finished its boot, and the drive throws AL 36 or AL E3 before parameters arrive. The fix is not to replace the drive again — it’s to power-cycle the machine, which sequences NC and drive boots correctly. I’ve seen techs swap three drives chasing this before someone old enough remembered the workaround.

Common causes (ranked by frequency)

1. Recent servo drive swap with factory-default parameters and no parameter download — drive boots with defaults, doesn’t match motor/encoder, throws AL 37/38
2. Recent NC board swap or parameter clear without restoring from backup — NC has nothing to send, drive errors out
3. Lost or weak NC parameter battery (separate from encoder battery) that allowed parameter memory to corrupt during a power-off period
4. Aborted parameter download — someone started a parameter restore via the maintenance menu, machine power-cycled mid-write, parameter file is now half-old half-new and fails checksum
5. Mismatched motor swap — replacement motor on the spare-parts shelf is the right physical form factor but a different model code (HC152 vs HC202 for example); drive throws AL 37
6. Encoder cable connected to the wrong axis after a multi-axis disconnect during head removal — drive sees encoder it doesn’t expect, throws AL 38

Step-by-step diagnosis

Standard CNC safety: lock and tag the disconnect, wait 5 minutes for bus capacitors to discharge, verify zero energy. For any axis with a mechanical brake or that can drop under gravity (vertical Z, Variaxis B-axis tilted, ATC magazine), set the brake or use mechanical blocking before working on motor connections.

Critical prerequisite: locate a verified parameter backup before you start. The single most valuable artifact for this alarm is a known-good parameter file from this specific machine. Mazak supplies parameter backup procedures in the maintenance manual — your shop should have a backup taken at machine commissioning and refreshed after any parameter change. If you don’t have one, the recovery path is much longer (contact Mazak service to pull factory parameters by serial number).

1. Capture all current alarm detail. NC alarm number, axis name, drive 7-segment AL sub-code. Photograph the drive display. Read drive parameters from the NC’s parameter-display menu if possible (path varies by platform).

2. Establish: when did this last work? If the error appeared after a service event (drive swap, NC swap, battery replacement, parameter operation), the answer is almost always to restore parameters from backup. If it appeared after a power-off period with no service event, suspect parameter memory corruption from a failing NC battery.

3. For AL 37 (motor type mismatch): check the motor nameplate against the parameter SV001. If they disagree, either the wrong motor was installed or the parameter is wrong. Restore parameters from backup if the motor is correct for this machine. If the motor itself is wrong (replacement from spare-parts shelf was a different model code), you need the correct motor or you need to reconfigure parameters for the substitute motor — Mazak service controls that reconfiguration.

4. For AL 38 (encoder type mismatch): verify the encoder cable is connected to the correct drive (axis X cable to X drive, not Y drive). If multiple cables were disconnected during head service and one got swapped, the symptoms include AL 38 on the swapped axis and often AL 38 on its partner axis as well.

5. For AL 36 (checksum): restore parameters from backup. The procedure on Matrix is Maintenance → Parameter → Restore from External Memory with a USB or CF card containing the backup file. Follow Mazak’s documented procedure — do not interrupt the write.

6. For AL E3/E4 (timing): power-cycle the entire machine at the main disconnect. Wait 30 seconds after the cabinet fans stop. Power back up. If the alarm clears, you’ve hit the boot-sequence race condition — note it in the log but do not chase further. If the alarm persists, treat as AL 36 (restore parameters).

7. Verify backup integrity before restoring. A parameter backup file should be the right size (Matrix backups are typically 2–4 MB depending on options) and dated before the failure. Restoring from a backup that’s older than a known parameter change is fine — you’ll just re-do those changes — but restoring from a backup taken after the corruption is worse than no backup at all.

8. Restore parameters per Mazak procedure. Maintenance manual section “Parameter Backup and Restore.” Do not abort. After restore, cycle power once. Confirm all servo axes enable cleanly.

9. After successful restore, re-establish reference position if any axis lost absolute position during the event. Use the documented reference-return procedure for each axis. Verify first-article on a known part before releasing the machine back to production.

Parts that may need replacement

Parameter errors rarely require parts. The main exceptions are NC parameter memory battery (different from encoder battery) and the servo drive itself if its parameter memory is failing.

When to call a CNC service engineer

Call when: you do not have a verified parameter backup for this machine and parameters need to be restored — Mazak can pull factory parameters by serial number, but the procedure requires their proprietary diagnostic software; the error persists after a verified-good parameter restore and a known-good drive swap, suggesting an NC board or cable problem; you need to substitute a different motor model code and reconfigure servo parameters (this is not a field-level adjustment — gains have to be retuned and stability verified); or you’ve crossed into territory where you need to re-establish absolute reference on multiple axes simultaneously (5-axis machines especially), which is faster to do with factory support than from the manual.

FAQs

Reference Mazak Maintenance Manual section? “Parameter Operations / Parameter Backup and Restore” in the Matrix and Smooth maintenance manuals. The drive AL sub-code list is in the Mitsubishi MDS-D/DH Series Service Manual (Mazak-branded copy), section “Alarm Code List.”

Can I restore parameters from a sister machine? Only if the machines are the identical configuration — same model, same options, same servo axes, same software revision. Even small differences (different turret, different ATC, different B-axis configuration) will cause some parameters to be wrong. Worth trying as a stopgap only if you cannot get the correct file otherwise — and do not run production until verified.

Will parameter restore lose my offsets? No. Servo parameters and work offsets are stored separately. Restoring servo parameters does not touch G54-G59 offsets, tool offsets, or part programs.

My parameter error fires only after weekend shutdowns. Is this a battery problem? Almost certainly. Long power-off periods drain the NC parameter backup battery faster than short shutdowns. Replace the NC board coin cell on a 2-year interval. Note this is a different battery from the encoder backup pack.

Difference between Alarm 1280 and a drive AL 37? 1280 is the NC’s posting of a generic parameter error. AL 37 is the drive’s specific sub-code telling you which parameter group failed (motor type in this case). Always read both — the drive’s sub-code is the actionable diagnostic.

Related guides

• Mazak Alarm 218 — Spindle Motor Overheat Fix
• Mazak Alarm 415 — Position Detector Error Fix
• Mazak Matrix Alarm 1041 — Battery Voltage Drop Fix
• Fanuc Alarm 300 — APC Battery Voltage Low Fix
• Fanuc Alarm 414 — Servo Digital Alarm Fix
• Fanuc Alarm 401 — Servo Amp Ready Off Fix

See Also

• Mazak Alarm 700 — MPC Alarm
• Mazak Alarm 218 — Spindle Motor Overheat Fix
• Mazak Matrix Alarm 1041 — Battery Voltage Drop / Encoder Battery Fix
• Mazak Alarm 1 Servo Alarm — Causes & Fix