Parker TPD-M Servo Drive

Parker TPD-M Servo Drive Fault Codes:

Fault Code and MeaningCause 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.