Parker TPD-M Servo Drive Fault Codes

Troubleshoot your Parker TPD-M triple-axis servo drive with our updated guide. Learn to use MotionWiz, interpret LED display errors, and manage common DC bus faults.

Parker TPD-M Fault Codes Reference Table

Below is the complete list of fault codes for the TPD-M series. Since this is a multi-axis unit, the display will often cycle through errors for Axis 1, Axis 2, and Axis 3 respectively.

Parker Hannifin TPDM Alarms

Parker Hannifin TPDM Alarms List

Fault Code and Meaning Cause and Remedy
0

No alarm		 Cause: Standard operation status.

Remedy:
  • If Pr24 is not 0, see the "SUB Alarms table" below.
1

DC circuit overvoltage		 Cause: Voltage on DC bus is too high.

Remedy:
  • Check the three-phase power line (max 480V + 10%).
  • Check the brake circuit and the braking resistor.
2

DC circuit undervoltage		 Cause: Voltage on DC bus is too low.

Remedy:
  • Check the three-phase power line.
3

Overcurrent		 Cause: Current exceeds limits, potential short circuit.

Remedy:
  • If Pr24=0 (Overcurrent): Check motor connections and any phase-phase or phase-ground short-circuits.
  • Check the motor data.
  • If Pr24 is not 0: See the "SUB Alarms table" section.
4

FBK error (resolver or encoder)		 Cause: Feedback device signal failure.

Remedy:
  • Check the connections of the speed loop and the connectors on both sides (drive-motor).
  • Check the feedback parameters.
5

PTC motor alarm		 Cause: Motor temperature sensor issue.

Remedy:
  • Check the PTC connection cable.
  • Check parameters Pr33 (Inom) and Pr19 (Ipeak).
6

Power module overtemperature		 Cause: Drive module is overheating.

Remedy:
  • Check the cooling fans and for any restrictions to air flow.
  • Check the braking cycle.
  • Check the ambient temperature in the electric cabinet and outside the cabinet.
7

External alarm		 Cause: Triggered by external input.

Remedy:
  • Depends on the application (b41.7 – see Pico PLC program).
8

Auxiliary alarm		 Cause: Triggered by auxiliary condition.

Remedy:
  • Depends on the application (b41.8 – see Pico PLC program).
10 (*)

Check sum pico-PLC		 Cause: Parameter/Programming checksum error.

Remedy:
  • Set and save default parameters.
  • Switch off and on again the drive.
  • Repeat programming.
11 (*)

Check sum parameters		 Cause: Parameter checksum error.

Remedy:
  • Set and save default parameters.
  • Switch off and on again the drive.
  • Repeat programming.
12

Signature firmware		 Cause: The signature is not installed.

Remedy:
  • Internal issue; send to repair.
13

CANopen DS402 abort connection		 Cause: Communication abort.

Remedy:
  • Check the connections.
15

Default parameters		 Cause: Parameters reset or corrupt.

Remedy:
  • Set and save default parameters.
  • Switch off and on again the drive.
  • Repeat programming.
16

CANopen missing sync		 Cause: Synchronization signal lost.

Remedy:
  • Check the connections.
17 (**)

Hardware alarm		 Cause: Internal hardware damage or fault.

Remedy:
  • Internal damage, send to repair.
  • Refer to the "SUB Alarms table" below for specific code.
22

Ambient over temperature		 Cause: The ambient temperature in the electric cabinet is excessive (>45°C).

Remedy:
  • Check the cooling fans.
  • Check for any restrictions to air flow.
24

PSU alarm		 Cause: Power Supply Unit issue.

Remedy:
  • See the "SUB Alarms table".
25 (**)

Speed loop FBK initialization error		 Cause: Issue during feedback initialization.

Remedy:
  • Check the speed FBK settings.
  • Check the speed FBK connection.
  • Ensure motor shaft is not in movement during start-up.
  • The encoder is not phased. See the procedure.
27

Overloads digital outputs		 Cause: Excessive load on outputs.

Remedy:
  • Check the load of the digital outputs.
31

Communication error		 Cause: Field-bus issue.

Remedy:
  • Check the field-bus connection.
TripP.x

