Parker SLVD-N Servo Drive Fault Codes

Troubleshoot your Parker SLVD-N compact servo drive with our updated fault code list. Learn to interpret the 2-digit LED display, use MotionWiz, and resolve common motion errors.

Parker SLVD-N Fault Codes Reference Table

Below is the complete list of fault codes. Please check the numeric value flashing on the front of the drive unit to identify the specific alarm.

Parker SLVD-N Servo Drive Fault Codes

Parker SLVD-N Servo Drive Fault Codes

Fault Code and Meaning Cause and Remedy
0
Drive OK
Cause:
Drive is functioning normally.

Remedy:
None required.
1
Over Voltage on the D.C. Link
Cause:
Voltage on the DC link has exceeded limits.

Remedy:
  • Check the three-phase power line.
  • Check the break circuit and the braking resistor.
2
Under Voltage on the D.C. Link
Cause:
Voltage on the DC link is too low.

Remedy:
  • Check the three-phase power line.
3
Over current
Cause:
Excessive current detected.

Remedy:
  • Check for any mechanical blockage and make sure the motor is the appropriate size for its current use.
  • Check the motor connections and for any phase-phase or phase-ground short-circuits.
  • Check the machine speed and the service cycle.
  • Make sure a line trap isn’t connected to the motor!
4
Resolver
Cause:
Feedback signal issue.

Remedy:
  • Check the connections of the resolver and the connectors on both sides (drive-motor).
5
PTC motor alarm
Cause:
Motor overheating or sensor fault.

Remedy:
  • Check the PTC connection cable.
  • If the alarm persists, disable the drive, remove power from the motor and de-energize the drive (24VDC).
  • Remove the PTC connector from the drive, short-circuit the PTC (connecting PTC+ and PTC-) on the same drive terminal block.
  • Supply power to the drive (24VDC). If the alarm persists, either the drive is in fault state, or the PTC on the motor is in fault state.
  • (At the end of the test, remove the PTC short-circuiting connection).
6
Drive Over Temperature
Cause:
Drive unit is overheating.

Remedy:
  • Check the cooling fans and for any restrictions to air flow.
  • Check the breaking cycle.
  • Check the environmental temperature of the electrical control panel where the drive is installed, as well as the external room temperature.
7
External alarm
Cause:
Triggered by application (see the pico-PLC).

Remedy:
  • Check application specific pico-PLC logic.
8
Auxiliary alarm
Cause:
Triggered by application (see the pico-PLC).

Remedy:
  • Check application specific pico-PLC logic.
10
check sum PLC
Cause:
PLC data corruption or error.

Remedy:
  • Set the default of the drive, save and restart the drive.
  • Reprogramming the drive.
11
check sum parameters
Cause:
Parameter data corruption.

Remedy:
  • Set the default of the drive, save and restart the drive.
  • Reprogramming the drive.
14
Brake overload
Cause:
Braking resistance use overload.

Remedy:
  • Check braking cycle and resistor sizing.
15
Default parameter
Cause:
Parameter error.

Remedy:
  • Reprogramming the drive, save and restart the drive.
17
Calibration error
Cause:
Calibration data invalid.

Remedy:
  • Contact technical support or retry calibration if applicable.
22
Ambient over temperature
Cause:
Ambient temperature too high.

Remedy:
  • Check the temperature of the environment.
24
Braking transistor protection
Cause:
Short-circuit braking resistance.

Remedy:
  • If an external braking resistor is connected to the drive, check the resistor status and wiring.
  • Can be only reset at the next power on.
25
Feedback speed error
Cause:
Issue with speed feedback signal.

Remedy:
  • Check the selection of feedback and the connection.
....
Limitation of current (I²T)
Cause:
The drive goes in I²T mode due to an overload (it required more current that was available).

Remedy:
  • Check the cables between motor and SLVD-N (there should be no inverted phases).
  • Take special care with motors with terminals rather than the connector: it’s easy to make a mistake.
  • Adhere strictly to the wiring diagrams.
  • Check Power limit active (if 1-phase supply: b94.15=1).
 

How to Read Parker SLVD-N Faults via MotionWiz

While the 2-digit LED provides a quick reference, connecting your PC to the drive using the MotionWiz configuration software is the best way to perform deep diagnostics in 2026. Connection is typically established via the RS232 serial interface (using the X10 port).

Key Diagnostic Features:

  • Error Log: MotionWiz provides access to the internal error buffer. This allows you to see not just the current fault, but a historical list of events that may have led to the current trip.
  • Oscilloscope Window: You can trace motor variables such as Phase Current, DC Bus Voltage, and Speed Error. This is essential for troubleshooting intermittent “Error 2” (Overvoltage) or “Error 5” (Ixt) trips caused by aggressive deceleration or mechanical friction.
  • Real-Time Status Bits: The “Drive Status” window in MotionWiz shows the status of internal logic bits, helping you determine if the drive is disabled due to a hardware fault or a missing “Drive Enable” signal from the PLC.

Frequently Asked Questions (FAQ)

Q: What is the difference between an Alarm and a Fault on the SLVD-N?

A:

  • Alarms/Warnings: These indicate the drive is reaching a limit (e.g., motor thermal image) but is still operational. The display may flash a code but the motor keeps running.
  • Faults: These are critical failures that immediately open the power bridge, stopping the motor. The fault code will be locked on the LED display.

Q: How do I reset a Parker SLVD-N fault?

A: Once the cause of the trip is addressed, you can reset the drive by:

  1. Toggling the Alarm Reset digital input (if programmed).
  2. Using the “Reset” command within the MotionWiz software environment.
  3. Cycling the 24V DC control power (terminals 1 and 2 on the X4 connector).

Q: Why is my drive displaying “Error 7” (Resolver/Encoder Error)?

A: This indicates a failure in the feedback loop. Check the feedback cable connections at both the drive (X1) and the motor end. This is often caused by electrical noise interference or a damaged cable shield. Ensure the motor frame is properly grounded.

Q: Where is the fault history stored?

A: The fault history is stored in the drive’s internal non-volatile memory. It can be accessed through the “Diagnostic” menu in MotionWiz or by scrolling through the drive’s internal parameters using the keypad (if an external keypad is attached).

Comments

Popular posts from this blog

Allen Bradley Kinetix 5500 Drive Fault Codes List

Danfoss VACON 100 FLOW Drive Fault Codes List

ABB ACH580 Drive Fault Codes List