Professional Documents
Culture Documents
CT UV CT / Emerson Commander
SK
CT OV CT / Emerson Commander
SK
CT OI.AC** CT / Emerson Commander
SK
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 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)
WEG CFW-11 FAQ - Motor does not start ZS+VSD, ZE/A VSD
RAM error
Keyboard error
AC-Line Fault
External alarm 1
External alarm 2
Overcurrent
Overvoltage
Inverter temperature
Motor temperature
Motor movement
I2t inverter
I2t motor
Overspeed
Motor stall/lock
Ls, Rr Dev
Stands. Meas
Motld: Dr.M
Contactor Checkback
Pre-Charging
DC link Overvoltage
DC link Undervoltage
DC link Overvoltage
Overcurrent
I too low
Motor Stall
Motor Temperature
Motor I2t
Inverter Temperature
UCE ph. L1
There was an UCE shut down in phase L1
UCE ph. L2
There was an UCE shut down in phase L2
UCE ph. L3
There was an UCE shut down in phase L3
Supply phase
External fault 1
External fault 2
AS internal fault
EEPROM fault
Coupling int.
Opt. Board HW
Par task / con.
GRND Init
GRND UCE
GRND Phase
Ground fault
Overcurrent
Motor Overload
Motor Pullout
Motor stall
PreCharge Error
Motor Temp.
Link Internal
UCE ph. L1
There was an UCE shut down in phase L1
Fault in EEPROM
UCE ph. L2
There was an UCE shut down in phase L2
UCE ph. L3
There was an UCE shut down in phase L3
Supply phase
Undervoltage
One phase missing
External fault 1
External fault 2
AC-Line Fault
AS internal fault
EEPROM fault
Coupling int.
Opt. Board HW
Overvoltage
Motor Overtemp
RAM 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:
Eprom checksum error
Wrong active display
Communication error
Load imbalance
External fault
Communication error
Excessive heat
Loss of communication
Short circuited
Download failed
Communication fault
ID Run is on
Motor ID Run is selected
Communication lost
Not uploaded
Thermistor warning
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
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 AI SCALE
PAR AO SCALE
PAR PCU 2
PAR EXT RO
PAR FIELDBUS
MISSING
PAR PCU 1
RESERVED
PAR PFC IO 1
PAR PFC IO 2
PAR PFC IO 3
RESERVED
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
EMERGENCY STOP
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)
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:
42.12 Brake fault func
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
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)
RESOLVER
AUTOTUNE ERR
(0x7388)
ENCODER 1 CABLE
(0x7389)
ENCODER 2 CABLE
(0x738A)
D2D
COMMUNICATION
(0x7520)
Programmable fault:
57.02 Comm loss func
D2D BUFFER
OVERLOAD
(0x7520)
Programmable fault:
57.02 Comm loss func
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)
SPEED FEEDBACK
(0x8480)
OPTION COMM
LOSS
(0x7000)
MOTOR TEMP2
(0x4313)
Programmable fault:
31.05 Mot temp2 prot
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)
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)
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)
INTBOARD
OVERTEMP
(0x7182)
BC MOD OVERTEMP
(0x7183)
AUTOPHASING
(0x3187)
PU LOST
(0x5400)
PS COMM
(0x5480)
EXTERNAL
(0x9000)
OVERSPEED
(0x7310)
BRAKE START
TORQUE
(0x7185)
Programmable fault:
42.12 Brake fault func
BRAKE NOT
CLOSED
(0x7186)
Programmable fault:
42.12 Brake fault func
BRAKE NOT OPEN
(0x7187)
Programmable fault:
42.12 Brake fault func
NVMEM
CORRUPTED
(0x6320)
OPTIONCOMM LOSS
(0x7000)
ENCODER 1
(0x7301)
ENCODER 2
(0x7381)
FIELDBUS COMM
(0x7510)
Programmable fault:
50.02 Comm loss func
FB MAPPING FILE
(0x6306)
MOTOR OVERTEMP
(0x4310)
Programmable fault:
31.01 Mot temp1 prot
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:
90.05 Enc cable fault
D2D CONFIG
(0x7583)
D2D COMM
(0x7520)
Programmable fault:
57.02 Comm loss func
TECH LIB
(0x6382)
TECH LIB CRITICAL
(0x6382)
FORCED TRIP
(0xFF90)
FB PAR ERROR
(0x6320)
STALL
(0x7121)
Programmable fault:
30.09 Stall function
LOAD CURVE
(0x2312)
Programmable fault:
34.01 Overload func /
34.02 Underload func
SPEED FEEDBACK
(0x8480)
MOTOR TEMP2
(0x4313)
Programmable fault:
31.05 Mot temp2 prot
current calibration
Overcurrent
Earth Leakage
Short Circuit
IGBT overload
DC link overvoltage
DC link undervoltage
DC not charged
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
Measurement circuit
temperature
PU board powerfail
PU communication internal
Measurement circuit
ADC
Measurement circuit DFF
PU state feedback
Charging feedback
AI parametization
Motor stall
Programmable warning:
31.24 Stall function
Motor fan
Programmable warning:
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
opening not allowed
Programmable warning:
44.17 Brake fault function
Extension AI
parameterization
Extension I/O
configuration failure
FBA B communication
Programmable warning:
50.32 FBA B comm loss
func
DDCS controller
comm loss
Programmable warning:
60.59 DDCS controller
comm loss function
Encoder
Programmable warning:
90.45 Motor feedback fault
Panel Loss Programmable warning:
49.05 Communication loss
action
Motor bearing
Programmable warnings:
33.14 On-time 1 warn message
33.24 On-time 2 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)
Programmable warning:
33.24 On-time 2 warn
message
Edge counter 1
Editable message text)
Programmable warning:
33.35 Edge counter 1
warn message
Edge counter 2
(Editable message text)
Programmable warning:
33.45 Edge counter 2
warn message
Value counter 1
(Editable message text)
Programmable warning:
33.55 Value counter 1
warn message
Value counter 2
(Editable message text)
Programmable warning:
33.65 Value counter 2
warn message
Device clean
DC capactior
Cabinet fan
cooling fan
additional cooling
AI supervision
Programmable warning:
12.03 AI supervision
function
Signal supervision
(Editable message text)
Programmable warning:
32.06 Supervision 1 action
Signal supervision 2
(Editable message text)
Programmable warning:
32.16 Supervision 2 action
Signal supervision 3
(Editable message text)
Programmable warning:
32.26 Supervision 3 action
External warning 1
(Editable message text)
Programmable warning:
31.01 External event 1
source
31.02 External event 1
type
External warning 2
(Editable message text)
Programmable warning:
31.03 External event 2
source
31.04 External event 2
type
External warning 3
(Editable message text)
Programmable warning:
31.05 External event 3
source
31.06 External event 3
type
External warning 4
(Editable message text)
Programmable warning:
31.07 External event 4
source
31.08 External event 4
type
External warning 5
(Editable message text)
Programmable warning:
31.09 External event 5
source
31.10 External event 5
type
Idtenification run
Autophasing
STO event Programmable event:
31.22 STO indication
run/stop
Calibration
Overcurrent
Short circuit
IGBT overload
BU current difference
BU earth leakage
DC link overvoltage
DC link undervoltage
Standby timeout
BU DC link difference
Autophasing
IGBT overtemperature
Cooling
IGBT temperature
excess temperature
External temperature
1
(Editable message text)
Fan
Auxiliary fan broken
PU logic error
Rating ID mismatch
PU communication
PU communication
PU communication internal
Measuremnt cirucit ADC
PU board powerfail
measurment circuit DFF
PU communication configuration
Reduced run
Pu state feedback
Charging Feedback
Internal SW error
FPGA version
incompatible
Task overload
Stack overflow
Licensing fault
Kernal overload
Parameter system
EFB invalid
parameterization
Panel port
communication
Programmable fault: 49.05
Communication loss
action
Ext I/O comm loss
Motor stall
Programmable fault: 31.24
Stall function
Brake resistor
BR excess temperature
BC short circuit
BC IGBT excess
temperature
Mechanical brake
closing failed
Programmable fault: 44.17
Brake fault function
Mechanical brake
opening failed
Programmable fault: 44.17
Brake fault function
Mechanical brake
opening not allowed
Programmable fault: 44.17
Brake fault function
Mechanical brake
opening not allowed
Programmable fault: 44.17
Brake fault function
Motor fan
Programmable fault:
35.106 DOL starter event
type
overspeed
Encoder internal
Encoder
Programmable fault: 90.45
Motor feedback fault
Speed feedback
configuration
Load feedback
Programmable fault: 90.55
Load feedback fault
Emergency ramp
failed
stop failed
FBA A communication
Programmable fault: 50.02
FBA A comm loss func
FBA B communication
Programmable fault: 50.32
FBA B comm loss func
DDCS controller
comm loss
Programmable fault: 60.59
DDCS controller comm
loss function
MF comm loss
Programmable fault: 60.09
M/F comm loss function
Line side unit faulted
AI supervision
Programmable fault:
12.03 AI supervision
function
Signal supervision
(Editable message text)
Programmable fault:
32.06 Supervision 1 action
Signal supervision 2
(Editable message text)
Programmable fault:
32.16 Supervision 2 action
Signal supervision 3
(Editable message text)
Programmable fault:
32.26 Supervision 3 action
External fault 1
(Editable message text)
Programmable fault: 31.01
External event 1 source
31.02 External event 1
type
External fault 2
(Editable message text)
Programmable fault: 31.03
External event 2 source
31.04 External event 2
type
External fault 3
(Editable message text)
Programmable fault: 31.05
External event 3 source
31.06 External event 3
type
External fault 4
(Editable message text)
Programmable fault: 31.07
External event 4 source
31.08 External event 4
type
External fault 5
(Editable message text)
Programmable fault: 31.09
External event 5 source
31.10 External event 5
type
ID RUN
Follower
FB A force trip
FB B force trip
FB C force trp
Hardware faults
RAM error
Keyboard error
G120
(Online) 12V short circuit or FET to enable damaged
AC-Line Fault
Earth fault
Powerstack fault
Overcurrent on W phase
EM brake overcurrent
BOP-EEPROM Fault
BOP fault
Asic Timeout
Par Cl. MMC-PS not fitted Fault
External Fault
Watchdog Reset
Stack Overflow
Belt Failure
Motor Stalled
Current Limit
Overvoltage limit
UnderVoltage Limit
Inverter OverTemperature
Inverter I2T
Output fault
CB communication error
CB configuration error
EEPROM inconsistent
Switch-on is inhibited
Overcurrent
Overload
Initialistion fault
Internal interface fault
External Trip
Programme fault
Flying Start Instability
Wrong Converter Status Word
Switch On Inhibit is active
Wrong Converter Status Word
The Elektronikon reads out the wrong bytes and
interprets them as the status word.
Wrong Converter Status Word
Converter Status = “running“, while Elektronikon
expects it has ‘stopped’
External Fault
LOS_NodeGuardCheck
LOS_NodeGuardCheck
LOS_NodeGuardCheck
LOS_NodeGuardCheck
LOS_NodeGuardCheck
LOS_CANstartupTimeOut
LOS_CANstartupTimeOut
LOS_CANstartupTimeOut
LOS_CANstartupTimeOut
LOS_CANstartupTimeOut
LOS_CANstartupTimeOut
LOS_CANstartupTimeOut
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 I2t
Earth Fault
Powerstack Fault
Output fault
Wrong IO board
Asic Timeout
CB Setpoint Fault
USS (BOP-Link) setpoint fault
External Fault
Stack Overflow
Current Limit
OverVoltage Limit
UnderVoltage Limit
Inverter Overtemperature
Inverter I2t
Motor Overtemperature
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
Motor Stalled
Undervoltage
Undervoltage
Undervoltage
Undervoltage
Undervoltage
Undervoltage
DC Link Overvoltage
DC Link Overvoltage
Undervoltage
Undervoltage
Overvoltage
Overvoltage
Overvoltage
Overvoltage
Overvoltage
Overvoltage
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Drive overtemperature
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Motor overcurrent
Overvoltage
Overvoltage
24 V power missing
TM: Speed setpoint filter natural frequency >
Shannon frequency
External alarm 1
External alarm 2
External alarm 3
DC brake active
VSM: EEPROM
TM: CRC
TM: EEPROM
TM: Initialization
Bypass LSS:
External fault 1
External fault 2
External fault 3
VSM: CRC
VSM: Initialization
TM54F: 24 V undervoltage
TM54F: 24 V overvoltage
RAM 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:
Eprom checksum error
Wrong active display
Motor stalled
Motor Overtemperature
Motor Underload
Stored Data has been changed
Reference Warning
External warning
Overcurrent
Drive undertemperature
Drive overtemperature
Motor stalled
Motor temperature
Motor underload
Analogue input polarity fault or analogue input
hardware fault
Option board identification
Overvoltage
Microprocessor Watchdog
Ground Fault
Analog input Iin < 4mA (signal range selected 4-
20mA)
Inverter Fault
External Fault
Charging Switch
Undervoltage
Control Fault
The torque limit was reached continuously for
three seconds or longer while ramping to stop in
OLV
Control.
Hybrid IC Failure
- 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.
- 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.
DriveWorksEZ Fault
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.
- 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).
Overvoltage
Thermistor Disconnect
Undertorque Detection 1
Undertorque Detection 2
Current Unbalance
DC Bus Undervoltage
base block
close brake
open brake
calculate drive
DC brake
Low speed/dc brake
forward acceleration
forward constant
forward deceleration
LA stop
Ld stop
positioning active
reverse acceleration
reverse constant
reverse deceleration
quick stop
Error! Brake
Error! Watchdog
no ERROR overload
no ERROR
Error! Overcurrent
Error! Overload 2
Error! Set
Warning! Overload
Warning! Overload 2
Warning! Prot.rot.for.
Warning! Prot.rot.rev
Warning ! Synchron
Warning! Set
AI2 Input
DBR overload
Precharge
Thyr. Soft charge
Control Eeprom
Power Eeprom
IGBT desaturation
Rating error
Incompatible PB
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
over speed
Auto-tuning
Application fault
Com. Network
CAN com.
External flt-Ll/bit
External fault com.
Out contact open.
input contractor
No flow fault
Over braking
Drive overheat
Mains overvoltage
PTC1 overheat
PTC2 overheat
PTC=LI6 overheat
PTC1 probe
PTC2 probe
Modbus com.
PowerSuite com
HMI com
PI feedback
Torque/current lim
IGBT overheat
Incorrect config
invalid config
Card pairing
Power Ident
Under voltage
DC Link fluctuations
Communications cannot be understood or are
not conform the expected messages
Overcurrent
Thermistor problem
DC Over Voltage
Short circuit
System Fault
Thermistor problem
DC Over Voltage
DC Link fluctuations
Converter Status failures
External alarm 1
External alarm 2
Overcurrent
Overvoltage
Inverter temperature
Motor temperature
Motor movement
I2t inverter
I2t motor
Overspeed
Motor stall/lock
Ls, Rr Dev
Stands. Meas
Motld: Dr.M
Contactor Checkback
Pre-Charging
DC link Overvoltage
DC link Undervoltage
DC link Overvoltage
Overcurrent
I too low
Motor Stall
Motor Temperature
Motor I2t
Inverter Temperature
UCE ph. L1
There was an UCE shut down in phase L1
UCE ph. L2
There was an UCE shut down in phase L2
UCE ph. L3
There was an UCE shut down in phase L3
Supply phase
External fault 1
External fault 2
AS internal fault
EEPROM fault
Coupling int.
Opt. Board HW
GRND Init
GRND UCE
GRND Phase
Ground fault
Overcurrent
Motor Overload
Motor Pullout
Motor stall
PreCharge Error
Motor Temp.
Link Internal
UCE ph. L1
There was an UCE shut down in phase L1
Fault in EEPROM
UCE ph. L2
There was an UCE shut down in phase L2
UCE ph. L3
There was an UCE shut down in phase L3
Supply phase
Undervoltage
One phase missing
External fault 1
External fault 2
AC-Line Fault
AS internal fault
EEPROM fault
Computing time problem
Coupling int.
Opt. Board HW
Overvoltage
Motor Overtemp
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.
Overcurrent/Short-circuit. Overcurrent or
short-circuit detected at the output, in the DC
bus, or at the braking resistor.
Motor Current
Imbalance. Fault of motor current unbalance.
Note:
It may be disabled by setting P0342 = 0.
CANopen
Communication Error. Alarm that indicates a
communication error.
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.
Internal Air
Overtemperature. Internal air
overtemperature fault.
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 Temperature
Fault. It indicates a temperature fault at the
sensor 2.
Sensor 1 Temperature
Alarm. It indicates a temperature alarm at the
sensor 1.
Sensor 2Temperature
Alarm. It indicates a temperature alarm at the
sensor 2.
Sensor 3 Temperature
Alarm. It indicates a temperature alarm at the
sensor 3.
Sensor 4 Temperature
Alarm. It indicates a temperature alarm at the
sensor 4.
Sensor 5 Temperature
Alarm. It indicates a temperature alarm at the
sensor 5.
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).
Chances are FET, and or diodes had gone. Possible what happen here is when the
connector is put upside down, and when 24V
Most probably due to a short circuit of the 12V supply for the digital inputs
Unrecoverable failures generated by the regulator.
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.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
Internal error
Unrecoverable failures generated by the regulator.
Internal error
Unrecoverable failures generated by the regulator.
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.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
A fault has occur, however the message has been masked by the parameter P60
- 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
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.
- 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.
- When pre-charging, the minimum DC link voltage (P071 Line volts x 1.34) of 80%
has not been reached .
During excitation of the induction motor, the current did not rise above 12.5% of
the setpoint magnetising current for no-load operation
Parameterized limit value of the I2t monitoring for the motor has been exceeded.
The frequency and amplitude of the DC link ripple indicates a single phase supply
failure.
Similar to F8
Internal coupling error. One of the two coupling partners does not respond
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
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
Motor overload (calculated): Motor current too high for too long a period.
ZR160VSD:
- Temperature limiting switch of motor is activated - open contact, ie, motor
overtemperature.
- Faulty temperature limiting switch.
- Loose connection at X101: 1 & 7
Could be one phase missing, where consumption on all 3 phases arevery different.
Fault in internal linking. One of the two linked partners does not reply.
- Loose / bad connection,
- Short circuit in one of the electronics board,
- Imbalance in supply line voltage
- IGBT / IGD1 faulty.
Higher level of F11
The frequency and amplitude of the DC link ripple indicates a single phase supply
failure.
Similar to F8
Dummy plug for the keypad not (properly) engaged, or PMU controller missing
- External fault 1 parameter is used for temperature sensor for the cabinet, and it
is parameterised t trigger when temp reaches 51 deg. C
Usually happen during hot weather / conditions
Internal coupling error. One of the two coupling partners does not respond
A fault has occur during the transfer of parameters to the gating unit processor
Line voltage too high, extreme generator operation, ramp down rate too fast.
CU: DC voltage was too low, ie 76% x line voltage x 1.34 was not reached
Most porbably due to a short circuit of the 12V supply for the digital inputs
Unrecoverable failures generated by the regulator.
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.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
Internal error
Unrecoverable failures generated by the regulator.
Internal error
Unrecoverable failures generated by the regulator.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
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.
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.
Electronmagnetic interference.
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.
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.
A Control Panel or Drives Window selected as active control location for the ACS
600 has ceased communicating.
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 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 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 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
Motor load is too low. This can be caused by a release mechanism in the driven
equipment
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
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.
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.
A Control panel selected as active control location for the ACS 600 has ceased
communicating.
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.
Motor is too hot, based on either the drives estimate or on temperature feedback.
Not used.
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.
MEAS Internal fault. Current measurement is out of range. Contact your local ABB
representative.
Motor speed is greater than 120% of the larger (in magnitude) of 2001
MINIMUM SPEED or 2002 MAXIMUM SPEED.
Not used.
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 code reserved for the embedded fieldbus (EFB) protocol application.
The meaning is protocol dependent.
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.
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.
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
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
(4210)
3.05 FW 1 bit 3
(8110)
3.06 FW 2 bit 10
(programmable
Fault Function
30.01)
(7113)
3.17 FW 5 bit 2
(7110)
3.17 FW 5 bit 0
(7111)
3.17 FW 5 bit 1
(FF82)
(7510)
3.06 FW 2 bit 12
(programmable
Fault Function
30.18)
4110)
3.06 FW 2 bit 7
(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
(7302)
(9000)
3.06 FW 2 bit 8
(programmable
Fault Function
30.03)
(FF83)
(5410)
03.17 FW 5 bit 9
Communication error on control board,
channel CH1
Electromagnetic interference
(7000)
3.06 FW 2 bit 6
(FF56)
3.06 FW 2 bit 15
(programmable
Fault Function
30.16)
(4312)
3.15 FW 4 bit 1
(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
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
(2340)
3.05 FW 1 bit 0 and
4.02
Two option modules have same connection
interface selection.
(FF8A)
(4311)
3.05 FW 1 bit 5
(programmable
Fault Function
30.04…30.05)
(FF6A)
3.05 FW 1 bit 8
(programmable
Fault Function
30.13…30.15)
(FFA1)
3.07 SFW bit 1
(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)
(4210)
3.05 FW 1 bit 3
(8110)
3.06 FW 2 bit 10
(programmable
Fault Function
30.01)
(FF80)
Pulse encoder phasing is wrong: Phase A is
connected to terminal of phase B and vice
versa.
(7302)
(7301)
3.06 FW 2 bit 5
(9000)
3.06 FW 2 bit 8
(programmable
Fault Function
30.03)
(7000)
3.06 FW 2 bit 6
(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)
(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
(FF52)
3.06 FW 2 bit 1
(2310)
3.05 FW 1 bit 1 and
4.01
Output current exceeds trip limit.
(2310)
3.05 FW 1 bit 1
(5120)
3.06 FW 2 bit 11
3.17 FW 5 bit 5
(2340)
3.05 FW 1 bit 0 and
4.02
(FF8A)
(3130)
3.06 FW 2 bit 0
(FF6A)
3.05 FW 1 bit 8
(programmable
Fault Function
30.13…30.15)
Incompatible firmware
interface
Note: This fault cannot be
reset.
Restoration of backed-up
parameters failed.
Cyclical communication
between drive and fieldbus
adapter module or between
PLC and fieldbus adapter
module is lost.
Error in temperature
measurement when
temperature sensor (KTY or
PTC) connected to encoder
interface FEN-xx is used.
Error in temperature
measurement when KTY
sensor connected to encoder
interface FEN-01 is used.
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.
Extension: 8 Short-ci
Communication errors
detected between the JCU
Control Unit and the power unit
of the drive.
Cyclical communication
between drive and fieldbus
adapter module or between
PLC and fieldbus adapter
module is lost.
Transmission of drive-to-drive
references failed because of
message buffer overflow.
No speed feedback is
received.
Current offset and again measuremtn calibration wil occur at next start
Output current has exceeded
internal fault limit.
Drive has detected load unbalance typically
due to earth fault in motor or motor cable.
Communication errors
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.
Error in temperature
measurement when
temperature sensor (KTY or
PTC) connected to encoder
interface FEN-xx is used.
Error in temperature
measurement when KTY
sensor connected to encoder
interface FEN-01 is used.
Cyclical communication
between drive and fieldbus
adapter module A or between
PLC and fieldbus adapter
module A is lost.
Cyclical communication
between drive and fieldbus
adapter module B or between
PLC and fieldbus adapter
module B 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.
Internal error.
Internal fault
Communication break in
embedded fieldbus (EFB)
communication.
Internal fault
Internal fault
Internal fault
Internal fault.
Encoder feedback fault.
Cyclical communication
between drive and fieldbus
adapter module B or between
PLC and fieldbus adapter
module B is lost.
Master/follower
communication is lost.
Chances are FET, and or diodes had gone. Possible what happen here is when the
connector is put upside down, and when 24V
Most probably due to a short circuit of the 12V supply for the digital inputs
Unrecoverable failures generated by the regulator.
G120
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.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
Internal error
Unrecoverable failures generated by the regulator.
Internal error
Unrecoverable failures generated by the regulator.
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.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
Motor overloaded
Reaction: OFF 2 (OFF 3)
Acknowledge: Quit fault eg. via DI2
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
Acknowledge: Quit fault eg. via DI2
Fault occurs if the sum of the phase currents is higher than 5 % of the nominal
inverter current.
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
This hardware fault caused by the following events:
• DC-link overcurrent = short circuit of IGBT
• Short circuit of chopper
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
Cause: Gate driver not enabled. Can be caused also by a synchronization error of
the safety state machines.
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
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: Quit fault eg. via DI2
Reaction: OFF 2 (OFF 3)
Acknowledge: Power on
Cause: Auto restart attempts exceed value of p1211.
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
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
Acknowledge: Quit fault eg. via DI2
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
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
Acknowledge: Quit fault eg. via DI2
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
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
Internal communications failure
• r0949 = 0: HW reported Link Fail
• r0949 = 1: SW reported Link Fail
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
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
Acknowledge: Quit fault eg. via DI2
File exists but the contents are not valid Control Word Corruption.
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
No Clone00.bin File in the correct directory /USER/SINAMICS/DATA.
• Broken wire
• Signal out of limits
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
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
Acknowledge: Quit fault eg. via DI2
Software Error
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
Software error or processor failure.
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
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
Acknowledge: Quit fault eg. via DI2
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
Acknowledge: Quit fault eg. via DI2
Reaction: OFF 2
Acknowledge: Quit fault eg. via DI2
• 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
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
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
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
Reaction: NONE
Acknowledge: NONE
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
Reaction: NONE
Acknowledge: NONE
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
Reaction: NONE
Acknowledge: NONE
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
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
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
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
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.
Overcurrent
Overload
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.
Alarm is active
Converter fault
Run Enable is open
Converter fault
Converter fault
Converter is in state “switch on inhibited”
- When upgrading from Mk III to Mk IV / V, the baud rate and address are not
correct.
- When rep
Converter fault
Wrong checksum
Frame Errors
Service Switch = 1
PKW length parameter is not 3
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 !
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
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
- 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
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
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)
Fan malfunction
Broken wire
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
- Motor power (P0307) does not correspond to the inverter power (P0206)
- Motor leads too long
- Earth fault
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
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
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.
Undervoltage detected
Undervoltage detected
hardware)
Internal communication timeout
Internal checksum error detected
Overvoltage detected
Overvoltage detected
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.
Alarm value (r2124, interpret decimal):
Component number of the DRIVE-CLiQ component involved.
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.
The inserted component has still not been initiated, as the pulses are
enabled.
A drive object number is missing in p0978
Alarm value (r2124, interpret decimal):
Index of p0101 under which the missing drive object number can be
determined.
In p0978, dummy drive object numbers (255) are only permitted in the first
partial list.
Alarm value (r2124, interpret decimal):
Index of p0978 under which the illegal value is located.
The topology comparison has detected a power unit in the actual topology
that has been shifted with respect to the
target topology.
Alarm value (r2124, interpret hexadecimal):
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.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex:
dd = connection number
cc = component number
bb = component cl
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.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex: aa = component number of the
The topology comparison has detected differences in the actual and target
topologies in relation to one component.
The component class, the component type or the number of connections
differ.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex: aa =
The topology comparison has detected differences in the actual and target
topologies in relation to one component.
The serial number is different.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex:
cc = number of differences
bb = component class
aa
The topology comparison has detected differences in the actual and target
topologies in relation to one component.
A component was connected to another connection.
The different connections of a component are described in the alarm value:
Alarm value (r21
The topology comparison has detected a power unit in the target topology
that is not available in the actual topology.
Alarm value (r2124, interpret decimal):
Component number of the additional target components.
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 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 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 unit did not accept the receive configuration data.
Alarm value (r2124, interpret decimal):
Return value of the receive configuration data check.
0: Configuration accepted.
1: Connection established to more drive objects than configured in the d
The current controller clock cycle of all drives must be set the same for the
clock cycle synchronous operation.
Alarm value (r2124, interpret decimal):
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.
Alarm value (r2124, interpret decimal):
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
The bus is in the data exchange state and clock synchronous operation has
been selected using the parameterizing
telegram. The global control telegram for synchronization is not being
received.
The bus is in the data exchange state and clock synchronous operation has
been selected using the parameterizing
telegram. The global control telegram for synchronization is being
irregularly received.
-.the master is sending an irregular global control t
The bus is in the data exchange state and clock synchronous operation has
been selected using the parameterizing
telegram. Synchronization with the master sign-of-life (STW2.12 ...
STW2.15) could not be completed because the
sign-of-life is changing diffe
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
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
The function generator has already been started.
The set operating mode (p1300) of the drive object is not permissible when
using the function generator.
Alarm value (r2124, interpret decimal):
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.
Alarm value (r2124, interpret decimal):
Number of the drive object involved.
The speed actual value of a drive selected for connection is greater than
the value for the standstill detection set
using p1226.
Alarm value (r2124, interpret decimal):
Number of the drive object involved.
Cause: The master control and/or enable signals are missing to connect to
the specified drive.
Alarm value (r2124, interpret decimal):
Number of the drive object involved.
See also: p4815 (Function generator drive number)
Magnetizing has not yet been completed on a drive object specified for
connection.
Alarm value (r2124, interpret decimal):
Number of the drive object involved.
See also: p4815 (Function generator drive number)
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:
The time slice clock cycle selected does not match any of the existing time
slices.
See also: p4830 (Function generator time slice cycle)
The time slice clock cycle selected does not match any of the existing time
slices.
See also: p4723 (Time slice cycle for trace)
The time slice clock cycle selected does not match any of the existing time
slices.
See also: p4723 (Time slice cycle for trace)
The selected time slice clock cycle cannot be used for the endless trace
See also: p4723 (Time slice cycle for trace)
The selected time slice clock cycle cannot be used for the setting p4702 = 1
(2 x 8 recording channels).
See also: p4723 (Time slice cycle for trace)
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.
See also: p4700, p4710, p4711, p4712, p4713, p4714, p4715, p4716,
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
The system wwas not able to load an OA application.
Alarm value (r2124, interpret hexadecimal):
Only for internal Siemens troubleshooting.
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.
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
F30035 is initiated.
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.
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.
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)
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 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
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
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
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
The configuration of the flux control (p1401) is contradictory.
Alarm value (r2124, interpret hexadecimal):
ccbbaaaa hex
aaaa = parameter
bb = index
cc = fault cause
cc = 01 hex = 1 dec:
Quick magnetizing (p1401.6) for soft start (p1401.0).
cc = 02 hex = 2 dec:
Quick magnetizing (p1401.6) for flux build-up control (p1401.2).
cc = 03 hex = 3 dec:
Quick magnetizing (p1401.6) for Rs identification after restart (p0621 = 2).
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
Theormaximum
p0189 = 99).
velocity (p2571) is too high to correctly calculate the modulo
correction.
Within the sampling time for positioning (p0115[5]), with the maximum
The current setpoint velocity is greater than the parameterized maximum
velocity (p2571) and is therefore limited.
In the traversing block the specified absolute target position lies outside
the range limited by the software limit switch
minus.
Alarm value (r2124, interpret decimal):
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.
Alarm value (r2124, interpret decimal):
Number of the traversing block with illegal target position.
In the traversing block the target position lies outside the modulo range.
Alarm value (r2124, interpret decimal):
Number of the traversing block with illegal target position.
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.
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.
The position actual value is set to the value received via CI: p2515while BI:
p2514 = 1 signal. A possible system
deviation cannot be corrected.
The selected drive data set changeover and the assigned motor changeover
are
Whennotcarrying
possibleout
anda are not setting
factory carried (e.g.
out. 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.
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
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
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
An encoder error was signaled for encoder 1 via the PROFIdrive encoder
interface (G1_ZSW.15).
Alarm value (r2124, interpret decimal):
An encoder error was signaled for encoder 2 via the PROFIdrive encoder
interface (G2_ZSW.15).
Alarm value (r2124, interpret decimal):
An encoder error was signaled for encoder 3 via the PROFIdrive encoder
interface (G3_ZSW.15).
Alarm value (r2124, interpret decimal):
During encoder identification (servicing) with p0400 = 10100, the encoder
could not beoperation
Encoderless identified.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)
The position actual value is set to the value received via CI: p2515while BI:
p2514 = 1 signal. A possible system
deviation cannot be corrected.
The position actual value is set to the value received via CI: p2515while BI:
p2514 = 1 signal. A possible system
deviation cannot be corrected.
The position actual value is set to the value received via CI: p2515while BI:
p2514 = 1 signal. A possible system
deviation cannot be corrected.
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).
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).
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).
The value range (-2147483648 ... 2147483647) for the position actual value
representation was exceeded.
When the overflow occurs, the "referenced" or "adjustment absolute
The value range (-2147483648 ... 2147483647) for the position actual value
representation was exceeded.
When the overflow occurs, the "referenced" or "adjustment absolute
The value range (-2147483648 ... 2147483647) for the position actual value
representation was exceeded.
When the overflow occurs, the "referenced" or "adjustment absolute
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.
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.
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.
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 absolute value of the speed difference from the two setpoints (p2151,
p2154) and thethe
When closing, speed actual feedback
contactor value (r2169)
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.
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 torque deviates from the torque/speed envelope characteristic in the
positive direction (too high).
The torque deviates from the torque/speed envelope characteristic in the
positive direction (too high).
The torque deviates from the torque/speed envelope characteristic.
The cyclic actual and/or setpoint values were not transferred within the
specified times.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.
The drive unit did not accept the receive configuration data.
Alarm value (r2124, interpret decimal):
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.
The memory or the buffer status of the non-cyclic channel has an error.
Alarm value (r2124, interpret decimal):
0: Error in the buffer status.
1: Error in the memory.
The memory or the buffer status of the message channel has an error.
Alarm value (r2124, interpret decimal):
0: Error in the buffer status.
1: Error in the memory.
The assignment of the hardware to the PZD interface has been incorrectly
parameterized.
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.
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)
The temperature difference between the heat sink and chip has exceeded
the permissible limit value.
- the permissible load duty cycle was not maintained.
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
Hardware is always
current output
limit for phaseif V
the hardware The
responded. current limitinfor
pulsing thisphase U,isV
phase
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
Hardware is always
current output
limit for phaseif W
theresponded.
hardware current limitin
The pulsing forthis
phase U, is
phase V
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
24 A30031
V power is always
supply fault output
for the if the hardware
power unit. current limit for phase U, V
- the 16 V threshold was undershot..
Fault value (r0949, interpret decimal):
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:
Fault value (r0949, interpret decimal):
0: The maximum fan operating time is 500 hours.
1: The maximum fan operating time has been exceeded.
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.
Fault value (r0949):
Register value of the voltage fault register.
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.
Alarm value (r2124, interpret decimal):
1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm, PT100: R >
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.
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
The 1.5 x parameterized zero mark distance was exceeded.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary
encoder) or p0424 (linear encoder).
Serial communication protocol transfer error between the encoder and
evaluation module.
Alarm value (r2124, interpret binary):
Bit 0: Alarm bit in the position protocol.
The error word of the EnDat encoder has alarm bits that have been set.
Alarm value (r2124,
The encoder sends ainterpret
set errorbinary):
bit via the serial protocol.
Alarm value (r2124, interpret binary):
Bit 0: Fault bit in the position protocol.
Bit 1: Alarm 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.
Alarm value (r2124, interpret hexadecimal):
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
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.
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
SMC10: Offset correction: +/-650 mV
Alarm value (r2124, interpret hexadecimal):
xxxx1: Minimum of the offset correction, track B
For the actual value sensing, an error was detected. As a result of this error,
it
Themust befor
error assumed thatisthe
track C/D actual
greater value
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
When monitoring responds
the zero pulse if, for aexample,
is passed, deviationHall sensors
in the are connected
incremental aswas
position
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
Fortimes
trackthe distance
A/B, pulses referred
have been to lost
the first
or toozero mark.
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 amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall
signals, is not within the tolerance bandwidth.
Alarm value (r2124, interpret hexadecimal):
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
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.
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
SMC10: Offset correction: +/-650 mV
Alarm value (r2124, interpret hexadecimal):
xxxx1: Minimum of the offset correction, track B
For the actual value sensing, an error was detected. As a result of this error,
it must be assumed that the actual value
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
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
For trackthe distance
A/B, pulses referred
have beento lost
the first zero
or too mark.
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 amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall
signals, is not within the tolerance bandwidth.
Alarm value (r2124, interpret hexadecimal):
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
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.
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
SMC10: Offset correction: +/-650 mV
Alarm value (r2124, interpret hexadecimal):
xxxx1: Minimum of the offset correction, track B
For the actual value sensing, an error was detected. As a result of this error,
it
Themust befor
error assumed thatisthe
track C/D actual
greater value
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
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.
Alarm value (r2124, interpret decimal):
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 3 is outside the
permissible tolerance.
Alarm value (r2124, interpret binary):
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 DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Bit x = 1: Effectivity test x unsuccessful.
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 value (r2124, interpret decimal):
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 temperature (r3666) measured using the Voltage Sensing Module
(VSM) has exceeded the threshold value
(p3667).
Alarm value (r2124, interpret decimal):
The hundred thousands and ten thousands position specifies the
component number of the VSM where the fault
occurred.
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.
Fault value (r0949, interpret binary):
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.
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.
The encoder pulse number entered does not match the permissible pulse
number from a hardware perspective.
Fault value (r0949, interpret decimal):
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 temperature in the module has exceeded the highest permissible limit.
A checksum error (CRC) occurred when the program memory on the DRIVE-
CLiQ Hub Module was read out.
Alarm value (r2124, interpret hexadecimal):
Difference between the checksum at POWER ON and the current
checksum.
The internal parameter data on the DRIVE-CLiQ Hub Module are incorrect.
Alarm value (r2124, interpret hexadecimal):
01: EEPROM access error.
02: Too many blocks in the EEPROM.
An alarm has occurred at the drive object at the DRIVE-CLiQ socket X100.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.
An alarm has occurred at the drive object at the DRIVE-CLiQ socket X101.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.
An alarm has occurred at the drive object at the DRIVE-CLiQ socket X102.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.
An alarm has occurred at the drive object at the DRIVE-CLiQ socket X103.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.
An alarm has occurred at the drive object at the DRIVE-CLiQ socket X104.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.
An alarm has occurred at the drive object at the DRIVE-CLiQ socket X105.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.
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)
The cooling liquid intake temperature has exceeded the specified alarm
threshold.
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.
Fault value (r0949, interpret decimal):
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:
- stop request from the higher-level control.
- subsequent response to the mes
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 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 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:
- stop request from the Control Unit.
- 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).
"Safe Operating Stop" (SOS) is activated after the parameterized timer has
expired.
Possible causes:
- stop request from the higher-level control.
- 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).
"Safe Operating Stop" (SOS) is activated after the parameterized timer has
expired.
Possible causes:
- stop request from the Control Unit.
- 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))
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. decimal)
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.
Fault Value (r0949, decimal):
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.
Fault Value (r0949, decimal):
Number of the first drive object with a different power module type.
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 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.
Fault value (r0949, decimal):
The fault value speficies the
The parameter for the basic clock cycle is set too short for the number of
connected drives.
Fault value (r0949, decimal):
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
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)
Fault value (r0949, decimal)
The fault value includes the particular data set
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.
Fault value (r0949, interpret hexadecimal):
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
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.
Fault value (r0949, interpret decimal):
Parameter number to which an interconnection should be made
(connector output).
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
The drive-based "Safety Integrated" function in the Control Unit (CU) has
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
The drive-based "Safety Integrated" function in the Control Unit (CU) has
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
The drive-based "Safety Integrated" function in the Control Unit (CU) has
detected a brake control error and initiated
a STOP A.
Fault value (r0949, interpret decimal):
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.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.
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.
Fault value (r0949, interpret decimal):
130: Safety parameters for the Motor Module not available.
When accessing the Safety Integrated parameters for the Motor Module
(MM) on the CompactFlash card, an error
has occurred.
Note:
This fault results in a STOP A that can be acknowledged.
Fault value (r0949, interpret decimal):
129: Safety parameters for th
The write request for one or several Safety Integrated parameters on the
Control Unit (CU) was rejected.
Note:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
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:
This fault does not result in a safety stop response.
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
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:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
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 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:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
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:
This fault does not result in a safety stop response.
There is not sufficient memory space in the NVRAM on the drive to save
parameters r9781 and r9782 (safety logbook).
Note:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
0: There is no physical NVRAM available
At this drive object, the connection to at least one Publisher for PROFIBUS
peer-to-peer data transfer in cyclic operation
has been aborted.
Alarm value (r2124, interpret binary):
Bit 0 = 1: Publisher with address in r2077[0], connection aborted.
...
Bit
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.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Too many functions have been configured on this Control Unit (e.g. too
many drives, function modules, data sets,
OA applications, blocks, etc).
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
When initializaing the Terminal Modules, the terminal of the Control Unit
or the Terminal Board 30, an internal software error has occurred.
Fault Value (r0949, decimal):
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.
Fault value (r0949, decimal)
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.
Fault value (r0949, interpret decimal):
Parameter in which the first different power unit code number was
detected.
The EEPROM versions of the Voltage Sensing Modules (VSM) do not match.
Fault value (r0949, interpret decimal):
Parameter in which the first different version number was detected.
The firmware versions of the Voltage Sensing Module (VSM) do not match.
Fault value (r0949, interpret decimal):
Parameter in which the first different version number was detected.
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.
The response parameterized in p0610 becomes active.
PTC:
The response threshold of 1650 Ohm was exceeded and the timer (p0606)
has expired.
The response parameterized in p0610 becomes active.
Possible causes:
- motor is overloaded.
- motor ambient temperature too high.
- wire breakage or sensor not connected.
Fault value (r0949, interpret decimal):
For SME selected (p0601 = 10), number of the sensor channel leading to
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.
See also: p0604 (Motor overtemperature alarm threshold), p0605 (Motor
overtemperature fault threshold), p0606
(Motor overtemperature timer), p0610 (Motor overtemperature response)
The ACX file (macro) to be executed was not able to be found in the
appropriate directory.
Fault value (r0949, interpret decimal):
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.
Fault value (r0949, interpret decimal):
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.
Fault value (r0949, interpret decimal):
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
The parameterized sampling times do not match the basic clock cycle.
Fault value (r0949, interpret decimal):
The fault value specifies the parameter involved.
See also: r0110, r0111, p0115
- 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)
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.
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 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.
The reference point coordinate received when adjusting the encoder via
connector input p2599 lies outside the half
of the encoder range and cannot be set as current axis position.
Fault value (r0949, interpret decimal):
Maximum permissible value for the reference point coordinate.
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].
Fault value (r0949, interpret decimal):
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 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.
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.
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.
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.
Alarm value (r2124, interpret decimal):
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.
Fault value (r0949, interpret decimal):
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.
Fault value (r0949, interpret decimal):
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)
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.
Alarm value (r2124, interpret decimal):
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.
Fault value (r0949, interpret decimal):
Drive data set to be re-commissioned.
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.
Alarm value (r2124, interpret hexadecimal):
xxxxyyyy:
xxxx: First DDS with assigned MDS, yyyy: Second DDS with assigned MDS
For rotary absolute encoders, the pulse number in p0408 must be to the
power of two.
Fault value (r0949, interpret decimal):
The fault value includes the encoder data set number involved.
The maximum encoder value times the factor to convert the absolute
position (r0483 and/or r2723) from increments
to length units (LU) has exceeed the value range (-2147483648 ...
2147483647) for displaying the position actual
value.
The maximum encoder value times the factor to convert the absolute
position (r0483 and/or r2723) from increments
to length units (LU) has exceeed the value range (-2147483648 ...
2147483647) for displaying the position actual
value.
The maximum encoder value times the factor to convert the absolute
position (r0483 and/or r2723) from increments
to length units (LU) has exceeed the value range (-2147483648 ...
2147483647) for displaying the position actual
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)
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.
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).
Fault value (r0949, interpret decimal):
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.
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)
When opening, the contactor feedback signal (p1235) did not issue the
signal "Open" (r1239.1 = 0) within the monitoring
time (p1236).
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.
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 code number of the current motor with DRIVE-CLiQ does not match
the saved number.
Fault value (r0949, interpret decimal):
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).
Fault value (r0949, interpret decimal):
Motor code of the motor with DRIVE-CLiQ
The conditions to record the friction characteristic are not fulfilled.
Fault value (r0949, interpret decimal):
0046: Missing enable signals (r0046).
1082: The highest speed value to be approached (p3829) is greater than
the maximum speed (p1082).
1084: The highest speed value to be approached (p3829) is greater than
the maximum speed (r1084, p1083, p1085).
1087: The highest speed value to be approached (p3829) is greater than
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.
Only for internal Siemens troubleshooting.
The set monitoring time expired while transferring process data via COMM
BOARD.
See also: p8840 (COMM BOARD monitoring time)
The temperature of the power unit heat sink has exceeded the permissible
limit value.
- insufficient cooling, fan failure.
- overload.
- ambient temperature too high.
- pulse frequency too high.
Fault value (r0949):
Temperature [1 bit = 0.01 °C].
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.
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
Chip temperature of the semiconductor 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.
Fault value (r0949):
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).
Fault value (r0949, interpret binary):
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.
- ambient temperature too high.
- insufficient cooling, fan failure.
Fault value (r0949, interpret decimal):
Temperature [1 bit = 0.01 °C].
The temperature in the module slot of the drive converter has exceeded
the permissible temperature limit.
- insufficient cooling, fan failure.
- overload.
- ambient temperature too high.
Fault value (r0949, interpret decimal):
Temperature [1 bit = 0.1 °C].
The temperature in the rectifier of the power unit has exceeded the
permissible temperature limit.
- insufficient cooling, fan failure.
- overload.
- ambient temperature too high.
- line supply phase failure.
Fault value (r0949, interpret decimal):
Temperature [1 bit = 0.01 °C].
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.
Fault value (r0949, interpret decimal):
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).
Fault value (r0949, interpret decimal):
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 Motor Module has detected a communications error with the higher-
level control or the TM54F to transfer the
safety-relevant information.
Note:
This fault results in a STOP A that can be acknowledged.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
An internal error in the Safety Integrated software on the Motor Module
has occurred.
Note:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.
When accessing the Safety Integrated parameters for the Motor Module
(MM) on the CompactFlash card, an error
has occurred.
Note:
This fault results in a STOP A that can be acknowledged.
Fault value (r0949, interpret decimal):
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:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
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:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
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:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret decimal):
0: Checksum error for SI parameters for motion monitoring.
1: Checksum error for SI parameters for component assignment.
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:
This message does not result in a safety stop response.
Fault value (r0949, interpret decimal):
Maximum permissible speed.
For the initialization within the power unit, an internal software error has
occurred.
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).
Fault value (r0949, interpret decimal):
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.
See also: p0491 (Motor encoder fault response ENCODER)
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.
Fault value (r0949, interpret hexadecimal):
xxxx hex:
xxxx = Signal level, track R (16 bits with sign).
The unipolar nominal signal level of the encoder must lie in the range 2500
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.
The signal level is not evaluated unless the following conditions are
satisfied:
- Sensor Module properties available (r0459.30 = 1, r0459.31 = 1).
- monitoring active (p0437.30 = 1, p0437.31 = 1).
See also: p0491 (Motor encoder fault response ENCODER)
Serial communication protocol transfer error between the encoder and
evaluation module.
Fault value (r0949, interpret binary):
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
Bit 8: Protocol is too long (e.
Bit 9: Receive buffer overflow.
Bit 10: Frame error when reading
Bit 11: Parity error.
Bit 12: Data line signal level
Bit 13: Data line incorrect.
The EnDat encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
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.
See also: p0491 (Motor encoder fault response ENCODER)
The encoder sends a set error bit via the serial protocol.
Fault value (r0949, interpret binary):
Bit 0: Fault bit in the position protocol.
The amplitude (root of A^2 + B^2) for encoder 1 exceeds the permissible
tolerance.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (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 of
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.
A signal level of 2900 mV peak value corresponds to the numerical value of
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.
See also: p0491 (Motor encoder fault response ENCODER)
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.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (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 < 176 mV (observe the frequency response of
the encoder) and > 955 mV.
A signal level of 500 mV peak value corresponds to the numerical value
5333 hex = 21299 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.
See also: p0491 (Motor encoder fault response ENCODER)
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.
See also: p0491 (Motor encoder fault response ENCODER)
For an HTL/TTL encoder, the speed difference has exceeded the value in
p0492 over several sampling cycles.
The change to the averaged speed actual value - if applicable - is monitored
in the current controller sampling time.
Encoder 1 is used as motor encoder and can be effective has fault response
to change over to encoderless operation.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
See also: p0491 (Motor encoder fault response ENCODER), p0492 (Square-
wave encoder, maximum speed difference
per sampling cycle)
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.
See also: p0491 (Motor encoder fault response ENCODER)
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.
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.
Fault value (r0949, interpret decimal):
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
corresponds to 1 °).
See also: p0491 (Motor encoder fault response ENCODER)
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.
Fault value (r0949, interpret hexadecimal):
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 °
See also: p0491 (Motor encoder fault response ENCODER)
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:
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.
Fault value (r0949, interpret decimal):
Deviation in quadrants (1 pulse = 4 quadrants).
See also: p0491 (Motor encoder fault response ENCODER)
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.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display)
Bit 1: F2 (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 27: Multiturn position 2 (--> 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)
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.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display)
Bit 1: F2 (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 27: Multiturn position 2 (--> 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)
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Only for internal SIEMENS use.
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Only for internal SIEMENS use.
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.
Alarm value (r2124, interpret decimal):
Measured board/module temperature in 0.1 °C.
The encoder with measuring gear no longer provides any valid signals.
A cycle requested from the Control Unit or RX/TX timing is not supported.
Alarm value (r2124, interpret decimal):
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.
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Bit 0: ALU watchdog has responded.
Bit 1: ALU has detected a sign-of-life error.
A DRIVE-CLiQ communication error has occurred from the Control Unit to
the encoder involved.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
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.
See also: p0491 (Motor encoder fault response ENCODER)
The amplitude of the reference track signal (track R) does not lie within the
tolerance bandwidth for encoder 2.
The fault can be initiated when the unipolar voltage range is exceeded or
the differential amplitude is initiated.
Fault value (r0949, interpret hexadecimal):
xxxx hex:
xxxx = Signal level, track R (16 bits with sign).
The unipolar nominal signal level of the encoder must lie in the range 2500
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.
The signal level is not evaluated unless the following conditions are
satisfied:
- Sensor Module properties available (r0459.30 = 1, r0459.31 = 1).
- monitoring active (p0437.30 = 1, p0437.31 = 1).
vSerial communication protocol transfer error between the encoder and
evaluation module.
Fault value (r0949, interpret binary):
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.
Bit 13: Data line incorrect.
The EnDat encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
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 encoder sends a set error bit via the serial protocol.
Fault value (r0949, interpret binary):
Bit 0: Fault bit in the position protocol.
The amplitude (root of A^2 + B^2) for encoder 2 exceeds the permissible
tolerance.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (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 of
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.
A signal level of 2900 mV peak value corresponds to the numerical value of
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 2
are not within the tolerance bandwidth.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (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 < 176 mV (observe the frequency response of
the encoder) and > 955 mV.
A signal level of 500 mV peak value corresponds to the numerical value
5333 hex = 21299 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.
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.
The change to the averaged speed actual value - if applicable - is monitored
in the current controller sampling time.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
See also: p0492 (Square-wave encoder, maximum speed difference per
sampling cycle)
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.
The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 2 exceeds the
permissible tolerance.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Angle
xxxx = Amplitude, i.e. root from A^2 + B^2 (16 bits without sign)
The nominal signal level of the encoder must lie in the range 375 mV to 600
mV (500 mV -25/+20 %).
The response threshold for (|A| + |B|) is > 1120 mV or the root of (A^2 +
B^2) > 955 mV.
A signal level of 500 mV peak value corresponds to the numerical value of
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:
The analog values of the amplitude error are not measured at the same
time with the hardware fault output by the
sensor module.
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.
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 A32429.
Fault value (r0949, interpret decimal):
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
corresponds to 1 °).
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.
Fault value (r0949, interpret hexadecimal):
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:
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.
Fault value (r0949, interpret decimal):
Deviation in quadrants (1 pulse = 4 quadrants).
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Only for internal SIEMENS use.
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Only for internal SIEMENS use.
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.
Alarm value (r2124, interpret decimal):
Measured board/module temperature in 0.1 °C.
The encoder with measuring gear no longer provides any valid signals.
The encoder serial number has changed. The change is only checked for
encoders with serial number (e.g. EnDat
encoders).
Cause:
The encoder was replaced.
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).
A cycle requested from the Control Unit or RX/TX timing is not supported.
Alarm value (r2124, interpret decimal):
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.
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Bit 0: ALU watchdog has responded.
Bit 1: ALU has detected a sign-of-life error.
A DRIVE-CLiQ communication error has occurred from the Control Unit to
the encoder involved.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
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 amplitude of the reference track signal (track R) does not lie within the
tolerance bandwidth for encoder 3.
The fault can be initiated when the unipolar voltage range is exceeded or
the differential amplitude is initiated.
Fault value (r0949, interpret hexadecimal):
xxxx hex:
xxxx = Signal level, track R (16 bits with sign).
The unipolar nominal signal level of the encoder must lie in the range 2500
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.
The signal level is not evaluated unless the following conditions are
satisfied:
- Sensor Module properties available (r0459.30 = 1, r0459.31 = 1).
- monitoring active (p0437.30 = 1, p0437.31 = 1).
Serial communication protocol transfer error between the encoder and
evaluation module.
Fault value (r0949, interpret binary):
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.
Bit 13: Data line incorrect.
The EnDat encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
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 encoder sends a set error bit via the serial protocol.
Fault value (r0949, interpret binary):
Bit 0: Fault bit in the position protocol.
The amplitude (root of A^2 + B^2) for encoder 3 exceeds the permissible
tolerance.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (16 bits with sign).
The amplitude of the rectified encoder signals A and B and the amplitude
from the roots of A^2 + B^2 for encoder 3
are not within the tolerance bandwidth.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (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 < 176 mV (observe the frequency response of
the encoder) and > 955 mV.
A signal level of 500 mV peak value corresponds to the numerical value
5333 hex = 21299 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.
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.
The change to the averaged speed actual value - if applicable - is monitored
in the current controller sampling time.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
See also: p0492 (Square-wave encoder, maximum speed difference per
sampling cycle)
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 3.
Fault value (r0949, interpret decimal):
1: Reference voltage error.
2: Internal undervoltage.
3: Internal overvoltage.
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.
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 A33429.
Fault value (r0949, interpret decimal):
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
corresponds to 1 °).
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.
Fault value (r0949, interpret hexadecimal):
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:
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.
Fault value (r0949, interpret decimal):
Deviation in quadrants (1 pulse = 4 quadrants).
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.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display)
Bit 1: F2 (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)
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Only for internal SIEMENS use.
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Only for internal SIEMENS use.
The encoder speed is too high during while initializing the sensor.
The encoder with measuring gear no longer provides any valid signals.
The encoder serial number has changed. The change is only checked for
encoders with serial number (e.g. EnDat
encoders).
Cause:
The encoder was replaced.
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).
A cycle requested from the Control Unit or RX/TX timing is not supported.
Alarm value (r2124, interpret decimal):
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.
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Fault value (r0949, interpret binary):
Bit 0: ALU watchdog has responded.
Bit 1: ALU has detected a sign-of-life error.
For the Voltage Sensing Module (VSM), a fault has occurred while
initializing.
A DRIVE-CLiQ communications error has occurred from the Control Unit to
the Voltage Sensing Module.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
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.
A DRIVE-CLiQ communications error has occurred from the Control Unit to
the Voltage Sensing Module. The nodes
do not send and receive in synchronism.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
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.
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.
Fault value (r0949, interpret hexadecimal):
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
motion monitoring functions.
Fault value (r0949, interpret binary):
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.
As fault response fail-safe input terminal signals are transferred to the
motion monitoring functions.
The Terminal Module 54F (TM54F) has identified an error in the data cross
check between the two control channels.
As fault response fail-safe input terminal signals are transferred to the
motion monitoring functions.
Fault value (r0949, interpret hexadecimal):
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
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.
IMMEDIATELY
A DRIVE-CLiQ communication error has occurred from the Terminal Module
to the encoder involved.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
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.
A fault has occurred at the drive object at the DRIVE-CLiQ socket X101.
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.
A fault has occurred at the drive object at the DRIVE-CLiQ socket X102.
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.
A fault has occurred at the drive object at the DRIVE-CLiQ socket X103.
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.
A fault has occurred at the drive object at the DRIVE-CLiQ socket X104.
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.
A fault has occurred at the drive object at the DRIVE-CLiQ socket X105.
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.
The configured transfer end time when transferring the cyclic actual values
was exceeded.
A DRIVE-CLiQ communications error has occurred from the Control Unit to
the controller extension involved.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex:
The sign-of-life bit in the receive telegram is not set.
A DRIVE-CLiQ communications error has occurred from the Control Unit to
the controller extension involved.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
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 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 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 "Safe Torque Off" (STO) function has been selected on the Control Unit
(CU) using the input terminal and is
active.
Note:
This message does not result in a safety stop response.
The "Safe Stop 1" (SS1) function has been selected on the Control Unit (CU)
and is active.
Note:
This message does not result in a safety stop response.
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:
This message does not result in a safety stop response.
The "Safe Stop 1" function (SS1) was selected on the Motor Module (MM)
and is active.
Note:
This message does not result in a safety stop response.
Most porbably due to a short circuit of the 12V supply for the digital inputs
Unrecoverable failures generated by the regulator.
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.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
These failures are used to signal some critical, but not disastrous situation. The
compressor can start after the failure reset.
Internal error
Unrecoverable failures generated by the regulator.
Internal error
Unrecoverable failures generated by the regulator.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
These failures are generated after the autoconfiguration start. They indicate that
one or more conditions, checked during the autoconfiguration phase, are not valid.
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
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
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
- interference fault
- component failure
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
Hardware is damaged
Hardware is damaged
Hardware is damaged
Hardware is damaged
- Hardware problem
- 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
- 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
- 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
- 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
- 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")
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)
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
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)
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 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.
Instability
Overhauling load
Zero fluid
Power component
Drive overheated
- 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
See F0022
- Converter is in "stopped mode" and cannot be started
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
The service switch is in the wrong position (is set in SERVICE MODE)
Converter problem
Output current is excessive. The software overcurrent trip limit is 3.5 * I 2hd
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
No idea
The ACS 600 / 800 internal temperature is excessive. The trip level of
inverter module temperature is 125 deg. C
- If ABB converter says "Supply Phase" but supply phase is ok, then
probably the rectifier circuit, ie NINP board is faulty
The service switch is in the wrong position (is set in SERVICE MODE)
The service switch is in the wrong position (is set in SERVICE MODE)
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
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
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
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
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
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
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
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.
- 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.
- When pre-charging, the minimum DC link voltage (P071 Line volts x 1.34) of 80%
has not been reached .
- 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.
During excitation of the induction motor, the current did not rise above 12.5% of
the setpoint magnetising current for no-load operation
Parameterized limit value of the I2t monitoring for the motor has been exceeded.
Internal coupling error. One of the two coupling partners does not respond
A fault has occur during the transfer of parameters to the gating unit processor
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
Motor overload (calculated): Motor current too high for too long a period.
ZR160VSD:
- Temperature limiting switch of motor is activated - open contact, ie, motor
overtemperature.
- Faulty temperature limiting switch.
- Loose connection at X101: 1 & 7
Could be one phase missing, where consumption on all 3 phases arevery different.
Fault in internal linking. One of the two linked partners does not reply.
- Loose / bad connection,
- Short circuit in one of the electronics board,
- Imbalance in supply line voltage
- IGBT / IGD1 faulty.
The frequency and amplitude of the DC link ripple indicates a single phase supply
failure.
Similar to F8
Dummy plug for the keypad not (properly) engaged, or PMU controller missing
- External fault 1 parameter is used for temperature sensor for the cabinet, and it
is parameterised t trigger when temp reaches 51 deg. C
Usually happen during hot weather / conditions
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
Internal coupling error. One of the two coupling partners does not respond
A fault has occur during the transfer of parameters to the gating unit processor
Line voltage too high, extreme generator operation, ramp down rate too fast.
CU: DC voltage was too low, ie 76% x line voltage x 1.34 was not reached
Electrical noise.
Communication problems.
Wrong master configuration/settings.
Incorrect configuration of the communication objects.
DD: Fault
Settings
Settings
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
- Power other
down thedigital inputs at connector 2x4, and at 2x6 as well.
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)
Replace Elektronikon Mk III if all else fails
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.
Replace Elektronikon
These failures are used to signal some critical, but not disastrous situation. The
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.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
Wifh power supply and contactors that switches the power supply.
Make sure that there is only ONE COM module for the VSD. Then restart
autoconfiguration.
- 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
Try to reprogram
Try to reprogram
- Switch machine OFF then back ON again. Allow a few mins for all power inside
electronics to dissipate.
- Reprogam the converter.
- 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
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:
- whether the cable to the corresponding digital input has been interrupted.
- parameter P588 Src No Ext Warn 2
- Remove the drive and perform visual inspection of IGD.
- IGD (and maybe PSU) may need replacement.
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
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 the standstill measurement can be executed withou any danger:
- Power up the converter.
- Pin 1 & 2: Use Vdc multimeter to check for 24 Vdc. If not, then the power supply card,
- Check for loose connections
- Try to reprogam the MKIII
- 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)
- 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
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
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 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 supply voltage
- 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
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
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
- Replace CU (A10)
- Check connection of the board and optional boards.
- Power unit down and up again
- Replace CU (A10)
Replace CU (A10)
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 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+
PMU / Simovis: Read-out fault from r949. The digit of the xth position specifies the valve,
which, when triggered, manifested the fault.
Supplementary
- Check motor Reading:
- One case in Switzerland, where the burned cables on RFI filters or bad contacts on the
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
- 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 shortcircuit.
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.)
- Check fan E1 is working, and in the correct direction
- Temperature sensor at -X30
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 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 supply voltage
- Check the proper connection at the line reactor (L1)
- Check if one of the coils of line reactor L1 is short circuit.
- 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 and make sure this plug is engage via dummy plug of the hand held controller
(PMU)
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.
- 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.
Wifh power supply and contactors that switches the power supply.
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
- Replace CU (A10)
- Check connection of the board and optional boards.
- Power unit down and up again
- 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
Check with FSP, or reprogram the module and make sure all necessary I/O are declared.
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
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 othe
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.
These failures are used to signal some critical, but not disastrous situation. The
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 par
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.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
- 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 c
Try to reprogram
Try to reprogram
- Switch machine OFF then back ON again. Allow a few mins for all power inside
electronics to dissipate.
.
- Check connections of converter / COM module
- Isolate converter from COM module, and use VSD simulation software to test whether
COM module or co
- Switch machine OFF then back ON again. Allow a few mins for all power inside
electronics to dissipate.
- Reprogam the converter.
- Switch machine OFF then back ON again. Allow a few mins for all power inside
electronics to dissipate.
- Reprogam the converter.
- 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
- 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
- Check motor
- Check motor cable
- Check there are no power factor correction capacitors or surge absorbers in the motor
cable.
- 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.
See the line side converter manual for the fault description
- Motor overload
- Seized element
- Check fault function parameters for further details
- Faulty bearings
- Check power supply TO motor. May be a phase is missing
- Make sure all the parameters in the group 99 START-UP DATA are correct, and c
- Check the connection from the inverter module Main Circuit Interface Board, NINT to
the PPCC Branch
- Check the connection from the inverter module Main Circuit Interface Board, NINT to
the PPCC Branch
- 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.
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
* 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.
Check for and correct:
Source and connection for analog input.
Parameter settings for AI2 FAULT LIMIT (3022) and 3001 AI<MIN FUNCTION
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).
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
Contact your local ABB representative and report the error number.
Faults that indicate conflicts in the parameter settings
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
- 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
- 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 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
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.
* 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
- 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.
Informative alarm
Check Fault Function parameters.
Check motor.
Check motor cable.
Check there are no power factor correction
capacitors or surge absorbers in motor cable.
Check motor.
Check motor cable.
Check there are no power factor correction
capacitors or surge absorbers in motor cable.
Informative alarm
Check Fault Function parameters.
Check motor.
Check motor cable.
Check that there are no power factor correction
or surge absorbers in motor cable.
* Please use REDUCED MOTOR ID RUN where possible, as element is still coupled to
motor.
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.
- By using your multimeter, perform diode check on the output (U,V, W) of the drive.
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
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]).
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
Check the s
Contact your local ABB representative.
Informative alarm.
Informative alarm.
Informative alarm.
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 the s
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:
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 thethe
Check module or the
auxiliary parameter
code. to solve the mismatch.
The code
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).
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
(see actions for each code below).
Check status of fieldbus communication.
See user documentation of fieldbus
interface.
Check settings of parameter groups 50
Fieldbus adapter (FBA), 51 FBA A
settings, 52 FBA A data in and 53 FBA A
data out.
Check status of fieldbus communication.
See user documentation of fieldbus
interface.
Check settings of parameter group 50
Fieldbus adapter (FBA).
Check cable connections.
Check if communication master is able to
communicate.
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
(see actions for each code below).
Check PC tool or control panel connection.
Check control panel connector.
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
1: 33.23 On-time 2 source
4: 33.53 Value counter 1 source
5: 33.63 Value counter 2 source.
Check the auxiliary code. Check the source of the warning corresponding to the code:
2: 33.33 Edge counter 1 source
3: 33.43 Edge counter 2 source.
Check the auxiliary code. Check the source of the warning corresponding to the code:
2: 33.33 Edge counter 1 source
3: 33.43 Edge counter 2 source.
Check the auxiliary code. Check the source of the warning corresponding to the code:
2: 33.33 Edge counter 1 source
3: 33.43 Edge counter 2 source.
Check the auxiliary code. Check the source of the warning corresponding to the code:
2: 33.33 Edge counter 1 source
3: 33.43 Edge counter 2 source.
Check the auxiliary code. Check the source of the warning corresponding to the code:
2: 33.33 Edge counter 1 source
3: 33.43 Edge counter 2 source.
Informative warning
Informative warning
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 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
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
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
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.
* The Enable/Reset terminal will not reset an O.Ld1 trip. Use the Stop/Reset key.
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 othe
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.
G120
Replace Elektronikon
These failures are used to signal some critical, but not disastrous situation. The
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 par
It is possible to clear this kind of failure through the reset function key of the system
failure display.
- ‘Watchdog’ error. Check for part number. If below 1900 0700 05, replace
with new version.
Try to power OFF and ON again. If cannot resolved, then try a new module.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
Wifh power supply and contactors that switches the power supply.
- 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 c
Try to reprogram
- Switch machine OFF then back ON again. Allow a few mins for all power inside
electronics to dissipate.
- Reprogam the converter.
- Switch machine OFF then back ON again. Allow a few mins for all power inside
electronics to dissipate.
- Reprogam the converter.
- Switch machine OFF then back ON again. Allow a few mins for all power inside
electronics to dissipate.
- Reprogam the converter.
Check with FSP, or reprogram the module and make sure all necessary I/O are declared.
Remedy:
Note: Framesizes D to F: this fault only occurs on inverters that have 3 current sensors.
• 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
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: Check and if necessary improve the monitoring time in the STARTER SW while
getting the command source.
Check USS master
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 steps and shock loads lie within specified limits.
Note: Higher inertia requires longer ramp times; otherwise, apply braking resistor.
• Reduce EMC.
• Perform a forced dynamisation
• Run self-test again (set bit 1 in p9601 and p9801 and enter the STO mode, then leave
the STO mode again).
• Check all PROFIsafe settings (including your higher level failsafe control system).
• Acknowledge PROFIsafe fault.
• 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: 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: 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 if the Run Enable contact on the converter is closed. Also check if the Elektronikon
closes this contact. (K09)
- The warning bit can be turned off again by the time the Elektronikon decides to do a
shutdown handling. So 16#F2F1 i
Check if the Run Enable contact on the converter is closed. Also check if the Elektronikon
closes this contact (K09).
Check if the Run Enable contact on the converter is closed. Also check if the Elektronikon
closes this contact (K09).
- 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
Check if the Run Enable contact on the converter is closed. Also check if the Elektronikon
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.
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
Remove the short circuit, apply the correct pin-out, make sure the CAN is still
operational
Correctly fit this connector
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
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 motor
Replaced fan
- Check data
- Change I/O
Check Data
Change IO board
Change inverter, if all else fail
- 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
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
If P601 = 0 or 1, check the following:
- 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
• Check for tripped fuses at the secondary of the transformer T1 in the electrical panel
• Check for tripped fuses at the secondary of the transformer T1 in the electrical panel
* Check for earth fault of motor. Usually this is the main cause of overvoltage.
* Check for earth fault of motor. Usually this is the main cause of overvoltage.
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
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)
None necessary.
This alarm automatically disappears after the firmware has been updated.
Clear alarm:
Set p9496 to 1 or 2
or
de-activate DO again
Pulse inhibit
Re fault cause = 1:
Replace all NX10 or NX15 by a CX32.
Re fault cause = 2:
Replace all CX32 by an NX10 or NX15.
- 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
- delete the DRIVE-CLiQ Hub Module 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 for interru
- delete the CX32 / NX 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 for interruption and co
- 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).
None necessary.
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:
SI: Safety Integrated
See also: p9705 (SI Motion: Test stop signal source)
None necessary.
Note:
CU: Control Unit
SI: Safety Integrated
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
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
- 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
Change the operating mode for this drive object to p1300 = 20 (encoderless
speed control) or p1300 = 21 (speed
control with encoder).
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
For all of the drives specified for connection, set the speed setpoints to 0.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
Set the relevant drives to zero speed before starting the function generator.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
Fetch the master control to the specified drive object and set all enable signals.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
Enter an existing time slice clock cycle. The existing time slices can be read out
via p7901.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: r7901 (Time slice cycle times)
Enter an existing time slice clock cycle. The existing time slices can be read out
via p7901.
See also: r7901 (Time slice cycle times)
Enter an existing time slice clock cycle. The existing time slices can be read out
via p7901.
See also: r7901 (Time slice cycle times)
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.
See also: r7901 (Time slice cycle times)
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.
See also: r7901 (Time slice cycle times)
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)
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).
See also: p0290 (Power unit overload response)
- 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.
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).
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).
- Shut down quick magnetizing (p1401.6 = 0).
Re fault cause = 3:
- Re-parameterize Rs identification (p0621 = 0, 1)
- Shut down quick magnetizing (p1401.6 = 0).
None necessary.
This alarm automatically disappears after the offset has been saved.
Check the drive data sets, encoder data sets and encoder assignment.
See also: p0187 (Encoder 1 encoder data set number), p0188 (Encoder 2
encoder data set number), p0189
(Encoder 3 encoder data set number), p0400 (Encoder type selection)
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.
Connect a 1 signal to the binector input "do not reject traversing task/reject
traversing task" (BI: p2641) and re-start
motion.
None necessary.
The alarm automatically disappears with BI: p2514 = 0 signal.
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.
Set the reference point coordinate less than the value from the supplementary
information.
Set the reference point coordinate less than the value from the supplementary
information.
Acknowledge the encoder error using the encoder control word (G1_STW.15 =
1).
Acknowledge the encoder error using the encoder control word (G2_STW.15 =
1).
Acknowledge the encoder error using the encoder control word (G3_STW.15 =
1).
- Check and, if necessary, connect the encoder and/or encoder cable.
-Acknowledge
Check and, ifthe
necessary,
encoderestablish thethe
error using DRIVE-CLiQ connection.
encoder control word (G3_STW.15 =
1).
Acknowledge the encoder error using the encoder control word (G3_STW.15 =
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 and, if necessary, connect the encoder and/or encoder cable.
-Correct
Check and, if necessary,
parameter p0141.establish the DRIVE-CLiQ connection.
None necessary.
The alarm automatically disappears with BI: p2514 = 0 signal.
None necessary.
The alarm automatically disappears with BI: p2514 = 0 signal.
None necessary.
The alarm automatically disappears with BI: p2514 = 0 signal.
To changeover the drive data set, initially, exit the "operation" mode.
To changeover the drive data set, initially, exit the "operation" mode.
To changeover the drive data set, initially, exit the "operation" mode.
Set the parameters for the load monitoring according to the applicable rules.
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)
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
None necessary.
The alarm automatically disappears after the motor data identification routine
has been successfully completed or
for the setting p1900 = 0.
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).
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
Select another PDO COB-ID.
Re alarm value = 0:
Additional
Compare the licenses are
license required
key (p9920)and thesewith
entered mustthe
belicense
activated
key(p9920, p9921).
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
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.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
. check the encoder type (encoder with equidistant zero marks).
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
. check the encoder type (encoder with equidistant zero marks).
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder.
Replace encoder.
- carry out a POWER ON (power off/on) for all components.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- check the Hall sensor box
Re alarm value = 3:
-- for a standard
track C or D notencoder with cable, if required, contact the manufacturer.
connected.
- correct the direction of rotation of the Hall sensor possibly connected as
equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- remove any dirt from the coding disk or strong magnetic fields.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check encoder limit frequency.
- adapt the parameter for the distance between zero marks (p0424, p0425).
- check that the encoder cables and shielding are routed in compliance with
EMC.
- check the plug connections and contacts.
Re causes 1, 2:
Carry out an automatic adjustment using the pole position identification routine.
First, accept the serial number with
- replace the Sensor Module.
- if required, upgrade the firmware in the Sensor Module.
- contact the Hotline.
- 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).
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
. check the encoder type (encoder with equidistant zero marks).
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
. check the encoder type (encoder with equidistant zero marks).
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder.
Replace encoder.
- carry out a POWER ON (power off/on) for all components.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- check the Hall sensor box
Re alarm value = 3:
- for a standard encoder with cable, if required, contact the manufacturer.
- track C or D not connected.
- correct the direction of rotation of the Hall sensor possibly connected as
equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- remove any dirt from the coding disk or strong magnetic fields.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check encoder limit frequency.
- adapt the parameter for the distance between zero marks (p0424, p0425).
- check that the encoder cables and shielding are routed in compliance with
EMC.
- check the plug connections and contacts.
- 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).
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
. check the encoder type (encoder with equidistant zero marks).
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
. check the encoder type (encoder with equidistant zero marks).
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder.
Replace encoder.
- carry out a POWER ON (power off/on) for all components.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- check the Hall sensor box
Re alarm value = 3:
-- for a standard
track C or D notencoder with cable, if required, contact the manufacturer.
connected.
- correct the direction of rotation of the Hall sensor possibly connected as
equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- remove any dirt from the coding disk or strong magnetic fields.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check encoder limit frequency.
- adapt the parameter for the distance between zero marks (p0424, p0425).
- 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.
- 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).
Error, timeout in the sequence control on the Voltage Sensing Module (VSM).
- check whether the firmware version of the VSM (r0158) matches the firmware
version of Control Unit (r0018).
- if required, replace the Voltage Sensing Module.
- check that the sensor is connected correctly.
-replace sensor.
- check whether the firmware version of the Terminal Module (r0158) matches
the firmware version of Control Unit
(r0018).
Check the terminals for the power supply voltage (L1+, L2+, L3+, M).
NONE
- Replace the firmware on the DRIVE-CLiQ Hub Module with older firmware
(r0158).
- upgrade the firmware on the Control Unit (r0018).
- check the wiring between the cooling system and the input terminal (Terminal
Module).
- check the external control device for the cooling system.
- check the wiring between the cooling system and the Power Stack Adapter
(PSA).
- check the function of the sensor to measure the conductivity.
- remove the fault cause in the control and carry out a POWER ON.
- carry out a diagnostics routine for message C01714.
- carry out a diagnostics routine for message C01711.
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
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).
This message can be acknowledged as follows:
- motion monitoring functions integrated in the drive: Via Terminal Modul
None necessary.
The message is withdrawn when the test stop is finished.
Note:
SI: Safety Integrated
None necessary.
The message is withdrawn when exiting the acceptance test mode.
Note:
SI: Safety Integrated
- remove the fault cause in the control and carry out a POWER ON.
- carry out a diagnostics routine for message C01714.
- carry out a diagnostics routine for message C01711.
This message can only be acknowledged in the acceptance test mode without
POWER ON via the Terminal Module
54F (TM54F) or PROFIsafe.
Note:
SI: Safety Integrated
Check the braking behavior, if required, adapt the tolerance for "Safe
Acceleration Monitor".
This message can only be acknowledged in the acceptance test mode without
POWER ON via the Terminal Module
54F (TM54F) or PROFIsafe.
Note:
- 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
removeoutthe
a POWER
cause ofON.
the fault at the control.
- carry out a diagnostics routine for message C30714.
This message can only be acknowledged via the Terminal Module 54F (TM54F)
or PROFIsafe.
Note:
SI: Safety Integrated
SOS: Safe Operating Stop / SBH: Safe operating stop
- remove the cause of the fault at the control.
- carry out a diagnostics routine for message C30714.
This message can only be acknowledged via the Terminal Module 54F (TM54F)
or PROFIsafe.
Note:
SI: Safety Integrated
SOS: Safe Operating Stop / SBH: Safe operating stop
None necessary.
The message is withdrawn when exiting the acceptance test mode.
Note:
SI: Safety Integrated
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.
Only power modules of one particular drive type may be operated with one CU
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
Enter the missing component number or remove the component and restart
commissioning.
See also, P0121, P0131, P0141, P0142, P0151, P0161, P0186, P0187, P0188,
P0189
Read out the fault value and remove one of the specified connections.
Then download the target topology again using the commissioning software.
Note:
Under "Topology --> Topology view" the commissioning software offers
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:
Under "Topology --> Topology view" the commissioning software offers
improved diagnostics capability
Establish another interconnection.
- 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
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
SI: Safety Integrated
STO: Safe Torque Off / SH: Safe standstill
- 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
SI: Safety Integrated
STO: Safe Torque Off
- set p9700 = 0.
- check p9501and p9601 and correct if necessary.
- start the copy function again by entering the appropriate value in p9700.
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:
SI: Safety Integrated
- 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:
SI: Safety Integrated
Enable the function "SOS/SLS" (p9501.0) and carry out a POWER ON.
Note:
SI: Safety Integrated
SLS: Safely-Limited Speed / SG: Safely reduced speed
SOS: Safe Operating Stop / SBH: Safe operating stop
See also: p9501 (SI Motion enable safety functions (Cont
Correct the limit values in p9534 and p9535 and carry out a POWER ON.
Note:
SI: Safety Integrated
SLP: Safely-Limited Position / SE: Safe software limit switches
Correct the limit values for SLS and carry out a POWER ON.
Note:
SI: Safety Integrated
SLS: Safely-Limited Speed / SG: Safely reduced speed
See also: p9531 (SI Motion SLS (SG) limit values (Control Unit))
Correct the cam position and carry out a POWER ON.
Note:
SCA: Safe Cam / SN: Safe software cam
SI: Safety Integrated
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:
SCA: Safe Cam / SN: Safe software cam
SI: Safety Integrated
See also: p9505 (SI Motion SCA (SN) modulo value (Control Unit))
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.
- contact the Hotline.
Re 1.
- restore the factory setting.
- carry out the first commissioning.
Re 2.
- download the SMI data from the back-up (p4690, p4691).
- carry out a POWER ON (power off/on) for all components.
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
- 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:
OA: Open Architecture
- Power down the power supply for the Control Unit and power up again.
- Check the DRIVE-CLiQ connection
- 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
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.
- 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
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 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)
- 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
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)
Set the reference point coordinate to a lower value than specified in the fault
value.
Check the traversing block and where relevant, take into consideration alarms
that are present.
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.
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
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
- check the encoder parameterization (p0400, p0404).
- use the matching encoder evaluation (r0456).
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:
1. Motor encoder without position tracking:
p2506 * p0433 * p2505 / (p0432 * p2504)
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:
1. Motor encoder without position tracking:
p2506 * p0433 * p2505 / (p0432 * p2504)
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:
1. Motor encoder without position tracking:
p2506 * p0433 * p2505 / (p0432 * p2504)
- 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.
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
- switch out (disable)(booksize,
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).
- increase the monitoring time (p0857).
- 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
Eliminatefails.
the causes of this fault.
Compare the motor data with the rating plate data and if required, correct.
See also: p0300, p0301, p0304, p0305, p0307, p0310, p0311, p0314, p0316,
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. with DRIVE-CLiQ and the matching motor code.
Use a motor
The first three digits of the motor code generally correspond to the matching list
motor type.
Fulfill the conditions to record the friction characteristic.
Re fault value = 0046:
Establish missing enable signals.
Re fault value = 0840:
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).
Re fault value = 1110:
Select the friction characteristic record, positive direction (p3845).
Re fault value = 1111:
Select the friction characteristic record, negative direction (p3845).
Re fault value = 1198:
Enable the permitted direction (p1110, p1111, r1198).
Re fault value = 1300:
Set the control mode (p1300) on the closed-loop speed control (p1300 = 20, 21).
Re fault value = 1755:
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).
Re fault value = 1910:
Exit the motor data identification routine (p1910).
Re fault value = 1:
Check whether the motor is correctly connected.
Check whether motor data have been correctly entered.
Replace the Motor Module involved.
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 motor is correctly connected.
Check whether the encoder pulse number (p0408) and gearbox factor (p0432,
p0433) are correct.
Check whether the motor pole pair number is correct (p0314).
Re fault value = 10:
Increase the value for p0325.
Check whether the motor is correctly connected.
Replace the Motor Module involved.
Re fault value = 11:
Increase the value for p0329.
Check whether the motor is correctly connected.
Replace the Motor
Re fault value = 1: Module involved.
- 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:
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.
Re fault value = 1 ... 2:
- increase the measuring speed (p1961) and repeat the measurement.
Re fault value = 1 ... 4:
- 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.
- carry out a motor data identification routine (p1910).
- if required, reduce the dynamic factor (p1967 < 25 %).
Re fault value = 5:
- the speed setpoint (p1961) is too high. Reduce the speed.
Re fault value = 1:
- 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.
- carry out a motor data identification routine (p1910).
- if required, reduce the dynamic factor (p1967 < 25 %).
Re fault value = 2, 5:
- adapt the speed setpoint (p1965) or adapt the minimum limit (p1080).
Re fault value = 3, 6:
- adapt the speed setpoint (p1965) or suppression (skip) bandwidths (p1091 ...
p1094, p1101).
Re fault value = 4, 7:
- adapt the speed setpoint (p1965) or maximum limit (p1082, p1083 and p1086).
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)
Re fault value = 10:
- check the moment of inertia (p0341, p0342). After the change: Calculate p0340
= 3.
Note:
The moment of inertia identification routine can be disabled using p1959.2.
See also: p1959 (Rotating measurement configuration)
Re fault value = 1:
- 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.
- 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:
Re fault value = 1:
Enable the direction (p1110 or p1111).
Select at least one function for automatic optimization of the speed controller
(p1959).
See also: p1959 (Rotating measurement configuration)
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:
- 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 = 0:
- check whether the motor is correctly connected. Observe configuration
(star/delta).
Re fault value = 1 ... 40:
- 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.
Re fault value = 4, 7:
- check whether inductances are correctly entered in p0233 and p0353.
- check whether motor was correctly connected (star/delta).
Re fault value = 50:
- reduce the current controller sampling rate.
Re fault value = 101:
- 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).
None necessary.
Acknowledge the fault and continue operation.
- check the motor data - if required, carry out commissioning.
- check the motor circuit configuration (star-delta).
- 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.
- check the power cable connections.
- check the power cables for short-circuit or ground fault.
- check the length of the power cables.
- 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).
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.
- check the electrical cabinet design and cable routing for EMC compliance
- 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)
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.
See also: p0210 (Drive unit line supply voltage)
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:
The following applies for CU31x and CUA31:
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.
Correct the limit values for SLS and carry out a POWER ON.
Note:
SI: Safety Integrated
SLS: Safely-Limited Speed / SG: Safely reduced speed
See also: p9331 (SI Motion SLS limit values (Motor Module))
- when replacing cables, only use cables with the same length as the original
cables.
- when replacing components, use the same components and firmware releases.
- carry out a POWER ON.
- replace the firmware on the power unit by an older firmware version (r0128).
- upgrade the firmware on the Control Unit (r0018).C456
- 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 (p0425).
- if message output above speed threshold, reduce filter time if necessary
(p0438).
- when p0437.1 is active, check p4686.
- replace the encoder or encoder cable.
- check that the encoder cables and shielding are routed in compliance with
EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- 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)
- check that the encoder cables and shielding are routed in compliance with
EMC.
- replace the encoder or encoder cable.
- check that the encoder cables and shielding are routed in compliance with
EMC.
- replace the encoder or encoder cable.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check whether the coding disk is dirty or there are strong ambient magnetic
fields.
- adapt the parameter for the distance between zero marks (p0425).
- if message output above speed threshold, reduce filter time if necessary
(p0438).
Replace DRIVE-CLiQ encoder.
Replace DRIVE-CLiQ encoder.
Replace encoder
Replace encoder
It must be ensured that all of the encoders, with mounted measuring gear,
provide valid actual values in operation.
The fault should be resolved as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- check the electrical cabinet design and cable routing for EMC compliance
- replace the component involved.
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Reduce the current controller frequency.
Replace encoder
- carry out a POWER ON.
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
- when replacing cables, only use cables with the same length as the original
cables.
- when replacing components, use the same components and firmware releases.
- carry out a POWER ON.
- check whether the connected encoder type matches the encoder that has been
parameterized.
- correct the parameter specified by the fault value (r0949) and p0187.
- 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).
- if message output above speed threshold, reduce filter time if necessary
(p0438).
- replace the encoder or encoder cable.
- 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 (p0425).
- if message output above speed threshold, reduce filter time if necessary
(p0438).
- when p0437.1 is active, check p4686.
- replace the encoder or encoder cable.
- check that the encoder cables and shielding are routed in compliance with
EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- make sure that the encoder cables and shielding are installed in an EMC-
compliant manner.
- check the plug connections and contacts.
- check the short-circuit of a signal cable with mass or the operating voltage.
- replace the encoder cable.
- check that the encoder cables and shielding are routed in compliance with
EMC.
- replace the encoder or encoder cable.
- check that the encoder cables and shielding are routed in compliance with
EMC.
- replace the encoder or encoder cable.
- track C or D not connected.
- correct the direction of rotation of the Hall sensor possibly connected as
equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- 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.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check whether the coding disk is dirty or there are strong ambient magnetic
fields.
- adapt the parameter for the distance between zero marks (p0425).
- if message output above speed threshold, reduce filter time if necessary
(p0438).
Replace encoder
Replace encoder
It must be ensured that all of the encoders, with mounted measuring gear,
provide valid actual values in operation.
The fault should be resolved as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- check the electrical cabinet design and cable routing for EMC compliance
- replace the component involved.
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Mechanically adjust the encoder. Accept the new serial number with p0440 = 1.
Replace encoder
- carry out a POWER ON.
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
- when replacing cables, only use cables with the same length as the original
cables.
- when replacing components, use the same components and firmware releases.
- carry out a POWER ON.
- check whether the connected encoder type matches the encoder that has been
parameterized.
- correct the parameter specified by the fault value (r0949) and p0187.
- 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).
- if message output above speed threshold, reduce filter time if necessary
(p0438).
- replace the encoder or encoder cable.
- 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 (p0425).
- if message output above speed threshold, reduce filter time if necessary
(p0438).
- when p0437.1 is active, check p4686.
- replace the encoder or encoder cable.
- check that the encoder cables and shielding are routed in compliance with
EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- check that the encoder cables and shielding are routed in compliance with
EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- make sure that the encoder cables and shielding are installed in an EMC-
compliant manner.
- check the plug connections and contacts.
- check the short-circuit of a signal cable with mass or the operating voltage.
- replace the encoder cable.
- check that the encoder cables and shielding are routed in compliance with
EMC.
- replace the encoder or encoder cable.
- check that the encoder cables and shielding are routed in compliance with
EMC.
- replace the encoder or encoder cable.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check whether the coding disk is dirty or there are strong ambient magnetic
fields.
- adapt the parameter for the distance between zero marks (p0425).
- if message output above speed threshold, reduce filter time if necessary
(p0438).
Replace DRIVE-CLiQ encoder.
Replace encoder
Replace encoder
Reduce the ambient temperature for the DRIVE-CLiQ connection of the motor.
It must be ensured that all of the encoders, with mounted measuring gear,
provide valid actual values in operation.
The fault should be resolved as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- check the electrical cabinet design and cable routing for EMC compliance
- replace the component involved.
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Mechanically adjust the encoder. Accept the new serial number with p0440 = 1.
Replace encoder
- when replacing cables, only use cables with the same length as the original
cables.
- when replacing components, use the same components and firmware releases.
- carry out a POWER ON.
'- replace the firmware on the Sensor Module by an older firmware version
(r0148).
- upgrade the firmware on the Control Unit (r0018).
- 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).
- check whether the connected encoder type matches the encoder that has been
parameterized.
- correct the parameter specified by the fault value (r0949) and p0187.
- when replacing cables, only use cables with the same length as the original
cables.
- when replacing components, use the same components and firmware releases.
- carry out a POWER ON.
Adapt the sampling time (e.g. set the recommended valid sampling time).
See also: p10000 (SI sampling time)
- check the electrical cabinet design and cable routing for EMC compliance
- upgrade the software on the TM54F.
- contact the Hotline.
- replace the TM54F.
- when replacing cables, only use cables with the same length as the original
cables.
- when replacing components, use the same components and firmware releases.
- carry out a POWER ON.
- when replacing cables, only use cables with the same length as the original
cables.
- when replacing components, use the same components and firmware releases.
- carry out a POWER ON.
- 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.
- check the wiring between the cooling system and the input terminal (Terminal
Module).
- check the external control device for the cooling system.
See also: p0266 (Cooling system, feedback signals, signal source)
- check the wiring between the cooling system and the input terminal (Terminal
Module).
- check the external control device for the cooling system.
- check the wiring between the cooling system and the input terminal (Terminal
Module).
- check the external control device for the cooling system.
- check the cooling system for leaks in the cooling circuit.
- check the wiring of the input terminal (terminal Module) used to monitor
leaking fluid.
None necessary.
Note:
CU: Control Unit
SI: Safety Integrated
STO: Safe Torque Off / SH: Safe standstill
None necessary.
Note:
CU: Control Unit
SI: Safety Integrated
SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)
None necessary. The alarm automatically disappears when the limit value is
undershot.
See also: p0290 (Power unit overload response)
None necessary.
Note:
MM: Motor Module
SI: Safety Integrated
STO: Safe Torque Off / SH: Safe standstill
None necessary.
Note:
MM: Motor Module
SI: Safety Integrated
SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)
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
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 mod
These failures are used to signal some critical, but not disastrous situation. The
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.
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.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
It is possible to clear this kind of failure through the reset function key of the system
failure display.
Check Motor
Decrease motor loading
Check motor loading
No actions necessary. Take a critical attitude to these values
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.
Check with FSP, or reprogram the module and make sure all necessary I/O are declared.
• 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 drive. Contact
Yaskawa or a Yaskawa
representative for instructions on replacing the control board.
• 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 drive. Contact
Yaskawa or a Yaskawa
representative for instructions on replacing the control board.
• 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
• 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 drive. Contact
Yaskawa or a Yaskawa
representative for instructions on replacing the control board.
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.
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.
- 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.
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- • Check for faulty wiring or poor connections on the output side of the drive.
• Correct the wiring.
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
- 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.
- 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.
- 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
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 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).
• Adjust the preset V/f pattern (E1-04 through E1-10) by reducing E1-08 and E1-10.
•D
• 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
• Check for wiring errors in the main circuit drive input power.
• Correct the wiring.
• 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
- 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.
• 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.
• 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 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.
• Correct the wiring.
• 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 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.
• Check the internal connections.
• Contact Schneider Electric Product Support.
• Contact Schneider Electric Product Support to have the drive recalibrated.
• Check the cables connecting the drive to the motor, and the insulation of the
motor
• Perform the diagnostic tests via the [1.10 DIAGNOSTICS] menu.
• Reduce the switching frequency.
• Connect chokes in series with the motor.
• Check the cables connecting the drive to the motor, and the insulation of the
motor
• Perform the diagnostic tests via the [1.10 DIAGNOSTICS] menu.
• Reduce the switching frequency.
• Connect chokes in series with the motor.
Check the motor load, the drive ventilation, and the ambient temperature. Wait
for the controller to cool down before restarting.
• Check the PTC probes and the wiring between them and the motor/controller.
• Check the PTC probes and the wiring between them and the motor/controller.
• Check the PTC probes and the wiring between them and the motor/controller.
• Check the cables connecting the controller to the motor, and the motor
insulation.
• Perform a test via the [1.10 DIAGNOSTICS] menu.
• Contact Schneider Electric Product Support.
• 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.
• Contact Schneider Electric Product Support.
- 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
- The service switch is in the wrong position (is set in service mode)
- Set the service switch back to normal position
- Run converter manually with service switch on, to see whether it is the drive or
the elektronikon
- See F0022
- Run converter manually with service switch on, to see whether it is the drive or
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)
Change the following parameters on the Masterdrive by using the PMU or Drive
Monitor.
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,
* 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
* The service switch is in the wrong position (is set in service mode)
* Set the service switch back to normal position
* Check the frequency converter panel for fault messages and go to the relevant
VSD drive fault search list for further information.
- Check the motor and motor cable
- Check there are no power factor correction capacitors or surge absorbers in the
motor cable.
Contact ABB
No idea
A PC and RS485 <-> RS232 converter box is required as well as the DFM4win
- 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
Check the frequency converter panel for fault messages and go to the relevant
VSD drive fault search list for further information.
Contact ABB
No idea
- 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
frequency 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 th
- 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,
- The service switch is in the wrong position (is set in service mode)
- Set the service switch back to normal position
- Run converter manually with service switch on, to see whether it is the drive or
the elektronikon
- Check the fault message on the Siemens PMU (operator panel) and
- The service switch is in the wrong position (is set in service mode)
- Set the service switch back to normal position
- The service switch is in the wrong position (is set in service mode)
- Set the service switch back to normal position
The expansion module giving the problem can be found in the "EXTRA" display,
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
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 the standstill measurement can be executed withou any danger:
- Power up the converter.
- Check voltage C and D. Should get high 500V's (dc). While having the multimeter on it,
- Check supply voltage or DC voltage
- Converter is working at upper tolerance limit and at full load.
- Can be caused by line phase failure
- 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-
- 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)
- 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
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
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 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 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 supply voltage
- 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
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
CUVC - Increase P357 samping time, Calculate individual blocks in a slower sampling
time, observe r829 CalcTimeHdroom
- Replace CU (A10)
- Check connection of the board and optional boards.
- Power unit down and up again
- Replace CU (A10)
Replace CU (A10)
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 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.
- One case in Switzerland, where the burned cables on RFI filters or bad contacts on the
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
- 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 shortcircuit.
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.)
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.
Switch off the unit and switch it on again. If the fault re-occurs, replace the Cuxx
- 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 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 supply voltage
- Check the proper connection at the line reactor (L1)
- Check if one of the coils of line reactor L1 is short circuit.
- 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 and make sure this plug is engage via dummy plug of the hand held controller
(PMU)
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.
- 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 onand
Wifh power supply pinscontactors
3 - 4 on the micromaster.
that switches the power supply.
CUVC - Increase P357 samping time, Calculate individual blocks in a slower sampling
time, observe r829 CalcTimeHdroom
- Replace CU (A10)
- Check connection of the board and optional boards.
- Power unit down and up again
- 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
**** 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
Please perform DIODE checks with respect to the DC Link terminals. Please see
VSD notes for more information on how to perform this task
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 for IBGT failures. May use DIODE checks on output of convertors to
motor.
***Check for IBGT failures. May use DIODE checks on output of convertors to
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 cooling fan, exhausts, and inlet filters (if any) to cabinet
***Check for IBGT failures. May use DIODE checks on output of convertors to
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
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
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. Decrease P0180
2. Check P0410
1. Decrease P0180