Hardware broken		 Cause: Hardware failure (x is a number).

Remedy:
  • Internal damage, send to repair.
I²T

Current limit (I²T)		 Cause: Drive entered I²T mode due to overload (current required > current supplied).

Remedy:
  • Check wiring between drive and motor (ensure no inverted phases).
  • Take special care with motors where the connector is replaced by a terminal block (easy to mistake).
  • Adhere strictly to wiring diagrams.
  • Check mechanical dimensioning.
Pr23: 0 / Pr24: 4

Serial line error		 Cause: Connection issue.

Remedy:
  • Insert the terminal plug-in.
Pr23: 0 / Pr24: 5

Power supply not 3-phases		 Cause: Phase loss.

Remedy:
  • Check the main supply.
Pr23: 3 / Pr24: 1

Hardware from FPGA		 Cause: Internal hardware signal.

Remedy:
  • (Contact technical support / Check hardware).
Pr23: 3 / Pr24: 2

I2t maximum reached		 Cause: Overload threshold reached.

Remedy:
  • Check load and cooling.
Pr23: 3 / Pr24: 3

Stall status of V/F		 Cause: Motor stalled in V/F mode.

Remedy:
  • Check motor load and mechanics.
Pr23: 17 / Pr24: 1

Different number of axes		 Cause: Configuration mismatch.

Remedy:
  • Internal damage, send to repair.
Pr23: 17 / Pr24: 2

Number of axes configuration		 Cause: Configuration error.

Remedy:
  • Internal damage, send to repair.
Pr23: 17 / Pr24: 3

Feedback configuration		 Cause: Configuration error.

Remedy:
  • Internal damage, send to repair.
Pr23: 17 / Pr24: 4

ADC on FPGA error		 Cause: Conversion error on FPGA.

Remedy:
  • Switch off the drive.
  • Wait one minute before restarting the drive.
Pr23: 17 / Pr24: 5

EEprom error		 Cause: Memory failure.

Remedy:
  • Internal damage, send to repair.
Pr23: 17 / Pr24: 6

FPGA fault		 Cause: Processor fault.

Remedy:
  • Internal damage, send to repair.
Pr23: 17 / Pr24: 7

EEprom checksum error		 Cause: Memory data corruption.

Remedy:
  • Internal damage, send to repair.
Pr23: 17 / Pr24: 8

NIOS SDRAM checksum error		 Cause: RAM data corruption.

Remedy:
  • Internal damage, send to repair.
Pr23: 17 / Pr24: 9

NIOS RAM checksum error		 Cause: RAM data corruption.

Remedy:
  • Internal damage, send to repair.
Pr23: 17 / Pr24: 10

FPGA blocked		 Cause: Processor freeze.

Remedy:
  • Internal damage, send to repair.
Pr23: 17 / Pr24: 11

FPGA watchdog alarm		 Cause: Watchdog timer expiration.

Remedy:
  • Internal damage, send to repair.
Pr23: 17 / Pr24: 12

NIOS watchdog alarm		 Cause: Watchdog timer expiration.

Remedy:
  • Internal damage, send to repair.
 

How to Read Parker TPD-M Faults via MotionWiz

For complex multi-axis troubleshooting in 2026, the MotionWiz configuration software is the primary tool for diagnostics. Connectivity is simplified through the drive’s onboard USB interface, allowing you to monitor all three axes simultaneously from a single PC connection.

Key Diagnostic Features:

  • Multi-Axis Monitoring: MotionWiz allows you to view the status of each axis (Current, Velocity, Position) in a single dashboard. This is critical for identifying if a “DC Bus” fault is being caused by an aggressive move on just one specific axis.
  • SD Card Logging: The TPD-M features a standard SD card interface. You can configure the drive to log parameters and fault history to the card, which is invaluable for capturing intermittent “nuisance” trips that happen during high-speed production cycles.
  • Oscilloscope Trace: Use the MotionWiz digital scope to trigger on a “Drive Fault” bit. By tracing the DC Bus Voltage and Phase Currents, you can determine if a trip was caused by regenerative energy during simultaneous braking of multiple motors.
  • Checksum Diagnostics: If the drive displays “Error 11,” MotionWiz can be used to perform a parameter reset and re-save default values to resolve internal memory checksum conflicts.

