GA37 Troubleshooting Guide

VSD/Elektronikon Model Fault Control Type / Series
MKIII and Siemens MasterDrive "Blank Screen" All Mk III Elektronikons
MKIII and Siemens MasterDrive 0 All Siemens VSD.

This is not really a fault.
MKIII and Siemens MasterDrive 10 Elektronikon Mk III LRR V1.8,

2.3
HRR

2.3
2.3
2.3
2.3
2.3, HRR
2.3
HRR

2.3
2.3
MKIII and Siemens MasterDrive 109 Elektronikon Mk III LRR V 2.3
MKIII and Siemens MasterDrive 10XX Elektronikon Mk III LRR/HRR

2.3, HRR
MKIII and Siemens MasterDrive 11XX Elektronikon Mk III HRR

2.3
2.3
2.3
MKIII and Siemens MasterDrive 15 Elektronikon Mk III LRR V 2.3
MKIII and Siemens MasterDrive 17 Elektronikon Mk III LRR V1.8
MKIII and Siemens MasterDrive 200 Elektronikon Mk III LRR V

2.3, HRR
MKIII and Siemens MasterDrive 2000 Elektronikon Mk III LRR/HRR
MKIII and Siemens MasterDrive 2001 Elektronikon Mk III HRR

2.3, HRR
2.3, HRR



MKIII and Siemens MasterDrive 37 Elektronikon Mk III -

GA90VSD Simovert P

MKIII and Siemens MasterDrive 53 Elektronikon Mk III HRR /
VSD

VSD

VSD
MKIII and Siemens MasterDrive 70XX Elektronikon Mk III HRR /

VSD

VSD
VSD

VSD

VSD
VSD
VSD
VSD

VSD
SIEMENS / ABB

VSD
SIEMENS / ABB
VSD
SIEMENS / ABB
MKIII and Siemens MasterDrive 7601 HRR / VSD - Masterdrive

(CUVC) Series
MKIII and Siemens MasterDrive A015 MasterDrive Series - CUVC
MKIII and Siemens MasterDrive A017 Masterdrive / CUVC, CU2

MKIII and Siemens MasterDrive E All masterdrive CUVC series -

GA30VSD . . .
MKIII and Siemens MasterDrive F0 GA50VSD - CU2

MKIII and Siemens MasterDrive F001 Siemens CU2, CUVC
MKIII and Siemens MasterDrive F002 Siemens MasterDrive Series

CU2, CUVC
MKIII and Siemens MasterDrive F006 Siemens CUVC (MasterDrive)

MKIII and Siemens MasterDrive F011 Siemens CUVC
(MasterDrive), CU2

MKIII and Siemens MasterDrive F021 Siemens, CUVC
MKIII and Siemens MasterDrive F023 Siemens converter, CUVC

CUVC
CUVC
CUVC

CUVC
MKIII and Siemens MasterDrive F029 Siemens, all VSD's except

GA90VSD Simovert P
MKIII and Siemens MasterDrive F035 VSD - Siemens CUVC / CU2
MKIII and Siemens MasterDrive F036 AIF VSD - Siemens CUVC

ZT37VSD
GA50VSD
GA50VSD
GA50VSD

GA50VSD
GA50VSD

GA50VSD
GA50VSD
GA50VSD
MKIII and Siemens MasterDrive F1 Siemens CCU - Simovert P
GA90VSD
MKIII and Siemens MasterDrive F100 Siemens CUVC, CU2


MKIII and Siemens MasterDrive F12 Siemens CCU - Simovert P -
6SE13 . . .
GA90VSD

6SE13 . . .
GA90VSD
6SE13 . . .
GA90VSD
MKIII and Siemens MasterDrive F148 CUVC Series - ZR160VSD

(ECB1397/C1 implemented)

6SE13 . . .
GA90VSD
MKIII and Siemens MasterDrive F243 MasterDrive VSD

CUVC
MKIII and Siemens MasterDrive F255 MasterDrive VSD

CUVC
CUVC

CUVC

CUVC
MKIII and Siemens MasterDrive F3 Siemens CCU - Simovert P

GA90VSD

6SE13 . . .
GA90VSD
MKIII and Siemens MasterDrive F35 VSD - Siemens CUVC / CU2
MKIII and Siemens MasterDrive F36 AIF VSD - Siemens CUVC
ZT37VSD
MKIII and Siemens MasterDrive F37 Elektronikon Mk III -

GA90VSD Simovert P

GA50VSD
GA50VSD
GA50VSD

GA50VSD
GA50VSD
GA50VSD
GA50VSD
GA50VSD
6SE13 . . .
GA90VSD
6SE13 . . .
GA90VSD
6SE13 . . .
GA90VSD
MKIII and Siemens MasterDrive F8 GA50VSD - CU2, CUVC

GA90VSD - CCU / Simovert
MKIII and Siemens MasterDrive Internal Fault # 1 Elektronikon Mk IV - II or

Higher
ABB ACS600 "Blank Screen" All Mk III Elektronikons
ABB ACS600 100 Elektronikon Mk III, LRR

V1.8, 2.3
V1.8, 2.3
V1.8, 2.3
V1.8, 2.3
ABB ACS600 104 Elektronikon Mk III LRR V1.8,
2.3, HRR

V1.8, 2.3
HRR

V1.8, 2.3
V1.8, 2.3
ABB ACS600 109 Elektronikon Mk III, LRR V
2.3
ABB ACS600 10XX Elektronikon Mk III -
LRR/HRR
V1.8, 2.3, HRR
ABB ACS600 11XX Elektronikon Mk III - HRR

V1.8, 2.3

V1.8, 2.3

V1.8, 2.3

2.3
ABB ACS600 17 Elektronikon Mk III, LRR V1.8

2.3, HRR
ABB ACS600 2000 Elektronikon Mk III -
LRR/HRR
ABB ACS600 2001 Elektronikon Mk III - HRR
2.3, HRR
2.3, HRR


ABB ACS600 30XX Elektronikon Mk III, LRR
V1.8, 2.3, HRR

ABB ACS600 7001 Elektronikon Mk III HRR /

VSD
ABB ACS600 70XX Elektronikon Mk III HRR /
VSD

VSD
VSD

VSD

VSD
ABB ACS600 7301 Elektronikon Mk III - HRR /

VSD
ABB

VSD
ABB

VSD
ABB
ABB ACS600 74XX Elektronikon Mk III - HRR /

VSD
ABB
ABB ACS600 FAULT: ACS 600 TEMP ABB VSD
ABB ACS600 FAULT: Al < MIN FUNC ABB VSD
ABB ACS600 FAULT: AMBIENT TEMP ABB VSD

ABB ACS600 FAULT: COMM MODULE ABB VSD
ABB ACS600 FAULT: CURR MEAS ABB VSD

ABB ACS600 FAULT: DC OVERVOLT ABB VSD
ABB ACS600 FAULT: DC UNDERVOLT ABB VSD
ABB ACS600 FAULT: EARTH FAULT ABB VSD
ABB ACS600 FAULT: EXTERNAL FLT ABB VSD
ABB ACS600 FAULT: I/O COMM ABB VSD
ABB ACS600 FAULT: ID RUN FAIL ABB VSD
ABB ACS600 FAULT: IN CHOKE TEMP ABB VSD
ABB ACS600 FAULT: LINE CONV ABB VSD
ABB ACS600 FAULT: MOTOR 1 TEMP ABB VSD
ABB ACS600 FAULT: MOTOR 2 TEMP ABB VSD

ABB ACS600 FAULT: MOTOR PHASE ABB VSD
ABB ACS600 FAULT: MOTOR STALL ABB VSD
ABB ACS600 FAULT: MOTOR STALL ABB VSD
ABB ACS600 FAULT: MOTOR TEMP ABB VSD
ABB ACS600 FAULT: NO MOT DATA ABB VSD

ABB ACS600 FAULT: OVERCURRENT ABB VSD
ABB ACS600 FAULT: OVERFREQ ABB VSD
ABB ACS600 FAULT: PANEL LOSS ABB VSD
ABB ACS600 FAULT: PPCC LINK ABB VSD

ABB ACS600 FAULT: RUN DISABLE ABB VSD
ABB ACS600 FAULT: SC (INU 1) ABB VSD

ABB ACS600 FAULT: SHORT CIRC ABB VSD
ABB ACS600 FAULT: START INHIBIT ABB VSD

ABB ACS600 FAULT: START INTERLOCK ABB VSD
ABB ACS600 FAULT: SUPPLY PHASE ABB VSD
ABB ACS600 FAULT: THERMISTOR ABB VSD
ABB ACS600 FAULT: UNDERLOAD ABB VSD
ABB ACS600 FAULT: USER MACRO ABB VSD

ABB ACS600 WARNING: ACS 600 TEMP ABB VSD
ABB ACS600 WARNING: Al < MIN FUNC ABB VSD

ABB ACS600 WARNING: COMM MODULE ABB VSD
ABB ACS600 WARNING: DOWNLOAD ABB VSD

FAILED
ABB ACS600 WARNING: DRIVE ABB VSD

INCOMPATIBLE
DOWNLOADING NOT POSS.
ABB ACS600 WARNING: DRIVE RUNNING ABB VSD
DOWNLOAD NOT POSS.
ABB ACS600 WARNING: ENCODER ERR ABB VSD
ABB ACS600 WARNING: ID DONE ABB VSD
ABB ACS600 WARNING: ID DONE ABB VSD
ABB ACS600 WARNING: ID MAGN ABB VSD
ABB ACS600 WARNING: ID MAGN REQ ABB VSD
ABB ACS600 WARNING: ID N CHANGED ABB VSD
ABB ACS600 WARNING: ID RUN ABB VSD

ABB ACS600 WARNING: ID RUN SEL ABB VSD
ABB ACS600 WARNING: MACRO CHANGE ABB VSD
ABB ACS600 WARNING: MOTOR STALL ABB VSD
ABB ACS600 WARNING: MOTOR STARTS ABB VSD
ABB ACS600 WARNING: MOTOR TEMP ABB VSD
ABB ACS600 WARNING: NO ABB VSD

COMMUNICATION (X)
ABB ACS600 WARNING: NO FREE ID ABB VSD

NUMBERS ID NUMBER
SETTING NOT POSS.
ABB ACS600 WARNING: NOT UPLOADED ABB VSD
DOWNLOADING NOT POSS.
ABB ACS600 WARNING: PANEL LOSS ABB VSD
ABB ACS600 WARNING: THERMISTOR ABB VSD
ABB ACS600 WARNING: UNDERLOAD ABB VSD
ABB ACS600 WARNING: UPLOAD FAILED ABB VSD
ABB ACS600 WARNING: WRITE ACCESS ABB VSD

DENIED PAR. SETT. NOT
POSSIBLE
ABB ACS550 1 ACS550

FDVSD
ABB ACS550 2 ACS550

FDVSD
ABB ACS550 3 ACS550

FDVSD
ABB ACS550 4 ACS550

FDVSD
ABB ACS550 5 ACS550

FDVSD
ABB ACS550 6 ACS550
FDVSD
ABB ACS550 7 ACS550

FDVSD
ABB ACS550 8 ACS550
FDVSD
ABB ACS550 9 ACS550

FDVSD
ABB ACS550 10 ACS550

FDVSD

FDVSD

FDVSD

FDVSD
FDVSD
FDVSD
FDVSD

FDVSD
FDVSD
FDVSD

FDVSD

FDVSD

FDVSD

FDVSD
FDVSD

FDVSD
FDVSD
FDVSD
FDVSD

FDVSD
FDVSD
FDVSD
FDVSD
FDVSD
FDVSD

FDVSD

FDVSD

FDVSD

FDVSD
ABB ACS550 101 . . . 199 ACS550
FDVSD
ABB ACS550 201 . . . 299 ACS550
FDVSD
ABB ACS550 - ACS550
FDVSD
FDVSD

FDVSD
FDVSD
FDVSD

FDVSD

FDVSD

FDVSD

FDVSD

FDVSD
FDVSD
ABB ACS550 1010 /1011 ACS550

FDVSD
FDVSD

FDVSD

FDVSD

FDVSD
FDVSD
FDVSD

FDVSD

FDVSD
FDVSD

FDVSD

FDVSD

FDVSD

FDVSD

FDVSD

FDVSD

FDVSD

FDVSD
ABB ACS550 2013 (note 1) ACS550
FDVSD
ABB ACS550 2014 (note 2) ACS550
FDVSD
FDVSD
ABB ACS550 2016/2017 ACS550
FDVSD
ABB ACS550 2018 ( note 1) ACS550
FDVSD
FDVSD
FDVSD
FDVSD

FDVSD

FDVSD
FDVSD
FDVSD
ABB ACS800 ACS800 TEMP ACS800
ABB ACS800 ACS TEMP xx y ACS800
ABB ACS800 AI < MIN FUNC ACS800
ABB ACS800 BACKUP ERROR ACS800

ABB ACS800 BC OVERHEAT ACS800
ABB ACS800 BC SHORT CIR ACS800
ABB ACS800 BRAKE ACKN ACS800
ABB ACS800 BR BROKEN ACS800
ABB ACS800 BR OVERHEAT ACS800
ABB ACS800 BR WIRIN ACS800
ABB ACS800 CHOKE OTEMP ACS800
ABB ACS800 COMM MODULE ACS800
ABB ACS800 CTRL B TEMP ACS800
ABB ACS800 CURR MEAS ACS800

ABB ACS800 CUR UNBAL xx ACS800
ABB ACS800 DC HIGH RUSH ACS800
ABB ACS800 DC OVERVOLT ACS800
ABB ACS800 DC UNDERVOLT ACS800
ABB ACS800 ENCODER A<>B ACS800
ABB ACS800 ENCODER FLT ACS800
ABB ACS800 EXTERNAL FLT ACS800
ABB ACS800 FAN OVERTEMP ACS800

ABB ACS800 INT CONFIG ACS800
ABB ACS800 I/O COMM ERR ACS800
ABB ACS800 LINE CONV ACS800
ABB ACS800 MOTOR PHASE ACS800
ABB ACS800 MOTOR STALL ACS800
ABB ACS800 MOTOR TEMP ACS800
ABB ACS800 MOTOR 1 TEMP ACS800
ABB ACS800 MOTOR 2 TEMP ACS800

ABB ACS800 NO MOT DATA ACS800
ABB ACS800 OVERCURR xx ACS800
ABB ACS800 OVERCURRENT ACS800
ABB ACS800 OVERFREQ ACS800
ABB ACS800 PANEL LOSS ACS800
ABB ACS800 PPCC LINK xx ACS800
ABB ACS800 RUN DISABLE ACS800
ABB ACS800 SC INV xx y ACS800

ABB ACS800 SHORT CIRC ACS800
ABB ACS800 SLOT OVERLAP ACS800
ABB ACS800 START INHIBI ACS800
ABB ACS800 SUPPLY PHASE ACS800
ABB ACS800 THERMAL MODE ACS800
ABB ACS800 THERMISTOR ACS800
ABB ACS800 UNDERLOAD ACS800
ABB ACS800 USER L CURVE ACS800
ABB ACS800 USER MACRO ACS800

ABB ACS800 DC BUS LIM ACS800
ABB ACS800 EARTH FAULT
ABB ACS800 4210 (ACS800 TEMP) ACS800
ABB ACS800 2330 (EARTH FAULT)
ABB ACS800 3211 (DC BUS LIM) ACS800
ABB ACS800 FFA1 (USER MACRO) ACS800
ABB ACS800 8110 (AI < MIN FUNC) ACS800

ABB ACS800 7114 (BC OVERHEAT) ACS800
ABB ACS800 7113 (BC SHORT CIR) ACS800
ABB ACS800 FF74 (BRAKE ACKN) ACS800
ABB ACS800 7110 (BR BROKEN) ACS800
ABB ACS800 7112 (BR OVERHEAT) ACS800
ABB ACS800 7111 (BR WIRIN) ACS800
ABB ACS800 FF82 (CHOKE OTEMP) ACS800
ABB ACS800 7510 (COMM MODULE) ACS800
ABB ACS800 4110 (CTRL B TEMP) ACS800
ABB ACS800 2211 (CURR MEAS) ACS800

ABB ACS800 CUR UNBAL xx ACS800
ABB ACS800 FF80 (DC HIGH RUSH) ACS800
ABB ACS800 7302 (ENCODER A<>B) ACS800
ABB ACS800 7301 (ENCODER FLT) ACS800
ABB ACS800 9000 (EXTERNAL FLT) ACS800
ABB ACS800 FF83 (FAN OVERTEMP) ACS800
ABB ACS800 FORCED TRIP ACS800
ABB ACS800 ID RUN FAIL ACS800
ABB ACS800 5410 (INT CONFIG) ACS800

ABB ACS800 INV DISABLED ACS800
ABB ACS800 7000 (I/O COMM ERR) ACS800
ABB ACS800 FF51 (LINE CONV) ACS800
ABB ACS800 FF56 (MOTOR PHASE) ACS800
ABB ACS800 7121 (MOTOR STALL) ACS800
ABB ACS800 4310 (MOTOR TEMP) ACS800
ABB ACS800 4312 (MOTOR 1 TEMP) ACS800
ABB ACS800 4313 (MOTOR 2 TEMP) ACS800
ABB ACS800 FF52 (NO MOT DATA) ACS800

ABB ACS800 2310 (OVERCURR xx) ACS800
ABB ACS800 2310 (OVERCURRENT) ACS800
ABB ACS800 OVERFREQ ACS800
ABB ACS800 5300 (PANEL LOSS) ACS800
ABB ACS800 POWERF INT xx ACS800
ABB ACS800 POWERF INT ACS800
ABB ACS800 5120 (PPCC LINK) ACS800
ABB ACS800 PP OVERLOAD ACS800

ABB ACS800 2340 (SC INV xx y) ACS800
ABB ACS800 2340 (SHORT CIRC) ACS800
ABB ACS800 FF8A (SLOT OVERLAP) ACS800
ABB ACS800 3130 (SUPPLY PHASE) ACS800
ABB ACS800 TEMP DIF xx y ACS800
ABB ACS800 FF50 (THERMAL MODE) ACS800
ABB ACS800 4311 (THERMISTOR) ACS800
ABB ACS800 FF6A (UNDERLOAD) ACS800

ABB ACS850 0064
ABB ACS850 0065
ABB ACS850 0066
ABB ACS850 0067
ABB ACS850 0068
ABB ACS850 0069
ABB ACS850 0070
ABB ACS850 0071
ABB ACS850 0072
ABB ACS850 0073
ABB ACS850 0074
ABB ACS850 0075
ABB ACS850 0201
ABB ACS850 0202

ABB ACS850 0203
ABB ACS850 0204
ABB ACS850 0205
ABB ACS850 0206
ABB ACS850 0207
ABB ACS850 0208
ABB ACS850 0209
ABB ACS850 0210
ABB ACS850 0301
ABB ACS850 0302
ABB ACS850 0303
ABB ACS850 0304
ABB ACS850 0305
ABB ACS850 0306
ABB ACS850 0307
ABB ACS850 0308

ABB ACS850 0309
ABB ACS850 0310
ABB ACS850 0311
ABB ACS850 0312
ABB ACS850 0313
ABB ACS850 0314
ABB ACS850 0315
ABB ACS850 0316
ABB ACS850 0317
ABB ACS850 0318
ABB ACS850 2000 (alarm) ABB ACS850
ABB ACS850 2001 (alarm)







ABB ACS850 0001
ABB ACS850 0002
ABB ACS850 0004
ABB ACS850 0005

ABB ACS850 0006
ABB ACS850 0007
ABB ACS850 0008
ABB ACS850 0009
ABB ACS850 0010
ABB ACS850 0011
ABB ACS850 0012
ABB ACS850 0013
ABB ACS850 0014
ABB ACS850 0015

ABB ACS850 0016
ABB ACS850 0017
ABB ACS850 0018
ABB ACS850 0019
ABB ACS850 0020
ABB ACS850 0021
ABB ACS850 0022
ABB ACS850 0023

ABB ACS850 0024
ABB ACS850 0025
ABB ACS850 0026
ABB ACS850 0027
ABB ACS850 0028
ABB ACS850 0030
ABB ACS850 0031
ABB ACS850 0032

ABB ACS850 0033
ABB ACS850 0034
ABB ACS850 0035
ABB ACS850 0036
ABB ACS850 0037
ABB ACS850 0038
ABB ACS850 0039
ABB ACS850 0040
ABB ACS850 0045

ABB ACS850 0046
ABB ACS850 0047
ABB ACS850 0049
ABB ACS850 0050
ABB ACS850 0051
ABB ACS850 0052
ABB ACS850 0053
ABB ACS850 0054
ABB ACS850 0055
ABB ACS850 0056
ABB ACS850 0057

ABB ACS850 0058
ABB ACS850 0059
ABB ACS850 0060
ABB ACS850 0061
ABB ACS850 0062
ABB ACS850 0063
ABB ACS850 fluctuating speed
ABB ACS880 A2A1

ABB ACS880 A2B1
ABB ACS880 A2B3
ABB ACS880 A2B4
ABB ACS880 A2BA

ABB ACS880 A3A1
ABB ACS880 A3A2
ABB ACS880 A3AA
ABB ACS880 A480
ABB ACS880 A490
ABB ACS880 A490

ABB ACS880 A491
ABB ACS880 A492
ABB ACS880 A4A0
ABB ACS880 A4A1
ABB ACS880 A4A9
ABB ACS880 A4B0

ABB ACS880 A4B1
ABB ACS880 A4B2
ABB ACS880 A4F6
ABB ACS880 A580
ABB ACS880 A581

ABB ACS880 A582
ABB ACS880 A5A0
ABB ACS880 A5EA
ABB ACS880 A5EB
ABB ACS880 A5EC
ABB ACS880 A5ED
ABB ACS880 A5EE

ABB ACS880 A5EF
ABB ACS880 A5F0
ABB ACS880 A5F3
ABB ACS880 A683

ABB ACS880 A684
ABB ACS880 A685

ABB ACS880 A6A4
ABB ACS880 A6A4
ABB ACS880 A6A5
ABB ACS880 A6D1
ABB ACS880 A6D2
ABB ACS880 A6E5

ABB ACS880 A780
ABB ACS880 A781
ABB ACS880 A782
ABB ACS880 A782
ABB ACS880 A791
ABB ACS880 A793
ABB ACS880 A794

ABB ACS880 A797
ABB ACS880 A79B
ABB ACS880 A79C
ABB ACS880 A7A1
ABB ACS880 A7A2
ABB ACS880 A7A5

ABB ACS880 A7AA
ABB ACS880 A7AB
ABB ACS880 A7B0
ABB ACS880 A7B1
ABB ACS880 A7C1

ABB ACS880 A7C2
ABB ACS880 A7CB
ABB ACS880 A7CE
ABB ACS880 A7E1
ABB ACS880 A7EE
ABB ACS880 A880
ABB ACS880 A881
ABB ACS880 A882
ABB ACS880 A883

ABB ACS880 A884
ABB ACS880 A885
ABB ACS880 A886
ABB ACS880 A887
ABB ACS880 A888
ABB ACS880 A889
ABB ACS880 A88A
ABB ACS880 A88B
ABB ACS880 A88C
ABB ACS880 A88D
ABB ACS880 A88E

ABB ACS880 A88F
ABB ACS880 A890
ABB ACS880 A8A0
ABB ACS880 A8B0
ABB ACS880 A8B1
ABB ACS880 A8B2
ABB ACS880 A8C0
ABB ACS880 A981

ABB ACS880 A982
ABB ACS880 A983
ABB ACS880 A984
ABB ACS880 A985
ABB ACS880 AF80
ABB ACS880 AF85
ABB ACS880 AF8C

ABB ACS880 AF90
ABB ACS880 AFAA
ABB ACS880 AFE1
ABB ACS880 AFE2
ABB ACS880 AFE7
ABB ACS880 AFEA
ABB ACS880 AFEB
ABB ACS880 AFEC
ABB ACS880 AFF6

ABB ACS880 AFF7
ABB ACS880 B5A0
ABB ACS880 2281
ABB ACS880 2310

ABB ACS880 2330
ABB ACS880 2340
ABB ACS880 2381
ABB ACS880 2391

ABB ACS880 2392
ABB ACS880 3130
ABB ACS880 3180
ABB ACS880 3181
ABB ACS880 3181
ABB ACS880 3181
ABB ACS880 3210
ABB ACS880 3220
ABB ACS880 3280

ABB ACS880 3291
ABB ACS880 3381
ABB ACS880 3385
ABB ACS880 4000
ABB ACS880 4210
ABB ACS880 4290
ABB ACS880 42F1
ABB ACS880 4310
ABB ACS880 4380

ABB ACS880 4381
ABB ACS880 4981
ABB ACS880 5080

ABB ACS880 5081
ABB ACS880 5090
ABB ACS880 5091
ABB ACS880 5092

ABB ACS880 5093
ABB ACS880 5094
ABB ACS880 5681
ABB ACS880 5681
ABB ACS880 5682
ABB ACS880 5690

ABB ACS880 5691
ABB ACS880 5692
ABB ACS880 5693

ABB ACS880 5694
ABB ACS880 5695
ABB ACS880 5696
ABB ACS880 5697
ABB ACS880 5698
ABB ACS880 6000
ABB ACS880 6181
ABB ACS880 6306
ABB ACS880 6307
ABB ACS880 6481
ABB ACS880 6487
ABB ACS880 64A1
ABB ACS880 64A2

ABB ACS880 64A3
ABB ACS880 64A5

ABB ACS880 64B0
ABB ACS880 64B1
ABB ACS880 64B2
ABB ACS880 64E1
ABB ACS880 6581
ABB ACS880 65A1
ABB ACS880 65A2
ABB ACS880 6681
ABB ACS880 6682
ABB ACS880 6683
ABB ACS880 6684
ABB ACS880 6684
ABB ACS880 6881
ABB ACS880 6882

ABB ACS880 6883
ABB ACS880 6885
ABB ACS880 7080
ABB ACS880 7081
ABB ACS880 7082
ABB ACS880 7121
ABB ACS880 7181
ABB ACS880 7183

ABB ACS880 7184
ABB ACS880 7191
ABB ACS880 7192
ABB ACS880 71A2
ABB ACS880 71A3
ABB ACS880 71A5
ABB ACS880 71A5

ABB ACS880 71B1
ABB ACS880 7301
ABB ACS880 7310
ABB ACS880 7310
ABB ACS880 7358
ABB ACS880 7380

ABB ACS880 7381
ABB ACS880 73A0
ABB ACS880 73A1
ABB ACS880 73B0

ABB ACS880 75B1
ABB ACS880 7510
ABB ACS880 7520
ABB ACS880 7580
ABB ACS880 7581
ABB ACS880 7582
ABB ACS880 7583

ABB ACS880 80A0
ABB ACS880 80B0
ABB ACS880 80B1
ABB ACS880 80B2
ABB ACS880 9081
ABB ACS880 9082
ABB ACS880 9083
ABB ACS880 9084
ABB ACS880 9085

ABB ACS880 FA81
ABB ACS880 FA82
ABB ACS880 FB11
ABB ACS880 FB11

ABB ACS880 FF61
ABB ACS880 FF7E
ABB ACS880 FF81
ABB ACS880 FF82
ABB ACS880 FF8E
CT UV CT / Emerson Commander
SK
CT OV CT / Emerson Commander
SK
CT OI.AC** CT / Emerson Commander
SK
CT OI.br** CT / Emerson Commander
SK
CT O.SPd CT / Emerson Commander
SK
CT tunE CT / Emerson Commander
SK
CT It.br CT / Emerson Commander
SK
CT It.AC CT / Emerson Commander
SK
CT O.ht1 CT / Emerson Commander

SK
SK
CT th CT / Emerson Commander
SK
CT O.Ld1* CT / Emerson Commander
SK
SK
SK
CT cL1 CT / Emerson Commander
SK
CT SCL CT / Emerson Commander
SK
CT EEF CT / Emerson Commander
SK
CT PH CT / Emerson Commander
SK
CT rS CT / Emerson Commander
SK
CT C.Err CT / Emerson Commander
SK
CT C.dAt CT / Emerson Commander
SK
CT C.Acc CT / Emerson Commander
SK
CT C.rtg CT / Emerson Commander
SK
CT O.cL CT / Emerson Commander
SK
CT HFxx trip CT / Emerson Commander
SK
CT Parity Errors CT / Emerson
MK III "Blank Screen" All Mk III Elektronikons

MK III 10 Elektronikon Mk III LRR V1.8,
2.3
HRR

2.3
2.3
2.3
2.3
2.3, HRR

2.3
HRR

2.3

2.3
MK III 109 Elektronikon Mk III LRR V 2.3
MK III 10XX Elektronikon Mk III LRR/HRR

2.3, HRR
MK III 1111aaa G120

MK III 11XX Elektronikon Mk III HRR

2.3
2.3
2.3
MK III 15 Elektronikon Mk III LRR V 2.3
MK III 17 Elektronikon Mk III LRR V1.8
MK III 200 Elektronikon Mk III LRR V

2.3, HRR
MK III 2000 Elektronikon Mk III LRR/HRR
MK III 2001 Elektronikon Mk III HRR

2.3, HRR
2.3, HRR


MK III 37 Elektronikon Mk III -

GA90VSD Simovert P

MK III 53 Elektronikon Mk III HRR /

VSD

VSD

VSD
MK III 70XX Elektronikon Mk III HRR /

VSD

VSD
VSD

VSD
VSD

VSD

VSD

VSD

VSD
SIEMENS / ABB

VSD
SIEMENS / ABB

VSD
SIEMENS / ABB
MK III Internal Fault # 1 Elektronikon Mk IV - II or

Higher
Sinamics G120 F00006 Siemens Sinamic G120 /

GA15-30VSD / CU240

GA15-30VSD / CU240
GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
GA15-30VSD / CU240
GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
GA15-30VSD / CU240
Sinamics G120 F00101 (N) Siemens Sinamic G120 /

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
Sinamics G120 F00400 (N) Siemens Sinamic G120 /

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
Sinamics G120 A00501 Siemens Sinamic G120 /

GA15-30VSD / CU240
GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
GA15-30VSD / CU240

GA15-30VSD / CU240
GA15-30VSD / CU240
GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240

GA15-30VSD / CU240
Micromaster Constant Speed Micromaster Eco

Micromaster F001 Micromaster Eco




Mk5 0xEB33 (or 33) Siemens Sinamics 120
Mk5 Bit2 = 0 (Ex: Status 0xFB31 Micromaster 440

0xFB61 or 1)
Mk5 0xFA71 (or 71) Micromaster 440

Mk5 0xFA71 (or F7) Micromaster 440
Mk5 0x1845 (or 45 ) VACON CX

Mk5 Status 0x65 (or 65 ) VACON CX
Mk5 Status 0x834) VACON CX
Mk5 Bit0 = 0 KEB
Mk5 Bit1 = 1 KEB

Mk5 Bit1 = 0 Control Techniques
Commander SK
Mk5 Bit0 = 0 Control Techniques

Commander SK
Mk5 Bit2 = 0 Yaskawa
Mk5 Bit3 = 1 Yaskawa

Mk5 50 (or Ex: Status 0x0a50) Schneider Altivar 61/71
Mk5 Ex: Status 0x50 bit 9 = 0
Mk5 Timeout All VSDs
Mk5 Status All VSDs

0xXXXX
Mk5 Fault xxxx All VSDs
Mk5 Format Function Siemens Sinamics
Mk5 Format Chk Error All VSDs

Mk5 Format Frame Error All VSDs
Mk5 40 (or Ex: Status 0xE940) Siemens Sinamics 120

Mk5 Status 0x0 Siemens Sinamics 120
Mk5 60 (or Ex: Status 0xEA60) Siemens Sinamics 120
Mk5 34 (or Ex: Status 0xFA34) Siemens Sinamics 120

Micromaster 440
Mk5 0 rpm stored in menu “Saved Siemens Sinamics 120

Data” after a shutdown
during running
Mk5 0XFA31 (FA31) Mk 5 and VSD such as
MM440
Mk5 NO VALID Pressure Control Mk 5

Mk5 ErrorCode0x1 ZH355(+) - 900


Mk5 ErrorCode"0xXX ZH355(+) - 900


Mk5 Position Watchdog Trips ZH355(+) - 900

Mk5 MK5 returns to inoperative ZH355(+) - 900

during configuration
Mk5 Mk5 Reboots ZH355(+) - 900
Mk5 No CAN communciation ZH355(+) - 900

MM440 F0001 MicroMaster / MM4 - 420,

440

440

440

440

440

440
440

440

440

440

440

440
440
440
440

440

440
440
440
440

440
440
440
440
440

440
440

440
440
440
440

440
MM440 A0501 MicroMaster / MM4 - 420,

440

440

440

440

440
440

440
440
440
440
440
440

440
440
440
440
440
440
440
440
440
440
440
440
440
440

440
440

440
440

440
440
440
440

440
NEOS 0x1111 (Hex) NEOS
NEOS 4369 (Dec) NEOS
NEOS 0x3221 (hex) NEOS
NEOS 12833 (dec) NEOS
NEOS 12835 (Dec) NEOS




NEOS 0x610A (hex) NEOS
NEOS 0x610B (hex) NEOS

NEOS 8980(dec) NEOS
Sinamics G130 A01006 Sinamics / AIF VSD

Sinamics G130 A01017




Sinamics G130 A01317 (N)





Sinamics G130 A01507 (F, N)

Sinamics G130 A01514 (F)

Sinamics G130 A01796 (F, N)


Sinamics G130 a02016



Sinamics G130 A03506 (F,N)










Sinamics G130 A07566(F,N)

Sinamics G130 A07578(F)































Sinamics G130 A36217 (IN)
Sinamics G130 A36999 (F,N))


Sinamics G130 C01689





Sinamics G130 C30799 (F)
Sinamics G130 F01000 Sinamics / AIF VSD



Sinamics G130 F01340

Sinamics G130 F01505 (A)

Sinamics G130 F01507 (N,A)





Sinamics G130 F01910 (N, A)










Sinamics G130 F07435 (N)














Sinamics G130 F07905 (n,A)



Sinamics G130 F97935 (N)

































Sinamics G130 F31820 (N,A))

Sinamics G130 F31850 N,A)


Sinamics G130 F31886 (N,A















Sinamics G130 F32887 (N,A













Sinamics G130 F33885 N,A)









Sinamics G130 F35052 (a)














Sinamics G130 N01004 (F,A)
Sinamics G130 N01620 (F, A)
Sinamics G130 N01621 (F, A)
Sinamics G130 N05007 (A)
Sinamics G130 N30620 (F,N)

Sinamics G130 N30621 (F,N)
Sinamics G130 N30800 (F)



Vacon "Blank Screen" All Mk III Elektronikons
Vacon 10 Elektronikon Mk III, LRR

V1.8, 2.3
HRR

V1.8, 2.3
V1.8, 2.3
V1.8, 2.3
V1.8, 2.3
Vacon 104 Elektronikon Mk III LRR V1.8,
2.3, HRR

V1.8, 2.3
HRR

V1.8, 2.3
V1.8, 2.3
Vacon 109 Elektronikon Mk III, LRR V
2.3
Vacon 10XX Elektronikon Mk III -
LRR/HRR
V1.8, 2.3, HRR
Vacon 11XX Elektronikon Mk III - HRR

V1.8, 2.3

V1.8, 2.3
V1.8, 2.3

2.3
Vacon 17 Elektronikon Mk III, LRR V1.8

2.3, HRR
Vacon 2000 Elektronikon Mk III -
LRR/HRR
Vacon 2001 Elektronikon Mk III - HRR
2.3, HRR
2.3, HRR



Vacon A15 Vacon VSD

Vacon A16 Vacon VSD
Vacon A17 Vacon VSD
Vacon A24 Vacon VSD
Vacon A28 Vacon VSD

Vacon A30 Vacon VSD
Vacon A45 Vacon VSD
Vacon A46 Vacon VSD
Vacon A47 Vacon VSD

Vacon F1 Vacon VSD
Vacon F10 Vacon VSD

Vacon F11 Vacon VSD
Vacon F12 Vacon VSD
Vacon F13 Vacon VSD

Vacon F14 Vacon VSD
Vacon F15 Vacon VSD

Vacon F16 Vacon VSD
Vacon F17 Vacon VSD

Vacon F18 Vacon VSD
Vacon F19 Vacon VSD
Vacon F2 Vacon VSD
Vacon F20 Vacon VSD

Vacon F21 Vacon VSD
Vacon F22 Vacon VSD
Vacon F23 Vacon VSD
Vacon F25 Vacon VSD
Vacon F26 Vacon VSD

Vacon F29 Vacon VSD
Vacon F3 Vacon VSD
Vacon F36 Vacon VSD
Vacon F4 Vacon VSD
Vacon F41 Vacon VSD

Vacon F5 Vacon VSD
Vacon F9 Vacon VSD
Vacon Internal Fault # 1 Elektronikon Mk IV - II or

Higher
Yaskawa boL Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa bUS Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa CE Yaskawa A1000 / GAe15VSD
- 30VSD
Yaskawa CF Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa CPF11 to CPF14 Yaskawa A1000 / GAe15VSD

CPF16 to CPF19 - 30VSD
Yaskawa CPF02 Yaskawa A1000 / GAe15VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD
Yaskawa CPF20 or CPF21 Yaskawa A1000 / GAe15VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD
Yaskawa CPF26 to CPF34 Yaskawa A1000 / GAe15VSD

CPF40 to CPF45 - 30VSD
Yaskawa dEv Yaskawa A1000 / GAe15VSD
- 30VSD
Yaskawa dv1 Yaskawa A1000 / GAe15VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD
Yaskawa dWAL, dWFL Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa E5 Yaskawa A1000 / GAe15VSD
- 30VSD
Yaskawa EF0 Yaskawa A1000 / GAe15VSD

- 30VSD

- 30VSD
- 30VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD
Yaskawa Err Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa Fan Yaskawa A1000 / GAe15VSD
- 30VSD
Yaskawa FbH Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa FbL Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa GF Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa LF Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa LF2 Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa LF3 Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa nSE Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa oC Yaskawa A1000 / GAe15VSD
- 30VSD
Yaskawa oFA00 Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa oFA01 Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa oFA03 to oFA06 Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa oFA10, oFA11 Yaskawa A1000 / GAe15VSD

- 30VSD

- 30VSD

- 30VSD
Yaskawa oFb00 Yaskawa A1000 / GAe15VSD

- 30VSD

- 30VSD

- 30VSD
Yaskawa oFb03 to oFb11 Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa oFb12 to oFb17 Yaskawa A1000 / GAe15VSD
- 30VSD
Yaskawa oFC00 Yaskawa A1000 / GAe15VSD

- 30VSD

- 30VSD

- 30VSD
Yaskawa oFC03 to oFC11 Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa oFC12 to oFC17 Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa oH Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa oH1 Yaskawa A1000 / GAe15VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD
Yaskawa oL1 Yaskawa A1000 / GAe15VSD
- 30VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD
Yaskawa oPr Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa oS Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa ov Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa PF Yaskawa A1000 / GAe15VSD
- 30VSD
Yaskawa Pgo Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa PGoH Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa rF Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa rH Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa rr Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa SC Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa Ser Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa Sto Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa SvE Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa Tho Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa UL3 Yaskawa A1000 / GAe15VSD
- 30VSD

- 30VSD

- 30VSD
Yaskawa UnbC Yaskawa A1000 / GAe15VSD

- 30VSD
Yaskawa Uv1 Yaskawa A1000 / GAe15VSD

- 30VSD

- 30VSD

- 30VSD

- 30VSD
Yaskawa voF Yaskawa A1000 / GAe15VSD

- 30VSD
KEB bbl
KEB bon
KEB boFF
KEB cDD
KEB dcb
KEB dLS
KEB FAcc
KEB Fcon
KEB FdEc
KEB HCL
KEB LAS
KEB LdS
KEB LS
KEB nO_pu
KEB noP
KEB PA
KEB PLS
KEB PnA
KEB POFF
KEB POSI
KEB rAcc
KEB rcon
KEB rdEc
KEB rFP
KEB SLL
KEB SrA
KEB SSF
KEB STOP
KEB E. br
KEB E. buS
KEB E. Cdd
KEB E. co1
KEB E. co2
KEB E. dOH
KEB E. dri
KEB E. EEP
KEB E. EF
KEB E.EnC
KEB E. Hyb
KEB E. Hybc
KEB E. iEd
KEB E. InI
KEB E. LSF
KEB E. ndOH
KEB E. nOH
KEB E. nOHI
KEB E. nOL
KEB E. nOL2
KEB E. OC
KEB E. OH
KEB E. OH2
KEB E. OHI
KEB E.OL
KEB E. OL2
KEB E.OP
KEB E.OS
KEB E. PFC
KEB E. PrF
KEB E. Prr
KEB E. Pu
KEB E. Puci
KEB E.Puch
KEB E. PUCO
KEB E. PUIN
KEB E.SbuS
KEB E. SEt
KEB E. SLF
KEB E. SLr
KEB E. UP
KEB E.UPh
KEB A. buS
KEB A. dOH
KEB A. EF
KEB A. ndOH
KEB A.nOH
KEB A.nOHI
KEB A.nOL
KEB A.nOL2
KEB A. OH
KEB A.OH2
KEB A OHI
KEB A. OL
KEB A. OL2
KEB A. PrF
KEB A. Prr
KEB A. SbuS
KEB A.SEt
KEB A. SLF
KEB A . SLr
Schneider AI2F
Schneider bOF
Schneider bUF
Schneider CrF1
Schneider CrF2
Schneider EEF1
Schneider EEF2
Schneider FCF1
Schneider HdF
Schneider InF1
Schneider InF2
Schneider InF3
Schneider InF4
Schneider InF6
Schneider InF7
Schneider InF8
Schneider InF9
Schneider InFA
Schneider InFb
Schneider InFC
Schneider InFE
Schneider OCF
Schneider PrF
Schneider SCF1
Schneider SCF2
Schneider SCF3
Schneider SOF
Schneider SPF
Schneider tnF
Schneider APF
Schneider CnF
Schneider COF
Schneider EPF 1
Schneider EPF 2
Schneider FCF2
Schneider LCF
Schneider LFF2
LFF3
LFF4
Schneider nFF
Schneider ObF
Schneider OHF
Schneider OLC
Schneider OLF
Schneider OPF1
Schneider OPF2
Schneider OSF
Schneider OtF1
Schneider OtF2
Schneider OtFL
Schneider PtF1
Schneider PtF2
Schneider PtFL
Schneider SCF4
Schneider SCF5
Schneider SLF1
Schneider SLF2
Schneider SLF3
Schneider SPIF
Schneider SSF
Schneider tJF
Schneider ULF
Schneider CFF
Schneider CFI
Schneider HCF
Schneider PHF
Schneider PrtF
Schneider USF
Mk IV Conv.FormatFail - "other Mk IV-II and VSD: ABB
numbers" ACS600/800, Vacon,
Siemens
Mk IV Conv.FormatFail 0 Mk IV-II and VSD: ABB,

CUVC (Siemens)
Mk IV Conv.FormatFail 113 Mk IV-II and VSD:

Siemens

Siemens MM4

Siemens
Mk IV Conv.FormatFail 30 Mk IV - II upgrade -
Simovert P -
6SE13 . .GA90VSD
Mk IV Conv.FormatFail 49 Mk IV-II and VSD: MM4
GA7VSD
Mk IV Conv.FormatFail 52 MkIV (FDP) new software
(and MkIII to MkIV
upgrad)
Mk IV Conv.FormatFail 70 Mk IV-II and VSD: ABB

ACS600 / 800, Vacon
Mk IV Conv.FormatFail 80 Mk IV-II and VSD: ABB,

Vacon
Mk IV Conv.FormatFail 90 Mk IV-II and VSD: ABB
ACS600 / 800, Vacon
Mk IV Conv.FormatFail 96 Mk IV-II upgrade -

Simovert P

Siemens
Mk IV Convert.Failure 0 Mk IV-II and VSD: ABB

ACS600 / 800
ACS600 / 800
Mk IV Convert.Failure 128 Mk IV-III and VSD: ABB

ACS600 / 800

ACS600 / 800
ACS600 / 800

ACS600 / 800

ACS600 / 800

ACS600 / 800

ACS600 / 800
Mk IV Convert.Timeout Mk IV-II and VSD: ABB

ACS600 / 800, Siemens,
Vacon
Mk IV Converter Timeout Mk IV-III, VSD: ABB

ACS600 / 800, Siemens,
Vacon
Mk IV Converter Failure 0 Mk IV-III and VSD: ABB
ACS600 / 800

ACS600 / 800

ACS600 / 800

ACS600 / 800
ACS600 / 800

ACS600 / 800

ACS600 / 800

ACS600 / 800

ACS600 / 800
Mk IV Converter Format Fail - Mk IV-III and VSD: ABB

"other numbers" ACS600/800, Vacon,
Siemens
Mk IV Converter Format Fail 0 Mk IV-II and VSD: ABB
Mk IV Converter Format Fail 49 Mk IV-III and VSD: MM4

GA7VSD
Mk IV Converter Format Fail 70 Mk IV-III and VSD: ABB
ACS600 / 800, Vacon
Mk IV Converter Format Fail 80 Mk IV-III and VSD: ABB,

Vacon
Mk IV Converter Format Fail 90 Mk IV-III and VSD: ABB

ACS600 / 800, Vacon
Mk IV Converter Format Fail 96 Mk IV-II upgrade -

Simovert P
Mk IV Conveter Format Fail 113 Mk IV-III and VSD:

Siemens

Siemens

Siemens
Mk IV ConvFormatFail 65 Mk IV-II and VSD:
Siemens MM4
Mk IV Format Fail 48 MM4
Mk IV Internal failure No. 1 Mk IV with expansion

module

module

module

module

module

module
module
Siemens MasterDrive A015 MasterDrive Series - CUVC
Siemens MasterDrive A017 Masterdrive / CUVC, CU2


Siemens MasterDrive E All masterdrive CUVC series -

GA30VSD . . .
Siemens MasterDrive F0 GA50VSD - CU2
Siemens MasterDrive F001 Siemens CU2, CUVC

Siemens MasterDrive F002 Siemens MasterDrive Series
CU2, CUVC
Siemens MasterDrive F006 Siemens CUVC (MasterDrive)

Siemens MasterDrive F011 Siemens CUVC
(MasterDrive), CU2

Siemens MasterDrive F021 Siemens, CUVC
Siemens MasterDrive F023 Siemens converter, CUVC

CUVC
CUVC
CUVC

CUVC
Siemens MasterDrive F029 Siemens, all VSD's except

GA90VSD Simovert P
Siemens MasterDrive F035 VSD - Siemens CUVC / CU2
Siemens MasterDrive F036 AIF VSD - Siemens CUVC

ZT37VSD
GA50VSD
GA50VSD
GA50VSD

GA50VSD
GA50VSD

GA50VSD
GA50VSD
GA50VSD
Siemens MasterDrive F1 Siemens CCU - Simovert P
GA90VSD
Siemens MasterDrive F100 Siemens CUVC, CU2


Siemens MasterDrive F12 Siemens CCU - Simovert P -
6SE13 . . .
GA90VSD

6SE13 . . .
GA90VSD
6SE13 . . .
GA90VSD
Siemens MasterDrive F148 CUVC Series - ZR160VSD

(ECB1397/C1 implemented)

6SE13 . . .
GA90VSD
Siemens MasterDrive F243 MasterDrive VSD

CUVC
Siemens MasterDrive F255 MasterDrive VSD

CUVC
CUVC

CUVC

CUVC
Siemens MasterDrive F3 Siemens CCU - Simovert P

GA90VSD

6SE13 . . .
GA90VSD
Siemens MasterDrive F35 VSD - Siemens CUVC / CU2
Siemens MasterDrive F36 AIF VSD - Siemens CUVC
ZT37VSD
Siemens MasterDrive F37 Elektronikon Mk III -

GA90VSD Simovert P

GA50VSD
GA50VSD
GA50VSD

GA50VSD
GA50VSD
GA50VSD
GA50VSD
GA50VSD
6SE13 . . .
GA90VSD
6SE13 . . .
GA90VSD
6SE13 . . .
GA90VSD
Siemens MasterDrive F8 GA50VSD - CU2, CUVC

GA90VSD - CCU / Simovert
WEG CFW-11 F006 ZS+VSD, ZE/A VSD

WEG CFW-11 A046 ZS+VSD, ZE/A VSD











WEG CFW-11 FAQ - Motor does not start ZS+VSD, ZE/A VSD
WEG CFW-11 FAQ - Motor speed oscillateZS+VSD, ZE/A VSD
WEG CFW-11 FAQ - Too high or too low ZS+VSD, ZE/A VSD
motor
speed
WEG CFW-11 FAQ - Motor does not ZS+VSD, ZE/A VSD

reach the
rated speed, or motor
speed starts oscillating
around the rated speed
(Vector Control)
WEG CFW-11 FAQ - Display is off ZS+VSD, ZE/A VSD
WEG CFW-11 FAQ - Motor does not ZS+VSD, ZE/A VSD

operate in
the field weakening region
(Vector Control)
WEG CFW-11 FAQ - Low motor speed ZS+VSD, ZE/A VSD
and
P0009 = P0169 or
P0170 (motor operating
with torque limitation), for
P0202 = 4 - vector with
encoder
Meaning
No power to display of Elektronikon
Programmed stop
Relay outputs read-back error

- Inconsistency between the status of the relays and
the status the relays should be in
Register file error
RAM error
12V relay not disabled at power on
Relays status uncorrect at power on
Short circuit on 12V (relays and digital inputs) OR

12V enabling FET damaged
Relays enable at power on
the status that the relay should be in.
Serial line error
Keyboard error
Filter error (relay ouputs read-back not stable)
(Online) Read back output error
V1.8: EEprom not writable

V2.3: Relays supply error
(Online) 12V short circuit or FET to enable damaged
V1.8: Division by zero

V1.8: Wrong active display,
V2.3: EEprom checksum error
V1.8: Relays supply error,
V2.3: Eprom checksum error
Wrong activated display
Watch dog error
Watch dog error. 200XX (bootstrap)
(Bootstrap) Reserved area checksum incorrect

Internal power failure routine not completed
201xx(bootstrap)
Backupped RAM checksum error
202xx(bootstrap)
Power off during EEPROM writing
203xx (bootstrap)
Power off during EEPROM writing and power failure
interrupt routine enabled
204xx(bootstrap)
Power off during EEPROM writing and backup ram
checksum incorrect.
(Bootstrap) EPROM checksum incorrect
Eprom checksum error
(Bootstrap) Flash checksum incorrect

(Online) Division by 0
(Online) Wrong activated display
Eeprom checksum error
AC-Line Fault
(Autoconfig) No delivery air input
(Autoconfig) More than 1 delivery air input
(Autoconfig) More than 1 backup pressure input
(Autoconfig) More than 1 intercooler pressure input
(Autoconfig) More than 4 DIOE modules connected
(Autoconfig) More than 4 SIOE modules connected
(Autoconfig) More than 3 COM1 modules

connected

connected
(Autoconfig) COM3 not permitted in configuration
(Autoconfig) SIOE module not permitted in

configuration
(Autoconfig) Wrong CCM during autoconfiguration

(CMS1, CMS2)
(Autoconfig) DIOE type configured is for ES100

system
(Autoconfig) No VSD COM module during
configuration
(Autoconfig) More than 1 VSD COM module

connected.
(Online) Internal communication failed
(Online) A module in INOPERATIVE UNLOCK was

connected to an OPERATIVE regulator
(Online) A module in INOPERATIVE LOCK was

connected to an INOPERATIVE or OPERATIVE
regulator
regulator
(Online) Communication failure between regulator
and converter
and converter
and converter
(Online) Incorrect format in data send from

converter to regulator

Unknown fault as occur in converter (Online)
External alarm 1
External alarm 2
Drive is not in healthy state
Overcurrent
Overvoltage
Inverter temperature
Motor temperature
Motor movement
I2t inverter
I2t motor
Overspeed
Setpoint/actual value deviation
Motor stall/lock
Ls, Rr Dev
Stands. Meas
Mld Inv Stop
Motld: Dr.M
Insufficient power to display panel (PMU)
Converter Fail. Undefined error code, not enough

time to register fault
Contactor Checkback
Pre-Charging
DC link Overvoltage
DC link Undervoltage
DC link Overvoltage
Overcurrent
Current too Low
I too low
Motor Stall
Motor not found

Motor Temperature
Motor I2t
Inverter Temperature
UCE ph. L1
There was an UCE shut down in phase L1
UCE ph. L2
UCE ph. L3
Supply phase
Measured Valued Sensor
External fault 1
External fault 2
AS internal fault
EEPROM fault
Computing time problem
Coupling int.
BiCo manager Fault
Opt. Board HW
Par task / con.
Gating Calc Time / internal Comp. Time
Incorrect phase sequence
GRND Init
GRND UCE
GRND Phase
Ground fault
Overcurrent
Motor Overload
Motor Pullout
Active Signal @ binector U061 is present.
Motor stall
PreCharge Error
Motor Temp.
Motor I2t. Parameterized limit value of the i2t

monitoring for the motor was excedded
Inverter Temp.
Link Internal
UCE ph. L1
Fault in EEPROM
UCE ph. L2
UCE ph. L3
Supply phase
Undervoltage
One phase missing
Operator Panel Fault
External fault 1
External fault 2
AC-Line Fault
AS internal fault
EEPROM fault
Coupling int.
BiCo manager Fault

Opt. Board HW
Par task / con.
Overvoltage
Heat Sink Temp
Motor Overtemp
CU: DC voltage too low

CCU: Pulsed Res Temp
System input Error
Register file error
RAM error


Serial line error

Keyboard error
V1.8:
EEprom not writable
V2.3:
Relays supply error
V1.8:
Division by zero
V2.3:
EEprom not writable
V1.8:
Wrong active display, V2.3:
EEprom checksum error
V1.8:
Relays supply error, V2.3:
Wrong active display
Watch dog error

201xx(bootstrap)
202xx(bootstrap)
203xx (bootstrap)
204xx(bootstrap)
checksum incorrect.



connected

connected

configuration

(CMS1, CMS2)

system



regulator
regulator
Communication error between Elektronikon (Com
2) and converter



Internal temperature is excessive
Analog signal is below allowed value

Communication error
Current transformer failed

DC Voltage is excessive
DC Voltage is not sufficient
Load imbalance
External fault
Communication error
ID Run not successful
Excessive heat
Measured motor temp has exceeded fault limit set

by parameter 35.03 (150deg C)
Measured motor temp has exceeded fault limit set

by parameter 35.06 (110deg C)
One of the phase is lost
Motor is operating in stall region
Motor is operating in the stall region
Motor temperature too high
Motor data not given / not avail.

Output current is excessive
Motor is turning faster then allowed
Loss of communication
Fibre optic link is faulty

No "Run enable" signal received
Short circuit in the inverter

Short circuited
No "Start Interlock" signal received

DC Voltage is oscillating
Motor thermal protection fault
Motor load too low
High Temp warning
Analog control signal below min. allow

Communication error between ACS 600 fieldbus
and ACS 600 Master
Download failed
Program and Panel do not match
Drive is running, download not possible
Communication fault
ID Run done, and ready for operation
Motor ID magnetisation is done and ready for

operation
Motor ID magnetisation is on.
Motor identification magnetisation required.
ID Number has been changed
ID Run is on
Motor ID Run is selected
MACRO is being saved
Motor is operating in stall region
Motor ID Run Starts
Communication lost
Not uploaded
Control Panel not communicate with ACS600
Thermistor warning
Motor load is too low
Upload has failed
Parameter Access Denied
OVERCURRENT
DC OVERVOLT
DEV OVERTEMP
SHORT CIRC
RESERVED
DC UNDERVOLT
AI1 LOSS
AI2 LOSS
MOT OVERTEMP
PANEL LOSS
ID RUN FAIL
MOTOR STALL
RESERVED
EXT FAULT 1
EXT FAULT 2
EARTH FAULT
OBSOLETE
THERM FAIL
OPEX LINK
OPEX PWR
CURR MEAS
SUPPLY PHASE
ENCODER ERR
OVERSPEED
RESERVED
DRIVE ID
CONFIG FILE
SERIAL 1 ERR
EFB CON FILE
FORCE TRIP
EFB 1
EFB 2
EFB 3
MOTOR PHASE
OUTP WIRING
INCOMPATIBLE
SW
CB OVERTEMP
USER LOAD
CURVE
SYSTEM ERROR
SYSTEM ERROR
UNKNOWN
DRIVE TYPE:
ACS550
SUPPORTED
DRIVES: X
PAR HZRPM
PAR PFC REF

NEG
RESERVED
PAR AI SCALE
PAR AO SCALE
PAR PCU 2
PAR EXT RO
PAR FIELDBUS
MISSING
PAR PFC MODE
PAR PCU 1
RESERVED
PAR PFC IO 1
PAR PFC IO 2
PAR PFC IO 3
RESERVED
PAR USER LOAD C

Over Current
Over Voltage
Under voltage
DIR lock
I/O Comm
AI1 Loss
AI2 LOSS
PANEL LOSS
Device Overtemp
MOT OVERTEMP
Underload
Motor Stall
Auto reset
Auto change
PFC interlock
RESERVED
PID sleep
ID run
Reserved
Start enable 1 missing
Start enable 2 missing
EMERGENCY STOP
If this alarm code appears, refer to the appropriate

accesory manual
First start
Inverter Over temp

OVERCURRENT
Inverter Over temp
OVERCURRENT
IGBT OVERLOAD
(0x5482)
IGBT TEMP
(0x4210)
COOLING
(0x4290)
FPGA ERROR1
(0x5401)
FPGA ERROR2
(0x5402)
ADC ERROR
(0x5403)
TEMP MEAS
FAILURE
(0x4211)
EFB COMM LOSS
(0x7540)
TEMP DIFFERENCE
(0x4212)
ENC 1 PULSE
FREQUENCY
(0x738E)
ENC 2 PULSE
FREQUENCY
(0x738F)
OVERFREQUENCY
(0x7390)
T2 OVERLOAD
(0x0201)
T3 OVERLOAD
(0x6100)
T4 OVERLOAD
(0x6100)
T5 OVERLOAD
(0x6100)
A1 OVERLOAD
(0x6100)
A2 OVERLOAD
(0x6100)
A1 INIT FAULT
(0x6100)
A2 INIT FAULT
(0x6100)
STACK ERROR
(0x6100)
JMU MISSING
(0xFF61)
UFF FILE READ
(0x6300)
APPL DIR CREATION

(0x6100)
FPGA CONFIG DIR

(0x6100)
PU RATING ID
(0x5483)
RATING DATABASE
(0x6100)
LICENSING
(0x6100)
DEFAULT FILE
(0x6100)
APPLFILE PAR
(0x6300)
APPL LOADING
(0x6300)
USERSET LOAD
(0xFF69)
USERSET SAVE
(0xFF69)
UFF OVERSIZE
(0x6300)
UFF EOF
(0x6300)
TECH LIB
INTERFACE
(0x6100)
RESTORE FILE
(0x630D)
DAPS MISMATCH
(0x5484)
SOLUTION FAULT
(0x6200)
MENU HIDING
(0x6200)
BRAKE START
TORQUE
(0x7185)
Programmable fault:
42.12 Brake fault func
BRAKE NOT
CLOSED
(0x7186)
Programmable fault:
BRAKE NOT OPEN
(0x7187)
Programmable fault:
SAFE TORQUE OFF

(0xFF7A)
Programmable fault:
30.07 Sto diagnostic
STO MODE CHANGE

(0xFF7A)
MOTOR
TEMPERATURE
(0x4310)
Programmable fault:
31.01 Mot temp1 prot
EMERGENCY OFF
(0xF083)
RUN ENABLE
(0xFF54)
MOTOR ID-RUN
(0xFF84)
EMERGENCY STOP
(0xF081)
BR OVERHEAT
(0x7112)
BC OVERHEAT
(0x7181)
DEVICE OVERTEMP
(0x4210)
INTBOARD
OVERTEMP
(0x7182)
BC MOD OVERTEMP
(0x7183)
FIELDBUS COMM
(0x7510)
Programmable fault:
50.02 Comm loss func
LOCAL CTRL LOSS

(0x5300)
Programmable fault:
30.03 Local ctrl loss
AI SUPERVISION
(0x8110)
Programmable fault:
13.32 AI superv func
FB PAR CONF
(0x6320)
NO MOTOR DATA
(0x6381)
ENCODER 1
FAILURE (0x7301)
ENCODER 2
FAILURE (0x7381)
FEN TEMP MEAS

FAILURE
(0x7385)
RESOLVER
AUTOTUNE ERR
(0x7388)
ENCODER 1 CABLE
(0x7389)
ENCODER 2 CABLE
(0x738A)
D2D
COMMUNICATION
(0x7520)
Programmable fault:
D2D BUFFER
OVERLOAD
(0x7520)
Programmable fault:
PS COMM
(0x5480)
RESTORE
(0x6300)
CUR MEAS
CALIBRATION
(0x2280)
AUTOPHASING
(0x3187)
EARTH FAULT
(0x2330)
Programmable fault:
30.05 Earth fault
AUTORESET
(0x6080)
MOTOR NOM VALUE
(0x6383)
D2D CONFIG
(0x7583)
STALL
(0x7121)
Programmable fault:
30.09 Stall function
LCURVE
(0x2312)
Programmable fault:
34.01 Overload func /
34.02 Underload func
LCURVE PAR
(0x6320)
FLUX REF PAR
(0x6320)
SPEED FEEDBACK
(0x8480)
OPTION COMM
LOSS
(0x7000)
MOTOR TEMP2
(0x4313)
Programmable fault:
IGBTOLALARM
(0x5482)
IGBTTEMPALARM
(0x4210)
COOLING
(0x4290)
MENU CHG
PASSWORD REQ
(0x6F81)
MENU CHANGED
(0x6F82)
DEVICE CLEAN
(0x5080)
COOLING FAN
(0x5081)
ADD COOLING
(0x5082)
CABINET FAN
(0x5083)
DC CAPACITOR
(0x5084)
MOTOR BEARING
(0x738C)
MAIN CONTACTOR
(0x548D)
RELAY OUTPUT SW
(0x548E)
MOTOR START
COUNT
(0x6180)
POWER UP COUNT
(0x6181)
DC CHARGE COUNT
(0x6182)
ONTIME1 ALARM
(0x5280)
ONTIME2 ALARM
(0x5281)
EDGE1 ALARM
(0x5282)
EDGE2 ALARM
(0x5283)
VALUE1 ALARM
(0x5284)
VALUE2 ALARM
(0x5285)
DC NOT CHARGED
(0x3250)
SPEED CTRL TUNE

FAIL
(0x8481)
START INTERLOCK
(0xF082)
TEMP MEAS
FAILURE
(0x4211)
EFB COMM LOSS
(0x060E)
TEMP DIFFERENCE
(0x4212)
ENC 1 PULSE
FREQUENCY
(0x738E)
ENC 2 PULSE
FREQUENCY
(0x738F)
AO CALIBRATION
(0x7380)
BR DATA
(0x7113)
SOLUTION ALARM
(0x6F80)
OVERCURRENT
(0x2310)
DC OVERVOLTAGE
(0x3210)
SHORT CIRCUIT
(0x2340)
DC UNDERVOLTAGE
(0x3220)
EARTH FAULT
(0x2330)
Programmable fault:
30.05 Earth fault
FAN FAULT
(0xFF83)
IGBT OVERTEMP
(0x7184)
BC WIRING
(0x7111)
BC SHORT CIRCUIT
(0x7113)
BC OVERHEAT
(0x7181)
BR OVERHEAT
(0x7112)
CURR MEAS GAIN

(0x3183)
WIRING OR EARTH
FAULT
(0x3181)
Programmable fault:
30.08 Wiring or earth
SUPPLY PHASE
(0x3130)
Programmable fault:
30.06 Suppl phs loss
MOTOR PHASE
(0x3182)
Programmable fault:
30.04 Mot phase loss
MOTOR ID-RUN
FAULT
(0xFF84)
CURR U2 MEAS
(0x3184)
CURR V2 MEAS
(0x3185)
CURR W2 MEAS
(0x3186)
STO1 LOST
(0x8182)
0022 STO2 LOST

(0x8183)
STO MODE CHANGE

(0xFF7A)
INTBOARD
OVERTEMP
(0x7182)
BC MOD OVERTEMP
(0x7183)
AUTOPHASING
(0x3187)
PU LOST
(0x5400)
PS COMM
(0x5480)
EXTERNAL
(0x9000)
SAFE TORQUE OFF

(0xFF7A)
Programmable fault:
30.07 Sto diagnostic
OVERSPEED
(0x7310)
BRAKE START
TORQUE
(0x7185)
Programmable fault:
BRAKE NOT
CLOSED
(0x7186)
Programmable fault:
BRAKE NOT OPEN

(0x7187)
Programmable fault:
LOCAL CTRL LOSS

(0x5300)
Programmable fault:
30.03 Local ctrl loss
NVMEM
CORRUPTED
(0x6320)
OPTIONCOMM LOSS
(0x7000)
ENCODER 1
(0x7301)
ENCODER 2
(0x7381)
FIELDBUS COMM
(0x7510)
Programmable fault:
FB MAPPING FILE
(0x6306)
MOTOR OVERTEMP
(0x4310)
Programmable fault:
AI SUPERVISION
(0x8110)
Programmable fault:
13.32 AI superv func
ENCODER 1 CABLE
(0x7389)
Programmable fault:
90.05 Enc cable fault
ENCODER 2 CABLE
(0x738A)
Programmable fault:
D2D CONFIG
(0x7583)
D2D COMM
(0x7520)
Programmable fault:
D2D BUF OVLOAD

(0x7520)
Programmable fault:
TECH LIB
(0x6382)
TECH LIB CRITICAL
(0x6382)
FORCED TRIP
(0xFF90)
FB PAR ERROR
(0x6320)
STALL
(0x7121)
Programmable fault:
LOAD CURVE
(0x2312)
Programmable fault:
34.01 Overload func /
34.02 Underload func
SPEED FEEDBACK
(0x8480)
D2D SLOT COMM

(0x7584)
MOTOR TEMP2
(0x4313)
Programmable fault:
Fluctuation in motor speed
current calibration
Overcurrent
Earth Leakage
Short Circuit
IGBT overload
DC link overvoltage
DC link undervoltage
DC not charged
Motor cable overload
Incorrect temperature sensor setup
Incorrect temperature sensor setup

External temperature 1 (editable message text)
External temperature
2
Editable message text)
Several Meanings:
- Control Board Temperature
- (none)
-1
IGBT overtemperature
cooling
excess temperature
Excess temperature
difference
PCB space cooling
IGBT temperature
PU communication
Fan
Auxiliary fan missing
Safe torque off

Programmable warning:
31.22 STO indication
run/stop
Measurement circuit
temperature
PU board powerfail
PU communication internal
Measurement circuit
ADC
Measurement circuit DFF
PU state feedback
Charging feedback
switching frequency below requested
Data saving to power unit

SD card
Power fail saving

Motor nominal value
Motor nominal value
no motor data
FBA A parameter conflict
FBA B parameter conflict
AI parametization
Motor stall
Motor fan
35.106 DOL starter event
type
FEN temperature
FEN temperature
Brake resistor
BR excess temperature
BR Data
Speed feedback configuration
BC short circuit
BC IGBT excess
temperature
Mechanical brake closing failed

Programmable warning: 44.17 Brake fault function
Mechanical brake
opening failed
44.17 Brake fault function
Mechanical brake
opening not allowed
44.17 Brake fault function
Extension AI
parameterization
Extension I/O
configuration failure
Motor speed feedback

90.45 Motor feedback fault
Load speed feedback

90.55 Load feedback fault
FBA A communication
50.02 FBA A comm loss
func
FBA B communication
50.32 FBA B comm loss
func
DDCS controller
comm loss
60.59 DDCS controller
comm loss function
EFB comm loss

58.14 Communication loss
action
Encoder
90.45 Motor feedback fault
Panel Loss Programmable warning:

action
Motor bearing
Programmable warnings:
33.14 On-time 1 warn message
33.55 Value counter 1 warn message
33.65 Value counter 2 warn message
Output relay
Motor Starts
Power Ups
Main contactor
DC charge
On-time 1
On-time 2
(Editable message text)
33.24 On-time 2 warn
message
Edge counter 1
Editable message text)
33.35 Edge counter 1
warn message
Edge counter 2
33.45 Edge counter 2
warn message
Value counter 1
33.55 Value counter 1
warn message
Value counter 2
33.65 Value counter 2
warn message
Device clean
DC capactior
Cabinet fan
cooling fan
additional cooling
AI supervision
12.03 AI supervision
function
Signal supervision
32.06 Supervision 1 action
Signal supervision 2
Fan service counter
External warning 1
31.01 External event 1
source
type
External warning 2
source
type
External warning 3
source
type
External warning 4
source
type
External warning 5
source
type
FA2FA DDCS comm

loss
60.79 INU-LSU comm loss
function
Line side unit warning
Process PID sleep mode

Speed controller autotuning
Autoreset
Emergency stop (off2)
Emergency stop (off1

or off3)
Follower
Enable start signal missing (Editable message text)
Run enable missing
External power missing
Idtenification run
Autophasing
STO event Programmable event:
31.22 STO indication
run/stop
Calibration
Overcurrent
Earth leakage Programmable fault 31.20 Earth fault
Short circuit
IGBT overload
BU current difference
BU earth leakage
Input phase loss

Programmable fault: 31.21
Supply phase loss
Charge relay lost
Wiring or earth fault


DC link overvoltage
DC link undervoltage
Standby timeout
BU DC link difference
Output phase loss
Autophasing
Motor cable overload
IGBT overtemperature
Cooling
IGBT temperature
excess temperature
Excess temperature difference

PCB space cooling
External temperature
1
Fan
Auxiliary fan broken
STO hardware failure
Safe torque off

STO indication run/stop
PU logic error
Rating ID mismatch
Measurment cirucit temperature
PU communication
PU communication
Power unit lost
PU communication internal
Measuremnt cirucit ADC
PU board powerfail
measurment circuit DFF

PU communication configuration
Reduced run
Pu state feedback
Charging Feedback
Unknown power unit fault
Internal SW error
FPGA version
incompatible
FBA A Mapping file
FBA B mapping file
Task overload
Stack overflow
internal file load
internal record load

application loading
Licensing fault
Memory unit detached
Internal SSW fault
User set fault
Kernal overload
Parameter system
FBA A parameter conflict
FBA B parameter conflict
EFB comm loss

Programmable fault:
action
EFB config file
EFB invalid
parameterization
EFB load fault
EFB load fault
Text data overflow
Text 32-bit table overflow

Text 64-bit table overload
Text file overflow
Option module comm loss
Panel port
communication
Communication loss
action
Ext I/O comm loss
Motor stall
Stall function
Brake resistor
BR excess temperature
Brake resistor wiring
BC short circuit
BC IGBT excess
temperature
Mechanical brake
closing failed
Brake fault function
Mechanical brake
opening failed
Mechanical brake
opening not allowed
Mechanical brake
opening not allowed
Motor fan
Programmable fault:
35.106 DOL starter event
type
Motor speed feedback

Motor feedback fault
overspeed
overspeed
Line side converter

faulted
Encoder internal
Encoder
Motor feedback fault
Speed feedback
configuration
Load feedback
Load feedback fault
Emergency ramp
failed
stop failed
FBA A communication
FBA A comm loss func
FBA B communication
FBA B comm loss func
FA2FA DDCS comm

loss
INU-LSU comm loss
function
DDCS controller
comm loss
DDCS controller comm
loss function
MF comm loss
M/F comm loss function
Line side unit faulted
AI supervision
Programmable fault:
12.03 AI supervision
function
Signal supervision
Programmable fault:
Programmable fault:
Programmable fault:
External fault 1
External event 1 source
type
External fault 2
type
External fault 3
type
External fault 4
type
External fault 5
type
Safe torque off 1
Safe torque off 2
Memory unit missing
Memory unit missing

ID RUN
Follower
FB A force trip
FB B force trip
FB C force trp
DC bus under voltage
DC bus over voltage
Drive output instantaneous over

current
Braking resistor instantaneous
over current
Over speed
Autotune stopped before

completion
I2t on braking resistor
AC I2t on drive output current
IGBT over heat based on drives

thermal model
Over heat based on drives
heatsink
Motor thermistor trip
User +24V or digital output

overload
Drive over-heat based on drives
thermal model
Power module rectifier over
temperature.
Analog input 1 current mode,
current loss
Serial communications loss timeout
Internal drive EEPROM trip
Input phase imbalance or input

phase loss
Failure to measure motors stator
resistance
SmartStick data error
SmartStick data does not exist
SmartStick read/write fail
SmartStick/drive rating change
Overload on current loop input
Hardware faults
Parity Errors - communications

Register file error
RAM error


Serial line error
Keyboard error

V2.3: Relays supply error
G120
V1.8: Division by zero

V1.8: Wrong active display,
V2.3: EEprom checksum error
V1.8: Relays supply error,
V2.3: Eprom checksum error
Wrong activated display
Watch dog error

201xx(bootstrap)
202xx(bootstrap)
203xx (bootstrap)
204xx(bootstrap)
checksum incorrect.

AC-Line Fault


connected

connected

configuration

(CMS1, CMS2)

system
(Autoconfig) No VSD COM module during

configuration
(Autoconfig) More than 1 VSD COM module

connected.


regulator
regulator
and converter

and converter

and converter



System input Error
Chip temperature rise exceeds critical levels.
Motor Over Temperature

Motor temperature signal lost
Mains Phase Missing
Earth fault
Powerstack fault
Output phase fault
F3E Dclink Ripple
Supply to Gate Driver Not Enabled
Overcurrent on W phase
Power limit exceeded during regeneration
EM brake overcurrent
Auto restart after n

Motor Data Identification Failure
Speed Control Optimisation Failure
Parameter EEPROM Fault
power stack Fault
BOP-EEPROM Fault
BOP not fitted
BOP fault
BOP contents incompatible
Asic Timeout
Par Cl. MMC-PS not fitted Fault
Par Cl. MMC-PS contents invalid
Par Cl. MMC-PS contents incompatible
Drive attempted to do an automatic clone during

startup.
PLC setpoint fault
USS setpoint fault
USS Setpoint Fault
Control Panel setpoint fault
AI lost Input Signal
External Fault
Encoder feedback loss

Watchdog Reset
Stack Overflow
PID Feedback below min. Value
PID Feedback above max. Value
Configuration vector for the drive failed
Acceptance Test / Confirmation pending
PROFIBUS: DS101/DB101 (control pannel) failure.
Belt Failure
Motor Stalled
Current Limit
Overvoltage limit
UnderVoltage Limit
Inverter OverTemperature
Inverter I2T
IGBT junction temperature rise warning
Inverter temp. signal lost
Motor OverTemperature I2T
Output fault
F3E Dclink Ripple
Braking Resistor Overload
Motor Data Identification Active

Speed Control Optimisation Active
Speed deviation
MMC Plugged During Operation
Encoder feedback loss warning
RTOS Overrun Warning
PROFIBUS: Parameter or configuration error
PROFIBUS: DoubleWord error
PROFIBUS: no bus detection
PROFIBUS: no reference values
PROFIBUS: loose of links
PROFIBUS: timeout actual value
PROFIBUS: fatal SW error (e.g. hardware check,

communication, V
PROFIBUS: wrong PB address at startup
--- not used ---
--- not used ---
CB communication error
CB configuration error
Vdc-max controller de-activated
Vdc-max controller active
Vdc-min Controller active
AO parameters not set properly.
No load applied to inverter
Both JOG Left and JOG Right are requested

PID Autotuning Active
Belt Failure Detected
Passivated STO with drive fault
System startup error
EEPROM inconsistent
Defect in cross comparis.
Diff. in hardw. Detection
Maximum frequency exceeded
Frequency consistency fault

Error in hardw. environm.
Processor selftest faulty
Consecutive no. incorr.
Safe Brake Control faulty
PROFIsafe Driver Fault
Internal software error
Fault in safety parametr.
Fault at processor reset

Denial of paramet. Change
Wrong safety checksum
Safety parameter changed
SLS signal inconsistency
Speed for SLS exceeded
Switch-on is inhibited
Wrong safety param. Data
Safety commis./reset act.
Forced dynamis. Required
Micromaster only runs at fixed speed

Overvoltage
Overcurrent
Overload
Overheating of motor (monitoring with PTC)
Inverter overtemperature (internal PTC)
USS protocol time-out
Initialistion fault
Internal interface fault
External Trip
Programme fault
Flying Start Instability
Auto-restart after fault
Motor overtemperature by I2t calculation
Parameter fault P006

Parameter fault P012 / P013
Digital input parameter fault
Automatic calibration failure
Parameter fault P211 / P212

Output current measurement imbalance
Wrong Converter Status Word

Converter Status = “running“, while Elektronikon
expects it has ‘stopped’

During Ramdown we need to give the converter
more time to stop.
- Wrong Converter Status Word
- Bit “Running” does not become ‘1’ after sending a

Ready command.
Converter Start-up procedure is not updated.

Inverter overload / motor current limit

The converter will not start as long as his Run
Enable is open (this status means that the converter
is still in Stop).
The converter gives an alarm and because of this
the Ready Bit becomes ‘0’. Since the Ready Bit is 0
the Elektronikon cannot start the compressor.
is still in ‘Stop’).
Drive has tripped.
is still in ‘Stop’)
Drive has tripped.

is still in ‘Stop’).
Drive has tripped.
Converter is in state “switch on inhibited” while the
Mk5 expects otherwise.
0x50 = 0x0 0 50 Meaning bit 9 = 0.
The drive is not in remote control.
No Communication between VSD and Elektronikon
Actual converter status and expected converter

status in Elektronikon do not match.
Converter fault number or fault indicator is

communicated to Elektronikon.
The Elektronikon might get confused due to
improper voltage levels and reflections on
communication bus.
Message checksum is not correct.
Message frame is not correct.


Switch On Inhibit is active


The Elektronikon reads out the wrong bytes and
interprets them as the status word.


Switch On Inhibit is active during start up, drive is
Not Ready


Converter Status = “running“, while Elektronikon
expects it has ‘stopped’
External Fault
Input in wrong position, service switch not correct,

K05 (or K09, etc) faulty
No pressure sensor for compressor to regulate

LOS_NodeGuardCheck
LOS_NodeGuardCheck
LOS_NodeGuardCheck
LOS_NodeGuardCheck
LOS_NodeGuardCheck
LOS_CANstartupTimeOut
IllegalResponse_SDOUnknown
IllegalResponse_ActuatorID
: no operation, control release (terminal ST) is not
switched
any other error code
TimeOut_Homing
TimeOut_Homing
TImeOut_Resetting
TImeOut_Resetting
TImeOut_Resetting
Overcurrent
OverVoltage
UnderVoltage
Inverter Over Temperature
Inverter I2t
Motor over Temperature

Inverter temp.signal lost
Motor temperature signal lost
Mains Phase Missing
Earth Fault
Powerstack Fault
Output fault
Fan has failed
Auto Restart after n
Motor Data Identification Failure
Speed Control Optimisation Failure
Parameter EEPROM Fault
Power Stack Fault
IOP EEPROM Fault
Wrong IO board
Asic Timeout
CB Setpoint Fault
USS (BOP-Link) setpoint fault
USS (COMM link) setpoint fault
ADC lost input signal
External Fault
Encoder feedback loss
Stack Overflow
PID Feedback below min. value
PID Feedback above max.value
BIST Tests Failure
Belt Failure Detected
Current Limit
OverVoltage Limit
UnderVoltage Limit
Inverter Overtemperature
Inverter I2t
Motor Overtemperature
I2C read out timeout
Output fault
Braking Resistor Hot
Motor Data Identification Active
Speed Control Optimisation Active
Encoder Feedback Loss Warning
RTOS Overrun Warning
CB Warning 1
CB Warning 2
CB Warning 3
CB Warning 4
CB Warning 5
CB Warning 6
CB Warning 7
CB Warning 8
CB Warning 9
CB Warning 10
CB Communication Error
CB Configurator error
Vdc-max controller de-activated
Vdc-max controller Active
Vdc-min controller Active
ADC Parameters not set properly

DAC parameters not set properly
No Load applied to inverter
Both JOG Left and JOG Right are requested
PID Autotuning Active
Belt Failure Warning
Motor Stalled
Undervoltage
Undervoltage
Undervoltage
Undervoltage
Undervoltage
Undervoltage
DC Link Overvoltage
DC Link Overvoltage
Undervoltage
Undervoltage
Overvoltage
Overvoltage
Overvoltage
Overvoltage
Overvoltage
Overvoltage
Drive overtemperature
Emergency off (STO)
Emergency off (STO)
Emergency off (STO)
Emergency off (STO)
Emergency off (STO)
Emergency off (STO)
Drive failure (hardware)

Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Overvoltage
Overvoltage
Firmware update DRIVE-CLiQ component

required
POWER ON DRIVE-CLiQ component required
CompactFlash card changed

Component lists changed
ACX: Run-up from backup files
CU CompactFlash: Configuration data invalid
CU CompactFlash: Configuration data invalid
ACX: Parameter Write Error
CU CompactFlash: It is not possible write into

the file
CU: System overload calculates, for the
complete target topologie
CU: System overload measured
Parameter save necessary

Drive: Fault on non-active encoder
Non-volatile data save cannot be activated.
Tolerance window of time synchronization

exited
CU: CompactFlash card withdrawn

CU: Sampling time inconsistent
CU: Pulse frequency inconsistent
CU: CU-EEPROM incorrect read-write data
CU: Opt. module EEPROM incorrect read-only

data
Firmware version of DRIVE-CLiQ component is
not up-to-date
Firmware of the DRIVE-CLiQ component being

updated
Topology: Component must not be present
Drive object not ready for operation
Drive object not ready for operation
Drive object inactive and again ready for

operation
Drive object inactive and again ready for

operation
De-activated component again present
BICO: De-activated interconnections present

Inserted component not initialized
Topology: Drive object number does not exist

in configuration
Topology: Drive object number does not exist

in configuration
Topology: Drive object number present twice

in configuration
Topology: More than two partial lists created
Topology: Dummy drive object number

incorrectly created
Topology: Quick commissioning not possible

Topology: At least one component not
assigned to a drive object
Topology: Actual topology contains SINUMERIK

and SIMOTION components
Topology: Comparison power unit shifted
Topology: Comparison Sensor Module shifted
Topology: Comparison Terminal Module

shifted
Message value: Component number: %1,
Component class: %2, Component (target):
Topology: Comparison DRIVE-CLiQ Hub Module

shifted
Topology: Comparison, Cx32 Shifted
Topology: Comparison DRIVE-CLiQ component

shifted
Topology: Comparison option slot component

shifted
Topology: Comparison EnDat encoder shifted
Topology: Comparison motor with DRIVE-CLiQ

shifted
Topology: Comparison additional component
in actual topology
Topology: Comparison a component is

different
Topology: Comparison different components
Topology: Comparison serial number of a

component is different
Topo: Comparison connection of a component

is different
Topology: Comparison connection is different

for more than one component
Topology: Comparison power unit missing in

the actual topology
Topology: Comparison Sensor Module missing
in the actual topology
Topology: Comparison Terminal Module

missing in the actual topology
Topology: Comparison DRIVE-CLiQ Hub Module

Topology: Comparison CX32 missing in the

actual topology
Topology: Comparison DRIVE-CLiQ components

Topology: Comparison option slot components

Topology: Comparison EnDat encoder missing

in the actual topology
Topology: Comparison motor with DRIVE-CLiQ

BICO: Interconnections to inactive objects

present
BICO: Interconnections to inactive objects
exceeded
BICO: Error when writing during a reconnect
Drive: Motor maintenance interval expired
SI Motion: Ti and To unsuitable for DP cycle
SI Motion: Testing of the motion monitoring

functions selected when booting
SI Motion: Motion monitoring functions must

be tested
SI CU: Commissioning mode active
SI CU: Shutdown path must be tested

SI Motion CU: Wait for communication
PROFIBUS: Configuration telegram error
PROFIBUS: Parameterizing telegram error
IF1: PB/PN clock cycle synchronous operation

parameterization not permissible
COMM INT: Receive configuration data invalid
PROFIBUS: Interruption cyclic connection
PROFIBUS: Receive setpoints after To
IF1: PB/PN current controller clock cycle clock

cycle synchronous not equal
IF1: PB/PN speed controller clock cycle clock

cycle synchronous not equal
IF1: PB/PN clock cycle synchronism not
reached
IF1: PB/PN clock cycle signal missing when

establishing bus communication
IF1: PB/PN clock cycle signal error when

establishing bus communication
IF1: PB/PN sign-of-life synchronism not

reached
PROFIBUS: Connection to the Publisher failed
CU DRIVE-CLiQ: Synchronization not completed
CU DRIVE-CLiQ: Synchronization DO not

completed
Function generator: Start not possible

Function generator: Does not exist
Function generator: No drive specfied for

connection
Function Generator: Drive not SERVO/VECTOR
Function generator: Drive specified a multiple

number of times
Function generator: Illegal mode
Function generator: Speed setpoint from the

drive is not zero
Function generator: The actual drive speed is

not zero
Function generator: Magnetizing running
Function generator: Parameter cannot be

changed
Function generator: Parameter cannot be
changed
Function generator: Period too short
Function generator: Pulse width too high
Function generator: Physical address equals

zero
Function generator: Illegal value for offset
Function gnerator: Illegal value for bandwidth

Function generator: Time slice clock cycle
invalid
Trace: Start not possible
Trace: recording time too short
Trace: Time slice clock cycle invalid
Trace: Time slice clock cycle invalid
Trace: Time slice clock cycle for endless trace

not valid
Trace: Time slice clock cycle for 2 x 8 recording

channels not valid
Trace: Signal to be traced missing
Trace: Invalid signal
Tracer: Invalid trigger signal
Trace: Invalid data type

Trace: Parameter cannot be changed
Trace: Pretrigger time for too long
Trace: Insufficient Control Unit memory
CU: Computing dead time current controller

too short
OA: Application cannot be loaded
TM: Sampling time change
24 V power missing
TM: Speed setpoint filter natural frequency >
Shannon frequency
Power module: Overtemperature heatsink
Power module: Overtemperature chip
Power module: Overtemp air intake

Power module: Overtemperature electronics
unit
Power module: Overtemperature rectifier
Cooling system: Cooling medium flow rate too

low.
Power unit: Overtemperature thermal model
Parallel circuit configuration: Impermissible

current dissymmetry
Parallel circuit configuration: Inadmissible DC

link voltage dissymmetry
Parallel circuit: Power unit de-activated
Drive: I2t motor model overtemperature

Drive: Motor temperature sensor alarm
Changing over units: Adding a function module

blocked if units changed over
Drive: Master control ON/OFF1 command

present
Drive: Automatic restart active
Drive: Measuring probe parameterized to a

digital output
Drive: DC link voltage maximum controller

active
Drive: DC link voltage maximum controller de-

activated
Drive: DC link voltage minimum controller
active
Drive: V/f control, current limiting controller

active
Drive: DC link voltage maximum controller de-

activated
Drive: Flux controller configuration
EPOS: Jerk time is limited
LR: Save the position offset of the absolute

encoder adjustment
LR: Position actual value preprocessing does

not have a valid encoder
EPOS: Maximum velocity limited
EPOS: Setpoint velocity limited
EPOS: Combination of input signals illegal
EPOS: Reference point not set
EPOS: Selected traversing block number does

not exist
EPOS: External block change not requested in

the traversing block
EPOS: Traversing block does not have a

subsequent block
EPOS: Traversing block number assigned a

multiple number of times
EPOS: Traversing block has illegal task

parameters
EPOS: Traversing block jump destination does

not exist
EPOS: Traversing block < target position <
software limit switch minus
EPOS: Traversing block> target position >

software limit switch plus
EPOS: Traversing block target position outside

the modulo range
EPOS: Traversing block ABS_POS/ABS_NEG not

possible
EPOS: Beginning of traversing range reached

EPOS: End of traversing range reached
EPOS: Target position < software limit switch
minus
EPOS: Target position > software limit switch
plus
EPOS: Software limit switch minus reached
EPOS: Software limit switch plus reached
EPOS: Travel to fixed stop clamping torque not

reached
EPOS: Intermediate stop missing
EPOS: Reject traversing task missing
EPOS: Reference point correction outside the

window
LR: Reference function interrupted
EPOS: Enable not possible
LR: Position setting value activated
LR: Measuring probe evaluation not possible
Drive: Motor data set is not assigned to a drive

data set
Drive: Data structure does not correspond to
the interface module
Drive: Motor changeover incorrectly

parameterized
Drive: Motor cannot be changed over
Drive: Drive Data Set DDS not present
Drive: Data set changeover not possible
Drive: Not possible to reset encoder

parameters
Encoder 1: Reference point coordinate not in
the permissible range


Drive: Encoder error in PROFIdrive encoder

interface 1

interface 2

interface 3
Encoder could not be identified
Drive: Encoderless operation due to a fault

active
Encoder 1: Measuring probe evaluation not
possible
Encoder 2: Measuring probe evaluation not

possible
Encoder could not be identified
Drive: No Sensor Module with matching

component number
Encoder 1: Position actual value preprocessing

error
error
error
Encoder 1: Position setting value activated

does not have a valid encoder


Encoder 1: Drive Data Set changeover in

operation

operation

operation
Encoder 1: Value range for position actual

value exceeded

value exceeded
value exceeded
Encoder 1: Reference function interrupted
Drive: Power unit overload I2t
Drive: Temperature sensor not connected

Drive: Simulation mode activated
External alarm 1
External alarm 2
External alarm 3
Drive: Motor speed deviation
External armature short-circuit: Contactor

feedback signal "Closed" missing
Internal armature short-circuit active

Drive: Motor overtemperature
Three-phase setpoint generator operation

selected/active
Drive: Torque too low
Drive: Torque too high
Drive: Torque outside the tolerance

Drive: Envelope curve, parameter invalid
DC brake active
Brake does not open
Brake does not close
Sync-line-drive: Target frequency not

permissible
Sync-line-drive: Setpoint frequency is

completely different than the target frequency
Sync-line-drive: Synchronization not permitted
Drive: Incorrect friction characteristic

Drive: Friction characteristic record activated
Drive: Angular commutation offset

determination activated
Drive: Rotating measurement activated
Drive: Enable signals for the rotating

measurement missing
Drive: Rotating measurement, no encoder

available
Drive: Motor data identification activated
COMM BOARD: Internal cyclic data transfer

error
COMM BOARD: Receive configuration data
invalid
COMM BOARD: Non-cyclic channel error
COMM BOARD: No cyclic connection
COMM BOARD: Message channel error
PZD Interface Hardware assignment error
CBC: Telegram loss
CBC: Error counter for error passive exceeded

CBC: Message buffer overflow
CBC: Incorrect communications mode
CBC: Obj cannot be mapped
CBC: Number of mapped bytes exceeded
CBC: Set COB-ID invalid
CBC: Number of PDO channels too low
CBC: PDO COB-ID already available

Select another PDO COB-ID.
Error in license checksum
Power unit: Sign-of-life error cyclic data
Power unit: Load supply switched out

alarm
Power unit: Hardware current limiting, phase U

Power unit: Hardware current limiting, phase V
Power unit: Hardware current limiting, phase

W
Power unit: Undervoltage 24 V alarm
Power unit: Fan operating time reached or

exceeded
Power unit: Overvoltage 24 V alarm
Power unit: Undervoltage, alarm
Actual value/setpoint preprocessing no longer

synchronous to DRIVE-CLiQ
Power unit: CRC
Power unit: Watchdog timer

Power unit: Temperature sensor fault
Power unit: Unknown alarm
Encoder 1: Alarm threshold zero mark distance

error
Encoder 1: Alarm threshold zero marked failed

Encoder 1: Serial communications
Encoder 1: EnDat encoder signals alarms
Encoder 1: Error bit set in the serial protocol
Encoder 1: Amplitude error track C or D (C^2 +

D^2)
Encoder 1: Speed difference per sampling rate
exceeded
Encoder 1: Track A or B outside the tolerance

range
Encoder 1: Coarse position error
Encoder 1: Position difference, hall

sensor/track C/D and A/B too large
Encoder 1: Deviation, position
incremental/absolute too large
Encoder 1: Rotor position adaptation corrects

deviation
Encoder 1: Signal level C/D unipolar outside

tolerance
Encoder 1: Encoder serial number changed
Encoder 1: SPI-BUS error occurred
Encoder 1: I2C-BUS error occurred
Encoder 1: Configuration error
Encoder 1: Temperature sensor fault
Encoder 1: Unknown alarm

error

D^2)

exceeded

range



deviation

tolerance
Encoder 2: Effectivity test does not supply the

expected value

error


D^2)
exceeded

range

1

deviation

tolerance
Encoder 3: Effectivity test does not supply the

expected value

VSM: Temperature alarm threshold exceeded
VSM: Sequence control time monitoring
VSM: I2C bus error occurred

VSM: EEPROM
VSM: Parameter access
VSM: Temperature sensor fault
VSM: Unknown alarm

TM54F: Test stop active
TM54F: Test stop required
TM54F: Communication with drive not

established
TM54F: Net data communication with drive

not established
TM54F: Temperature alarm threshold

exceeded
TM54F: Internal communications
TM54F: Checksum error safety parameters
TM54F: Static 1 signal at F-DI for safe

acknowledgement
TM: Calibration data
TM: Temperature alarm threshold exceeded
TM: Encoder pulse number not permissible
TM: Zero mark offset not permissible

TM DRIVE-CLiQ: Sign-of-life missing
TM: Time slice overflow

TM: Memory test
TM: CRC
TM: EPROM checksum error
TM: Sequence control time monitoring

TM: I2C bus error occurred
TM: EEPROM
TM: Parameter access
TM: 24 V power supply missing
TM: Hardware initialization error
TM: Module overtemperature

TM: Clock synchronous operation sign-of-life
missing
TM: Temperature sensor fault
TM: Unknown alarm
Hub: undervoltage alarm 24 V supply
Hub DRIVE-CLiQ: sign-of-life missing
Hub: Checksum error
Hub: EEPROM checksum incorrect
Hub: Unknown alarm

Alarm at DRIVE-CLiQ socket X100
Cooling system: Alarm has occurred
Cooling system: Conductivity has exceeded the

alarm threshold
Cooling system: Conductivity actual value is not

valid
Cooling system: Cooling liquid temperature has

exceeded the alarm threshold
Excitation group signal alarm
COMM BOARD: Alarm 1
SI Motion: Axis re-configured

SI Motion CU: STOP A initiated
SI Motion CU: STOP B initiated
SI Motion CU: Safe Acceleration Monitor limit

exceeded
SI Motion CU: Tolerance for safe operating

stop exceeded
SI Motion CU: STOP C initiated
SI Motion CU: STOP D initiated
SI Motion CU: STOP E initiated
SI Motion CU: Defect in a monitoring channel

SI Motion CU: Safely-Limited Speed exceeded
SI Motion CU: Checking braking torque for the

brake test
SI Motion CU: Hardware fault safety-relevant

encoder
SI Motion CU: eff.test error safe encoder
SI Motion CU: Test stop running
SI Motion CU: Acceptance test mode active
SI Motion MM: Incorrect parameter value

SI Motion MM: STOP A initiated
SI Motion MM: STOP B initiated
SI Motion MM: Safe Acceleration Monitor limit

exceeded
SI Motion MM: Tolerance for safe operating

stop exceeded
SI Motion MM: STOP C initiated
SI Motion MM: STOP D initiated
SI MM MM: Defect in a monitoring channel

SI Motion MM: Safely-Limited Speed exceeded
SI Motion MM: Test stop running
SI Motion MM: Acceptance test mode active
Internal Software Error
Acknowledgement delay when accessing the

memory
Firmware download DRIVE - CLiQ component
unsuccessful
Drive type unknown
Monitoring master control: Sign-of-life failure

PC
ACX: Parameter back-up file missing
ACX: Re-naming parameter file not successful
ACX: Writing to the parametere back-up file

was unsuccesful
Save parameter settings and carry out a

POWER ON
Parameter error during project download
Fatal error when downloading a project
CU CompactFlash: Message description

incorrect
CompactFlash card and device not compatible
Drive object type is not available
CU: Insufficient memory

CU: Save to CompactFlash card unsuccessful
CU: More than one SINAMICS G on one Control

Unit
CU: SINAMICS S and G together on one Control

Unit
Terminal initialization has failed
Frequency at the measuring probe input too

high
CU: Number if instances of a drive object type

have been exceeded
CU: Time slice overflow
CU: Basic clock cycle selection and DRIVE-CLiQ

clock cycles do not match
CU: Bas clock cyc too low

CU: Bas clock too low
CU: CU-EEPROM incorrect read-only data
CU: Opt. module EEPROM incorrect read-only

data
DRIVE-CLiQ component does not support the

required function
Topology: Component number missing
Topology: Too many components on one line
Topology: Actual topology indicates an illegal

component
Topology: Actual topology changed

Topology: Actual topology is illegal
Topology: Actual topology, duplicate

connection between two components
Topology: Actual topology, defective EEPROM
Topology: Target topology is invalid
Topology: Target topology ring-type

connection
Topology: Target topology duplicate

connection between two components
BICO: Interconnection cannot be established

BICO: No standard telegram
BICO: Internconnections to inactive objects

present
BICO: Signal source is not float type
BICO: Interconnection between different

normalizations
BICO: No normalization available
BICO: Spanning DO between different

normalizations
BICO: Writing to parameter not permitted as

the master control is active
SI CU: STOP A initiated
SI CU: Defect in a monitoring channel
SI CU: STO inputs for power units connected in

parallel different
SI CU: Sign-of-life error in safety data
SI CU: Brake control error
SI CU: Internal software error
SI CU: Acceptance test required
SI CU: Synchronization safety time slices

unsuccessful
SI CU: Illegal monitoring clock cycle
SI CU: PROFIBUS configuration error
SI CU: Align monitoring functions
SI CU: Motor Module parameter error
SI CU: Write request for parameter rejected
SI CU: Safety-related functions not supported
SI CU: Copying of SI parameters rejected

SI CU: No automatic firmware update
SI Motion: Invalid parameterization Sensor

Module
SI Motion: Parameterization encoder error
SI Motion: Motor Module software/hardware

incompatible
SI Motion: Sensor Module software/hardware

incompatible
SI Motion CU: Checksum error safety

monitoring functions
SI Motion CU: Incorrect parameter value
SI Motion CU: Monitoring function not

supported
SI Motion CU: SOS/SLS enable missing
SI Motion: Safely limited position limit values

interchanged
SI Motion CU: Safely-limited speed limit value

too high
SI Motion: Illegal parameterization cam

position
SI Motion: Illegal parameterization modulo

value SCA (SN)
SI Motion CU: Actual value synchronization not

permissible
SI Motion: Data save problem for the NVRAM

DRIVE-CLiQ: Hardware/configuration error
CU DRIVE-CLiQ: POWER ON due to basic

sampling times
SMI: Component found with changed data
PROFIBUS: Setpoint timeout

clock cycle failure

sign-of-life failure
COMM INT: Monitoring time sign-of-life

expired
COMM INT: Monitoring time configuration

expired
PROFIBUS: Connection to the Publisher

aborted
synchronization unsuccessful
CU DRIVE-CLiQ: Synchronization application

clock cycle missing
CU DRIVE-CLiQ: Synchronization of component

not supported
CU DRIVE-CLiQ: Synchronization unsuccessful
Trace: Delete trace because units changed over
OA: internal software error
OA: Insufficient memory
TM: Initialization
TM: Analo input, wire breakage
TM: Module not ready
Parallel circuit configuration: Pulse enable in

spite of pulse inhibit
Parallel circuit configuration: Power module

pulse enable missing
Power circuit: Power units with different code

numbers
Parallel circuit: Power unit EPROM versions

differ
Parallel circuit: Power unit firmware versions

differ
Parallel circuit: VSM EEPROM versions differ
Parallel circuit: VSM firmware versions differ
Parallel circuit: Power unit firmware version

does not match
Infeed, number of VSM
Supply voltage (p0210) incorrectly

parameterized
Drive: Motor overtemperature
Drive: Motor temperature sensor fault
Drive: Incorrect control parameter

Macro: Execution not possible
Macro: ACX file not found
Macro: Condition for WaitUntil not fulfilled
Drive: Open-loop/closed-loop control

parameters changed
Units changeover: Parameter limit violation
due to reference value change
Drive: Sampling times cannot be reset
Drive: Sampling times and basic clock cycle do

not match
Master control PC/AOP inhibited

Drive: Master control by PLC missing
Drive: Line contactor feedback signal missing

Bypass motor switch
Bypass LSS:
Drive: Automatic restart interrupted
Flying restart: Measured search current too

low
FlyRestart: Not Supported
Drive: Lower DC link voltage threshold reached
Drive: Upper DC link voltage threshold reached
Drive: Kinetic buffering minimum speed not

reached
Drive: Kinetic buffering maximum time

exceeded
Drive: Current controller output limited
Drive: Flux setpoint not reached when building

up excitation
Drive: Commutation angle incorrect (motor
model)
Drive: Commutation angle incorrect (pole

position identification)
Drive: Reference model natural frequency >

Shannon frequency
Drive: It is not possible to change the direction

of rotation with the pulses enabled
Drive: Setting the ramp-function generator for
sensorless vector control
LR: Multiturn does not match the modulo

range
LR: Reference point coordinate not in the

permissible range
Load gear: Position tracking cannot be reset

Load gear: Position tracking, maximum actual
value exceeded
Load gear: Position tracking, linear axis has

exceeded the maximum range
Load gear: Position tracking, current position

outside tolerance window
LR: Standstill monitoring has responded
LR: Position monitoring has responded
LR: Following error too high
LR: Position actual value preprocessing error

EPOS: Reference cam not found
EPOS: No zero mark
EPOS: End of reference cam not found
EPOS: Traversing block is inconsistent
EPOS: Target position < start of traversing

range
EPOS: Target position > end of the traversing
range
EPOS: Axis position < software limit switch
minus
EPOS: Axis position > software limit switch plus
EPOS: Fixed stop outside the monitoring

window
EPOS: Fixed stop not reached
EPOS: Relative positioning not possible
EPOS: Enable signal withdrawn while traversing
EPOS: STOP cam minus reached
EPOS: STOP cam plus reached
LR: Overflow of the value range for position

actual value
LR: Drive Data Set changeover in operation
Drive: Encoder Data Set EDS not configured
Drive: Component number missing
Drive: Identical encoder in the drive data set

Drive: Encoder used a multiple number of
times
Drive: Encoder data set changeover cannot be

parameterized
Drive: Power unit and motor incorrectly

connected
Drive: Re-commission the data set
Drive: Encoder data set changeover incorrectly

parameterized
Drive: Motor data set changeover incorrectly
parameterized
Drive encoder: No commutation angle

information
Drive encoder: Encoder configuration not

supported
Drive encoder: Sensor Module configuration
not supported
Drive encoder: Configuration position tracking

Measuring gear: Position tracking, maximum
actual value exceeded
Drive encoder: Number of pulses is not to the

power of two
Drive encoder: Number of multiturn pulses is

not to the power of two
Drive, encoder: Position tracking, incremental

encoder not possible
Drive: Motor encoder not ready

Encoder 1: Adjustment not possible

Drive: No power unit present
Drive: Motor overcurrent
Drive: Infeed or power unit not ready
Drive: Power unit EEPROM without rated data

Drive: Power unit has been changed
Drive: Simulation mode with DC link voltage

too high
Drive: Infeed operation missing
Drive: Infeed operation withdrawn
External fault 1
External fault 2
External fault 3
Internal voltage protection/internal armature
short-circuit with Safe Torque Off active
Drive: Motor locked/speed controller at its

limit
Drive: Motor overspeed

Drive: Motor stalled
External armature short-circuit: Contactor

feedback signal "Open" missing
Armature short-circuit / internal voltage
protection: Parameterization error
Internal armature short-circuit: Motor

terminals are not at zero potential after pulse
suppression
Internal voltage protection: De-activation only
effective after POWER ON
Excitation current outside the tolerance range
Flux out of tolerance
Drive: Torque too low
Drive: Torque too high
Drive: Torque outside the tolerance

Internal voltage protection initiated
Drive: Brake control error
Drv: Motor holding brake detected
Sync-line-drive: Synchronization error
Drive: Incorrect motor parameter

Drive: Motor has been changed
Drive: Motor code does not match the list

(catalog) motor
Drive: Friction characteristic record interrupted
Drive: Automatic encoder adjustment incorrect

Drive: Lq-Ld measurement incorrect
Drive: Incorrect pole position identification

Drive: Automatic encoder adjustment incorrect
Drive: Rotating measurement encoder test
Drive: Rotating measurement saturation

characteristic
Drive: Speed controller optimization, moment
of inertia
Drive: Speed controller optimization

(oscillation test)
Drive: Rotating measurement ramp-function
generator
Drive: Rotating measurement, no configuration

selected
Drive: Rotating measurement leakage

inductance (q-axis)
Drive: Incorrect motor data identification
TB: +/-15 V power supply faulted
TB: Analog-digital converter
COMM BOARD: Monitoring time configuration

expired
COMM BOARD: Monitoring time process data

expired
COMM BOARD: Send configuration data invalid

CBC: Communications error
CBC: NMT state change

Power unit: Overcurrent
Power unit: DC link voltage, overvoltage
Power unit: DC link voltage, undervoltage

Power unit: Overtemperature heat sink AC
inverter
Power unit: Overload I2t
Power unit: Thyristor Control Board
Power unit: Sign-of-life error cyclic data
Power unit: Line phase failure in main circuit
Power unit: Temperature sensor heat sink wire

breakage
Power unit: Temperature sensor heat sink
short-circuit
Power unit: Hardware current limit has

responded too often
Power unit: Configuration not supported
Power unit: Ground fault

Power unit: Monitoring V_ce
Power unit: Chip overtemperature

Power unit: Precharging DC link time
monitoring
Power unit: Air intake overtemperature
Power unit: Electronics board overtemperature
Power unit: Rectifier overtemperature

Power unit: Undervolt 24 V
Power unit: Overvolt 24 V
Power unit: Supply undervoltage
Cooling system: Cooling medium flow rate too

low
Power unit: Supply overvoltage
EEPROM data error
The bypass contactor was opened under

current
Cycle requested by the power unit module not

supported
No new actual values received from the power

unit module
Setpoints are no longer being transferred to
the power unit
Communications error to the power unit
module
PU: Actual value sensing fault
Power unit: DC link voltage, overvoltage
SI MM: STOP A initiated

SI MM: Defect in a monitoring channel
SI MM: Sign-of-life error in safety data

SI MM: Brake control error
SI MM: Fault in the shutdown path of the

second channel
SI MM: Internal software error
SI MM: Acceptance test required
SI MM: Synchronization with Control Unit

unsuccessful
SI MM: Illegal monitoring clock cycle

SI MM: Align monitoring functions
SI MM: Motor Module parameter error
SI MM: Write request for parameter rejected

SI Motion: Control Unit software incompatible
SI Motion MM: Checksum error safety

monitoring functions
SI Motion MM: Monitoring function not

supported
SI Motion MM: SOS/SLS enable missing
SI Motion MM: Safely-Limited Speed limit

value too high
SI Motion MM: Actual value synchronization

not permissible
Power unit DRIVE-CLiQ: Sign-of-life missing
Power unit: Time slice overflow
Power unit: EPROM checksum error
Power unit: Switching information not valid
Power unit DRIVE-CLiQ: Telegram error

Power unit DRIVE-CLiQ: Cyclic data transfer
error
Power unit DRIVE-CLiQ: Send error for DRIVE-

CLiQ data
Power unit DRIVE-CLiQ: Component fault
Power unit DRIVE-CLiQ: Cyclic data transfer

error
Power unit: Internal software error
Power unit DRIVE-CLiQ (CU): Sign-of-life

missing
Power unit DRIVE-CLiQ (CU): Telegram error
CU DRIVE-CLiQ (CU): Cyclic data transfer error
PU DRIVE-CLiQ (CU): Error when sending

DRIVE-CLiQ data
Power unit DRIVE-CLiQ (CU): Component fault
PU DRIVE-CLiQ (CU): Alternating cyclic data

transfer error
Power unit DRIVE-CLiQ (CU): Inconsistent

component properties
Power unit: Unknown fault
Power unit: I2C bus error occurred
Power unit: FPGA configuration unsuccessful

Encoder 1: Zero mark distance error
Encoder 1: Zero marked failed
Encoder 1: Amplitude error, track R

Encoder 1: Serial communications error
Encoder 1: Absolute encoder EnDat, internal
fault/error

Encoder 1: Amplitude error track A/B fault
(A^2 + B^2)
Encoder 1: Amplitude error track A + B
Encoder 1: Inversion error signals A and B and

R
Encoder 1: Speed difference outside the
tolerance range
Encoder 1: Power supply voltage fault
Encoder 1: Internal power supply voltage fault
Encoder 1: Signal level A/B unipolar outside

tolerance
Encoder 1: Amplitude error track A/B
overcontrolled
Encoder 1: Amplitude AB too high

Encoder 1: Zero mark and position error from

the coarse synchronization
Encoder 1: Fault when determining the
position
Encoder 1: Error when determining multiturn
information
Encoder 1: Internal error when determining

the position

multiturn information
Encoder 1: Initialization error
Encoder 1: Encoder speed for initialization AB

too high
Encoder 1: Temperature in the encoder
evaluation inadmissible
Encoder 1: Position tracking traversing range

exceeded
Encoder 1: Position tracking encoder position

Encoder 1: Encoder with measuring gear,

without valid signals
Encoder 1: Position tracking cannot be reset
Encoder 1 DRIVE-CLiQ: Sign-of-life missing

Encoder 1: Time slice overflow
Encoder 1: Checksum error
Encoder 1: EPROM checksum error
Encoder 1: Requested cycle or RX-/TX timing

not supported
Encoder 1: Hardware logic unit failed

Encoder 1 DRIVE-CLiQ: Telegram error
Encoder 1 DRIVE-CLiQ: Cyclic data transfer

error
Encoder 1 DRIVE-CLiQ: Send error for DRIVE-

CLiQ data
Encoder 1 DRIVE-CLiQ: Component fault

error
Encoder 1: Encoder evaluation, internal

software error
Encoder 1 DRIVE-CLiQ (CU): Sign-of-life missing

Encoder 1 DRIVE-CLiQ (CU): Telegram error
Encoder 1 DRIVE-CLiQ (CU): Cyclic data transfer

error
Encoder 1 DRIVE-CLiQ (CU): Error when
sending DRIVE-CLiQ data
Encoder 1 DRIVE-CLiQ (CU): Component fault
Encoder 1 DRIVE-CLiQ (CU): Alternating cyclic

data transfer error
Encoder 1 DRIVE-CLiQ (CU): Inconsistent

Encoder 1: Unknown fault

Encoder 1: Parameterization error


fault/error

(A^2 + B^2)

R
tolerance range

tolerance
overcontrolled



position
information

the position


too high

exceeded




not supported


error

CLiQ data

error

software error


error
Component number: %1, fault cause: %2

data transfer error




fault/error

(A^2 + B^2)

R

tolerance range

tolerance

overcontrolled


position

information

the position


too high


exceeded



not supported

error

CLiQ data

error

software error


error

data transfer error


VSM: Temperature fault threshold exceeded

VSM DRIVE-CLiQ: Sign-of-life missing
VSM: Time slice overflow

VSM: Memory test
VSM: CRC
VSM: EPROM checksum error
VSM: Initialization
VSM DRIVE-CLiQ: Telegram error

VSM DRIVE-CLiQ: Cyclic data transfer error
VSM DRIVE-CLiQ: Send error for DRIVE-CLiQ

data
VSM DRIVE-CLiQ: Component fault
VSM DRIVE-CLiQ: Cyclic data transfer error
VSM: Internal software error
VSM DRIVE-CLiQ (CU): Sign-of-life missing

VSM DRIVE-CLiQ (CU): Telegram error
VSM DRIVE-CLiQ (CU): Cyclic data transfer

error
VSM DRIVE-CLiQ (CU): Error when sending

DRIVE-CLiQ data
VSM DRIVE-CLiQ (CU): Component fault
VSM DRIVE-CLiQ (CU): Alternating cyclic data

transfer error
VSM DRIVE-CLiQ (CU): Inconsistent component

properties
VSM: Unknown fault
TM54F: Sampling time invalid
TM54F: Parameter value invalid

TM54F: Commissioning not possible
TM54F: Acknowledgement on the Control Unit

is required
TM54F: Drive object number assignment illegal
TM54F: Test stop error
TM54F: 24 V undervoltage
TM54F: 24 V overvoltage
TM54F: Defect in a monitoring channel
TM54F: Internal hardware fault
TM54F: Temperature fault threshold exceeded
TM54F: Communication error

TM54F: Discrepancy error
TM: Temperature fault/alarm threshold

exceeded
TM: Frequency limit reached for signal output
TM: Setpoint - actual value deviation, outside

the tolerance range
HW problem with the TM module
DRIVE-CLiQ component does not support the

required function
TM DRIVE-CLiQ: Telegram error

TM DRIVE-CLiQ: Cyclic data transfer error
TM DRIVE-CLiQ: Send error for DRIVE-CLiQ

data
PTM DRIVE-CLiQ: Component fault
TM DRIVE-CLiQ: Cyclic data transfer error
TM: Internal software error
TM DRIVE-CLiQ (CU): Sign-of-life missing

TM DRIVE-CLiQ (CU): Telegram error
TM DRIVE-CLiQ (CU): Cyclic data transfer error

TM DRIVE-CLiQ (CU): Error when sending
DRIVE-CLiQ data
TM DRIVE-CLiQ (CU): Component fault
TM DRIVE-CLiQ (CU): Alternating cyclic data

transfer error
TM DRIVE-CLiQ (CU): Inconsistent component

properties
TM: Unknown fault
Hub: Overtemperature component

Hub: overvoltage fault 24 V supply
Hub: undervoltage fault 24 V supply
Hub: Time slice overflow
Hub DRIVE-CLiQ: Telegram error
Hub DRIVE-CLiQ: Cyclic data transfer error

Hub DRIVE-CLiQ: Send error for DRIVE-CLiQ
data
Hub DRIVE-CLiQ: Component fault
Hub DRIVE-CLiQ: Cyclic data transfer error
Hub DRIVE-CLiQ (CU): Sign-of-life missing

Hub DRIVE-CLiQ (CU): Telegram error
Hub DRIVE-CLiQ (CU): Cyclic data transfer error

Hub DRIVE-CLiQ (CU): Error when sending
DRIVE-CLiQ data
Hub DRIVE-CLiQ (CU): Component fault
Hub DRIVE-CLiQ (CU): Alternating cyclic data

transfer error
Hub DRIVE-CLiQ (CU): Inconsistent component

properties
Hub: Unknown fault
Fault at DRIVE-CLiQ socket X100

Evaluate the fault buffer of the specified
object.
CX32: Configured transfer end time exceeded
CX32 DRIVE-CLiQ: Sign-of-life missing
CX32 DRIVE-CLiQ: Telegram error

CX32 DRIVE-CLiQ: Cyclic data transfer error
CX32 DRIVE-CLiQ: Send error for DRIVE-CLiQ

data
CX32 DRIVE-CLiQ: Component fault
CX32 DRIVE-CLiQ: Cyclic data transfer error
CX32 DRIVE-CLiQ (CU): Sign-of-life missing

CX32 DRIVE-CLiQ (CU): Telegram error
CX32 DRIVE-CLiQ (CU): Cyclic data transfer

error
CX32 DRIVE-CLiQ (CU): Error when sending

DRIVE-CLiQ data
CX32 DRIVE-CLiQ (CU): Component fault
CX32 DRIVE-CLiQ (CU): Cyclic data transfer

error
Cooling system: Fault occurred
Cooling system: Conductivity has exceeded the

fault threshold
Cooling system: ON command feedback signal

missing
Cooling system: Liquid flow too low

Cooling system: Liquid leak is present
Cooling system: Power Stack Adapter,

firmware version too old
Cooling system: Cooling liquid temperature has

exceeded the fault threshold
Excitation group signal fault
Internal software error
SI CU: Safe Torque Off active
SI CU: Safe Stop 1 active

(chassis PU)
SI MM: Safe Torque Off active

SI MM: Safe Stop 1 active
Power unit: Group signal

Encoder 1: Amplitude error track A/B alarm
(A^2 + B^2)
(A^2 + B^2)
Encoder 2: Group signal

(A^2 + B^2)
Encoder 3: Group signal

VSM: Group signal
TM: Group signal
Hub: group signal

Register file error
RAM error


Serial line error
Keyboard error
V1.8:
EEprom not writable
V2.3:
Relays supply error
V1.8:
Division by zero
V2.3:
EEprom not writable
V1.8:
Wrong active display, V2.3:
EEprom checksum error
V1.8:
Relays supply error, V2.3:
Wrong active display
Watch dog error

201xx(bootstrap)
202xx(bootstrap)
203xx (bootstrap)
204xx(bootstrap)
checksum incorrect.


connected

connected

configuration

(CMS1, CMS2)

system
Motor stalled
Motor Overtemperature
Motor Underload
Stored Data has been changed
Changed Application failed

Unbalance current fault
Overtemperature
Reference Warning
External warning
Overcurrent
Input line supervision

Output phase supervision
Brake chopper supervision
Drive undertemperature
Motor stalled
Motor temperature
Motor underload
Analogue input polarity fault or analogue input
hardware fault
Option board identification
Overvoltage
10V voltage reference

24V supply
EEPROM check-sum fault
EEPROM check-sum fault
Microprocessor Watchdog
Panel communication error

Thermistor Protection
Ground Fault
Analog input Iin < 4mA (signal range selected 4-

20mA)
Inverter Fault
External Fault
Charging Switch
Undervoltage
System input Error
Braking Transistor Overload Fault
Option Communication Error

MEMOBUS/Modbus Communication Error
Control Fault
The torque limit was reached continuously for three
seconds or longer while ramping to stop in OLV
Control.
Control Circuit Error
- A/D Conversion Error

- An A/D conversion error or control circuit error
occurred.
- Control Board Connection Error

- Connection error between the control board and
the drive
- EEPROM Memory Data Error

- Error in the data saved to EEPROM
Terminal Board Connection Error
Control Circuit Error
Hybrid IC Failure
- Control Board Connection Error

-Connection error between the control board and
the drive
Drive Unit Signal Fault

-The drive capacity cannot be detected correctly
(drive capacity is checked when the drive is
powered up).
- Control Circuit Error

- CPU error
- Speed Deviation (for Control Mode with PG)
-The deviation between the speed reference and
speed feedback is greater than the setting in F1-10
for
longer than the time set to F1-11.
- Z Pulse Fault
- The motor turned one full rotation without the Z
Pulse being detected.
- Z Pulse Noise Fault Detection

- The Z Pulse is out of phase by more than 5
degrees for the number of times specified in
parameter F1-17.
- Inversion Detection
- The torque reference and acceleration are in
opposite directions and the speed reference and
actual motor
speed differ by more than 30% for the number of
times set to F1-18.
- Inversion Prevention Detection

- Pulses indicate that the motor is rotating in the
opposite direction of the speed reference. Set the
number
of pulses to trigger inverse detection to F1-19.
Polarity Judge Timeout
DriveWorksEZ Fault
- SI-T3 Watchdog Timer Error
- The watchdog timed out.
- Option Card External Fault

- An external fault condition is present.
- External Fault (input terminal S1)

- External fault at multi-function input terminal S1.







- EEPROM Write Error

- Data cannot be written to the EEPROM
- Internal Fan Fault
- Fan or magnetic contactor failure
Excessive PID Feedback

PID feedback input is greater than the level set to
b5-36 for longer than the time set to b5-37. Set b5-
12
to 2 or 5 to enable fault detection.
- PID Feedback Loss

- This fault occurs when PID feedback loss detection
is programmed to trigger a fault (b5-12 = 2) and the
PID feedback level is below the detection level set
to b5-13 for longer than the time set to b5-14.
Ground Fault
• A current short to ground exceeded 50% of rated
current on the output side of the drive.
• Setting L8-09 to 1 enables ground fault detection.
Output Phase Loss

• Phase loss on the output side of the drive.
• Setting L8-07 to 1 or 2 enables Phase Loss
Detection.
Output Current Imbalance

One or more of the phases in the output current
are lost.
Power Unit Output Phase Loss 3

• Phase loss occurred on the output side
• Setting L8-78 to 1 enables Power Unit Output
Phase Loss Protection
Node Setup Error

A terminal assigned to the node setup function
closed during run.
Overcurrent
Drive sensors detected an output current greater
than the specified overcurrent level.
Option Card Connection Error at Option Port CN5-A

Option compatibility error
- Option Card Fault at Option Port CN5-A

- Option not properly connected
Option Card Error Occurred at Option Port CN5-A
Option Card Error Occurred at Option Port CN5-A
Option Card Connection Error (CN5-A)
Communication Option Card Connection Error

(CN5-A)
- Option Card Fault at Option Port CN5-B

- Option compatibility error
Option Card Fault at Option Port CN5-B

Option not properly connected
Option Card Fault at Option Port CN5-B

Same type of option card is currently connected
Option card error occurred at Option Port CN5-B

Option card error occurred at Option Port CN5-B
- Option Card Connection Error at Option Port CN5-

C
- Option compatibility error
- Option Card Fault at Option Port CN5-C
- Option not properly connected
- Option Card Fault at Option Port CN5-C

- Same type of option card is currently connected
Option Card Error Occurred at Option Port CN5-C
Option Card Error Occurred at Option Port CN5-C
Heatsink Overheat
The heatsink temperature exceeded the overheat
pre-alarm level set to L8-02. The default value for
L8-02
is determined by drive capacity (o2-04).
Overheat 1 (Heatsink Overheat)

The heatsink temperature exceeded the drive
overheat level. Overheat level is determined by
drive
capacity (o2-04).
Motor Overheat Alarm (PTC Input)

• The motor overheat signal to analog input
terminal A1, A2, or A3 exceeded the alarm
detection level.
• Detection requires setting multi-function analog
inputs H3-02, H3-06, or H3-10 to E.
Motor Overheat Fault (PTC Input)

• The motor overheat signal to analog input
terminal A1, A2, or A3 exceeded the fault detection
level.
• Detection requires setting multi-function analog
inputs H3-02, H3-06, or H3-10 to E.
Motor Overheat (NTC Input)

The motor temperature exceeded the level set to
L1-16 (or L1-18 for motor 2)
Motor Overload
The electronic motor overload protection tripped
- Drive Overload
- The thermal sensor of the drive triggered overload
protection.
Overtorque Detection 1
The current has exceeded the value set for torque
detection (L6-02) for longer than the allowable time
(L6-03).
- Overtorque Detection 2
- The current has exceeded the value set for
Overtorque Detection 2 (L6-05) for longer than the
allowable
time (L6-06).
- Mechanical Weakening Detection 1

- Overtorque occurred, matching the conditions
specified in L6-08.
- High Slip Braking oL
- The output frequency stayed constant for longer
than the time set to n3-04 during High Slip Braking.
External Digital Operator Connection Fault
Overspeed (for Control Mode with PG)

The motor speed feedback exceeded the F1-08
setting.
Overvoltage
- Input Phase Loss
- PG Disconnect (for any control modes using a PG

option card)
- No PG pulses are received for longer than the time
set to F1-14.
- PG Hardware Fault (detected when using a PG-X3

option card)
- PG cable is not connected properly.
Braking Resistor Fault
Braking Resistor Overheat
Dynamic Braking Transistor
IGBT Short Circuit or Ground Fault
Too Many Speed Search Restarts
Motor Pull Out or Step Out Detection
Zero Servo Fault
Thermistor Disconnect
Undertorque Detection 1
Undertorque Detection 2
Mechanical Weakening Detection 2
Current Unbalance
DC Bus Undervoltage
Control Power Supply Voltage Fault
Undervoltage 3 (Soft-Charge Bypass Circuit Fault)
Gate Drive Board Undervoltage
Output Voltage Detection Fault
base block
close brake
open brake
calculate drive
DC brake
Low speed/dc brake
forward acceleration
forward constant
forward deceleration
hardware current limit
LA stop
Ld stop
Low speed/dc brake

power unit not ready
no operation
positioning active
low speed/power off
position not reachable
power off function
positioning active
reverse acceleration
reverse constant
reverse deceleration
ready for positioning

Stall
search for ref.active

speed search
quick stop
Error! Brake
Error! Watchdog
Error! Calc.drive data

Error! Counter overrun 1
Error! Counter overrun 2
Error! Drive overheat
Error! Drive relay
Error! EEPROM defective t
Error! External fault
Error! Encoder cable

hybrid
Error! Hybrid changed
Error! Input error detect
Error! Initialisation MFC

Error! Load shunt fault
no ERROR drive overheat
no E. over heat pow.mod.
no ERROR overheat. Int
no ERROR overload
no ERROR
Error! Overcurrent
Error! Overhead pow.mod
Error! Motor protection

Error! Overheat internal
Error! Overload (Ixt)
Error! Overload 2
Error! Over voltage
Error! Over speed

Error! Power factor control
Error! Prot. Rot. For
Error! Prot . Rot. Rev
Error! Power unit

Error! Unknown power unit
Error! Power unit changed
Error! Power unit communication
Error! Power unit invalid
Error! Bus synchron
Error! Set
Error! Software limit switch forward
Error! Software limit switch reverse

Error! Under potential
Error! Phase failure

Warning! Watchdog
Warning! Drive overhead
Warning! External fault
All-clear! Drive overheat
All-clear! Overhead pow.mod

All clear! Internal
All clear! Overload

All clear! Overload 2
Warning! Overhead pow.mod
Warning! Motor protection
Warning! Overheat internal
Warning! Overload
Warning! Overload 2
Warning! Prot.rot.for.
Warning! Prot.rot.rev
Warning ! Synchron
Warning! Set
Warning! Software limit switch forward
Warning! Software limit switch reverse
AI2 Input
DBR overload
DB unit sh. Circuit
Precharge
Thyr. Soft charge
Control Eeprom
Power Eeprom
Out contact stuck
IGBT desaturation
Rating error
Incompatible PB
Internal serial link
internal MFG area

Internal option
Internal hard init
Internal ctrl supply
Internal-I measure
Internal-mains circuit
Internal-th sensor
Internal-time meas.
internal - CPU
Overcurrent
Power Removal
Motor short circuit
Impudent sh. Circuit
Ground short circuit
over speed
speed feedback loss
Auto-tuning
Application fault
Com. Network
CAN com.
External flt-Ll/bit
External fault com.
Out contact open.
input contractor
AI2 4-20mA loss

AI3 4-20mA loss
AI4 4-20mA loss
No flow fault
Over braking
Drive overheat
Proc overload Flt
Motor overload
1 Motor phase loss

3 motor phase loss
Mains overvoltage
PTC1 overheat
PTC2 overheat
PTC=LI6 overheat
PTC1 probe
PTC2 probe
LI6 = PTC probe

IGBT short circuit
Motor short circuit
Modbus com.
PowerSuite com
HMI com
PI feedback
Torque/current lim
IGBT overheat
Proc. Under load Fit
Incorrect config
invalid config
Card pairing
Input phase loss
Power Ident
Under voltage
Converter Status failures
The communicated messages cannot be

decoded, nor conforms with the expected
message
Communications cannot be understood or are
not conform the expected messages
DC Link fluctuations

See F0022 - Power stack fault

Converter Status failures (see ECB AIF1633)
ABB: External Control Location = EXT2

(expected to be EXT1)
Vacon: Remote Control = OFF (ON expected)

Remote Control of Converter is OFF (expected
to be ON)


External Run Enable = OFF, (expected to be =

ON)

ON)
Status Word 1, bit 5,6 active->switchon inhibit

Problem cannot be read, please check the

frequency converter panel
Short circuit
System Fault
Earth Fault - Load imbalance
Overcurrent
Thermistor problem
DC Over Voltage
ACS 600 / 800 temperature is excessive
No communication between Elektronikon and

converter
No communication between Elektronikon and

converter
Problem cannot be read, please check the
frequency converter panel
Short circuit
System Fault
Earth Fault - Load imbalance
Overcurrent
Thermistor problem
DC Over Voltage
ACS 600 / 800 temperature is excessive
The communicated messages cannot be

decoded, nor conforms with the expected
message
DC Link fluctuations


Remote Control of Converter is OFF (expected
to be ON)


ON)

ON)
Status Word 1, bit 5,6 active->switchon inhibit



Commissioning Parameter (P010) has wrong

definition
Expansion module No. 1 has problem

External alarm 1
External alarm 2
Drive is not in healthy state
Overcurrent
Overvoltage
Inverter temperature
Motor temperature
Motor movement
I2t inverter
I2t motor
Overspeed
Setpoint/actual value deviation
Motor stall/lock
Ls, Rr Dev
Stands. Meas
Mld Inv Stop
Motld: Dr.M
Insufficient power to display panel (PMU)
Converter Fail. Undefined error code, not enough

time to register fault
Contactor Checkback
Pre-Charging
DC link Overvoltage
DC link Undervoltage
DC link Overvoltage
Overcurrent
Current too Low
I too low
Motor Stall
Motor not found

Motor Temperature
Motor I2t
Inverter Temperature
UCE ph. L1
UCE ph. L2
UCE ph. L3
Supply phase
External fault 1
External fault 2
AS internal fault
EEPROM fault
Coupling int.
BiCo manager Fault
Opt. Board HW
Par task / con.
GRND Init
GRND UCE
GRND Phase
Ground fault
Overcurrent
Motor Overload
Motor Pullout
Active Signal @ binector U061 is present.
Motor stall
PreCharge Error
Motor Temp.
Motor I2t. Parameterized limit value of the i2t

monitoring for the motor was excedded
Inverter Temp.
Link Internal
UCE ph. L1
Fault in EEPROM
UCE ph. L2
UCE ph. L3
Supply phase
Undervoltage
One phase missing
External fault 1
External fault 2
AC-Line Fault
AS internal fault
EEPROM fault
Coupling int.
BiCo manager Fault

Opt. Board HW
Par task / con.
Overvoltage
Heat Sink Temp
Motor Overtemp
CU: DC voltage too low

CCU: Pulsed Res Temp
Imbalance or Input Phase Loss. Mains voltage

imbalance too high or phase missing
in the input power supply.
Note:
- If the motor is unloaded or operating with
reduced
load this fault may not occur.
- Fault delay is set at parameter P0357
P0357 = 0 disables the fault.
DC bus undervoltage condition occurred.

DC bus overvoltage condition occurred.
Power Module U Fault. Desaturation of IGBT

occured in Power Module U.
Power Module V Fault. Desaturation of IGBT
occured in Power Module V.
Power Module W Fault. Desaturation of IGBT
occured in Power Module W.
DB IGBT Fault. Desaturation of Dynamic
Braking IGBT occured.
High Load on Motor. Load is too high for the
used motor.
Note:
It may be disabled by setting P0348 = 0 or 2.
IGBTs Overload Alarm. An IGBTs overload

alarm occurred.
Note:
IGBTs Overload Fault. An IGBTs overload fault

occurred.
IGBTs High Temperature
U. A high temperature alarm was detected by
the NTC
temperature sensors located on the IGBTs.
Note:
IGBTs Overtemperature U. A high temperature

fault was detected by the NTC
temperature sensors located on the IGBTs.
High Temperature on
IGBTs V. Alarm of high temperature measured
at thetemperature sensors (NTC) of the IGBTs.
Note:
It can be disabled by setting P0353 = 2 or 3.
Overtemperature on
IGBTs V. Fault of overtemperature measured at
the temperature sensors (NTC) of the IGBTs.
High Temperature on
IGBTs W. Alarm of high temperature measured
at the temperature sensors (NTC) of the IGBTs .
Note:
It can be disabled by setting P0353 = 2 or 3.
Overtemperature on
IGBTs W. Fault of overtemperature measured
at the temperature sensors (NTC) of the IGBTs.
Thermal Imbalance. Fault of power module

temperature imbalance.
Encoder/Motor Wiring is
Inverted. Fault related to the phase relation of
the encoder
signals if P0202 = 4 and P0408 = 0, 2, 3 or 4.
Note:
- It is not possible to reset this fault during the
selftuning.
- In this case, power down the inverter, solve
the
problem and then power up.
- When P0408 = 0, this fault can be deactivated
by means of parameter P0358. In this case, it is
not
possible to reset the fault.
Overcurrent/Short-circuit. Overcurrent or
short-circuit detected at the output, in the DC
bus, or at the braking resistor.
Output Overcurrent. The inverter output

current was too high for too long.
Motor Overload. The motor overload

protection operated.
Note:
Ground Fault. A ground fault occured either in

the cable between
the inverter and the motor or in the motor
itself.
Note:
It may be disabled by setting P0343 = 0.
Motor Current
Imbalance. Fault of motor current unbalance.
Note:
It may be disabled by setting P0342 = 0.
DB Resistor Overload. The dynamic braking

resistor overload protection
operated.
Motor
Overtemperature. Fault related to the PTC
temperature sensor installed
in the motor.
Note:
- It may be disabled by setting P0351 = 0 or 3.
- It is required to set the analog input / output
to the
PTC function.
Encoder Signal Fault. Lack of encoder signals.

By Hw - fault can be disable with switch of
ENC1
and ENC2 board.
By Sw - fault can be disable at parameter
P0358.
CPU Watchdog. Microcontroller watchdog

fault.
Copy Function Fault. Fault while copying
parameters.
Auto-diagnosis Fault.
Communication Lost. Indicates a problem
between the keypad and control
board communication.
External Alarm. External alarm via digital input.
Note:
It is required to set a digital input to "No
external
alarm".
External Fault. External fault via digital input.

Note:
It is required to set a digital input to "No
external
fault".
Invalid Current Offset. Current measurement

circuit is measuring a wrong
value for null current.
High Motor
Temperature. Alarm related to the PTC
temperature sensor
installed in the motor.
Note:
- It may be disabled by setting P0351 = 0 or 2.
- It is required to set the analog input / output
to the
PTC function.
Timeout for Serial

Communication. Indicates that the inverter
stopped receiving valid
messages within a certain time interval.
Note:
It may be disabled by setting P0314 = 0.0 s.
Anybus is Offline. Alarm that indicates

interruption of the Anybus-CC
communication.
Anybus Access Error. Alarm that indicates an

access error to the
Anybus-CC communication module.
CAN Not Powered. Alarm indicating that the
power supply was not
connected to the CAN controller.
Bus Off. Inverter CAN interface has entered
into the bus-off
state.
CANopen
Communication Error. Alarm that indicates a
communication error.
Idle Master. Network master has entered into
the idle state.
DNet Connection Timeout. I/O connection
timeout - DeviceNet communication
alarm.
Profibus DP Interface in
Clear Mode. It indicates that the inverter
received a command
from the Profibus DP network master to enter
the clear mode.
Offline Profibus DP
Interface. It indicates an interruption in the
communication
between the Profibus DP network master and
the
inverter.
Profibus DP Module
Access Error. It indicates an error in the access
to the Profibus DP
communication module data.
Motor Overspeed. Overspeed fault.

It is activated when the real speed exceeds the
value
of P0134 x (100 % + P0132) for more than 20
ms.
FLASH Memory Module

Fault. FLASH Memory Module fault (MMF-03).
Internal Air High

Temperature. Alarm indicating that the
internal air temperature is
too high.
Note:
Internal Air
Overtemperature. Internal air
overtemperature fault.
Undertemperature. Only 1 sensor indicates

temperature below -30 ºC
(-22 °F).
Undertemperature. Undertemperature fault
(below -30 °C (-22 °F)(13)) in
the IGBTs or rectifier measured by the
temperature
sensors.
Safety Stop Relays. Safety Stop relay fault.
Timeout PLC11CFW-11. Refer to the PLC11-01

module programming manual.
Incompatible PLC
Firmware. Refer to the PLC11-01 module
programming manual.
Break Detect AI1. It indicates that the AI1
current (4-20 mA or 20-4 mA)
reference is out of the 4 to 20 mA range.
Left Fan Speed Fault. Heatsink left fan speed
fault.
Center Fan Speed Fault. Heatsink center fan

speed fault.
Right Fan Speed Fault. Heatsink right fan speed

fault.
Fan Replacement. Fan replacement alarm

(P0045 > 50000 hours).
Note:
This function may be disabled by setting P0354
= 0.
Fan Speed Alarm. Alarm referring to the fan

speed of the heatsink.
Heatsink Fan Speed Fault. This fault indicates a

problem with the heatsink fan.
Note:
This function may be disabled by setting P0354
= 0.
Invalid Clock Value. Invalid clock value alarm.
Pulse Feedback Fault. Indicates a fault on the

output pulses feedback.
IGBTs Overload +
Temperature. Overtemperature related to the
IGBTs overload
protection.
Pre-charge Contactor
Fault. It indicates fault at the pre-charge
Contactor.
Sensor 1 Temperature
Fault. It indicates a temperature fault at the
sensor 1.
sensor 2.
Sensor 3 Temperature. It indicates a
temperature fault at the sensor 3.
Sensor 4 Temperature. It indicates a
temperature fault at the sensor 4.
sensor 5.
Alarm. It indicates a temperature alarm at the
sensor 1.
Sensor 2Temperature
sensor 2.
sensor 3.
sensor 4.
sensor 5.
Sensor 1 Cable Alarm. Sensor 1 cable alarm.
Sensor 2 Cable Alarm.
Serial Communication
Timeout
Anybus Offline
Anybus Access Error
CAN Bus Power Failure
Bus Off
CANopen
Communication Error
Master Idle
DeviceNet Connect
Timeout
Profibus DP Interface in
Clear Mode
Offline Profibus DP
Interface
Profibus DP Module
Access Error
IGBT Curr. Imb. Fault. Fault of current
imbalance on the IGBTs.
Thermal Imbalance. The temperature
difference between IGBT modules of
the same phase (U, V, W) was above 10 °C (50 °
F).
Air Control Overtemp. Fault of
overtemperature of the internal air on the
control board.
Control Air Temperature
High Alarm. Alarm of overtemperature of the
internal air on the
control board.
Detached HMI. Alarm or fault related to the

HMI disconnection
Detached HMI. Alarm or fault related to the
HMI disconnection
Inverter Disabled. Alarm indicating that the
General Enable command
is not active.
Two Movements Enabled
Speed Reference Not

Programmed for SoftPLC. Speed reference not
programmed for SoftPLC
Cause
Faulty Board, loose connections (ribbon cables) inside.
Elektronikon try again and again to start, but system keeps on re-starting and
PROGRAMMED STOP is present repeatedly
Relay damaged, internal error

Unrecoverable failures generated by the regulator.
- Compressor is running or standing still. Regulator is powered up. Only one
contact (out of three) of the Emergency stop button is activated. This means that
the power suppl
Relay possibly damaged due to incorrect power input

In Most cases, attributed to a voltage coming in through one of the digital inputs.
But digital inputs are voltage free contacts.
Chances are FET, and or diodes had gone. Possible what happen here is when the
connector is put upside down, and when 24V
Relay possible damaged due to incorrect power input
- Elektronikon is not powered up. Only one contact (out of three) of the Emergency
stop button is activated. Power is restored to the Elektronikon. At this moment the
power supply to the internal relays
Most probably due to a short circuit of the 12V supply for the digital inputs

Internal error
Some external conditions were not met while system was checking for operation.
Recoverable failure.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
Hardware or software problem.
Unrecoverable error. Caused by corruption within the electronics to misread.

Internal error
Internal error
Line Failute detected; in the "Ready" and "On" states, and alarm is output initially
for 120 S followed by converter shutdown with fault message; a line failure during
DC Link precharging causes immediate shutdown; onkly an alarm is output in other
operat
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
Internal communication between master and a com. Module
Internal communication between master and com. Module
Module 01 became inoperative and it was connected to another operative module
Module XX became inoperative and it was connected to another operative module
eg. ZR315VSD with COM2 modbus module

F71XX ==> 01 = fault @ module 01 (module 01 = SIOE module)
==> 02 = fault @ module 02 (module 02 = VSD's COM2)
==> 03
Module 01 (COM module) is inoperative by incorrect programming or by

connecting an empty module.

- Loose connection between HRR and converter.
- COM 1 (or COM 2) is faulty
- CU /CUVC in doubt (Siemens)
- PSU card (it is possible that 24Vdc is available for the CUVC, however, there may
not be +/- 5, or 15V for other functions)
- GAX card (power supply
Error 0 - incorrect data format (byte 6/7, readback status)

Error 100 - incorrect data format (byte 2/3/8/9, parameters)
Error 200 - Checksum failure
Siemens VSD: A possible fault would that some data in EPROM is lost, or
corrupted, or during programming,

A fault has occur, however the message has been masked by the parameter P60
Converter failure readng failed
Parameterizable external alarm input 1 has been activated
- Possibly due to faulty IGD. SS is also not able to perform properly. R012 (Active
BICO) does not change state when SS change position
- Also possible is power supply card is faulty, hence not able to give the converter
the correct signals to inhibit the
An overcurrent condition has occurred
An overvoltage condition has occurred
The threshold for initiating an alarm has been exceeded.
The parameterizable threshold for initiating an alarm has been exceeded.
The motor has been moved during motor data identification

If the instantaneous load condition is maintained, then the inverter will be
thermally overloaded.
The parameterized limit value for the I2t monitoring of the motor has been
exceeded.
Bit 3 in r553 status word 2 of the setpoint channel. The speed actual value has
exceeded the value of maximum speed plus the set hysteresis.
Bit 8 in r552 status word 1 of the setpoint channel. The difference between
frequency setpoint/actual value is greater than the parameterized value and the
control monitoring time has elapsed.
Motor is stalled or blocked.
The alarm cannot be influenced by P805 "PullOut/BlckTime", but by P794

"Deviation Time"
The measured values of the leakage measurement or of rotor resistance deviate

significantly.
The standstill measurement is executed when the converter is powered up. The
motor can align itself several times in a certain direction with this measurement.
The rotating measurement has been aborted or cannot commence because an

inverter stop command is present.
When the converter is powered up, the rotating measurement automatically

accelerates the drive. The drive can then only be externally controlled in a
restricted fashion.
Either the power supply card (PSU1) or the CUVC card is faulty.
- This is an defined error code, meaning that there was not enough time to read
out the fault message from the converter.
- Most probably caused by a voltage interruption.

If the a contactor checkback signal is configured, a checkback signal was not
received within 500ms after the power-up command
- When pre-charging, the minimum DC link voltage (P071 Line volts x 1.34) of 80%
has not been reached .
- The maximum pre-charging time of 3 seconds has been exceeded.
- SHOULD NEVER HAPPEN DURING OPERATION, ONLY HAPPEN AT STARTUP
- Shutdown due to excessive DC link voltage
- The lower limit value of 76% of the DC link voltage (P071 Lin Volts), or 61% when
kinetic buffering has benn enabled, has been fallen short of.
- Undervoltage in the DC link with active kinetic buffering and speed less than 10%
of the rated motor speed.
MOST UNLIKELY TO OCCUR IN OUR APPLICATION

- Due to excessive DC link voltage, shutdown has taken place.
- Lower threshold value than F006
- Overcurrent shutdown has occurred.
- The shutdown threshold has been reached.
- The phase in which an overcurrent has occurred is indicated in a bit-coded
manner in the fault value (see r949)
Phase U--> Bit 0 = 1--> fault value = 1
Phase V--> Bit 1 = 1-
During excitation of the induction motor, the current did not rise above 12.5% of
the setpoint magnetising current for no-load operation
SHOULD NOT HAPPEN

- During excitation of the motor, the current component is less than 25% of the
motor no-load current
- Only U800 = 1
irrespective of the type of control
(Difference to F012)
- Likely cause is mechanical blockage of motor

- Motor has stalled or locked
- If the static load is too high
- Possible that a bearing has failed, ie, the non-drive end, thus still enable the
motor the ability to rotate at slow speed
- Drive in running
- Motor been stolen / not there

- Flying restart without tachometer
The motor temperature limit value has been exceeded.
* r949 = 1 means limit value of motor temperature exceeded
* r949 = 2 means short-circuit in cable to the motor temperature sensor or sensor
defective.
* r949 = 4 means wire break in cable to the motor
Parameterized limit value of the I2t monitoring for the motor has been exceeded.
The limit value of the inverter temperature has been exceeded.
R949 = 1 : Limit value of inverter temperature has been exceeded.

R949 = 2 : Sensor 1 : wire break of sensor cable or sensor defective.
r949 = 18 : Sensor 2 : " "
r949 = 34 : Sensor 3 : " "
- Loose / bad connection,
- Short circuit in one of the electronics board,
- Imbalance in supply line voltage
- IGBT / IGD1 faulty.
Higher level of F11

Higher level of F11

Higher level of F11
The frequency and amplitude of the DC link ripple indicates a single phase supply
failure.
Similar to F8
Fault occurs in the measured value sensing system

r949 = 1 Offset adjustment not possible in phase L1
r949 = 2 Offset adjustment not possible in phase 3
r949 = 3 Offset adjustment not possible in Phases 1 & 3
r949 = 65 The analog inputs cannot be automati
- External fault 1 has been triggered

- External fault 1 parameter is used for temperature sensor for the cabinet, and it
is parameterised trigger when temp reaches 51 deg. C
Usually happen during hot weather / conditions

P575 Src No ExtFault1

- This failure can be caused by a wrong or loose connection from the micromaster
(fan motor control ) to the main convertor (main motor control). GA180VSD and
others which have micromaster
- Aux. Drive Fault. ZT37VSD
Incorrect operating status
a fault has occurred when storing the values in the EEPROM
Calculating time problem
Internal coupling error. One of the two coupling partners does not respond
- A fault has occurred during the softwiring of Binectors and connectors
Hardware fault has occurred when assessing an optional board
A fault has occur during the transfer of parameters to the gating unit processor
The calculating time in the gating unit computer is not sufficient
During the ground fault test, a current not equal to 0 was measured, or a UCE or
the overcurrent monitoring responded, although none of the valves were
triggered.
During the ground fault test a UCE monitoring function responded in a phase in
which no valve was triggered
Transistor conductive when not triggered to do so
During the ground fault test, current flowed in one phase when none of the valves
were triggered, or the UCE monitoring in the phase responded in which the valve
was triggered.
An earth fault or a fault in the power section is present. During the ground fault
test, a current flows from the phase in which a valve was triggered, the
overcurrent comparitor responded, or a UCE monitoring in a phase has responded
in which a valve wa
Short circuit, low-resistance ground fault
Motor overload (calculated): Motor current too high for too long a period.
Load too high, or excessive dynamic stressing.
Seized element.
ZR160VSD:
- Temperature limiting switch of motor is activated - open contact, ie, motor
overtemperature.
- Faulty temperature limiting switch.
- Loose connection at X101: 1 & 7
Motor stalled or locked
Could be one phase missing, where consumption on all 3 phases arevery different.
Precharging malfunction, line voltage, inverter defective

Motor thermistor problem
- Motor overheat
r949 = 1 Motor temperature limit exceeded
r949 = 2 Short circuit in the cable to the temperature sensor or sensor defect
r949 = 3 Open circuit in the cable to the temperature sensor or sensor defect
- Check P363 Mot.temp T1
The temperature limit of the inverter has been exceeded.
r949 = 1 The temp. limit of the inverter has been exceeded

r949 = 2 Sensor 1: Wire break in the sensor wire or sensor defect
r949 = 18 Sensor 2: ""
r949 = 34 Sensor 3:
Fault in internal linking. One of the two linked partners does not reply.
Higher level of F11
A fault has occurred in the EEPROM

Higher level of F11

Higher level of F11
failure.
Similar to F8

DC-link voltage (ULC) too low.

Possibly caused by a voltage dip
Line power failure. Phase failure
Dummy plug for the keypad not (properly) engaged, or PMU controller missing
is parameterised t trigger when temp reaches 51 deg. C
P575 Src No ExFault1
operat
A fault has occurred when storing the values in the EEPROM
- A fault has occurred during the softwiring of Binectors and Connectors

Line voltage too high, extreme generator operation, ramp down rate too fast.
Too high temperature inside converter. Inadequate cooling
Motor overtemp. (PTC thermistor term. X13:24/25), motor overload
CU: DC voltage was too low, ie 76% x line voltage x 1.34 was not reached
An I/O is missing from the module after programming.

The error 1 indicates that the master expects an extra extension module which is
not found or recognized on the system.



Most porbably due to a short circuit of the 12V supply for the digital inputs

Internal error

Internal error
the power suppl
Internal error
Internal communication between master and a com. Module

Internal communication between master and com. Module

==> 03


- Loose connection between Com 2 and ABB converter

- Com 2 defective.
- COM 2 was not properly earthed.
- NIOC board (of ABB drive) defective,
- Modbus adapter model is defective



The ACS 600 internal temperature is excessive. The trip level of inverter module
temperature is 125 deg. C
An analogue control signal is below minimum allowed value. This can be caused by
incorrect signal level or a failure in the control wiring.
I/O Control board temperature is lower than -5 … 0 deg. C or exceeds +73 … 82

deg. C
Cyclical communication with ACS 600 and fieldbus/ACS 600 Master is lost
Current transformer failure in output current measurement circuit.

Intermediate circuit DC voltage is excessive. DC overvoltage trip limit is 1.3 U1max,
where U1max is the maximum value of the mains voltage range. For 400 V units,
U1max is 415V. The actual voltage in the intermediate circuit corresponding to the
mains vo
Intermediate circuit DC voltage is not sufficient. This can be caused by a missing

mains phase, a blown fuse or a bridge internal fault
DC undervoltage trip limit is 0.65 U1min, where U1min is the minimum value of
the mains voltage range. For 400 V and 5
The load on the incoming mains system is out of balance. This can be caused by a
fault in the motor, motor cable or an internal malfunction.
There is a fault in one of the external devices.

(This information is configured through one of the programmable digital inputs.)
A communication error has occurred on the NAMC board, channel CH1
Electronmagnetic interference.
There is an internal fault on the NIOC board.
The motor ID Run is not completed successfully
Excessive input choke temperature
Fault on the line side converter
Possible causes:
- Faulty thermistor
- loose / broken connection of thermistor (PT100) cable
- Motor is hot
Possible causes:
- Faulty thermistor
- loose / broken connection of thermistor (PT100) cable
- Motor is hot
This can be caused by a fault in the motor, the motor cable, a thermal relay (if
used) or an internal fault.
This can be caused by excessive load or insufficient motor power
Excessive load or insufficient motor power
Motor temperature is too high (or appears to be too high). This can be caused by
excessive load, insufficient motor power, inadequate cooling or incorrect start-up
data.
Motor data is not given or motor data does not match with inverter data
Output current is excessive. The software overcurrent trip limit is 3.5 * I 2hd
Motor is turning faster than the highest allowed speed. This can be caused by an
incorrectly set minimum/maximum speed, insufficient braking torque or changes
in the load when using torque reference.
The trip level is 40Hz over the operating range absolu
A Control Panel or Drives Window selected as active control location for the ACS
600 has ceased communicating.
The fibre optic link to the NINT board is faulty
Short circuit in the inverter unit consisting of several parallel inverter modules.
Number refers to the faulty inverter module number.
NINT board fibre optic connection fault in inverter unit consisting of several
parallel inverter modules. Number refer
Short circuit in the motor cable(s) or motor
The output bridge of the converter unit is faulty
Optional start inhibit hardware logic is activated.
Intermediate circuit DC voltage is oscillating. This can be caused by a missing mains

phase, a blown fuse or a rectifier bridge internal fault.
A trip occurs when the DC voltage ripple is 13 % of the DC voltage

The problem is more probable when the moto
Motor thermal protection mode selected as THERMISTOR and the temperature is

excessive.
Motor load is too low. This can be caused by a release mechanism in the driven
equipment
There is np User Macro saved or file is defective

The ACS 600 internal temperature is excessive. A warning is given if inverter
module temp. exceds 115 deg. C
An analogue control signal is below minimum allowed value. This can be caused by
incorrect signal level or a failure in the control wiring.
Cyclical communication between ACS 600 and fieldbus/ACS 600 Master is lost.
Download function of the panel has failed. No data has been copied from the
Panel to the ACS 600.
Program versions in the Panel and in the ACS 600 do not match. It is not possible
to copy data from Panel to the ACS 600
Downloading is not possible while the motor is running.
Communication fault between the pulse encoder and the NTAC module or
between the NTAC module and the ACS 600
The ACS 600 has performed the Identification Run and is ready for operation. This
warning belongs to the ID Run procedure
The ACS 600 has performed the motor id magnetisation and is ready for operation.
This warning belongs to the normal start-up procedure.
Motor identification magnetisation is on. This warning belongs to the normal start-
up procedure.
Motor identification magnetisation is required. This warning belongs to the normal
start-up procedure. The drive expects the user to select how the motor
identification is to be performed: By ID magnetisation or by ID Run.
This is usually happen when the
The ID number of the drive has been changed from 1 in Drive Selection Mode (the
change is not shown on the display)
Motor Identification Run is on.
Motor ID Run is selected, and the drive is ready to start the ID Run. This warning
belongs to the ID Run procedure
Motor is operating in the stall region. This can be caused by excessive load or
insufficient motor power.
Motor Identification Run starts. This warning belongs to the IR Run procedure.
Motor temperature is too high (or appears to be too high). This can be caused by
excessive load, insufficient motor power, inadequate cooling or incorrect start-up
data.
There is a cabling problem or hardware malfunction on the Panel Link.

(4) = Panel type is not compatible with the version of the drive application
program. CDP 312 Panel does not communicate with Standard Application
Program (ACS) version 3.x or earlier.
The Panel Link already includes 31 stations

No upload function has been performed
A Control panel selected as active control location for the ACS 600 has ceased
communicating.
Motor thermal protection mode selected as THERMISTOR and the temperature is

excessive
Motor load is too low. This can be caused by a release mechanism in the driven
equipment.
Upload function of the panel has failed. No data has been copied from the Panel to
the ACS 600.
Certain parameters do not allow changes while motor is running. If tried, no

change is accepted, and a warning is displayed.
Parameter Lock is on.
Output current is excessive.
Insufficient acceleration time (parameters 2202 ACCELER TIME 1 and 2205

ACCELER TIME 2).
Intermediate circuit DC voltage is excessive.

Insufficient deceleration time (parameters 2203 DECELER TIME 1 and 2206
DECELER TIME 2).
Drive heatsink is overheated. Temperature is at or above limit.

R1R4 & R7/R8: 115 °C (239 °F)
R5/R6: 125 °C (257 °F)
Excessive ambient temperature.
Excessive motor load.
Fault current. Check for and correct:

A short-circuit in the motor cable(s) or motor.
Supply disturbances.
Not used.
Intermediate circuit DC voltage is not sufficient.
Check for and correct:

Source and connection for analog input.
Parameter settings for AI1 FAULT LIMIT (3021) and 3001 AI<MIN FUNCTION.
Analog input 2 loss. Analog input value is less than AI2 FAULT LIMIT (3022).
Motor is too hot, based on either the drives estimate or on temperature feedback.
Panel communication is lost and either:

Drive is in local control mode (the control panel displays LOC), or
Drive is in remote control mode (REM) and is parameterized to accept
start/stop, direction or reference from the control panel.
The Motor ID Run was not completed successfully.
Motor or process stall. Motor is operating in the stall region.
Not used.
Digital input defined to report first external fault is active.
Digital input defined to report second external fault is active.
Possible ground fault detected in the motor or motor cables.
Not used.
Internal fault. The thermistor measuring the internal temperature of the drive is
open or shorted.
Internal fault. A communication-related problem has been detected on the fiber
optic link between the control and OINT boards.
Internal fault. Low voltage condition detected on OINT power supply.
MEAS Internal fault. Current measurement is out of range. Contact your local ABB
representative.
Ripple voltage in the DC link is too high.
The drive is not detecting a valid encoder signal.

Motor speed is greater than 120% of the larger (in magnitude) of 2001
MINIMUM SPEED or 2002 MAXIMUM SPEED.
Not used.
Internal fault. Configuration Block Drive ID is not valid.
Internal configuration file has an error.
Fieldbus communication has timed out.
Error in reading the configuration file for the embedded fieldbus.
Fault trip forced by the fieldbus. See the fieldbus User s Manual.
Fault code reserved for the embedded fieldbus (EFB) protocol application.
The meaning is protocol dependent.
Fault in the motor circuit. One of the motor phases is lost.
Possible power wiring error detected. When the drive is not running it
monitors for an improper connection between the drive input power and the
drive output.
The drive cannot use the software.

Internal fault.
The loaded software is not compatible with the drive.
Call support representative.
Drive control board is overheated. The fault trip limit is 88 °C.
Condition defined by parameter 3701 USER LOAD C MODE has been valid longer
than the time defined by 3703 USER LOAD C TIME.
Error internal to the drive. Contact your local ABB representative and report the
error number.
Error in the system.
Wrong type of panel, i.e. panel that supports drive X but not the ACS550,
has been connected to the ACS550.
Parameter values are inconsistent. Check for any of the following:
2001 MINIMUM SPEED > 2002 MAXIMUM SPEED.
2007 MINIMUM FREQ > 2008 MAXIMUM FREQ.
2001 MINIMUM SPEED / 9908 MOTOR NOM SPEED is outside proper range
(> 50).
2002 MAXIMUM SPEED / 9908
Parameter values are inconsistent. Check for the following:

2007 MINIMUM FREQ is negative, when 8123 PFC ENABLE is active.
Not used.

1301 MINIMUM AI1 > 1302 MAXIMUM AI1.
1304 MINIMUM AI2 > 1305 MAXIMUM AI2.
1504 MINIMUM AO1 > 1505 MAXIMUM AO1.
1510 MINIMUM AO2 > 1511 MAXIMUM AO2.
Parameter values for power control are inconsistent: Improper motor
nominal kVA or motor nominal power. Check for the following:
1.1 < (9906 MOTOR NOM CURR · 9905 MOTOR NOM VOLT · 1.73 / PN) < 3.0
where: PN = 1000 · 9909 MOTOR NOM POWER (if units are kW
Parameter values are inconsistent. Check for the following:

Extension relay module not connected and
14101412 RELAY OUTPUTS 46 have non-zero values.
Parameter values are inconsistent. Check for and correct:
A parameter is set for fieldbus control (e.g. 1001 EXT1 COMMANDS = 10
(COMM)), but 9802 COMM PROT SEL = 0.
Parameter values are inconsistent 9904 MOTOR CTRL MODE must be = 3
(SCALAR:FREQ), when 8123 PFC ENABLE is activated.
Parameter values for power control are inconsistent: Improper motor
nominal frequency or speed. Check for both of the following:
1 < (60 · 9907 MOTOR NOM FREQ / 9908 MOTOR NOM SPEED < 16
0.8 < 9908 MOTOR NOM SPEED /
(120 · 9907 MOTOR NOM FREQ / Motor
Not used.
IO configuration is not complete not enough relays are parameterized to

PFC. Or, a conflict exists between Group 14: RELAY OUTPUTS, parameter
8117 NR OF AUX MOT and parameter 8118 AUTOCHNG INTERV.
IO configuration is not complete the actual number of PFC motors
(parameter 8127, MOTORS) does not match the PFC motors in Group 14:
RELAY OUTPUTS and parameter 8118 AUTOCHNG INTERV.
IO configuration is not complete the drive is unable to allocate a digital
input (interlock) for each PFC motor (parameters 8120 INTERLOCKS and
8127 MOTORS).
Not used.
Parameter values for the user load curve are inconsistent. Check that the
following conditions are met:
3704 LOAD FREQ 1 < 3707 LOAD FREQ 2 < 3710 LOAD FREQ 3 <
3713 LOAD FREQ 4 < 3716 LOAD FREQ 5.
3705 LOAD TORQ LOW 1 < 3706 LOAD TORQ HIGH 1.
3708
Current limiting controller is active
Over voltage controller is active
Under voltage controller is active
The change in direction being attempted is not allowed
Fieldbus communication has timed out.
Analog input 1 is loss or value is less than the minimum setting
Analog input 2 is loss or value is less than the minimum setting.
Panel communication is lost and either:

- Drive is in local control mode (the control panel displays LOC), or
- Drive is in remote control mode (REM) and is parameterized to accept
start/stop, direction or reference from the control panel.
Drive heat sink is hot. This alarm warns that a DEVICE OVERTEMP fault my be near
R1…R4 and R7/R8 100 degrees 212 Fahrenheit R5/R6 110 degrees 230 Fahrenheit
Motor is hot on either the drive's estimate or on temperature feedback. This alarm
wanrs hat a Motor Underload fault trip may be near
Motor load is lower than expected. This alamr wanrs that a mtor Underload fault
trip may be near
Motor is operating in the stall region. This alarm wanrs that a Motor Stall fault trip
may be near
This larm warns that the dive is about to perform an automatic fault reset which
may start the motor
This alarm warns that the PFC autochange function is active.
This larm warns tha the PFC interlocks are active, which means that the drive
cannot start the following
This alarm wanrs that the PID sleep function is active, which means that the motor
could accelerate when the PID sleep function ends
Performing ID Run
This alarm wanrs that the start enable 1 signal is missing.
The alarm wanrs that the START ENABLE 2 signal is missing
Emergency stop activated
Signals that the drive is performing a FIRST START evaluation of motor

characteristics. This is normally the first time the motor is run after motor
parameters are entered or changed. See parameter 9910 (MOTOR ID RUN) for a
description of motor models.
Drive IGBT temperature is excessive. Fault trip

limit is 100%.
(4210)
3.05 FW 1 bit 3
Excessive internal temperature in inverter unit

of several parallel connected inverter modules.
xx (1...12) refers to inverter module number
and y refers to phase (U, V, W).
(4210)
3.05 FW 1 bit 3 and
4.01
Analogue control signal is below minimum

allowed value due to incorrect signal level or
failure in control wiring.
(8110)
3.06 FW 2 bit 10
(programmable
Fault Function
30.01)
Failure when restoring PC stored backup of

drive parameters.
Brake chopper overload
(7114)
3.17 FW 5 bit 4
Short circuit in brake chopper IGBT(s)
(7113)
3.17 FW 5 bit 2
Unexpected state of brake acknowledge signal

(FF74)
3.15 FW 4 bit 3
Brake resistor is not connected or it is

damaged.
Resistance rating of brake resistor is too high.
(7110)
3.17 FW 5 bit 0
Brake resistor overload

-(7112)
3.17 FW 5 bit 3
Wrong connection of brake resistor
(7111)
3.17 FW 5 bit 1
Excessive temperature of drive output filter.

Supervision is in use in step-up drives.
(FF82)
Cyclical communication between drive and

master is lost.
(7510)
3.06 FW 2 bit 12
(programmable
Fault Function
30.18)
Control board temperature is above 88°C.
4110)
3.06 FW 2 bit 7
Current transformer failure in output current

measurement circuit
(2211)
Drive has detected excessive output current
unbalance in inverter unit of several parallel
connected inverter modules. This can be
caused by external fault (earth fault, motor,
motor cabling, etc.) or internal fault (damaged
inverter component). xx (2...1
Drive supply voltage is excessive. When

supply voltage is over 124% of unit voltage
rating (415, 500 or 690 V), motor speed rushes
to trip level (40% of nominal speed).
(FF80)
Excessive intermediate circuit DC voltage.

DC overvoltage trip limit is 1.3 · U1max, where
U1max is maximum value of mains voltage
range. For 400 V units, U1max is 415 V. For
500 V units, U1max is 500 V. Actual voltage in
intermediate circuit correspondin
Intermediate circuit DC voltage is not sufficient

due to missing mains phase, blown fuse or
rectifier bridge internal fault.
DC undervoltage trip limit is 0.6 · U1min, where
U1min is minimum value of mains voltage
range. For 400 V and 500 V units, U1min i
Pulse encoder phasing is wrong: Phase A is

connected to terminal of phase B and vice
versa.
(7302)
Communication fault between pulse encoder

and pulse encoder interface module and
between module and drive
(7301)
3.06 FW 2 bit 5
Fault in external device. (This information is

configured through one of programmable
digital inputs.)
(9000)
3.06 FW 2 bit 8
(programmable
Fault Function
30.03)
Excessive temperature of drive output filter fan.

(FF83)
Number of inverter modules is not equal to
original number of inverters.
(5410)
03.17 FW 5 bit 9
Communication error on control board,

channel CH1
Electromagnetic interference
(7000)
3.06 FW 2 bit 6
Fault on line side converter
(FF51)
One of motor phases is lost due to fault in

motor, motor cable, thermal relay (if used) or
internal fault.
(FF56)
3.06 FW 2 bit 15
(programmable
Fault Function
30.16)
Motor is operating in stall region due to e.g.

excessive load or insufficient motor power.
7121)
3.06 FW 2 bit 14
(programmable
Fault Function
30.10…30.12)
Motor temperature is too high (or appears to be

too high) due to excessive load, insufficient
motor power, inadequate cooling or incorrect
start-up data.
(4310)
3.05 FW 1 bit 6
(programmable
Fault Function
30.04…30.09)
Measured motor temperature has exceeded

fault limit set by parameter 35.03.
(4312)
3.15 FW 4 bit 1

(4313)
3.15 FW 4 bit 2
Motor data is not given or motor data does not
match with inverter data.
(FF52)
3.06 FW 2 bit 1
Overcurrent fault in inverter unit of several

parallel connected inverter modules. xx (2...12)
refers to inverter module number.
(2310)
3.05 FW 1 bit 1 and
4.01
Output current exceeds trip limit.
(2310)
3.05 FW 1 bit 1
Motor is turning faster than highest allowed

speed due to incorrectly set minimum/
maximum speed, insufficient braking torque or
changes in load when using torque reference.
Trip level is 40 Hz over operating range
absolute maximum speed limit (Direct Tor
Control panel or DriveWindow selected as

active control location for drive has ceased
communicating.
(5300)
3.06 FW 2 bit 13
(programmable
Fault Function
30.02)
INT board fibre optic connection fault in

inverter unit of several parallel connected
inverter modules. xx refers to inverter module
number.
3.06 FW 2 bit 11 and

4.01
No Run enable signal received.
3.06 FW 2 bit 4
Short circuit in inverter unit of several parallel
connected inverter modules. xx (1...12) refers
to inverter module number and y refers to
phase (U, V, W).
2340)
3.05 FW 1 bit 0, 4.01
and 4.02
Short-circuit in motor cable(s) or motor
Output bridge of converter unit is faulty.
(2340)
3.05 FW 1 bit 0 and
4.02
Two option modules have same connection

interface selection.
(FF8A)
Optional start inhibit hardware logic is

activated.
3.03 bit 8
Possibly service switch has loose connection(s)
Intermediate circuit DC voltage is oscillating

Trip occurs when DC voltage ripple is 13% of
DC voltage.
(3130)
3.06 FW 2 bit 0
Motor thermal protection mode is set to DTC

for high-power motor.
(FF50)
Motor temperature is excessive. Motor thermal

protection mode selection is THERMISTOR.
(4311)
3.05 FW 1 bit 5
(programmable
Fault Function
30.04…30.05)
Motor load is too low due to e.g. release

mechanism in driven equipment.
(FF6A)
3.05 FW 1 bit 8
(programmable
Fault Function
30.13…30.15)
Integrated motor current has exceeded load

curve defined by parameter group 72 USER
LOAD CURVE.
No User Macro saved or file is defective.

(FFA1)
3.07 SFW bit 1
Drive limits torque due to too high or too low
intermediate circuit DC voltage.
(3211)
3.18 AW5 bit 9
(programmable
Fault Function
30.23)
Drive has detected load unbalance typically

due to earth fault in motor or motor cable.
(2330)
3.08 AW 1 bit 14
(programmable
Fault Function
30.17)
Drive IGBT temperature is excessive. Fault trip

limit is 100%.
(4210)
3.05 FW 1 bit 3

(2330)
3.08 AW 1 bit 14
(programmable
Fault Function
30.17)
Drive limits torque due to too high or too low

intermediate circuit DC voltage.
(3211)
3.18 AW5 bit 9
(programmable
Fault Function
30.23)
No User Macro saved or file is defective.
(FFA1)
3.07 SFW bit 1
Analogue control signal is below minimum

allowed value due to incorrect signal level or
failure in control wiring.
(8110)
3.06 FW 2 bit 10
(programmable
Fault Function
30.01)
Brake chopper overload
(7114)
3.17 FW 5 bit 4
Short circuit in brake chopper IGBT(s)
(7113)
3.17 FW 5 bit 2
Unexpected state of brake acknowledge signal

(FF74)
3.15 FW 4 bit 3
Brake resistor is not connected or it is

damaged.
Resistance rating of brake resistor is too high.
(7110)
3.17 FW 5 bit 0
Brake resistor overload

(7112)
3.17 FW 5 bit 3
Wrong connection of brake resistor
(7111)
3.17 FW 5 bit 1
Excessive temperature of drive output filter.

(FF82)
Cyclical communication between drive and

master is lost.
(7510)
3.06 FW 2 bit 12
(programmable
Fault Function
30.18)
Control board temperature is above 88°C.
4110)
3.06 FW 2 bit 7
Current transformer failure in output current

measurement circuit
(2211)
Drive has detected excessive output current
unbalance in inverter unit of several parallel
connected inverter modules. This can be
caused by external fault (earth fault, motor,
motor cabling, etc.) or internal fault (damaged
inverter component). xx (2...1
Drive supply voltage is excessive. When

supply voltage is over 124% of unit voltage
rating (415, 500 or 690 V), motor speed rushes
to trip level (40% of nominal speed).
(FF80)
Pulse encoder phasing is wrong: Phase A is

connected to terminal of phase B and vice
versa.
(7302)
Communication fault between pulse encoder

and pulse encoder interface module and
between module and drive
(7301)
3.06 FW 2 bit 5
Fault in external device. (This information is

configured through one of programmable
digital inputs.)
(9000)
3.06 FW 2 bit 8
(programmable
Fault Function
30.03)
Excessive temperature of drive output filter fan.

(FF83)
Generic Drive Communication Profile trip

command
Motor ID Run is not completed successfully.
Number of inverter modules is not equal to

original number of inverters.
(5410)
03.17 FW 5 bit 9
Optional DC switch has opened while unit was
running or start command was given.
Communication error on control board,
channel CH1
Electromagnetic interference
(7000)
3.06 FW 2 bit 6
Fault on line side converter

(FF51)
One of motor phases is lost due to fault in

motor, motor cable, thermal relay (if used) or
internal fault.
(FF56)
3.06 FW 2 bit 15
(programmable
Fault Function
30.16)
Motor is operating in stall region due to e.g.

excessive load or insufficient motor power.
7121)
3.06 FW 2 bit 14
(programmable
Fault Function
30.10…30.12)
Motor temperature is too high (or appears to be

too high) due to excessive load, insufficient
motor power, inadequate cooling or incorrect
start-up data.
(4310)
3.05 FW 1 bit 6
(programmable
Fault Function
30.04…30.09)

(4312)
3.15 FW 4 bit 1

(4313)
3.15 FW 4 bit 2
Motor data is not given or motor data does not

match with inverter data.
(FF52)
3.06 FW 2 bit 1
Overcurrent fault in inverter unit of several
parallel connected inverter modules. xx (2...12)
refers to inverter module number.
(2310)
3.05 FW 1 bit 1 and
4.01
Output current exceeds trip limit.
(2310)
3.05 FW 1 bit 1
Motor is turning faster than highest allowed

speed due to incorrectly set minimum/
maximum speed, insufficient braking torque or
changes in load when using torque reference.
Trip level is 40 Hz over operating range
absolute maximum speed limit (Direct Tor
Control panel or DriveWindow selected as

active control location for drive has ceased
communicating.
(5300)
3.06 FW 2 bit 13
(programmable
Fault Function
30.02)
INT board powerfail in inverter unit of several

parallel connected inverter modules. xx refers
to inverter module number.
3.17 FW 5 bit 8 and

4.01
INT board powerfail in inverter unit of several

parallel connected inverter modules. xx refers
to inverter module number.
3.17 FW 5 bit 8
Fibre optic link to INT board is faulty.
(5120)
3.06 FW 2 bit 11
Excessive IGBT junction to case temperature.

This fault protects IGBT(s) and it can be
activated by short circuit at output of long
motor cables.
3.17 FW 5 bit 5
Short circuit in inverter unit of several parallel
connected inverter modules. xx (1...12) refers
to inverter module number and y refers to
phase (U, V, W).
2340)
3.05 FW 1 bit 0, 4.01
and 4.02
Short-circuit in motor cable(s) or motor

Output bridge of converter unit is faulty.
(2340)
3.05 FW 1 bit 0 and
4.02
Two option modules have same connection

interface selection.
(FF8A)
Intermediate circuit DC voltage is oscillating

Trip occurs when DC voltage ripple is 13% of
DC voltage.
(3130)
3.06 FW 2 bit 0
Excessive temperature difference between

several parallel connected inverter modules. xx
(1...12) refers to inverter module number and y
refers to phase (U, V, W).
Alarm is indicated when temperature difference
is 15°C. Fault is indicated when temperature
Motor thermal protection mode is set to DTC

for high-power motor.
(FF50)
Motor temperature is excessive. Motor thermal

protection mode selection is THERMISTOR.
(4311)
3.05 FW 1 bit 5
(programmable
Fault Function
30.04…30.05)
Motor load is too low due to e.g. release

mechanism in driven equipment.
(FF6A)
3.05 FW 1 bit 8
(programmable
Fault Function
30.13…30.15)
Excessive IGBT junction to
case temperature. This fault
protects the IGBT(s) and can
be activated by a short circuit
in the motor cable.
Drive IGBT temperature is

excessive.
Drive module temperature is

excessive.
Drive internal fault
Problem with internal

temperature measurement of
the drive.
Embedded fieldbus interface
has been taken into use, and
there is a communication
break between the drive and
the master station.
Too high a temperature

difference between the IGBTs
of different phases.
Encoder 1 is receiving too high
data flow (pulse frequency).

Inverter output (motor)

frequency is over the
frequency limit 500 Hz.
Firmware time level 2 overload
Note: This fault cannot be
reset.
reset.
reset.

reset.
Application time level 1 fault
reset.
Application time level 2 fault
reset.
Application task creation fault
reset.
Application task creation fault
reset.
reset.
JMU Memory Unit is missing or

broken.
File read error
reset.
reset.
reset.
reset.
reset.
reset.
reset.
Corrupted application file
reset.
Application file incompatible or
corrupted
reset.
Extension: 8 == Template used in the

application incompatible with
drive firmware.
Extension: 10 == Parameters defined in the

application conflict with
existing drive parameter
Loading of user set is not

successfully completed
because:
- requested user set does not
exist
- user set is not compatible
with drive program
- drive has been switched off
during loading.
User set is not saved because

of memory corruption.
UFF file is too big
UFF file structure failure
Incompatible firmware
interface
reset.
Restoration of backed-up
parameters failed.
Mismatch between JCU

Control Unit firmware and
power unit logic versions.
Fault generated by function
block SOLUTION_FAULT in
the application program.
Menu hiding file missing or
corrupted.
Mechanical brake alarm. Alarm
is activated if required motor
starting torque (42.08 Brake
open torq) is not achieved.
Mechanical brake control

alarm. Alarm is activated e.g. if
brake acknowledgement is not
as expected during brake
closing.
Mechanical brake control
alarm. Alarm is activated e.g. if
brake acknowledgement is not
as expecte
Safe torque off function is

active, i.e. safety circuit
signal(s) connected to
connector XSTO is lost.
Error in changing Safe torque

off supervision, i.e. parameter
30.07 Sto diagnostic setting
could not be changed to value
Alarm.
Estimated motor temperature

(based on motor thermal
model) has exceeded alarm
limit defined by parameter
31.03 Mot temp1 almLim.
Measured motor temperature
has exceeded alarm limit
defined by parameter 31.03
Mot temp1 almLim.
Drive has received emergency

OFF2 command.
No run enable signal is

received.
Motor identification run is on.
Motor identification is required.
Drive has received emergency

stop command (OFF1/OFF3).
Brake resistor temperature has
exceeded alarm limit defined
by parameter 48.07 Br temp
alarmlim.
Brake chopper IGBT

temperature has exceeded
internal alarm limit.
Measured drive temperature

has exceeded internal alarm
limit.
Interface board (between

power unit and control unit)
Input bridge or brake chopper

Cyclical communication
between drive and fieldbus
adapter module or between
PLC and fieldbus adapter
module is lost.
Control panel or PC tool

selected as active control
location for drive has ceased
communicating.
An analog input has reached

13.33 AI superv cw.
The drive does not have a
functionality requested by
PLC, or requested functionality
has not been activated.
Parameters in group 99 have

not been set.
Encoder 1 has been activated

by parameter but the encoder
interface (FEN-xx) cannot be
found.
Encoder 2 has been activated

by parameter but the encoder
interface (FEN-xx) cannot be
found.
Error in temperature
measurement when
temperature sensor (KTY or
PTC) connected to encoder
interface FEN-xx is used.
measurement when KTY
sensor connected to encoder
interface FEN-01 is used.
Resolver autotuning routines,

which are automatically started
when resolver input is
activated for the first time,
have failed.
Encoder 1 cable fault detected.

On the master drive: The drive
has not been replied to by an
activated follower for five
consecutive polling cycles.
On a follower drive: The drive

has not received new
reference 1 and/or 2 for five
consecutive reference
handling cycles.
Transmission of drive-to-drive
references failed because of
message buffer overflow.
Communication errors
detected between the JCU
Control Unit and the power unit
of the drive.
Restoration of backed-up
parameters failed.
Current measurement
calibration will occur at next
start.
Autophasing will occur at next
start.
Drive has detected load
unbalance typically due to
earth fault in motor or motor
cable.
A fault is to be autoreset.
The motor configuration

parameters are set incorrectly.
The drive is not dimensioned
correctly.
The settings of drive-to-drive

link configuration parameters
(group 57) are incompatible.
Motor is operating in stall
region because of e.g.
excessive load or insufficient
motor power.
Overload or underload limit

has been exceeded.
The load curve has been

incorrectly or inconsistently
defined.
The U/f (voltage/frequency)
curve has been incorrectly or
inconsistently defined.
No speed feedback is
received.
Communication between drive

and option module (FEN-xx
and/or FIO-xx) is lost.

model) has exceeded alarm
31.07 Mot temp2 almLim.

has exceeded alarm limit
Mot temp2 almLim.

case temperature. This alarm
in the motor cable.

excessive.

excessive.
Loading a parameter listing

requires a password.
A different parameter listing is

being loaded.
Maintenance counter alarm.

The voltage of the intermediate

DC circuit has not yet risen to
operating level.
Speed controller autotune
routine did not finish
successfully.
No Start interlock signal
received.
the drive.
Embedded fieldbus interface
has been taken into use, and
there is a communication
break between the drive and
the master station.
High temperature difference

between the IGBTs of different
phases.
Analog output calibration has

failed.
Brake chopper is configured

wrong.
Alarm generated by custom
application program.
Output current has exceeded
internal fault limit.
Excessive intermediate circuit

DC voltage
Short-circuit in motor cable(s)

or motor
Extension: 1 Short-circuit in the upper

transistor of U-phase.
Extension: 2 Short-circuit in the lower

transistor of U-phase.
Extension: 4 Short-circuit in the upper
transistor of V-phase.
Extension: 8 Short-ci
Intermediate circuit DC voltage

is not sufficient due to missing
mains phase, blown fuse or
cable.
Fan is not able to rotate freely

or fan is disconnected. Fan
operation is monitored by
measuring fan current.
Drive temperature based on

thermal model has exceeded
Brake resistor short circuit or

brake chopper control fault
Short circuit in brake chopper

IGBT
Brake chopper IGBT


exceeded fault limit defined by
parameter 48.06 Br temp
faultlim.
Difference between output

phase U2 and W2 current
measurement gain is too great.
Incorrect input power and
motor cable connection, or
ground (earth) fault in the
motor cable or motor.

is oscillating due to missing
input power line phase or
blown fuse.
Motor circuit fault due to
missing motor connection (all
three phases are not
connected).
Motor ID run was not

completed successfully.
Extension: 1 = The ID run cannot be
completed because the
maximum current setting and/
or internal current limit of the
drive is too low.
Extension: 2 = The ID run cannot be

completed because the
maximum speed
Measured offset error of U2

output phase current
measurement is too great.
(Offset value is updated during
current calibration.)
Measured offset error of V2

Measured offset error of W2


active, i.e. safety circuit signal
1 connected between XSTO:1
and XSTO:3 is lost.

active, i.e. safety circuit signal
2 connected between XSTO:2
and XSTO:4 is lost.
Error in changing Safe torque

off supervision, i.e. parameter
30.07 Sto diagnostic setting
could not be changed to value
Fault.
Interface board (between
power unit and control unit)
Input bridge or brake chopper

Autophasing routine (see

section Autophasing on page
68) failed.
Connection between the JCU

of the drive is lost.
detected between the JCU
of the drive.
Fault in external device. (This

information is configured
through one of programmable
digital inputs.)

connector XSTO is lost during
start or run, or while drive is
stopped and parameter 30.07
Sto diagnostic is set to Fault.
Motor is turning faster than

highest allowed speed due to
incorrectly set minimum/
maximum speed, insufficient
braking torque or changes in
load when using torque
reference.
Mechanical brake fault. Fault is
activated if required motor
starting torque (42.08 Brake
open torq) is not achieved.
Mechanical brake control fault.

Activated e.g. if brake
acknowledgement is not as
expected during brake closing.

Activated e.g. if brake
expected during brake
opening.

communicating.
Drive internal fault.

reset.
Extension: 2051 == Total number of parameters

(including unused space
between parameters) exceeds
firmware maximum.

and option module (FEN-xx
and/or FIO-xx) is lost.
Encoder 1 feedback fault.
Encoder 2 feedback fault.
adapter module or between
module is lost.

model) has exceeded fault limit
Mot temp1 fltLim.

has exceeded fault limit
Mot temp1 fltLim.
Faulty temperature sensor o
An analog input has reached

13.33 AI superv cw.
Configuration of the drive-todrive

link has failed for a
reason other than those
indicated by alarm A-2042, for
example start inhibition is
requested but not granted.
On the master drive: The drive

has not been replied to by an
activated follower for five
consecutive polling cycles.
On a follower drive: The drive

has not received new
reference 1 and/or 2 for five
consecutive reference
handling cycles.
Transmission of drive-to-drive
references failed because of
message buffer overflow.
Resettable fault generated by

a technology library.
Permanent fault generated by
a technology library.
Generic Drive Communication
Profile trip command.

motor power.
Overload or underload limit

has been exceeded.
No speed feedback is
received.
Drive-to-drive link is set to use

an FMBA module for
communication, but no module
is detected in specified slot.

model) has exceeded fault limit
Mot temp2 fltLim.

has exceeded fault limit
Mot temp2 fltLim.
Faulty temperature sensor o
Probably corrupted memory module
Current offset and again measuremtn calibration wil occur at next start

Short circuit in motor cable(S) or motor

case temperature. This
warning protects the IGBT(s)
and can be activated by a short
circuit in the motor cable.
Intermediate circuit DC voltage too high (when the drive is stopped).
Intermediate circuit DC voltage too low (when the drive is stopped)
The voltage of the intermediate DC circuit has not yet risen to operating level
Calculated motor cable temperature has exceeded warning light
sensor type mismatch
Faulty wiring between an

encoder interface module and
the temperature sensor.
Measured temperautre 1 has exceeded warning limit
Measured temperature 2 has

exceeded warning limit.
Control unit temperature is excessive.
Temperature above warning limit
Thermistor broken
Estimated drive IGBT temperature is excessive

excessive.
Power unit module

temperature is excessive.
phases.
Temperature difference
between ambient and drive
module PCB space is
excessive.

excessive.
detected between the drive
control unit and the power unit.
Cooling fan stuck or

disconnected.
An auxiliary cooling fan
(connected to the fan
connectors on the control unit)
is stuck or disconnected.
Safe torque off function is active, i.e. safety circuit signal(s) connected to connector
XSTO is lost.

the drive.
Power unit power supply

failure.
Measurement circuit fault.

State feedback from output
phases does not match control
signals.
Charging feedback signal
missing.
Adequate motor control at
requested output frequency
cannot be reached because of
limited switching frequency
(eg. by parameter 95.15).
an error in saving data to the power unit

Error related to SD card used to store data (BCU control unit only)
power fail saving is requested too frequently due to oscillating power supply to the
control unit. Some of the requests may have been discarded, potentially causing
data loss.
The motor parameters are set incorrectly
The drive is not dimensioned

correctly.
parameters in group 99 have not been set

functionality requested by a

functionality requested by a
The current/voltage hardware

setting of an analog input does
not correspond to parameter
settings.
motor power.
No feedback received from

external fan.
measurement when
temperature sensor (KTY or
PTC) connected to encoder
interface FEN-xx is used.
measurement when KTY
sensor connected to encoder
interface FEN-01 is used.

exceeded warning limit defined
by parameter 43.12 Brake
resistor warning limit.

exceeded warning limit defined
by parameter 43.12 Brake
resistor warning limit.
Breake resistor data has not been given

speed faceback configuration has changed

IGBT
Brake chopper IGBT

internal warning limit.
Status of mechanical brake acknowledgement is not as

expected during brake close.
Status of mechanical brake

expected during brake open.
Open conditions of mechanical

brake cannot be fulfilled (for
example, brake has been
prevented from opening by
parameter 44.11 Keep brake
closed).
The hardware current/voltage
setting of an analog input (on
an I/O extension module) does
not correspond to parameter
settings.
The I/O extension module

types and locations specified
by parameters do not match
the detected configuration.
No motor speed feedback is

received.
No load speed feedback is

received.
adapter module A or between
module A is lost.
adapter module B or between
module B is lost.
DDCS (fiber optic)

communication between drive
and external controller is lost.
Communication break in
embedded fieldbus (EFB)
communication.
Encoder Error
Control panel or PC tool selected as active control location for drive has ceased
communicating.
Warning generated by an on-time timer or a value counter
Warning generated by an edge counter.

33.35 Edge counter 1 warn message
33.45 Edge counter 2 warn Message



Warning generated by on-time

timer 1.
Warning generated by on-time
timer 2.
Warning generated by edge counter 1
Warning generated by edge

counter 2.
Warning generated by value

counter 1.
Warning generated by value counter 2
Warning generated by an ontime

timer.

timer.

timer.
timer.

timer.
An analog signal is outside the

limits specified for the analog
input.
Warning generated by the

signal supervision 1 function.


A cooling fan has reached the

end of its estimated lifetime.
See parameters 05.41 and
05.42.
Fault in external device 1

DDCS (fiber optic)

communication between
converters (for example, the
inverter unit and the supply
unit) is lost.
The supply unit has generated

a warning.
The drive is entering sleep mode

the speed controller autotune routine did not complete sucessfully
A fault is about to the autoreset
Drive has received an

emergency stop (mode
selection off2) command.
Drive has received an

emergency stop (mode
selection off1 or off3)
command.
A follower drive has tripped.
No enable start signal

received.
No run enable signal is

received.
95.04 Control board supply is

set to External 24V but no
voltage is connected to the
XPOW connector of the control
unit.
Motor ID run will occur at next start

Autophasing will occur at next start
connector XSTO is lost.
Measured offset of output

phase current measurement or
difference between output
phase U2 and W2 current
measurement is too great (the
values are updated during
current calibration).

cable.
Short-circuit in motor cable(s)

or motor

case temperature. This fault
in the motor cable.
AC phase current difference

between parallel-connected
inverter modules is excessive.
Total earth leakage of inverter
modules is excessive.

is oscillating due to missing
input power line phase or
blown fuse.
No acknowledgement received
from charge relay.
The drive hardware is supplied
from a common DC bus.
Incorrect input power and

motor cable connection (i.e.
input power cable is connected
to the motor connection).

cable.
Excessive intermediate circuit

DC voltage.

is not sufficient because of a
missing supply phase, blown
fuse or fault in the rectifier
bridge.
Automatic restart failed (see

section Automatic restart on
page 73).
Difference in DC voltages
between parallel-connected
inverter modules.
Motor circuit fault due to

missing motor connection (all
three phases are not
connected).
Autophasing routine (see

section Autophasing on page
57) has failed.
Calculated motor cable

warning limit.
Estimated drive IGBT


excessive.

excessive.
Power unit module

phases.
Temperature difference
between ambient and drive
module PCB space is
excessive.
Measured temperature 1 has

exceeded fault limit.
cooling fan stuck or disconnected

An auxiliary cooling fan
(connected to the fan
connectors on the control unit)
is stuck or disconnected.
Safe torque off hardware

failure.

connector XSTO is broken
during start or run.
Power unit memory has

cleared.
The hardware of the drive does
not match the information
stored in the memory unit. This
may occur eg. after a firmware
update or memory unit
replacement.

the drive.
The way the control unit is
powered does not correspond
to parameter setting.
Connection between the drive

control unit and the power unit
is lost.
Internal communication error.
Power unit power supply

failure.

Version check cannot find a
matching power unit FPGA
logic.
Number of inverter modules
detected does not match the
value of parameter 95.13
Reduced run mode.
State feedback from output

phases does not match control
signals.
Charging feedback signal
missing.
Unidentified power unit logic
fault.
Internal error.
Firmware and FPGA file

version in the power unit are
incompatible.
Fieldbus adapter A mapping

file read error.
Fieldbus adapter B mapping
file read error.
Internal fault
Internal fault
file read error
internal record load error

Application file incompatible or
corrupted.
A license that is required for

the drive to function properly is
missing.
The memory unit was
detached when the control unit
was powered.
Internal fault
Loading of user parameter set

failed because
• requested set does not exist
• set is not compatible with
control program
• drive was switched off
during loading.
Operating system error.
Parameter load or save failed.


Communication break in
embedded fieldbus (EFB)
communication.
Embedded fieldbus (EFB)

configuration file could not be
read.
parameter settings
inconsistent or not compatible
with selected protocol.

protocol firmware could not be
loaded.
Version mismatch between
EFB protocol firmware and
drive firmware.
Internal fault
Internal fault
Internal fault
Internal fault

and an option module is lost.

communicating.
The I/O extension module

types specified by parameters
do not match the detected
configuration.

motor power.
Brake resistor broken or not

connected.

exceeded fault limit defined by
parameter 43.11 Brake resistor
fault limit.
Brake resistor short circuit or
brake chopper control fault.

IGBT.
Brake chopper IGBT


Activated eg. if brake
expected during brake closing.

Activated eg. if brake
expected during brake
opening.
Open conditions of mechanical

brake cannot be fulfilled (for
example, brake has been
prevented from opening by
parameter 44.11 Keep brake
closed).
In an encoderless application,
the brake is kept closed by a
brake close request (either
from parameter 44.12 Brake
close request or from an
FSO-xx safety functions
module) against a modulating
drive for longer than 5
seconds.
No feedback received from
external fan.
No motor speed feedback

received.
Motor is turning faster than

highest allowed speed due to
incorrectly set
minimum/maximum speed,
insufficient braking torque or
changes in load when using
torque reference.
Incorrect estimated speed.
The supply unit has tripped on

a fault.
Internal fault.
Encoder feedback fault.
Speed feedback configuration

incorrect.
No load feedback received.
Emergency stop did not finish

within expected time.
Ramp stop did not finish within
expected time.
adapter module A or between
module A is lost.
adapter module B or between
module B is lost.
DDCS (fiber optic)

communication between
converters (for example, the
inverter unit and the supply
unit) is lost.
DDCS (fiber optic)

communication between drive
and external controller is lost.
Master/follower
communication is lost.
The supply unit (or other

converter) connected to the
inverter unit has generated a
fault.
An analog signal is outside the
limits specified for the analog
input.
Fault generated by the signal

supervision 1 function.



active, ie. STO circuit 1 is
broken.

active, ie. STO circuit 2 is
broken.
No memory unit is attached to

the control unit.
The memory unit attached to
the control unit is empty.
Motor ID run was not
completed successfully.
A follower drive has tripped.
A fault trip command has been

received through fieldbus
adapter A.
received through fieldbus
adapter B.
received through the
embedded fieldbus interface.
Low AC supply voltage
Low DC bus voltage when supplied by an external DC power
supply
Deceleration rate set too fast for the inertia of the machine.
Mechanical load driving the motor
Insufficient ramp times
Phase to phase or phase to ground short circuit on the drives
output
Drive requires autotuning to the motor
Motor or motor connections changed, re-autotune drive to motor
Excessive braking current in braking resistor
Braking resistor value too small
Excessive motor speed (typically caused by mechanical load
driving the motor)
Run command removed before autotune complete
Excessive braking resistor energy
Excessive mechanical load

High impedance phase to phase or phase to ground short circuit
at drive output
Drive requires re-autotuning to motor
Overheat software thermal model
Heatsink temperature exceeds allowable maximum
Excessive motor temperature
Excessive load or short circuit on +24V output
Overheat software thermal model
Power module rectifier temperature exceeds allowable

maximum
Input current less than 3mA when 4-20 or 20-4mA modes
selected
Loss of communication when drive is under remote control
Possible loss of parameter values

(set default parameters (see Pr 29 on page 59))
One of the input phases has become disconnected from the
drive (not dual rated drives)
Motor too small for drive
Motor cable disconnected during measurement
Bad connection or memory corrupt within SmartStick
New/empty SmartStick being read
Bad connection or faulty SmartStick
Already programmed SmartStick read by a drive of a different

rating
Input current exceeds 25mA
Internal drive hardware fault (see Commander SK Advanced

User Guide)
Possibly due to EMC interference, communication cable faulty, faulty control
board.
the power suppl


Most probably due to a short circuit of the 12V supply for the digital inputs
G120

Internal error

Internal error
Internal error
operat
Internal communication between master and a COM module
Internal communication between master and a COM module

==> 03


- GAX card (power supply card for 90 VSD Simovert P) is in doubt
- Main Control Card (ABB)
* 730X, where x = 1 means communication module no.1 or com






Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
• Load at start-up is too high

• Load step is too high
• Ramp-up rate is too fast
Reaction: OFF 2 (OFF 3)

Motor overloaded
Open or short circuit of motor temperature sensor. If signal loss is detected,
temperature monitoring switches over
to monitoring with the motor thermal model.

Fault occurs if one of the three input phases are missed and the pulses are enabled
and drive is loaded
Reaction: OFF 2
Fault occurs if the sum of the phase currents is higher than 5 % of the nominal
inverter current.
Reaction: OFF 2
This hardware fault caused by the following events:

• DC-link overcurrent = short circuit of IGBT
• Short circuit of chopper

One output phase is disconnected.

Large ripples on the dclink.
Reaction: OFF 2
Cause: Gate driver not enabled. Can be caused also by a synchronization error of
the safety state machines.
Reaction: OFF 2
This hardware fault caused by the following events:
• Over current trip on W phase
• Earth Fault
Reaction: OFF 2
Occurs if motor is driven by an active load, causing motor to go into excessive
regeneration.
Occurs at very high load inertias, when ramping down.
Reaction: OFF 2
Acknowledge: Power on
Cause: Auto restart attempts exceed value of p1211.
Reaction: OFF 2
Motor data identification failed.
• r0949 = 0: Load missing
• r0949 = 1: Current limit level reached during identification.
• r0949 = 2: Identified stator resistance less than 0.1% or greater than 100%.
Reaction: OFF 2
Motor data identification failed.
• r0949 = 0: Time out waiting for stable speed
• r0949 = 1: Inconsistent readings
Reaction: OFF 2
Read or write failure while access to EEPROM.
This can also be caused by the EEPROM being full, too many parameters have been
changed.
Reaction: OFF 2
Cause: Read failure for power stack information or invalid data.
Remedy: • Check connection between inverter power module and inverter control
unit
• Powercycle inverter Control Unit.
• Change inverter P

Read or write failure while saving non-volatile parameter to EEPROM on BOP
whilst parameter cloning.

Trying to initiate parameter cloning without BOP fitted.

• Parameter cloning with empty BOP.
• Parameter cloning with invalid BOP.

Trying to initiate parameter cloning with BOP created on another type of drive.
Reaction: OFF 2
Internal communications failure

• r0949 = 0: HW reported Link Fail
• r0949 = 1: SW reported Link Fail
Reaction: OFF 2
Cause: MMC-PS Cloning Failed.
• r0949 = 0: MMC-PS Not Connected or incorrect MMC-PS Type
• r0949 = 1: MMC-PS cannot write to MMC
• r0949 = 2: MMC-PS File not available
• r0949 = 3: MMC-PS cannot read the
Reaction: OFF 2
File exists but the contents are not valid Control Word Corruption.
Reaction: OFF 2
File exists but was not the correct drive type.
Reaction: OFF 2
No Clone00.bin File in the correct directory /USER/SINAMICS/DATA.

No setpoint values from PLC during telegram off time

No setpoint values from USS during telegram off time


No setpoint values from Control Panel during telegram off time

• Broken wire
• Signal out of limits

External fault triggered via command input via control word 2, bit 13
Reaction: OFF 2
Signal from Encoder lost (check fault value r0949):
• r0949 = 0: Encoder signal lost.
• r0949 = 1: Encoder loss detected due to sudden speed change (i.e. speed change
detected on encoder in a
single sca
Reaction: OFF 2
Software Error
Reaction: OFF 2
Software error or processor failure.

PID Feedback below min. value p2268.

PID feedback above max. value p2267.
Reaction: OFF 2
During startup the drive checks if the configuration vector (SZL vector) has been
programmed correctly and if hw
matches the programmed vector. If not the drive will trip.
• r0949 = 1: Internal Failure
Reaction: OFF 2
This fault occurs after a Powermodul (PM) / Control Unit (CU) Swap or a Startup
Clone. It can also be caused by a
faulty read from the EEPROM, see F0051 for more details.
The parameterset after a CU swa
Reaction: OFF 2
Timeout, trigger fault,…

Load conditions on motor indicate belt failure or mechanical fault.
• r0949 = 0: trip low torque/speed
• r0949 = 1: trip high torque/speed
Reaction: OFF 2
• In SLVC or VC (p1300 greater than 20) and Ramp rate too fast
• In SLVC or VC (p1300 greater than 20) and done OFF2 and RUN onto a spinning
motor without Flying start
enabled
• In SLVC (p1300 = 20 or 2
Reaction: NONE
Acknowledge: NONE
• Motor power does not correspond to the inverter power

• Motor leads are too long
• Earth faults
Reaction: NONE
Acknowledge: NONE
Overvoltage limit is reached. This warning can occur during ramp down, if the Vdc
controller is disabled (P1240 = 0).
Reaction: NONE
Acknowledge: NONE
• Main supply failed
• Main supply and consequently DC-link voltage (r0026) below specified limit.
Reaction: NONE
Acknowledge: NONE
Warning level of inverter heat sink temperature, warning level of chip junction
temperature, or allowed change in temperature
on chip junction is exceeded, resulting in pulse frequency reduction and/or output
frequency re
Reaction: NONE
Acknowledge: NONE
Warning level exceeded, current will be reduced if parameterized (P0610 = 1)
Reaction: NONE
Acknowledge: NONE
Overload warning. Difference between heat sink and IGBT junction temperature
exceeds warning limits.
Reaction: NONE
Acknowledge: NONE
Inverter temperature signal loss
Reaction: NONE
Acknowledge: NONE
• Motor overloaded.
• Load cycles or load steps too high.
Reaction: NONE
Acknowledge: NONE
One phase of output is disconnected.
Reaction: NONE
Acknowledge: NONE
Large dclink ripple

Large dclink ripple detected
Reaction: NONE
Acknowledge: NONE
The breaking energy is too large.
The breaking resistor is not suited for the application.
Reaction: NONE
Acknowledge: NONE
Motor data identification (P1910) selected or running.
Reaction: NONE
Acknowledge: NONE
Speed Control Optimisation (P1960) is selected or running.
Reaction: NONE
Acknowledge: NONE
The actual speed has exceeded the maximal speed (status bit r2197.12) or the
speed deviation is larger than specified
(status bit 2197.7).
Reaction: NONE
Acknowledge: NONE
Cause: MMC-PS Plugged During Operation and none was present at startup.
Therefore, possible corruption of current
dataset on next power cycle from Automatic Cloning at Startup.
Reaction: NONE
Acknowledge: NONE
Signal from Encoder lost; Inverter might have switched to sensorless vector
control.
Check also alarm value r0947:
• r0949 = 0: Encoder signal lost.
• r0949 = 5: Encoder not configured in P0400, but required for sensored
Reaction: NONE
Acknowledge: NONE
Internal time slice overrun
Reaction: NONE
Acknowledge: NONE
Wrong parameter and/or configuration telegram
Reaction: NONE
Acknowledge: NONE
Error in double word reference table
Reaction: NONE
Acknowledge: NONE
connection error, no bus initialization (no master), no clear bus signal, …
Reaction: NONE
Acknowledge: NONE
no or empty control word 1 received
Reaction: NONE
Acknowledge: NONE
lost subscriber information
Reaction: NONE
Acknowledge: NONE
no actual data from CUP
Reaction: NONE
Acknowledge: NONE
e.g. hardware check, communication, V1SL stack, …

Reaction: NONE
Acknowledge: NONE
wrong DIP switch or parameter settings for PROFIBUS address
Reaction: NONE
Acknowledge: NONE
Cause: Communication with CB (communication board) is lost.
Reaction: NONE
Acknowledge: NONE
CB (communication board) reports a configuration error.
Reaction: NONE
Acknowledge: NONE
Occurs
• if main supply voltage (P0210) is permanently too high.
• if motor is driven by an active load, causing motor to goes into regenerative
mode.
• at very high load inertias, when ramping down.
Reaction: NONE
Acknowledge: NONE
Vdc max controller is active; so ramp-down times will be increased automatically

to keep DC-link voltage (r0026)
within limits (P2172).
Remedy: Check the following:
• Supply voltage must lie within limits indicated on rat
Reaction: NONE
Acknowledge: NONE
Vdc min controller will be activated if DC-link voltage (r0026) falls below minimum
level (P2172).
The kinetic energy of the motor is used to buffer the DC-link voltage, thus causing
deceleration of the drive! So short
ma
Reaction: NONE
Acknowledge: NONE
Cause: AO parameters (P0777 and P0779) should not be set to identical values,
since this would produce illogical results.
Reaction: NONE
Acknowledge: NONE
Cause: No Load is applied to the inverter.
As a result, some functions may not work as under normal load conditions.
Reaction: NONE
Acknowledge: NONE
Both JOG right and JOG left (P1055/P1056) have been requested. This freezes the
RFG output frequency at its current
value.
Reaction: NONE
Acknowledge: NONE
Cause: PID Autotuning (P2350) selected or running
Reaction: NONE
Acknowledge: NONE
Load conditions on motor indicate belt failure or mechanical fault.

A passivated safe torque off (passivated STO) has been initiated by hardware due
to a drive fault:
• r0949 = 33: passivated STO acknowledge after a drive fault requires the OFF first
and then an

Acknowledge: Power on
System startup error. Error during the startup initialisation after a PowerCycle or
HotSwap.
This error is critical and cannot be acknowledged. A restart (hotswap or power
cycle) of the drive is required!
•r

Cause: EEPROM data inconsistency error:
• r0949 = 100: Safety parameters have not been written correctly to EEPROM on
P1. Try to load parameters
again.
• r0949 = 200: EEPROM data inconsistency er

Cause: Data exchange error between processors:
• r0949 = 100: P2 has entered the safe torque off due to a drive fault on P2 or a
subsequent fault of F1600/F1630
• r0949 = 102: Dynamic checksums a

Cause: The hardware (safety or non-safety hardware) could no be identified.
• r0949 = 100: Identification error during startup on P1.
• r0949 = 101: Runtime detection error on P1.
• r0949 = 102: Hardware or software con

The maximum frequency has been exceeded.
• r0949 = 100: Frequency error on P1, maximum frequency exceeded.
• r0949 = 200: Maximum frequency exceeded on P2.

Error in frequency detection of the frequency estimation circuit (voltage frequency

measurement (VFM) module):
• r0949 = 100: Difference in frequency comparison on P1.
• r0949 = 101: VFM estimat
• r0949 = 100: Error in supply voltage 3.3 V or 24 V on the control board.
• r0949 = 101: Temperature of control board exceeds the limits.

Cause: The processor selftest has uncovered an error:
• r0949 = 100: General error on P1.
• r0949 = 101: Error in RAM test on P1.
• r0949 = 102: Error in ROM test on P1.
• r0949 = 103: Error in p

Cause: The consecutive counter checks the consistency of the communication
between P1 and P2:
• r0949 = 100: The consecutive monitoring counter has an error on P1.
• r0949 = 101: Processors are o

An error has been detected with the brake feedback.
• r0949 = 0: Problem with the safe brake.
• r0949 = 100: SB-Module: wire break detected or internal braketests failed during
dynamisation.
•r

An error has been detected with the PROFIsafe driver.
• r0949 = 102: A parameterisation error occured on P1. The parameters received
from the bus are not correct.
Check PROFIsafe parameters.
•r

• r0949 = 1: Buffer overflow on checksum calculation for P1 parameter access
functions.
• r0949 = 2: Buffer overflow on checksum calculation for P2 parameter access
functions.
• r0949 = 3: Endle

Error during startup or safety commissioning/reset:
• r0949 = 0: Error during safety commissioning/reset.
• r0949 = 1: Checksum error during safety commissioning or safety reset.
• r0949 = 2: Er

Cause: • r0949 = 100: Safety reset timeout on P1.
• r0949 = 200: Safety reset timeout on P2.
Cause: A write request for one or more safety parameters was rejected:
• r0949 = 0: Problem during finalization of safety parameters. Drive has reloaded
the old data.
• r0949 = 1: Safety password

• r0949 = 0: Attempt to leave safety commissioning with r9798 != p9799.

• r0949 = 1: Attempt to leave safety commissioning with r9898 != p9899.
• r0949 = 2: Attempt to leave safety commissioning
Reaction: NONE
Acknowledge: NONE
The warning indicates that at least one parameter has been changed in the safety
commissioning or safety reset.
Reaction: NONE
Acknowledge: NONE
Cause: Problem with the consistency of the safety input signals. The drive reduces
the frequency according to the settings
of the SS1.
When zero frequency is reached, the passivated STO is entered and a drive fault is
issu
Reaction: NONE
Acknowledge: NONE
a) Output frequency when entering the SLS is higher than p9690 and p9692 is
configured to trigger a passivated
STO with a drive fault.
b) Output frequency exceeds the SLS tolerance p9691.
In both cases, the frequency is r
Reaction: NONE
Acknowledge: NONE
Switching on of the drive not possible and the drive will therefore remain in the
READY state (see r0002).
Reaction: NONE
Acknowledge: NONE
Semaphore problem at startup. Cannot load last safety parameters. Loading
default values instead.
Reaction: NONE
Acknowledge: NONE
The safety reset or the safety commissioning are currently active (selected via
p0010 = 95).
Reaction: NONE
Acknowledge: NONE
Cause: Dynamisation timer (see r9660) has expired. A new dynamisation test is
required.
Improper anolgue signal from Masterdrive or Micromaster has problem.

Overvoltage
Overcurrent
Overload
Run Enable is not closed
Bit0 = 1 (Ready to switch on) & Bit6=1(Switch on disabled. Ex: Status 0xFA71
The converter stops due to inverter overload and turns on the switch on inhibit bit.
Service Switch on Wrong position

Run Enable is open
Alarm is active
Run Enable is open
Converter fault
Run Enable is open
Converter fault
Run Enable is open
Converter fault
Converter is in state “switch on inhibited”
Converter is in state “switch on inhibited”
- RS485 Port faulty

- RS232 (old GA90VSD with Simovert P Converter), when upgrade, the
RS232/RS485 converter faulty
- Power Supply board of VSD is faulty.
- When upgrading from Mk III to Mk IV / V, the baud rate and address are not
correct.
- When rep
Wrong converter status
Converter fault
Synchronisation errors or wrong function replies
Wrong checksum
Frame Errors
Service Switch = 1
PKW length parameter is not 3
Run Enable is not closed
When the Sinamics120 goes into external fault, it sends 0rpm to the Elektronikon
although the motor is still running.
fa31 is HEXADECIMAL value for the status word. Converting FA31(hex) gives
1111101000110001(binary) = STATUS WORD !
Status word of the MM440 :

You can see the drive status says that "Drive ready to run" = 0 = NO --> Run enable
is not coming in at start or
Faulty pressure sensor that is used for pressure regulation

Mk5 CAN1 connector got loose after power on
KEB-Drive for IGV CAN connector got loose after power on
KEB-Drive for BOV CAN connector got loose after power on
KEB drive has no mains power, only 24V
KEB bus terminator resistances on one or more intermediate nodes are mounted
An unknown CAN port was configured on the KEB driver
Mk5 CAN1 connector fitted to Mk5 CAN2 slot

Mk5 CAN1 connector got loose before power on
KEB-Drive for IGV CAN connector got loose before power on
KEB-Drive for BOV CAN connector got loose before power on
KEB bus terminator resistances on one or more intermediate nodes are mounted
CAN_H and CAN_L are exchange during CAN cable connector manufacturing
CAN_L signal is disconnected in the connector
CAN_H and CAN_L are exchange during CAN cable connector manufacturing
KEB-drive for IGV and BOV have been exchanged
ErrorCode"0xXX: any other error code
consult annex 1
Mechanical blocking on the load path, KEB delivers insufficient HOMING torque to
overcome the blockage
The hard stop is not present, the KEB-drive keeps searching for this hard stop untill
the homing timeout has elapsed
The Mk5 reset function was tried before the resolving the KEB related error
KEB bus terminator resistances on end nodes are not mounted

KEB bus terminator resistances on one more intermediate nodes are mounted
Control release (terminal ST) is not switched

Mechanical blocking on the load path, KEB delivers insufficient torque to overcome
the blockage
“Nervous” behavior of valves. The valves need to acquire a new position too fast
before reporting arriving to the previous one
KEB was configured with a wrong baudrate
A short circuit is present in one of the CAN connectors
The connector of the CAN bus for the KEB drives is not fitted to the Mk5 CAN1
connector
Mk5 was downloaded for a 4 to 20mA actuator
Mistake in diagnosis, CAN communication is not failing
440: - Motor power (P0307) does not correspond to the inverter power (r0206)
- Motor leads are too long (unlikely in Atlas Copco application)
- Motor leads short circuit
- Earth Faults
440: - DC-Link controller disabled (P1240 = 0)

- DC-Link voltage (r0026) exceeds trip level (P2172)
- Too high main supply, or if motor is in regenerative mode. (Regenerative mode
can be caused by fast ramp downs or if the motor is driven from an active l
440: - Main supply failed

- Incorrect parameter settings
- DC Link low voltage
440: - Ventilation inadequate

- Ambient temperature is too high
- The parameter P1755, which is the start frequency of minimum 0.1 Hz, however,
it does a "walkabout" and gives erratic F004. In most cases, P1755 = 7.3 ==> this
should be modified to 0.2 (H
440: Inverter overload

- Duty cycle too demanding
- Motor power (P0307) exceeds inverter power capability (r0206)
Motor overloaded, defective sensor

Wire breakage of inverter temperature (heatsink) sensor
Open or short circuit of motor temperature sensor. If the signal loss is detected,
temperature monitoring switches over to monitoring with the motor thermal
model.
Fault occurs if one of the three input phass are missed while the pulses are
enabled and drive is loaded
Possibly due to burn out or badly crimped cable as reported by colleagues in
France, Germany and Switzerland.
Fault occurs if the sum of the phase currents is higher than 5% of the nominal
inverter current .
This fault only occurs on inverters that have 3 current sensors (Fram sizes D to F &
FX, GX)
Hardware fault (r0947 = 22 and r0494 = 1) caused by the following events:

1) DC-Link overcurrent = short circuit of IGBT
2) Short circuit of chopper
3) Earth Fault
4) I/O board is not properly inserted
- UCE failure was detected, when r0947 = 22 and faul
One motor phase is disconnected
Fan malfunction
Auto restart attempts exceed value of P1211
Motor Data ID failed:

Fault Value
= 0: Load missing
= 1: Current limit level reached during identification
= 2: Identified stator Resistance less than 0.1% or great than 100%
= 3: """" rotor ""
= 4: Identified stator reactance less than 50% and greater t
Speed control optimisation (P1960) failed

- Fault Value = 0: Time out waiting for stable speed
= 1: Inconsistent Readings
Read or write while saving non-volatile parameter
Read failure for power stack information or invalid data
Read failure for IP EEPROM info or invalid data
- Wrong IO board is connected

- No ID detected on IO Board, no data
Intenral Communications failure
No Setpoint values from CB (communications board) during telegram off time

Broken wire
Signal out of limits

External fault triggered via for example terminal input
Signal from Encoder lost
Software error, or processor failure
PID Feedback below min. value P2268
PID Feedback above max. value P2267
Fault value:
= 1: Some power section tests have failed
= 2: Some control board tests have failed
= 4: Some functional tests have failed (MM420 only)
= 16 Internal RAM failed on power-up check
Load conditions on motor indicate belt failure or mechanical fault
- Motor power (P0307) does not correspond to the inverter power (P0206)
- Motor leads too long
- Earth fault
Overvoltage limit is reached

This warning can occur during ramp down, if the dc-link controller is disabled
(P1240 = 0)
Main supply failed

Main supply (P0210) must lie within limits on rating plate
Warning level of heat-sink temp. (P0614) is exceeded, resulting in pulse reduction

and/or output frequency reduction (depending on parameterisation in P0610)
Warning level (P0294) exceeded, output frequency and/or pulse frequency will be
reduced if parameterised (P0290)
Motor overloaded warning
The cyclic access to the UCE Values and powerstack temperatures via I2C bus
One motor phase missing

Motor Data ID run selected or running
Speed Control Optimisation (P1960) is selected or running
Signal from Encoder lost and Inverter has switched to sensorless vector control
CB is lost
Vdc max controller has been de-activated, since controller is not capable of
keeping DC-Link voltage (r0026) within limits (P2172)
-> Occurs if main supply voltage (P0210) is permamently too high
-> Occurs if motor is driven by an active load, causing mot
Vdc max controller is active; rampl down times will be increased automatically to
keep DC-Link voltage (r0026) within limits (P2172)
Vdc min controller will be activated if DC-Link voltage (r0026) falls below minimum
level (P2172). The kinetic energy of the motor is used to buffer the DC-Link voltage,
thus causing deceleration of the drive ! So short mains failures do not necessarily l
ADC parameters should not be set to identical values, since this would produce
illogical results.
Fault vaule:
= 0: Parameter settings for output identical
= 1: Parameter settings for input identical
= 2: Parameter settings input do not correspond to ADC
DAC parameters should not be set to identical values, since this would produce
illogical results.
Fault Value:
= 0: Parameter settings for output identical
= 1: Parameter settings for input identical
= 2: Parameter settings for output do not correspond to
No Load is applied to inverter

-
Both left and right are requested ==> freezes the RFG output frequency at its
current value
PID Autotuning (P2350) selected or running
- up / down ramp too steep (excessive gradient)

- inverter connected to an already spinning without using the flying restart
function
- motor incorrectly connected
- motor to small
- Voltage boost P1611 for sensorless vector control too low
- Running with
Main Power supply voltage too low or missing links in the control panel.
Main Power supply voltage too low or missing links in the control panel.
Main Power supply voltage too low.
Main Power supply voltage too low.
Phase loss detected
Phase loss detected

Maximum allowable voltage of the DC-link exceeded; Threshold is lowered in case
of higher temperature
Maximum allowable voltage of the DC-link exceeded; Threshold is lowered in case

of higher temperature
Undervoltage detected
Undervoltage detected
Overvoltage or overtemperature detected in IGBT (U phase)
Overvoltage or overtemperature detected in IGBT (U phase)
Overvoltage or overtemperature detected in IGBT (V phase)
Overvoltage or overtemperature detected in IGBT (V phase)
Overvoltage or overtemperature detected in IGBT (W phase)
Overvoltage or overtemperature detected in IGBT (W phase)

Overtemperature detected in an IGBT
Overtemperature detected in an IGBT
Overtemperature detected in the heatsink
Overtemperature detected in the heatsink
Overtemperature detected in IGBT junction UH
Overtemperature detected in IGBT junction UH
Overtemperature detected in IGBT junction UL
Overtemperature detected in IGBT junction UL
Overtemperature detected in IGBT junction VH
Overtemperature detected in IGBT junction VH
Overtemperature detected in IGBT junction VL

Overtemperature detected in IGBT junction VL
Overtemperature detected in IGBT junction WH
Overtemperature detected in IGBT junction WH
Overtemperature detected in IGBT junction WL
Overtemperature detected in IGBT junction WL
Emergency stop circuit opened
- Emergency stop circuit opened

- Hardware fault detected
- Emergency stop circuit opened

- Hardware fault detected
Internal power supply tripped
General fault detected in power section

- Eeprom read failed

- Timeout communication
- Eeprom read failed
- Timeout communication
- Failed temperature reading of power board
- Timeout communication at initialization
- Failed temperature reading of power board
- Timeout communication at initialization
General fault detected
General fault detected
Internal checksum error detected
Internal communication timeout
hardware)
Internal communication overload
Internal communication overload
Internal control overload
Internal control overload
Overcurrent detected at motor side

Overcurrent detected at motor side. **** from GA55-90VSD ==>, one problem
could be faulty sensor. But cannot change this sensor onsite, has to replace
convertor. See ECB WUXI0155 (P IV)
Short Circuit detected in U phase
Short Circuit detected in V phase
Short Circuit detected in U phase
Short Circuit detected in V phase
Short Circuit detected in W phase
Short Circuit detected in W phase
Overvoltage detected
Overvoltage detected
The firmware of a DRIVE CLiQ component must be updated as there is no

suitable firmware or firmware version in the component for operation with
the Control Unit. Alarm value (r2124, decimal)
a Drive-CliQ component must be powered-up again (POWER ON) as, for

example, the firmware was updated. Alarm value (r2124, decimal):
Component number of the DRIVE-CLiQ component.
On the CompactFlash card, at least one file in the directory
/SIEMENS/SINAMICS/ has been illegally changed with respect to that
supplied from the factory. No changes are permitted in this directory.
Alarm value (r2124, decimal):
0: Checksum of one file is
On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA
or /ADDON/SINAMICS/DATA has been
illegally changed with respect to that supplied from the factory. No changes
are permitted in this directory.
Alarm value (r2124, interpret decimal):
The problem is indicated in the first digit of the alarm value:
1: File does not exist.
2: Firmware version of the file does not match the software version.
3: The file checksum is incorrect.
The second digit of the alarm value indicates in which directory the file is
located:
0: Directory /SIEMENS/SINAMICS/DATA/
1: Directory /ADDON/SINAMICS/DATA/
The third digit of the alarm value indicates the file:
0: File MOTARM.ACX
1: File MOTSRM.ACX
2: File MOTSLM.ACX
3: File ENCDATA.ACX
4: File FILTDATA.ACX
5: File BRKDATA.ACX
When the Control Unit ran-up no complete data set from the parameter
save files was found. The last time that the parameterization was saved, it
was not completely carried-out. Instead, a backup data set or file is
downloaded. Alarm value (r2124, hexadeci
An invalid data type was detected when evaluating parameter files

Psxxxyyy.ACX, Ptxxxyyy.ACX, Ptxxxyyy.ACX, Caxxxyyy.ACX or Ccxxxyyy.ACX,
saved on the CompactFlash card.
Alarm value (r2124, hexadecimal) only for internal Siemens

troubleshooting.
An invalid data type was detected when evaluating parameter files

Psxxxyyy.ACX, Ptxxxyyy.ACX, Ptxxxyyy.ACX, Caxxxyyy.ACX or Ccxxxyyy.ACX,
saved on the CompactFlash card.
Alarm value (r2124, hexadecimal) only for internal Siemens

troubleshooting.
When evaluating the parameters files Psxxxyyy.ACX, Ptxxxyyy.ACX,

Caxxxyyy.ACX, or Ccxxxyyy.ACX, saved on the CompactFlash card, a
parameter value was not able to be transferred into the Control Unit
memory.
Alarm value (r2124, hexadecimal) Only for intern
It is not possible to write into a write-protectice file (PSxxxxx.ACX). The

write request was interrupted.
Alarm value (r2124, decimal): Drive object number
A system overload was calculated on a complete active target topology.
Alarm value (r2124, decimal)
2: Computation time load too high
6: Cyclic computation time load too high
A system overload was determined based on measured values.

Alarm value (r2124, decimal)
2: Computation time load too high
6: Cyclic computation time load too high
See also: r9976
One or several inactive encoders indicate an error.

Non-volatile data save cannot be activated as this is not supported by the
CU
The time master exited the selected tolerance window for time
synchronization.
See also: p3109 (RTC real time synchronization, tolerance window)
The CompactFlash card (non-volatile memory) was withdrawn in operation.

Notice:
It is not permissable that the CompactFlas card is withdrawn or inserted
under voltage.
When changing a sampling time (p0115[0], p0799 or p4099), inconsistency
between the clock cycles has been identified.
1: Value, low minimum value.
2: Value, high maximum value.
3: Value not a multiple of 1.25 μs.
4: Value does not match clock-cycle synchronous PROFIBUS operation.
5: Value not a multiple of 125 μs.
10: Special restriction of the drive object violated.
20: For a SERVO with a 62.5 μs sampling time, more than a maximum of
two SERVO-type drive objects were
detected on the DRIVE-CLiQ line (no other drive object is permitted on this
line).
21: Value can be a multiple of the current controller sampling time of a
servo or vector drive in the system (e.g. for
TB30, the values of all of the indices should be taken into account).
30: Value less than 31.25 μs.
31: Value less than 62.5 μs.
32: Value less than 125 μs.
40: Nodes have been identified on the DRIVE-CLiQ line whose highest
common denominator of the sampling times
is less than 125 μs. Further, none of the nodes has a sampling time of less
than 125 μs.
41: A chassis unit was identified on the DRIVE-CLiQ line as a node. Further,
the highest common denominator of
the sampling times of all of the nodes connected to the line is less than 250
μs.
42: An Active Line Module was identified on the DRIVE-CLiQ line as a node.
Further, the highest common denominator
of the sampling times of all of the nodes connected to the line is less than
125 μs.
43: A Voltage Sensing Module (VSM) was identified on the DRIVE-CLiQ line
as a node. Further, the highest common
denominator of the sampling times of all of the nodes connected to the line
When changing the minimum pulse frequency (p0113) inconsistency
between the pulse frequencies was identified.
1: Value, low minimum value.
2: Value, high maximum value.
3: Resulting sampling time is not a multiple of 1.25 μs.
4: Value does not match clock-cycle synchronous PROFIBUS operation.
10: Special restriction of the drive object violated.
99: Inconsistency of cross drive objects detected.
116: Recommended clock cycle in r0116[0...1].
Error when reading the read-write data of the EEPROM in the Control Unit.
Alarm value (r2124, decimal): Only for internal Siemens Troubleshooting
Error when reading the read-only data of the EEPROM in the option
module.
Fault Value (r0949, decimal): Internal Siemens troubleshooting
The memory card contains a more recent firmware version than the one in
the connected DRIVE-CLiQ component.
Component number of the DRIVE-CLiQ component involved.
Firmware update is active for at least one DRIVE-CLiQ component.

Component number of the DRIVE-CLiQ component.
For a component, "de-activate and not present" is set but this component
is still in the topology.
Alarm value (r2124, interpret hexadecimal):
Byte 1: Component number
Byte 2: Component class of the component
Byte 3: Connection number
Note: Component clas
For the active drive object involved, at least one activated component is
missing.
Note:
All other active and operational drive objects can be in the "RUN" state.
For the active drive object involved, at least one activated component is
missing.
Note:
All other active and operational drive objects can be in the "RUN" state.
If, when inserting a component of the target topology, an inactive, non-

operational drive object becomes operational again. The associated
parameter of the component is, in this case, set to "activate" (P0145,
P0155, P0165).
Note: This is only a message,
If, when inserting a component of the target topology, an inactive, non-

operational drive object becomes operational
again. The associated parameter of the component is, in this case, set to
"activate" (p0125, p0145, p0155, p0165).
Note:
This is the only
If a component of the target topology for an active drive object is inserted

and the associated parameter of the component
is set to "de-activate" (p0125, p0145, p0155, p0165).
Note:
This is the only message that is displayed for a de-activated component.
This alarm is output:

If an inactive/non-operational drive object is again active/ready for
operation
and
r9498[] or r9499[] are not empty
and
the connections listed in r9498[] and r9499 have actually been changed
The inserted component has still not been initiated, as the pulses are
enabled.
A drive object number is missing in p0978
Index of p0101 under which the missing drive object number can be
determined.
p0978 contains a drive object number that does not exist.

Index of p0978 under which the drive object number can be determined.
A drive object number is present more than once in p0978.

Index of p0978 under which the involved drive object number is located.
Partial lists are available more than twice in p0978. After the second 0, all
must be 0.
Index of p0978 under which the illegal value is located.
In p0978, dummy drive object numbers (255) are only permitted in the first
partial list.
Index of p0978 under which the illegal value is located.
Unable to carry out a quick commissioning. The existing actual topology

does not fulfill the requirements.
ccccbbaa hex: cccc = preliminary component number, bb = supplementary
information, aa = fault cause
aa =
At least one component is not assigned to a drive object.
- when commissioning, a component was not able to be automatically
assigned to a drive object.
- the parameters for the data sets are not correctly set.
Comp
The detected actual topology contains SINUMERIK and SIMOTION

components.
The drive system is no longer booted. In this state, the drive control
(closed-loop) cannot be enabled.
Fault value (r0949, interpret hexadecimal):
ddccbbaa hex: cc = fault cause, bb
The topology comparison has detected a power unit in the actual topology
that has been shifted with respect to the
target topology.
ddccbbaa hex:
dd = connection number
cc = component number
bb = component class
The topology comparison has detected a Sensor Module in the actual

topology that has been shifted with respect to
the target topology.
ddccbbaa hex:
bb = component cl
The topology comparison has detected a Terminal Module in the actual

topology that has been shifted with respect
to the target topology.
ddccbbaa hex:
bb = component
The topology comparison has detected a DRIVE-CLiQ Hub Module in the

actual topology that has been shifted with
respect to the target topology.
ddccbbaa hex:
bb = comp
The topology comparison has detected a controller extension 32 (CX32) in
the actual topology that has been shifted
with respect to the target topology.
ddccbbaa hex:
aa = component number of the component shifted in the target topology
Note:
The connection in the actual topology where the shifted component was
detected is described in dd, cc and bb.
Component class and connection number are described in F01375.
The drive system is no longer booted. In this state, the drive control
(closed-loop) cannot be enabled.
The topology comparison has detected a DRIVE-CLiQ component in the

ddccbbaa hex:
bb = compo
The topology comparison has detected a option slot component in the

ddccbbaa hex:
bb = comp
The topology comparison has detected an EnDat encoder in the actual

topology that has been shifted with respect
to the target topology.
ddccbbaa hex:
bb = component c
The topology comparison has detected a motor with DRIVE-CLiQ in the

ddccbbaa hex:
bb = comp
The topology comparison has found a component in the actual topology
which is not specified in the target topology.
The alarm value includes the component number and connection number
of the component with which the additional
component is connected.
Alar
The topology comparison has detected differences in the actual and target
topologies in relation to one component.
There are differences in the electronic rating plate.
ddccbbaa hex: aa = component number of the
The component class, the component type or the number of connections
differ.
ddccbbaa hex: aa =
The serial number is different.
ddccbbaa hex:
cc = number of differences
aa
A component was connected to another connection.
The different connections of a component are described in the alarm value:
Alarm value (r21
A topology comparison has found differences between the actual and

target topology for several components. A
component was connected to another connection.
The different connections of a component are described in the alarm value:
Alarm value (r2124, inte
The topology comparison has detected a power unit in the target topology
that is not available in the actual topology.
Component number of the additional target components.
The topology comparison has detected a Sensor Module in the target
topology that is not available in the actual topology.
The topology comparison has detected a Terminal Module in the target

topology that is not available in the actual
topology.
The topology comparison has detected a DRIVE-CLiQ Hub Module in the

target topology that does not exist in the
actual topology.
The topology comparison has detected a controller extension 32 (CX32) in

the target topology that is not available
in the actual topology.
The topology comparison has detected a DRIVE-CLiQ component in the

target topology that is not available in the
actual topology.
The topology comparison has detected an option slot module in the target
topology.
The topology comparison has detected an EnDat encoder in the target

topology.
The topology comparison has detected a motor with DRIVE-CLiQ in the

target topology that is not available in the
actual topology.
There are BICO interconnections as signal sink from a drive object that is
either inactive/not operational.
The BI/CI parameters involved are listed in r9498.
The associated BO/CO parameters are listed in r9499.
The list of the BICO interconnections to ot
The maximum number of BICO interconnections (signal sinks) when de-
activating a drive object was exceeded.
When de-activating a drive object, all BICO interconnections (signal sinks)
are listed in the following parameters:
- r9498[0...29]: List of the BI/
During a reconnect operation (e.g. while booting or downloading - but can

also occur in normal operation) a parameter
was not able to be written to.
Example:
When writing to a double word BICO input in the second index, the
memory areas overlap (e.g. p886
The selected service/maintenance interval for this motor was reached.

Motor data set number.
See also: p0650 (Actual motor operating hours), p0651 (Motor operating
hours maintenance interval)
The configured times for PROFIBUS communication are not permitted and
the DP cycle is used as the actual value
acquisition cycle for the safe movement monitoring functions:
Isochronous PROFIBUS: the total of Ti and To is too high for the set DP
cycle. The
The test of the motion monitoring functions was already illegally active
when booting.
This is the reason that the test is only carried out again after selecting the
forced checking procedure parameterized
in p9705.
Note:
This message does not result in a
The time set in p9559 for the forced checking procedure of the safety
motion monitoring functions has been
exceeded. A new test is required.
After next selecting the forced checking procedure parameterized in p9705,
the message is withdrawn and the monito
The commissioning of the "Safety Integrated" function is selected.

This message is withdrawn after the safety functions have been
commissioned.
Note:
This message does not result in a safety stop response.
See also: p0010
The time set in p9659 for the forced checking procedure of the safety
shutdown paths has been exceeded. The
safety shutdown paths must be re-tested.
After the next time the "STO" function is de-selected, the message is
withdrawn and the monitoring time is
The drive waits for communication to be established with SINUMERIK or
TM54F to execute the safety-relevant
motion monitoring functions.
Note:
In this state, the pulses are safely suppressed.
A PROFIBUS master attempts to establish a connection using an incorrect

configuring telegram.
50: Syntax error.
51: Connection established to more drive objects than configured in the
device. The drive objects for p
A PROFIBUS master attempts to establish a connection using an incorrect

parameterizing telegram.
1: Incorrect parameterizing bits.
10: Illegal length of an optional parameterizing block.
11: Illegal ID of an optiona

0: Bus cycle time Tdp < 0.5 ms.
1: Bus cycle time Tdp > 32 ms.
2: Bus cycle time Tdp is not an integer multiple of the current controller
clock cycle.
3: Instant of the actual value sensing Ti > Bus cycle time Tdp o
The drive unit did not accept the receive configuration data.
Return value of the receive configuration data check.
0: Configuration accepted.
1: Connection established to more drive objects than configured in the d
The cyclic connection to the PROFIBUS master is interrupted.
Output data of PROFIBUS master (setpoints) received at the incorrect

instant in time within the PROFIBUS clock
cycle.
The current controller clock cycle of all drives must be set the same for the
clock cycle synchronous operation.
Number of the drive object with different current controller clock cycle.
The speed controller clock cycle of all drives must be set the same for the
clock cycle synchronous operation.
Number of the drive object with the different speed controller clock cycle.
The bus is in the data exchange state and clock synchronous operation has
been selected using the parameterizing
telegram. It was not possible to synchronize to the clock cycle specified by
the master.
- the master does not send a clock synchronous global
telegram. The global control telegram for synchronization is not being
received.
telegram. The global control telegram for synchronization is being
irregularly received.
-.the master is sending an irregular global control t
telegram. Synchronization with the master sign-of-life (STW2.12 ...
STW2.15) could not be completed because the
sign-of-life is changing diffe
For PROFIBUS peer-to-peer data transfer, the connection to at least one

Publisher has failed.
Alarm value (r2124, interpret binary):
Bit 0 = 1: Publisher with address in r2077[0], connection failed.
...
Bit 15 = 1: Publisher with address in r2077[15], con
After the drive system is powered up, the synchronization between the
basic clock cycle, DRIVE-CLiQ clock cycle
and application clock cycle was started but was not completed within the
selected time tolerance.
Only for internal Siemens troubleshooting.
and application clock cycle was started but was not completed within the
selected time tolerance.
The function generator has already been started.

The drive object specified for connection does not exist.
See also: p4815 (Function generator drive number)
No drive specified for connection in p4815.

The drive object specified for connection is not a SERVO / VECTOR.

The drive object specified for connection is already specified.

Drive object number of the drive object that is specified a multiple number
of times.
The set operating mode (p1300) of the drive object is not permissible when
using the function generator.
Number of the drive object involved.
The speed setpoint of a drive selected for connection is greater than the
value for the standstill detection set using
p1226.
The speed actual value of a drive selected for connection is greater than
the value for the standstill detection set
using p1226.
Cause: The master control and/or enable signals are missing to connect to
the specified drive.
Magnetizing has not yet been completed on a drive object specified for
connection.
This parameter setting cannot be changed when the function generator is
active (p4800 = 1).
See also: p4810, p4812, p4813, p4815, p4820, p4821, p4822, p4823,
p4824, p4825, p4826, p4827, p4828, p4829
The value for the period is too short.

See also: p4821 (Function generator period
The selected pulse width is too high.

The pulse width must be less than the period duration.
See also: p4822 (Function generator pulse width)
The specified physical address is zero.

See also: p4812 (Function generator physical address)
The value for the offset is higher than the value for the upper limit or lower
than the value for the lower limit.
See also: p4826 (Function generator offset)
The bandwidth referred to the time slice clock cycle of the function
generator has either been set too low or too high.
Depending on the time slice clock cycle, the bandwidth is defined as
follows:
Bandwidth_max = 1 / (2 * time slice clock cycle)
Bandwidth_min = Bandwidth_max / 100000
Example:
Assumption: p4830 = 125 μs
--> Bandwidth_max = 1 / (2 * 125 μs) = 4000 Hz
--> Bandwidth_min = 4000 Hz / 100000 = 0.04 Hz
Note:
p4823: Function generator bandwidth
p4830: Function generator time slice clock cycle
See also: p4823 (Function generator bandwidth), p4830 (Function
generator time slice cycle)
The time slice clock cycle selected does not match any of the existing time
slices.
See also: p4830 (Function generator time slice cycle)
The trace has already been started.

See also:p4700(trace control)
The trace duration is too short.
The minimum is twice the value of the trace clock cycle.
See also: p4271 (trace recording time)
slices.
See also: p4723 (Time slice cycle for trace)
slices.
The selected time slice clock cycle cannot be used for the endless trace
The selected time slice clock cycle cannot be used for the setting p4702 = 1
(2 x 8 recording channels).
- a signal to be traced was not specified.

- the specified signals are not valid.
See also: p4730 (Trace record signal 0), p4731 (Trace record signal 1),
p4732 (Trace record signal 2), p4733 (Trace
record signal 3)
- the specified signal does not exist.

- the specified signal can no longer be traced (recorded).
See also: p4730 (Trace record signal 0), p4731 (Trace record signal 1),
p4732 (Trace record signal 2), p4733 (Trace
record signal 3)
- a trigger signal was not specified.

- the specified signal does not exist.
- the specified signal is not a fixed-point signal.
- the specified signal cannot be used as a trigger signal for the trace.
See also: p4711 (Trace trigger signal)
The specified data type to select a signal using a physical address is invalid.
See also: p4711 (Trace trigger signal), p4730 (Trace record signal 0), p4731
(Trace record signal 1), p4732 (Trace
record signal 2), p4733 (Trace record signal 3)
The trace parameter settings cannot be changed when the trace is active.
p4720, p4721, p4722, p4730, p4731, p4732,
p4733, p4780, p4781, p4782, p4783, p4789, p4795
The selected pretrigger time must be shorter than the trace time.
See also: p4721 (Trace recording time), p4722 (Trace trigger delay)
The memory space still available on the Control Unit is no longer sufficient
for the trace function.
The value in p0118 produces a dead time of one clock cycle because it is
prior to setpoint availability. A possible
cause could be, for example, that the system characteristics no longer
match those parameterized after a component
has been replaced.
Alarm value (r2134, floating point):
The minimum value for p0118 where a dead time no longer occurs.
The system wwas not able to load an OA application.

The sampling times of the inputs/outputs were changed.

This change only becomes valid after the next boot.
The 24 V power supply for the digital outputs (X124) is missing.
The natural filter frequency of the speed setpoint filter (P1417) is greater
than the Shannon frequency. The Shannon frequency is calculated
according to the following formula: 0.5 / P0155[0]
The alarm threshold for overtemperature at the inverter heatsink has been
reached. The response is set using P0290.
If the temperature of the heatsink increases by an additional 5K, then fault
F30004 is initiated.
Maybe the cooling fan is faulty, the fil
The alarm threshold for overtemperature of the power semiconductor in

the AC converter has been reached. The response is set using P0290.
If the temperature of the chip increases by an additional 15 K, then fault
Maybe the cooling fa
The alarm threshold for the air intake overtemperature has been reached.
The response is set using P0290.
If the air intake temperature increases by an additional 5 K, then fault
Maybe the cooling fan is faulty, the filter block. The

The alarm threshold for the overtemperature of the electronics module has
been reached. The response is set using P0290.
If the temperature of the electronics module increases by an additional 5 K,
then fault F30036 is initiated.
Maybe the cooling fan is
The alarm threshold for the overtemperature of the rectifier has been
reached. The response is set using P0290.
If the temperature of the electronics module increases by an additional 5 K,
then fault F30037 is initiated.
Maybe the cooling fan is faulty,
Cooling system: alarm - flow rate has fallen below the alarm value
The temperature difference between the chip and heat sink has exceeded
the permissible limit value (for blocksize
power units only). Depending on p0290, a suitable overload response is
initiated.
See also: r0037
The deviation of the individaul currents of the power modules exceeds the
alarm threshold specified in P7010.
Alarm value (r2124, decimal)5/01/2007
1: Phase U
2: Phase V
3: Phase W
The deviation of the DC link voltage measured values exceeds the alarm
threshold specified in p7011.
For the drive object involved, fewer power unit components connected in
parallel are active than exist in the target
topology. Operation is only possible at reduced power (power de-rating).
The thermal I2t motor model identified that the temperature alarm
threshold was exceeded.
See also: r0034 (Motor utilization), p0605 (Motor overtemperature fault
threshold), p0611 (I2t motor model thermal
time constant)
An error was detected when evaluating the temperature sensor set in
p0600 and p0601.
With the fault, the time in p0607 is started. If the fault is still present after
this time has expired, then fault F07016 is
output; however, at the earliest, 1 s after alarm A07015.
Possible causes:
- wire breakage or sensor not connected (KTY: R > 1630 Ohm).
- measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).
For SME selected (p0601 = 10), number of the sensor channel leading to
the message.
An attempt was made to add a function module. This is not permissible if

the units have already been changed over.
See also: p0100 (IEC/NEMA mot stds), p0349 (System of units, motor
equivalent circuit diagram data), p0505
(Selecting the system of units
The ON/OFF1 command is not 0, either via binector input p0840 (current
CDS) or in control word p3982 bit 0.
The automatic restart (AR) is active. When the line supply returns and/or
the causes of the existing faults are
removed the drive is automatically restarted. The pulses are enabled and
the motor starts to rotate.
The measuring probe is connected

Alarm value (r2124, decimal):
9: DI/DO 9 (X122.8)
10: DI/DO 10 (X122.10)
11: DI/DO 11 (X122.11)
13: DI/DO 13 (X132.8)
14: DI/DO 14 (X132.10)
15: DI/DO 15 (X132.11)
The DC link voltage controller has been activated because the upper
switch-in threshold has been exceeded (r1242).
The ramp-down times are automatically increased in order to maintain the
DC link voltage (r0026) within the permissible
limits. There is a system deviation between the setpoint and actual speeds.
See also: p1240 (Vdc controller or Vdc monitoring configuration)
When the DC link voltage controller is switched out (disabled), this is the
reason that the ramp-function generator
output is set to the speed actual value.
The Vdc_max controller can no longer maintain the DC link voltage (r0026)
below the limit value (r1242) and was
therefore switched out (disabled).
- the line supply voltage is permanently higher than specified for the power
unit.
- the motor is permanently in the regenerative mode as a result of a load
that is driving the motor.
The DC link voltage controller has been activated as the lower switch-in
threshold has been undershot (r1246).
The kinetic energy of the motor is used in order to buffer the DC link. This
brakes the drive.
See also: p1240 (Vdc controller or Vdc monitoring configuration)
The current limiting controller of the V/f control was activated because the
current limit was exceeded.
The Vdc_max controller can no longer maintain the DC link voltage (r0026)
below the limit value (r1242) and was
therefore switched out (disabled).
- the line supply voltage is permanently higher than specified for the power
unit.
- the motor is permanently in the regenerative mode as a result of a load
that is driving the motor.
The configuration of the flux control (p1401) is contradictory.

ccbbaaaa hex
aaaa = parameter
bb = index
cc = fault cause
cc = 01 hex = 1 dec:
Quick magnetizing (p1401.6) for soft start (p1401.0).
Quick magnetizing (p1401.6) for flux build-up control (p1401.2).
Quick magnetizing (p1401.6) for Rs identification after restart (p0621 = 2).
The calculation of the jerk time Tr = MAX(p2572, p2573) / p2574 resulted in

an excessively high value so that the
jerk time is internally limited to 1000 ms.
Note:
The alarm is also output if jerk limiting is not active.
The status of the absolute encoder adjustment has changed.

In order to permanently save the determined position offset (p2525) it
must be saved in a non-volatile fashion (p0971,
p0977).
One of the following problems has occurred with the position actual value
preprocessing:
- an encoder is not assigned for the position actual value preprocessing
(p2502 = 0).
- an encoder is assigned, but no encoder data set (p0187 = 99 or p0188 =
99 or p0189 = 99).
- an encoder an an encoder data set have been assigned, however, the
encoder data set does not contain any
encoder data (p0400 = 0) or invalid data (e.g. p0408 = 0).
The maximum velocity (p2571) is too high to correctly calculate the modulo
correction.
Within the sampling time for positioning (p0115[5]), with the maximum
velocity, a maximum of the half modulo length
must be moved through. p2571 was limited to this value.
The current setpoint velocity is greater than the parameterized maximum

velocity (p2571) and is therefore limited.
An illegal combination of input signals that are simultaneously set was

identified.
0: Jog 1 and jog 2 (p2589, p2590).
1: Jog 1 or jog 2 and direct setpoint input/MDI (p2589, p2590, p2647).
2: Jog 1 or jog 2 and start referencing (p2589, p2590, p2595).
3: Jog 1 or jog 2 and activate traversing task (p2589, p2590, p2631).
4: Direct setpoint input/MDI and starting referencing (p2647, p2595).
5: Direct setpoint input/MDI and activate traversing task (p2647, p2631).
6: Start referencing and activate traversing task (p2595, p2631).
When starting a traversing block/direct setpoint input, a reference point is

not set (r2684.11 = 0).
A traversing block selected via BI: p2625 to BI: p2630 was started via BI:
p2631 = 0/1 edge "Activate traversing task".
- the number of the started traversing block is not contained in
p2616[0...n].
- the started traversing block is suppressed.
Number of the selected traversing block that is also not available.
For a traversing block with the block change enable

CONTINUE_EXTERNAL_ALARM, the external block change
was not requested.
Number of the traversing block.
There is no subsequent block in the traversing block.

Number of the traversing block with the missing subsequent block.
The same traversing block number was assigned a multiple number of

times.
Number of the traversing block that was assigned a multiple number of
times.
The task parameter in the traversing block contains an illegal value.

Number of the traversing block with an illegal task parameter.
In a traversing block, a jump was programmed to a non-existent block.
Number of the traversing block with a jump destination that does not exist.
In the traversing block the specified absolute target position lies outside
the range limited by the software limit switch
minus.
Number of the traversing block with illegal target position.
In the traversing block the specified absolute target position lies outside
the range limited by the software limit switch
plus.
In the traversing block the target position lies outside the modulo range.
In the traversing block the positioning mode ABS_POS or ABS_NEG were

parameterized with the modulo correction
not activated.
Number of the traversing block with the illegal positioning mode.
When traversing, the axis has moved to the traversing range limit.
When traversing, the axis has moved to the traversing range limit.
In the current traversing operation, the target position is less than the
software limit switch minus.
In the current traversing operation, the target position is greater than the
software limit switch plus.
The axis is at the position of the software limit switch minus. An active
traversing block was interrupted.
The axis is at the position of the software limit switch plus. An active
traversing block was interrupted.
The fixed stop in the traversing block was reached without the clamping
torque/clamping force having been achieved.
In the modes "traversing blocks" or "direct setpoint input/MDI" at the start

of motion, the binector input "no intermediate
stop/intermediate stop" (BI: p2640) did not have a 1 signal.
In the modes "traversing blocks" or "direct setpoint input/MDI" at the start
of motion, the binector input "do not reject
traversing task/reject traversing task" (BI: p2641) does not have a 1 signal.
For the function "flying referencing" the difference between the measured
position at the measuring probe and the
reference point coordinate lies outside the parameterized window.
An activated reference function (reference mark search or measuring probe
evaluation) was interrupted.
- an encoder fault has occurred (Gn_ZSW.15 = 1).
- position actual value was set during an activated reference function.
- simultaneously activate reference mark search and measuring probe
evaluation (BI: p2508 and BI: p2509 = 1 signal).
- activated reference function (reference mark search or measuring probe
evaluation) was de-activated (BI: p2508
and BI: p2509 = 0 signal).
It is not possible to enable the basic positioner because at least one signal
is missing.
1: EPOS enable missing (BI: p2656).
2: Position actual value, valid feedback signal missing (BI: p2658).
The position actual value is set to the value received via CI: p2515while BI:
p2514 = 1 signal. A possible system
deviation cannot be corrected.
When evaluating the measuring probe, an error occurred.
6: The input terminal for the measuring probe is not set.
4098: Error when initializing the measuring probe.
4100: The measuring pulse frequency is too high.
> 50000: The measuring clock cycle is not a multiple integer of the position
controller clock cycle.
A motor data set is not assigned to a drive object.

All of the existing motor data sets in the drive data sets must be assigned
using the MDS number (p0186[0...n]).
There must be at least as many drive data sets as motor data sets.
Number of the motor data set that has not been assigned.
The interface mode "SIMODRIVE 611 universal" was set (p2038 = 1) and
the data structure does not correspond to
this mode.
For the data structure, the following rule must be complied with.
Within the group of 8 drive data sets, the assignment to the motor data set
must be set the same:
p0186[0] = p0186[1] = ... = p0186[7]
p0186[8] = p0186[9] = ... = p0186[15]
p0186[16] = p0186[17] = ... = p0186[23]
p0186[24] = p0186[25] = ... = p0186[31]
See also: p0180 (Number of Drive Data Sets (DDS)), p0186 (Motor Data Sets
(MDS) number), p2038 (PROFIdrive
STW/ZSW interface mode)
With the setting p0833.0 = 1, a motor changeover via the application is

selected. This is the reason that p0827 must
have different values in the appropriate motor data set.
xxxxyyyy:
xxxx: First MDS, yyyy: Second MDS
The motor cannot be changed over.

1:
The contactor for the motor that is presently active cannot be opened,
because for a synchronous motor, the speed
(r0063) is greater than the speed at the start of field weakening (p3048). As
long as r0063 > p0348, the current in
the motor does not decay in spite of the pulses being suppressed.
2:
The "contactor opened" feedback signal was not detected within 1 s.
3:
The "contactor closed" feedback signal was not detected within 1 s.
The selected drive data set is not available (p0837 > p0180). The drive data
set was not changed over.
See also: p0180, p0820, p0821, p0822, p0823, p0824, r0837
The selected drive data set changeover and the assigned motor changeover
are not possible and are not carried out.
For synchronous motors, the motor contactor may only be switched for
actual speeds less than the speed at the start
of field weakening (r0063 < p0348).
See also: r0063 (Actual speed value)
When carrying out a factory setting (e.g. using p0970 = 1), it was not
possible to reset the encoder parameters. The
encoder parameters are directly read out of the encoder via DRIVE-CLiQ.
Component number of the encoder involved.
The reference point coordinate received when adjusting the encoder via
connector input CI:p2599 lies outside the
half of the encoder range and cannot be set as current axis position. The
maximum permissible value is displayed
in the supplementary information.
An encoder error was signaled for encoder 1 via the PROFIdrive encoder
interface (G1_ZSW.15).
Error code from G1_XIST2, refer to the description regarding r0483.
Note:
This alarm is only output if p0480[0] is not equal to zero.
Note:
Note:
During encoder identification (servicing) with p0400 = 10100, the encoder

could not be identified.
Either the wrong encoder has been installed or no encoder has been
installed, the wrong encoder cable has been
connected or no encoder cable has been connected, or the DRIVE-CLiQ
component has not been connected to
DRIVE-CLiQ.
Note:
Encoder identification must be supported by the encoder and is possible in
the following cases:
Encoder with EnDat interface, motor with DRIVE-CLiQ.
Encoderless operation is active due to a fault (r1407.13).

The required response when an encoder fault occurs is parameterized in
p0491.
See also: p0491 (Motor encoder fault response ENCODER)
4200: The PROFIBUS clock cycle is not a multiple of integer of the position

4200: The PROFIBUS clock cycle is not a multiple of integer of the position
During encoder identification (servicing) with p0400 = 10100, the encoder

could not be identified.
Either the wrong encoder has been installed or no encoder has been
installed, the wrong encoder cable has been
connected or no encoder cable has been connected, or the DRIVE-CLiQ
component has not been connected to
DRIVE-CLiQ.
Note:
Encoder identification must be supported by the encoder and is possible in
the following cases:
Encoder with EnDat interface, motor with DRIVE-CLiQ.
A Sensor Module with the component number specified in p0141 was not
found.
Encoder data set involved (index of p0141).
An error has occurred during the position actual value preprocessing.
The following problem has occurred during the position actual value
preprocessing.
- an encoder data set has been assigned, however, the encoder data set
does not contain any encoder data (p0400
= 0) or invalid data (e.g. p0408 = 0).
preprocessing.
preprocessing.
A Drive Data Set changeover (DDS) with a change of the mechanical

relationships and the encoder assignment
(p2502) was requested in operation.
The value range (-2147483648 ... 2147483647) for the position actual value
representation was exceeded.
When the overflow occurs, the "referenced" or "adjustment absolute
measuring system" status is reset.
Fault value (r0949, interpret decimal):
1: The position actual value (r2521) has exceeded the value range.
2: The encoder position actual value Gn_XIST2 (r0483) or the absolute
value after the load gear (r2723) has
exceeded the value range.
3: The maximum encoder value times the factor to convert the absolute
position (r0483 and/or r2723) from increments
to length units (LU) has exceeded the value range for displaying the
position actual value.



Alarm threshold for I2t overload (p0294) of the power unit exceeded.
The response parameterized in p0290 becomes active.
See also: p0290 (Power unit overload response)
The temperature sensor for motor temperature monitoring, specified in

p0600, is not available.
- parameter download with "incorrect" setting.
- module with sensor evaluation has been, in the meantime, been
removed.
- temperature sensor via Motor Module, not for CU310.
The simulation mode is activated.
The drive can only be powered up if the DC link voltage is less than 40 V.
The BICO signal for "external alarm 1" was triggered.

The condition for this external alarm is fulfilled.
See also: p2112 (External alarm 1)
The absolute value of the speed difference from the two setpoints (p2151,
p2154) and the speed actual value (r2169)
exceeds the tolerance threshold (p2163) longer than tolerated (p2164,
p2166).
The alarm is only enabled for p2149.0 = 1.
Possible causes could be:
- the load torque is greater than the torque setpoint.
- when accelerating, the torque/current/power limit is reached. If the limits
are not sufficient, then it is possible that
the drive has been dimensioned too small.
- the speed controller is inhibited (refer to p0856; refer to Kp/Tn adaptation
of the speed controller).
- for closed-loop torque control, the speed setpoint does not track the
speed actual value.
- for active Vdc controller.
- the encoder pulse number was incorrectly parameterized (p0408).
When closing, the contactor feedback signal (p1235) did not issue the
signal "Closed" (r1239.1 = 1) within the monitoring
time (p1236).
The Motor Module signals that the motor is short-circuited through the
power semiconductors (r1239.5 = 1). The
pulses cannot be enabled. The internal armature short-circuit is selected
(p1231 = 4):
KTY:
The motor temperature has exceeded the fault threshold (p0604 or p0616).
VECTOR: The response parameterized in p0610 becomes active.
PTC:
The response threshold of 1650 Ohm was exceeded.
SME not selected in p0601:
1: No output current reduction.
2: Output current reduction active.
SME selected in p0601 (p0601 = 10):
The number specifies the sensor channel that resulted in the alarm being
output.
See also: p0604 (Motor overtemperature alarm threshold), p0610 (Motor
overtemperature response)
Only for separately excited synchronous motors (p0300 = 5):

The current open-loop/closed-loop control mode is I/f control (open-loop)
with a fixed current (p1300 = 18).
The speed is entered via the setpoint channel and the current setpoint is
given by the minimum current (p1620).
It must be ensured that in this mode, the control dynamic performance is
very limited. This is the reason that longer
ramp-up times should be set for the setpoint speed than for normal
operation.
See also: p1620 (Stator current, minimum)
The torque deviates from the torque/speed envelope characteristic in the

positive direction (too high).
The torque deviates from the torque/speed envelope characteristic.
Invalid parameter values were entered for the envelope characteristic of
the load monitoring.
The following rules apply for the speed thresholds:
p2182 < p2183 < p2184
The following rules apply for the torque thresholds:
p2185 > p2186
p2187 > p2188
p2189 > p2190
Number of the parameter with the invalid value.
The motor is braked using DC current - the DC current brake is active.

This alarm is output for r1229.4 = 1.
See also: p1216 (Motor holding brake, opening time), r1229 (Motor holding
brake status word)
This alarm is output for r1229.5 = 1.
For r1229.5 = 1, OFF/OFF3 are suppressed to prevent the drive accelerating
by a load that drives the motor -
whereby OFF2 remains effective.
See also: p1217 (Motor holding brake closing time), r1229 (Motor holding
brake status word)
The target frequency is outside the permissible value range.

1084: Target frequency greater than the positive speed limit, f_sync >
f_max (r1084).
1087: Target frequency less than the negative speed limit, f_sync < f_min
(r1087).
There is a considerable difference between the setpoint frequency and the

target frequency (f_set <> f_target). The
deviation that can be tolerated is set in p3806.
Synchronization is not permitted.

1300: The control mode (p1300) has not been set to encoderless closed-
loop speed control or V/f characteristic.
1910: Motor data identification activated.
1960: Speed controller optimization activated.
1990: Encoder adjustment activated.
3801: Voltage Sensing Module (VSM) not found.
3845: Friction characteristic record activated.
The friction characteristic is incorrect.

1538:
The friction torque is greater than the maximum from the upper effective
torque limit (p1538) and zero. This is the
reason that the output of the friction characteristic (r3841) is limited to this
value.
The automatic friction characteristic record is activated.
The friction characteristic is recorded at the next power-on command.
The automatic determination of the angular commutation offset (encoder

adjustment) is activated (p1990 = 1).
The automatic determination is carried out with the next power-on
command.
For SERVO and fault F07414 present, the following applies:
The determination of the angular commutation offset is automatically
activated (p1990 = 1), if a pole position identification
technique is set in p1980.
See also: p1990 (Encoder adjustment, determine angular commutation
offset)
The rotating measurement (automatic speed controller optimization) is

activated.
The rotating measurement is carried out at the next power-on command.
See also: p1960 (Rotating measurement selection)
The rotating measurement cannot be started due to missing enable signals.
No encoder available. The rotating measurement was carried out without

encoder.
The motor data ident. routine is activated.
The motor data identification routine is carried out at the next power-on
command.
See also: p1910 (Motor data identification selection)
The cyclic actual and/or setpoint values were not transferred within the
specified times.
The drive unit did not accept the receive configuration data.
Return value of the receive configuration data check.
0: Configuration accepted.
1: Connection established to more drive objects than configured in the
device. The drive objects for process data
exchange and their sequence were defined using p0978.
2: Too many data words for input or output to a drive object. A max. of 16
words is permitted for SERVO and VECTOR;
a max. of 5 words for A_INF, TB30, TM31 and CU320.
3: Uneven number of bytes for input or output.
4: Setting data for synchronization not accepted.
5: Drive still not in cyclic operation.
6: Buffer system not accepted.
7: Cyclic channel length too short for this setting.
8: Cyclic channel address not initialized.
9: 3-buffer system not permitted.
10: DRIVE-CLiQ fault.
11: CU-Link fault.
12: CX32 not in cyclic operation.
The memory or the buffer status of the non-cyclic channel has an error.
0: Error in the buffer status.
1: Error in the memory.
There is no cyclic connection to the control.
The memory or the buffer status of the message channel has an error.
0: Error in the buffer status.
1: Error in the memory.
The assignment of the hardware to the PZD interface has been incorrectly
parameterized.
1: Only one of the two indices is not equal to 99 (automatic).
2: Both PZD interfaces are assigned to the same hardware.
3: Assigned COMM BOARD missing.
4: CBC10 is assigned to interface 1.
See also: p8839 (PZD interface hardware assignment)
The error counter for the send or receive telegrams has exceeded the value
127.
The error counter for the send or receive telegrams has exceeded the value
127.
A message buffer overflow.
1: Non-cyclic send buffer (SDO response buffer) overflow.
2: Non-cyclic receive buffer (SDO receive buffer) overflow.
3: Cyclic send buffer (PDO send buffer) overflow.
In the "operational" mode, an attempt was made to change parameters

p8700 ... p8737.
The CANopen object is not provided for the Process Data Object (PDO)
Mapping.
The number of bytes of the mapped objects exceeds the telegram size for
net data. A max. of 8 bytes is permissible.
For online operation, the appropriate COB-ID must be set invalid before
mapping.
Example:
Mapping for RPDO 1 should be changed (p8710[0]).
--> set p8700[0] = C00006E0 hex (invalid COB-ID)
--> set p8710[0] as required.
--> p8700[0] enter a valid COB-ID
The number of PDO channels in p8740 has either been set to 0 or too low.
See also: p8740 (CBC channel assignment)
An existing PDO COB-ID was allocated.

- for the drive unit, the options that require a license are being used but the
licenses are not sufficient.
- an error occurred when checking the existing licenses.
0:
The existing license is not sufficient.
1:
An adequate license was not able to be determined as the memory card
with the required licensing data was withdrawn
in operation.
2:
An adequate license was not able to be determined, as an error occurred
when reading-out the required licensing
data from the memory card.
3:
An adequate license was not able to be determined as there is a checksum
error in the license key.
4:
An internal error occurred when checking the license.
When checking the checksum of the license key, an error was detected.
A DRIVE-CLiQ communication error has occurred between the Control Unit

and the power unit involved.
The cyclic setpoint telegrams of the Control Unit were not received on time
by the power unit for at least one clock
cycle.
The following applies for CU31x and CUA31:

The DC link voltage is too low.
DC link voltage in [V].
The temperature difference between the heat sink and chip has exceeded
the permissible limit value.
- the permissible load duty cycle was not maintained.
- insufficient cooling, fan failure.
- overload.
- ambient temperature too high.
- pulse frequency too high.
See also: r0037
Hardware current limit for phase U responded. The pulsing in this phase is
inhibited for one pulse period.
- closed-loop control is incorrectly parameterized.
- fault in the motor or in the power cables.
- the power cables exceed the maximum permissible length.
- motor load too high
- power unit defective.
Note:
Alarm A30031 is always output if the hardware current limit for phase U, V
or W on a Power Module responds.
Hardware current limit for phase V responded. The pulsing in this phase is
Note:
Hardware current limit for phase W responded. The pulsing in this phase is
Note:
24 V power supply fault for the power unit.

- the 16 V threshold was undershot..
24 V voltage [1 bit = 0.1 V].
The maximum operating time of the fan in the power unit is set in p0252.
This message indicates the following:
0: The maximum fan operating time is 500 hours.
1: The maximum fan operating time has been exceeded.
The following applies for CU31x:

24 V power supply fault for the power unit.
- the 32.0 V threshold was exceeded.
Fault value (r0949):
Before the last new start, a problem occurred at the power unit power
supply.
- the voltage monitoring in the internal FPGA of the PSA signals an
undervoltage fault on the module.
Register value of the voltage fault register.

Communications to the power unit module are no longer in synchronism
with DRIVE-CLiQ.
CRC error actuator
When booting it was detected that the cause of the previous reset was an
SAC watchdog timer overflow.
When evaluating the temperature sensor, an error occurred.
1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm, PT100: R >
375 Ohm).
2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm, PT100:
R < 30 Ohm).
An alarm occurred on the power unit that cannot be interpreted by the

Control Unit firmware.
This can occur if the firmware on this component is more recent than the
firmware on the Control Unit.
Alarm number.
Note:
If required, the significance of this new alarm can be read about in a more
recent description of the Control Unit.
The measured zero mark distance does not correspond to the

parameterized zero mark distance.
For distance-coded encoders, the zero mark distance is determined from
zero marks detected pairs. This means that
if a zero mark is missing, depending on the pair generation, this cannot
result in a fault and also has no effect in the
system.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary
encoder) or p0424 (linear encoder).
Last measured zero mark distance in increments (4 increments = 1 encoder
pulse).
The sign designates the direction of motion when detecting the zero mark
distance.
The 1.5 x parameterized zero mark distance was exceeded.

Number of increments after POWER ON or since the last zero mark that
was detected (4 increments = 1 encoder
pulse).
Serial communication protocol transfer error between the encoder and
evaluation module.
Bit 0: Alarm bit in the position protocol.
Bit 1: Incorrect quiescent level on the data line.
Bit 2: Encoder does not respond (does not supply a start bit within 50 ms).
Bit 3: CRC error: The checksum in the protocol from the encoder does not
match the data.
Bit 4: Encoder acknowledgement error: The encoder incorrectly understood
the task (request) or cannot execute it.
Bit 5: Internal error in the serial driver: An illegal mode command was
requested.
Bit 6: Timeout when cyclically reading.
Bit 8: Protocol is too long (e.g. > 64 bits).
Bit 9: Receive buffer overflow.
Bit 10: Frame error when reading twice.
Bit 11: Parity error.
Bit 12: Data line signal level error during the monoflop time.
The error word of the EnDat encoder has alarm bits that have been set.
Bit 0: Frequency exceeded (speed too high).
Bit 1: Temperature exceeded.
Bit 2: Control reserve, lighting system exceeded.
Bit 3: Battery discharged.
Bit 4: Reference point passed.
The encoder sends a set error bit via the serial protocol.
Bit 0: Fault bit in the position protocol.
The amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall
signals, is not within the tolerance bandwidth.
yyyyxxxx hex:
yyyy = Signal level, track D (16 bits with sign).
xxxx = Signal level, track C (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600
mV (500 mV -25/+20 %).
The response thresholds are < 230 mV (observe the frequency response of
the encoder) and > 750 mV.
A signal level of 500 mV peak value corresponds to the numerical value
5333 hex = 21299 dec.
Note:
If the amplitude is not within the tolerance bandwidth, then it cannot be
used to initialize the start position.
For an HTL/TTL encoder, the speed difference between two sampling cycles
has exceeded the value in p0492.
The change to the averaged speed actual value - if applicable - is monitored
in the current controller sampling time.
See also: p0492 (Square-wave encoder, maximum speed difference per
sampling cycle)
The amplitude, phase or offset correction for track A or B is at the limit.

Amplitude error correction: Amplitude B / Amplitude A = 0.78 ... 1.27
Phase: <84 degrees or >96 degrees
SMC20: Offset correction: +/-140 mV
xxxx1: Minimum of the offset correction, track B
xxxx2: Maximum of the offset correction, track B
xxx1x: Minimum of the offset correction, track A
xxx2x: Maximum of the offset correction, track A
xx1xx: Minimum of the amplitude correction, track B/A
xx2xx: Maximum of the amplitude correction, track B/A
x1xxx: Minimum of the phase error correction
x2xxx: Maximum of the phase error correction
1xxxx: Minimum of the cubic correction
2xxxx: Maximum of the cubic correction
For the actual value sensing, an error was detected. As a result of this error,
it must be assumed that the actual value
sensing supplies an incorrect coarse position.
3: The absolute position of the serial protocol and track A/B differ by half
an encoder pulse. The absolute position
must have its zero position in the quadrants in which both tracks are
negative. In the case of a fault, the position can
be incorrect by one encoder pulse.
The error for track C/D is greater than +/-15 ° mechanical or +/-60 °
electrical or the error for the Hall signals is greater
than +/-60 ° electrical.
One period of track C/D corresponds to 360 ° mechanical.
One period of the Hall signal corresponds to 360 ° electrical.
The monitoring responds if, for example, Hall sensors are connected as
equivalent for the C/D tracks with the incorrect
rotational sense or supply values that are not accurate enough.
For track C/D, the following applies:
Measured deviation as mechanical angle (16 bits with sign, 182 dec
corresponds to 1 °).
For Hall signals, the following applies:
Measured deviation as electrical angle (16 bits with sign, 182 dec
When the zero pulse is passed, a deviation in the incremental position was
detected.
For equidistant zero marks, the following applies:
- The first zero mark passed supplies the reference point for all subsequent
checks. The other zero marks must have
n times the distance referred to the first zero mark.
For distance-coded zero marks, the following applies:
- the first zero mark pair supplies the reference point for all subsequent
checks. The other zero mark pairs must have
the expected distance to the first zero mark pair.
Deviation in quadrants (1 pulse = 4 quadrants).
For track A/B, pulses have been lost or too many have been counted. These
pulses are presently being corrected.
Alarm value (r2124, interpret decimal): Last measured deviation of the zero
mark distance in increments (4 increments
= 1 encoder pulse). The sign designates the direction of motion when
detecting the zero mark distance.
The unipolar level (CP/CN or DP/DN) for encoder 1 is outside the

permissible tolerance.
Bit 0 = 1: Either CP or CN outside the tolerance.
Bit 16 = 1: Either DP or DN outside the tolerance.
The unipolar nominal signal level of the encoder must lie in the range 2500
mV +/- 500 mV.
The response thresholds are < 1700 mV and > 3300 mV.
Note:
The signal level is not evaluated unless the following conditions are
satisfied:
- Sensor Module properties available (r0459.31 = 1).
- Monitoring active (p0437.31 = 1).
The serial number of the motor encoder of a synchronous motor has
changed. The change was only checked for
encoders with serial number (e.g. EnDat encoders) and build-in motors (e.g.
p0300 = 401) or third-party motors
(p0300 = 2).
Cause 1:
The encoder was replaced.
Cause 2:
A third-party, build-in or linear motor was re-commissioned.
Cause 3:
The motor with integrated and adjusted encoder was replaced.
Cause 4:
The firmware was updated to a version that checks the encoder serial
number.
Note:
With closed-loop position control, the serial number is accepted when
starting the adjustment (p2507 = 2).
When the encoder is adjusted (p2507 = 3), the serial number is checked for
changes and if required, the adjustment
is reset (p2507 = 1).
Error when operating the internal SPI bus.

Error when operating the internal I2C bus.
The configuration for encoder 1 is incorrect.
1: Re-parameterization between fault/alarm is not permissible.
Low word low byte: Cause:
1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm).
2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).
Additional values:
Low word high byte: Channel number.
A alarm has occurred on the Sensor Module for encoder 1 that cannot be
interpreted by the Control Unit firmware.
Alarm number.
Note:
system.
pulse).
distance.

pulse).

evaluation module.
match the data.
yyyyxxxx hex:
mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
Note:
sampling cycle)

detected.

mV +/- 500 mV.
Note:
satisfied:
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Bit x = 1: Effectivity test x unsuccessful.
Additional values:
A alarm has occurred on the Sensor Module for encoder 2 that cannot be
Alarm number.
Note:

system.
pulse).
distance.

pulse).
evaluation module.
match the data.
requested.
yyyyxxxx hex:
mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
Note:
sampling cycle)

detected.

mV +/- 500 mV.
Note:
satisfied:
Bit x = 1: Effectivity test x unsuccessful.

Additional values:
A alarm has occurred on the Sensor Module for encoder 3 that cannoy be
interpreted by the Control Unit Firmware. This can occur if the firmware on
this component is more recent than the firmware on the Control Unit.
Alarm number.
Note:
The temperature (r3666) measured using the Voltage Sensing Module

(VSM) has exceeded the threshold value
(p3667).
The hundred thousands and ten thousands position specifies the
component number of the VSM where the fault
occurred.
Error, timeout in the sequence control on the Voltage Sensing Module

(VSM).
An error has occurred in while accessing via the internal TM I2C bus.
An error has occurred accessing the non-volatile memory on the Terminal
Module.
The Control Unit attempted to write an illegal parameter value to the
Voltage Sensing Module (VSM).

A fault occurred on the Voltage Sensing Module (VSM) an alarm has

occurred that cannot be interpreted by the Control
Unit firmware.
Alarm number.
Note:
The test stop for the Terminal Module 54F (TM54F) is presently being
executed.
F35013 is output when a error occurs during the test stop.
- after powering up the drive, a test stop has still not been carried out.
- a new test stop is required after commissioning.
- the time to carry out the forced checking procedure (test stop) has
expired (p10003).E339
Cyclic communication of one or several drives with the Terminal Module

54F (TM54F) is not active.
Bit 0 = 1: No communication with drive 1.
...
Bit 5 = 1: No communication with drive 6.
For fault value = 0, the following applies:
The number of drive objects specified in p10010 is not equal to the number
of drives that have drive-based motion
monitoring functions that have been enabled.
The drive object number for drive n is set in p10010[n-1].
When this fault is present, none of the drives that have drive-based motion
monitoring functions operating with
TM54F, are enabled.
The cyclic net data communication within the Terminal Module 54F
(TM54F) is still not active.
This message is output after the TM54F master and TM54F slave have
booted and is automatically withdrawn as
soon as communications have been established.
a drive does not communicate with the TM54F, then none of the drives
parameterized in p10010 are enabled.
0x99: Action: All master-DOs at OFF - error: State of DI 20...23 of the slave
does not correspond to the expected
state (0V) or the slave not in state 0x8E.
0xA4: Action: All master DOs at OFF - error: Slave not in state 0x99.
0xAF: Action: All master-DOs at OFF - error: Status of DI 20...23 of the slave
does not correspond to the expected
state (24V) or the slave not in state 0xA4.
0xBA: Action: All master DOs at the original state - error: Slave not in state
0xAF.
0xC5: Action: All master DOs at the original state - error: Slave not in state
0xBA.
0xD0: Wait for the end of the test stop and return to the start state
Note: A check of the switching state of the F-DIs and DIs always refers to
the switching operation of the previous
state. The actions in one state are always only carried out after the actual
state has been checked.
The temperature measured using the temperature sensing on the TM54F

has exceeded the threshold value to initiate
this alarm.
An internal communications error has occurred in the Terminal Module 54F
(TM54F).
This alarm can also occur if the TM54F exists and no safety function has yet
been parameterized.
Only for internal Siemens diagnostics.
The calculated checksum entered in r10004 over the safety-relevant

parameters does not match the reference
checksum saved in p10005 at the last machine acceptance.
1: Checksum error for functional SI parameters.
2: Checksum error for SI parameters for component assignment.
A logical "1" signal is present at the F-DI configured in p10006 for more
than 10 seconds. A logical "0" signal must
be statically applied at the F-DI. This prevents the output of an unintended
safe acknowledgement signal (or the
"Internal Event Acknowledge" signal) if a wire break occurs or one of the
two digital inputs bounces.
An error was detected in the calibration data of the Terminal Module.

The hundred thousands and ten thousands location specifies the
component Id of the Terminal Module where the
fault occurred.
The thousands location specifies whether the analog input 0 (=0) or analog
output 1 (= 1) is involved.
The hundreds location specifies the fault type:
0: No calibration data available.
1: Offset too high (> 100 mV).
The tens and ones location specifies the number of the input involved.
The temperature measured using the temperature sensing of the Terminal

Module (TM) (r4105) has exceeded the
threshold value to initiate this alarm (p4102[0]).
component number of the TMxx where the fault
occurred.
The encoder pulse number entered does not match the permissible pulse
number from a hardware perspective.
1: Encoder pulse number is too high.
2: Encoder pulse number is too low.
4: Encoder pulse number is less than the zero mark offset (p4426).
The entered zero mark offset is not permissible.

1: Zero mark offset is too high.
A DRIVE-CLiQ communication error has occurred from the Terminal Module
to the encoder involved.
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex:
The sign-of-life bit in the receive telegram is not set.
Time slice overflow on Terminal Module.

NONE
NONE
An error has occurred during the memory test on the Terminal Module.
A checksum error has occurred when reading-out the program memory on
the Terminal Module.
Difference between the checksum at POWER ON and the current
checksum.
Internal parameter data is corrupted.

01: EEPROM access error.
02: Too many blocks in the EEPROM.
Error, timeout, sequence control on the Terminal Module.

An error has occurred while accessing the internal I2C bus of the Terminal
Module.
An error has occurred accessing the non-volatile memory on the Terminal
Module.
The Control Unit attempted to write an illegal parameter value to the
Terminal Module.
The 24 V power supply for the digital outputs is missing.

01: TM17 24 V power supply for DI/DO 0 ... 7 missing.
04: TM15 24 V power supply for DI/DO 0 ... 7 (X520) missing.
The Terminal Module was not successfully initialized.

01: TM17 or TM41 - incorrect configuration request.
02: TM17 or TM41 - programming not successful.
04: TM17 or TM41 - invalid time stamp
The temperature in the module has exceeded the highest permissible limit.
The maximum permissible number of errors in the master sign-of-life (clock
synchronous operation) has been
exceeded in cyclic operation.
When the alarm is output, the module outputs are reset up to the next
synchronization.

An alarm has occurred on the Terminal Module that cannot be interpreted

by the Control Unit firmware.
Alarm number.
Note:
24 V power supply on DRIVE-CLiQ Hub Module has undershot alarm

threshold.
Current operating voltage in 0.1 °C resolution.
DRIVE-CLiQ communication error from Control Unit to DRIVE-CLiQ Hub

Module in question.
xx = 0A hex = 10 dec:
A checksum error (CRC) occurred when the program memory on the DRIVE-
CLiQ Hub Module was read out.
Difference between the checksum at POWER ON and the current
checksum.
The internal parameter data on the DRIVE-CLiQ Hub Module are incorrect.
An alarm occurred on the DRIVE-CLiQ Hub Module that cannot be

Alarm number.
Note:
An alarm has occurred at the drive object at the DRIVE-CLiQ socket X100.
First alarm that has occurred for this drive object.
The cooling system signals a general alarm.
The conductivity monitoring of the cooling liquid is set (r0267 bit 7, from
p0266 index 7).
See also: p0261 (Cooling system, starting time 2), p0262 (Cooling system,
fault conductivity delay time), p0266
(Cooling system, feedback signals, signal source), r0267 (Cooling system
status word)
When monitoring the conductivity of the cooling liquid, there is a fault in

the wiring or in the sensor.
The cooling liquid intake temperature has exceeded the specified alarm
threshold.
The "excitation group signal alarm" signal is present.
CBE20: A PROFINET controller attempts to establish a connection using an
incorrect configuring telegram. The
PROFINET version (V2.1/V2.2) of the project (HW Config) is not compatible
with the CBE20 firmware.
The axis configuration was changed (e.g. changeover between linear axis
and rotary axis).
Parameter p0108.13 is internally set to the correct value.
Note:
This fault does not result in a safety stop response.
Parame
The drive is stopped via a STOP A (pulses are suppressed via the safety
shutdown path of the Control Unit).
Possible causes:
- stop request from the higher-level control.
- pulses not suppressed after a parameterized time (p9557) after test stop
selection
The drive is stopped via STOP B (braking along the OFF3 deceleration
ramp).
As a result of this fault, after the time parameterized in p9556 has expired,
or the speed threshold parameterized in
p9560 has been undershot, message C01700 "STOP A initiated" i
After initiating STOP B or STOP C, the velocity has exceeded the selected
tolerance.
The drive is shut down by the message C01700 "SI Motion: STOP A
initiated".
The actual position has distanced itself further from the target position
than the standstill tolerance.
The drive is shut down by the message C01701 "SI Motion: STOP B
initiated".
The drive is stopped via STOP C (braking along the OFF3 deceleration
ramp).
"Safe Operating Stop" (SOS) is activated after the parameterized timer has
expired.
Possible causes:
- subsequent response to the mes
The drive is stopped via a STOP D (braking along the path).

expired.
Possible causes:
- subsequent response to the message C01714 "SI
The drive is stopped via a STOP E (retraction motion).

expired.
Possible causes:
- subsequent response to the message C01714 "SI Motio
When cross-checking and comparing the two monitoring channels, the

drive detected a difference between the input
data or results of the monitoring functions and initiated a STOP F. One of
the monitoring functions no longer reliably
functions - i.e. safe o
The drive has moved faster than that specified by the velocity limit value
(p9531). The drive is stopped as a result of
the configured stop response (p9563).
Message value (r9749, interpret decimal):
100: SLS1 exceeded.
200: SLS2 exceeded.
300: SLS3 excee
The normalization of the brake torque for the brake test can be changed
using parameter p2003.
An acceptance test must be carried out again for the braking test. This
determines whether the braking test is still
carried out with the correct braking torque
The encoder that is used for the safety-relevant motion monitoring

functions signals a hardware fault.
Encoder status word 1, encoder status word 2 that resulted in the message.
The DQ encoder used for the safety-relevant motion monitoring functions

signals an effectiveness test error.
1 - TFD bit in EncoderStatusWord2 set in last effectiveness test set
2 - Actual effectiveness test no. i
The test stop is active.
The acceptance test mode is active. The POWER ON signals of the safety-
relevant motion monitoring functions can
be acknowledged during the acceptance test using the RESET button of the
higher-level control.
The parameter value cannot be parameterized with this value.

Note:
Parameter number with the incorrect value.
The drive is stopped via a STOP A (pulses are suppressed via the safety
shutdown path of the Control Unit).
Possible causes:
- stop request from the Control Unit.
- pulses not suppressed after a parameterized time (p9357) after test stop
selection.
- subsequent response to the message C30706 "SI Motion MM: Safe
Acceleration Monitoring, limit exceeded".
- subsequent response to the message C30714 "SI Motion MM: Safely-
Limited Speed exceeded".
- subsequent response to the message C30701 "SI Motion MM: STOP B
initiated".
The drive is stopped via a STOP B (braking along the OFF3 ramp).
As a result of this fault, after the time parameterized in p9356 has expired,
or the speed threshold parameterized in
p9360 has been undershot, message C30700 "SI Motion MM: STOP A
initiated" is output.
Possible causes:
- subsequent response to the message C30714 "SI Motion MM: Safely
limited speed exceeded".
- subsequent response to the message C30711 "SI Motion MM: Defect in a
monitoring channel".
After initiating STOP B or STOP C, the velocity has exceeded the selected
tolerance.
The drive is shut down by the message C30700 "SI Motion MM: STOP A
initiated".
The actual position has distanced itself further from the target position
than the standstill tolerance.
The drive is shut down by the message C30701 "SI Motion MM: STOP B
initiated".
The drive is stopped via a STOP C (braking along the OFF3 ramp).
expired.
Possible causes:
- subsequent response to the message C30714 "SI Motion MM: Safely
limited speed exceeded".
See also: p9552 (SI Motion transition time STOP C to SOS (SBH) (Control
Unit))
The drive is stopped via a STOP D (braking along the path).

expired.
Possible causes:
- subsequent response to the message C30714 "SI Motion: Safely limited
speed exceeded".
See also: p9353 (SI Motion transition time STOP D to SOS (Motor Module)),
p9553 (SI Motion transition time STOP
D to SOS (SBH) (Control Unit))
When cross-checking and comparing the two monitoring channels, the

drive detected a difference between the input
data or results of the monitoring functions and initiated a STOP F. One of
the monitoring functions no longer reliably
functions - i.e. safe operation is no longer possible.
If at least one monitoring function is active, then after the parameterized
timer has expired, the message C30701 "SI
Motion: STOP B initiated" is output. The message is output with message
value 1031 when the Sensor Module hardware
is replaced.
0 ... 999: Number of the cross-checked data that resulted in this message.
Refer to safety message C01711for a
description of the individual data.
The significance of the individual message values is described in safety
message C01711 of the Control Unit.
1000: Watchdog timer has expired. Too many signal changes have occurred
at safety-relevant inputs.
1001: Initialization error of watchdog timer.
1005: Pulses already suppressed for test stop selection.
1011: Acceptance test status between the monitoring channels differ.
1012: Plausibility violation of the actual value from the encoder.
1020: Cyc. communication failure between the monit. cycles.
1021: Cyc. communication failure between the monit. channel and Sensor
Module.
1023: Error during the effectivity test in the Sensor Module.
1030: Encoder fault detected from another monitoring channel.
1031: Data transfer error between the monitoring channel and the Sensor
Module.
5000 ... 5140: PROFIsafe message values.
6000 ... 6166: PROFIsafe message values (PROFIsafe driver for PROFIBUS
DP V1/V2 and PROFINET).
See also: p9555 (SI Motion transition time STOP F to STOP B (Control Unit)),
The drive had moved faster than that specified by the velocity limit value
(p9331). The drive is stopped as a result of
the configured stop response (p9363).
100: SLS1 exceeded.
200: SLS2 exceeded.
300: SLS3 exceeded.
400: SLS4 exceeded.
1000: Encoder limit frequency exceeded.
The test stop is active.
The acceptance test mode is active. The POWER ON signals of the safety-
relevant motion monitoring functions can
be acknowledged during the acceptance test using the acknowledgement
functions of the higher-level control.
An internal software error has occurred. Check fault value (r0949.

hexadecimal)

hexadecimal)

hexadecimal)
A memory area was accessed that does not return a "READY".

Faule value (r949, hexadecimal)
Firmware was not able to be downloaded into a DRIVE-CLiQ component.
xxyyyy hex: xx=component number, yyyy = cause of the fault
Cause of the fault (Decimal):
011: DRIVE-CliQ component has detected a checksum error
015: The selected DRI
An unknown drive type was found.

Fault value (r0949, decimal).
Drive object number
An internal software error has occurred. Check fault value (r0949. decimal)
For active PC master control, no sign-of-life was received within the

monitoring time. The master control was returned to the active BICO
interconnection.
When downloading the device parameterization, a file associate with a
drive object cannot be found. Neither a Psxxxyyy.ACX, a Psxxxyyy.NEW nor
a Psxxxyyy.BAK exists on the CompactFlash card for this drive object. Fault
value (r0949, hexadecimal)
The re-naming after saving a parameter -save file on the CompactFlash card
was unsuccessful. One of the files to be re-named had the "read only"
attribute. The parameter-save files are saved on the CompactFlash card in
the directory \USER\SINAMICS\DATA.
I
Writing to at least one parameter back up file Psxxxyyy.acx on the

CompactFlash card was unsuccessful.
- on the CompactFlash card in the directory /USER/SINAMICS/DATA at least
one parameter back up file has the "read only" file attribute and cannot be
sav
A parameter was changed in the drive system that means that it is

necessary to save the parameters and run-up again. (Eg. P0110)
Defective or missing files were detected on the CompactFlash card at run
up.
Fault value (r0949, decimal)
- 1: Source file cannot be opened
- 2: Source file cannot be read
- 3: Target directory cannot be set-up
- 4: Target file cannot be set up / opened
-
An error was detected when downloading a project using the

commissioning (startup) software (eg incorrect parameter value)
For the specified parameter, it was detected that dynamic limits were
exceeded that could possibly depend on the other paramters. Se
A fatal error was detected when downloading a project using the

commissioning (startup) software (eg incorrect parameter value)
See fault value (r0949, decimal), and refer to List Manual Sinamics G, page
589 for more info)
An error was detected when loading the message descriptions

(Fdxxxyyy.ACX) saved on the CompactFlash card.
Only for internal Siemens troubkeshooting
The CompactFlash card and the device type do not match (eg. A
CompactFlash card for SINAMICS is inserted in SINAMICS G).
The drive object type in conjuction with the selected application-specific
perspective is not available. The required descriptive file (Pdxxxyyy.ACX)
does not exist on the CompactFlash card.
Fault valur (r0949, decimal):
Index of P0103 and P0107. See also
Two many functions, data sets or drives configured on this Control Unit.
Fault value (r0949, decimal): Only for Internal Siemens troubleshooting
A data save on the CompactFlash card was not able to be successfully
carried-out.
- CompactFlash card is defective
- CompactFlash card does not have sufficient memory space
Fault Value (r0949, decimal):
-1: The file on the RAM was not able to be opened
-2
More than one SINAMICS G pwer module type is being operated drom the
Control Unit.
Number of the second drive with a SINAMICS G power module type
SINAMICS S and G drive units are being operated together on one Control
Unit.
Number of the first drive object with a different power module type.
An internal software error has occurred when initializing the terminal

functions on the CU3xx, the TB30 or the TM31.
Fault value (r0949, hexadecimal): Only for internal Siemens troubleshooting
The frequency of the pulses at the measuring probe input is too high.
Fault value (r0949, decimal):
1: DI/DO 9 (X122.8)
2: DI/DO 10 (X122.10)
4: DI/DO 11 (X122.11)
8: DI/DO 13 (X132.8)
16: DI/DO 14 (X132.10)
32: DI/DO 15 (X132.11)
1001: DI/DO 9 (X122.8) i
The maximum permissable number of instances of a drive object type was

exceeded.
Byte 1: Drive object type (p0107)
Byte 2: Max. permissible number of instances for this drive object type
Byte 3: Actual number of instances for
Insufficient processing time is available for the existing topology.

Fault value (r0949, hexadecimal). Only for internal Siemens troubleshooting
The parameter to select the basic clock cycle does not match the drive
topology. Drives connected to the same DRIVE-CLiQ port of the Control
Unit have been assigned different basic clock cycles.
The fault value speficies the
The parameter for the basic clock cycle is set too short for the number of
connected drives.
The fault specifies the parameter involved. See also P0110
The closed -loop control / monitoring cannot maintain the intended clock
cyle.
The runtime of the closed-loop control/monitoring is too long for the
particular clock cycle or the computation time remaining in the system is
not sufficient for the closed-lo
Errror when reading the read-only data of the EEPROM in the Control Unit.
Fault value (r0949, decimal): Only for internal Siemens troubleshooting
Error when reading the read-only data of the EEPROM in the option
module.
Fault Value (r0949, decimal): Internal Siemens troubleshooting
A function requested by the Control Unit is not supported by a DRIVE-CLiQ
component.
Fault Value (r0949, decimal)
1: A component does not support the de-activation
101: The Motor Module does not support an internal armature short-
circuit.
102: The Motor M
The component number from the topology was not parameterized (p0121
(for power module, refer to P0107), P0131. (for Servo / vector drives, refer
to p0107), p0141, p0151, p0161)
The fault value includes the particular data set
For the selected communications clock cycle, too many DRIVE-CLiQ

components are connected to one line of the
Control Unit.
xyy hex: x = fault cause, yy = component number or connection number.
1yy:
The communica
The actual topology indicates at least one illegal component.

yyxx hex: yy = component number, xx = cause.
xx = 1: Component at this Control Unit not permissible.
xx = 2: Component in combination with another co
The device target topology (p0099) does not correspond to the device
actual topology (r0098).
The fault only occurs if the topology was commissioned using the
automatic internal device mechanism and not using
the commissioning software.
Fault value (r0949
The detected actual topology is not permissible.
ccccbbaa hex: cccc = preliminary component number, aa = fault cause
aa = 01 hex = 1 dec:
Too many components were detected at the Control Unit. The maximum
permis
When detecting the actual topology, a ring-type connection was detected.

ccbbaaaa hex:
cc = connection number
aaaa = preliminary component number of a component included in the ring
Componen
When detecting the actual topology, a component with a defective

EEPROM was detected.
bbbbaaaa hex:
aaaa = preliminary component number of the defective components
An error was detected in the target topology.

The target topology is invalid.
ccccbbaa hex: cccc = index error, bb = component number, aa = fault cause
aa = 1B hex = 27 dec: Error not specified.
aa = 1C hex = 28
A ring-type connection was detected when writing to the target topology.

ddccbbaa hex:
cc = connection number
aa = component number of a component included in the ring
Note:
Component class
When writing the target topology, a duplicate connection between two

components was detected.
ddccbbaa hex:
dd = connection number 2 of the duplicate connection
cc = connection number 1 of the duplicate connecti
A PROFIdrive telegram has been set (p0922).

An interconnection contained in the telegram was not able to be
established.
Parameter receiver that should be changed.
The standard telegram in p0922 is not maintained and therefore p0922 is
set to 999.
BICO parameter for which the write attempt was unsuccessful.
There are BICO as signal drain from a drive object that is either inactive/not
operational.
The BI/CI parameters involved are listed in R9498. The associateed BO/CO
parameters in R9499.
The list of the BICO interconnections to other drive objects is displayed in
r9491 and r9492 of the de activated drive object.
Note:
r9499 are only written into if, p495 is not set to 0.
Alarm value (r2124 decimal):
Number of BICO interconnections found to be inactive drive objects.
See also : r9491, r9492, 9498, r9499
The requested connector output does not have the correct data type. This
interconnection is not established.
Parameter number to which an interconnection should be made
(connector output).
The requested interconnection was established. However, a conversion is

made between the BICO output and BICO
input using the reference values.
- the BICO output has different normalized units than the BICO input.
- message only for interconnections withi
An attempt was made to determine a conversion factor for a normalization

that does not exist.
Unit (e.g. corresponding to SPEED) for which an attempt was made to
determine a factor.
The requested interconnection was established. However, a conversion is

made between the BICO output and BICO
input using the reference values.
An interconnection is made between different drive objects and the BICO
output has different normalized units t
While changing the number of CDS or when copying from CDS, the master
control was active.
The drive-based "Safety Integrated" function in the Control Unit (CU) has
detected a fault and initiated a STOP A
(pulse suppression via the safety shutdown path of the Control Unit).
- forced checking procedure of the safety shutdown path of the Control
detected a fault in the data cross-check
between the CU and Motor Module (MM) and initiated a STOP F.
As a result of this fault, after the parameterized transition has expired
(p965
The drive-based "Safety Integrated" function on the Control Unit (CU) has
identified different states of the AND'ed
STO inputs for power units connected in parallel and has initiated a STOP F.
As a result of this fault, after the parameterized transition
detected an error in the sign-of-life of the
safety data between the CU and Motor Module (MM) and initiated a STOP
A.
- there is either a DRIVE-CLiQ communication error or communica
detected a brake control error and initiated
a STOP A.
10, 11:
Fault in "open holding brake" operation.
- Parameter p1278 incorrectly set.
-
An internal error in the Safety Integrated software on the Control Unit has
occurred.
Note:
This fault results in a STOP A that cannot be acknowledged.
The drive-based "Safety Integrated" function in the Control Unit requires

an acceptance test.
Note:
This fault results in a STOP A that can be acknowledged.
130: Safety parameters for the Motor Module not available.
The "Safety Integrated" function requires a synchronization of the safety

time slices between the Control Unit (CU)
and Motor Module (MM) and between the Control Unit and the higher-
level control. This synchronization routine was
unsuccessful.
Note:
This
One of the Safety Integrated monitoring clock cycles is not permissible:
- the drive-based monitoring clock cycle cannot be maintained due to the
communication conditions required in the
system.
- the monitoring clock cycle for safe motion monitoring func
There is a PROFIBUS configuration error for using Safety Integrated

monitoring functions with a higher-level control
(SINUMERIK or F-PLC).
Note:
For safety functions that have been enabled, this fault results in a STOP A
that cannot be acknowledged.
Fault
An error has occurred when aligning the Safety Integrated monitoring

functions on the Control Unit (CU) and Motor
Module (MM). Control Unit and Motor Module were not able to determine
a common set of supported SI monitoring
functions.
- there is either a
When accessing the Safety Integrated parameters for the Motor Module
(MM) on the CompactFlash card, an error
has occurred.
Note:
129: Safety parameters for th
The write request for one or several Safety Integrated parameters on the
Control Unit (CU) was rejected.
Note:
1: The Safety Integrated password is not set.
2: A
The Motor Module (MM) does not support the safety-related functions
(e.g. the Motor Module version is not the correct
one). Safety Integrated cannot be commissioned.
Note:
One of the following values is stored in p9700 or has been entered offline:
87 or 208. This is the reason that the
system is attempting to copy the SI parameters from the Control Unit to
the Motor Module during booting. However,
no safety function is sele
When booting, parameter p7826 "automatic firmware update" did not
have the value "1" that is required for the automatic
firmware upgrade/downgrade. This means that when the safety functions
are enabled, an inadmissible combination
of versions can occur.
N
The parameterization of a Sensor Module used for Safety Integrated is not

permissible.
Note:
1: No encoder was parameterized for Safety Integrated.
2: An e
The parameterization of the encoder used by Safety Integrated is different

to the parameterization of the standard
encoder.
Note:
Parameter number of the non-cor
The existing Motor Module software does not support safe motion
monitoring or is not compatible to the software on
the Control Unit or there is a communications error between the Control
Unit and Motor Module.
Note:
This fault results in a STOP A that can
The existing Sensor Module software and/or hardware does not support
the safe motion monitoring function with the
higher-level control.
Note:
Only for internal S
The actual checksum calculated by the drive and entered in r9728 via the
safety-relevant parameters does not match
the reference checksum saved in p9729 at the last machine acceptance.
Safety-relevant parameters have been changed or a fault is present.
No
The parameter cannot be parameterized with this value.

Note:
Parameter number with the incorrect value.
The monitoring function enabled in p9501, p9601 or p9801 is not

supported in this firmware version.
Note:
1: Monitoring function SLP not supported (p9501.1
The safety-relevant basic function "SOS/SLS" is not enabled in p9501
although other safety-relevant monitoring
functions are enabled.
Note:
For the function "Safely-Limited Position" (SE), a lower value is in p9534

than in p9535.
Note:
1: Limit values SLP1 interchanged.
2: Limit values SLP2 interchan
The limit value for the function "Safely-Limited Speed" (SLS) is greater than
the speed that corresponds to an
encoder limit frequency of 500 kHz.
Note:
Maximum
At least one enabled "Safety Cam" (SCA) is parameterized in p9536 or

p9537 too close to the tolerance range around
the modulo position.
The following conditions must be complied with to assign cams to a cam
track:
- the cam length of cam x = p9536[x]-p953
The parameterized modulo value for the "Safe Cam" (SCA) function is not a
multiple of 360 000 mDegrees.
Note:
It is not permissible to simultaneously enable the actual value

synchronization and a monitoring function with absolute
reference (SCA/SLP).
Note:
There is not sufficient memory space in the NVRAM on the drive to save
parameters r9781 and r9782 (safety logbook).
Note:
0: There is no physical NVRAM available
A DRIVE-CLiQ connection fault has occurred.
100 ... 107:
Communication via DRIVE-CLiQ sockets X100 ... X107 has not switched to
cyclic mode. The cause may be an incorrect
structure or a configuration that results in
It is not possible to change the DRIVE-CLiQ basic sampling times p0110 in

operation. POWER ON is required.
Index of p0110.
Another Sensor Module Integrated (SMI) was found.

The reasons could be as follows:
1. A motor with DRIVE-CLiQ (SMI) and another order No. were used as
replacement.
2. A Sensor Module Integrated was used as spare part where there is no
encoder data and mot
The receipt of setpoints from the PROFIBUS interface is interrupted

because the bus connection is interrupted or the
PROFIBUS master is switched off or was set to the STOP state.
See also: p2047 (PROFIBUS additional monitoring time)
The global control telegram to synchronize the clock cycles has failed - in
cyclic operation - for several DP clock
cycles or has violated the time grid specified in the parameterizing telegram
over several consecutive DP clock
cycles (refer to the bus cy
The maximum permissible number of errors in the master sign-of-life (clock

synchronous operation) has been
exceeded in cyclic operation.
The monitoring time for the sign-of-life counter has expired.

The connection between the drive and the higher-level control (SIMOTION,
SINUMERIK) has been interrupted for
the following reasons:
- the control was reset.
- the data transfer to the control w
The monitoring time for the configuration has expired.

0: The transfer time of the send configuration data has been exceeded.
1: The transfer time of the receive configuration data has been exceeded.
At this drive object, the connection to at least one Publisher for PROFIBUS
peer-to-peer data transfer in cyclic operation
has been aborted.
Bit 0 = 1: Publisher with address in r2077[0], connection aborted.
...
Bit
Synchronization of the internal clock cycle to the global control telegram
has failed. The internal clock cycle exhibits
an unexpected shift.
If DRIVE-CLiQ components with different application clock cycle are

operated at a DRIVE-CLiQ port, then this
requires synchronization with the Control Unit.
This synchronization routine was unsuccessful.
Only for in
The existing system configuration requires that the connected DRIVE-CLiQ

components support the synchronization
between the basic clock cycle, DRIVE-CLiQ clock cycle and the application
clock cycle.
However, not all DRIVE-CLiQ components have this functio
and application clock cycle was started and was not able to be successfully
completed.
Only for internal Siemens troubleshooting
The trace was deleted due to the fact that the units were changed over or
the reference parameters changed.
An internal software error has occurred within an OA application.
Too many functions have been configured on this Control Unit (e.g. too
many drives, function modules, data sets,
OA applications, blocks, etc).
When initializaing the Terminal Modules, the terminal of the Control Unit
or the Terminal Board 30, an internal software error has occurred.
The thousands location: 1 . . . 3:
The component number (P0151) of the module involv
The input currentn of the TM analog input has exceeded the threshold
value parameterized in P4061[x].
This fault can only occur, if P4056[x] = 3 (4 . . . 20 mA with monitoring) is
set.
Index x = 0: Analog input 0 (X522.1 to .3)
Index x = 1: Analog input 1
The Terminal Module involved does not send a ready signal and no valid
cyclic data.
Drive object number
A power module signals that the pulses are enabled although the pulses
are inhibited.
Fault value (r0949, decimal): Number of the power module involved.
For one or several power modules, the pulses were not able to be enabled.
Fault value (r0949, decimal): Number of the power module involved
The code numbers of the power units do not match.

Parameter in which the first different power unit code number was
detected.
The EEPROM versions of the power units do not match.

Parameter in which the first different version number was detected.
The firmware versions of the power units connected in parallel do not
match.
The EEPROM versions of the Voltage Sensing Modules (VSM) do not match.
The firmware versions of the Voltage Sensing Module (VSM) do not match.
Firmware from version V02.30.01.00 is required when connecting the

power units in parallel
The number of active Voltage Sensing Modules (VSM) for the drive object
infeed with chassis power units is not correct.
For A_Infeed, each active power unit must be assigned an active VSM also
for a parallel circuit configuration.
For S_Infeed, the active drive object, must be assigned at least one active
VSM.
Number of VSMs that are currently assigned to the drive object.
For AC/AC drive units, the measured DC voltage lies outside the tolerance
range after pre-charging has been completed:
1.16 * p0210 < r0070 < 1.6 * p0210.
The fault can only be acknowledged when the drive is powered down.
See also: p0210 (Drive unit line supply voltage)
KTY:
The motor temperature has exceeded the fault threshold (p0605) or the
timer (p0606) after the alarm threshold was
exceeded (p0604) has expired.
PTC:
The response threshold of 1650 Ohm was exceeded and the timer (p0606)
has expired.
Possible causes:
- motor is overloaded.
- motor ambient temperature too high.
- wire breakage or sensor not connected.
the message.
For I2t motor model activated (p0612 bit 0 = yes, p0611 > 0), fault value =
200 refers to a fault that was initiated by
the I2t motor model.
overtemperature fault threshold), p0606
(Motor overtemperature timer), p0610 (Motor overtemperature response)
An error was detected when evaluating the temperature sensor set in

p0600 and p0601.
Possible causes:
- wire breakage or sensor not connected (KTY: R > 1630 Ohm).
- measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).
Note:
If alarm A07015 is present, the time in p0607 is started. If the fault is still
present after this time has expired, then
fault F07016 is output; however, at the earliest, 1 s after alarm A07015.
the message.
See also: p0607 (Temperature sensor fault timer)
The closed-loop control parameters have been parameterized incorrectly

(e.g. p0356 = L_spread = 0).
The fault value includes the parameter number involved.
The following parameter numbers only occur as fault values for vector
drives:
p0310, for synchronous motors: p0341, p0344, p0350, p0357
The following parameter numbers do not occur as fault values for
synchronous motors:
p0354, p0358, p0360
p0358, p0360, p0400, p0404, p0408, p0640,
p1082, p1300
The macro cannot be executed.
ccccbbaa hex:
cccc = preliminary parameter number, bb = supplementary information, aa
= fault cause
Fault causes for the trigger parameter itself:
-20: Called file is not valid for parameter 15.
-24: Data type of a TAG is incorrect (e.g.: Index, number or bit is not U16).
Fault causes for the parameters to be set:
-25: Error level has an undefined value.
-26: Mode has an undefined value.
-27: A value was entered as string in the tag value that is not "DEFAULT".
The ACX file (macro) to be executed was not able to be found in the
appropriate directory.
Parameter number with which the execution was started.
See also: p0015, p0700 (Macro Binector Input (BI)), p1000 (Macro
Connector Inputs (CI) for speed setpoints), p1500
(Macro Connector Inputs (CI) for torque setpoints)
The WaitUntil condition set in the macro was not fulfilled in a certain
number of attempts.
Parameter number for which the condition was set
Parameters of the open-loop/closed-loop control had to be changed as

they exceeded dynamic limits as a result of
other parameters.
The fault value includes the modified parameter number.
340: The motor and control parameters were automatically calculated
(p0340 = 1), because the vector control was
subsequently activated as configuration (r0108.2).
See also: p0640 (Current limit), p1082 (Maximum speed), p1300 (Open-
loop/closed-loop control operating mode),
p1800 (Pulse frequency)
A reference parameter was changed in the system. This resulted in the fact
that for the parameters involved, the
selected value was not able to be written in the per unit representation
(cause: e.g. the steady-state minimum/maximum
limit or that defined in the application was violated). The values of the
parameters were set to the corresponding
violated minimum/maximum limit or to the factory setting.
Fault value (r0949, parameter):
Diagnostics parameter r9450 to display the parameters that were not able
to be re-calculated.
See also: p0304, p0305, p0310, p0596, p2000, p2001, p2002, p2003, r2004
When resetting drive parameter (p0976) sampling times cannot be reset

using p0111, p0112, p0115.
Parameter whose setting prevents the sampling times being reset.
See also: r0110 (Basic sampling times)
The parameterized sampling times do not match the basic clock cycle.
The fault value specifies the parameter involved.
See also: r0110, r0111, p0115
The transfer of master control is disabled via binector input p3985.

The "master control by PLC" signal was missing in operation.
- interconnection of the binector input for "master control by PLC" is
incorrect (p0854).
- the higher-level control has withdrawn the "master control by PLC" signal.
- data transfer via the fieldbus (master/drive) was interrupted
- the line contactor was not able to be closed within the time in p0861.
- the line contactor was not able to be opened within the time in p0861.
- the line contactor has dropped out in operation.
- the line contactor has closed although the drive converter is powered
down.
Fault value: Bit field BYPASS_CONTACTOR_ERROR_STATE
Bit 1
BYPASS_CONTACTOR_ERR_FBK_ON_MISSING
Switch "Closed" feedback signal missing
Bit 2
BYPASS_CONTACTOR_ERR_FBK_OFF_MISSING
Switch "opened" feedback signal missing
Bit 3
BYPASS_CONTACTOR_ERR_TOO_SLOW
Switch feedback signal too slow:
After switching, the system waits for the positive feedback signal. If the
feedback signal is received later than the
specified time, then a fault trip (shutdown) is issued.
Bit 6
BYPASS_CONTACTOR_ERR_BYPASS_INCONSISTENCY
Drive switch feedback signal is not consistent with the bypass state:
When powering up or for STAGING, the drive switch is closed.
See also: p1260 (Bypass configuration), r1261 (Bypass control/status word),
p1266 (Bypass, control command),
p1267 (Bypass changeover source configuration), p1269 (Bypass switch
feedback signal), p1274 (Bypass switch
monitoring time)
Fault value: Bit field BYPASS_CONTACTOR_ERROR_STATE

Bit 1
BYPASS_CONTACTOR_ERR_FBK_ON_MISSING
Switch "Closed" feedback signal missing
Bit 2
BYPASS_CONTACTOR_ERR_FBK_OFF_MISSING
Switch "opened" feedback signal missing
- The specified number of restart attempts (p1211) has been completely

used up because within the monitoring time
(p1213) the faults were not able to be acknowledged. The number of
restart attempts (p1211) is decremented at each
new start attempt.
- there is no active ON command.
- the monitoring time for the power unit has expired (p0857).
- when exiting commissioning or at the end of the motor identification
routine or the speed controller optimization, the
drive unit is not automatically powered up again.
During a flying restart, it was identified that the search current reached is
too low.
It is possible that the motor is not connected.
It is not possible to power up with the motor rotating (no flying restart). In
the following cases, the "flying restart" function
is not supported:
Permanent-magnet and separately-excited synchronous motors (PEM,
FEM): Operation with V/f characteristic.
Permanent-magnet synchronous motor (PEM): Encoderless operation
without a Voltage Sensing Module (VSM)
being connected.
The DC link voltage monitoring is active (p1240 , p1280 = 5, 6) and the

lower DC link voltage threshold (r1246, r1286)
was reached in the "Operation" state.
The DC link voltage monitoring is active (p1240 , p1280 = 4, 6) and the

upper DC link voltage threshold (r1242,
r1282) was reached in the "Operation" state.
During kinetic buffering the speed fell below minimum speed (p1257 or
p1297 for vector drives with V/f control) and
the line supply did not return.
The maximum buffer time (p1255 and p1295 for vector drives with V/f
control) has been exceeded without the line
supply having returned.
The condition "I_act = 0 and Uq_set_1 longer than 16 ms at its limit" is
present and can be caused by the following:
- motor not connected or motor contactor open.
- no DC link voltage present.
- Motor Module defective.
- the "flying restart" function is not activated.
When quick magnetizing is configured (p1401 Bit6 = 1) the specified flux

setpoint is not reached although 90 % of
the maximum current is specified.
- incorrect motor data.
- motor data and motor configuration (star/delta) do not match.
- the current limit has been set too low for the motor.
- induction motor (encoderless, open-loop controlled) in I2t limiting.
- the Motor Module is too small.
An incorrect commutation angle was detected, that can result in a positive
coupling in the speed controller.
Possible causes:
- the motor encoder is incorrectly adjusted with respect to the magnet
position.
- the motor encoder is damaged.
- the angular commutation offset is incorrectly set (p0431).
- data to calculate the motor model has been incorrectly set (p0356
(motor-stator leakage inductance) and/or p0350
(motor-stator resistance) and/or p0352 (cable resistance).
- the changeover speed for the motor model is too low (p1752). The
monitoring function only becomes effective
above the changeover speed.
- the motor encoder speed signal is faulted.
- the control loop is instable due to incorrect parameterization.
SERVO:
0: The comparison of the pole position angle from the encoder and the
motor model resulted in an excessively high
value (> 80 ° electrical).
1: -
VECTOR:
0: The comparison of the pole position angle from the encoder and the
motor model resulted in an excessively high
value (> 45 ° electrical).
1: The change in the speed signal from the motor encoder has changed by
> p0492 within a current controller clock
cycle.
An incorrect commutation angle was detected, that can result in a positive

coupling in the speed controller.
- within the pole position identification routine (p1982 = 2):
A difference of > 45° electrical to the encoder angle was determined.
- for VECTOR, within the encoder adjustment (p1990 = 2):
A difference of > 6 ° electrical to the encoder angle was determined.
The natural filter frequency of the PT2 element for the reference model
(p1433) is greater than the Shannon frequency.
The Shannon frequency is calculated according to the following formula:
0.5 / p0115[1]
A drive data set was selected - with the pulses enabled - which has a
different parameterized direction of rotation
(p1821).
It is only possible to change the motor direction of rotation using p1821
when the pulses are inhibited.
During operation with sensorless vector control (r1407.1) the ramp-
function generator was stopped (p1141) or
bypassed (p1122). An internal setting command of the ramp-function
generator output caused the set setpoint speed
to be frozen or was not able to be realized.
The ratio between the multiturn resolution and the modular range (p2576)
is not an integer number.
This results in the adjustment being set back, as the position actual value
cannot be reproduced after poweroff/
power-on.
connector input p2599 lies outside the half
of the encoder range and cannot be set as current axis position.
Maximum permissible value for the reference point coordinate.
The position tracking cannot be reset.

When the position tracking of the load gear is configured, the
drive/encoder (motor encoder) identifies a maximum
possible absolute position actual value (r2723) that can no longer be
represented within 32 bits.
Maximum value: p0408 * p2721 * 2^p0419
ccbbaa hex
aa = encoder data set
bb = component number
cc = drive data set
See also: p0408 (Rotary encoder pulse No.), p0419 (Fine resolution
absolute value Gx_XIST2 (in bits)), p2721 (Load
gear, rotary absolute gearbox, revolutions, virtual)
For a configured linear axis/no modulo axis, the currently effective motor
encoder (encoder 1) has exceeded the
maximum possible traversing range.
For the configured linear axis, the maximum traversing range is defined to
be 64x (+/- 32x) of p0421. It should be
read in p2721 and interpreted as the number of load revolutions.
Note:
Here, only the motor encoder in the currently effective drive data set is
monitored. The currently effective drive data
set is displayed in x = r0051 and the corresponding motor encoder is
specified in p0187[x].
When powered down, the currently effective motor encoder was moved
through a distance greater than was parameterized
in the tolerance window. It is possible that there is no longer any reference
between the mechanical system
and encoder.
Note:
Here, only the motor encoder in the currently effective drive data set is
monitored. The currently effective drive data
set is displayed in x = r0051 and the corresponding motor encoder is
specified in p0187[x].
Deviation (difference) to the last encoder position in increments of the
absolute value after the measuring gear - if
one is being used. The sign designates the traversing direction.
Note:
The deviation (difference) found is also displayed in r2724.
See also: p2722 (Load gear, position tracking tolerance window), r2724
(Load gear position difference)
After the standstill monitoring time (p2543) expired, the drive left the
standstill window (p2542).
- position actual value inversion incorrectly set (p0410).
- standstill window set too small (p2542).
- standstill monitoring time set too low (p2543).
- position loop gain too low (p2538).
- position loop gain too high (instability/oscillation, p2538).
- mechanical overload.
- check the connecting cable, motor/drive converter (phase missing,
interchange).
- when selecting motor identification, select tracking mode (BI: p2655[0] =
1 signal).
- when selecting function generator, select tracking mode (BI: p2655[0] = 1
signal) and de-activate position control
(BI:p2550 = 0 signal).
When the position monitoring time (p2545) expired, the drive had still not
reached the positioning window (p2544).
- positioning window parameterized too small (p2544).
- position monitoring time parameterized too short (p2545).
- position loop gain too low (p2538).
- position loop gain too high (instability/oscillation, p2538).
- drive mechanically locked.
The difference between the position setpoint position actual value

(following error dynamic model, r2563) is greater
than the tolerance (p2546).
- the drive torque or accelerating capacity exceeded.
- position measuring system fault.
- position control sense incorrect.
- mechanical system locked.
- excessively high traversing velocity or excessively high position reference
value (setpoint) differences

After starting the search for reference, the axis moved through the
maximum permissible distance to search for the
reference cam without actually finding the reference cam.
After leaving the reference cam, the axis has traversed the maximum
permissible distance between the reference
cam and zero mark without finding the zero mark.
During the search for reference, when the axis reached the zero mark it
also reached the end of the traversing range
without detecting an edge at the binector input "reference cam" (BI:
p2612).
Maximum traversing range: -2147483648 [LU] ... -2147483647 [LU]
The traversing block does not contain valid information.

Number of the traversing block with invalid information.
The target position for relative traversing lies outside the traversing range.
The target position for relative traversing lies outside the traversing range.
The current position of the axis is less than the position of the software
limit switch minus.
The current position of the axis is greater than the position of the software
limit switch plus.
In the "fixed stop reached" state, the axis has moved outside the defined
monitoring window (p2635).
In a traversing block with the task FIXED STOP, the end position was
reached without detecting a fixed stop.
In the mode "direct setpoint input/MDI", for continuous transfer (p2649 =

1) relative positioning was selected (BI:
p2648 = 0 signal).
for a standard assignment, another fault may have occurred as a result of
withdrawing the enable signals.
the drive is in the "switching on inhibited" state (for a standard
assignment).
A zero signal was detected at binector input BI: p2569, i.e. the STOP cam
minus was reached.
For a positive traversing direction, the STOP cam minus was reached - i.e.
the wiring of the STOP cam is incorrect.
A zero signal was detected at binector input BI: p2570, i.e. the STOP cam
plus was reached.
For a negative traversing direction, the STOP cam plus was reached - i.e.
the wiring of the STOP cam is incorrect.
A drive data set changeover (DDS changeover) when the mechanical
relationships change (p2503 .. 2506), the
direction of rotation (p1821) or the encoder assignment (p2502) were
requested during operation.
Only for power units:

The encoder data set was not configured - this means that a data set
number was not entered into the associated
drive data set.
The fault value includes the drive data set number of p0187, p0188 and
p0189.
The fault value is increased by 100 * encoder number (e.g. for p0189: Fault
value 3xx with xx = data set number).
A Drive Data Set (DDS) is assigned to a Motor Data Set (MDS) or Encoder
Data Set (EDS) that does not have a
component number.
nnmmmxxyyy
nn: Number of the MDS/EDS.
mmm: Parameter number of the missing component number.
xx: Number of the DDS that is assigned to the MDS/EDS.
yyy: Parameter number that references the MDS/EDS.
Example:
p0186[7] = 5: DDS 7 is assigned MDS 5.
p0131[5] = 0: There is no component number set in MDS 5.
Alarm value = 0513107186
More than one encoder with identical component number is assigned to a

single drive data set. In one drive data set,
it is not permissible that identical encoders are operated together.
1000 * first identical encoder + 100 * second identical encoder + drive data
set.
Example:
Fault value = 1203 means:
In drive data set 3, the first (p0187[3]) and second encoder (p0188[3]) are
identical.
Each encoder may only be assigned to one drive and within a drive must -
in each drive data set - either always be
encoder 1, always encoder 2 or always encoder 3. This unique assignment
has been violated.
The two parameters in coded form, that refer to the same component
number.
First parameter:
Index: First and second decimal place (99 for EDS, not assigned DDS)
Parameter number: Third decimal place (1 for p0187, 2 for p0188, 3 for
p0189, 4 for EDS not assigned DDS)
Drive number: Fourth and fifth decimal place
Second parameter:
Index: Sixth and seventh decimal place (99 for EDS, not assigned DDS)
Parameter number: Eighth decimal place (1 for p0187, 2 for p0188, 3 for
p0189, 4 for EDS, not assigned DDS)
Drive number: Ninth and tenth decimal place
See also: p0141 (Encoder interface (Sensor Module) component number)
Using p0141, a changeover of the encoder data set is prepared that is

illegal. In this firmware release, an encoder
data set changeover is only permitted for the components in the actual
topology.
Incorrect EDS data set number.
See also: p0187 (Encoder 1 encoder data set number), p0188 (Encoder 2
encoder data set number), p0189
(Encoder 3 encoder data set number)
A power unit (via PDS) was assigned to a motor (via MDS) in a drive data set
that is not connected in the target
topology.
Number of the incorrectly parameterized drive data set.
The assignment between the drive data set and motor data set (p0186) or
between the drive data set and the
encoder data set was modified (p0187). This is the reason that the drive
data set must re-commissioned.
Drive data set to be re-commissioned.
An MDS cannot have different motor encoders in two different DDS.

The following parameterization therefore results results in an error:
p0186[0] = 0, p0187[0] = 0
p0186[0] = 0, p0187[0] = 1
The lower 16 bits indicate the first DDS and the upper 16 bits indicate the
second DDS.
The system has identified that two motor data sets were incorrectly
parameterized.
Parameter r0313 (calculated from p0314, p0310, p0311), r0315 and p1982
may only have different values if the
motor data sets are assigned different motors. p0827 is used to assign the
motors and/contactors.
It is not possible to toggle between motor data sets.
xxxxyyyy:
xxxx: First DDS with assigned MDS, yyyy: Second DDS with assigned MDS
The commutation angle information is missing. This means that

synchronous motors cannot be controlled (closedloop
control)
yyyyxxxx dec: yyyy = fault cause, xxxx = drive data set
yyyy = 1 dec:
The motor encoder used does not supply an absolute commutation angle.
yyyy = 2 dec:
The selected ratio of the measuring gear does not match the motor pole
pair number.
The requested encoder configuration is not supported. Only bits may be

requested in p0404 that are signaled as
being supported by the encoder evaluation in r0456.
Low word low byte: Encoder data set number
Low word high byte: Component number
High word:
The encoder evaluation does not support a function selected in p0404.
1: sin/cos encoder with absolute track (this is supported by SME25).
3: Squarewave encoder (this is supported by SMC30).
4: sin/cos encoder (this is supported by SMC20, SMI20, SME20, SME25).
12: sin/cos encoder with reference mark (this is supported by SME20).
15: Commutation with zero mark for separately-excited synchronous
motors with VECTORMV.
23: Resolver (this is supported by SMC10, SMI10).
65535: Other function (compare r0456 and p0404).
See also: p0404 (Encoder configuration effective), r0456 (Encoder
configuration supported)
The Sensor Module does not support the requested configuration.
If p0430 (cc = 0) incorrect, the following applies:
- In p0430 (requested functions), at least 1 bit was set that is not set in
r0458 (supported functions) (exception: bits
19, 28, 29, 30, 31).
- p1982 > 0 (pole position identification requested), but r0458.16 = 0 (pole
position identification not supported).
If p0437 (cc = 1) incorrect, the following applies:
- In p0437 (requested functions), at least 1 bit was set that is not set in
r0459 (supported functions).
ddccbbaa hex
aa: encoder data set no.
bb: first incorrect bit
cc: incorrect parameter
cc = 0: incorrect parameter is p0430
cc = 1: incorrect parameter is p0437
dd: reserved (always 0)
The configuration of the position tracking is not supported.

Position tracking can only be activated for absolute encoders.
For linear axes, it is not possible to simultaneously activate the position
tracking for load- and measuring gear.
ddccbbaa hex
aa = encoder data set
cc = drive data set
dd = fault cause
dd = 00 hex = 0 dez
An absolute encoder is not being used.
dd = 01 hex = 1 dez
Position tracking cannot be activated because the memory of the internal
NVRAM is not sufficient or a Control Unit
does not have an NVRAM.
dd = 02 hex = 2 dez
For a linear axis, the position tracking was activated for the load and
measuring gear.
dd = 03 hex = 3 dez
Position tracking cannot be activated because position tracking with
another gear ratio, axis type or tolerance window
has already been detected for this encoder data set.
dd = 04 hex = 4 dez
A linear encoder is being used.
See also: p0404 (Encoder configuration effective), p0411 (Measuring gear,
configuration)
When the position tracking of the measuring gear is configured, the
drive/encoder identifies a maximum possible
absolute position actual value (r0483) that cannot be represented within 32
bits.
Maximum value: p0408 * p0412 * 2^p0419
Low word low byte: Encoder data set number
Low word high byte: Component number
See also: p0408 (Rotary encoder pulse No.), p0412 (Measuring gear, rotary
absolute gearbox, revolutions, virtual),
p0419 (Fine resolution absolute value Gx_XIST2 (in bits))
For rotary absolute encoders, the pulse number in p0408 must be to the
power of two.
The fault value includes the encoder data set number involved.
The multiturn resolution in p0421 must be to the power of two.

The fault value includes the encoder data set number involved.
The requested position tracking for incremental encoders is not supported.
ccccbbaa hex
aa = encoder Data Set number
cccc = fault cause
cccc = 00 hex = 0 dec
The encoder type does not support the "Position tracking incremental
encoder" function.
Position tracking cannot be activated because the memory of the internal
NVRAM is not sufficient or a Control Unit
does not have an NVRAM.
A linear encoder is used that does not support the position tracking
function.
See also: p0404 (Encoder configuration effective), p0411 (Measuring gear,
configuration), r0456 (Encoder configuration
supported)
The motor encoder signals that it is not ready.

- initialization of encoder 1 (motor encoder) was unsuccessful.
- the function "parking encoder" is active (encoder control word
G1_STW.14 = 1).
- the encoder interface (Sensor Module) is de-activated (p0145).
- the Sensor Module is defective.
The maximum encoder value times the factor to convert the absolute
to length units (LU) has exceeed the value range (-2147483648 ...
2147483647) for displaying the position actual
value.
value.
value.
The power unit parameters cannot be read or no parameters are stored in

the power unit.
Connection between the Control Unit and the Motor Module was
interrupted or is defective.
This fault also occurs if an incorrect topology was selected in the
commissioning software and this parameterization
is then downloaded to the Control Unit.
See also: r0200 (Power unit current code number)
The permissible motor limit current was exceeded.

- effective current limit set too low.
- current controller not correctly set.
- motor was braked with an excessively high stall torque correction factor.
- V/f operation: Up ramp was set too short or the load is too high.
- V/f operation: Short-circuit in the motor cable or ground fault.
- V/f operation: Motor current does not match the current of Motor
Module.
Note:
Limit current = 2 * Minimum( p0640, 4 * p0305) >= 2 * p0305
After an internal power-on command, the infeed or drive does not signal
ready.
- monitoring time is too short.
- DC link voltage is not present.
- associated infeed or drive of the signaling component is defective.
- supply voltage incorrectly set.
No rated data are stored in the power unit EEPROM.

See also: p0205 (Power unit application), r0206 (Rated power unit power),
r0207 (Rated power unit current), r0208
(Rated power unit line supply voltage), r0209 (Power unit, maximum
current)
The code number of the current power unit does not match the saved
number. The fault only occurs if the comparator
in p9906 or p9908 is not at f 2 (low) or 3 (minimum).
Number of the incorrect parameter.
See also: r0200 (Power unit current code number), p0201 (Power unit code
number)
The simulation mode is activated and the DC link voltage is greater than the
permissible value of 40 V.
The signal "infeed operation" is not present although the enable signals for
the drive have been present for longer
than the parameterized monitoring time (p0857).
- infeed not operational.
- interconnection of the binector input for the ready signal is either
incorrect or missing (p0864).
- infeed is presently carrying out a line supply identification routine.
The signal "infeed operation" was withdrawn in operation.

- interconnection of the binector input for the signal "infeed operation" is
either incorrect or missing (p0864).
- the enable signals of the infeed were disabled.
- due to a fault, the infeed withdraws the signal "infeed operation".
The BICO signal "external fault 1" was triggered.

See also: p2106 (External fault 1)
See also: p2107 (External fault 2)
See also: p2108, p3111, p3112
The internal armature short-circuit (p1231 = 4) is not possible as Safe
Torque Off (STO) is enabled. The pulses cannot
be enabled.
Motor has been operating at the torque limit longer than the time specified
in p2177 and below the speed threshold
set in p2175.
This signal can also be initiated if the speed actual value is oscillating and
the speed controller output repeatedly
goes to its limit.
If the simulation mode is enabled (p1272 = 1) and the closed-loop control
with speed encoder activated (p1300 =
21), then the inhibit signal is generated if the encoder signal is not received
from a motor that is driven with the torque
setpoint of the closed-loop control.
See also: p2175 (Motor locked speed threshold), p2177 (Motor locked
delay time)
The maximum permissible speed was either positively or negatively

exceeded.
The maximum permissible positive speed is formed as follows: Minimum
(p1082, CI: p1085) + p2162
The maximum permissible negative speed is formed as follows: Maximum
(-p1082, CI: 1088) - p2162
For a vector drive the system has identified that the motor has stall for a
time longer than is set in p2178.
1: Stall detection using r1408.11 (p1744 or p0492).
2: Stall detection using r1408.12 (p1745).
3: Stall detection using r0056.11 (only for separately excited synchronous
motors).
See also: p1744 (Motor model speed threshold stall detection), p2178
(Motor stalled delay time)
When opening, the contactor feedback signal (p1235) did not issue the
signal "Open" (r1239.1 = 0) within the monitoring
time (p1236).
The armature short-circuit is incorrectly parameterized.
Low word: Motor data set number
High word: Cause:
1: A permanent-magnet synchronous motor has not been selected.
101: External armature short-circuit: Output (r1239.0) not connected up.
102: External armature short-circuit with contactor feedback signal: No
feedback signal connected (BI:p1235).
103: External armature short-circuit without contactor feedback signal:
Delay time when opening (p1237) is 0.
The function "Internal voltage protection" (p1231 = 3) was activated. The

following must be observed:
- when the internal voltage protection is active, after pulse suppression, all
of the motor terminals are at half of the
DC link voltage (without an internal voltage protection, the motor terminals
are at zero potential)!
- it is only permissible to use motors that are short-circuit proof (p0320 <
p0323).
- the Motor Module must be able to continually conduct 180% short-circuit
current (r0331) of the motor (r0289).
- the internal voltage protection cannot be interrupted due to a fault
response. If an overcurrent condition occurs during
the active, internal voltage protection, then this can destroy the Motor
Module and/or the motor.
- if the Motor Module does not support the autonomous, internal voltage
protection (r0192.10 = 0), in order to ensure
safe, reliable functioning when the line supply fails, an external 24 V power
supply (UPS) must be used for the components.
- if the Motor Module does support the autonomous, internal voltage
protection (r0192.10 = 1), in order to ensure
safe, reliable functioning when the line supply fails, the 24 V power supply
for the components must be provided
through a Control Supply Module.
- if the internal voltage protection is active, it is not permissible that the
motor is driven by the load for a longer period
of time (e.g. as a result of loads that move the motor or another coupled
motor).
The de-activation of the internal voltage protection (p1231 not equal to 3)
only becomes effective after POWER ON.
The status signal r1239.6 = 1 indicates that the internal voltage protection
is ready.
The difference between the excitation current actual value and setpoint
has exceeded the tolerance:
abs(r1641 - r1626) > p3201 + p3202
The cause of this fault is again reset for abs(r1641 - r1626) < p3201.
The difference between the flux actual value and setpoint has exceeded
the tolerance:
abs(r0084 - r1598) > p3204 + p3205
The cause of this fault is again reset for abs(r0084 - r1598) < p3204.
The fault is only issued after the delay time in p3206 has expired.

negative direction (too low).
The torque deviates from the torque/speed envelope characteristic.
The Motor Module signals that the motor is short-circuited through the
power semiconductors (r1239.5 = 1). The
pulses cannot be enabled. The internal voltage protection is selected
(p1231 = 3).
The Control Unit has detected a brake control error.
10, 11:
- No brake connected or wire breakage (check whether brake releases for
p1278 = 1).
- Ground fault in brake cable.
20:
Fault in "brake open" state.
- Short-circuit in brake winding.
30, 31:
Fault in "close holding brake" operation.
p1278 = 1).
40:
Fault in "brake closed" state.
50:
Fault in the brake control circuit of the Control Unit or communication fault
between the Control Unit and Motor Module
(brake control).
A motor with integrated motor holding brake was detected where the
brake control has not been configured (p1215
= 0). The brake control configuration was then set to "motor holding brake
the same as sequence control" (p1215 =
1).
After synchronization has been completed, the phase difference (r3808) is

greater than the threshold value, phase
synchronism (p3813).
OFF1 or OFF3 response, while the closed-loop phase control is active
(r3819.6 = 1) or synchronism reached
(r3819.2 = 1).
Enable signal withdrawn (p3802 = 0), while the closed-loop phase control
was active (r3819.6 = 1).
- the motor parameters were incorrectly entered while commissioning (e.g.

p0300 = 0, no motor)
The braking resistor (p6811) has still not been parameterized -
commissioning cannot be completed.
The parameter number involved.
p0316, p0320, p0322, p0323
The code number of the current motor with DRIVE-CLiQ does not match
the saved number.
Number of the incorrect parameter.
See also: p0301 (Motor code number selection), r0302 (Motor code
number of motor with DRIVE-CLiQ)
The motor code of the current motor with DRIVE-CLiQ does not match the
possible list motor types (refer to the
selection, p0300).
Motor code of the motor with DRIVE-CLiQ
The conditions to record the friction characteristic are not fulfilled.

0046: Missing enable signals (r0046).
1082: The highest speed value to be approached (p3829) is greater than
the maximum speed (p1082).
the maximum speed (r1084, p1083, p1085).
the maximum speed (r1087, p1086, p1088).
1110: Friction characteristic record, negative direction selected (p3845) and
negative direction inhibited (p1110).
1111: Friction characteristic record, positive direction selected (p3845) and
positive direction inhibited (p1111).
1198: Friction characteristic record selected (p3845 > 0) and negative
(p1110) and positive directions (p1111) inhibited
(r1198).
1300: The control mode (p1300) has not been set to closed-loop speed
control.
1755: For encoderless closed-loop control (p1300 = 20), the lowest speed
value to be approached (p3820) is less
than or equal to the changeover speed, open-loop controlled operation
(p1755).
1910: Motor data identification activated.
1960: Speed controller optimization activated.
3820 ... 3829: Speed (p382x) cannot be approached.
3840: Friction characteristic incorrect.
3845: Friction characteristic record de-selected.
A fault has occurred during the automatic encoder adjustment or the pole
position identification.
A fault has occurred during the Lq-Ld measurement.
10: Stage 1: The ratio between the measured current and zero current is
too low.
12: Stage 1: The maximum current was exceeded.
15: Second harmonic too low.
16: Drive converter too small for the measuring technique.
17: Abort due to pulse inhibit.
A fault has occurred during the pole position identification routine.

1: Current controller limited
2: Motor shaft locked.
4: Encoder speed signal not plausible.
too low.
too low.
14: Current difference to determine the +d axis too low.
18: First harmonic too low.
20: Pole position identification requested with the motor shaft rotating and
activated flying restart function.
A fault has occurred during the automatic encoder adjustment.
1: Current controller limited
2: Motor shaft locked.
4: Encoder speed signal not plausible.
too low.
too low.
14: Current difference to determine the +d axis too low.
A fault has occurred during the encoder test.
1: The speed did not reach a steady-state condition.
2: The speed setpoint was not able to be approached as the minimum
limiting is active.
3: The speed setpoint was not able to be approached as the suppression
(skip) bandwidth is active.
4: The speed setpoint was not able to be approached as the maximum
limiting is active.
5: The encoder does not supply a signal.
6: Incorrect polarity.
7: Incorrect pulse number.
8: Noise in the encoder signal or speed controller unstable.
9: Voltage Sensing Module (VSM) incorrectly connected.
A fault has occurred while determining the saturation characteristic.

2: The rotor flux did not reach a steady-state condition.
3: The adaptation circuit did not reach a steady-state condition.
4: The adaptation circuit was not enabled.
5: Field weakening active.
limiting is active.
limiting is active.
9: Several values of the determined saturation characteristic are not
plausible.
10: Saturation characteristic could not be sensibly determined because load
torque too high.
A fault has occurred while identifying the moment of inertia.
limiting is active.
3. The speed setpoint was not able to be approached as the suppression
4. The speed setpoint was not able to be approached as the maximum
limiting is active.
5: It is not possible to increase the speed by 10% as the minimum limiting is
active.
6: It is not possible to increase the speed by 10% as the suppression (skip)
bandwidth is active.
7: It is not possible to increase the speed by 10% as the maximum limiting is
active.
8: The torque difference after the speed setpoint step is too low in order to
be able to still reliably identify the moment
of inertia.
9: Too few data to be able to reliably identify the moment of inertia.
10: After the setpoint step, the speed either changed too little or in the
incorrect direction.
11: The identified moment of inertia is not plausible.
A fault has occurred during the vibration test.

limiting is active.
limiting is active.
5: Torque limits too low for a torque step.
6: No suitable speed controller setting was found.
During the rotating measurements, problems with the ramp-function
generator occurred.
1: The positive and negative directions are inhibited.
When configuring the rotating measurement (p1959), no function was

selected.
An error has occurred while measuring the dynamic leakage inductance.

limiting is active.
limiting is active.
5: The 100% flux setpoint was not reached.
6: No Lq measurement possible because field weakening is active.
7: Speed actual value exceeds the maximum speed p1082 or 75% of the
rated motor speed.
8: Speed actual value is below 2 % of the rated motor speed.
A fault has occurred during the identification routine.
1: Current limit value reached.
2: Identified stator resistance lies outside the expected range 0.1 ... 100 %
of Zn.
3: Identified rotor resistance lies outside the expected range 0.1 ... 100 % of
Zn.
4: Identified stator reactance lies outside the expected range 50 ... 500 % of
Zn.
5: Identified magnetizing reactance lies outside the expected range 50 ...
500 % of Zn.
6: Identified rotor time constant lies outside the expected range 10 ms ... 5
s.
7: Identified total leakage reactance lies outside the expected range 4 ... 50
% of Zn.
8: Identified stator leakage reactance lies outside the expected range 2 ...
50 % of Zn.
9: Identified rotor leakage reactance lies outside the expected range 2 ... 50
% of Zn.
10: Motor has been incorrectly connected.
11: Motor shaft rotates.
20: Identified threshold voltage of the semiconductor devices lies outside
the expected range 0 ... 10 V.
30: Current controller in voltage limiting.
Terminal Board 30 detects an incorrect internal power supply voltage.

0: Error when testing the monitoring circuit.
1: Fault in normal operation.
The analog/digital converter on Terminal Board 30 has not supplied any

converted data.
The monitoring time for the configuration has expired.
0: The transfer time of the send configuration data has been exceeded.
1: The transfer time of the receive configuration data has been exceeded.
The set monitoring time expired while transferring process data via COMM
BOARD.
See also: p8840 (COMM BOARD monitoring time)
COMM BOARD did not accept the send-configuration data.
Return value of the send-configuration data check.
A CAN communications error has occurred.
1: The error counter for the send telegrams has exceeded the BUS OFF
value 255. The bus disables the CAN controller.
- bus cable interrupted.
- bus cable not connected.
- incorrect baud rate.
- incorrect bit timing.
2: The master no longer interrogated the CAN node status longer than for
its "life time". The "life time" is obtained
from the "guard time" (p8604[0]) multiplied by the "life time factor"
(p8604[1]).
- bus cable interrupted.
- bus cable not connected.
- incorrect baud rate.
- incorrect bit timing.
- master fault.
Note:
The fault response can be set as required using p8641.
See also: p8604 (CBC node guarding), p8641 (CBC abort connection option
code)
A CANopen NMT state transition from "operational" to "pre-operational" or

after "stopped".
1: CANopen NMT state transition from "operational" to "pre-operational".
2: CANopen NMT state transition from "operational" to "stopped".
Note:
In the NMT state "pre-operational", process data cannot be transferred and
in the NMT state "stopped", no process
data and no service data can be transferred.
The power unit has detected an overcurrent condition.
- motor has a short-circuit or fault to ground (frame).
- V/f operation: Up ramp set too low.
- V/f operation: Rated motor current is significantly greater than that of the
Motor Module.
- infeed: High discharge and post-charging current for line supply voltage
interruptions.
- infeed: High post-charging currents for overload when motoring and DC
link voltage dip.
- infeed: Short-circuit currents at power-on due to the missing
commutating reactor.
- power cables are not correctly connected.
- power cables exceed the maximum permissible length.
Additional causes for a parallel switching device (r0108.15 = 1):
- a power unit has tripped (powered down) due to a ground fault.
- the closed-loop circulating current control is either too slow or has been
set too fast.
Fault value (r0949, interpret bitwise binary):
Bit 0: Phase U.
Bit 1: Phase V.
Bit 2: Phase W.
Note:
Fault = 0 means that the phase with overcurrent is not recognized (e.g. for
Blocksize device).
The power unit has detected an overvoltage condition in the DC link.

- motor regenerates too much energy.
- device supply voltage too high.
- when operating with a VSM, the phase assignment L1, L2, L3 at the VSM
differs from the phase assignment at the
power unit.
DC link voltage [1 bit = 100 mV].
For SINAMICS GM/SM, the following applies:
32: Overvoltage in the negative partial DC link (VdcP)
64: Overvoltage in the positive partial DC link (VdcN)
96: Overvoltage in both partial DC links
The power unit has detected an undervoltage condition in the DC link.

- line supply failure
- line supply voltage below the permissible value.
- line supply infeed failed or interrupted.
Note:
The monitoring threshold for the DC link undervoltage is the minimum of
the following values:
- for a calculation, refer to p0210.
The temperature of the power unit heat sink has exceeded the permissible
limit value.
- overload.
Temperature [1 bit = 0.01 °C].
The power unit was overloaded (r0036 = 100 %).

- the permissible rated power unit current was exceeded for an
inadmissibly long time.
I2t [100 % = 16384].
The Thyristor Control Board (TCB) of the Basic Line Module signals a fault.
- there is no line supply voltage.
- the line contactor is not closed.
- the line supply voltage is too low.
- line supply frequency outside the permissible range (45 ... 66 Hz).
- there is a DC link short-circuit.
- there is a DC link short-circuit (during the pre-charging phase).
- voltage supply for the Thyristor Control Board outside the nominal range
(5 ... 18 V) and line voltage >30 V.
- there is an internal fault in the Thyristor Control Board.
The power unit has detected that the cyclic setpoint telegrams of the
Control Unit were not punctually updated for at
least two clock cycles within a time interval of 20 ms.
A line phase failure was detected at the power unit.

- the fuse of a phase of a main circuit has ruptured.
- the DC link voltage ripple has exceeded the permissible limit value.
The connection to one of the heat sink temperature sensors in the power
unit is interrupted.
Bit 0: Module slot (electronics slot)
Bit 1: Air intake
Bit 2: Inverter 1
Bit 3: Inverter 2
Bit 4: Inverter 3
Bit 5: Inverter 4
Bit 6: Inverter 5
Bit 7: Inverter 6
Bit 8: Rectifier 1
Bit 9: Rectifier 2
The heat sink temperature sensor in the Motor Module is short-circuited.
Bit 0: Module slot (electronics slot)
Bit 1: Air intake
Bit 2: Inverter 1
Bit 3: Inverter 2
Bit 4: Inverter 3
Bit 5: Inverter 4
Bit 6: Inverter 5
Bit 7: Inverter 6
Bit 8: Rectifier 1
Bit 9: Rectifier 2
The hardware current limitation in the relevant phase (see A30031,

A30032, A30033) has responded too often. The
number of times the limit has been exceeded depends on the design and
type of power unit.
For infeed units, the following applies:
- load on the infeed is too high.
- Voltage Sensing Module incorrectly connected.
- commutating reactor missing or the incorrect type.
The following applies to Motor Modules:
Bit 0: Phase U
Bit 1: Phase V
Bit 2: Phase W
A configuration is requested that is not supported by the power unit.

0:
Autonomous operation is requested but is not supported.
Power unit has detected a ground fault.

- ground fault in the power cables
- winding fault or ground fault at the motor.
- CT defective.
Additional cause for CU310/CUA31:
- when the brake is applied, this causes the hardware DC current
monitoring to respond.
Additional cause for parallel switching devices (r0108.15 = 1):
- the closed-loop circulating current control is either too slow or has been
set too fast.
Absolute value, summation current [32767 = 271 % rated current].
In the power unit, the monitoring of the collector-emitter voltage (V_ce) of
the semiconductor has responded.
Possible causes:
- fiber-optic cable interrupted.
- power supply of the IGBT gating module missing.
- short-circuit at the Motor Module output.
- defective semiconductor in the power unit.
Bit 0: Short-circuit in phase U
Bit 1: Short circuit in phase V
Bit 2: Short-circuit in phase W
Bit 3: Light transmitter enable defective
Bit 4: V_ce group fault signal interrupted
See also: r0949 (Fault value)
The temperature difference between the heat sink and chip has exceeded
the permissible limit value.
- overload.
See also: r0037
Chip temperature of the semiconductor has exceeded the permissible limit

value.
- overload.
Temperature difference between the heat sink and chip [1 Bit = 0.01 °C].
The power unit DC link was not able to be pre-charged within the expected
time.
1) There is no line supply voltage connected.
2) The line contactor/line side switch has not been closed.
3) The line supply voltage is too low.
4) Line supply voltage incorrectly set (p0210).
5) The pre-charging resistors are overheated as there were too many pre-
charging operations per time unit.
6) The pre-charging resistors are overheated as the DC link capacitance is
too high.
7) The pre-charging resistors are overheated because when there is no
"ready for operation" (r0863.0) of the infeed
unit, power is taken from the DC link.
8) The pre-charging resistors are overheated as the line contactor was
closed during the DC link fast discharge
through the Braking Module.
9) The DC link has either a ground fault or a short-circuit.
10) The pre-charging circuit is possibly defective (only for chassis units).
Missing internal enable signals, power unit (lower 16 bit):
(Inverted bit-coded representation FFFF hex -> all internal enable signals
available)
Bit 0: Power supply of the IGBT gating shut down
Bit 1: Reserved
Bit 2: Reserved
Bit 3: Ground fault detected
Bit 4: Peak current intervention
Bit 5: I2t exceeded
Bit 6. Thermal model overtemperature calculated
Bit 7: (heat sink, gating module, power unit) overtemperature measured
Bit 8: Reserved
Bit 9: Overvoltage detected
Bit 10: Power unit has completed pre-charging, ready for pulse enable
Bit 11: STO terminal missing
Bit 12: Overcurrent detected
Bit 13: Armature short-circuit active
Bit 14: DRIVE-CLiQ fault active
The air intake in the power unit has exceeded the permissible temperature
limit.
For air-cooled power units, the temperature limit is at 55 °C.
The temperature in the module slot of the drive converter has exceeded
the permissible temperature limit.
- overload.
The temperature in the rectifier of the power unit has exceeded the
permissible temperature limit.
- overload.
- line supply phase failure.
Failure of the 24 V power supply for the power unit.
the 16 V threshold was undershot for longer than 3 ms.

Overvoltage of the 24 V power supply for the power unit.
- the 31.5 V threshold was exceeded for more than 3 ms.

Power supply fault in the power unit.
- the voltage monitoring on the DAC board signals an undervoltage fault on
the module.
Cooling system: Cooling medium flow rate too low

the voltage monitoring on the DAC board signals an overvoltage fault on
the module.
EEPROM data error of the power unit module.
0: The EEPROM data read in from the power unit module is inconsistent.
1: EEPROM data is not compatible to the firmware of the power unit
application.
The bypass contactor of the infeed unit was damaged by being opened
(multiple number of times) while it was conducting
current.
Possible causes:
- scheduled opening under load can be necessary, for example, to protect
the drive converter group in the event of
a ground fault in high frequency spindles.
- incorrect operator control of the infeed can cause the contactor to switch
under load. If, in spite of a missing operating
enable, the infeed unit draws active motoring power from the DC link.

A cycle is requested that is not supported by the power unit.
0: The current control cycle is not supported.
1: The DRIVE-CLiQ cycle is not supported.
2: Internal timing problem (distance between RX and TX instants too low).
3: Internal timing problem (TX instant too early).

More than one actual value telegram from the power unit has failed.
More than one setpoint telegram was not able to be transferred to the
power unit.
Communication is not possible with the power unit via the plug contact.
At least one incorrect actual value channel was detected on the Power
Stack Adapter (PSA).
The incorrect actual value channels are displayed in the following
diagnostic parameters.
The power unit has detected overvoltage in the DC link with a pulse inhibit.
- device supply voltage too high.
- line reactor incorrectly dimensioned.
DC link voltage [1 bit = 100 mV].
See also: r0070 (Actual DC link voltage)
The drive-based "Safety Integrated" function in the Motor Module (MM)

has detected a fault and initiated STOP A
(pulse suppression via the safety shutdown path of the Motor Module).
- forced checking procedure of the safety shutdown path of the Motor
Module unsuccessful.
- subsequent response to fault F30611 (defect in a monitoring channel).
0: Stop request from the Control Unit.
1005: Pulses suppressed although STO not selected and there is no internal
STOP A present.
1010: Pulses enabled although STO is selected or an internal STOP A is
present.
1020: Internal software error in the "Internal voltage protection" function.
The "Internal voltage protection" function is
withdrawn. A STOP A that cannot be acknowledged is initiated.
9999: Subsequent response to fault F30611.
The drive-based "Safety Integrated" function in the Motor Module (MM)
has detected a fault in the data cross-check
between the Control Unit (CU) and MM and initiated a STOP F.
As a result of this fault, after the parameterized transition has expired
(p9858), fault F30600 is output (SI MM: STOP
A initiated).
0: Stop request from the Control Unit.
1 to 999:
Number of the cross-checked data that resulted in this fault. This number is
also displayed in r9895.
1: SI monitoring clock cycle (r9780, r9880).
2: SI enable safety functions (p9601, p9801). Crosswise data comparison is
only carried out for the supported bits.
3: SI SGE changeover tolerance time (p9650, p9850).
4: SI transition period STOP F to STOP A (p9658, p9858).
5: SI enable Safe Brake Control (p9602, p9802).
6: SI Motion enable, safety-relevant functions (p9501, internal value).
7: SI pulse suppression delay time for Safe Stop 1 (p9652, p9852).
8: SI PROFIsafe address (p9610, p9810).
1000: Watchdog timer has expired. Within a period corresponding to
approximately 5 * p9850, too many switching
operations have occurred at the safety-relevant inputs of the Control Unit,
or STO (including subsequent responses)
has been triggered too frequently via PROFIsafe/TM54F.
1001, 1002: Initialization error, change timer / check timer.
2000: Status of the STO selection on the Control Unit and Motor Module
are different.
2001: Feedback signal for safe pulse suppression on the Control Unit and
Motor Module are different.
2002: Status of the delay timer SS1 on the Control Unit and Motor Module
are different.
The drive-based "Safety Integrated" function on the Motor Module (MM)

has detected an error in the sign-of-life of
the safety data between the Control Unit (CU) and MM and initiated a
STOP A.
- there is either a DRIVE-CLiQ communication error or communication has
failed.
- a time slice overflow of the safety software has occurred.
The drive-based "Safety Integrated" function on the Motor Module (MM)
has detected a brake control error and initiated
a STOP A.
10:
- Parameter p1278 incorrectly set.
p1278 = 1 and p9602/p9802 = 0 (SBC
deactivated)).
- Ground fault in brake cable.
30:
Fault in "close holding brake" operation.
p1278 = 1 and p9602/p9802 = 0 (SBC
deactivated)).
40:
Fault in "brake closed" state.
60, 70:
Fault in the brake control circuit of the Control Unit or communication fault
between the Control Unit and Motor Module
(brake control).
Note:
The following causes may apply to fault values:
- motor cable is not shielded correctly.
- defect in control circuit of the Motor Module.
The Motor Module has detected a communications error with the higher-
level control or the TM54F to transfer the
safety-relevant information.
Note:
An internal error in the Safety Integrated software on the Motor Module
has occurred.
Note:
The "Safety Integrated" function on the Motor Module requires an

acceptance test.
Note:
130: Safety parameters for the Motor Module not available.
1000: Reference and actual checksum in the Motor Module are not
identical (booting).
- at least one checksum-checked piece of data is defective.
2000: Reference and actual checksum on the Motor Module are not
identical (commissioning mode).
- reference checksum incorrectly entered into the Motor Module (p9899
not equal to r9898).
2003: Acceptance test is required as a safety parameter has been changed.
2005: The safety logbook has identified that the safety checksums have
changed. An acceptance test is required.
3003: Acceptance test is required as a hardware-related safety parameter
has been changed.
9999: Subsequent response of another safety-related fault that occurred
when booting that requires an acceptance
test.
The drive-based "Safety Integrated" function is requesting synchronization

of the safety time slices on the Control
Unit and Motor Module. This synchronization routine was unsuccessful.
Note:
The Safety Integrated monitoring clock cycle cannot be maintained due to

the communication conditions requested
in the system.
Note:
An error has occurred when aligning the Safety Integrated monitoring
functions on the Control Unit (CU) and Motor
Module (MM). Control Unit and Motor Module were not able to determine
a common set of supported SI monitoring
functions.
- there is either a DRIVE-CLiQ communication error or communication has
failed.
- Safety Integrated software releases on the Control Unit and Motor
Module are not compatible with one another.
Note:
When accessing the Safety Integrated parameters for the Motor Module
(MM) on the CompactFlash card, an error
has occurred.
Note:
129: Safety parameters for the Motor Module corrupted.
131: Internal software error on the Control Unit.
255: Internal Motor Module software error.
The write request for one or several Safety Integrated parameters on the
Motor Module (MM) was rejected.
Note:
10: An attempt was made to enable the STO function although this cannot
be supported.
11: An attempt was made to enable the SBC function although this cannot
be supported.
13: An attempt was made to enable the SS1 function although this cannot
be supported.
14: An attempt was made to enable the safe motion monitoring function
with the higher-level control, although this
cannot be supported.
15: An attempt was made to enable the motion monitoring functions
integrated in the drive although these cannot be
supported.
16: An attempt was made to enable the PROFIsafe communication -
although this cannot be supported or the version
of the PROFIsafe driver used on the CU and MM is different.
See also: r9771 (SI common functions (Control Unit)), r9871 (SI common
functions (Motor Module)
The existing Control Unit software does not support the safe drive-based
motion monitoring function.
Note:
The actual checksum calculated by the Motor Module and entered in r9398
over the safety-relevant parameters does
not match the reference checksum saved in p9399 at the last machine
acceptance.
Safety-relevant parameters have been changed or a fault is present.
Note:
0: Checksum error for SI parameters for motion monitoring.
1: Checksum error for SI parameters for component assignment.
The monitoring function enabled in p9301, p9501, p9601 or p9801 is not

supported in this firmware version.
Note:
30: The firmware version of the Motor Module is older than the version of
the Control Unit.
The safety-relevant basic function "SOS/SLS" is not enabled in p9301

although other safety-relevant monitoring
functions are enabled.
Note:
The limit value for the function "Safely-Limited Speed" (SLS) is greater than
the speed that corresponds to an
encoder limit frequency of 500 kHz.
Note:
Maximum permissible speed.
It is not permissible to simultaneously enable the actual value

synchronization and a monitoring function with absolute
reference (SCA/SLP).
Note:
A DRIVE-CLiQ communication error has occurred form the Control Unit to
the power unit involved.
The computing time load might be too high.
xx = 0A hex:
Time slide overflow.

For 3P gating unit:

The last switching status word in the setpoint telegram is identified by the
end ID. Such an end ID was not found.
xx = 01 hex:
CRC error.
xx = 02 hex:
Telegram is shorter than specified in the length byte or in the receive list.
xx = 03 hex:
Telegram is longer than specified in the length byte or in the receive list.
xx = 04 hex:
The length of the receive telegram does not match the receive list.
xx = 05 hex:
The type of the receive telegram does not match the receive list.
xx = 06 hex:
The address of the component in the telegram and in the receive list do not
match.
xx = 07 hex:
A SYNC telegram is expected - but the receive telegram is not a SYNC
telegram.
xx = 08 hex:
No SYNC telegram is expected - but the receive telegram is one.
xx = 09 hex:
The error bit in the receive telegram is set.
xx = 10 hex:
The receive telegram is too early.
the power unit involved. The nodes do not
send and receive in synchronism.
xx = 21 hex:
The cyclic telegram has not been received.
xx = 22 hex:
Timeout in the telegram receive list.
xx = 40 hex:
Timeout in the telegram send list.

the power unit involved. Data were not
able to be sent.
xx = 41 hex:
Telegram type does not match send list.
Fault detected on the DRIVE-CLiQ component involved. Faulty hardware

cannot be excluded.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:

xx = 0B hex:
Synchronization error during alternating cyclic data transfer.
An internal software error in the power unit has occurred.

A DRIVE-CLiQ communication error has occurred from the power unit to
the Control Unit involved.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
xx = 11 hex = 17 dec:
CRC error and the receive telegram is too early.
xx = 01 hex = 01 dec:
Checksum error (CRC error).
xx = 12 hex = 18 dec:
The telegram is shorter than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 02 hex = 02 dec:
xx = 13 hex = 19 dec:
The telegram is longer than that specified in the length byte or in the
xx = 03 hex = 03 dec:

The nodes do not send and receive in synchronism.
Sign-of-life bit in the receive telegram not set and the receive telegram is
too early.
xx = 21 hex = 33 dec:
xx = 22 hex 34 dec:
xx = 40 hex = 64 dec:
xx = 62 hex = 98 dec:
Error at the transition to cyclic operation.

Data were not able to be sent.
xx = 41 hex:
Fault detected on the DRIVE-CLiQ component (power unit) involved. Faulty
hardware cannot be excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:
xx = 60 hex:
Response received too late during runtime measurement.
xx = 61 hex:
Time taken to exchange characteristic data too long.

xx = 0B hex:
The properties of the DRIVE-CLiQ component (power unit), specified by the

fault value, have changed in an incompatible
fashion with respect to the properties when booted. One cause can be, e.g.
that a DRIVE-CLiQ cable or
DRIVE-CLiQ component has been replaced.
Component number.
A fault occurred on the power unit that cannot be interpreted by the

Control Unit firmware.
Fault number.
Note:
If required, the significance of this new fault can be read about in a more
Communications error with an EEPROM or A/D converter.

80000000 hex:
- internal software error.
00000001 hex ... 0000FFFF hex:
- module fault.
For the initialization within the power unit, an internal software error has
occurred.
system.
pulse).
distance.

pulse).
The amplitude of the reference track signal (track R) does not lie within the
tolerance bandwidth for encoder 1.
The fault can be initiated when the unipolar voltage range is exceeded or
the differential amplitude is initiated.
xxxx hex:
xxxx = Signal level, track R (16 bits with sign).
mV +/- 500 mV.
The response threshold is < 1700 mV and > 3300 mV.
The nominal differential signal level of the encoder must lie in the range
375 mV to 600 mV (500 mV -25/+20 %).
The response threshold is > 750 mV.
A signal level of 500 mV peak value corresponds to the numerical value of
5333 hex = 21299 dec.
Note:
The analog value of the amplitude error is not measured at the same time
with the hardware fault output by the sensor
module.
satisfied:
- Sensor Module properties available (r0459.30 = 1, r0459.31 = 1).
- monitoring active (p0437.30 = 1, p0437.31 = 1).
evaluation module.
match the data.
requested.
Bit 6: Timeout when cyclically
Bit 8: Protocol is too long (e.
Bit 10: Frame error when reading
Bit 12: Data line signal level
Bit 13: Data line incorrect.
The EnDat encoder fault word supplies fault bits that have been set.
Bit 0: Lighting system failed.
Bit 1: Signal amplitude too low.
Bit 2: Position value incorrect.
Bit 3: Encoder power supply overvoltage condition.
Bit 4: Encoder power supply undervoltage condition.
Bit 5: Encoder power supply overcurrent condition.
Bit 6: The battery must be changed.
The amplitude (root of A^2 + B^2) for encoder 1 exceeds the permissible
tolerance.
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (16 bits with sign).
mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
Note for sensors modules for resolvers (e. g. SMC10):
The nominal signal level is at 2900 mV (2.0 Vrms). The response thresholds
are < 1070 mV and > 3582 mV.
6666 hex = 26214 dec.
Note:
The analog values of the amplitude error are not measured at the same
time with the hardware fault output by the
sensor module.
The amplitude of the rectified encoder signals A and B and the amplitude
from the roots of A^2 + B^2 for encoder 1
are not within the tolerance bandwidth.
yyyyxxxx hex:
mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
Note:
sensor module.
For a square-wave signal encoder (TTL. bipolar. double ended) the A* and
B* and R* signals are not inverted with
respect to signals A and B and R.
Note:
For CU310, CUA32, D410, SMC30 (only Order No. 6SL3055-0AA00-5CA0
and 6SL3055-0AA00-5CA1), the following
applies:
A squarewave encoder without track R is used and the track monitoring
(p0405.2 = 1) is activated.
For an HTL/TTL encoder, the speed difference has exceeded the value in
p0492 over several sampling cycles.
Encoder 1 is used as motor encoder and can be effective has fault response
to change over to encoderless operation.
See also: p0491 (Motor encoder fault response ENCODER), p0492 (Square-
wave encoder, maximum speed difference
per sampling cycle)
Encoder 1 power supply voltage fault.

Note:
If the encoder cables 6FX2002-2EQ00-.... and 6FX2002-2CH00-.... are
interchanged, this can result in the encoder
being destroyed because the pins of the operating voltage are reversed.
Bit 0: Undervoltage condition on the sense line.
Bit 1: Overcurrent condition for the encoder power supply.
For the actual value sensing, an error was detected on the module. As a
result of this error, it must be assumed that
the actual value sensing supplies an incorrect coarse position.
Fault in internal reference voltage of ASICs for encoder 1.

1: Reference voltage error.
2: Internal undervoltage.
3: Internal overvoltage.
The unipolar level (AP/AN or BP/BN) for encoder 1 is outside the

Bit 0 = 1: Either AP or AN outside the tolerance.
Bit 16 = 1: Either BP or BN outside the tolerance.
mV +/- 500 mV.
Note:
satisfied:
The amplitude of track A or B for encoder 1 exceeds the permissble
tolerance band.
yyyyxxxx hex:
mV (500 mV -25/+20 %).
The response threshold is > 750 mV. This fault also occurs if the A/D
converter is overcontrolled.
5333 hex = 21299 dec.
The nominal signal level is at 2900 mV (2.0 Vrms). The response threshold is
> 3582 mV.
6666 hex = 26214 dec.
Note:
sensor module.
The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 1 exceeds the
yyyyxxxx hex:
yyyy = Angle
xxxx = Amplitude, i.e. root from A^2 + B^2 (16 bits without sign)
mV (500 mV -25/+20 %).
The response threshold for (|A| + |B|) is > 1120 mV or the root of (A^2 +
B^2) > 955 mV.
299A hex = 10650 dec.
The angle 0 ... FFFF hex corresponds to 0 ... 360 degrees of the fine
position. Zero degrees is at the negative zero
crossover of track B.
Note:
sensor module.
After the fine synchronization using one reference mark or 2 reference
marks for distance-coded encoders, this fault
is no longer initiated, but instead, Alarm A31429.
After initializing the pole position using track C/D, Hall signals or pole
position identification routine, the zero mark
was detected outside the permissible range. For distance-coded encoders,
the test is carried out after passing 2 zero
marks. Fine synchronization was not carried out.
When initializing via track C/D (p0404) then it is checked whether the zero
mark occurs in an angular range of +/-18
° mechanical.
When initializing via Hall sensors (p0404) or pole position identification
(p1982) it is checked whether the zero mark
occurs in an angular range of +/-60 ° electrical.
yyyyxxxx hex
yyyy: Determined mechanical zero mark position (can only be used for
track C/D).
xxxx: Deviation of the zero mark from the expected position as electrical
angle.
Normalization: 32768 dec = 180 °
Absolute encoder:
When cyclically reading the absolute position, an excessively high
difference to the incremental position was
detected. The absolute position that was read is rejected.
Limit value for the deviation:
- EnDat encoder: Is supplied from the encoder and is a minimum of 2
quadrants (e.g. EQI 1325 > 2 quadrants, EQN
1325 > 50 quadrants).
- other encoders: 15 pulses = 60 quadrants.
Incremental encoder:
detected.
The DRIVE-CLiQ encoder supplies status information via bits in an internal
status/fault word.
Some of these bits cause this fault to be triggered. Other bits are status
displays. The status/fault word is displayed
in the fault value.
Bit 0: F1 (safety status display)
Bit 2: Lighting (reserved)
Bit 3: Signal amplitude (reserved)
Bit 4: Position value (reserved)
Bit 5: Overvoltage (reserved)
Bit 6: Undervoltage (reserved)
Bit 7: Overcurrent (reserved)
Bit 8: Battery (reserved)
Bit 16: Lighting (--> F3x135, x = 1, 2, 3)
Bit 17: Signal amplitude (--> F3x135, x = 1, 2, 3)
Bit 18: Singleturn position 1 (--> F3x135, x = 1, 2, 3)
Bit 19: Overvoltage (--> F3x135, x = 1, 2, 3)
Bit 20: Undervoltage (--> F3x135, x = 1, 2, 3)
Bit 21: Overcurrent (--> F3x135, x = 1, 2, 3)
Bit 22: Temperature exceeded (--> F3x405, x = 1, 2, 3)
Bit 23: Singleturn position 2 (safety status display)
Bit 24: Singleturn system (--> F3x135, x = 1, 2, 3)
Bit 25: Singleturm power down (--> F3x135, x = 1, 2, 3)
Bit 26: Multiturn position 1 (--> F3x136, x = 1, 2, 3)
Bit 28: Multiturn system (--> F3x136, x = 1, 2, 3)
Bit 29: Multiturn power down (--> F3x136, x = 1, 2, 3)
Bit 30: Multiturn overflow/underflow (--> F3x136, x = 1, 2, 3)
Bit 31: Multiturn battery (reserved)
status/fault word.
in the fault value.
Bit 16: Lighting (--> F3x135, x = 1, 2, 3)
Only for internal SIEMENS use.
Encoder functionality selected in p0404 is not operating correctly.

The fault value is a bit field. Every set bit indicates functionality that is
faulted.
The bit assignment corresponds to that of p0404 (e.g. bit 5 set: Error track
C/D).
See also: p0404 (Encoder configuration effective), p0491 (Motor encoder
fault response ENCODER)
The encoder speed is too high during while initializing the sensor.
The encoder evaluation for a motor with DRIVE-CLiQ has detected an
inadmissible temperature.
The fault threshold is 125 ° C.
Measured board/module temperature in 0.1 °C.
For a configured linear axis without modulo correction, the drive/encoder

has exceeded the maximum possible traversing
range. The value should be read in p0412 and interpreted as the number of
motor revolutions.
When p0411.0 = 1, the maximum traversing range for a configured linear
axis is defined to be 64x (+/- 32x) the setting
in p0421.
axis is preset to the highest possible value
and equals +/-p0412/2 (rounded to whole rotations). The highest possible
value depends on the pulse number
(p0408) and fine resolution (p0419).
When powered down, the drive/encoder was moved through a distance

greater than was parameterized in the tolerance
window. It is possible that there is no longer any reference between the
mechanical system and encoder.
absolute value.
The sign designates the traversing direction.
Note:
See also: p0413 (Measuring gear, position tracking tolerance window),
r0477 (Measuring gear, position difference)
The encoder with measuring gear no longer provides any valid signals.
The position tracking for the measuring gear cannot be reset.
A DRIVE-CLiQ communication error has occurred from the Control Unit to

the encoder involved.
xx = 0A hex:
Time slice overflow, encoder 1.
9: Time slice overflow of the fast (current controller clock cycle) time slice.
10: Time slice overflow of the average time slice.
12: Time slice overflow of the slow time slice.
999: Timeout when waiting for SYNO, e.g. unexpected return to non-cyclic
operation.

the Sensor Module.
yyyyxxxx hex
yyyy: Memory area involved.
xxxx: Difference between the checksum at POWER ON and the current
checksum.

The encoder was not successfully initialized.

1, 2, 3: Encoder initialization with the motor rotating.
A cycle requested from the Control Unit or RX/TX timing is not supported.
0: Application cycle is not supported.
1: DQ cycle is not supported.
2: Distance between RX and TX instants in time too low.
3: TX instant in time too early.
Bit 0: ALU watchdog has responded.
Bit 1: ALU has detected a sign-of-life error.
xx = 01 hex:
CRC error.
xx = 02 hex:
xx = 03 hex:
xx = 04 hex:
xx = 05 hex:
xx = 06 hex:
match.
xx = 07 hex:
telegram.
xx = 08 hex:
xx = 09 hex:
xx = 10 hex:

the encoder involved. The nodes do not
xx = 21 hex:
xx = 22 hex:
xx = 40 hex:

the encoder involved. Data were not able
to be sent.
xx = 41 hex:
cannot be excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:

xx = 0B hex:
Internal software error in the Sensor Module of encoder 1.

1: Background time slice is blocked.
2: Checksum over the code memory is not OK.
10000: OEM memory of the EnDat encoder contains data that cannot be
interpreted.
11000 - 11499: Descriptive data from EEPROM incorrect.
11500 - 11899: Calibration data from EEPROM incorrect.
11900 - 11999: Configuration data from EEPROM incorrect.
16000: DRIVE-CLiQ encoder initialization application error.
16001: DRIVE-CLiQ encoder initialization ALU error.
16002: DRIVE-CLiQ encoder HISI / SISI initialization error.
16003: DRIVE-CLiQ encoder safety initialization error.
16004: DRIVE-CLiQ encoder internal system error.
A DRIVE-CLiQ communication error has occurred from the Sensor Module

(encoder 1) involved to the Control Unit.
xx = 11 hex 17 dec:
xx = 01 hex = 01 dec:
xx = 12 hex = 18 dec:
xx = 02 hex = 02 dec:
xx = 13 hex = 19 dec:
xx = 03 hex = 03 dec:
xx = 14 hex = 20 dec:
The length of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 04 hex = 04 dec:
xx = 15 hex = 21 dec:
The type of the receive telegram does not match the receive list and the
xx = 05 hex = 05 dec:

too early.
xx = 21 hex = 33 dec:
xx = 22 hex = 34 dec:
xx = 40 hex = 64 dec:
xx = 62 hex = 98 dec:
xx = 41 hex:
Fault detected on the DRIVE-CLiQ component involved (Sensor Module for

encoder 1). Faulty hardware cannot be
excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:
xx = 60 hex:
xx = 61 hex:

xx = 0B hex:
The properties of the DRIVE-CLiQ component (Sensor Module for encoder

1), specified by the fault value, have
changed in an incompatible fashion with respect to the properties when
booted. One cause can be, e.g. that a
DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced.
Component number.
A fault occurred on the Sensor Module for encoder 1 that cannot be

Fault number.
Note:
A parameter of encoder 1 was detected as being incorrect.
It is possible that the parameterized encoder type does not match the
connected encoder.
The parameter involved can be determined as follows:
- determine the parameter number using the fault value (r0949).
- determine the parameter index (p0187).
yyyyxxxx dec: yyyy = supplementary information, xxxx = parameter
Supplementary information = 0:
No information available.
The component does not support HTL level (p0405.1 = 0) combined with
track monitoring A/B <> -A/B (p0405.2 = 1).
A code number for an identified encoder has been entered into p0400,
however, no identification was carried out.
Please start a new encoder identification.
Please select a listed encoder in p0400 with a code number < 10000.
This component does not support SSI encoders (p0404.9 = 1) without track
A/B.
For the SQW encoder, the value in p4686 is greater than that in p0425.
The DRIVE-CLiQ encoder cannot be used with this firmware version.

connected encoder.
Parameter number
The fault is only output for encoders with r404[0].10 = 1. This corresponds
to A31905 for encoders with r404[0].10 =
0.
system.
pulse).
distance.

pulse).
xxxx hex:
mV +/- 500 mV.
375 mV to 600 mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
Note:
module.
satisfied:
vSerial communication protocol transfer error between the encoder and
evaluation module.
match the data.
requested.
tolerance.
yyyyxxxx hex:
mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
The nominal signal level is at 2900 mV (2.0 Vrms). The response thresholds
are < 1070 mV and > 3582 mV.
6666 hex = 26214 dec.
Note:
sensor module.
yyyyxxxx hex:
mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
Note:
sensor module.
Note:
applies:
sampling cycle)

Note:

mV +/- 500 mV.
Note:
satisfied:
tolerance band.
yyyyxxxx hex:
mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
> 3582 mV.
6666 hex = 26214 dec.
Note:
sensor module.
yyyyxxxx hex:
yyyy = Angle
mV (500 mV -25/+20 %).
B^2) > 955 mV.
299A hex = 10650 dec.
Note:
sensor module.
° mechanical.
yyyyxxxx hex
track C/D).
angle.
Absolute encoder:
detected.

status/fault word.
in the fault value.
Bit 16: Lighting (--> F3x135, x = 1, 2, 3)
status/fault word.
in the fault value.
Bit 16: Lighting (--> F3x135, x = 1, 2, 3)

faulted.
C/D).

motor revolutions.
in p0421.

absolute value.
Note:

xx = 0A hex:

operation.
the Sensor Module.
yyyyxxxx hex
checksum.


The encoder serial number has changed. The change is only checked for
encoders with serial number (e.g. EnDat
encoders).
Cause:
Note:
is reset (p2507 = 1).
xx = 01 hex:
CRC error.
xx = 02 hex:
xx = 03 hex:
xx = 04 hex:
xx = 05 hex:
xx = 06 hex:
match.
xx = 07 hex:
telegram.
xx = 08 hex:
xx = 09 hex:
xx = 10 hex:

xx = 21 hex:
xx = 22 hex:
xx = 40 hex:

to be sent.
xx = 41 hex:
cannot be excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:

xx = 0B hex:

interpreted.

xx = 11 hex = 17 dec:
xx = 01 hex = 01 dec:
xx = 12 hex = 18 dec:
xx = 02 hex = 02 dec:
xx = 13 hex = 19 dec:
xx = 03 hex = 03 dec:
xx = 14 hex = 20 dec:
xx = 04 hex = 04 dec:
xx = 15 hex = 21 dec:
xx = 05 hex = 05 dec:

too early.
xx = 21 hex = 33 dec:
xx = 22 hex = 34 dec:
xx = 40 hex = 64 dec:
xx = 62 hex = 98 dec:
xx = 41 hex:

excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:
xx = 60 hex:
xx = 61 hex:

xx = 0B hex:

Component number.

Fault number.
Note:
connected encoder.
A/B.

connected encoder.
Parameter number
0.
system.
pulse).
distance.

pulse).
xxxx hex:
mV +/- 500 mV.
375 mV to 600 mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
Note:
module.
satisfied:
evaluation module.
match the data.
requested.
tolerance.
yyyyxxxx hex:
yyyyxxxx hex:
mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
Note:
sensor module.
Note:
applies:
sampling cycle)

Note:
mV +/- 500 mV.
Note:
satisfied:

tolerance band.
yyyyxxxx hex:
mV (500 mV -25/+20 %).
5333 hex = 21299 dec.
> 3582 mV.
6666 hex = 26214 dec.
Note:
sensor module.
yyyyxxxx hex:
yyyy = Angle
mV (500 mV -25/+20 %).
B^2) > 955 mV.
299A hex = 10650 dec.
Note:
sensor module.
° mechanical.
yyyyxxxx hex
track C/D).
angle.
Absolute encoder:
detected.
status/fault word.
in the fault value.
Bit 16: Lighting (--> F3x135, x = 1, 2, 3)

status/fault word.
in the fault value.
Bit 16: Lighting (--> F3x135, x = 1, 2, 3)
faulted.
C/D).


motor revolutions.
in p0421.

absolute value.
Note:

xx = 0A hex:

operation.

the Sensor Module.
yyyyxxxx hex
checksum.


The encoder serial number has changed. The change is only checked for
encoders with serial number (e.g. EnDat
encoders).
Cause:
Note:
is reset (p2507 = 1).

xx = 01 hex:
CRC error.
xx = 02 hex:
xx = 03 hex:
xx = 04 hex:
xx = 05 hex:
xx = 06 hex:
match.
xx = 07 hex:
telegram.
xx = 08 hex:
xx = 09 hex:
xx = 10 hex:

xx = 21 hex:
xx = 22 hex:
xx = 40 hex:

to be sent.
xx = 41 hex:
cannot be excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:

xx = 0B hex:

interpreted.

xx = 11 hex = 17 dec:
xx = 01 hex = 01 dec:
xx = 12 hex = 18 dec:
xx = 02 hex = 02 dec:
xx = 13 hex = 19 dec:
xx = 03 hex = 03 dec:
xx = 14 hex = 20 dec:
xx = 04 hex = 04 dec:
xx = 15 hex = 21 dec:
xx = 05 hex = 05 dec:
xx = 16 hex = 22 dec:
The address of the power unit in the telegram and in the receive list does
not match and the receive telegram is too
early.
xx = 06 hex = 06 dec:

too early.
xx = 21 hex = 33 dec:
xx = 22 hex = 34 dec:
xx = 40 hex = 64 dec:
xx = 62 hex = 98 dec:
xx = 41 hex:

excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:
xx = 60 hex:
xx = 61 hex:

xx = 0B hex:

Component number.

Fault number.
Note:
connected encoder.
A/B.

connected encoder.
Parameter number
0.
The temperature (r3666) measured using the Voltage Sensing Module

(VSM) has exceeded the threshold value
(p3668).
This fault can only be initiated if the temperature evaluation was activated
(p3665 = 2 for a KTY sensor or p3665 =
1 for a PTC sensor).
The hundred thousands and ten thousands position specifies the
component number of the VSM where the fault
occurred.
A DRIVE-CLiQ communications error has occurred from the Control Unit to
the Voltage Sensing Module (VSM).
xx = 0A hex:
Time slice overflow on the Voltage Sensing Module.

An error has occurred during the memory test on the Voltage Sensing
Module.


For the Voltage Sensing Module (VSM), a fault has occurred while
initializing.
the Voltage Sensing Module.
xx = 01 hex:
CRC error.
xx = 02 hex:
xx = 03 hex:
xx = 04 hex:
xx = 05 hex:
xx = 06 hex:
match.
xx = 07 hex:
telegram.
xx = 08 hex:
xx = 09 hex:
xx = 10 hex:
the Voltage Sensing Module. The nodes
do not send and receive in synchronism.
xx = 21 hex:
xx = 22 hex:
xx = 40 hex:

the Voltage Sensing Module. Data were
not able to be sent.
xx = 41 hex:

cannot be excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:

xx = 0B hex:
An internal software error in the Voltage Sensing Module (VSM) has

occurred.
A DRIVE-CLiQ communications error has occurred from the Voltage Sensing

Module (VSM) to the Control Unit.
xx = 11 hex = 17 dec:
xx = 01 hex = 01 dec:
xx = 12 hex = 18 dec:
xx = 02 hex = 02 dec:
xx = 13 hex = 19 dec:

too early.
xx = 21 hex = 33 dec:
xx = 22 hex = 34 dec:
xx = 40 hex = 64 dec:
xx = 62 hex = 98 dec:

xx = 41 hex:
Fault detected on the DRIVE-CLiQ component (Voltage Sensing Module)
involved. Faulty hardware cannot be
excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:
xx = 60 hex:
xx = 61 hex:

xx = 0B hex:
The properties of the DRIVE-CLiQ component (Voltage Sensing Module),

specified by the fault value, have changed
in an incompatible fashion with respect to the properties when booted.
One cause can be, e.g. that a DRIVE-CLiQ
cable or DRIVE-CLiQ component has been replaced.
Component number.
A fault occurred on the Voltage Sensing Module that cannot be interpreted

Fault number.
Note:
The set sampling time is invalid.

- not a multiple integer of the DP clock cycle.
Fault value (r0949, floating point):
Recommended valid sampling time.
The entered value is invalid.

Parameter number with the invalid value.
The commissioning mode setting was rejected because for at least one
drive belonging to the TM54F, the pulses
had not been suppressed.
Drive object number of the first drive found without pulse suppression.
A fault on the Terminal Module 54F (TM54) was acknowledged using the
safe acknowledgement (P10006).
An additional acknowledgement is also required at the Control Unit.
A drive object number was assigned twice. Each drive object number can
be assigned only once.
An error was detected when carrying out the test stop on the TM54F. As
fault response fail-safe input terminal signals
are transferred to the motion monitoring functions.
0xaaaabbcc hex
aaaa: Specifies the DOs or F-DIs (dependent on test step cc) for which the
expected state was not assumed. The
number is bit-coded (bit 0 = F-DI 0 or F-DO 0; bit 3 = F-DI 3 or F-DO 3).
bb: Precise problem:
0x01 = Internal error (error state on the opposite side).
0x02 = Error when comparing the switching signals.
0x03 = Internal error (delay time in the new state has still not expired).
cc: Test step of the test stop in which the error has occurred.
Test stop step cc for slave (hexadecimal):
0x00: Action: L1+ switched out, L2+ switched in - error: Master not in initial
state 0x00 and 0x0A.
0x0A: Action: L1+ switched out, L2+ switched in - error: Master not in state
0x15.
0x15: Action: L1+ switched out, L2+ switched out - error: F-DIs 0...4 of the
master do not correspond to those of the
slave (expected: level 0) or master not in state 0x20.
0x20: Action: L1+ switched out, L2+ switched out - error: Master not in
state 0x2B.
0x2B: Action: L1+ switched in, L2+ switched in - error: F-DIs 5...9 of the
master do not correspond to those of the
slave (expected: level 0) or master not in state 0x36.
0x36: Action: All slave DOs at OFF - error: Master not in state 0x41.
0x41: Action: All slave DOs at OFF - error: Master not in state 0x4C.
0x4C: Action: All slave-DOs at ON - error: State of DI 20...23 does not
correspond to the expected state (24V) or the
master not in state 0x57.
0x57: Action: All slave DOs at ON - error: Master not in state 0x62.
0x62: Action: All slave-DOs at OFF - error: State of DI 20...23 does not
correspond to the expected state (0V) or the
master not in state 0x6D.
0x6D: Action: All slave DOs at OFF - error: Master not in state 0x78.
0x78: Action: All slave-DOs at ON - error: State of DI 20...23 does not
For the 24 V power supply for the Terminal Module 54F (TM54F) an
undervoltage condition was detected.
As fault response fail-safe input terminal signals are transferred to the
Bit 0 = 1: Power supply undervoltage at connection X524.
Bit 1 = 1: Power supply undervoltage at connection X514.
For the 24 V power supply for the Terminal Module 54F (TM54F) an
overvoltage condition was detected.
The Terminal Module 54F (TM54F) has identified an error in the data cross
check between the two control channels.
aaaabbcc hex
aaaa: A value greater than zero indicates an internal software error.
bb: Data to be cross-checked that resulted in the error.
bb = 00 hex: p10000
bb = 01 hex: p10001
bb = 02 hex: p10002
bb = 03 hex: p10006
bb = 04 hex: p10008
bb = 05 hex: p10010
bb = 06 hex: p10011
bb = 07 hex: p10020
bb = 08 hex: p10021
bb = 09 hex: p10022
bb = 0A hex: p10023
bb = 0B hex: p10024
bb = 0C hex: p10025
bb = 0D hex: p10026
An internal software/hardware fault on the TM54F was identified.

The temperature measured using the temperature sensing on the TM54F

has exceeded the threshold value to initiate
this fault.
A communication error between the TM54F master and Control Unit or

between the TM54F slave and the Motor
Module was detected.
The safety input terminals or output terminals show a different state longer
than that parameterized in p10002.
yyyyxxxx hex
xxxx:
The safety-relevant input terminals F-DI indicate a discrepancy.
Bit 0: Discrepancy for F-DI 0
...
Bit 9: Discrepancy for F-DI 9
yyyy:
The safety-relevant output terminals F-DO indicate a discrepancy.
Bit 0: Discrepancy for F-DO 0
...
Bit 3: Discrepancy for F-DO 3
Note:
If several discrepancy errors occur consecutively, then this fault is only
signaled for the first error that occurs.
The following possibilities exist of diagnosing all of the discrepancy errors:
- in the commissioning software, evaluate the input states and output
states of the TM54F. All discrepancy errors are
displayed here.
- compare parameters p10051 and p10052 from the TM54F master and
TM54F slave for discrepancy.
The temperature measured using the temperature sensing of the Terminal

Module (TM) (r4105) has exceeded the
threshold value to initiate this fault (p4102[1]) - or the temperature
exceeded the alarm threshold (p4102[0]) for longer
than the dead time in parameter p4103.
Please note that this fault can only be initiated if the temperature
evaluation was activated (p4100 = 2 for KTY sensor
or p4100 = 1 for PTC sensor).
component number of the TMxx where the fault
occurred.
Alarm:
Please note that Fault F35207 only causes the drive to be shut down if
there is at least one BICO interconnection
between the drive and TM31.
The signals output from the Terminal Module 41 (TM41) for tracks A/B
have reached the limit frequency. The output
signals are no longer in synchronism with the specified setpoint.
The deviation between the setpoint and the output signals (track A/B)
exceeds the tolerance of +/-3 %. Difference
between internal and external measured values is too high.
The terminal module used has signaled an internal error. Signals of this
module may not be evaluated and are potentially
incorrect.
A function requested by the Control Unit is not supported by a DRIVE-CLiQ
component.
1: This Terminal Module TM31 does not support the motor
overtemperature time stage.
IMMEDIATELY
to the encoder involved.
xx = 01 hex:
CRC error.
xx = 02 hex:
xx = 03 hex:
xx = 04 hex:
xx = 05 hex:
xx = 06 hex:
match.
xx = 07 hex:
telegram.
to the encoder involved. The nodes do
not send and receive in synchronism.
xx = 21 hex:
xx = 22 hex:
xx = 40 hex:

to the encoder involved. Data were not
able to be sent.
xx = 41 hex:

cannot be excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:

(TM) to the encoder involved.
xx = 0B hex:
An internal software error in the Terminal Module (TM) has occurred.


(TM) to the Control Unit involved.
xx = 11 hex = 17 dec:
xx = 01 hex = 01 dec:
xx = 12 hex = 18 dec:
xx = 02 hex = 02 dec:
xx = 13 hex = 19 dec:
xx = 03 hex = 03 dec:
xx = 14 hex = 20 dec:
xx = 04 hex = 04 dec:
xx = 15 hex = 21 dec:
xx = 05 hex = 05 dec:
xx = 16 hex = 22 dec:
The address of the power unit in the telegram and in the receive list does
not match and the receive telegram is too
early.
xx = 06 hex = 06 dec:
The address of the power unit in the telegram and in the receive list do not
match.

too early.
xx = 21 hex = 33 dec:
xx = 22 hex = 34 dec:
xx = 40 hex = 64 dec:
xx = 62 hex = 98 dec:
xx = 41 hex:
Fault detected on the DRIVE-CLiQ component (Terminal Module) involved.

Faulty hardware cannot be excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:
xx = 60 hex:
xx = 61 hex:

xx = 0B hex:
The properties of the DRIVE-CLiQ component (Terminal Module), specified

by the fault value, have changed in an
incompatible fashion with respect to the properties when booted. One
cause can be, e.g. that a DRIVE-CLiQ cable
or DRIVE-CLiQ component has been replaced.
Component number.
A fault has occurred on the Terminal Module that cannot be interpreted by

the Control Unit firmware.
Fault number.
Note:
Temperature on DRIVE-CLiQ Hub Module has exceeded fault threshold.

Current temperature in 0.1°C resolution.
24 V power supply on DRIVE-CLiQ Hub Module has exceeded fault
threshold.
24 V power supply on DRIVE-CLiQ Hub Module has undershot fault

threshold.
A time slice overflow has occurred on the DRIVE-CLiQ Hub Module.

xx: Time slice number xx

Module in question.
xx = 01 hex = 1 dec:
match.
telegram.
xx = 10 hex = 16 dec:

Module in question. The nodes do not send
and receive in synchronism.
xx = 21 hex = 33 dec:
xx = 22 hex = 34 dec:
xx = 40 hex = 64 dec:
Module in question. Data were not able to
be sent.
xx = 41 hex = 65 dec:

cannot be excluded.
xx = 20 hex = 32 dec:
xx = 23 hex = 35 dec:
xx = 42 hex = 66 dec:
xx = 43 hex = 67 dec:

Module in question.
xx = 0B hex = 11 dec:
DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question

to Control Unit.
to Control Unit.
xx = 11 hex = 17 dec:
Checksum error (CRC error) and receive telegram is too early.
xx = 01 hex = 01 dec:
xx = 12 hex = 18 dec:
xx = 02 hex = 02 dec:
xx = 13 hex = 19 dec:
xx = 03 hex = 03 dec:
xx = 14 hex = 20 dec:
xx = 04 hex = 04 dec:
xx = 15 hex = 21 dec:
xx = 05 hex = 05 dec:

to Control Unit.
too early.
xx = 21 hex = 33 dec:
xx = 22 hex = 34 dec:
xx = 40 hex = 64 dec:
xx = 62 hex = 98 dec:
to Control Unit.
xx = 41 hex = 65 dec:
Fault detected on the DRIVE-CLiQ component (DRIVE-CLiQ Hub Module)

involved. Faulty hardware cannot be
excluded.
xx = 20 hex = 32 dec:
xx = 23 hex = 35 dec:
xx = 42 hex = 66 dec:
xx = 43 hex = 67 dec:
xx = 60 hex = 96 dec:
xx = 61 hex = 97 dec:

to Control Unit.
xx = 0B hex = 11 dec:
The properties of the DRIVE-CLiQ component (DRIVE-CLiQ Hub Module)

specified by the fault value have changed
in an incompatible fashion with respect to the properties when booted.
One cause can be, e.g. that a DRIVE-CLiQ
cable or DRIVE-CLiQ component has been replaced.
Component number.
A fault occurred on the DRIVE-CLiQ Hub Module that cannot be interpreted

Fault number.
Note:
A fault has occurred at the drive object at the DRIVE-CLiQ socket X100.
First fault that has occurred for this drive object.
The configured transfer end time when transferring the cyclic actual values
was exceeded.
the controller extension involved.
xx = 0A hex:

xx = 01 hex:
CRC error.
xx = 02 hex:
xx = 03 hex:
xx = 04 hex:
xx = 05 hex:
xx = 06 hex:
match.
xx = 07 hex:
telegram.
xx = 08 hex:
xx = 09 hex:
xx = 10 hex:
the controller extension involved. The
nodes do not send and receive in synchronism.
xx = 21 hex:
xx = 22 hex:
xx = 40 hex:

the controller extension involved. Data
were not able to be sent.
xx = 41 hex:

cannot be excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:

xx = 0B hex:
A DRIVE-CLiQ communications error has occurred from the controller

extension involved to the Control Unit.
xx = 0A hex:
xx = 11 hex:
xx = 01 hex:
CRC error.
xx = 12 hex:
xx = 02 hex:
xx = 13 hex:
xx = 03 hex:
xx = 14 hex:
xx = 04 hex:

xx = 1A hex:
too early.
xx = 21 hex:
xx = 22 hex:
xx = 40 hex:
xx = 62 hex:

xx = 41 hex:
cannot be excluded.
xx = 20 hex:
xx = 23 hex:
xx = 42 hex:
xx = 43 hex:
xx = 60 hex:
xx = 61 hex:

xx = 0B hex:
The cooling system signals a general fault.
The conductivity of the cooling liquid has exceeded the selected fault
threshold (p0269[2]).
See also: p0261 (Cooling system, starting time 2), p0262 (Cooling system,
fault conductivity delay time), p0266
(Cooling system, feedback signals, signal source)
The feedback signal of the ON command of the cooling system is missing.

- after the ON command, the feedback signal has not been received within
the selected starting time (p0260).
- the feedback signal has failed in operation.
See also: p0260 (Cooling system, starting time 1), r0267 (Cooling system
status word)
The drive converter cooling system signals that the cooling liquid flow is too
low.
- after the ON command, the feedback signal has not been received within
the selected starting time (p0260).
- in operation, the feedback signal has failed for longer than the permitted
failure time (p0263).
See also: p0260 (Cooling system, starting time 1), p0263 (Cooling system
fault liquid flow, delay time), r0267 (Cooling
system status word)
The liquid leakage monitoring function has responded.
Caution:
Before this fault is re-parameterized as an alarm, you must ensure that the
drive is shut down if cooling water is lost.
See also: r0267 (Cooling system status word)
POWER ON
The firmware version in the Power Stack Adapter (PSA) is too old and does
not support the liquid cooling.
The cooling liquid intake temperature has exceeded the permanently set
fault threshold.
The excitation sequence control signals a fault.
Fault value (r0949, hexadecimal):
Bit 0:
When powered down or when powering down the excitation, the signal
"excitation ready to be powered up feedback
signal" was not received within the monitoring time.
Bit 1:
After an ON command, the signal "excitation ready feedback signal" was
not received within the monitoring time.
Bit 2:
After the pulses were enabled, the signal "excitation operational feedback
signal" was not received within the monitoring
time.
Bit 3:
The "excitation group signal fault" signal is present.
An internal software error has occurred.

Fault value (r0949, hexadecimal):
The "Safe Torque Off" (STO) function has been selected on the Control Unit
(CU) using the input terminal and is
active.
Note:
The "Safe Stop 1" (SS1) function has been selected on the Control Unit (CU)
and is active.
Note:
The temperature difference between the chip and heat sink has exceeded
the permissible limit value (r0293) (for
chassis power units only). Depending on p0290, a suitable overload
response is initiated.
See also: r0037, r0293 (Power unit alarm threshold model temperature)
The "Safe Torque Off" function was selected on the Motor Module (MM)
via the input terminal and is active.
Note:
The "Safe Stop 1" function (SS1) was selected on the Motor Module (MM)
and is active.
Note:
The power unit has detected at least one fault.

tolerance.
yyyyxxxx hex:
yyyy = Angle
mV (500 mV -25/+20 %).
The response threshold is < 300 mV (observe the frequency response of the
encoder).
299A hex = 10650 dec.
< 1414 mV (1.0 Vrms).
3333 hex = 13107 dec.
Note:
sensor module.
tolerance.
yyyyxxxx hex:
yyyy = Angle
mV (500 mV -25/+20 %).
encoder).
299A hex = 10650 dec.
< 1414 mV (1.0 Vrms).
3333 hex = 13107 dec.
Note:
sensor module.
The motor encoder has detected at least one fault.

tolerance.
yyyyxxxx hex:
yyyy = Angle
mV (500 mV -25/+20 %).
encoder).
299A hex = 10650 dec.
< 1414 mV (1.0 Vrms).
3333 hex = 13107 dec.
Note:
sensor module.
The motor encoder has detected at least one fault.

VSM: Group signal
The Terminal Module has detected at least one fault.
The DRIVE-CLiQ Hub Module has detected at least one fault.

the power suppl


Most porbably due to a short circuit of the 12V supply for the digital inputs

Internal error

Internal error
Internal error
(Motor stall protection)

(Motor thermal protection)
(Warning can be activated in Five In One applications) (not sure what is going on
here !!)
The values in the Fault History, MWh counters or operating day/hour counters
might have been changed in the previous mains interruption
The change of application has failed
The load of the segments is not equal
The converter overtemperature warning: Overtemp. Trip limit minus 5 deg. C
The current of input Iin+ < 4 mA (Warning can be activated in Five in One
applications)
Warning can be activated in Five In One applications)
The frequency converter has measured too high a current (> 4* In) in the motor
output:
- sudden heavy load increase
- short circuit in the motor cables
- unsuitable motor
Input line phase is missing

Current measurement has detected that there is no current in one motor phase
- brake resistor not installed

- brake resistor broken
- Brake chopper broken
Temperature of heat sink below -10 deg. C
Temperature of heat sink over 70 deg. C
The motor stall protection has tripped

The converter motor temperature model has detected motor overheat
- motor is overloaded
The motor underload protection has tripped
Wrong analogue input polarity
Component failure on control board
Reading of the option board has failed
The voltage of the internal DC-Link of the converter has exceeded the nominal
voltage by 35%
- deceleration time too fast
- high overvoltage spikes at utility
+10 V reference shorted on control board or option board

+24V supply shorted on control board or option board
Parameter restoring error
- interference fault
- component failure
Parameter restoring error
- component failure
- Interference fault
- Component failure
The connection between panel and the frequency converter is not working
Thermistor input of the I/O expander board has detected increase of the motor
temperature
Current measurement detected that the sum of the motor phase current is not
zero.
- insulation failure in the motor or the cables
The current in the analog input Iin is below 4 mA
- signal source has failed
- control cable is broken
The converter has detected faulty operation in the gate drivers or IGBT bridge
- component failure
Fault is detected in external fault digital input
Charging switch open when START command active
- component failure
DC-Bus voltage has gone below 65% of the nominal voltage
- most common reason is failure of the utility supply
- internal failure of the frequency converter can also cause an undervoltage trip

The braking transistor reached its overload level.
The wrong braking resistor is installed

• The connection was lost after establishing initial communication.
• Only detected when the run command frequency reference is assigned to an
option card.
- No signal was received from the PLC

- Faulty communications wiring or an existing
short circuit
Control data was not received for the CE detection time set to H5-09.
Faulty communications wiring or an existing
short circuit
Communication data error occurred due to
noise
- Motor parameters are set improperly

- Torque limit is too low
- Load inertia is too big
- There is a self-diagnostic error in the control

circuit
- Connector on the operator is damaged
Control circuit is damaged
- There is a connection error

- Drive fails to operate properly due to noise
interference
- There is an error in EEPROM control circuit

- The power supply was switched off while
parameters were being saved to the drive
There is a faulty connection between the

terminal board and the control board
Hardware is damaged
Hybrid IC failure on the power board
Hardware is damaged
Hardware is damaged
Hardware is damaged
- Load is too heavy
- Acceleration and deceleration times are set too
short
- The load is locked up
- Parameters are not set appropriately
- Incorrect speed feedback scaling when using
terminal RP as speed feedback input in V/f
control
- Motor brake is en
PG encoder is disconnected, improperly

wired, or the PG option card or PG encoder are
damaged
- Noise interference along the PG cable

- PG cable is not wired properly
- PG option card or the PG encoder are damaged
- The Z Pulse offset is not set properly to E5-11

- An external force on the load side caused the
motor to move
affecting the A or B pulse
- PG encoder is disconnected, improperly wired, or the PG option card or PG
- The Z Pulse offset is not set properly to E5-11

affecting the A or B pulse
- PG encoder is disconnected, improperly
wired, or the PG option card or PG encoder are
damaged
- Disconnection in the motor coil winding
- Loose output terminals
Fault output by DriveWorksEZ
- Data has not been received from the PLC
- An external fault was received from the PLC

and F6-03 is set to a value other than 3.
- Problem with the PLC program
- An external device tripped an alarm function

- Wiring is incorrect
- Multi-function contact input setting is
incorrect
incorrect

incorrect

incorrect

incorrect

incorrect

incorrect

incorrect

incorrect
- Noise has corrupted data while writing to the

EEPROM
- Hardware problem
Internal cooling fan has malfunctioned
Fault detected in the internal cooling fan or
magnetic contactor to the power supply.
- Parameters are set inappropriately

- Incorrect PID feedback wiring
- There is a problem with the feedback sensor
- Parameters are set inappropriately

- Incorrect PID feedback wiring
- There is a problem with the feedback sensor
- Motor insulation is damaged

- A damaged motor cable is creating a short
circuit
- Excessive leakage current at the drive output
- The drive started to run during a current offset
fault or while coasting to a stop
- Hardware problem
- The output cable is disconnected

- The motor winding is damaged
- The output terminal is loose
- The rated current of the motor being used is
less than 5% of the drive rated current
- An output transistor is damaged
- A single-phase motor is being used
- Phase loss has occurred on the output side of

the drive
- Terminal wires are loose on the output side of
the drive
- The output circuit is damaged
- Motor impedance or motor phases are uneven
The gate drive board in the power unit is

damaged.
Cable to the current detection circuit in the
power unit is damaged or not connected
properly.
Cable between the output rector and the power
unit is loose or not connected.
- The node setup terminal closed during run.

A Run command was issued while the node setup function was active.
- The motor has been damaged due to
overheating or the motor insulation is
damaged
- One of the motor cables has shorted out or
there is a grounding problem
- The load is too heavy
- The acceleration or deceleration times are too
short
- The drive is atte
- The option card installed into port CN5-A is

incompatible with the drive
- A PG option card is connected to option port
CN5-A
The option card connection to port CN5-A is

faulty
Option card or hardware is damaged
- The option card installed into port CN5-B is

- A communication option card has been
installed in option port CN5-B
The option card connection to port CN5-B is

faulty
- An option card of the same type is already

installed in option port CN5-A
- An input option card is already installed in
option port CN5-A

The option card installed into port CN5-C is

The option card connection to port CN5-C is

faulty.
- An option card of the same type is already

installed in option port CN5-A or CN5-B.
An input option card is already installed in

option port CN5-A or CN5-B.
Three PG option boards are installed.
- Surrounding temperature is too high

- Load is too heavy
- Internal cooling fan is stopped
Surrounding temperature is too high

Load is too heavy
Motor has overheated

- Load is too heavy
- Cycle times are too short during acceleration
and deceleration
- A general-purpose motor is driven below the
rated speed with a high load
- The output voltage is too high
- The wrong motor rated current is set to E2-01
- The maximum
- Load is too heavy

- Acceleration or deceleration time is too short
- The output voltage is too high
- Drive capacity is too small
- Overload occurred when operating at low
speeds
- Excessive torque compensation
- Parameters related to Speed Search are s
- Parameter settings are not appropriate for the

load
- Fault on the machine side (e.g., machine is
locked up)
Parameter settings are not appropriate for the

load
Overtorque triggered mechanical weakening

detection level set to L6-08
- Excessive load inertia

- Motor is driven by the load
- Something on the load side is restricting
deceleration
- The overload time during High Slip Braking
is too short
The external operator has been disconnected from the drive.

Note: An oPr fault will occur when all of the following conditions are true:
• Output is interrupted when the operator is disconnected (o2-06 = 1).
• The Run command is assigned to the operator (
- Overshoot is occurring
- Incorrect speed feedback scaling if terminal
RP is used as speed feedback input in V/f
control
- Incorrect number of PG pulses has been set
- Inappropriate parameter settings
Voltage in the DC bus has exceeded the overvoltage detection level.

• For 200 V class drives: approximately 410 V
• For 400 V class drives: approximately 820 V (740 V when E1-01 is less than 400)
- Decelerat
- Drive input power has an open phase or has a large imbalance of voltage
between phases. Detected when
L8-05 is set 1 (enabled).
- There is phase loss in the drive input power
- There is loose wiring in the drive input power
terminals
- There is excessiv
- PG cable is disconnected
- PG cable wiring is wrong
- PG has no power
- PG encoder brake is clamped shut
PG cable is disconnected
The resistance of the braking resistor is too low.

-The proper braking resistor option has not
been installed
-A regenerative converter, regenerative unit, or
braking unit is being used
- Braking resistor protection was triggered.

Fault detection is enabled when L8-01 = 1 (disabled as a default).
- Deceleration time is too short and excessive
regenerative energy is flowing back into the
drive
- Excessive braking inertia
- The braking ope
- The built-in dynamic braking transistor failed.

- The braking transistor is damaged
- The control circuit is damaged
- IGBT fault
- IGBT short circuit detection circuit fault
- The number of Speed Search restarts exceeded the value set to b3-19.
- Parameters related to Speed Search are set to
the wrong values
- The motor is coasting in the opposite direction
of the Run command
- Motor pull out or step out has occurred. Motor has exceeded its pull-out torque.
- The wrong motor code is set (Yaskawa motors
only)
- Load is too heavy
- Load inertia is too heavy
- Acceleration and deceleration times are too
short
- Speed response is
- Position deviation during zero servo.

- Torque limit is set too low
- Excessive load torque
- Noise interference along PG encoder wiring
- The thermistor that detects motor temperature has become disconnected.

- The motor thermistor is not connected
properly.
- The current has fallen below the minimum value set for torque detection (L6-02)
for longer than the
allowable time (L6-03).
- Parameter settings are not appropriate for the
load
- There is a fault on the machine side
- The current has fallen below the minimum value set for torque detection (L6-05)
for longer than the
allowable time (L6-06).
Parameter settings are not appropriate for the
load
There is a fault on the machine side
- The operation conditions matched the conditions set to L6-08.

- Undertorque was detected and matched the
conditions for mechanical loss detection set to
L6-08
- Current flow has become unbalanced.

- The internal current sensor has detected a
current unbalance situation.
Voltage in the DC bus fell below the undervoltage detection level (L2-05).
• For 400 V class drives: approximately 380 V (350 V when E1-01 is less than 400)
The fa
- Voltage is too low for the control drive input power.

- In drive models CIMR-Ao2A0004 to
2A0056 or 4A0002 to 4A0031, L2-02 was
changed from its default value without
installing a Momentary Power Loss Ride-Thru
unit
- Control power supply wiring is damag
- The soft-charge bypass circuit failed.

- The relay or contactor on the soft-charge
bypass circuit is damaged
- Voltage drop in the gate drive board circuit

- Not enough power is being supplied to the gate
drive board.
- Problem detected with the voltage on the output side of the drive.
- Hardware is damaged
Power modules for motor de-excitation locked
Brake control, brake engaged (see chapter 6.9)
Brake control, break released (see chapter 6.9)
Measurement of the motor stator resistance.
Motor is decelerated by a DC-voltage at the output.
Modulation is switch off after DC-braking (see chapter 6.9 "DC-braking")
Acceleration with the adjust ramps in clockwise direction of rotation.

Acceleration/deceleration phase is completed and it is drive with constant
speed/frequency in clockwise direction of rotation
It is stopped with the adjusted ramp times in clockwise direction of
rotation.
The message is output if the output current reaches the hardware current
limit.
This message is displayed if during acceleration the load is limited to the
adjusted load level
This message is displayed if during deceleration the load is limited to the
adjusted load level or the DC-link current to the adjusted voltage level.
No direction of rotation pre-set modulation is off.

Power circuit jot ready or not identified by the control.
control release (terminal ST) is not switched.
This message is displayed during a positioning process
no modulation after Power-Off.
This specified position cannot be reached within the pre-set ramps. This
abort of the positioning can be programmed.
Depending on the programming of the function (see chapter 6.9, power-off
function) the inverter restarts automatically upon system of recovery or
after a reset.
Positioning function active (FS-G)
Acceleration with the adjusted ramp times in anti- clockwise direction of
rotation.
Acceleration/deceleration phase is completed and it is drive with constant
speed/frequency in clockwise direction of rotation
it is stopped with the adjusted ramp times in anti-clockwise direction of
rotation.
The drive signals that it is ready to start the positioning process.
this message is displayed if during constant operation the load is limited to
the adjusted current limit
Search for reference point approach active.
Speed search function active, that means that the inverter attempts to
synchronize onto a running down motor.
The message is output if as response to a warning signal the quick-stop
function becomes active
Error can occur in the case of switched on brake control (see chapter 6.9.5)
if
-the load is below the minimum load level (Pn. 43) at start up or the
absence of an engine phase was detected.
-the load is too high and the hardware current limit is reached
Adjusted monitoring time (Watchdog) of communication between operator

and PC/operator and inverter has been exceeded
Error: During the automatic motor stator resistance measurement.
Counter overflow encoder channel 1.
Counter overflow encoder channel 2.
Error: Over temperature of motor PTC. Error can only be rest at E.ndOH, if
PTC is again low-resistance. Causes:
- resistance at the terminals T1/T2 > 1650 Ohm
- motor overloaded
- line breakage to the temperature sensor
Error: Driver relay. Relay for driver voltage on power circuit has not picked
up even though control release was given.
After reset the operation is again possible (without storage in the EEPROM)
Error: External Error. Is triggered if a digital input is being programed as

external error input and trips.
Cable breakage at the resolver or incremental encoder
invalid encoder interface identifier
Error: Encoder interface identifier has changed, it must be confirmed over
ec.0 or ec.10
Hardware failure at the NPN/PNP change-over or at the start/stop
measurement
MFC not booted
Load shunt relay has not picked up. Occurs for a short time during the
switch-on phase but must automatically be reset immediately. If the error
message remains the following causes may be applicable:
- load-shunt defective
- input voltage or too low
-high losses in the supply cable
- braking resistor wrongly connected or damaged
- braking module defective
Motor temperature switch or PTC at the terminals T1/T2 is again in the

normal operating range. The error can be reset now
Temperature of the heat sink is again in the permissible operating range.
The error can be reset now.
No longer overheating in the interior E.OHI, interior temperature has fallen
by at least 3 degrees.
No more overload. OL- counter has reached 0% after the error E.OL a
cooling phase must elapse. This message appears upon completion of the
cooling phase. The error can be reset now. The inverter must remain
switched on during the cooling phase
The cooling time has elapsed. The error can be reset.

Occurs if the specified peak current is exceeded. Causes:
- acceleration ramps too short
-the load is too big at turned off acceleration stop and turned off constant
current limit
- short-circuit at the output
- deceleration ramp too short
-motor cable too long
- EMC
- DC brake at high ratings active (see 6.9.3)
Error: over temperature of power module. Error can be only be reset at

E.nOH causes:
-insufficient air flow at the heat sink (soiled)
-ambient temperature too high
- ventilator clogged
Electronic motor protective relay has tripped.

Error: overheating in the interior: error can only be reset at E.nOHI if the
interior temperature has dropped by at least 3 degrees
Error: Overload error can only be reset at E.nOL if OL-counter reaches 0%
again. Occurs if an excessive load is applied longer than for the permissible
time (see technical data): causes :
- poor control adjustment (overshooting)
-mechanical fault or overload in the application
-inverter not correctly dimensioned
-motor wrongly wired
- encoder damaged
Occurs if the standstill constant current is exceeded (see technical data and
overload characteristics). The error can only be reset if the cooling time has
elapsed and E.nOL2 is displayed
Voltage in the DC-link circuit is too high. Occurs when the DC bus voltage
rises above the permissible value. Causes:
- poor controller adjustment (overshooting)
-input voltage too high
-interference voltages at the input
-deceleration ramp too short
-braking resistor defective or too small
Real speed is bigger than the max. output speed.

Error in the power factor control
The drive has driven onto the right limit switch. Programmed response
Error, restart after reset ( see chapter 6.7 , Response to errors or warning
messages)
The drive has driven onto the left limit switch. Programmed response Error,
restart after reset (see chapter 6.7 Response to errors or warning
messages)
Error: General power circuit fault
Error: During the initialisation the power circuit could not be recognized or
was identified as invalid
Error: Power circuit identification was changed: with a valid power circuit
this error can be reset by writing to SY.3 If the value displayed in SY.3 is
written, only the power-circuit parameters are reinitialized. If any other
value is written, then the default set is loaded. on some systems after
writing Sy.3 a power-on reset is necessary.
Error: Parameter value could not be written to the power circuit.

Acknowledgment from LT <> OK
Error: Software version for power circuit and control card are different .
Error cannot be reset (only at F5-G B-housing)
Synchronization over sercos-bus not possible. Programmed response Error,
restart after reset
It has been attempted to select a locked parameter set. Programmed
response Error, restart after reset
The target position lies outside of the limit defined with the right software
limit switch. Programmed response Error, restart after reset
The target position lies outside of the limit defined with the left software
limit switch. Programmed response Error, restart after reset
Error: under voltage (DC-Link circuit) Occurs if DC-link voltage fails below
the permissible value causes:
-input voltage too low or instable
-inverter rating too small
-voltage losses through wrong cabling
-the supply voltage through generator/transformer breaks down at very
short ramps
-at F5-G housing B E.Up is also displayed if no communication takes place
between power circuit and control card
-jump factor (Pn.56) too small
-if a digital input was programmed as external error input with error
message E.Up (Pn.65)
One phase of the input voltage is missing (ripple-detection)

Warning: watchdog for communication between operator/control card or
operator/PC has responded. The response to this warning ca be
programmed.
the motor temperature has exceeded and adjustable warning level. The
switch off time is started. The response to this warning can be
programmed. This warning can be generated only with a special power
circuit
This warning is triggered via an external input. The response to this warning
can be programmed.
The motor temperature is again below the adjusted warning level. The
switch off time Is stopped.
The heat sink temperature is again below the adjusted warning level
The temperature in the interior of the inverter is again blow the warning
threshold
OL counter has reached 0% the warning "overload" can be reset
The cooling time after "warning! Overload during standstill" has elapsed.
The warning message can be reset.
A level can be defined when it is exceeded this warning is output. The
response to this warning can be programmed.
Warning: electronic motor protective relay has tripped. The response to
this warning can be programmed.
The temperature in the interior of the inverter lies above the permissible
level. The switch off time was started. The programmed response to this
warning message is executed.
A level between 0 and 100% of the load counter can be adjusted when it is
exceeded this warning is output. The response to this warning can be
programmed
The warning is output when the standstill continuous current is
exceeded( see technical data and overload characteristics) . The response
to this warning can be programmed. The warning message can only be
reset after the cooling time has elapsed and A.nOL2 is displayed
The drive has driven onto the right limit switch. The response to this can be
programmed.
The drive has driven onto the left limit switch. The response to this warning
can be programmed.
Synchronisation over sercos-bus not possible. The response to this can be
programmed.
it has been attempted to select a locked parameter set. The response to
this warning can be programmed.
The target position ls outside of the limit defined with the right software
limit switch. The response to this warning can be programmed.
The target position lies outside of the limit defined with the left software
limit switch. The response to this warning can be programmed.
AI2 signal out of range

Incorrect DB resistor settings
Short-circuit output from braking unit
Charging relay control condition or charging resistor damaged
Improper DC bus charging condition (thyristors)
Control card internal memory
Power card internal memory
The output contractor remains closed although the opening conditions

have been met
short circuit or grounding at the drive output
the power card is different from the card stored
The power card is incompatible with the control card
Communication condition between the internal cards
Internal data inconsistent

The option installed in the controlled is not recognized
Initialisation of the drive is incomplete
The control section power supply is incorrect
The current measurements are incorrect
The input stage is not operating correctly
The drive temperature sensor is not operating correctly

Detected fault on the electronic time measurement component
internal microprocessor event
• Motor parameters are not set correctly
• Excessive inertia or load
• Mechanical locking
Detected fault with the drive's Power Removal safety function
• Short-circuit or grounding at the drive output
• Significant earth leakage current at the controller output if several motors
are connected in parallel


Instability
Overhauling load
Encoder feedback signal missing.
• Special motor, or motor power not suitable for the drive

• Motor not connected to the drive
Controller inside card

communication interpretation
Interruption in communication on the CANopen bus.
An external device depending on user

a communication network
The output contractor remains open although the closing conditions have
been met
the drive is not turned on even though (Mains V. timeout) (LCt) has elapsed
Loss of the 4 to 20 mA reference on analog input AI2, AI3 or AI4

Zero fluid
• Braking ramp too short

• Overhauling load
• Ambient temperature too high

• Drive ventilation blocked
• Drive cooling fan failure
Process overload (consult the programming manual CD-ROM
• Motor power rating too small for the application

• Overload setting incorrect for the motor full-load rating
• Output phase loss (see OPF1)
Loose connection causing loss of one phase at controller output
• Motor not connected or motor power too low
• Output contactor open
• Instantaneous instability in the motor current
• Line voltage too high

• Disturbances in the line
supply
overheating of the PTC1 probes detected
overheating of the PTC2 probes detected
overheating of the PTC probes detected on input LI6
PTC1 probes open or short circuited
PTC2 probes open or short circuited
PTC probes on input LI6 open or short-circuited

Power component
short circuit at drive output
Interruption in communication on the Modbus bus
Communication with PowerSuite™ software
Communication with the graphic display terminal
PID feedback below the lower limit
Switch to torque limitation
Drive overheated
Process under load
• Option card changed or removed

• The current configuration is inconsistent
Invalid configuration. The configuration loaded in the controller via the bus
or network is inconsistent
The [CARDS PAIRING] (PPI-) function has been configured and a drive card
has been changed
• Controller incorrectly supplied or a fuse blown
• Loss of one phase
• 3-phase ATV61 used on a single phase line supply
• Unbalanced load Monitors only with the drive on load.
• The [Power Identification] (Prt) parameter is incorrect.

• Control card replaced by a control card configured on a drive with a
different rating
• Line supply too low

• Transient voltage dip
• Damaged pre-charge resistor
* Contact technical support
- Check the converter for correct message.
- If ABB converter says "Supply Phase" but supply phase is ok, then
probably the rectifier circuit, ie NINP board is faulty
- Converter is in "stopped mode" and cannot be started
- Service switch in wrong postion
See F0022
- Alarm A017 ?? Cannot be started by the PMU with SS switch activated?

SS changed position, however, r0012 (r050 / r051 (MM4) (or similar ) for
active BICO DSET did not changed? ==> PSU or IGD.
Dummy plug for the keypad not (properly) engaged, or PMU controller
missing or faulty
The service switch is in the wrong position (is set in SERVICE MODE)
The reason is that the Elektronikon software has been updated with a new
functionality. The New Elektronikon software has the possibility to put a
holding torque after a stop to prevent backward rotation. This is with a new
stop command which is introduce
- Cause / trigger by the converter condition

* Converter was set to LOCAL when it was suppose to be on REMOTE.
This is possible when performming programming procedures on the

converter.
* In running condition:
1. For Maint motor converter, the elektronikon K05 relay should be closed.
2. For Dryer converter (if present) the elektronikon K02 relay should be
closed.
3. For Fan converter (if prese

1. For Maint motor converter, the elektronikon K05 relay should be closed..
Converter is in "stopped mode" and cannot be started
Converter problem
No idea
Please contact ABB

Typically due to earth fault in motor or motor cables
Motor thermal protection mode selected as THERMISTOR and the

Intermediate circuit DC voltage is excessive. DC overvoltage trip limit is 1.3

U1max, where U1max is the maximum value of the mains voltage range.
For 400 V units, U1max is 415V. The actual voltage in the intermediate
circuit corresponding to the mains vo
Motor temperature is too high (or appears to be too high). This can be
caused by excessive load, insufficient motor power, inadequate cooling or
incorrect start-up data.
The ACS 600 / 800 internal temperature is excessive. The trip level of
inverter module temperature is 125 deg. C
- Communication cable
- Elektronikon module
- Converter communication card
- Modbus adapter card
- Communication cable
- Elektronikon module
- Converter communication card
- Modbus adapter card
Converter problem
See Converter format fail 0
No idea
Please contact ABB
Typically due to earth fault in motor or motor cables
Motor thermal protection mode selected as THERMISTOR and the

Intermediate circuit DC voltage is excessive. DC overvoltage trip limit is 1.3

U1max, where U1max is the maximum value of the mains voltage range.
For 400 V units, U1max is 415V. The actual voltage in the intermediate
circuit corresponding to the mains vo
Motor temperature is too high (or appears to be too high). This can be
caused by excessive load, insufficient motor power, inadequate cooling or
incorrect start-up data.
The ACS 600 / 800 internal temperature is excessive. The trip level of
inverter module temperature is 125 deg. C
- Contact technical support
- Check the converter for correct message.
- If ABB converter says "Supply Phase" but supply phase is ok, then
probably the rectifier circuit, ie NINP board is faulty

* Converter was set to LOCAL when it was suppose to be on REMOTE.
This is possible when performming programming procedures on the

converter.

1. For Maint motor converter, the elektronikon K05 relay should be closed.
2. For Dryer converter (if present) the elektronikon K02 relay should be
closed.
3. For Fan converter (if prese
1. For Maint motor converter, the elektronikon K05 relay should be closed..
- Service switch in wrong postion

- Commissioning Parameter (P010) has wrong definition

* eg READY instead of other settings
The first expansion module from the Mk IV regulator has a problem. This
could be caused by:
- Expansion module not programmed
- Expansion module faulty, or no connection, or no power
could be caused by:
could be caused by:
could be caused by:
could be caused by:
could be caused by:
could be caused by:
- Possibly due to faulty IGD. SS is also not able to perform properly. R012 (Active
BICO) does not change state when SS change position
- Also possible is power supply card is faulty, hence not able to give the converter
the correct signals to inhibit the
An overcurrent condition has occurred
An overvoltage condition has occurred
The threshold for initiating an alarm has been exceeded.
The parameterizable threshold for initiating an alarm has been exceeded.
The motor has been moved during motor data identification

If the instantaneous load condition is maintained, then the inverter will be
thermally overloaded.
The parameterized limit value for the I2t monitoring of the motor has been
exceeded.
Bit 3 in r553 status word 2 of the setpoint channel. The speed actual value has
exceeded the value of maximum speed plus the set hysteresis.
Bit 8 in r552 status word 1 of the setpoint channel. The difference between
frequency setpoint/actual value is greater than the parameterized value and the
control monitoring time has elapsed.
Motor is stalled or blocked.

The alarm cannot be influenced by P805 "PullOut/BlckTime", but by P794
"Deviation Time"
The measured values of the leakage measurement or of rotor resistance deviate

significantly.
The standstill measurement is executed when the converter is powered up. The
motor can align itself several times in a certain direction with this measurement.
The rotating measurement has been aborted or cannot commence because an

inverter stop command is present.
When the converter is powered up, the rotating measurement automatically

accelerates the drive. The drive can then only be externally controlled in a
restricted fashion.
Either the power supply card (PSU1) or the CUVC card is faulty.
- This is an defined error code, meaning that there was not enough time to read
out the fault message from the converter.
- Most probably caused by a voltage interruption.
If the a contactor checkback signal is configured, a checkback signal was not

received within 500ms after the power-up command
- When pre-charging, the minimum DC link voltage (P071 Line volts x 1.34) of 80%
has not been reached .
- The maximum pre-charging time of 3 seconds has been exceeded.
- SHOULD NEVER HAPPEN DURING OPERATION, ONLY HAPPEN AT STARTUP
- Shutdown due to excessive DC link voltage
- The lower limit value of 76% of the DC link voltage (P071 Lin Volts), or 61% when
kinetic buffering has benn enabled, has been fallen short of.
- Undervoltage in the DC link with active kinetic buffering and speed less than 10%
of the rated motor speed.
MOST UNLIKELY TO OCCUR IN OUR APPLICATION

- Due to excessive DC link voltage, shutdown has taken place.
- Lower threshold value than F006
- Overcurrent shutdown has occurred.
- The shutdown threshold has been reached.
- The phase in which an overcurrent has occurred is indicated in a bit-coded
manner in the fault value (see r949)
Phase U--> Bit 0 = 1--> fault value = 1
Phase V--> Bit 1 = 1-
During excitation of the induction motor, the current did not rise above 12.5% of
the setpoint magnetising current for no-load operation
SHOULD NOT HAPPEN

- During excitation of the motor, the current component is less than 25% of the
motor no-load current
- Only U800 = 1
irrespective of the type of control
(Difference to F012)
- Likely cause is mechanical blockage of motor

- Motor has stalled or locked
- If the static load is too high
- Possible that a bearing has failed, ie, the non-drive end, thus still enable the
motor the ability to rotate at slow speed
- Drive in running
- Motor been stolen / not there

- Flying restart without tachometer
The motor temperature limit value has been exceeded.
* r949 = 1 means limit value of motor temperature exceeded
* r949 = 2 means short-circuit in cable to the motor temperature sensor or sensor
defective.
* r949 = 4 means wire break in cable to the motor
Parameterized limit value of the I2t monitoring for the motor has been exceeded.
The limit value of the inverter temperature has been exceeded.
R949 = 1 : Limit value of inverter temperature has been exceeded.

R949 = 2 : Sensor 1 : wire break of sensor cable or sensor defective.
r949 = 18 : Sensor 2 : " "
r949 = 34 : Sensor 3 : " "
Higher level of F11

Higher level of F11

Higher level of F11
failure.
Similar to F8


is parameterised trigger when temp reaches 51 deg. C

P575 Src No ExtFault1

a fault has occurred when storing the values in the EEPROM
- A fault has occurred during the softwiring of Binectors and connectors
During the ground fault test, a current not equal to 0 was measured, or a UCE or
the overcurrent monitoring responded, although none of the valves were
triggered.
During the ground fault test a UCE monitoring function responded in a phase in
which no valve was triggered
Transistor conductive when not triggered to do so
During the ground fault test, current flowed in one phase when none of the valves
were triggered, or the UCE monitoring in the phase responded in which the valve
was triggered.
An earth fault or a fault in the power section is present. During the ground fault
test, a current flows from the phase in which a valve was triggered, the
overcurrent comparitor responded, or a UCE monitoring in a phase has responded
in which a valve wa
Short circuit, low-resistance ground fault
Motor overload (calculated): Motor current too high for too long a period.
Load too high, or excessive dynamic stressing.
Seized element.
ZR160VSD:
- Temperature limiting switch of motor is activated - open contact, ie, motor
overtemperature.
- Faulty temperature limiting switch.
- Loose connection at X101: 1 & 7
Motor stalled or locked
Could be one phase missing, where consumption on all 3 phases arevery different.
Precharging malfunction, line voltage, inverter defective

Motor thermistor problem
- Motor overheat
r949 = 1 Motor temperature limit exceeded
r949 = 2 Short circuit in the cable to the temperature sensor or sensor defect
r949 = 3 Open circuit in the cable to the temperature sensor or sensor defect
- Check P363 Mot.temp T1
The temperature limit of the inverter has been exceeded.
r949 = 1 The temp. limit of the inverter has been exceeded

r949 = 2 Sensor 1: Wire break in the sensor wire or sensor defect
r949 = 18 Sensor 2: ""
r949 = 34 Sensor 3:
Fault in internal linking. One of the two linked partners does not reply.
Higher level of F11
A fault has occurred in the EEPROM

Higher level of F11

Higher level of F11
failure.
Similar to F8

DC-link voltage (ULC) too low.

Possibly caused by a voltage dip
Line power failure. Phase failure
Dummy plug for the keypad not (properly) engaged, or PMU controller missing
is parameterised t trigger when temp reaches 51 deg. C
P575 Src No ExFault1
operat
A fault has occurred when storing the values in the EEPROM
- A fault has occurred during the softwiring of Binectors and Connectors

Line voltage too high, extreme generator operation, ramp down rate too fast.
Too high temperature inside converter. Inadequate cooling
Motor overtemp. (PTC thermistor term. X13:24/25), motor overload
CU: DC voltage was too low, ie 76% x line voltage x 1.34 was not reached
Phase missing at the inverter's input power supply.

Input voltage imbalance >5 %.
For the frame size E:
Phase loss at L3/R or L3/S may cause F021 or F185.
Phase loss at L3/T will cause F006.
For frame sizes F and G:
Pre-charge circuit fault.
The input voltage is too low and the DC bus voltage

dropped below the minimum permitted value (monitor the
value at parameter P0004):
Ud < 530 V - Supply voltage 500 / 525 V (P0296 = 5).
Ud < 605 V - Supply voltage 600 V (P0296 = 7).
Phase loss in the input power supply.
Pre-charge circuit failure.
Parameter P0296 was set to a value above of the power
supply rated voltage.
The input voltage is too high and the DC bus voltage
surpassed the maximum permitted value:
Ud > 1000 V - For P0296 = 5, 6 or 7.
Ud > 1200 V - For P0296 = 8.
Inertia of the driven-load is too high or deceleration time
is too short.
Wrong settings for parameters P0151, or P0153, or
P0185.
Short-circuit between motor phases U and V or U and W.
Short-circuit between motor phases V and U or V and W.
Short-circuit between motor phases W and U or W and V.
Short-circuit between the connection cables of the

dynamic braking resistor.
Settings of P0156, P0157, and P0158 are too low for
the used motor.
Motor shaft load is excessive.
Inverter output current is too high.
Inverter output current is too high.
Surrounding air temperature is too high (>50 °C (122 °F))

and output current is too high.
Blocked or defective fan.
Very dirty heatsink.




The temperature difference between IGBTs modules of

the same phase (U, V, W) was above 10 °C.
The temperature difference between IGBTs modules
of different phases (U and V, U and W, V and W) was
above 20 °C.
The temperature difference between rectifier modules of
different phases (R and S, R and T, S and T) was above
10 °C.
U, V, W wiring to the motor is inverted.

Encoder channels A and B are inverted.
Error in the encoder assembly position.
Short-circuit between two motor phases.

Short-circuit between the connection cables of the
dynamic braking resistor.
IGBT modules are shorted.
Excessive load inertia or acceleration time too short.

Settings of P0135 or P0169, P0170, P0171, and P0172
are too high.
Settings of P0156, P0157, and P0158 are too low for
the used motor.
Shorted wiring in one or more of the output phases

Motor cable capacitance is too large, resulting in current
peaks at the output
Loose connection or broken wiring between the motor
and inverter connection.
Vector control with wrong orientation.
Vector control with encoder, encoder wiring or encoder
motor connection inverted.
Excessive load inertia or desacceleration time too short.

Wrong setttings for parameters P0154 and P0155.
Excessive load at the motor shaft.
Excessive duty cycle (too many starts / stops per minute).
Surrounding air temperature too high.
Loose connection or short-circuit (resistance < 100 Ω) in
the wiring connected to the motor termistor.
Motor termistor is not installed.
Blocked motor shaft.
Broken wiring between motor encoder and option kit for

encoder interface.
Defective encoder.
Electrical noise.
An attempt to copy the keypad parameters to an inverter

with a different firmware version.
Defect in the inverter internal circuitry.
Loose keypad cable connection.
Electrical noise in the installation.
Wiring was not connected to the digital input (DI1 to

DI8) set to "No external alarm".
Wiring was not connected to the digital input (DI1 to

DI8) set to "No external fault".
Defect in the inverter internal circuitry.

Excessive load at the motor shaft.
Excessive duty cycle (too many starts / stops per minute).
Loose connection or short-circuit (resistance < 100 Ω) in
the wiring connected to the motor termistor.
Motor termistor is not installed.
Blocked motor shaft.
Check the wiring and grounding installation.

Make sure the inverter has sent a new message within
the time interval set at P0314.
PLC entered into the idle state.

Programming error. Master and slave set with a different
number of I/O words.
Communication with master has been lost (broken
cable, unplugged connector, etc.).
Defective, unrecognized, or improperly installed Anybus-

CC module.
Conflict with a WEG option board.
Broken or loose cable.
Power supply is off.
Incorrect communication baud-rate.

Two nodes configured with the same address in the network.
Wrong cable connection (inverted signals).
Communication problems.
Wrong master configuration/settings.
Incorrect configuration of the communication objects.
PLC in IDLE mode.
Bit of the PLC command register set to zero (0).
One or more allocated I/O connections have entered
into the timeout state.
Verify the network master status, making sure it is in

execution mode (Run).
Refer to the Profibus DP communication manual for
more information.
Verify whether the network master is correctly configured

and operating normally.
Verify the network installation in a general manner -
cable routing, grounding.
more information.
Verify whether the Profibus DP module is correctly fit into
the slot 3.
more information.
Wrong settings of P0161 and/or P0162.

Problem with the hoist-type load.
Defective FLASH memory module.

Check the connection of the FLASH memory module.
Surrounding air temperature too high (>50 °C (122 °F))

and excessive output current.
Defective internal fan.
High temperature (> 45 ºC (113 °F)) inside the cabinet.
Surrounding air temperature too high (>50 °C (122 °F))

and excessive output current.
Defective internal fan.
High temperature (> 45 ºC (113 °F)) inside the cabinet.
Surrounding air temperature ≤ -30 °C (-22 °F).
Surrounding air temperature ≤ -30 °C (-22 °F) (
It was only applied +24 Vdc to one STO input (STO1 or

STO2).
One of the relays is defective.
Refer to the PLC11-01 module programming manual.
Broken AI1 cable.

Bad contact at the signal connection to the terminal
strip.
Broken AI2 cable.
strip.
Broken AI3 cable.
strip.
Broken AI4 cable.
strip.
Dirt on the blades and in the bearings of the fan.
Defective fan.
Defective fan power supply connection.
Dirty on the blades and in the bearings of the fan.
Defective fan.
Defective fan.
Maximum number of operating hours for the heatsink
fan has been reached.
Dirt on the blades and rolling bearings of the fan.

Defective fan.
Defective connection of the fan power supply.
Defective fan.
It is necessary to set date and time at parameters P0194

to P0199.
Keypad battery is discharged, defective, or not installed.
No motor connected or the motor connected to the
.inverter output is too small.
Possible defect on the internal circuits of the inverter
Possible solutions:
Reset inverter and try again.
Set P0356 = 0 and try again.

Operation with frequencies < 10 Hz under overload.
Pre-charge contactor defect.

Inverter CFW11 frame size E powered by DC Link:
P0355 should be programd to 0.
Motor high temperature.
Motor high temperature


A problem in the wiring connecting the sensor to the IOE
01 (02 or 03).
01 (02 or 03).
Motor high temperature
01 (02 or 03).
01 (02 or 03).
01 (02 or 03).
Shorted temperature sensor.
Refer to the RS-232 / RS-485 Serial communication manual.
Refer to the Anybus-CC communication manual.

Refer to the CANopen communication manual and/or the DeviceNet
communication manual.
Refer to the CANopen communication manual
Refer to the CANopen communication manual.

Refer to the Profibus DP communication manual.
IGBTs of the same phase presented a current imbalance

above 15 %.
The temperature difference between IGBT modules
of different phases (U and V, U and W, V and W) was
above 10 °C (50 ° F). The temperature difference
between rectifier modules of different phases (R and S, R
and T, S and T) was above 10 °C (50 °F).
Temperature of the internal air of the control board is
above 85 °C (185 ° F)
When the temperature of the internal air of the control

board is above 70 °C (158 °F) .
RTC function block has been activated in the applicative

and the HMI is disconnected from the inverter.
RTC function block has been activated in the applicative
and the HMI is disconnected from the inverter.
The SoftPLC Run/Stop command is equal to Run or a
movement block has been enable while the inverter is
general disabled.
It occurs when two or more movement blocks are
enabled simultaneously.
It occurs when a movement block has been enabled and
the speed reference has not been configured for SoftPLC
(check P0221 and P0222).
AA: Incorrect wiring
BB: Analog reference (if used)
CC: Incorrect settings
DD: Fault
EE: Stalled motor

AA: Loose connections
BB: Defective speed reference
CC: Oscillation of the external

analog reference
DD: (vector control)
AA: Incorrect settings

(reference limits)
BB: Control signal from the
analog reference (if used)
CC: Motor nameplate
Settings
AA: Keypad connections 1. Check the inverter keypad connection

BB: Power supply voltage 1. Rated values must be within the limits
specified below:
- Minimum: 425 V
- Maximum: 759 V
CC: Mains supply fuses open 1. Replace the fuses
Settings
Encoder signals are inverted
or power connections are
inverted
Counter measure
Check the module for loose connection.
If no loose connection is found, chances are the diode that controls the power supply to
the display is gone. It is not recommended to repair them, because whilst repairing,
there is a chance of disturbing neighbour ICs, hence System 200 fault would come up
after power is back on.
(For those elektronikons enthusiasts, the part is a BYW 98 - 400 )
In Masterdrive series, it is possible that the parameter P373 index 001 is set to 1, hence
the system is always re-starting. This come about, if there is only a "brief" failure, but
system has not got enough time to register a fault.
Hence, solution is set parameter P373 index 001 to 0 and try again. This will prompt a
fault in the converter, whatever it may be, eg. F008.
Please note that if the Compressor has ARAVF programmed, then it is necessary to have
parameter P373 index 001 back to 1 when finished with fault finding.
- Power down the regulator.

- Check the Emergency stop button.
* Make sure all wires connected firmly and no bad contacts are existing.
* All the components of the Emergency stop button (base and contacts) should have
the same colour (black or brown)
* A mixture of colours could cause this problem to exist.
Check the wiring from the Emergency stop button to the regulator.
- Power up the regulator again.
Replace Elektronikon Mk III if all else fails
Replace Elektronion, if all else fails
These failures are used to signal some dangerous situation caused by hardware or
software problems.
Check 2x1 connector. Possibly, the FET, inductor (the green resistor lookalike), or diode
is gone here, due to reverse biased of power.
Also, check other digital inputs at connector 2x4, and at 2x6 as well.
Depends on what the REGULATOR is used for, ie LOCAL only, or REMOTE only, as one of
these digital contacts is faulty, and by using the "wrong" option, the fault may come up.
For example, if the component that is controlling the LOCAL control for START/STOP, etc,
is faulty, hence when we operate the Elektronikon locally, the fault message would
probably turn up, howver, if we operate the Elektronikon remotely, chances are it will be
ok.
If module was "brand new but faulty", then replace the Elektronikon and send faulty
part back to head office.
Replace Elektronikon
the same colour (black or brown)
* A mixture of colours could cause this problem to exist.
Check the wiring from the Emergency stop button to the regulator.
- Power up the regulator again.
For example, when this module being use for remote control. As two digital inputs were
closed, please check which one is causing the failure 11. Is it the CMS 2 as from when it is
closed or is it 30 & 34 contact.
If nothing is found, then change the module.
This bad module, however maybe used for machine which remains in "local
control"only.
Hardware or software problem

compressor can start after the failure reset. It is possible to clear this kind of failure
through the reset function key of the system failure display.
Check external parts for fault, loose connections, power missing of one phase, etc.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
Possibly need a new regulator
Try to power OFF and ON again. If cannot resolved, then try a new module.
failure display.
failure display.
failure display.
failure display.
failure display.
Wifh power supply and contactors that switches the power supply.
To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to

restart the autoconfiguration.










Please check to make sure CMS is in correct position

Please check for the right module.
Please connect COM module to regulator before autoconfiguration.

Make sure that there is only ONE COM module for the VSD. Then restart
autoconfiguration.
- Check the cable for connection between the 2 modules

- Check the power supply to the modules (24V)
- 700X, where X = the com module no., for example, 7001 implies no. 1 module is not
communicating with Master module. 7002 implies no. 2 module is not co

communicating with Master module. 7002 implies no. 2 module is not communicating
with Master module. 7002 implies no. 2 module is not communicating. This is more
relevant when there are more than one communication module is configured to the
Master / Compressor.
- Try to power OFF the compressor, then ON again a short time later.
Try to reprogram the modules and check the start configuration
Try to reprogram
Try to reprogram
- Check connections of converter / COM module
- Isolate converter from COM module, and use VSD simulation software to test whether
COM module or converter is at fault. A pc with RS232 cable or RS485 ( such as that use
for SDP4win) is required. The cable is to be connected in place of converter cable
connection.
- If converter at fault:
* If fault occurs all the times, it is more likely the GAX card need to be looked at.
Please take care when changing GAX card, and watch out for resistor bank jumpers. GAX
card = power supply card (for GA90VSD with Simovert P drive)
* If intermittently, then CU or CCU card fault is more likely. These cards are
normally arrive with no memory. Please see programming procedures if required.
- ABB - Reprogram the Elektronikon Mk III and test again.

- Siemens - This fault could occurs when the CUVC control card is freshly
(re)programmed. This is due to the fact one or more parameters have incorrect
communication baud rate. The correct settings should be:
P701.1 = 6 (baud rate = 9600 for communication between converter and PC (Simovis))
This parameter setting may be changed so that both the Simovis and the Converter have
the same values. For some machines, it is default at 9600, while others, default at 19200
P701.2 = 7 (baud rate = 19200 for communication between converter and COM2 /
Elektronikon.
If this parameter has the wrong setting, F7301 will be displayed. This setting should be
identical to that of the VSD simulation program.
P701.3 = 7 (baud rate = 19200)

PLEASE BE ENSURED THAT THE RESISTOR BANK FROM THE GAX CARD IS FUNCTION
PROPERLY. AS EXPERIENCED IN ACNZ HAS SHOWN THAT FAULTY RESISTOR BANK CAN
(AND PROBABLY WILL) DISGUISE ITSELF HAS F14, F12, ETC. AND ARE INTERMITTENT
FAULTS.
BECAUSE THE RESISTOR BANK HAS TO BE TAKEN OUT EVERYTIME THE GAX CARD BEEN
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.
COM module or converter is at fault. A PC and RS485 <-> RS232 converter box is
required as well as the DFM4win cable. The cable is to be connected in place of
converter cable connection.

Elektronikon.
P701.3 = 7 (baud rate = 19200)

FAULTS.
COM module or converter is at fault. A PC and RS485 <-> RS232 converter box is
required as well as the DFM4win cable. The cable is to be connected in place of
converter cable connection.

Elektronikon.
P701.3 = 7 (baud rate = 19200)

FAULTS.
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.E58
- Switch machine OFF then back ON again. Allow a few mins for all power inside
electronics to dissipate.
- Reprogam the converter.
- Check parameters, compare with list and adjust any discrepancies
- Siemens MasterDrive: Check the DC Link voltage and r006 parameter, see if all agree or
within tolerance of each other. If not, then either the CUVC card or (and ??) PSU card has
a problem. If the PSU card has a problem, then the Start Inhibit may not be possible,
hence the converter cannot be started by the Elektronikon. This can also be monitored
by r012 parameter, (Service Switch parameter acknowledgement. r012 = 1 => PMU
controlled, r012 = 2 => Elektronikon Controlled)
Change the parameter P60 = 0 to P60 = 1. This can be done via the PMU (ParaMeterizing
Unit). And observe the new fault code (if any) on the HRR or PMU
Check:
- whether the cable to the corresponding digital input has been interrupted.
- parameter P588 Src No Ext Warn 1
Check:
- Remove the drive and perform visual inspection of IGD.
- IGD (and maybe PSU) may need replacement.
Check the driven load for an overload condition.

- Are the motor and the converter matched?
- Have the dynamic performance requirements been exceeded.
Check the supply voltage. The converter regenerates without regeneration possbility.
Measure intake air or ambient temperature. Observe reduction curves at >40 deg. C.
Check:
- Whether the fan -E1 is connected and is rotating in the correct direction.
- The air intake and discharge openings for blockage.
- The temperature sensor at -X30
- Check the motor (load, ventilation, etc.). The current temperature can be read in r009
motor tmp.
- Check the KTY84 input at connector - X103:29, 30 for short-circuit.
Lock the motor.
Check:
- P72 Rtd Drive Amps
- MLFB P70
- P128 Imax
- r010 Drive Utilizat
Motor load cycle is exceeded !!
Check:
- P382 Motor Cooling
- P383 Mot Tmp T1
- P384 Mot Load Limits
- P804 Overspeed Hys plus

- P452 n/f(max, FWD spd) or
- P453 n/f(max, REV spd) has been exceeded.
Increase the parameter for the maximum frequencies or reduce the regenerative load.
Check:
- whether an excessive torque requirement is present.
- whether the motor has been dimensioned too small.
Increase values P792 Perm Deviation Frq/set/actual DevSpeed and P794 Deviation Time.
Check:
- Whether the drive is locked
- Whether the encoder cable is interrupted during speed control and whether the shield
is connected.
- Whether the drive has stalled
- For synchronous motors (P095 = 12): excitation current injection
Usually the leakage reactance P122 is the average value resulting from the measured
values in r546.1…12, and the rotor resistance r126 from the values in r542.1..3.
If individual measured values significantly deviate from the average values, they are
automatically not taken into account for the calculation (for RI) or the value of the
automatic parameterization remains (for Ls). It is only necessary to check the results for
their plausibility in the case of the drives with high requirements on torque or speed
accuracy.
If the standstill measurement can be executed withou any danger:

- Power up the converter.
P561 Scr InvRelease - Release the inverter
If necessary, re-start the measurement by powering up the converter.

If the rotating measurement can be executed without any danger:

At terminal X101 of CUVC card check:
- Pin 1 & 2: Use Vdc multimeter to check for 24 Vdc. If not, then the power supply card,
PSU1 is faulty.
Also, at X102, pin 13 should have 10 Vdc, and pin 14 = -10Vdc, with pin 2 common.
If these voltages are present, then the CUVC card is faulty.
- Check for loose connections

- Try to reprogam the MKIII
P591 S.MC chkbck sign.
The parameter value must match the main contactor checkback signal connection. Check
the main contactor checkback signal circuit.
Should NEVER happen in Masterdrive Series.
- Check the supply voltage.

- Can fail if low V, because software setting for V is wrong.
- Compare with P071 Line Volts (Compare P071 with the DC link voltage on DC units)
- Check the rectifier / regenerative unit on DC units. The rectifier/regenerative unit on
DC units. The rectifier/regenerative unit must be switched on before the inverter is
switched on.
- Check voltage C and D. Should get high 500V's (dc). While having the multimeter on it,
please restart the machine (in converter local control mode). If the voltage deteriorate in
over a short period of time, then there is pre-charge problem, hence, change the pre-
charger PCB, or Siemens to change it if under warranty. For G85GA30VSD case, the
whole drive should be return to Siemens for evaluation, if under warranty.
- Check supply voltage or DC voltage

- Converter is working at upper tolerance limit and at full load.
- Can be caused by line phase failure
- Converter is operating in regenerative mode without feedback possibility
- Try:
- Increase P464 Decel Time
- Activate P515 DC Bus Volts Reg (check P071 beforehand)
- Reduce P526 Fly Search Speed
- Reduce P259 Max Regen Power (only for P100 = 3, 4 or 5)
On a GA 37 VSD, that we have been working on was starting /stopping intermittantly.
It had the same problem as before showing an erratic DC Link voltage at the PMU, with
stable voltage at the DC Link. The original power supply (PSU) was faulty, and replaced
with a new PSU. Weeks later, the problem still existed.
The problem was traced to a break it a joint on the power supply control card that was
replaced by us.
The card was repaired onsite and the problem rectified.
- Check Input DC voltage

- DC link - Check for PCC (precharger card) and PCU (Precharger Unit - the less dense in
terms of electronics, of the two cards - This card normally OK)
- Maybe diodes blown as well, please check.
- Check for thyristor modules, should be approx. 6v in-circuit diode check! And OPEN-
CIRCUIT out-of-circuit diode check !
- IVI card may be faulty as well.
- Terminal C and D should be checked using multimeter with Vdc, or some sort of Scope
meter. Should expect to be in excess of 500Vdc
- Can also be seen Simovis program. Parameter r006 (DC bus voltage). Can be checked
on PMU as well
- Check supply voltage

- Check braking resistors
- Converter operates regeneratively without a feedback possibility. Braking unit must be
set to the lower response then threshold (673V)
- Check the free rotation (by hand) of the compressor element / motor
- Check connections at the measuring devices in the front of the converter
- Check if incoming supply voltage < 400 -10% and verify if cable section is accurate to
spec. (min 50mm square)
- Check RFI - net filter for short circuit
- Check the converter output for short-circuit or earth fault
- Check the load for an overload condition
- Check whether motor and converter are correctly matched (this should always be true)
- CT (current transformer) maybe faulty. As current is asked for again and again causing
build up of --> overcurrent. This condition is usually NOT intermittent. CT are very hard
to check, can only be done by v/hz meter and observe for characteristics.
- Check IVI (inverter interface card), replace if cannot solve. Check ABO (adaptor board),
ABO and IVI must be matched.
- Check the resistance of the motor windings in the 3 phases
- Try to start without back pressure, ie with an empty air net
- Try to program P0462 to 30 sec for slower acceleration
- Try new CUVC board
* The fault display must be cleared first before the parameters can be accessed. If the
F011 cannot be cleared, then it is probably the CT (LEM) module is at fault.
But to clear the fault, the scroll UP / DOWN must be pressed at the same time.
When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and L1(u), then L2(v) and L3(w); D across L1(u), L2(v) and L3(w).
If we get short in any of the combinations, eg, resistance between C and L1 then the
IGBT (transistor) is damaged. For all IGBT's to be OK, then some resistance is expected on
all combinations.
Try to start the converter with MOTOR DISCONNECTED and Service switch to manual
control:
- To do this, please observe and adjust the following parameters:
For CUVC MasterDrive:

- Make P53 = 6 (on Simovis, it is binary number . . . 110), then P060 = 5 (Drive Setting),
then P100.1 = 3 (f regulated) to P100.1 = 1 (u/f). The idea here is to change the VECTOR
CONTROL to voltage control. THEN, change P060 = 0 (or 1) in order to start the converter
manually. If NOT, then 005 always appear on the PMU.
If F011 CANNOT be resolved, and P060 = 5, and DOES NOT able to be programmed back
to P060 = 0 or 1, then the CT (LEM) is faulty. This symptom occurs when the PMU is been
- Only for closed loop n/f/T control (P100 = 3, 4 or 5)
- If no motor is connected, go into the simulation mode P372
- Check current detection, check power section
- Check the output contactor
- Check the motor cable
- Check Motor / element for free rotation

- Check current in all three phases to the motor, make sure that they are within 10% of
each other.
- Check the bearings of the motor.
- Reduce Load
- Increase current Limits
- Reprogram card
- Change new CUVC card
- Could be one phase missing, where consumption on all 3 phases arevery different.E97
- One case in Switzerland, where the burned cables on RFI filters or bad contacts on the
inverter bridge.
- Power up after coasting

- Possibly increase P525 Fly Search Amps
- Check the motor (load, ventilation, etc). The actual motor temperature can be read in
r009 of Siemens PMU (panel display)
- Motor temperature.
- Check P381 Mot Temp settings.
- Fault - check the KTY84 input at connector - X103:29, 30 for short circuit.
KTY84 resistance at room temperature should be in the vicinity of 700 - 1000 Ohms
- Check with multimeter, Converter trips when infinite resistance registered.
CHECK: Input of CUVC (ie analog inputs at X103:29,30 and related software / hardware
wiring.)
Use a 0 - 4kOhms potentiometer, and connect to X103:29,30. (For the potentiometer,

short the middle lead to ONE of the other leads)
Make parameter P044.1 = K245 (Mot Temp) . . . . . . . K245 means input is of type KTY84
thermistor / resistor
Check parameter r045. Reading on r045 should change as potentiometer to X103:29,30
changes. If not, then CUVC card may be faulty.
If the card is ok, then r009 = r045 = settings of potentiometer / KTY84 thermistor.
CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance in
supply voltage can lead to 10% extra current in one of the motor phases. 3.5% unbalance
in supply voltage will give 25 deg. C higher in motor temperature.
EMERGENCY ONLY:
Make Parameter P380.1 = 0
Parameter P381.1 = 0
The compressor / drive will now run without thermal protection on the motor.
MOTOR TEMP SENSOR (KTY 84) IS BEING REPLACE BY STANDARD MOTOR THERMISTOR
- This may happen when the KTY 84 motor temperature is not available at time of
service / breakdown, and a new standard motor thermistor is being fitted.
- If a standard motor thermistor is being fitted instead, the Masterdrive will not able to
display the actual motor temperature, HOWEVER, it will still the protects the system and
shutdown at and above temperature 180 deg. C.
** Parameter changes to suit STANDARD THERMISTOR modification:

- P380.1 = 0
- P381.1 = 1 (=1 to make the input to the CUVC of 1.5 Kohms when temperature is 180
deg. C)
- P385 = DE-ACTIVATED (automatically)
Check : P383 Mot Tmp T1
Measure the air intake and ambient temperature. Please observe the reduction curves
at >40 deg. C
Check:
- Whether the fan E1 is connected and is rotating in the correct direction
- that the air entry and discharge openings are not restricted
- Temperature sensor at -X30
- Check the torque on all power connections
- Check voltage before and after the netfilter (A1)
- Check voltage before and after main switch
- Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.
- Check phase 2 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.
- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.G98
PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-
ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.
NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are

maybe on its way out as well.

unbalance in supply voltage E100will give 25 deg. C higher in motor temperature.
- Check the proper connection at the line reactor (L1)
- Check if one of the coils of line reactor L1 is short circuit.F106
- Possibly CU is faulty
- IGBT or IGD may be defective as it is conductive while signal command does not tell it
to do so.
- Defective phase section
- Check cabinet for ventilation

The problem probably does not related to the Masterdrive converter, and because it
receives faulty signals from the external, hence EXTERNAL FAULT #2 comes up. Should
check for problems outside the main converter.
- See ECB 1339

- GA180VSD and related
Replace CU card (A10)
Reduce the calculating time by:
CU2 - increase P308 sampling time, observe r725 - free comp time
CUVC - Increase P357 samping time, Calculate individual blocks in a slower sampling
time, observe r829 CalcTimeHdroom
- Check MWH - CU2 connection

- Replace CU card (A10)
- Reparameterize
- Reset unit
In CUVC, observe r949:
> 1000: Fault during softwiring of connectors
> 2000: Fault during softwiring of binectors
- Replace CU (A10)
- Check connection of the board and optional boards.
- Power unit down and up again
- Replace CU (A10)
Replace CU (A10)
Reverse 2 incoming lines
On PMU / Simovis - The fault cause can be read our of r358 (CU2) or r 376 (CUVC)
"ground fault test result"
- Check the converter output for short circuit of ground fault (-X2:U2, V2, W2 - including
motor)
- Check CU is inserted correctly
Frame Sizes 1 & 2

- Check the transistor modules on the PEU board A23 for short circuit
Frame Sizes 3 & 4
- Check transistor modules A100, A200, A300 for short circuit
Check the power section valves for a short circuit, and for converters with fiber-optic
gating, the gating unit and the UCE checkback signals, for the correct assignment.
PMU / Simovis: r358 (CU2), r376 (CUVC) can be interrogated to indicate which UCE mo
PMU / Simovis: Read-out fault value from R949. The digit of the xth position indicates
the valve, where the fault occurred at power-up.
XOOO Digit X = 1 = V+, X = 2 = V-, X = 3 = U+
Digit X = 4 = U-, X = 5 = W+, X = 6 = W-
The digit of the xth position defines the pahse, in which i is 0 and thus a valve is
defective (always conductive)
OOOX Digit X = 1 = Phase 1 (U)

X = 3 = Phase 3 (W)
X = 4 = Phase 1 (U) r 3 (W)
Examine phase for defective valves (always conductive)
PMU / Simovis: Read-out fault from r949. The digit of the xth position specifies the valve,
which, when triggered, manifested the fault.
XOOO x = 1 = V+, x = 2 = V-, x = 3 = U+

x = 4 = U-, x = 5 = W+, x = 6 = W-
Check the motor including feeder cable for ground faults. If there is no ground fault,
check the power section for defective valves which remain conductive.
The digit of the xth position defines the phase in which I is 0, and therefore a valve must
be defective (always conductive)
OOOX Digit x = 1 = Current in phase 1(U)
x = 2 = UCE in phase 2 (V)
x = 3 = Current in phase 3 (W)
x = 4 = Only overcurrent occur
The motor speed should be less than 10% of the stated speed during the ground fault
test !
A ground fault is present in phase V, or there is a defective valve (always conductive)

- Check the free rotation of the compressor element and/or motor eg a motor bearing
failure
- Check motor windings for possible ground fault
- Check resistance of the motor windings in the 3 phases
- Try start with no back pressure, ie with an empty net
- Check parameter P019 for the proper value (320A); as a trail lower the value in steps of
5 A to a minimum 300A
- Current transfomer may be faulty.
- Try new CCU board.
PLEASE NOTE: on former model GA90 VSD (SN < AII 492 000) Please observe ECB AII0070
(Priority IV) with regards to OIL RESTRICTION AT LOW SPEED for GA90VSD with Simovert
P converter.
FAULTS.
- Check for mechanical resistance in compressor / motor

- Check the small hole of 4mm in the centre of the boss in the check valve housing which
ensures the full opening of the check valve.
unbalance in supply voltage will give 25 deg. C E120higher in motor temperature.
FAULTS.
- PLEASE NOTE: on former model GA90 VSD (SN < AII 492 000) Please observe ECB
AII0070 (Priority IV) with regards to OIL RESTRICTION AT LOW SPEED for GA90VSD with
Simovert P converter.
FAULTS.
ZR160VSD:
- Based on ECB 1397/C1, this fault is present if the terminal X101-7 of the CUVC card is
open contact.
- This happen if the motor temperature is too high, or the temperature switch is faulty,
or loose connections. Please check these conditions..
Supplementary Reading:
* See function diagram 710, where binector U061 = 0 was made to U061 = 19,
* Binector U952.i059 = 20 was made to U952.i059 = 4.
- Check motor
inverter bridge.
May occur after a long period of standstill. In this case, restart the machine for up to 10
times.
If fault persists, check:
- Supply voltage is within tolerance 400V +/- 10%
- PCC (PreCharging Circuit)
- One of the capacitors may be defective
- Fault - check the KTY84 input at connector - X103:29, 30 for shortcircuit.
wiring.)

EMERGENCY ONLY:
display the E123actual motor temperature, HOWEVER, it will still the protects the system
and shuddown at and above temperature 180 deg. C.

- P380.1 = 0
deg. C)
- Check fan E1 is working, and in the correct direction

Replace Cuxx (-A10)


Switch off the unit and switch it on again. If the fault re-occurs, replace the Cuxx


- Check if one of the coils of line reactor L1 is short circuit.
- Possibly, CU is faulty
to do so.
- Reprogam Mark III and put in ARAVF.

- Check DC link voltage during operation which should be around 1.34 x Supply voltage.
- Check fuses.
- Check and make sure this plug is engage via dummy plug of the hand held controller
(PMU)
=F136- Check cabinet for ventilation

- GA180VSD and related compressors with VSD cooling fans. Check that the connection
between the masterdrive and the micromaster is located at pins 19 - 20 on the
masterdrive, and on pins 3 - 4 on the micromaster.
Also, very important to note that on a very HOT day, the micromaster also may
experience overtemperature problem, and therefore would malfunction, and the
Masterdrive converter will register fault F36 (or F036). There may be a fault message on
the micromaster itself, however, this fault message will only registered as an external
fault via the Masterdrive to the elektronikon.
- Therefore, should try to improve the air temperature within the cabinet to eliminate
this fault.
- ZT37VSD: (this may apply to others which have Micromasters drive as well) ARAVF,
everything else was re-started except the micromaster, hence giving F36. Solution was to
set Parameter P15 --- 0 to disabled, and 1 to enabled, and Parameter P18 --- 0 to
disabled and 1 to enabled. Take note when programming the Micromaster, the
parameters P7 = 1 and P9 = 3 for keypad accessibility.
- GA180VSD W (watercool): F36 indicates that the auxiallary drive has a fault. This
auxiallary drive is the positioner Y40 that regulates the By-Pass Oil Cooler solenoid valve.
Please check the status of this positioner. Pay attention to the connections, the OPEN &
CLOSE limit switches. If nothing is found, probably needs a new positioner. Atlas Part No.
1089 0652 01.
In an EMERGENCY, this by-pass oil cooler solenoid valve may be overwritten to allow the
compressor to continue running. The valve has to be overwritten mechanically,
electrically and on Siemens converter.
Mechanically: By turning to hand knob
Electrically: By disconnecting the power to the positioner, please consult electrical
diagram for confirmation of wire number, typically it should be wire labelled No. 2.
Disconnect the active wire only is sufficient.
Siemens Converter: Before any programming is done, make sure that P053 = 0006 for
general access to parameter changes. Go to P586, and change P586.1 from 601 to 001.
P586.1 = Parameter P586, first index. To access to P586.1, please go to P586, then press
P, and .001 shows up, press P again to access first index and scroll up (or down) to get to
the right value. (This is much simpler, if you are using the Simovis Software.)
- There is a thermal switch at the CUVC card of Siemen's converter, at X101, pin 3-4. This

- Reparameterize
- Reset unit

- Replace CU (A10)
- Replace CU (A10)
Replace CU (A10)
- Check operation of cooling fan, as well as power supply (380V) over K5 towards these
fans
- Check for polluted heat sink
- Check resistance value of both sets of thermistors which should be < 500 ohm at 20
Deg.C
For Simovert P:
- Check proper engagement of connector at X13 of CCU
- Check cooling flow over the drive motor
- An externally clogged oilcooler reduces the cooling
CU:- Voltage dips might be the reason, Reprogram the MKIII with latest service software
and put ARAVF active.
- Check DC link voltage during operation through r006 on the Siemens PMU
- IGBT or IGD1 defective is possibility. Maybe loose or bad connection.
See F008
CCU: - Pulsed Resistor or electronics overheating, ambient temp too high. Cooling fan
may be defective
Check with FSP, or reprogram the module and make sure all necessary I/O are declared.
there is a chance of disturbing neighbour
Replace Elektronikon Mk III, if all else fails
Replace Elektronikon Mk IIIMk III, if all else fails
software problems.
Also, check othe

the same colour (black or brow

If nothing is found, then change the mod

Replace Elektronikon Mk III

Check external par
failure display.
failure display.
failure display.
failure display.
failure display.
failure display.














communicating with Master module. 7002 implies no. 2 module is not c
Try to reprogram
Try to reprogram
.
COM module or co
- Check ambient conditions

- Check air flow and fan operations
- Check heatsink fins for dust pick-up
- Check motor power against unit power
- Check for proper analog control signal levels

- Check the control wiring
- Check Al < MIN FUNC Fault Function parameters
Programmable Fault Function 30.01
- Check air flow and fan operation

- Check the status communication. See Appendix C
- Check the parameter settings:
* Group 51 (for CH0 fieldbus adapter), or
* Group 52 (for Standard Modbus Link)
- Check cable connections

- Check if the bus master is not communicating or configured.
- Check the current transformer connected to Main Circuit Interface Board, NINT.
- Check that the overvoltage controller is on (parameter 20.05)
- Check mains for static or transient overvoltage
- Check Braking Chopper and Resistor (if used)
- Check decelaration time
Usin Coasting to Stop function (if applicable)

Retrofit the frequen
- Check mains supply and fuses.
- Check motor
- Check motor cable
- Check there are no power factor correction capacitors or surge absorbers in the motor
cable.
- Check external devices for faults

- Check Parameter 30.03 EXTERNAL FAULT
- Check the connections of the fibre optic cables on NAMC channel CH1
- Check all I/O modules (if present) connected to channel CH1
- Check for proper earthing of the equipment.
- Check for highly emissive components nearby.
- Replace the NIOC board.
- Check the maximum speed (Parameter 20.02). It should be at least 80% of the nominal
speed of the motor (Parameter 99.08)
- Stop drive and let it cool down. Check ambient temperature.
- Check air flow and fan rotation direction

Shift the Panel from the motor side converter control board to line side converter
control board.
See the line side converter manual for the fault description
- Check the wiring of the temperature measurement (+ connections PT100)

- Check the value of the fault limit. Ensure proper motor cooling: check cooling fan,
clean cooling surfaces, etc.
- Check the PT100 resistance off-circuit. Ie, unplug from the NIOC-
Check the wiring of the temperature measurement (+ connections PT100)

- Check motor and motor cable
- Check thermal relay (if used)
- Check MOTOR PHASE Fault Function parameters. Disable this protection
Programmable Fault Function 30.16 (ACC: 30.10)

- Check power supply TO motor. May be a phase is missing
- Check motor load and the ACS 600 ratings.

- Check MOTOR STALL Fault Function parameters.
Programmable Fault Function 30.10 … 30.12

- Motor overload
- Seized element
- Check fault function parameters for further details
- Faulty bearings
- Check motor ratings and load

- Check start - up data
- Check MOTO TEMP Fault Function parameters
- Check the motor data given by Parameters 99.04 … 99.09

- Check motor load
- Check acceleration time.
- Check motor and motor cable (including phasing)
cable.
- Check encoder cable (including phase)
- Check minimum/maximum speed settings

- Check adequacy of motor braking torque
- Check applicability of torque control
- Check the need for a Braking Chopper and Resistor(s)
- Make sure all the parameters in the group 99 START-UP DATA are correct, and c
- Check the Panel is connected to the right connector (see manual)

- Check Control Panel connector
- Re-insert Control Panel in the mounting platform
- Check PANEL LOSS Fault Function parameters.
- Check DriveWindow connection
Programmable Fault Function
- Check the fibre optic cables connected to the power plates.

- Check setting of parameter 16.01
- Check connection X22:8-11
- Check the motor and motor cable.
- Check the power semiconductors (IGBT power plates) of the inverter module. (INU 1
stand for inverter module 1, etc)
- Check the connection from the inverter module Main Circuit Interface Board, NINT to
the PPCC Branch
the PPCC Branch

the PPCC Branch

the PPCC Branch
- Check the motor and motor cable

cable.
Contact ABB
- Check the start inhibit circuit (NGPS board)

- Check connections 8-11 (X22) and 7-1 (X22)
- Check main fuses
- Check for mains supply imbalance
- Maybe motor overload. Check !! = = > fuse blown

- Mains supply contactor. Check all three contacts
- When the machine is running at various frequency, then all the sudden shutdown, but
the supply

- Check start-up data
- Check thermistor connections for digital input DI6
- Check thermistor cabling
Programmable Fault Function 30.04 .. 30.05
- Check for a problem in the driven equipment

- Check UNDERLOAD Fault Function parameters
Create the User Macro again

- Check ambient conditions.
- Check air flow and fan operation
- Check for proper analogue control signal levels.

- Check the control wiring
- Check Al < MIN FUNC Fault Function parameters.
- Check the status of fieldbus communication. See Appendix C - Fieldbus control
- Check the parameter settings:
* Group 51 (for CH0 fieldbus adapter), or
* Group 52 (for standard Modbus Link)
- Check cable connections

- Check if the bus master is not
Make sure the Panel is in local mode
Retry (there might be interference on the link)

Contact ABB
Check program version
(See parameter group 33 )

Stop the motor. Perform the downloading
- Check the pulse encoder and its wiring, the NTAC module, Parameter Group 50 settings
and the fibre optic connections on NAMC channel CH1
Continue drive operation.
Continue drive operation.
Wait until the drive indicates that motor identification is completed.
To Start the ID magnetisation:

- Press the Start Key
- To Start the ID Run procedure:
* Select the Identification Run type (See Parameter 99.10 MOTOR ID Run).
To change the ID number back to 1 go to Drive Selection Mode by pressing DRIVE. Press
ENTER. Set the ID number to 1. Press ENTER.
Wait until the drive indicates that Identication Run is completed.
Press Start key to start the Identification Run
Please wait
- Check motor load and the ACS 600 ratings.

- Check MOTOR STALL Fault Function parameters.
Progammable Fault Function 30.10
Wait until the drive indicates that motor identification is completed.
- Check motor ratings, load and cooling

- Check MOTOR TEMP Fault Function parameters.
- Check the Panel Link connections

- Press the RESET key. The panel reset may take up to half a minute.
- Check the Paenl type and the version of the drive application program. The Panel type
is printed on the cover of the Panel. The application program
Disconnect another station from the link to free an ID number.

Perform the Upload function before downloading.
- Check the Panel is connected to the right connector (See manual)

- Check Control Panel connector
- Replace Control Panel in the mounting platform.
- Check PANEL LOSS fault function parameters.

- Check thermistor connections for digital input DI6 of NIOC board.
Programmable function 30.04 … 30.05
- Check for a problem in the driven equipment.

- Check UNDERLOAD Fault Function parameters.
- Make sure the Panel is in local mode.

- Retry (there might be interference on the link)
- Contact ABB
Stop the motor then change the parameter value
Open parameter Lock (See Parameter 16.02 PARAMETER LOCK)

Excessive motor load.
Faulty motor, motor cables or connections.

Static or transient overvoltages in the input pow supply
Undersized brake chopper (if present).
Verify that overvoltage controller is ON (using parameter 2005).
* Check for motor earth fault. Majority of DC Overvoltage is ca

Fan failure.
Obstructions in the air flow.
Dirt or dust coating on the heat sink.
* Use Multimeter and perform DIODE check....with MAINS POWER off and isolated. Wait
10mins before perform this work
Check for and correct: Missing phase in the input power supply.
Blown fuse.
Undervoltage on mains.
Source and connection for analog input.
Parameter settings for AI2 FAULT LIMIT (3022) and 3001 AI<MIN FUNCTION
Check for overloaded motor.

Adjust the parameters used for the estimate (3005 3009).
Check the temperature sensors and Group 35: MOTOR TEMP MEAS
parameters.
Check:
Communication lines and connections.
Parameter 3002 PANEL COMM ERR.
Parameters in Group 10: START/STOP/DIR and Group 11:
REFERENCE SELECT (if drive operation is REM).

Motor connections.
Motor parameters 99059909.
Excessive load.
Insufficient motor power.
Parameters 30103012.
See parameter 3003 EXTERNAL FAULT 1.
See parameter 3004 EXTERNAL FAULT 2.
The drive
monitors for ground faults while the drive is running and while the drive is
not running. Detection is more sensitive when the drive is not running and
can produce false positives.
Possible corrections:
Check for/correct faults in the input
Faulty thermistor. Replace thermistor or Contact your local ABB representative.
* Communicationg cable faulty.
Contact your local ABB representative.

Faulty power card, replace card or complet VSD cabinet
Possibly due to CURRENT TRANSFORMER faulty

Missing mains phase.
Blown fuse.
Encoder presence and proper connection (reverse wired, loose
connection or short circuit).
Voltage logic levels are outside of the specified range.
A working and properly connected Pulse Encoder Interface Module,
OTAC-01.
Wr
Parameter settings for 2001 and 2002.
Adequacy of motor braking torque.
Applicability of torque control.
Contact your local

ABB representative.
Contact your local ABB
representative.
Fault setup (3018 COMM FAULT FUNC and 3019 COMM FAULT TIME).
Communication settings (Group 51: EXT COMM MODULE or Group 53:
EFB PROTOCOL as appropriate).
Poor connections and/or noise on line.

Motor fault.
Motor cable fault.
Thermal relay fault (if used).
Internal fault.

Proper input wiring line voltage is NOT connected to drive output.
The fault can be erroneously declared if the input power is a delta
grounded system and motor cable capacitance is large. This fault can be
disabled using para

Excessive ambient temperature.
Fan failure.
Obstructions in the air flow.
Not for drives with an OMIO control board.
Contact your local ABB representative and report the error number.
Faults that indicate conflicts in the parameter settings

Check for and correct the follow
- Excessive motor load
- Insufficient accelerating time( see parameters 2202 ACCELER TIME 1 and 2205
ACCELER TIME 2).
-Faulty motor, motor cables or connections
Check for correct the following

- Static or transient over voltages in the input power supply
- Insufficient decelerating time (parameters 2203 DECELER TIME 1 and 2206
DECLER TIME 2)
Check for and correct the under voltage on mains.
Either
-DO not attempted to change the direction of the motor rotation
- Change parameter 1003 DIRECTION to allow direction change (if reverse operating is
safe)
Check and correct

- Fault setup (3018 COMM FAULT FUNC and 3019 COMM FAULT TIME)
-Communication settings (Group 51 and 53 as appropriate)
- Poor connections and or noise on line
Check
- Input sources and connections
- Parameter that sets the minimum (3021)
- Parameter that sets the Alarm/Fault operation (3001)
Check
- Input sources and connections
- Parameter that sets the minimum (3022)
- Parameter that sets the Alarm/Fault operation (3001)
To correct check
-Communcation lines and connections
-Parameter 3002 PANEL LOSS
-Paramters in groups 10 COMMAND INPUTS AND 11 REFERNCE SELECT (if drive
operation is REM)
Check and correct

- Fan failure
- Obstructions in the air flow
- Dirt or dust coating on the heat sink
- Excessive ambient temperautre
- Excessive motor load
Check
- Check for overloaded motor
- Adjust the parameters used for the estimate (3005…3009)
Check
- Motor and drive ratings match (motor is NOT undersized for the drive)
- Settings on parameters 3013 to 3015
To control automatic reset use parameter group 31 AUTOMATIC RESET
To control PFC use parameter group 81 PFC CONTROL and "Application macro:
PFC" on page 49.
To control the PID function use parameters 4022…4026 or 4122…4126
To control START ENABLE 1 function use parameter 1608

To correct check
- Digital input configuration
- Communication settings.
To control START ENABLE 2 function use parameters 1609

To correct check
- Digital input configuration
- Communcation settings
Check ambient conditions.

Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against unit power.

Check for proper analogue control signal

levels.
Check control wiring.
Check Fault Function parameters.
Retry.
Check connections.
Check that parameters are compatible with
drive.
Let chopper cool down.
Check parameter settings of resistor overload
protection function (see parameter group 27
BRAKE CHOPPER).
Check that braking cycle meets allowed limits.
Check that drive supply AC voltage is not
excessive.
Replace brake chopper.

Ensure brake resistor is connected and not
damaged.
See parameter group 42 BRAKE CONTROL.

Check connection of brake acknowledgement
signal.
Check resistor and resistor connection.

Check that resistance rating meets
specifications. See appropriate drive hardware
manual.
Let resistor cool down.

BRAKE CHOPPER).
excessive.
Check resistor connection.

Ensure brake resistor is not damaged.
Let drive cool down.

Check ambient temperature.
Check filter fan rotates in correct direction and
air flows freely.
Check status of fieldbus communication. See

chapter Fieldbus control, or appropriate
fieldbus adapter manual.
Check parameter settings:
- group 51 COMM MOD DATA (for fieldbus

adapter), or
- group 52 STANDARD MODBUS (for
Standard Modbus Link)
Check cable

Check air flow.
Check main and additional cooling fans.
Check current transformer connections to Main

Circuit Interface Board, INT.
Check motor.
Check motor cable.
Check that there are no power factor correction
or surge absorbers in motor cable.
Check supply voltage level, drive rated voltage

and allowed voltage range of drive.
Check that overvoltage controller is on

(parameter 20.05).
Check mains for static or transient overvoltage.
Check brake chopper and resistor (if used).
Check deceleration time.
Use coast-to-stop function (if applicable).
Retrofit frequency converter with
Check mains supply and fuses.

* Use Multimeter and DIODE check for correct working condition of DIODES. MAY SURE
POWER IS COMPLETELY OFF AND WAIT 10 MINUTES BEFORE PERFORMING THIS TEST
Interchange connection of pulse encoder

phases A and B.
Check pulse encoder and its wiring, pulse

encoder interface module and its wiring and
parameter group 50 ENCODER MODULE
settings.
Check external devices for faults.

Check parameter 30.03 EXTERNAL FAULT.
Stop drive. Let it cool down.

Check fan rotates in correct direction and air
flows freely.
Check status of inverters. See signal 4.01 INT
FAULT INFO.
Check fibre optic cables between APBU and
inverter modules.
If Reduced Run function is used, remove
faulted inverter module from main circuit and
write number of remaining inverter modules
into pa
Check connections of fibre optic cables on

channel CH1.
Check all I/O modules (if present) connected to
channel CH1.
Check for proper earthing of equipment. Check
for highly emissive components nearby.
Shift panel from motor side converter control

board to line side converter control board.
See line side converter manual for fault
description.
Check motor and motor cable.

Check thermal relay (if used).
Check Fault Function parameters (Group 30 / parameter 16. Disable this
protection from FAULT to NO
Check motor load and drive ratings.

Check motor ratings and load.

Check start-up data.
Check value of fault limit.

Let motor cool down. Ensure proper motor
cooling: Check cooling fan, clean cooling
surfaces, etc.

surfaces, etc.
Check motor data parameters
99.04…99.09.
Check motor load.

Check acceleration time.
Check motor and motor cable (including
phasing).
Check encoder cable (including phasing).
Check motor nominal values from group 99
START-UP DATA to confirm that motor model
is correct.
Check that there are no pow
Check motor load.

phasing).
capacitors or surge absorbers in motor cable.
Check minimum/maximum speed settings.

Check adequacy of motor braking torque.
Check applicability of torque control.
Check need for brake chopper and resistor(s).
Check panel connection (see appropriate

hardware manual).
Check control panel connector.
Replace control panel in mounting platform.
Check DriveWindow connection.
Check connection from inverter module Main

Circuit Interface Board, INT to PPCC
Branching Unit, PBU. (Inverter module 1 is
connected to PBU INT1 etc.)
Check signal 03.19. Contact ABB
representative if any of faults in signal 3.19 are
active.
Check setting of parameter 16.01. Switch on

signal or check wiring of selected source.

Check power semiconductors (IGBTs) of
inverter module.
Check there are no power factor correction
- By using your multimeter, perform diode check on the output (U,V, W) of the drive.
Check connection interface selections in group

98 OPTION MODULES.
Check start inhibit circuit (AGPS board).
Check mains fuses.

Check for mains supply imbalance.
See parameter 30.05.

Check thermistor connections to digital input
DI6.
Check for problem in driven equipment.

Check parameter group 72 USER LOAD

CURVE settings.
After motor cooling time specified by
parameter 72.20 LOAD COOLING TIME has
elapsed, fault can be reset.
Create User Macro.

Informative alarm
Check motor.
Check motor cable.

Check motor.
Check motor cable.
Informative alarm
Create User Macro.
Check for proper analogue control signal

levels.
Check control wiring.
BRAKE CHOPPER).
excessive.

Ensure brake resistor is connected and not
damaged.
See parameter group 42 BRAKE CONTROL.

Check connection of brake acknowledgement
signal.
Check resistor and resistor connection.

Check that resistance rating meets
specifications. See appropriate drive hardware
manual.
Let resistor cool down.

BRAKE CHOPPER).
excessive.
Check resistor connection.


Check filter fan rotates in correct direction and
air flows freely.
Check status of fieldbus communication. See

chapter Fieldbus control, or appropriate
fieldbus adapter manual.
Check parameter settings:
- group 51 COMM MOD DATA (for fieldbus

adapter), or
- group 52 STANDARD MODBUS (for
Standard Modbus Link)
Check cable

Check air flow.
Check main and additional cooling fans.
Check current transformer connections to Main

Circuit Interface Board, INT.
Check motor.
Check motor cable.
or surge absorbers in motor cable.
Check supply voltage level, drive rated voltage

and allowed voltage range of drive.
Interchange connection of pulse encoder

phases A and B.
Check pulse encoder and its wiring, pulse

encoder interface module and its wiring and
parameter group 50 ENCODER MODULE
settings.

Check parameter 30.03 EXTERNAL FAULT.
Stop drive. Let it cool down.

Check fan rotates in correct direction and air
flows freely.
See appropriate communication module

manual.
Check maximum speed (parameter 20.02). It
should be at least 80% of motor nominal speed
(parameter 99.08).
* Please use REDUCED MOTOR ID RUN where possible, as element is still coupled to
motor.
* ELEMENT MAYBE DAMAGED IF MOTOR ID RUN IN STANDARD MODE.
Check status of inverters. See signal 4.01 INT

FAULT INFO.
Check fibre optic cables between APBU and
inverter modules.
If Reduced Run function is used, remove
faulted inverter module from main circuit and
write number of remaining inverter modules
into pa
Close DC switch.
Check AFSC-0x Fuse Switch Controller unit.
Check connections of fibre optic cables on
channel CH1.
Check all I/O modules (if present) connected to
channel CH1.
Check for proper earthing of equipment. Check
for highly emissive components nearby.
Shift panel from motor side converter control

board to line side converter control board.
See line side converter manual for fault
description.

Check thermal relay (if used).
Check Fault Function parameters (Group 30 / parameter 16. Disable this
protection from FAULT to NO



surfaces, etc.

surfaces, etc.
Check motor data parameters

99.04…99.09.
Check motor load.
phasing).
Check motor nominal values from group 99
START-UP DATA to confirm that motor model
is correct.
Check that there are no pow
Check motor load.

phasing).
Check minimum/maximum speed settings.

Check need for brake chopper and resistor(s).
Check panel connection (see appropriate

hardware manual).
Replace control panel in mounting platform.
Check DriveWindow connection.
Check that INT board power cable is

connected.
Check that POW board is working correctly.
Replace INT board.
Check that INT board power cable is

connected.
Check that POW board is working correctly.
Replace INT board.
Check fibre optic cables or galvanic link. With

frame sizes R2-R6 link is galvanic.
If RMIO is powered from external supply,
ensure that supply is on.
Check signal 03.19. Contact ABB
representative if any of faults in signal 3.19 are
active.
Check motor cables.

Check power semiconductors (IGBTs) of
inverter module.

- By using your multimeter, perform diode check on the output (U,V, W) of the drive.
Check connection interface selections in group

98 OPTION MODULES.
Check mains fuses.

Check for mains supply imbalance.
Check cooling fan.

Replace fan.
Check air filters.
See parameter 30.05.

Check thermistor connections to digital input
DI6.
Check for problem in driven equipment.

Check motor cable.

Check motor power against drive power.
Check setting of parameter 95.03 Temp

inu ambient.
Check ambient temperature. If it exceeds
40 °C (104 °F), ensure that load current
does not exceed derated load capacity of
drive. See the appropriate Hardware
Manual.
Check drive module cooling air flow a
Check:
• selection of the parameter which
enables/disables EFB communication
(58.01 Protocol ena sel)
• EFB connection at terminal XD2D on
the JCON board
• status of the fieldbus master (online/
offline)
• settings of the communication
supervision functio
Check cooling and the fan.

Contact your local ABB representative
Check encoder settings and cabling

(shield). After any modifications, reconfigure
the interface by activating
parameter 90.10 Enc par refresh.
Check encoder settings and cabling

(shield). After any modifications, reconfigure
the interface by activating
parameter 90.10 Enc par refresh.

This fault code is 100% related to a firmware bug. This fault only occurs extremely
sporadic. So once you reset this fault, it will likely1 never come back.

Code Fault
(fieldbus code)
Cause What to do
Check that the JMU is properly installed.

If the problem persists, replace the JMU.
Reload application.
If fault is still active, contact your local
ABB representative.
Check the fault logger for a fault code
extension. See appropriate actions for
each extension below.
*Refer to Application programming for
ACS850 and ACQ810 drives application
guide (3AUA0000078664 [English]).
*Change the template of the application
in D
Reload.
Check the setting of parameter 95.01 Ctrl

boardSupply.
If the fault still occurs, contact your local
ABB representative.

The fault is reset after a successful
restoration via the control panel or
DriveStudio.
Check the usage of the

SOLUTION_FAULT block in the
application program.
Reload application.
Check brake open torque setting,
parameter 42.08.
Check drive torque and current limits.
See parameter group 20 Limits.
Check mechanical brake connection.

Check mechanical brake settings in
parameter group 42 Mech brake ctrl.
To determine whether problem is with
acknowledgement signal or brake,
acknowledgement signal or brake, check
if brake is closed or open.
Check safety circuit connections. For

more information, see the appropriate
drive Hardware Manual, description of
parameter 30.07 (page 199), and
Application guide - Safe torque off
function for ACSM1, ACS850 and
ACQ810 drives (3AFE68929814
[English]).

Let motor cool down. Ensure proper
motor cooling: Check cooling fan, clean
cooling surfaces, etc.
Check value of alarm limit.
Check motor thermal model settings
(parameters 31.09…31.14).
Check that actual number of sensors

c
To restart drive, activate run enable

signal (source selected by parameter
10.11 Run enable) and start drive.
This is normal: when the compressor stops and starts, it’s normal to see the alarms on
the BOP panel flashing. The drive nor the Elektronikon wi
Check setting of parameter 10.11 Run

enable. Switch signal on (e.g. in the
fieldbus Control Word)
This is normal: when the compressor stops and starts, it’s normal to see the alarms on
the BOP panel flashing. The drive nor the Elektronikon will not trip
This alarm belongs to normal start-up

procedure. Wait until drive indicates that
motor identification is completed.
This alarm belongs to normal start-up

procedure.
Select how motor identification should be
performed, parameter 99.13 IDrun mode.
Start id
Check that it is safe to continue

operation.
Return emergency stop push button to
normal position (or adjust the fieldbus
Control Word accordingly).
Restart drive.
Stop drive. Let resistor cool down.
Check resistor overload protection
function settings (parameters
48.01…48.05).
Check alarm limit setting, parameter
48.07 Br temp alarmlim.
Check that braking cycle meets allowed
limits.

Check for excessive ambient
temperature.
Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of
the cabinet.
48.0


temperature.
the cabinet.

temperature.
the cabinet.
Check status of fieldbus communication.

See the appropriate User’s Manual of
fieldbus adapter module.
Check settings of parameter group 50
Fieldbus.
Check cable connections.
Check if communication master is able to
communicate.
Check PC tool or control panel

connection.
Replace control panel in mounting
platform.
Check analog input source and

connections.
Check analog input minimum and
maximum limit settings.
Check PLC programming.
Fieldbus.
Check that all the required parameters in

group 99 have been set.
Note: It is normal for this alarm to appear
during the start-up until the motor data is
entered.
Check parameter 90.01 Encoder 1 sel

setting corresponds to actual encoder
interface 1 (FEN-xx) installed in drive
Slot 1/2 (parameter 09.20 Option slot1 /
09.21 Option slot2).
Note: The new setting will only take
effect after parameter 90.10 Enc par
refre
Check parameter 90.02 Encoder 2 sel

interface 1 (FEN-xx) installed in drive
Slot 1/2 (parameter 09.20 Option slot1 /
09.21 Option slot2).
Note: The new setting will only take
effect after parameter 90.10 Enc par
refre
Check that parameter 31.02 Mot temp1

src / 31.06 Mot temp2 src setting
corresponds to actual encoder interface
installation (09.20 Option slot1 / 09.21
Option slot2):
If one FEN-xx module is used:
- Parameter 31.02 Mot temp1 src / 31.06
Mot temp2 src must
Check cable between resolver and

resolver interface module (FEN-21) and
order of connector signal wires at both
ends of cable.
Check resolver parameter settings.
For resolver parameters and information,
see parameter group 92 Resolver conf.
Note: Resolver
Check cable between FEN-xx interface

and encoder 1. After any modifications in
cabling, re-configure interface by
switching drive power off and on, or by
activating parameter 90.10 Enc par
refresh.

refresh.
Check that all drives that are polled
(parameters 57.04 Follower mask 1 and
57.05 Follower mask 2) on the drive-todrive
link are powered, properly
connected to the link, and have the
correct node address.
Check the drive-to-drive link wiring.
Check the s
Check the connections between the JCU

Control Unit and the power unit.
Informative alarm.
Informative alarm.
Check there are no power factor

correction capacitors or surge absorbers
in motor cable.
Check for an earth fault in motor or motor
cables by measuring the insulation
resistances of motor and motor cable.
If no earth fault can be detected, contact
your lo
Informative alarm. See parameter group

32 Automatic reset.
Check the settings of the motor
configuration parameters in group 99.
Check that the drive is sized correctly for
the motor.
Check the settings of the parameters in

group 57 D2D communication.

Check fault function parameters.

group 34 User load curve.

group 38 Flux ref.

group 19 Speed calculation.
Check encoder installation. See the
description of fault 0039 for more
information.
Check that option modules are properly

connected to Slot 1 and (or) Slot 2.
Check that option modules or Slot 1/2
connectors are not damaged. To
determine whether module or connector
is damaged: Test each module
individually in Slot 1 and Slot 2.

c
Check motor cable.


drive. See the appropriate Hardware
Manual.
Check value of parameter 95.03 Temp
inu ambient.
Check drive module cooling air flow and
Enter password at parameter 16.03 Pass

code.
Informative alarm.
See parameter group 44 Maintenance.

Wait for the DC voltage to rise.
See parameter 23.20 PI tune mode.
Check circuit connected to DIIL input.
Check:
• selection of the parameter which
enables/disables EFB communication
(58.01 Protocol ena sel)
• EFB connection at terminal XD2D on
the JCU control unit
• status of the fieldbus master (online/
offline)
• settings of the communication
supervision f
Check cooling and the fan.
Check encoder settings. After any

modifications, re-configure the interface
by activating parameter 90.10 Enc par
refresh.
Check encoder settings. After any
modifications, re-configure the interface
by activating parameter 90.10 Enc par
refresh.
Check that the analog output to be

calibrated is connected to the
corresponding analog input (AO1 to AI1,
AO2 to AI2). See description of
parameter 15.30 AO calibration.
Check that the analog input has been set
to current using the jumper on the control
u
Check the brake chopper configuration in

parameter group 48 Brake chopper.
Check custom application program.
Check motor load.

Check acceleration times in parameter
group 22 Speed ref ramp.
phasing and delta/star connection).
Check that the start-up data in parameter
group 99 corresponds to the motor rating
plate.
Check tha
Check that overvoltage controller is on,

parameter 47.01 Overvolt ctrl.
Check that the supply (input power)
voltage matches the drive nominal input
voltage.
Check mains for static or transient
overvoltage.
Check brake chopper and resistor (if
used).
Check

in motor cable.
Check mains supply and fuses.

Get ABB to upgrade drive firmware from ver.2300 to ver2700
in motor cable.
Check that there is no earth fault in motor
or motor cables:
- measure insulation resistances of motor
and motor cable.
you
Check fan operation and connection.

Check brake chopper and brake resistor

connection.
Ensure brake resistor is connected and
not damaged.
temperature.
the cabinet.
48.0

48.01…48.05).
Check fault limit setting, parameter 48.06
Br temp faultlim.
limits.
Check input power and motor cable

connections.
Check the insulation resistance of the
motor cable and motor.
Check input power line fuses.

Check for input power supply imbalance.
Connect motor cable.

1. Check setting of parameters 99.06 Mot
nom current and 20.05 Maximum current.
Make sure that 20.05 Maximum current >
99.06 Mot nom current.
Check that

[English]).

[English]).

temperature.
the cabinet.
First action is to check if the drive cooling fan is working and if th

temperature.
the cabinet.
Try other autophasing modes (see

parameter 11.07 Autophasing mode) if
possible.
Ensure no slipping occurs between the
encoder and the motor shaft.
Check setting of parameter 95.01 Ctrl

boardSupply.
First check the connections on the control unit. Then on the power unit.
If all this is checked, replace the control unit (1089 9549


Check parameter 30.01 External fault
setting.

drive Hardware Manual, and Application
guide - Safe torque off function for
ACSM1, ACS850 and ACQ810 drives
(3AFE68929814 [English]).
This fault is somewhat misleading.. The STO
Check minimum/maximum speed

settings, parameters 20.01 Maximum
speed and 20.02 Minimum speed.
Check need for brake chopper and
resistor(s).
If this fault code appears, please

Check brake open torque setting,
parameter 42.08.
Check drive torque and current limits.
See parameter group 20 Limits.



connection.
Replace

*Refer to Application programming for
ACS850 and ACQ810 drives application
guide (3AUA0000078664 [English]).
*Move parameters from the firmware
groups to
Check that option modules are properly

connected to Slot 1 and (or) Slot 2.
Check that option modules or Slot 1/2
connectors are not damaged. To
determine whether module or connector
is damaged: Test each module
individually in Slot 1 and Slot 2.
If fault appears during first start-up before

encoder feedback is used:
- Check cable between encoder and
encoder interface module (FEN-xx) and
order of connector signal wires at both
ends of cable.
If fault appears after encoder feedback
has already been
See fault 0039.

See the appropriate User’s Manual of
fieldbus adapter module.
Fieldbus.
communicate.

c
Check analog input source and

connections.
Check analog input minimum and
maximum limit settings.

refresh.

refresh.
Check that all drives that are polled

(parameters 57.04 Follower mask 1 and
57.05 Follower mask 2) on the drive-todrive
link are powered, properly
connected to the link, and have the
correct node address.
Check the drive-to-drive link wiring.
Check the s
Refer to the documentation of the

technology library.
Refer to the documentation of the
technology library.
Check PLC status.
Fieldbus.



group 19 Speed calculation.
Check encoder installation. See the
description of fault 0039 (ENCODER1)
for more information.
Check the settings of parameters 57.01

and 57.15. Ensure that the FMBA
module has been detected by checking
parameters 09.20…09.22.
Check that the FMBA module is correctly
wired.
Try installing the FMBA module into
another slot. If the problem persists,
c


c
Of all cases (less than 10) worldwide, 100% was solved by downloading the parameters
(the .dsb-file) again to the drive with DriveStudio (instructions how to program your
drive you can find in printed matter 2946 1826 00 “ACS850 Beginner’s Guide”).
Note:
Inofmative warning. (See parameter 99.13 ID run requested.)

Check motor load.
group 23 Speed reference ramp (speed
control), 26 Torque reference chain
(torque control) or 28 Frequency
reference chain (frequency control). Also
check parameters 46.01 Speed scaling,
46.02 Frequency scaling and 46.03
Torque scaling.
Check there are no contactors opening
and closing in motor cable.
plate.
Check that there are no power factor
in motor cable.
Check encoder cable (including
phasing).

in motor cable.
Try running the motor in scalar control
mode if allowed. (See parameter 99.04
Motor control mode.)
your local ABB representative.
Check motor and motor cable for cabling

errors.
in motor cable.
Check motor cable.

Check the supply voltage setting
(parameter 95.01 Supply voltage). Note
that the wrong setting of the parameter
may cause the motor to rush
uncontrollably, or may overload the brake
chopper or resistor.
Check the supply voltage.
With A3A1 or A3A2 on parallelconnected
inverter modules, the auxiliary
code indicates the affected module. The
format of the code is 0x000X XX00,
where “XXX” specifies the channel on the
BCU control unit.
If the problem persists, contact your local
ABB representative.

BCU control unit.
ABB representative.

BCU control unit.
ABB representative.

and 35.62.
Check the dimensioning of the motor
cable in regard to required load.
Check the settings of temperature source

parameters 35.11 and 35.21 against
91.21 and 91.24.
Check the wiring of the sensor.
The auxiliary code identifies the interface
module. (0 = Module 1, 1 = Module 2).
Check the value of parameter 35.02
Measured temperature 1.
Check the cooling of the motor (or other
equipment whose temperature is being
measured).
Check the value of 35.13 Temperature 1
warning limit.

measured).
Check the value of 35.23 Temperature 2
warning limit.
Check the auxiliary code. See actions for

each code below.

contact an ABB service representative for control unit replacement


drive. See appropriate Hardware manual.
fan operation.
Check inside of cabinet and heatsink of
drive module for dust pick-up. Clean
whenever necessary.

Check the auxiliary code (format XXXY
YYZZ). “Y YY” specifies through which
BCU control unit channel the fault was
received. “ZZ” specifies the location (1:
U-phase, 2: V-phase, 3: W-phase, 4: INT
board, 5: Brake chopper, 6: Air inlet, 7:
Power supply board, 8: du/dt filter (R8i)
or temperature switch (XT), 0FA:
Ambient temperature).
Check the motor cabling.
Check cooling of drive module(s).
YYZZ). “XXX” indicates the source of
difference (0: Single module, difference
between phase IGBTs, 1: parallelconnected
modules, minimum-maximum
difference between all IGBTs of all
modules). With parallel-connected
modules, “Y YY” specifies through which
received. “ZZ” specifies the phase (0:
single module, 1: U-phase [parallel
connection], 2: W-phase [parallel
connection], 3: W-phase [parallel
connection]).
Check the cooling fan inside the PCB

space.
With parallel-connected modules, check
the auxiliary code (format XXXY YYZZ).
“Y YY” specifies through which BCU
control unit channel the fault was
received.

Check the connections between the drive

YYZZ). “XXX” specifies the detailed
transmission error warning code. With
parallel-connected modules, “Y YY”
specifies the affected BCU control unit
channel (0: broadcast). “ZZ” specifies the
error source (8: Transmission errors in
PSL link [detailed code in XXX],
9: Transmitter FIFO warning limit hit).
Check the auxiliary code to identify the

fan. Code 0 denotes main fan 1. Other
codes (format XYZ): “X” specifies state
code (1: ID run, 02: normal). “Y” specifies
the index of the inverter unit connected to
BCU (0…n, always 0 for ZCU control
units). “Z” specifies the index of the fan
(0: Main fan 1, 1: Main fan 2, 2: Main fan
3, 3: Auxiliary fan 1, 4: Auxiliary fan 2, 5:
Auxiliary fan 3, 6: Filter fan 1, 7: Filter fan
2, 8: Filter fan 3).
Check fan operation and connection.
Replace fan if faulty.
Check auxiliary fan(s) and connection(s).
Replace faulty fan.
Make sure the front cover of the drive
module is in place and tightened. If the
commissioning of the drive requires that
the cover is off, this warning will be
generated even if the corresponding fault
is defeated. See fault 5081 Auxiliary fan
broken (page 457).

more information, see appropriate drive
hardware manual and description of
parameter 31.22 STO indication run/stop
page 246).

YYZZ). “Y YY” specifies through which
received. “ZZ” specifies the location (1:
U-phase, 2: V-phase, 3: W-phase, 4: INT
board, 5: Brake chopper, 6: Air inlet, 7:
Power supply board, 8: du/dt filter).
Check the connections between the drive


Check the feedback signal coming from

the charging system.
Informative warning
contact your local ABB representative

each code below.
For 1 - No SD card - Insert a compatible, writable SD card into
the SD CARD slot of the BCU control
unit.
For 2 - SD Card write protected - Insert a compatible, writable SD card into
unit.
For 3 - SD card unreadable - Insert a compatible, writable SD card into
unit.
Check the power supply of the control

unit. If powered internally from the drive,
check the supply voltage of the drive.
each code below.
1 - Slip frequency is too small
2 - Synchronous and nominal speeds differ too much
3 - Nominal speed is higher than synchronous speed with 1 pole pair
4 - Nominal current is outside limits
5 - Nominal voltage is outside limits
6 - Nominal power is higher than apparent power
7 - Nominal power not consistent with nominal speed and torque
For all code values Check the settings of the motor
configuration parameters in groups 98
and 99.
the motor.

each code below.
1 - Slip frequency is too small
2 - Synchronous and nominal speeds differ too much
3 - Nominal speed is higher than synchronous speed with 1 pole pair
4 - Nominal current is outside limits
5 - Nominal voltage is outside limits
6 - Nominal power is higher than apparent power
7 - Nominal power not consistent with nominal speed and torque
For all code values Check the settings of the motor
configuration parameters in groups 98
and 99.
the motor.
Check that all the required parameters in

group 99 have been set.
Note: It is normal for this warning to
appear during the start-up and continue
until the motor data is entered.

Check settings of parameter groups 50
Fieldbus adapter (FBA) and 51 FBA A
settings.

Fieldbus adapter (FBA) and 54 FBA B
settings.
Check the auxiliary code. The code

identifies the analog input whose settings
are in conflict.
Adjust either the hardware setting (on the
drive control unit) or parameter
12.15/12.25.
Note: Control board reboot (either by
cycling the power or through parameter
96.08 Control board boot) is required to
validate any changes in the hardware
settings.
Check external fan (or other equipment

controlled) by the logic.
Check settings of parameters
35.100…35.106.
Check that parameter 35.11 Temperature

source / 35.21 Temperature 2 source
interface installation.
FEN-01 does not support temperature

measurement with KTY sensor. Use PTC
sensor or other encoder interface
module.

function settings (parameter group 43
Brake chopper).
Check warning limit setting, parameter
43.12 Brake resistor warning limit.
Check that the resistor has been
dimensioned correctly.
limits.

Brake chopper).
Check warning limit setting, parameter
43.12 Brake resistor warning limit.
Check that the resistor has been
dimensioned correctly.
limits.
One or more of the resistor data settings

(parameters 43.08…43.10) is incorrect.
The parameter is specified by the
auxiliary code.
0000 0001 - Resistance Value too low - Check value of brake resistance
0000 0002 - Thermal time constant not given - Check value of thermal time constant of
the brake resistor
0000 0003 - Maximum continuous power not given - Check value of maximum continous
braking power of the resistor
Check the auxiliary code (format XXYY ZZZZ). “XX” specifies the number of the encoder
interface module (01: 91.11/91.12, 02: 91.13/91.14), “YY” specifies the encoder (01: 92
Encoder 1 configuration, 02: 93 Encoder 2 configuration). “ZZZZ” indicates the problem
(see actions for each code below).
0001 - Adapter not found in specified slot - Check module location
0002 - Detected type of interface module does not match parameter setting - Check
module type against status
0003 - Logic version too old - Contact your local ABB representative
0004 - Software version too old - Contact your local ABB prepresentative
0006 - Encoder type incompatible with interface module type - Check module type
(91.11 or 91.13) against encoder type (92.01 or 93.01).
0007 - Adapter not configured - Check module location
0008 - Speed feedback configuation has changed - Use parameter 91.10 Encode
parameter refresh) to validate any changes in the settings.
0009 - No encorders to configure encoder module - Configure the encoder in group 92
Encoder 1 configuration or 93 Encoder 2 configuration.
000A - Non-existing emulation input - Check input selection
000B - Echo not supported by selected input (for example, resolver or aboluate encoder)
- Check input selection (91.31 or 91.41), interface module type, and encoder type.
000C - Emulation in continuous mode not supported - Check input selection (91.31 or
91.41) and serial link mode (92.30 or 93.30) settings.
Replace brake chopper if external. Drives with internal choppers will need to be
returned to ABB.
Ensure brake resistor is connected and not damaged.
Check for excessive ambient temperature.
Check the dimensioning and cooling of the cabinet.
Check resistor overload protection function settings (parameters 43.06…43.10).
Check minimum allowed resistor value for the chopper being used.
Check that drive supply AC voltage is not excessive.

parameter group 44 Mechanical brake
control.
Check that acknowledgement signal
matches actual status of brake.

Check mechanical brake settings in parameter group 44 Mechanical brake control.
Check that acknowledgement signal matches actual status of brake.

control (especially 44.11 Keep brake
closed).
Check that acknowledgement signal (if
used) matches actual status of brake.
Check the auxiliary code (format XX00 00YY). “XX” specifies the number of the I/O
extension module (01: parameter group 14 I/O extension module 1, 02: 15 I/O extension
module 2, 03: 16 I/O extension module 3). “YY” specifies the analog input on the
module. For example, in case of I/O extension module 1, analog input AI1 (auxiliary code
0000 0101), the hardware current/voltage setting on the module is shown by parameter
14.29. The corresponding parameter setting is 14.30. Adjust either the hardware setting
on the module or the parameter to solve the mismatch.
Note: Control board reboot (either by cycling the power or through parameter 96.08
Control board boot) is required to validate any changes in the hardware settings.

indicates which I/O extension module is
affected.
Check the type and location settings of
the modules (parameters 14.01, 14.02,
15.01, 15.02, 16.01 and 16.02).
Check that the modules are properly
installed.
Check the auxiliary code (format XXYY ZZZZ). “XX” specifies the number of the
encoder interface module (01: 91.11/91.12, 02: 91.13/91.14), “YY” specifies the encoder
(01: 92 Encoder 1 configuration, 02: 93 Encoder 2 configuration). “ZZZZ” indicates the
problem (see actions for each code below).
0001 - Motor gear definition invalid or outside limits - Check motor gear settings (90.43
and 90.44).
0002 - Encoder not configured - Check encoder settings (92 Encoder 1 configuration or
93 Encoder 2 configuration).
Use parameter 91.10 Encoder parameter refresh) to validate any changes in the
settings.
0003 - Encoder stopped working - Check encoder status
0004 - Encoder drift detected - Check for slippage between encoder and motor
Check the auxiliary code (format XXYY ZZZZ). “XX” specifies the number of the encoder
interface module (01: 91.11/91.12, 02: 91.13/91.14), “YY”n specifies the encoder (01: 92
Encoder 1 configuration, 02: 93 Encoder 2 configuration). “ZZZZ” indicates the problem
0001 - Load gear definition invalid or outside limits - check load gear settings 90.53 and
90.54)
0002 - Feed constant definition invalid or outside limits - Check feed constant settings
(90.63 and
90.64).
0003 - Encoder stopped working - check encoder status

See user documentation of fieldbus
interface.
Fieldbus adapter (FBA), 51 FBA A
settings, 52 FBA A data in and 53 FBA A
data out.
communicate.
interface.
Fieldbus adapter (FBA).
communicate.
Check status of controller. See user

documentation of controller.
DDCS communication.
Check cable connections. If necessary,
replace cables.
Check the status of the fieldbus master

online/offline/error etc.).
Check cable connections to the XD2D
connector on the control unit.
Check the auxiliary code (format XXYY ZZZZ). “XX” specifies the number of encoder
interface module (01: 91.11/91.12, 02: 91.13/91.14), “YY” specifies the encoder (01: 92
Encoder configuration, 02: 93 Encoder 2 configuration). “ZZZZ” indicates the problem
0001 - Cable Fault - Check the conductor order at both ends of the encoder cable.
Check the groundings of the encoder cable.
If the encoder was working previously, check the encoder, encoder cable and
encoder interface module for damage.
See also parameter 92.21 Encoder cable fault mode.
0002 - No Encoder Signal - Check the condiiton of the encoder
0003 - Overspeed - Contact your local ABB representative.
0004 - Overfrequency - Contact your local ABB representative.
0005 - Resolver ID run failed - Contact your local ABB representative.
0006 - Resolver overcurrent fault - Contact your local ABB representative.
0007 - Speed scaling error - Contact your local ABB representative.
Check PC tool or control panel connection.

Check mounting platform if being used.
Disconnect and reconnect the control panel.
Check the auxiliary code. Check the source of the warning corresponding to the code:
0: 33.13 On-time 1 source
4: 33.53 Value counter 1 source
5: 33.63 Value counter 2 source.
2: 33.33 Edge counter 1 source
3: 33.43 Edge counter 2 source.
Check the source of the warning

(parameter 33.13 On-time 1 source)
(parameter 33.23 On-time 2 source).

(parameter 33.33 Edge counter 1
source).

parameter 33.43 Edge counter 2
source).

(parameter 33.53 Value counter 1
source).

(parameter 33.63 Value counter 2
source).
Check the auxiliary code. Check the

source of the warning corresponding to
the code:
10: 05.04 Fan on-time counter.

the code:

the code:
the code:

the code:
Check the auxiliary code (format XYY).

“X” specifies the location of the input (0:
AI on control unit; 1: I/O extension
module 1, etc.), “YY” specifies the input
and limit (01: AI1 under minimum,
02: AI1 over maximum, 03: AI2 under
minimum, 04: AI2 over maximum).
Check signal level at the analog input.
Check the wiring connected to the input.
Check the minimum and maximum limits
of the input in parameter group 12
Standard AI.

(parameter 32.07 Supervision 1 signal).



indicates which fan is to be replaced.
0: Main cooling fan
1: Auxiliary cooling fan
2: Auxiliary cooling fan 2
3: Cabinet cooling fan
4: PCB compartment fan
Refer to the hardware manual of the
drive for fan replacement instructions.
Check the external device.

Check setting of parameter 31.01
External event 1 source.



Check status of other converter

(parameters 06.36 and 06.39).
DDCS communication. Check the
corresponding settings in the control
program of the other converter.
replace cables.
If using a control panel or the Drive

composer tool, connect to the supply unit
to read the warning code. Refer to the
firmware manual of the supply unit for
instructions related to the code.
Informative warning. See section Sleep

function for process PID control (page
64), and parameters 40.41…40.48.
Check the auxiliary code (format XXXX YYYY). “YYYY” indicates the problem (see actions
for each code below).
0000 - The drive was stopped before the autotune routine finished. - Repeat autotune
untill successful
0001 - The drive was started but was not ready to follow the autotune command.
- Make sure the prerequisites of the autotune run are fulfilled. See section Before
activating the autotune routine
(page 44).
0002 - Required torque reference could not be reached before the drive reached
maximum speed. - Decrease torque step (parameter 25.38) or increase speed step
(25.39).
0003 - Motor could not accelerate/decelerate to maximum/minimum speed. - Increase
torque step (parameter 25.38) or decrease speed step (25.39).
0005 - Motor could not decelerate with full autotune torque. - Decrease torque step
(parameter 25.38) or speed step (25.39).
Informative warning. See the settings in

parameter group 31 Fault functions.
operation. Reset the source of the
emergency stop signal (such as an
emergency stop push button). Restart
drive.
If the emergency stop was unintentional,
check the source of the stop signal (for
example, 21.05 Emergency stop source,
or control word received from an external
control system).

operation. Reset the source of the
emergency stop signal (such as an
emergency stop push button). Restart
drive.
If the emergency stop was unintentional,
check the source of the stop signal (for
example, 21.05 Emergency stop source,
or control word received from an external
control system).
Check the auxiliary code. Add 2 to the

code to find out the node address of the
faulted drive.
Correct the fault in the follower drive.
Check the setting of (and the source

selected by) parameter 20.19 Enable
start command.
Check setting of parameter 20.12 Run
enable 1 source. Switch signal on (e.g. in
the fieldbus Control Word) or check
wiring of selected source.
Check the external 24 V DC power

supply to the control unit, or change the
setting of parameter 95.04.
Informative warning
Informative warning
more information, see appropriate drive
hardware manual and description of
(page 246).
Try performing the current calibration

again (select Current measurement
calibration at parameter 99.13). If the
fault persists, contact your local ABB
representative.
Check motor load.

group 23 Speed reference ramp (speed
control), 26 Torque reference chain
(torque control) or 28 Frequency
reference chain (frequency control). Also
check parameters 46.01 Speed scaling,
46.02 Frequency scaling and 46.03
Torque scaling.
Check there are no contactors opening
and closing in motor cable.
plate.
Check that there are no power factor
in motor cable.
Check encoder cable (including
phasing).
YYZZ). With parallel-connected inverter
received. “ZZ” indicates the phase that
triggered the fault (0: No detailed
information available, 1: U-phase, 2: Vphase,
4: W-phase, 3/5/6/7: multiple
phases).
in motor cable.
received.
Check motor and motor cable for cabling

errors.
in motor cable.
YYZZ). With parallel-connected inverter
received. “ZZ” indicates the location of
the short circuit (0: No detailed
information available, 1: Upper branch of
U-phase, 2: Lower branch of U-phase, 4:
Upper branch of V-phase, 8: Lower
branch of V-phase, 10: Upper branch of
W-phase, 20: Lower branch of W-phase,
other: combinations of the above).
After correcting the cause of the fault,
reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power.
Check motor cable.

Check motor cabling.

in motor cable.
YYZZ). “XXX” specifies the source of the
first error (see “YYY”). “YYY” specifies
the module through which BCU control
unit channel the fault was received (0:
Channel 1, 1: Channel 2, 2: Channel 3,
4: Channel 4, 8: Channel 5, …, 400:
Channel 12, other: combinations of the
above). “ZZ” indicates the phase (1: U, 2:
V, 3: W).
in motor cable.
Measure insulation resistances of motor
cables and motor.
Check input power line fuses.

Check for loose power cable
connections.
Check for input power supply imbalance.
Switch off the protection in parameter

31.23.
Check the power connections.

in motor cable.
Check that overvoltage control is on

(parameter 30.30 Overvoltage control).
Check that the supply voltage matches
the nominal input voltage of the drive.
Check the supply line for static or
transient overvoltage.
Check brake chopper and resistor (if
present).
Check deceleration time.
Use coast-to-stop function (if applicable).
Retrofit drive with brake chopper and
brake resistor.
received.
Check supply cabling, fuses and

switchgear.
received.
Check the condition of the supply

(voltage, cabling, fuses, switchgear).
YYZZ). “XXX” specifies the source of the
first error (see “YYY”). “YYY” specifies
the module through which BCU control
unit channel the fault was received (0:
Channel 1, 1: Channel 2, 2: Channel 3,
4: Channel 4, 8: Channel 5, …, 400:
Channel 12).
Connect motor cable.
Try other autophasing modes (see

parameter 21.13 Autophasing mode) if
possible.
If the Turning with Z-pulse mode is
selected, check the zero pulse given by
the encoder.
Check that the motor ID run has been
successfully completed.
Clear parameter 98.15 Position offset
user.
Check that the encoder is not slipping on
the motor shaft.
Check that the motor is not already
turning when the autophasing routine
starts.
Check the setting of parameter 99.03
Motor type.

and 35.62.
Check the dimensioning of the motor
cable in regard to required load.


drive. See appropriate Hardware manual.
fan operation.
Check inside of cabinet and heatsink of
drive module for dust pick-up. Clean
whenever necessary.

See A4B0 Excess temperature (page

441).
See A4B1 Excess temperature
difference (page 441).
See A4B2 PCB space cooling (page
441).

measured).
Temperature 1 fault limit.
see A581 Fan (page 4422)

Check auxiliary fan(s) and connection(s).
Replace faulty fan.
Make sure the front cover of the drive
module is in place and tightened. If the
commissioning of the drive requires that
the cover is off, activate parameter 31.36
Aux fan fault bypass within 2 minutes
from control unit reboot to temporarily
suppress the fault.
The auxiliary code identifies the fan (1:
Main fan 1, 2: Main fan 2, 3: Main fan 3,
4: Auxiliary fan 1, 5: Auxiliary fan 2, 6:
Auxiliary fan 3, 7: Filter fan 1, 8: Filter fan
2, 9: Filter fan 3).
Contact your local ABB representative,

quoting the auxiliary code. The code
contains location information, especially
with parallel-connected inverter modules.
When converted into a 32-bit binary
number, the bits of the code indicate the
following:
31…28: Number of faulty inverter module
(0…11 decimal). 1111: STO_ACT states
of control unit and inverter modules in
conflict
27: STO_ACT state of inverter modules
26: STO_ACT state of control unit
25: STO1 of control unit
23…12: STO1 of inverter modules 12…1
(Bits of non-existing modules set to 1)
11…0: STO2 of inverter modules 12…1
(Bits of non-existing modules set to 1)
Check safe torque off circuit connections.

For more information, see appropriate
drive hardware manual and description of
(page 246).
Cycle the power to the drive. If the

control unit is externally powered, also
its power. If the problem persists, contact
Cycle the power to the drive.
Check the auxiliary code. The auxiliary
code categories are as follows:
1 = PU and CU ratings not the same.
Rating ID has changed.
2 = Parallel connection rating ID has
changed.
3 = PU types not the same in all power
units.
4 = Parallel connection rating ID is active
in a single power unit setup.
5 = It is not possible to implement the
selected rating with the current PUs.
6 = PU rating ID is 0.
7 = Reading PU rating ID or PU type
failed on PU connection.
With parallel connection faults, the format
of the auxiliary code is 0X0Y. “Y”
indicates the auxiliary code category, “X”
indicates the first faulty PU channel in
hexadecimal (1…C).
See A5EA Measurement circuit

temperature (page 442).
Check setting of 95.04 Control board

supply.
Check the connection between the

YYZZ). “XXX” specifies the transmitter
FIFO error code. With parallel-connected
modules, “Y YY” specifies the affected
BCU control unit channel (0: broadcast).
“ZZ” specifies the error source
(1: Transmitter side [link error], 2:
Transmitter side [no communication], 3:
Receiver side [link error], 4: Receiver
side [no communication], 5: Transmitter
FIFO error XXX, 6: Module [xINT board]
not found, 7: BAMU board not found).
Check the connection between the


quoting the auxiliary code.
Check the auxiliary code (format
ZZZY YYXX). “YY Y” specifies the
affected inverter module (0…C, always 0
for ZCU control units). “XX” specifies the
affected power supply (1: Power supply
1, 2: Power supply 2).

Check that the value of 95.13 Reduced

run mode corresponds to the number of
inverter modules present. Check that the
modules present are powered from the
DC bus and connected by fiber optic
cables to the BCU control unit.
If all modules of the inverter unit are in
fact available (eg. maintenance work has
been completed), check that parameter
95.13 is set to 0 (reduced run function
disabled).

Check the feedback signal coming from

the charging system.
Check power unit logic and firmware
compatibility.
Reboot the control unit (using parameter
power. If the problem persists, contact




each code below.
8006 - Not enough memory for the application
8007 - The application contains the wrong library version
800A - The application contains an unknown target (System) library function.
Record the auxiliary codes of all active

licensing faults and contact your product
vendor for further instructions.
Switch off the power to the control unit
and reinstall the memory unit.
In case the memory unit was not actually
removed when the fault occurred, check
that the memory unit is properly inserted
into its connector and its mounting screw
is tight. Reboot the control unit (using
parameter 96.08 Control board boot) or
by cycling power. If the problem persists,
contact your local ABB representative.

Ensure that a valid user parameter set

exists. Reload if uncertain.

Try forcing a save using parameter 96.07

Parameter save manually. Retry.
Fieldbus adapter (FBA) and 51 FBA A
settings.

Fieldbus adapter (FBA) and 54 FBA B
settings.
Check the status of the fieldbus master

(online/offline/error etc.).
Check cable connections to the XD2D
connector on the control unit.
Check the settings in parameter group 58

Embedded fieldbus.
Reset the fault. Contact your local ABB

representative if the fault persists.
Check that all option modules are
properly seated in their slots.
Check that all option modules or slot
connectors are not damaged. To pinpoint
the problem, try installing the modules
into different slots one at a time.

connection.
Disconnect and reconnect the control
panel.
specifies the I/O port used as follows: 0:
Panel, 1: Fieldbus interface A, 2:
Fieldbus interface B, 3: Ethernet, 4:
D2D/EFB port).
Check the auxiliary code (format XXYY YYYY). “XX” specifies the number of the I/O
extension module (01: parameter group 14 I/O extension module 1, 02: 15 I/O extension
module 2, 03: 16 I/O extension module 3). “YY YYYY” indicates the problem (see actions
for each code below).
00 0001 - Communcation with module failed - Check that the module is properly seated
in its slot.
Check that the module and the slotconnector is not damaged.
Try installing the module into another slot.
00 0002 - Module not found. - Check the type and location settings of the modules
(parameters 14.01/14.02, 15.01/15.02 or 16.01/16.02).
Check that the module is properly seated in its slot.
Check that the module and the slot connector is not damaged.
00 0003 - 00 0004 - Configuration of module failed. - Check the type and location
settings of the modules (parameters 14.01/14.02, 15.01/15.02 or 16.01/16.02).
Check that the module is properly seated in its slot.
Check that the module and the slot connector is not damaged.

Check that a brake resistor has been

connected.
Check the condition of the brake resistor.
Check the dimensioning of the brake
resistor.

Brake chopper).
Check fault limit setting, parameter 43.11
Brake resistor fault limit.
limits.
Check brake chopper and brake resistor
connection.
power.
Ensure brake resistor is connected and

not damaged.
Check the electrical specifications of the
brake resistor against the Hardware
manual.
Replace brake chopper (if replaceable).
power.

Check for excessive ambient temperature.
Check the dimensioning and cooling of the cabinet.
Check resistor overload protection function settings (parameter group 43 Brake
chopper).
Check that drive supply AC voltage is not excessive.

control.

control.

control (especially 44.11 Keep brake
closed).
Check that acknowledgement signal (if
used) matches actual status of brake.
Check the source signal selected by

parameter 44.12 Brake close request.
Check the safety circuits connected to
the FSO-xx safety functions module.
Check external fan (or other equipment
controlled) by the logic.
Check settings of parameters
35.100…35.106.
See A7B0 Motor speed feedback (page

447).
Check minimum/maximum speed

settings, parameters 30.11 Minimum
speed and 30.12 Maximum speed.
Check need for brake chopper and
resistor(s).
Check the status of motor current

measurement.
Perform a Normal, Advanced or
Advanced Standstill ID run instead of, for
example, a Reduced or Standstill ID run.
See parameter 99.13 ID run requested
(page 379).
If using a control panel or the Drive

composer tool, connect to the supply unit
to read the fault code. Refer to the
firmware manual of the supply unit for
instructions related to the code.

See A7E1 Encoder (page 448).
See A797 Speed feedback configuration

(page 445).
Check the auxiliary code (format XXYY ZZZZ). “XX” specifies the number of the
encoder interface module (01: 91.11/91.12, 02: 91.13/91.14), “YY” specifies the
encoder (01: 92 Encoder 1 configuration, 02: 93 Encoder 2 configuration). “ZZZZ”
indicates the problem (see actions for each code below).
0001 - Load gear definition invalid or outside limits. - Check load gear settings
(90.53 and 90.54).
0002 - Feed constant definition invalid or outside limits.Check feed constant
settings (90.63 and 90.64).
0003 - Motor/load gear definition invalid or outside limits. - Check motor/load gear
settings (90.61 and 90.62).
0004 - Encoder not configured. - Check encoder settings (92 Encoder 1
configuration or 93 Encoder 2 configuration). Use parameter 91.10 Encoder
parameter refresh) to validate any changes in the settings.
0005 - Encoder stopped working - Check encoder status

Emergency ramp supervision and 31.33
Emergency ramp supervision delay.
Check the predefined ramp times
(23.11…23.19 for mode Off1, 23.23 for
mode Off3).
Ramp stop supervision and 31.38 Ramp
stop supervision delay.
Check the predefined ramp times in
parameter group 23 Speed reference
ramp.

interface.
Fieldbus adapter (FBA), 51 FBA A
settings, 52 FBA A data in and 53 FBA A
data out.
communicate.

interface.
Fieldbus adapter (FBA).
communicate.
Check status of other converter

(parameters 06.36 and 06.39).
DDCS communication. Check the
corresponding settings in the control
program of the other converter.
replace cables.
Check status of controller. See user

documentation of controller.
DDCS communication.
replace cables.
See A7CB MF comm loss (page 448).
Check fault status of supply unit (or other

converter).
Refer to the firmware manual of the
supply unit.
Check the auxiliary code (format XXXX
XYZZ). “Y” specifies the location of the
input (0: Control unit, 1: I/O extension
module 1, 2: I/O extension module 2, 3:
I/O extension module 3). “ZZ” specifies
the limit (01: AI1 under minimum, 02: AI1
above maximum, 03: AI2 under
minimum, 04: AI2 above maximum).
Check signal level at the analog input.
Check the wiring connected to the input.
Check the minimum and maximum limits
of the input in parameter group 12
Standard AI.
Check the source of the fault (parameter

32.07 Supervision 1 signal).







Check safety circuit connections. For more information, see appropriate drive hardware
manual and description of parameter 31.22 STO indication run/stop (page 246). Check
the auxiliary code, The code contains location information, especially with parallel-
connected inverter modules. When converted into a 32-bit binary number, the bits of
the code indicate the following: 31…28: Number of faulty inverter module (0…11
decimal). 1111: STO_ACT states of control unit and inverter modules in conflict
23…12: STO1 of inverter modules 12…1 (Bits of non-existing modules set to 1)
Check safety circuit connections. For more information, see appropriate drive hardware
manual and description of parameter 31.22 STO indication run/stop (page 246). Check
the auxiliary code, The code contains location information, especially with parallel-
connected inverter modules. When converted into a 32-bit binary number, the bits of
the code indicate the following: 31…28: Number of faulty inverter module (0…11
decimal). 1111: STO_ACT states of control unit and inverter modules in conflict
Power down the control unit.

Check that the memory unit is properly inserted into the control unit.
Power down the control unit. Attach a memory unit (with the appropriate firmware) to
the control unit.
Check the nominal motor values in parameter group 99 Motor data.
Check that no external control system is connected to the drive. Cycle the power to the
drive (and its control unit, if powered separately). Check that the motor shaft is not
locked.
Check the auxiliary code. The second number of the code indicates the problem (see
actions for each code below).
0001 - Maximum current limit too low. - Check settings of parameters 99.06
Motor nominal current and 30.17 Maximum current. Make sure that 30.17 > 99.06.
Check that the drive is dimensioned correctly according to the motor.
0002 - Maximum speed limit or calculated field weakening point too low. - Check
settings of parameters
• 30.11 Minimum speed
• 30.12 Maximum speed
• 99.07 Motor nominal voltage
• 99.08 Motor nominal frequency
• 99.09 Motor nominal speed.
Make sure that
• 30.12 > (0.55 × 99.09) > (0.50 × synchronous speed)
• 30.11 < 0, and
• supply voltage > (0.66 × 99.07).
0003 - Maximum torque limit too low. - Check settings of parameter 99.12 Motor
nominal torque, and the torque limits in group 30 Limits. Make sure that the maximum
torque limit in force is greater than 100%.
0004 - Current measurement calibration did not finish within reasonable time.
0005....0008 - Internal Erro
0009 - (Asynchronous motors only) Acceleration did not finish within reasonable time.
000A - (Asynchronous motors only) Deceleration did not finish within reasonable time.
000B - Asynchronous motors only) Speed dropped to zero during ID run.
000C - (Permanent magnet motors only) First acceleration did not finish within
reasonable time.
000D - (Permanent magnet motors only) Second acceleration did not finish within
reasonable time.
000E....0010 - Internal Error
For auxiliary codes 0004 - 0010 Contact your local ABB representative.
Check the auxiliary code. Add 2 to the

code to find out the node address of the
faulted drive.
Correct the fault in the follower drive.
Check the fault information provided by

the PLC.

the PLC.

the Modbus controller.
** These trips cannot be reset for 10 seconds after they occur.

** These trips cannot be reset for 10 seconds after they occur.
* The Enable/Reset terminal will not reset an O.Ld1 trip. Use the Stop/Reset key.
Replaced cable, Replace controller of the CT

software problems.
Also, check othe

Switch off/on the voltage, sometimes the failure is recoverable!® If still

no operation? Continue checklist.
- In case of warranty, replace the module.
- In case of non-warranty, carefully open the module a
G120

Check external par
failure display.
- ‘Watchdog’ error. Check for part number. If below 1900 0700 05, replace
with new version.
- Switch off/on the voltage, sometimes the failure is
failure display.
failure display.
failure display.
failure display.
failure display.












Please connect COM module to regulator before autoconfiguration.

Make sure that there is only ONE COM module for the VSD. Then restart
autoconfiguration.


communicating with Master module. 7002 implies no. 2 module is not c
Try to reprogram
Try to reprogram

for SDP4win) is required. The cable i



• Load or load step too high?
• Reduce ramp-up time (P1120).
• Motor power (p0307) must match inverter power (r0206).
• Use setting P0290 = 0 or 2 for preventing F00006.

• Load or load step too high?
• Motor nominal overtemperatures (p0626 - p0628) must be correct
• Motor temperature warning level (p0604) must match
• the connection of the motor temperature sensor to the control unit
• the setting of p0601
Remedy: Check the input wiring of the mains phases
Remedy:
Note: Framesizes D to F: this fault only occurs on inverters that have 3 current sensors.
Remedy: Contact Service Department.

Change inverter power module
Remedy: Check motor connection.
Remedy: Check Inverter and Motor wiring
• Reduce regeneration from active load

• Reduce ramp down rate
• Increase Imax regeneration limit in p1253
• r0949 = 0: is the motor connected to the inverter.
• r0949 = 1-49: are the motor data in p0304 - p0311 correct.
• Check what type of motor wiring is required (star, delta).
Remedy: Make sure motor has data been entered correctly.

Motor data identification needs to have been done.
• Must be Power Cycled to cancel this bug as some parameters may not be read correct.
• Factory Reset and new parameterization, if power cycle does not remove fault
• Change inverter control unit
• Change some parameters back to default values if the
• r0949 = 1: Failed reading PS identity

• r0949 = 2: PS identity wrong
• r0949 = 3: Failed reading PS version
• r0949 = 4: PS version wrong
• r0949 = 5: Start of Part 1 PS data wrong
• r0949 = 6: PS number of temp. sensor wrong
• r0949 = 7: PS numb
• Factory Reset and new parameterization

• Change BOP
• r0949 = 5096 : Use a BOP with a bigger EEPROM
• r0949 = 9160 : Use a BOP with a smaller EEPROM
• r0949 = 1000 + Block No: Reading data block failed
• r0949 = 3000 + Block No: Reading data block
Remedy: Fit BOP and try again.
Remedy: Download to BOP or replace BOP.
created on another type of drive.
Check connection between inverter power module and inverter control unit
Fault appears sporadically:
• Communication failure due to EMC problems
• Check - and if necessary - improve EMC
• Use EMC filter
Fault appears immediately when mains voltage is a
• r0949 = 0: Use MMC-PS with FAT12 or FAT16 format or correct MMC-PS Type, or fit an
MMC-PS to Drive.
• r0949 = 1: Check MMC ( e.g is MMC full ) - Format MMC again to FAT16
• r0949 = 2: Put the correct named file in the correct directory /USER/SINAMICS
Remedy: Recopy and ensure operation completes.
Remedy: Ensure clone from compatiable drive type.
Remedy: If a automatic clone is required:

- Insert MMC with correct File anc power cycle.
If no automatic clone is required:
- Remove MMC if not needed and power cycle.
- Reset P8458 = 0 and power cycle.
• Check and improve - if necesarry - the value in p2040

• Acknowledge fault
• if fault persists, change inverter control unit
Remedy: Check and if necessary improve the monitoring time in the STARTER SW while
getting the command source.
Check USS master
Remedy: Check USS master
Remedy: • Check and improve - if necesarry - the value in p3984

• Acknowledge fault
• if fault persists, change inverter control unit
Remedy: • Check P2106.

• Disable control word 2 bit 13 as command source.
• Disable terminal input for fault trigger.
Remedy: Stop the inverter.

• r0949 = 2, Increase value of p0494 or reduce value of p1120 and p1121.
• r0949 = 5, select encoder type via p0400.
• r0949 = 5, select SLVC mode (p1300 = 20 or 22).
• r0949 = 7, select SLVC mode (p1300 = 20 or 22).
• Check con
Change inverter control unit.

Change inverter control unit
Remedy: • Change value of p2268.

• Adjust feedback gain.
F00222 PID Feedback above max.
• Change value of p2267.

• Adjust feedback gain.
nternal Failures can not be fixed.

r0949 = 13 - Make sure the right power module is fitted
Note: Fault needs power cycle to be acknowledged.
Remedy: Safety Units:

An Acceptance Test needs to be performed. Follow the the steps of the Acceptance Log
which is part of the Operating
Instructions.
After performing the acceptance test the fault can be acknowledged by the following
procedure:
P0010 =
Remedy: Restart C2 connection.
Check the following:

• No breakage, seizure or obstruction of drive train.
• If using an external speed sensor, check the following parameters for correct function:
• If using the torque envelope, check parameters:
• Apply lubrication if required.
• Reduce ramp rate in p1120

• Enable flying start (p1200 equal to 1)
• Increase boost in p1611
• Connect motor or use larger motor for this inverter or use VF mode (p1300 less than
20).
• Correct the wiring to the motor and / or the encoder as requir

• Motor power (P0307) must correspond to inverter power (r0206).
• Cable length limits must not be exceeded.
• Motor cable and motor must have no short-circuits or earth faults
• Motor parameters must match the motor in us
Remedy: If this warning is displayed permanently, check drive input voltage.
Remedy: Check main supply voltage.
Remedy: Note:
r0037 = 0: Heat sink temperature
r0037 = 1: Chip junction temperature (includes heat sink)
Check the following:
• Ambient temperature must lie within specified limits
• Load conditions and load steps must be appropriate
• Fan must turn wh
Remedy: Check that load cycle lies within specified limits.
Remedy: Check that load steps and shock loads lie within specified limits.

• the connection of the motor temperature sensor to the control unit
• the setting of p0601
Remedy: Independently of the kind of temperature determination check:

• P0604 motor temperature warning threshold
• P0625 motor ambient temperature
If P0601 = 0 or 1, check the following:
• Check if name plate data are correct? If not perform quick com
Remedy: Check motor connection
Remedy: Reduce the breaking energy.

Use a breaking resistor with a higher rating.
Remedy: The motoring or regenerative load is too large.
Remedy: Remove MMC-PS from drive.
Remedy: Stop inverter and then

• Check encoder fitted. If encoder fitted and r0949 = 5, select encoder type via P0400.
• If encoder fitted and r0949 = 6, check connections between encoder module and
inverter.
• If encoder not fitted and r0949 = 5, sele
Remedy: Contact Service Department
Remedy: check parameter and/or configuration telegram
Remedy: power cycle
Remedy: check the cables and the bus hardware
Remedy: check bus transmission
Remedy: temporary, if permanent the fault detection is activated
Remedy: temporary, if permanent the fault detection is activated
Remedy: if permanent power cycle, reload firmware

Remedy: check DIP switch and/or P0918
Remedy: Check CB hardware
Remedy: Check CB parameters

• Input voltage must lie within range.
• Load must be match.
• In certain cases apply braking resistor.
Note: Higher inertia requires longer ramp times; otherwise, apply braking resistor.

• Parameter settings for output identical
• Parameter settings for input identical
• Parameter settings for output do not correspond to AO type
Set P0777 and P0779 to different values.
Remedy: Check that motor is connected to inverter.
Remedy: Do not press JOG right and left simulutanously.

Remedy: Alarm disappears when PID Autotuning has finished.

• No breakage, seizure or obstruction of drive train.
• If using an external speed sensor, check the following parameters for correct function.
• If using the torque envelope, check parameters:
• Apply lubrication if requi
• r0949 = 100 or 200

Increase the ramping times p1120/p1121 or the safety tolerance p9691/p9891,
check the motor parameters (p0394 - p0311) or run the motor identification (p1910)
again.
Decrease the rate of switching the safety signals or lower the cycl
• Power-cycle CU (since fault F1601 cannot be acknowledged).

• Make sure that CU is connected correctly to PM.
• Reduce EMC.
Load safety parameters again.
• Reduce EMC.
• Perform a forced dynamisation
• Inverter hardware is faulty or problem in processor communication. Perform a power

cycle.
• Check application or increase safety threshold p9691/p9891.

• See also remedies for F1614.
• Increase ramping times p1120 and p1121.

• Make sure that drive is not at current limit when starting.
• See remedies for F0453.
• Check hardware speed estimation circuit.
• r0949 = 100:
• Check supply voltage.
• Reduce EMC.
• r0949 = 101:
• Check ambient temperature.
• Run self-test again (set bit 1 in p9601 and p9801 and enter the STO mode, then leave
the STO mode again).
• Acknowledge safety fault.

• Restart inverter module or check EMC levels on accumulated faults.
• Check the wiring of the brake module

• Exchange brake module.
• Check all PROFIsafe settings (including your higher level failsafe control system).
• Acknowledge PROFIsafe fault.
• Perform safety commissioning.

• Try leaving via p3900 = 11.
• Retrigger the safety reset (perform a hot swap of the inverter module).
• Acknowledge fault and enter safety commissioning again. If not possible, leave the
safety commissioning with
p3900 = 11 and operate the drive with the old safety settings.
• Make sure that checksums in p9798 and p9898 are identical. If not, ensure that
parametrisation is identical
(p96xx = p98xx).
• Set checksum in p9799 or p9899 correctly.
• If setting the checksums not successful, leave safety commissioning via p3900 =
Remedy: Finish safety commissioning by setting p3900 = 10 or p3900 = 11 or wait until

safety reset is complete.
Remedy: Check consistency of safety input signals and acknowledge the following safe
torque off due to a drive fault.
Remedy: ad a) Reduce speed before entering the SLS or change the setting in p9692.
ad b) increase the tolerance in p9691/p9891 compared to p9690/p9890.
In both cases the passivated STO will be entered once zero frequency is reached.
Acknowledge the passiv
Remedy: Check if a deactivated gate driver or the current safety mode (STO, SS1, SLS) is
inhibiting the start. Check the inhibit
bit (r0052.6).
Remedy: Restart drive (perform power cycle) to load correct safety data.
Remedy: Finish commissioning with p3900 = 10 (accept changed) or p3900 = 11 (discard

changes) or wait until safety reset
is complete.
Remedy: Select and then de-select STO (p9601.bit1 and p9801.bit1 must be set).
- Check and make sure that the signal cable from the Masterdrive (X102:19 / 20) to the
Micromaster Eco (9/10) has good connection.
- X102: 19/20 provides 0 - 10 Vdc to the micromaster, verify this. If not, then maybe the
control card CUVC, of the Masterdr
Check whether supply voltage is within the limits indicated on the rating plate.
Increase the Ramp-down time (P003) or apply braking resistor (option).
Check whether the required braking power is within the specified limits.
- Check whether the motor power corresponds to the inverter power.

- Check that the cable length limits have not been exceeded.
- Check motor cable and motor for short - circuits and earth faults.
- Check whether the motor parameters (P080 - P085) corresp
- Check whether the motor is overloaded.

- Increase the maximum motor frequency if a motor with high slip is used.
- Check if the motor is overloaded
- Check the connections to the PTC
- Check that P087 has not been set to 1 without a PTC being connected
- Check that the ambient temperature is not too high.
- Check that the air inlet and outlet are not obstructed
- Check that the inverter's integral fan is working
- Check the serial interface
- Check the settings of the bus master and P091 - P093
- Check whether the time-out interval is too short (P093)
- Check the entire parameter set. Set P009 to '0000' before power down.
- Switch off power and switch on again
- Source of trip is digital input (configured as an external trip input) going low - check the
external source
- Switch off power and switch on again
- Disable flying start
- Ensure that P080 to P085 correspond to the name plate motor details.
- Adjust P386. Note that flying restart will not operate correctly with multi-motors.
Automatic re-start after fault (P018) is pending.
WARNING: Inverter may start at any time.

- Trip occurs only if P074 = 4, 5, 6 or 7. Check that the motor current does not exceed the
value set in P083 and P086
Parameterise fixed frequency(ies) on the digital inputs.
Set parameter P012 < P013
Change the settings of digital inputs P051 to P055 and P356
Motor not connected to inverter - connect motor.
If the fault persists, set P088 = 0 and then enter the measured stator resistance of the
motor into P089 manually.
Set parameter P211 < P212

Check motor cable and motor for short - circuits and earth faults.
Increase “Timeout + Holding Torque Time”
Check if the Run Enable contact on the converter is closed. Also check if the Elektronikon
closes this contact. (K09)
Use a higher software version then: 1900525020 or 1900525023.

Use a higher database version then: 1900521100_08.ds5
Check the limitations of the current protections.
- Check for the status of the drive - check for overload of drive, motor health, etc
- The warning bit can be turned off again by the time the Elektronikon decides to do a
shutdown handling. So 16#F2F1 i
Service Switch = 0 , ie should be set to OFF

closes this contact (K09).
Check the converter display for the active alarm.
Check the converter display for active fault.

Check the converter display for the active fault.
Check the converter display for the active fault.

Check the connections of the Run Enable contact between the Elektronikon Controller
(K09) and the Converter.
Verify in drive menu 1.6 if Ref.1 Channel (Fr1 on the integrated 7-segment display) is set
to Modbus (Mdb).
- Check the cable, and connectors for loose connections
- Check and confirm that the Power Supply is OK. The power supply board provides the
+/- 5V for the RS485 port also, if this is faulty, then there will be no communication.
Please note that this fau
- Power DOWN and give it a few minutes rest, power Up again.
- New download of Elektronikon and / or converter might be required

Check the datasheets of the converter for the meaning of fault number xxxx.
Check the line termination
Consult Atlas Copco

- See also timeout/wrong Baudrate.
- Consult Atlas Copco

Service Switch = 0
Parameter P2013 must be 3
closes this contact.
(K09)
On extremely rare occasions, the elektronikon and / or converter got corrupted, due to
whatever reasons, this incorrect feedback may happens, so WRONG STATUS word is
shown.
- Remedy: Please reprogram both the Elektronikon and the converter.
- Check the drive for other messages, normally external faults are programmed to
monitor conditions around the drive, eg, status of fanmotor, etc
Check service switch, K0something relay (please check with your service diagram for
correct relay ..K05, K06, K09, etc). Could be I / O board faulty. Could be there is no 24V
feed to the digital inputs due to power supply card faulty. Please check these.
Replaced sensor. Check wiring

Tighten this connector
Investigate mains power problem
Remove the terminator resistances
Terminator resistances must be mounted on the end nodes of the bus, not on the
intermediate node(s) NOTE: this error appears for the end node, not the intermediate
node!
Configure the correct CAN port (see TBD)

CAN port = 3 must be configured for BOV,
CAN port = 4 must be configured for IGV
Fit these connectors correctly
IGV shows external fault (drive converter error, error code 0x1f),
KEB display shown E.EF
remove the terminator resistances
Terminator resistances must be mounted on the end nodes of the bus, not on the
intermediate node(s)
NOTE: this error appears for the end node, not the intermediate node!
Apply correct pinout to the CAN connector

Mount the KEB-drives correctly
Apply the bridge for switching ST
consult annex 1
Investigate and correct the problem along the mechanical load path
correct the problem with the hard stop
Power off and on the controller (or the entire compressor), note down the KEB-drive
error prior to attempting reset
Mount the terminating resistances
Remove the terminating resistances
Apply the bridge for switching ST

Investigate and correct the problem along the mechanical load path
Modify parameters on MK5: Delay at signal: 20 s Position Tolerance Regulation Actual

=350 x 0.01% = 3.5%
Download the KEB with a correct set of parameters, reboot Mk5 by pressing the left and
right key simultaneously in inoperative mode (works only for ZH)
Remove the short circuit, apply the correct pin-out, make sure the CAN is still
operational
Correctly fit this connector
Download the correct Mk5 parameter set for the compressor

Lookup error type and code of the converter, re-asses the problem based on this
information
440: Check: - Motor power (P0307) must correspond to inverter power (r0206) - most
likely programming fault after modification
- Check short circuits of motor / cable
- Check motor parameters -> should match motor in use
- Value of stator resistance (P035
440: - Check supply voltage (P0210) must lie within limits indicated on rating plate
- DC-Link voltage controller must be enabled and correctly parametised
- Ramp-down time (P1121) must match inertia of load
- Required braking power must lie within speci
440: Check - Supply voltage (P0210) must lie within indicated on rating plate
- Supply must not be susceptible to temporary failures or voltage reductions
- Enable kinetic buffering (P1240 = 2)
- Supply interruption:
If the supply is disconnected while t
440: Check that fan must turn when inverter is running

- Pulse frequency (P1800) must be set to default value
- Ambient temperature could be higher than specified for the inverter
- for MM440 FX and GX:
=> Fault value = 1 Rectifier overtemperature
440: - Check Load cycle must lie within specified limits

- Motor power must match inverter power (r0206)
- This fault is caused when the converter calculates that it is overloaded. This will occur
when the converter is operated above its continuous rated
- Check nominal overtemperatures (P0628-P0628) must be correct

- Motor temperature warning level (P0604) must match
- Check if name plate data are correct (if not perform quick commissioning)
- Perform motor identi
If a temperature sensor is fitted to the motor, and connected to the inverter and
monitoring activated (P0601=1 or 2), then an F0015 will be indicated if the connection or
sensor is broken giving a short or open circuit.
Check the wiring to the sensor, an
Check the input wiring of the mains phases

A Report from the field:
Found that the compressor didn't have a "normal" noise , not mechanical noise but
strange noise.
One of our technican went on plant and found the problem. On this unit, there is cables
- Check I/O board. It has to be firmly inserted.

- Check the fault history and values as these will lead to the sympton of the cause.
- Check the PX modules, maybe the IGBT / drivers gone, or the TDB and thyristors, or
may be both. Please use a multimete
Check motor
Replaced fan
Fault = 0 Check motor is connected to inverter

Fault = 1-40: Check if motor data in P0304 to P0311 are correct
Check what type of motor wiring is required (star, delta)
- Factory reset and new parameterisation

- Consult Atlas Copco
Hardware defect
- Check data
- Change I/O
Check Data
Change IO board
Change inverter, if all else fail
Check CB and communication partner

Check USS master
Check USS master
Disable for example, the terminal for fault trigger
- Check encoder fitted. If encoder not fitted, set P0400 = 0 and select SLVC mode
(*P1300 = 20 or 22)
- If encoder fitted, check correct encoder selected (Check encoder set-up in P0400_
- Check connections between encoder and inverter
- Check encoder not
Run self test routines
- Change value of P2268

- Adjust feedback gain
- Change value of P2267
- Adjust feedback gain
Hardware problem, contact Atlas Copco.
Check - No breakage, seizure or obstruction of drive train

2. If using an external speed sensor, check for correct function. Check parameters
==> P2192 (Delay time for permitted deviation)
3.
440: Check: - Motor power (P0307) must correspond to inverter power (r0206) - most
likely programming fault after modification
- Check short circuits of motor / cable
- Check motor parameters -> should match motor in use
- Value of stator resistance (P035
440: - Check supply voltage (P0210) must lie within limits indicated on rating plate
- DC-Link voltage controller must be enabled and correctly parametised
- Ramp-down time (P1121) must match inertia of load
- Required braking power must lie within speci
440: Check - Supply voltage (P0210) must lie within indicated on rating plate
- Supply must not be susceptible to temporary failures or voltage reductions
- Enable kinetic buffering (P1240 = 2)
Check that fan must turn when inverter is running
- Pulse frequency (P1800) must be set to default value
- Ambient temperature could be higher than specified for the inverter
Load duty cycle must be within limits
- Motor power (P0307) must match inverter power (r0206)
Check nominal overtemperatures (P0628-P0628) must be correct
- Motor temperature warning level (P0604) must match

- Check if name plate data are correct (if not perform quick commissioning)
- Perform motor identif
1. Increase duty cycle P1237
2. Increase ramp down time P1121
Stop inverter and check:

- Whether Encoder is fitted, if not set P0400 = 0 and select SLVC mode (P1300 = 20 or 22)
- If fitted, check correct encoder selected (check encoder set-up in P0400)
- Check connections between encoder and inverter
- Check encoder
Check that input voltage (P0210) must lie within range

- Load must be matched.
Check - No breakage, seizure or obstruction of drive train
2. If using an external speed sensor, check for correct function. Check parameters
==> P2192 (Delay time for permitted deviation)
3.
- Check the motor connections

- Increase the ramp-up time P1120 or the ramp down time P1121
- activate the flying restart function P1200
- use a (larger) motor
- Increase the voltage boost (P1611) for sensorless closed loop vector control
- use closed loo
• Check if main supply voltage is within specs. Check Main fuses.
• Check for loose connectors at the control unit of the inverter and Elektronikon.
• Check for tripped fuses at the secondary of the transformer T1 in the electrical panel
• Check if main supply voltage is within specs. Check Main fuses.

• Check for loose connectors at the control unit of the inverter and Elektronikon.
• Check for tripped fuses at the secondary of the transformer T1 in the electrical panel
• Check if main supply voltage is within specs.
• Check Main fuses.

* Sometimes, if VSD is in operation, and power is lost, this msg comes up. But usually
with DC link undervoltage, it is self reset

* Sometimes, if VSD is in operation, and power is lost, this msg comes up. But usually
with DC link undervoltage, it is self reset


• Let drive cool off .
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle .
• Ensure proper flow of cooling air in compressor room.
• Check if supply voltage is within specs.
* Check for earth fa
• Let drive cool off .

• Clean inlet filter cubicle .
* Check for earth fa

• Check main fuses.
• Check main fuses.
• Let drive cool off.
• Clean inlet filter cubicle.



















• Check emergency stop button

• Check for loose connectors at the control unit of the inverter.
• Check the temperature switch
• Try to reset the error.
• If error returns, contact service.
* Motor / element seized
* Motor / element seized **** For GA55-90VSD ==> Failure can’t be resettable;
 Occasionally it happened during commissioning, which means running hours < 2 hours
 Converter SN information showed that its’ manufacturing date is from 32th week 2016
– 7th week 2017. ***** Please see ECB WUXI 0155 (P IV). A replacement convertor is
required. 90kw ==> 1900 5350 01; 75kw ==> 1900 5350 02; 55kw ==> 1900 5350 03.
* Check output for shortcircuit

* Use Multimeter & diode checks

* Check supply voltage is within spec
* Check for correct input voltage settings
* Check for earth fault of motor. Usually this is the main cause of overvoltage.
* Check supply voltage is within spec

* Check for correct input voltage settings
* Check for earth fault of motor. Usually this is the main cause of overvoltage.
Firmware update using the commissioning software:

The firmware version of all of tge components on the "version overview" page
can be read in the Project Navigator under "Configuration" of the associated
drive unit and an appropriate firmware update can b
Switch off the power supply of the specefied DRIVE-CLiQ component and Switch
on the power again.
For the CompactFlash card, restore the status when originally supplied from the
factory.
Note:
The file involved can be read out using parameter r9925. See also, r9926
On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA or
/ADDON/SINAMICS/DATA has been
illegally changed with respect to that supplied from the factory. No changes are
permitted in this directory.
The problem is indicated in the first digit of the alarm value:
1: File does not exist.
2: Firmware version of the file does not match the software version.
3: The file checksum is incorrect.
The second digit of the alarm value indicates in which directory the file is
located:
0: Directory /SIEMENS/SINAMICS/DATA/
1: Directory /ADDON/SINAMICS/DATA/
The third digit of the alarm value indicates the file:
0: File MOTARM.ACX
1: File MOTSRM.ACX
2: File MOTSLM.ACX
3: File ENCDATA.ACX
4: File FILTDATA.ACX
5: File BRKDATA.ACX
If you saved the project in STARTER, download your project again and save using
the function "Copy RAM to ROM" or with P0977 = 1. This means that all of the
parameter files are again completely written into the CompactFlash card.
Restore the factory setting using (p0976 = 1) and re-load thje project into the
drive unit. Operation without any restrictions is then possible,
After downloading the project, save the parameterisation in STARTER using the
function "Copy RAM to ROM" or P
Restore the factory setting using (p0976 = 1) and re-load thje project into the
drive unit. Operation without any restrictions is then possible,
After downloading the project, save the parameterisation in STARTER using the
function "Copy RAM to ROM" or P
Restore the factory setting using (p0976 =1) and re-load the project into the
drive unit. Operation without any restrictions is then possible.
After downloading the project, save the parameterization in STARTER using the
function "Copy RAM to ROM" or wit
Check whether the write-protected attribute has been set for the files on the
CompactFlash card under . . . /USER/SINAMICS/DATA/ . . . When required,
remove write protection and save again, (eg. Set P0971 to 1)
- Reduce the sampling time
- Only use one data set (CDS, DDS)
- de-activate the function module
- de-activate the drive object
- remove the drive object from the target topology
Note: After executing the appropriate counter-measure, a new calculation mus
- Reduce the sampling time

- Only use one data set (CDS, DDS)
- de-activate the function module
- de-activate the drive object
- remove the drive object from the target topology
Remove the error for the inactive encoder.
Select the re-synchronization interval so that the synchronization deviation

between the time master and drive system
lies within the tolerance window.
See also: r3108 (RTC last synchronization deviation)
- Power down the drive system

- re-insert the Compact Flash card that was withdrawn - this card must match
the drive system.
- power up the drive system again.
- check the DRIVE-CLiQ cables.
- set a valid sampling time.
See also: p0115, p0799 (CU inputs/outputs, sampling time), p4099
Set a valid pulse frequency.

See also: p0113 (Minimum pulse frequency, selection)
For alarm value r2124 < 256, the following applies:

- Delete (clear) the fault memory on the drive object on which the alarm
occurred (P0952 = 0)
- As an alternative, delete (clear) the fault memories of all drive objects (P2147 =
1)
- Replace the Control
- Carry out a POWER ON

- Replace the Control Unit
Update the firmware (p7828, p7829 and commissioning software).
None necessary.
This alarm automatically disappears after the firmware has been updated.
- remove the corresponding component.

- change the setting "de-activate and not present".
Note:
Under "Topology --> Topology view" the commissioning software offers
improved diagnostics capability (e.g. setpoint/
actual value comparison).
See also: p0105
The alarm automatically disappears again with the following actions.

- De-activate the drive object involved (P0105 = 0)
- De-activate the components involved (P0125 = 0, P0145 = 0, P0155 = 0, P0165
= 0)
- Re-insert the components involved.
See also: P01
The alarm automatically disappears again with the following actions:

- de-activate the drive object involved (p0105 = 0).
- de-activate the components involved (p0125 = 0, p0145 = 0, p0155 = 0, p0165 =
0).
- re-insert the components involved.
See also: p0

- activate the drive object involved (P0105 = 1)
- Again, withdraw the components involved.
See also P 0105

- activate the drive object involved (p0105 = 1).
- again withdraw the components involved.
See also: p0105 (Activate/de-activate drive object)

- activate the components involved (p0125 = 1, p0145 = 1, p0155 = 1, p0165 = 1).
- again withdraw the components involved.
See also: p0125 (Activate/de-activate power unit components), p
Clear alarm:
Set p9496 to 1 or 2
or
de-activate DO again
Pulse inhibit
Set p0009 to 1 and change p0978:

Rules:
- p0978 must include all of the drive object numbers (p0101).
- it is not permissible for a drive object number to be repeated.
- by entering a 0, the drive objects with PZD are separated from those without
PZD.
-o

Rules:
PZD.
-o

Rules:
PZD.
-o

Rules:
PZD.
-o

Rules:
PZD.
-o
- adapt the output topology to the permissible requirements.

- carry out commissioning using the commissioning software.
- for motors with DRIVE-CLiQ, connect the power and DRIVE-CLiQ cable to the
same Motor Module (Single Motor
Module: DRIVE-CLiQ at X202
This component is assigned to a drive object.
Check the parameters for the data sets.
Examples:
- power unit (p0121).
- motor (p0131, p0186).
- encoder interface (p0140, p0141, p0187 ... p0189).
- encoder (p0140, p0142, p0187 ... p0189).
- Terminal Module
Re fault cause = 1:
Replace all NX10 or NX15 by a CX32.
Re fault cause = 2:
Replace all CX32 by an NX10 or NX15.
Adapting the topologies:

- undo the change to the actual topology by changing over the DRIVE-CLiQ
cables.
- commissioning software: Go online, upload the drive unit, adapt the topology
offline and download the modified
project.
- automatically remove the

cables.
project.

cables.
project.

cables.
project.
cables.
project.
- automatically remove the topology error (p9904).
Note:

cables.
project.

cables.
project.

cables.
project.

cables.
project.
- remove the additional component in the actual topology.
- download the target topology that matches the actual topology
(commissioning software).
Note:
Under "Topology --> Topology view" the commissioning software offers improve

- check the component soft-wired connections against the hardware
configuration of the drive unit in the commissioning
software and correct differences.
- parameterize the topology comparison of all components (p9906).
- parameter
Check the component soft-wired connections against the hardware

configuration of the drive unit in the commissioning
software and correct differences.
Note:
improved diagnostics capabili

- change over the actual topology to match the target topology.
Re byte cc:
cc = 1 --> can be acknowledged using p9904 or p9905.
cc > 1 -->

- automatically remove the topology error (p9904).
Note:
Under "Topology -->

Note:
In the software, a Double Motor Module behaves just like two separate
- delete the drive belonging to the power unit in the commissioning software
project and download the new configuration
to the drive unit.
- check that the actual topology matches the target topology and if required,
change over.
- check DRIVE-CLiQ cables
- re-configure the drive belonging to the Sensor Module in the commissioning
software project (encoder configuration)
and download the new configuration to the drive unit.
- delete the drive belonging to the Sensor Module in the commissioning software
pro
- delete the Terminal Module in the commissioning software project and

download the new configuration to the drive
unit.
change over.
- check DRIVE-CLiQ cables for interruption
- delete the DRIVE-CLiQ Hub Module in the commissioning software project and
download the new configuration to
the drive unit.
change over.
- check DRIVE-CLiQ cables for interru
- delete the CX32 / NX in the commissioning software project and download the
new configuration to the drive unit.
change over.
- check DRIVE-CLiQ cables for interruption and co
- delete the drive belonging to this component in the commissioning software

to the drive unit.
- re-configure the drive belonging to this component in the commissioning
software project and download the new
conf
- delete the option board in the commissioning software project and download
the new configuration to the drive unit.
- re-configure the drive unit in the commissioning software project and
download the new configuration to the drive
unit.
- check that th
- re-configure the drive belonging to the encoder in the commissioning software

project (encoder configuration) and
download the new configuration to the drive unit.
- delete the drive belonging to the encoder in the commissioning software
project and dow
- re-configure the drive belonging to this motor in the commissioning software

to the drive unit.
- re-configure the drive belonging to this motor in the commissioning software
project and download the new config
- set all open BICO interconnections centrally to the factory setting with p9495 =
2.
- make the non-operational drive object active/operational again (re-insert or
activate components).
The alarm automatically disappears as soon as no BICO interconnection (value =
0) is entered in r9498[29] and
r9499[29].
Notice:
When re-activating the drive object, all BICO interconnections should be checked
and if required, re-established.
None necessary.
carry out service/maintenance and reset the service/maintenance interval

(p0651).
Configure Ti and To low so that they are suitable for the DP cycle or increase the
DP cycle time.
Option for enabled drive-based SI monitoring (p9601/p9801 > 0):
Use the actual value sampling cycle p9511/p9311 and, therefore, set it
independently of the D
De-select the forced checking procedure of the safety motion monitoring

functions and then select again.
The signal source for initiation is parameterized in binector input p9705.
Note:
SI: Safety Integrated
See also: p9705 (SI Motion: Test stop signal so
Carry out the forced checking procedure of the safety motion monitoring
functions.
The signal source for initiation is parameterized in BI: p9705.
Note:
See also: p9705 (SI Motion: Test stop signal source)
None necessary.
Note:
CU: Control Unit
Select STO and then deselect again.

Note:
CU: Control Unit
STO: Safe Torque Off / SH: Safe standstill
After a longer period of time, if the message is not automatically withdrawn, the
following checks should be made
dependent on the communication:
For communication with SINUMERIK, the following applies:
- check additional messages that are present regardi
Check the bus configuring on the master and slave sides.

Re alarm value = 51:
Check the list of the drive objects with process data exchange (p0978). With
p0978[x] = 0, all of the following drive
objects in the list are excluded from the process data exch
Check the bus configuration:

- bus addresses
- slave configuring
- adapt the current and speed controller clock cycle.

Re alarm value = 9:
- carry out a POWER ON.
- check the number of specific drive object types in the configuration.
Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
Check the receive configuration data.

Re alarm value = 1:
objects in the list are excluded from the process data exchange.
Establish the PROFIBUS connection and activate the PROFIBUS master in the
cyclic mode.
- check parameters for clock cycle synchronization (ensure To > Tdx).
Note:
To: Time of setpoint acceptance
Tdx: Data exchange time
Set current controller clock cycles to identical values (p0115[0]).

Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
See also: p0115
Set the speed controller clock cycles the same (p0115[1]).

Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
See also: p0115
- check the master application and bus configuration.
- check the consistency between the clock cycle input when configuring the slave
and clock cycle setting at the master.
- ensure that the pulses of drive objects that are not controlled by
PROFIBUS/PRO
Check the master application and bus configuration.

Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
- check the master application and bus configuration.

- check the consistency between the clock cycle input when configuring the slave
and clock cycle setting at the master.
Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
- ensure that the master correctly increments the sign-of-life in the master
application clock cycle Tmapc.
- correct the interconnection of the master sign-of-life (p2045).
Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
- check the PROFIBUS cables.

- carry out a first commissioning of the Publisher that has the failed connection.
See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses)
Carry out a POWER ON (power off/on) for all components.

If the error occurs after the drive sampling times were adjusted, and if a TM31
module is being used, the sampling
times (p0115, p4099) should be set as integer multiples to the drive clock cycles
(p0115).
Carry out a POWER ON (power off/on) for all components of the DO.
Stop the function generator and restart again if necessary.

Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4800 (Function generator control)
Use the existing drive object with the corresponding number.
Note:
At least one drive to be connected must be specified in p4815.

Note:
Use a SERVO / VECTOR drive object with the corresponding number.

Note:
Note:
Change the operating mode for this drive object to p1300 = 20 (encoderless
speed control) or p1300 = 21 (speed
control with encoder).
Note:
For all of the drives specified for connection, set the speed setpoints to 0.
Note:
Set the relevant drives to zero speed before starting the function generator.
Note:
Fetch the master control to the specified drive object and set all enable signals.
Note:
Wait for magnetizing of the motor (r0056.4).

Note:
See also: r0056 (Status word, closed-loop control)
A02020 Function generator: Parameter cannot be
- stop the function generator before parameterizing (p4800 = 0).
- if required, start the function generator (p4800 = 1).
Note:
See also: p4800 (Function generator control)
Check and adapt the value for the period.

Note:
See also: p4821 (Function generator period)
Reduce pulse width.

Note:
See also: p4821 (Function generator period), p4822 (Function generator pulse
width)
Set a physical address with a value other than zero.

Note:
See also: p4812 (Function generator physical address
Adjust the offset value accordingly.

Note:
See also: p4826 (Function generator offset), p4828 (Function generator lower
limit), p4829 (Function generator
upper limit)
Check the value for the bandwidth and adapt accordingly.

Note:
Enter an existing time slice clock cycle. The existing time slices can be read out
via p7901.
Note:
See also: r7901 (Time slice cycle times)
Stop the trace and, if necessary , start again.
Check the selected recording time and if necessary adjust.
via p7901.
via p7901.
Enter the clock cycle of an existing time slice with a cycle time >= 2 ms for up to
4 recording channels or >= 4 ms
from 5 recording channels per trace.
The existing time slices can be read out via p7901.
Enter the clock cycle of an existing time slice with a cycle time >= 4 ms or reduce
the number of recording channels
to 4 per trace.
The existing time slices can be read out via p7901.
- specify the signal to be traced.

- check whether the relevant signal can be traced.
- specify the signal to be traced.

- check whether the relevant signal can be traced.
Specify a valid trigger signal
Use a valid data type.

- stop the trace before parameterization.
- if required, start the trace.
Check the pretrigger time setting and change if necessary.
- set p0118 to a value greater than or equal to the alarm value.

- set p0117 to an automatic setting.
- check the firmware releases of the components involved.
See also: p0117 (Current controller computing dead time mode), p0118 (Current
controller computing dead time)
- carry out a POWER ON (power off/on) for all components.

- upgrade firmware to later version.
- contact the Hotline.
Note:
OA: Open Architecture
See also: r4950, r4955, p4956, r4957
Carry out a POWER ON.
Check the terminals for the power supply voltage (X124, L1+, M).
Reduce the the natural frequency of the speed setpoint filter (PT2 low pass)
(P1417)
- Check if the ambient temperature within the defined limit values.

- have the load conditions and the load duty cycle been appropriately
dimensioned
- Has the cooling failed, ie the fan is stopped, either intermittently or faulty.
Check direction of fan

dimensioned?

dimensioned?
dimensioned?

dimensioned?
None necessary.
The alarm automatically disappears when the limit value is undershot.
Note:
If the alarm does not disappear automatically and the temperature continues to
rise, this can trigger fault F30024.
- If DC brake is active: reduce braking current (see p1232).
- inhibit the pulses of the faulted power module (P7001)

- Check the connecting cables. Loose contacts can cause current spikes
- The motor reactors are non-symmetrical or faulty and must be replaced
- The CTs must be calibrated or replaced.
- inhibit the pulses of the faulted power unit (p7001).

- check the DC link connecting cables.
- the DC link voltage measurement is incorrect and must be calibrated or
renewed.
Re-activate the de-activated power unit components.

See also: p0125 (Activate/de-activate power unit components), p0895
(Activate/de-activate power unit components),
p0897 (Parking axis selection)
- check the motor load and if required, reduce.

- check the motor ambient temperature.
- check the thermal time constant p0611.
- check the overtemperature fault threshold p0605 (= alarm threshold for the I2t
motor model)
- check that the sensor is connected correctly.
- check the parameterization (p0600, p0601).
See also: r0035, p0600, p0601, p0607, p4600, p4601, p4602, p4603, r4620
Restore units that have been changed over to the default value.
The signal at binector input p0840 (current CDS) as well as p3982 bit 0 must be
0.
- the automatic restart (AR) should, if required, be inhibited (p1210 = 0).
- an automatic restart can be directly interrupted by withdrawing the power-on
command (BI: p0840).
- set the terminal as input (p0728).

- de-select the measuring probe (p0488, p0489, p0580).
If the controller is not to intervene:

- increase the ramp-down times.
- disable the Vdc max controller
If the ramp-down times are not to be changed:
- use a chopper or regenerative feedback unit
- check whether the input voltage is within the permissible range.

- check whether the load duty cycle and load limits are within the permissible
limits.
The alarm disappears when power supply returns.
The alarm is automatically withdrawn when increasing the current limit (p0640),
reducing the load or using a slower
up ramp for the setpoint (reference) speed.
- check whether the input voltage is within the permissible range.
- check whether the load duty cycle and load limits are within the permissible
limits.
Re fault cause = 1:
- Shut down soft start (p1401.0 = 0).
- Shut down quick magnetizing (p1401.6 = 0).
Re fault cause = 2:
- De-energize flux build-up control (p1401.2 = 0).
Re fault cause = 3:
- Re-parameterize Rs identification (p0621 = 0, 1)
- increase the jerk limiting (p2574).

- reduce maximum acceleration or maximum deceleration (p2572, p2573).
None necessary.
This alarm automatically disappears after the offset has been saved.
Check the drive data sets, encoder data sets and encoder assignment.
(Encoder 3 encoder data set number), p0400 (Encoder type selection)
- reduce the maximum velocity (p2571).
- increase the sampling time for positioning (p0115[5]).
- check the entered setpoint velocity.

- reduce the velocity override (CI: p2646).
- increase the maximum velocity (p2571).
- check the signal source for the externally limited velocity (CI: p2594).
Check the appropriate input signals and correct.
Reference the system (search for reference, flying referencing, set reference
point).
- correct the traversing program.
- select an available traversing block number.
Resolve the reason as to why the edge is missing at binector input (BI: p2632).
- parameterize this traversing block with the block change enable END.
- parameterize additional traversing blocks with a higher block number and for
the last block, using the block change
enable END.
Correct the traversing blocks.
Correct the task parameter in the traversing block.
- correct the traversing block.

- add the missing traversing block.
- change software limit switch minus (CI: p2578, p2580).

- change software limit switch plus (CI: p2579, p2581).
- in the traversing block, correct the target position.

- change the modulo range (p2576).
Correct the traversing block.
Move away in the positive direction.

Move away in the negative direction.
- correct the target position.
- Check the maximum torque-generating current (r1533).
- check the torque limits (p1520, p1521).
- check the power limits (p1530, p1531).
- check the BICO interconnections of the torque limits (p1522, p1523, p1528,
p1529).
Connect a 1 signal to the binector input "no intermediate stop/intermediate

stop" (BI: p2640) and re-start motion.
Connect a 1 signal to the binector input "do not reject traversing task/reject
traversing task" (BI: p2641) and re-start
motion.
- check the mechanical system.

- check the parameterization of the window (p2602).
- check the causes and resolve.
- reset the control (BI: p2508 and BI: p2509 = 0 signal) and activate the
requested function.
Check the appropriate binector inputs and signals.
None necessary.
The alarm automatically disappears with BI: p2514 = 0 signal.
De-activate the measuring probe evaluation (BI: p2509 = 0 signal).

Re alarm value = 6:
Set the input terminal for the measuring probe (p0488, p0489 or p2517, p2518).
Check the Control Unit hardware.
Reduce the frequency of the measuring pulses at the measuring probe.
Re alarm value > 50000:
Set the clock cycle ratio of the measuring clock cycle to the position controller
clock cycle to an integer multiple.
To do this, the currently effective measuring clock cycle can be determined from
the alarm value as follows:
Tmeas[125μs] = alarm value - 50000.
With PROFIBUS, the measuring clock cycle corresponds to the PROFIBUS clock
cycle r2064[1].
Without PROFIBUS, the measuring clock cycle is an internal cycle time that
cannot be influenced.
In the drive data sets, assign the non-assigned motor data set using the MDS
number (p0186[0...n]).
- check whether all of the motor data sets are assigned to drive data sets.
- if required, delete superfluous motor data sets.
- if required, set up new drive data sets and assign to the corresponding motor
data sets.
See also: p0186 (Motor Data Sets (MDS) number)
- structure the data according to the rules of the "SIMODRIVE 611 universal"
interface mode.
- check the interface mode (p2038).C179
- parameterize the appropriate motor data sets differently (p0827).

- select the setting p0833.0 = 0 (motor changeover via the drive).
Re alarm value = 1:
Set the speed lower than the speed at the start of field weakening (r0063 <
p0348).
Re alarm value = 2, 3:
Check the feedback signals of the contactor involved.
- select the existing drive data set.

- set up additional drive data sets.C182
Reduce the speed below the speed at the start of field weakening.
- repeat the operation.

- check the DRIVE-CLiQ connection.
Set the reference point coordinate less than the value from the supplementary
information.
information.
information.
Acknowledge the encoder error using the encoder control word (G1_STW.15 =
1).
1).
1).
- Check and, if necessary, connect the encoder and/or encoder cable.

- Check and, if necessary, establish the DRIVE-CLiQ connection.
- In the case of encoders that cannot be identified (e.g. encoders without EnDat
interface), the correct encoder type
must be entered in p0400.
1).
1).
De-activate the measuring probe evaluation (BI: p2509 = 0 signal).

Re alarm value = 6:
Set the input terminal for the measuring probe (p0488, p0489 or p2517, p2518).
Check the Control Unit hardware.
Reduce the frequency of the measuring pulses at the measuring probe.
Set the clock cycle ratio between the PROFIBUS clock cycle and the position
controller clock cycle to an integer multiple.
- Check and, if necessary, connect the encoder and/or encoder cable.

- Check and, if necessary, establish the DRIVE-CLiQ connection.
- In the case of encoders that cannot be identified (e.g. encoders without EnDat
interface), the correct encoder type
must be entered in p0400.
Correct parameter p0141.
Check the encoder for the position actual value preprocessing.
None necessary.
None necessary.
None necessary.
Check the drive data sets, encoder data sets.


To changeover the drive data set, initially, exit the "operation" mode.
If required, reduce the traversing range or position resolution.

Re alarm value = 3:
Reducing the position resolution and conversion factor:
- reduce the length unit (LU) per load revolution for rotary encoders (p2506).
- increase the fine resolution of absolute position actual values (p0419).

Re alarm value = 3:
Re alarm value = 3:

requested function.

requested function.C213

requested function.C214
- reduce the continuous load.

- adapt the load duty cycle.
- check the assignment of the rated currents of the motor and Motor Module.
- connect the module with temperature sensor.

- set the available temperature sensor (p0600, p0601).
See also: p0600 (Motor temperature sensor for monitoring), p0601 (Motor
temperature sensor type)
The alarm automatically disappears if simulation mode is de-activated with
p1272 = 0.
Eliminate the causes of this alarm.
- increase p2163 and/or p2166.

- increase the torque/current/power limits.
- enable the speed controller.
- for closed-loop torque control: The speed setpoint should track the speed
actual value.
- correct the encoder pulse number in p0408 or mount the correct tachometer.
- check that the contactor feedback signal is correctly connected (p1235).

- check the logic of the contactor feedback signal (r1239.1 = 1: "Closed", r1239.1
= 0: "Open").
- increase the monitoring time (p1236).
- if required, set the external armature short-circuit without contactor feedback
signal (p1231=2).
For synchronous motors, the armature short-circuit braking is activated if a 1

signal is present via binector input
p1230.
See also: p1230 (Armature short-circuit / DC brake activation), p1231 (Armature
short-circuit / DC brake configuration)
- check the motor load.
- check the motor ambient temperature.
- check KTY84.
Select another open-loop/closed-loop control mode

See also: p1300 (Open-loop/closed-loop control operating mode)
Adapt the load.
Adapt the load.
Adapt the load.

Set the parameters for the load monitoring according to the applicable rules.
1) An alarm with alarm response DC brake is active.

The motor is braked with the DC braking current p1232 for the duration in
p1233. If the standstill threshold p1226 is
undershot, then braking is prematurely canceled.
2) The DC braking function was activated at Bico input p1230 for a set DC brake
p1230=4.
Braking current p1232 should be impressed until the Bico activation is canceled
again.
- check the functionality of the motor holding brake.
- check the feedback signal (p1223).C231
- check the functionality of the motor holding brake.

- check the feedback signal (p1222).
Fulfill the conditions for the target frequency for line-drive synchronization.
See also: r1084 (Speed limit positive effective), r1087 (Speed limit negative
effective)
The alarm automatically disappears after the difference that can be tolerated
between the setpoint and target frequencies
(p3806) is reached.
See also: p3806 (Sync-line-drive frequency difference threshold value)
Fulfill the conditions for the line-drive synchronization.

Set the control mode (p1300) to encoderless closed-loop speed control (p1300 =
20) or V/f characteristic (p1300 =
0 ... 19).
Exit the motor data identification routine (p1910).
Exist the speed controller optimization routine (p1960).
Exit the encoder adjustment (p1990).
Connect-up a Voltage Sensing Module (VSM) and when connecting to an
adjacent drive object ensure that the drive
objects have the same basis clock cycle.
Exit the friction characteristic record (p3845).
Fulfill the conditions for the friction characteristic.

Check the upper effective torque limit (e.g. in the field weakening range).
Check the lower effective torque limit (e.g. in the field weakening range).
Re alarm value = 3820 ... 3839:
Fulfill the conditions to set the parameters of the friction characteristic.
If the motor data (e.g. the maximum speed p0322) are changed during
commissioning (p0010 = 1, 3), then the technological
limits and threshold values, dependent on this, must be re-calculated by
selecting p0340= 5).
None necessary.
The alarm disappears automatically after the friction characteristic record has
been successfully completed or the
record is de-activated (p3845 = 0).
None necessary.
The alarm automatically disappears after determination or for the setting p1990
= 0.
None necessary.
The alarm disappears automatically after the speed controller optimization has
been successfully completed or for
the setting p1900 = 0.
Drive: Enable signals for the rotating measurement missing
- acknowledge faults that are present.

- establish missing enable signals.
See also: r0002, r0046
Connect encoder or select p1960 = 1, 3.
None necessary.
The alarm automatically disappears after the motor data identification routine
has been successfully completed or
for the setting p1900 = 0.
Check the parameterizing telegram (Ti, To, Tdp, etc.).

Check the receive configuration data.
Re alarm value = 1:
objects in the list are excluded from the process data exchange.
Check communication line.
Establish the cyclic connection and activate the control with cyclic operation.
For PROFINET, check the parameters "Name of Station" and "IP of Station"
(r61000, r61001).
Correct the parameterization (p8839).
Reduce the cycle times of the receive messages.
- check the bus cable

- set a higher baud rate (p8622).
- check the bit timing and if required optimize (p8623).
See also: p8622 (CBC baud rate), p8623 (CBC bit timing selection)
Check the bus cable.
Set a higher baud rate (p8622).
Check the bit timing and if required optimize (p8623).
Re alarm value = 2:
- reduce the cycle times of the SDO receive messages.
Change to the "pre-operational" or "stopped" mode.
Use a CANopen object intended for the PDO mapping or enter 0.

The following objects can be mapped in the Receive Process Data Object (RPDO)
or Transmit Process Data Object
(TPDO):
- RPDO: 6040 hex, 6060 hex, 60FF hex, 6071 hex; 5800 hex - 580F hex; 5820 hex
- 5827 hex
- TPDO: 6041 hex, 6061 hex, 6063 hex, 6069 hex, 606B hex, 606C hex, 6074 hex;
5810 hex - 581F hex; 5830 hex
- 5837 hex
Only sub-index 0 of the specified objects can be mapped.
Note:
As long as A08755 is present, the COB-ID cannot be set to valid.
Map fewer objects or objects with a smaller data type.

See also: p8710, p8711, p8712, p8713, p8714, p8715, p8716, p8717, p8730,
p8731, p8732, p8733, p8734, p8735,
p8736, p8737
Set the COB-ID to invalid.
The number of channels set in p8740 must be greater than or equal to the
number of PDOs.
There are 2 possibilities:
Increase the number of channels in p8740 and confirm the selection using
p8741.
Reduce the number of PDOs by setting the COB-ID to invalid.
See also: p8740 (CBC channel assignment), p8741 (CBC PDO configuration
acknowledgement)
Select another PDO COB-ID.

Re alarm value = 0:
Additional licenses are required and these must be activated (p9920, p9921).
Re alarm value = 1:
With the system powered down, re-insert the memory card that matches the
system.
Re alarm value = 2:
Enter and activate the license key (p9920, p9921).
Re alarm value = 3:
Compare the license key (p9920) entered with the license key on the certificate
of license.
Re-enter the license key and activate (p9920, p9921).
Re alarm value = 4:
Compare the license key (p9920) entered with the license key on the certificate
of license.
Re-enter the license key and activate (p9920, p9921).
check the electrical cabinet design and cable routing for EMC compliance

Under certain circumstances, the AC line supply is not switched in.

- check whether the fan is running.
- check the fan elements
- check whether the ambient temperature is in the permissible range.
- reduce the pulse frequency if this is higher than the rated pulse frequency.
- check the motor data.

- check the motor circuit configuration (star-delta).
- check the power cable connections.
- check the power cables for short-circuit or ground fault.
- check the length of the power cables.D268
- check the length of the power cables.

Check the 24 V DC voltage supply to power unit.
Replace the fan in the power unit and reset the operating hours counter to 0
(p0251 = 0).
See also: p0251 (Operating hours counter power unit fan), p0252 (Maximum
operating time power unit fan)
Check the 24 V DC power supply for the power unit and if required replace the
module.

Wait until synchronization is re-established.

- replace sensor.
- replace the firmware on the power unit by an older firmware version (r0128).
- upgrade the firmware on the Control Unit (r0018).
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
. check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the distance between zero marks (p0424, p0425).
- replace the encoder or encoder cable.
- adapt the parameter for the distance between zero marks (p0425).
- replace the encoder.
Replace encoder.

- check the Sensor Module (e.g. contacts).
- check the Hall sensor box
- check the tachometer feeder cable for interruptions.
- check the grounding of the tachometer shielding.
- if required, increase the setting of p0492.
- check mechanical mounting tolerances for encoders without their own

bearings (e.g. toothed-wheel encoders).
- check the plug connections (also the transition resistance).
- check the encoder signals.
Re alarm value = 3:
- for a standard encoder with cable, if required, contact the manufacturer.
- correct the assignment of the tracks to the position value that is serially
transferred. To do this, the two tracks must
be connected, inverted, at the Sensor Module (interchange A with A* and B with
B*) or, for a programmable encoder,
check the zero offset of the position.
- track C or D not connected.

- correct the direction of rotation of the Hall sensor possibly connected as
equivalent for track C/D.
- remove any dirt from the coding disk or strong magnetic fields.
- check encoder limit frequency.
- check that the encoder cables and shielding are routed in compliance with
EMC.
- check the plug connections and contacts.
- are the C/D tracks connected correctly (have the signal lines CP and CN or DP
and DN been interchanged)?
- replace the encoder cable.
Re causes 1, 2:
Carry out an automatic adjustment using the pole position identification routine.
First, accept the serial number with
p0440 = 1. Acknowledge the fault. Initiate the pole position identification routine
with p1990 = 1. Then check that the
pole position identification routine is correctly executed.
SERVO:
If a pole position identification technique is selected in p1980, and if p0301 does
not contain a motor type with an
encoder adjusted in the factory, then p1990 is automatically activated.
or
Set the adjustment via p0431. In this case, the new serial number is
automatically accepted.
or
Mechanically adjust the encoder. Accept the new serial number with p0440 = 1.
Re causes 3, 4:
Accept the new serial number with p0440 = 1.
- replace the Sensor Module.

- if required, upgrade the firmware in the Sensor Module.
No re-parameterization between fault/alarm.
- check that the encoder cable is the correct type and is correctly connected.
- check the temperature sensor selection in p0600 to p0603.
- replace the Sensor Module (hardware defect or incorrect calibration data).
- replace the firmware on the Sensor Module by an older firmware version

(r0148).
Replace encoder.


- if required, increase the setting of p0492.C300

Re alarm value = 3:
- check the adjustment of the Hall sensor.
EMC.

(r0148).
- replace the encoder or encoder cable.D313
Replace encoder.

- if required, increase the setting of p0492.

Re alarm value = 3:

EMC.

replace the sensor Module.
- if required, upgrade the firmware in the sensor Module.

(r0148).
- check the fan.

- reduce the power.
Error, timeout in the sequence control on the Voltage Sensing Module (VSM).
Replace the Terminal Module.

- check whether the firmware version of the VSM (r0158) matches the firmware
version of Control Unit (r0018).
- if required, replace the Voltage Sensing Module.
Note:
The firmware versions that match each other are in the readme.txt file on the
memory card.

-replace sensor.
- replace the firmware on the Voltage Sensing Module by an older firmware

version (r0148).
The alarm disappears automatically after successfully ending or canceling (when
a fault condition occurs) the test
stop.
Initiate test stop (BI: p10007).
For all drive objects specified in p10010, check whether the drive-based motion
monitoring functions with TM54F are
enabled (p9601).
When replacing a Motor Module, carry out the following steps:

- start the copy function for the node identifier on the TM54F (p9700 = 1D hex).
- acknowledge the hardware CRC on the TM54F (p9701 = EC hex).
- save all parameters (p0977 = 1).
The following always applies:
- for all drive objects specified in p10010, check whether the drive-based motion
monitoring functions with TM54F
are enabled (p9601).
- check whether fault F35150 is present and if required, remove the cause of the
fault.
See also: r10055 (SI TM54F communication status drive-specific)
- allow the TM54F to cool down.

- carry out safe acknowledgement (p10006).
For internal communication errors:
- check the electrical cabinet design and cable routing for EMC compliance
- upgrade the software on the TM54F.
- replace the TM54F.
If TM54F exists and no safety function has yet been parameterized:
- None necessary. The alarm disappears automatically after a safety function has
been parameterized.
- Check the safety-relevant parameters and if required, correct.

- set the reference checksum to the actual checksum.
- acknowledge that hardware was replaced
- carry out an acceptance test.
Set F-DI (see p10006) to logical "0" signal.
Power down the unit and power up again.

If the fault is still present, replace the module/board.
Allow the temperature sensor to cool down.
Enter the encoder pulse number in the permissible range (p0408).
Enter the zero mark offset in the permissible range (p4426).

- replace the component involved.
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)

- check whether the permissible ambient temperature for the Terminal Module
is being maintained.
- replace the Terminal Module.E353
- check whether the permissible ambient temperature for the component is
maintained.
- replace the Terminal Module.

maintained.
- replace the Terminal Module 31 (TM31).

- check whether the firmware version of the Terminal Module (r0158) matches
the firmware version of Control Unit
(r0018).
- if required, replace the Terminal Module.
Note:
The firmware versions that match each other are in the readme.txt file on the
memory card.
Check the terminals for the power supply voltage (L1+, L2+, L3+, M).
NONE
- reduce the ambient temperature.

- check the physical bus configuration (terminating resistor, shielding, etc.).
- check the interconnection of the master sign-of-life (r4201 via p0915).
- check whether the master correctly sends the sign-of-life (e.g. set up a trace
with r4201.12 ... r4201.15 and trigger
signal r4301.9).
- check the bus and master for utilization level (e.g. bus cycle time Tdp was set
too short).

- replace sensor.
- replace the firmware on the Terminal Module by an older firmware version

(r0158).
- check the supply voltage of the component involved.



maintained.
- Replace DRIVE-CLiQ Hub Module.

maintained.
- Replace DRIVE-CLiQ Hub Module.
- Replace the firmware on the DRIVE-CLiQ Hub Module with older firmware
(r0158).
Evaluate the alarm buffer of the specified object.
- check the wiring between the cooling system and the input terminal (Terminal
Module).
- check the external control device for the cooling system.
Check the device to de-ionize the cooling liquid.
- check the wiring between the cooling system and the Power Stack Adapter
(PSA).
- check the function of the sensor to measure the conductivity.
Check the cooling system and the ambient conditions.
Check the excitation equipment.

CBE20: Upgrade the PROFINET version of the project (HW Config) and/or the
CBE20 firmware to make them compatible.
See also: p8835 (CBE20 firmware selection)
The following should be carried out after the changeover:

- exit the safety commissioning mode (p0010).
- save all parameters (p0977 = 1 or "copy RAM to ROM").
Once the Control Unit has been switched on, safety message F01680 or F3
- remove the fault cause in the control and carry out a POWER ON.
- check the value in p9557, if necessary, increase the value, and carry out
POWER ON.
- check the shutdown path of the Control Unit (check DRIVE-CLiQ
communication).
- carry out a diagnosti
- carry out a diagnostics routine for message C01714.
This message can only be acknowledged as follows in the acceptance test mode
with
Check the braking behavior, if required, adapt the tolerance for "Safe
Acceleration Monitor".
This message can only be acknowledged as follows in the acceptance test mode
without POWER ON:
- motion monitoring functions integrated in the drive: Via Termina
- check whether safety faults are present and if required carry out the
appropriate diagnostic routines for the particular
faults.
- check whether the standstill tolerance matches the accuracy and control
dynamic performance of the axis.
- carry out a POW
- remove the cause of the fault at the control.

This message can be acknowledged as follows:
- motion monitoring functions integrated in the drive: Via Terminal Module 54F
(TM54F) or PROFIsafe
- motion

- motion

- motion
1: Status image of monitoring functions SOS, SLS or SLP (result list 1) (r9710[0],
r9710[1]).
2: Status image of monitoring function SCA or n < nx (result list 2) (r9711[0],
r9711[1]).
3: Pos. act. val. (r9712).
4: Error when synchronizing the crosswise d
- check the traversing/motion program in the control.
- check the limits for "Safely-Limited Speed (SLS) and if required, adapt (p9531).
- motion monitoring functions integrated in the drive: Via Terminal Modul

- repeat the acceptance test for the safe brake test if the brake test is used.
See also: p2003 (Reference torque)
- check the encoder connection.

- motion monitoring functions with SINUMERIK: Via the m

- motion monitoring functions with SINUMERIK: Via the m
None necessary.
The message is withdrawn when the test stop is finished.
Note:
None necessary.
The message is withdrawn when exiting the acceptance test mode.
Note:
Correct the parameter value.

- remove the cause to the fault on the Control Unit.
- check the value in p9357, if required, increase the value.
- check the shutdown path of the Control Unit (check DRIVE-CLiQ
communication).
- replace Motor Module.
- replace Control Unit.
This message can only be acknowledged in the acceptance test mode without
POWER ON via the Terminal Module
54F (TM54F) or PROFIsafe.
Note:
Note:
Check the braking behavior, if required, adapt the tolerance for "Safe
Acceleration Monitor".
Note:
SBR: Safe Acceleration Monitor
See also: p9548 (SI Motion SBR actual velocity tolerance (Control Unit))
- check whether safety faults are present and if required carry out the
appropriate diagnostic routines for the particular
faults.
- check whether the standstill tolerance matches the accuracy and control
dynamic performance of the axis.
Note:
SOS: Safe Operating Stop / SBH: Safe operating stop
See also: p9530 (SI Motion standstill tolerance (Control Unit))
This message can only be acknowledged via the Terminal Module 54F (TM54F)
or PROFIsafe.
Note:

or PROFIsafe.
Note:
Re message value = 1030:

- if required, replace the encoder.
Re message value = 1031:
When replacing a Sensor Module, carry out the following steps:
- start the copy function for the node identifier on the drive (p9700 = 1D hex).
- acknowledge the hardware CRC on the drive (p9701 = EC hex).
- if required, replace the encoder.
Re other message values:
- The significance of the individual message values is described in safety message
C01711 of the Control Unit.
Note:
or PROFIsafe.
See also: p9300 (SI Motion monitoring clock cycle (Motor Module)), p9500 (SI
Motion monitoring clock cycle (Control
Unit))
- check the traversing/motion program in the control.
- check the limits for "Safely-Limited Speed" (SLS) and if required, adapt (p9331).
or PROFIsafe.
Note:
SLS: Safely-Limited Speed / SG: Safely reduced speed
See also: p9331 (SI Motion SLS limit values (Motor Module)), p9363 (SI Motion
SLS stop response (Motor Module))
None necessary.
The message is withdrawn when the test stop is finished.
Note:
None necessary.
The message is withdrawn when exiting the acceptance test mode.
Note:
- Carry out a POWER ON (power off/on) for all components

- upgrade the firmware release, if possible
- Carry out a POWER ON (power off / on) for all components
- Check the selected component number (P7828)

- Check the DRIVE-CLiQ connection
- Save suitable firmware file for download in the directory
/siemens/sinamics/code/sac/
- After POWER ON has been carried-out again for the DRIVE-CLiQ component,
download the
Check the EEPROM data of the drive objects.

Set the monitoring time higher at the PC/AOP or disable completely.
Notice:
The monitoring time should be set as short as possible. A long monitoring time
means a late response when the communications fail.
The monitoring time is set in milliseconds.
- in
If you have saved your project data using STARTER, carry out a new download
for your project. Save using the function 'Copy RAM to ROM" or with P0977 = 1
so that all the parameter files are again completely written into the
CompactFlash card.
If you have
Check whether one of the files to be overwritten has the attibute "read only"
and change this file attribute into "writable". Check all the files (Psxxxyyy.*,
Ccxxxyyy.*, Caxxxyyy.*) that belong to drive yyy designated in the fault value.
Replace the Comp
- Check the file attribute of the files (Psxxxyyy.*, Caxxxyyy.*, Ccxxxyyy.*) and, if
required, change from "read only" to "writeable"
- Replace the CompactFlash card.
- Save the parameters (P0971 / P0977)

- Carry out a POWER ON (power off / on) for all components.
- Save the parameters (P0977)
- Download the project again into te drive unit.
- Enter the correct value into the specified parameter

- Identify the parameter that narrows (restricts) the limits of the specified
parameter.
- Use the actual version of the commissioning software.

- Modify the offline project and carry out a new download (eg. Compare the
number of the drive objects, motor, encoder, power module in the offline
project and at the drive )
- Change the drive syste
Replace the CompactFlash card
- Insert the matching CompactFlash card

- Use the matching Control Unit or power module
- For this drive object type (p0107), select a valid application-specific perspective
(p0103).
- Save the required descriptive file (Pdxxxyyy.ACX) on the CompactFlash card.
- Change the configuration on this Control Unit

- Use an additional Control Unit
- Try to save again
- Use another CompactFlash card
Only one SINAMICS G drive type is permitted.
Only power modules of one particular drive type may be operated with one CU

- Upgrade the firmware release
- Contact the Hotline
- Replace the Control Unit.
Reduce the frequency of the pulses at the measuring probe input
- Power down the unit

- Suitably restrict the number of instances of a drive object type by reducing the
number of inserted components.
- Re-commission the unit
- Reduce the number of drives

- Increase the sampling times
Only those drive objects may be connected to the same DRIVE-CLiQ socket of
the Control Unit that should run with the same basic clock cycle. For example,
Active Line Modules and Motor Modules shouldbe inserted at differen DRIVE-
CLiQ ports as their basic c
- Increase the basic clock cycle

- Reduce the number of connected drives and start to re-commission the unit
See also p0110
Increase the basic clock cycle of DRIVE-CLiQ communications.
See also P0112


Upgrade the firmware of the DRIVE-CLiQ component involved.
Enter the missing component number or remove the component and restart
commissioning.
See also, P0121, P0131, P0141, P0142, P0151, P0161, P0186, P0187, P0188,
P0189
Check the DRIVE-CLiQ connection:

Reduce the number of components on the DRIVE-CLiQ line involved and
distribute these to other DRIVE-CLiQ connections
of the Control Unit. This means that communication is uniformly distributed over
several communication
li
Remove the illegal components and restart the system.
One of the following counter-measures can be selected if no faults have

occurred in the topology detection itself:
If commissioning was still not completed:
- carry out a self-commissioning routine (starting from p0009 = 1).
General: Set p0099 to r0098, s
Re fault cause = 1:
Change the configuration. Connect less than 199 components to the Control
Unit.
Re fault cause = 2:
Remove the component with unknown component type.
Re fault cause = 3, 4, 5:
Establish a valid combination.
Re fault cause = 6, 7:
Conne
Output the fault value and remove the specified connection.

Note:
Output the fault value and remove the defected component.
Reload the target topology using the commissioning software.
Read out the fault value and remove one of the specified connections.
Then download the target topology again using the commissioning software.
Note:
improved diagnostics capability (e.g
Read out the fault value and remove one of the two specified connections.
Then download the target topology again using the commissioning software.
Note:
improved diagnostics capability
Establish another interconnection.

Again set the required standard telegram (p0922).
- set all open BICO interconnections centrally to the factory setting with p9495 =
2.
- make the non-operational drive object active/operational again (re-insert or
activate components).
Interconnect this connector input with a connector output having a float data
type.
Example:
The BICO output has, as normalized unit, voltage and the BICO input has current.
This means that the factor p2002 (contains the reference value for current) /
p2001 (contains the reference value for
voltage) is calculated between the BICO output
Apply normalization or check the transfer value.
None necessary.
None necessary.
- select Safe Torque Off and de-select again.

- replace the Motor Module involved.
Re fault value = 9999:
- carry out diagnostics for fault F01611.
Note:
CU: Control Unit
MM: Motor Module
Re fault value = 1 to 5 and 7 to 999:
- check the cross-checked data that resulted in a STOP F.
- upgrade the Motor Module software.
- upgrade the Control Unit software.
Re fault value = 6:
- carry
- check the tolerance time SGE changeover and if required, increase the value
(p9650).
- check the wiring of the safety-relevant inputs (SGE) (contact problems).
Note:
CU: Control Unit
SGE: Safety-relevant input
STO: Safe Torque Off

- check whether there is a DRIVE-CLiQ communication error between the Control
Unit and the Motor Module
involved and, if required, carry out a diagnost
- check parameter p1278 (for SBC, only p1278 = 0 is permissible).

- check the motor holding brake connection.
- check the function of the motor holding brake.
- check whether there is a DRIVE-CLiQ communicatio

- re-commission the "Safety Integrated" function and carry out a POWER ON.
- replace the Control Unit.
Note:
CU: Control Unit
MM: Motor M

- carry out safety commissioning routine.
- again carry out safety commissioning routine.
- replace the CompactFlash card.
- check the safety parameters in the Control Unit and adapt the

- check the setting of p9510 (SI Motion clock-cycle synchronous PROFIBUS
master) and if required, correct.
General:
- upgrade the Control
For enabled drive-based SI monitoring (p9601/p9801 > 0):
For enabled motion monitoring function (p9501 > 0):
- correct the monitoring clock cycle (p9500) and carry out POWER ON.
Re fault value 101:
- the actual value s

- remove the PROFIsafe configuring in the higher-level F control or enable
PROFIsafe in the drive.
The following generally applies:
- check the PROFIBUS configuration of the safety slot on the master side and, if
necessary, correct.

Note:
CU: Control Unit
MM: Motor Module
SI: Safe
- re-commission the safety functions.

Note:
CU: Con
Re fault value = 1:
- set the Safety Integrated password (p9761).
Re fault value = 2:
- inhibit Safety Integrated and again reset the drive parameters.
Re fault value = 3:
- end the simulation mode for the digital input (p0795).
Re fault value = 10, 11, 1
- use a Motor Module that supports the safety-related functions.

Note:
CU: Control Unit
MM: Motor Module
- set p9700 = 0.
- check p9501and p9601 and correct if necessary.
- start the copy function again by entering the appropriate value in p9700.
For enabled drive-based SI monitoring:
1. Set parameter p7826 to the value 1
2. Save the parameter (p0977 = 1) and carry out a power-on reset
When de-activating the drive-based SI monitoring (p9601 = 0), the alarm can be
acknowledged after exiting the
saf
Re fault value = 1, 2:
- use and parameterize an encoder that Safety Integrated supports (encoder
with track A/B sine-wave, p0404.4 = 1).
Re fault value = 3:
- check whether the drive or drive commissioning function is active and if
required, exit this (p
Align the encoder parameterization between the safety encoder and the
standard encoder.
Note:
- check whether there are faults in the safety function alignment between the
Control Unit and the Motor Module
involved
(F01655, F30655) and if required, carry out the appropriate diagnostics routine
for the particular faults.
Re fault value = 1:
- use a
- upgrade the Sensor Module software.

- use a Sensor Module that supports the safe motion monitoring function.
Note:

Note:
De-select the monitoring function involved (p9501, p9503, p9601, p9801).

Note:
SCA: Safe Cam / SN: Safe software cam
SLP: Safely-Limited Position / SE: Safe software limit switches
Enable the function "SOS/SLS" (p9501.0) and carry out a POWER ON.
Note:
See also: p9501 (SI Motion enable safety functions (Cont
Correct the limit values in p9534 and p9535 and carry out a POWER ON.
Note:
Correct the limit values for SLS and carry out a POWER ON.
Note:
See also: p9531 (SI Motion SLS (SG) limit values (Control Unit))
Correct the cam position and carry out a POWER ON.

Note:
See also: p9536 (SI Motion SCA (SN) plus cam position (Control Unit)), p9537 (SI
Motion SCA (SN) plus cam position
(Control Unit))
Correct the modulo value for SCA and carry out a POWER ON.
Note:
See also: p9505 (SI Motion SCA (SN) modulo value (Control Unit))
Either de-select the function "actual value synchronization" or the monitoring

functions with absolute reference
(SCA/SLP) and carry out a POWER ON.
Note:
SLP: Safely-Limited Position / SE: Safe
Re fault value = 0:
- use a Control Unit NVRAM.
Re fault value = 1:
- deselect functions that are not required and that take up memory space in the
NVRAM.
Re fault value = 100 ... 107:
- ensure that the DRIVE-CLiQ components have the same firmware releases.
- avoid longer topologies for short current controller clock cycles.
- check the DRIVE-CLiQ cables at the Control Unit.
- remove an
- save (p0971 = 1).

Re 1.
- restore the factory setting.
- carry out the first commissioning.
Re 2.
- download the SMI data from the back-up (p4690, p4691).
Restore the bus connection and set the PROFIBUS master to RUN.
See also: p2047 (PROFIBUS additional monitoring time)
- check whether communication was briefly or permanently interrupted.

- check the bus and master for utilization level (e.g. bus cycle time Tdp was set
too short).
Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
- check the physical bus configuration (terminating resistor, shielding, etc.).

- correct the interconnection of the master sign-of-life (p2045).
- check whether the master correctly sends the sign-of-life (e.g. create a trace
with STW2.12 ... STW2.15 and
- wait until the control has re-booted.

- restore data transfer to the control.
- acknowledge faults that are present.

- check the PROFIBUS cables.

- check the state of the Publisher that has the aborted connection.
See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses)
Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET

- upgrade the software of the DRIVE-CLiQ components.
Upgrade the firmware of the component specified in the fault value.

Note:
If required, also upgrade additional components in the DRIVE-CLiQ line.
1. Ensure perfect functioning of the DRIVE-CLiQ.

2. Initiate a new synchronization, e.g. as follows:
- remove the PROFIBUS master and re-insert again.
- restart the PROFIBUS master.
- power down the Control Unit and power it up again.
- press the Control Unit reset button.
- reset the parameter and download the saved parameters (p0009 = 30, p0976 =
2).

- replace the Control Unit.
Note:
See also: r4950, r4955, p4956, r4957
- change the configuration on this Control Unit (e.g. fewer drives, function
modules, data sets, OA applications,
blocks, etc).
- use an additional Control Unit.
Note:
- Power down the power supply for the Control Unit and power up again.
- If required, replace the Terminal Module.
The Terminal Module should be directly connected to a DRIVE-CLiQ socket of the
Control Unit.
If fault occu
Check the connection to the signal source for interruptions
Check the magnitude of the impressed current - it is possible that the impressed
signl is too low
Please note that the input has a great resistor of 250Ohms
The input current measured by the TM
- Check he 24V power supply

The power module is defective and must be replaced
- Acknowledge power module faults that are still present

- Inhibit the pulses of the power module involved (P7001)
For parallel circuit configurations, only power units with identical power unit
data may be used.
For parallel circuit configurations, only power units with identical EEPROM
versions may be used.
For parallel circuit configurations, only power units with identical firmware
versions may be used.
For parallel circuit configurations, only Voltage Sensing Modules (VSM) with
identical EEPROM versions may be
used.
For parallel circuit configurations, only Voltage Sensing Modules (VSM) with
identical firmware versions may be
used.
Update the firmware of the power units (at least V02.30.01.00).
Adapts the number of active Voltage Sensing Modules (VSM).
- check the parameterized supply voltage and if required change (p0210).

- check the line supply voltage.
- reduce the motor load.
- check the ambient temperature.
- check the wiring and sensor connector.
overtemperature fault threshold), p0606
(Motor overtemperature timer)

- induction motors: De-activate temperature sensor fault (p0607 = 0).
See also: r0035, p0600, p0601, p0607, p4600, p4601, p4602, p4603, r4620
Modify the parameter indicated in the fault value (r0949) (e.g. p0640 = current
limit > 0).
p0404, p0408, p0640, p1082
- check the parameter involved.
- check the macro file and BICO interconnection.
See also: p0015, p0700 (Macro Binector Input (BI)), p1000 (Macro Connector
Inputs (CI) for speed setpoints), p1500
(Macro Connector Inputs (CI) for torque setpoints)
- check whether the file is saved in the appropriate directory on the memory
card.
Example:
If p0015 is set to 1501, then the selected ACX file must be located in the
following directory:
... /PMACROS/DEVICE/P15/PM001501.ACX
Check and correct the conditions for the WaitUntil loop.
It is not necessary to change the parameters as they have already been correctly
limited.
Check the adapted parameter value and if required correct.
See also: r9450 (Reference value change parameter with unsuccessful
calculation)
- continue to work with the set sampling times.

- before resetting the drive parameters, set the basic clock cycle p0110[0] to the
original value.
See also: r0110 (Basic sampling times)
Enter the current controller sampling times so that they are identical to the basic
clock cycle, e.g. by selecting p0112.
Note which basic clock cycle is selected in p0111.
The sampling times in p0115 can only be changed manually in the sampling
times presetting "Expert" (p0112).
See also: r0110, r0111, p0112, p0115
Change the signal via binector input p3985.

- check the interconnection of the binector input for "master control by PLC"
(p0854).
- check the "master control by PLC" signal and, if required, switch in.
- check the data transfer via the fieldbus (master/drive).
Note:
If the drive should continue to operate after withdrawing "master control by
PLC" then fault response must be parameterized
to NONE or the message type should be parameterized as alarm.
- check the setting of p0860.

- check the feedback circuit from the line contactor.
- increase the monitoring time in p0861.
See also: p0860 (Line cont. fdbk sig), p0861 (Line contactor monitoring time)
- check the transfer of the feedback signals.
- check the switch
- check the transfer of the feedback signals.

- check the switch
- increase the number of restart attempts (p1211). The current number of

starting attempts is displayed in r1214.
- increase the delay time in p1212 and/or the monitoring time in p1213.
- issue an ON command (p0840).
- either increase or disable the monitoring time of the power unit (p0857).
Check the motor feeder cables.

- de-activate the "flying restart" function (p1200 = 0).
- change the open-loop/closed-loop control mode (p1300).
- connect a Voltage Sensing Module (VSM) (voltage measurement).

- check the infeed module
- adapt the device supply voltage (p0210) or the switch-on level (p1245, p1285).
- disable the DC link voltage monitoring (p1240, p1280 = 0).

- check the infeed module
- adapt the device supply voltage (p0210).
- disable the DC link voltage monitoring (p1240, p1280 = 0).
Check the speed threshold for the Vdc_min controller (kinetic buffering) (p1257,
p1297).
See also: p1257 (Vdc_min controller speed threshold)
Check the time threshold for Vdc-min controller (kinetic buffering) (p1255,
p1295).
See also: p1255 (Vdc_min controller time threshold)
- connect the motor or check the motor contactor.
- check the DC link voltage (r0070).
- check the Motor Module.
- activate the "flying restart" function (p1200).
- correct the motor data.

- check the motor configuration.
- correct the current limits (p0640).
- reduce the induction motor load.
- if required, use a larger Motor Module.
- check motor supply cable.
- check power unit.
- if the encoder mounting was changed - re-adjust the encoder.
- replace the defective motor encoder.
- correctly set the angular commutation offset (p0431).
- correctly set the motor stator resistance, cable resistance and motor-stator
leakage inductance (p0350, p0352,
p0356).
- increase the changeover speed for the motor model (p1752). The monitoring is
completely de-activated for p1752
> p1082 (maximum speed)
Note:
For High Dynamic Motors (1FK7xxx-7xxx), for applications with a higher current,
if necessary, the monitoring should
be disabled.
- correctly set the angular commutation offset (p0431).

- re-adjust the motor encoder after the encoder has been replaced.
- replace the defective motor encoder.
- check the pole position identification routine. If the pole position identification
routine is not suitable for this motor
type, then disable the plausibility check (p1982 = 0).
- reduce the natural frequency of PT2 element for reference model (p1433).
- reduce the speed controller sampling time (p0115[1]).
- change over the drive data set with the pulses inhibited.
- ensure that the changeover to a drive data set does not result in the motor
direction of rotation being changed (i.e.
for these drive data sets, the same value must be in p1821).
See also: p1821 (Dir of rot)
- de-activate the holding command for the ramp-function generator (p1141).
- do not bypass the ramp-function generator (p1122).
- suppress the fault (p2101, p2119). This is necessary if the ramp-function
generator is held using jogging and the
speed setpoint is simultaneously inhibited (r0898.6).
Note:
For sensorless vector control it is not practical to read-in the main setpoint of
the speed control via p1155 or p1160
(p0922). In this case, the main setpoint should be injected before the ramp-
function generator (p1070). The reason
for this is that the ramp-function generator output is automatically set when
transitioning from closed-loop speed controlled
into open-loop speed controlled operation.
Make the ration between the multiturn resolution and the modulo range an
integer number.
The ratio v is calculated as follows:
1. Motor encoder without position tracking:
v = (p0421 * p2506 * p0433 * p2505) / (p0432 * p2504 * p2576)
2. Motor encoder with position tracking for the measuring gear:
v = (p0412 * p2506 * p2505) / (p2504 * p2576)
3. Motor encoder with position tracking for the load gear:
v = (p2721 * p2506 * p0433) / (p0432 * p2576)
4. Motor encoder with position tracking for the load and measuring gear:
v = (p2721 * p2506) / p2576
5. Direct encoder without position tracking:
v = (p0421 * p2506 * p0433) / (p0432 * p2576)
6. Direct encoder with position tracking for the measuring gear:
v = (p0412 * p2506) / p2576
Note:
With position tracking, it is recommended that p0412 and p2721 are changed
See also: p0412 (Measuring gear, rotary absolute gearbox, revolutions, virtual),
p0432 (Gearbox factor, encoder revolutions),
p0433 (Gearbox factor, motor/load revolutions), p2721 (Load gear, rotary
absolute gearbox, revolutions,
virtual)
Set the reference point coordinate to a lower value than specified in the fault
value.
Reset the position tracking as follows:

- select encoder commissioning (p0010 = 4).
- reset position tracking, position (p2720.2 = 1).
- de-select encoder commissioning (p0010 = 0).
The fault should then be acknowledged and, if necessary, the absolute encoder
adjusted (p2507).
- reduce the fine resolution (p0419).
- reduce the multiturn resolution (p2721).
See also: p0419 (Fine resolution absolute value Gx_XIST2 (in bits)), p2721 (Load
gear, rotary absolute gearbox,
revolutions, virtual)
The fault should be resolved as follows:

The fault should then be acknowledged and the absolute encoder adjusted.

adjusted (p2507).
See also: p0010
Check the causes and resolve.

- check the "reference cam" binector input (BI: p2612).
- check the maximum permissible distance to the reference cam (p2606).
- if axis does not have any reference cam, then set p2607 to 0.
- check the encoder regarding the zero mark
- check the maximum permissible distance between the reference cam and zero
mark (p2609).
- use an external encoder zero mark (equivalent zero mark) (p0495).
See also: p0495 (Equivalent zero mark, input terminal)
- check the "reference cam" binector input (BI: p2612).

- repeat the search for reference.
Check the traversing block and where relevant, take into consideration alarms
that are present.
Correct the target position.

Correct the target position.
correct the target position.

change software limit switch minus (CI: p2578, p2580).
- check the monitoring window (p2635).
- check the mechanical system.
- check the traversing block and locate the target position further into the
workpiece.
- check the "fixed stop reached" control signal (p2637).
- if required, reduce the maximum following error window to detect the fixed
stop (p2634).
Check the control.
set the enable signals or check the cause of the fault that first occurred and then
result (for a standard assignment).
check the assignment to enable the basic positioning function.
- leave the STOP cam minus in the positive traversing direction and return the
axis to the valid traversing range.
- check the wiring of the STOP cam.
- leave the STOP cam plus in the negative traversing direction and return the axis
to the valid traversing range.
- check the wiring of the STOP cam.
If required, reduce the traversing range or position resolution (p2506).

Increase the fine resolution of absolute position actual value (p0419).
Reference to fault value = 3:
If the value for the maximum possible absolute position (LU) is greater than
4294967296, an adjustment cannot be
made due to an overflow.
For rotary encoders, the maximum possible absolute position (LU) is calculated
as follows:
p2506 * p0433 * p2505 / (p0432 * p2504)
p2506 * p0433 * p2505 * p0421 / (p0432 * p2504) for multiturn encoders
2. Motor encoder with position tracking for measuring gear
p2506 * p0412 * p2505 / p2504
3. Motor encoder with position tracking for load gear:
p2506 * p2721 * p0433 / p0432
4. Motor encoder with position tracking for load and measuring gear:
p2506 * p2721
p2506 * p0433 / p0432
p2506 * p0433 * p0421 / p0432 for multiturn encoders
6. Direct encoder with position tracking for measuring gear:
p2506 * p0412
The index of the encoder data set associated with the drive data set should be
entered into p0187 (1st encoder),
p0188 (2nd encoder) and p0189 (3rd encoder).
In the drive data sets, no longer assign MDS/EDS using p0186, p0187, p0188,
p0189 or set a valid component number.
See also: p0131, p0141, p0142, p0186, p0187, p0188, p0189
Assign the drive data set to different encoders.

See also: p0141 (Encoder interface (Sensor Module) component number), p0187
(Encoder 1 encoder data set number),
p0188 (Encoder 2 encoder data set number), p0189 (Encoder 3 encoder data set
number)
Correct the double use of a component number using the two parameters coded
in the fault value.
Every encoder data set must be assigned its own dedicated DRIVE-CLiQ socket.
The component numbers of the
encoder interfaces (p0141) must have different values within a drive object.
The following must apply:
p0141[0] not equal to p0141[1] not equal to ... not equal to p0141[n]
- assign the drive data set to a combination of motor and power unit permitted
by the target topology.
- adapt the target topology.
See also: p0121 (Power unit component number), p0131 (Motor component
number), p0186 (Motor Data Sets
(MDS) number)
Commission the drive data set specified in the fault value (r0949).
If you wish to operate a motor once with one motor encoder and then another
time with the other motor encoder,
then you must set up two different MDSs, in which the motor data are the same.
Example:
p0186[0] = 0, p0187[0] = 0
p0186[0] = 1, p0187[0] = 1
Correct the parameterization of the motor data sets.
Re fault cause = 1:
- check the encoder parameterization (p0404).
- use an encoder with track C/D, EnDat interface of Hall sensors.
- use an encoder with sine-wave A/B track for which the motor pole pair number
(r0313) is an integer multiple of the
encoder pulse number (p0408).
- activate the pole position identification routine (p1982 = 1).
Re fault cause = 2:
- the quotient of the pole pair number divided by the ratio of the measuring gear
must be an integer number: (p0314
* p0433) / p0432.
Note:
For operation with track C/D, this quotient must be less than 8.
See also: p0402 (Gearbox type selection), p0404 (Encoder configuration
effective), p0432 (Gearbox factor, encoder
revolutions), p0433 (Gearbox factor, motor/load revolutions)
- check the encoder parameterization (p0400, p0404).

- use the matching encoder evaluation (r0456).
- check the encoder parameterization (p0430, p0437).
- check the pole position identification routine (p1982).
- use the matching encoder evaluation (r0458, r0459).
See also: p0430 (Sensor Module configuration), p0437 (Sensor Module
configuration extended), r0458 (Sensor
Module properties), r0459 (Sensor Module properties extended), p1982 (Pole
position identification selection)
- use an absolute encoder.

- if necessary, de-select the position tracking (p0411 for the measuring gear,
p2720 for the load gear).
- use a Control Unit with sufficient NVRAM.
- Only activate position tracking of the load gear in the same encoder data set if
the gear ratio (p2504, p2505), axis
type (p2720.1) and tolerance window (p2722) are also the same.
- reduce the fine resolution (p0419).
- reduce the multiturn resolution (p0412).
See also: p0412 (Measuring gear, rotary absolute gearbox, revolutions, virtual),
p0419 (Fine resolution absolute
value Gx_XIST2 (in bits))
- check the parameterization (p0408, p0404.1, r0458.5).

- if required, upgrade the Sensor Module firmware.
check the parameterization (p0421, p0404.1, r0458.5).

if required, upgrade the Sensor Module firmware.
check the encoder parameterization (p0400, p0404).

use a Control Unit with sufficient NVRAM.
if required, deselect position tracking for the incremental encoder (p0411.3 = 0).
Evaluate other queued faults via encoder 1.

as follows:
p2506 * p0433 * p2505 / (p0432 * p2504)
p2506 * p0412 * p2505 / p2504
p2506 * p2721 * p0433 / p0432
p2506 * p2721
p2506 * p0433 / p0432
p2506 * p0412
as follows:
p2506 * p0433 * p2505 / (p0432 * p2504)
p2506 * p0412 * p2505 / p2504
p2506 * p2721 * p0433 / p0432
p2506 * p2721
p2506 * p0433 / p0432
p2506 * p0412
as follows:
p2506 * p0433 * p2505 / (p0432 * p2504)
p2506 * p0412 * p2505 / p2504
p2506 * p2721 * p0433 / p0432
p2506 * p2721
p2506 * p0433 / p0432
p2506 * p0412
- connect the data line to power unit and restart the Control Unit (POWER ON).
- check or replace the Control Unit.
- check the cable between the Control Unit and Motor Module.
- after correcting the topology, the parameters must be again downloaded using
the commissioning software.
- check the current limits (p0640).

- vector control: Check the current controller (p1715, p1717).
- V/f control: Check the current limiting controller (p1340 ... p1346).
- increase the up ramp (p1120) or reduce the load.
- check the motor and motor cables for short-circuit and ground fault.
- check the Motor Module and motor combination.

- ensure that there is a DC link voltage. Check the DC link busbar. Enable the
infeed.
- replace the associated infeed or drive of the signaling component.
- check the line supply voltage setting (p0210).
See also: p0857 (Power unit monitoring time)
Replace the power unit or inform Siemens Customer Service.

Connect the original power unit and power up the Control Unit again (POWER
ON) or set p0201 to r0200 and exit
commissioning with p0010 = 0.
For infeeds, the following applies:
Commutating reactors or line filters must be used that are specified for the new
power unit. A line supply and DC link
identification routine (p3410 = 5) must then be carried out. It is not possible to
change the power unit without re-commissioning
the system if the type of infeed (A_Infeed, B_Infeed, S_Infeed), the type of
construction/design (booksize,
chassis) or the voltage class differ between the old and new power units.
For inverters, the following applies:
If the new power unit is accepted, then if required, the current limit p0640 can
be reduced by a lower maximum current
of the power unit (r0209) (torque limits stay the same).
If not only the power unit is changed, but also the motor, then the motor must
be re-commissioning (e.g. using p0010
= 1). This is also necessary if motor data is still to be downloaded via DRIVE-CLiQ.
If the comparison stage in p9906 is set to 2, 3, then commissioning can be exited
(p0010 = 0) and the fault acknowledged.
See also: r0200 (Power unit current code number)
- switch out (disable) simulation mode (p1272 = 0) and acknowledge the fault.
- reduce the input voltage in order to reach a DC link voltage below 40 V.
- bring the infeed into an operational state.

- check the interconnection of the binector input for the signal "infeed
operation" (p0864).
- wait until the infeed has completed the line supply identification routine.
See also: p0857 (Power unit monitoring time), p0864 (Infeed operation)
- check the interconnection of the binector input for the signal "infeed
operation" (p0864).
- check the enable signals of the infeed and if required, enable.
- remove and acknowledge an infeed fault.
Note:
If this drive is intended to back-up the DC link regeneratively, then the fault
response must be parameterized for
NONE, OFF1 or OFF3 so that the drive can continue to operate even after the
infeed fails.
Eliminate the causes of this fault.
Eliminate the causes of this fault.
'Eliminate the causes of this fault.

Switch out the internal armature short-circuit (p1231=0) or de-activate Safe
Torque Off (p9501 = p9561 = 0).
Note:
- check that the motor can freely rotate.

- check the torque limit: For a positive direction of rotation r1538, for a negative
direction of rotation r1539.
- check the parameter, message "Motor locked" and if required, correct (p2175,
p2177).
- check the inversion of the actual value (p0410).
- check the motor encoder connection.
- check the encoder pulse number (p0408).
- for SERVO with encoderless operation and motors with low power ratings (<
300 W), increase the pulse frequency
(p1800).
- after de-selecting basic positioning, check the torque limits when motoring
(p1528) and when regenerating (p1529).
- in the simulation mode and operation with speed encoder, the power unit to
which the motor is connected must be
powered up and must be supplied with the torque setpoint of the simulated
closed-loop control. Otherwise, change
over to encoderless control (refer to p1300).
The following applies for a positive direction of rotation:

- check r1084 and if required, correct p1082, CI:p1085 and p2162.
The following applies for a negative direction of rotation:
- check r1087 and if required, correct p1082, CI:p1088 and p2162.
It should always be carefully ensured that the motor data identification (p1910)
as well as the rotating measurement
(p1960) were carried out (also refer to p3925). For synchronous motors with
encoder, the encoder must have been
adjusted (p1990).
For closed-loop speed and torque control with speed encoder, the following
applies:
- check the speed signal (interrupted cable, polarity, pulse number, broken
encoder shaft).
- check the speed encoder, if another speed encoder was selected using the data
set changeover. This must be connected
to the same motor that is controlled for the data set changeover.
If there is no fault, then the fault tolerance (p1744 and p0492) can be increased.
If the stalled motor should take place in the range of the monitor model and for
speeds of less than 30 % of the rated
motor speed, then a change can be made directly from the current model into
the flux impression (p1401.5 = 1). We
therefore recommend that the time-controlled model change is switched in
(p1750.4 = 1) or the model changeover
limits are significantly increased (p1752 > 0.35 * p0311; p1753 = 5 %).
For closed-loop speed and torque control without speed encoder, the following
applies:
- Check whether the drive stalls solely due to the load in controlled mode
(r1750.0) or when the speed setpoint is still
zero. If so, increase the current setpoint via p1610 or set p1750 bit 2 = 1
(sensorless vector control to standstill for
passive loads).
- If the motor excitation time (p0346) was reduced significantly and the drive
stalls when it is switched on and run
immediately, p0346 should be increased again or quick magnetization (p1401)
selected.
- Check the current limits (p0640, r0067, r0289). If the current limits are too low,
then the drive cannot be magnetized.
- check the current controller (p1715, p1717) and the speed adaptation
controller (p1764, p1767). If the dynamic
response was significantly reduced, then this should be increased again.
- check the speed encoder, if another speed encoder was selected using the data
- check that the contactor feedback signal is correctly connected (p1235).
- check the logic of the contactor feedback signal (r1239.1 = 1: "Closed", r1239.1
= 0: "Open").
- if required, set the external armature short-circuit without contactor feedback
signal (p1231=2).
Re cause 1:
- an armature short-circuit / voltage protection is only permissible for
permanent-magnetic synchronous motors. The
highest position of the motor type in p0300 must either be 2 or 4.
Re cause 101:
- the contactor for the external armature short-circuit configuration should be
controlled using output signal r1239.0.
The signal can, e.g. be connected to an output terminal BI: p0738. Before this
fault can be acknowledged, p1231
must be set again.
Re cause 102:
- if the external armature short-circuit with contactor feedback signal (p1231 =
1) is selected, this feedback signal
must be connected to an input terminal (e.g. r722.x) and then connected to BI:
p1235.
- alternatively, the external armature short-circuit without contactor feedback
signal (p1231 = 2) can be selected.
Re cause 103:
- if the external armature short-circuit without contactor feedback signal (p1231
= 2) is selected, then a delay time
must be parameterized in p1237. This time must always be greater than the
actual contactor opening time, as otherwise
the Motor Module would be short-circuited!
None necessary.
This a note for the user.
None necessary.
This a note for the user.
- check the parameterization (p1640, p3201, p3202).

- check the interfaces to the excitation equipment (r1626, p1640).
- check the excitation equipment.

- check the interfaces to the excitation equipment (r1626, p1640).
- check the excitation equipment.
- check the flux control (p1592, p1592, p1597).
- check the control for oscillation and take the appropriate counter measures
(e.g. optimize the speed control loop,
parameterize a bandstop filter).
Adapt the load.
Adapt the load.
Adapt the load.

If the Motor Module supports the autonomous internal voltage protection
(r0192.10 = 1), then the Motor Module automatically
decides - using the DC link voltage - as to whether the armature short-circuit
should be activated.
The armature short-circuit is activated and response OFF2 is initiated if the DC
link voltage exceeds 800 V. If the DC
link voltage falls below 450 V, then the armature short-circuit is withdrawn.
If the motor is still in a critical speed range, the armature short-circuit is re-
activated once the DC link voltage exceeds
the threshold of 800 V.
If the autonomous (independent) internal voltage protection is active (r1239.5 =
1) and the line supply returns (450
V < DC link voltage < 800 V), the armature short-circuit is withdrawn after 1
minute.
involved and, if required, carry out a diagnostics routine for the faults identified.
- check that the electrical cabinet design and cable routing are in compliance
with EMC regulations (e.g. shield of the
motor cable and brake conductors are connected with the shield connecting
plate and the motor connectors are
tightly screwed to the housing).
Operation with Safe Brake Module:
- check the Safe Brake Modules connection.
- replace the Safe Brake Module.
See also: p1215 (Motor holding brake configuration), p1278 (Brake control,
diagnostics evaluation)
None necessary.
If required increase the threshold value phase synchronism (p3813) for

synchronizing the line supply to the drive.
Before OFF1 or OFF3, complete synchronizing (r03819.0 = 0).
Before withdrawing the enable signal (p3802 = 0), reach synchronism (r3819.2 =
1).
See also: p3813 (Sync-line-drive phase synchronism threshold value)
Compare the motor data with the rating plate data and if required, correct.
p0320, p0322, p0323
Connect the original motor, power up the Control Unit again (POWER ON) and
exit the quick commissioning by setting
p0010 to 0.
Or set p0300 = 10000 (load the motor parameter with DRIVE-CLiQ) and re-
commission.
Quick commissioning (p0010 = 1) is automatically exited with p3900 > 0.
If quick commissioning was exited by setting p0010 to 0, then an automatic
controller calculation (p0340 = 1) is not
carried out.
Use a motor with DRIVE-CLiQ and the matching motor code.

The first three digits of the motor code generally correspond to the matching list
motor type.
Fulfill the conditions to record the friction characteristic.

Establish missing enable signals.
Select OFF1 (p0840) only after the friction characteristic record has been
completed.
Re fault value = 1082, 1084, 1087:
Select the highest speed value to be approached (p3829) less than or equal to
the maximum speed (p1082, r1084,
r1087).
Re-calculate the speed points along the friction characteristic (p0340 = 5).
Select the friction characteristic record, positive direction (p3845).
Select the friction characteristic record, negative direction (p3845).
Enable the permitted direction (p1110, p1111, r1198).
Set the control mode (p1300) on the closed-loop speed control (p1300 = 20, 21).
For encoderless closed-loop speed control (p1300 = 20) select the lowest speed
value to be approached (p3820)
greater than the changeover speed of open-loop controlled operation (p1755).
Re-calculate the speed points along the friction characteristic (p0340 = 5).
Exit the motor data identification routine (p1910).

Check whether the motor is correctly connected.
Replace the Motor Module involved.
De-activate traversing (p1909).
Check whether motor data have been correctly entered.
Repeat traversing.
Re fault value = 1:
Re fault value = 2:
Open the motor holding brake (p1215) and bring the motor into a no-load
condition.
Re fault value = 4:
Check whether the encoder pulse number (p0408) and gearbox factor (p0432,
p0433) are correct.
Check whether the motor pole pair number is correct (p0314).
When selecting p1980 = 4: Increase the value for p0325.
When selecting p1980 = 1: Increase the value for p0329.
Increase the value for p0329.
When selecting p1980 = 4: Reduce the value for p0325.
When selecting p1980 = 1: Reduce the value for p0329.
Re fault value = 1:
Re fault value = 2:
Open the motor holding brake (p1215) and bring the motor into a no-load
condition.
Re fault value = 4:
Check whether the speed actual value inversion is correct (p0410.0).
Check whether the encoder pulse number (p0408) and gearbox factor (p0432,
p0433) are correct.
Check whether the motor pole pair number is correct (p0314).
Reduce the value for p0325.
Reduce the value for p0329.
Re fault value = 1:
- check the motor parameters.
- carry out a motor data identification routine (p1910).
- if required, reduce the dynamic factor (p1967 < 25 %).
Re fault value = 2:
- adapt the speed setpoint (p1965) or adapt the minimum limit (p1080).
Re fault value = 3:
- adapt the speed setpoint (p1965) or suppression (skip) bandwidths (p1091 ...
p1094, p1101).
Re fault value = 4:
- adapt the speed setpoint (p1965) or maximum limit (p1082, p1083 and p1086).
Re fault value = 5:
- check the encoder connection. If required, replace the encoder.
Re fault value = 6:
- check the connection assignment of the encoder cable. Adapt the polarity
(p0410).
Re fault value = 7:
- adapt the pulse number (p0408).
Re fault value = 8:
- check the encoder connection and encoder cable. It is possible that there is a
problem associated with the ground
connection.
- reduce the dynamic response of the speed controller (p1460, p1462 and
p1470, p1472).
Re fault value = 9:
- check the connections of the Voltage Sensing Module (VSM).
Note:
The encoder test can be switched out (disabled) using p1959.0.
See also: p1959 (Rotating measurement configuration)
Re fault value = 1:
- the total drive moment of inertia is far higher than that of the motor (p0341,
p0342).
De-select rotating measurement (p1960), enter the moment of inertia p0342, re-
calculate the speed controller p0340
= 4 and repeat the measurement.
- increase the measuring speed (p1961) and repeat the measurement.
- check the motor parameters (rating plate data). After the change: Calculate
p0340 = 3.
- check the moment of inertia (p0341, p0342). After the change: Calculate p0340
= 3.
Re fault value = 5:
- the speed setpoint (p1961) is too high. Reduce the speed.
Re fault value = 1:
p0340 = 3.
= 3.
p1094, p1101).
Re fault value = 8:
- the total drive moment of inertia is far higher than that of the motor (refer to
p0341, p0342). De-select rotating measurement
(p1960), enter the moment of inertia p342, re-calculate the speed controller
p0340 = 4 and repeat the measurement.
Re fault value = 9:
- check the moment of inertia (p0341, p0342). After the change, re-calculate
(p0340 = 3 or 4)
= 3.
Note:
The moment of inertia identification routine can be disabled using p1959.2.
Re fault value = 1:
p0340 = 3.
= 3.
Re fault value = 2:
Re fault value = 3:
p1094, p1101).
Re fault value = 4:
Re fault value = 5:
- increase the torque limits (e.g. p1520, p1521).
Re fault value = 6:
- reduce the dynamic factor (p1967).
- disable the vibration test (p1959.4 = 0) and repeat the rotating measurement.
Re fault value = 1:
Enable the direction (p1110 or p1111).
Select at least one function for automatic optimization of the speed controller
(p1959).
Re fault value = 1:
- check the motor parameters.
Re fault value = 2:
Re fault value = 3:
p1094, p1101).
Re fault value = 4:
Re fault value = 5:
- flux setpoint p1570 = 100% and current setpoint p1610 = 0% kept during the Lq
measurement.
Re fault value = 6:
- reduce the regenerative load so that the drive does not reach field weakening
when accelerating.
- reduce p1965 so that the q leakage inductance is recorded at lower speeds.
Re fault value = 7:
- increase p1082 if this is technically permissible.
- reduce p1965 so that the q leakage inductance is recorded at lower speeds.
Re fault value = 8:
- reduce the load when motoring so that the drive is not braked.
- increase p1965 so that the measurement is possibly done at higher speeds.
Note:
The measurement of the q leakage inductance can be disabled using p1959.5. If
only p1959.5 is set, then only this
measurement is carried out if p1960 is set to 1, 2 and the drive is powered up.
Re fault value = 0:
- check whether the motor is correctly connected. Observe configuration
(star/delta).
- check whether motor data have been correctly entered in p0300, p0304 ...
p0311.
- is there an appropriate relationship between the motor power rating and that
of the Motor Module? The ratio of the
Motor Module to the rated motor current should not be less than 0.5 and not be
greater than 4.
- check configuration (star/delta).
Re fault value = 2:
- for parallel circuits, check the motor winding system in p7003. If, for power
units connected in parallel, a motor is
specified with a single-winding system (p7003 = 0), although a multi-winding
system is being used, then a large proportion
of the stator resistance is interpreted as feeder cable resistance and entered in
p0352.
- check whether inductances are correctly entered in p0233 and p0353.
- check whether motor was correctly connected (star/delta).
- reduce the current controller sampling rate.
- increase current limit (p0640) or torque limit (p1520, p1521).
- check current controller gain (p1715).
- reduce current controller sampling time (p0115).
- it may be impossible to completely identify the L characteristic, as required
current amplitude is too high.
- suppress meas. (p1909, p1959).
- replace Terminal Board 30.

- replace Control Unit.
- check the power supply.

- replace Terminal Board 30.
- check communications link.

- check the set monitoring time if the error persists.
See also: p8840 (COMM BOARD monitoring time)
Check the send configuration data.
- check the bus cable
- check the baud rate (p8622).
- check the bit timing (p8623).
- check the master.
None necessary.
Acknowledge the fault and continue operation.
- check the motor data - if required, carry out commissioning.
- V/f operation: Increase up ramp.
- V/f operation: Check the assignment of the rated currents of the motor and
Motor Module.
- infeed: Check the line supply quality.
- infeed: Reduce the load when motoring.
- infeed: Correct connection of the line commutating reactor.
- replace power unit.
For a parallel switching device (r0108.15 = 1) the following additionally applies:
- check the ground fault monitoring thresholds (p0287).
- check the setting of the closed-loop circulating current control (p7036, p7037).
- increase the ramp-down time.

- activate the DC link voltage controller.
- use a brake resistor or Active Line Module.
- increase the current limit of the infeed or use a larger module (for the Active
Line Module).
- check the device supply voltage.
- check and correct the phase assignment at the VSM and at the power unit.
See also: p0210 (Drive unit line supply voltage), p1240 (Vdc controller or Vdc
monitoring configuration)
- check the line supply voltage

- check the line supply infeed and if necessary observe the fault messages of the
line supply infeed.
Note:
The "ready for operation" signal of the infeed r0863 must be connected to the
associated inputs p0864 of the drives.
Notice:
This fault can only be acknowledged after this alarm threshold for alarm A05000
has been undershot.
See also: p1800 (Pulse frequency)
- reduce the continuous load.

- check the motor and power unit rated currents.
See also: r0036 (Power unit overload I2t), r0206 (Rated power unit power),
p0307 (Rated motor power)
The faults must be saved in the Thyristor Control Board and must be
acknowledged. To do this, the supply voltage
of the Thyristor Control Board must be switched out for at least 10 s!
- check the line supply voltage
- check or energize the line contactor.
- check the monitoring time and, if required, increase (p0857).
- if required, observe additional power unit messages/signals.
- check the DC link regarding short-circuit or ground fault.
- evaluate diagnostic LEDs for the Thyristor Control Board.
- for projects with the VECTOR drive object, check whether p0117 = 6 has been
set on the Control Unit.
See also: p0117 (Current controller computing dead time mode)
Check the fuses in the main circuit.
Contact the manufacturer.

Contact the manufacturer.
For infeed units, the following applies:

- check the controller settings, if required, reset and identify the controller
(p0340 = 2, p3410 = 5).
- reduce the load, if required, increase the DC link capacitance or use a higher-
rating infeed.
- check the connection of the optional Voltage Sensing Module.
- check the connection and technical data of the commutating reactor.
The following applies to Motor Modules:
Re fault value = 0:
If internal voltage protection is active (p1231 = 3), de-activate it if necessary.
See also: p1231 (Armature short-circuit / DC brake configuration)

- check the motor.
- check the CT.
The following applies additionally for CU310 and CUA31:
- check the cables and contacts of the brake connection (a wire is possibly
broken).
For parallel switching devices (r0108.15 = 1) the following additionally applies:
- check the ground fault monitoring thresholds (p0287).
- check the setting of the closed-loop circulating current control (p7036, p7037).
See also: p0287 (Ground fault monitoring thresholds)
- check the fiber-optic cable and if required, replace.
'- check the power supply of the IGBT gating module (24 V).
- select the defective semiconductor and replace.C401


Notice:
has been undershot.
See also: r0037
In general:
- check the line supply voltage at the input terminals.
- check the line supply voltage setting (p0210).
- the following applies to booksize units: Wait (approx. 8 min.) until the pre-
charging resistors have cooled down. For
this purpose, preferably disconnect the infeed unit from the line supply.
Re 5):
- carefully observe the permissible pre-charging frequency (refer to the
appropriate Equipment Manual).
Re 6):
- check the total capacitance of the DC link and if required, correspondingly
reduce the maximum permissible DC
link capacitance (refer to the appropriate Equipment Manual).
Re 7):
- interconnect the ready for operation signal of the infeed unit (r0863.0) in the
enable logic of the drives connected
to this DC link.
Re 8):
- check the connections of the external line contactor. The line contactor must
be open during the DC link fast discharge.
Re 9):
- check the DC link regarding ground fault or short-circuit.

Notice:
has been undershot.
check whether the fan is running.

check the fan elements
check whether the ambient temperature is in the permissible range.
Notice:
has been undershot.
check whether the fan is running.

check the fan elements
check whether the ambient temperature is in the permissible range.
check the motor load.
check the line supply phases.
Notice:
has been undershot.
Check the 24 V DC power supply for the power unit and if required replace the
module.
- check the voltage supply for the Control Unit (24 V).
- if required, replace the module.
Re fault value = 0:
Replace the power unit module or update the EEPROM data.
Re fault value = 1:
Update the firmware \SIEMENS\SINAMICS\CODE\SAC\cu31xi.ufw (cua31.ufw)
In order to avoid critically damaging the complete drive converter group, it is

urgently recommended to replace the
damaged infeed unit.

The power unit only supports the following cycles:
62.5 μs, 125 μs, 250 μs and 500 μs
0: Set a permitted current control cycle.
1: Set a permitted DRIVE-CLiQ cycle.
2/3: Contact the manufacturer (there is possibly an incompatible firmware
version).

Check the interface (adjustment and locking) to the power unit.
Check the interface (adjustment and locking) to the power unit.
Either replace the CU board or the power unit. You must check which of the two
components must be replaced by
replacing one and then the other component; if neither are available then both
components must be returned.
Evaluate the diagnostic parameters.

If the actual value channel is incorrect, check the components and if required,
replace.
- check the device supply voltage (p0210).

- check the dimensioning of the line reactor.

- replace the Motor Module.
- carry out diagnostics for fault F30611.
Note:
CU: Control Unit
MM: Motor Module
Re fault value = 1 to 5 and 7 to 999:
- check the cross-checked data that resulted in a STOP F.
Re fault value = 6:
- check the wiring of the safety-relevant inputs (SGE) on the Control Unit
(contact problems).
- PROFIsafe: rectify contact problems/faults on the PROFIBUS master/PROFINET
controller. - check the wiring of
the fail-safe inputs on TM54F (contact problems).

- de-select all drive functions that are not absolutely necessary.
- reduce the number of drives.
Note:
CU: Control Unit
MM: Motor Module
- check parameter p1278 (for SBC, only p1278 = 0 is permissible).
- check that the electrical cabinet design and cable routing are in compliance
with EMC regulations (e.g. shield of the
motor cable and brake conductors are connected with the shield connecting
plate and the motor connectors are
tightly screwed to the housing).
Operation with Safe Brake Module:
- check the Safe Brake Modules connection.
- replace the Safe Brake Module.
Note:
MM: Motor Module
SBC: Safe Brake Control
For the higher-level control, the following applies:

- check the PROFIsafe address in the higher-level control and Motor Modules
and if required, align.
For TM54F, carry out the following steps:
- start the copy function for the node identifier (p9700 = 1D hex).
- acknowledge hardware CRC (p9701 = EC hex).
The following generally applies:
Note:
MM: Motor Module
See also: p9810 (SI PROFIsafe address (Motor Module))
- re-commission the Safety Integrated function and carry out a POWER ON.
- replace the Motor Module.
Note:
MM: Motor Module

- carry out safety commissioning routine.
- again carry out safety commissioning routine.
- check the safety parameters in the Motor Module and adapt the reference
checksum (p9899).
- Carry out an acceptance test and generate an acceptance report.
The procedure when carrying out an acceptance test as well as an example of
the acceptance report are provided
in the following literature:
SINAMICS S120 Function Manual Safety Integrated
- carry out the function checks for the modified hardware and generate an
acceptance report.
The procedure when carrying out an acceptance test as well as an example of
the acceptance report are provided
in the following literature:
SINAMICS S120 Function Manual Safety Integrated
- carry out diagnostics for the other safety-related fault that is present.
Note:
MM: Motor Module
See also: p9799 (SI reference checksum SI parameters (Control Unit)), p9899 (SI
reference checksum SI parameters
(Motor Module))

Note:
MM: Motor Module
Upgrade the Motor Module software.

Note:
MM: Motor Module
Note:
CU: Control Unit
MM: Motor Module
- re-commission the safety functions.

Note:
MM: Motor Module
Re fault value = 10, 11, 13, 14, 15, 16:

involved (F01655, F30655) and if required, carry out diagnostics for the faults
involved.
- use a Motor Module that supports the required function ("Safe Torque Off",
"Safe Brake Control",
"PROFIsafe/PROFIsafe V2", "motion monitoring functions integrated in the
drive").
Note:
CU: Control Unit
MM: Motor Module
SBC: Safe Brake Control
SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)
involved (F01655, F30655) and if required, carry out diagnostics for the faults
involved.
- use a Control Unit that supports the safe motion monitoring function.
Note:

- set the reference checksum to the actual checksum.
Note:
- De-select the monitoring function involved (p9301, p9301, p9303, p9601,

p9801).
- Upgrade the Motor Module firmware.
See also: p9301 (SI Motion enable safety functions (Motor Module)), p9501 (SI
Motion enable safety functions (Control
Unit)), p9503 (SI Motion SCA (SN) enable (Control Unit)), p9601 (SI enable,
functions integrated in the drive
(Control Unit)), p9801 (SI enable, functions integrated in the drive (Motor
Module))
Enable the function "SOS/SLS" (p9301.0).

Note:
See also: p9301 (SI Motion enable safety functions (Motor Module))
Correct the limit values for SLS and carry out a POWER ON.
Note:
See also: p9331 (SI Motion SLS limit values (Motor Module))
Either de-select the function "actual value synchronization" or the monitoring

functions with absolute reference
(SCA/SLP) and carry out a POWER ON.
Note:
See also: p9501 (SI Motion enable safety functions (Control Unit))
- remove DRIVE-CLiQ components that are not required.
- de-select functions that are not required.
- if required, increase the sampling times (p0112, p0115).

Replace the module.

- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).

- if required, use another DRIVE-CLiQ socket (p9904).


- if required, upgrade the firmware in the power unit.
Upgrade the firmware of the component involved.
See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
- check the power supply voltage of the component involved.



- when replacing cables, only use cables with the same length as the original
cables.
- when replacing components, use the same components and firmware releases.
- replace the firmware on the power unit by an older firmware version (r0128).
- upgrade the firmware on the Control Unit (r0018).C456
Re fault value = 80000000 hex:

Re fault value = 00000001 hex ... 0000FFFF hex:
- replace the module.
- if required, upgrade the firmware in the power unit.

- if message output above speed threshold, reduce filter time if necessary
(p0438).
(p0438).
- when p0437.1 is active, check p4686.
- check the speed range, frequency characteristic (amplitude characteristic) of

the measuring equipment may not be
sufficient for the speed range.
EMC.
- check whether the zero mark is connected and the signal cables RP and RN
connected correctly.
- if the coding disk is soiled or the lighting worn, replace the encoder.
Re fault value, bit 0 = 1:
- encoder defective. F31111 may provide additional details.
- Incorrect encoder type / replace the encoder or encoder cable.
- EMC / connect the cable shield, replace the encoder or encoder cable.
- EMC / connect the cable shield, replace the encoder or encoder cable, replace
the Sensor Module.
the Sensor Module.
- Update the firmware for the Sensor Module.
- Check the parameterization (p0429.2).
the Sensor Module.
- Check the parameterization (p0429.2, p0449).
- Check the parameterization (p0436).
- Check the data line.
Encoder is defective. Replace the encoder, where the motor encoder has a direct
DRIVE-CLiQ socket: Replace the
motor.
motor.
motor.
5 V power supply voltage fault.
When using an SMC: Check the plug-in cable between the encoder and SMC or
replace the SMC.
When a motor encoder with a direct DRIVE-CLiQ connection is used: Replace the
motor.
replace the SMC.
When using a motor with DRIVE-CLiQ: Replace the motor.
motor.
The battery must be changed (only for encoders with battery back-up).
For fault value, bit 0 = 1:

In the case of an EnDat encoder, F31111 may provide further details.
EMC.
- with measuring systems without their own bearing system: Adjust the scanning
head and check the bearing system
of the measuring wheel.
- for measuring systems with their own bearing system: Ensure that the encoder
housing is not subject to any axial
force.
EMC.
- check the setting of p0405: p0405.2 = 1 is only possible if the encoder is

connected at X520.
- check the encoder/cable: Does the encoder supply TTL signals and the
associated inverted signals?
Note:
For a squarewave encoder without track R, the following jumpers must be set at
the encoder connection:
- pin 10 (reference signal R) <--> pin 7 (encoder power supply, ground)
- pin 11 (reference signal R inverted) <--> pin 4 (encoder power supply)
- if required, increase the maximum speed difference per sampling cycle (p0492).

- correct encoder cable connected?
- check the plug connections of the encoder cable.
- SMC30: Check the parameterization (p0404.22).
Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module.
- make sure that the encoder cables and shielding are installed in an EMC-
compliant manner.
- check the short-circuit of a signal cable with mass or the operating voltage.
- replace the encoder cable.A472
EMC.
EMC.
- Check and, if necessary, correct p0431 (trigger via p1990 = 1 if necessary).

- if the Hall sensor is used as an equivalent for track C/D, check the connection.
- Check connection of track C or D.
- check whether the coding disk is dirty or there are strong ambient magnetic
fields.
(p0438).
Replace DRIVE-CLiQ encoder.
Replace encoder
Replace encoder
- Check that p0404 is correctly set.

- check the encoder type used (incremental/absolute value) and for SMCxx, the
encoder cable.
- if relevant, note additional fault/error messages that describe the fault in
detail.
Reduce the speed of the encoder accordingly during initialization.

If necessary, deactivate monitoring (p0437.29).
See also: p0437 (Sensor Module configuration extended)
Reduce the ambient temperature for the DRIVE-CLiQ connection of the motor.

- reset the position tracking as follows (p0411.2 = 1).

adjusted (p2507).
See also: p0010
It must be ensured that all of the encoders, with mounted measuring gear,
provide valid actual values in operation.
Reduce the current controller frequency.

maintained.
Replace the module.
Acknowledge the fault.
Replace encoder





- check whether the firmware version of the encoder (r0148) matches the
firmware version of Control Unit (r0018).


cables.

(r0148).
- check whether the connected encoder type matches the encoder that has been
parameterized.
- correct the parameter specified by the fault value (r0949) and p0187.
- re parameter number 314: Check the pole pair number and measuring gear
ratio. The quotient of the "pole pair
number" divided by the "measuring gear ratio" must be less than or equal to
1000 ((r0313 * p0433) / p0432 <= 1000).
parameterized.
(p0438).
(p0438).

EMC.
the Sensor Module.
the Sensor Module.
the Sensor Module.
motor.
motor.
motor.
replace the SMC.
motor.
replace the SMC.
motor.

EMC.
- with measuring systems without their own bearing system: Adjust the scanning
head and check the bearing system
of the measuring wheel.
- for measuring systems with their own bearing system: Ensure that the encoder
housing is not subject to any axial
force.
EMC.

connected at X520.
Note:
- if required, increase the maximum speed difference per sampling cycle (p0492).

compliant manner.
EMC.
EMC.
- if the Hall sensor is used as an equivalent for track C/D, check the connection.
- check the connection of track C or D.
fields.
(p0438).

Replace encoder
Replace encoder

encoder cable.
detail.


adjusted (p2507).
See also: p0010

maintained.
Replace the module.
Acknowledge the fault.
Replace encoder








cables.

(r0148).
parameterized.
1000 ((r0313 * p0433) / p0432 <= 1000).
parameterized.
(p0438).
(p0438).

EMC.
'- replace the encoder cable.
the Sensor Module.
the Sensor Module.
the Sensor Module.
motor.
motor.
motor.
replace the SMC.
motor.
replace the SMC.
motor.

EMC.
EMC.

connected at X520.
Note:

- if required, increase the maximum speed difference per sampling cycle
(p0492).C575Encoder 3: Power supply voltage fault


compliant manner.
EMC.
EMC.
;- track C or D not connected.

- check the adjustment of the Hall sensor.E580
'- if the Hall sensor is used as an equivalent for track C/D, check the connection.
- check the connection of track C or D.
- replace the encoder or encoder cable.E583:E587
fields.
(p0438).
Replace encoder
Replace encoder
encoder cable.
detail.



adjusted (p2507).
See also: p0010

maintained.
Replace the module.

Replace encoder









cables.
'- replace the firmware on the Sensor Module by an older firmware version
(r0148).
parameterized.
1000 ((r0313 * p0433) / p0432 <= 1000).
parameterized.
- check the fan.

- reduce the power.
Replace the Voltage Sensing Module.

- check whether the permissible ambient temperature for the Voltage Sensing
Module is being maintained.
- replace the Voltage Sensing Module.
maintained.
- replace the Voltage Sensing Module.
maintained.
- replace the Voltage Sensing Module (VSM).
Replace the Voltage Sensing Module.



- replace the Voltage Sensing Module (VSM).

- if required, upgrade the firmware in the Voltage Sensing Module.



- replace the component involved.C636

cables.
- replace the firmware on the Voltage Sensing Module by an older firmware

version (r0158).
Adapt the sampling time (e.g. set the recommended valid sampling time).
See also: p10000 (SI sampling time)

Cancel the pulses for the drive specified in the fault value.
Correct the assignment of the drive object numbers.

See also: p10010 (SI drive object assignment)
Check the wiring of the F-DIs and F-DOs and restart the test stop. The fault is
withdrawn if the test stop is successfully
completed.
- check the 24 V DC power supply for the TM54F.

- check the 24 V DC power supply for the TM54F.

Carry out the following steps on the TM54F:
- activate the safety commissioning mode (p0010 = 95).
- start the copy function for SI parameters (p9700 = 57 hex).
- acknowledge complete data change (p9701 = AC hex).
- exit the safety commissioning mode (p0010 = 0).
For an internal software error (aaaa greater than zero):
- allow the TM54F to cool down.


Check the wiring of the F-DI and F-DO (contact problems).
Note:
A discrepancy of the F-DO also occurs (in this special case, in conjunction with
fault F35150 for the TM54F slave),
if, after replacing a Motor Module, it was forgotten to acknowledge this.
F-DI: Failsafe Digital Input
F-DO: Failsafe Digital Output
Discrepancy errors of the F-DIs can only be completely acknowledged if, after
the cause of the error has been
resolved, safe acknowledgement was carried out (refer to p10006). As long as
safety acknowledgement was not carried
out, the corresponding F-DI stays in the safe state.
- allow the temperature sensor to cool down.

- if required, set the fault response to NONE (p2100, p2101).
SIMOTION (p4400 = 0) operating mode:
- enter a lower speed setpoint (p1155).
- reduce the encoder pulse number (p0408).
- if the TM41 is configured as technology object in SIMOTION, then this fault is
generated if the A/B signals in connector
X520 are short-circuited
SINAMICS (p4400 = 1) operating mode:
- the fine resolution of TM41 in p0418 does not match that of the connector
input that was interconnected at P4420
- the encoder position actual value r0479 interconnected at connector input
p4420 has an excessively high actual
speed
- reduce the basic clock cycle (p0110, p0111).

- replace the module.
The module must be replaced if no other alarms that refer to a communications

error are present in the system.
Upgrade the firmware of the DRIVE-CLiQ component involved.

Re fault value = 1:
If the motor overtemperature time stage is to be used, the TM31 must be
replaced. The order number of the replacement
module should be 6SL3055-0AA00-3AA1 with software version V2.6 or higher..



- replace the Terminal Module (TM).

- if required, upgrade the firmware in the Terminal Module.




cables.
- replace the firmware on the Terminal Module by an older firmware version

(r0158).
- Check ambient temperature at component installation location.

- replace the component involved.C674

- reduce the current controller frequency.

- carry out a POWER ON.- carry out a POWER ON.





- Check supply voltage of component involved.



cables.
- Replace the firmware on the DRIVE-CLiQ Hub Module with older firmware
(r0158).
- upgrade the firmware on the Control Unit (r0018).C689
Evaluate the fault buffer of the specified object.

Evaluate the fault buffer of the specified object..








Module).
See also: p0266 (Cooling system, feedback signals, signal source)
Check the device to de-ionize the cooling liquid.
Module).
Module).
- check the cooling system for leaks in the cooling circuit.
- check the wiring of the input terminal (terminal Module) used to monitor
leaking fluid.
Upgrade the firmware. Check EEPROM data.
Check the cooling system and the ambient conditions.
- check the excitation.

- check commands, feedback signals and BICO interconnections.
- read out diagnostics parameter (r9999).

See also: r9999 (Software error internal supplementary diagnostics)
None necessary.
Note:
CU: Control Unit
None necessary.
Note:
CU: Control Unit
None necessary. The alarm automatically disappears when the limit value is
undershot.
None necessary.
Note:
MM: Motor Module
None necessary.
Note:
MM: Motor Module
Evaluates other current messages.

the measuring equipment is not sufficient
for the speed range.
EMC.
- if the coding disk is soiled or the lighting worn, replace the encoder.D981
EMC.

EMC.


software problems.
Also, check othe



Check external par
failure display.
failure display.
failure display.
failure display.
failure display.
failure display.











Check Motor
Decrease motor loading
Check motor loading
No actions necessary. Take a critical attitude to these values
Choose the application again and push the ENTER button

Contact Vacon
Check the cooling air flow and the ambient temperature
Check the current loop circuitry
Check the external fault circuit or device.

- Check loading
- Check motor size
- Check cables
Check utility connection.

Check motor cables
Check brake resistor

- If resistor is OK the chopper is broken, contact Vacon.
- Check the cooling air flow

- Check that the sink is not dirty
- Check ambient temperature
- Check that the switching frequency is not too high compared with ambient
temperature and motor load
- Check the motor

Decrease motor load.
Check the temperature model parameters if the motor was not overheated.
Check the polarity of the analogue input.

Contact Vacon
Check installation
- If installation is correct, contact Vacon.
Adjust the decelaration time
Check the cabling from +10V reference voltage

Check the cabling from +24V reference voltage.
When the fault is reset the frequency drive will automatically load parameter settings
after reset.
If the fault occurs again contact Vacon.
When the fault is reset the frequency drive will automatically load parameter settings
after reset.
If the fault occurs again contact Vacon.
Reset the fault and restart. Consult Vacon, if fault occurs again
Check the panel cable

- Check motor cooling and loading
- Check thermistor connection (if thermistor input of the I/O expander board is not in
use it has to be short circuited)
Check the motor cables
Check the current loop circuitry
Reset the fault and restart again. If the fault occurs again contact Vacon.
Check the external fault circuit or device.

Reset the fault and restart again. If the fault occurs again contact Vacon.
In case of temporary supply voltage break, reset the fault and start again.
Check utility input.
If the utility supply is correct and internal failure has occurred, contact Vacon.
Select the correct braking resistor.
• Check for faulty wiring.

• Correct the wiring.
• Check for disconnected cables and short circuits and repair as needed.
Replace the
• Check the various options available to minimize the effects of noise.
• Counteract noise in the control circuit, main circuit, and
- Check the motor parameter settings and repeat Auto-Tuning.

- Set the torque limit to the most appropriate setting (L7-01 through L7-04).
• Adjust the deceleration time (C1-02, C1-04, C1-06, C1-08).
• Set the frequency to the minimum value and interrupt
• Cycle power to the drive.

• If the problem continues, replace the control board or the entire drive. Contact
Yaskawa or a Yaskawa
representative for instructions on replacing the control board.
- Replace the operator.

• Turn off the power and check the connection between the control board and the drive.
• If the problem continues, replace the control board or the entire


• If the problem continues, replace the power board or the entire drive. Contact
representative for instructions on replacing the power board.
If the problem continues, replace the control board or the entire drive. Contact Yaskawa
or a Yaskawa
If the problem continues, replace the control board or the entire drive. Contact Yaskawa
or a Yaskawa
- Reduce the load.
- Increase the acceleration and deceleration times (C1-01 through C1-08).
- Check the machine.
- Check the settings of parameters F1-10 and F1-11.
- • Set H6-02 to the same value as the speed feedback signal frequency when the motor
run
• Make sure the PG encoder is properly connected and all shielded lines are properly
grounded.
• If the problem continues after cycling power, replace the PG option card or the PG
encoder.
* Separate the PG cable lines from the source of the noise.

* Rewire the PG encoder and properly ground all shielded lines.
* If the problem continues after cycling power, replace the PG option card or the PG
encoder.
- Set the value for Δθ to E5-11 as specified on the motor nameplate. Readjust the Z Pulse
offset when
replacing the PG encoder or changing the application to rotate the motor in reverse.
- • Make sure the motor is rotating in the proper direction.
• Ident
- • Set the value for Δθ to E5-11 as specified on the motor nameplate.

• If the problem continues after cycling power, replace the PG option card or the PG
encoder. Readjust
the Z Pulse offset when replacing the PG encoder or changing the application to r
• Measure the motor line-to-line resistance and replace the motor if the motor coil
winding is
disconnected.
• Check for loose terminals. Apply the tightening torque specified in this manual to
fasten the terminals.
Refer to Wire Gauges and Tightening Tor
Correct the cause of the fault.
- Execute DISCONNECT or ALM_CLR, then issue a CONNECT command or SYNC_SET

command and
proceed to phase 3. Refer to the SI-T3 Option Technical Manual for more details on
troubleshooting.
• Remove the cause of the external fault.

• Remove the external fault input from the PLC.
Check the PLC program and correct problems.
- Remove the cause of the external fault and reset the fault.
- • Properly connect the signal lines to the terminals assigned for external fault detection
(H1-oo = 20 to 2F).
• Reconnect the signal line.
• Check for unused terminals set for H1-oo = 20 to
(H1-oo = 20 to 2F).
(H1-oo = 20 to 2F).
(H1-oo = 20 to 2F).
(H1-oo = 20 to 2F).
(H1-oo = 20 to 2F).
(H1-oo = 20 to 2F).
(H1-oo = 20 to 2F).
(H1-oo = 20 to 2F).
- EEPROM Write Error

- Data cannot be written to the EEPROM
- • Press “ENTER” on the digital operator.
• Correct the parameter setting.
Yaskawa
• Check for fan operation.
• Verify the cumulative operation time of the fan with monitor U4-03, and verify the
cumulative operation
time of the fan maintenance timer with U4-04.
• If the cooling fan has exceeded its expected p
- Check b5-36 and b5-37 settings.

- Correct the wiring.
- • Check the sensor on the control side.
• Replace the sensor if damaged.
- Check b5-13 and b5-14 settings.

- • Check the sensor on the control side.
• Replace the sensor if damaged.
- • Check the insulation resistance of the motor.

• Replace the motor.
• Check the motor cable.
• Remove the short circuit and reapply power to the drive
• Check the resistance between the cable and the ground terminal .
• Replace the cable.
• Reduce the
• Check for wiring errors and properly connect the output cable.
• Check the resistance between motor lines.
• Replace the motor if the winding is damaged.
• Apply the tightening torque specified in this manual to fasten the terminal
- • Check for faulty wiring or poor connections on the output side of the drive.
Apply the tightening torque specified in this manual to fasten the terminals. Refer to
Wire Gauges and
Tightening Torque on page 89 for details.
If t
Cycle the power supply. Refer to Diagnosing and Resetting Faults on page 386 for details.
If the fault
continues to occur, replace the gate drive board or the entire drive. Contact Yaskawa or
a Yaskawa
representative for instructions on replacing the gate
Stop the drive when using the node setup function.

• Check the insulation resistance.
• Replace the motor.
• Check the motor cables.
• Remove the short circuit and reapply power to the drive.
• Check the resistance between the motor cables and the ground terminal .
• Replace damaged cables.
• Measure the
- Check if the drive supports the option card to be installed. Contact Yaskawa for
assistance.
- PG option cards are supported by option ports CN5-B and CN5-C only. Connect the PG
option card to
the correct option port.
• Turn off the power and reconnect the option card.

• Check if the option card is properly plugged into the option port. Make sure the card is
fixed properly.
• If the option is not a communication option card, try to use the card in a different
option po




- Make sure the drive supports the option card to be installed. Contact Yaskawa for
assistance.
- Communication option cards are only supported by option port CN5-A. It is not possible
to install more
than one communication option.
• Turn off the power and reconnect the option card.

fixed properly.
• Try to use the card in a different option port (in case of a PG option, use port CN5-C). If
th
- Except for PG options, only one of each option card type can only be installed
simultaneously. Make sure
only one type of option card is connected.
- Install a communication option, a digital input option, or an analog input option. More
than one of the

Confirm that the drive supports the option card to be installed. Contact Yaskawa for
assistance.s
• Turn the power off and reconnect the option card.

fixed properly.
• Try to use the card in a different option port (in case of a PG option, use port CN5-B). If
th
Except for PG options, only one of each option card type can only be installed
simultaneously. Make sure
only one type of option card is connected.
Install a communication option, a digital input option, or an analog input option. More
than one of the
s


• Check the temperature surrounding the drive. Verify temperature is within drive
specifications.
• Improve the air circulation within the enclosure panel.
• Install a fan or air conditioner to cool the surrounding area.
• Remove anything near the drive t
• Check the temperature surrounding the drive.

• Improve the air circulation within the enclosure panel.
• Install a fan or air conditioner to cool the surrounding area.
• Remove anything near the drive that might be producing excessive heat.
• Measure th
• Check the size of the load, the accel/decel times, and the cycle times.
• Decrease the load.
• Increase the acceleration and deceleration times (C1-01 through C1-08).
• Adjust the preset V/f pattern (E1-04 through E1-10) by reducing E1-08 and E1-10.
•D
• Check the size of the load, the accel/decel times, and the cycle times.
• Decrease the load.
• Increase the acceleration and deceleration times (C1-01 through C1-08).
•D
• Reduce the load.

• Check the ambient temperature.
- Reduce the load.
- Increase the acceleration and deceleration times (C1-01 through C1-08).
• Reduce the load.
• Increase the speed.
• If the motor is supposed to operate at low speeds, either increase the motor capacity
or use a motor
specifically desig
- Reduce the load.

- Increase the settings for the acceleration and deceleration times (C1-01 through C1-
08).
• Do not lower E1-08 and E1-10 excessively. This reduces load
- Check L6-02 and L6-03 settings.

- Check the status of the load. Remove the cause of the fault.
Check the settings of parameters L6-05 and L6-06.
Identify the cause of mechanical weakening.
• Reduce deceleration times in parameters C1-02, C1-04, C1-06, and C1-08 for
applications that do not
use High Slip Braking.
• Use a braking resistor to shorten deceleration time.
• Increase parameter n3-04 (High-slip Braking Overload Time).
• Install a t
• Check the connection between the operator and the drive.

• Replace the cable if damaged.
• Turn off the drive input power and disconnect the operator. Reconnect the operator
and reapply drive
input power.
• Increase the settings for C5-01 (Speed Control Proportional Gain 1) and reduce C5-02
(Speed Control
Integral Time 1).
• If using Closed Loop Vector mode, enable Feed Forward and perform Inertia Auto-
Tuning.
• Set H6-02 to the value of the speed feedback
• Increase the deceleration time (C1-02, C1-04, C1-06, C1-08).

• Install a dynamic braking resistor or a dynamic braking resistor unit.
• Set L3-04 to 1 to enable stall prevention during deceleration. Stall Prevention is
enabled as the default
setting.
-
• Check for wiring errors in the main circuit drive input power.
• Ensure the terminals are tightened properly.
• Apply the tightening torque as specified in this manual. Refer to Wire Gauges and
Tightening
Torque on page 89 for deta
- Reconnect the cable.

- Check the power line to the PG encoder.
- Ensure the motor brake releases properly.
Reconnect the cable and check the setting of F1-20.
- Select a braking resistor option that it fits the drive braking transistor specification.
- Set L8-55 to 0 to disable the braking transistor protection selection.
• Check the load, deceleration time, and speed.

• Reduce the load inertia.
• Increase the deceleration times (C1-02, C1-04, C1-06, C1-08, C1-09).
• Replace the dynamic braking option with a larger device that can handle the power
that is discharged.
-Reca
• Cycle power to the drive and check for reoccurrence of the fault.
• Replace either the control board or the entire drive. For instructions on replacing the
control board, contact Yaskawa or a Yaskawa representative.
• Check motor wiring.
• Turn off the power supply, then turn it on. If the problem continues, contact your
Yaskawa representative or the nearest Yaskawa sales office.
• Reduce the detection compensation gain during Speed Search (b3-10).
• Increase the current level when attempting Speed Search (b3-17).
• Increase the detection time during Speed Search (b3-18).
• Repeat Auto-Tuning.
- Set b3-14 to 1 to enable Bi-Direct
• Enter the correct motor code for the PM being used into E5-01.
• For special-purpose motors, enter the correct data to all E5 parameters according to
the test report
provided for the motor.
• Increase the load inertia for PM motor (n8-55).
• Increase th
- Set the torque limit to an appropriate value using parameters L7-01 to L7-04.
- Reduce the amount of load torque.
- Check the PG signal for noise interference.
Check the thermistor wiring.

Check the settings of parameters L6-02 and L6-03.
Check the load for any problems.
Check L6-05 and L6-06 settings

Check the load for any problems.
Check the load side for any problems.
• Check wiring
• Check for damaged transistors.
• Check for short circuits or grounding problems on the connected motor.
• The main circuit drive input power is wired incorrectly.
• Ensure there are no loose terminals.
• Apply the tightening torque specified in this manual to fasten the terminals. Refer to
Wire Gauges
and Tightening Torque on page 89 f
- Correct the setting to L2-02 or install an optional Momentary Power Loss Ride-Thru
unit.
• Cycle power to the drive. Check if the fault reoccurs.
• If the problem continues, replace the control board, the entire drive, or the control
power supply. For
i
• Cycle power to the drive and see if the fault reoccurs.

• If the problem continues, replace either the control board or the entire drive. For
instructions on replacing the control board, contact Yaskawa or a Yaskawa
representative.
• Check monitor U4-06
• Cycle power to the drive and see if the fault reoccurs. Refer to Diagnosing and
Resetting Faults on page 386 for details.
• If the problem continues, replace either the gate drive board or the entire drive. For
instructions on replacing the gate drive b
Replace the control board or the entire drive. For instructions on replacing the control
board, contact Yaskawa or a Yaskawa representative.
Check the wiring of analog input AI2 and the value of the signal
• Check the size of the resistor and wait for it to cool down.
• Check parameters [DB Resistor Power] (brP) and [DB Resistor value] (brU)
(consult the CD-ROM supplied with the drive).
• Check the wiring of the braking unit and the resistor.
• Check the braking resistor.
• Turn the drive off and then back on again.
• Check the internal connections.
• Contact Schneider Electric Product Support.
• Turn the drive off and then back on again.
• Check the environment (electromagnetic compatibility).
• Turn off, reset, return to factory settings.
• Turn off, reset, return to factory settings.
• Check the contactor and its wiring.
• Check the feedback circuit.
• Check the cables connecting the drive to the motor, and the motor insulation.
• Perform the diagnostic tests via the
[1.10 DIAGNOSTICS] menu.
• Check the catalog number of the power card and ensure that it is compatible
with the drive.
• Check the catalog number of the power card and ensure that it is compatible
with the drive.
• Contact Schneider Electric Product Support to have the drive recalibrated.
• Check the catalog reference and compatibility of the option.
Turn off the drive and reset
Check the control section power supply
• Replace the current sensors or the power card.
• Perform the diagnostic tests via the [1.10 DIAGNOSTICS] menu.
• Replace the temperature sensor.
Turn off the drive and reset. Contact Schneider Electric Product Support
• Check the motor parameters.
• Check the size of the motor, controller, and load.
• Check the state of the mechanism.
Contact Schneider Electric Product Support
• Check the cables connecting the drive to the motor, and the insulation of the
motor
• Reduce the switching frequency.
• Connect chokes in series with the motor.
motor
motor
• Check the motor, gain and stability parameters.

• Add a braking resistor.
• Check the size of the motor, controller, and load.
• Check the wiring between the encoder and the
drive.
• Check the encoder.
• Ensure that the motor and drive are compatible.
• Ensure that the motor is present during auto tuning.
• If an output contactor is being used, close it during auto-tuning.
Check the card programming, refer to the card documentation
• Check the wiring.
• Check the time-out.
• Replace the option card.
• Check the communication bus.

• Refer to the CANopen user's manual.
Correct the device and reset the drive
Correct the communication network and reset the drive
• Check the feedback circuit.
• Check the line/contactor/controller connection.
Check the connection on the analog inputs.
• Check and correct the cause of the low flow.
• Check the zero fluid detection parameters (consult the Programming Manual
on the CD-ROM supplied with the drive).
• Increase the deceleration time.
• Install a braking resistor if necessary.
• Activate the [Dec ramp adapt.] (brA) function (consult the Programming
Manual on the CD-ROM supplied with the drive), if it is compatible with the
application.
Check the motor load, the drive ventilation, and the ambient temperature. Wait
for the controller to cool down before restarting.
• Check and remove the cause of the overload.

• Check the parameters of the [PROCESS UNDERLOAD] (OLd-) function (consult
the CD-ROM supplied with the controller).
Check the setting of the motor thermal current parameter. Check the motor
load. Wait for the motor to cool down before restarting.
Check the connections from the drive to the motor

-Check the connections from the drive to the motor
- if an output contactor is being used, consult the programming manual on the
CD-ROM supplied with the drive.
-Test on a low-power motor or without a motor. In factory settings mode, motor
phase loss detection is active [Output phase loss](OPL)=[Yes](YES). To check the
drive in a test or maintenance environment without having to switch to a motor
with the same rating as the drive (particularly useful in the case of high-power
drives), deactivate motor phase loss detection [Output phase loss] (OPL)=[No]
(NO)
-Check and optimize the parameters [Rated motor volt.](UnS) and [Rated mot.
current](nCr) and perform an [auto tuning] (tUn)
Check the line voltage
• Check the motor load and motor size.

• Check the motor ventilation.
• Wait for the motor to cool before restarting.
• Check the type and state of the PTC probes.


• Check the PTC probes and the wiring between them and the motor/controller.
• Perform a test via the [1.10
DIAGNOSTICS] menu.
• Contact Schneider Electric Product
Support.
• Check the cables connecting the controller to the motor, and the motor
insulation.
• Perform a test via the [1.10 DIAGNOSTICS] menu.
• Check the communication bus.

• Refer to the Modbus User's Manual
• Check the PowerSuite -connecting cable.
• Check the terminal connection.
• Check the PID function feedback.
• Check the PID feedback supervision threshold and time delay (consult the
Programming Manual on the CD-ROM supplied with the drive).
• Check if there are any mechanical problems.
• Consult the Programming Manual on the CD-ROM supplied with the drive.
• Check the size of the load, motor, and controller.
• Wait for the drive to cool before restarting.
• Check and remove the cause of the under load.
• Consult the Programming Manual on the CD-ROM supplied with the drive.
• Check that there are no card errors.
• If the option card was changed or removed deliberately, consult the
Programming Manual on the CD-ROM supplied with the drive.
• Return to factory settings or retrieve the backup configuration, if it is valid
(consult the Programming Manual on the CD-ROM supplied with the drive).
• Check the configuration loaded previously.

• Load a compatible configuration.
• Consult the Programming Manual on the
CD-ROM supplied with the drive.
• Check the power connection and the fuses.
• Use a 3-phase mains supply
• Disable [Input phase loss] (IPL) = [No] (nO).
• Enter the correct parameter (reserved for Schneider Electric product support).
• Check that there are no card errors.
• If the control card was changed deliberately, consult the Programming Manual
on the CD-ROM supplied with the drive.
• Check the voltage and the voltage parameter (consult the Programming
Manual on the CD-ROM supplied with the drive).
• Replace the pre-charge resistor.
- Check the converter display panel for further messages, if there are messages,
please go to the relevant fault search list for further details.
* Replace NINP in ABB, if the DC link voltage fluctuated beyond 13%, also, when
ID motor run failed.
* One case in Germany where a CUVC board was replaced, and the Format
Failure 0 came up. This was due to the fact that the dip - switches of the new
CUVC is different to that of the ones we used. Dip switches adjusted to same
position. Compressor run ok.
- The service switch is in the wrong position (is set in service mode)
- Set the service switch back to normal position
- Outside electrical interference, switch OFF and ON compressor.
- Check the fault message on the Siemens PMU (operator panel)

- Run converter manually with service switch on, to see whether it is the drive or
the elektronikon
- Check the fault message on the Siemens BOP (operator panel)
- See F0022
the elektronikon
- Check the fault message on the Siemens PMU (operator panel) if A017 is
displayed, then
- Check and make sure this plug is engage via dummy plug of the hand held
controller (PMU)
Set the service switch back to normal position.
Change the following parameters on the Masterdrive by using the PMU or Drive
Monitor.
* P60 = 7 (Parameter access)

* P53 = 7 (Enable Write Access)
* P555i001 = 6101 (old value =1) (SCom2Word1Bit1)
In the control panel, push the "LOC / REM" to set the converter to REMOTE.
* Check the connection between the relevant relay and the corresponding
frequency converter.
* The K05 relay (as part of the service switch condition), under normal operation,
should be closed, however, due to unforseen circumstances, it was opened.
Bridge out this relay, and run the machine again. If the machine runs, then the
Elektronikon is probably has a bad relay, hence, replace the Elektronikon (or the
relay in case of emergency). This relay should only be bridged for fault finding,
under NO circumstances that this relay be remain bridged, as the converter will
run without the protection of the Elektronikon.
* If the K05 relay is bridged, but the converter still cannot, then it is the converter
fault. Check the converter fault message and follow the appropriate action
according to this fault code.
* NIOC card on the ABB converter could be faulty, please check this. This is done
by: on X2 of NIOC board, link DI1 and DI13. If this solve the problem, then the
problem is in the cable to the Service Switch or the K05 relay of the elektronikon.
Check the elektronikon if not done so.
* Check the connection between the relevant relay and the corresponding
* The K05 relay (as part of the service switch condition), under normal operation,
* If the K05 relay is bridged, but the converter still cannot, then it is the converter
- NIOC card on the ABB converter could be faulty, please check this. This is done
by: on X2 of NIOC board, link DI1 and DI13. If this solve the problem, then the
problem is in the cable to the Service Switch or the K05 relay of the elektronikon.
Check the elektronikon if not done so.
* The service switch is in the wrong position (is set in service mode)
* Set the service switch back to normal position
* Outside electrical interference, switch OFF and ON compressor.
* Check the fault message on the Siemens PMU (operator panel)

* Siemens MasterDrive: Check the DC Link voltage and r006 parameter, see if all
agree or within tolerance of each other. If not, then either the CUVC card or
(and ??) PSU card has a problem. If the PSU card has a problem, then the Start
Inhibit may not be possible, hence the converter cannot be started by the
Elektronikon. This can also be monitored by r012 parameter, (Service Switch
parameter acknowledgement. r012 = 1 => PMU controlled, r012 = 2 =>
Elektronikon Controlled)
* Check the frequency converter panel for fault messages and go to the relevant
VSD drive fault search list for further information.
* One case in Germany where a CUVC board was replaced, and the Format
Failure 0 came up. This was due to the fact that the dip - switches of the new
CUVC is different to that of the ones we used. Dip switches adjusted to same
position. Compressor run ok.
- Check there are no power factor correction capacitors or surge absorbers in the
motor cable.
Contact ABB
No idea
Please contact ABB

Check motor and motor cables.
- Check motor load

motor cable.
- Check Thermistors (PT100)
* Check that the overvoltage controller is on (parameter 20.05)

- Check parameter group 22
Usin Coasting to Stop function (if applicable)

Retrofit the frequency converter with a Braking Chopper and a Braking Resistor.


* Check communication cable
* Isolate converter from module, and use the VSD simulation software to test
whether module or converter is at fault.
A PC and RS485 <-> RS232 converter box is required as well as the DFM4win
cable) is required.The cable is to be connected in place of converter cable
connection. If the RS485 port is faulty ==> new module is required.
- Replace modbus adapter card
- Check communication cable

- Isolate converter from module, and use the VSD simulation software to test
whether module or converter is at fault.
A PC and RS485 <-> RS232 converter box is required as well as the DFM4win
cable. The cable is to be connected in place of converter cable connection. If the
RS485 port is faulty ==> new module is required.
- Replace modbus adapter card
Check the frequency converter panel for fault messages and go to the relevant
VSD drive fault search list for further information.
- Check DC link voltage, if this is fluctuated, then check NINP card.

motor cable.
Contact ABB
No idea
- Check the fault message on the operator panel.
Please contact ABB

Check motor and motor cables.
- Check motor load

motor cable.
- Check Thermistors (PT100)
- Check that the overvoltage controller is on (parameter 20.05)

- Check parameter group 22
Using Coasting to Stop function (if applicable)

Retrofit the frequency converter with a Braking Chopper and a Braking Resistor.


- Check the converter display panel for further messages, if there are messages,
please go to the relevant fault search list for further details.
- Replace NINP in ABB, if the DC link voltage fluctuated beyond 13%, also, when
ID motor run failed.

In the control panel, push the "LOC / REM" to set the converter to REMOTE.
- Check the connection between the relevant relay and the corresponding
- NIOC card on the ABB converter could be faulty, please check this. This is done
by: on X2 of NIOC board, link DI1 and DI13. If this solve the problem, then th
- Check the connection between the relevant relay and the corresponding
- The K05 relay (as part of the service switch condition), under normal operation,
- If the K05 relay is bridged, but the converter still cannot, then it is the converter

the elektronikon
- Check the fault message on the Siemens PMU (operator panel) and

- Check the fault message on the Siemens PMU/BOP (operator panel)
- Change P010 back to 0 (READY)
Check EXPANSION module no. 1 thoroughly. Reprogram module.

- Check connection cable between Master module (2X3) and the expansion
module (. X3)
- Power OFF and ON the compressor
The expansion module giving the problem can be found in the "EXTRA" display,
module (. X3)
- Power OFF and ON the compressor.
the one with the problem flashes.

module (. X3)

module (. X3)

module (. X3)

module (. X3)
module (. X3)
Check:
Check:
- Remove the drive and perform visual inspection of IGD.
- IGD (and maybe PSU) may need replacement.
Check the driven load for an overload condition.

- Are the motor and the converter matched?
- Have the dynamic performance requirements been exceeded.
Check the supply voltage. The converter regenerates without regeneration possbility.
Measure intake air or ambient temperature. Observe reduction curves at >40 deg. C.
Check:
- Whether the fan -E1 is connected and is rotating in the correct direction.
- The air intake and discharge openings for blockage.
- The temperature sensor at -X30
- Check the motor (load, ventilation, etc.). The current temperature can be read in r009
motor tmp.
- Check the KTY84 input at connector - X103:29, 30 for short-circuit.
Lock the motor.
Check:
- P72 Rtd Drive Amps
- MLFB P70
- P128 Imax
- r010 Drive Utilizat
Motor load cycle is exceeded !!

Check:
- P382 Motor Cooling
- P383 Mot Tmp T1
- P384 Mot Load Limits
- P804 Overspeed Hys plus

- P452 n/f(max, FWD spd) or
- P453 n/f(max, REV spd) has been exceeded.
Increase the parameter for the maximum frequencies or reduce the regenerative load.
Check:
- whether an excessive torque requirement is present.
- whether the motor has been dimensioned too small.
Increase values P792 Perm Deviation Frq/set/actual DevSpeed and P794 Deviation Time.
Check:
- Whether the drive is locked
- Whether the encoder cable is interrupted during speed control and whether the shield
is connected.
- Whether the drive has stalled
- For synchronous motors (P095 = 12): excitation current injection
Usually the leakage reactance P122 is the average value resulting from the measured
values in r546.1…12, and the rotor resistance r126 from the values in r542.1..3.
If individual measured values significantly deviate from the average values, they are
automatically not taken into account for the calculation (for RI) or the value of the
automatic parameterization remains (for Ls). It is only necessary to check the results for
their plausibility in the case of the drives with high requirements on torque or speed
accuracy.
If the standstill measurement can be executed withou any danger:

P561 Scr InvRelease - Release the inverter
If necessary, re-start the measurement by powering up the converter.

If the rotating measurement can be executed without any danger:
At terminal X101 of CUVC card check:
- Pin 1 & 2: Use Vdc multimeter to check for 24 Vdc. If not, then the power supply card,
PSU1 is faulty.
Also, at X102, pin 13 should have 10 Vdc, and pin 14 = -10Vdc, with pin 2 common.
If these voltages are present, then the CUVC card is faulty.

- Try to reprogam the MKIII
P591 S.MC chkbck sign.

The parameter value must match the main contactor checkback signal connection. Check
the main contactor checkback signal circuit.
Should NEVER happen in Masterdrive Series.
- Check the supply voltage.
- Can fail if low V, because software setting for V is wrong.
- Compare with P071 Line Volts (Compare P071 with the DC link voltage on DC units)
- Check the rectifier / regenerative unit on DC units. The rectifier/regenerative unit on
DC units. The rectifier/regenerative unit must be switched on before the inverter is
switched on.
- Check voltage C and D. Should get high 500V's (dc). While having the multimeter on it,
please restart the machine (in converter local control mode). If the voltage deteriorate in
over a short period of time, then there is pre-charge problem, hence, change the pre-
charger PCB, or Siemens to change it if under warranty. For G85GA30VSD case, the
whole drive should be return to Siemens for evaluation, if under warranty.
- Check supply voltage or DC voltage

- Converter is working at upper tolerance limit and at full load.
- Can be caused by line phase failure
- Converter is operating in regenerative mode without feedback possibility
- Try:
- Increase P464 Decel Time
- Activate P515 DC Bus Volts Reg (check P071 beforehand)
- Reduce P526 Fly Search Speed
- Reduce P259 Max Regen Power (only for P100 = 3, 4 or 5)
On a GA 37 VSD, that we have been working on was starting /stopping intermittantly.

It had the same problem as before showing an erratic DC Link voltage at the PMU, with
stable voltage at the DC Link. The original power supply (PSU) was faulty, and replaced
with a new PSU. Weeks later, the problem still existed.
The problem was traced to a break it a joint on the power supply control card that was
replaced by us.
The card was repaired onsite and the problem rectified.
- Check Input DC voltage

- DC link - Check for PCC (precharger card) and PCU (Precharger Unit - the less dense in
terms of electronics, of the two cards - This card normally OK)
- Maybe diodes blown as well, please check.
- Check for thyristor modules, should be approx. 6v in-circuit diode check! And OPEN-
CIRCUIT out-of-circuit diode check !
- IVI card may be faulty as well.
- Terminal C and D should be checked using multimeter with Vdc, or some sort of Scope
meter. Should expect to be in excess of 500Vdc
- Can also be seen Simovis program. Parameter r006 (DC bus voltage). Can be checked
on PMU as well

- Check braking resistors
- Converter operates regeneratively without a feedback possibility. Braking unit must be
set to the lower response then threshold (673V)
- Check the free rotation (by hand) of the compressor element / motor
- Check connections at the measuring devices in the front of the converter
- Check if incoming supply voltage < 400 -10% and verify if cable section is accurate to
spec. (min 50mm square)
- Check RFI - net filter for short circuit
- Check the converter output for short-circuit or earth fault
- Check the load for an overload condition
- Check whether motor and converter are correctly matched (this should always be true)
- CT (current transformer) maybe faulty. As current is asked for again and again causing
build up of --> overcurrent. This condition is usually NOT intermittent. CT are very hard
to check, can only be done by v/hz meter and observe for characteristics.
- Check IVI (inverter interface card), replace if cannot solve. Check ABO (adaptor board),
ABO and IVI must be matched.
- Check the resistance of the motor windings in the 3 phases
- Try to start without back pressure, ie with an empty air net
- Try to program P0462 to 30 sec for slower acceleration
- Try new CUVC board
* The fault display must be cleared first before the parameters can be accessed. If the
F011 cannot be cleared, then it is probably the CT (LEM) module is at fault.
But to clear the fault, the scroll UP / DOWN must be pressed at the same time.
for resistance across C and L1(u), then L2(v) and L3(w); D across L1(u), L2(v) and L3(w).
If we get short in any of the combinations, eg, resistance between C and L1 then the
IGBT (transistor) is damaged. For all IGBT's to be OK, then some resistance is expected on
all combinations.
Try to start the converter with MOTOR DISCONNECTED and Service switch to manual
control:
- To do this, please observe and adjust the following parameters:
For CUVC MasterDrive:

- Make P53 = 6 (on Simovis, it is binary number . . . 110), then P060 = 5 (Drive Setting),
then P100.1 = 3 (f regulated) to P100.1 = 1 (u/f). The idea here is to change the VECTOR
CONTROL to voltage control. THEN, change P060 = 0 (or 1) in order to start the converter
manually. If NOT, then 005 always appear on the PMU.
If F011 CANNOT be resolved, and P060 = 5, and DOES NOT able to be programmed back
to P060 = 0 or 1, then the CT (LEM) is faulty. This symptom occurs when the PMU is been
- Only for closed loop n/f/T control (P100 = 3, 4 or 5)
- If no motor is connected, go into the simulation mode P372
- Check current detection, check power section
- Check the output contactor
- Check the motor cable
- Check Motor / element for free rotation

- Check current in all three phases to the motor, make sure that they are within 10% of
each other.
- Check the bearings of the motor.
- Reduce Load
- Increase current Limits
- Reprogram card
- Change new CUVC card
- Could be one phase missing, where consumption on all 3 phases arevery different.E97
inverter bridge.
- Power up after coasting

- Possibly increase P525 Fly Search Amps
- Fault - check the KTY84 input at connector - X103:29, 30 for short circuit.
wiring.)

EMERGENCY ONLY:
display the actual motor temperature, HOWEVER, it will still the protects the system and
shutdown at and above temperature 180 deg. C.

- P380.1 = 0
deg. C)
Check : P383 Mot Tmp T1
Measure the air intake and ambient temperature. Please observe the reduction curves
at >40 deg. C
Check:
- Whether the fan E1 is connected and is rotating in the correct direction
- that the air entry and discharge openings are not restricted

maybe on its way out as well.G98


unbalance in supply voltage E100will give 25 deg. C higher in motor temperature.
- Check if one of the coils of line reactor L1 is short circuit.F106
- Possibly CU is faulty
to do so.
- Check cabinet for ventilation

- See ECB 1339

- GA180VSD and related

- Reparameterize
- Reset unit
- Replace CU (A10)
- Replace CU (A10)
Replace CU (A10)
Reverse 2 incoming lines
On PMU / Simovis - The fault cause can be read our of r358 (CU2) or r 376 (CUVC)
"ground fault test result"
- Check the converter output for short circuit of ground fault (-X2:U2, V2, W2 - including
motor)
- Check CU is inserted correctly
Frame Sizes 1 & 2

- Check the transistor modules on the PEU board A23 for short circuit
Frame Sizes 3 & 4
- Check transistor modules A100, A200, A300 for short circuit
Check the power section valves for a short circuit, and for converters with fiber-optic
gating, the gating unit and the UCE checkback signals, for the correct assignment.
PMU / Simovis: r358 (CU2), r376 (CUVC) can be interrogated to indicate which UCE mo
PMU / Simovis: Read-out fault value from R949. The digit of the xth position indicates
the valve, where the fault occurred at power-up.
XOOO Digit X = 1 = V+, X = 2 = V-, X = 3 = U+
Digit X = 4 = U-, X = 5 = W+, X = 6 = W-
The digit of the xth position defines the pahse, in which i is 0 and thus a valve is
defective (always conductive)
OOOX Digit X = 1 = Phase 1 (U)

X = 3 = Phase 3 (W)
X = 4 = Phase 1 (U) r 3 (W)
Examine phase for defective valves (always conductive)
PMU / Simovis: Read-out fault from r949. The digit of the xth position specifies the valve,
which, when triggered, manifested the fault.
XOOO x = 1 = V+, x = 2 = V-, x = 3 = U+

x = 4 = U-, x = 5 = W+, x = 6 = W-
Check the motor including feeder cable for ground faults. If there is no ground fault,
check the power section for defective valves which remain conductive.
The digit of the xth position defines the phase in which I is 0, and therefore a valve must
be defective (always conductive)
OOOX Digit x = 1 = Current in phase 1(U)
x = 2 = UCE in phase 2 (V)
x = 3 = Current in phase 3 (W)
x = 4 = Only overcurrent occur
The motor speed should be less than 10% of the stated speed during the ground fault
test !
A ground fault is present in phase V, or there is a defective valve (always conductive)

- Check the free rotation of the compressor element and/or motor eg a motor bearing
failure
- Check motor windings for possible ground fault
- Check resistance of the motor windings in the 3 phases
- Try start with no back pressure, ie with an empty net
- Check parameter P019 for the proper value (320A); as a trail lower the value in steps of
5 A to a minimum 300A
- Current transfomer may be faulty.
- Try new CCU board.
PLEASE NOTE: on former model GA90 VSD (SN < AII 492 000) Please observe ECB AII0070
(Priority IV) with regards to OIL RESTRICTION AT LOW SPEED for GA90VSD with Simovert
P converter.
FAULTS.

unbalance in supply voltage will give 25 deg. C E120higher in motor temperature.
FAULTS.
- PLEASE NOTE: on former model GA90 VSD (SN < AII 492 000) Please observe ECB
AII0070 (Priority IV) with regards to OIL RESTRICTION AT LOW SPEED for GA90VSD with
Simovert P converter.
FAULTS.
ZR160VSD:
- Based on ECB 1397/C1, this fault is present if the terminal X101-7 of the CUVC card is
open contact.
- This happen if the motor temperature is too high, or the temperature switch is faulty,
or loose connections. Please check these conditions..
Supplementary Reading:
* See function diagram 710, where binector U061 = 0 was made to U061 = 19,
* Binector U952.i059 = 20 was made to U952.i059 = 4.
- Check motor
inverter bridge.
May occur after a long period of standstill. In this case, restart the machine for up to 10
times.
If fault persists, check:
- Supply voltage is within tolerance 400V +/- 10%
- PCC (PreCharging Circuit)
- One of the capacitors may be defective
- Fault - check the KTY84 input at connector - X103:29, 30 for shortcircuit.
wiring.)

EMERGENCY ONLY:
display the E123actual motor temperature, HOWEVER, it will still the protects the system
and shuddown at and above temperature 180 deg. C.

- P380.1 = 0
deg. C)
- Check fan E1 is working, and in the correct direction

Replace Cuxx (-A10)


Switch off the unit and switch it on again. If the fault re-occurs, replace the Cuxx


- Check if one of the coils of line reactor L1 is short circuit.
- Possibly, CU is faulty
to do so.
- Reprogam Mark III and put in ARAVF.

- Check DC link voltage during operation which should be around 1.34 x Supply voltage.
- Check fuses.
- Check and make sure this plug is engage via dummy plug of the hand held controller
(PMU)
=F136- Check cabinet for ventilation

- GA180VSD and related compressors with VSD cooling fans. Check that the connection
between the masterdrive and the micromaster is located at pins 19 - 20 on the
masterdrive, and on pins 3 - 4 on the micromaster.
Also, very important to note that on a very HOT day, the micromaster also may
experience overtemperature problem, and therefore would malfunction, and the
Masterdrive converter will register fault F36 (or F036). There may be a fault message on
the micromaster itself, however, this fault message will only registered as an external
fault via the Masterdrive to the elektronikon.
- Therefore, should try to improve the air temperature within the cabinet to eliminate
this fault.
- ZT37VSD: (this may apply to others which have Micromasters drive as well) ARAVF,
everything else was re-started except the micromaster, hence giving F36. Solution was to
set Parameter P15 --- 0 to disabled, and 1 to enabled, and Parameter P18 --- 0 to
disabled and 1 to enabled. Take note when programming the Micromaster, the
parameters P7 = 1 and P9 = 3 for keypad accessibility.
- GA180VSD W (watercool): F36 indicates that the auxiallary drive has a fault. This
auxiallary drive is the positioner Y40 that regulates the By-Pass Oil Cooler solenoid valve.
Please check the status of this positioner. Pay attention to the connections, the OPEN &
CLOSE limit switches. If nothing is found, probably needs a new positioner. Atlas Part No.
1089 0652 01.
In an EMERGENCY, this by-pass oil cooler solenoid valve may be overwritten to allow the
compressor to continue running. The valve has to be overwritten mechanically,
electrically and on Siemens converter.
Mechanically: By turning to hand knob
Electrically: By disconnecting the power to the positioner, please consult electrical
diagram for confirmation of wire number, typically it should be wire labelled No. 2.
Disconnect the active wire only is sufficient.
Siemens Converter: Before any programming is done, make sure that P053 = 0006 for
general access to parameter changes. Go to P586, and change P586.1 from 601 to 001.
P586.1 = Parameter P586, first index. To access to P586.1, please go to P586, then press
P, and .001 shows up, press P again to access first index and scroll up (or down) to get to
the right value. (This is much simpler, if you are using the Simovis Software.)
- There is a thermal switch at the CUVC card of Siemen's converter, at X101, pin 3-4. This

- Reparameterize
- Reset unit

- Replace CU (A10)
- Replace CU (A10)
Replace CU (A10)
- Check operation of cooling fan, as well as power supply (380V) over K5 towards these
fans
- Check for polluted heat sink
- Check resistance value of both sets of thermistors which should be < 500 ohm at 20
Deg.C
For Simovert P:
- Check proper engagement of connector at X13 of CCU
- Check cooling flow over the drive motor
- An externally clogged oilcooler reduces the cooling
CU:- Voltage dips might be the reason, Reprogram the MKIII with latest service software
and put ARAVF active.
- Check DC link voltage during operation through r006 on the Siemens PMU
- IGBT or IGD1 defective is possibility. Maybe loose or bad connection.
See F008
CCU: - Pulsed Resistor or electronics overheating, ambient temp too high. Cooling fan
may be defective
**** Check input power supply. ***Using DIODE check on the INPUT line 1,2, and 3 and D/C link line.
Check motor for Earth fault. Usually, Overvoltage do not happen in most
countries, unless there is a major speak in power supply.
Please perform DIODE checks with respect to the DC Link terminals. Please see
VSD notes for more information on how to perform this task
*** Check element / bearing and make sure they are not seized. *** check Run
hours of motor / compressors since last had bearing change. Most bearings have
25,000 - 30,000 run hours. So if compressors maintenance record they within
this run hours window, should consider change of bearings before further works.
*** Check element / bearing and make sure they are not seized. *** check Run
hours of motor / compressors since last had bearing change. Most bearings have
25,000 - 30,000 run hours. So if compressors maintenance record they within
this run hours window, should consider change of bearings before further works.
*** Check fan for correct operations.

***Check for IBGT failures. May use DIODE checks on output of convertors to
motor.
motor.
***check for seized elements, bearings, check and confirm run hours since last
(if any) bearing changes. Typically, the motor bearings has 25,000 - 30,000
running hrs.
*** Check for ground faults of motor. *** Sometimes motor ground faults
present themselves as DC Link overvoltage
*** Check motor connections
*** check thermistor. *** check cooling fan, and room exhausts
Check for outside interference, eg, mobile phones, repeaters, etc

*** Check cooling fan, exhausts, and inlet filters (if any) to cabinet
*** Check cooling fan, exhausts, and inlet filters (if any) to cabinet

motor.
*** check actual temp of motor, and check thermistor for correct operations.
Refer to the RS-232 / RS-485 Serial communication manual.

Refer to the CANopen communication manual

motor.
AA: Incorrect wiring 1. Check all power and control connections. For instance,
the digital inputs set to
Start/Stop, General Enable, or no external error must be connected to the 24
Vdc
or to DGND* terminals (refer to Figure 3.36 on page 3-47)
BB: Analog reference (if used) 1. Check if the external signal is properly
connected
2. Check the status of the control potentiometer (if used)
CC: Incorrect settings 1. Check if the parameter values are correct for the
application
DD: Fault 1. Check whether the inverter is disabled due to a fault condition
2. Make sure that the terminals XC1:13 and XC1:11 are not shorted (short-circuit
at
the 24 Vdc power supply)
EE: Stalled motor 1. Decrease the motor overload
2. Increase P0136, P0137 (V/f), or P0169/P0170 (vector control)
AA: Loose connections 1. Stop the inverter, turn off the power supply, check and
tighten all the power
connections
2. Check all the internal connections of the inverter
BB: Defective speed reference
potentiometer
1. Replace the potentiometer
CC: Oscillation of the external
analog reference
1. Identify the cause of the oscillation. If it is caused by electrical noise, use
shielded
cables or separate them from the power and control wiring
Incorrect settings
DD: (vector control)
1. Check parameters P0410, P0412, P0161, P0162, P0175, and P0176
2. Refer to the programming manual
AA: Incorrect settings

(reference limits)
1. Check whether the values of P0133 (minimum speed) and P0134 (maximum
speed)
are properly set for the used motor and application
BB: Control signal from the
analog reference (if used)
1. Check the level of the reference control signal
2. Check the settings (gain and offset) of parameters P0232 to P0249
CC: Motor nameplate 1. Check whether the used motor matches the application
1. Decrease P0180
2. Check P0410
AA: Keypad connections 1. Check the inverter keypad connection

BB: Power supply voltage 1. Rated values must be within the limits specified
below:
- Minimum: 425 V
- Maximum: 759 V
CC: Mains supply fuses open 1. Replace the fuses
1. Decrease P0180
1. Check signals A - A, B - B , refer to the incremental encoder interface manual.
If
signals are properly wired, invert two of the output phases. For instance U and V

GA37 Troubleshooting Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GA37 Troubleshooting Guide

Uploaded by

Copyright:

Available Formats

VSD/Elektronikon Model Fault Control Type / Series

MKIII and Siemens MasterDrive "Blank Screen" All Mk III Elektronikons

MKIII and Siemens MasterDrive 0 All Siemens VSD.

MKIII and Siemens MasterDrive 10 Elektronikon Mk III LRR V1.8,

MKIII and Siemens MasterDrive 100 Elektronikon Mk III LRR V1.8,

MKIII and Siemens MasterDrive 107 Elektronikon Mk III LRR V1.8,

MKIII and Siemens MasterDrive 10XX Elektronikon Mk III LRR/HRR

MKIII and Siemens MasterDrive 11 Elektronikon Mk III LRR V1.8,

MKIII and Siemens MasterDrive 11XX Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 12 Elektronikon Mk III LRR V1.8,

MKIII and Siemens MasterDrive 17 Elektronikon Mk III LRR V1.8

MKIII and Siemens MasterDrive 200 Elektronikon Mk III LRR V

MKIII and Siemens MasterDrive 2001 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 204 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 20XX Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 22XX Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 37 Elektronikon Mk III -

MKIII and Siemens MasterDrive 40 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 41 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 42 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 43 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 44 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 45 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 46 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 47 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 48 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 49 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 50 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 51 Elektronikon Mk III HRR

MKIII and Siemens MasterDrive 54 Elektronikon Mk III HRR /

MKIII and Siemens MasterDrive 7001 Elektronikon Mk III HRR /

MKIII and Siemens MasterDrive 70XX Elektronikon Mk III HRR /

MKIII and Siemens MasterDrive 7101 Elektronikon Mk III HRR /

MKIII and Siemens MasterDrive 7201 Elektronikon Mk III HRR /

MKIII and Siemens MasterDrive 72XX Elektronikon Mk III HRR /

MKIII and Siemens MasterDrive 7401 Elektronikon Mk III HRR /

MKIII and Siemens MasterDrive 7402 Elektronikon Mk III HRR /

MKIII and Siemens MasterDrive 7601 HRR / VSD - Masterdrive

MKIII and Siemens MasterDrive A015 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A016 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A017 Masterdrive / CUVC, CU2

MKIII and Siemens MasterDrive A020 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A021 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A022 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A023 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A024 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A033 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A034 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A042 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A075 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A078 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A079 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive A080 MasterDrive Series - CUVC

MKIII and Siemens MasterDrive E All masterdrive CUVC series -

MKIII and Siemens MasterDrive F0 GA50VSD - CU2

MKIII and Siemens MasterDrive F002 Siemens MasterDrive Series

MKIII and Siemens MasterDrive F006 Siemens CUVC (MasterDrive)

MKIII and Siemens MasterDrive F008 Siemens CUVC (MasterDrive)

MKIII and Siemens MasterDrive F010 Siemens CUVC (MasterDrive)

MKIII and Siemens MasterDrive F012 Siemens CUVC (MasterDrive)

MKIII and Siemens MasterDrive F014 Siemens CUVC (MasterDrive)

MKIII and Siemens MasterDrive F015 Siemens CUVC (MasterDrive)

MKIII and Siemens MasterDrive F019 Siemens CUVC (MasterDrive)

MKIII and Siemens MasterDrive F021 Siemens, CUVC