Frequently Asked Questions (FAQ)

Q: How do I know which axis is causing the fault?

A: The 7-segment display on the TPD-M typically cycles through the status of each axis. If an axis-specific fault occurs, the display will indicate the axis number followed by the error code (e.g., A1 – 02). In MotionWiz, each axis is clearly labeled with its own status indicator.

Q: What is the most common cause of “DC Bus” faults on TPD-M?

A: Because the TPD-M uses a common DC bus, an Overvoltage trip is often caused by multiple axes decelerating at the same time. Check your shared braking resistor sizing and ensure it is properly wired to the PSU (Power Supply Unit) module.

Q: How do I reset a Parker TPD-M fault?

A: Once the root cause is resolved, you can reset the system by:

  1. Toggling a Digital Input configured for “Alarm Reset” in MotionWiz.
  2. Sending a reset command via the communication network (EtherCAT or CANopen).
  3. Using the “Reset Faults” button in the MotionWiz software.
  4. Cycling the 24V control power to the TPD-M module.

Q: Where is the fault history stored?

A: Fault history can be retrieved through the “Diagnostic” menu in MotionWiz or by accessing the log files stored on the SD card (if an SD card was inserted during the event).

Comments

Post a Comment

Popular posts from this blog

Allen Bradley Kinetix 5500 Drive Fault Codes List

Complete guide to Allen Bradley Kinetix 5500 fault codes. Troubleshoot FLT codes, Single-Cable (DSL) feedback errors, shared bus faults, and perform diagnostics via Studio 5000. Kinetix 5500 Fault Codes Reference Table Kinetix 5500 Fault Codes Reference Table Kinetix 5500 Fault Codes Reference Table Fault Code and Meaning Cause and Remedy FLT S03 – MTR OVERSPEED FL Motor Overspeed Factory Limit Fault Cause: Motor speed has exceeded 125% of its maximum speed. Remedy: Check control loop tuning. FLT S04 – MTR OVERSPEED UL Motor Overspeed User Limit Fault Cause: Motor speed has exceeded motor overspeed user limit. Remedy: Check control loop tuning. Increase the Motor Overspeed UL attribute value. FLT S05 – MTR OVERTEMP FL Motor Overtemperature Factory Limit Fault Cause: Calculations based ...
Read more

Danfoss VACON 100 FLOW Drive Fault Codes List

Access the complete reference guide for Danfoss VACON 100 FLOW drive fault codes. Learn to diagnose Multipump communication errors, dry run faults, and use Vacon Live software. VACON 100 FLOW Fault Codes Reference Table VACON 100 FLOW Faults and Alarms VACON 100 FLOW - Fault Tracing Fault Code and Meaning Cause and Remedy Fault Code 1, ID 1 Overcurrent (Hardware Fault) Cause: There is too high a current (> 4 × IH) in the motor cable. a sudden heavy load increase a short circuit in the motor cables the motor is not the correct type the parameter settings are not properly made Remedy: Check the loading. Check the motor. Check the cables and connections. Make an identification run. Set the acceleration time longer (P3.4.1.2 and P3.4.2.2). Fault Code 1, ID 2 Overcurrent (Software Fault...
Read more

ABB ACH580 Drive Fault Codes List

Access the complete reference guide for ABB ACH580 HVAC drive fault codes. Learn to diagnose issues via the Hand-Off-Auto panel, BACnet integration, and Fireman’s Override. The ABB ACH580 is the industry-standard flagship drive for HVACR applications. Designed to control air handling units, cooling towers, and chillers, it ensures critical comfort and safety in buildings. When a malfunction occurs, the dedicated Hand-Off-Auto (HOA) control panel displays a 4-digit code alongside plain-text diagnostics, often integrated directly into the Building Management System (BMS). This guide provides the most updated reference to help you interpret these codes and maintain building environmental standards. ACH580 Fault Codes Reference Table Use the search bar below or browse the table to identify your specific error code: ABB ACH580 Drive Fault Codes List ABB ACH580 Drive Fault Codes List Fault Code and Meaning Cause and Remedy A2B1...
Read more