VSD/Elektronikon Model Fault Control Type / Series Meaning Cause Counter measure

MKIII and Siemens MasterDrive "Blank Screen" All Mk III Elektronikons No power to display of Elektronikon Faulty Board, loose connections (ribbon cables) inside. Check the module for loose connection.

If no loose connection is found, chances are the diode that controls the power supply to
the display is gone. It is not recommended to repair them, because whilst repairing,
there is a chance of disturbing neighbour ICs, hence System 200 fault would come up
after power is back on.
(For those elektronikons enthusiasts, the part is a BYW 98 - 400 )

MKIII and Siemens MasterDrive 0 All Siemens VSD. Programmed stop Elektronikon try again and again to start, but system keeps on re-starting and In Masterdrive series, it is possible that the parameter P373 index 001 is set to 1, hence
This is not really a fault. PROGRAMMED STOP is present repeatedly the system is always re-starting. This come about, if there is only a "brief" failure, but
system has not got enough time to register a fault.

Hence, solution is set parameter P373 index 001 to 0 and try again. This will prompt a
fault in the converter, whatever it may be, eg. F008.
Please note that if the Compressor has ARAVF programmed, then it is necessary to have
parameter P373 index 001 back to 1 when finished with fault finding.

MKIII and Siemens MasterDrive 10 Elektronikon Mk III LRR V1.8, Relay outputs read-back error Relay damaged, internal error - Power down the regulator.
2.3 - Inconsistency between the status of the relays and Unrecoverable failures generated by the regulator. - Check the Emergency stop button.
HRR the status the relays should be in - Compressor is running or standing still. Regulator is powered up. Only one * Make sure all wires connected firmly and no bad contacts are existing.
contact (out of three) of the Emergency stop button is activated. This means that * All the components of the Emergency stop button (base and contacts) should have
the power suppl the same colour (black or brown)
* A mixture of colours could cause this problem to exist.
Check the wiring from the Emergency stop button to the regulator.
- Power up the regulator again.

Replace Elektronikon Mk III if all else fails

MKIII and Siemens MasterDrive 100 Elektronikon Mk III LRR V1.8, Register file error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III if all else fails
2.3
MKIII and Siemens MasterDrive 101 Elektronikon Mk III LRR V1.8, RAM error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III if all else fails
2.3
MKIII and Siemens MasterDrive 102 Elektronikon Mk III LRR V1.8, 12V relay not disabled at power on Relay possibly damaged due to incorrect power input Replace Elektronikon Mk III if all else fails
2.3
MKIII and Siemens MasterDrive 103 Elektronikon Mk III LRR V1.8, Relays status uncorrect at power on Relay possibly damaged due to incorrect power input Replace Elektronion, if all else fails
2.3 Unrecoverable failures generated by the regulator.
MKIII and Siemens MasterDrive 104 Elektronikon Mk III LRR V1.8, Short circuit on 12V (relays and digital inputs) OR In Most cases, attributed to a voltage coming in through one of the digital inputs. These failures are used to signal some dangerous situation caused by hardware or
2.3, HRR 12V enabling FET damaged But digital inputs are voltage free contacts. software problems.

Chances are FET, and or diodes had gone. Possible what happen here is when the Check 2x1 connector. Possibly, the FET, inductor (the green resistor lookalike), or diode
connector is put upside down, and when 24V is gone here, due to reverse biased of power.

Also, check other digital inputs at connector 2x4, and at 2x6 as well.
Depends on what the REGULATOR is used for, ie LOCAL only, or REMOTE only, as one of
these digital contacts is faulty, and by using the "wrong" option, the fault may come up.
For example, if the component that is controlling the LOCAL control for START/STOP, etc,
is faulty, hence when we operate the Elektronikon locally, the fault message would
probably turn up, howver, if we operate the Elektronikon remotely, chances are it will be
ok.

If module was "brand new but faulty", then replace the Elektronikon and send faulty
part back to head office.
Replace Elektronikon

MKIII and Siemens MasterDrive 106 Elektronikon Mk III LRR V1.8, Relays enable at power on Relay possible damaged due to incorrect power input - Power down the regulator.
2.3 - Inconsistency between the status of the relays and - Elektronikon is not powered up. Only one contact (out of three) of the Emergency - Check the Emergency stop button.
HRR the status that the relay should be in. stop button is activated. Power is restored to the Elektronikon. At this moment the * Make sure all wires connected firmly and no bad contacts are existing.
power supply to the internal relays * All the components of the Emergency stop button (base and contacts) should have
the same colour (black or brown)
* A mixture of colours could cause this problem to exist.
Check the wiring from the Emergency stop button to the regulator.
- Power up the regulator again.
Replace Elektronikon Mk III if all else fails

MKIII and Siemens MasterDrive 107 Elektronikon Mk III LRR V1.8, Serial line error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III if all else fails
2.3
MKIII and Siemens MasterDrive 108 Elektronikon Mk III LRR V1.8, Keyboard error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III if all else fails
2.3
MKIII and Siemens MasterDrive 109 Elektronikon Mk III LRR V 2.3 Filter error (relay ouputs read-back not stable)

MKIII and Siemens MasterDrive 10XX Elektronikon Mk III LRR/HRR (Online) Read back output error

MKIII and Siemens MasterDrive 11 Elektronikon Mk III LRR V1.8, V1.8: EEprom not writable Most probably due to a short circuit of the 12V supply for the digital inputs For example, when this module being use for remote control. As two digital inputs were
2.3, HRR V2.3: Relays supply error Unrecoverable failures generated by the regulator. closed, please check which one is causing the failure 11. Is it the CMS 2 as from when it is
closed or is it 30 & 34 contact.
If nothing is found, then change the module.

This bad module, however maybe used for machine which remains in "local
control"only.

MKIII and Siemens MasterDrive 11XX Elektronikon Mk III HRR (Online) 12V short circuit or FET to enable damaged
MKIII and Siemens MasterDrive 12 Elektronikon Mk III LRR V1.8, V1.8: Division by zero Unrecoverable failures generated by the regulator. Hardware or software problem
2.3 V2.3: EEprom not writable Replace Elektronikon
MKIII and Siemens MasterDrive 13 Elektronikon Mk III LRR V1.8, V1.8: Wrong active display, Unrecoverable failures generated by the regulator. Hardware or software problem
2.3 V2.3: EEprom checksum error Replace Elektronikon
MKIII and Siemens MasterDrive 14 Elektronikon Mk III LRR V1.8, V1.8: Relays supply error, Unrecoverable failures generated by the regulator. Replace Elektronikon
2.3 V2.3: Eprom checksum error Internal error
MKIII and Siemens MasterDrive 15 Elektronikon Mk III LRR V 2.3 Wrong activated display Unrecoverable failures generated by the regulator. Replace Elektronikon

MKIII and Siemens MasterDrive 17 Elektronikon Mk III LRR V1.8 Watch dog error Some external conditions were not met while system was checking for operation. 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
Recoverable failure. through the reset function key of the system failure display.
Check external parts for fault, loose connections, power missing of one phase, etc.

MKIII and Siemens MasterDrive 200 Elektronikon Mk III LRR V Watch dog error. 200XX (bootstrap) These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR compressor can start after the failure reset. failure display.
MKIII and Siemens MasterDrive 2000 Elektronikon Mk III LRR/HRR (Bootstrap) Reserved area checksum incorrect Hardware or software problem. Possibly need a new regulator

MKIII and Siemens MasterDrive 2001 Elektronikon Mk III HRR (Bootstrap) Reserved area checksum incorrect Unrecoverable error. Caused by corruption within the electronics to misread. Try to power OFF and ON again. If cannot resolved, then try a new module.

MKIII and Siemens MasterDrive 201 Elektronikon Mk III LRR V Internal power failure routine not completed These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR 201xx(bootstrap) compressor can start after the failure reset. failure display.
MKIII and Siemens MasterDrive 202 Elektronikon Mk III LRR V Backupped RAM checksum error These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR 202xx(bootstrap) compressor can start after the failure reset. failure display.
MKIII and Siemens MasterDrive 203 Elektronikon Mk III HRR Power off during EEPROM writing These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
203xx (bootstrap) compressor can start after the failure reset. failure display.
MKIII and Siemens MasterDrive 204 Elektronikon Mk III HRR Power off during EEPROM writing and power failure These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
interrupt routine enabled compressor can start after the failure reset. failure display.
204xx(bootstrap)
MKIII and Siemens MasterDrive 205 Elektronikon Mk III HRR Power off during EEPROM writing and backup ram These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
checksum incorrect. compressor can start after the failure reset. failure display.
MKIII and Siemens MasterDrive 20XX Elektronikon Mk III HRR (Bootstrap) Reserved area checksum incorrect
MKIII and Siemens MasterDrive 21XX Elektronikon Mk III HRR (Bootstrap) EPROM checksum incorrect
MKIII and Siemens MasterDrive 22 Elektronikon Mk III LRR V1.8 Eprom checksum error Internal error Replace Elektronikon Mk III if all else fails
Unrecoverable failures generated by the regulator.
MKIII and Siemens MasterDrive 22XX Elektronikon Mk III HRR (Bootstrap) Flash checksum incorrect
MKIII and Siemens MasterDrive 30XX Elektronikon Mk III HRR (Online) Division by 0
MKIII and Siemens MasterDrive 31XX Elektronikon Mk III HRR (Online) Wrong activated display
MKIII and Siemens MasterDrive 33 Elektronikon Mk III LRR V1.8 Eeprom checksum error Internal error Replace Elektronikon Mk III if all else fails
Unrecoverable failures generated by the regulator.
MKIII and Siemens MasterDrive 37 Elektronikon Mk III - AC-Line Fault Line Failute detected; in the "Ready" and "On" states, and alarm is output initially Wifh power supply and contactors that switches the power supply.
GA90VSD Simovert P 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

MKIII and Siemens MasterDrive 40 Elektronikon Mk III HRR (Autoconfig) No delivery air input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MKIII and Siemens MasterDrive 41 Elektronikon Mk III HRR (Autoconfig) More than 1 delivery air input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MKIII and Siemens MasterDrive 42 Elektronikon Mk III HRR (Autoconfig) More than 1 backup pressure input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MKIII and Siemens MasterDrive 43 Elektronikon Mk III HRR (Autoconfig) More than 1 intercooler pressure input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MKIII and Siemens MasterDrive 44 Elektronikon Mk III HRR (Autoconfig) More than 4 DIOE modules connected These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MKIII and Siemens MasterDrive 45 Elektronikon Mk III HRR (Autoconfig) More than 4 SIOE modules connected These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MKIII and Siemens MasterDrive 46 Elektronikon Mk III HRR (Autoconfig) More than 3 COM1 modules These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
connected one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MKIII and Siemens MasterDrive 47 Elektronikon Mk III HRR (Autoconfig) More than 2 COM3 modules These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
connected one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MKIII and Siemens MasterDrive 48 Elektronikon Mk III HRR (Autoconfig) COM3 not permitted in configuration These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MKIII and Siemens MasterDrive 49 Elektronikon Mk III HRR (Autoconfig) SIOE module not permitted in These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
configuration one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MKIII and Siemens MasterDrive 50 Elektronikon Mk III HRR (Autoconfig) Wrong CCM during autoconfiguration These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
(CMS1, CMS2) one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.
Please check to make sure CMS is in correct position

MKIII and Siemens MasterDrive 51 Elektronikon Mk III HRR (Autoconfig) DIOE type configured is for ES100 These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
system one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Please check for the right module.

MKIII and Siemens MasterDrive 53 Elektronikon Mk III HRR / (Autoconfig) No VSD COM module during These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
VSD configuration one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Please connect COM module to regulator before autoconfiguration.

MKIII and Siemens MasterDrive 54 Elektronikon Mk III HRR / (Autoconfig) More than 1 VSD COM module These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
VSD connected. one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Make sure that there is only ONE COM module for the VSD. Then restart
autoconfiguration.

MKIII and Siemens MasterDrive 7001 Elektronikon Mk III HRR / (Online) Internal communication failed Internal communication between master and a com. Module - Check the cable for connection between the 2 modules
VSD - Check the power supply to the modules (24V)
- 700X, where X = the com module no., for example, 7001 implies no. 1 module is not
communicating with Master module. 7002 implies no. 2 module is not co

MKIII and Siemens MasterDrive 70XX Elektronikon Mk III HRR / (Online) Internal communication failed Internal communication between master and com. Module - Check the cable for connection between the 2 modules
VSD - Check the power supply to the modules (24V)

- 700X, where X = the com module no., for example, 7001 implies no. 1 module is not
communicating with Master module. 7002 implies no. 2 module is not communicating
with Master module. 7002 implies no. 2 module is not communicating. This is more
relevant when there are more than one communication module is configured to the
Master / Compressor.
- Try to power OFF the compressor, then ON again a short time later.

MKIII and Siemens MasterDrive 7101 Elektronikon Mk III HRR / (Online) A module in INOPERATIVE UNLOCK was Module 01 became inoperative and it was connected to another operative module Try to reprogram the modules and check the start configuration
VSD connected to an OPERATIVE regulator
MKIII and Siemens MasterDrive 71XX Elektronikon Mk III HRR / (Online) A module in INOPERATIVE UNLOCK was Module XX became inoperative and it was connected to another operative module Try to reprogram the modules and check the start configuration
VSD connected to an OPERATIVE regulator
eg. ZR315VSD with COM2 modbus module
F71XX ==> 01 = fault @ module 01 (module 01 = SIOE module)
==> 02 = fault @ module 02 (module 02 = VSD's COM2)
==> 03

MKIII and Siemens MasterDrive 7201 Elektronikon Mk III HRR / (Online) A module in INOPERATIVE LOCK was Module 01 (COM module) is inoperative by incorrect programming or by Try to reprogram
VSD connected to an INOPERATIVE or OPERATIVE connecting an empty module.
regulator
MKIII and Siemens MasterDrive 72XX Elektronikon Mk III HRR / (Online) A module in INOPERATIVE LOCK was Module 01 (COM module) is inoperative by incorrect programming or by Try to reprogram
VSD connected to an INOPERATIVE or OPERATIVE connecting an empty module.
regulator
MKIII and Siemens MasterDrive 7301 Elektronikon Mk III HRR / (Online) Communication failure between regulator - Loose connection between HRR and converter. - Check connections of converter / COM module
VSD and converter - COM 1 (or COM 2) is faulty - Isolate converter from COM module, and use VSD simulation software to test whether
- CU /CUVC in doubt (Siemens) COM module or converter is at fault. A pc with RS232 cable or RS485 ( such as that use
- PSU card (it is possible that 24Vdc is available for the CUVC, however, there may for SDP4win) is required. The cable is to be connected in place of converter cable
not be +/- 5, or 15V for other functions) connection.
- GAX card (power supply - If converter at fault:
* If fault occurs all the times, it is more likely the GAX card need to be looked at.
Please take care when changing GAX card, and watch out for resistor bank jumpers. GAX
card = power supply card (for GA90VSD with Simovert P drive)
* If intermittently, then CU or CCU card fault is more likely. These cards are
normally arrive with no memory. Please see programming procedures if required.

- ABB - Reprogram the Elektronikon Mk III and test again.

- Siemens - This fault could occurs when the CUVC control card is freshly
(re)programmed. This is due to the fact one or more parameters have incorrect
communication baud rate. The correct settings should be:

P701.1 = 6 (baud rate = 9600 for communication between converter and PC (Simovis))
This parameter setting may be changed so that both the Simovis and the Converter have
the same values. For some machines, it is default at 9600, while others, default at 19200

P701.2 = 7 (baud rate = 19200 for communication between converter and COM2 /
Elektronikon.
If this parameter has the wrong setting, F7301 will be displayed. This setting should be
identical to that of the VSD simulation program.
P701.3 = 7 (baud rate = 19200)
PLEASE BE ENSURED THAT THE RESISTOR BANK FROM THE GAX CARD IS FUNCTION
PROPERLY. AS EXPERIENCED IN ACNZ HAS SHOWN THAT FAULTY RESISTOR BANK CAN
(AND PROBABLY WILL) DISGUISE ITSELF HAS F14, F12, ETC. AND ARE INTERMITTENT
FAULTS.

BECAUSE THE RESISTOR BANK HAS TO BE TAKEN OUT EVERYTIME THE GAX CARD BEEN
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.
MKIII and Siemens MasterDrive 7302 Elektronikon Mk III HRR / (Online) Communication failure between regulator - Loose connection between HRR and converter. - Check connections of converter / COM module
VSD and converter - COM 1 (or COM 2) is faulty - Isolate converter from COM module, and use VSD simulation software to test whether
- CU /CUVC in doubt (Siemens) COM module or converter is at fault. A PC and RS485 <-> RS232 converter box is
- PSU card (it is possible that 24Vdc is available for the CUVC, however, there may required as well as the DFM4win cable. The cable is to be connected in place of
not be +/- 5, or 15V for other functions) converter cable connection.
- GAX card (power supply - If converter at fault:
* If fault occurs all the times, it is more likely the GAX card need to be looked at.
Please take care when changing GAX card, and watch out for resistor bank jumpers. GAX
card = power supply card (for GA90VSD with Simovert P drive)
* If intermittently, then CU or CCU card fault is more likely. These cards are
normally arrive with no memory. Please see programming procedures if required.

- ABB - Reprogram the Elektronikon Mk III and test again.

- Siemens - This fault could occurs when the CUVC control card is freshly
(re)programmed. This is due to the fact one or more parameters have incorrect
communication baud rate. The correct settings should be:

P701.1 = 6 (baud rate = 9600 for communication between converter and PC (Simovis))
This parameter setting may be changed so that both the Simovis and the Converter have
the same values. For some machines, it is default at 9600, while others, default at 19200

P701.2 = 7 (baud rate = 19200 for communication between converter and COM2 /
Elektronikon.
If this parameter has the wrong setting, F7301 will be displayed. This setting should be
identical to that of the VSD simulation program.

P701.3 = 7 (baud rate = 19200)

PLEASE BE ENSURED THAT THE RESISTOR BANK FROM THE GAX CARD IS FUNCTION
PROPERLY. AS EXPERIENCED IN ACNZ HAS SHOWN THAT FAULTY RESISTOR BANK CAN
(AND PROBABLY WILL) DISGUISE ITSELF HAS F14, F12, ETC. AND ARE INTERMITTENT
FAULTS.

BECAUSE THE RESISTOR BANK HAS TO BE TAKEN OUT EVERYTIME THE GAX CARD BEEN
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.

MKIII and Siemens MasterDrive 73XX Elektronikon Mk III HRR / (Online) Communication failure between regulator - Loose connection between HRR and converter. - Check connections of converter / COM module
VSD and converter - COM 1 (or COM 2) is faulty - Isolate converter from COM module, and use VSD simulation software to test whether
- CU /CUVC in doubt (Siemens) COM module or converter is at fault. A PC and RS485 <-> RS232 converter box is
- PSU card (it is possible that 24Vdc is available for the CUVC, however, there may required as well as the DFM4win cable. The cable is to be connected in place of
not be +/- 5, or 15V for other functions) converter cable connection.
- GAX card (power supply - If converter at fault:
* If fault occurs all the times, it is more likely the GAX card need to be looked at.
Please take care when changing GAX card, and watch out for resistor bank jumpers. GAX
card = power supply card (for GA90VSD with Simovert P drive)
* If intermittently, then CU or CCU card fault is more likely. These cards are
normally arrive with no memory. Please see programming procedures if required.

- ABB - Reprogram the Elektronikon Mk III and test again.

- Siemens - This fault could occurs when the CUVC control card is freshly
(re)programmed. This is due to the fact one or more parameters have incorrect
communication baud rate. The correct settings should be:
P701.1 = 6 (baud rate = 9600 for communication between converter and PC (Simovis))
This parameter setting may be changed so that both the Simovis and the Converter have
the same values. For some machines, it is default at 9600, while others, default at 19200

P701.2 = 7 (baud rate = 19200 for communication between converter and COM2 /
Elektronikon.
If this parameter has the wrong setting, F7301 will be displayed. This setting should be
identical to that of the VSD simulation program.

P701.3 = 7 (baud rate = 19200)

PLEASE BE ENSURED THAT THE RESISTOR BANK FROM THE GAX CARD IS FUNCTION
PROPERLY. AS EXPERIENCED IN ACNZ HAS SHOWN THAT FAULTY RESISTOR BANK CAN
(AND PROBABLY WILL) DISGUISE ITSELF HAS F14, F12, ETC. AND ARE INTERMITTENT
FAULTS.
BECAUSE THE RESISTOR BANK HAS TO BE TAKEN OUT EVERYTIME THE GAX CARD BEEN
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.E58

MKIII and Siemens MasterDrive 7401 Elektronikon Mk III HRR / (Online) Incorrect format in data send from Error 0 - incorrect data format (byte 6/7, readback status) - Switch machine OFF then back ON again. Allow a few mins for all power inside
VSD converter to regulator Error 100 - incorrect data format (byte 2/3/8/9, parameters) electronics to dissipate.
SIEMENS / ABB Error 200 - Checksum failure - Reprogam the converter.
Siemens VSD: A possible fault would that some data in EPROM is lost, or
corrupted, or during programming, - Check parameters, compare with list and adjust any discrepancies

MKIII and Siemens MasterDrive 7402 Elektronikon Mk III HRR / (Online) Incorrect format in data send from Error 0 - incorrect data format (byte 6/7, readback status) - Switch machine OFF then back ON again. Allow a few mins for all power inside
VSD converter to regulator Error 100 - incorrect data format (byte 2/3/8/9, parameters) electronics to dissipate.
SIEMENS / ABB Error 200 - Checksum failure - Reprogam the converter.
Siemens VSD: A possible fault would that some data in EPROM is lost, or
corrupted, or during programming, - Check parameters, compare with list and adjust any discrepancies
MKIII and Siemens MasterDrive 74XX Elektronikon Mk III HRR / (Online) Incorrect format in data send from Error 0 - incorrect data format (byte 6/7, readback status) - Switch machine OFF then back ON again. Allow a few mins for all power inside
VSD converter to regulator Error 100 - incorrect data format (byte 2/3/8/9, parameters) electronics to dissipate.
SIEMENS / ABB Error 200 - Checksum failure - Reprogam the converter.
Siemens VSD: A possible fault would that some data in EPROM is lost, or
corrupted, or during programming, - Check parameters, compare with list and adjust any discrepancies

- Siemens MasterDrive: Check the DC Link voltage and r006 parameter, see if all agree or
within tolerance of each other. If not, then either the CUVC card or (and ??) PSU card has
a problem. If the PSU card has a problem, then the Start Inhibit may not be possible,
hence the converter cannot be started by the Elektronikon. This can also be monitored
by r012 parameter, (Service Switch parameter acknowledgement. r012 = 1 => PMU
controlled, r012 = 2 => Elektronikon Controlled)

MKIII and Siemens MasterDrive 7601 HRR / VSD - Masterdrive Unknown fault as occur in converter (Online) A fault has occur, however the message has been masked by the parameter P60 Change the parameter P60 = 0 to P60 = 1. This can be done via the PMU (ParaMeterizing
(CUVC) Series Unit). And observe the new fault code (if any) on the HRR or PMU
Converter failure readng failed

MKIII and Siemens MasterDrive A015 MasterDrive Series - CUVC External alarm 1 Parameterizable external alarm input 1 has been activated Check:
- whether the cable to the corresponding digital input has been interrupted.
- parameter P588 Src No Ext Warn 1
MKIII and Siemens MasterDrive A016 MasterDrive Series - CUVC External alarm 2 Parameterizable external alarm input 2 has been activated Check:
- whether the cable to the corresponding digital input has been interrupted.
- parameter P588 Src No Ext Warn 2
MKIII and Siemens MasterDrive A017 Masterdrive / CUVC, CU2 Drive is not in healthy state - Possibly due to faulty IGD. SS is also not able to perform properly. R012 (Active - Remove the drive and perform visual inspection of IGD.
BICO) does not change state when SS change position - IGD (and maybe PSU) may need replacement.
- Also possible is power supply card is faulty, hence not able to give the converter
the correct signals to inhibit the

MKIII and Siemens MasterDrive A020 MasterDrive Series - CUVC Overcurrent An overcurrent condition has occurred Check the driven load for an overload condition.
- Are the motor and the converter matched?
- Have the dynamic performance requirements been exceeded.
MKIII and Siemens MasterDrive A021 MasterDrive Series - CUVC Overvoltage An overvoltage condition has occurred Check the supply voltage. The converter regenerates without regeneration possbility.

MKIII and Siemens MasterDrive A022 MasterDrive Series - CUVC Inverter temperature The threshold for initiating an alarm has been exceeded. 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

MKIII and Siemens MasterDrive A023 MasterDrive Series - CUVC Motor temperature The parameterizable threshold for initiating an alarm has been exceeded. - 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.
MKIII and Siemens MasterDrive A024 MasterDrive Series - CUVC Motor movement The motor has been moved during motor data identification Lock the motor.

MKIII and Siemens MasterDrive A025 MasterDrive Series - CUVC I2t inverter If the instantaneous load condition is maintained, then the inverter will be Check:
thermally overloaded. - P72 Rtd Drive Amps
- MLFB P70
- P128 Imax
- r010 Drive Utilizat

MKIII and Siemens MasterDrive A029 MasterDrive Series - CUVC I2t motor The parameterized limit value for the I2t monitoring of the motor has been Motor load cycle is exceeded !!
exceeded. Check:
- P382 Motor Cooling
- P383 Mot Tmp T1
- P384 Mot Load Limits

MKIII and Siemens MasterDrive A033 MasterDrive Series - CUVC Overspeed Bit 3 in r553 status word 2 of the setpoint channel. The speed actual value has - P804 Overspeed Hys plus
exceeded the value of maximum speed plus the set hysteresis. - P452 n/f(max, FWD spd) or
- P453 n/f(max, REV spd) has been exceeded.
Increase the parameter for the maximum frequencies or reduce the regenerative load.

MKIII and Siemens MasterDrive A034 MasterDrive Series - CUVC Setpoint/actual value deviation Bit 8 in r552 status word 1 of the setpoint channel. The difference between Check:
frequency setpoint/actual value is greater than the parameterized value and the - whether an excessive torque requirement is present.
control monitoring time has elapsed. - whether the motor has been dimensioned too small.
Increase values P792 Perm Deviation Frq/set/actual DevSpeed and P794 Deviation Time.

MKIII and Siemens MasterDrive A042 MasterDrive Series - CUVC Motor stall/lock Motor is stalled or blocked. Check:
- Whether the drive is locked
The alarm cannot be influenced by P805 "PullOut/BlckTime", but by P794 - Whether the encoder cable is interrupted during speed control and whether the shield
"Deviation Time" is connected.
- Whether the drive has stalled
- For synchronous motors (P095 = 12): excitation current injection
MKIII and Siemens MasterDrive A075 MasterDrive Series - CUVC Ls, Rr Dev The measured values of the leakage measurement or of rotor resistance deviate Usually the leakage reactance P122 is the average value resulting from the measured
significantly. values in r546.1…12, and the rotor resistance r126 from the values in r542.1..3.

If individual measured values significantly deviate from the average values, they are
automatically not taken into account for the calculation (for RI) or the value of the
automatic parameterization remains (for Ls). It is only necessary to check the results for
their plausibility in the case of the drives with high requirements on torque or speed
accuracy.

MKIII and Siemens MasterDrive A078 MasterDrive Series - CUVC Stands. Meas The standstill measurement is executed when the converter is powered up. The If the standstill measurement can be executed withou any danger:
motor can align itself several times in a certain direction with this measurement. - Power up the converter.

MKIII and Siemens MasterDrive A079 MasterDrive Series - CUVC Mld Inv Stop The rotating measurement has been aborted or cannot commence because an P561 Scr InvRelease - Release the inverter
inverter stop command is present.
If necessary, re-start the measurement by powering up the converter.
MKIII and Siemens MasterDrive A080 MasterDrive Series - CUVC Motld: Dr.M When the converter is powered up, the rotating measurement automatically If the rotating measurement can be executed without any danger:
accelerates the drive. The drive can then only be externally controlled in a
restricted fashion. - Power up the converter.
MKIII and Siemens MasterDrive E All masterdrive CUVC series - Insufficient power to display panel (PMU) Either the power supply card (PSU1) or the CUVC card is faulty. At terminal X101 of CUVC card check:
GA30VSD . . .
- Pin 1 & 2: Use Vdc multimeter to check for 24 Vdc. If not, then the power supply card,
PSU1 is faulty.
Also, at X102, pin 13 should have 10 Vdc, and pin 14 = -10Vdc, with pin 2 common.

If these voltages are present, then the CUVC card is faulty.

MKIII and Siemens MasterDrive F0 GA50VSD - CU2 Converter Fail. Undefined error code, not enough - This is an defined error code, meaning that there was not enough time to read - Check for loose connections
time to register fault out the fault message from the converter. - Try to reprogam the MKIII
- Most probably caused by a voltage interruption.

MKIII and Siemens MasterDrive F001 Siemens CU2, CUVC Contactor Checkback If the a contactor checkback signal is configured, a checkback signal was not P591 S.MC chkbck sign.
received within 500ms after the power-up command The parameter value must match the main contactor checkback signal connection. Check
the main contactor checkback signal circuit.
Should NEVER happen in Masterdrive Series.

MKIII and Siemens MasterDrive F002 Siemens MasterDrive Series Pre-Charging - When pre-charging, the minimum DC link voltage (P071 Line volts x 1.34) of 80% - Check the supply voltage.
CU2, CUVC has not been reached . - Can fail if low V, because software setting for V is wrong.
- Compare with P071 Line Volts (Compare P071 with the DC link voltage on DC units)
- The maximum pre-charging time of 3 seconds has been exceeded. - Check the rectifier / regenerative unit on DC units. The rectifier/regenerative unit on
DC units. The rectifier/regenerative unit must be switched on before the inverter is
- SHOULD NEVER HAPPEN DURING OPERATION, ONLY HAPPEN AT STARTUP switched on.
- Check voltage C and D. Should get high 500V's (dc). While having the multimeter on it,
please restart the machine (in converter local control mode). If the voltage deteriorate in
over a short period of time, then there is pre-charge problem, hence, change the pre-
charger PCB, or Siemens to change it if under warranty. For G85GA30VSD case, the
whole drive should be return to Siemens for evaluation, if under warranty.

MKIII and Siemens MasterDrive F006 Siemens CUVC (MasterDrive) DC link Overvoltage - Shutdown due to excessive DC link voltage - Check supply voltage or DC voltage
- Converter is working at upper tolerance limit and at full load.
- Can be caused by line phase failure
- Converter is operating in regenerative mode without feedback possibility
- Try:
- Increase P464 Decel Time
- Activate P515 DC Bus Volts Reg (check P071 beforehand)
- Reduce P526 Fly Search Speed
- Reduce P259 Max Regen Power (only for P100 = 3, 4 or 5)
On a GA 37 VSD, that we have been working on was starting /stopping intermittantly.
It had the same problem as before showing an erratic DC Link voltage at the PMU, with
stable voltage at the DC Link. The original power supply (PSU) was faulty, and replaced
with a new PSU. Weeks later, the problem still existed.

The problem was traced to a break it a joint on the power supply control card that was
replaced by us.
The card was repaired onsite and the problem rectified.

MKIII and Siemens MasterDrive F008 Siemens CUVC (MasterDrive) DC link Undervoltage - The lower limit value of 76% of the DC link voltage (P071 Lin Volts), or 61% when - Check Input DC voltage
kinetic buffering has benn enabled, has been fallen short of. - DC link - Check for PCC (precharger card) and PCU (Precharger Unit - the less dense in
- Undervoltage in the DC link with active kinetic buffering and speed less than 10% terms of electronics, of the two cards - This card normally OK)
of the rated motor speed. - Maybe diodes blown as well, please check.
- Check for thyristor modules, should be approx. 6v in-circuit diode check! And OPEN-
CIRCUIT out-of-circuit diode check !
- IVI card may be faulty as well.
- Terminal C and D should be checked using multimeter with Vdc, or some sort of Scope
meter. Should expect to be in excess of 500Vdc
- Can also be seen Simovis program. Parameter r006 (DC bus voltage). Can be checked
on PMU as well
MKIII and Siemens MasterDrive F010 Siemens CUVC (MasterDrive) DC link Overvoltage MOST UNLIKELY TO OCCUR IN OUR APPLICATION - Check supply voltage
- Due to excessive DC link voltage, shutdown has taken place. - Check braking resistors
- Lower threshold value than F006 - Converter operates regeneratively without a feedback possibility. Braking unit must be
set to the lower response then threshold (673V)

MKIII and Siemens MasterDrive F011 Siemens CUVC Overcurrent - Overcurrent shutdown has occurred. - Check the free rotation (by hand) of the compressor element / motor
(MasterDrive), CU2 - The shutdown threshold has been reached. - Check connections at the measuring devices in the front of the converter
- The phase in which an overcurrent has occurred is indicated in a bit-coded - Check if incoming supply voltage < 400 -10% and verify if cable section is accurate to
manner in the fault value (see r949) spec. (min 50mm square)
Phase U--> Bit 0 = 1--> fault value = 1 - Check RFI - net filter for short circuit
Phase V--> Bit 1 = 1- - Check the converter output for short-circuit or earth fault
- Check the load for an overload condition
- Check whether motor and converter are correctly matched (this should always be true)
- CT (current transformer) maybe faulty. As current is asked for again and again causing
build up of --> overcurrent. This condition is usually NOT intermittent. CT are very hard
to check, can only be done by v/hz meter and observe for characteristics.
- Check IVI (inverter interface card), replace if cannot solve. Check ABO (adaptor board),
ABO and IVI must be matched.
- Check the resistance of the motor windings in the 3 phases
- Try to start without back pressure, ie with an empty air net
- Try to program P0462 to 30 sec for slower acceleration
- Try new CUVC board
* The fault display must be cleared first before the parameters can be accessed. If the
F011 cannot be cleared, then it is probably the CT (LEM) module is at fault.
But to clear the fault, the scroll UP / DOWN must be pressed at the same time.

When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and L1(u), then L2(v) and L3(w); D across L1(u), L2(v) and L3(w).

If we get short in any of the combinations, eg, resistance between C and L1 then the
IGBT (transistor) is damaged. For all IGBT's to be OK, then some resistance is expected on
all combinations.
Try to start the converter with MOTOR DISCONNECTED and Service switch to manual
control:
- To do this, please observe and adjust the following parameters:
For CUVC MasterDrive:
- Make P53 = 6 (on Simovis, it is binary number . . . 110), then P060 = 5 (Drive Setting),
then P100.1 = 3 (f regulated) to P100.1 = 1 (u/f). The idea here is to change the VECTOR
CONTROL to voltage control. THEN, change P060 = 0 (or 1) in order to start the converter
manually. If NOT, then 005 always appear on the PMU.

If F011 CANNOT be resolved, and P060 = 5, and DOES NOT able to be programmed back
to P060 = 0 or 1, then the CT (LEM) is faulty. This symptom occurs when the PMU is been
MKIII and Siemens MasterDrive F012 Siemens CUVC (MasterDrive) Current too Low During excitation of the induction motor, the current did not rise above 12.5% of - Only for closed loop n/f/T control (P100 = 3, 4 or 5)
the setpoint magnetising current for no-load operation - If no motor is connected, go into the simulation mode P372
- Check current detection, check power section
MKIII and Siemens MasterDrive F014 Siemens CUVC (MasterDrive) I too low SHOULD NOT HAPPEN - Check the output contactor
- During excitation of the motor, the current component is less than 25% of the - Check the motor cable
motor no-load current
- Only U800 = 1
irrespective of the type of control
(Difference to F012)

MKIII and Siemens MasterDrive F015 Siemens CUVC (MasterDrive) Motor Stall - Likely cause is mechanical blockage of motor - Check Motor / element for free rotation
- Motor has stalled or locked - Check current in all three phases to the motor, make sure that they are within 10% of
- If the static load is too high each other.
- Possible that a bearing has failed, ie, the non-drive end, thus still enable the - Check the bearings of the motor.
motor the ability to rotate at slow speed - Reduce Load
- Drive in running - Increase current Limits
- Reprogram card
- Change new CUVC card
- Could be one phase missing, where consumption on all 3 phases arevery different.E97
- One case in Switzerland, where the burned cables on RFI filters or bad contacts on the
inverter bridge.

MKIII and Siemens MasterDrive F019 Siemens CUVC (MasterDrive) Motor not found - Motor been stolen / not there - Power up after coasting
- Flying restart without tachometer - Possibly increase P525 Fly Search Amps
MKIII and Siemens MasterDrive F020 Siemens CUVC (MasterDrive) Motor Temperature The motor temperature limit value has been exceeded. - Check the motor (load, ventilation, etc). The actual motor temperature can be read in
* r949 = 1 means limit value of motor temperature exceeded r009 of Siemens PMU (panel display)
* r949 = 2 means short-circuit in cable to the motor temperature sensor or sensor - Motor temperature.
defective. - Check P381 Mot Temp settings.
* r949 = 4 means wire break in cable to the motor - Fault - check the KTY84 input at connector - X103:29, 30 for short circuit.
KTY84 resistance at room temperature should be in the vicinity of 700 - 1000 Ohms
- Check with multimeter, Converter trips when infinite resistance registered.
CHECK: Input of CUVC (ie analog inputs at X103:29,30 and related software / hardware
wiring.)

Use a 0 - 4kOhms potentiometer, and connect to X103:29,30. (For the potentiometer,

short the middle lead to ONE of the other leads)
Make parameter P044.1 = K245 (Mot Temp) . . . . . . . K245 means input is of type KTY84
thermistor / resistor
Check parameter r045. Reading on r045 should change as potentiometer to X103:29,30
changes. If not, then CUVC card may be faulty.

If the card is ok, then r009 = r045 = settings of potentiometer / KTY84 thermistor.
CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance in
supply voltage can lead to 10% extra current in one of the motor phases. 3.5% unbalance
in supply voltage will give 25 deg. C higher in motor temperature.
EMERGENCY ONLY:
Make Parameter P380.1 = 0
Parameter P381.1 = 0
The compressor / drive will now run without thermal protection on the motor.
MOTOR TEMP SENSOR (KTY 84) IS BEING REPLACE BY STANDARD MOTOR THERMISTOR
- This may happen when the KTY 84 motor temperature is not available at time of
service / breakdown, and a new standard motor thermistor is being fitted.
- If a standard motor thermistor is being fitted instead, the Masterdrive will not able to
display the actual motor temperature, HOWEVER, it will still the protects the system and
shutdown at and above temperature 180 deg. C.

** Parameter changes to suit STANDARD THERMISTOR modification:

- P380.1 = 0
- P381.1 = 1 (=1 to make the input to the CUVC of 1.5 Kohms when temperature is 180
deg. C)
- P385 = DE-ACTIVATED (automatically)
MKIII and Siemens MasterDrive F021 Siemens, CUVC Motor I2t Parameterized limit value of the I2t monitoring for the motor has been exceeded. Check : P383 Mot Tmp T1

MKIII and Siemens MasterDrive F023 Siemens converter, CUVC Inverter Temperature The limit value of the inverter temperature has been exceeded. Measure the air intake and ambient temperature. Please observe the reduction curves
at >40 deg. C
R949 = 1 : Limit value of inverter temperature has been exceeded.
R949 = 2 : Sensor 1 : wire break of sensor cable or sensor defective. Check:
- Whether the fan E1 is connected and is rotating in the correct direction
r949 = 18 : Sensor 2 : " " - that the air entry and discharge openings are not restricted
r949 = 34 : Sensor 3 : " " - Temperature sensor at -X30

MKIII and Siemens MasterDrive F025 GA50VSD - CU2 UCE ph. L1 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L1 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 2 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted
When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.

- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.G98
PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-
ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.

NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
MKIII and Siemens MasterDrive F026 GA50VSD - CU2 UCE ph. L2 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L2 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 2 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted

When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.
- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.

PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-

ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.
NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
MKIII and Siemens MasterDrive F027 GA50VSD - CU2 UCE ph. L3 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L3 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 2 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted
When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.

- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.
PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-
ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage E100will give 25 deg. C higher in motor temperature.

NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
MKIII and Siemens MasterDrive F028 GA50VSD - CU2 Supply phase The frequency and amplitude of the DC link ripple indicates a single phase supply - Check supply voltage
CUVC failure. - Check the proper connection at the line reactor (L1)
- Check if one of the coils of line reactor L1 is short circuit.F106
Similar to F8

MKIII and Siemens MasterDrive F029 Siemens, all VSD's except Measured Valued Sensor Fault occurs in the measured value sensing system - Possibly CU is faulty
GA90VSD Simovert P r949 = 1 Offset adjustment not possible in phase L1 - IGBT or IGD may be defective as it is conductive while signal command does not tell it
r949 = 2 Offset adjustment not possible in phase 3 to do so.
r949 = 3 Offset adjustment not possible in Phases 1 & 3 - Defective phase section
r949 = 65 The analog inputs cannot be automati

MKIII and Siemens MasterDrive F035 VSD - Siemens CUVC / CU2 External fault 1 - External fault 1 has been triggered - Check cabinet for ventilation
- Check for loose connections
- External fault 1 parameter is used for temperature sensor for the cabinet, and it
is parameterised trigger when temp reaches 51 deg. C

Usually happen during hot weather / conditions

P575 Src No ExtFault1
MKIII and Siemens MasterDrive F036 AIF VSD - Siemens CUVC External fault 2 - External fault 2 has been triggered The problem probably does not related to the Masterdrive converter, and because it
ZT37VSD - This failure can be caused by a wrong or loose connection from the micromaster receives faulty signals from the external, hence EXTERNAL FAULT #2 comes up. Should
(fan motor control ) to the main convertor (main motor control). GA180VSD and check for problems outside the main converter.
others which have micromaster
- Aux. Drive Fault. ZT37VSD - See ECB 1339
- GA180VSD and related

MKIII and Siemens MasterDrive F040 Siemens CU2, CUVC AS internal fault Incorrect operating status Replace CU card (A10)
GA50VSD
MKIII and Siemens MasterDrive F041 Siemens CU2, CUVC EEPROM fault a fault has occurred when storing the values in the EEPROM Replace CU card (A10)
GA50VSD
MKIII and Siemens MasterDrive F042 Siemens CU2, CUVC Computing time problem Calculating time problem Reduce the calculating time by:
GA50VSD
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

MKIII and Siemens MasterDrive F043 Siemens CU2, CUVC Coupling int. Internal coupling error. One of the two coupling partners does not respond - Check MWH - CU2 connection
GA50VSD - Replace CU card (A10)
MKIII and Siemens MasterDrive F044 Siemens CU2, CUVC BiCo manager Fault - A fault has occurred during the softwiring of Binectors and connectors - Reparameterize
GA50VSD - Reset unit
- Replace CU card (A10)
In CUVC, observe r949:
> 1000: Fault during softwiring of connectors
> 2000: Fault during softwiring of binectors

MKIII and Siemens MasterDrive F045 Siemens CU2, CUVC Opt. Board HW Hardware fault has occurred when assessing an optional board - Replace CU (A10)
GA50VSD - Check connection of the board and optional boards.
MKIII and Siemens MasterDrive F046 Siemens CU2, CUVC Par task / con. A fault has occur during the transfer of parameters to the gating unit processor - Power unit down and up again
GA50VSD - Replace CU (A10)
MKIII and Siemens MasterDrive F047 Siemens CU2, CUVC Gating Calc Time / internal Comp. Time The calculating time in the gating unit computer is not sufficient Replace CU (A10)
GA50VSD
MKIII and Siemens MasterDrive F1 Siemens CCU - Simovert P Incorrect phase sequence Incorrect phase sequence Reverse 2 incoming lines
GA90VSD
MKIII and Siemens MasterDrive F100 Siemens CUVC, CU2 GRND Init During the ground fault test, a current not equal to 0 was measured, or a UCE or On PMU / Simovis - The fault cause can be read our of r358 (CU2) or r 376 (CUVC)
the overcurrent monitoring responded, although none of the valves were "ground fault test result"
triggered. - Check the converter output for short circuit of ground fault (-X2:U2, V2, W2 - including
motor)
- Check CU is inserted correctly
Frame Sizes 1 & 2
- Check the transistor modules on the PEU board A23 for short circuit
Frame Sizes 3 & 4
- Check transistor modules A100, A200, A300 for short circuit

MKIII and Siemens MasterDrive F101 Siemens CUVC, CU2 GRND UCE During the ground fault test a UCE monitoring function responded in a phase in Check the power section valves for a short circuit, and for converters with fiber-optic
which no valve was triggered gating, the gating unit and the UCE checkback signals, for the correct assignment.

Transistor conductive when not triggered to do so PMU / Simovis: r358 (CU2), r376 (CUVC) can be interrogated to indicate which UCE mo

MKIII and Siemens MasterDrive F102 Siemens CUVC, CU2 GRND Phase During the ground fault test, current flowed in one phase when none of the valves PMU / Simovis: Read-out fault value from R949. The digit of the xth position indicates
were triggered, or the UCE monitoring in the phase responded in which the valve the valve, where the fault occurred at power-up.
was triggered.
XOOO Digit X = 1 = V+, X = 2 = V-, X = 3 = U+
Digit X = 4 = U-, X = 5 = W+, X = 6 = W-

The digit of the xth position defines the pahse, in which i is 0 and thus a valve is
defective (always conductive)
OOOX Digit X = 1 = Phase 1 (U)
X = 3 = Phase 3 (W)
X = 4 = Phase 1 (U) r 3 (W)

Examine phase for defective valves (always conductive)

MKIII and Siemens MasterDrive F103 Siemens CUVC, CU2 Ground fault An earth fault or a fault in the power section is present. During the ground fault PMU / Simovis: Read-out fault from r949. The digit of the xth position specifies the valve,
test, a current flows from the phase in which a valve was triggered, the which, when triggered, manifested the fault.
overcurrent comparitor responded, or a UCE monitoring in a phase has responded
in which a valve wa XOOO x = 1 = V+, x = 2 = V-, x = 3 = U+
x = 4 = U-, x = 5 = W+, x = 6 = W-
Check the motor including feeder cable for ground faults. If there is no ground fault,
check the power section for defective valves which remain conductive.

The digit of the xth position defines the phase in which I is 0, and therefore a valve must
be defective (always conductive)

OOOX Digit x = 1 = Current in phase 1(U)

x = 2 = UCE in phase 2 (V)
x = 3 = Current in phase 3 (W)
x = 4 = Only overcurrent occur

The motor speed should be less than 10% of the stated speed during the ground fault
test !
A ground fault is present in phase V, or there is a defective valve (always conductive)

MKIII and Siemens MasterDrive F12 Siemens CCU - Simovert P - Overcurrent Short circuit, low-resistance ground fault - Check the free rotation of the compressor element and/or motor eg a motor bearing
6SE13 . . . failure
GA90VSD - Check motor windings for possible ground fault
- Check resistance of the motor windings in the 3 phases
- Try start with no back pressure, ie with an empty net
- Check parameter P019 for the proper value (320A); as a trail lower the value in steps of
5 A to a minimum 300A
- Current transfomer may be faulty.
- Try new CCU board.

PLEASE NOTE: on former model GA90 VSD (SN < AII 492 000) Please observe ECB AII0070
(Priority IV) with regards to OIL RESTRICTION AT LOW SPEED for GA90VSD with Simovert
P converter.

CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance in
supply voltage can lead to 10% extra current in one of the motor phases. 3.5% unbalance
in supply voltage will give 25 deg. C higher in motor temperature.

PLEASE BE ENSURED THAT THE RESISTOR BANK FROM THE GAX CARD IS FUNCTION
PROPERLY. AS EXPERIENCED IN ACNZ HAS SHOWN THAT FAULTY RESISTOR BANK CAN
(AND PROBABLY WILL) DISGUISE ITSELF HAS F14, F12, ETC. AND ARE INTERMITTENT
FAULTS.

BECAUSE THE RESISTOR BANK HAS TO BE TAKEN OUT EVERYTIME THE GAX CARD BEEN
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.

MKIII and Siemens MasterDrive F13 Siemens CCU - Simovert P - Motor Overload Motor overload (calculated): Motor current too high for too long a period. - Check for mechanical resistance in compressor / motor
6SE13 . . . - Check the small hole of 4mm in the centre of the boss in the check valve housing which
GA90VSD ensures the full opening of the check valve.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C E120higher in motor temperature.
PLEASE BE ENSURED THAT THE RESISTOR BANK FROM THE GAX CARD IS FUNCTION
PROPERLY. AS EXPERIENCED IN ACNZ HAS SHOWN THAT FAULTY RESISTOR BANK CAN
(AND PROBABLY WILL) DISGUISE ITSELF HAS F14, F12, ETC. AND ARE INTERMITTENT
FAULTS.
BECAUSE THE RESISTOR BANK HAS TO BE TAKEN OUT EVERYTIME THE GAX CARD BEEN
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.

MKIII and Siemens MasterDrive F14 Siemens CCU - Simovert P - Motor Pullout Load too high, or excessive dynamic stressing. - Check for mechanical resistance in compressor / motor
6SE13 . . . Seized element. - Check the small hole of 4mm in the centre of the boss in the check valve housing which
GA90VSD ensures the full opening of the check valve.

- PLEASE NOTE: on former model GA90 VSD (SN < AII 492 000) Please observe ECB
AII0070 (Priority IV) with regards to OIL RESTRICTION AT LOW SPEED for GA90VSD with
Simovert P converter.
PLEASE BE ENSURED THAT THE RESISTOR BANK FROM THE GAX CARD IS FUNCTION
PROPERLY. AS EXPERIENCED IN ACNZ HAS SHOWN THAT FAULTY RESISTOR BANK CAN
(AND PROBABLY WILL) DISGUISE ITSELF HAS F14, F12, ETC. AND ARE INTERMITTENT
FAULTS.
BECAUSE THE RESISTOR BANK HAS TO BE TAKEN OUT EVERYTIME THE GAX CARD BEEN
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.E122
MKIII and Siemens MasterDrive F148 CUVC Series - ZR160VSD Active Signal @ binector U061 is present. ZR160VSD: ZR160VSD:
(ECB1397/C1 implemented) - Temperature limiting switch of motor is activated - open contact, ie, motor - Based on ECB 1397/C1, this fault is present if the terminal X101-7 of the CUVC card is
overtemperature. open contact.
- Faulty temperature limiting switch. - This happen if the motor temperature is too high, or the temperature switch is faulty,
- Loose connection at X101: 1 & 7 or loose connections. Please check these conditions..
Supplementary Reading:

* See function diagram 710, where binector U061 = 0 was made to U061 = 19,
* Binector U952.i059 = 20 was made to U952.i059 = 4.

MKIII and Siemens MasterDrive F15 GA50VSD - CU2 Motor stall Motor stalled or locked - Check motor
Could be one phase missing, where consumption on all 3 phases arevery different. - One case in Switzerland, where the burned cables on RFI filters or bad contacts on the
inverter bridge.

MKIII and Siemens MasterDrive F2 Siemens CCU - Simovert P - PreCharge Error Precharging malfunction, line voltage, inverter defective May occur after a long period of standstill. In this case, restart the machine for up to 10
6SE13 . . . times.
GA90VSD If fault persists, check:
- Supply voltage is within tolerance 400V +/- 10%
- PCC (PreCharging Circuit)
- One of the capacitors may be defective

MKIII and Siemens MasterDrive F20 GA50VSD - CU2 Motor Temp. Motor thermistor problem - Check the motor (load, ventilation, etc). The actual motor temperature can be read in
- Motor overheat r009 of Siemens PMU (panel display)
- Motor temperature.
r949 = 1 Motor temperature limit exceeded - Check P381 Mot Temp settings.
r949 = 2 Short circuit in the cable to the temperature sensor or sensor defect - Fault - check the KTY84 input at connector - X103:29, 30 for shortcircuit.
r949 = 3 Open circuit in the cable to the temperature sensor or sensor defect KTY84 resistance at room temperature should be in the vicinity of 700 - 1000 Ohms
- Check with multimeter, Converter trips when infinite resistance registered.

CHECK: Input of CUVC (ie analog inputs at X103:29,30 and related software / hardware
wiring.)

Use a 0 - 4kOhms potentiometer, and connect to X103:29,30. (For the potentiometer,

short the middle lead to ONE of the other leads)
Make parameter P044.1 = K245 (Mot Temp) . . . . . . . K245 means input is of type KTY84
thermistor / resistor
Check parameter r045. Reading on r045 should change as potentiometer to X103:29,30
changes. If not, then CUVC card may be faulty.

If the card is ok, then r009 = r045 = settings of potentiometer / KTY84 thermistor.
CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance in
supply voltage can lead to 10% extra current in one of the motor phases. 3.5% unbalance
in supply voltage will give 25 deg. C higher in motor temperature.
EMERGENCY ONLY:
Make Parameter P380.1 = 0
Parameter P381.1 = 0
The compressor / drive will now run without thermal protection on the motor.
MOTOR TEMP SENSOR (KTY 84) IS BEING REPLACE BY STANDARD MOTOR THERMISTOR
- This may happen when the KTY 84 motor temperature is not available at time of
service / breakdown, and a new standard motor thermistor is being fitted.
- If a standard motor thermistor is being fitted instead, the Masterdrive will not able to
display the E123actual motor temperature, HOWEVER, it will still the protects the system
and shuddown at and above temperature 180 deg. C.

** Parameter changes to suit STANDARD THERMISTOR modification:

- P380.1 = 0
- P381.1 = 1 (=1 to make the input to the CUVC of 1.5 Kohms when temperature is 180
deg. C)
- P385 = DE-ACTIVATED (automatically)
MKIII and Siemens MasterDrive F21 GA50VSD - CU2 Motor I2t. Parameterized limit value of the i2t - Check P363 Mot.temp T1
monitoring for the motor was excedded
MKIII and Siemens MasterDrive F23 GA50VSD - CU2 Inverter Temp. The temperature limit of the inverter has been exceeded. - Check fan E1 is working, and in the correct direction
- Temperature sensor at -X30
r949 = 1 The temp. limit of the inverter has been exceeded
r949 = 2 Sensor 1: Wire break in the sensor wire or sensor defect
r949 = 18 Sensor 2: ""
r949 = 34 Sensor 3:

MKIII and Siemens MasterDrive F243 MasterDrive VSD Link Internal Fault in internal linking. One of the two linked partners does not reply. Replace Cuxx (-A10)
MKIII and Siemens MasterDrive F25 GA50VSD - CU2 UCE ph. L1 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L1 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 1 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted

When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.
- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.

PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-

ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.
NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
MKIII and Siemens MasterDrive F255 MasterDrive VSD Fault in EEPROM A fault has occurred in the EEPROM Switch off the unit and switch it on again. If the fault re-occurs, replace the Cuxx
MKIII and Siemens MasterDrive F26 GA50VSD - CU2 UCE ph. L2 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L2 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 1 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted

When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.

If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.
- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.

PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-

ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.

- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.

NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
MKIII and Siemens MasterDrive F27 GA50VSD - CU2 UCE ph. L3 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L3 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 1 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted

When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.
- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.

PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-

ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.
NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
MKIII and Siemens MasterDrive F28 GA50VSD - CU2 Supply phase The frequency and amplitude of the DC link ripple indicates a single phase supply - Check supply voltage
CUVC failure. - Check the proper connection at the line reactor (L1)
- Check if one of the coils of line reactor L1 is short circuit.
Similar to F8

MKIII and Siemens MasterDrive F29 GA50VSD - CU2 Measured Valued Sensor Fault occurs in the measured value sensing system - Possibly, CU is faulty
CUVC r949 = 1 Offset adjustment not possible in phase L1 - IGBT or IGD may be defective as it is conductive while signal command does not tell it
r949 = 2 Offset adjustment not possible in phase 3 to do so.
r949 = 3 Offset adjustment not possible in Phases 1 & 3 - Defective phase section
r949 = 65 The analog inputs cannot be automati

MKIII and Siemens MasterDrive F3 Siemens CCU - Simovert P Undervoltage DC-link voltage (ULC) too low. - Reprogam Mark III and put in ARAVF.
GA90VSD One phase missing Possibly caused by a voltage dip - Check DC link voltage during operation which should be around 1.34 x Supply voltage.
Line power failure. Phase failure - Check fuses.

MKIII and Siemens MasterDrive F30 Siemens CCU - Simovert P - Operator Panel Fault Dummy plug for the keypad not (properly) engaged, or PMU controller missing - Check and make sure this plug is engage via dummy plug of the hand held controller
6SE13 . . . (PMU)
GA90VSD
MKIII and Siemens MasterDrive F35 VSD - Siemens CUVC / CU2 External fault 1 - External fault 1 has been triggered =F136- Check cabinet for ventilation
- Check for loose connections
- 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

P575 Src No ExFault1

MKIII and Siemens MasterDrive F36 AIF VSD - Siemens CUVC External fault 2 - External fault 2 has been triggered The problem probably does not related to the Masterdrive converter, and because it
ZT37VSD - This failure can be caused by a wrong or loose connection from the micromaster receives faulty signals from the external, hence EXTERNAL FAULT #2 comes up. Should
(fan motor control ) to the main convertor (main motor control). GA180VSD and check for problems outside the main converter.
others which have micromaster
- Aux. Drive Fault. ZT37VSD - GA180VSD and related compressors with VSD cooling fans. Check that the connection
between the masterdrive and the micromaster is located at pins 19 - 20 on the
masterdrive, and on pins 3 - 4 on the micromaster.
Also, very important to note that on a very HOT day, the micromaster also may
experience overtemperature problem, and therefore would malfunction, and the
Masterdrive converter will register fault F36 (or F036). There may be a fault message on
the micromaster itself, however, this fault message will only registered as an external
fault via the Masterdrive to the elektronikon.
- Therefore, should try to improve the air temperature within the cabinet to eliminate
this fault.
- ZT37VSD: (this may apply to others which have Micromasters drive as well) ARAVF,
everything else was re-started except the micromaster, hence giving F36. Solution was to
set Parameter P15 --- 0 to disabled, and 1 to enabled, and Parameter P18 --- 0 to
disabled and 1 to enabled. Take note when programming the Micromaster, the
parameters P7 = 1 and P9 = 3 for keypad accessibility.

- GA180VSD W (watercool): F36 indicates that the auxiallary drive has a fault. This
auxiallary drive is the positioner Y40 that regulates the By-Pass Oil Cooler solenoid valve.
Please check the status of this positioner. Pay attention to the connections, the OPEN &
CLOSE limit switches. If nothing is found, probably needs a new positioner. Atlas Part No.
1089 0652 01.

In an EMERGENCY, this by-pass oil cooler solenoid valve may be overwritten to allow the
compressor to continue running. The valve has to be overwritten mechanically,
electrically and on Siemens converter.
Mechanically: By turning to hand knob
Electrically: By disconnecting the power to the positioner, please consult electrical
diagram for confirmation of wire number, typically it should be wire labelled No. 2.
Disconnect the active wire only is sufficient.
Siemens Converter: Before any programming is done, make sure that P053 = 0006 for
general access to parameter changes. Go to P586, and change P586.1 from 601 to 001.
P586.1 = Parameter P586, first index. To access to P586.1, please go to P586, then press
P, and .001 shows up, press P again to access first index and scroll up (or down) to get to
the right value. (This is much simpler, if you are using the Simovis Software.)
- There is a thermal switch at the CUVC card of Siemen's converter, at X101, pin 3-4. This
MKIII and Siemens MasterDrive F37 Elektronikon Mk III - AC-Line Fault Line Failute detected; in the "Ready" and "On" states, and alarm is output initially Wifh power supply and contactors that switches the power supply.
GA90VSD Simovert P 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

MKIII and Siemens MasterDrive F40 Siemens CU2, CUVC AS internal fault Incorrect operating status Replace CU card (A10)
GA50VSD
MKIII and Siemens MasterDrive F41 Siemens CU2, CUVC EEPROM fault A fault has occurred when storing the values in the EEPROM Replace CU card (A10)
GA50VSD
MKIII and Siemens MasterDrive F42 Siemens CU2, CUVC Computing time problem Calculating time problem Reduce the calculating time by:
GA50VSD
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

MKIII and Siemens MasterDrive F43 Siemens CU2, CUVC Coupling int. Internal coupling error. One of the two coupling partners does not respond - Check MWH - CU2 connection
GA50VSD - Replace CU card (A10)
MKIII and Siemens MasterDrive F44 Siemens CU2, CUVC BiCo manager Fault - A fault has occurred during the softwiring of Binectors and Connectors - Reparameterize
GA50VSD - Reset unit
- Replace CU card (A10)

In CUVC, observe r949:

> 1000: Fault during softwiring of connectors
> 2000: Fault during softwiring of binectors

MKIII and Siemens MasterDrive F45 Siemens CU2, CUVC Opt. Board HW Hardware fault has occurred when assessing an optional board - Replace CU (A10)
GA50VSD - Check connection of the board and optional boards.
MKIII and Siemens MasterDrive F46 Siemens CU2, CUVC Par task / con. A fault has occur during the transfer of parameters to the gating unit processor - Power unit down and up again
GA50VSD - Replace CU (A10)
MKIII and Siemens MasterDrive F47 Siemens CU2, CUVC Gating Calc Time / internal Comp. Time The calculating time in the gating unit computer is not sufficient Replace CU (A10)
GA50VSD
MKIII and Siemens MasterDrive F5 Siemens CCU - Simovert P - Overvoltage Line voltage too high, extreme generator operation, ramp down rate too fast.
6SE13 . . .
GA90VSD
MKIII and Siemens MasterDrive F6 Siemens CCU - Simovert P - Heat Sink Temp Too high temperature inside converter. Inadequate cooling - Check operation of cooling fan, as well as power supply (380V) over K5 towards these
6SE13 . . . fans
GA90VSD - Check for polluted heat sink
MKIII and Siemens MasterDrive F7 Siemens CCU - Simovert P - Motor Overtemp Motor overtemp. (PTC thermistor term. X13:24/25), motor overload - Check resistance value of both sets of thermistors which should be < 500 ohm at 20
6SE13 . . . Deg.C
GA90VSD 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

MKIII and Siemens MasterDrive F8 GA50VSD - CU2, CUVC CU: DC voltage too low CU: DC voltage was too low, ie 76% x line voltage x 1.34 was not reached CU:- Voltage dips might be the reason, Reprogram the MKIII with latest service software
GA90VSD - CCU / Simovert CCU: Pulsed Res Temp and put ARAVF active.
- Check DC link voltage during operation through r006 on the Siemens PMU
- IGBT or IGD1 defective is possibility. Maybe loose or bad connection.
See F008

CCU: - Pulsed Resistor or electronics overheating, ambient temp too high. Cooling fan
may be defective
MKIII and Siemens MasterDrive Internal Fault # 1 Elektronikon Mk IV - II or System input Error An I/O is missing from the module after programming. Check with FSP, or reprogram the module and make sure all necessary I/O are declared.
Higher The error 1 indicates that the master expects an extra extension module which is
not found or recognized on the system.
ABB ACS600 "Blank Screen" All Mk III Elektronikons No power to display of Elektronikon Faulty Board, loose connections (ribbon cables) inside. Check the module for loose connection.
If no loose connection is found, chances are the diode that controls the power supply to
the display is gone. It is not recommended to repair them, because whilst repairing,
there is a chance of disturbing neighbour

ABB ACS600 100 Elektronikon Mk III, LRR Register file error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III, if all else fails
V1.8, 2.3
ABB ACS600 101 Elektronikon Mk III, LRR RAM error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III, if all else fails
V1.8, 2.3
ABB ACS600 102 Elektronikon Mk III, LRR 12V relay not disabled at power on Relay possible damaged due to incorrect power input Replace Elektronikon Mk IIIMk III, if all else fails
V1.8, 2.3
ABB ACS600 103 Elektronikon Mk III, LRR Relays status uncorrect at power on Relay possible damaged due to incorrect power input Replace Elektronion, if all else fails
V1.8, 2.3 Unrecoverable failures generated by the regulator.
ABB ACS600 104 Elektronikon Mk III LRR V1.8, Short circuit on 12V (relays and digital inputs) OR In Most cases, attributed to a voltage coming in through one of the digital inputs. These failures are used to signal some dangerous situation caused by hardware or
2.3, HRR 12V enabling FET damaged But digital inputs are voltage free contacts. software problems.
Chances are FET, and or diodes had gone. Possible what happen here is when the Check 2x1 connector. Possibly, the FET, inductor (the green resistor lookalike), or diode
connector is put upside down, and when 24V is gone here, due to reverse biased of power.

Also, check othe

ABB ACS600 106 Elektronikon Mk III, LRR Relays enable at power on Relay possible damaged due to incorrect power input - Power down the regulator.
V1.8, 2.3 - Inconsistency between the status of the relays and - Elektronikon is not powered up. Only one contact (out of three) of the Emergency - Check the Emergency stop button.
HRR the status that the relay should be in. stop button is activated. Power is restored to the Elektronikon. At this moment the * Make sure all wires connected firmly and no bad contacts are existing.
power supply to the internal relays * All the components of the Emergency stop button (base and contacts) should have
the same colour (black or brow

ABB ACS600 107 Elektronikon Mk III, LRR Serial line error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III, if all else fails
V1.8, 2.3
ABB ACS600 108 Elektronikon Mk III, LRR Keyboard error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III, if all else fails
V1.8, 2.3
ABB ACS600 109 Elektronikon Mk III, LRR V Filter error (relay ouputs read-back not stable)
2.3
ABB ACS600 10XX Elektronikon Mk III - (Online) Read back output error
LRR/HRR
ABB ACS600 11 Elektronikon Mk III, LRR V1.8: Most porbably due to a short circuit of the 12V supply for the digital inputs For example, when this module being use for remote control. As two digital inputs were
V1.8, 2.3, HRR EEprom not writable Unrecoverable failures generated by the regulator. closed, please check which one is causing the failure 11. Is it the CMS 2 as from when it is
V2.3: closed or is it 30 & 34 contact.
Relays supply error
If nothing is found, then change the mod

ABB ACS600 11XX Elektronikon Mk III - HRR (Online) 12V short circuit or FET to enable damaged

ABB ACS600 12 Elektronikon Mk III, LRR V1.8: Unrecoverable failures generated by the regulator. Hardware or software problem
V1.8, 2.3 Division by zero Replace Elektronikon Mk III
V2.3:
EEprom not writable

ABB ACS600 13 Elektronikon Mk III, LRR V1.8: Unrecoverable failures generated by the regulator. Hardware or software problem
V1.8, 2.3 Wrong active display, V2.3: Replace Elektronikon Mk III
EEprom checksum error
ABB ACS600 14 Elektronikon Mk III, LRR V1.8: Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III
V1.8, 2.3 Relays supply error, V2.3: Internal error
Eprom checksum error
ABB ACS600 15 Elektronikon Mk III, LRR V Wrong active display Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III
2.3
ABB ACS600 17 Elektronikon Mk III, LRR V1.8 Watch dog error Some external conditions were not met while system was checking for operation. 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
Recoverable failure. through the reset function key of the system failure display.

Check external par

ABB ACS600 200 Elektronikon Mk III, LRR V Watch dog error. 200XX (bootstrap) These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR compressor can start after the failure reset. failure display.
ABB ACS600 2000 Elektronikon Mk III - (Bootstrap) Reserved area checksum incorrect Hardware or software problem. Possibly need a new regulator
LRR/HRR
ABB ACS600 2001 Elektronikon Mk III - HRR (Bootstrap) Reserved area checksum incorrect Unrecoverable error. Caused by corruption within the electronics to misread. Try to power OFF and ON again. If cannot resolved, then try a new module.

ABB ACS600 201 Elektronikon Mk III, LRR V Internal power failure routine not completed These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR 201xx(bootstrap) compressor can start after the failure reset. failure display.
ABB ACS600 202 Elektronikon Mk III, LRR V Backupped RAM checksum error These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR 202xx(bootstrap) compressor can start after the failure reset. failure display.
ABB ACS600 203 Elektronikon Mk III - HRR Power off during EEPROM writing These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
203xx (bootstrap) compressor can start after the failure reset. failure display.
ABB ACS600 204 Elektronikon Mk III - HRR Power off during EEPROM writing and power failure These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
interrupt routine enabled compressor can start after the failure reset. failure display.
204xx(bootstrap)
ABB ACS600 205 Elektronikon Mk III - HRR Power off during EEPROM writing and backup ram These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
checksum incorrect. compressor can start after the failure reset. failure display.
ABB ACS600 20XX Elektronikon Mk III - HRR (Bootstrap) Reserved area checksum incorrect
ABB ACS600 21XX Elektronikon Mk III - HRR (Bootstrap) EPROM checksum incorrect
ABB ACS600 22 Elektronikon Mk III, LRR V1.8 Eprom checksum error Internal error Replace Elektronikon Mk III, if all else fails
Unrecoverable failures generated by the regulator.
ABB ACS600 22XX Elektronikon Mk III - HRR (Bootstrap) Flash checksum incorrect
ABB ACS600 30XX Elektronikon Mk III - HRR (Online) Division by 0
ABB ACS600 30XX Elektronikon Mk III, LRR Relay outputs read-back error Relay damaged, internal error - Power down the regulator.
V1.8, 2.3, HRR - Inconsistency between the status of the relays and Unrecoverable failures generated by the regulator. - Check the Emergency stop button.
the status the relays should be in - Compressor is running or standing still. Regulator is powered up. Only one * Make sure all wires connected firmly and no bad contacts are existing.
contact (out of three) of the Emergency stop button is activated. This means that * All the components of the Emergency stop button (base and contacts) should have
the power suppl the same colour (black or brow

ABB ACS600 31XX Elektronikon Mk III - HRR (Online) Wrong activated display
ABB ACS600 33 Elektronikon Mk III, LRR V1.8 Eeprom checksum error Internal error Replace Elektronikon Mk III, if all else fails
Unrecoverable failures generated by the regulator.
ABB ACS600 40 Elektronikon Mk III - HRR (Autoconfig) No delivery air input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

ABB ACS600 41 Elektronikon Mk III - HRR (Autoconfig) More than 1 delivery air input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

ABB ACS600 42 Elektronikon Mk III - HRR (Autoconfig) More than 1 backup pressure input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

ABB ACS600 43 Elektronikon Mk III - HRR (Autoconfig) More than 1 intercooler pressure input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

ABB ACS600 44 Elektronikon Mk III - HRR (Autoconfig) More than 4 DIOE modules connected These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

ABB ACS600 45 Elektronikon Mk III - HRR (Autoconfig) More than 4 SIOE modules connected These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

ABB ACS600 46 Elektronikon Mk III - HRR (Autoconfig) More than 3 COM1 modules These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
connected one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

ABB ACS600 47 Elektronikon Mk III - HRR (Autoconfig) More than 2 COM3 modules These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
connected one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

ABB ACS600 48 Elektronikon Mk III - HRR (Autoconfig) COM3 not permitted in configuration These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

ABB ACS600 49 Elektronikon Mk III - HRR (Autoconfig) SIOE module not permitted in These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
configuration one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

ABB ACS600 50 Elektronikon Mk III - HRR (Autoconfig) Wrong CCM during autoconfiguration These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
(CMS1, CMS2) one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Please check to make sure CMS is in correct position

ABB ACS600 51 Elektronikon Mk III - HRR (Autoconfig) DIOE type configured is for ES100 These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
system one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Please check for the right module.

ABB ACS600 7001 Elektronikon Mk III HRR / (Online) Internal communication failed Internal communication between master and a com. Module - Check the cable for connection between the 2 modules
VSD - Check the power supply to the modules (24V)

- 700X, where X = the com module no., for example, 7001 implies no. 1 module is not
communicating with Master module. 7002 implies no. 2 module is not co

ABB ACS600 70XX Elektronikon Mk III HRR / (Online) Internal communication failed Internal communication between master and com. Module - Check the cable for connection between the 2 modules
VSD - Check the power supply to the modules (24V)

- 700X, where X = the com module no., for example, 7001 implies no. 1 module is not
communicating with Master module. 7002 implies no. 2 module is not c

ABB ACS600 7101 Elektronikon Mk III HRR / (Online) A module in INOPERATIVE UNLOCK was Module 01 became inoperative and it was connected to another operative module Try to reprogram the modules and check the start configuration
VSD connected to an OPERATIVE regulator
ABB ACS600 71XX Elektronikon Mk III HRR / (Online) A module in INOPERATIVE UNLOCK was Module XX became inoperative and it was connected to another operative module Try to reprogram the modules and check the start configuration
VSD connected to an OPERATIVE regulator
eg. ZR315VSD with COM2 modbus module
F71XX ==> 01 = fault @ module 01 (module 01 = SIOE module)
==> 02 = fault @ module 02 (module 02 = VSD's COM2)
==> 03

ABB ACS600 7201 Elektronikon Mk III HRR / (Online) A module in INOPERATIVE LOCK was Module 01 (COM module) is inoperative by incorrect programming or by Try to reprogram
VSD connected to an INOPERATIVE or OPERATIVE connecting an empty module.
regulator
ABB ACS600 72XX Elektronikon Mk III HRR / (Online) A module in INOPERATIVE LOCK was Module 01 (COM module) is inoperative by incorrect programming or by Try to reprogram
VSD connected to an INOPERATIVE or OPERATIVE connecting an empty module.
regulator
ABB ACS600 7301 Elektronikon Mk III - HRR / Communication error between Elektronikon (Com - Loose connection between Com 2 and ABB converter - Switch machine OFF then back ON again. Allow a few mins for all power inside
VSD 2) and converter - Com 2 defective. electronics to dissipate.
ABB - COM 2 was not properly earthed. .
- Check connections of converter / COM module
- NIOC board (of ABB drive) defective,
- Isolate converter from COM module, and use VSD simulation software to test whether
- Modbus adapter model is defective COM module or co
ABB ACS600 7401 Elektronikon Mk III - HRR / (Online) Incorrect format in data send from Error 0 - incorrect data format (byte 6/7, readback status) - Switch machine OFF then back ON again. Allow a few mins for all power inside
VSD converter to regulator Error 100 - incorrect data format (byte 2/3/8/9, parameters) electronics to dissipate.
ABB Error 200 - Checksum failure - Reprogam the converter.
Siemens VSD: A possible fault would that some data in EPROM is lost, or
corrupted, or during programming, - Check parameters, compare with list and adjust any discrepancies

ABB ACS600 7402 Elektronikon Mk III - HRR / (Online) Incorrect format in data send from Error 0 - incorrect data format (byte 6/7, readback status) - Switch machine OFF then back ON again. Allow a few mins for all power inside
VSD converter to regulator Error 100 - incorrect data format (byte 2/3/8/9, parameters) electronics to dissipate.
ABB Error 200 - Checksum failure - Reprogam the converter.
Siemens VSD: A possible fault would that some data in EPROM is lost, or
corrupted, or during programming, - Check parameters, compare with list and adjust any discrepancies

ABB ACS600 74XX Elektronikon Mk III - HRR / (Online) Incorrect format in data send from Error 0 - incorrect data format (byte 6/7, readback status) - Switch machine OFF then back ON again. Allow a few mins for all power inside
VSD converter to regulator Error 100 - incorrect data format (byte 2/3/8/9, parameters) electronics to dissipate.
ABB Error 200 - Checksum failure - Reprogam the converter.
Siemens VSD: A possible fault would that some data in EPROM is lost, or
corrupted, or during programming, - Check parameters, compare with list and adjust any discrepancies

ABB ACS600 FAULT: ACS 600 TEMP ABB VSD Internal temperature is excessive The ACS 600 internal temperature is excessive. The trip level of inverter module - Check ambient conditions
temperature is 125 deg. C - Check air flow and fan operations
- Check heatsink fins for dust pick-up
- Check motor power against unit power

ABB ACS600 FAULT: Al < MIN FUNC ABB VSD Analog signal is below allowed value An analogue control signal is below minimum allowed value. This can be caused by - Check for proper analog control signal levels
incorrect signal level or a failure in the control wiring. - Check the control wiring
- Check Al < MIN FUNC Fault Function parameters
Programmable Fault Function 30.01

ABB ACS600 FAULT: AMBIENT TEMP ABB VSD I/O Control board temperature is lower than -5 … 0 deg. C or exceeds +73 … 82 - Check air flow and fan operation
deg. C
ABB ACS600 FAULT: COMM MODULE ABB VSD Communication error Cyclical communication with ACS 600 and fieldbus/ACS 600 Master is lost - Check the status communication. See Appendix C
- Check the parameter settings:
* Group 51 (for CH0 fieldbus adapter), or
* Group 52 (for Standard Modbus Link)

- Check cable connections

- Check if the bus master is not communicating or configured.

ABB ACS600 FAULT: CURR MEAS ABB VSD Current transformer failed Current transformer failure in output current measurement circuit. - Check the current transformer connected to Main Circuit Interface Board, NINT.
ABB ACS600 FAULT: DC OVERVOLT ABB VSD DC Voltage is excessive Intermediate circuit DC voltage is excessive. DC overvoltage trip limit is 1.3 U1max, - Check that the overvoltage controller is on (parameter 20.05)
where U1max is the maximum value of the mains voltage range. For 400 V units, - Check mains for static or transient overvoltage
U1max is 415V. The actual voltage in the intermediate circuit corresponding to the - Check Braking Chopper and Resistor (if used)
mains vo - Check decelaration time

Usin Coasting to Stop function (if applicable)

Retrofit the frequen

ABB ACS600 FAULT: DC UNDERVOLT ABB VSD DC Voltage is not sufficient Intermediate circuit DC voltage is not sufficient. This can be caused by a missing - Check mains supply and fuses.
mains phase, a blown fuse or a bridge internal fault
DC undervoltage trip limit is 0.65 U1min, where U1min is the minimum value of
the mains voltage range. For 400 V and 5

ABB ACS600 FAULT: EARTH FAULT ABB VSD Load imbalance The load on the incoming mains system is out of balance. This can be caused by a - Check motor
fault in the motor, motor cable or an internal malfunction. - Check motor cable
- Check there are no power factor correction capacitors or surge absorbers in the motor
cable.
Programmable Fault Function 30.17

ABB ACS600 FAULT: EXTERNAL FLT ABB VSD External fault There is a fault in one of the external devices. - Check external devices for faults
(This information is configured through one of the programmable digital inputs.) - Check Parameter 30.03 EXTERNAL FAULT

ABB ACS600 FAULT: I/O COMM ABB VSD Communication error A communication error has occurred on the NAMC board, channel CH1 - Check the connections of the fibre optic cables on NAMC channel CH1
- Check all I/O modules (if present) connected to channel CH1
Electronmagnetic interference. - Check for proper earthing of the equipment.
- Check for highly emissive components nearby.
There is an internal fault on the NIOC board. - Replace the NIOC board.

ABB ACS600 FAULT: ID RUN FAIL ABB VSD ID Run not successful The motor ID Run is not completed successfully - Check the maximum speed (Parameter 20.02). It should be at least 80% of the nominal
speed of the motor (Parameter 99.08)
ABB ACS600 FAULT: IN CHOKE TEMP ABB VSD Excessive heat Excessive input choke temperature - Stop drive and let it cool down. Check ambient temperature.
- Check air flow and fan rotation direction
ABB ACS600 FAULT: LINE CONV ABB VSD Fault on the line side converter Shift the Panel from the motor side converter control board to line side converter
control board.
See the line side converter manual for the fault description

ABB ACS600 FAULT: MOTOR 1 TEMP ABB VSD Measured motor temp has exceeded fault limit set Possible causes: - Check the wiring of the temperature measurement (+ connections PT100)
by parameter 35.03 (150deg C) - Faulty thermistor - Check the value of the fault limit. Ensure proper motor cooling: check cooling fan,
- loose / broken connection of thermistor (PT100) cable clean cooling surfaces, etc.
- Motor is hot - Check the PT100 resistance off-circuit. Ie, unplug from the NIOC-

ABB ACS600 FAULT: MOTOR 2 TEMP ABB VSD Measured motor temp has exceeded fault limit set Possible causes: Check the wiring of the temperature measurement (+ connections PT100)
by parameter 35.06 (110deg C) - Faulty thermistor
- loose / broken connection of thermistor (PT100) cable
- Motor is hot

ABB ACS600 FAULT: MOTOR PHASE ABB VSD One of the phase is lost This can be caused by a fault in the motor, the motor cable, a thermal relay (if - Check motor and motor cable
used) or an internal fault. - Check thermal relay (if used)
- Check MOTOR PHASE Fault Function parameters. Disable this protection

Programmable Fault Function 30.16 (ACC: 30.10)

- Check power supply TO motor. May be a phase is missing
ABB ACS600 FAULT: MOTOR STALL ABB VSD Motor is operating in stall region This can be caused by excessive load or insufficient motor power - Check motor load and the ACS 600 ratings.
- Check MOTOR STALL Fault Function parameters.

Programmable Fault Function 30.10 … 30.12

- Check power supply TO motor. May be a phase is missing

ABB ACS600 FAULT: MOTOR STALL ABB VSD Motor is operating in the stall region Excessive load or insufficient motor power - Motor overload
- Seized element
- Check fault function parameters for further details
- Faulty bearings
- Check power supply TO motor. May be a phase is missing

ABB ACS600 FAULT: MOTOR TEMP ABB VSD Motor temperature too high Motor temperature is too high (or appears to be too high). This can be caused by - Check motor ratings and load
excessive load, insufficient motor power, inadequate cooling or incorrect start-up - Check start - up data
data. - Check MOTO TEMP Fault Function parameters
Programmable Fault Function 30.04 … 30.09

ABB ACS600 FAULT: NO MOT DATA ABB VSD Motor data not given / not avail. Motor data is not given or motor data does not match with inverter data - Check the motor data given by Parameters 99.04 … 99.09
ABB ACS600 FAULT: OVERCURRENT ABB VSD Output current is excessive Output current is excessive. The software overcurrent trip limit is 3.5 * I 2hd - Check motor load
- Check acceleration time.
- Check motor and motor cable (including phasing)
- Check there are no power factor correction capacitors or surge absorbers in the motor
cable.
- Check encoder cable (including phase)

ABB ACS600 FAULT: OVERFREQ ABB VSD Motor is turning faster then allowed Motor is turning faster than the highest allowed speed. This can be caused by an - Check minimum/maximum speed settings
incorrectly set minimum/maximum speed, insufficient braking torque or changes - Check adequacy of motor braking torque
in the load when using torque reference. - Check applicability of torque control
- Check the need for a Braking Chopper and Resistor(s)
The trip level is 40Hz over the operating range absolu
- Make sure all the parameters in the group 99 START-UP DATA are correct, and c

ABB ACS600 FAULT: PANEL LOSS ABB VSD Loss of communication A Control Panel or Drives Window selected as active control location for the ACS - Check the Panel is connected to the right connector (see manual)
600 has ceased communicating. - Check Control Panel connector
- Re-insert Control Panel in the mounting platform
- Check PANEL LOSS Fault Function parameters.
- Check DriveWindow connection
Programmable Fault Function

ABB ACS600 FAULT: PPCC LINK ABB VSD Fibre optic link is faulty The fibre optic link to the NINT board is faulty - Check the fibre optic cables connected to the power plates.
ABB ACS600 FAULT: RUN DISABLE ABB VSD No "Run enable" signal received - Check setting of parameter 16.01
- Check connection X22:8-11
ABB ACS600 FAULT: SC (INU 1) ABB VSD Short circuit in the inverter Short circuit in the inverter unit consisting of several parallel inverter modules. - Check the motor and motor cable.
Number refers to the faulty inverter module number. - Check the power semiconductors (IGBT power plates) of the inverter module. (INU 1
stand for inverter module 1, etc)
NINT board fibre optic connection fault in inverter unit consisting of several
parallel inverter modules. Number refer - Check the connection from the inverter module Main Circuit Interface Board, NINT to
the PPCC Branch

ABB ACS600 FAULT: SC (INU 2) ABB VSD Short circuit in the inverter Short circuit in the inverter unit consisting of several parallel inverter modules. - Check the motor and motor cable.
Number refers to the faulty inverter module number. - Check the power semiconductors (IGBT power plates) of the inverter module. (INU 1
stand for inverter module 1, etc)
NINT board fibre optic connection fault in inverter unit consisting of several
parallel inverter modules. Number refer - Check the connection from the inverter module Main Circuit Interface Board, NINT to
the PPCC Branch

ABB ACS600 FAULT: SC (INU 3) ABB VSD Short circuit in the inverter Short circuit in the inverter unit consisting of several parallel inverter modules. - Check the motor and motor cable.
Number refers to the faulty inverter module number. - Check the power semiconductors (IGBT power plates) of the inverter module. (INU 1
stand for inverter module 1, etc)
NINT board fibre optic connection fault in inverter unit consisting of several
parallel inverter modules. Number refer - Check the connection from the inverter module Main Circuit Interface Board, NINT to
the PPCC Branch

ABB ACS600 FAULT: SC (INU 4) ABB VSD Short circuit in the inverter Short circuit in the inverter unit consisting of several parallel inverter modules. - Check the motor and motor cable.
Number refers to the faulty inverter module number. - Check the power semiconductors (IGBT power plates) of the inverter module. (INU 1
stand for inverter module 1, etc)
NINT board fibre optic connection fault in inverter unit consisting of several
parallel inverter modules. Number refer - Check the connection from the inverter module Main Circuit Interface Board, NINT to
the PPCC Branch

ABB ACS600 FAULT: SHORT CIRC ABB VSD Short circuited Short circuit in the motor cable(s) or motor - Check the motor and motor cable
- Check there are no power factor correction capacitors or surge absorbers in the motor
The output bridge of the converter unit is faulty cable.

Contact ABB

ABB ACS600 FAULT: START INHIBIT ABB VSD Optional start inhibit hardware logic is activated. - Check the start inhibit circuit (NGPS board)
ABB ACS600 FAULT: START INTERLOCK ABB VSD No "Start Interlock" signal received - Check connections 8-11 (X22) and 7-1 (X22)
ABB ACS600 FAULT: SUPPLY PHASE ABB VSD DC Voltage is oscillating Intermediate circuit DC voltage is oscillating. This can be caused by a missing mains - Check main fuses
phase, a blown fuse or a rectifier bridge internal fault. - Check for mains supply imbalance

A trip occurs when the DC voltage ripple is 13 % of the DC voltage - Maybe motor overload. Check !! = = > fuse blown
The problem is more probable when the moto - Mains supply contactor. Check all three contacts

- When the machine is running at various frequency, then all the sudden shutdown, but
the supply
ABB ACS600 FAULT: THERMISTOR ABB VSD Motor thermal protection fault Motor thermal protection mode selected as THERMISTOR and the temperature is - Check motor ratings and load
excessive. - Check start-up data
- Check thermistor connections for digital input DI6
- Check thermistor cabling

Programmable Fault Function 30.04 .. 30.05

ABB ACS600 FAULT: UNDERLOAD ABB VSD Motor load too low Motor load is too low. This can be caused by a release mechanism in the driven - Check for a problem in the driven equipment
equipment - Check UNDERLOAD Fault Function parameters
Programmable Fault Function 30.13 .. 30.15

ABB ACS600 FAULT: USER MACRO ABB VSD There is np User Macro saved or file is defective Create the User Macro again
ABB ACS600 WARNING: ACS 600 TEMP ABB VSD High Temp warning The ACS 600 internal temperature is excessive. A warning is given if inverter - Check ambient conditions.
module temp. exceds 115 deg. C - Check air flow and fan operation
- Check heatsink fins for dust pick-up
- Check motor power against unit power

ABB ACS600 WARNING: Al < MIN FUNC ABB VSD Analog control signal below min. allow An analogue control signal is below minimum allowed value. This can be caused by - Check for proper analogue control signal levels.
incorrect signal level or a failure in the control wiring. - Check the control wiring
- Check Al < MIN FUNC Fault Function parameters.
ABB ACS600 WARNING: COMM MODULE ABB VSD Communication error between ACS 600 fieldbus Cyclical communication between ACS 600 and fieldbus/ACS 600 Master is lost. - Check the status of fieldbus communication. See Appendix C - Fieldbus control
and ACS 600 Master - Check the parameter settings:
* Group 51 (for CH0 fieldbus adapter), or
* Group 52 (for standard Modbus Link)

- Check cable connections

- Check if the bus master is not

ABB ACS600 WARNING: DOWNLOAD ABB VSD Download failed Download function of the panel has failed. No data has been copied from the Make sure the Panel is in local mode
FAILED Panel to the ACS 600.
Retry (there might be interference on the link)

Contact ABB

ABB ACS600 WARNING: DRIVE ABB VSD Program and Panel do not match Program versions in the Panel and in the ACS 600 do not match. It is not possible Check program version
INCOMPATIBLE to copy data from Panel to the ACS 600
DOWNLOADING NOT POSS. (See parameter group 33 )

ABB ACS600 WARNING: DRIVE RUNNING ABB VSD Drive is running, download not possible Downloading is not possible while the motor is running. Stop the motor. Perform the downloading
DOWNLOAD NOT POSS.

ABB ACS600 WARNING: ENCODER ERR ABB VSD Communication fault Communication fault between the pulse encoder and the NTAC module or - Check the pulse encoder and its wiring, the NTAC module, Parameter Group 50 settings
between the NTAC module and the ACS 600 and the fibre optic connections on NAMC channel CH1
ABB ACS600 WARNING: ID DONE ABB VSD ID Run done, and ready for operation The ACS 600 has performed the Identification Run and is ready for operation. This Continue drive operation.
warning belongs to the ID Run procedure
ABB ACS600 WARNING: ID DONE ABB VSD Motor ID magnetisation is done and ready for The ACS 600 has performed the motor id magnetisation and is ready for operation. Continue drive operation.
operation This warning belongs to the normal start-up procedure.
ABB ACS600 WARNING: ID MAGN ABB VSD Motor ID magnetisation is on. Motor identification magnetisation is on. This warning belongs to the normal start- Wait until the drive indicates that motor identification is completed.
up procedure.
ABB ACS600 WARNING: ID MAGN REQ ABB VSD Motor identification magnetisation required. Motor identification magnetisation is required. This warning belongs to the normal To Start the ID magnetisation:
start-up procedure. The drive expects the user to select how the motor - Press the Start Key
identification is to be performed: By ID magnetisation or by ID Run. - To Start the ID Run procedure:
* Select the Identification Run type (See Parameter 99.10 MOTOR ID Run).
This is usually happen when the

ABB ACS600 WARNING: ID N CHANGED ABB VSD ID Number has been changed The ID number of the drive has been changed from 1 in Drive Selection Mode (the To change the ID number back to 1 go to Drive Selection Mode by pressing DRIVE. Press
change is not shown on the display) ENTER. Set the ID number to 1. Press ENTER.
ABB ACS600 WARNING: ID RUN ABB VSD ID Run is on Motor Identification Run is on. Wait until the drive indicates that Identication Run is completed.
ABB ACS600 WARNING: ID RUN SEL ABB VSD Motor ID Run is selected Motor ID Run is selected, and the drive is ready to start the ID Run. This warning Press Start key to start the Identification Run
belongs to the ID Run procedure
ABB ACS600 WARNING: MACRO CHANGE ABB VSD MACRO is being saved Please wait

ABB ACS600 WARNING: MOTOR STALL ABB VSD Motor is operating in stall region Motor is operating in the stall region. This can be caused by excessive load or - Check motor load and the ACS 600 ratings.
insufficient motor power. - Check MOTOR STALL Fault Function parameters.

Progammable Fault Function 30.10

ABB ACS600 WARNING: MOTOR STARTS ABB VSD Motor ID Run Starts Motor Identification Run starts. This warning belongs to the IR Run procedure. Wait until the drive indicates that motor identification is completed.

ABB ACS600 WARNING: MOTOR TEMP ABB VSD Motor temperature too high Motor temperature is too high (or appears to be too high). This can be caused by - Check motor ratings, load and cooling
excessive load, insufficient motor power, inadequate cooling or incorrect start-up - Check start-up data
data. - Check MOTOR TEMP Fault Function parameters.

Programmable Fault Function 30.04 … 30.10

ABB ACS600 WARNING: NO ABB VSD Communication lost There is a cabling problem or hardware malfunction on the Panel Link. - Check the Panel Link connections
COMMUNICATION (X) (4) = Panel type is not compatible with the version of the drive application - Press the RESET key. The panel reset may take up to half a minute.
program. CDP 312 Panel does not communicate with Standard Application
Program (ACS) version 3.x or earlier. - Check the Paenl type and the version of the drive application program. The Panel type
is printed on the cover of the Panel. The application program

ABB ACS600 WARNING: NO FREE ID ABB VSD The Panel Link already includes 31 stations Disconnect another station from the link to free an ID number.
NUMBERS ID NUMBER
SETTING NOT POSS.
ABB ACS600 WARNING: NOT UPLOADED ABB VSD Not uploaded No upload function has been performed Perform the Upload function before downloading.
DOWNLOADING NOT POSS.
ABB ACS600 WARNING: PANEL LOSS ABB VSD Control Panel not communicate with ACS600 A Control panel selected as active control location for the ACS 600 has ceased - Check the Panel is connected to the right connector (See manual)
communicating. - Check Control Panel connector
- Replace Control Panel in the mounting platform.
- Check PANEL LOSS fault function parameters.

Programmable Fault Function 30.02

ABB ACS600 WARNING: THERMISTOR ABB VSD Thermistor warning Motor thermal protection mode selected as THERMISTOR and the temperature is - Check motor ratings and load
excessive - Check start-up data
- Check thermistor connections for digital input DI6 of NIOC board.
Programmable function 30.04 … 30.05

ABB ACS600 WARNING: UNDERLOAD ABB VSD Motor load is too low Motor load is too low. This can be caused by a release mechanism in the driven - Check for a problem in the driven equipment.
equipment. - Check UNDERLOAD Fault Function parameters.

Programmable Fault Function 30.13

ABB ACS600 WARNING: UPLOAD FAILED ABB VSD Upload has failed Upload function of the panel has failed. No data has been copied from the Panel to - Make sure the Panel is in local mode.
the ACS 600. - Retry (there might be interference on the link)
- Contact ABB
ABB ACS600 WARNING: WRITE ACCESS ABB VSD Parameter Access Denied Certain parameters do not allow changes while motor is running. If tried, no Stop the motor then change the parameter value
DENIED PAR. SETT. NOT change is accepted, and a warning is displayed.
POSSIBLE Open parameter Lock (See Parameter 16.02 PARAMETER LOCK)
Parameter Lock is on.

ABB ACS550 1 ACS550 OVERCURRENT Output current is excessive. Check for and correct:
FDVSD • Excessive motor load.
Insufficient acceleration time (parameters 2202 ACCELER TIME 1 and 2205
ACCELER TIME 2). • Faulty motor, motor cables or connections.

ABB ACS550 2 ACS550 DC OVERVOLT Intermediate circuit DC voltage is excessive. Check for and correct:
FDVSD • Static or transient overvoltages in the input pow supply
Insufficient deceleration time (parameters 2203 DECELER TIME 1 and 2206
DECELER TIME 2). • Undersized brake chopper (if present).
• Verify that overvoltage controller is ON (using parameter 2005).

* Check for motor earth fault. Majority of DC Overvoltage is ca

ABB ACS550 3 ACS550 DEV OVERTEMP Drive heatsink is overheated. Temperature is at or above limit. Check for and correct:
FDVSD R1…R4 & R7/R8: 115 °C (239 °F) • Fan failure.
R5/R6: 125 °C (257 °F) • Obstructions in the air flow.
• Dirt or dust coating on the heat sink.
• Excessive ambient temperature.
• Excessive motor load.

ABB ACS550 4 ACS550 SHORT CIRC Fault current. Check for and correct: * Use Multimeter and perform DIODE check....with MAINS POWER off and isolated. Wait
FDVSD • A short-circuit in the motor cable(s) or motor. 10mins before perform this work
• Supply disturbances.
ABB ACS550 5 ACS550 RESERVED Not used.
FDVSD
ABB ACS550 6 ACS550 DC UNDERVOLT Intermediate circuit DC voltage is not sufficient. Check for and correct:• Missing phase in the input power supply.
FDVSD
Blown fuse.

Undervoltage on mains.

ABB ACS550 7 ACS550 AI1 LOSS Check for and correct:

FDVSD • Source and connection for analog input.
• Parameter settings for AI1 FAULT LIMIT (3021) and 3001 AI<MIN FUNCTION.
ABB ACS550 8 ACS550 AI2 LOSS Analog input 2 loss. Analog input value is less than AI2 FAULT LIMIT (3022).
FDVSD Check for and correct:
• Source and connection for analog input.
• Parameter settings for AI2 FAULT LIMIT (3022) and 3001 AI<MIN FUNCTION

ABB ACS550 9 ACS550 MOT OVERTEMP Motor is too hot, based on either the drive’s estimate or on temperature feedback. • Check for overloaded motor.
FDVSD • Adjust the parameters used for the estimate (3005 …3009).
• Check the temperature sensors and Group 35: MOTOR TEMP MEAS
parameters.

ABB ACS550 10 ACS550 PANEL LOSS Panel communication is lost and either: Check:
FDVSD • Drive is in local control mode (the control panel displays LOC), or • Communication lines and connections.
• Drive is in remote control mode (REM) and is parameterized to accept • Parameter 3002 PANEL COMM ERR.
start/stop, direction or reference from the control panel. • Parameters in Group 10: START/STOP/DIR and Group 11:
REFERENCE SELECT (if drive operation is REM).

ABB ACS550 11 ACS550 ID RUN FAIL The Motor ID Run was not completed successfully. Check for and correct:
FDVSD • Motor connections.
• Motor parameters 9905…9909.
ABB ACS550 12 ACS550 MOTOR STALL Motor or process stall. Motor is operating in the stall region. Check for and correct:
FDVSD • Excessive load.
• Insufficient motor power.
• Parameters 3010…3012.

ABB ACS550 13 ACS550 RESERVED Not used.

FDVSD
ABB ACS550 14 ACS550 EXT FAULT 1 Digital input defined to report first external fault is active. See parameter 3003 EXTERNAL FAULT 1.
FDVSD
ABB ACS550 15 ACS550 EXT FAULT 2 Digital input defined to report second external fault is active. See parameter 3004 EXTERNAL FAULT 2.
FDVSD
ABB ACS550 16 ACS550 EARTH FAULT Possible ground fault detected in the motor or motor cables. The drive
FDVSD 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

ABB ACS550 17 ACS550 OBSOLETE Not used.

FDVSD
ABB ACS550 18 ACS550 THERM FAIL Internal fault. The thermistor measuring the internal temperature of the drive is Faulty thermistor. Replace thermistor or Contact your local ABB representative.
FDVSD open or shorted.
ABB ACS550 19 ACS550 OPEX LINK Internal fault. A communication-related problem has been detected on the fiber * Communicationg cable faulty.
FDVSD optic link between the control and OINT boards.
Contact your local ABB representative.
ABB ACS550 20 ACS550 OPEX PWR Internal fault. Low voltage condition detected on OINT power supply. Faulty power card, replace card or complet VSD cabinet
FDVSD
Contact your local ABB representative.
ABB ACS550 21 ACS550 CURR MEAS MEAS Internal fault. Current measurement is out of range. Contact your local ABB Possibly due to CURRENT TRANSFORMER faulty
FDVSD representative.

ABB ACS550 22 ACS550 SUPPLY PHASE Ripple voltage in the DC link is too high. Check for and correct:
FDVSD • Missing mains phase.
• Blown fuse.
ABB ACS550 23 ACS550 ENCODER ERR The drive is not detecting a valid encoder signal. Check for and correct:
FDVSD • Encoder presence and proper connection (reverse wired, loose
connection or short circuit).
• Voltage logic levels are outside of the specified range.
• A working and properly connected Pulse Encoder Interface Module,
OTAC-01.
• Wr

ABB ACS550 24 ACS550 OVERSPEED Motor speed is greater than 120% of the larger (in magnitude) of 2001 Check for and correct:
FDVSD MINIMUM SPEED or 2002 MAXIMUM SPEED. • Parameter settings for 2001 and 2002.
• Adequacy of motor braking torque.
• Applicability of torque control.

ABB ACS550 25 ACS550 RESERVED Not used.

FDVSD
ABB ACS550 26 ACS550 DRIVE ID Internal fault. Configuration Block Drive ID is not valid. Contact your local
FDVSD ABB representative.
ABB ACS550 27 ACS550 CONFIG FILE Internal configuration file has an error. Contact your local ABB
FDVSD representative.
ABB ACS550 28 ACS550 SERIAL 1 ERR Fieldbus communication has timed out. Check for and correct:
FDVSD • Fault setup (3018 COMM FAULT FUNC and 3019 COMM FAULT TIME).
• Communication settings (Group 51: EXT COMM MODULE or Group 53:
EFB PROTOCOL as appropriate).
• Poor connections and/or noise on line.

ABB ACS550 29 ACS550 EFB CON FILE Error in reading the configuration file for the embedded fieldbus.
FDVSD
ABB ACS550 30 ACS550 FORCE TRIP Fault trip forced by the fieldbus. See the fieldbus User’s Manual.
FDVSD
ABB ACS550 31 ACS550 EFB 1 Fault code reserved for the embedded fieldbus (EFB) protocol application.
FDVSD The meaning is protocol dependent.
ABB ACS550 32 ACS550 EFB 2 Fault code reserved for the embedded fieldbus (EFB) protocol application.
FDVSD The meaning is protocol dependent.
ABB ACS550 33 ACS550 EFB 3 Fault code reserved for the embedded fieldbus (EFB) protocol application.
FDVSD The meaning is protocol dependent.
ABB ACS550 34 ACS550 MOTOR PHASE Fault in the motor circuit. One of the motor phases is lost. Check for and correct:
FDVSD • Motor fault.
• Motor cable fault.
• Thermal relay fault (if used).
• Internal fault.

ABB ACS550 35 ACS550 OUTP WIRING Possible power wiring error detected. When the drive is not running it Check for and correct:
FDVSD monitors for an improper connection between the drive input power and the • Proper input wiring – line voltage is NOT connected to drive output.
drive output. • The fault can be erroneously declared if the input power is a delta
grounded system and motor cable capacitance is large. This fault can be
disabled using para

ABB ACS550 36 ACS550 INCOMPATIBLE The drive cannot use the software.
FDVSD SW • Internal fault.
• The loaded software is not compatible with the drive.
• Call support representative.

ABB ACS550 37 ACS550 CB OVERTEMP Drive control board is overheated. The fault trip limit is 88 °C. Check for and correct:
FDVSD • Excessive ambient temperature.
• Fan failure.
• Obstructions in the air flow.
Not for drives with an OMIO control board.

ABB ACS550 38 ACS550 USER LOAD Condition defined by parameter 3701 USER LOAD C MODE has been valid longer
FDVSD CURVE than the time defined by 3703 USER LOAD C TIME.
ABB ACS550 101 . . . 199 ACS550 SYSTEM ERROR Error internal to the drive. Contact your local ABB representative and report the
FDVSD error number.
ABB ACS550 201 . . . 299 ACS550 SYSTEM ERROR Error in the system. Contact your local ABB representative and report the error number.
FDVSD
ABB ACS550 - ACS550 UNKNOWN Wrong type of panel, i.e. panel that supports drive X but not the ACS550,
FDVSD DRIVE TYPE: has been connected to the ACS550.
ACS550
SUPPORTED
DRIVES: X

ABB ACS550 1000 ACS550 PAR HZRPM Parameter values are inconsistent. Check for any of the following: Faults that indicate conflicts in the parameter settings
FDVSD • 2001 MINIMUM SPEED > 2002 MAXIMUM SPEED.
• 2007 MINIMUM FREQ > 2008 MAXIMUM FREQ.
• 2001 MINIMUM SPEED / 9908 MOTOR NOM SPEED is outside proper range
(> 50).
• 2002 MAXIMUM SPEED / 9908

ABB ACS550 1001 ACS550 PAR PFC REF Parameter values are inconsistent. Check for the following: Faults that indicate conflicts in the parameter settings
FDVSD NEG • 2007 MINIMUM FREQ is negative, when 8123 PFC ENABLE is active.
ABB ACS550 1002 ACS550 RESERVED Not used. Faults that indicate conflicts in the parameter settings
FDVSD
ABB ACS550 1003 ACS550 PAR AI SCALE Parameter values are inconsistent. Check for any of the following: Faults that indicate conflicts in the parameter settings
FDVSD • 1301 MINIMUM AI1 > 1302 MAXIMUM AI1.
• 1304 MINIMUM AI2 > 1305 MAXIMUM AI2.
ABB ACS550 1004 ACS550 PAR AO SCALE Parameter values are inconsistent. Check for any of the following: Faults that indicate conflicts in the parameter settings
FDVSD • 1504 MINIMUM AO1 > 1505 MAXIMUM AO1.
• 1510 MINIMUM AO2 > 1511 MAXIMUM AO2.
ABB ACS550 1005 ACS550 PAR PCU 2 Parameter values for power control are inconsistent: Improper motor Faults that indicate conflicts in the parameter settings
FDVSD nominal kVA or motor nominal power. Check for the following:
• 1.1 < (9906 MOTOR NOM CURR · 9905 MOTOR NOM VOLT · 1.73 / PN) < 3.0
where: PN = 1000 · 9909 MOTOR NOM POWER (if units are kW

ABB ACS550 1006 ACS550 PAR EXT RO Parameter values are inconsistent. Check for the following: Faults that indicate conflicts in the parameter settings
FDVSD • Extension relay module not connected and
• 1410…1412 RELAY OUTPUTS 4…6 have non-zero values.
ABB ACS550 1007 ACS550 PAR FIELDBUS Parameter values are inconsistent. Check for and correct: Faults that indicate conflicts in the parameter settings
FDVSD MISSING • A parameter is set for fieldbus control (e.g. 1001 EXT1 COMMANDS = 10
(COMM)), but 9802 COMM PROT SEL = 0.
ABB ACS550 1008 ACS550 PAR PFC MODE Parameter values are inconsistent – 9904 MOTOR CTRL MODE must be = 3 Faults that indicate conflicts in the parameter settings
FDVSD (SCALAR:FREQ), when 8123 PFC ENABLE is activated.
ABB ACS550 1009 ACS550 PAR PCU 1 Parameter values for power control are inconsistent: Improper motor Faults that indicate conflicts in the parameter settings
FDVSD nominal frequency or speed. Check for both of the following:
• 1 < (60 · 9907 MOTOR NOM FREQ / 9908 MOTOR NOM SPEED < 16
• 0.8 < 9908 MOTOR NOM SPEED /
(120 · 9907 MOTOR NOM FREQ / Motor

ABB ACS550 1010 /1011 ACS550 RESERVED Not used. Faults that indicate conflicts in the parameter settings
FDVSD
ABB ACS550 1012 ACS550 PAR PFC IO 1 IO configuration is not complete – not enough relays are parameterized to Faults that indicate conflicts in the parameter settings
FDVSD PFC. Or, a conflict exists between Group 14: RELAY OUTPUTS, parameter
8117 NR OF AUX MOT and parameter 8118 AUTOCHNG INTERV.
ABB ACS550 1013 ACS550 PAR PFC IO 2 IO configuration is not complete – the actual number of PFC motors Faults that indicate conflicts in the parameter settings
FDVSD (parameter 8127, MOTORS) does not match the PFC motors in Group 14:
RELAY OUTPUTS and parameter 8118 AUTOCHNG INTERV.
ABB ACS550 1014 ACS550 PAR PFC IO 3 IO configuration is not complete – the drive is unable to allocate a digital Faults that indicate conflicts in the parameter settings
FDVSD input (interlock) for each PFC motor (parameters 8120 INTERLOCKS and
8127 MOTORS).
ABB ACS550 1015 ACS550 RESERVED Not used. Faults that indicate conflicts in the parameter settings
FDVSD
ABB ACS550 1016 ACS550 PAR USER LOAD C Parameter values for the user load curve are inconsistent. Check that the Faults that indicate conflicts in the parameter settings
FDVSD 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

ABB ACS550 2001 ACS550 Over Current Current limiting controller is active Check for and correct the follow
FDVSD - Excessive motor load
- Insufficient accelerating time( see parameters 2202 ACCELER TIME 1 and 2205
ACCELER TIME 2).
-Faulty motor, motor cables or connections

ABB ACS550 2002 ACS550 Over Voltage Over voltage controller is active Check for correct the following
FDVSD - Static or transient over voltages in the input power supply
- Insufficient decelerating time (parameters 2203 DECELER TIME 1 and 2206
DECLER TIME 2)

ABB ACS550 2003 ACS550 Under voltage Under voltage controller is active Check for and correct the under voltage on mains.
FDVSD
ABB ACS550 2004 ACS550 DIR lock The change in direction being attempted is not allowed Either
FDVSD -DO not attempted to change the direction of the motor rotation
- Change parameter 1003 DIRECTION to allow direction change (if reverse operating is
safe)

ABB ACS550 2005 ACS550 I/O Comm Fieldbus communication has timed out. Check and correct
FDVSD - Fault setup (3018 COMM FAULT FUNC and 3019 COMM FAULT TIME)
-Communication settings (Group 51 and 53 as appropriate)
- Poor connections and or noise on line

ABB ACS550 2006 ACS550 AI1 Loss Analog input 1 is loss or value is less than the minimum setting Check
FDVSD - Input sources and connections
- Parameter that sets the minimum (3021)
- Parameter that sets the Alarm/Fault operation (3001)
ABB ACS550 2007 ACS550 AI2 LOSS Analog input 2 is loss or value is less than the minimum setting. Check
FDVSD - Input sources and connections
- Parameter that sets the minimum (3022)
- Parameter that sets the Alarm/Fault operation (3001)

ABB ACS550 2008 ACS550 PANEL LOSS Panel communication is lost and either: To correct check
FDVSD •- Drive is in local control mode (the control panel displays LOC), or -Communcation lines and connections
•- Drive is in remote control mode (REM) and is parameterized to accept -Parameter 3002 PANEL LOSS
start/stop, direction or reference from the control panel. -Paramters in groups 10 COMMAND INPUTS AND 11 REFERNCE SELECT (if drive
operation is REM)

ABB ACS550 2009 ACS550 Device Overtemp Drive heat sink is hot. This alarm warns that a DEVICE OVERTEMP fault my be near Check and correct
FDVSD R1…R4 and R7/R8 100 degrees 212 Fahrenheit R5/R6 110 degrees 230 Fahrenheit - Fan failure
- Obstructions in the air flow
- Dirt or dust coating on the heat sink
- Excessive ambient temperautre
- Excessive motor load

ABB ACS550 2010 ACS550 MOT OVERTEMP Motor is hot on either the drive's estimate or on temperature feedback. This alarm Check
FDVSD wanrs hat a Motor Underload fault trip may be near - Check for overloaded motor
- Adjust the parameters used for the estimate (3005…3009)

ABB ACS550 2011 ACS550 Underload Motor load is lower than expected. This alamr wanrs that a mtor Underload fault Check
FDVSD trip may be near - Motor and drive ratings match (motor is NOT undersized for the drive)
- Settings on parameters 3013 to 3015

ABB ACS550 2012 ACS550 Motor Stall Motor is operating in the stall region. This alarm wanrs that a Motor Stall fault trip
FDVSD may be near
ABB ACS550 2013 (note 1) ACS550 Auto reset This larm warns that the dive is about to perform an automatic fault reset which To control automatic reset use parameter group 31 AUTOMATIC RESET
FDVSD may start the motor
ABB ACS550 2014 (note 2) ACS550 Auto change This alarm warns that the PFC autochange function is active. To control PFC use parameter group 81 PFC CONTROL and "Application macro:
FDVSD PFC" on page 49.
ABB ACS550 2015 ACS550 PFC interlock This larm warns tha the PFC interlocks are active, which means that the drive
FDVSD cannot start the following
ABB ACS550 2016/2017 ACS550 RESERVED
FDVSD
ABB ACS550 2018 ( note 1) ACS550 PID sleep This alarm wanrs that the PID sleep function is active, which means that the motor To control the PID function use parameters 4022…4026 or 4122…4126
FDVSD could accelerate when the PID sleep function ends
ABB ACS550 2019 ACS550 ID run Performing ID Run
FDVSD
ABB ACS550 2020 ACS550 Reserved
FDVSD
ABB ACS550 2021 ACS550 Start enable 1 missing This alarm wanrs that the start enable 1 signal is missing. To control START ENABLE 1 function use parameter 1608
FDVSD To correct check
- Digital input configuration
- Communication settings.

ABB ACS550 2022 ACS550 Start enable 2 missing The alarm wanrs that the START ENABLE 2 signal is missing To control START ENABLE 2 function use parameters 1609
FDVSD To correct check
- Digital input configuration
- Communcation settings

ABB ACS550 2023 ACS550 EMERGENCY STOP Emergency stop activated

FDVSD
ABB ACS550 2024 ACS550 If this alarm code appears, refer to the appropriate
FDVSD accesory manual
ABB ACS550 2025 ACS550 First start Signals that the drive is performing a FIRST START evaluation of motor
FDVSD characteristics. This is normally the first time the motor is run after motor
parameters are entered or changed. See parameter 9910 (MOTOR ID RUN) for a
description of motor models.

ABB ACS800 ACS800 TEMP ACS800 Inverter Over temp Drive IGBT temperature is excessive. Fault trip Check ambient conditions.
limit is 100%. Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against unit power.
(4210)
3.05 FW 1 bit 3

ABB ACS800 ACS TEMP xx y ACS800 Excessive internal temperature in inverter unit Check ambient conditions.
of several parallel connected inverter modules. Check air flow and fan operation.
xx (1...12) refers to inverter module number Check heatsink fins for dust pick-up.
and y refers to phase (U, V, W). Check motor power against unit power.
(4210)
3.05 FW 1 bit 3 and
4.01

ABB ACS800 AI < MIN FUNC ACS800 Analogue control signal is below minimum Check for proper analogue control signal
allowed value due to incorrect signal level or levels.
failure in control wiring. Check control wiring.
Check Fault Function parameters.
(8110)
3.06 FW 2 bit 10
(programmable
Fault Function
30.01)
ABB ACS800 BACKUP ERROR ACS800 Failure when restoring PC stored backup of Retry.
drive parameters. Check connections.
Check that parameters are compatible with
drive.

ABB ACS800 BC OVERHEAT ACS800 Brake chopper overload Let chopper cool down.
Check parameter settings of resistor overload
(7114) protection function (see parameter group 27
3.17 FW 5 bit 4 BRAKE CHOPPER).
Check that braking cycle meets allowed limits.
Check that drive supply AC voltage is not
excessive.

ABB ACS800 BC SHORT CIR ACS800 Short circuit in brake chopper IGBT(s) Replace brake chopper.
Ensure brake resistor is connected and not
(7113) damaged.
3.17 FW 5 bit 2

ABB ACS800 BRAKE ACKN ACS800 Unexpected state of brake acknowledge signal See parameter group 42 BRAKE CONTROL.
Check connection of brake acknowledgement
(FF74) signal.
3.15 FW 4 bit 3

ABB ACS800 BR BROKEN ACS800 Brake resistor is not connected or it is Check resistor and resistor connection.
damaged. Check that resistance rating meets
Resistance rating of brake resistor is too high. specifications. See appropriate drive hardware
manual.
(7110)
3.17 FW 5 bit 0

ABB ACS800 BR OVERHEAT ACS800 Brake resistor overload Let resistor cool down.
Check parameter settings of resistor overload
-(7112) protection function (see parameter group 27
3.17 FW 5 bit 3 BRAKE CHOPPER).
Check that braking cycle meets allowed limits.
Check that drive supply AC voltage is not
excessive.

ABB ACS800 BR WIRIN ACS800 Wrong connection of brake resistor Check resistor connection.
Ensure brake resistor is not damaged.
(7111)
3.17 FW 5 bit 1

ABB ACS800 CHOKE OTEMP ACS800 Excessive temperature of drive output filter. Let drive cool down.
Supervision is in use in step-up drives. Check ambient temperature.
Check filter fan rotates in correct direction and
(FF82) air flows freely.

ABB ACS800 COMM MODULE ACS800 Cyclical communication between drive and Check status of fieldbus communication. See
master is lost. chapter Fieldbus control, or appropriate
fieldbus adapter manual.
(7510) Check parameter settings:
3.06 FW 2 bit 12
(programmable - group 51 COMM MOD DATA (for fieldbus
Fault Function adapter), or
30.18)
- group 52 STANDARD MODBUS (for
Standard Modbus Link)
Check cable

ABB ACS800 CTRL B TEMP ACS800 Control board temperature is above 88°C. Check ambient conditions.
Check air flow.
4110) Check main and additional cooling fans.
3.06 FW 2 bit 7

ABB ACS800 CURR MEAS ACS800 Current transformer failure in output current Check current transformer connections to Main
measurement circuit Circuit Interface Board, INT.

(2211)

ABB ACS800 CUR UNBAL xx ACS800 Drive has detected excessive output current Check motor.
unbalance in inverter unit of several parallel Check motor cable.
connected inverter modules. This can be Check that there are no power factor correction
caused by external fault (earth fault, motor, or surge absorbers in motor cable.
motor cabling, etc.) or internal fault (damaged
inverter component). xx (2...1

ABB ACS800 DC HIGH RUSH ACS800 Drive supply voltage is excessive. When Check supply voltage level, drive rated voltage
supply voltage is over 124% of unit voltage and allowed voltage range of drive.
rating (415, 500 or 690 V), motor speed rushes
to trip level (40% of nominal speed).

(FF80)

ABB ACS800 DC OVERVOLT ACS800 Excessive intermediate circuit DC voltage. Check that overvoltage controller is on
DC overvoltage trip limit is 1.3 · U1max, where (parameter 20.05).
U1max is maximum value of mains voltage Check mains for static or transient overvoltage.
range. For 400 V units, U1max is 415 V. For Check brake chopper and resistor (if used).
500 V units, U1max is 500 V. Actual voltage in Check deceleration time.
intermediate circuit correspondin Use coast-to-stop function (if applicable).
Retrofit frequency converter with
ABB ACS800 DC UNDERVOLT ACS800 Intermediate circuit DC voltage is not sufficient Check mains supply and fuses.
due to missing mains phase, blown fuse or
rectifier bridge internal fault. * Use Multimeter and DIODE check for correct working condition of DIODES. MAY SURE
DC undervoltage trip limit is 0.6 · U1min, where POWER IS COMPLETELY OFF AND WAIT 10 MINUTES BEFORE PERFORMING THIS TEST
U1min is minimum value of mains voltage
range. For 400 V and 500 V units, U1min i

ABB ACS800 ENCODER A<>B ACS800 Pulse encoder phasing is wrong: Phase A is Interchange connection of pulse encoder
connected to terminal of phase B and vice phases A and B.
versa.
(7302)

ABB ACS800 ENCODER FLT ACS800 Communication fault between pulse encoder Check pulse encoder and its wiring, pulse
and pulse encoder interface module and encoder interface module and its wiring and
between module and drive parameter group 50 ENCODER MODULE
settings.
(7301)
3.06 FW 2 bit 5

ABB ACS800 EXTERNAL FLT ACS800 Fault in external device. (This information is Check external devices for faults.
configured through one of programmable Check parameter 30.03 EXTERNAL FAULT.
digital inputs.)

(9000)
3.06 FW 2 bit 8
(programmable
Fault Function
30.03)

ABB ACS800 FAN OVERTEMP ACS800 Excessive temperature of drive output filter fan. Stop drive. Let it cool down.
Supervision is in use in step-up drives. Check ambient temperature.
Check fan rotates in correct direction and air
(FF83) flows freely.

ABB ACS800 INT CONFIG ACS800 Number of inverter modules is not equal to Check status of inverters. See signal 4.01 INT
original number of inverters. FAULT INFO.
Check fibre optic cables between APBU and
(5410) inverter modules.
03.17 FW 5 bit 9 If Reduced Run function is used, remove
faulted inverter module from main circuit and
write number of remaining inverter modules
into pa

ABB ACS800 I/O COMM ERR ACS800 Communication error on control board, Check connections of fibre optic cables on
channel CH1 channel CH1.
Electromagnetic interference Check all I/O modules (if present) connected to
channel CH1.
(7000) Check for proper earthing of equipment. Check
3.06 FW 2 bit 6 for highly emissive components nearby.

ABB ACS800 LINE CONV ACS800 Fault on line side converter Shift panel from motor side converter control
board to line side converter control board.
(FF51) See line side converter manual for fault
description.

ABB ACS800 MOTOR PHASE ACS800 One of motor phases is lost due to fault in Check motor and motor cable.
motor, motor cable, thermal relay (if used) or Check thermal relay (if used).
internal fault. Check Fault Function parameters (Group 30 / parameter 16. Disable this
protection from FAULT to NO
(FF56)
3.06 FW 2 bit 15
(programmable
Fault Function
30.16)

ABB ACS800 MOTOR STALL ACS800 Motor is operating in stall region due to e.g. Check motor load and drive ratings.
excessive load or insufficient motor power. Check Fault Function parameters.

7121)
3.06 FW 2 bit 14
(programmable
Fault Function
30.10…30.12)

ABB ACS800 MOTOR TEMP ACS800 Motor temperature is too high (or appears to be Check motor ratings and load.
too high) due to excessive load, insufficient Check start-up data.
motor power, inadequate cooling or incorrect Check Fault Function parameters.
start-up data.

(4310)
3.05 FW 1 bit 6
(programmable
Fault Function
30.04…30.09)

ABB ACS800 MOTOR 1 TEMP ACS800 Measured motor temperature has exceeded Check value of fault limit.
fault limit set by parameter 35.03. Let motor cool down. Ensure proper motor
cooling: Check cooling fan, clean cooling
(4312) surfaces, etc.
3.15 FW 4 bit 1
ABB ACS800 MOTOR 2 TEMP ACS800 Measured motor temperature has exceeded Check value of fault limit.
fault limit set by parameter 35.06. Let motor cool down. Ensure proper motor
cooling: Check cooling fan, clean cooling
(4313) surfaces, etc.
3.15 FW 4 bit 2

ABB ACS800 NO MOT DATA ACS800 Motor data is not given or motor data does not Check motor data parameters
match with inverter data. 99.04…99.09.

(FF52)
3.06 FW 2 bit 1

ABB ACS800 OVERCURR xx ACS800 Overcurrent fault in inverter unit of several Check motor load.
parallel connected inverter modules. xx (2...12) Check acceleration time.
refers to inverter module number. Check motor and motor cable (including
phasing).
(2310) Check encoder cable (including phasing).
3.05 FW 1 bit 1 and Check motor nominal values from group 99
4.01 START-UP DATA to confirm that motor model
is correct.
Check that there are no pow

ABB ACS800 OVERCURRENT ACS800 OVERCURRENT Output current exceeds trip limit. Check motor load.
Check acceleration time.
(2310) Check motor and motor cable (including
3.05 FW 1 bit 1 phasing).
Check that there are no power factor correction
capacitors or surge absorbers in motor cable.
Check encoder cable (including phasing).

ABB ACS800 OVERFREQ ACS800 Motor is turning faster than highest allowed Check minimum/maximum speed settings.
speed due to incorrectly set minimum/ Check adequacy of motor braking torque.
maximum speed, insufficient braking torque or Check applicability of torque control.
changes in load when using torque reference. Check need for brake chopper and resistor(s).
Trip level is 40 Hz over operating range
absolute maximum speed limit (Direct Tor

ABB ACS800 PANEL LOSS ACS800 Control panel or DriveWindow selected as Check panel connection (see appropriate
active control location for drive has ceased hardware manual).
communicating. Check control panel connector.
Replace control panel in mounting platform.
(5300) Check Fault Function parameters.
3.06 FW 2 bit 13 Check DriveWindow connection.
(programmable
Fault Function
30.02)

ABB ACS800 PPCC LINK xx ACS800 INT board fibre optic connection fault in Check connection from inverter module Main
inverter unit of several parallel connected Circuit Interface Board, INT to PPCC
inverter modules. xx refers to inverter module Branching Unit, PBU. (Inverter module 1 is
number. connected to PBU INT1 etc.)
Check signal 03.19. Contact ABB
3.06 FW 2 bit 11 and representative if any of faults in signal 3.19 are
4.01 active.

ABB ACS800 RUN DISABLE ACS800 No Run enable signal received. Check setting of parameter 16.01. Switch on
signal or check wiring of selected source.
3.06 FW 2 bit 4
ABB ACS800 SC INV xx y ACS800 Short circuit in inverter unit of several parallel Check motor and motor cable.
connected inverter modules. xx (1...12) refers Check power semiconductors (IGBTs) of
to inverter module number and y refers to inverter module.
phase (U, V, W).
2340)
3.05 FW 1 bit 0, 4.01
and 4.02

ABB ACS800 SHORT CIRC ACS800 Short-circuit in motor cable(s) or motor Check motor and motor cable.
Check there are no power factor correction
Output bridge of converter unit is faulty. capacitors or surge absorbers in motor cable.

(2340) - By using your multimeter, perform diode check on the output (U,V, W) of the drive.
3.05 FW 1 bit 0 and
4.02

ABB ACS800 SLOT OVERLAP ACS800 Two option modules have same connection Check connection interface selections in group
interface selection. 98 OPTION MODULES.
(FF8A)

ABB ACS800 START INHIBI ACS800 Optional start inhibit hardware logic is Check start inhibit circuit (AGPS board).
activated.

3.03 bit 8
Possibly service switch has loose connection(s)
ABB ACS800 SUPPLY PHASE ACS800 Intermediate circuit DC voltage is oscillating Check mains fuses.
due to missing mains phase, blown fuse or Check for mains supply imbalance.
rectifier bridge internal fault.
Trip occurs when DC voltage ripple is 13% of
DC voltage.
(3130)
3.06 FW 2 bit 0

ABB ACS800 THERMAL MODE ACS800 Motor thermal protection mode is set to DTC See parameter 30.05.
for high-power motor.

(FF50)

ABB ACS800 THERMISTOR ACS800 Motor temperature is excessive. Motor thermal Check motor ratings and load.
protection mode selection is THERMISTOR. Check start-up data.
Check thermistor connections to digital input
(4311) DI6.
3.05 FW 1 bit 5
(programmable
Fault Function
30.04…30.05)

ABB ACS800 UNDERLOAD ACS800 Motor load is too low due to e.g. release Check for problem in driven equipment.
mechanism in driven equipment. Check Fault Function parameters.
(FF6A)
3.05 FW 1 bit 8
(programmable
Fault Function
30.13…30.15)

ABB ACS800 USER L CURVE ACS800 Integrated motor current has exceeded load Check parameter group 72 USER LOAD
curve defined by parameter group 72 USER CURVE settings.
LOAD CURVE. After motor cooling time specified by
parameter 72.20 LOAD COOLING TIME has
elapsed, fault can be reset.

ABB ACS800 USER MACRO ACS800 No User Macro saved or file is defective. Create User Macro.
(FFA1)
3.07 SFW bit 1

ABB ACS800 DC BUS LIM ACS800 Drive limits torque due to too high or too low Informative alarm
intermediate circuit DC voltage. Check Fault Function parameters.

(3211)
3.18 AW5 bit 9
(programmable
Fault Function
30.23)

ABB ACS800 EARTH FAULT Drive has detected load unbalance typically Check motor.
due to earth fault in motor or motor cable. Check motor cable.
Check there are no power factor correction
(2330) capacitors or surge absorbers in motor cable.
3.08 AW 1 bit 14
(programmable
Fault Function
30.17)

ABB ACS800 4210 (ACS800 TEMP) ACS800 Inverter Over temp Drive IGBT temperature is excessive. Fault trip Check ambient conditions.
limit is 100%. Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against unit power.
(4210)
3.05 FW 1 bit 3

ABB ACS800 2330 (EARTH FAULT) Drive has detected load unbalance typically Check motor.
due to earth fault in motor or motor cable. Check motor cable.
Check there are no power factor correction
(2330) capacitors or surge absorbers in motor cable.
3.08 AW 1 bit 14
(programmable
Fault Function
30.17)

ABB ACS800 3211 (DC BUS LIM) ACS800 Drive limits torque due to too high or too low Informative alarm
intermediate circuit DC voltage. Check Fault Function parameters.
(3211)
3.18 AW5 bit 9
(programmable
Fault Function
30.23)

ABB ACS800 FFA1 (USER MACRO) ACS800 No User Macro saved or file is defective. Create User Macro.

(FFA1)
3.07 SFW bit 1
ABB ACS800 8110 (AI < MIN FUNC) ACS800 Analogue control signal is below minimum Check for proper analogue control signal
allowed value due to incorrect signal level or levels.
failure in control wiring. Check control wiring.
Check Fault Function parameters.
(8110)
3.06 FW 2 bit 10
(programmable
Fault Function
30.01)

ABB ACS800 7114 (BC OVERHEAT) ACS800 Brake chopper overload Let chopper cool down.
Check parameter settings of resistor overload
(7114) protection function (see parameter group 27
3.17 FW 5 bit 4 BRAKE CHOPPER).
Check that braking cycle meets allowed limits.
Check that drive supply AC voltage is not
excessive.

ABB ACS800 7113 (BC SHORT CIR) ACS800 Short circuit in brake chopper IGBT(s) Replace brake chopper.
Ensure brake resistor is connected and not
(7113) damaged.
3.17 FW 5 bit 2

ABB ACS800 FF74 (BRAKE ACKN) ACS800 Unexpected state of brake acknowledge signal See parameter group 42 BRAKE CONTROL.
Check connection of brake acknowledgement
(FF74) signal.
3.15 FW 4 bit 3

ABB ACS800 7110 (BR BROKEN) ACS800 Brake resistor is not connected or it is Check resistor and resistor connection.
damaged. Check that resistance rating meets
Resistance rating of brake resistor is too high. specifications. See appropriate drive hardware
manual.
(7110)
3.17 FW 5 bit 0

ABB ACS800 7112 (BR OVERHEAT) ACS800 Brake resistor overload Let resistor cool down.
Check parameter settings of resistor overload
(7112) protection function (see parameter group 27
3.17 FW 5 bit 3 BRAKE CHOPPER).
Check that braking cycle meets allowed limits.
Check that drive supply AC voltage is not
excessive.

ABB ACS800 7111 (BR WIRIN) ACS800 Wrong connection of brake resistor Check resistor connection.
Ensure brake resistor is not damaged.
(7111)
3.17 FW 5 bit 1

ABB ACS800 FF82 (CHOKE OTEMP) ACS800 Excessive temperature of drive output filter. Let drive cool down.
Supervision is in use in step-up drives. Check ambient temperature.
Check filter fan rotates in correct direction and
(FF82) air flows freely.

ABB ACS800 7510 (COMM MODULE) ACS800 Cyclical communication between drive and Check status of fieldbus communication. See
master is lost. chapter Fieldbus control, or appropriate
fieldbus adapter manual.
(7510) Check parameter settings:
3.06 FW 2 bit 12
(programmable - group 51 COMM MOD DATA (for fieldbus
Fault Function adapter), or
30.18)
- group 52 STANDARD MODBUS (for
Standard Modbus Link)
Check cable

ABB ACS800 4110 (CTRL B TEMP) ACS800 Control board temperature is above 88°C. Check ambient conditions.
Check air flow.
4110) Check main and additional cooling fans.
3.06 FW 2 bit 7

ABB ACS800 2211 (CURR MEAS) ACS800 Current transformer failure in output current Check current transformer connections to Main
measurement circuit Circuit Interface Board, INT.

(2211)

ABB ACS800 CUR UNBAL xx ACS800 Drive has detected excessive output current Check motor.
unbalance in inverter unit of several parallel Check motor cable.
connected inverter modules. This can be Check that there are no power factor correction
caused by external fault (earth fault, motor, or surge absorbers in motor cable.
motor cabling, etc.) or internal fault (damaged
inverter component). xx (2...1

ABB ACS800 FF80 (DC HIGH RUSH) ACS800 Drive supply voltage is excessive. When Check supply voltage level, drive rated voltage
supply voltage is over 124% of unit voltage and allowed voltage range of drive.
rating (415, 500 or 690 V), motor speed rushes
to trip level (40% of nominal speed).
(FF80)

ABB ACS800 7302 (ENCODER A<>B) ACS800 Pulse encoder phasing is wrong: Phase A is Interchange connection of pulse encoder
connected to terminal of phase B and vice phases A and B.
versa.

(7302)
ABB ACS800 7301 (ENCODER FLT) ACS800 Communication fault between pulse encoder Check pulse encoder and its wiring, pulse
and pulse encoder interface module and encoder interface module and its wiring and
between module and drive parameter group 50 ENCODER MODULE
settings.
(7301)
3.06 FW 2 bit 5

ABB ACS800 9000 (EXTERNAL FLT) ACS800 Fault in external device. (This information is Check external devices for faults.
configured through one of programmable Check parameter 30.03 EXTERNAL FAULT.
digital inputs.)
(9000)
3.06 FW 2 bit 8
(programmable
Fault Function
30.03)

ABB ACS800 FF83 (FAN OVERTEMP) ACS800 Excessive temperature of drive output filter fan. Stop drive. Let it cool down.
Supervision is in use in step-up drives. Check ambient temperature.
Check fan rotates in correct direction and air
(FF83) flows freely.

ABB ACS800 FORCED TRIP ACS800 Generic Drive Communication Profile trip See appropriate communication module
command manual.
ABB ACS800 ID RUN FAIL ACS800 Motor ID Run is not completed successfully. Check maximum speed (parameter 20.02). It
should be at least 80% of motor nominal speed
(parameter 99.08).
* Please use REDUCED MOTOR ID RUN where possible, as element is still coupled to
motor.

* ELEMENT MAYBE DAMAGED IF MOTOR ID RUN IN STANDARD MODE.

ABB ACS800 5410 (INT CONFIG) ACS800 Number of inverter modules is not equal to Check status of inverters. See signal 4.01 INT
original number of inverters. FAULT INFO.
Check fibre optic cables between APBU and
(5410) inverter modules.
03.17 FW 5 bit 9 If Reduced Run function is used, remove
faulted inverter module from main circuit and
write number of remaining inverter modules
into pa

ABB ACS800 INV DISABLED ACS800 Optional DC switch has opened while unit was Close DC switch.
running or start command was given. Check AFSC-0x Fuse Switch Controller unit.
ABB ACS800 7000 (I/O COMM ERR) ACS800 Communication error on control board, Check connections of fibre optic cables on
channel CH1 channel CH1.
Electromagnetic interference Check all I/O modules (if present) connected to
channel CH1.
(7000) Check for proper earthing of equipment. Check
3.06 FW 2 bit 6 for highly emissive components nearby.

ABB ACS800 FF51 (LINE CONV) ACS800 Fault on line side converter Shift panel from motor side converter control
board to line side converter control board.
(FF51) See line side converter manual for fault
description.

ABB ACS800 FF56 (MOTOR PHASE) ACS800 One of motor phases is lost due to fault in Check motor and motor cable.
motor, motor cable, thermal relay (if used) or Check thermal relay (if used).
internal fault. Check Fault Function parameters (Group 30 / parameter 16. Disable this
protection from FAULT to NO
(FF56)
3.06 FW 2 bit 15
(programmable
Fault Function
30.16)

ABB ACS800 7121 (MOTOR STALL) ACS800 Motor is operating in stall region due to e.g. Check motor load and drive ratings.
excessive load or insufficient motor power. Check Fault Function parameters.

7121)
3.06 FW 2 bit 14
(programmable
Fault Function
30.10…30.12)

ABB ACS800 4310 (MOTOR TEMP) ACS800 Motor temperature is too high (or appears to be Check motor ratings and load.
too high) due to excessive load, insufficient Check start-up data.
motor power, inadequate cooling or incorrect Check Fault Function parameters.
start-up data.
(4310)
3.05 FW 1 bit 6
(programmable
Fault Function
30.04…30.09)

ABB ACS800 4312 (MOTOR 1 TEMP) ACS800 Measured motor temperature has exceeded Check value of fault limit.
fault limit set by parameter 35.03. Let motor cool down. Ensure proper motor
cooling: Check cooling fan, clean cooling
(4312) surfaces, etc.
3.15 FW 4 bit 1
ABB ACS800 4313 (MOTOR 2 TEMP) ACS800 Measured motor temperature has exceeded Check value of fault limit.
fault limit set by parameter 35.06. Let motor cool down. Ensure proper motor
cooling: Check cooling fan, clean cooling
(4313) surfaces, etc.
3.15 FW 4 bit 2

ABB ACS800 FF52 (NO MOT DATA) ACS800 Motor data is not given or motor data does not Check motor data parameters
match with inverter data. 99.04…99.09.

(FF52)
3.06 FW 2 bit 1

ABB ACS800 2310 (OVERCURR xx) ACS800 Overcurrent fault in inverter unit of several Check motor load.
parallel connected inverter modules. xx (2...12) Check acceleration time.
refers to inverter module number. Check motor and motor cable (including
phasing).
(2310) Check encoder cable (including phasing).
3.05 FW 1 bit 1 and Check motor nominal values from group 99
4.01 START-UP DATA to confirm that motor model
is correct.
Check that there are no pow

ABB ACS800 2310 (OVERCURRENT) ACS800 OVERCURRENT Output current exceeds trip limit. Check motor load.
Check acceleration time.
(2310) Check motor and motor cable (including
3.05 FW 1 bit 1 phasing).
Check that there are no power factor correction
capacitors or surge absorbers in motor cable.
Check encoder cable (including phasing).

ABB ACS800 OVERFREQ ACS800 Motor is turning faster than highest allowed Check minimum/maximum speed settings.
speed due to incorrectly set minimum/ Check adequacy of motor braking torque.
maximum speed, insufficient braking torque or Check applicability of torque control.
changes in load when using torque reference. Check need for brake chopper and resistor(s).
Trip level is 40 Hz over operating range
absolute maximum speed limit (Direct Tor

ABB ACS800 5300 (PANEL LOSS) ACS800 Control panel or DriveWindow selected as Check panel connection (see appropriate
active control location for drive has ceased hardware manual).
communicating. Check control panel connector.
Replace control panel in mounting platform.
(5300) Check Fault Function parameters.
3.06 FW 2 bit 13 Check DriveWindow connection.
(programmable
Fault Function
30.02)

ABB ACS800 POWERF INT xx ACS800 INT board powerfail in inverter unit of several Check that INT board power cable is
parallel connected inverter modules. xx refers connected.
to inverter module number. Check that POW board is working correctly.
Replace INT board.
3.17 FW 5 bit 8 and
4.01

ABB ACS800 POWERF INT ACS800 INT board powerfail in inverter unit of several Check that INT board power cable is
parallel connected inverter modules. xx refers connected.
to inverter module number. Check that POW board is working correctly.
Replace INT board.
3.17 FW 5 bit 8

ABB ACS800 5120 (PPCC LINK) ACS800 Fibre optic link to INT board is faulty. Check fibre optic cables or galvanic link. With
frame sizes R2-R6 link is galvanic.
(5120) If RMIO is powered from external supply,
3.06 FW 2 bit 11 ensure that supply is on.
Check signal 03.19. Contact ABB
representative if any of faults in signal 3.19 are
active.

ABB ACS800 PP OVERLOAD ACS800 Excessive IGBT junction to case temperature. Check motor cables.
This fault protects IGBT(s) and it can be
activated by short circuit at output of long
motor cables.

3.17 FW 5 bit 5

ABB ACS800 2340 (SC INV xx y) ACS800 Short circuit in inverter unit of several parallel Check motor and motor cable.
connected inverter modules. xx (1...12) refers Check power semiconductors (IGBTs) of
to inverter module number and y refers to inverter module.
phase (U, V, W).

2340)
3.05 FW 1 bit 0, 4.01
and 4.02

ABB ACS800 2340 (SHORT CIRC) ACS800 Short-circuit in motor cable(s) or motor Check motor and motor cable.
Check there are no power factor correction
Output bridge of converter unit is faulty. capacitors or surge absorbers in motor cable.

(2340) - By using your multimeter, perform diode check on the output (U,V, W) of the drive.
3.05 FW 1 bit 0 and
4.02
ABB ACS800 FF8A (SLOT OVERLAP) ACS800 Two option modules have same connection Check connection interface selections in group
interface selection. 98 OPTION MODULES.

(FF8A)

ABB ACS800 3130 (SUPPLY PHASE) ACS800 Intermediate circuit DC voltage is oscillating Check mains fuses.
due to missing mains phase, blown fuse or Check for mains supply imbalance.
rectifier bridge internal fault.
Trip occurs when DC voltage ripple is 13% of
DC voltage.
(3130)
3.06 FW 2 bit 0

ABB ACS800 TEMP DIF xx y ACS800 Excessive temperature difference between Check cooling fan.
several parallel connected inverter modules. xx Replace fan.
(1...12) refers to inverter module number and y Check air filters.
refers to phase (U, V, W).
Alarm is indicated when temperature difference
is 15°C. Fault is indicated when temperature

ABB ACS800 FF50 (THERMAL MODE) ACS800 Motor thermal protection mode is set to DTC See parameter 30.05.
for high-power motor.

(FF50)

ABB ACS800 4311 (THERMISTOR) ACS800 Motor temperature is excessive. Motor thermal Check motor ratings and load.
protection mode selection is THERMISTOR. Check start-up data.
Check thermistor connections to digital input
(4311) DI6.
3.05 FW 1 bit 5
(programmable
Fault Function
30.04…30.05)

ABB ACS800 FF6A (UNDERLOAD) ACS800 Motor load is too low due to e.g. release Check for problem in driven equipment.
mechanism in driven equipment. Check Fault Function parameters.

(FF6A)
3.05 FW 1 bit 8
(programmable
Fault Function
30.13…30.15)

ABB ACS850 0064 IGBT OVERLOAD Excessive IGBT junction to Check motor cable.
(0x5482) case temperature. This fault
protects the IGBT(s) and can
be activated by a short circuit
in the motor cable.

ABB ACS850 0065 IGBT TEMP Drive IGBT temperature is Check ambient conditions.
(0x4210) excessive. Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against drive power.

ABB ACS850 0066 COOLING Drive module temperature is Check setting of parameter 95.03 Temp
(0x4290) excessive. inu ambient.
Check ambient temperature. If it exceeds
40 °C (104 °F), ensure that load current
does not exceed derated load capacity of
drive. See the appropriate Hardware
Manual.
Check drive module cooling air flow a

ABB ACS850 0067 FPGA ERROR1 Drive internal fault Contact your local ABB representative.
(0x5401)
ABB ACS850 0068 FPGA ERROR2 Drive internal fault Contact your local ABB representative.
(0x5402)
ABB ACS850 0069 ADC ERROR Drive internal fault Contact your local ABB representative.
(0x5403)
ABB ACS850 0070 TEMP MEAS Problem with internal Contact your local ABB representative.
FAILURE temperature measurement of
(0x4211) the drive.
ABB ACS850 0071 EFB COMM LOSS Embedded fieldbus interface Check:
(0x7540) has been taken into use, and • selection of the parameter which
there is a communication enables/disables EFB communication
break between the drive and (58.01 Protocol ena sel)
the master station. • EFB connection at terminal XD2D on
the JCON board
• status of the fieldbus master (online/
offline)
• settings of the communication
supervision functio

ABB ACS850 0072 TEMP DIFFERENCE Too high a temperature Check cooling and the fan.
(0x4212) difference between the IGBTs Contact your local ABB representative
of different phases.
ABB ACS850 0073 ENC 1 PULSE Encoder 1 is receiving too high Check encoder settings and cabling
FREQUENCY data flow (pulse frequency). (shield). After any modifications, reconfigure
(0x738E) the interface by activating
parameter 90.10 Enc par refresh.
ABB ACS850 0074 ENC 2 PULSE Encoder 2 is receiving too high Check encoder settings and cabling
FREQUENCY data flow (pulse frequency). (shield). After any modifications, reconfigure
(0x738F) the interface by activating
parameter 90.10 Enc par refresh.

ABB ACS850 0075 OVERFREQUENCY Inverter output (motor)

(0x7390) frequency is over the
frequency limit 500 Hz.
ABB ACS850 0201 T2 OVERLOAD Firmware time level 2 overload Contact your local ABB representative.
(0x0201) Note: This fault cannot be
reset.
ABB ACS850 0202 T3 OVERLOAD Firmware time level 3 overload Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0203 T4 OVERLOAD Firmware time level 4 overload Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset. This fault code is 100% related to a firmware bug. This fault only occurs extremely
sporadic. So once you reset this fault, it will likely1 never come back.

ABB ACS850 0204 T5 OVERLOAD Firmware time level 5 overload Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0205 A1 OVERLOAD Application time level 1 fault Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0206 A2 OVERLOAD Application time level 2 fault Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0207 A1 INIT FAULT Application task creation fault Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0208 A2 INIT FAULT Application task creation fault Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0209 STACK ERROR Drive internal fault Contact your local ABB representative.
(0x6100) Note: This fault cannot be Code Fault
reset. (fieldbus code)
Cause What to do

ABB ACS850 0210 JMU MISSING JMU Memory Unit is missing or Check that the JMU is properly installed.
(0xFF61) broken. If the problem persists, replace the JMU.
ABB ACS850 0301 UFF FILE READ File read error Contact your local ABB representative.
(0x6300) Note: This fault cannot be
reset.
ABB ACS850 0302 APPL DIR CREATION Drive internal fault Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0303 FPGA CONFIG DIR Drive internal fault Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0304 PU RATING ID Drive internal fault Contact your local ABB representative.
(0x5483) Note: This fault cannot be
reset.
ABB ACS850 0305 RATING DATABASE Drive internal fault Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0306 LICENSING Drive internal fault Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0307 DEFAULT FILE Drive internal fault Contact your local ABB representative.
(0x6100) Note: This fault cannot be
reset.
ABB ACS850 0308 APPLFILE PAR Corrupted application file Reload application.
(0x6300) Note: This fault cannot be If fault is still active, contact your local
reset. ABB representative.
ABB ACS850 0309 APPL LOADING Application file incompatible or Check the fault logger for a fault code
(0x6300) corrupted extension. See appropriate actions for
Note: This fault cannot be each extension below.
reset. *Refer to Application programming for
ACS850 and ACQ810 drives application
Extension: 8 == Template used in the guide (3AUA0000078664 [English]).
application incompatible with
drive firmware. *Change the template of the application
in D
Extension: 10 == Parameters defined in the
application conflict with
existing drive parameter

ABB ACS850 0310 USERSET LOAD Loading of user set is not Reload.
(0xFF69) successfully completed
because:
- requested user set does not
exist
- user set is not compatible
with drive program
- drive has been switched off
during loading.
ABB ACS850 0311 USERSET SAVE User set is not saved because Check the setting of parameter 95.01 Ctrl
(0xFF69) of memory corruption. boardSupply.
If the fault still occurs, contact your local
ABB representative.

ABB ACS850 0312 UFF OVERSIZE UFF file is too big Contact your local ABB representative.
(0x6300)
ABB ACS850 0313 UFF EOF UFF file structure failure Contact your local ABB representative.
(0x6300)
ABB ACS850 0314 TECH LIB Incompatible firmware Contact your local ABB representative.
INTERFACE interface
(0x6100) Note: This fault cannot be
reset.

ABB ACS850 0315 RESTORE FILE Restoration of backed-up Contact your local ABB representative.
(0x630D) parameters failed. The fault is reset after a successful
restoration via the control panel or
DriveStudio.

ABB ACS850 0316 DAPS MISMATCH Mismatch between JCU Contact your local ABB representative.
(0x5484) Control Unit firmware and
power unit logic versions.
ABB ACS850 0317 SOLUTION FAULT Fault generated by function Check the usage of the
(0x6200) block SOLUTION_FAULT in SOLUTION_FAULT block in the
the application program. application program.
ABB ACS850 0318 MENU HIDING Menu hiding file missing or Reload application.
(0x6200) corrupted. Contact your local ABB representative.
ABB ACS850 2000 (alarm) ABB ACS850 BRAKE START Mechanical brake alarm. Alarm Check brake open torque setting,
TORQUE is activated if required motor parameter 42.08.
(0x7185) starting torque (42.08 Brake Check drive torque and current limits.
Programmable fault: open torq) is not achieved. See parameter group 20 Limits.
42.12 Brake fault func

ABB ACS850 2001 (alarm) BRAKE NOT Mechanical brake control Check mechanical brake connection.
CLOSED alarm. Alarm is activated e.g. if Check mechanical brake settings in
(0x7186) brake acknowledgement is not parameter group 42 Mech brake ctrl.
Programmable fault: as expected during brake To determine whether problem is with
42.12 Brake fault func closing. acknowledgement signal or brake,

ABB ACS850 2002 (alarm) BRAKE NOT OPEN Mechanical brake control Check mechanical brake connection.
(0x7187) alarm. Alarm is activated e.g. if Check mechanical brake settings in
Programmable fault: brake acknowledgement is not parameter group 42 Mech brake ctrl.
42.12 Brake fault func as expecte To determine whether problem is with
acknowledgement signal or brake, check
if brake is closed or open.

ABB ACS850 2003 (alarm) SAFE TORQUE OFF Safe torque off function is Check safety circuit connections. For
(0xFF7A) active, i.e. safety circuit more information, see the appropriate
Programmable fault: signal(s) connected to drive Hardware Manual, description of
30.07 Sto diagnostic connector XSTO is lost. parameter 30.07 (page 199), and
Application guide - Safe torque off
function for ACSM1, ACS850 and
ACQ810 drives (3AFE68929814
[English]).

ABB ACS850 2004 (alarm) STO MODE CHANGE Error in changing Safe torque Contact your local ABB representative.
(0xFF7A) off supervision, i.e. parameter
30.07 Sto diagnostic setting
could not be changed to value
Alarm.

ABB ACS850 2005 (alarm) MOTOR Estimated motor temperature Check motor ratings and load.
TEMPERATURE (based on motor thermal Let motor cool down. Ensure proper
(0x4310) model) has exceeded alarm motor cooling: Check cooling fan, clean
Programmable fault: limit defined by parameter cooling surfaces, etc.
31.01 Mot temp1 prot 31.03 Mot temp1 almLim. Check value of alarm limit.
Check motor thermal model settings
Measured motor temperature (parameters 31.09…31.14).
has exceeded alarm limit
defined by parameter 31.03 Check that actual number of sensors
Mot temp1 almLim. c

ABB ACS850 2006 (alarm) EMERGENCY OFF Drive has received emergency To restart drive, activate run enable
(0xF083) OFF2 command. signal (source selected by parameter
10.11 Run enable) and start drive.

This is normal: when the compressor stops and starts, it’s normal to see the alarms on
the BOP panel flashing. The drive nor the Elektronikon wi

ABB ACS850 2007 (alarm) RUN ENABLE No run enable signal is Check setting of parameter 10.11 Run
(0xFF54) received. enable. Switch signal on (e.g. in the
fieldbus Control Word)

This is normal: when the compressor stops and starts, it’s normal to see the alarms on
the BOP panel flashing. The drive nor the Elektronikon will not trip
ABB ACS850 2008 (alarm) MOTOR ID-RUN Motor identification run is on. This alarm belongs to normal start-up
(0xFF84) procedure. Wait until drive indicates that
Motor identification is required. motor identification is completed.
This alarm belongs to normal start-up
procedure.
Select how motor identification should be
performed, parameter 99.13 IDrun mode.
Start id

ABB ACS850 2009 (alarm) EMERGENCY STOP Drive has received emergency Check that it is safe to continue
(0xF081) stop command (OFF1/OFF3). operation.
Return emergency stop push button to
normal position (or adjust the fieldbus
Control Word accordingly).
Restart drive.

ABB ACS850 2011 (alarm) BR OVERHEAT Brake resistor temperature has Stop drive. Let resistor cool down.
(0x7112) exceeded alarm limit defined Check resistor overload protection
by parameter 48.07 Br temp function settings (parameters
alarmlim. 48.01…48.05).
Check alarm limit setting, parameter
48.07 Br temp alarmlim.
Check that braking cycle meets allowed
limits.

ABB ACS850 2012 (alarm) BC OVERHEAT Brake chopper IGBT Let chopper cool down.
(0x7181) temperature has exceeded Check for excessive ambient
internal alarm limit. temperature.
Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of
the cabinet.
Check resistor overload protection
function settings (parameters
48.0

ABB ACS850 2013 (alarm) DEVICE OVERTEMP Measured drive temperature Check ambient conditions.
(0x4210) has exceeded internal alarm Check air flow and fan operation.
limit. Check heatsink fins for dust pick-up.
Check motor power against unit power.

ABB ACS850 2014 (alarm) INTBOARD Interface board (between Let drive cool down.
OVERTEMP power unit and control unit) Check for excessive ambient
(0x7182) temperature has exceeded temperature.
internal alarm limit. Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of
the cabinet.

ABB ACS850 2015 (alarm) BC MOD OVERTEMP Input bridge or brake chopper Let drive cool down.
(0x7183) temperature has exceeded Check for excessive ambient
internal alarm limit. temperature.
Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of
the cabinet.

ABB ACS850 2017 (alarm) FIELDBUS COMM Cyclical communication Check status of fieldbus communication.
(0x7510) between drive and fieldbus See the appropriate User’s Manual of
Programmable fault: adapter module or between fieldbus adapter module.
50.02 Comm loss func PLC and fieldbus adapter Check settings of parameter group 50
module is lost. Fieldbus.
Check cable connections.
Check if communication master is able to
communicate.

ABB ACS850 2018 (alarm) LOCAL CTRL LOSS Control panel or PC tool Check PC tool or control panel
(0x5300) selected as active control connection.
Programmable fault: location for drive has ceased Check control panel connector.
30.03 Local ctrl loss communicating. Replace control panel in mounting
platform.

ABB ACS850 2019 (alarm) AI SUPERVISION An analog input has reached Check analog input source and
(0x8110) limit defined by parameter connections.
Programmable fault: 13.33 AI superv cw. Check analog input minimum and
13.32 AI superv func maximum limit settings.

ABB ACS850 2020 (alarm) FB PAR CONF The drive does not have a Check PLC programming.
(0x6320) functionality requested by Check settings of parameter group 50
PLC, or requested functionality Fieldbus.
has not been activated.

ABB ACS850 2021 (alarm) NO MOTOR DATA Parameters in group 99 have Check that all the required parameters in
(0x6381) not been set. group 99 have been set.
Note: It is normal for this alarm to appear
during the start-up until the motor data is
entered.
ABB ACS850 2022 (alarm) ENCODER 1 Encoder 1 has been activated Check parameter 90.01 Encoder 1 sel
FAILURE (0x7301) by parameter but the encoder setting corresponds to actual encoder
interface (FEN-xx) cannot be interface 1 (FEN-xx) installed in drive
found. Slot 1/2 (parameter 09.20 Option slot1 /
09.21 Option slot2).
Note: The new setting will only take
effect after parameter 90.10 Enc par
refre

ABB ACS850 2023 (alarm) ENCODER 2 Encoder 2 has been activated Check parameter 90.02 Encoder 2 sel
FAILURE (0x7381) by parameter but the encoder setting corresponds to actual encoder
interface (FEN-xx) cannot be interface 1 (FEN-xx) installed in drive
found. Slot 1/2 (parameter 09.20 Option slot1 /
09.21 Option slot2).
Note: The new setting will only take
effect after parameter 90.10 Enc par
refre

ABB ACS850 2027 (alarm) FEN TEMP MEAS Error in temperature Check that parameter 31.02 Mot temp1
FAILURE measurement when src / 31.06 Mot temp2 src setting
(0x7385) temperature sensor (KTY or corresponds to actual encoder interface
PTC) connected to encoder installation (09.20 Option slot1 / 09.21
interface FEN-xx is used. Option slot2):
If one FEN-xx module is used:
Error in temperature - Parameter 31.02 Mot temp1 src / 31.06
measurement when KTY Mot temp2 src must
sensor connected to encoder
interface FEN-01 is used.

ABB ACS850 2030 (alarm) RESOLVER Resolver autotuning routines, Check cable between resolver and
AUTOTUNE ERR which are automatically started resolver interface module (FEN-21) and
(0x7388) when resolver input is order of connector signal wires at both
activated for the first time, ends of cable.
have failed. Check resolver parameter settings.
For resolver parameters and information,
see parameter group 92 Resolver conf.
Note: Resolver

ABB ACS850 2031 (alarm) ENCODER 1 CABLE Encoder 1 cable fault detected. Check cable between FEN-xx interface
(0x7389) and encoder 1. After any modifications in
cabling, re-configure interface by
switching drive power off and on, or by
activating parameter 90.10 Enc par
refresh.

ABB ACS850 2032 (alarm) ENCODER 2 CABLE Encoder 2 cable fault detected. Check cable between FEN-xx interface
(0x738A) and encoder 2. After any modifications in
cabling, re-configure interface by
switching drive power off and on, or by
activating parameter 90.10 Enc par
refresh.

ABB ACS850 2033 (alarm) D2D On the master drive: The drive Check that all drives that are polled
COMMUNICATION has not been replied to by an (parameters 57.04 Follower mask 1 and
(0x7520) activated follower for five 57.05 Follower mask 2) on the drive-todrive
Programmable fault: consecutive polling cycles. link are powered, properly
57.02 Comm loss func connected to the link, and have the
On a follower drive: The drive correct node address.
has not received new Check the drive-to-drive link wiring.
reference 1 and/or 2 for five
consecutive reference Check the s
handling cycles.

ABB ACS850 2034 (alarm) D2D BUFFER Transmission of drive-to-drive Contact your local ABB representative.
OVERLOAD references failed because of
(0x7520) message buffer overflow.
Programmable fault:
57.02 Comm loss func

ABB ACS850 2035 (alarm) PS COMM Communication errors Check the connections between the JCU
(0x5480) detected between the JCU Control Unit and the power unit.
Control Unit and the power unit
of the drive.

ABB ACS850 2036 (alarm) RESTORE Restoration of backed-up Contact your local ABB representative.
(0x6300) parameters failed.
ABB ACS850 2037 (alarm) CUR MEAS Current measurement Informative alarm.
CALIBRATION calibration will occur at next
(0x2280) start.
ABB ACS850 2038 (alarm) AUTOPHASING Autophasing will occur at next Informative alarm.
(0x3187) start.
ABB ACS850 2039 (alarm) EARTH FAULT Drive has detected load Check there are no power factor
(0x2330) unbalance typically due to correction capacitors or surge absorbers
Programmable fault: earth fault in motor or motor in motor cable.
30.05 Earth fault cable. Check for an earth fault in motor or motor
cables by measuring the insulation
resistances of motor and motor cable.
If no earth fault can be detected, contact
your lo

ABB ACS850 2040 (alarm) AUTORESET A fault is to be autoreset. Informative alarm. See parameter group
(0x6080) 32 Automatic reset.
ABB ACS850 2041 (alarm) MOTOR NOM VALUE The motor configuration Check the settings of the motor
(0x6383) parameters are set incorrectly. configuration parameters in group 99.

The drive is not dimensioned Check that the drive is sized correctly for
correctly. the motor.

ABB ACS850 2042 (alarm) D2D CONFIG The settings of drive-to-drive Check the settings of the parameters in
(0x7583) link configuration parameters group 57 D2D communication.
(group 57) are incompatible.
ABB ACS850 2043 (alarm) STALL Motor is operating in stall Check motor load and drive ratings.
(0x7121) region because of e.g. Check fault function parameters.
Programmable fault: excessive load or insufficient
30.09 Stall function motor power.

ABB ACS850 2044 (alarm) LCURVE Overload or underload limit Check the settings of the parameters in
(0x2312) has been exceeded. group 34 User load curve.
Programmable fault:
34.01 Overload func /
34.02 Underload func

ABB ACS850 2045 (alarm) LCURVE PAR The load curve has been Check the settings of the parameters in
(0x6320) incorrectly or inconsistently group 34 User load curve.
defined.
ABB ACS850 2046 (alarm) FLUX REF PAR The U/f (voltage/frequency) Check the settings of the parameters in
(0x6320) curve has been incorrectly or group 38 Flux ref.
inconsistently defined.
ABB ACS850 2047 (alarm) SPEED FEEDBACK No speed feedback is Check the settings of the parameters in
(0x8480) received. group 19 Speed calculation.
Check encoder installation. See the
description of fault 0039 for more
information.

ABB ACS850 2048 (alarm) OPTION COMM Communication between drive Check that option modules are properly
LOSS and option module (FEN-xx connected to Slot 1 and (or) Slot 2.
(0x7000) and/or FIO-xx) is lost. Check that option modules or Slot 1/2
connectors are not damaged. To
determine whether module or connector
is damaged: Test each module
individually in Slot 1 and Slot 2.

ABB ACS850 2049 (alarm) MOTOR TEMP2 Estimated motor temperature Check motor ratings and load.
(0x4313) (based on motor thermal Let motor cool down. Ensure proper
Programmable fault: model) has exceeded alarm motor cooling: Check cooling fan, clean
31.05 Mot temp2 prot limit defined by parameter cooling surfaces, etc.
31.07 Mot temp2 almLim. Check value of alarm limit.
Check motor thermal model settings
Measured motor temperature (parameters 31.09…31.14).
has exceeded alarm limit
defined by parameter 31.07 Check that actual number of sensors
Mot temp2 almLim. c

ABB ACS850 2050 (alarm) IGBTOLALARM Excessive IGBT junction to Check motor cable.
(0x5482) case temperature. This alarm
protects the IGBT(s) and can
be activated by a short circuit
in the motor cable.

ABB ACS850 2051 (alarm) IGBTTEMPALARM Drive IGBT temperature is Check ambient conditions.
(0x4210) excessive. Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against drive power.

ABB ACS850 2052 (alarm) COOLING Drive module temperature is Check ambient temperature. If it exceeds
(0x4290) excessive. 40 °C (104 °F), ensure that load current
does not exceed derated load capacity of
drive. See the appropriate Hardware
Manual.
Check value of parameter 95.03 Temp
inu ambient.
Check drive module cooling air flow and

ABB ACS850 2053 (alarm) MENU CHG Loading a parameter listing Enter password at parameter 16.03 Pass
PASSWORD REQ requires a password. code.
(0x6F81)
ABB ACS850 2054 (alarm) MENU CHANGED A different parameter listing is Informative alarm.
(0x6F82) being loaded.
ABB ACS850 2055 (alarm) DEVICE CLEAN Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5080)
ABB ACS850 2056 (alarm) COOLING FAN Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5081)
ABB ACS850 2057 (alarm) ADD COOLING Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5082)
ABB ACS850 2058 (alarm) CABINET FAN Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5083)
ABB ACS850 2059 (alarm) DC CAPACITOR Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5084)
ABB ACS850 2060 (alarm) MOTOR BEARING Maintenance counter alarm. See parameter group 44 Maintenance.
(0x738C)
ABB ACS850 2061 (alarm) MAIN CONTACTOR Maintenance counter alarm. See parameter group 44 Maintenance.
(0x548D)
ABB ACS850 2062 (alarm) RELAY OUTPUT SW Maintenance counter alarm. See parameter group 44 Maintenance.
(0x548E)
ABB ACS850 2063 (alarm) MOTOR START Maintenance counter alarm. See parameter group 44 Maintenance.
COUNT
(0x6180)
ABB ACS850 2064 (alarm) POWER UP COUNT Maintenance counter alarm. See parameter group 44 Maintenance.
(0x6181)
ABB ACS850 2065 (alarm) DC CHARGE COUNT Maintenance counter alarm. See parameter group 44 Maintenance.
(0x6182)
ABB ACS850 2066 (alarm) ONTIME1 ALARM Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5280)
ABB ACS850 2067 (alarm) ONTIME2 ALARM Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5281)
ABB ACS850 2068 (alarm) EDGE1 ALARM Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5282)
ABB ACS850 2069 (alarm) EDGE2 ALARM Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5283)
ABB ACS850 2070 (alarm) VALUE1 ALARM Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5284)
ABB ACS850 2071 (alarm) VALUE2 ALARM Maintenance counter alarm. See parameter group 44 Maintenance.
(0x5285)
ABB ACS850 2072 (alarm) DC NOT CHARGED The voltage of the intermediate Wait for the DC voltage to rise.
(0x3250) DC circuit has not yet risen to
operating level.
ABB ACS850 2073 (alarm) SPEED CTRL TUNE Speed controller autotune See parameter 23.20 PI tune mode.
FAIL routine did not finish
(0x8481) successfully.
ABB ACS850 2074 (alarm) START INTERLOCK No Start interlock signal Check circuit connected to DIIL input.
(0xF082) received.
ABB ACS850 2076 (alarm) TEMP MEAS Problem with internal Contact your local ABB representative.
FAILURE temperature measurement of
(0x4211) the drive.
ABB ACS850 2077 (alarm) EFB COMM LOSS Embedded fieldbus interface Check:
(0x060E) has been taken into use, and • selection of the parameter which
there is a communication enables/disables EFB communication
break between the drive and (58.01 Protocol ena sel)
the master station. • EFB connection at terminal XD2D on
the JCU control unit
• status of the fieldbus master (online/
offline)
• settings of the communication
supervision f

ABB ACS850 2078 (alarm) TEMP DIFFERENCE High temperature difference Check cooling and the fan.
(0x4212) between the IGBTs of different
phases.
ABB ACS850 2079 (alarm) ENC 1 PULSE Encoder 1 is receiving too high Check encoder settings. After any
FREQUENCY data flow (pulse frequency). modifications, re-configure the interface
(0x738E) by activating parameter 90.10 Enc par
refresh.

ABB ACS850 2080 (alarm) ENC 2 PULSE Encoder 2 is receiving too high Check encoder settings. After any
FREQUENCY data flow (pulse frequency). modifications, re-configure the interface
(0x738F) by activating parameter 90.10 Enc par
refresh.

ABB ACS850 2081 (alarm) AO CALIBRATION Analog output calibration has Check that the analog output to be
(0x7380) failed. calibrated is connected to the
corresponding analog input (AO1 to AI1,
AO2 to AI2). See description of
parameter 15.30 AO calibration.
Check that the analog input has been set
to current using the jumper on the control
u

ABB ACS850 2082 (alarm) BR DATA Brake chopper is configured Check the brake chopper configuration in
(0x7113) wrong. parameter group 48 Brake chopper.
ABB ACS850 2400 (alarm) SOLUTION ALARM Alarm generated by custom Check custom application program.
(0x6F80) application program.
ABB ACS850 0001 OVERCURRENT Output current has exceeded Check motor load.
(0x2310) internal fault limit. Check acceleration times in parameter
group 22 Speed ref ramp.
Check motor and motor cable (including
phasing and delta/star connection).
Check that the start-up data in parameter
group 99 corresponds to the motor rating
plate.
Check tha

ABB ACS850 0002 DC OVERVOLTAGE Excessive intermediate circuit Check that overvoltage controller is on,
(0x3210) DC voltage parameter 47.01 Overvolt ctrl.
Check that the supply (input power)
voltage matches the drive nominal input
voltage.
Check mains for static or transient
overvoltage.
Check brake chopper and resistor (if
used).
Check
ABB ACS850 0004 SHORT CIRCUIT Short-circuit in motor cable(s) Check motor and motor cable.
(0x2340) or motor Check there are no power factor
correction capacitors or surge absorbers
Extension: 1 Short-circuit in the upper in motor cable.
transistor of U-phase. Check the fault logger for a fault code
extension. See appropriate actions for
Extension: 2 Short-circuit in the lower each extension below.
transistor of U-phase.

Extension: 4 Short-circuit in the upper

transistor of V-phase.

Extension: 8 Short-ci

ABB ACS850 0005 DC UNDERVOLTAGE Intermediate circuit DC voltage Check mains supply and fuses.
(0x3220) is not sufficient due to missing
mains phase, blown fuse or Get ABB to upgrade drive firmware from ver.2300 to ver2700
rectifier bridge internal fault.

ABB ACS850 0006 EARTH FAULT Drive has detected load Check there are no power factor
(0x2330) unbalance typically due to correction capacitors or surge absorbers
Programmable fault: earth fault in motor or motor in motor cable.
30.05 Earth fault cable. Check that there is no earth fault in motor
or motor cables:
- measure insulation resistances of motor
and motor cable.
If no earth fault can be detected, contact
you

ABB ACS850 0007 FAN FAULT Fan is not able to rotate freely Check fan operation and connection.
(0xFF83) or fan is disconnected. Fan
operation is monitored by
measuring fan current.

ABB ACS850 0008 IGBT OVERTEMP Drive temperature based on Check ambient conditions.
(0x7184) thermal model has exceeded Check air flow and fan operation.
internal fault limit. Check heatsink fins for dust pick-up.
Check motor power against unit power.

ABB ACS850 0009 BC WIRING Brake resistor short circuit or Check brake chopper and brake resistor
(0x7111) brake chopper control fault connection.
Ensure brake resistor is not damaged.
ABB ACS850 0010 BC SHORT CIRCUIT Short circuit in brake chopper Replace brake chopper.
(0x7113) IGBT Ensure brake resistor is connected and
not damaged.
ABB ACS850 0011 BC OVERHEAT Brake chopper IGBT Let chopper cool down.
(0x7181) temperature has exceeded Check for excessive ambient
internal fault limit. temperature.
Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of
the cabinet.
Check resistor overload protection
function settings (parameters
48.0

ABB ACS850 0012 BR OVERHEAT Brake resistor temperature has Stop drive. Let resistor cool down.
(0x7112) exceeded fault limit defined by Check resistor overload protection
parameter 48.06 Br temp function settings (parameters
faultlim. 48.01…48.05).
Check fault limit setting, parameter 48.06
Br temp faultlim.
Check that braking cycle meets allowed
limits.

ABB ACS850 0013 CURR MEAS GAIN Difference between output Contact your local ABB representative.
(0x3183) phase U2 and W2 current
measurement gain is too great.
ABB ACS850 0014 WIRING OR EARTH Incorrect input power and Check input power and motor cable
FAULT motor cable connection, or connections.
(0x3181) ground (earth) fault in the Check the insulation resistance of the
Programmable fault: motor cable or motor. motor cable and motor.
30.08 Wiring or earth

ABB ACS850 0015 SUPPLY PHASE Intermediate circuit DC voltage Check input power line fuses.
(0x3130) is oscillating due to missing Check for input power supply imbalance.
Programmable fault: input power line phase or
30.06 Suppl phs loss blown fuse.

ABB ACS850 0016 MOTOR PHASE Motor circuit fault due to Connect motor cable.
(0x3182) missing motor connection (all
Programmable fault: three phases are not
30.04 Mot phase loss connected).
ABB ACS850 0017 MOTOR ID-RUN Motor ID run was not Check the fault logger for a fault code
FAULT completed successfully. extension. See appropriate actions for
(0xFF84) Extension: 1 = The ID run cannot be each extension below.
completed because the
maximum current setting and/ 1. Check setting of parameters 99.06 Mot
or internal current limit of the nom current and 20.05 Maximum current.
drive is too low. Make sure that 20.05 Maximum current >
99.06 Mot nom current.
Extension: 2 = The ID run cannot be Check that
completed because the
maximum speed

ABB ACS850 0018 CURR U2 MEAS Measured offset error of U2 Contact your local ABB representative.
(0x3184) output phase current
measurement is too great.
(Offset value is updated during
current calibration.)

ABB ACS850 0019 CURR V2 MEAS Measured offset error of V2 Contact your local ABB representative.
(0x3185) output phase current
measurement is too great.
(Offset value is updated during
current calibration.)

ABB ACS850 0020 CURR W2 MEAS Measured offset error of W2 Contact your local ABB representative.
(0x3186) output phase current
measurement is too great.
(Offset value is updated during
current calibration.)

ABB ACS850 0021 STO1 LOST Safe torque off function is Check safety circuit connections. For
(0x8182) active, i.e. safety circuit signal more information, see the appropriate
1 connected between XSTO:1 drive Hardware Manual, description of
and XSTO:3 is lost. parameter 30.07 (page 199), and
Application guide - Safe torque off
function for ACSM1, ACS850 and
ACQ810 drives (3AFE68929814
[English]).

ABB ACS850 0022 0022 STO2 LOST Safe torque off function is Check safety circuit connections. For
(0x8183) active, i.e. safety circuit signal more information, see the appropriate
2 connected between XSTO:2 drive Hardware Manual, description of
and XSTO:4 is lost. parameter 30.07 (page 199), and
Application guide - Safe torque off
function for ACSM1, ACS850 and
ACQ810 drives (3AFE68929814
[English]).

ABB ACS850 0023 STO MODE CHANGE Error in changing Safe torque Contact your local ABB representative.
(0xFF7A) off supervision, i.e. parameter
30.07 Sto diagnostic setting
could not be changed to value
Fault.

ABB ACS850 0024 INTBOARD Interface board (between Let drive cool down.
OVERTEMP power unit and control unit) Check for excessive ambient
(0x7182) temperature has exceeded temperature.
internal fault limit. Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of
the cabinet.

First action is to check if the drive cooling fan is working and if th

ABB ACS850 0025 BC MOD OVERTEMP Input bridge or brake chopper Let drive cool down.
(0x7183) temperature has exceeded Check for excessive ambient
internal fault limit. temperature.
Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of
the cabinet.

ABB ACS850 0026 AUTOPHASING Autophasing routine (see Try other autophasing modes (see
(0x3187) section Autophasing on page parameter 11.07 Autophasing mode) if
68) failed. possible.
Ensure no slipping occurs between the
encoder and the motor shaft.

ABB ACS850 0027 PU LOST Connection between the JCU Check setting of parameter 95.01 Ctrl
(0x5400) Control Unit and the power unit boardSupply.
of the drive is lost. Check the connections between the JCU
Control Unit and the power unit.

First check the connections on the control unit. Then on the power unit.
If all this is checked, replace the control unit (1089 9549

ABB ACS850 0028 PS COMM Communication errors Check the connections between the JCU
(0x5480) detected between the JCU Control Unit and the power unit.
Control Unit and the power unit
of the drive.

ABB ACS850 0030 EXTERNAL Fault in external device. (This Check external devices for faults.
(0x9000) information is configured Check parameter 30.01 External fault
through one of programmable setting.
digital inputs.)
ABB ACS850 0031 SAFE TORQUE OFF Safe torque off function is Check safety circuit connections. For
(0xFF7A) active, i.e. safety circuit more information, see the appropriate
Programmable fault: signal(s) connected to drive Hardware Manual, and Application
30.07 Sto diagnostic connector XSTO is lost during guide - Safe torque off function for
start or run, or while drive is ACSM1, ACS850 and ACQ810 drives
stopped and parameter 30.07 (3AFE68929814 [English]).
Sto diagnostic is set to Fault.
This fault is somewhat misleading.. The STO

ABB ACS850 0032 OVERSPEED Motor is turning faster than Check minimum/maximum speed
(0x7310) highest allowed speed due to settings, parameters 20.01 Maximum
incorrectly set minimum/ speed and 20.02 Minimum speed.
maximum speed, insufficient Check adequacy of motor braking torque.
braking torque or changes in Check applicability of torque control.
load when using torque Check need for brake chopper and
reference. resistor(s).

If this fault code appears, please

ABB ACS850 0033 BRAKE START Mechanical brake fault. Fault is Check brake open torque setting,
TORQUE activated if required motor parameter 42.08.
(0x7185) starting torque (42.08 Brake Check drive torque and current limits.
Programmable fault: open torq) is not achieved. See parameter group 20 Limits.
42.12 Brake fault func

ABB ACS850 0034 BRAKE NOT Mechanical brake control fault. Check mechanical brake connection.
CLOSED Activated e.g. if brake Check mechanical brake settings in
(0x7186) acknowledgement is not as parameter group 42 Mech brake ctrl.
Programmable fault: expected during brake closing. To determine whether problem is with
42.12 Brake fault func acknowledgement signal or brake, check
if brake is closed or open.

ABB ACS850 0035 BRAKE NOT OPEN Mechanical brake control fault. Check mechanical brake connection.
(0x7187) Activated e.g. if brake Check mechanical brake settings in
Programmable fault: acknowledgement is not as parameter group 42 Mech brake ctrl.
42.12 Brake fault func expected during brake To determine whether problem is with
opening. acknowledgement signal or brake, check
if brake is closed or open.

ABB ACS850 0036 LOCAL CTRL LOSS Control panel or PC tool Check PC tool or control panel
(0x5300) selected as active control connection.
Programmable fault: location for drive has ceased Check control panel connector.
30.03 Local ctrl loss communicating. Replace

ABB ACS850 0037 NVMEM Drive internal fault. Check the fault logger for a fault code
CORRUPTED Note: This fault cannot be extension. See appropriate actions for
(0x6320) reset. each extension below.
*Refer to Application programming for
Extension: 2051 == Total number of parameters ACS850 and ACQ810 drives application
(including unused space guide (3AUA0000078664 [English]).
between parameters) exceeds
firmware maximum. *Move parameters from the firmware
groups to

ABB ACS850 0038 OPTIONCOMM LOSS Communication between drive Check that option modules are properly
(0x7000) and option module (FEN-xx connected to Slot 1 and (or) Slot 2.
and/or FIO-xx) is lost. Check that option modules or Slot 1/2
connectors are not damaged. To
determine whether module or connector
is damaged: Test each module
individually in Slot 1 and Slot 2.

ABB ACS850 0039 ENCODER 1 Encoder 1 feedback fault. If fault appears during first start-up before
(0x7301) encoder feedback is used:
- Check cable between encoder and
encoder interface module (FEN-xx) and
order of connector signal wires at both
ends of cable.
If fault appears after encoder feedback
has already been

ABB ACS850 0040 ENCODER 2 Encoder 2 feedback fault. See fault 0039.
(0x7381)
ABB ACS850 0045 FIELDBUS COMM Cyclical communication Check status of fieldbus communication.
(0x7510) between drive and fieldbus See the appropriate User’s Manual of
Programmable fault: adapter module or between fieldbus adapter module.
50.02 Comm loss func PLC and fieldbus adapter Check settings of parameter group 50
module is lost. Fieldbus.
Check cable connections.
Check if communication master is able to
communicate.

ABB ACS850 0046 FB MAPPING FILE Drive internal fault Contact your local ABB representative.
(0x6306)
ABB ACS850 0047 MOTOR OVERTEMP Estimated motor temperature Check motor ratings and load.
(0x4310) (based on motor thermal Let motor cool down. Ensure proper
Programmable fault: model) has exceeded fault limit motor cooling: Check cooling fan, clean
31.01 Mot temp1 prot defined by parameter 31.04 cooling surfaces, etc.
Mot temp1 fltLim. Check value of fault limit.
Check motor thermal model settings
Measured motor temperature (parameters 31.09…31.14).
has exceeded fault limit
defined by parameter 31.04 Check that actual number of sensors
Mot temp1 fltLim. c
Faulty temperature sensor o

ABB ACS850 0049 AI SUPERVISION An analog input has reached Check analog input source and
(0x8110) limit defined by parameter connections.
Programmable fault: 13.33 AI superv cw. Check analog input minimum and
13.32 AI superv func maximum limit settings.

ABB ACS850 0050 ENCODER 1 CABLE Encoder 1 cable fault detected. Check cable between FEN-xx interface
(0x7389) and encoder 1. After any modifications in
Programmable fault: cabling, re-configure interface by
90.05 Enc cable fault switching drive power off and on, or by
activating parameter 90.10 Enc par
refresh.

ABB ACS850 0051 ENCODER 2 CABLE Encoder 2 cable fault detected. Check cable between FEN-xx interface
(0x738A) and encoder 2. After any modifications in
Programmable fault: cabling, re-configure interface by
90.05 Enc cable fault switching drive power off and on, or by
activating parameter 90.10 Enc par
refresh.

ABB ACS850 0052 D2D CONFIG Configuration of the drive-todrive Contact your local ABB representative.
(0x7583) link has failed for a
reason other than those
indicated by alarm A-2042, for
example start inhibition is
requested but not granted.

ABB ACS850 0053 D2D COMM On the master drive: The drive Check that all drives that are polled
(0x7520) has not been replied to by an (parameters 57.04 Follower mask 1 and
Programmable fault: activated follower for five 57.05 Follower mask 2) on the drive-todrive
57.02 Comm loss func consecutive polling cycles. link are powered, properly
connected to the link, and have the
On a follower drive: The drive correct node address.
has not received new Check the drive-to-drive link wiring.
reference 1 and/or 2 for five
consecutive reference Check the s
handling cycles.

ABB ACS850 0054 D2D BUF OVLOAD Transmission of drive-to-drive Contact your local ABB representative.
(0x7520) references failed because of
Programmable fault: message buffer overflow.
90.05 Enc cable fault

ABB ACS850 0055 TECH LIB Resettable fault generated by Refer to the documentation of the
(0x6382) a technology library. technology library.
ABB ACS850 0056 TECH LIB CRITICAL Permanent fault generated by Refer to the documentation of the
(0x6382) a technology library. technology library.
ABB ACS850 0057 FORCED TRIP Generic Drive Communication Check PLC status.
(0xFF90) Profile trip command.
ABB ACS850 0058 FB PAR ERROR The drive does not have a Check PLC programming.
(0x6320) functionality requested by Check settings of parameter group 50
PLC, or requested functionality Fieldbus.
has not been activated.

ABB ACS850 0059 STALL Motor is operating in stall Check motor load and drive ratings.
(0x7121) region because of e.g. Check fault function parameters.
Programmable fault: excessive load or insufficient
30.09 Stall function motor power.

ABB ACS850 0060 LOAD CURVE Overload or underload limit Check the settings of the parameters in
(0x2312) has been exceeded. group 34 User load curve.
Programmable fault:
34.01 Overload func /
34.02 Underload func

ABB ACS850 0061 SPEED FEEDBACK No speed feedback is Check the settings of the parameters in
(0x8480) received. group 19 Speed calculation.
Check encoder installation. See the
description of fault 0039 (ENCODER1)
for more information.

ABB ACS850 0062 D2D SLOT COMM Drive-to-drive link is set to use Check the settings of parameters 57.01
(0x7584) an FMBA module for and 57.15. Ensure that the FMBA
communication, but no module module has been detected by checking
is detected in specified slot. parameters 09.20…09.22.
Check that the FMBA module is correctly
wired.
Try installing the FMBA module into
another slot. If the problem persists,
c
ABB ACS850 0063 MOTOR TEMP2 Estimated motor temperature Check motor ratings and load.
(0x4313) (based on motor thermal Let motor cool down. Ensure proper
Programmable fault: model) has exceeded fault limit motor cooling: Check cooling fan, clean
31.05 Mot temp2 prot defined by parameter 31.08 cooling surfaces, etc.
Mot temp2 fltLim. Check value of alarm limit.
Check motor thermal model settings
Measured motor temperature (parameters 31.09…31.14).
has exceeded fault limit
defined by parameter 31.08 Check that actual number of sensors
Mot temp2 fltLim. c
Faulty temperature sensor o

ABB ACS850 fluctuating speed Fluctuation in motor speed Probably corrupted memory module 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:

ABB ACS880 A2A1 current calibration Current offset and again measuremtn calibration wil occur at next start Inofmative warning. (See parameter 99.13 ID run requested.)
ABB ACS880 A2B1 Overcurrent Output current has exceeded Check motor load.
internal fault limit. Check acceleration times in parameter
group 23 Speed reference ramp (speed
control), 26 Torque reference chain
(torque control) or 28 Frequency
reference chain (frequency control). Also
check parameters 46.01 Speed scaling,
46.02 Frequency scaling and 46.03
Torque scaling.
Check motor and motor cable (including
phasing and delta/star connection).
Check there are no contactors opening
and closing in motor cable.
Check that the start-up data in parameter
group 99 corresponds to the motor rating
plate.
Check that there are no power factor
correction capacitors or surge absorbers
in motor cable.
Check encoder cable (including
phasing).

ABB ACS880 A2B3 Earth Leakage Drive has detected load unbalance typically Check there are no power factor
due to earth fault in motor or motor cable. correction capacitors or surge absorbers
in motor cable.
Check for an earth fault in motor or motor
cables by measuring the insulation
resistances of motor and motor cable.
Try running the motor in scalar control
mode if allowed. (See parameter 99.04
Motor control mode.)
If no earth fault can be detected, contact
your local ABB representative.

ABB ACS880 A2B4 Short Circuit Short circuit in motor cable(S) or motor Check motor and motor cable for cabling
errors.
Check there are no power factor
correction capacitors or surge absorbers
in motor cable.

ABB ACS880 A2BA IGBT overload Excessive IGBT junction to Check motor cable.
case temperature. This Check ambient conditions.
warning protects the IGBT(s) Check air flow and fan operation.
and can be activated by a short Check heatsink fins for dust pick-up.
circuit in the motor cable. Check motor power against drive power.

ABB ACS880 A3A1 DC link overvoltage Intermediate circuit DC voltage too high (when the drive is stopped). Check the supply voltage setting
(parameter 95.01 Supply voltage). Note
that the wrong setting of the parameter
may cause the motor to rush
uncontrollably, or may overload the brake
chopper or resistor.
Check the supply voltage.
With A3A1 or A3A2 on parallelconnected
inverter modules, the auxiliary
code indicates the affected module. The
format of the code is 0x000X XX00,
where “XXX” specifies the channel on the
BCU control unit.
If the problem persists, contact your local
ABB representative.
ABB ACS880 A3A2 DC link undervoltage Intermediate circuit DC voltage too low (when the drive is stopped) Check the supply voltage setting
(parameter 95.01 Supply voltage). Note
that the wrong setting of the parameter
may cause the motor to rush
uncontrollably, or may overload the brake
chopper or resistor.
Check the supply voltage.
With A3A1 or A3A2 on parallelconnected
inverter modules, the auxiliary
code indicates the affected module. The
format of the code is 0x000X XX00,
where “XXX” specifies the channel on the
BCU control unit.
If the problem persists, contact your local
ABB representative.

ABB ACS880 A3AA DC not charged The voltage of the intermediate DC circuit has not yet risen to operating level Check the supply voltage setting
(parameter 95.01 Supply voltage). Note
that the wrong setting of the parameter
may cause the motor to rush
uncontrollably, or may overload the brake
chopper or resistor.
Check the supply voltage.
With A3A1 or A3A2 on parallelconnected
inverter modules, the auxiliary
code indicates the affected module. The
format of the code is 0x000X XX00,
where “XXX” specifies the channel on the
BCU control unit.
If the problem persists, contact your local
ABB representative.

ABB ACS880 A480 Motor cable overload Calculated motor cable temperature has exceeded warning light Check the settings of parameters 35.61
and 35.62.
Check the dimensioning of the motor
cable in regard to required load.

ABB ACS880 A490 Incorrect temperature sensor setup sensor type mismatch Check the settings of temperature source
parameters 35.11 and 35.21 against
91.21 and 91.24.
ABB ACS880 A490 Incorrect temperature sensor setup Faulty wiring between an Check the wiring of the sensor.
encoder interface module and The auxiliary code identifies the interface
the temperature sensor. module. (0 = Module 1, 1 = Module 2).
ABB ACS880 A491 External temperature 1 (editable message text) Measured temperautre 1 has exceeded warning limit Check the value of parameter 35.02
Measured temperature 1.
Check the cooling of the motor (or other
equipment whose temperature is being
measured).
Check the value of 35.13 Temperature 1
warning limit.

ABB ACS880 A492 External temperature Measured temperature 2 has Check the value of parameter 35.03
2 exceeded warning limit. Measured temperature 2.
Editable message text) Check the cooling of the motor (or other
equipment whose temperature is being
measured).
Check the value of 35.23 Temperature 2
warning limit.

ABB ACS880 A4A0 Several Meanings: Control unit temperature is excessive. Check the auxiliary code. See actions for
- Control Board Temperature each code below.
- (none) Temperature above warning limit
-1 Check ambient conditions.
Thermistor broken Check air flow and fan operation.
Check heatsink fins for dust pick-up.

contact an ABB service representative for control unit replacement

ABB ACS880 A4A1 IGBT overtemperature Estimated drive IGBT temperature is excessive Check ambient conditions.
Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against drive power.

ABB ACS880 A4A9 cooling Drive module temperature is Check ambient temperature. If it exceeds
excessive. 40 °C (104 °F), ensure that load current
does not exceed derated load capacity of
drive. See appropriate Hardware manual.
Check drive module cooling air flow and
fan operation.
Check inside of cabinet and heatsink of
drive module for dust pick-up. Clean
whenever necessary.
ABB ACS880 A4B0 excess temperature Power unit module Check ambient conditions.
temperature is excessive. Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against drive power.
Check the auxiliary code (format XXXY
YYZZ). “Y YY” specifies through which
BCU control unit channel the fault was
received. “ZZ” specifies the location (1:
U-phase, 2: V-phase, 3: W-phase, 4: INT
board, 5: Brake chopper, 6: Air inlet, 7:
Power supply board, 8: du/dt filter (R8i)
or temperature switch (XT), 0FA:
Ambient temperature).

ABB ACS880 A4B1 Excess temperature High temperature difference Check the motor cabling.
difference between the IGBTs of different Check cooling of drive module(s).
phases. Check the auxiliary code (format XXXY
YYZZ). “XXX” indicates the source of
difference (0: Single module, difference
between phase IGBTs, 1: parallelconnected
modules, minimum-maximum
difference between all IGBTs of all
modules). With parallel-connected
modules, “Y YY” specifies through which
BCU control unit channel the fault was
received. “ZZ” specifies the phase (0:
single module, 1: U-phase [parallel
connection], 2: W-phase [parallel
connection], 3: W-phase [parallel
connection]).

ABB ACS880 A4B2 PCB space cooling Temperature difference Check the cooling fan inside the PCB
between ambient and drive space.
module PCB space is With parallel-connected modules, check
excessive. the auxiliary code (format XXXY YYZZ).
“Y YY” specifies through which BCU
control unit channel the fault was
received.

ABB ACS880 A4F6 IGBT temperature Drive IGBT temperature is Check ambient conditions.
excessive. Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against drive power.

ABB ACS880 A580 PU communication Communication errors Check the connections between the drive
detected between the drive control unit and the power unit.
control unit and the power unit. Check the auxiliary code (format XXXY
YYZZ). “XXX” specifies the detailed
transmission error warning code. With
parallel-connected modules, “Y YY”
specifies the affected BCU control unit
channel (0: broadcast). “ZZ” specifies the
error source (8: Transmission errors in
PSL link [detailed code in XXX],
9: Transmitter FIFO warning limit hit).

ABB ACS880 A581 Fan Cooling fan stuck or Check the auxiliary code to identify the
disconnected. fan. Code 0 denotes main fan 1. Other
codes (format XYZ): “X” specifies state
code (1: ID run, 02: normal). “Y” specifies
the index of the inverter unit connected to
BCU (0…n, always 0 for ZCU control
units). “Z” specifies the index of the fan
(0: Main fan 1, 1: Main fan 2, 2: Main fan
3, 3: Auxiliary fan 1, 4: Auxiliary fan 2, 5:
Auxiliary fan 3, 6: Filter fan 1, 7: Filter fan
2, 8: Filter fan 3).
Check fan operation and connection.
Replace fan if faulty.

ABB ACS880 A582 Auxiliary fan missing An auxiliary cooling fan Check auxiliary fan(s) and connection(s).
(connected to the fan Replace faulty fan.
connectors on the control unit) Make sure the front cover of the drive
is stuck or disconnected. module is in place and tightened. If the
commissioning of the drive requires that
the cover is off, this warning will be
generated even if the corresponding fault
is defeated. See fault 5081 Auxiliary fan
broken (page 457).

ABB ACS880 A5A0 Safe torque off Safe torque off function is active, i.e. safety circuit signal(s) connected to connector Check safety circuit connections. For
Programmable warning: XSTO is lost. more information, see appropriate drive
31.22 STO indication hardware manual and description of
run/stop parameter 31.22 STO indication run/stop
page 246).
ABB ACS880 A5EA Measurement circuit Problem with internal Check the auxiliary code (format XXXY
temperature temperature measurement of YYZZ). “Y YY” specifies through which
the drive. BCU control unit channel the fault was
received. “ZZ” specifies the location (1:
U-phase, 2: V-phase, 3: W-phase, 4: INT
board, 5: Brake chopper, 6: Air inlet, 7:
Power supply board, 8: du/dt filter).

ABB ACS880 A5EB PU board powerfail Power unit power supply Contact your local ABB representative
failure.
ABB ACS880 A5EC PU communication internal Communication errors Check the connections between the drive
detected between the drive control unit and the power unit.
control unit and the power unit.
ABB ACS880 A5ED Measurement circuit Measurement circuit fault. Contact your local ABB representative
ADC
ABB ACS880 A5EE Measurement circuit DFF Measurement circuit fault. Contact your local ABB representative
ABB ACS880 A5EF PU state feedback State feedback from output Contact your local ABB representative.
phases does not match control
signals.
ABB ACS880 A5F0 Charging feedback Charging feedback signal Check the feedback signal coming from
missing. the charging system.
ABB ACS880 A5F3 switching frequency below requested Adequate motor control at Informative warning
requested output frequency
cannot be reached because of
limited switching frequency
(eg. by parameter 95.15).

ABB ACS880 A683 Data saving to power unit an error in saving data to the power unit contact your local ABB representative
ABB ACS880 A684 SD card Error related to SD card used to store data (BCU control unit only) Check the auxiliary code. See actions for
each code below.
For 1 - No SD card - Insert a compatible, writable SD card into
the SD CARD slot of the BCU control
unit.
For 2 - SD Card write protected - Insert a compatible, writable SD card into
the SD CARD slot of the BCU control
unit.
For 3 - SD card unreadable - Insert a compatible, writable SD card into
the SD CARD slot of the BCU control
unit.

ABB ACS880 A685 Power fail saving power fail saving is requested too frequently due to oscillating power supply to the Check the power supply of the control
control unit. Some of the requests may have been discarded, potentially causing unit. If powered internally from the drive,
data loss. check the supply voltage of the drive.
ABB ACS880 A6A4 Motor nominal value The motor parameters are set incorrectly Check the auxiliary code. See actions for
each code below.
1 - Slip frequency is too small
2 - Synchronous and nominal speeds differ too much
3 - Nominal speed is higher than synchronous speed with 1 pole pair
4 - Nominal current is outside limits
5 - Nominal voltage is outside limits
6 - Nominal power is higher than apparent power
7 - Nominal power not consistent with nominal speed and torque
For all code values Check the settings of the motor
configuration parameters in groups 98
and 99.
Check that the drive is sized correctly for
the motor.

ABB ACS880 A6A4 Motor nominal value The drive is not dimensioned Check the auxiliary code. See actions for
correctly. each code below.
1 - Slip frequency is too small
2 - Synchronous and nominal speeds differ too much
3 - Nominal speed is higher than synchronous speed with 1 pole pair
4 - Nominal current is outside limits
5 - Nominal voltage is outside limits
6 - Nominal power is higher than apparent power
7 - Nominal power not consistent with nominal speed and torque
For all code values Check the settings of the motor
configuration parameters in groups 98
and 99.
Check that the drive is sized correctly for
the motor.

ABB ACS880 A6A5 no motor data parameters in group 99 have not been set Check that all the required parameters in
group 99 have been set.
Note: It is normal for this warning to
appear during the start-up and continue
until the motor data is entered.

ABB ACS880 A6D1 FBA A parameter conflict The drive does not have a Check PLC programming.
functionality requested by a Check settings of parameter groups 50
PLC, or requested functionality Fieldbus adapter (FBA) and 51 FBA A
has not been activated. settings.
ABB ACS880 A6D2 FBA B parameter conflict The drive does not have a Check PLC programming.
functionality requested by a Check settings of parameter groups 50
PLC, or requested functionality Fieldbus adapter (FBA) and 54 FBA B
has not been activated. settings.

ABB ACS880 A6E5 AI parametization The current/voltage hardware Check the auxiliary code. The code
setting of an analog input does identifies the analog input whose settings
not correspond to parameter are in conflict.
settings. Adjust either the hardware setting (on the
drive control unit) or parameter
12.15/12.25.
Note: Control board reboot (either by
cycling the power or through parameter
96.08 Control board boot) is required to
validate any changes in the hardware
settings.

ABB ACS880 A780 Motor stall Motor is operating in stall Check motor load and drive ratings.
Programmable warning: region because of e.g. Check fault function parameters.
31.24 Stall function excessive load or insufficient
motor power.

ABB ACS880 A781 Motor fan No feedback received from Check external fan (or other equipment
Programmable warning: external fan. controlled) by the logic.
35.106 DOL starter event Check settings of parameters
type 35.100…35.106.

ABB ACS880 A782 FEN temperature Error in temperature Check that parameter 35.11 Temperature
measurement when source / 35.21 Temperature 2 source
temperature sensor (KTY or setting corresponds to actual encoder
PTC) connected to encoder interface installation.
interface FEN-xx is used.

ABB ACS880 A782 FEN temperature Error in temperature FEN-01 does not support temperature
measurement when KTY measurement with KTY sensor. Use PTC
sensor connected to encoder sensor or other encoder interface
interface FEN-01 is used. module.

ABB ACS880 A791 Brake resistor Brake resistor temperature has Stop drive. Let resistor cool down.
exceeded warning limit defined Check resistor overload protection
by parameter 43.12 Brake function settings (parameter group 43
resistor warning limit. Brake chopper).
Check warning limit setting, parameter
43.12 Brake resistor warning limit.
Check that the resistor has been
dimensioned correctly.
Check that braking cycle meets allowed
limits.

ABB ACS880 A793 BR excess temperature Brake resistor temperature has Stop drive. Let resistor cool down.
exceeded warning limit defined Check resistor overload protection
by parameter 43.12 Brake function settings (parameter group 43
resistor warning limit. Brake chopper).
Check warning limit setting, parameter
43.12 Brake resistor warning limit.
Check that the resistor has been
dimensioned correctly.
Check that braking cycle meets allowed
limits.

ABB ACS880 A794 BR Data Breake resistor data has not been given One or more of the resistor data settings
(parameters 43.08…43.10) is incorrect.
The parameter is specified by the
auxiliary code.
0000 0001 - Resistance Value too low - Check value of brake resistance
0000 0002 - Thermal time constant not given - Check value of thermal time constant of
the brake resistor
0000 0003 - Maximum continuous power not given - Check value of maximum continous
braking power of the resistor

ABB ACS880 A797 Speed feedback configuration speed faceback configuration has changed Check the auxiliary code (format XXYY ZZZZ). “XX” specifies the number of the encoder
interface module (01: 91.11/91.12, 02: 91.13/91.14), “YY” specifies the encoder (01: 92
Encoder 1 configuration, 02: 93 Encoder 2 configuration). “ZZZZ” indicates the problem
(see actions for each code below).
0001 - Adapter not found in specified slot - Check module location
0002 - Detected type of interface module does not match parameter setting - Check
module type against status
0003 - Logic version too old - Contact your local ABB representative
0004 - Software version too old - Contact your local ABB prepresentative
0006 - Encoder type incompatible with interface module type - Check module type
(91.11 or 91.13) against encoder type (92.01 or 93.01).
0007 - Adapter not configured - Check module location
0008 - Speed feedback configuation has changed - Use parameter 91.10 Encode
parameter refresh) to validate any changes in the settings.
0009 - No encorders to configure encoder module - Configure the encoder in group 92
Encoder 1 configuration or 93 Encoder 2 configuration.
000A - Non-existing emulation input - Check input selection
000B - Echo not supported by selected input (for example, resolver or aboluate encoder)
- Check input selection (91.31 or 91.41), interface module type, and encoder type.
000C - Emulation in continuous mode not supported - Check input selection (91.31 or
91.41) and serial link mode (92.30 or 93.30) settings.
ABB ACS880 A79B BC short circuit Short circuit in brake chopper Replace brake chopper if external. Drives with internal choppers will need to be
IGBT returned to ABB.
Ensure brake resistor is connected and not damaged.
ABB ACS880 A79C BC IGBT excess Brake chopper IGBT Let chopper cool down.
temperature temperature has exceeded Check for excessive ambient temperature.
internal warning limit. Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of the cabinet.
Check resistor overload protection function settings (parameters 43.06…43.10).
Check minimum allowed resistor value for the chopper being used.
Check that braking cycle meets allowed limits.
Check that drive supply AC voltage is not excessive.

ABB ACS880 A7A1 Mechanical brake closing failed Status of mechanical brake acknowledgement is not as Check mechanical brake connection.
Programmable warning: 44.17 Brake fault function expected during brake close. Check mechanical brake settings in
parameter group 44 Mechanical brake
control.
Check that acknowledgement signal
matches actual status of brake.

ABB ACS880 A7A2 Mechanical brake Status of mechanical brake Check mechanical brake connection.
opening failed acknowledgement is not as Check mechanical brake settings in parameter group 44 Mechanical brake control.
Programmable warning: expected during brake open. Check that acknowledgement signal matches actual status of brake.
44.17 Brake fault function

ABB ACS880 A7A5 Mechanical brake Open conditions of mechanical Check mechanical brake settings in
opening not allowed brake cannot be fulfilled (for parameter group 44 Mechanical brake
Programmable warning: example, brake has been control (especially 44.11 Keep brake
44.17 Brake fault function prevented from opening by closed).
parameter 44.11 Keep brake Check that acknowledgement signal (if
closed). used) matches actual status of brake.

ABB ACS880 A7AA Extension AI The hardware current/voltage Check the auxiliary code (format XX00 00YY). “XX” specifies the number of the I/O
parameterization setting of an analog input (on extension module (01: parameter group 14 I/O extension module 1, 02: 15 I/O extension
an I/O extension module) does module 2, 03: 16 I/O extension module 3). “YY” specifies the analog input on the
not correspond to parameter module. For example, in case of I/O extension module 1, analog input AI1 (auxiliary code
settings. 0000 0101), the hardware current/voltage setting on the module is shown by parameter
14.29. The corresponding parameter setting is 14.30. Adjust either the hardware setting
on the module or the parameter to solve the mismatch.
Note: Control board reboot (either by cycling the power or through parameter 96.08
Control board boot) is required to validate any changes in the hardware settings.

ABB ACS880 A7AB Extension I/O The I/O extension module Check the auxiliary code. The code
configuration failure types and locations specified indicates which I/O extension module is
by parameters do not match affected.
the detected configuration. 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.

ABB ACS880 A7B0 Motor speed feedback No motor speed feedback is Check the auxiliary code (format XXYY ZZZZ). “XX” specifies the number of the
Programmable warning: received. encoder interface module (01: 91.11/91.12, 02: 91.13/91.14), “YY” specifies the encoder
90.45 Motor feedback fault (01: 92 Encoder 1 configuration, 02: 93 Encoder 2 configuration). “ZZZZ” indicates the
problem (see actions for each code below).
0001 - Motor gear definition invalid or outside limits - Check motor gear settings (90.43
and 90.44).
0002 - Encoder not configured - Check encoder settings (92 Encoder 1 configuration or
93 Encoder 2 configuration).
Use parameter 91.10 Encoder parameter refresh) to validate any changes in the
settings.
0003 - Encoder stopped working - Check encoder status
0004 - Encoder drift detected - Check for slippage between encoder and motor

ABB ACS880 A7B1 Load speed feedback No load speed feedback is Check the auxiliary code (format XXYY ZZZZ). “XX” specifies the number of the encoder
Programmable warning: received. interface module (01: 91.11/91.12, 02: 91.13/91.14), “YY”n specifies the encoder (01: 92
90.55 Load feedback fault Encoder 1 configuration, 02: 93 Encoder 2 configuration). “ZZZZ” indicates the problem
(see actions for each code below).
0001 - Load gear definition invalid or outside limits - check load gear settings 90.53 and
90.54)
0002 - Feed constant definition invalid or outside limits - Check feed constant settings
(90.63 and
90.64).
0003 - Encoder stopped working - check encoder status

ABB ACS880 A7C1 FBA A communication Cyclical communication Check status of fieldbus communication.
Programmable warning: between drive and fieldbus See user documentation of fieldbus
50.02 FBA A comm loss adapter module A or between interface.
func PLC and fieldbus adapter Check settings of parameter groups 50
module A is lost. Fieldbus adapter (FBA), 51 FBA A
settings, 52 FBA A data in and 53 FBA A
data out.
Check cable connections.
Check if communication master is able to
communicate.
ABB ACS880 A7C2 FBA B communication Cyclical communication Check status of fieldbus communication.
Programmable warning: between drive and fieldbus See user documentation of fieldbus
50.32 FBA B comm loss adapter module B or between interface.
func PLC and fieldbus adapter Check settings of parameter group 50
Fieldbus adapter (FBA).
module B is lost. Check cable connections.
Check if communication master is able to
communicate.

ABB ACS880 A7CB DDCS controller DDCS (fiber optic) Check status of controller. See user
comm loss communication between drive documentation of controller.
Programmable warning: and external controller is lost. Check settings of parameter group 60
60.59 DDCS controller DDCS communication.
comm loss function Check cable connections. If necessary,
replace cables.

ABB ACS880 A7CE EFB comm loss Communication break in Check the status of the fieldbus master
Programmable warning: embedded fieldbus (EFB) online/offline/error etc.).
58.14 Communication loss communication. Check cable connections to the XD2D
action connector on the control unit.

ABB ACS880 A7E1 Encoder Encoder Error Check the auxiliary code (format XXYY ZZZZ). “XX” specifies the number of encoder
Programmable warning: interface module (01: 91.11/91.12, 02: 91.13/91.14), “YY” specifies the encoder (01: 92
90.45 Motor feedback fault Encoder configuration, 02: 93 Encoder 2 configuration). “ZZZZ” indicates the problem
(see actions for each code below).
0001 - Cable Fault - Check the conductor order at both ends of the encoder cable.
Check the groundings of the encoder cable.
If the encoder was working previously, check the encoder, encoder cable and
encoder interface module for damage.
See also parameter 92.21 Encoder cable fault mode.
0002 - No Encoder Signal - Check the condiiton of the encoder
0003 - Overspeed - Contact your local ABB representative.
0004 - Overfrequency - Contact your local ABB representative.
0005 - Resolver ID run failed - Contact your local ABB representative.
0006 - Resolver overcurrent fault - Contact your local ABB representative.
0007 - Speed scaling error - Contact your local ABB representative.

ABB ACS880 A7EE Panel Loss Programmable warning: Control panel or PC tool selected as active control location for drive has ceased Check PC tool or control panel connection.
49.05 Communication loss communicating. Check control panel connector.
action Check mounting platform if being used.
Disconnect and reconnect the control panel.

ABB ACS880 A880 Motor bearing Warning generated by an on-time timer or a value counter Check the auxiliary code. Check the source of the warning corresponding to the code:
Programmable warnings: 0: 33.13 On-time 1 source
33.14 On-time 1 warn message 1: 33.23 On-time 2 source
33.24 On-time 2 warn message 4: 33.53 Value counter 1 source
33.55 Value counter 1 warn message 5: 33.63 Value counter 2 source.
33.65 Value counter 2 warn message

ABB ACS880 A881 Output relay Warning generated by an edge counter. Check the auxiliary code. Check the source of the warning corresponding to the code:
Programmable warnings: 2: 33.33 Edge counter 1 source
33.35 Edge counter 1 warn message 3: 33.43 Edge counter 2 source.
33.45 Edge counter 2 warn Message

ABB ACS880 A882 Motor Starts Warning generated by an edge counter. Check the auxiliary code. Check the source of the warning corresponding to the code:
Programmable warnings: 2: 33.33 Edge counter 1 source
33.35 Edge counter 1 warn message 3: 33.43 Edge counter 2 source.
33.45 Edge counter 2 warn Message

ABB ACS880 A883 Power Ups Warning generated by an edge counter. Check the auxiliary code. Check the source of the warning corresponding to the code:
Programmable warnings: 2: 33.33 Edge counter 1 source
33.35 Edge counter 1 warn message 3: 33.43 Edge counter 2 source.
33.45 Edge counter 2 warn Message

ABB ACS880 A884 Main contactor Warning generated by an edge counter. Check the auxiliary code. Check the source of the warning corresponding to the code:
Programmable warnings: 2: 33.33 Edge counter 1 source
33.35 Edge counter 1 warn message 3: 33.43 Edge counter 2 source.
33.45 Edge counter 2 warn Message

ABB ACS880 A885 DC charge Warning generated by an edge counter. Check the auxiliary code. Check the source of the warning corresponding to the code:
Programmable warnings: 2: 33.33 Edge counter 1 source
33.35 Edge counter 1 warn message 3: 33.43 Edge counter 2 source.
33.45 Edge counter 2 warn Message

ABB ACS880 A886 On-time 1 Warning generated by on-time Check the source of the warning
timer 1. (parameter 33.13 On-time 1 source)
ABB ACS880 A887 On-time 2 Warning generated by on-time Check the source of the warning
(Editable message text) timer 2. (parameter 33.23 On-time 2 source).
Programmable warning:
33.24 On-time 2 warn
message

ABB ACS880 A888 Edge counter 1 Warning generated by edge counter 1 Check the source of the warning
Editable message text) (parameter 33.33 Edge counter 1
Programmable warning: source).
33.35 Edge counter 1
warn message

ABB ACS880 A889 Edge counter 2 Warning generated by edge Check the source of the warning
(Editable message text) counter 2. parameter 33.43 Edge counter 2
Programmable warning: source).
33.45 Edge counter 2
warn message
ABB ACS880 A88A Value counter 1 Warning generated by value Check the source of the warning
(Editable message text) counter 1. (parameter 33.53 Value counter 1
Programmable warning: source).
33.55 Value counter 1
warn message

ABB ACS880 A88B Value counter 2 Warning generated by value counter 2 Check the source of the warning
(Editable message text) (parameter 33.63 Value counter 2
Programmable warning: source).
33.65 Value counter 2
warn message

ABB ACS880 A88C Device clean Warning generated by an ontime Check the auxiliary code. Check the
timer. source of the warning corresponding to
Programmable warnings: the code:
33.14 On-time 1 warn message 0: 33.13 On-time 1 source
33.24 On-time 2 warn message 1: 33.23 On-time 2 source
10: 05.04 Fan on-time counter.

ABB ACS880 A88D DC capactior Warning generated by an ontime Check the auxiliary code. Check the
timer. source of the warning corresponding to
Programmable warnings: the code:
33.14 On-time 1 warn message 0: 33.13 On-time 1 source
33.24 On-time 2 warn message 1: 33.23 On-time 2 source
10: 05.04 Fan on-time counter.

ABB ACS880 A88E Cabinet fan Warning generated by an ontime Check the auxiliary code. Check the
timer. source of the warning corresponding to
Programmable warnings: the code:
33.14 On-time 1 warn message 0: 33.13 On-time 1 source
33.24 On-time 2 warn message 1: 33.23 On-time 2 source
10: 05.04 Fan on-time counter.

ABB ACS880 A88F cooling fan Warning generated by an ontime Check the auxiliary code. Check the
timer. source of the warning corresponding to
Programmable warnings: the code:
33.14 On-time 1 warn message 0: 33.13 On-time 1 source
33.24 On-time 2 warn message 1: 33.23 On-time 2 source
10: 05.04 Fan on-time counter.

ABB ACS880 A890 additional cooling Warning generated by an ontime Check the auxiliary code. Check the
timer. source of the warning corresponding to
Programmable warnings: the code:
33.14 On-time 1 warn message 0: 33.13 On-time 1 source
33.24 On-time 2 warn message 1: 33.23 On-time 2 source
10: 05.04 Fan on-time counter.

ABB ACS880 A8A0 AI supervision An analog signal is outside the Check the auxiliary code (format XYY).
Programmable warning: limits specified for the analog “X” specifies the location of the input (0:
12.03 AI supervision input. AI on control unit; 1: I/O extension
function module 1, etc.), “YY” specifies the input
and limit (01: AI1 under minimum,
02: AI1 over maximum, 03: AI2 under
minimum, 04: AI2 over maximum).
Check signal level at the analog input.
Check the wiring connected to the input.
Check the minimum and maximum limits
of the input in parameter group 12
Standard AI.

ABB ACS880 A8B0 Signal supervision Warning generated by the Check the source of the warning
(Editable message text) signal supervision 1 function. (parameter 32.07 Supervision 1 signal).
Programmable warning:
32.06 Supervision 1 action

ABB ACS880 A8B1 Signal supervision 2 Warning generated by the Check the source of the warning
(Editable message text) signal supervision 2 function. (parameter 32.17 Supervision 2 signal).
Programmable warning:
32.16 Supervision 2 action

ABB ACS880 A8B2 Signal supervision 3 Warning generated by the Check the source of the warning
(Editable message text) signal supervision 3 function. (parameter 32.27 Supervision 3 signal).
Programmable warning:
32.26 Supervision 3 action

ABB ACS880 A8C0 Fan service counter A cooling fan has reached the Check the auxiliary code. The code
end of its estimated lifetime. indicates which fan is to be replaced.
See parameters 05.41 and 0: Main cooling fan
05.42. 1: Auxiliary cooling fan
2: Auxiliary cooling fan 2
3: Cabinet cooling fan
4: PCB compartment fan
Refer to the hardware manual of the
drive for fan replacement instructions.

ABB ACS880 A981 External warning 1 Fault in external device 1 Check the external device.
(Editable message text) Check setting of parameter 31.01
Programmable warning: External event 1 source.
31.01 External event 1
source
31.02 External event 1
type
ABB ACS880 A982 External warning 2 Fault in external device 2 Check the external device.
(Editable message text) Check setting of parameter 31.03
Programmable warning: External event 2 source.
31.03 External event 2
source
31.04 External event 2
type

ABB ACS880 A983 External warning 3 Fault in external device 3 Check the external device.
(Editable message text) Check setting of parameter 31.05
Programmable warning: External event 3 source.
31.05 External event 3
source
31.06 External event 3
type

ABB ACS880 A984 External warning 4 Fault in external device 4 Check the external device.
(Editable message text) Check setting of parameter 31.07
Programmable warning: External event 4 source.
31.07 External event 4
source
31.08 External event 4
type

ABB ACS880 A985 External warning 5 Fault in external device 5 Check the external device.
(Editable message text) Check setting of parameter 31.09
Programmable warning: External event 5 source.
31.09 External event 5
source
31.10 External event 5
type

ABB ACS880 AF80 FA2FA DDCS comm DDCS (fiber optic) Check status of other converter
loss communication between (parameters 06.36 and 06.39).
Programmable warning: converters (for example, the Check settings of parameter group 60
60.79 INU-LSU comm loss inverter unit and the supply DDCS communication. Check the
function unit) is lost. corresponding settings in the control
program of the other converter.
Check cable connections. If necessary,
replace cables.

ABB ACS880 AF85 Line side unit warning The supply unit has generated If using a control panel or the Drive
a warning. composer tool, connect to the supply unit
to read the warning code. Refer to the
firmware manual of the supply unit for
instructions related to the code.

ABB ACS880 AF8C Process PID sleep mode The drive is entering sleep mode Informative warning. See section Sleep
function for process PID control (page
64), and parameters 40.41…40.48.
ABB ACS880 AF90 Speed controller autotuning the speed controller autotune routine did not complete sucessfully Check the auxiliary code (format XXXX YYYY). “YYYY” indicates the problem (see actions
for each code below).
0000 - The drive was stopped before the autotune routine finished. - Repeat autotune
untill successful
0001 - The drive was started but was not ready to follow the autotune command.
- Make sure the prerequisites of the autotune run are fulfilled. See section Before
activating the autotune routine
(page 44).
0002 - Required torque reference could not be reached before the drive reached
maximum speed. - Decrease torque step (parameter 25.38) or increase speed step
(25.39).
0003 - Motor could not accelerate/decelerate to maximum/minimum speed. - Increase
torque step (parameter 25.38) or decrease speed step (25.39).
0005 - Motor could not decelerate with full autotune torque. - Decrease torque step
(parameter 25.38) or speed step (25.39).

ABB ACS880 AFAA Autoreset A fault is about to the autoreset Informative warning. See the settings in
parameter group 31 Fault functions.
ABB ACS880 AFE1 Emergency stop (off2) Drive has received an Check that it is safe to continue
emergency stop (mode operation. Reset the source of the
selection off2) command. emergency stop signal (such as an
emergency stop push button). Restart
drive.
If the emergency stop was unintentional,
check the source of the stop signal (for
example, 21.05 Emergency stop source,
or control word received from an external
control system).

ABB ACS880 AFE2 Emergency stop (off1 Drive has received an Check that it is safe to continue
or off3) emergency stop (mode operation. Reset the source of the
selection off1 or off3) emergency stop signal (such as an
command. emergency stop push button). Restart
drive.
If the emergency stop was unintentional,
check the source of the stop signal (for
example, 21.05 Emergency stop source,
or control word received from an external
control system).
ABB ACS880 AFE7 Follower A follower drive has tripped. 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.

ABB ACS880 AFEA Enable start signal missing (Editable message text) No enable start signal Check the setting of (and the source
received. selected by) parameter 20.19 Enable
start command.
ABB ACS880 AFEB Run enable missing No run enable signal is Check setting of parameter 20.12 Run
received. enable 1 source. Switch signal on (e.g. in
the fieldbus Control Word) or check
wiring of selected source.

ABB ACS880 AFEC External power missing 95.04 Control board supply is Check the external 24 V DC power
set to External 24V but no supply to the control unit, or change the
voltage is connected to the setting of parameter 95.04.
XPOW connector of the control
unit.

ABB ACS880 AFF6 Idtenification run Motor ID run will occur at next start Informative warning
ABB ACS880 AFF7 Autophasing Autophasing will occur at next start Informative warning
ABB ACS880 B5A0 STO event Programmable event: Safe torque off function is Check safety circuit connections. For
31.22 STO indication active, i.e. safety circuit more information, see appropriate drive
run/stop signal(s) connected to hardware manual and description of
connector XSTO is lost. parameter 31.22 STO indication run/stop
(page 246).

ABB ACS880 2281 Calibration Measured offset of output Try performing the current calibration
phase current measurement or again (select Current measurement
difference between output calibration at parameter 99.13). If the
phase U2 and W2 current fault persists, contact your local ABB
measurement is too great (the representative.
values are updated during
current calibration).

ABB ACS880 2310 Overcurrent Output current has exceeded Check motor load.
internal fault limit. Check acceleration times in parameter
group 23 Speed reference ramp (speed
control), 26 Torque reference chain
(torque control) or 28 Frequency
reference chain (frequency control). Also
check parameters 46.01 Speed scaling,
46.02 Frequency scaling and 46.03
Torque scaling.
Check motor and motor cable (including
phasing and delta/star connection).
Check there are no contactors opening
and closing in motor cable.
Check that the start-up data in parameter
group 99 corresponds to the motor rating
plate.
Check that there are no power factor
correction capacitors or surge absorbers
in motor cable.
Check encoder cable (including
phasing).
Check the auxiliary code (format XXXY
YYZZ). With parallel-connected inverter
modules, “Y YY” specifies through which
BCU control unit channel the fault was
received. “ZZ” indicates the phase that
triggered the fault (0: No detailed
information available, 1: U-phase, 2: Vphase,
4: W-phase, 3/5/6/7: multiple
phases).

ABB ACS880 2330 Earth leakage Programmable fault 31.20 Earth fault Drive has detected load Check there are no power factor
unbalance typically due to correction capacitors or surge absorbers
earth fault in motor or motor in motor cable.
cable. Check for an earth fault in motor or motor
cables by measuring the insulation
resistances of motor and motor cable.
Try running the motor in scalar control
mode if allowed. (See parameter 99.04
Motor control mode.)
With parallel-connected modules, check
the auxiliary code (format XXXY YYZZ).
“Y YY” specifies through which BCU
control unit channel the fault was
received.
If no earth fault can be detected, contact
your local ABB representative.
ABB ACS880 2340 Short circuit Short-circuit in motor cable(s) Check motor and motor cable for cabling
or motor errors.
Check there are no power factor
correction capacitors or surge absorbers
in motor cable.
Check the auxiliary code (format XXXY
YYZZ). With parallel-connected inverter
modules, “Y YY” specifies through which
BCU control unit channel the fault was
received. “ZZ” indicates the location of
the short circuit (0: No detailed
information available, 1: Upper branch of
U-phase, 2: Lower branch of U-phase, 4:
Upper branch of V-phase, 8: Lower
branch of V-phase, 10: Upper branch of
W-phase, 20: Lower branch of W-phase,
other: combinations of the above).
After correcting the cause of the fault,
reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power.

ABB ACS880 2381 IGBT overload Excessive IGBT junction to Check motor cable.
case temperature. This fault Check ambient conditions.
protects the IGBT(s) and can Check air flow and fan operation.
be activated by a short circuit Check heatsink fins for dust pick-up.
in the motor cable. Check motor power against drive power.

ABB ACS880 2391 BU current difference AC phase current difference Check motor cabling.
between parallel-connected Check there are no power factor
inverter modules is excessive. correction capacitors or surge absorbers
in motor cable.
Check the auxiliary code (format XXXY
YYZZ). “XXX” specifies the source of the
first error (see “YYY”). “YYY” specifies
the module through which BCU control
unit channel the fault was received (0:
Channel 1, 1: Channel 2, 2: Channel 3,
4: Channel 4, 8: Channel 5, …, 400:
Channel 12, other: combinations of the
above). “ZZ” indicates the phase (1: U, 2:
V, 3: W).

ABB ACS880 2392 BU earth leakage Total earth leakage of inverter Check there are no power factor
modules is excessive. correction capacitors or surge absorbers
in motor cable.
Measure insulation resistances of motor
cables and motor.
Contact your local ABB representative.

ABB ACS880 3130 Input phase loss Intermediate circuit DC voltage Check input power line fuses.
Programmable fault: 31.21 is oscillating due to missing Check for loose power cable
Supply phase loss input power line phase or connections.
blown fuse. Check for input power supply imbalance.

ABB ACS880 3180 Charge relay lost No acknowledgement received Contact your local ABB representative
from charge relay.
ABB ACS880 3181 Wiring or earth fault The drive hardware is supplied Switch off the protection in parameter
Programmable fault: 31.23 from a common DC bus. 31.23.
Wiring or earth fault
ABB ACS880 3181 Wiring or earth fault Incorrect input power and Check the power connections.
Programmable fault: 31.23 motor cable connection (i.e.
Wiring or earth fault input power cable is connected
to the motor connection).

ABB ACS880 3181 Wiring or earth fault Drive has detected load Check there are no power factor
Programmable fault: 31.23 unbalance typically due to correction capacitors or surge absorbers
Wiring or earth fault earth fault in motor or motor in motor cable.
cable. Check for an earth fault in motor or motor
cables by measuring the insulation
resistances of motor and motor cable.
Try running the motor in scalar control
mode if allowed. (See parameter 99.04
Motor control mode.)
ABB ACS880 3210 DC link overvoltage Excessive intermediate circuit Check that overvoltage control is on
DC voltage. (parameter 30.30 Overvoltage control).
Check that the supply voltage matches
the nominal input voltage of the drive.
Check the supply line for static or
transient overvoltage.
Check brake chopper and resistor (if
present).
Check deceleration time.
Use coast-to-stop function (if applicable).
Retrofit drive with brake chopper and
brake resistor.
With parallel-connected modules, check
the auxiliary code (format XXXY YYZZ).
“Y YY” specifies through which BCU
control unit channel the fault was
received.

ABB ACS880 3220 DC link undervoltage Intermediate circuit DC voltage Check supply cabling, fuses and
is not sufficient because of a switchgear.
missing supply phase, blown With parallel-connected modules, check
fuse or fault in the rectifier the auxiliary code (format XXXY YYZZ).
bridge. “Y YY” specifies through which BCU
control unit channel the fault was
received.

ABB ACS880 3280 Standby timeout Automatic restart failed (see Check the condition of the supply
section Automatic restart on (voltage, cabling, fuses, switchgear).
page 73).
ABB ACS880 3291 BU DC link difference Difference in DC voltages Check the auxiliary code (format XXXY
between parallel-connected YYZZ). “XXX” specifies the source of the
inverter modules. first error (see “YYY”). “YYY” specifies
the module through which BCU control
unit channel the fault was received (0:
Channel 1, 1: Channel 2, 2: Channel 3,
4: Channel 4, 8: Channel 5, …, 400:
Channel 12).

ABB ACS880 3381 Output phase loss Motor circuit fault due to Connect motor cable.
missing motor connection (all
three phases are not
connected).

ABB ACS880 3385 Autophasing Autophasing routine (see Try other autophasing modes (see
section Autophasing on page parameter 21.13 Autophasing mode) if
57) has failed. possible.
If the Turning with Z-pulse mode is
selected, check the zero pulse given by
the encoder.
Check that the motor ID run has been
successfully completed.
Clear parameter 98.15 Position offset
user.
Check that the encoder is not slipping on
the motor shaft.
Check that the motor is not already
turning when the autophasing routine
starts.
Check the setting of parameter 99.03
Motor type.

ABB ACS880 4000 Motor cable overload Calculated motor cable Check the settings of parameters 35.61
temperature has exceeded and 35.62.
warning limit. Check the dimensioning of the motor
cable in regard to required load.

ABB ACS880 4210 IGBT overtemperature Estimated drive IGBT Check ambient conditions.
temperature is excessive. Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against drive power.

ABB ACS880 4290 Cooling Drive module temperature is Check ambient temperature. If it exceeds
excessive. 40 °C (104 °F), ensure that load current
does not exceed derated load capacity of
drive. See appropriate Hardware manual.
Check drive module cooling air flow and
fan operation.
Check inside of cabinet and heatsink of
drive module for dust pick-up. Clean
whenever necessary.

ABB ACS880 42F1 IGBT temperature Drive IGBT temperature is Check ambient conditions.
excessive. Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against drive power.

ABB ACS880 4310 excess temperature Power unit module See A4B0 Excess temperature (page
temperature is excessive. 441).
ABB ACS880 4380 Excess temperature difference High temperature difference See A4B1 Excess temperature
between the IGBTs of different difference (page 441).
phases.
ABB ACS880 4381 PCB space cooling Temperature difference See A4B2 PCB space cooling (page
between ambient and drive 441).
module PCB space is
excessive.

ABB ACS880 4981 External temperature Measured temperature 1 has Check the value of parameter 35.02
1 exceeded fault limit. Measured temperature 1.
(Editable message text) Check the cooling of the motor (or other
equipment whose temperature is being
measured).
Check the value of parameter 35.12
Temperature 1 fault limit.

ABB ACS880 5080 Fan cooling fan stuck or disconnected see A581 Fan (page 4422)
ABB ACS880 5081 Auxiliary fan broken An auxiliary cooling fan Check auxiliary fan(s) and connection(s).
(connected to the fan Replace faulty fan.
connectors on the control unit) Make sure the front cover of the drive
is stuck or disconnected. module is in place and tightened. If the
commissioning of the drive requires that
the cover is off, activate parameter 31.36
Aux fan fault bypass within 2 minutes
from control unit reboot to temporarily
suppress the fault.
The auxiliary code identifies the fan (1:
Main fan 1, 2: Main fan 2, 3: Main fan 3,
4: Auxiliary fan 1, 5: Auxiliary fan 2, 6:
Auxiliary fan 3, 7: Filter fan 1, 8: Filter fan
2, 9: Filter fan 3).

ABB ACS880 5090 STO hardware failure Safe torque off hardware Contact your local ABB representative,
failure. quoting the auxiliary code. The code
contains location information, especially
with parallel-connected inverter modules.
When converted into a 32-bit binary
number, the bits of the code indicate the
following:
31…28: Number of faulty inverter module
(0…11 decimal). 1111: STO_ACT states
of control unit and inverter modules in
conflict
27: STO_ACT state of inverter modules
26: STO_ACT state of control unit
25: STO1 of control unit
24: STO2 of control unit
23…12: STO1 of inverter modules 12…1
(Bits of non-existing modules set to 1)
11…0: STO2 of inverter modules 12…1
(Bits of non-existing modules set to 1)

ABB ACS880 5091 Safe torque off Safe torque off function is Check safe torque off circuit connections.
Programmable fault: 31.22 active, i.e. safety circuit For more information, see appropriate
STO indication run/stop signal(s) connected to drive hardware manual and description of
connector XSTO is broken parameter 31.22 STO indication run/stop
during start or run. (page 246).

ABB ACS880 5092 PU logic error Power unit memory has Cycle the power to the drive. If the
cleared. control unit is externally powered, also
reboot the control unit (using parameter
96.08 Control board boot) or by cycling
its power. If the problem persists, contact
your local ABB representative.

ABB ACS880 5093 Rating ID mismatch The hardware of the drive does Cycle the power to the drive.
not match the information Check the auxiliary code. The auxiliary
stored in the memory unit. This code categories are as follows:
may occur eg. after a firmware 1 = PU and CU ratings not the same.
update or memory unit Rating ID has changed.
replacement. 2 = Parallel connection rating ID has
changed.
3 = PU types not the same in all power
units.
4 = Parallel connection rating ID is active
in a single power unit setup.
5 = It is not possible to implement the
selected rating with the current PUs.
6 = PU rating ID is 0.
7 = Reading PU rating ID or PU type
failed on PU connection.
With parallel connection faults, the format
of the auxiliary code is 0X0Y. “Y”
indicates the auxiliary code category, “X”
indicates the first faulty PU channel in
hexadecimal (1…C).

ABB ACS880 5094 Measurment cirucit temperature Problem with internal See A5EA Measurement circuit
temperature measurement of temperature (page 442).
the drive.
ABB ACS880 5681 PU communication The way the control unit is Check setting of 95.04 Control board
powered does not correspond supply.
to parameter setting.
ABB ACS880 5681 PU communication Communication errors Check the connection between the
detected between the drive control unit and the power unit.
control unit and the power unit. Check the auxiliary code (format XXXY
YYZZ). “XXX” specifies the transmitter
FIFO error code. With parallel-connected
modules, “Y YY” specifies the affected
BCU control unit channel (0: broadcast).
“ZZ” specifies the error source
(1: Transmitter side [link error], 2:
Transmitter side [no communication], 3:
Receiver side [link error], 4: Receiver
side [no communication], 5: Transmitter
FIFO error XXX, 6: Module [xINT board]
not found, 7: BAMU board not found).

ABB ACS880 5682 Power unit lost Connection between the drive Check the connection between the
control unit and the power unit control unit and the power unit.
is lost.
ABB ACS880 5690 PU communication internal Internal communication error. Contact your local ABB representative.
ABB ACS880 5691 Measuremnt cirucit ADC Measurement circuit fault. Contact your local ABB representative,
quoting the auxiliary code.
ABB ACS880 5692 PU board powerfail Power unit power supply Check the auxiliary code (format
failure. ZZZY YYXX). “YY Y” specifies the
affected inverter module (0…C, always 0
for ZCU control units). “XX” specifies the
affected power supply (1: Power supply
1, 2: Power supply 2).

ABB ACS880 5693 measurment circuit DFF Measurement circuit fault. Contact your local ABB representative,
quoting the auxiliary code.
ABB ACS880 5694 PU communication configuration Version check cannot find a Contact your local ABB representative,
matching power unit FPGA
logic.
ABB ACS880 5695 Reduced run Number of inverter modules Check that the value of 95.13 Reduced
detected does not match the run mode corresponds to the number of
value of parameter 95.13 inverter modules present. Check that the
Reduced run mode. modules present are powered from the
DC bus and connected by fiber optic
cables to the BCU control unit.
If all modules of the inverter unit are in
fact available (eg. maintenance work has
been completed), check that parameter
95.13 is set to 0 (reduced run function
disabled).

ABB ACS880 5696 Pu state feedback State feedback from output Contact your local ABB representative,
phases does not match control quoting the auxiliary code.
signals.
ABB ACS880 5697 Charging Feedback Charging feedback signal Check the feedback signal coming from
missing. the charging system.
ABB ACS880 5698 Unknown power unit fault Unidentified power unit logic Check power unit logic and firmware
fault. compatibility.
Contact your local ABB representative.
ABB ACS880 6000 Internal SW error Internal error. Contact your local ABB representative,
quoting the auxiliary code.
ABB ACS880 6181 FPGA version Firmware and FPGA file Reboot the control unit (using parameter
incompatible version in the power unit are 96.08 Control board boot) or by cycling
incompatible. power. If the problem persists, contact
your local ABB representative.

ABB ACS880 6306 FBA A Mapping file Fieldbus adapter A mapping Contact your local ABB representative.
file read error.
ABB ACS880 6307 FBA B mapping file Fieldbus adapter B mapping Contact your local ABB representative.
file read error.
ABB ACS880 6481 Task overload Internal fault Reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power. If the problem persists, contact
your local ABB representative.

ABB ACS880 6487 Stack overflow Internal fault Reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power. If the problem persists, contact
your local ABB representative.

ABB ACS880 64A1 internal file load file read error Reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power. If the problem persists, contact
your local ABB representative.

ABB ACS880 64A2 internal record load internal record load error Contact your local ABB representative.
ABB ACS880 64A3 application loading Application file incompatible or Check the auxiliary code. See actions for
corrupted. each code below.
8006 - Not enough memory for the application
8007 - The application contains the wrong library version
800A - The application contains an unknown target (System) library function.

ABB ACS880 64A5 Licensing fault A license that is required for Record the auxiliary codes of all active
the drive to function properly is licensing faults and contact your product
missing. vendor for further instructions.
ABB ACS880 64B0 Memory unit detached The memory unit was Switch off the power to the control unit
detached when the control unit and reinstall the memory unit.
was powered. In case the memory unit was not actually
removed when the fault occurred, check
that the memory unit is properly inserted
into its connector and its mounting screw
is tight. Reboot the control unit (using
parameter 96.08 Control board boot) or
by cycling power. If the problem persists,
contact your local ABB representative.

ABB ACS880 64B1 Internal SSW fault Internal fault Reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power. If the problem persists, contact
your local ABB representative.

ABB ACS880 64B2 User set fault Loading of user parameter set Ensure that a valid user parameter set
failed because exists. Reload if uncertain.
• requested set does not exist
• set is not compatible with
control program
• drive was switched off
during loading.

ABB ACS880 64E1 Kernal overload Operating system error. Reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power. If the problem persists, contact
your local ABB representative.

ABB ACS880 6581 Parameter system Parameter load or save failed. Try forcing a save using parameter 96.07
Parameter save manually. Retry.
ABB ACS880 65A1 FBA A parameter conflict The drive does not have a Check PLC programming.
functionality requested by Check settings of parameter groups 50
PLC, or requested functionality Fieldbus adapter (FBA) and 51 FBA A
has not been activated. settings.

ABB ACS880 65A2 FBA B parameter conflict The drive does not have a Check PLC programming.
functionality requested by Check settings of parameter groups 50
PLC, or requested functionality Fieldbus adapter (FBA) and 54 FBA B
has not been activated. settings.

ABB ACS880 6681 EFB comm loss Communication break in Check the status of the fieldbus master
Programmable fault: embedded fieldbus (EFB) (online/offline/error etc.).
58.14 Communication loss communication. Check cable connections to the XD2D
action connector on the control unit.

ABB ACS880 6682 EFB config file Embedded fieldbus (EFB) Contact your local ABB representative.
configuration file could not be
read.
ABB ACS880 6683 EFB invalid Embedded fieldbus (EFB) Check the settings in parameter group 58
parameterization parameter settings Embedded fieldbus.
inconsistent or not compatible
with selected protocol.

ABB ACS880 6684 EFB load fault Embedded fieldbus (EFB) Contact your local ABB representative.
protocol firmware could not be
loaded.
ABB ACS880 6684 EFB load fault Version mismatch between Contact your local ABB representative.
EFB protocol firmware and
drive firmware.
ABB ACS880 6881 Text data overflow Internal fault Reset the fault. Contact your local ABB
representative if the fault persists.
ABB ACS880 6882 Text 32-bit table overflow Internal fault Reset the fault. Contact your local ABB
representative if the fault persists.
ABB ACS880 6883 Text 64-bit table overload Internal fault Reset the fault. Contact your local ABB
representative if the fault persists.
ABB ACS880 6885 Text file overflow Internal fault Reset the fault. Contact your local ABB
representative if the fault persists.
ABB ACS880 7080 Option module comm loss Communication between drive Check that all option modules are
and an option module is lost. properly seated in their slots.
Check that all option modules or slot
connectors are not damaged. To pinpoint
the problem, try installing the modules
into different slots one at a time.

ABB ACS880 7081 Panel port Control panel or PC tool Check PC tool or control panel
communication selected as active control connection.
Programmable fault: 49.05 location for drive has ceased Check control panel connector.
Communication loss communicating. Disconnect and reconnect the control
action panel.
Check the auxiliary code. The code
specifies the I/O port used as follows: 0:
Panel, 1: Fieldbus interface A, 2:
Fieldbus interface B, 3: Ethernet, 4:
D2D/EFB port).
ABB ACS880 7082 Ext I/O comm loss The I/O extension module Check the auxiliary code (format XXYY YYYY). “XX” specifies the number of the I/O
types specified by parameters extension module (01: parameter group 14 I/O extension module 1, 02: 15 I/O extension
do not match the detected module 2, 03: 16 I/O extension module 3). “YY YYYY” indicates the problem (see actions
configuration. for each code below).
00 0001 - Communcation with module failed - Check that the module is properly seated
in its slot.
Check that the module and the slotconnector is not damaged.
Try installing the module into another slot.
00 0002 - Module not found. - Check the type and location settings of the modules
(parameters 14.01/14.02, 15.01/15.02 or 16.01/16.02).
Check that the module is properly seated in its slot.
Check that the module and the slot connector is not damaged.
Try installing the module into another slot.
00 0003 - 00 0004 - Configuration of module failed. - Check the type and location
settings of the modules (parameters 14.01/14.02, 15.01/15.02 or 16.01/16.02).
Check that the module is properly seated in its slot.
Check that the module and the slot connector is not damaged.
Try installing the module into another slot.

ABB ACS880 7121 Motor stall Motor is operating in stall Check motor load and drive ratings.
Programmable fault: 31.24 region because of e.g. Check fault function parameters.
Stall function excessive load or insufficient
motor power.

ABB ACS880 7181 Brake resistor Brake resistor broken or not Check that a brake resistor has been
connected. connected.
Check the condition of the brake resistor.
Check the dimensioning of the brake
resistor.

ABB ACS880 7183 BR excess temperature Brake resistor temperature has Stop drive. Let resistor cool down.
exceeded fault limit defined by Check resistor overload protection
parameter 43.11 Brake resistor function settings (parameter group 43
fault limit. Brake chopper).
Check fault limit setting, parameter 43.11
Brake resistor fault limit.
Check that braking cycle meets allowed
limits.

ABB ACS880 7184 Brake resistor wiring Brake resistor short circuit or Check brake chopper and brake resistor
brake chopper control fault. connection.
Ensure brake resistor is not damaged.
After correcting the cause of the fault,
reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power.

ABB ACS880 7191 BC short circuit Short circuit in brake chopper Ensure brake resistor is connected and
IGBT. not damaged.
Check the electrical specifications of the
brake resistor against the Hardware
manual.
Replace brake chopper (if replaceable).
After correcting the cause of the fault,
reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power.

ABB ACS880 7192 BC IGBT excess Brake chopper IGBT Let chopper cool down.
temperature temperature has exceeded Check for excessive ambient temperature.
internal fault limit. Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of the cabinet.
Check resistor overload protection function settings (parameter group 43 Brake
chopper).
Check that braking cycle meets allowed limits.
Check that drive supply AC voltage is not excessive.

ABB ACS880 71A2 Mechanical brake Mechanical brake control fault. Check mechanical brake connection.
closing failed Activated eg. if brake Check mechanical brake settings in
Programmable fault: 44.17 acknowledgement is not as parameter group 44 Mechanical brake
Brake fault function expected during brake closing. control.
Check that acknowledgement signal
matches actual status of brake.

ABB ACS880 71A3 Mechanical brake Mechanical brake control fault. Check mechanical brake connection.
opening failed Activated eg. if brake Check mechanical brake settings in
Programmable fault: 44.17 acknowledgement is not as parameter group 44 Mechanical brake
Brake fault function expected during brake control.
opening. Check that acknowledgement signal
matches actual status of brake.

ABB ACS880 71A5 Mechanical brake Open conditions of mechanical Check mechanical brake settings in
opening not allowed brake cannot be fulfilled (for parameter group 44 Mechanical brake
Programmable fault: 44.17 example, brake has been control (especially 44.11 Keep brake
Brake fault function prevented from opening by closed).
parameter 44.11 Keep brake Check that acknowledgement signal (if
closed). used) matches actual status of brake.
ABB ACS880 71A5 Mechanical brake In an encoderless application, Check the source signal selected by
opening not allowed the brake is kept closed by a parameter 44.12 Brake close request.
Programmable fault: 44.17 brake close request (either Check the safety circuits connected to
Brake fault function from parameter 44.12 Brake the FSO-xx safety functions module.
close request or from an
FSO-xx safety functions
module) against a modulating
drive for longer than 5
seconds.

ABB ACS880 71B1 Motor fan No feedback received from Check external fan (or other equipment
Programmable fault: external fan. controlled) by the logic.
35.106 DOL starter event Check settings of parameters
type 35.100…35.106.

ABB ACS880 7301 Motor speed feedback No motor speed feedback See A7B0 Motor speed feedback (page
Programmable fault: 90.45 received. 447).
Motor feedback fault
ABB ACS880 7310 overspeed Motor is turning faster than Check minimum/maximum speed
highest allowed speed due to settings, parameters 30.11 Minimum
incorrectly set speed and 30.12 Maximum speed.
minimum/maximum speed, Check adequacy of motor braking torque.
insufficient braking torque or Check applicability of torque control.
changes in load when using Check need for brake chopper and
torque reference. resistor(s).

ABB ACS880 7310 overspeed Incorrect estimated speed. Check the status of motor current
measurement.
Perform a Normal, Advanced or
Advanced Standstill ID run instead of, for
example, a Reduced or Standstill ID run.
See parameter 99.13 ID run requested
(page 379).

ABB ACS880 7358 Line side converter The supply unit has tripped on If using a control panel or the Drive
faulted a fault. composer tool, connect to the supply unit
to read the fault code. Refer to the
firmware manual of the supply unit for
instructions related to the code.

ABB ACS880 7380 Encoder internal Internal fault. Contact your local ABB representative
ABB ACS880 7381 Encoder Encoder feedback fault. See A7E1 Encoder (page 448).
Programmable fault: 90.45
Motor feedback fault
ABB ACS880 73A0 Speed feedback Speed feedback configuration See A797 Speed feedback configuration
configuration incorrect. (page 445).
ABB ACS880 73A1 Load feedback No load feedback received. Check the auxiliary code (format XXYY ZZZZ). “XX” specifies the number of the
Programmable fault: 90.55 encoder interface module (01: 91.11/91.12, 02: 91.13/91.14), “YY” specifies the
Load feedback fault encoder (01: 92 Encoder 1 configuration, 02: 93 Encoder 2 configuration). “ZZZZ”
indicates the problem (see actions for each code below).
0001 - Load gear definition invalid or outside limits. - Check load gear settings
(90.53 and 90.54).
0002 - Feed constant definition invalid or outside limits.Check feed constant
settings (90.63 and 90.64).
0003 - Motor/load gear definition invalid or outside limits. - Check motor/load gear
settings (90.61 and 90.62).
0004 - Encoder not configured. - Check encoder settings (92 Encoder 1
configuration or 93 Encoder 2 configuration). Use parameter 91.10 Encoder
parameter refresh) to validate any changes in the settings.
0005 - Encoder stopped working - Check encoder status

ABB ACS880 73B0 Emergency ramp Emergency stop did not finish Check the settings of parameters 31.32
failed within expected time. Emergency ramp supervision and 31.33
Emergency ramp supervision delay.
Check the predefined ramp times
(23.11…23.19 for mode Off1, 23.23 for
mode Off3).

ABB ACS880 75B1 stop failed Ramp stop did not finish within Check the settings of parameters 31.37
expected time. Ramp stop supervision and 31.38 Ramp
stop supervision delay.
Check the predefined ramp times in
parameter group 23 Speed reference
ramp.

ABB ACS880 7510 FBA A communication Cyclical communication Check status of fieldbus communication.
Programmable fault: 50.02 between drive and fieldbus See user documentation of fieldbus
FBA A comm loss func adapter module A or between interface.
PLC and fieldbus adapter Check settings of parameter groups 50
module A is lost. Fieldbus adapter (FBA), 51 FBA A
settings, 52 FBA A data in and 53 FBA A
data out.
Check cable connections.
Check if communication master is able to
communicate.
ABB ACS880 7520 FBA B communication Cyclical communication Check status of fieldbus communication.
Programmable fault: 50.32 between drive and fieldbus See user documentation of fieldbus
FBA B comm loss func adapter module B or between interface.
PLC and fieldbus adapter Check settings of parameter group 50
module B is lost. Fieldbus adapter (FBA).
Check cable connections.
Check if communication master is able to
communicate.

ABB ACS880 7580 FA2FA DDCS comm DDCS (fiber optic) Check status of other converter
loss communication between (parameters 06.36 and 06.39).
Programmable fault: 60.79 converters (for example, the Check settings of parameter group 60
INU-LSU comm loss inverter unit and the supply DDCS communication. Check the
function unit) is lost. corresponding settings in the control
program of the other converter.
Check cable connections. If necessary,
replace cables.

ABB ACS880 7581 DDCS controller DDCS (fiber optic) Check status of controller. See user
comm loss communication between drive documentation of controller.
Programmable fault: 60.59 and external controller is lost. Check settings of parameter group 60
DDCS controller comm DDCS communication.
loss function Check cable connections. If necessary,
replace cables.

ABB ACS880 7582 MF comm loss Master/follower See A7CB MF comm loss (page 448).
Programmable fault: 60.09 communication is lost.
M/F comm loss function
ABB ACS880 7583 Line side unit faulted The supply unit (or other Check fault status of supply unit (or other
converter) connected to the converter).
inverter unit has generated a Refer to the firmware manual of the
fault. supply unit.

ABB ACS880 80A0 AI supervision An analog signal is outside the Check the auxiliary code (format XXXX
Programmable fault: limits specified for the analog XYZZ). “Y” specifies the location of the
12.03 AI supervision input. input (0: Control unit, 1: I/O extension
function module 1, 2: I/O extension module 2, 3:
I/O extension module 3). “ZZ” specifies
the limit (01: AI1 under minimum, 02: AI1
above maximum, 03: AI2 under
minimum, 04: AI2 above maximum).
Check signal level at the analog input.
Check the wiring connected to the input.
Check the minimum and maximum limits
of the input in parameter group 12
Standard AI.

ABB ACS880 80B0 Signal supervision Fault generated by the signal Check the source of the fault (parameter
(Editable message text) supervision 1 function. 32.07 Supervision 1 signal).
Programmable fault:
32.06 Supervision 1 action

ABB ACS880 80B1 Signal supervision 2 Fault generated by the signal Check the source of the fault (parameter
(Editable message text) supervision 2 function. 32.17 Supervision 2 signal).
Programmable fault:
32.16 Supervision 2 action

ABB ACS880 80B2 Signal supervision 3 Fault generated by the signal Check the source of the fault (parameter
(Editable message text) supervision 3 function. 32.27 Supervision 3 signal).
Programmable fault:
32.26 Supervision 3 action

ABB ACS880 9081 External fault 1 Fault in external device 1 Check the external device.
(Editable message text) Check setting of parameter 31.01
Programmable fault: 31.01 External event 1 source.
External event 1 source
31.02 External event 1
type

ABB ACS880 9082 External fault 2 Fault in external device 2 Check the external device.
(Editable message text) Check setting of parameter 31.03
Programmable fault: 31.03 External event 2 source.
External event 2 source
31.04 External event 2
type

ABB ACS880 9083 External fault 3 Fault in external device 3 Check the external device.
(Editable message text) Check setting of parameter 31.05
Programmable fault: 31.05 External event 3 source.
External event 3 source
31.06 External event 3
type

ABB ACS880 9084 External fault 4 Fault in external device 4 Check the external device.
(Editable message text) Check setting of parameter 31.07
Programmable fault: 31.07 External event 4 source.
External event 4 source
31.08 External event 4
type
ABB ACS880 9085 External fault 5 Fault in external device 5 Check the external device.
(Editable message text) Check setting of parameter 31.09
Programmable fault: 31.09 External event 5 source.
External event 5 source
31.10 External event 5
type

ABB ACS880 FA81 Safe torque off 1 Safe torque off function is Check safety circuit connections. For more information, see appropriate drive hardware
active, ie. STO circuit 1 is manual and description of parameter 31.22 STO indication run/stop (page 246). Check
broken. the auxiliary code, The code contains location information, especially with parallel-
connected inverter modules. When converted into a 32-bit binary number, the bits of
the code indicate the following: 31…28: Number of faulty inverter module (0…11
decimal). 1111: STO_ACT states of control unit and inverter modules in conflict
27: STO_ACT state of inverter modules
26: STO_ACT state of control unit
25: STO1 of control unit
24: STO2 of control unit
23…12: STO1 of inverter modules 12…1 (Bits of non-existing modules set to 1)
11…0: STO2 of inverter modules 12…1 (Bits of non-existing modules set to 1)

ABB ACS880 FA82 Safe torque off 2 Safe torque off function is Check safety circuit connections. For more information, see appropriate drive hardware
active, ie. STO circuit 2 is manual and description of parameter 31.22 STO indication run/stop (page 246). Check
broken. the auxiliary code, The code contains location information, especially with parallel-
connected inverter modules. When converted into a 32-bit binary number, the bits of
the code indicate the following: 31…28: Number of faulty inverter module (0…11
decimal). 1111: STO_ACT states of control unit and inverter modules in conflict
27: STO_ACT state of inverter modules
26: STO_ACT state of control unit
25: STO1 of control unit
24: STO2 of control unit
23…12: STO1 of inverter modules 12…1 (Bits of non-existing modules set to 1)
11…0: STO2 of inverter modules 12…1 (Bits of non-existing modules set to 1)

ABB ACS880 FB11 Memory unit missing No memory unit is attached to Power down the control unit.
the control unit. Check that the memory unit is properly inserted into the control unit.
ABB ACS880 FB11 Memory unit missing The memory unit attached to Power down the control unit. Attach a memory unit (with the appropriate firmware) to
the control unit is empty. the control unit.
ABB ACS880 FF61 ID RUN Motor ID run was not Check the nominal motor values in parameter group 99 Motor data.
completed successfully. Check that no external control system is connected to the drive. Cycle the power to the
drive (and its control unit, if powered separately). Check that the motor shaft is not
locked.
Check the auxiliary code. The second number of the code indicates the problem (see
actions for each code below).
0001 - Maximum current limit too low. - Check settings of parameters 99.06
Motor nominal current and 30.17 Maximum current. Make sure that 30.17 > 99.06.
Check that the drive is dimensioned correctly according to the motor.
0002 - Maximum speed limit or calculated field weakening point too low. - Check
settings of parameters
• 30.11 Minimum speed
• 30.12 Maximum speed
• 99.07 Motor nominal voltage
• 99.08 Motor nominal frequency
• 99.09 Motor nominal speed.
Make sure that
• 30.12 > (0.55 × 99.09) > (0.50 × synchronous speed)
• 30.11 < 0, and
• supply voltage > (0.66 × 99.07).
0003 - Maximum torque limit too low. - Check settings of parameter 99.12 Motor
nominal torque, and the torque limits in group 30 Limits. Make sure that the maximum
torque limit in force is greater than 100%.
0004 - Current measurement calibration did not finish within reasonable time.
0005....0008 - Internal Erro
0009 - (Asynchronous motors only) Acceleration did not finish within reasonable time.
000A - (Asynchronous motors only) Deceleration did not finish within reasonable time.
000B - Asynchronous motors only) Speed dropped to zero during ID run.
000C - (Permanent magnet motors only) First acceleration did not finish within
reasonable time.
000D - (Permanent magnet motors only) Second acceleration did not finish within
reasonable time.
000E....0010 - Internal Error
For auxiliary codes 0004 - 0010 Contact your local ABB representative.

ABB ACS880 FF7E Follower A follower drive has tripped. 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.

ABB ACS880 FF81 FB A force trip A fault trip command has been Check the fault information provided by
received through fieldbus the PLC.
adapter A.
ABB ACS880 FF82 FB B force trip A fault trip command has been Check the fault information provided by
received through fieldbus the PLC.
adapter B.
ABB ACS880 FF8E FB C force trp A fault trip command has been Check the fault information provided by
received through the the Modbus controller.
embedded fieldbus interface.
CT UV CT / Emerson Commander DC bus under voltage Low AC supply voltage
SK Low DC bus voltage when supplied by an external DC power
supply
CT OV CT / Emerson Commander DC bus over voltage Deceleration rate set too fast for the inertia of the machine.
SK Mechanical load driving the motor
CT OI.AC** CT / Emerson Commander Drive output instantaneous over Insufficient ramp times ** These trips cannot be reset for 10 seconds after they occur.
SK current Phase to phase or phase to ground short circuit on the drives
output
Drive requires autotuning to the motor
Motor or motor connections changed, re-autotune drive to motor

CT OI.br** CT / Emerson Commander Braking resistor instantaneous Excessive braking current in braking resistor ** These trips cannot be reset for 10 seconds after they occur.
SK over current Braking resistor value too small
CT O.SPd CT / Emerson Commander Over speed Excessive motor speed (typically caused by mechanical load
SK driving the motor)
CT tunE CT / Emerson Commander Autotune stopped before Run command removed before autotune complete
SK completion
CT It.br CT / Emerson Commander I2t on braking resistor Excessive braking resistor energy
SK
CT It.AC CT / Emerson Commander AC I2t on drive output current Excessive mechanical load
SK High impedance phase to phase or phase to ground short circuit
at drive output
Drive requires re-autotuning to motor

CT O.ht1 CT / Emerson Commander IGBT over heat based on drives Overheat software thermal model
SK thermal model
CT O.ht2 CT / Emerson Commander Over heat based on drives Heatsink temperature exceeds allowable maximum
SK heatsink
CT th CT / Emerson Commander Motor thermistor trip Excessive motor temperature
SK
CT O.Ld1* CT / Emerson Commander User +24V or digital output Excessive load or short circuit on +24V output * The Enable/Reset terminal will not reset an O.Ld1 trip. Use the Stop/Reset key.
SK overload
CT O.ht3 CT / Emerson Commander Drive over-heat based on drives Overheat software thermal model
SK thermal model
CT O.ht4 CT / Emerson Commander Power module rectifier over Power module rectifier temperature exceeds allowable
SK temperature. maximum
CT cL1 CT / Emerson Commander Analog input 1 current mode, Input current less than 3mA when 4-20 or 20-4mA modes
SK current loss selected
CT SCL CT / Emerson Commander Serial communications loss timeout Loss of communication when drive is under remote control
SK
CT EEF CT / Emerson Commander Internal drive EEPROM trip Possible loss of parameter values
SK (set default parameters (see Pr 29 on page 59))
CT PH CT / Emerson Commander Input phase imbalance or input One of the input phases has become disconnected from the
SK phase loss drive (not dual rated drives)
CT rS CT / Emerson Commander Failure to measure motors stator Motor too small for drive
SK resistance Motor cable disconnected during measurement
CT C.Err CT / Emerson Commander SmartStick data error Bad connection or memory corrupt within SmartStick
SK
CT C.dAt CT / Emerson Commander SmartStick data does not exist New/empty SmartStick being read
SK
CT C.Acc CT / Emerson Commander SmartStick read/write fail Bad connection or faulty SmartStick
SK
CT C.rtg CT / Emerson Commander SmartStick/drive rating change Already programmed SmartStick read by a drive of a different
SK rating
CT O.cL CT / Emerson Commander Overload on current loop input Input current exceeds 25mA
SK
CT HFxx trip CT / Emerson Commander Hardware faults Internal drive hardware fault (see Commander SK Advanced
SK User Guide)
CT Parity Errors CT / Emerson Parity Errors - communications Possibly due to EMC interference, communication cable faulty, faulty control Replaced cable, Replace controller of the CT
board.
MK III "Blank Screen" All Mk III Elektronikons No power to display of Elektronikon Faulty Board, loose connections (ribbon cables) inside. Check the module for loose connection.

If no loose connection is found, chances are the diode that controls the power supply to
the display is gone. It is not recommended to repair them, because whilst repairing,
there is a chance of disturbing neighbour

MK III 10 Elektronikon Mk III LRR V1.8, Relay outputs read-back error Relay damaged, internal error - Power down the regulator.
2.3 - Inconsistency between the status of the relays and Unrecoverable failures generated by the regulator. - Check the Emergency stop button.
HRR the status the relays should be in - Compressor is running or standing still. Regulator is powered up. Only one * Make sure all wires connected firmly and no bad contacts are existing.
contact (out of three) of the Emergency stop button is activated. This means that * All the components of the Emergency stop button (base and contacts) should have
the power suppl the same colour (black or brow

MK III 100 Elektronikon Mk III LRR V1.8, Register file error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III if all else fails
2.3
MK III 101 Elektronikon Mk III LRR V1.8, RAM error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III if all else fails
2.3
MK III 102 Elektronikon Mk III LRR V1.8, 12V relay not disabled at power on Relay possibly damaged due to incorrect power input Replace Elektronikon Mk III if all else fails
2.3
MK III 103 Elektronikon Mk III LRR V1.8, Relays status uncorrect at power on Relay possibly damaged due to incorrect power input Replace Elektronion, if all else fails
2.3 Unrecoverable failures generated by the regulator.
MK III 104 Elektronikon Mk III LRR V1.8, Short circuit on 12V (relays and digital inputs) OR In Most cases, attributed to a voltage coming in through one of the digital inputs. These failures are used to signal some dangerous situation caused by hardware or
2.3, HRR 12V enabling FET damaged But digital inputs are voltage free contacts. software problems.

Chances are FET, and or diodes had gone. Possible what happen here is when the Check 2x1 connector. Possibly, the FET, inductor (the green resistor lookalike), or diode
connector is put upside down, and when 24V is gone here, due to reverse biased of power.

Also, check othe

MK III 106 Elektronikon Mk III LRR V1.8, Relays enable at power on Relay possible damaged due to incorrect power input - Power down the regulator.
2.3 - Inconsistency between the status of the relays and - Elektronikon is not powered up. Only one contact (out of three) of the Emergency - Check the Emergency stop button.
HRR the status that the relay should be in. stop button is activated. Power is restored to the Elektronikon. At this moment the * Make sure all wires connected firmly and no bad contacts are existing.
power supply to the internal relays * All the components of the Emergency stop button (base and contacts) should have
the same colour (black or brow

MK III 107 Elektronikon Mk III LRR V1.8, Serial line error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III if all else fails
2.3
Switch off/on the voltage, sometimes the failure is recoverable!® If still
no operation? Continue checklist.
- In case of warranty, replace the module.

- In case of non-warranty, carefully open the module a

MK III 108 Elektronikon Mk III LRR V1.8, Keyboard error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III if all else fails
2.3
MK III 109 Elektronikon Mk III LRR V 2.3 Filter error (relay ouputs read-back not stable)

MK III 10XX Elektronikon Mk III LRR/HRR (Online) Read back output error

MK III 11 Elektronikon Mk III LRR V1.8, V1.8: EEprom not writable Most probably due to a short circuit of the 12V supply for the digital inputs For example, when this module being use for remote control. As two digital inputs were
2.3, HRR V2.3: Relays supply error Unrecoverable failures generated by the regulator. 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

MK III 1111aaa G120 G120 G120 G120

MK III 11XX Elektronikon Mk III HRR (Online) 12V short circuit or FET to enable damaged

MK III 12 Elektronikon Mk III LRR V1.8, V1.8: Division by zero Unrecoverable failures generated by the regulator. Hardware or software problem
2.3 V2.3: EEprom not writable Replace Elektronikon
MK III 13 Elektronikon Mk III LRR V1.8, V1.8: Wrong active display, Unrecoverable failures generated by the regulator. Hardware or software problem
2.3 V2.3: EEprom checksum error Replace Elektronikon
MK III 14 Elektronikon Mk III LRR V1.8, V1.8: Relays supply error, Unrecoverable failures generated by the regulator. Replace Elektronikon
2.3 V2.3: Eprom checksum error Internal error
MK III 15 Elektronikon Mk III LRR V 2.3 Wrong activated display Unrecoverable failures generated by the regulator. Replace Elektronikon

MK III 17 Elektronikon Mk III LRR V1.8 Watch dog error Some external conditions were not met while system was checking for operation. 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
Recoverable failure. through the reset function key of the system failure display.

Check external par

MK III 200 Elektronikon Mk III LRR V Watch dog error. 200XX (bootstrap) These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR compressor can start after the failure reset. failure display.

- ‘Watchdog’ error. Check for part number. If below 1900 0700 05, replace
with new version.

- Switch off/on the voltage, sometimes the failure is

MK III 2000 Elektronikon Mk III LRR/HRR (Bootstrap) Reserved area checksum incorrect Hardware or software problem. Possibly need a new regulator

MK III 2001 Elektronikon Mk III HRR (Bootstrap) Reserved area checksum incorrect Unrecoverable error. Caused by corruption within the electronics to misread. Try to power OFF and ON again. If cannot resolved, then try a new module.

MK III 201 Elektronikon Mk III LRR V Internal power failure routine not completed These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR 201xx(bootstrap) compressor can start after the failure reset. failure display.
MK III 202 Elektronikon Mk III LRR V Backupped RAM checksum error These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR 202xx(bootstrap) compressor can start after the failure reset. failure display.
MK III 203 Elektronikon Mk III HRR Power off during EEPROM writing These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
203xx (bootstrap) compressor can start after the failure reset. failure display.
MK III 204 Elektronikon Mk III HRR Power off during EEPROM writing and power failure These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
interrupt routine enabled compressor can start after the failure reset. failure display.
204xx(bootstrap)
MK III 205 Elektronikon Mk III HRR Power off during EEPROM writing and backup ram These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
checksum incorrect. compressor can start after the failure reset. failure display.
MK III 20XX Elektronikon Mk III HRR (Bootstrap) Reserved area checksum incorrect
MK III 21XX Elektronikon Mk III HRR (Bootstrap) EPROM checksum incorrect
MK III 22 Elektronikon Mk III LRR V1.8 Eprom checksum error Internal error Replace Elektronikon Mk III if all else fails
Unrecoverable failures generated by the regulator.
MK III 22XX Elektronikon Mk III HRR (Bootstrap) Flash checksum incorrect
MK III 30XX Elektronikon Mk III HRR (Online) Division by 0
MK III 31XX Elektronikon Mk III HRR (Online) Wrong activated display
MK III 33 Elektronikon Mk III LRR V1.8 Eeprom checksum error Internal error Replace Elektronikon Mk III if all else fails
Unrecoverable failures generated by the regulator.
MK III 37 Elektronikon Mk III - AC-Line Fault Line Failute detected; in the "Ready" and "On" states, and alarm is output initially Wifh power supply and contactors that switches the power supply.
GA90VSD Simovert P 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

MK III 40 Elektronikon Mk III HRR (Autoconfig) No delivery air input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MK III 41 Elektronikon Mk III HRR (Autoconfig) More than 1 delivery air input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.
MK III 42 Elektronikon Mk III HRR (Autoconfig) More than 1 backup pressure input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MK III 43 Elektronikon Mk III HRR (Autoconfig) More than 1 intercooler pressure input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MK III 44 Elektronikon Mk III HRR (Autoconfig) More than 4 DIOE modules connected These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MK III 45 Elektronikon Mk III HRR (Autoconfig) More than 4 SIOE modules connected These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MK III 46 Elektronikon Mk III HRR (Autoconfig) More than 3 COM1 modules These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
connected one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MK III 47 Elektronikon Mk III HRR (Autoconfig) More than 2 COM3 modules These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
connected one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MK III 48 Elektronikon Mk III HRR (Autoconfig) COM3 not permitted in configuration These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MK III 49 Elektronikon Mk III HRR (Autoconfig) SIOE module not permitted in These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
configuration one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

MK III 50 Elektronikon Mk III HRR (Autoconfig) Wrong CCM during autoconfiguration These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
(CMS1, CMS2) one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Please check to make sure CMS is in correct position

MK III 51 Elektronikon Mk III HRR (Autoconfig) DIOE type configured is for ES100 These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
system one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Please check for the right module.

MK III 53 Elektronikon Mk III HRR / (Autoconfig) No VSD COM module during These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
VSD configuration one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.
Please connect COM module to regulator before autoconfiguration.

MK III 54 Elektronikon Mk III HRR / (Autoconfig) More than 1 VSD COM module These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
VSD connected. one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.
Make sure that there is only ONE COM module for the VSD. Then restart
autoconfiguration.

MK III 7001 Elektronikon Mk III HRR / (Online) Internal communication failed Internal communication between master and a COM module - Check the cable for connection between the 2 modules
VSD - Check the power supply to the modules (24V)

- 700X, where X = the com module no., for example, 7001 implies no. 1 module is not
communicating with Master module. 7002 implies no. 2 module is not co

MK III 70XX Elektronikon Mk III HRR / (Online) Internal communication failed Internal communication between master and a COM module - Check the cable for connection between the 2 modules
VSD - Check the power supply to the modules (24V)

- 700X, where X = the com module no., for example, 7001 implies no. 1 module is not
communicating with Master module. 7002 implies no. 2 module is not c

MK III 7101 Elektronikon Mk III HRR / (Online) A module in INOPERATIVE UNLOCK was Module 01 became inoperative and it was connected to another operative module Try to reprogram the modules and check the start configuration
VSD connected to an OPERATIVE regulator
MK III 71XX Elektronikon Mk III HRR / (Online) A module in INOPERATIVE UNLOCK was Module XX became inoperative and it was connected to another operative module Try to reprogram the modules and check the start configuration
VSD connected to an OPERATIVE regulator
eg. ZR315VSD with COM2 modbus module
F71XX ==> 01 = fault @ module 01 (module 01 = SIOE module)
==> 02 = fault @ module 02 (module 02 = VSD's COM2)
==> 03

MK III 7201 Elektronikon Mk III HRR / (Online) A module in INOPERATIVE LOCK was Module 01 (COM module) is inoperative by incorrect programming or by Try to reprogram
VSD connected to an INOPERATIVE or OPERATIVE connecting an empty module.
regulator
MK III 72XX Elektronikon Mk III HRR / (Online) A module in INOPERATIVE LOCK was Module 01 (COM module) is inoperative by incorrect programming or by Try to reprogram
VSD connected to an INOPERATIVE or OPERATIVE connecting an empty module.
regulator
MK III 7301 Elektronikon Mk III HRR / (Online) Communication failure between regulator - Loose connection between HRR and converter. - Check connections of converter / COM module
VSD and converter - COM 1 (or COM 2) is faulty - Isolate converter from COM module, and use VSD simulation software to test whether
- CU /CUVC in doubt (Siemens) COM module or converter is at fault. A pc with RS232 cable or RS485 ( such as that use
- GAX card (power supply card for 90 VSD Simovert P) is in doubt for SDP4win) is required. The cable i
- Main Control Card (ABB)

* 730X, where x = 1 means communication module no.1 or com

MK III 7302 Elektronikon Mk III HRR / (Online) Communication failure between regulator - Loose connection between HRR and converter. - Check connections of converter / COM module
VSD and converter - COM 1 (or COM 2) is faulty - Isolate converter from COM module, and use VSD simulation software to test whether
- CU /CUVC in doubt (Siemens) COM module or converter is at fault. A pc with RS232 cable or RS485 ( such as that use
- GAX card (power supply card for 90 VSD Simovert P) is in doubt for SDP4win) is required. The cable i
- Main Control Card (ABB)
* 730X, where x = 1 means communication module no.1 or com
MK III 73XX Elektronikon Mk III HRR / (Online) Communication failure between regulator - Loose connection between HRR and converter. - Check connections of converter / COM module
VSD and converter - COM 1 (or COM 2) is faulty - Isolate converter from COM module, and use VSD simulation software to test whether
- CU /CUVC in doubt (Siemens) COM module or converter is at fault. A pc with RS232 cable or RS485 ( such as that use
- GAX card (power supply card for 90 VSD Simovert P) is in doubt for SDP4win) is required. The cable i
- Main Control Card (ABB)
* 730X, where x = 1 means communication module no.1 or com

MK III 7401 Elektronikon Mk III HRR / (Online) Incorrect format in data send from Error 0 - incorrect data format (byte 6/7, readback status) - Switch machine OFF then back ON again. Allow a few mins for all power inside
VSD converter to regulator Error 100 - incorrect data format (byte 2/3/8/9, parameters) electronics to dissipate.
SIEMENS / ABB Error 200 - Checksum failure - Reprogam the converter.
Siemens VSD: A possible fault would that some data in EPROM is lost, or
corrupted, or during programming, - Check parameters, compare with list and adjust any discrepancies

MK III 7402 Elektronikon Mk III HRR / (Online) Incorrect format in data send from Error 0 - incorrect data format (byte 6/7, readback status) - Switch machine OFF then back ON again. Allow a few mins for all power inside
VSD converter to regulator Error 100 - incorrect data format (byte 2/3/8/9, parameters) electronics to dissipate.
SIEMENS / ABB Error 200 - Checksum failure - Reprogam the converter.
Siemens VSD: A possible fault would that some data in EPROM is lost, or
corrupted, or during programming, - Check parameters, compare with list and adjust any discrepancies

MK III 74XX Elektronikon Mk III HRR / (Online) Incorrect format in data send from Error 0 - incorrect data format (byte 6/7, readback status) - Switch machine OFF then back ON again. Allow a few mins for all power inside
VSD converter to regulator Error 100 - incorrect data format (byte 2/3/8/9, parameters) electronics to dissipate.
SIEMENS / ABB Error 200 - Checksum failure - Reprogam the converter.
Siemens VSD: A possible fault would that some data in EPROM is lost, or
corrupted, or during programming, - Check parameters, compare with list and adjust any discrepancies

MK III Internal Fault # 1 Elektronikon Mk IV - II or System input Error An I/O is missing from the module after programming. Check with FSP, or reprogram the module and make sure all necessary I/O are declared.
Higher The error 1 indicates that the master expects an extra extension module which is
not found or recognized on the system.
Sinamics G120 F00006 Siemens Sinamic G120 / Chip temperature rise exceeds critical levels. Reaction: OFF 2 Remedy: Check the following:
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Load or load step too high?
• Reduce ramp-up time (P1120).
• Load at start-up is too high • Motor power (p0307) must match inverter power (r0206).
• Load step is too high • Use setting P0290 = 0 or 2 for preventing F00006.
• Ramp-up rate is too fast

Sinamics G120 F00011 Siemens Sinamic G120 / Motor Over Temperature Reaction: OFF 2 (OFF 3) Remedy: Check the following:
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Load or load step too high?
• Motor nominal overtemperatures (p0626 - p0628) must be correct
Motor overloaded • Motor temperature warning level (p0604) must match

Sinamics G120 F00015 Siemens Sinamic G120 / Motor temperature signal lost Reaction: OFF 2 (OFF 3) Remedy: Check the following:
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • the connection of the motor temperature sensor to the control unit
• the setting of p0601
Open or short circuit of motor temperature sensor. If signal loss is detected,
temperature monitoring switches over
to monitoring with the motor thermal model.

Sinamics G120 F00020 Siemens Sinamic G120 / Mains Phase Missing Reaction: OFF 2 (OFF 3) Remedy: Check the input wiring of the mains phases
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2
Fault occurs if one of the three input phases are missed and the pulses are enabled
and drive is loaded

Sinamics G120 F00021 Siemens Sinamic G120 / Earth fault Reaction: OFF 2 Remedy:
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 Note: Framesizes D to F: this fault only occurs on inverters that have 3 current sensors.
Fault occurs if the sum of the phase currents is higher than 5 % of the nominal
inverter current.

Sinamics G120 F00022 Siemens Sinamic G120 / Powerstack fault Reaction: OFF 2 Remedy: Contact Service Department.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 Change inverter power module

This hardware fault caused by the following events:

• DC-link overcurrent = short circuit of IGBT
• Short circuit of chopper

Sinamics G120 F00023 Siemens Sinamic G120 / Output phase fault Reaction: OFF 2 (OFF 3) Remedy: Check motor connection.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2

One output phase is disconnected.

Sinamics G120 F00025 Siemens Sinamic G120 / F3E Dclink Ripple Reaction: OFF 2 (OFF 3) Remedy: Contact Service Department.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2

Large ripples on the dclink.

Sinamics G120 F00026 Siemens Sinamic G120 / Supply to Gate Driver Not Enabled Reaction: OFF 2 Remedy: Contact Service Department.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2
Cause: Gate driver not enabled. Can be caused also by a synchronization error of
the safety state machines.

Sinamics G120 F00027 Siemens Sinamic G120 / Overcurrent on W phase Reaction: OFF 2 Remedy: Check Inverter and Motor wiring
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2
This hardware fault caused by the following events:
• Over current trip on W phase
• Earth Fault

Sinamics G120 F00028 Siemens Sinamic G120 / Power limit exceeded during regeneration Reaction: OFF 2 • Reduce regeneration from active load
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Reduce ramp down rate
• Increase Imax regeneration limit in p1253
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.

Sinamics G120 F00029 Siemens Sinamic G120 / EM brake overcurrent Reaction: OFF 2
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2
Sinamics G120 F00035 Siemens Sinamic G120 / Auto restart after n Reaction: OFF 2 (OFF 3)
GA15-30VSD / CU240 Acknowledge: Power on
Cause: Auto restart attempts exceed value of p1211.
Sinamics G120 F00041 Siemens Sinamic G120 / Motor Data Identification Failure Reaction: OFF 2 Remedy: Check the following:
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • r0949 = 0: is the motor connected to the inverter.
• r0949 = 1-49: are the motor data in p0304 - p0311 correct.
Motor data identification failed. • Check what type of motor wiring is required (star, delta).
• 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%.

Sinamics G120 F00042 Siemens Sinamic G120 / Speed Control Optimisation Failure Reaction: OFF 2 Remedy: Make sure motor has data been entered correctly.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 Motor data identification needs to have been done.

Motor data identification failed.

• r0949 = 0: Time out waiting for stable speed
• r0949 = 1: Inconsistent readings

Sinamics G120 F00051 Siemens Sinamic G120 / Parameter EEPROM Fault Reaction: OFF 2 • Must be Power Cycled to cancel this bug as some parameters may not be read correct.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Factory Reset and new parameterization, if power cycle does not remove fault
• Change inverter control unit
Read or write failure while access to EEPROM. • Change some parameters back to default values if the
This can also be caused by the EEPROM being full, too many parameters have been
changed.

Sinamics G120 F00052 Siemens Sinamic G120 / power stack Fault Reaction: OFF 2 • r0949 = 1: Failed reading PS identity
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • r0949 = 2: PS identity wrong
Cause: Read failure for power stack information or invalid data. • r0949 = 3: Failed reading PS version
Remedy: • Check connection between inverter power module and inverter control • r0949 = 4: PS version wrong
unit • r0949 = 5: Start of Part 1 PS data wrong
• Powercycle inverter Control Unit. • r0949 = 6: PS number of temp. sensor wrong
• Change inverter P • r0949 = 7: PS numb

Sinamics G120 F00055 Siemens Sinamic G120 / BOP-EEPROM Fault Reaction: OFF 2 (OFF 3) • Factory Reset and new parameterization
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Change BOP
• r0949 = 5096 : Use a BOP with a bigger EEPROM
Read or write failure while saving non-volatile parameter to EEPROM on BOP • r0949 = 9160 : Use a BOP with a smaller EEPROM
whilst parameter cloning. • r0949 = 1000 + Block No: Reading data block failed
• r0949 = 3000 + Block No: Reading data block

Sinamics G120 F00056 Siemens Sinamic G120 / BOP not fitted Reaction: OFF 2 (OFF 3) Remedy: Fit BOP and try again.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2
Trying to initiate parameter cloning without BOP fitted.

Sinamics G120 F00057 Siemens Sinamic G120 / BOP fault Reaction: OFF 2 (OFF 3) Remedy: Download to BOP or replace BOP.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2

• Parameter cloning with empty BOP.

• Parameter cloning with invalid BOP.

Sinamics G120 F00058 Siemens Sinamic G120 / BOP contents incompatible Reaction: OFF 2 (OFF 3) created on another type of drive.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2
Trying to initiate parameter cloning with BOP created on another type of drive.

Sinamics G120 F00060 Siemens Sinamic G120 / Asic Timeout Reaction: OFF 2 Check connection between inverter power module and inverter control unit
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 Fault appears sporadically:
• Communication failure due to EMC problems
Internal communications failure • Check - and if necessary - improve EMC
• r0949 = 0: HW reported Link Fail • Use EMC filter
• r0949 = 1: SW reported Link Fail Fault appears immediately when mains voltage is a

Sinamics G120 F00061 Siemens Sinamic G120 / Par Cl. MMC-PS not fitted Fault Reaction: OFF 2 • r0949 = 0: Use MMC-PS with FAT12 or FAT16 format or correct MMC-PS Type, or fit an
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 MMC-PS to Drive.
Cause: MMC-PS Cloning Failed. • r0949 = 1: Check MMC ( e.g is MMC full ) - Format MMC again to FAT16
• r0949 = 0: MMC-PS Not Connected or incorrect MMC-PS Type • r0949 = 2: Put the correct named file in the correct directory /USER/SINAMICS
• r0949 = 1: MMC-PS cannot write to MMC
• r0949 = 2: MMC-PS File not available
• r0949 = 3: MMC-PS cannot read the

Sinamics G120 F00062 Siemens Sinamic G120 / Par Cl. MMC-PS contents invalid Reaction: OFF 2 Remedy: Recopy and ensure operation completes.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2

File exists but the contents are not valid Control Word Corruption.

Sinamics G120 F00063 Siemens Sinamic G120 / Par Cl. MMC-PS contents incompatible Reaction: OFF 2 Remedy: Ensure clone from compatiable drive type.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2

File exists but was not the correct drive type.

Sinamics G120 F00064 Siemens Sinamic G120 / Drive attempted to do an automatic clone during Reaction: OFF 2 Remedy: If a automatic clone is required:
GA15-30VSD / CU240 startup. Acknowledge: Quit fault eg. via DI2 - Insert MMC with correct File anc power cycle.
If no automatic clone is required:
No Clone00.bin File in the correct directory /USER/SINAMICS/DATA. - Remove MMC if not needed and power cycle.
- Reset P8458 = 0 and power cycle.

Sinamics G120 F00070 Siemens Sinamic G120 / PLC setpoint fault Reaction: OFF 2 (OFF 3) • Check and improve - if necesarry - the value in p2040
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Acknowledge fault
• if fault persists, change inverter control unit
No setpoint values from PLC during telegram off time
Sinamics G120 F00071 Siemens Sinamic G120 / USS setpoint fault Reaction: OFF 2 (OFF 3) Remedy: Check and if necessary improve the monitoring time in the STARTER SW while
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 getting the command source.
Check USS master
No setpoint values from USS during telegram off time

Sinamics G120 F00072 Siemens Sinamic G120 / USS Setpoint Fault Reaction: OFF 2 (OFF 3) Remedy: Check USS master
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2

No setpoint values from USS during telegram off time

Sinamics G120 F00073 Siemens Sinamic G120 / Control Panel setpoint fault Reaction: OFF 2 (OFF 3) Remedy: • Check and improve - if necesarry - the value in p3984
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Acknowledge fault
• if fault persists, change inverter control unit
No setpoint values from Control Panel during telegram off time

Sinamics G120 F00080 Siemens Sinamic G120 / AI lost Input Signal Reaction: OFF 2 (OFF 3)
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2
• Broken wire
• Signal out of limits

Sinamics G120 F00085 Siemens Sinamic G120 / External Fault Reaction: OFF 2 (OFF 3) Remedy: • Check P2106.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Disable control word 2 bit 13 as command source.
• Disable terminal input for fault trigger.
External fault triggered via command input via control word 2, bit 13

Sinamics G120 F00090 Siemens Sinamic G120 / Encoder feedback loss Reaction: OFF 2 Remedy: Stop the inverter.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • r0949 = 2, Increase value of p0494 or reduce value of p1120 and p1121.
• r0949 = 5, select encoder type via p0400.
Signal from Encoder lost (check fault value r0949): • r0949 = 5, select SLVC mode (p1300 = 20 or 22).
• r0949 = 0: Encoder signal lost. • r0949 = 7, select SLVC mode (p1300 = 20 or 22).
• r0949 = 1: Encoder loss detected due to sudden speed change (i.e. speed change • Check con
detected on encoder in a
single sca

Sinamics G120 F00100 Siemens Sinamic G120 / Watchdog Reset Reaction: OFF 2 Remedy: Contact Service Department.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 Change inverter control unit.
Software Error

Sinamics G120 F00101 (N) Siemens Sinamic G120 / Stack Overflow Reaction: OFF 2 Remedy: Contact Service Department.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 Change inverter control unit

Software error or processor failure.

Sinamics G120 F00221 Siemens Sinamic G120 / PID Feedback below min. Value Reaction: OFF 2 (OFF 3) Remedy: • Change value of p2268.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Adjust feedback gain.
F00222 PID Feedback above max.
PID Feedback below min. value p2268.

Sinamics G120 F00222 Siemens Sinamic G120 / PID Feedback above max. Value Reaction: OFF 2 (OFF 3) • Change value of p2267.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Adjust feedback gain.

PID feedback above max. value p2267.

Sinamics G120 F00350 Siemens Sinamic G120 / Configuration vector for the drive failed Reaction: OFF 2 nternal Failures can not be fixed.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 r0949 = 13 - Make sure the right power module is fitted
During startup the drive checks if the configuration vector (SZL vector) has been Note: Fault needs power cycle to be acknowledged.
programmed correctly and if hw
matches the programmed vector. If not the drive will trip.
• r0949 = 1: Internal Failure

Sinamics G120 F00395 Siemens Sinamic G120 / Acceptance Test / Confirmation pending Reaction: OFF 2 Remedy: Safety Units:
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 An Acceptance Test needs to be performed. Follow the the steps of the Acceptance Log
which is part of the Operating
This fault occurs after a Powermodul (PM) / Control Unit (CU) Swap or a Startup Instructions.
Clone. It can also be caused by a After performing the acceptance test the fault can be acknowledged by the following
faulty read from the EEPROM, see F0051 for more details. procedure:
The parameterset after a CU swa P0010 =

Sinamics G120 F00400 (N) Siemens Sinamic G120 / PROFIBUS: DS101/DB101 (control pannel) failure. Reaction: OFF 2 Remedy: Restart C2 connection.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2

Timeout, trigger fault,…

Sinamics G120 F00452 Siemens Sinamic G120 / Belt Failure Reaction: OFF 2 (OFF 3) Check the following:
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • No breakage, seizure or obstruction of drive train.
• If using an external speed sensor, check the following parameters for correct function:
Load conditions on motor indicate belt failure or mechanical fault. • If using the torque envelope, check parameters:
• r0949 = 0: trip low torque/speed • Apply lubrication if required.
• r0949 = 1: trip high torque/speed

Sinamics G120 F00453 Siemens Sinamic G120 / Motor Stalled Reaction: OFF 2 • Reduce ramp rate in p1120
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Enable flying start (p1200 equal to 1)
• Increase boost in p1611
• In SLVC or VC (p1300 greater than 20) and Ramp rate too fast • Connect motor or use larger motor for this inverter or use VF mode (p1300 less than
• In SLVC or VC (p1300 greater than 20) and done OFF2 and RUN onto a spinning 20).
motor without Flying start • Correct the wiring to the motor and / or the encoder as requir
enabled
• In SLVC (p1300 = 20 or 2

Sinamics G120 A00501 Siemens Sinamic G120 / Current Limit Reaction: NONE Remedy: Check the following:
GA15-30VSD / CU240 Acknowledge: NONE • Motor power (P0307) must correspond to inverter power (r0206).
• Cable length limits must not be exceeded.
• Motor power does not correspond to the inverter power • Motor cable and motor must have no short-circuits or earth faults
• Motor leads are too long • Motor parameters must match the motor in us
• Earth faults
Sinamics G120 A00502 Siemens Sinamic G120 / Overvoltage limit Reaction: NONE Remedy: If this warning is displayed permanently, check drive input voltage.
GA15-30VSD / CU240 Acknowledge: NONE

Overvoltage limit is reached. This warning can occur during ramp down, if the Vdc
controller is disabled (P1240 = 0).

Sinamics G120 A00503 Siemens Sinamic G120 / UnderVoltage Limit Reaction: NONE Remedy: Check main supply voltage.
GA15-30VSD / CU240 Acknowledge: NONE

• Main supply failed

• Main supply and consequently DC-link voltage (r0026) below specified limit.

Sinamics G120 A00504 Siemens Sinamic G120 / Inverter OverTemperature Reaction: NONE Remedy: Note:
GA15-30VSD / CU240 Acknowledge: NONE r0037 = 0: Heat sink temperature
r0037 = 1: Chip junction temperature (includes heat sink)
Warning level of inverter heat sink temperature, warning level of chip junction Check the following:
temperature, or allowed change in temperature • Ambient temperature must lie within specified limits
on chip junction is exceeded, resulting in pulse frequency reduction and/or output • Load conditions and load steps must be appropriate
frequency re • Fan must turn wh

Sinamics G120 A00505 Siemens Sinamic G120 / Inverter I2T Reaction: NONE Remedy: Check that load cycle lies within specified limits.
GA15-30VSD / CU240 Acknowledge: NONE

Warning level exceeded, current will be reduced if parameterized (P0610 = 1)

Sinamics G120 A00506 Siemens Sinamic G120 / IGBT junction temperature rise warning Reaction: NONE Remedy: Check that load steps and shock loads lie within specified limits.
GA15-30VSD / CU240 Acknowledge: NONE
Overload warning. Difference between heat sink and IGBT junction temperature
exceeds warning limits.

Sinamics G120 A00507 Siemens Sinamic G120 / Inverter temp. signal lost Reaction: NONE Remedy: Check the following:
GA15-30VSD / CU240 Acknowledge: NONE • the connection of the motor temperature sensor to the control unit
• the setting of p0601
Inverter temperature signal loss

Sinamics G120 A00511 Siemens Sinamic G120 / Motor OverTemperature I2T Reaction: NONE Remedy: Independently of the kind of temperature determination check:
GA15-30VSD / CU240 Acknowledge: NONE • P0604 motor temperature warning threshold
• P0625 motor ambient temperature
• Motor overloaded. If P0601 = 0 or 1, check the following:
• Load cycles or load steps too high. • Check if name plate data are correct? If not perform quick com

Sinamics G120 A00523 Siemens Sinamic G120 / Output fault Reaction: NONE Remedy: Check motor connection
GA15-30VSD / CU240 Acknowledge: NONE

One phase of output is disconnected.

Sinamics G120 A00525 Siemens Sinamic G120 / F3E Dclink Ripple Reaction: NONE
GA15-30VSD / CU240 Acknowledge: NONE

Large dclink ripple

Large dclink ripple detected

Sinamics G120 A00535 Siemens Sinamic G120 / Braking Resistor Overload Reaction: NONE Remedy: Reduce the breaking energy.
GA15-30VSD / CU240 Acknowledge: NONE Use a breaking resistor with a higher rating.
The breaking energy is too large.
The breaking resistor is not suited for the application.

Sinamics G120 A00541 Siemens Sinamic G120 / Motor Data Identification Active Reaction: NONE
GA15-30VSD / CU240 Acknowledge: NONE
Motor data identification (P1910) selected or running.

Sinamics G120 A00542 Siemens Sinamic G120 / Speed Control Optimisation Active Reaction: NONE
GA15-30VSD / CU240 Acknowledge: NONE
Speed Control Optimisation (P1960) is selected or running.

Sinamics G120 A00544 Siemens Sinamic G120 / Speed deviation Reaction: NONE Remedy: The motoring or regenerative load is too large.
GA15-30VSD / CU240 Acknowledge: NONE
The actual speed has exceeded the maximal speed (status bit r2197.12) or the
speed deviation is larger than specified
(status bit 2197.7).

Sinamics G120 A00564 Siemens Sinamic G120 / MMC Plugged During Operation Reaction: NONE Remedy: Remove MMC-PS from drive.
GA15-30VSD / CU240 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.

Sinamics G120 A00590 Siemens Sinamic G120 / Encoder feedback loss warning Reaction: NONE Remedy: Stop inverter and then
GA15-30VSD / CU240 Acknowledge: NONE • Check encoder fitted. If encoder fitted and r0949 = 5, select encoder type via P0400.
• If encoder fitted and r0949 = 6, check connections between encoder module and
Signal from Encoder lost; Inverter might have switched to sensorless vector inverter.
control. • If encoder not fitted and r0949 = 5, sele
Check also alarm value r0947:
• r0949 = 0: Encoder signal lost.
• r0949 = 5: Encoder not configured in P0400, but required for sensored

Sinamics G120 A00600 Siemens Sinamic G120 / RTOS Overrun Warning Reaction: NONE Remedy: Contact Service Department
GA15-30VSD / CU240 Acknowledge: NONE

Internal time slice overrun

Sinamics G120 A00700 Siemens Sinamic G120 / PROFIBUS: Parameter or configuration error Reaction: NONE Remedy: check parameter and/or configuration telegram
GA15-30VSD / CU240 Acknowledge: NONE

Wrong parameter and/or configuration telegram

Sinamics G120 A00701 Siemens Sinamic G120 / PROFIBUS: DoubleWord error Reaction: NONE Remedy: power cycle
GA15-30VSD / CU240 Acknowledge: NONE

Error in double word reference table

Sinamics G120 A00702 Siemens Sinamic G120 / PROFIBUS: no bus detection Reaction: NONE Remedy: check the cables and the bus hardware
GA15-30VSD / CU240 Acknowledge: NONE

connection error, no bus initialization (no master), no clear bus signal, …

Sinamics G120 A00703 Siemens Sinamic G120 / PROFIBUS: no reference values Reaction: NONE Remedy: check bus transmission
GA15-30VSD / CU240 Acknowledge: NONE
no or empty control word 1 received

Sinamics G120 A00704 Siemens Sinamic G120 / PROFIBUS: loose of links Reaction: NONE Remedy: temporary, if permanent the fault detection is activated
GA15-30VSD / CU240 Acknowledge: NONE
lost subscriber information

Sinamics G120 A00705 Siemens Sinamic G120 / PROFIBUS: timeout actual value Reaction: NONE Remedy: temporary, if permanent the fault detection is activated
GA15-30VSD / CU240 Acknowledge: NONE
no actual data from CUP

Sinamics G120 A00706 Siemens Sinamic G120 / PROFIBUS: fatal SW error (e.g. hardware check, Reaction: NONE Remedy: if permanent power cycle, reload firmware
GA15-30VSD / CU240 communication, V Acknowledge: NONE

e.g. hardware check, communication, V1SL stack, …

Sinamics G120 A00707 Siemens Sinamic G120 / PROFIBUS: wrong PB address at startup Reaction: NONE Remedy: check DIP switch and/or P0918
GA15-30VSD / CU240 Acknowledge: NONE
wrong DIP switch or parameter settings for PROFIBUS address

Sinamics G120 A00708 Siemens Sinamic G120 / --- not used ---
GA15-30VSD / CU240
Sinamics G120 A00709 Siemens Sinamic G120 / --- not used ---
GA15-30VSD / CU240
Sinamics G120 A00710 Siemens Sinamic G120 / CB communication error Reaction: NONE Remedy: Check CB hardware
GA15-30VSD / CU240 Acknowledge: NONE
Cause: Communication with CB (communication board) is lost.
Sinamics G120 A00711 Siemens Sinamic G120 / CB configuration error Reaction: NONE Remedy: Check CB parameters
GA15-30VSD / CU240 Acknowledge: NONE
CB (communication board) reports a configuration error.

Sinamics G120 A00910 Siemens Sinamic G120 / Vdc-max controller de-activated Reaction: NONE Remedy: Check the following:
GA15-30VSD / CU240 Acknowledge: NONE • Input voltage must lie within range.
• Load must be match.
Occurs • In certain cases apply braking resistor.
• 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.

Sinamics G120 A00911 Siemens Sinamic G120 / Vdc-max controller active Reaction: NONE Note: Higher inertia requires longer ramp times; otherwise, apply braking resistor.
GA15-30VSD / CU240 Acknowledge: NONE
Vdc max controller is active; so ramp-down times will be increased automatically
to keep DC-link voltage (r0026)
within limits (P2172).
Remedy: Check the following:
• Supply voltage must lie within limits indicated on rat

Sinamics G120 A00912 Siemens Sinamic G120 / Vdc-min Controller active Reaction: NONE
GA15-30VSD / CU240 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

Sinamics G120 A00921 Siemens Sinamic G120 / AO parameters not set properly. Reaction: NONE Remedy: Check the following:
GA15-30VSD / CU240 Acknowledge: NONE • Parameter settings for output identical
Cause: AO parameters (P0777 and P0779) should not be set to identical values, • Parameter settings for input identical
since this would produce illogical results. • Parameter settings for output do not correspond to AO type
Set P0777 and P0779 to different values.

Sinamics G120 A00922 Siemens Sinamic G120 / No load applied to inverter Reaction: NONE Remedy: Check that motor is connected to inverter.
GA15-30VSD / CU240 Acknowledge: NONE
Cause: No Load is applied to the inverter.
As a result, some functions may not work as under normal load conditions.

Sinamics G120 A00923 Siemens Sinamic G120 / Both JOG Left and JOG Right are requested Reaction: NONE Remedy: Do not press JOG right and left simulutanously.
GA15-30VSD / CU240 Acknowledge: NONE
Both JOG right and JOG left (P1055/P1056) have been requested. This freezes the
RFG output frequency at its current
value.
Sinamics G120 A00936 Siemens Sinamic G120 / PID Autotuning Active Reaction: NONE Remedy: Alarm disappears when PID Autotuning has finished.
GA15-30VSD / CU240 Acknowledge: NONE
Cause: PID Autotuning (P2350) selected or running
Sinamics G120 A00952 Siemens Sinamic G120 / Belt Failure Detected Reaction: NONE Remedy: Check the following:
GA15-30VSD / CU240 Acknowledge: NONE • No breakage, seizure or obstruction of drive train.
• If using an external speed sensor, check the following parameters for correct function.
Load conditions on motor indicate belt failure or mechanical fault. • If using the torque envelope, check parameters:
• Apply lubrication if requi

Sinamics G120 F01600 Siemens Sinamic G120 / Passivated STO with drive fault Reaction: OFF 2 (OFF 3) • r0949 = 100 or 200
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 Increase the ramping times p1120/p1121 or the safety tolerance p9691/p9891,
check the motor parameters (p0394 - p0311) or run the motor identification (p1910)
A passivated safe torque off (passivated STO) has been initiated by hardware due again.
to a drive fault: Decrease the rate of switching the safety signals or lower the cycl
• r0949 = 33: passivated STO acknowledge after a drive fault requires the OFF first
and then an

Sinamics G120 F01601 Siemens Sinamic G120 / System startup error Reaction: OFF 2 (OFF 3) • Power-cycle CU (since fault F1601 cannot be acknowledged).
GA15-30VSD / CU240 Acknowledge: Power on • Make sure that CU is connected correctly to PM.
• Reduce EMC.
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

Sinamics G120 F01610 Siemens Sinamic G120 / EEPROM inconsistent Reaction: OFF 2 (OFF 3) Load safety parameters again.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2
Cause: EEPROM data inconsistency error:
• r0949 = 100: Safety parameters have not been written correctly to EEPROM on
P1. Try to load parameters
again.
• r0949 = 200: EEPROM data inconsistency er

Sinamics G120 F01611 Siemens Sinamic G120 / Defect in cross comparis. Reaction: OFF 2 (OFF 3) • Reduce EMC.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Perform a forced dynamisation
Cause: Data exchange error between processors:
• r0949 = 100: P2 has entered the safe torque off due to a drive fault on P2 or a
subsequent fault of F1600/F1630
• r0949 = 102: Dynamic checksums a

Sinamics G120 F01612 Siemens Sinamic G120 / Diff. in hardw. Detection Acknowledge: Quit fault eg. via DI2 • Inverter hardware is faulty or problem in processor communication. Perform a power
GA15-30VSD / CU240 Cause: The hardware (safety or non-safety hardware) could no be identified. cycle.
• r0949 = 100: Identification error during startup on P1.
• r0949 = 101: Runtime detection error on P1.
• r0949 = 102: Hardware or software con

Sinamics G120 F01613 Siemens Sinamic G120 / Maximum frequency exceeded Reaction: OFF 2 (OFF 3) • Check application or increase safety threshold p9691/p9891.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • See also remedies for F1614.

The maximum frequency has been exceeded.

• r0949 = 100: Frequency error on P1, maximum frequency exceeded.
• r0949 = 200: Maximum frequency exceeded on P2.

Sinamics G120 F01614 Siemens Sinamic G120 / Frequency consistency fault Reaction: OFF 2 (OFF 3) • Increase ramping times p1120 and p1121.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Make sure that drive is not at current limit when starting.
• See remedies for F0453.
Error in frequency detection of the frequency estimation circuit (voltage frequency • Check hardware speed estimation circuit.
measurement (VFM) module):
• r0949 = 100: Difference in frequency comparison on P1.
• r0949 = 101: VFM estimat

Sinamics G120 F01615 Siemens Sinamic G120 / Error in hardw. environm. Reaction: OFF 2 (OFF 3) • r0949 = 100:
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Check supply voltage.
• Reduce EMC.
• r0949 = 100: Error in supply voltage 3.3 V or 24 V on the control board. • r0949 = 101:
• r0949 = 101: Temperature of control board exceeds the limits. • Check ambient temperature.

Sinamics G120 F01616 Siemens Sinamic G120 / Processor selftest faulty Reaction: OFF 2 (OFF 3) • Run self-test again (set bit 1 in p9601 and p9801 and enter the STO mode, then leave
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 the STO mode again).
Cause: The processor selftest has uncovered an error:
• r0949 = 100: General error on P1.
• r0949 = 101: Error in RAM test on P1.
• r0949 = 102: Error in ROM test on P1.
• r0949 = 103: Error in p

Sinamics G120 F01625 Siemens Sinamic G120 / Consecutive no. incorr. Reaction: OFF 2 (OFF 3) • Acknowledge safety fault.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Restart inverter module or check EMC levels on accumulated faults.
Cause: The consecutive counter checks the consistency of the communication
between P1 and P2:
• r0949 = 100: The consecutive monitoring counter has an error on P1.
• r0949 = 101: Processors are o

Sinamics G120 F01630 Siemens Sinamic G120 / Safe Brake Control faulty Reaction: OFF 2 (OFF 3) • Check the wiring of the brake module
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Exchange brake module.
An error has been detected with the brake feedback.
• r0949 = 0: Problem with the safe brake.
• r0949 = 100: SB-Module: wire break detected or internal braketests failed during
dynamisation.
•r
Sinamics G120 F01640 Siemens Sinamic G120 / PROFIsafe Driver Fault Reaction: OFF 2 (OFF 3) • Check all PROFIsafe settings (including your higher level failsafe control system).
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Acknowledge PROFIsafe fault.

An error has been detected with the PROFIsafe driver.

• r0949 = 102: A parameterisation error occured on P1. The parameters received
from the bus are not correct.
Check PROFIsafe parameters.
•r

Sinamics G120 F01649 Siemens Sinamic G120 / Internal software error Reaction: OFF 2 (OFF 3)
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2

• r0949 = 1: Buffer overflow on checksum calculation for P1 parameter access

functions.
• r0949 = 2: Buffer overflow on checksum calculation for P2 parameter access
functions.
• r0949 = 3: Endle

Sinamics G120 F01650 Siemens Sinamic G120 / Fault in safety parametr. Reaction: OFF 2 (OFF 3) • Perform safety commissioning.
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 • Try leaving via p3900 = 11.
Error during startup or safety commissioning/reset:
• r0949 = 0: Error during safety commissioning/reset.
• r0949 = 1: Checksum error during safety commissioning or safety reset.
• r0949 = 2: Er

Sinamics G120 F01655 Siemens Sinamic G120 / Fault at processor reset Reaction: OFF 2 (OFF 3) • Retrigger the safety reset (perform a hot swap of the inverter module).
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2
Cause: • r0949 = 100: Safety reset timeout on P1.
• r0949 = 200: Safety reset timeout on P2.

Sinamics G120 F01659 Siemens Sinamic G120 / Denial of paramet. Change Reaction: OFF 2 (OFF 3) • Acknowledge fault and enter safety commissioning again. If not possible, leave the
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 safety commissioning with
Cause: A write request for one or more safety parameters was rejected: p3900 = 11 and operate the drive with the old safety settings.
• r0949 = 0: Problem during finalization of safety parameters. Drive has reloaded
the old data.
• r0949 = 1: Safety password

Sinamics G120 F01660 Siemens Sinamic G120 / Wrong safety checksum Reaction: OFF 2 (OFF 3) • Make sure that checksums in p9798 and p9898 are identical. If not, ensure that
GA15-30VSD / CU240 Acknowledge: Quit fault eg. via DI2 parametrisation is identical
(p96xx = p98xx).
• r0949 = 0: Attempt to leave safety commissioning with r9798 != p9799. • Set checksum in p9799 or p9899 correctly.
• r0949 = 1: Attempt to leave safety commissioning with r9898 != p9899. • If setting the checksums not successful, leave safety commissioning via p3900 =
• r0949 = 2: Attempt to leave safety commissioning

Sinamics G120 A01690 Siemens Sinamic G120 / Safety parameter changed Reaction: NONE Remedy: Finish safety commissioning by setting p3900 = 10 or p3900 = 11 or wait until
GA15-30VSD / CU240 Acknowledge: NONE safety reset is complete.
The warning indicates that at least one parameter has been changed in the safety
commissioning or safety reset.

Sinamics G120 A01691 Siemens Sinamic G120 / SLS signal inconsistency Reaction: NONE Remedy: Check consistency of safety input signals and acknowledge the following safe
GA15-30VSD / CU240 Acknowledge: NONE torque off due to a drive fault.
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

Sinamics G120 A01692 Siemens Sinamic G120 / Speed for SLS exceeded Reaction: NONE Remedy: ad a) Reduce speed before entering the SLS or change the setting in p9692.
GA15-30VSD / CU240 Acknowledge: NONE 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.
a) Output frequency when entering the SLS is higher than p9690 and p9692 is Acknowledge the passiv
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

Sinamics G120 A01696 Siemens Sinamic G120 / Switch-on is inhibited Reaction: NONE Remedy: Check if a deactivated gate driver or the current safety mode (STO, SS1, SLS) is
GA15-30VSD / CU240 Acknowledge: NONE inhibiting the start. Check the inhibit
bit (r0052.6).
Switching on of the drive not possible and the drive will therefore remain in the
READY state (see r0002).

Sinamics G120 A01697 Siemens Sinamic G120 / Wrong safety param. Data Reaction: NONE Remedy: Restart drive (perform power cycle) to load correct safety data.
GA15-30VSD / CU240 Acknowledge: NONE

Semaphore problem at startup. Cannot load last safety parameters. Loading

default values instead.

Sinamics G120 A01698 Siemens Sinamic G120 / Safety commis./reset act. Reaction: NONE Remedy: Finish commissioning with p3900 = 10 (accept changed) or p3900 = 11 (discard
GA15-30VSD / CU240 Acknowledge: NONE changes) or wait until safety reset
is complete.
The safety reset or the safety commissioning are currently active (selected via
p0010 = 95).

Sinamics G120 A01699 Siemens Sinamic G120 / Forced dynamis. Required Reaction: NONE Remedy: Select and then de-select STO (p9601.bit1 and p9801.bit1 must be set).
GA15-30VSD / CU240 Acknowledge: NONE
Cause: Dynamisation timer (see r9660) has expired. A new dynamisation test is
required.

Micromaster Constant Speed Micromaster Eco Micromaster only runs at fixed speed Improper anolgue signal from Masterdrive or Micromaster has problem. - 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
Micromaster F001 Micromaster Eco Overvoltage Overvoltage 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.

Micromaster F002 Micromaster Eco Overcurrent Overcurrent - Check whether the motor power corresponds to the inverter power.
- Check that the cable length limits have not been exceeded.
- Check motor cable and motor for short - circuits and earth faults.
- Check whether the motor parameters (P080 - P085) corresp

Micromaster F003 Micromaster Eco Overload Overload - Check whether the motor is overloaded.
- Increase the maximum motor frequency if a motor with high slip is used.
Micromaster F004 Micromaster Eco Overheating of motor (monitoring with PTC) - Check if the motor is overloaded
- Check the connections to the PTC
- Check that P087 has not been set to 1 without a PTC being connected
Micromaster F005 Micromaster Eco Inverter overtemperature (internal PTC) - Check that the ambient temperature is not too high.
- Check that the air inlet and outlet are not obstructed
- Check that the inverter's integral fan is working
Micromaster F008 Micromaster Eco USS protocol time-out - Check the serial interface
- Check the settings of the bus master and P091 - P093
- Check whether the time-out interval is too short (P093)
Micromaster F010 Micromaster Eco Initialistion fault - Check the entire parameter set. Set P009 to '0000' before power down.
Micromaster F011 Micromaster Eco Internal interface fault - Switch off power and switch on again
Micromaster F012 Micromaster Eco External Trip - Source of trip is digital input (configured as an external trip input) going low - check the
external source
Micromaster F013 Micromaster Eco Programme fault - Switch off power and switch on again
Micromaster F016 Micromaster Eco Flying Start Instability - Disable flying start
- Ensure that P080 to P085 correspond to the name plate motor details.
- Adjust P386. Note that flying restart will not operate correctly with multi-motors.

Micromaster F018 Micromaster Eco Auto-restart after fault Automatic re-start after fault (P018) is pending.

WARNING: Inverter may start at any time.

Micromaster F074 Micromaster Eco Motor overtemperature by I2t calculation - Trip occurs only if P074 = 4, 5, 6 or 7. Check that the motor current does not exceed the
value set in P083 and P086
Micromaster F106 Micromaster Eco Parameter fault P006 Parameterise fixed frequency(ies) on the digital inputs.
Micromaster F112 Micromaster Eco Parameter fault P012 / P013 Set parameter P012 < P013
Micromaster F151 Micromaster Eco Digital input parameter fault Change the settings of digital inputs P051 to P055 and P356
Micromaster F188 Micromaster Eco Automatic calibration failure Motor not connected to inverter - connect motor.

If the fault persists, set P088 = 0 and then enter the measured stator resistance of the
motor into P089 manually.

Micromaster F212 Micromaster Eco Parameter fault P211 / P212 Set parameter P211 < P212
Micromaster F231 Micromaster Eco Output current measurement imbalance Check motor cable and motor for short - circuits and earth faults.
Mk5 0xEB33 (or 33) Siemens Sinamics 120 Wrong Converter Status Word Increase “Timeout + Holding Torque Time”

Converter Status = “running“, while Elektronikon
expects it has ‘stopped’

During Ramdown we need to give the converter
more time to stop.

Mk5 Bit2 = 0 (Ex: Status 0xFB31 Micromaster 440 - Wrong Converter Status Word Run Enable is not closed Check if the Run Enable contact on the converter is closed. Also check if the Elektronikon
0xFB61 or 1) closes this contact. (K09)
- Bit “Running” does not become ‘1’ after sending a
Ready command.

Mk5 0xFA71 (or 71) Micromaster 440 Converter Start-up procedure is not updated. Bit0 = 1 (Ready to switch on) & Bit6=1(Switch on disabled. Ex: Status 0xFA71 Use a higher software version then: 1900525020 or 1900525023.
Use a higher database version then: 1900521100_08.ds5
Mk5 0xFA71 (or F7) Micromaster 440 Inverter overload / motor current limit The converter stops due to inverter overload and turns on the switch on inhibit bit. Check the limitations of the current protections.
- Check for the status of the drive - check for overload of drive, motor health, etc
- The warning bit can be turned off again by the time the Elektronikon decides to do a
shutdown handling. So 16#F2F1 i

Mk5 0x1845 (or 45 ) VACON CX Wrong Converter Status Word Service Switch on Wrong position Service Switch = 0 , ie should be set to OFF
Mk5 Status 0x65 (or 65 ) VACON CX The converter will not start as long as his Run Run Enable is open Check if the Run Enable contact on the converter is closed. Also check if the Elektronikon
Enable is open (this status means that the closes this contact (K09).
converter is still in Stop).
Mk5 Status 0x834) VACON CX The converter gives an alarm and because of this Alarm is active Check the converter display for the active alarm.
the Ready Bit becomes ‘0’. Since the Ready Bit is 0
the Elektronikon cannot start the compressor.

Mk5 Bit0 = 0 KEB The converter will not start as long as his Run Run Enable is open Check if the Run Enable contact on the converter is closed. Also check if the Elektronikon
Enable is open (this status means that the closes this contact (K09).
converter is still in ‘Stop’).
Mk5 Bit1 = 1 KEB Drive has tripped. Converter fault Check the converter display for active fault.
Mk5 Bit1 = 0 Control Techniques The converter will not start as long as his Run Run Enable is open Check if the Run Enable contact on the converter is closed. Also check if the Elektronikon
Commander SK Enable is open (this status means that the closes this contact (K09).
converter is still in ‘Stop’)
Mk5 Bit0 = 0 Control Techniques Drive has tripped. Converter fault Check the converter display for the active fault.
Commander SK
Mk5 Bit2 = 0 Yaskawa The converter will not start as long as his Run Run Enable is open Check if the Run Enable contact on the converter is closed. Also check if the Elektronikon
Enable is open (this status means that the closes this contact (K09).
converter is still in ‘Stop’).
Mk5 Bit3 = 1 Yaskawa Drive has tripped. Converter fault Check the converter display for the active fault.
Mk5 50 (or Ex: Status 0x0a50) Schneider Altivar 61/71 Converter is in state “switch on inhibited” while the Converter is in state “switch on inhibited” Check the connections of the Run Enable contact between the Elektronikon Controller
Mk5 expects otherwise. (K09) and the Converter.
Mk5 Ex: Status 0x50 bit 9 = 0 0x50 = 0x0 0 50 Meaning bit 9 = 0. Converter is in state “switch on inhibited” Verify in drive menu 1.6 if Ref.1 Channel (Fr1 on the integrated 7-segment display) is set
The drive is not in remote control. to Modbus (Mdb).
Mk5 Timeout All VSDs No Communication between VSD and Elektronikon - RS485 Port faulty - Check the cable, and connectors for loose connections
- RS232 (old GA90VSD with Simovert P Converter), when upgrade, the
RS232/RS485 converter faulty - Check and confirm that the Power Supply is OK. The power supply board provides the
- Power Supply board of VSD is faulty. +/- 5V for the RS485 port also, if this is faulty, then there will be no communication.
Please note that this fau
- When upgrading from Mk III to Mk IV / V, the baud rate and address are not
correct.

- When rep

Mk5 Status All VSDs Actual converter status and expected converter Wrong converter status - Power DOWN and give it a few minutes rest, power Up again.
0xXXXX status in Elektronikon do not match.
- New download of Elektronikon and / or converter might be required
Mk5 Fault xxxx All VSDs Converter fault number or fault indicator is Converter fault Check the datasheets of the converter for the meaning of fault number xxxx.
communicated to Elektronikon.
Mk5 Format Function Siemens Sinamics The Elektronikon might get confused due to Synchronisation errors or wrong function replies Check the line termination
improper voltage levels and reflections on
communication bus.
Mk5 Format Chk Error All VSDs Message checksum is not correct. Wrong checksum Consult Atlas Copco
Mk5 Format Frame Error All VSDs Message frame is not correct. Frame Errors - See also timeout/wrong Baudrate.
- Consult Atlas Copco
Mk5 40 (or Ex: Status 0xE940) Siemens Sinamics 120  Service Switch = 1 Service Switch = 0
Wrong Converter Status Word

Switch On Inhibit is active

Mk5 Status 0x0 Siemens Sinamics 120  PKW length parameter is not 3 Parameter P2013 must be 3
Wrong Converter Status Word

The Elektronikon reads out the wrong bytes and
interprets them as the status word.

Mk5 60 (or Ex: Status 0xEA60) Siemens Sinamics 120 Wrong Converter Status Word Run Enable is not closed Check if the Run Enable contact on the converter is closed. Also check if the Elektronikon
 closes this contact.
Switch On Inhibit is active during start up, drive is (K09)
Not Ready

Mk5 34 (or Ex: Status 0xFA34) Siemens Sinamics 120  On extremely rare occasions, the elektronikon and / or converter got corrupted, due to
Micromaster 440 Wrong Converter Status Word whatever reasons, this incorrect feedback may happens, so WRONG STATUS word is
 shown.
Converter Status = “running“, while Elektronikon
expects it has ‘stopped’ - Remedy: Please reprogram both the Elektronikon and the converter.

Mk5 0 rpm stored in menu “Saved Siemens Sinamics 120 External Fault When the Sinamics120 goes into external fault, it sends 0rpm to the Elektronikon - Check the drive for other messages, normally external faults are programmed to
Data” after a shutdown although the motor is still running. monitor conditions around the drive, eg, status of fanmotor, etc
during running
Mk5 0XFA31 (FA31) Mk 5 and VSD such as Input in wrong position, service switch not correct, fa31 is HEXADECIMAL value for the status word. Converting FA31(hex) gives Check service switch, K0something relay (please check with your service diagram for
MM440 K05 (or K09, etc) faulty 1111101000110001(binary) = STATUS WORD ! 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.
Status word of the MM440 :
You can see the drive status says that "Drive ready to run" = 0 = NO --> Run enable
is not coming in at start or

Mk5 NO VALID Pressure Control Mk 5 No pressure sensor for compressor to regulate Faulty pressure sensor that is used for pressure regulation Replaced sensor. Check wiring

Mk5 ErrorCode0x1 ZH355(+) - 900 LOS_NodeGuardCheck Mk5 CAN1 connector got loose after power on Tighten this connector
Mk5 ErrorCode0x1 ZH355(+) - 900 LOS_NodeGuardCheck KEB-Drive for IGV CAN connector got loose after power on Tighten this connector
Mk5 ErrorCode0x1 ZH355(+) - 900 LOS_NodeGuardCheck KEB-Drive for BOV CAN connector got loose after power on Tighten this connector
Mk5 ErrorCode0x1 ZH355(+) - 900 LOS_NodeGuardCheck KEB drive has no mains power, only 24V Investigate mains power problem
Mk5 ErrorCode0x1 ZH355(+) - 900 LOS_NodeGuardCheck KEB bus terminator resistances on one or more intermediate nodes are mounted Remove the terminator resistances
Terminator resistances must be mounted on the end nodes of the bus, not on the
intermediate node(s) NOTE: this error appears for the end node, not the intermediate
node!

Mk5 ErrorCode0x4 ZH355(+) - 900 LOS_CANstartupTimeOut An unknown CAN port was configured on the KEB driver Configure the correct CAN port (see TBD)
CAN port = 3 must be configured for BOV,
CAN port = 4 must be configured for IGV
Mk5 ErrorCode0x4 ZH355(+) - 900 LOS_CANstartupTimeOut Mk5 CAN1 connector fitted to Mk5 CAN2 slot Fit these connectors correctly
Mk5 ErrorCode0x4 ZH355(+) - 900 LOS_CANstartupTimeOut Mk5 CAN1 connector got loose before power on Tighten this connector
Mk5 ErrorCode0x4 ZH355(+) - 900 LOS_CANstartupTimeOut KEB-Drive for IGV CAN connector got loose before power on Tighten this connector
Mk5 ErrorCode0x4 ZH355(+) - 900 LOS_CANstartupTimeOut KEB-Drive for BOV CAN connector got loose before power on Tighten this connector
IGV shows external fault (drive converter error, error code 0x1f),
KEB display shown E.EF
Mk5 ErrorCode0x4 ZH355(+) - 900 LOS_CANstartupTimeOut KEB bus terminator resistances on one or more intermediate nodes are mounted remove the terminator resistances
Terminator resistances must be mounted on the end nodes of the bus, not on the
intermediate node(s)
NOTE: this error appears for the end node, not the intermediate node!

Mk5 ErrorCode0x4 ZH355(+) - 900 LOS_CANstartupTimeOut CAN_H and CAN_L are exchange during CAN cable connector manufacturing Apply correct pinout to the CAN connector
Mk5 ErrorCode0x4 ZH355(+) - 900 LOS_CANstartupTimeOut CAN_L signal is disconnected in the connector Apply correct pinout to the CAN connector
Mk5 ErrorCode0x1 ZH355(+) - 900 IllegalResponse_SDOUnknown CAN_H and CAN_L are exchange during CAN cable connector manufacturing Apply correct pinout to the CAN connector
Mk5 ErrorCode0x2 ZH355(+) - 900 IllegalResponse_ActuatorID KEB-drive for IGV and BOV have been exchanged Mount the KEB-drives correctly
Mk5 ErrorCode0x0 ZH355(+) - 900 : no operation, control release (terminal ST) is not ErrorCode"0xXX: any other error code Apply the bridge for switching ST
switched
Mk5 ErrorCode"0xXX ZH355(+) - 900 any other error code consult annex 1 consult annex 1
Mk5 ErrorCode0x1 ZH355(+) - 900 TimeOut_Homing Mechanical blocking on the load path, KEB delivers insufficient HOMING torque to Investigate and correct the problem along the mechanical load path
overcome the blockage
Mk5 ErrorCode0x1 ZH355(+) - 900 TimeOut_Homing The hard stop is not present, the KEB-drive keeps searching for this hard stop untill correct the problem with the hard stop
the homing timeout has elapsed
Mk5 ErrorCode0x2 ZH355(+) - 900 TImeOut_Resetting The Mk5 reset function was tried before the resolving the KEB related error Power off and on the controller (or the entire compressor), note down the KEB-drive
error prior to attempting reset
Mk5 ErrorCode0x2 ZH355(+) - 900 TImeOut_Resetting KEB bus terminator resistances on end nodes are not mounted Mount the terminating resistances
Mk5 ErrorCode0x2 ZH355(+) - 900 TImeOut_Resetting KEB bus terminator resistances on one more intermediate nodes are mounted Remove the terminating resistances

Mk5 Position Watchdog Trips ZH355(+) - 900 Control release (terminal ST) is not switched Apply the bridge for switching ST
Mk5 Position Watchdog Trips ZH355(+) - 900 Mechanical blocking on the load path, KEB delivers insufficient torque to overcome Investigate and correct the problem along the mechanical load path
the blockage
Mk5 Position Watchdog Trips ZH355(+) - 900 “Nervous” behavior of valves. The valves need to acquire a new position too fast Modify parameters on MK5: Delay at signal: 20 s Position Tolerance Regulation Actual
before reporting arriving to the previous one =350 x 0.01% = 3.5%
Mk5 MK5 returns to inoperative ZH355(+) - 900 KEB was configured with a wrong baudrate Download the KEB with a correct set of parameters, reboot Mk5 by pressing the left and
during configuration right key simultaneously in inoperative mode (works only for ZH)

Mk5 Mk5 Reboots ZH355(+) - 900 A short circuit is present in one of the CAN connectors Remove the short circuit, apply the correct pin-out, make sure the CAN is still operational

Mk5 No CAN communciation ZH355(+) - 900 The connector of the CAN bus for the KEB drives is not fitted to the Mk5 CAN1 Correctly fit this connector
connector
Mk5 No CAN communciation ZH355(+) - 900 Mk5 was downloaded for a 4 to 20mA actuator Download the correct Mk5 parameter set for the compressor
Mk5 No CAN communciation ZH355(+) - 900 Mistake in diagnosis, CAN communication is not failing Lookup error type and code of the converter, re-asses the problem based on this
information
MM440 F0001 MicroMaster / MM4 - 420, Overcurrent 440: - Motor power (P0307) does not correspond to the inverter power (r0206) 440: Check: - Motor power (P0307) must correspond to inverter power (r0206) - most
440 - Motor leads are too long (unlikely in Atlas Copco application) likely programming fault after modification
- Motor leads short circuit - Check short circuits of motor / cable
- Earth Faults - Check motor parameters -> should match motor in use
- Value of stator resistance (P035

MM440 F0002 MicroMaster / MM4 - 420, OverVoltage 440: - DC-Link controller disabled (P1240 = 0) 440: - Check supply voltage (P0210) must lie within limits indicated on rating plate
440 - DC-Link voltage (r0026) exceeds trip level (P2172) - DC-Link voltage controller must be enabled and correctly parametised
- Too high main supply, or if motor is in regenerative mode. (Regenerative mode - Ramp-down time (P1121) must match inertia of load
can be caused by fast ramp downs or if the motor is driven from an active l - Required braking power must lie within speci

MM440 F0003 MicroMaster / MM4 - 420, UnderVoltage 440: - Main supply failed 440: Check - Supply voltage (P0210) must lie within indicated on rating plate
440 - Incorrect parameter settings - Supply must not be susceptible to temporary failures or voltage reductions
- DC Link low voltage - Enable kinetic buffering (P1240 = 2)
- Supply interruption:
If the supply is disconnected while t

MM440 F0004 MicroMaster / MM4 - 420, Inverter Over Temperature 440: - Ventilation inadequate 440: Check that fan must turn when inverter is running
440 - Ambient temperature is too high - Pulse frequency (P1800) must be set to default value
- Ambient temperature could be higher than specified for the inverter
- The parameter P1755, which is the start frequency of minimum 0.1 Hz, however, - for MM440 FX and GX:
it does a "walkabout" and gives erratic F004. In most cases, P1755 = 7.3 ==> this => Fault value = 1 Rectifier overtemperature
should be modified to 0.2 (H

MM440 F0005 MicroMaster / MM4 - 420, Inverter I2t 440: Inverter overload 440: - Check Load cycle must lie within specified limits
440 - Duty cycle too demanding - Motor power must match inverter power (r0206)
- Motor power (P0307) exceeds inverter power capability (r0206)
- This fault is caused when the converter calculates that it is overloaded. This will occur
when the converter is operated above its continuous rated

MM440 F0011 MicroMaster / MM4 - 420, Motor over Temperature Motor overloaded, defective sensor - Check nominal overtemperatures (P0628-P0628) must be correct
440 - 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 identi

MM440 F0012 MicroMaster / MM4 - 420, Inverter temp.signal lost Wire breakage of inverter temperature (heatsink) sensor If a temperature sensor is fitted to the motor, and connected to the inverter and
440 monitoring activated (P0601=1 or 2), then an F0015 will be indicated if the connection or
sensor is broken giving a short or open circuit.
Check the wiring to the sensor, an

MM440 F0015 MicroMaster / MM4 - 420, Motor temperature signal lost Open or short circuit of motor temperature sensor. If the signal loss is detected,
440 temperature monitoring switches over to monitoring with the motor thermal
model.
MM440 F0020 MicroMaster / MM4 - 420, Mains Phase Missing Fault occurs if one of the three input phass are missed while the pulses are Check the input wiring of the mains phases
440 enabled and drive is loaded A Report from the field:

Possibly due to burn out or badly crimped cable as reported by colleagues in Found that the compressor didn't have a "normal" noise , not mechanical noise but
France, Germany and Switzerland. strange noise.

One of our technican went on plant and found the problem. On this unit, there is cables

MM440 F0021 MicroMaster / MM4 - 420, Earth Fault Fault occurs if the sum of the phase currents is higher than 5% of the nominal
440 inverter current .

This fault only occurs on inverters that have 3 current sensors (Fram sizes D to F &
FX, GX)
MM440 F0022 MicroMaster / MM4 - 420, Powerstack Fault Hardware fault (r0947 = 22 and r0494 = 1) caused by the following events: - Check I/O board. It has to be firmly inserted.
440 1) DC-Link overcurrent = short circuit of IGBT - Check the fault history and values as these will lead to the sympton of the cause.
2) Short circuit of chopper - Check the PX modules, maybe the IGBT / drivers gone, or the TDB and thyristors, or
3) Earth Fault may be both. Please use a multimete
4) I/O board is not properly inserted
- UCE failure was detected, when r0947 = 22 and faul

MM440 F0023 MicroMaster / MM4 - 420, Output fault One motor phase is disconnected Check motor
440
MM440 F0030 MicroMaster / MM4 - 420, Fan has failed Fan malfunction Replaced fan
440
MM440 F0035 MicroMaster / MM4 - 420, Auto Restart after n Auto restart attempts exceed value of P1211
440
MM440 F0041 MicroMaster / MM4 - 420, Motor Data Identification Failure Motor Data ID failed: Fault = 0 Check motor is connected to inverter
440 Fault Value
= 0: Load missing Fault = 1-40: Check if motor data in P0304 to P0311 are correct
= 1: Current limit level reached during identification
= 2: Identified stator Resistance less than 0.1% or great than 100% Check what type of motor wiring is required (star, delta)
= 3: """" rotor ""
= 4: Identified stator reactance less than 50% and greater t

MM440 F0042 MicroMaster / MM4 - 420, Speed Control Optimisation Failure Speed control optimisation (P1960) failed
440 - Fault Value = 0: Time out waiting for stable speed
= 1: Inconsistent Readings
MM440 F0051 MicroMaster / MM4 - 420, Parameter EEPROM Fault Read or write while saving non-volatile parameter - Factory reset and new parameterisation
440 - Consult Atlas Copco
MM440 F0052 MicroMaster / MM4 - 420, Power Stack Fault Read failure for power stack information or invalid data Hardware defect
440
MM440 F0053 MicroMaster / MM4 - 420, IOP EEPROM Fault Read failure for IP EEPROM info or invalid data - Check data
440 - Change I/O
MM440 F0054 MicroMaster / MM4 - 420, Wrong IO board - Wrong IO board is connected Check Data
440 - No ID detected on IO Board, no data
Change IO board
MM440 F0060 MicroMaster / MM4 - 420, Asic Timeout Intenral Communications failure Change inverter, if all else fail
440
MM440 F0070 MicroMaster / MM4 - 420, CB Setpoint Fault No Setpoint values from CB (communications board) during telegram off time Check CB and communication partner
440
MM440 F0071 MicroMaster / MM4 - 420, USS (BOP-Link) setpoint fault No setpoint values from USS during telegram off time Check USS master
440
MM440 F0072 MicroMaster / MM4 - 420, USS (COMM link) setpoint fault No setpoint values from USS during telegram off time Check USS master
440
MM440 F0080 MicroMaster / MM4 - 420, ADC lost input signal Broken wire
440
Signal out of limits
MM440 F0085 MicroMaster / MM4 - 420, External Fault External fault triggered via for example terminal input Disable for example, the terminal for fault trigger
440
MM440 F0090 MicroMaster / MM4 - 420, Encoder feedback loss Signal from Encoder lost - Check encoder fitted. If encoder not fitted, set P0400 = 0 and select SLVC mode
440 (*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

MM440 F0101 MicroMaster / MM4 - 420, Stack Overflow Software error, or processor failure Run self test routines
440
MM440 F0221 MicroMaster / MM4 - 420, PID Feedback below min. value PID Feedback below min. value P2268 - Change value of P2268
440 - Adjust feedback gain
MM440 F0222 MicroMaster / MM4 - 420, PID Feedback above max.value PID Feedback above max. value P2267 - Change value of P2267
440 - Adjust feedback gain
MM440 F0450 MicroMaster / MM4 - 420, BIST Tests Failure Fault value: Hardware problem, contact Atlas Copco.
440 = 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

MM440 F0452 MicroMaster / MM4 - 420, Belt Failure Detected Load conditions on motor indicate belt failure or mechanical fault Check - No breakage, seizure or obstruction of drive train
440 2. If using an external speed sensor, check for correct function. Check parameters
==> P2192 (Delay time for permitted deviation)
3.

MM440 A0501 MicroMaster / MM4 - 420, Current Limit - Motor power (P0307) does not correspond to the inverter power (P0206) 440: Check: - Motor power (P0307) must correspond to inverter power (r0206) - most
440 - Motor leads too long likely programming fault after modification
- Earth fault - Check short circuits of motor / cable
- Check motor parameters -> should match motor in use
- Value of stator resistance (P035

MM440 A0502 MicroMaster / MM4 - 420, OverVoltage Limit Overvoltage limit is reached 440: - Check supply voltage (P0210) must lie within limits indicated on rating plate
440 This warning can occur during ramp down, if the dc-link controller is disabled - DC-Link voltage controller must be enabled and correctly parametised
(P1240 = 0) - Ramp-down time (P1121) must match inertia of load
- Required braking power must lie within speci

MM440 A0503 MicroMaster / MM4 - 420, UnderVoltage Limit Main supply failed 440: Check - Supply voltage (P0210) must lie within indicated on rating plate
440 Main supply (P0210) must lie within limits on rating plate - Supply must not be susceptible to temporary failures or voltage reductions
- Enable kinetic buffering (P1240 = 2)
MM440 A0504 MicroMaster / MM4 - 420, Inverter Overtemperature Warning level of heat-sink temp. (P0614) is exceeded, resulting in pulse reduction Check that fan must turn when inverter is running
440 and/or output frequency reduction (depending on parameterisation in P0610) - Pulse frequency (P1800) must be set to default value
- Ambient temperature could be higher than specified for the inverter
MM440 A0505 MicroMaster / MM4 - 420, Inverter I2t Warning level (P0294) exceeded, output frequency and/or pulse frequency will be Load duty cycle must be within limits
440 reduced if parameterised (P0290) - Motor power (P0307) must match inverter power (r0206)
MM440 A0511 MicroMaster / MM4 - 420, Motor Overtemperature Motor overloaded warning Check nominal overtemperatures (P0628-P0628) must be correct
440 - 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

MM440 A0522 MicroMaster / MM4 - 420, I2C read out timeout The cyclic access to the UCE Values and powerstack temperatures via I2C bus
440
MM440 A0523 MicroMaster / MM4 - 420, Output fault One motor phase missing
440
MM440 A0535 MicroMaster / MM4 - 420, Braking Resistor Hot 1. Increase duty cycle P1237
440 2. Increase ramp down time P1121
MM440 A0541 MicroMaster / MM4 - 420, Motor Data Identification Active Motor Data ID run selected or running
440
MM440 A0542 MicroMaster / MM4 - 420, Speed Control Optimisation Active Speed Control Optimisation (P1960) is selected or running
440
MM440 A0590 MicroMaster / MM4 - 420, Encoder Feedback Loss Warning Signal from Encoder lost and Inverter has switched to sensorless vector control Stop inverter and check:
440 - Whether Encoder is fitted, if not set P0400 = 0 and select SLVC mode (P1300 = 20 or 22)
- If fitted, check correct encoder selected (check encoder set-up in P0400)
- Check connections between encoder and inverter
- Check encoder

MM440 A0600 MicroMaster / MM4 - 420, RTOS Overrun Warning

440
MM440 A0700 MicroMaster / MM4 - 420, CB Warning 1
440
MM440 A0701 MicroMaster / MM4 - 420, CB Warning 2
440
MM440 A0702 MicroMaster / MM4 - 420, CB Warning 3
440
MM440 A0703 MicroMaster / MM4 - 420, CB Warning 4
440
MM440 A0704 MicroMaster / MM4 - 420, CB Warning 5
440
MM440 A0705 MicroMaster / MM4 - 420, CB Warning 6
440
MM440 A0706 MicroMaster / MM4 - 420, CB Warning 7
440
MM440 A0707 MicroMaster / MM4 - 420, CB Warning 8
440
MM440 A0708 MicroMaster / MM4 - 420, CB Warning 9
440
MM440 A0709 MicroMaster / MM4 - 420, CB Warning 10
440
MM440 A0710 MicroMaster / MM4 - 420, CB Communication Error CB is lost
440
MM440 A0711 MicroMaster / MM4 - 420, CB Configurator error
440
MM440 A0910 MicroMaster / MM4 - 420, Vdc-max controller de-activated Vdc max controller has been de-activated, since controller is not capable of Check that input voltage (P0210) must lie within range
440 keeping DC-Link voltage (r0026) within limits (P2172) - Load must be matched.
-> Occurs if main supply voltage (P0210) is permamently too high
-> Occurs if motor is driven by an active load, causing mot

MM440 A0911 MicroMaster / MM4 - 420, Vdc-max controller Active Vdc max controller is active; rampl down times will be increased automatically to
440 keep DC-Link voltage (r0026) within limits (P2172)
MM440 A0912 MicroMaster / MM4 - 420, Vdc-min controller Active Vdc min controller will be activated if DC-Link voltage (r0026) falls below minimum
440 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

MM440 A0920 MicroMaster / MM4 - 420, ADC Parameters not set properly ADC parameters should not be set to identical values, since this would produce
440 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

MM440 A0921 MicroMaster / MM4 - 420, DAC parameters not set properly DAC parameters should not be set to identical values, since this would produce
440 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

MM440 A0922 MicroMaster / MM4 - 420, No Load applied to inverter No Load is applied to inverter
440 -
MM440 A0923 MicroMaster / MM4 - 420, Both JOG Left and JOG Right are requested Both left and right are requested ==> freezes the RFG output frequency at its
440 current value
MM440 A0936 MicroMaster / MM4 - 420, PID Autotuning Active PID Autotuning (P2350) selected or running
440
MM440 A0952 MicroMaster / MM4 - 420, Belt Failure Warning Check - No breakage, seizure or obstruction of drive train
440 2. If using an external speed sensor, check for correct function. Check parameters
==> P2192 (Delay time for permitted deviation)
3.
MM440 F0453 MicroMaster / MM4 - 420, Motor Stalled - up / down ramp too steep (excessive gradient) - Check the motor connections
440 - inverter connected to an already spinning without using the flying restart - Increase the ramp-up time P1120 or the ramp down time P1121
function - activate the flying restart function P1200
- motor incorrectly connected - use a (larger) motor
- motor to small - Increase the voltage boost (P1611) for sensorless closed loop vector control
- Voltage boost P1611 for sensorless vector control too low - use closed loo
- Running with

NEOS 0x1111 (Hex) NEOS Undervoltage Main Power supply voltage too low or missing links in the control panel. • Check if main supply voltage is within specs. Check Main fuses.

• Check for loose connectors at the control unit of the inverter and Elektronikon.

• Check for tripped fuses at the secondary of the transformer T1 in the electrical panel

NEOS 4369 (Dec) NEOS Undervoltage Main Power supply voltage too low or missing links in the control panel. • Check if main supply voltage is within specs. Check Main fuses.

• Check for loose connectors at the control unit of the inverter and Elektronikon.
• Check for tripped fuses at the secondary of the transformer T1 in the electrical panel

NEOS 0x3221 (hex) NEOS Undervoltage Main Power supply voltage too low. • Check if main supply voltage is within specs.

• Check Main fuses.

* Sometimes, if VSD is in operation, and power is lost, this msg comes up. But usually
with DC link undervoltage, it is self reset

NEOS 12833 (dec) NEOS Undervoltage Main Power supply voltage too low. • Check if main supply voltage is within specs.
• Check Main fuses.
* Sometimes, if VSD is in operation, and power is lost, this msg comes up. But usually
with DC link undervoltage, it is self reset

NEOS 0x3223 (hex) NEOS Undervoltage Phase loss detected • Check if main supply voltage is within specs.
• Check Main fuses.
NEOS 12835 (Dec) NEOS Undervoltage Phase loss detected • Check if main supply voltage is within specs.
• Check Main fuses.
NEOS 0x3224 (hex) NEOS DC Link Overvoltage Maximum allowable voltage of the DC-link exceeded; Threshold is lowered in case • Let drive cool off .
of higher temperature • Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle .
• Ensure proper flow of cooling air in compressor room.
• Check if supply voltage is within specs.
* Check for earth fa

NEOS 12836 (dec) NEOS DC Link Overvoltage Maximum allowable voltage of the DC-link exceeded; Threshold is lowered in case • Let drive cool off .
of higher temperature • Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle .
• Ensure proper flow of cooling air in compressor room.
• Check if supply voltage is within specs.

* Check for earth fa

NEOS 0x3225 (Hex) NEOS Undervoltage Undervoltage detected • Check if main supply voltage is within specs.
• Check main fuses.
NEOS 12837 (dec) NEOS Undervoltage Undervoltage detected • Check if main supply voltage is within specs.
• Check main fuses.
NEOS 0x3226 (hex) NEOS Overvoltage Overvoltage or overtemperature detected in IGBT (U phase) • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.
• Check if supply voltage is within specs.

NEOS 12838 (dec) NEOS Overvoltage Overvoltage or overtemperature detected in IGBT (U phase) • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.
• Check if supply voltage is within specs.

NEOS 0x3227 (hex) NEOS Overvoltage Overvoltage or overtemperature detected in IGBT (V phase) • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.
• Check if supply voltage is within specs.

NEOS 12839 (dec) NEOS Overvoltage Overvoltage or overtemperature detected in IGBT (V phase) • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.
• Check if supply voltage is within specs.
NEOS 0x3228 (Hex) NEOS Overvoltage Overvoltage or overtemperature detected in IGBT (W phase) • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.
• Check if supply voltage is within specs.

NEOS 12840 (dec) NEOS Overvoltage Overvoltage or overtemperature detected in IGBT (W phase) • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.
• Check if supply voltage is within specs.

NEOS 0x4311 (hex) NEOS Drive overtemperature Overtemperature detected in an IGBT • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 17169 (dec) NEOS Drive overtemperature Overtemperature detected in an IGBT • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 0x4312 (Hex) NEOS Drive overtemperature Overtemperature detected in the heatsink • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 17170 (dec) NEOS Drive overtemperature Overtemperature detected in the heatsink • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 0x4314 (hex) NEOS Drive overtemperature Overtemperature detected in IGBT junction UH • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 17172 (dec) NEOS Drive overtemperature Overtemperature detected in IGBT junction UH • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 0x4315 (hex) NEOS Drive overtemperature Overtemperature detected in IGBT junction UL • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 17173 (dec) NEOS Drive overtemperature Overtemperature detected in IGBT junction UL • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 0x4316 (hex) NEOS Drive overtemperature Overtemperature detected in IGBT junction VH • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 17174 (dec) NEOS Drive overtemperature Overtemperature detected in IGBT junction VH • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 0x4317 (hex) NEOS Drive overtemperature Overtemperature detected in IGBT junction VL • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 17175 (dec) NEOS Drive overtemperature Overtemperature detected in IGBT junction VL • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 0x4318 (Hex) NEOS Drive overtemperature Overtemperature detected in IGBT junction WH • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 17176 (dec) NEOS Drive overtemperature Overtemperature detected in IGBT junction WH • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.
NEOS 0x4319 (Hex) NEOS Drive overtemperature Overtemperature detected in IGBT junction WL • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 17177 (dec) NEOS Drive overtemperature Overtemperature detected in IGBT junction WL • Let drive cool off.
• Check for excessive ambient temperature.
• Clean Heatsink with compressed air.
• Clean inlet filter cubicle.
• Ensure proper flow of cooling air in compressor room.

NEOS 0x5020 (hex) NEOS Emergency off (STO) Emergency stop circuit opened • Check emergency stop button
• Check for loose connectors at the control unit of the inverter.
• Check the temperature switch
NEOS 20512 (dec) NEOS Emergency off (STO) Emergency stop circuit opened • Check emergency stop button
• Check for loose connectors at the control unit of the inverter.
• Check the temperature switch
NEOS 0x5021 (hex) NEOS Emergency off (STO) Emergency stop circuit opened • Check emergency stop button
• Check for loose connectors at the control unit of the inverter.
• Check the temperature switch
NEOS 20513 (dec) NEOS Emergency off (STO) Emergency stop circuit opened • Check emergency stop button
• Check for loose connectors at the control unit of the inverter.
• Check the temperature switch
NEOS 0x5022 (hex) NEOS Emergency off (STO) - Emergency stop circuit opened • Check emergency stop button
- Hardware fault detected • Check for loose connectors at the control unit of the inverter.
• Check the temperature switch
NEOS 20514 (dec) NEOS Emergency off (STO) - Emergency stop circuit opened • Check emergency stop button
- Hardware fault detected • Check for loose connectors at the control unit of the inverter.
• Check the temperature switch
NEOS 0x5114 (Hex) NEOS Drive failure (hardware) Internal power supply tripped • Try to reset the error.
• If error returns, contact service.
NEOS 20756 (dec) NEOS Drive failure (hardware) Internal power supply tripped • Try to reset the error.
• If error returns, contact service.
NEOS 0x5115 (hex) NEOS Drive failure (hardware) Internal power supply tripped • Try to reset the error.
• If error returns, contact service.
NEOS 20757 (dec) NEOS Drive failure (hardware) Internal power supply tripped • Try to reset the error.
• If error returns, contact service.
NEOS 0x5401 (hex) NEOS Drive failure (hardware) General fault detected in power section • Try to reset the error.
• If error returns, contact service.
NEOS 21505 (dec) NEOS Drive failure (hardware) General fault detected in power section • Try to reset the error.
• If error returns, contact service.
NEOS 0x5402 (hex) NEOS Drive failure (hardware) General fault detected in power section • Try to reset the error.
• If error returns, contact service.
NEOS 21506 (dec) NEOS Drive failure (hardware) General fault detected in power section • Try to reset the error.
• If error returns, contact service.
NEOS 0x6101 (hex) NEOS Drive failure (hardware) - Eeprom read failed • Try to reset the error.
- Timeout communication • If error returns, contact service.
NEOS 24833 (dec) NEOS Drive failure (hardware) - Eeprom read failed • Try to reset the error.
- Timeout communication • If error returns, contact service.
NEOS 0x6102 (hex) NEOS Drive failure (hardware) - Failed temperature reading of power board • Try to reset the error.
- Timeout communication at initialization • If error returns, contact service.
NEOS 24834 (dec) NEOS Drive failure (hardware) - Failed temperature reading of power board • Try to reset the error.
- Timeout communication at initialization • If error returns, contact service.
NEOS 0x6103 (hex) NEOS Drive failure (hardware) General fault detected • Try to reset the error.
• If error returns, contact service.
NEOS 24835 (dec) NEOS Drive failure (hardware) General fault detected • Try to reset the error.
• If error returns, contact service.
NEOS 0x6104 (hex) NEOS Drive failure (hardware) Internal checksum error detected • Try to reset the error.
• If error returns, contact service.
NEOS 24836 (dec) NEOS Drive failure (hardware) Internal checksum error detected • Try to reset the error.
• If error returns, contact service.
NEOS 0x6105 (hex) NEOS Drive failure (hardware) Internal communication timeout • Try to reset the error.
• If error returns, contact service.
NEOS 24837 (dec) NEOS Drive failure (hardware) Internal communication timeout • Try to reset the error.
• If error returns, contact service.
NEOS 0x6106 (hex) NEOS Drive failure (hardware) Internal checksum error detected • Try to reset the error.
• If error returns, contact service.
NEOS 24838 (dec) NEOS Drive failure (hardware) Internal checksum error detected • Try to reset the error.
• If error returns, contact service.
NEOS 0x6107 (hex) NEOS Drive failure (hardware) Internal communication timeout • Try to reset the error.
• If error returns, contact service.
NEOS 24839 (dec) NEOS Drive failure (hardware) Internal communication timeout • Try to reset the error.
• If error returns, contact service.
NEOS 0x6108 (hex) NEOS Drive failure (hardware) Internal communication timeout • Try to reset the error.
• If error returns, contact service.
NEOS 24840 (dec) NEOS Drive failure (hardware) hardware) • Try to reset the error.
Internal communication timeout • If error returns, contact service.
NEOS 0x6109 (hex) NEOS Drive failure (hardware) Internal checksum error detected • Try to reset the error.
• If error returns, contact service.
NEOS 24841 (dec) NEOS Drive failure (hardware) Internal checksum error detected • Try to reset the error.
• If error returns, contact service.
NEOS 0x610A (hex) NEOS Drive failure (hardware) Internal communication overload • Try to reset the error.
• If error returns, contact service.
NEOS 24842 (dec) NEOS Drive failure (hardware) Internal communication overload • Try to reset the error.
• If error returns, contact service.
NEOS 0x610B (hex) NEOS Drive failure (hardware) Internal control overload • Try to reset the error.
• If error returns, contact service.
NEOS 24843 (dec) NEOS Drive failure (hardware) Internal control overload • Try to reset the error.
• If error returns, contact service.
NEOS 0x2312 (Hex) NEOS Motor overcurrent Overcurrent detected at motor side • Check if main supply voltage is within specs.

* Motor / element seized

NEOS 0x2314 (Hex) NEOS Motor overcurrent Overcurrent detected at motor side • Check if main supply voltage is within specs.

* Motor / element seized

NEOS 8978 (dec) NEOS Motor overcurrent Overcurrent detected at motor side • Check if main supply voltage is within specs.

* Motor / element seized

NEOS 8980(dec) NEOS Motor overcurrent Overcurrent detected at motor side. **** from GA55-90VSD ==>, one problem • Check if main supply voltage is within specs.
could be faulty sensor. But cannot change this sensor onsite, has to replace * Motor / element seized **** For GA55-90VSD ==> Failure can’t be resettable;
convertor. See ECB WUXI0155 (P IV)  Occasionally it happened during commissioning, which means running hours < 2 hours
 Converter SN information showed that its’ manufacturing date is from 32th week 2016
– 7th week 2017. ***** Please see ECB WUXI 0155 (P IV). A replacement convertor is
required. 90kw ==> 1900 5350 01; 75kw ==> 1900 5350 02; 55kw ==> 1900 5350 03.

NEOS 0x2315 (Hex) NEOS Motor overcurrent Short Circuit detected in U phase * Check output for shortcircuit
* Use Multimeter & diode checks
NEOS 0x2316 (Hex) NEOS Motor overcurrent Short Circuit detected in V phase * Check output for shortcircuit
* Use Multimeter & diode checks
NEOS 8981 (dec) NEOS Motor overcurrent Short Circuit detected in U phase * Check output for shortcircuit
* Use Multimeter & diode checks
NEOS 8982 (dec) NEOS Motor overcurrent Short Circuit detected in V phase * Check output for shortcircuit

* Use Multimeter & diode checks

NEOS 8983 (dec) NEOS Motor overcurrent Short Circuit detected in W phase * Check output for shortcircuit
* Use Multimeter & diode checks
NEOS 0x2317 (Hex) NEOS Motor overcurrent Short Circuit detected in W phase * Check output for shortcircuit

* Use Multimeter & diode checks

NEOS 0x3210 (hex) NEOS Overvoltage Overvoltage detected * Check supply voltage is within spec

* Check for correct input voltage settings

* Check for earth fault of motor. Usually this is the main cause of overvoltage.

NEOS 12816 (dec) NEOS Overvoltage Overvoltage detected * Check supply voltage is within spec
* Check for correct input voltage settings

* Check for earth fault of motor. Usually this is the main cause of overvoltage.

Sinamics G130 A01006 Sinamics / AIF VSD Firmware update DRIVE-CLiQ component The firmware of a DRIVE CLiQ component must be updated as there is no Firmware update using the commissioning software:
required suitable firmware or firmware version in the component for operation with The firmware version of all of tge components on the "version overview" page
the Control Unit. Alarm value (r2124, decimal) can be read in the Project Navigator under "Configuration" of the associated
drive unit and an appropriate firmware update can b

Sinamics G130 A01007 Sinamics / AIF VSD POWER ON DRIVE-CLiQ component required a Drive-CliQ component must be powered-up again (POWER ON) as, for Switch off the power supply of the specefied DRIVE-CLiQ component and Switch
example, the firmware was updated. Alarm value (r2124, decimal): on the power again.
Component number of the DRIVE-CLiQ component.

Sinamics G130 A01016 Sinamics / AIF VSD CompactFlash card changed On the CompactFlash card, at least one file in the directory For the CompactFlash card, restore the status when originally supplied from the
/SIEMENS/SINAMICS/ has been illegally changed with respect to that factory.
supplied from the factory. No changes are permitted in this directory. Note:
Alarm value (r2124, decimal): The file involved can be read out using parameter r9925. See also, r9926
0: Checksum of one file is
Sinamics G130 A01017 Component lists changed On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA or
or /ADDON/SINAMICS/DATA has been /ADDON/SINAMICS/DATA has been
illegally changed with respect to that supplied from the factory. No changes illegally changed with respect to that supplied from the factory. No changes are
are permitted in this directory. permitted in this directory.
Alarm value (r2124, interpret decimal): Alarm value (r2124, interpret decimal):
The problem is indicated in the first digit of the alarm value: The problem is indicated in the first digit of the alarm value:
1: File does not exist. 1: File does not exist.
2: Firmware version of the file does not match the software version. 2: Firmware version of the file does not match the software version.
3: The file checksum is incorrect. 3: The file checksum is incorrect.
The second digit of the alarm value indicates in which directory the file is The second digit of the alarm value indicates in which directory the file is
located: located:
0: Directory /SIEMENS/SINAMICS/DATA/ 0: Directory /SIEMENS/SINAMICS/DATA/
1: Directory /ADDON/SINAMICS/DATA/ 1: Directory /ADDON/SINAMICS/DATA/
The third digit of the alarm value indicates the file: The third digit of the alarm value indicates the file:
0: File MOTARM.ACX 0: File MOTARM.ACX
1: File MOTSRM.ACX 1: File MOTSRM.ACX
2: File MOTSLM.ACX 2: File MOTSLM.ACX
3: File ENCDATA.ACX 3: File ENCDATA.ACX
4: File FILTDATA.ACX 4: File FILTDATA.ACX
5: File BRKDATA.ACX 5: File BRKDATA.ACX

Sinamics G130 A01035 Sinamics / AIF VSD ACX: Run-up from backup files When the Control Unit ran-up no complete data set from the parameter If you saved the project in STARTER, download your project again and save using
save files was found. The last time that the parameterization was saved, it the function "Copy RAM to ROM" or with P0977 = 1. This means that all of the
was not completely carried-out. Instead, a backup data set or file is parameter files are again completely written into the CompactFlash card.
downloaded. Alarm value (r2124, hexadeci

Sinamics G130 A01045 Sinamics / AIF VSD CU CompactFlash: Configuration data invalid An invalid data type was detected when evaluating parameter files Restore the factory setting using (p0976 = 1) and re-load thje project into the
Psxxxyyy.ACX, Ptxxxyyy.ACX, Ptxxxyyy.ACX, Caxxxyyy.ACX or Ccxxxyyy.ACX, drive unit. Operation without any restrictions is then possible,
saved on the CompactFlash card.
After downloading the project, save the parameterisation in STARTER using the
Alarm value (r2124, hexadecimal) only for internal Siemens function "Copy RAM to ROM" or P
troubleshooting.

Sinamics G130 A01046 Sinamics / AIF VSD CU CompactFlash: Configuration data invalid An invalid data type was detected when evaluating parameter files Restore the factory setting using (p0976 = 1) and re-load thje project into the
Psxxxyyy.ACX, Ptxxxyyy.ACX, Ptxxxyyy.ACX, Caxxxyyy.ACX or Ccxxxyyy.ACX, drive unit. Operation without any restrictions is then possible,
saved on the CompactFlash card.
After downloading the project, save the parameterisation in STARTER using the
Alarm value (r2124, hexadecimal) only for internal Siemens function "Copy RAM to ROM" or P
troubleshooting.

Sinamics G130 A01047 Sinamics / AIF VSD ACX: Parameter Write Error When evaluating the parameters files Psxxxyyy.ACX, Ptxxxyyy.ACX, Restore the factory setting using (p0976 =1) and re-load the project into the
Caxxxyyy.ACX, or Ccxxxyyy.ACX, saved on the CompactFlash card, a drive unit. Operation without any restrictions is then possible.
parameter value was not able to be transferred into the Control Unit
memory. After downloading the project, save the parameterization in STARTER using the
Alarm value (r2124, hexadecimal) Only for intern function "Copy RAM to ROM" or wit

Sinamics G130 A01049 Sinamics / AIF VSD CU CompactFlash: It is not possible write into It is not possible to write into a write-protectice file (PSxxxxx.ACX). The Check whether the write-protected attribute has been set for the files on the
the file write request was interrupted. CompactFlash card under . . . /USER/SINAMICS/DATA/ . . . When required,
Alarm value (r2124, decimal): Drive object number remove write protection and save again, (eg. Set P0971 to 1)

Sinamics G130 A01052 Sinamics / AIF VSD CU: System overload calculates, for the A system overload was calculated on a complete active target topology. - Reduce the sampling time
complete target topologie Alarm value (r2124, decimal) - Only use one data set (CDS, DDS)
2: Computation time load too high - de-activate the function module
6: Cyclic computation time load too high - de-activate the drive object
- remove the drive object from the target topology

Note: After executing the appropriate counter-measure, a new calculation mus

Sinamics G130 A01053 Sinamics / AIF VSD CU: System overload measured A system overload was determined based on measured values. - Reduce the sampling time
Alarm value (r2124, decimal) - Only use one data set (CDS, DDS)
2: Computation time load too high - de-activate the function module
6: Cyclic computation time load too high - de-activate the drive object
See also: r9976 - remove the drive object from the target topology

Sinamics G130 A01054 Sinamics / AIF VSD Parameter save necessary

Sinamics G130 A01064 Sinamics / AIF VSD Parameter save necessary
Sinamics G130 A01065 Drive: Fault on non-active encoder One or several inactive encoders indicate an error. Remove the error for the inactive encoder.
Sinamics G130 A01090 Sinamics / AIF VSD Non-volatile data save cannot be activated. Non-volatile data save cannot be activated as this is not supported by the
CU
Sinamics G130 A01099 Tolerance window of time synchronization The time master exited the selected tolerance window for time Select the re-synchronization interval so that the synchronization deviation
exited synchronization. between the time master and drive system
See also: p3109 (RTC real time synchronization, tolerance window) lies within the tolerance window.
See also: r3108 (RTC last synchronization deviation)
Sinamics G130 A01100 Sinamics / AIF VSD CU: CompactFlash card withdrawn The CompactFlash card (non-volatile memory) was withdrawn in operation. - Power down the drive system
Notice: - re-insert the Compact Flash card that was withdrawn - this card must match
It is not permissable that the CompactFlas card is withdrawn or inserted the drive system.
under voltage. - power up the drive system again.

Sinamics G130 A01223 CU: Sampling time inconsistent When changing a sampling time (p0115[0], p0799 or p4099), inconsistency - check the DRIVE-CLiQ cables.
between the clock cycles has been identified. - set a valid sampling time.
Alarm value (r2124, interpret decimal): See also: p0115, p0799 (CU inputs/outputs, sampling time), p4099
1: Value, low minimum value.
2: Value, high maximum value.
3: Value not a multiple of 1.25 μs.
4: Value does not match clock-cycle synchronous PROFIBUS operation.
5: Value not a multiple of 125 μs.
6: Value not a multiple of 250 μs.
7: Value not a multiple of 375 μs.
8: Value not a multiple of 400 μs.
10: Special restriction of the drive object violated.
20: For a SERVO with a 62.5 μs sampling time, more than a maximum of
two SERVO-type drive objects were
detected on the DRIVE-CLiQ line (no other drive object is permitted on this
line).
21: Value can be a multiple of the current controller sampling time of a
servo or vector drive in the system (e.g. for
TB30, the values of all of the indices should be taken into account).
30: Value less than 31.25 μs.
31: Value less than 62.5 μs.
32: Value less than 125 μs.
40: Nodes have been identified on the DRIVE-CLiQ line whose highest
common denominator of the sampling times
is less than 125 μs. Further, none of the nodes has a sampling time of less
than 125 μs.
41: A chassis unit was identified on the DRIVE-CLiQ line as a node. Further,
the highest common denominator of
the sampling times of all of the nodes connected to the line is less than 250
μs.
42: An Active Line Module was identified on the DRIVE-CLiQ line as a node.
Further, the highest common denominator
of the sampling times of all of the nodes connected to the line is less than
125 μs.
43: A Voltage Sensing Module (VSM) was identified on the DRIVE-CLiQ line
as a node. Further, the highest common
denominator of the sampling times of all of the nodes connected to the line
Sinamics G130 A01224 CU: Pulse frequency inconsistent When changing the minimum pulse frequency (p0113) inconsistency Set a valid pulse frequency.
between the pulse frequencies was identified. See also: p0113 (Minimum pulse frequency, selection)
Alarm value (r2124, interpret decimal):
1: Value, low minimum value.
2: Value, high maximum value.
3: Resulting sampling time is not a multiple of 1.25 μs.
4: Value does not match clock-cycle synchronous PROFIBUS operation.
10: Special restriction of the drive object violated.
99: Inconsistency of cross drive objects detected.
116: Recommended clock cycle in r0116[0...1].

Sinamics G130 A01251 Sinamics / AIF VSD CU: CU-EEPROM incorrect read-write data Error when reading the read-write data of the EEPROM in the Control Unit. For alarm value r2124 < 256, the following applies:
Alarm value (r2124, decimal): Only for internal Siemens Troubleshooting - Delete (clear) the fault memory on the drive object on which the alarm
occurred (P0952 = 0)
- As an alternative, delete (clear) the fault memories of all drive objects (P2147 =
1)
- Replace the Control

Sinamics G130 A01256 Sinamics / AIF VSD CU: Opt. module EEPROM incorrect read-only Error when reading the read-only data of the EEPROM in the option - Carry out a POWER ON
data module. - Replace the Control Unit
Fault Value (r0949, decimal): Internal Siemens troubleshooting

Sinamics G130 A01304 Firmware version of DRIVE-CLiQ component is The memory card contains a more recent firmware version than the one in Update the firmware (p7828, p7829 and commissioning software).
not up-to-date the connected DRIVE-CLiQ component.
Alarm value (r2124, interpret decimal):
Component number of the DRIVE-CLiQ component involved.

Sinamics G130 A01306 Firmware of the DRIVE-CLiQ component being Firmware update is active for at least one DRIVE-CLiQ component. None necessary.
updated Alarm value (r2124, interpret decimal): This alarm automatically disappears after the firmware has been updated.
Component number of the DRIVE-CLiQ component.

Sinamics G130 A01314 Topology: Component must not be present For a component, "de-activate and not present" is set but this component - remove the corresponding component.
is still in the topology. - change the setting "de-activate and not present".
Alarm value (r2124, interpret hexadecimal): Note:
Byte 1: Component number Under "Topology --> Topology view" the commissioning software offers
Byte 2: Component class of the component improved diagnostics capability (e.g. setpoint/
Byte 3: Connection number actual value comparison).
Note: Component clas See also: p0105
Sinamics G130 A01315 Sinamics / AIF VSD Drive object not ready for operation For the active drive object involved, at least one activated component is The alarm automatically disappears again with the following actions.
missing. - De-activate the drive object involved (P0105 = 0)
Note: - De-activate the components involved (P0125 = 0, P0145 = 0, P0155 = 0, P0165
All other active and operational drive objects can be in the "RUN" state. = 0)
- Re-insert the components involved.

See also: P01

Sinamics G130 A01315 Drive object not ready for operation For the active drive object involved, at least one activated component is The alarm automatically disappears again with the following actions:
missing. - de-activate the drive object involved (p0105 = 0).
Note: - de-activate the components involved (p0125 = 0, p0145 = 0, p0155 = 0, p0165
All other active and operational drive objects can be in the "RUN" state. = 0).
- re-insert the components involved.
See also: p0

Sinamics G130 A01316 Sinamics / AIF VSD Drive object inactive and again ready for If, when inserting a component of the target topology, an inactive, non- The alarm automatically disappears again with the following actions:
operation operational drive object becomes operational again. The associated - activate the drive object involved (P0105 = 1)
parameter of the component is, in this case, set to "activate" (P0145, - Again, withdraw the components involved.
P0155, P0165).
Note: This is only a message, See also P 0105

Sinamics G130 A01316 Drive object inactive and again ready for If, when inserting a component of the target topology, an inactive, non- The alarm automatically disappears again with the following actions:
operation operational drive object becomes operational - activate the drive object involved (p0105 = 1).
again. The associated parameter of the component is, in this case, set to - again withdraw the components involved.
"activate" (p0125, p0145, p0155, p0165). See also: p0105 (Activate/de-activate drive object)
Note:
This is the only

Sinamics G130 A01317 (N) De-activated component again present If a component of the target topology for an active drive object is inserted The alarm automatically disappears again with the following actions:
and the associated parameter of the component - activate the components involved (p0125 = 1, p0145 = 1, p0155 = 1, p0165 = 1).
is set to "de-activate" (p0125, p0145, p0155, p0165). - again withdraw the components involved.
Note: See also: p0125 (Activate/de-activate power unit components), p
This is the only message that is displayed for a de-activated component.

Sinamics G130 A01318 BICO: De-activated interconnections present This alarm is output: Clear alarm:
If an inactive/non-operational drive object is again active/ready for Set p9496 to 1 or 2
operation or
and de-activate DO again
r9498[] or r9499[] are not empty
and
the connections listed in r9498[] and r9499 have actually been changed

Sinamics G130 A01319 Inserted component not initialized The inserted component has still not been initiated, as the pulses are Pulse inhibit
enabled.
Sinamics G130 A01320 Topology: Drive object number does not exist A drive object number is missing in p0978 Set p0009 to 1 and change p0978:
in configuration Alarm value (r2124, interpret decimal): Rules:
Index of p0101 under which the missing drive object number can be - p0978 must include all of the drive object numbers (p0101).
determined. - it is not permissible for a drive object number to be repeated.
- by entering a 0, the drive objects with PZD are separated from those without
PZD.
-o

Sinamics G130 A01321 Topology: Drive object number does not exist p0978 contains a drive object number that does not exist. Set p0009 to 1 and change p0978:
in configuration Alarm value (r2124, interpret decimal): Rules:
Index of p0978 under which the drive object number can be determined. - p0978 must include all of the drive object numbers (p0101).
- it is not permissible for a drive object number to be repeated.
- by entering a 0, the drive objects with PZD are separated from those without
PZD.
-o

Sinamics G130 A01322 Topology: Drive object number present twice A drive object number is present more than once in p0978. Set p0009 to 1 and change p0978:
in configuration Alarm value (r2124, interpret decimal): Rules:
Index of p0978 under which the involved drive object number is located. - p0978 must include all of the drive object numbers (p0101).
- it is not permissible for a drive object number to be repeated.
- by entering a 0, the drive objects with PZD are separated from those without
PZD.
-o

Sinamics G130 A01323 Topology: More than two partial lists created Partial lists are available more than twice in p0978. After the second 0, all Set p0009 to 1 and change p0978:
must be 0. Rules:
Alarm value (r2124, interpret decimal): - p0978 must include all of the drive object numbers (p0101).
Index of p0978 under which the illegal value is located. - it is not permissible for a drive object number to be repeated.
- by entering a 0, the drive objects with PZD are separated from those without
PZD.
-o
Sinamics G130 A01324 Topology: Dummy drive object number In p0978, dummy drive object numbers (255) are only permitted in the first Set p0009 to 1 and change p0978:
incorrectly created partial list. Rules:
Alarm value (r2124, interpret decimal): - p0978 must include all of the drive object numbers (p0101).
Index of p0978 under which the illegal value is located. - it is not permissible for a drive object number to be repeated.
- by entering a 0, the drive objects with PZD are separated from those without
PZD.
-o

Sinamics G130 A01330 Topology: Quick commissioning not possible Unable to carry out a quick commissioning. The existing actual topology - adapt the output topology to the permissible requirements.
does not fulfill the requirements. - carry out commissioning using the commissioning software.
Alarm value (r2124, interpret hexadecimal): - for motors with DRIVE-CLiQ, connect the power and DRIVE-CLiQ cable to the
ccccbbaa hex: cccc = preliminary component number, bb = supplementary same Motor Module (Single Motor
information, aa = fault cause Module: DRIVE-CLiQ at X202
aa =

Sinamics G130 A01331 Topology: At least one component not At least one component is not assigned to a drive object. This component is assigned to a drive object.
assigned to a drive object - when commissioning, a component was not able to be automatically Check the parameters for the data sets.
assigned to a drive object. Examples:
- the parameters for the data sets are not correctly set. - power unit (p0121).
Alarm value (r2124, interpret decimal): - motor (p0131, p0186).
Comp - encoder interface (p0140, p0141, p0187 ... p0189).
- encoder (p0140, p0142, p0187 ... p0189).
- Terminal Module

Sinamics G130 A01361 Topology: Actual topology contains SINUMERIK The detected actual topology contains SINUMERIK and SIMOTION Re fault cause = 1:
and SIMOTION components components. Replace all NX10 or NX15 by a CX32.
The drive system is no longer booted. In this state, the drive control Re fault cause = 2:
(closed-loop) cannot be enabled. Replace all CX32 by an NX10 or NX15.
Fault value (r0949, interpret hexadecimal):
ddccbbaa hex: cc = fault cause, bb

Sinamics G130 A01381 Topology: Comparison power unit shifted The topology comparison has detected a power unit in the actual topology Adapting the topologies:
that has been shifted with respect to the - undo the change to the actual topology by changing over the DRIVE-CLiQ
target topology. cables.
Alarm value (r2124, interpret hexadecimal): - commissioning software: Go online, upload the drive unit, adapt the topology
ddccbbaa hex: offline and download the modified
dd = connection number project.
cc = component number - automatically remove the
bb = component class

Sinamics G130 A01382 Topology: Comparison Sensor Module shifted The topology comparison has detected a Sensor Module in the actual Adapting the topologies:
topology that has been shifted with respect to - undo the change to the actual topology by changing over the DRIVE-CLiQ
the target topology. cables.
Alarm value (r2124, interpret hexadecimal): - commissioning software: Go online, upload the drive unit, adapt the topology
ddccbbaa hex: offline and download the modified
dd = connection number project.
cc = component number - automatically remove the
bb = component cl

Sinamics G130 A01383 Topology: Comparison Terminal Module The topology comparison has detected a Terminal Module in the actual Adapting the topologies:
shifted topology that has been shifted with respect - undo the change to the actual topology by changing over the DRIVE-CLiQ
Message value: Component number: %1, to the target topology. cables.
Component class: %2, Component (target): Alarm value (r2124, interpret hexadecimal): - commissioning software: Go online, upload the drive unit, adapt the topology
ddccbbaa hex: offline and download the modified
dd = connection number project.
cc = component number - automatically remove the
bb = component

Sinamics G130 A01384 Topology: Comparison DRIVE-CLiQ Hub The topology comparison has detected a DRIVE-CLiQ Hub Module in the Adapting the topologies:
Module shifted actual topology that has been shifted with - undo the change to the actual topology by changing over the DRIVE-CLiQ
respect to the target topology. cables.
Alarm value (r2124, interpret hexadecimal): - commissioning software: Go online, upload the drive unit, adapt the topology
ddccbbaa hex: offline and download the modified
dd = connection number project.
cc = component number - automatically remove the
bb = comp
Sinamics G130 A01385 Topology: Comparison, Cx32 Shifted The topology comparison has detected a controller extension 32 (CX32) in Adapting the topologies:
the actual topology that has been shifted - undo the change to the actual topology by changing over the DRIVE-CLiQ
with respect to the target topology. cables.
Alarm value (r2124, interpret hexadecimal): - commissioning software: Go online, upload the drive unit, adapt the topology
ddccbbaa hex: offline and download the modified
dd = connection number project.
cc = component number - automatically remove the topology error (p9904).
bb = component class Note:
aa = component number of the component shifted in the target topology Under "Topology --> Topology view" the commissioning software offers
Note: improved diagnostics capability (e.g. setpoint/
The connection in the actual topology where the shifted component was actual value comparison).
detected is described in dd, cc and bb.
Component class and connection number are described in F01375.
The drive system is no longer booted. In this state, the drive control
(closed-loop) cannot be enabled.

Sinamics G130 A01386 Topology: Comparison DRIVE-CLiQ component The topology comparison has detected a DRIVE-CLiQ component in the Adapting the topologies:
shifted actual topology that has been shifted with - undo the change to the actual topology by changing over the DRIVE-CLiQ
respect to the target topology. cables.
Alarm value (r2124, interpret hexadecimal): - commissioning software: Go online, upload the drive unit, adapt the topology
ddccbbaa hex: offline and download the modified
dd = connection number project.
cc = component number - automatically remove the
bb = compo

Sinamics G130 A01387 Topology: Comparison option slot component The topology comparison has detected a option slot component in the Adapting the topologies:
shifted actual topology that has been shifted with - undo the change to the actual topology by changing over the DRIVE-CLiQ
respect to the target topology. cables.
Alarm value (r2124, interpret hexadecimal): - commissioning software: Go online, upload the drive unit, adapt the topology
ddccbbaa hex: offline and download the modified
dd = connection number project.
cc = component number - automatically remove the
bb = comp

Sinamics G130 A01388 Topology: Comparison EnDat encoder shifted The topology comparison has detected an EnDat encoder in the actual Adapting the topologies:
topology that has been shifted with respect - undo the change to the actual topology by changing over the DRIVE-CLiQ
to the target topology. cables.
Alarm value (r2124, interpret hexadecimal): - commissioning software: Go online, upload the drive unit, adapt the topology
ddccbbaa hex: offline and download the modified
dd = connection number project.
cc = component number - automatically remove the
bb = component c

Sinamics G130 A01389 Topology: Comparison motor with DRIVE-CLiQ The topology comparison has detected a motor with DRIVE-CLiQ in the Adapting the topologies:
shifted actual topology that has been shifted with - undo the change to the actual topology by changing over the DRIVE-CLiQ
respect to the target topology. cables.
Alarm value (r2124, interpret hexadecimal): - commissioning software: Go online, upload the drive unit, adapt the topology
ddccbbaa hex: offline and download the modified
dd = connection number project.
cc = component number - automatically remove the
bb = comp

Sinamics G130 A01416 Topology: Comparison additional component The topology comparison has found a component in the actual topology Adapting the topologies:
in actual topology which is not specified in the target topology. - remove the additional component in the actual topology.
The alarm value includes the component number and connection number - download the target topology that matches the actual topology
of the component with which the additional (commissioning software).
component is connected. Note:
Alar Under "Topology --> Topology view" the commissioning software offers improve

Sinamics G130 A01420 Topology: Comparison a component is different The topology comparison has detected differences in the actual and target Adapting the topologies:
topologies in relation to one component. - check the component soft-wired connections against the hardware
There are differences in the electronic rating plate. configuration of the drive unit in the commissioning
Alarm value (r2124, interpret hexadecimal): software and correct differences.
ddccbbaa hex: aa = component number of the - parameterize the topology comparison of all components (p9906).
- parameter

Sinamics G130 A01421 Topology: Comparison different components The topology comparison has detected differences in the actual and target Check the component soft-wired connections against the hardware
topologies in relation to one component. configuration of the drive unit in the commissioning
The component class, the component type or the number of connections software and correct differences.
differ. Note:
Alarm value (r2124, interpret hexadecimal): Under "Topology --> Topology view" the commissioning software offers
ddccbbaa hex: aa = improved diagnostics capabili
Sinamics G130 A01425 Topology: Comparison serial number of a The topology comparison has detected differences in the actual and target Adapting the topologies:
component is different topologies in relation to one component. - change over the actual topology to match the target topology.
The serial number is different. - download the target topology that matches the actual topology
Alarm value (r2124, interpret hexadecimal): (commissioning software).
ddccbbaa hex: Re byte cc:
cc = number of differences cc = 1 --> can be acknowledged using p9904 or p9905.
bb = component class cc > 1 -->
aa

Sinamics G130 A01428 Topo: Comparison connection of a component The topology comparison has detected differences in the actual and target Adapting the topologies:
is different topologies in relation to one component. - change over the actual topology to match the target topology.
A component was connected to another connection. - download the target topology that matches the actual topology
The different connections of a component are described in the alarm value: (commissioning software).
Alarm value (r21 - automatically remove the topology error (p9904).
Note:
Under "Topology -->

Sinamics G130 A01429 Topology: Comparison connection is different A topology comparison has found differences between the actual and Adapting the topologies:
for more than one component target topology for several components. A - change over the actual topology to match the target topology.
component was connected to another connection. - download the target topology that matches the actual topology
The different connections of a component are described in the alarm value: (commissioning software).
Alarm value (r2124, inte Note:
In the software, a Double Motor Module behaves just like two separate

Sinamics G130 A01481 Topology: Comparison power unit missing in The topology comparison has detected a power unit in the target topology - delete the drive belonging to the power unit in the commissioning software
the actual topology that is not available in the actual topology. project and download the new configuration
Alarm value (r2124, interpret decimal): to the drive unit.
Component number of the additional target components. - check that the actual topology matches the target topology and if required,
change over.
- check DRIVE-CLiQ cables

Sinamics G130 A01482 Topology: Comparison Sensor Module missing The topology comparison has detected a Sensor Module in the target - re-configure the drive belonging to the Sensor Module in the commissioning
in the actual topology topology that is not available in the actual topology. software project (encoder configuration)
Alarm value (r2124, interpret decimal): and download the new configuration to the drive unit.
Component number of the additional target components. - delete the drive belonging to the Sensor Module in the commissioning software
pro

Sinamics G130 A01483 Topology: Comparison Terminal Module The topology comparison has detected a Terminal Module in the target - delete the Terminal Module in the commissioning software project and
missing in the actual topology topology that is not available in the actual download the new configuration to the drive
topology. unit.
Alarm value (r2124, interpret decimal): - check that the actual topology matches the target topology and if required,
Component number of the additional target components. change over.
- check DRIVE-CLiQ cables for interruption

Sinamics G130 A01484 Topology: Comparison DRIVE-CLiQ Hub The topology comparison has detected a DRIVE-CLiQ Hub Module in the - delete the DRIVE-CLiQ Hub Module in the commissioning software project and
Module missing in the actual topology target topology that does not exist in the download the new configuration to
actual topology. the drive unit.
Alarm value (r2124, interpret decimal): - check that the actual topology matches the target topology and if required,
Component number of the additional target components. change over.
- check DRIVE-CLiQ cables for interru

Sinamics G130 A01485 Topology: Comparison CX32 missing in the The topology comparison has detected a controller extension 32 (CX32) in - delete the CX32 / NX in the commissioning software project and download the
actual topology the target topology that is not available new configuration to the drive unit.
in the actual topology. - check that the actual topology matches the target topology and if required,
Alarm value (r2124, interpret decimal): change over.
Component number of the additional target components. - check DRIVE-CLiQ cables for interruption and co

Sinamics G130 A01486 Topology: Comparison DRIVE-CLiQ The topology comparison has detected a DRIVE-CLiQ component in the - delete the drive belonging to this component in the commissioning software
components missing in the actual topology target topology that is not available in the project and download the new configuration
actual topology. to the drive unit.
Alarm value (r2124, interpret decimal): - re-configure the drive belonging to this component in the commissioning
Component number of the additional target components. software project and download the new
conf

Sinamics G130 A01487 Topology: Comparison option slot components The topology comparison has detected an option slot module in the target - delete the option board in the commissioning software project and download
missing in the actual topology topology that is not available in the actual the new configuration to the drive unit.
topology. - re-configure the drive unit in the commissioning software project and
Alarm value (r2124, interpret decimal): download the new configuration to the drive
Component number of the additional target components. unit.
- check that th

Sinamics G130 A01488 Topology: Comparison EnDat encoder missing The topology comparison has detected an EnDat encoder in the target - re-configure the drive belonging to the encoder in the commissioning software
in the actual topology topology that is not available in the actual project (encoder configuration) and
topology. download the new configuration to the drive unit.
Alarm value (r2124, interpret decimal): - delete the drive belonging to the encoder in the commissioning software
Component number of the additional target components. project and dow

Sinamics G130 A01489 Topology: Comparison motor with DRIVE-CLiQ The topology comparison has detected a motor with DRIVE-CLiQ in the - re-configure the drive belonging to this motor in the commissioning software
missing in the actual topology target topology that is not available in the project and download the new configuration
actual topology. to the drive unit.
Alarm value (r2124, interpret decimal): - re-configure the drive belonging to this motor in the commissioning software
Component number of the additional target components. project and download the new config
Sinamics G130 A01507 (F, N) BICO: Interconnections to inactive objects There are BICO interconnections as signal sink from a drive object that is - set all open BICO interconnections centrally to the factory setting with p9495 =
present either inactive/not operational. 2.
The BI/CI parameters involved are listed in r9498. - make the non-operational drive object active/operational again (re-insert or
The associated BO/CO parameters are listed in r9499. activate components).
The list of the BICO interconnections to ot

Sinamics G130 A01508 BICO: Interconnections to inactive objects The maximum number of BICO interconnections (signal sinks) when de- The alarm automatically disappears as soon as no BICO interconnection (value =
exceeded activating a drive object was exceeded. 0) is entered in r9498[29] and
When de-activating a drive object, all BICO interconnections (signal sinks) r9499[29].
are listed in the following parameters: Notice:
- r9498[0...29]: List of the BI/ When re-activating the drive object, all BICO interconnections should be checked
and if required, re-established.

Sinamics G130 A01514 (F) BICO: Error when writing during a reconnect During a reconnect operation (e.g. while booting or downloading - but can None necessary.
also occur in normal operation) a parameter
was not able to be written to.
Example:
When writing to a double word BICO input in the second index, the
memory areas overlap (e.g. p886

Sinamics G130 A01590 (F) Drive: Motor maintenance interval expired The selected service/maintenance interval for this motor was reached. carry out service/maintenance and reset the service/maintenance interval
Alarm value (r2124, interpret decimal): (p0651).
Motor data set number.
See also: p0650 (Actual motor operating hours), p0651 (Motor operating
hours maintenance interval)

Sinamics G130 A01691 (F) SI Motion: Ti and To unsuitable for DP cycle The configured times for PROFIBUS communication are not permitted and Configure Ti and To low so that they are suitable for the DP cycle or increase the
the DP cycle is used as the actual value DP cycle time.
acquisition cycle for the safe movement monitoring functions: Option for enabled drive-based SI monitoring (p9601/p9801 > 0):
Isochronous PROFIBUS: the total of Ti and To is too high for the set DP Use the actual value sampling cycle p9511/p9311 and, therefore, set it
cycle. The independently of the D

Sinamics G130 A01696 (F) SI Motion: Testing of the motion monitoring The test of the motion monitoring functions was already illegally active De-select the forced checking procedure of the safety motion monitoring
functions selected when booting when booting. functions and then select again.
This is the reason that the test is only carried out again after selecting the The signal source for initiation is parameterized in binector input p9705.
forced checking procedure parameterized Note:
in p9705. SI: Safety Integrated
Note: See also: p9705 (SI Motion: Test stop signal so
This message does not result in a

Sinamics G130 A01697 (F) SI Motion: Motion monitoring functions must The time set in p9559 for the forced checking procedure of the safety Carry out the forced checking procedure of the safety motion monitoring
be tested motion monitoring functions has been functions.
exceeded. A new test is required. The signal source for initiation is parameterized in BI: p9705.
After next selecting the forced checking procedure parameterized in p9705, Note:
the message is withdrawn and the monito SI: Safety Integrated
See also: p9705 (SI Motion: Test stop signal source)

Sinamics G130 A01698 (F) SI CU: Commissioning mode active The commissioning of the "Safety Integrated" function is selected. None necessary.
This message is withdrawn after the safety functions have been Note:
commissioned. CU: Control Unit
Note: SI: Safety Integrated
This message does not result in a safety stop response.
See also: p0010

Sinamics G130 A01699 (F) SI CU: Shutdown path must be tested The time set in p9659 for the forced checking procedure of the safety Select STO and then deselect again.
shutdown paths has been exceeded. The Note:
safety shutdown paths must be re-tested. CU: Control Unit
After the next time the "STO" function is de-selected, the message is SI: Safety Integrated
withdrawn and the monitoring time is STO: Safe Torque Off / SH: Safe standstill

Sinamics G130 A01796 (F, N) SI Motion CU: Wait for communication The drive waits for communication to be established with SINUMERIK or After a longer period of time, if the message is not automatically withdrawn, the
TM54F to execute the safety-relevant following checks should be made
motion monitoring functions. dependent on the communication:
Note: For communication with SINUMERIK, the following applies:
In this state, the pulses are safely suppressed. - check additional messages that are present regardi

Sinamics G130 A01900 (F) PROFIBUS: Configuration telegram error A PROFIBUS master attempts to establish a connection using an incorrect Check the bus configuring on the master and slave sides.
configuring telegram. Re alarm value = 51:
Alarm value (r2124, interpret decimal): Check the list of the drive objects with process data exchange (p0978). With
50: Syntax error. p0978[x] = 0, all of the following drive
51: Connection established to more drive objects than configured in the objects in the list are excluded from the process data exch
device. The drive objects for p

Sinamics G130 A01901 (F) PROFIBUS: Parameterizing telegram error A PROFIBUS master attempts to establish a connection using an incorrect Check the bus configuration:
parameterizing telegram. - bus addresses
Alarm value (r2124, interpret decimal): - slave configuring
1: Incorrect parameterizing bits.
10: Illegal length of an optional parameterizing block.
11: Illegal ID of an optiona
Sinamics G130 A01902 IF1: PB/PN clock cycle synchronous operation Alarm value (r2124, interpret decimal): - adapt the current and speed controller clock cycle.
parameterization not permissible 0: Bus cycle time Tdp < 0.5 ms. Re alarm value = 9:
1: Bus cycle time Tdp > 32 ms. - carry out a POWER ON.
2: Bus cycle time Tdp is not an integer multiple of the current controller Re alarm value = 15:
clock cycle. - check the number of specific drive object types in the configuration.
3: Instant of the actual value sensing Ti > Bus cycle time Tdp o Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET

Sinamics G130 A01903 (F) COMM INT: Receive configuration data invalid The drive unit did not accept the receive configuration data. Check the receive configuration data.
Alarm value (r2124, interpret decimal): Re alarm value = 1:
Return value of the receive configuration data check. Check the list of the drive objects with process data exchange (p0978). With
0: Configuration accepted. p0978[x] = 0, all of the following drive
1: Connection established to more drive objects than configured in the d objects in the list are excluded from the process data exchange.

Sinamics G130 A01920 (F) PROFIBUS: Interruption cyclic connection The cyclic connection to the PROFIBUS master is interrupted. Establish the PROFIBUS connection and activate the PROFIBUS master in the
cyclic mode.
Sinamics G130 A01921 (F) PROFIBUS: Receive setpoints after To Output data of PROFIBUS master (setpoints) received at the incorrect - check parameters for clock cycle synchronization (ensure To > Tdx).
instant in time within the PROFIBUS clock Note:
cycle. To: Time of setpoint acceptance
Tdx: Data exchange time

Sinamics G130 A01930 IF1: PB/PN current controller clock cycle clock The current controller clock cycle of all drives must be set the same for the Set current controller clock cycles to identical values (p0115[0]).
cycle synchronous not equal clock cycle synchronous operation. Note:
Alarm value (r2124, interpret decimal): IF1: Interface 1
Number of the drive object with different current controller clock cycle. PB: PROFIBUS
PN: PROFINET
See also: p0115

Sinamics G130 A01931 IF1: PB/PN speed controller clock cycle clock The speed controller clock cycle of all drives must be set the same for the Set the speed controller clock cycles the same (p0115[1]).
cycle synchronous not equal clock cycle synchronous operation. Note:
Alarm value (r2124, interpret decimal): IF1: Interface 1
Number of the drive object with the different speed controller clock cycle. PB: PROFIBUS
PN: PROFINET
See also: p0115

Sinamics G130 A01940 IF1: PB/PN clock cycle synchronism not reached The bus is in the data exchange state and clock synchronous operation has - check the master application and bus configuration.
been selected using the parameterizing - check the consistency between the clock cycle input when configuring the slave
telegram. It was not possible to synchronize to the clock cycle specified by and clock cycle setting at the master.
the master. - ensure that the pulses of drive objects that are not controlled by
- the master does not send a clock synchronous global PROFIBUS/PRO

Sinamics G130 A01941 IF1: PB/PN clock cycle signal missing when The bus is in the data exchange state and clock synchronous operation has Check the master application and bus configuration.
establishing bus communication been selected using the parameterizing Note:
telegram. The global control telegram for synchronization is not being IF1: Interface 1
received. PB: PROFIBUS
PN: PROFINET

Sinamics G130 A01943 IF1: PB/PN clock cycle signal error when The bus is in the data exchange state and clock synchronous operation has - check the master application and bus configuration.
establishing bus communication been selected using the parameterizing - check the consistency between the clock cycle input when configuring the slave
telegram. The global control telegram for synchronization is being and clock cycle setting at the master.
irregularly received. Note:
-.the master is sending an irregular global control t IF1: Interface 1
PB: PROFIBUS
PN: PROFINET

Sinamics G130 A01944 IF1: PB/PN sign-of-life synchronism not reached The bus is in the data exchange state and clock synchronous operation has - ensure that the master correctly increments the sign-of-life in the master
been selected using the parameterizing application clock cycle Tmapc.
telegram. Synchronization with the master sign-of-life (STW2.12 ... - correct the interconnection of the master sign-of-life (p2045).
STW2.15) could not be completed because the Note:
sign-of-life is changing diffe IF1: Interface 1
PB: PROFIBUS
PN: PROFINET

Sinamics G130 A01945 PROFIBUS: Connection to the Publisher failed For PROFIBUS peer-to-peer data transfer, the connection to at least one - check the PROFIBUS cables.
Publisher has failed. - carry out a first commissioning of the Publisher that has the failed connection.
Alarm value (r2124, interpret binary): See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses)
Bit 0 = 1: Publisher with address in r2077[0], connection failed.
...
Bit 15 = 1: Publisher with address in r2077[15], con

Sinamics G130 A01953 CU DRIVE-CLiQ: Synchronization not completed After the drive system is powered up, the synchronization between the Carry out a POWER ON (power off/on) for all components.
basic clock cycle, DRIVE-CLiQ clock cycle If the error occurs after the drive sampling times were adjusted, and if a TM31
and application clock cycle was started but was not completed within the module is being used, the sampling
selected time tolerance. times (p0115, p4099) should be set as integer multiples to the drive clock cycles
Alarm value (r2124, interpret decimal): (p0115).
Only for internal Siemens troubleshooting.
Sinamics G130 A01955 CU DRIVE-CLiQ: Synchronization DO not After the drive system is powered up, the synchronization between the Carry out a POWER ON (power off/on) for all components of the DO.
completed basic clock cycle, DRIVE-CLiQ clock cycle
and application clock cycle was started but was not completed within the
selected time tolerance.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.

Sinamics G130 A02000 Function generator: Start not possible The function generator has already been started. Stop the function generator and restart again if necessary.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4800 (Function generator control)

Sinamics G130 A02005 Function generator: Does not exist The drive object specified for connection does not exist. Use the existing drive object with the corresponding number.
See also: p4815 (Function generator drive number) Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4815 (Function generator drive number)

Sinamics G130 A02006 Function generator: No drive specfied for No drive specified for connection in p4815. At least one drive to be connected must be specified in p4815.
connection See also: p4815 (Function generator drive number) Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4815 (Function generator drive number)

Sinamics G130 A02007 Function Generator: Drive not SERVO/VECTOR The drive object specified for connection is not a SERVO / VECTOR. Use a SERVO / VECTOR drive object with the corresponding number.
See also: p4815 (Function generator drive number) Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.

Sinamics G130 A02008 Function generator: Drive specified a multiple The drive object specified for connection is already specified. Note:
number of times Alarm value (r2124, interpret decimal): The alarm is reset as follows:
Drive object number of the drive object that is specified a multiple number - remove the cause of this alarm.
of times. - restart the function generator.

Sinamics G130 A02009 Function generator: Illegal mode The set operating mode (p1300) of the drive object is not permissible when Change the operating mode for this drive object to p1300 = 20 (encoderless
using the function generator. speed control) or p1300 = 21 (speed
Alarm value (r2124, interpret decimal): control with encoder).
Number of the drive object involved. Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.

Sinamics G130 A02010 Function generator: Speed setpoint from the The speed setpoint of a drive selected for connection is greater than the For all of the drives specified for connection, set the speed setpoints to 0.
drive is not zero value for the standstill detection set using Note:
p1226. The alarm is reset as follows:
Alarm value (r2124, interpret decimal): - remove the cause of this alarm.
Number of the drive object involved. - restart the function generator.

Sinamics G130 A02011 Function generator: The actual drive speed is The speed actual value of a drive selected for connection is greater than Set the relevant drives to zero speed before starting the function generator.
not zero the value for the standstill detection set Note:
using p1226. The alarm is reset as follows:
Alarm value (r2124, interpret decimal): - remove the cause of this alarm.
Number of the drive object involved. - restart the function generator.

Sinamics G130 A02015 Function generator: Magnetizing running Cause: The master control and/or enable signals are missing to connect to Fetch the master control to the specified drive object and set all enable signals.
the specified drive. Note:
Alarm value (r2124, interpret decimal): The alarm is reset as follows:
Number of the drive object involved. - remove the cause of this alarm.
See also: p4815 (Function generator drive number) - restart the function generator.

Sinamics G130 a02016 Function generator: Parameter cannot be Magnetizing has not yet been completed on a drive object specified for Wait for magnetizing of the motor (r0056.4).
changed connection. Note:
Alarm value (r2124, interpret decimal): The alarm is reset as follows:
Number of the drive object involved. - restart the function generator.
See also: p4815 (Function generator drive number) See also: r0056 (Status word, closed-loop control)
A02020 Function generator: Parameter cannot be

Sinamics G130 A02020 Function generator: Parameter cannot be This parameter setting cannot be changed when the function generator is - stop the function generator before parameterizing (p4800 = 0).
changed active (p4800 = 1). - if required, start the function generator (p4800 = 1).
See also: p4810, p4812, p4813, p4815, p4820, p4821, p4822, p4823, Note:
p4824, p4825, p4826, p4827, p4828, p4829 The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4800 (Function generator control)
Sinamics G130 A02025 Function generator: Period too short The value for the period is too short. Check and adapt the value for the period.
See also: p4821 (Function generator period Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4821 (Function generator period)

Sinamics G130 A02026 Function generator: Pulse width too high The selected pulse width is too high. Reduce pulse width.
The pulse width must be less than the period duration. Note:
See also: p4822 (Function generator pulse width) The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4821 (Function generator period), p4822 (Function generator pulse
width)

Sinamics G130 A02030 Function generator: Physical address equals The specified physical address is zero. Set a physical address with a value other than zero.
zero See also: p4812 (Function generator physical address) Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4812 (Function generator physical address

Sinamics G130 A02040 Function generator: Illegal value for offset The value for the offset is higher than the value for the upper limit or lower Adjust the offset value accordingly.
than the value for the lower limit. Note:
See also: p4826 (Function generator offset) The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4826 (Function generator offset), p4828 (Function generator lower
limit), p4829 (Function generator
upper limit)

Sinamics G130 A02041 Function gnerator: Illegal value for bandwidth The bandwidth referred to the time slice clock cycle of the function Check the value for the bandwidth and adapt accordingly.
generator has either been set too low or too high. Note:
Depending on the time slice clock cycle, the bandwidth is defined as The alarm is reset as follows:
follows: - remove the cause of this alarm.
Bandwidth_max = 1 / (2 * time slice clock cycle) - restart the function generator.
Bandwidth_min = Bandwidth_max / 100000
Example:
Assumption: p4830 = 125 μs
--> Bandwidth_max = 1 / (2 * 125 μs) = 4000 Hz
--> Bandwidth_min = 4000 Hz / 100000 = 0.04 Hz
Note:
p4823: Function generator bandwidth
p4830: Function generator time slice clock cycle
See also: p4823 (Function generator bandwidth), p4830 (Function
generator time slice cycle)

Sinamics G130 A02047 Function generator: Time slice clock cycle The time slice clock cycle selected does not match any of the existing time Enter an existing time slice clock cycle. The existing time slices can be read out
invalid slices. via p7901.
See also: p4830 (Function generator time slice cycle) Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: r7901 (Time slice cycle times)

Sinamics G130 A02050 Trace: Start not possible The trace has already been started. Stop the trace and, if necessary , start again.
See also:p4700(trace control)
Sinamics G130 A02055 Trace: recording time too short The trace duration is too short. Check the selected recording time and if necessary adjust.
The minimum is twice the value of the trace clock cycle.
See also: p4271 (trace recording time)

Sinamics G130 A02056 Trace: Time slice clock cycle invalid The time slice clock cycle selected does not match any of the existing time Enter an existing time slice clock cycle. The existing time slices can be read out
slices. via p7901.
See also: p4723 (Time slice cycle for trace) See also: r7901 (Time slice cycle times)

Sinamics G130 A02057 Trace: Time slice clock cycle invalid The time slice clock cycle selected does not match any of the existing time Enter an existing time slice clock cycle. The existing time slices can be read out
slices. via p7901.
See also: p4723 (Time slice cycle for trace) See also: r7901 (Time slice cycle times)

Sinamics G130 A02058 Trace: Time slice clock cycle for endless trace The selected time slice clock cycle cannot be used for the endless trace Enter the clock cycle of an existing time slice with a cycle time >= 2 ms for up to
not valid See also: p4723 (Time slice cycle for trace) 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)

Sinamics G130 A02059 Trace: Time slice clock cycle for 2 x 8 recording The selected time slice clock cycle cannot be used for the setting p4702 = 1 Enter the clock cycle of an existing time slice with a cycle time >= 4 ms or reduce
channels not valid (2 x 8 recording channels). the number of recording channels
See also: p4723 (Time slice cycle for trace) to 4 per trace.
The existing time slices can be read out via p7901.
See also: r7901 (Time slice cycle times)
Sinamics G130 A02060 Trace: Signal to be traced missing - a signal to be traced was not specified. - specify the signal to be traced.
- the specified signals are not valid. - check whether the relevant signal can be traced.
See also: p4730 (Trace record signal 0), p4731 (Trace record signal 1),
p4732 (Trace record signal 2), p4733 (Trace
record signal 3)

Sinamics G130 A02061 Trace: Invalid signal - the specified signal does not exist. - specify the signal to be traced.
- the specified signal can no longer be traced (recorded). - check whether the relevant signal can be traced.
See also: p4730 (Trace record signal 0), p4731 (Trace record signal 1),
p4732 (Trace record signal 2), p4733 (Trace
record signal 3)

Sinamics G130 A02062 Tracer: Invalid trigger signal - a trigger signal was not specified. Specify a valid trigger signal
- the specified signal does not exist.
- the specified signal is not a fixed-point signal.
- the specified signal cannot be used as a trigger signal for the trace.
See also: p4711 (Trace trigger signal)

Sinamics G130 A02063 Trace: Invalid data type The specified data type to select a signal using a physical address is invalid. Use a valid data type.
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)

Sinamics G130 A02070 Trace: Parameter cannot be changed The trace parameter settings cannot be changed when the trace is active. - stop the trace before parameterization.
See also: p4700, p4710, p4711, p4712, p4713, p4714, p4715, p4716, - if required, start the trace.
p4720, p4721, p4722, p4730, p4731, p4732,
p4733, p4780, p4781, p4782, p4783, p4789, p4795

Sinamics G130 A02075 Trace: Pretrigger time for too long The selected pretrigger time must be shorter than the trace time. Check the pretrigger time setting and change if necessary.
See also: p4721 (Trace recording time), p4722 (Trace trigger delay)
Sinamics G130 A02099 Trace: Insufficient Control Unit memory The memory space still available on the Control Unit is no longer sufficient
for the trace function.
Sinamics G130 A02100 CU: Computing dead time current controller The value in p0118 produces a dead time of one clock cycle because it is - set p0118 to a value greater than or equal to the alarm value.
too short prior to setpoint availability. A possible - set p0117 to an automatic setting.
cause could be, for example, that the system characteristics no longer - check the firmware releases of the components involved.
match those parameterized after a component See also: p0117 (Current controller computing dead time mode), p0118 (Current
has been replaced. controller computing dead time)
Alarm value (r2134, floating point):
The minimum value for p0118 where a dead time no longer occurs.

Sinamics G130 A02150 OA: Application cannot be loaded The system wwas not able to load an OA application. - carry out a POWER ON (power off/on) for all components.
Alarm value (r2124, interpret hexadecimal): - upgrade firmware to later version.
Only for internal Siemens troubleshooting. - contact the Hotline.
Note:
OA: Open Architecture
See also: r4950, r4955, p4956, r4957

Sinamics G130 A03501 TM: Sampling time change The sampling times of the inputs/outputs were changed. Carry out a POWER ON.
This change only becomes valid after the next boot.
Sinamics G130 A03506 (F,N) 24 V power missing The 24 V power supply for the digital outputs (X124) is missing. Check the terminals for the power supply voltage (X124, L1+, M).
Sinamics G130 A03550 Sinamics / AIF VSD TM: Speed setpoint filter natural frequency > The natural filter frequency of the speed setpoint filter (P1417) is greater Reduce the the natural frequency of the speed setpoint filter (PT2 low pass)
Shannon frequency than the Shannon frequency. The Shannon frequency is calculated (P1417)
according to the following formula: 0.5 / P0155[0]

Sinamics G130 A05000 Sinamics / AIF VSD Power module: Overtemperature heatsink The alarm threshold for overtemperature at the inverter heatsink has been - Check if the ambient temperature within the defined limit values.
reached. The response is set using P0290. - have the load conditions and the load duty cycle been appropriately
If the temperature of the heatsink increases by an additional 5K, then fault dimensioned
F30004 is initiated. - Has the cooling failed, ie the fan is stopped, either intermittently or faulty.
Check direction of fan
Maybe the cooling fan is faulty, the fil

Sinamics G130 A05001 Sinamics / AIF VSD Power module: Overtemperature chip The alarm threshold for overtemperature of the power semiconductor in - Check if the ambient temperature within the defined limit values.
the AC converter has been reached. The response is set using P0290. - have the load conditions and the load duty cycle been appropriately
If the temperature of the chip increases by an additional 15 K, then fault dimensioned?
F30025 is initiated. - Has the cooling failed, ie the fan is stopped, either intermittently or faulty.
Check direction of fan
Maybe the cooling fa

Sinamics G130 A05002 Sinamics / AIF VSD Power module: Overtemp air intake The alarm threshold for the air intake overtemperature has been reached. - Check if the ambient temperature within the defined limit values.
The response is set using P0290. - have the load conditions and the load duty cycle been appropriately
If the air intake temperature increases by an additional 5 K, then fault dimensioned?
F30035 is initiated. - Has the cooling failed, ie the fan is stopped, either intermittently or faulty.
Check direction of fan
Maybe the cooling fan is faulty, the filter block. The
Sinamics G130 A05003 Sinamics / AIF VSD Power module: Overtemperature electronics The alarm threshold for the overtemperature of the electronics module has - Check if the ambient temperature within the defined limit values.
unit been reached. The response is set using P0290. - have the load conditions and the load duty cycle been appropriately
If the temperature of the electronics module increases by an additional 5 K, dimensioned?
then fault F30036 is initiated. - Has the cooling failed, ie the fan is stopped, either intermittently or faulty.
Check direction of fan
Maybe the cooling fan is

Sinamics G130 A05004 Sinamics / AIF VSD Power module: Overtemperature rectifier The alarm threshold for the overtemperature of the rectifier has been - Check if the ambient temperature within the defined limit values.
reached. The response is set using P0290. - have the load conditions and the load duty cycle been appropriately
If the temperature of the electronics module increases by an additional 5 K, dimensioned?
then fault F30037 is initiated. - Has the cooling failed, ie the fan is stopped, either intermittently or faulty.
Check direction of fan
Maybe the cooling fan is faulty,

Sinamics G130 A05005 Sinamics / AIF VSD Cooling system: Cooling medium flow rate too Cooling system: alarm - flow rate has fallen below the alarm value
low.
Sinamics G130 A05006 (N) Power unit: Overtemperature thermal model The temperature difference between the chip and heat sink has exceeded None necessary.
the permissible limit value (for blocksize The alarm automatically disappears when the limit value is undershot.
power units only). Depending on p0290, a suitable overload response is Note:
initiated. If the alarm does not disappear automatically and the temperature continues to
See also: r0037 rise, this can trigger fault F30024.
- If DC brake is active: reduce braking current (see p1232).
See also: p0290 (Power unit overload response)

Sinamics G130 A05052 Sinamics / AIF VSD Parallel circuit configuration: Impermissible The deviation of the individaul currents of the power modules exceeds the - inhibit the pulses of the faulted power module (P7001)
current dissymmetry alarm threshold specified in P7010. - Check the connecting cables. Loose contacts can cause current spikes
Alarm value (r2124, decimal)5/01/2007 - The motor reactors are non-symmetrical or faulty and must be replaced
1: Phase U - The CTs must be calibrated or replaced.
2: Phase V
3: Phase W

Sinamics G130 A05053 Sinamics / AIF VSD Parallel circuit configuration: Inadmissible DC The deviation of the DC link voltage measured values exceeds the alarm - inhibit the pulses of the faulted power unit (p7001).
link voltage dissymmetry threshold specified in p7011. - check the DC link connecting cables.
- the DC link voltage measurement is incorrect and must be calibrated or
renewed.

Sinamics G130 A05054 Parallel circuit: Power unit de-activated For the drive object involved, fewer power unit components connected in Re-activate the de-activated power unit components.
parallel are active than exist in the target See also: p0125 (Activate/de-activate power unit components), p0895
topology. Operation is only possible at reduced power (power de-rating). (Activate/de-activate power unit components),
p0897 (Parking axis selection)

Sinamics G130 A07012 (N) Drive: I2t motor model overtemperature The thermal I2t motor model identified that the temperature alarm - check the motor load and if required, reduce.
threshold was exceeded. - check the motor ambient temperature.
See also: r0034 (Motor utilization), p0605 (Motor overtemperature fault - check the thermal time constant p0611.
threshold), p0611 (I2t motor model thermal - check the overtemperature fault threshold p0605 (= alarm threshold for the I2t
time constant) motor model)

Sinamics G130 A07015 Drive: Motor temperature sensor alarm An error was detected when evaluating the temperature sensor set in - check that the sensor is connected correctly.
p0600 and p0601. - check the parameterization (p0600, p0601).
With the fault, the time in p0607 is started. If the fault is still present after See also: r0035, p0600, p0601, p0607, p4600, p4601, p4602, p4603, r4620
this time has expired, then fault F07016 is
output; however, at the earliest, 1 s after alarm A07015.
Possible causes:
- wire breakage or sensor not connected (KTY: R > 1630 Ohm).
- measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).
Alarm value (r2124, interpret decimal):
For SME selected (p0601 = 10), number of the sensor channel leading to
the message.

Sinamics G130 A07089 Changing over units: Adding a function module An attempt was made to add a function module. This is not permissible if Restore units that have been changed over to the default value.
blocked if units changed over the units have already been changed over.
See also: p0100 (IEC/NEMA mot stds), p0349 (System of units, motor
equivalent circuit diagram data), p0505
(Selecting the system of units

Sinamics G130 A07200 Drive: Master control ON/OFF1 command The ON/OFF1 command is not 0, either via binector input p0840 (current The signal at binector input p0840 (current CDS) as well as p3982 bit 0 must be 0.
present CDS) or in control word p3982 bit 0.
Sinamics G130 A07321 Drive: Automatic restart active The automatic restart (AR) is active. When the line supply returns and/or - the automatic restart (AR) should, if required, be inhibited (p1210 = 0).
the causes of the existing faults are - an automatic restart can be directly interrupted by withdrawing the power-on
removed the drive is automatically restarted. The pulses are enabled and command (BI: p0840).
the motor starts to rotate.

Sinamics G130 A07350 (F) Drive: Measuring probe parameterized to a The measuring probe is connected - set the terminal as input (p0728).
digital output Alarm value (r2124, decimal): - de-select the measuring probe (p0488, p0489, p0580).
9: DI/DO 9 (X122.8)
10: DI/DO 10 (X122.10)
11: DI/DO 11 (X122.11)
13: DI/DO 13 (X132.8)
14: DI/DO 14 (X132.10)
15: DI/DO 15 (X132.11)
Sinamics G130 A07400 (N) Drive: DC link voltage maximum controller The DC link voltage controller has been activated because the upper If the controller is not to intervene:
active switch-in threshold has been exceeded (r1242). - increase the ramp-down times.
The ramp-down times are automatically increased in order to maintain the - disable the Vdc max controller
DC link voltage (r0026) within the permissible If the ramp-down times are not to be changed:
limits. There is a system deviation between the setpoint and actual speeds. - use a chopper or regenerative feedback unit
See also: p1240 (Vdc controller or Vdc monitoring configuration)
When the DC link voltage controller is switched out (disabled), this is the
reason that the ramp-function generator
output is set to the speed actual value.

Sinamics G130 A07401 (N) Drive: DC link voltage maximum controller de- The Vdc_max controller can no longer maintain the DC link voltage (r0026) - check whether the input voltage is within the permissible range.
activated below the limit value (r1242) and was - check whether the load duty cycle and load limits are within the permissible
therefore switched out (disabled). limits.
- the line supply voltage is permanently higher than specified for the power
unit.
- the motor is permanently in the regenerative mode as a result of a load
that is driving the motor.

Sinamics G130 A07402 (N) Drive: DC link voltage minimum controller The DC link voltage controller has been activated as the lower switch-in The alarm disappears when power supply returns.
active threshold has been undershot (r1246).
The kinetic energy of the motor is used in order to buffer the DC link. This
brakes the drive.
See also: p1240 (Vdc controller or Vdc monitoring configuration)

Sinamics G130 A07409 Drive: V/f control, current limiting controller The current limiting controller of the V/f control was activated because the The alarm is automatically withdrawn when increasing the current limit (p0640),
active current limit was exceeded. reducing the load or using a slower
up ramp for the setpoint (reference) speed.

Sinamics G130 A07410 (N) Drive: DC link voltage maximum controller de- The Vdc_max controller can no longer maintain the DC link voltage (r0026) - check whether the input voltage is within the permissible range.
activated below the limit value (r1242) and was - check whether the load duty cycle and load limits are within the permissible
therefore switched out (disabled). limits.
- the line supply voltage is permanently higher than specified for the power
unit.
- the motor is permanently in the regenerative mode as a result of a load
that is driving the motor.

Sinamics G130 A07416 Drive: Flux controller configuration The configuration of the flux control (p1401) is contradictory. Re fault cause = 1:
Alarm value (r2124, interpret hexadecimal): - Shut down soft start (p1401.0 = 0).
ccbbaaaa hex - Shut down quick magnetizing (p1401.6 = 0).
aaaa = parameter Re fault cause = 2:
bb = index - De-energize flux build-up control (p1401.2 = 0).
cc = fault cause - Shut down quick magnetizing (p1401.6 = 0).
cc = 01 hex = 1 dec: Re fault cause = 3:
Quick magnetizing (p1401.6) for soft start (p1401.0). - Re-parameterize Rs identification (p0621 = 0, 1)
cc = 02 hex = 2 dec: - Shut down quick magnetizing (p1401.6 = 0).
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).

Sinamics G130 A07440 EPOS: Jerk time is limited The calculation of the jerk time Tr = MAX(p2572, p2573) / p2574 resulted in - increase the jerk limiting (p2574).
an excessively high value so that the - reduce maximum acceleration or maximum deceleration (p2572, p2573).
jerk time is internally limited to 1000 ms.
Note:
The alarm is also output if jerk limiting is not active.

Sinamics G130 A07441 LR: Save the position offset of the absolute The status of the absolute encoder adjustment has changed. None necessary.
encoder adjustment In order to permanently save the determined position offset (p2525) it This alarm automatically disappears after the offset has been saved.
must be saved in a non-volatile fashion (p0971,
p0977).

Sinamics G130 A07454 LR: Position actual value preprocessing does One of the following problems has occurred with the position actual value Check the drive data sets, encoder data sets and encoder assignment.
not have a valid encoder preprocessing: See also: p0187 (Encoder 1 encoder data set number), p0188 (Encoder 2
- an encoder is not assigned for the position actual value preprocessing encoder data set number), p0189
(p2502 = 0). (Encoder 3 encoder data set number), p0400 (Encoder type selection)
- an encoder is assigned, but no encoder data set (p0187 = 99 or p0188 =
99 or p0189 = 99).
- an encoder an an encoder data set have been assigned, however, the
encoder data set does not contain any
encoder data (p0400 = 0) or invalid data (e.g. p0408 = 0).

Sinamics G130 A07455 EPOS: Maximum velocity limited The maximum velocity (p2571) is too high to correctly calculate the modulo - reduce the maximum velocity (p2571).
correction. - increase the sampling time for positioning (p0115[5]).
Within the sampling time for positioning (p0115[5]), with the maximum
velocity, a maximum of the half modulo length
must be moved through. p2571 was limited to this value.
Sinamics G130 A07456 EPOS: Setpoint velocity limited The current setpoint velocity is greater than the parameterized maximum - check the entered setpoint velocity.
velocity (p2571) and is therefore limited. - reduce the velocity override (CI: p2646).
- increase the maximum velocity (p2571).
- check the signal source for the externally limited velocity (CI: p2594).

Sinamics G130 A07457 EPOS: Combination of input signals illegal An illegal combination of input signals that are simultaneously set was Check the appropriate input signals and correct.
identified.
Alarm value (r2124, interpret decimal):
0: Jog 1 and jog 2 (p2589, p2590).
1: Jog 1 or jog 2 and direct setpoint input/MDI (p2589, p2590, p2647).
2: Jog 1 or jog 2 and start referencing (p2589, p2590, p2595).
3: Jog 1 or jog 2 and activate traversing task (p2589, p2590, p2631).
4: Direct setpoint input/MDI and starting referencing (p2647, p2595).
5: Direct setpoint input/MDI and activate traversing task (p2647, p2631).
6: Start referencing and activate traversing task (p2595, p2631).

Sinamics G130 A07461 EPOS: Reference point not set When starting a traversing block/direct setpoint input, a reference point is Reference the system (search for reference, flying referencing, set reference
not set (r2684.11 = 0). point).
Sinamics G130 A07462 EPOS: Selected traversing block number does A traversing block selected via BI: p2625 to BI: p2630 was started via BI: - correct the traversing program.
not exist p2631 = 0/1 edge "Activate traversing task". - select an available traversing block number.
- the number of the started traversing block is not contained in
p2616[0...n].
- the started traversing block is suppressed.
Alarm value (r2124, interpret decimal):
Number of the selected traversing block that is also not available.

Sinamics G130 A07463 (F) EPOS: External block change not requested in For a traversing block with the block change enable Resolve the reason as to why the edge is missing at binector input (BI: p2632).
the traversing block CONTINUE_EXTERNAL_ALARM, the external block change
was not requested.
Alarm value (r2124, interpret decimal):
Number of the traversing block.

Sinamics G130 A07465 EPOS: Traversing block does not have a There is no subsequent block in the traversing block. - parameterize this traversing block with the block change enable END.
subsequent block Alarm value (r2124, interpret decimal): - parameterize additional traversing blocks with a higher block number and for
Number of the traversing block with the missing subsequent block. the last block, using the block change
enable END.

Sinamics G130 A07466 EPOS: Traversing block number assigned a The same traversing block number was assigned a multiple number of Correct the traversing blocks.
multiple number of times times.
Alarm value (r2124, interpret decimal):
Number of the traversing block that was assigned a multiple number of
times.

Sinamics G130 A07467 EPOS: Traversing block has illegal task The task parameter in the traversing block contains an illegal value. Correct the task parameter in the traversing block.
parameters Alarm value (r2124, interpret decimal):
Number of the traversing block with an illegal task parameter.

Sinamics G130 A07468 EPOS: Traversing block jump destination does In a traversing block, a jump was programmed to a non-existent block. - correct the traversing block.
not exist Alarm value (r2124, interpret decimal): - add the missing traversing block.
Number of the traversing block with a jump destination that does not exist.

Sinamics G130 A07469 EPOS: Traversing block < target position < In the traversing block the specified absolute target position lies outside - correct the traversing block.
software limit switch minus the range limited by the software limit switch - change software limit switch minus (CI: p2578, p2580).
minus.
Alarm value (r2124, interpret decimal):
Number of the traversing block with illegal target position.

Sinamics G130 A07470 EPOS: Traversing block> target position > In the traversing block the specified absolute target position lies outside - correct the traversing block.
software limit switch plus the range limited by the software limit switch - change software limit switch plus (CI: p2579, p2581).
plus.
Alarm value (r2124, interpret decimal):
Number of the traversing block with illegal target position.

Sinamics G130 A07471 EPOS: Traversing block target position outside In the traversing block the target position lies outside the modulo range. - in the traversing block, correct the target position.
the modulo range Alarm value (r2124, interpret decimal): - change the modulo range (p2576).
Number of the traversing block with illegal target position.

Sinamics G130 A07472 EPOS: Traversing block ABS_POS/ABS_NEG not In the traversing block the positioning mode ABS_POS or ABS_NEG were Correct the traversing block.
possible parameterized with the modulo correction
not activated.
Alarm value (r2124, interpret decimal):
Number of the traversing block with the illegal positioning mode.

Sinamics G130 A07473 (F) EPOS: Beginning of traversing range reached When traversing, the axis has moved to the traversing range limit. Move away in the positive direction.

Sinamics G130 A07474 (F) EPOS: End of traversing range reached When traversing, the axis has moved to the traversing range limit. Move away in the negative direction.
Sinamics G130 A07477 (F) EPOS: Target position < software limit switch In the current traversing operation, the target position is less than the - correct the target position.
minus software limit switch minus. - change software limit switch minus (CI: p2578, p2580).
Sinamics G130 A07478 (F) EPOS: Target position > software limit switch In the current traversing operation, the target position is greater than the - correct the target position.
plus software limit switch plus. - change software limit switch plus (CI: p2579, p2581).
Sinamics G130 A07479 EPOS: Software limit switch minus reached The axis is at the position of the software limit switch minus. An active - correct the target position.
traversing block was interrupted. - change software limit switch minus (CI: p2578, p2580).
Sinamics G130 A07480 EPOS: Software limit switch plus reached The axis is at the position of the software limit switch plus. An active - correct the target position.
traversing block was interrupted. - change software limit switch plus (CI: p2579, p2581).
Sinamics G130 A07483 EPOS: Travel to fixed stop clamping torque not The fixed stop in the traversing block was reached without the clamping - Check the maximum torque-generating current (r1533).
reached torque/clamping force having been achieved. - check the torque limits (p1520, p1521).
- check the power limits (p1530, p1531).
- check the BICO interconnections of the torque limits (p1522, p1523, p1528,
p1529).

Sinamics G130 A07486 EPOS: Intermediate stop missing In the modes "traversing blocks" or "direct setpoint input/MDI" at the start Connect a 1 signal to the binector input "no intermediate stop/intermediate
of motion, the binector input "no intermediate stop" (BI: p2640) and re-start motion.
stop/intermediate stop" (BI: p2640) did not have a 1 signal.

Sinamics G130 A07487 EPOS: Reject traversing task missing In the modes "traversing blocks" or "direct setpoint input/MDI" at the start Connect a 1 signal to the binector input "do not reject traversing task/reject
of motion, the binector input "do not reject traversing task" (BI: p2641) and re-start
traversing task/reject traversing task" (BI: p2641) does not have a 1 signal. motion.

Sinamics G130 A07489 EPOS: Reference point correction outside the For the function "flying referencing" the difference between the measured - check the mechanical system.
window position at the measuring probe and the - check the parameterization of the window (p2602).
reference point coordinate lies outside the parameterized window.

Sinamics G130 A07495 (F) LR: Reference function interrupted An activated reference function (reference mark search or measuring - check the causes and resolve.
probe evaluation) was interrupted. - reset the control (BI: p2508 and BI: p2509 = 0 signal) and activate the
- an encoder fault has occurred (Gn_ZSW.15 = 1). requested function.
- position actual value was set during an activated reference function.
- simultaneously activate reference mark search and measuring probe
evaluation (BI: p2508 and BI: p2509 = 1 signal).
- activated reference function (reference mark search or measuring probe
evaluation) was de-activated (BI: p2508
and BI: p2509 = 0 signal).

Sinamics G130 A07496 EPOS: Enable not possible It is not possible to enable the basic positioner because at least one signal Check the appropriate binector inputs and signals.
is missing.
Alarm value (r2124, interpret decimal):
1: EPOS enable missing (BI: p2656).
2: Position actual value, valid feedback signal missing (BI: p2658).

Sinamics G130 A07497 LR: Position setting value activated The position actual value is set to the value received via CI: p2515while BI: None necessary.
p2514 = 1 signal. A possible system The alarm automatically disappears with BI: p2514 = 0 signal.
deviation cannot be corrected.

Sinamics G130 A07498 (F) LR: Measuring probe evaluation not possible When evaluating the measuring probe, an error occurred. De-activate the measuring probe evaluation (BI: p2509 = 0 signal).
Alarm value (r2124, interpret decimal): Re alarm value = 6:
6: The input terminal for the measuring probe is not set. Set the input terminal for the measuring probe (p0488, p0489 or p2517, p2518).
4098: Error when initializing the measuring probe. Re alarm value = 4098:
4100: The measuring pulse frequency is too high. Check the Control Unit hardware.
> 50000: The measuring clock cycle is not a multiple integer of the position Re alarm value = 4100:
controller clock cycle. Reduce the frequency of the measuring pulses at the measuring probe.
Re alarm value > 50000:
Set the clock cycle ratio of the measuring clock cycle to the position controller
clock cycle to an integer multiple.
To do this, the currently effective measuring clock cycle can be determined from
the alarm value as follows:
Tmeas[125μs] = alarm value - 50000.
With PROFIBUS, the measuring clock cycle corresponds to the PROFIBUS clock
cycle r2064[1].
Without PROFIBUS, the measuring clock cycle is an internal cycle time that
cannot be influenced.

Sinamics G130 A07504 Drive: Motor data set is not assigned to a drive A motor data set is not assigned to a drive object. In the drive data sets, assign the non-assigned motor data set using the MDS
data set All of the existing motor data sets in the drive data sets must be assigned number (p0186[0...n]).
using the MDS number (p0186[0...n]). - check whether all of the motor data sets are assigned to drive data sets.
There must be at least as many drive data sets as motor data sets. - if required, delete superfluous motor data sets.
Alarm value (r2124, interpret decimal): - if required, set up new drive data sets and assign to the corresponding motor
Number of the motor data set that has not been assigned. data sets.
See also: p0186 (Motor Data Sets (MDS) number)
Sinamics G130 A07514 (N) Drive: Data structure does not correspond to The interface mode "SIMODRIVE 611 universal" was set (p2038 = 1) and - structure the data according to the rules of the "SIMODRIVE 611 universal"
the interface module the data structure does not correspond to interface mode.
this mode. - check the interface mode (p2038).C179
For the data structure, the following rule must be complied with.
Within the group of 8 drive data sets, the assignment to the motor data set
must be set the same:
p0186[0] = p0186[1] = ... = p0186[7]
p0186[8] = p0186[9] = ... = p0186[15]
p0186[16] = p0186[17] = ... = p0186[23]
p0186[24] = p0186[25] = ... = p0186[31]
See also: p0180 (Number of Drive Data Sets (DDS)), p0186 (Motor Data Sets
(MDS) number), p2038 (PROFIdrive
STW/ZSW interface mode)

Sinamics G130 A07519 Drive: Motor changeover incorrectly With the setting p0833.0 = 1, a motor changeover via the application is - parameterize the appropriate motor data sets differently (p0827).
parameterized selected. This is the reason that p0827 must - select the setting p0833.0 = 0 (motor changeover via the drive).
have different values in the appropriate motor data set.
Alarm value (r2124, interpret hexadecimal):
xxxxyyyy:
xxxx: First MDS, yyyy: Second MDS

Sinamics G130 A07520 Drive: Motor cannot be changed over The motor cannot be changed over. Re alarm value = 1:
Alarm value (r2124, interpret decimal): Set the speed lower than the speed at the start of field weakening (r0063 <
1: p0348).
The contactor for the motor that is presently active cannot be opened, Re alarm value = 2, 3:
because for a synchronous motor, the speed Check the feedback signals of the contactor involved.
(r0063) is greater than the speed at the start of field weakening (p3048). As
long as r0063 > p0348, the current in
the motor does not decay in spite of the pulses being suppressed.
2:
The "contactor opened" feedback signal was not detected within 1 s.
3:
The "contactor closed" feedback signal was not detected within 1 s.

Sinamics G130 A07530 Drive: Drive Data Set DDS not present The selected drive data set is not available (p0837 > p0180). The drive data - select the existing drive data set.
set was not changed over. - set up additional drive data sets.C182
See also: p0180, p0820, p0821, p0822, p0823, p0824, r0837

Sinamics G130 A07541 Drive: Data set changeover not possible The selected drive data set changeover and the assigned motor changeover Reduce the speed below the speed at the start of field weakening.
are not possible and are not carried out.
For synchronous motors, the motor contactor may only be switched for
actual speeds less than the speed at the start
of field weakening (r0063 < p0348).
See also: r0063 (Actual speed value)

Sinamics G130 A07550 (F,N) Drive: Not possible to reset encoder When carrying out a factory setting (e.g. using p0970 = 1), it was not - repeat the operation.
parameters possible to reset the encoder parameters. The - check the DRIVE-CLiQ connection.
encoder parameters are directly read out of the encoder via DRIVE-CLiQ.
Alarm value (r2124, interpret decimal):
Component number of the encoder involved.

Sinamics G130 A07557 (F) Encoder 1: Reference point coordinate not in The reference point coordinate received when adjusting the encoder via Set the reference point coordinate less than the value from the supplementary
the permissible range connector input CI:p2599 lies outside the information.
half of the encoder range and cannot be set as current axis position. The
maximum permissible value is displayed
in the supplementary information.

Sinamics G130 A07558 (F) Encoder 2: Reference point coordinate not in The reference point coordinate received when adjusting the encoder via Set the reference point coordinate less than the value from the supplementary
the permissible range connector input CI:p2599 lies outside the information.
half of the encoder range and cannot be set as current axis position. The
maximum permissible value is displayed
in the supplementary information.

Sinamics G130 A07559 (F) Encoder 3: Reference point coordinate not in The reference point coordinate received when adjusting the encoder via Set the reference point coordinate less than the value from the supplementary
the permissible range connector input CI:p2599 lies outside the information.
half of the encoder range and cannot be set as current axis position. The
maximum permissible value is displayed
in the supplementary information.

Sinamics G130 A07565 (F,N) Drive: Encoder error in PROFIdrive encoder An encoder error was signaled for encoder 1 via the PROFIdrive encoder Acknowledge the encoder error using the encoder control word (G1_STW.15 =
interface 1 interface (G1_ZSW.15). 1).
Alarm value (r2124, interpret decimal):
Error code from G1_XIST2, refer to the description regarding r0483.
Note:
This alarm is only output if p0480[0] is not equal to zero.
Sinamics G130 A07566(F,N) Drive: Encoder error in PROFIdrive encoder An encoder error was signaled for encoder 2 via the PROFIdrive encoder Acknowledge the encoder error using the encoder control word (G2_STW.15 =
interface 2 interface (G2_ZSW.15). 1).
Alarm value (r2124, interpret decimal):
Error code from G2_XIST2, refer to the description regarding r0483.
Note:
This alarm is only output if p0480[1] is not equal to zero.

Sinamics G130 A07567 Drive: Encoder error in PROFIdrive encoder An encoder error was signaled for encoder 3 via the PROFIdrive encoder Acknowledge the encoder error using the encoder control word (G3_STW.15 =
interface 3 interface (G3_ZSW.15). 1).
Alarm value (r2124, interpret decimal):
Error code from G3_XIST2, refer to the description regarding r0483.
Note:
This alarm is only output if p0480[2] is not equal to zero.

Sinamics G130 A07569 (F) Encoder could not be identified During encoder identification (servicing) with p0400 = 10100, the encoder - Check and, if necessary, connect the encoder and/or encoder cable.
could not be identified. - Check and, if necessary, establish the DRIVE-CLiQ connection.
Either the wrong encoder has been installed or no encoder has been - In the case of encoders that cannot be identified (e.g. encoders without EnDat
installed, the wrong encoder cable has been interface), the correct encoder type
connected or no encoder cable has been connected, or the DRIVE-CLiQ must be entered in p0400.
component has not been connected to
DRIVE-CLiQ.
Note:
Encoder identification must be supported by the encoder and is possible in
the following cases:
Encoder with EnDat interface, motor with DRIVE-CLiQ.

Sinamics G130 A07576 Drive: Encoderless operation due to a fault Encoderless operation is active due to a fault (r1407.13). Acknowledge the encoder error using the encoder control word (G3_STW.15 =
active The required response when an encoder fault occurs is parameterized in 1).
p0491.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 A07577 (F) Encoder 1: Measuring probe evaluation not When evaluating the measuring probe, an error occurred. Acknowledge the encoder error using the encoder control word (G3_STW.15 =
possible Alarm value (r2124, interpret decimal): 1).
6: The input terminal for the measuring probe is not set.
4098: Error when initializing the measuring probe.
4100: The measuring pulse frequency is too high.
4200: The PROFIBUS clock cycle is not a multiple of integer of the position
controller clock cycle.

Sinamics G130 A07578(F) Encoder 2: Measuring probe evaluation not When evaluating the measuring probe, an error occurred. De-activate the measuring probe evaluation (BI: p2509 = 0 signal).
possible Alarm value (r2124, interpret decimal): Re alarm value = 6:
6: The input terminal for the measuring probe is not set. Set the input terminal for the measuring probe (p0488, p0489 or p2517, p2518).
4098: Error when initializing the measuring probe. Re alarm value = 4098:
4100: The measuring pulse frequency is too high. Check the Control Unit hardware.
4200: The PROFIBUS clock cycle is not a multiple of integer of the position Re alarm value = 4100:
controller clock cycle. Reduce the frequency of the measuring pulses at the measuring probe.
Re alarm value = 4200:
Set the clock cycle ratio between the PROFIBUS clock cycle and the position
controller clock cycle to an integer multiple.

Sinamics G130 A07579 (F) Encoder could not be identified During encoder identification (servicing) with p0400 = 10100, the encoder - Check and, if necessary, connect the encoder and/or encoder cable.
could not be identified. - Check and, if necessary, establish the DRIVE-CLiQ connection.
Either the wrong encoder has been installed or no encoder has been - In the case of encoders that cannot be identified (e.g. encoders without EnDat
installed, the wrong encoder cable has been interface), the correct encoder type
connected or no encoder cable has been connected, or the DRIVE-CLiQ must be entered in p0400.
component has not been connected to
DRIVE-CLiQ.
Note:
Encoder identification must be supported by the encoder and is possible in
the following cases:
Encoder with EnDat interface, motor with DRIVE-CLiQ.

Sinamics G130 A07580 (F,N) Drive: No Sensor Module with matching A Sensor Module with the component number specified in p0141 was not Correct parameter p0141.
component number found.
Alarm value (r2124, interpret decimal):
Encoder data set involved (index of p0141).

Sinamics G130 A07581 (F) Encoder 1: Position actual value preprocessing An error has occurred during the position actual value preprocessing. Check the encoder for the position actual value preprocessing.
error
Sinamics G130 A07582 (F) Encoder 2: Position actual value preprocessing An error has occurred during the position actual value preprocessing. Check the encoder for the position actual value preprocessing.
error
Sinamics G130 A07583 (F) Encoder 3: Position actual value preprocessing An error has occurred during the position actual value preprocessing. Check the encoder for the position actual value preprocessing.
error
Sinamics G130 A07584 Encoder 1: Position setting value activated The position actual value is set to the value received via CI: p2515while BI: None necessary.
p2514 = 1 signal. A possible system The alarm automatically disappears with BI: p2514 = 0 signal.
deviation cannot be corrected.
Sinamics G130 A07585 Encoder 2: Position setting value activated The position actual value is set to the value received via CI: p2515while BI: None necessary.
p2514 = 1 signal. A possible system The alarm automatically disappears with BI: p2514 = 0 signal.
deviation cannot be corrected.

Sinamics G130 A07586 Encoder 3: Position setting value activated The position actual value is set to the value received via CI: p2515while BI: None necessary.
p2514 = 1 signal. A possible system The alarm automatically disappears with BI: p2514 = 0 signal.
deviation cannot be corrected.

Sinamics G130 A07587 Encoder 1: Position actual value preprocessing The following problem has occurred during the position actual value Check the drive data sets, encoder data sets.
does not have a valid encoder preprocessing. See also: p0187 (Encoder 1 encoder data set number), p0188 (Encoder 2
- an encoder data set has been assigned, however, the encoder data set encoder data set number), p0189
does not contain any encoder data (p0400 (Encoder 3 encoder data set number), p0400 (Encoder type selection)
= 0) or invalid data (e.g. p0408 = 0).

Sinamics G130 A07588 Encoder 2: Position actual value preprocessing The following problem has occurred during the position actual value Check the drive data sets, encoder data sets.
does not have a valid encoder preprocessing. See also: p0187 (Encoder 1 encoder data set number), p0188 (Encoder 2
- an encoder data set has been assigned, however, the encoder data set encoder data set number), p0189
does not contain any encoder data (p0400 (Encoder 3 encoder data set number), p0400 (Encoder type selection)
= 0) or invalid data (e.g. p0408 = 0).

Sinamics G130 A07589 Encoder 3: Position actual value preprocessing The following problem has occurred during the position actual value Check the drive data sets, encoder data sets.
does not have a valid encoder preprocessing. See also: p0187 (Encoder 1 encoder data set number), p0188 (Encoder 2
- an encoder data set has been assigned, however, the encoder data set encoder data set number), p0189
does not contain any encoder data (p0400 (Encoder 3 encoder data set number), p0400 (Encoder type selection)
= 0) or invalid data (e.g. p0408 = 0).

Sinamics G130 A07590 (F) Encoder 1: Drive Data Set changeover in A Drive Data Set changeover (DDS) with a change of the mechanical To changeover the drive data set, initially, exit the "operation" mode.
operation relationships and the encoder assignment
(p2502) was requested in operation.

Sinamics G130 A07591 (F) Encoder 2: Drive Data Set changeover in A Drive Data Set changeover (DDS) with a change of the mechanical To changeover the drive data set, initially, exit the "operation" mode.
operation relationships and the encoder assignment
(p2502) was requested in operation.

Sinamics G130 A07592 (F) Encoder 3: Drive Data Set changeover in A Drive Data Set changeover (DDS) with a change of the mechanical To changeover the drive data set, initially, exit the "operation" mode.
operation relationships and the encoder assignment
(p2502) was requested in operation.

Sinamics G130 A07593 (F) Encoder 1: Value range for position actual The value range (-2147483648 ... 2147483647) for the position actual value If required, reduce the traversing range or position resolution.
value exceeded representation was exceeded. Re alarm value = 3:
When the overflow occurs, the "referenced" or "adjustment absolute Reducing the position resolution and conversion factor:
measuring system" status is reset. - reduce the length unit (LU) per load revolution for rotary encoders (p2506).
Fault value (r0949, interpret decimal): - increase the fine resolution of absolute position actual values (p0419).
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.

Sinamics G130 A07594 (F) Encoder 2: Value range for position actual The value range (-2147483648 ... 2147483647) for the position actual value If required, reduce the traversing range or position resolution.
value exceeded representation was exceeded. Re alarm value = 3:
When the overflow occurs, the "referenced" or "adjustment absolute Reducing the position resolution and conversion factor:
measuring system" status is reset. - reduce the length unit (LU) per load revolution for rotary encoders (p2506).
Fault value (r0949, interpret decimal): - increase the fine resolution of absolute position actual values (p0419).
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.

Sinamics G130 A07595 (F) Encoder 3: Value range for position actual The value range (-2147483648 ... 2147483647) for the position actual value If required, reduce the traversing range or position resolution.
value exceeded representation was exceeded. Re alarm value = 3:
When the overflow occurs, the "referenced" or "adjustment absolute Reducing the position resolution and conversion factor:
measuring system" status is reset. - reduce the length unit (LU) per load revolution for rotary encoders (p2506).
Fault value (r0949, interpret decimal): - increase the fine resolution of absolute position actual values (p0419).
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.
Sinamics G130 A07596 (F) Encoder 1: Reference function interrupted An activated reference function (reference mark search or measuring - check the causes and resolve.
probe evaluation) was interrupted. - reset the control (BI: p2508 and BI: p2509 = 0 signal) and activate the
- an encoder fault has occurred (Gn_ZSW.15 = 1). requested function.
- position actual value was set during an activated reference function.
- simultaneously activate reference mark search and measuring probe
evaluation (BI: p2508 and BI: p2509 = 1 signal).
- activated reference function (reference mark search or measuring probe
evaluation) was de-activated (BI: p2508
and BI: p2509 = 0 signal).

Sinamics G130 A07597 (F) Encoder 2: Reference function interrupted An activated reference function (reference mark search or measuring - check the causes and resolve.
probe evaluation) was interrupted. - reset the control (BI: p2508 and BI: p2509 = 0 signal) and activate the
- an encoder fault has occurred (Gn_ZSW.15 = 1). requested function.C213
- position actual value was set during an activated reference function.
- simultaneously activate reference mark search and measuring probe
evaluation (BI: p2508 and BI: p2509 = 1 signal).
- activated reference function (reference mark search or measuring probe
evaluation) was de-activated (BI: p2508
and BI: p2509 = 0 signal).

Sinamics G130 A07598 (F) Encoder 3: Reference function interrupted An activated reference function (reference mark search or measuring - check the causes and resolve.
probe evaluation) was interrupted. - reset the control (BI: p2508 and BI: p2509 = 0 signal) and activate the
- an encoder fault has occurred (Gn_ZSW.15 = 1). requested function.C214
- position actual value was set during an activated reference function.
- simultaneously activate reference mark search and measuring probe
evaluation (BI: p2508 and BI: p2509 = 1 signal).
- activated reference function (reference mark search or measuring probe
evaluation) was de-activated (BI: p2508
and BI: p2509 = 0 signal).

Sinamics G130 A07805 (N) Drive: Power unit overload I2t Alarm threshold for I2t overload (p0294) of the power unit exceeded. - reduce the continuous load.
The response parameterized in p0290 becomes active. - adapt the load duty cycle.
See also: p0290 (Power unit overload response) - check the assignment of the rated currents of the motor and Motor Module.

Sinamics G130 A07820 Drive: Temperature sensor not connected The temperature sensor for motor temperature monitoring, specified in - connect the module with temperature sensor.
p0600, is not available. - set the available temperature sensor (p0600, p0601).
- parameter download with "incorrect" setting. See also: p0600 (Motor temperature sensor for monitoring), p0601 (Motor
- module with sensor evaluation has been, in the meantime, been temperature sensor type)
removed.
- temperature sensor via Motor Module, not for CU310.

Sinamics G130 A07825 (N) Drive: Simulation mode activated The simulation mode is activated. The alarm automatically disappears if simulation mode is de-activated with
The drive can only be powered up if the DC link voltage is less than 40 V. p1272 = 0.

Sinamics G130 A07850 (F) External alarm 1 The BICO signal for "external alarm 1" was triggered. Eliminate the causes of this alarm.
The condition for this external alarm is fulfilled.
See also: p2112 (External alarm 1)

Sinamics G130 A07851 (F) External alarm 2 The BICO signal for "external alarm 2" was triggered. Eliminate the causes of this alarm.
The condition for this external alarm is fulfilled.
See also: p2116 (External alarm 2)

Sinamics G130 A07852 (F) External alarm 3 The BICO signal for "external alarm 3" was triggered. Eliminate the causes of this alarm.
The condition for this external alarm is fulfilled.
See also: p2117 (External alarm 3)

Sinamics G130 A07903 Drive: Motor speed deviation The absolute value of the speed difference from the two setpoints (p2151, - increase p2163 and/or p2166.
p2154) and the speed actual value (r2169) - increase the torque/current/power limits.
exceeds the tolerance threshold (p2163) longer than tolerated (p2164, - enable the speed controller.
p2166). - for closed-loop torque control: The speed setpoint should track the speed
The alarm is only enabled for p2149.0 = 1. actual value.
Possible causes could be: - correct the encoder pulse number in p0408 or mount the correct tachometer.
- the load torque is greater than the torque setpoint.
- when accelerating, the torque/current/power limit is reached. If the limits
are not sufficient, then it is possible that
the drive has been dimensioned too small.
- the speed controller is inhibited (refer to p0856; refer to Kp/Tn adaptation
of the speed controller).
- for closed-loop torque control, the speed setpoint does not track the
speed actual value.
- for active Vdc controller.
- the encoder pulse number was incorrectly parameterized (p0408).
Sinamics G130 A07904 (N) External armature short-circuit: Contactor When closing, the contactor feedback signal (p1235) did not issue the - check that the contactor feedback signal is correctly connected (p1235).
feedback signal "Closed" missing signal "Closed" (r1239.1 = 1) within the monitoring - check the logic of the contactor feedback signal (r1239.1 = 1: "Closed", r1239.1
time (p1236). = 0: "Open").
- increase the monitoring time (p1236).
- if required, set the external armature short-circuit without contactor feedback
signal (p1231=2).

Sinamics G130 A07908 Internal armature short-circuit active The Motor Module signals that the motor is short-circuited through the For synchronous motors, the armature short-circuit braking is activated if a 1
power semiconductors (r1239.5 = 1). The signal is present via binector input
pulses cannot be enabled. The internal armature short-circuit is selected p1230.
(p1231 = 4): See also: p1230 (Armature short-circuit / DC brake activation), p1231 (Armature
short-circuit / DC brake configuration)

Sinamics G130 A07910 (N) Drive: Motor overtemperature KTY: - check the motor load.
The motor temperature has exceeded the fault threshold (p0604 or - check the motor ambient temperature.
p0616). - check KTY84.
VECTOR: The response parameterized in p0610 becomes active.
PTC:
The response threshold of 1650 Ohm was exceeded.
Alarm value (r2124, interpret decimal):
SME not selected in p0601:
1: No output current reduction.
2: Output current reduction active.
SME selected in p0601 (p0601 = 10):
The number specifies the sensor channel that resulted in the alarm being
output.
See also: p0604 (Motor overtemperature alarm threshold), p0610 (Motor
overtemperature response)

Sinamics G130 A07918 (N) Three-phase setpoint generator operation Only for separately excited synchronous motors (p0300 = 5): Select another open-loop/closed-loop control mode
selected/active The current open-loop/closed-loop control mode is I/f control (open-loop) See also: p1300 (Open-loop/closed-loop control operating mode)
with a fixed current (p1300 = 18).
The speed is entered via the setpoint channel and the current setpoint is
given by the minimum current (p1620).
It must be ensured that in this mode, the control dynamic performance is
very limited. This is the reason that longer
ramp-up times should be set for the setpoint speed than for normal
operation.
See also: p1620 (Stator current, minimum)

Sinamics G130 A07920 Drive: Torque too low The torque deviates from the torque/speed envelope characteristic in the Adapt the load.
positive direction (too high).
Sinamics G130 A07921 Drive: Torque too high The torque deviates from the torque/speed envelope characteristic in the Adapt the load.
positive direction (too high).
Sinamics G130 A07922 Drive: Torque outside the tolerance The torque deviates from the torque/speed envelope characteristic. Adapt the load.

Sinamics G130 A07926 Drive: Envelope curve, parameter invalid Invalid parameter values were entered for the envelope characteristic of Set the parameters for the load monitoring according to the applicable rules.
the load monitoring.
The following rules apply for the speed thresholds:
p2182 < p2183 < p2184
The following rules apply for the torque thresholds:
p2185 > p2186
p2187 > p2188
p2189 > p2190
Alarm value (r2124, interpret decimal):
Number of the parameter with the invalid value.

Sinamics G130 A07927 DC brake active The motor is braked using DC current - the DC current brake is active. 1) An alarm with alarm response DC brake is active.
The motor is braked with the DC braking current p1232 for the duration in
p1233. If the standstill threshold p1226 is
undershot, then braking is prematurely canceled.
2) The DC braking function was activated at Bico input p1230 for a set DC brake
p1230=4.
Braking current p1232 should be impressed until the Bico activation is canceled
again.

Sinamics G130 A07931 (F,N) Brake does not open This alarm is output for r1229.4 = 1. - check the functionality of the motor holding brake.
See also: p1216 (Motor holding brake, opening time), r1229 (Motor holding - check the feedback signal (p1223).C231
brake status word)

Sinamics G130 A07932 Brake does not close This alarm is output for r1229.5 = 1. - check the functionality of the motor holding brake.
For r1229.5 = 1, OFF/OFF3 are suppressed to prevent the drive accelerating - check the feedback signal (p1222).
by a load that drives the motor -
whereby OFF2 remains effective.
See also: p1217 (Motor holding brake closing time), r1229 (Motor holding
brake status word)
Sinamics G130 A07941 Sync-line-drive: Target frequency not The target frequency is outside the permissible value range. Fulfill the conditions for the target frequency for line-drive synchronization.
permissible Alarm value (r2124, interpret decimal): See also: r1084 (Speed limit positive effective), r1087 (Speed limit negative
1084: Target frequency greater than the positive speed limit, f_sync > effective)
f_max (r1084).
1087: Target frequency less than the negative speed limit, f_sync < f_min
(r1087).

Sinamics G130 A07942 Sync-line-drive: Setpoint frequency is There is a considerable difference between the setpoint frequency and the The alarm automatically disappears after the difference that can be tolerated
completely different than the target frequency target frequency (f_set <> f_target). The between the setpoint and target frequencies
deviation that can be tolerated is set in p3806. (p3806) is reached.
See also: p3806 (Sync-line-drive frequency difference threshold value)

Sinamics G130 A07943 Sync-line-drive: Synchronization not permitted Synchronization is not permitted. Fulfill the conditions for the line-drive synchronization.
Alarm value (r2124, interpret decimal): Re alarm value = 1300:
1300: The control mode (p1300) has not been set to encoderless closed- Set the control mode (p1300) to encoderless closed-loop speed control (p1300 =
loop speed control or V/f characteristic. 20) or V/f characteristic (p1300 =
1910: Motor data identification activated. 0 ... 19).
1960: Speed controller optimization activated. Re alarm value = 1910:
1990: Encoder adjustment activated. Exit the motor data identification routine (p1910).
3801: Voltage Sensing Module (VSM) not found. Re alarm value = 1960:
3845: Friction characteristic record activated. Exist the speed controller optimization routine (p1960).
Re alarm value = 1990:
Exit the encoder adjustment (p1990).
Re alarm value = 3801:
Connect-up a Voltage Sensing Module (VSM) and when connecting to an
adjacent drive object ensure that the drive
objects have the same basis clock cycle.
Re alarm value = 3845:
Exit the friction characteristic record (p3845).

Sinamics G130 A07960 Drive: Incorrect friction characteristic The friction characteristic is incorrect. Fulfill the conditions for the friction characteristic.
Alarm value (r2124, interpret decimal): Re alarm value = 1538:
1538: Check the upper effective torque limit (e.g. in the field weakening range).
The friction torque is greater than the maximum from the upper effective Re alarm value = 1539:
torque limit (p1538) and zero. This is the Check the lower effective torque limit (e.g. in the field weakening range).
reason that the output of the friction characteristic (r3841) is limited to this Re alarm value = 3820 ... 3839:
value. Fulfill the conditions to set the parameters of the friction characteristic.
If the motor data (e.g. the maximum speed p0322) are changed during
commissioning (p0010 = 1, 3), then the technological
limits and threshold values, dependent on this, must be re-calculated by
selecting p0340= 5).

Sinamics G130 A07961 Drive: Friction characteristic record activated The automatic friction characteristic record is activated. None necessary.
The friction characteristic is recorded at the next power-on command. The alarm disappears automatically after the friction characteristic record has
been successfully completed or the
record is de-activated (p3845 = 0).

Sinamics G130 A07971 (N) Drive: Angular commutation offset The automatic determination of the angular commutation offset (encoder None necessary.
determination activated adjustment) is activated (p1990 = 1). The alarm automatically disappears after determination or for the setting p1990
The automatic determination is carried out with the next power-on = 0.
command.
For SERVO and fault F07414 present, the following applies:
The determination of the angular commutation offset is automatically
activated (p1990 = 1), if a pole position identification
technique is set in p1980.
See also: p1990 (Encoder adjustment, determine angular commutation
offset)

Sinamics G130 A07980 Drive: Rotating measurement activated The rotating measurement (automatic speed controller optimization) is None necessary.
activated. The alarm disappears automatically after the speed controller optimization has
The rotating measurement is carried out at the next power-on command. been successfully completed or for
See also: p1960 (Rotating measurement selection) the setting p1900 = 0.
Drive: Enable signals for the rotating measurement missing

Sinamics G130 A07981 Drive: Enable signals for the rotating The rotating measurement cannot be started due to missing enable signals. - acknowledge faults that are present.
measurement missing - establish missing enable signals.
See also: r0002, r0046

Sinamics G130 A07987 Drive: Rotating measurement, no encoder No encoder available. The rotating measurement was carried out without Connect encoder or select p1960 = 1, 3.
available encoder.
Sinamics G130 A07991 (N) Drive: Motor data identification activated The motor data ident. routine is activated. None necessary.
The motor data identification routine is carried out at the next power-on The alarm automatically disappears after the motor data identification routine
command. has been successfully completed or
See also: p1910 (Motor data identification selection) for the setting p1900 = 0.
Sinamics G130 A08504 (F) COMM BOARD: Internal cyclic data transfer The cyclic actual and/or setpoint values were not transferred within the Check the parameterizing telegram (Ti, To, Tdp, etc.).
error specified times.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.

Sinamics G130 A08511 (F) COMM BOARD: Receive configuration data The drive unit did not accept the receive configuration data. Check the receive configuration data.
invalid Alarm value (r2124, interpret decimal): Re alarm value = 1:
Return value of the receive configuration data check. Check the list of the drive objects with process data exchange (p0978). With
0: Configuration accepted. p0978[x] = 0, all of the following drive
1: Connection established to more drive objects than configured in the objects in the list are excluded from the process data exchange.
device. The drive objects for process data
exchange and their sequence were defined using p0978.
2: Too many data words for input or output to a drive object. A max. of 16
words is permitted for SERVO and VECTOR;
a max. of 5 words for A_INF, TB30, TM31 and CU320.
3: Uneven number of bytes for input or output.
4: Setting data for synchronization not accepted.
5: Drive still not in cyclic operation.
6: Buffer system not accepted.
7: Cyclic channel length too short for this setting.
8: Cyclic channel address not initialized.
9: 3-buffer system not permitted.
10: DRIVE-CLiQ fault.
11: CU-Link fault.
12: CX32 not in cyclic operation.

Sinamics G130 A08520 (F) COMM BOARD: Non-cyclic channel error The memory or the buffer status of the non-cyclic channel has an error. Check communication line.
Alarm value (r2124, interpret decimal):
0: Error in the buffer status.
1: Error in the memory.

Sinamics G130 A08526 (F) COMM BOARD: No cyclic connection There is no cyclic connection to the control. 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).

Sinamics G130 A08530 (F) COMM BOARD: Message channel error The memory or the buffer status of the message channel has an error. Check communication line.
Alarm value (r2124, interpret decimal):
0: Error in the buffer status.
1: Error in the memory.

Sinamics G130 A08550 PZD Interface Hardware assignment error The assignment of the hardware to the PZD interface has been incorrectly Correct the parameterization (p8839).
parameterized.
Alarm value (r2124, interpret decimal):
1: Only one of the two indices is not equal to 99 (automatic).
2: Both PZD interfaces are assigned to the same hardware.
3: Assigned COMM BOARD missing.
4: CBC10 is assigned to interface 1.
See also: p8839 (PZD interface hardware assignment)

Sinamics G130 A08751 CBC: Telegram loss The error counter for the send or receive telegrams has exceeded the value Reduce the cycle times of the receive messages.
127.
Sinamics G130 A08752 CBC: Error counter for error passive exceeded The error counter for the send or receive telegrams has exceeded the value - check the bus cable
127. - set a higher baud rate (p8622).
- check the bit timing and if required optimize (p8623).
See also: p8622 (CBC baud rate), p8623 (CBC bit timing selection)

Sinamics G130 A08753 CBC: Message buffer overflow A message buffer overflow. Check the bus cable.
Alarm value (r2124, interpret decimal): Set a higher baud rate (p8622).
1: Non-cyclic send buffer (SDO response buffer) overflow. Check the bit timing and if required optimize (p8623).
2: Non-cyclic receive buffer (SDO receive buffer) overflow. Re alarm value = 2:
3: Cyclic send buffer (PDO send buffer) overflow. - reduce the cycle times of the SDO receive messages.
See also: p8622 (CBC baud rate), p8623 (CBC bit timing selection)

Sinamics G130 A08754 CBC: Incorrect communications mode In the "operational" mode, an attempt was made to change parameters Change to the "pre-operational" or "stopped" mode.
p8700 ... p8737.
Sinamics G130 A08755 CBC: Obj cannot be mapped The CANopen object is not provided for the Process Data Object (PDO) Use a CANopen object intended for the PDO mapping or enter 0.
Mapping. The following objects can be mapped in the Receive Process Data Object (RPDO)
or Transmit Process Data Object
(TPDO):
- RPDO: 6040 hex, 6060 hex, 60FF hex, 6071 hex; 5800 hex - 580F hex; 5820 hex
- 5827 hex
- TPDO: 6041 hex, 6061 hex, 6063 hex, 6069 hex, 606B hex, 606C hex, 6074 hex;
5810 hex - 581F hex; 5830 hex
- 5837 hex
Only sub-index 0 of the specified objects can be mapped.
Note:
As long as A08755 is present, the COB-ID cannot be set to valid.

Sinamics G130 A08756 CBC: Number of mapped bytes exceeded The number of bytes of the mapped objects exceeds the telegram size for Map fewer objects or objects with a smaller data type.
net data. A max. of 8 bytes is permissible. See also: p8710, p8711, p8712, p8713, p8714, p8715, p8716, p8717, p8730,
p8731, p8732, p8733, p8734, p8735,
p8736, p8737

Sinamics G130 A08757 CBC: Set COB-ID invalid For online operation, the appropriate COB-ID must be set invalid before Set the COB-ID to invalid.
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

Sinamics G130 A08758 CBC: Number of PDO channels too low The number of PDO channels in p8740 has either been set to 0 or too low. The number of channels set in p8740 must be greater than or equal to the
See also: p8740 (CBC channel assignment) number of PDOs.
There are 2 possibilities:
Increase the number of channels in p8740 and confirm the selection using
p8741.
Reduce the number of PDOs by setting the COB-ID to invalid.
See also: p8740 (CBC channel assignment), p8741 (CBC PDO configuration
acknowledgement)

Sinamics G130 A08759 CBC: PDO COB-ID already available An existing PDO COB-ID was allocated. Select another PDO COB-ID.
Sinamics G130 A13000 Select another PDO COB-ID. - for the drive unit, the options that require a license are being used but the Re alarm value = 0:
licenses are not sufficient. Additional licenses are required and these must be activated (p9920, p9921).
- an error occurred when checking the existing licenses. Re alarm value = 1:
Alarm value (r2124, interpret decimal): With the system powered down, re-insert the memory card that matches the
0: system.
The existing license is not sufficient. Re alarm value = 2:
1: Enter and activate the license key (p9920, p9921).
An adequate license was not able to be determined as the memory card Re alarm value = 3:
with the required licensing data was withdrawn Compare the license key (p9920) entered with the license key on the certificate
in operation. of license.
2: Re-enter the license key and activate (p9920, p9921).
An adequate license was not able to be determined, as an error occurred Re alarm value = 4:
when reading-out the required licensing - carry out a POWER ON.
data from the memory card. - upgrade firmware to later version.
3: - contact the Hotline.
An adequate license was not able to be determined as there is a checksum
error in the license key.
4:
An internal error occurred when checking the license.

Sinamics G130 A13001 Error in license checksum When checking the checksum of the license key, an error was detected. Compare the license key (p9920) entered with the license key on the certificate
of license.
Re-enter the license key and activate (p9920, p9921).

Sinamics G130 A30010 (F) Power unit: Sign-of-life error cyclic data A DRIVE-CLiQ communication error has occurred between the Control Unit check the electrical cabinet design and cable routing for EMC compliance
and the power unit involved.
The cyclic setpoint telegrams of the Control Unit were not received on time
by the power unit for at least one clock
cycle.

Sinamics G130 A30016 (N) Power unit: Load supply switched out The following applies for CU31x and CUA31: The following applies for CU31x and CUA31:
The DC link voltage is too low. Under certain circumstances, the AC line supply is not switched in.
Fault value (r0949, interpret decimal):
DC link voltage in [V].

Sinamics G130 A30023 Power unit: Overtemperature thermal model The temperature difference between the heat sink and chip has exceeded - adapt the load duty cycle.
alarm the permissible limit value. - check whether the fan is running.
- the permissible load duty cycle was not maintained. - check the fan elements
- insufficient cooling, fan failure. - check whether the ambient temperature is in the permissible range.
- overload. - check the motor load.
- ambient temperature too high. - reduce the pulse frequency if this is higher than the rated pulse frequency.
- pulse frequency too high.
See also: r0037
Sinamics G130 A30031 Power unit: Hardware current limiting, phase U Hardware current limit for phase U responded. The pulsing in this phase is - check the motor data.
inhibited for one pulse period. - check the motor circuit configuration (star-delta).
- closed-loop control is incorrectly parameterized. - check the motor load.
- fault in the motor or in the power cables. - check the power cable connections.
- the power cables exceed the maximum permissible length. - check the power cables for short-circuit or ground fault.
- motor load too high - check the length of the power cables.D268
- power unit defective.
Note:
Alarm A30031 is always output if the hardware current limit for phase U, V
or W on a Power Module responds.

Sinamics G130 A30032 Power unit: Hardware current limiting, phase V Hardware current limit for phase V responded. The pulsing in this phase is - check the motor data.
inhibited for one pulse period. - check the motor circuit configuration (star-delta).
- closed-loop control is incorrectly parameterized. - check the motor load.
- fault in the motor or in the power cables. - check the power cable connections.
- the power cables exceed the maximum permissible length. - check the power cables for short-circuit or ground fault.
- motor load too high - check the length of the power cables.
- power unit defective.
Note:
Alarm A30031 is always output if the hardware current limit for phase U, V
or W on a Power Module responds.

Sinamics G130 A30033 Power unit: Hardware current limiting, phase Hardware current limit for phase W responded. The pulsing in this phase is - check the motor data.
W inhibited for one pulse period. - check the motor circuit configuration (star-delta).
- closed-loop control is incorrectly parameterized. - check the motor load.
- fault in the motor or in the power cables. - check the power cable connections.
- the power cables exceed the maximum permissible length. - check the power cables for short-circuit or ground fault.
- motor load too high - check the length of the power cables.
- power unit defective.
Note:
Alarm A30031 is always output if the hardware current limit for phase U, V
or W on a Power Module responds.

Sinamics G130 A30041 (F) Power unit: Undervoltage 24 V alarm 24 V power supply fault for the power unit. Check the 24 V DC voltage supply to power unit.
- the 16 V threshold was undershot..
Fault value (r0949, interpret decimal):
24 V voltage [1 bit = 0.1 V].

Sinamics G130 A30042 Power unit: Fan operating time reached or The maximum operating time of the fan in the power unit is set in p0252. Replace the fan in the power unit and reset the operating hours counter to 0
exceeded This message indicates the following: (p0251 = 0).
Fault value (r0949, interpret decimal): See also: p0251 (Operating hours counter power unit fan), p0252 (Maximum
0: The maximum fan operating time is 500 hours. operating time power unit fan)
1: The maximum fan operating time has been exceeded.

Sinamics G130 A30044 (F) Power unit: Overvoltage 24 V alarm The following applies for CU31x: Check the 24 V DC voltage supply to power unit.
24 V power supply fault for the power unit.
- the 32.0 V threshold was exceeded.
Fault value (r0949):
24 V voltage [1 bit = 0.1 V].

Sinamics G130 A30046 (F) Power unit: Undervoltage, alarm Before the last new start, a problem occurred at the power unit power Check the 24 V DC power supply for the power unit and if required replace the
supply. module.
- 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.

Sinamics G130 A30073 (N) Actual value/setpoint preprocessing no longer The following applies for CU31x and CUA31: The following applies for CU31x and CUA31:
synchronous to DRIVE-CLiQ Communications to the power unit module are no longer in synchronism Wait until synchronization is re-established.
with DRIVE-CLiQ.

Sinamics G130 A30804 (F) Power unit: CRC CRC error actuator - carry out a POWER ON (power off/on) for all components.
- upgrade firmware to later version.
- contact the Hotline.

Sinamics G130 A30810 (F) Power unit: Watchdog timer When booting it was detected that the cause of the previous reset was an - carry out a POWER ON (power off/on) for all components.
SAC watchdog timer overflow. - upgrade firmware to later version.
- contact the Hotline.

Sinamics G130 A30920 (F) Power unit: Temperature sensor fault When evaluating the temperature sensor, an error occurred. - check that the sensor is connected correctly.
Alarm value (r2124, interpret decimal): - replace sensor.
1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm, PT100: R >
375 Ohm).
2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm, PT100:
R < 30 Ohm).
Sinamics G130 A30999 (F,N) Power unit: Unknown alarm An alarm occurred on the power unit that cannot be interpreted by the - replace the firmware on the power unit by an older firmware version (r0128).
Control Unit firmware. - upgrade the firmware on the Control Unit (r0018).
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.

Sinamics G130 A31400 (F,N) Encoder 1: Alarm threshold zero mark distance The measured zero mark distance does not correspond to the - check that the encoder cables are routed in compliance with EMC.
error parameterized zero mark distance. - check the plug connections.
For distance-coded encoders, the zero mark distance is determined from . check the encoder type (encoder with equidistant zero marks).
zero marks detected pairs. This means that - adapt the parameter for the distance between zero marks (p0424, p0425).
if a zero mark is missing, depending on the pair generation, this cannot - replace the encoder or encoder cable.
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).
Alarm value (r2124, 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.

Sinamics G130 A31401 (F,N) Encoder 1: Alarm threshold zero marked failed The 1.5 x parameterized zero mark distance was exceeded. - check that the encoder cables are routed in compliance with EMC.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary - check the plug connections.
encoder) or p0424 (linear encoder). . check the encoder type (encoder with equidistant zero marks).
Alarm value (r2124, interpret decimal): - adapt the parameter for the distance between zero marks (p0425).
Number of increments after POWER ON or since the last zero mark that - replace the encoder or encoder cable.
was detected (4 increments = 1 encoder
pulse).

Sinamics G130 A31410 (F,N) Encoder 1: Serial communications Serial communication protocol transfer error between the encoder and - check that the encoder cables are routed in compliance with EMC.
evaluation module. - check the plug connections.
Alarm value (r2124, interpret binary): - replace the encoder.
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.

Sinamics G130 A31411 (F,N) Encoder 1: EnDat encoder signals alarms The error word of the EnDat encoder has alarm bits that have been set. Replace encoder.
Alarm value (r2124, interpret binary):
Bit 0: Frequency exceeded (speed too high).
Bit 1: Temperature exceeded.
Bit 2: Control reserve, lighting system exceeded.
Bit 3: Battery discharged.
Bit 4: Reference point passed.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 A31412 (F,N) Encoder 1: Error bit set in the serial protocol The encoder sends a set error bit via the serial protocol. - carry out a POWER ON (power off/on) for all components.
Alarm value (r2124, interpret binary): - check that the encoder cables are routed in compliance with EMC.
Bit 0: Fault bit in the position protocol. - check the plug connections.
Bit 1: Alarm bit in the position protocol. - replace the encoder.
Sinamics G130 A31414 (F,N) Encoder 1: Amplitude error track C or D (C^2 + The amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall - check that the encoder cables are routed in compliance with EMC.
D^2) signals, is not within the tolerance bandwidth. - check the plug connections.
Alarm value (r2124, interpret hexadecimal): - replace the encoder or encoder cable.
yyyyxxxx hex: - check the Sensor Module (e.g. contacts).
yyyy = Signal level, track D (16 bits with sign). - check the Hall sensor box
xxxx = Signal level, track C (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600
mV (500 mV -25/+20 %).
The response thresholds are < 230 mV (observe the frequency response of
the encoder) and > 750 mV.
A signal level of 500 mV peak value corresponds to the numerical value
5333 hex = 21299 dec.
Note:
If the amplitude is not within the tolerance bandwidth, then it cannot be
used to initialize the start position.

Sinamics G130 A31418 (F,N) Encoder 1: Speed difference per sampling rate For an HTL/TTL encoder, the speed difference between two sampling cycles - check the tachometer feeder cable for interruptions.
exceeded has exceeded the value in p0492. - check the grounding of the tachometer shielding.
The change to the averaged speed actual value - if applicable - is monitored - if required, increase the setting of p0492.
in the current controller sampling time.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.
See also: p0492 (Square-wave encoder, maximum speed difference per
sampling cycle)

Sinamics G130 A31419 (F,N) Encoder 1: Track A or B outside the tolerance The amplitude, phase or offset correction for track A or B is at the limit. - check mechanical mounting tolerances for encoders without their own
range Amplitude error correction: Amplitude B / Amplitude A = 0.78 ... 1.27 bearings (e.g. toothed-wheel encoders).
Phase: <84 degrees or >96 degrees - check the plug connections (also the transition resistance).
SMC20: Offset correction: +/-140 mV - check the encoder signals.
SMC10: Offset correction: +/-650 mV - replace the encoder or encoder cable.
Alarm value (r2124, interpret hexadecimal):
xxxx1: Minimum of the offset correction, track B
xxxx2: Maximum of the offset correction, track B
xxx1x: Minimum of the offset correction, track A
xxx2x: Maximum of the offset correction, track A
xx1xx: Minimum of the amplitude correction, track B/A
xx2xx: Maximum of the amplitude correction, track B/A
x1xxx: Minimum of the phase error correction
x2xxx: Maximum of the phase error correction
1xxxx: Minimum of the cubic correction
2xxxx: Maximum of the cubic correction
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 A31421 (F,N) Encoder 1: Coarse position error For the actual value sensing, an error was detected. As a result of this error, Re alarm value = 3:
it must be assumed that the actual value - for a standard encoder with cable, if required, contact the manufacturer.
sensing supplies an incorrect coarse position. - correct the assignment of the tracks to the position value that is serially
Alarm value (r2124, interpret decimal): transferred. To do this, the two tracks must
3: The absolute position of the serial protocol and track A/B differ by half be connected, inverted, at the Sensor Module (interchange A with A* and B with
an encoder pulse. The absolute position B*) or, for a programmable encoder,
must have its zero position in the quadrants in which both tracks are check the zero offset of the position.
negative. In the case of a fault, the position can
be incorrect by one encoder pulse.

Sinamics G130 A31429 (F,N) Encoder 1: Position difference, hall The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° - track C or D not connected.
sensor/track C/D and A/B too large electrical or the error for the Hall signals is greater - correct the direction of rotation of the Hall sensor possibly connected as
than +/-60 ° electrical. equivalent for track C/D.
One period of track C/D corresponds to 360 ° mechanical. - check that the encoder cables are routed in compliance with EMC.
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.
Alarm value (r2124, 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)
Sinamics G130 A31431 (F,N) Encoder 1: Deviation, position When the zero pulse is passed, a deviation in the incremental position was - check that the encoder cables are routed in compliance with EMC.
incremental/absolute too large detected. - check the plug connections.
For equidistant zero marks, the following applies: - replace the encoder or encoder cable.
- The first zero mark passed supplies the reference point for all subsequent - remove any dirt from the coding disk or strong magnetic fields.
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).
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 A31432 (F,N) Encoder 1: Rotor position adaptation corrects For track A/B, pulses have been lost or too many have been counted. These - check that the encoder cables are routed in compliance with EMC.
deviation pulses are presently being corrected. - check the plug connections.
Alarm value (r2124, interpret decimal): Last measured deviation of the zero - replace the encoder or encoder cable.
mark distance in increments (4 increments - check encoder limit frequency.
= 1 encoder pulse). The sign designates the direction of motion when - adapt the parameter for the distance between zero marks (p0424, p0425).
detecting the zero mark distance.

Sinamics G130 A31443 (F,N) Encoder 1: Signal level C/D unipolar outside The unipolar level (CP/CN or DP/DN) for encoder 1 is outside the - check that the encoder cables and shielding are routed in compliance with
tolerance permissible tolerance. EMC.
Alarm value (r2124, interpret binary): - check the plug connections and contacts.
Bit 0 = 1: Either CP or CN outside the tolerance. - are the C/D tracks connected correctly (have the signal lines CP and CN or DP
Bit 16 = 1: Either DP or DN outside the tolerance. and DN been interchanged)?
The unipolar nominal signal level of the encoder must lie in the range 2500 - replace the encoder cable.
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).
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 A31811 (F,N) Encoder 1: Encoder serial number changed The serial number of the motor encoder of a synchronous motor has Re causes 1, 2:
changed. The change was only checked for Carry out an automatic adjustment using the pole position identification routine.
encoders with serial number (e.g. EnDat encoders) and build-in motors First, accept the serial number with
(e.g. p0300 = 401) or third-party motors p0440 = 1. Acknowledge the fault. Initiate the pole position identification routine
(p0300 = 2). with p1990 = 1. Then check that the
Cause 1: pole position identification routine is correctly executed.
The encoder was replaced. SERVO:
Cause 2: If a pole position identification technique is selected in p1980, and if p0301 does
A third-party, build-in or linear motor was re-commissioned. not contain a motor type with an
Cause 3: encoder adjusted in the factory, then p1990 is automatically activated.
The motor with integrated and adjusted encoder was replaced. or
Cause 4: Set the adjustment via p0431. In this case, the new serial number is
The firmware was updated to a version that checks the encoder serial automatically accepted.
number. or
Note: Mechanically adjust the encoder. Accept the new serial number with p0440 = 1.
With closed-loop position control, the serial number is accepted when Re causes 3, 4:
starting the adjustment (p2507 = 2). Accept the new serial number with p0440 = 1.
When the encoder is adjusted (p2507 = 3), the serial number is checked for
changes and if required, the adjustment
is reset (p2507 = 1).
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 A31902 (F,N) Encoder 1: SPI-BUS error occurred Error when operating the internal SPI bus. - replace the Sensor Module.
Fault value (r0949, interpret hexadecimal): - if required, upgrade the firmware in the Sensor Module.
Only for internal Siemens troubleshooting. - contact the Hotline.

Sinamics G130 A31903 (F,N) Encoder 1: I2C-BUS error occurred Error when operating the internal I2C bus. - replace the Sensor Module.
Fault value (r0949, interpret hexadecimal): - if required, upgrade the firmware in the Sensor Module.
Only for internal Siemens troubleshooting. - contact the Hotline.

Sinamics G130 A31915 (F,N) Encoder 1: Configuration error The configuration for encoder 1 is incorrect. No re-parameterization between fault/alarm.
Fault value (r0949, interpret decimal):
1: Re-parameterization between fault/alarm is not permissible.
Sinamics G130 A31920 (F,N) Encoder 1: Temperature sensor fault When evaluating the temperature sensor, an error occurred. - check that the encoder cable is the correct type and is correctly connected.
Alarm value (r2124, interpret decimal): - check the temperature sensor selection in p0600 to p0603.
Low word low byte: Cause: - replace the Sensor Module (hardware defect or incorrect calibration data).
1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm).
2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).
Additional values:
Only for internal Siemens troubleshooting.
Low word high byte: Channel number.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 A31999 (F,N) Encoder 1: Unknown alarm A alarm has occurred on the Sensor Module for encoder 1 that cannot be - replace the firmware on the Sensor Module by an older firmware version
interpreted by the Control Unit firmware. (r0148).
This can occur if the firmware on this component is more recent than the - upgrade the firmware on the Control Unit (r0018).
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.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 A32400 (F,N) Encoder 2: Alarm threshold zero mark distance The measured zero mark distance does not correspond to the - check that the encoder cables are routed in compliance with EMC.
error parameterized zero mark distance. - check the plug connections.
For distance-coded encoders, the zero mark distance is determined from . check the encoder type (encoder with equidistant zero marks).
zero marks detected pairs. This means that - adapt the parameter for the distance between zero marks (p0424, p0425).
if a zero mark is missing, depending on the pair generation, this cannot - replace the encoder or encoder cable.
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).
Alarm value (r2124, 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.

Sinamics G130 A32401 (F,N) Encoder 2: Alarm threshold zero marked failed The 1.5 x parameterized zero mark distance was exceeded. - check that the encoder cables are routed in compliance with EMC.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary - check the plug connections.
encoder) or p0424 (linear encoder). . check the encoder type (encoder with equidistant zero marks).
Alarm value (r2124, interpret decimal): - adapt the parameter for the distance between zero marks (p0425).
Number of increments after POWER ON or since the last zero mark that - replace the encoder or encoder cable.
was detected (4 increments = 1 encoder
pulse).

Sinamics G130 A32410 (F,N) Encoder 2: Serial communications Serial communication protocol transfer error between the encoder and - check that the encoder cables are routed in compliance with EMC.
evaluation module. - check the plug connections.
Alarm value (r2124, interpret binary): - replace the encoder.
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 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.

Sinamics G130 A32411 (F,N) Encoder 2: EnDat encoder signals alarms The error word of the EnDat encoder has alarm bits that have been set. Replace encoder.
Alarm value (r2124, interpret binary):
Bit 0: Frequency exceeded (speed too high).
Bit 1: Temperature exceeded.
Bit 2: Control reserve, lighting system exceeded.
Bit 3: Battery discharged.
Bit 4: Reference point passed.

Sinamics G130 A32412 (F,N) Encoder 2: Error bit set in the serial protocol The encoder sends a set error bit via the serial protocol. - carry out a POWER ON (power off/on) for all components.
Alarm value (r2124, interpret binary): - check that the encoder cables are routed in compliance with EMC.
Bit 0: Fault bit in the position protocol. - check the plug connections.
Bit 1: Alarm bit in the position protocol. - replace the encoder.
Sinamics G130 A32414 (F,N) Encoder 2: Amplitude error track C or D (C^2 + The amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall - check that the encoder cables are routed in compliance with EMC.
D^2) signals, is not within the tolerance bandwidth. - check the plug connections.
Alarm value (r2124, interpret hexadecimal): - replace the encoder or encoder cable.
yyyyxxxx hex: - check the Sensor Module (e.g. contacts).
yyyy = Signal level, track D (16 bits with sign). - check the Hall sensor box
xxxx = Signal level, track C (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600
mV (500 mV -25/+20 %).
The response thresholds are < 230 mV (observe the frequency response of
the encoder) and > 750 mV.
A signal level of 500 mV peak value corresponds to the numerical value
5333 hex = 21299 dec.
Note:
If the amplitude is not within the tolerance bandwidth, then it cannot be
used to initialize the start position.

Sinamics G130 A32418 (F,N) Encoder 2: Speed difference per sampling rate For an HTL/TTL encoder, the speed difference between two sampling cycles - check the tachometer feeder cable for interruptions.
exceeded has exceeded the value in p0492. - check the grounding of the tachometer shielding.
The change to the averaged speed actual value - if applicable - is monitored - if required, increase the setting of p0492.C300
in the current controller sampling time.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.
See also: p0492 (Square-wave encoder, maximum speed difference per
sampling cycle)

Sinamics G130 A32419 (F,N) Encoder 2: Track A or B outside the tolerance The amplitude, phase or offset correction for track A or B is at the limit. - check mechanical mounting tolerances for encoders without their own
range Amplitude error correction: Amplitude B / Amplitude A = 0.78 ... 1.27 bearings (e.g. toothed-wheel encoders).
Phase: <84 degrees or >96 degrees - check the plug connections (also the transition resistance).
SMC20: Offset correction: +/-140 mV - check the encoder signals.
SMC10: Offset correction: +/-650 mV - replace the encoder or encoder cable.
Alarm value (r2124, interpret hexadecimal):
xxxx1: Minimum of the offset correction, track B
xxxx2: Maximum of the offset correction, track B
xxx1x: Minimum of the offset correction, track A
xxx2x: Maximum of the offset correction, track A
xx1xx: Minimum of the amplitude correction, track B/A
xx2xx: Maximum of the amplitude correction, track B/A
x1xxx: Minimum of the phase error correction
x2xxx: Maximum of the phase error correction
1xxxx: Minimum of the cubic correction
2xxxx: Maximum of the cubic correction

Sinamics G130 A32421 (F,N) Encoder 2: Coarse position error For the actual value sensing, an error was detected. As a result of this error, Re alarm value = 3:
it must be assumed that the actual value - for a standard encoder with cable, if required, contact the manufacturer.
sensing supplies an incorrect coarse position. - correct the assignment of the tracks to the position value that is serially
Alarm value (r2124, interpret decimal): transferred. To do this, the two tracks must
3: The absolute position of the serial protocol and track A/B differ by half be connected, inverted, at the Sensor Module (interchange A with A* and B with
an encoder pulse. The absolute position B*) or, for a programmable encoder,
must have its zero position in the quadrants in which both tracks are check the zero offset of the position.
negative. In the case of a fault, the position can
be incorrect by one encoder pulse.

Sinamics G130 A32429 (F,N) Encoder 2: Position difference, hall The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° - track C or D not connected.
sensor/track C/D and A/B too large electrical or the error for the Hall signals is greater - correct the direction of rotation of the Hall sensor possibly connected as
than +/-60 ° electrical. equivalent for track C/D.
One period of track C/D corresponds to 360 ° mechanical. - check that the encoder cables are routed in compliance with EMC.
One period of the Hall signal corresponds to 360 ° electrical. - check the adjustment of the Hall sensor.
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.
Alarm value (r2124, 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 °).
Sinamics G130 A32431 (F,N) Encoder 2: Deviation, position When the zero pulse is passed, a deviation in the incremental position was - check that the encoder cables are routed in compliance with EMC.
incremental/absolute too large detected. - check the plug connections.
For equidistant zero marks, the following applies: - replace the encoder or encoder cable.
- The first zero mark passed supplies the reference point for all subsequent - remove any dirt from the coding disk or strong magnetic fields.
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).

Sinamics G130 A32432 (F,N) Encoder 2: Rotor position adaptation corrects For track A/B, pulses have been lost or too many have been counted. These - check that the encoder cables are routed in compliance with EMC.
deviation pulses are presently being corrected. - check the plug connections.
Alarm value (r2124, interpret decimal): Last measured deviation of the zero - replace the encoder or encoder cable.
mark distance in increments (4 increments - check encoder limit frequency.
= 1 encoder pulse). The sign designates the direction of motion when - adapt the parameter for the distance between zero marks (p0424, p0425).
detecting the zero mark distance.

Sinamics G130 A32443 (F,N) Encoder 2: Signal level C/D unipolar outside The unipolar level (CP/CN or DP/DN) for encoder 2 is outside the - check that the encoder cables and shielding are routed in compliance with
tolerance permissible tolerance. EMC.
Alarm value (r2124, interpret binary): - check the plug connections and contacts.
Bit 0 = 1: Either CP or CN outside the tolerance. - are the C/D tracks connected correctly (have the signal lines CP and CN or DP
Bit 16 = 1: Either DP or DN outside the tolerance. and DN been interchanged)?
The unipolar nominal signal level of the encoder must lie in the range 2500 - replace the encoder cable.
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).

Sinamics G130 A32700 Encoder 2: Effectivity test does not supply the The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
expected value Fault value (r0949, interpret binary):
Bit x = 1: Effectivity test x unsuccessful.

Sinamics G130 A32902 (F,N) Encoder 2: SPI-BUS error occurred Error when operating the internal SPI bus. - replace the Sensor Module.
Fault value (r0949, interpret hexadecimal): - if required, upgrade the firmware in the Sensor Module.
Only for internal Siemens troubleshooting. - contact the Hotline.

Sinamics G130 A32903 (F,N) Encoder 2: I2C-BUS error occurred Error when operating the internal I2C bus. - replace the Sensor Module.
Fault value (r0949, interpret hexadecimal): - if required, upgrade the firmware in the Sensor Module.
Only for internal Siemens troubleshooting. - contact the Hotline.

Sinamics G130 A32915 (F,N) Encoder 2: Configuration error The configuration for encoder 2 is incorrect. No re-parameterization between fault/alarm.
Fault value (r0949, interpret decimal):
1: Re-parameterization between fault/alarm is not permissible.

Sinamics G130 A32920 (F,N) Encoder 2: Temperature sensor fault When evaluating the temperature sensor, an error occurred. - check that the encoder cable is the correct type and is correctly connected.
Alarm value (r2124, interpret decimal): - check the temperature sensor selection in p0600 to p0603.
Low word low byte: Cause: - replace the Sensor Module (hardware defect or incorrect calibration data).
1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm).
2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).
Additional values:
Only for internal Siemens troubleshooting.
Low word high byte: Channel number.

Sinamics G130 A32999 (F,N) Encoder 2: Unknown alarm A alarm has occurred on the Sensor Module for encoder 2 that cannot be - replace the firmware on the Sensor Module by an older firmware version
interpreted by the Control Unit firmware. (r0148).
This can occur if the firmware on this component is more recent than the - upgrade the firmware on the Control Unit (r0018).
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.
Sinamics G130 A33400 (F,N) Encoder 3: Alarm threshold zero mark distance The measured zero mark distance does not correspond to the - check that the encoder cables are routed in compliance with EMC.
error parameterized zero mark distance. - check the plug connections.
For distance-coded encoders, the zero mark distance is determined from . check the encoder type (encoder with equidistant zero marks).
zero marks detected pairs. This means that - adapt the parameter for the distance between zero marks (p0424, p0425).
if a zero mark is missing, depending on the pair generation, this cannot - replace the encoder or encoder cable.
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).
Alarm value (r2124, 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.

Sinamics G130 A33401 (F,N) Encoder 3: Alarm threshold zero marked failed The 1.5 x parameterized zero mark distance was exceeded. - check that the encoder cables are routed in compliance with EMC.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary - check the plug connections.
encoder) or p0424 (linear encoder). . check the encoder type (encoder with equidistant zero marks).
Alarm value (r2124, interpret decimal): - adapt the parameter for the distance between zero marks (p0425).
Number of increments after POWER ON or since the last zero mark that - replace the encoder or encoder cable.D313
was detected (4 increments = 1 encoder
pulse).

Sinamics G130 A33410 (F,N) Encoder 3: Serial communications Serial communication protocol transfer error between the encoder and - check that the encoder cables are routed in compliance with EMC.
evaluation module. - check the plug connections.
Alarm value (r2124, interpret binary): - replace the encoder.
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.

Sinamics G130 A33411 (F,N) Encoder 3: EnDat encoder signals alarms The error word of the EnDat encoder has alarm bits that have been set. Replace encoder.
Alarm value (r2124, interpret binary):
Bit 0: Frequency exceeded (speed too high).
Bit 1: Temperature exceeded.
Bit 2: Control reserve, lighting system exceeded.
Bit 3: Battery discharged.
Bit 4: Reference point passed.

Sinamics G130 A33412 (F,N) Encoder 3: Error bit set in the serial protocol The encoder sends a set error bit via the serial protocol. - carry out a POWER ON (power off/on) for all components.
Alarm value (r2124, interpret binary): - check that the encoder cables are routed in compliance with EMC.
Bit 0: Fault bit in the position protocol. - check the plug connections.
Bit 1: Alarm bit in the position protocol. - replace the encoder.

Sinamics G130 A33414 (F,N) Encoder 3: Amplitude error track C or D (C^2 + The amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall - check that the encoder cables are routed in compliance with EMC.
D^2) signals, is not within the tolerance bandwidth. - check the plug connections.
Alarm value (r2124, interpret hexadecimal): - replace the encoder or encoder cable.
yyyyxxxx hex: - check the Sensor Module (e.g. contacts).
yyyy = Signal level, track D (16 bits with sign). - check the Hall sensor box
xxxx = Signal level, track C (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600
mV (500 mV -25/+20 %).
The response thresholds are < 230 mV (observe the frequency response of
the encoder) and > 750 mV.
A signal level of 500 mV peak value corresponds to the numerical value
5333 hex = 21299 dec.
Note:
If the amplitude is not within the tolerance bandwidth, then it cannot be
used to initialize the start position.
Sinamics G130 A33418 (F,N) Encoder 3: Speed difference per sampling rate For an HTL/TTL encoder, the speed difference between two sampling cycles - check the tachometer feeder cable for interruptions.
exceeded has exceeded the value in p0492. - check the grounding of the tachometer shielding.
The change to the averaged speed actual value - if applicable - is monitored - if required, increase the setting of p0492.
in the current controller sampling time.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.
See also: p0492 (Square-wave encoder, maximum speed difference per
sampling cycle)

Sinamics G130 A33419 (F,N) Encoder 3: Track A or B outside the tolerance The amplitude, phase or offset correction for track A or B is at the limit. - check mechanical mounting tolerances for encoders without their own
range Amplitude error correction: Amplitude B / Amplitude A = 0.78 ... 1.27 bearings (e.g. toothed-wheel encoders).
Phase: <84 degrees or >96 degrees - check the plug connections (also the transition resistance).
SMC20: Offset correction: +/-140 mV - check the encoder signals.
SMC10: Offset correction: +/-650 mV - replace the encoder or encoder cable.
Alarm value (r2124, interpret hexadecimal):
xxxx1: Minimum of the offset correction, track B
xxxx2: Maximum of the offset correction, track B
xxx1x: Minimum of the offset correction, track A
xxx2x: Maximum of the offset correction, track A
xx1xx: Minimum of the amplitude correction, track B/A
xx2xx: Maximum of the amplitude correction, track B/A
x1xxx: Minimum of the phase error correction
x2xxx: Maximum of the phase error correction
1xxxx: Minimum of the cubic correction
2xxxx: Maximum of the cubic correction

Sinamics G130 A33421 (F,N) Encoder 3: Coarse position error For the actual value sensing, an error was detected. As a result of this error, Re alarm value = 3:
it must be assumed that the actual value - for a standard encoder with cable, if required, contact the manufacturer.
sensing supplies an incorrect coarse position. - correct the assignment of the tracks to the position value that is serially
Alarm value (r2124, interpret decimal): transferred. To do this, the two tracks must
3: The absolute position of the serial protocol and track A/B differ by half be connected, inverted, at the Sensor Module (interchange A with A* and B with
an encoder pulse. The absolute position B*) or, for a programmable encoder,
must have its zero position in the quadrants in which both tracks are check the zero offset of the position.
negative. In the case of a fault, the position can
be incorrect by one encoder pulse.

Sinamics G130 A33429 (F,N) Encoder 3: Position difference, hall The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° - track C or D not connected.
sensor/track C/D and A/B too large electrical or the error for the Hall signals is greater - correct the direction of rotation of the Hall sensor possibly connected as
1 than +/-60 ° electrical. equivalent for track C/D.
One period of track C/D corresponds to 360 ° mechanical. - check that the encoder cables are routed in compliance with EMC.
One period of the Hall signal corresponds to 360 ° electrical. - check the adjustment of the Hall sensor.
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.
Alarm value (r2124, 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 °).

Sinamics G130 A33431 (F,N) Encoder 3: Deviation, position When the zero pulse is passed, a deviation in the incremental position was - check that the encoder cables are routed in compliance with EMC.
incremental/absolute too large detected. - check the plug connections.
For equidistant zero marks, the following applies: - replace the encoder or encoder cable.
- The first zero mark passed supplies the reference point for all subsequent - remove any dirt from the coding disk or strong magnetic fields.
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).

Sinamics G130 A33432 (F,N) Encoder 3: Rotor position adaptation corrects For track A/B, pulses have been lost or too many have been counted. These - check that the encoder cables are routed in compliance with EMC.
deviation pulses are presently being corrected. - check the plug connections.
Alarm value (r2124, interpret decimal): Last measured deviation of the zero - replace the encoder or encoder cable.
mark distance in increments (4 increments - check encoder limit frequency.
= 1 encoder pulse). The sign designates the direction of motion when - adapt the parameter for the distance between zero marks (p0424, p0425).
detecting the zero mark distance.
Sinamics G130 A33433 (F,N) Encoder 3: Signal level C/D unipolar outside The unipolar level (CP/CN or DP/DN) for encoder 3 is outside the - check that the encoder cables and shielding are routed in compliance with
tolerance permissible tolerance. EMC.
Alarm value (r2124, interpret binary): - check the plug connections and contacts.
Bit 0 = 1: Either CP or CN outside the tolerance. - are the C/D tracks connected correctly (have the signal lines CP and CN or DP
Bit 16 = 1: Either DP or DN outside the tolerance. and DN been interchanged)?
The unipolar nominal signal level of the encoder must lie in the range 2500 - replace the encoder cable.
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).

Sinamics G130 A33700 Encoder 3: Effectivity test does not supply the The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
expected value Fault value (r0949, interpret binary):
Bit x = 1: Effectivity test x unsuccessful.

Sinamics G130 A33902 (F,N) Encoder 3: SPI-BUS error occurred Error when operating the internal SPI bus. - replace the Sensor Module.
Fault value (r0949, interpret hexadecimal): - if required, upgrade the firmware in the Sensor Module.
Only for internal Siemens troubleshooting. - contact the Hotline.

Sinamics G130 A33903 (F,N) Encoder 3: I2C-BUS error occurred Error when operating the internal I2C bus. replace the sensor Module.
Fault value (r0949, interpret hexadecimal): - if required, upgrade the firmware in the sensor Module.
Only for internal Siemens troubleshooting. - contact the Hotline.

Sinamics G130 A33915 (F,N) Encoder 3: Configuration error The configuration for encoder 3 is incorrect. No re-parameterization between fault/alarm.
Fault value (r0949, interpret decimal):
1: Re-parameterization between fault/alarm is not permissible.

Sinamics G130 A33920 (F,N) Encoder 3: Temperature sensor fault When evaluating the temperature sensor, an error occurred. - check that the encoder cable is the correct type and is correctly connected.
Alarm value (r2124, interpret decimal): - check the temperature sensor selection in p0600 to p0603.
Low word low byte: Cause: - replace the Sensor Module (hardware defect or incorrect calibration data).
1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm).
2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).
Additional values:
Only for internal Siemens troubleshooting.
Low word high byte: Channel number.

Sinamics G130 A33999 (F,N) Encoder 3: Unknown alarm A alarm has occurred on the Sensor Module for encoder 3 that cannoy be - replace the firmware on the Sensor Module by an older firmware version
interpreted by the Control Unit Firmware. This can occur if the firmware on (r0148).
this component is more recent than the firmware on the Control Unit. - upgrade the firmware on the Control Unit (r0018).
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.

Sinamics G130 A34211 (F,N) VSM: Temperature alarm threshold exceeded The temperature (r3666) measured using the Voltage Sensing Module - check the fan.
(VSM) has exceeded the threshold value - reduce the power.
(p3667).
Alarm value (r2124, interpret decimal):
The hundred thousands and ten thousands position specifies the
component number of the VSM where the fault
occurred.

Sinamics G130 A34807 (F,N) VSM: Sequence control time monitoring Error, timeout in the sequence control on the Voltage Sensing Module Error, timeout in the sequence control on the Voltage Sensing Module (VSM).
(VSM).
Sinamics G130 A34903 (F,N) VSM: I2C bus error occurred An error has occurred in while accessing via the internal TM I2C bus. Replace the Terminal Module.

Sinamics G130 A34904 (F,N) VSM: EEPROM An error has occurred accessing the non-volatile memory on the Terminal Replace the Terminal Module.
Module.
Sinamics G130 A34905 (F,N) VSM: Parameter access The Control Unit attempted to write an illegal parameter value to the - check whether the firmware version of the VSM (r0158) matches the firmware
Voltage Sensing Module (VSM). version of Control Unit (r0018).
- if required, replace the Voltage Sensing Module.
Note:
The firmware versions that match each other are in the readme.txt file on the
memory card.

Sinamics G130 A34920 (F,N) VSM: Temperature sensor fault When evaluating the temperature sensor, an error occurred. - check that the sensor is connected correctly.
Alarm value (r2124, interpret decimal): -replace sensor.
1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm).
2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).
Sinamics G130 A34999 (F,N) VSM: Unknown alarm A fault occurred on the Voltage Sensing Module (VSM) an alarm has - replace the firmware on the Voltage Sensing Module by an older firmware
occurred that cannot be interpreted by the Control version (r0148).
Unit firmware. - upgrade the firmware on the Control Unit (r0018).
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.

Sinamics G130 A35012 TM54F: Test stop active The test stop for the Terminal Module 54F (TM54F) is presently being The alarm disappears automatically after successfully ending or canceling (when
executed. a fault condition occurs) the test
F35013 is output when a error occurs during the test stop. stop.

Sinamics G130 A35014 TM54F: Test stop required - after powering up the drive, a test stop has still not been carried out. Initiate test stop (BI: p10007).
- a new test stop is required after commissioning.
- the time to carry out the forced checking procedure (test stop) has
expired (p10003).E339

Sinamics G130 A35015 TM54F: Communication with drive not Cyclic communication of one or several drives with the Terminal Module For all drive objects specified in p10010, check whether the drive-based motion
established 54F (TM54F) is not active. monitoring functions with TM54F are
Fault value (r0949, interpret binary): enabled (p9601).
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.

Sinamics G130 A35016 TM54F: Net data communication with drive The cyclic net data communication within the Terminal Module 54F When replacing a Motor Module, carry out the following steps:
not established (TM54F) is still not active. - start the copy function for the node identifier on the TM54F (p9700 = 1D hex).
This message is output after the TM54F master and TM54F slave have - acknowledge the hardware CRC on the TM54F (p9701 = EC hex).
booted and is automatically withdrawn as - save all parameters (p0977 = 1).
soon as communications have been established. - carry out a POWER ON (power off/on) for all components.
a drive does not communicate with the TM54F, then none of the drives The following always applies:
parameterized in p10010 are enabled. - for all drive objects specified in p10010, check whether the drive-based motion
0x99: Action: All master-DOs at OFF - error: State of DI 20...23 of the slave monitoring functions with TM54F
does not correspond to the expected are enabled (p9601).
state (0V) or the slave not in state 0x8E. - check whether fault F35150 is present and if required, remove the cause of the
0xA4: Action: All master DOs at OFF - error: Slave not in state 0x99. fault.
0xAF: Action: All master-DOs at OFF - error: Status of DI 20...23 of the slave See also: r10055 (SI TM54F communication status drive-specific)
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.

Sinamics G130 A35054 TM54F: Temperature alarm threshold The temperature measured using the temperature sensing on the TM54F - allow the TM54F to cool down.
exceeded has exceeded the threshold value to initiate - carry out safe acknowledgement (p10006).
this alarm.

Sinamics G130 A35075 (F) TM54F: Internal communications An internal communications error has occurred in the Terminal Module 54F For internal communication errors:
(TM54F). - check the electrical cabinet design and cable routing for EMC compliance
This alarm can also occur if the TM54F exists and no safety function has yet - upgrade the software on the TM54F.
been parameterized. - contact the Hotline.
Alarm value (r2124, interpret decimal): - replace the TM54F.
Only for internal Siemens diagnostics. If TM54F exists and no safety function has yet been parameterized:
- None necessary. The alarm disappears automatically after a safety function has
been parameterized.
Sinamics G130 A35080 (F) TM54F: Checksum error safety parameters The calculated checksum entered in r10004 over the safety-relevant - Check the safety-relevant parameters and if required, correct.
parameters does not match the reference - set the reference checksum to the actual checksum.
checksum saved in p10005 at the last machine acceptance. - acknowledge that hardware was replaced
Fault value (r0949, interpret decimal): - carry out a POWER ON.
1: Checksum error for functional SI parameters. - carry out an acceptance test.
2: Checksum error for SI parameters for component assignment.

Sinamics G130 A35081 (F) TM54F: Static 1 signal at F-DI for safe A logical "1" signal is present at the F-DI configured in p10006 for more Set F-DI (see p10006) to logical "0" signal.
acknowledgement 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.

Sinamics G130 A35200 (F,N) TM: Calibration data An error was detected in the calibration data of the Terminal Module. Power down the unit and power up again.
Alarm value (r2124, interpret decimal): If the fault is still present, replace the module/board.
The hundred thousands and ten thousands location specifies the
component Id of the Terminal Module where the
fault occurred.
The thousands location specifies whether the analog input 0 (=0) or analog
output 1 (= 1) is involved.
The hundreds location specifies the fault type:
0: No calibration data available.
1: Offset too high (> 100 mV).
The tens and ones location specifies the number of the input involved.

Sinamics G130 A35211 (F,N) TM: Temperature alarm threshold exceeded The temperature measured using the temperature sensing of the Terminal Allow the temperature sensor to cool down.
Module (TM) (r4105) has exceeded the
threshold value to initiate this alarm (p4102[0]).
Alarm value (r2124, interpret decimal):
The hundred thousands and ten thousands location specifies the
component number of the TMxx where the fault
occurred.

Sinamics G130 A35222 (F,N) TM: Encoder pulse number not permissible The encoder pulse number entered does not match the permissible pulse Enter the encoder pulse number in the permissible range (p0408).
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).

Sinamics G130 A35223 (F,N) TM: Zero mark offset not permissible The entered zero mark offset is not permissible. Enter the zero mark offset in the permissible range (p4426).
Fault value (r0949, interpret decimal):
1: Zero mark offset is too high.

Sinamics G130 A35801 (F,N) TM DRIVE-CLiQ: Sign-of-life missing A DRIVE-CLiQ communication error has occurred from the Terminal Module - check the DRIVE-CLiQ connection.
to the encoder involved. - replace the component involved.
Alarm value (r2124, interpret hexadecimal): See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 A35802 (F,N) TM: Time slice overflow Time slice overflow on Terminal Module. Replace the Terminal Module.
Sinamics G130 A35803 (F,N) TM: Memory test NONE - check whether the permissible ambient temperature for the Terminal Module
NONE is being maintained.
An error has occurred during the memory test on the Terminal Module. - replace the Terminal Module.E353

Sinamics G130 A35804 (F,N) TM: CRC A checksum error has occurred when reading-out the program memory on - check whether the permissible ambient temperature for the component is
the Terminal Module. maintained.
Fault value (r0949, interpret hexadecimal): - replace the Terminal Module.
Difference between the checksum at POWER ON and the current
checksum.

Sinamics G130 A35805 (F,N) TM: EPROM checksum error Internal parameter data is corrupted. - check whether the permissible ambient temperature for the component is
Alarm value (r2124, interpret hexadecimal): maintained.
01: EEPROM access error. - replace the Terminal Module 31 (TM31).
02: Too many blocks in the EEPROM.

Sinamics G130 A35807 (F,N) TM: Sequence control time monitoring Error, timeout, sequence control on the Terminal Module. Replace the Terminal Module.
Sinamics G130 A35903 (F,N) TM: I2C bus error occurred An error has occurred while accessing the internal I2C bus of the Terminal Replace the Terminal Module.
Module.
Sinamics G130 A35904 (F,N) TM: EEPROM An error has occurred accessing the non-volatile memory on the Terminal Replace the Terminal Module.
Module.
Sinamics G130 A35905 (F,N) TM: Parameter access The Control Unit attempted to write an illegal parameter value to the - check whether the firmware version of the Terminal Module (r0158) matches
Terminal Module. the firmware version of Control Unit
(r0018).
- if required, replace the Terminal Module.
Note:
The firmware versions that match each other are in the readme.txt file on the
memory card.

Sinamics G130 A35906 (F,N) TM: 24 V power supply missing The 24 V power supply for the digital outputs is missing. Check the terminals for the power supply voltage (L1+, L2+, L3+, M).
Alarm value (r2124, interpret hexadecimal): NONE
01: TM17 24 V power supply for DI/DO 0 ... 7 missing.
02: TM17 24 V power supply for DI/DO 8 ... 15 missing.
04: TM15 24 V power supply for DI/DO 0 ... 7 (X520) missing.
08: TM15 24 V power supply for DI/DO 8 ... 15 (X521) missing.
10: TM15 24 V power supply for DI/DO 16 ... 23 (X522) missing.
20: TM41 24 V power supply for DI/DO 0 ... 3 missing.

Sinamics G130 A35907 (F,N) TM: Hardware initialization error The Terminal Module was not successfully initialized. Carry out a POWER ON.
Alarm value (r2124, interpret hexadecimal):
01: TM17 or TM41 - incorrect configuration request.
02: TM17 or TM41 - programming not successful.
04: TM17 or TM41 - invalid time stamp

Sinamics G130 A35910 (F,N) TM: Module overtemperature The temperature in the module has exceeded the highest permissible limit. - reduce the ambient temperature.
- replace the Terminal Module.
Sinamics G130 A35911 (F,N) TM: Clock synchronous operation sign-of-life The maximum permissible number of errors in the master sign-of-life (clock - check the physical bus configuration (terminating resistor, shielding, etc.).
missing synchronous operation) has been - check the interconnection of the master sign-of-life (r4201 via p0915).
exceeded in cyclic operation. - check whether the master correctly sends the sign-of-life (e.g. set up a trace
When the alarm is output, the module outputs are reset up to the next with r4201.12 ... r4201.15 and trigger
synchronization. signal r4301.9).
- check the bus and master for utilization level (e.g. bus cycle time Tdp was set
too short).

Sinamics G130 A35920 (F,N) TM: Temperature sensor fault When evaluating the temperature sensor, an error occurred. - check that the sensor is connected correctly.
Alarm value (r2124, interpret decimal): - replace sensor.
1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm).
2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).

Sinamics G130 A35999 (F,N) TM: Unknown alarm An alarm has occurred on the Terminal Module that cannot be interpreted - replace the firmware on the Terminal Module by an older firmware version
by the Control Unit firmware. (r0158).
This can occur if the firmware on this component is more recent than the - upgrade the firmware on the Control Unit (r0018).
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.

Sinamics G130 A36217 (IN) Hub: undervoltage alarm 24 V supply 24 V power supply on DRIVE-CLiQ Hub Module has undershot alarm - check the supply voltage of the component involved.
threshold. - replace the component involved.
Alarm value (r2124, interpret decimal):
Current operating voltage in 0.1 °C resolution.

Sinamics G130 A36801 (F,N) Hub DRIVE-CLiQ: sign-of-life missing DRIVE-CLiQ communication error from Control Unit to DRIVE-CLiQ Hub - check the DRIVE-CLiQ connection.
Module in question. - replace the component involved.
Alarm value (r2124, interpret hexadecimal): See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex = 10 dec:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 A36804 (F,N) Hub: Checksum error A checksum error (CRC) occurred when the program memory on the DRIVE- - check whether the permissible ambient temperature for the component is
CLiQ Hub Module was read out. maintained.
Alarm value (r2124, interpret hexadecimal): - Replace DRIVE-CLiQ Hub Module.
Difference between the checksum at POWER ON and the current
checksum.

Sinamics G130 A36805 (F,N) Hub: EEPROM checksum incorrect The internal parameter data on the DRIVE-CLiQ Hub Module are incorrect. - check whether the permissible ambient temperature for the component is
Alarm value (r2124, interpret hexadecimal): maintained.
01: EEPROM access error. - Replace DRIVE-CLiQ Hub Module.
02: Too many blocks in the EEPROM.
Sinamics G130 A36999 (F,N)) Hub: Unknown alarm An alarm occurred on the DRIVE-CLiQ Hub Module that cannot be - Replace the firmware on the DRIVE-CLiQ Hub Module with older firmware
interpreted by the Control Unit firmware. (r0158).
This can occur if the firmware on this component is more recent than the - upgrade the firmware on the Control Unit (r0018).
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.

Sinamics G130 A40100 Alarm at DRIVE-CLiQ socket X100 An alarm has occurred at the drive object at the DRIVE-CLiQ socket X100. Evaluate the alarm buffer of the specified object.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.

Sinamics G130 A40101 Alarm at DRIVE-CLiQ socket X101 An alarm has occurred at the drive object at the DRIVE-CLiQ socket X101. Evaluate the alarm buffer of the specified object.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.

Sinamics G130 A40102 Alarm at DRIVE-CLiQ socket X102 An alarm has occurred at the drive object at the DRIVE-CLiQ socket X102. Evaluate the alarm buffer of the specified object.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.

Sinamics G130 A40103 Alarm at DRIVE-CLiQ socket X103 An alarm has occurred at the drive object at the DRIVE-CLiQ socket X103. Evaluate the alarm buffer of the specified object.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.

Sinamics G130 A40104 Alarm at DRIVE-CLiQ socket X104 An alarm has occurred at the drive object at the DRIVE-CLiQ socket X104. Evaluate the alarm buffer of the specified object.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.

Sinamics G130 A40105 Alarm at DRIVE-CLiQ socket X105 An alarm has occurred at the drive object at the DRIVE-CLiQ socket X105. Evaluate the alarm buffer of the specified object.
Alarm value (r2124, interpret decimal):
First alarm that has occurred for this drive object.

Sinamics G130 A49170 Cooling system: Alarm has occurred The cooling system signals a general alarm. - check the wiring between the cooling system and the input terminal (Terminal
Module).
- check the external control device for the cooling system.

Sinamics G130 A49171 Cooling system: Conductivity has exceeded the The conductivity monitoring of the cooling liquid is set (r0267 bit 7, from Check the device to de-ionize the cooling liquid.
alarm threshold 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)

Sinamics G130 A49172 Cooling system: Conductivity actual value is When monitoring the conductivity of the cooling liquid, there is a fault in - check the wiring between the cooling system and the Power Stack Adapter
not valid the wiring or in the sensor. (PSA).
- check the function of the sensor to measure the conductivity.

Sinamics G130 A49173 Cooling system: Cooling liquid temperature has The cooling liquid intake temperature has exceeded the specified alarm Check the cooling system and the ambient conditions.
exceeded the alarm threshold threshold.

Sinamics G130 A49201 Excitation group signal alarm The "excitation group signal alarm" signal is present. Check the excitation equipment.
Sinamics G130 A50001 COMM BOARD: Alarm 1 CBE20: A PROFINET controller attempts to establish a connection using an CBE20: Upgrade the PROFINET version of the project (HW Config) and/or the
incorrect configuring telegram. The CBE20 firmware to make them compatible.
PROFINET version (V2.1/V2.2) of the project (HW Config) is not compatible See also: p8835 (CBE20 firmware selection)
with the CBE20 firmware.

Sinamics G130 C01689 SI Motion: Axis re-configured The axis configuration was changed (e.g. changeover between linear axis The following should be carried out after the changeover:
and rotary axis). - exit the safety commissioning mode (p0010).
Parameter p0108.13 is internally set to the correct value. - save all parameters (p0977 = 1 or "copy RAM to ROM").
Note: - carry out a POWER ON.
This fault does not result in a safety stop response. Once the Control Unit has been switched on, safety message F01680 or F3
Fault value (r0949, interpret decimal):
Parame

Sinamics G130 C01700 SI Motion CU: STOP A initiated The drive is stopped via a STOP A (pulses are suppressed via the safety - remove the fault cause in the control and carry out a POWER ON.
shutdown path of the Control Unit). - check the value in p9557, if necessary, increase the value, and carry out
Possible causes: POWER ON.
- stop request from the higher-level control. - check the shutdown path of the Control Unit (check DRIVE-CLiQ
- pulses not suppressed after a parameterized time (p9557) after test stop communication).
selection - carry out a diagnosti

Sinamics G130 C01701 SI Motion CU: STOP B initiated The drive is stopped via STOP B (braking along the OFF3 deceleration - remove the fault cause in the control and carry out a POWER ON.
ramp). - carry out a diagnostics routine for message C01714.
As a result of this fault, after the time parameterized in p9556 has expired, - carry out a diagnostics routine for message C01711.
or the speed threshold parameterized in This message can only be acknowledged as follows in the acceptance test mode
p9560 has been undershot, message C01700 "STOP A initiated" i with
Sinamics G130 C01706 SI Motion CU: Safe Acceleration Monitor limit After initiating STOP B or STOP C, the velocity has exceeded the selected Check the braking behavior, if required, adapt the tolerance for "Safe
exceeded tolerance. Acceleration Monitor".
The drive is shut down by the message C01700 "SI Motion: STOP A This message can only be acknowledged as follows in the acceptance test mode
initiated". without POWER ON:
- motion monitoring functions integrated in the drive: Via Termina

Sinamics G130 C01707 SI Motion CU: Tolerance for safe operating The actual position has distanced itself further from the target position - check whether safety faults are present and if required carry out the
stop exceeded than the standstill tolerance. appropriate diagnostic routines for the particular
The drive is shut down by the message C01701 "SI Motion: STOP B faults.
initiated". - check whether the standstill tolerance matches the accuracy and control
dynamic performance of the axis.
- carry out a POW

Sinamics G130 C01708 SI Motion CU: STOP C initiated The drive is stopped via STOP C (braking along the OFF3 deceleration - remove the cause of the fault at the control.
ramp). - carry out a diagnostics routine for message C01714.
"Safe Operating Stop" (SOS) is activated after the parameterized timer has This message can be acknowledged as follows:
expired. - motion monitoring functions integrated in the drive: Via Terminal Module 54F
Possible causes: (TM54F) or PROFIsafe
- stop request from the higher-level control. - motion
- subsequent response to the mes

Sinamics G130 C01709 SI Motion CU: STOP D initiated The drive is stopped via a STOP D (braking along the path). - remove the cause of the fault at the control.
"Safe Operating Stop" (SOS) is activated after the parameterized timer has - carry out a diagnostics routine for message C01714.
expired. This message can be acknowledged as follows:
Possible causes: - motion monitoring functions integrated in the drive: Via Terminal Module 54F
- stop request from the higher-level control. (TM54F) or PROFIsafe
- subsequent response to the message C01714 "SI - motion

Sinamics G130 C01710 SI Motion CU: STOP E initiated The drive is stopped via a STOP E (retraction motion). - remove the cause of the fault at the control.
"Safe Operating Stop" (SOS) is activated after the parameterized timer has - carry out a diagnostics routine for message C01714.
expired. This message can be acknowledged as follows:
Possible causes: - motion monitoring functions integrated in the drive: Via Terminal Module 54F
- stop request from the higher-level control. (TM54F) or PROFIsafe
- subsequent response to the message C01714 "SI Motio - motion

Sinamics G130 C01711 SI Motion CU: Defect in a monitoring channel When cross-checking and comparing the two monitoring channels, the 1: Status image of monitoring functions SOS, SLS or SLP (result list 1) (r9710[0],
drive detected a difference between the input r9710[1]).
data or results of the monitoring functions and initiated a STOP F. One of 2: Status image of monitoring function SCA or n < nx (result list 2) (r9711[0],
the monitoring functions no longer reliably r9711[1]).
functions - i.e. safe o 3: Pos. act. val. (r9712).
4: Error when synchronizing the crosswise d

Sinamics G130 C01714 SI Motion CU: Safely-Limited Speed exceeded The drive has moved faster than that specified by the velocity limit value - check the traversing/motion program in the control.
(p9531). The drive is stopped as a result of - check the limits for "Safely-Limited Speed (SLS) and if required, adapt (p9531).
the configured stop response (p9563). This message can be acknowledged as follows:
Message value (r9749, interpret decimal): - motion monitoring functions integrated in the drive: Via Terminal Modul
100: SLS1 exceeded.
200: SLS2 exceeded.
300: SLS3 excee

Sinamics G130 C01745 SI Motion CU: Checking braking torque for the The normalization of the brake torque for the brake test can be changed - carry out a POWER ON (power off/on) for all components.
brake test using parameter p2003. - repeat the acceptance test for the safe brake test if the brake test is used.
An acceptance test must be carried out again for the braking test. This See also: p2003 (Reference torque)
determines whether the braking test is still
carried out with the correct braking torque

Sinamics G130 C01750 SI Motion CU: Hardware fault safety-relevant The encoder that is used for the safety-relevant motion monitoring - check the encoder connection.
encoder functions signals a hardware fault. - replace the encoder.
Message value (r9749, interpret decimal): This message can be acknowledged as follows:
Encoder status word 1, encoder status word 2 that resulted in the message. - motion monitoring functions integrated in the drive: Via Terminal Module 54F
(TM54F) or PROFIsafe
- motion monitoring functions with SINUMERIK: Via the m

Sinamics G130 C01751 SI Motion CU: eff.test error safe encoder The DQ encoder used for the safety-relevant motion monitoring functions - check the encoder connection.
signals an effectiveness test error. - replace the encoder.
Message value (r9749, interpret decimal): This message can be acknowledged as follows:
1 - TFD bit in EncoderStatusWord2 set in last effectiveness test set - motion monitoring functions integrated in the drive: Via Terminal Module 54F
2 - Actual effectiveness test no. i (TM54F) or PROFIsafe
- motion monitoring functions with SINUMERIK: Via the m

Sinamics G130 C01798 SI Motion CU: Test stop running The test stop is active. None necessary.
The message is withdrawn when the test stop is finished.
Note:
SI: Safety Integrated

Sinamics G130 C01799 SI Motion CU: Acceptance test mode active The acceptance test mode is active. The POWER ON signals of the safety- None necessary.
relevant motion monitoring functions can The message is withdrawn when exiting the acceptance test mode.
be acknowledged during the acceptance test using the RESET button of the Note:
higher-level control. SI: Safety Integrated
Sinamics G130 C30681 SI Motion MM: Incorrect parameter value The parameter value cannot be parameterized with this value. Correct the parameter value.
Note:
This message does not result in a safety stop response.
Fault value (r0949, interpret decimal):
Parameter number with the incorrect value.

Sinamics G130 C30700 SI Motion MM: STOP A initiated The drive is stopped via a STOP A (pulses are suppressed via the safety - remove the cause to the fault on the Control Unit.
shutdown path of the Control Unit). - check the value in p9357, if required, increase the value.
Possible causes: - check the shutdown path of the Control Unit (check DRIVE-CLiQ
- stop request from the Control Unit. communication).
- pulses not suppressed after a parameterized time (p9357) after test stop - carry out a diagnostics routine for message C30706.
selection. - carry out a diagnostics routine for message C30714.
- subsequent response to the message C30706 "SI Motion MM: Safe - carry out a diagnostics routine for message C30701.
Acceleration Monitoring, limit exceeded". - replace Motor Module.
- subsequent response to the message C30714 "SI Motion MM: Safely- - replace Control Unit.
Limited Speed exceeded". This message can only be acknowledged in the acceptance test mode without
- subsequent response to the message C30701 "SI Motion MM: STOP B POWER ON via the Terminal Module
initiated". 54F (TM54F) or PROFIsafe.
Note:
SI: Safety Integrated

Sinamics G130 C30701 SI Motion MM: STOP B initiated The drive is stopped via a STOP B (braking along the OFF3 ramp). - remove the fault cause in the control and carry out a POWER ON.
As a result of this fault, after the time parameterized in p9356 has expired, - carry out a diagnostics routine for message C01714.
or the speed threshold parameterized in - carry out a diagnostics routine for message C01711.
p9360 has been undershot, message C30700 "SI Motion MM: STOP A This message can only be acknowledged in the acceptance test mode without
initiated" is output. POWER ON via the Terminal Module
Possible causes: 54F (TM54F) or PROFIsafe.
- stop request from the Control Unit. Note:
- subsequent response to the message C30714 "SI Motion MM: Safely SI: Safety Integrated
limited speed exceeded".
- subsequent response to the message C30711 "SI Motion MM: Defect in a
monitoring channel".

Sinamics G130 C30706 SI Motion MM: Safe Acceleration Monitor limit After initiating STOP B or STOP C, the velocity has exceeded the selected Check the braking behavior, if required, adapt the tolerance for "Safe
exceeded tolerance. Acceleration Monitor".
The drive is shut down by the message C30700 "SI Motion MM: STOP A This message can only be acknowledged in the acceptance test mode without
initiated". POWER ON via the Terminal Module
54F (TM54F) or PROFIsafe.
Note:
SBR: Safe Acceleration Monitor
SI: Safety Integrated
See also: p9548 (SI Motion SBR actual velocity tolerance (Control Unit))

Sinamics G130 C30707 SI Motion MM: Tolerance for safe operating The actual position has distanced itself further from the target position - check whether safety faults are present and if required carry out the
stop exceeded than the standstill tolerance. appropriate diagnostic routines for the particular
The drive is shut down by the message C30701 "SI Motion MM: STOP B faults.
initiated". - check whether the standstill tolerance matches the accuracy and control
dynamic performance of the axis.
- carry out a POWER ON.
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
SOS: Safe Operating Stop / SBH: Safe operating stop
See also: p9530 (SI Motion standstill tolerance (Control Unit))

Sinamics G130 C30708 SI Motion MM: STOP C initiated The drive is stopped via a STOP C (braking along the OFF3 ramp). - remove the cause of the fault at the control.
"Safe Operating Stop" (SOS) is activated after the parameterized timer has - carry out a diagnostics routine for message C30714.
expired. This message can only be acknowledged via the Terminal Module 54F (TM54F)
Possible causes: or PROFIsafe.
- stop request from the higher-level control. Note:
- subsequent response to the message C30714 "SI Motion MM: Safely SI: Safety Integrated
limited speed exceeded". SOS: Safe Operating Stop / SBH: Safe operating stop
See also: p9552 (SI Motion transition time STOP C to SOS (SBH) (Control
Unit))

Sinamics G130 C30709 SI Motion MM: STOP D initiated The drive is stopped via a STOP D (braking along the path). - remove the cause of the fault at the control.
"Safe Operating Stop" (SOS) is activated after the parameterized timer has - carry out a diagnostics routine for message C30714.
expired. This message can only be acknowledged via the Terminal Module 54F (TM54F)
Possible causes: or PROFIsafe.
- stop request from the Control Unit. Note:
- subsequent response to the message C30714 "SI Motion: Safely limited SI: Safety Integrated
speed exceeded". SOS: Safe Operating Stop / SBH: Safe operating stop
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))
Sinamics G130 C30711 SI MM MM: Defect in a monitoring channel When cross-checking and comparing the two monitoring channels, the Re message value = 1030:
drive detected a difference between the input - check the encoder connection.
data or results of the monitoring functions and initiated a STOP F. One of - if required, replace the encoder.
the monitoring functions no longer reliably Re message value = 1031:
functions - i.e. safe operation is no longer possible. When replacing a Sensor Module, carry out the following steps:
If at least one monitoring function is active, then after the parameterized - start the copy function for the node identifier on the drive (p9700 = 1D hex).
timer has expired, the message C30701 "SI - acknowledge the hardware CRC on the drive (p9701 = EC hex).
Motion: STOP B initiated" is output. The message is output with message - save all parameters (p0977 = 1).
value 1031 when the Sensor Module hardware - carry out a POWER ON (power off/on) for all components.
is replaced. The following always applies:
Message value (r9749, interpret decimal): - check the encoder connection.
0 ... 999: Number of the cross-checked data that resulted in this message. - if required, replace the encoder.
Refer to safety message C01711for a Re other message values:
description of the individual data. - The significance of the individual message values is described in safety message
The significance of the individual message values is described in safety C01711 of the Control Unit.
message C01711 of the Control Unit. Note:
1000: Watchdog timer has expired. Too many signal changes have occurred This message can only be acknowledged via the Terminal Module 54F (TM54F)
at safety-relevant inputs. or PROFIsafe.
1001: Initialization error of watchdog timer. See also: p9300 (SI Motion monitoring clock cycle (Motor Module)), p9500 (SI
1005: Pulses already suppressed for test stop selection. Motion monitoring clock cycle (Control
1011: Acceptance test status between the monitoring channels differ. Unit))
1012: Plausibility violation of the actual value from the encoder.
1020: Cyc. communication failure between the monit. cycles.
1021: Cyc. communication failure between the monit. channel and Sensor
Module.
1023: Error during the effectivity test in the Sensor Module.
1030: Encoder fault detected from another monitoring channel.
1031: Data transfer error between the monitoring channel and the Sensor
Module.
5000 ... 5140: PROFIsafe message values.
The significance of the individual message values is described in safety
message C01711 of the Control Unit.
6000 ... 6166: PROFIsafe message values (PROFIsafe driver for PROFIBUS
DP V1/V2 and PROFINET).
The significance of the individual message values is described in safety
message C01711 of the Control Unit.
See also: p9555 (SI Motion transition time STOP F to STOP B (Control Unit)),
Sinamics G130 C30714 SI Motion MM: Safely-Limited Speed exceeded The drive had moved faster than that specified by the velocity limit value - check the traversing/motion program in the control.
(p9331). The drive is stopped as a result of - check the limits for "Safely-Limited Speed" (SLS) and if required, adapt (p9331).
the configured stop response (p9363). This message can only be acknowledged via the Terminal Module 54F (TM54F)
Message value (r9749, interpret decimal): or PROFIsafe.
100: SLS1 exceeded. Note:
200: SLS2 exceeded. SI: Safety Integrated
300: SLS3 exceeded. SLS: Safely-Limited Speed / SG: Safely reduced speed
400: SLS4 exceeded. See also: p9331 (SI Motion SLS limit values (Motor Module)), p9363 (SI Motion
1000: Encoder limit frequency exceeded. SLS stop response (Motor Module))

Sinamics G130 C30798 SI Motion MM: Test stop running The test stop is active. None necessary.
The message is withdrawn when the test stop is finished.
Note:
SI: Safety Integrated

Sinamics G130 C30799 (F) SI Motion MM: Acceptance test mode active The acceptance test mode is active. The POWER ON signals of the safety- None necessary.
relevant motion monitoring functions can The message is withdrawn when exiting the acceptance test mode.
be acknowledged during the acceptance test using the acknowledgement Note:
functions of the higher-level control. SI: Safety Integrated

Sinamics G130 F01000 Sinamics / AIF VSD Internal Software Error An internal software error has occurred. Check fault value (r0949. - Carry out a POWER ON (power off/on) for all components
hexadecimal) - upgrade the firmware release, if possible
- Replace the Control Unit

Sinamics G130 F01001 Sinamics / AIF VSD Internal Software Error An internal software error has occurred. Check fault value (r0949. - Carry out a POWER ON (power off/on) for all components
hexadecimal) - upgrade the firmware release, if possible
- Replace the Control Unit

Sinamics G130 F01002 Sinamics / AIF VSD Internal Software Error An internal software error has occurred. Check fault value (r0949. - Carry out a POWER ON (power off/on) for all components
hexadecimal) - upgrade the firmware release, if possible
- Replace the Control Unit

Sinamics G130 F01003 Sinamics / AIF VSD Acknowledgement delay when accessing the A memory area was accessed that does not return a "READY". - Carry out a POWER ON (power off / on) for all components
memory Faule value (r949, hexadecimal)
Sinamics G130 F01005 Sinamics / AIF VSD Firmware download DRIVE - CLiQ component Firmware was not able to be downloaded into a DRIVE-CLiQ component. - Check the selected component number (P7828)
unsuccessful Fault value (r0949): - Check the DRIVE-CLiQ connection
xxyyyy hex: xx=component number, yyyy = cause of the fault - Save suitable firmware file for download in the directory
Cause of the fault (Decimal): /siemens/sinamics/code/sac/
011: DRIVE-CliQ component has detected a checksum error - After POWER ON has been carried-out again for the DRIVE-CLiQ component,
015: The selected DRI download the

Sinamics G130 F01010 Sinamics / AIF VSD Drive type unknown An unknown drive type was found. Check the EEPROM data of the drive objects.
Fault value (r0949, decimal).
Drive object number

Sinamics G130 F01015 Sinamics / AIF VSD Internal Software Error An internal software error has occurred. Check fault value (r0949. decimal) - Carry out a POWER ON (power off/on) for all components
- upgrade the firmware release, if possible
- Replace the Control Unit
Sinamics G130 F01030 Sinamics / AIF VSD Monitoring master control: Sign-of-life failure For active PC master control, no sign-of-life was received within the Set the monitoring time higher at the PC/AOP or disable completely.
PC monitoring time. The master control was returned to the active BICO Notice:
interconnection. The monitoring time should be set as short as possible. A long monitoring time
means a late response when the communications fail.
The monitoring time is set in milliseconds.
- in

Sinamics G130 F01036 Sinamics / AIF VSD ACX: Parameter back-up file missing When downloading the device parameterization, a file associate with a If you have saved your project data using STARTER, carry out a new download
drive object cannot be found. Neither a Psxxxyyy.ACX, a Psxxxyyy.NEW nor for your project. Save using the function 'Copy RAM to ROM" or with P0977 = 1
a Psxxxyyy.BAK exists on the CompactFlash card for this drive object. Fault so that all the parameter files are again completely written into the
value (r0949, hexadecimal) CompactFlash card.

If you have

Sinamics G130 F01037 Sinamics / AIF VSD ACX: Re-naming parameter file not successful The re-naming after saving a parameter -save file on the CompactFlash card Check whether one of the files to be overwritten has the attibute "read only"
was unsuccessful. One of the files to be re-named had the "read only" and change this file attribute into "writable". Check all the files (Psxxxyyy.*,
attribute. The parameter-save files are saved on the CompactFlash card in Ccxxxyyy.*, Caxxxyyy.*) that belong to drive yyy designated in the fault value.
the directory \USER\SINAMICS\DATA. Replace the Comp
I

Sinamics G130 F01039 Sinamics / AIF VSD ACX: Writing to the parametere back-up file Writing to at least one parameter back up file Psxxxyyy.acx on the - Check the file attribute of the files (Psxxxyyy.*, Caxxxyyy.*, Ccxxxyyy.*) and, if
was unsuccesful CompactFlash card was unsuccessful. required, change from "read only" to "writeable"
- on the CompactFlash card in the directory /USER/SINAMICS/DATA at least - Replace the CompactFlash card.
one parameter back up file has the "read only" file attribute and cannot be
sav

Sinamics G130 F01040 Sinamics / AIF VSD Save parameter settings and carry out a A parameter was changed in the drive system that means that it is - Save the parameters (P0971 / P0977)
POWER ON necessary to save the parameters and run-up again. (Eg. P0110) - Carry out a POWER ON (power off / on) for all components.
Sinamics G130 F01041 Sinamics / AIF VSD Parameter save necessary Defective or missing files were detected on the CompactFlash card at run - Save the parameters (P0977)
up. - Download the project again into te drive unit.
Fault value (r0949, decimal)
- 1: Source file cannot be opened
- 2: Source file cannot be read
- 3: Target directory cannot be set-up
- 4: Target file cannot be set up / opened
-

Sinamics G130 F01042 Sinamics / AIF VSD Parameter error during project download An error was detected when downloading a project using the - Enter the correct value into the specified parameter
commissioning (startup) software (eg incorrect parameter value) - Identify the parameter that narrows (restricts) the limits of the specified
For the specified parameter, it was detected that dynamic limits were parameter.
exceeded that could possibly depend on the other paramters. Se

Sinamics G130 F01043 Sinamics / AIF VSD Fatal error when downloading a project A fatal error was detected when downloading a project using the - Use the actual version of the commissioning software.
commissioning (startup) software (eg incorrect parameter value) - Modify the offline project and carry out a new download (eg. Compare the
See fault value (r0949, decimal), and refer to List Manual Sinamics G, page number of the drive objects, motor, encoder, power module in the offline
589 for more info) project and at the drive )
- Change the drive syste

Sinamics G130 F01044 Sinamics / AIF VSD CU CompactFlash: Message description An error was detected when loading the message descriptions Replace the CompactFlash card
incorrect (Fdxxxyyy.ACX) saved on the CompactFlash card.
Only for internal Siemens troubkeshooting

Sinamics G130 F01050 Sinamics / AIF VSD CompactFlash card and device not compatible The CompactFlash card and the device type do not match (eg. A - Insert the matching CompactFlash card
CompactFlash card for SINAMICS is inserted in SINAMICS G). - Use the matching Control Unit or power module
Sinamics G130 F01051 Sinamics / AIF VSD Drive object type is not available The drive object type in conjuction with the selected application-specific - For this drive object type (p0107), select a valid application-specific perspective
perspective is not available. The required descriptive file (Pdxxxyyy.ACX) (p0103).
does not exist on the CompactFlash card. - Save the required descriptive file (Pdxxxyyy.ACX) on the CompactFlash card.
Fault valur (r0949, decimal):
Index of P0103 and P0107. See also

Sinamics G130 F01105 Sinamics / AIF VSD CU: Insufficient memory Two many functions, data sets or drives configured on this Control Unit. - Change the configuration on this Control Unit
Fault value (r0949, decimal): Only for Internal Siemens troubleshooting - Use an additional Control Unit

Sinamics G130 F01107 Sinamics / AIF VSD CU: Save to CompactFlash card unsuccessful A data save on the CompactFlash card was not able to be successfully - Try to save again
carried-out. - Use another CompactFlash card
- 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

Sinamics G130 F01110 Sinamics / AIF VSD CU: More than one SINAMICS G on one Control More than one SINAMICS G pwer module type is being operated drom the Only one SINAMICS G drive type is permitted.
Unit Control Unit.
Fault Value (r0949, decimal):
Number of the second drive with a SINAMICS G power module type
Sinamics G130 F01111 Sinamics / AIF VSD CU: SINAMICS S and G together on one Control SINAMICS S and G drive units are being operated together on one Control Only power modules of one particular drive type may be operated with one CU
Unit Unit.
Fault Value (r0949, decimal):
Number of the first drive object with a different power module type.

Sinamics G130 F01120 Sinamics / AIF VSD Terminal initialization has failed An internal software error has occurred when initializing the terminal - Carry out a POWER ON (power off/on) for all components
functions on the CU3xx, the TB30 or the TM31. - Upgrade the firmware release
Fault value (r0949, hexadecimal): Only for internal Siemens troubleshooting - Contact the Hotline
- Replace the Control Unit.

Sinamics G130 F01122 Sinamics / AIF VSD Frequency at the measuring probe input too The frequency of the pulses at the measuring probe input is too high. Reduce the frequency of the pulses at the measuring probe input
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

Sinamics G130 F01150 Sinamics / AIF VSD CU: Number if instances of a drive object type The maximum permissable number of instances of a drive object type was - Power down the unit
have been exceeded exceeded. - Suitably restrict the number of instances of a drive object type by reducing the
Fault value (r0949, decimal): number of inserted components.
Byte 1: Drive object type (p0107) - Re-commission the unit
Byte 2: Max. permissible number of instances for this drive object type
Byte 3: Actual number of instances for

Sinamics G130 F01205 Sinamics / AIF VSD CU: Time slice overflow Insufficient processing time is available for the existing topology. - Reduce the number of drives
Fault value (r0949, hexadecimal). Only for internal Siemens troubleshooting - Increase the sampling times

Sinamics G130 F01210 Sinamics / AIF VSD CU: Basic clock cycle selection and DRIVE-CLiQ The parameter to select the basic clock cycle does not match the drive Only those drive objects may be connected to the same DRIVE-CLiQ socket of
clock cycles do not match topology. Drives connected to the same DRIVE-CLiQ port of the Control the Control Unit that should run with the same basic clock cycle. For example,
Unit have been assigned different basic clock cycles. Active Line Modules and Motor Modules shouldbe inserted at differen DRIVE-
Fault value (r0949, decimal): CLiQ ports as their basic c
The fault value speficies the

Sinamics G130 F01220 Sinamics / AIF VSD CU: Bas clock cyc too low The parameter for the basic clock cycle is set too short for the number of - Increase the basic clock cycle
connected drives. - Reduce the number of connected drives and start to re-commission the unit
Fault value (r0949, decimal): See also p0110
The fault specifies the parameter involved. See also P0110

Sinamics G130 F01221 Sinamics / AIF VSD CU: Bas clock too low The closed -loop control / monitoring cannot maintain the intended clock Increase the basic clock cycle of DRIVE-CLiQ communications.
cyle. See also P0112
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

Sinamics G130 F01250 Sinamics / AIF VSD CU: CU-EEPROM incorrect read-only data Errror when reading the read-only data of the EEPROM in the Control Unit. - Carry out a POWER ON
Fault value (r0949, decimal): Only for internal Siemens troubleshooting - Replace the Control Unit

Sinamics G130 F01255 Sinamics / AIF VSD CU: Opt. module EEPROM incorrect read-only Error when reading the read-only data of the EEPROM in the option - Carry out a POWER ON
data module. - Replace the Control Unit
Fault Value (r0949, decimal): Internal Siemens troubleshooting

Sinamics G130 F01303 Sinamics / AIF VSD DRIVE-CLiQ component does not support the A function requested by the Control Unit is not supported by a DRIVE-CLiQ Upgrade the firmware of the DRIVE-CLiQ component involved.
required function component.
Fault Value (r0949, decimal)
1: A component does not support the de-activation
101: The Motor Module does not support an internal armature short-
circuit.
102: The Motor M

Sinamics G130 F01305 Sinamics / AIF VSD Topology: Component number missing The component number from the topology was not parameterized (p0121 Enter the missing component number or remove the component and restart
(for power module, refer to P0107), P0131. (for Servo / vector drives, refer commissioning.
to p0107), p0141, p0151, p0161) See also, P0121, P0131, P0141, P0142, P0151, P0161, P0186, P0187, P0188,
Fault value (r0949, decimal) P0189
The fault value includes the particular data set

Sinamics G130 F01340 Topology: Too many components on one line For the selected communications clock cycle, too many DRIVE-CLiQ Check the DRIVE-CLiQ connection:
components are connected to one line of the Reduce the number of components on the DRIVE-CLiQ line involved and
Control Unit. distribute these to other DRIVE-CLiQ connections
Fault value (r0949, interpret hexadecimal): of the Control Unit. This means that communication is uniformly distributed over
xyy hex: x = fault cause, yy = component number or connection number. several communication
1yy: li
The communica
Sinamics G130 F01354 Topology: Actual topology indicates an illegal The actual topology indicates at least one illegal component. Remove the illegal components and restart the system.
component Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = cause.
xx = 1: Component at this Control Unit not permissible.
xx = 2: Component in combination with another co

Sinamics G130 F01355 Topology: Actual topology changed The device target topology (p0099) does not correspond to the device One of the following counter-measures can be selected if no faults have
actual topology (r0098). occurred in the topology detection itself:
The fault only occurs if the topology was commissioned using the If commissioning was still not completed:
automatic internal device mechanism and not using - carry out a self-commissioning routine (starting from p0009 = 1).
the commissioning software. General: Set p0099 to r0098, s
Fault value (r0949

Sinamics G130 F01360 Topology: Actual topology is illegal The detected actual topology is not permissible. Re fault cause = 1:
Fault value (r0949, interpret hexadecimal): Change the configuration. Connect less than 199 components to the Control
ccccbbaa hex: cccc = preliminary component number, aa = fault cause Unit.
aa = 01 hex = 1 dec: Re fault cause = 2:
Too many components were detected at the Control Unit. The maximum Remove the component with unknown component type.
permis Re fault cause = 3, 4, 5:
Establish a valid combination.
Re fault cause = 6, 7:
Conne

Sinamics G130 F01375 Topology: Actual topology, duplicate When detecting the actual topology, a ring-type connection was detected. Output the fault value and remove the specified connection.
connection between two components Fault value (r0949, interpret hexadecimal): Note:
ccbbaaaa hex: Under "Topology --> Topology view" the commissioning software offers
cc = connection number improved diagnostics capability (e.g. setpoint/
bb = component class actual value comparison).
aaaa = preliminary component number of a component included in the ring
Componen

Sinamics G130 F01380 Topology: Actual topology, defective EEPROM When detecting the actual topology, a component with a defective Output the fault value and remove the defected component.
EEPROM was detected.
Fault value (r0949, interpret hexadecimal):
bbbbaaaa hex:
aaaa = preliminary component number of the defective components

Sinamics G130 F01451 Topology: Target topology is invalid An error was detected in the target topology. Reload the target topology using the commissioning software.
The target topology is invalid.
Fault value (r0949, interpret hexadecimal):
ccccbbaa hex: cccc = index error, bb = component number, aa = fault cause
aa = 1B hex = 27 dec: Error not specified.
aa = 1C hex = 28

Sinamics G130 F01470 Topology: Target topology ring-type connection A ring-type connection was detected when writing to the target topology. Read out the fault value and remove one of the specified connections.
Fault value (r0949, interpret hexadecimal): Then download the target topology again using the commissioning software.
ddccbbaa hex: Note:
cc = connection number Under "Topology --> Topology view" the commissioning software offers
bb = component class improved diagnostics capability (e.g
aa = component number of a component included in the ring
Note:
Component class

Sinamics G130 F01475 Topology: Target topology duplicate When writing the target topology, a duplicate connection between two Read out the fault value and remove one of the two specified connections.
connection between two components components was detected. Then download the target topology again using the commissioning software.
Fault value (r0949, interpret hexadecimal): Note:
ddccbbaa hex: Under "Topology --> Topology view" the commissioning software offers
dd = connection number 2 of the duplicate connection improved diagnostics capability
cc = connection number 1 of the duplicate connecti

Sinamics G130 F01505 (A) BICO: Interconnection cannot be established A PROFIdrive telegram has been set (p0922). Establish another interconnection.
An interconnection contained in the telegram was not able to be
established.
Fault value (r0949, interpret decimal):
Parameter receiver that should be changed.

Sinamics G130 F01506 (A) BICO: No standard telegram The standard telegram in p0922 is not maintained and therefore p0922 is Again set the required standard telegram (p0922).
set to 999.
Fault value (r0949, interpret decimal):
BICO parameter for which the write attempt was unsuccessful.
Sinamics G130 F01507 (N,A) BICO: Internconnections to inactive objects There are BICO as signal drain from a drive object that is either inactive/not - set all open BICO interconnections centrally to the factory setting with p9495 =
present operational. 2.
The BI/CI parameters involved are listed in R9498. The associateed BO/CO - make the non-operational drive object active/operational again (re-insert or
parameters in R9499. activate components).
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

Sinamics G130 F01510 BICO: Signal source is not float type The requested connector output does not have the correct data type. This Interconnect this connector input with a connector output having a float data
interconnection is not established. type.
Fault value (r0949, interpret decimal):
Parameter number to which an interconnection should be made
(connector output).

Sinamics G130 F01511 (A) BICO: Interconnection between different The requested interconnection was established. However, a conversion is Example:
normalizations made between the BICO output and BICO The BICO output has, as normalized unit, voltage and the BICO input has current.
input using the reference values. This means that the factor p2002 (contains the reference value for current) /
- the BICO output has different normalized units than the BICO input. p2001 (contains the reference value for
- message only for interconnections withi voltage) is calculated between the BICO output

Sinamics G130 F01512 BICO: No normalization available An attempt was made to determine a conversion factor for a normalization Apply normalization or check the transfer value.
that does not exist.
Fault value (r0949, interpret decimal):
Unit (e.g. corresponding to SPEED) for which an attempt was made to
determine a factor.

Sinamics G130 F01513 (A) BICO: Spanning DO between different The requested interconnection was established. However, a conversion is None necessary.
normalizations made between the BICO output and BICO
input using the reference values.
An interconnection is made between different drive objects and the BICO
output has different normalized units t

Sinamics G130 F01515 (A) BICO: Writing to parameter not permitted as While changing the number of CDS or when copying from CDS, the master None necessary.
the master control is active control was active.
Sinamics G130 F01600 SI CU: STOP A initiated The drive-based "Safety Integrated" function in the Control Unit (CU) has - select Safe Torque Off and de-select again.
detected a fault and initiated a STOP A - replace the Motor Module involved.
(pulse suppression via the safety shutdown path of the Control Unit). Re fault value = 9999:
- forced checking procedure of the safety shutdown path of the Control - carry out diagnostics for fault F01611.
Note:
CU: Control Unit
MM: Motor Module
SI: Safety Integrated
STO: Safe Torque Off / SH: Safe standstill

Sinamics G130 F01611 SI CU: Defect in a monitoring channel The drive-based "Safety Integrated" function in the Control Unit (CU) has Re fault value = 1 to 5 and 7 to 999:
detected a fault in the data cross-check - check the cross-checked data that resulted in a STOP F.
between the CU and Motor Module (MM) and initiated a STOP F. - carry out a POWER ON (power off/on) for all components.
As a result of this fault, after the parameterized transition has expired - upgrade the Motor Module software.
(p965 - upgrade the Control Unit software.
Re fault value = 6:
- carry

Sinamics G130 F01612 SI CU: STO inputs for power units connected in The drive-based "Safety Integrated" function on the Control Unit (CU) has - check the tolerance time SGE changeover and if required, increase the value
parallel different identified different states of the AND'ed (p9650).
STO inputs for power units connected in parallel and has initiated a STOP F. - check the wiring of the safety-relevant inputs (SGE) (contact problems).
As a result of this fault, after the parameterized transition Note:
CU: Control Unit
SGE: Safety-relevant input
SI: Safety Integrated
STO: Safe Torque Off

Sinamics G130 F01625 SI CU: Sign-of-life error in safety data The drive-based "Safety Integrated" function in the Control Unit (CU) has - select Safe Torque Off and de-select again.
detected an error in the sign-of-life of the - carry out a POWER ON (power off/on) for all components.
safety data between the CU and Motor Module (MM) and initiated a STOP - check whether there is a DRIVE-CLiQ communication error between the Control
A. Unit and the Motor Module
- there is either a DRIVE-CLiQ communication error or communica involved and, if required, carry out a diagnost
Sinamics G130 F01630 SI CU: Brake control error The drive-based "Safety Integrated" function in the Control Unit (CU) has - check parameter p1278 (for SBC, only p1278 = 0 is permissible).
detected a brake control error and initiated - select Safe Torque Off and de-select again.
a STOP A. - check the motor holding brake connection.
Fault value (r0949, interpret decimal): - check the function of the motor holding brake.
10, 11: - check whether there is a DRIVE-CLiQ communicatio
Fault in "open holding brake" operation.
- Parameter p1278 incorrectly set.
-

Sinamics G130 F01649 SI CU: Internal software error An internal error in the Safety Integrated software on the Control Unit has - carry out a POWER ON (power off/on) for all components.
occurred. - re-commission the "Safety Integrated" function and carry out a POWER ON.
Note: - upgrade the Control Unit software.
This fault results in a STOP A that cannot be acknowledged. - contact the Hotline.
Fault value (r0949, interpret hexadecimal): - replace the Control Unit.
Only for internal Siemens troubleshooting. Note:
CU: Control Unit
MM: Motor M

Sinamics G130 F01650 SI CU: Acceptance test required The drive-based "Safety Integrated" function in the Control Unit requires Re fault value = 130:
an acceptance test. - carry out safety commissioning routine.
Note: Re fault value = 1000:
This fault results in a STOP A that can be acknowledged. - again carry out safety commissioning routine.
Fault value (r0949, interpret decimal): - replace the CompactFlash card.
130: Safety parameters for the Motor Module not available. Re fault value = 2000:
- check the safety parameters in the Control Unit and adapt the

Sinamics G130 F01651 SI CU: Synchronization safety time slices The "Safety Integrated" function requires a synchronization of the safety Re fault value = 150:
unsuccessful time slices between the Control Unit (CU) - check the setting of p9510 (SI Motion clock-cycle synchronous PROFIBUS
and Motor Module (MM) and between the Control Unit and the higher- master) and if required, correct.
level control. This synchronization routine was General:
unsuccessful. - carry out a POWER ON (power off/on) for all components.
Note: - upgrade the Motor Module software.
This - upgrade the Control

Sinamics G130 F01652 SI CU: Illegal monitoring clock cycle One of the Safety Integrated monitoring clock cycles is not permissible: For enabled drive-based SI monitoring (p9601/p9801 > 0):
- the drive-based monitoring clock cycle cannot be maintained due to the - upgrade the Control Unit software.
communication conditions required in the For enabled motion monitoring function (p9501 > 0):
system. - correct the monitoring clock cycle (p9500) and carry out POWER ON.
- the monitoring clock cycle for safe motion monitoring func Re fault value 101:
- the actual value s

Sinamics G130 F01653 SI CU: PROFIBUS configuration error There is a PROFIBUS configuration error for using Safety Integrated Re fault value = 250:
monitoring functions with a higher-level control - remove the PROFIsafe configuring in the higher-level F control or enable
(SINUMERIK or F-PLC). PROFIsafe in the drive.
Note: The following generally applies:
For safety functions that have been enabled, this fault results in a STOP A - check the PROFIBUS configuration of the safety slot on the master side and, if
that cannot be acknowledged. necessary, correct.
Fault

Sinamics G130 F01655 SI CU: Align monitoring functions An error has occurred when aligning the Safety Integrated monitoring - carry out a POWER ON (power off/on) for all components.
functions on the Control Unit (CU) and Motor - upgrade the Motor Module software.
Module (MM). Control Unit and Motor Module were not able to determine - upgrade the Control Unit software.
a common set of supported SI monitoring - check the electrical cabinet design and cable routing for EMC compliance
functions. Note:
- there is either a CU: Control Unit
MM: Motor Module
SI: Safe

Sinamics G130 F01656 SI CU: Motor Module parameter error When accessing the Safety Integrated parameters for the Motor Module - re-commission the safety functions.
(MM) on the CompactFlash card, an error - upgrade the Control Unit software.
has occurred. - upgrade the Motor Module software.
Note: - replace the CompactFlash card.
This fault results in a STOP A that can be acknowledged. Re fault value = 132:
Fault value (r0949, interpret decimal): - check the electrical cabinet design and cable routing for EMC compliance
129: Safety parameters for th Note:
CU: Con

Sinamics G130 F01659 SI CU: Write request for parameter rejected The write request for one or several Safety Integrated parameters on the Re fault value = 1:
Control Unit (CU) was rejected. - set the Safety Integrated password (p9761).
Note: Re fault value = 2:
This fault does not result in a safety stop response. - inhibit Safety Integrated and again reset the drive parameters.
Fault value (r0949, interpret decimal): Re fault value = 3:
1: The Safety Integrated password is not set. - end the simulation mode for the digital input (p0795).
2: A Re fault value = 10, 11, 1
Sinamics G130 F01660 SI CU: Safety-related functions not supported The Motor Module (MM) does not support the safety-related functions - use a Motor Module that supports the safety-related functions.
(e.g. the Motor Module version is not the correct - upgrade the Motor Module software.
one). Safety Integrated cannot be commissioned. Note:
Note: CU: Control Unit
This fault does not result in a safety stop response. MM: Motor Module
SI: Safety Integrated

Sinamics G130 F01663 SI CU: Copying of SI parameters rejected One of the following values is stored in p9700 or has been entered offline: - set p9700 = 0.
87 or 208. This is the reason that the - check p9501and p9601 and correct if necessary.
system is attempting to copy the SI parameters from the Control Unit to - start the copy function again by entering the appropriate value in p9700.
the Motor Module during booting. However,
no safety function is sele

Sinamics G130 F01664 SI CU: No automatic firmware update When booting, parameter p7826 "automatic firmware update" did not For enabled drive-based SI monitoring:
have the value "1" that is required for the automatic 1. Set parameter p7826 to the value 1
firmware upgrade/downgrade. This means that when the safety functions 2. Save the parameter (p0977 = 1) and carry out a power-on reset
are enabled, an inadmissible combination When de-activating the drive-based SI monitoring (p9601 = 0), the alarm can be
of versions can occur. acknowledged after exiting the
N saf

Sinamics G130 F01670 SI Motion: Invalid parameterization Sensor The parameterization of a Sensor Module used for Safety Integrated is not Re fault value = 1, 2:
Module permissible. - use and parameterize an encoder that Safety Integrated supports (encoder
Note: with track A/B sine-wave, p0404.4 = 1).
This fault results in a STOP A that cannot be acknowledged. Re fault value = 3:
Fault value (r0949, interpret decimal): - check whether the drive or drive commissioning function is active and if
1: No encoder was parameterized for Safety Integrated. required, exit this (p
2: An e

Sinamics G130 F01671 SI Motion: Parameterization encoder error The parameterization of the encoder used by Safety Integrated is different Align the encoder parameterization between the safety encoder and the
to the parameterization of the standard standard encoder.
encoder. Note:
Note: SI: Safety Integrated
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
Parameter number of the non-cor

Sinamics G130 F01672 SI Motion: Motor Module software/hardware The existing Motor Module software does not support safe motion - check whether there are faults in the safety function alignment between the
incompatible monitoring or is not compatible to the software on Control Unit and the Motor Module
the Control Unit or there is a communications error between the Control involved
Unit and Motor Module. (F01655, F30655) and if required, carry out the appropriate diagnostics routine
Note: for the particular faults.
This fault results in a STOP A that can Re fault value = 1:
- use a

Sinamics G130 F01673 SI Motion: Sensor Module software/hardware The existing Sensor Module software and/or hardware does not support - upgrade the Sensor Module software.
incompatible the safe motion monitoring function with the - use a Sensor Module that supports the safe motion monitoring function.
higher-level control. Note:
Note: SI: Safety Integrated
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
Only for internal S

Sinamics G130 F01680 SI Motion CU: Checksum error safety The actual checksum calculated by the drive and entered in r9728 via the - Check the safety-relevant parameters and if required, correct.
monitoring functions safety-relevant parameters does not match - carry out a POWER ON.
the reference checksum saved in p9729 at the last machine acceptance. - carry out an acceptance test.
Safety-relevant parameters have been changed or a fault is present. Note:
No SI: Safety Integrated

Sinamics G130 F01681 SI Motion CU: Incorrect parameter value The parameter cannot be parameterized with this value. Correct the parameter value.
Note:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
Parameter number with the incorrect value.

Sinamics G130 F01682 SI Motion CU: Monitoring function not The monitoring function enabled in p9501, p9601 or p9801 is not De-select the monitoring function involved (p9501, p9503, p9601, p9801).
supported supported in this firmware version. Note:
Note: SCA: Safe Cam / SN: Safe software cam
This fault results in a STOP A that cannot be acknowledged. SI: Safety Integrated
Fault value (r0949, interpret decimal): SLP: Safely-Limited Position / SE: Safe software limit switches
1: Monitoring function SLP not supported (p9501.1 SLS: Safely-Limited Speed / SG: Safely reduced speed

Sinamics G130 F01683 SI Motion CU: SOS/SLS enable missing The safety-relevant basic function "SOS/SLS" is not enabled in p9501 Enable the function "SOS/SLS" (p9501.0) and carry out a POWER ON.
although other safety-relevant monitoring Note:
functions are enabled. SI: Safety Integrated
Note: SLS: Safely-Limited Speed / SG: Safely reduced speed
This fault does not result in a safety stop response. SOS: Safe Operating Stop / SBH: Safe operating stop
See also: p9501 (SI Motion enable safety functions (Cont
Sinamics G130 F01684 SI Motion: Safely limited position limit values For the function "Safely-Limited Position" (SE), a lower value is in p9534 Correct the limit values in p9534 and p9535 and carry out a POWER ON.
interchanged than in p9535. Note:
Note: SI: Safety Integrated
This fault does not result in a safety stop response. SLP: Safely-Limited Position / SE: Safe software limit switches
Fault value (r0949, interpret decimal):
1: Limit values SLP1 interchanged.
2: Limit values SLP2 interchan

Sinamics G130 F01685 SI Motion CU: Safely-limited speed limit value The limit value for the function "Safely-Limited Speed" (SLS) is greater than Correct the limit values for SLS and carry out a POWER ON.
too high the speed that corresponds to an Note:
encoder limit frequency of 500 kHz. SI: Safety Integrated
Note: SLS: Safely-Limited Speed / SG: Safely reduced speed
This fault does not result in a safety stop response. See also: p9531 (SI Motion SLS (SG) limit values (Control Unit))
Fault value (r0949, interpret decimal):
Maximum

Sinamics G130 F01686 SI Motion: Illegal parameterization cam At least one enabled "Safety Cam" (SCA) is parameterized in p9536 or Correct the cam position and carry out a POWER ON.
position p9537 too close to the tolerance range around Note:
the modulo position. SCA: Safe Cam / SN: Safe software cam
The following conditions must be complied with to assign cams to a cam SI: Safety Integrated
track: See also: p9536 (SI Motion SCA (SN) plus cam position (Control Unit)), p9537 (SI
- the cam length of cam x = p9536[x]-p953 Motion SCA (SN) plus cam position
(Control Unit))

Sinamics G130 F01687 SI Motion: Illegal parameterization modulo The parameterized modulo value for the "Safe Cam" (SCA) function is not a Correct the modulo value for SCA and carry out a POWER ON.
value SCA (SN) multiple of 360 000 mDegrees. Note:
Note: SCA: Safe Cam / SN: Safe software cam
This fault does not result in a safety stop response. SI: Safety Integrated
See also: p9505 (SI Motion SCA (SN) modulo value (Control Unit))

Sinamics G130 F01688 SI Motion CU: Actual value synchronization not It is not permissible to simultaneously enable the actual value Either de-select the function "actual value synchronization" or the monitoring
permissible synchronization and a monitoring function with absolute functions with absolute reference
reference (SCA/SLP). (SCA/SLP) and carry out a POWER ON.
Note: Note:
This fault results in a STOP A that cannot be acknowledged. SCA: Safe Cam / SN: Safe software cam
SI: Safety Integrated
SLP: Safely-Limited Position / SE: Safe

Sinamics G130 F01690 SI Motion: Data save problem for the NVRAM There is not sufficient memory space in the NVRAM on the drive to save Re fault value = 0:
parameters r9781 and r9782 (safety logbook). - use a Control Unit NVRAM.
Note: Re fault value = 1:
This fault does not result in a safety stop response. - deselect functions that are not required and that take up memory space in the
Fault value (r0949, interpret decimal): NVRAM.
0: There is no physical NVRAM available - contact the Hotline.

Sinamics G130 F01800 DRIVE-CLiQ: Hardware/configuration error A DRIVE-CLiQ connection fault has occurred. Re fault value = 100 ... 107:
Fault value (r0949, interpret decimal): - ensure that the DRIVE-CLiQ components have the same firmware releases.
100 ... 107: - avoid longer topologies for short current controller clock cycles.
Communication via DRIVE-CLiQ sockets X100 ... X107 has not switched to Re fault value = 10:
cyclic mode. The cause may be an incorrect - check the DRIVE-CLiQ cables at the Control Unit.
structure or a configuration that results in - remove an

Sinamics G130 F01802 (A) CU DRIVE-CLiQ: POWER ON due to basic It is not possible to change the DRIVE-CLiQ basic sampling times p0110 in - save (p0971 = 1).
sampling times operation. POWER ON is required. - carry out a POWER ON.
Fault value (r0949, interpret decimal):
Index of p0110.

Sinamics G130 F01840 SMI: Component found with changed data Another Sensor Module Integrated (SMI) was found. Re 1.
The reasons could be as follows: - restore the factory setting.
1. A motor with DRIVE-CLiQ (SMI) and another order No. were used as - carry out the first commissioning.
replacement. Re 2.
2. A Sensor Module Integrated was used as spare part where there is no - download the SMI data from the back-up (p4690, p4691).
encoder data and mot - carry out a POWER ON (power off/on) for all components.

Sinamics G130 F01910 (N, A) PROFIBUS: Setpoint timeout The receipt of setpoints from the PROFIBUS interface is interrupted Restore the bus connection and set the PROFIBUS master to RUN.
because the bus connection is interrupted or the See also: p2047 (PROFIBUS additional monitoring time)
PROFIBUS master is switched off or was set to the STOP state.
See also: p2047 (PROFIBUS additional monitoring time)

Sinamics G130 F01911 IF1: PB/PN clock cycle synchronous operation The global control telegram to synchronize the clock cycles has failed - in - check whether communication was briefly or permanently interrupted.
clock cycle failure cyclic operation - for several DP clock - check the bus and master for utilization level (e.g. bus cycle time Tdp was set
cycles or has violated the time grid specified in the parameterizing too short).
telegram over several consecutive DP clock Note:
cycles (refer to the bus cy IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
Sinamics G130 F01912 IF1: PB/PN clock cycle synchronous operation The maximum permissible number of errors in the master sign-of-life (clock - check the physical bus configuration (terminating resistor, shielding, etc.).
sign-of-life failure synchronous operation) has been - correct the interconnection of the master sign-of-life (p2045).
exceeded in cyclic operation. - check whether the master correctly sends the sign-of-life (e.g. create a trace
with STW2.12 ... STW2.15 and

Sinamics G130 F01913 (N, A) COMM INT: Monitoring time sign-of-life The monitoring time for the sign-of-life counter has expired. - wait until the control has re-booted.
expired The connection between the drive and the higher-level control (SIMOTION, - restore data transfer to the control.
SINUMERIK) has been interrupted for
the following reasons:
- the control was reset.
- the data transfer to the control w

Sinamics G130 F01914 (N, A) COMM INT: Monitoring time configuration The monitoring time for the configuration has expired. - acknowledge faults that are present.
expired Fault value (r0949, interpret decimal): - carry out a POWER ON (power off/on) for all components.
0: The transfer time of the send configuration data has been exceeded. - upgrade firmware to later version.
1: The transfer time of the receive configuration data has been exceeded. - contact the Hotline.

Sinamics G130 F01946 (A) PROFIBUS: Connection to the Publisher aborted At this drive object, the connection to at least one Publisher for PROFIBUS - check the PROFIBUS cables.
peer-to-peer data transfer in cyclic operation - check the state of the Publisher that has the aborted connection.
has been aborted. See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses)
Alarm value (r2124, interpret binary):
Bit 0 = 1: Publisher with address in r2077[0], connection aborted.
...
Bit

Sinamics G130 F01950 (N, A) IF1: PB/PN clock cycle synchronous operation Synchronization of the internal clock cycle to the global control telegram Only for internal Siemens troubleshooting.
synchronization unsuccessful has failed. The internal clock cycle exhibits Note:
an unexpected shift. IF1: Interface 1
PB: PROFIBUS
PN: PROFINET

Sinamics G130 F01951 CU DRIVE-CLiQ: Synchronization application If DRIVE-CLiQ components with different application clock cycle are - carry out a POWER ON (power off/on) for all components.
clock cycle missing operated at a DRIVE-CLiQ port, then this - upgrade the software of the DRIVE-CLiQ components.
requires synchronization with the Control Unit. - upgrade the Control Unit software.
This synchronization routine was unsuccessful.
Fault value (r0949, interpret decimal):
Only for in

Sinamics G130 F01952 CU DRIVE-CLiQ: Synchronization of component The existing system configuration requires that the connected DRIVE-CLiQ Upgrade the firmware of the component specified in the fault value.
not supported components support the synchronization Note:
between the basic clock cycle, DRIVE-CLiQ clock cycle and the application If required, also upgrade additional components in the DRIVE-CLiQ line.
clock cycle.
However, not all DRIVE-CLiQ components have this functio

Sinamics G130 F01954 CU DRIVE-CLiQ: Synchronization unsuccessful After the drive system is powered up, the synchronization between the 1. Ensure perfect functioning of the DRIVE-CLiQ.
basic clock cycle, DRIVE-CLiQ clock cycle 2. Initiate a new synchronization, e.g. as follows:
and application clock cycle was started and was not able to be successfully - remove the PROFIBUS master and re-insert again.
completed. - restart the PROFIBUS master.
Fault value (r0949, interpret decimal): - power down the Control Unit and power it up again.
Only for internal Siemens troubleshooting - press the Control Unit reset button.
- reset the parameter and download the saved parameters (p0009 = 30, p0976 =
2).

Sinamics G130 F02080 Trace: Delete trace because units changed over The trace was deleted due to the fact that the units were changed over or
the reference parameters changed.
Sinamics G130 F02151 (A) OA: internal software error An internal software error has occurred within an OA application. - carry out a POWER ON (power off/on) for all components.
Fault value (r0949, interpret hexadecimal): - upgrade firmware to later version.
Only for internal Siemens troubleshooting. - contact the Hotline.
- replace the Control Unit.
Note:
OA: Open Architecture
See also: r4950, r4955, p4956, r4957

Sinamics G130 F02152 (A) OA: Insufficient memory Too many functions have been configured on this Control Unit (e.g. too - change the configuration on this Control Unit (e.g. fewer drives, function
many drives, function modules, data sets, modules, data sets, OA applications,
OA applications, blocks, etc). blocks, etc).
Fault value (r0949, interpret decimal): - use an additional Control Unit.
Only for internal Siemens troubleshooting. Note:
OA: Open Architecture

Sinamics G130 F03500 Sinamics / AIF VSD TM: Initialization When initializaing the Terminal Modules, the terminal of the Control Unit - Power down the power supply for the Control Unit and power up again.
or the Terminal Board 30, an internal software error has occurred. - Check the DRIVE-CLiQ connection
Fault Value (r0949, decimal): - If required, replace the Terminal Module.
The thousands location: 1 . . . 3: The Terminal Module should be directly connected to a DRIVE-CLiQ socket of the
The component number (P0151) of the module involv Control Unit.
If fault occu
Sinamics G130 F03505 Sinamics / AIF VSD TM: Analo input, wire breakage The input currentn of the TM analog input has exceeded the threshold Check the connection to the signal source for interruptions
value parameterized in P4061[x]. Check the magnitude of the impressed current - it is possible that the impressed
This fault can only occur, if P4056[x] = 3 (4 . . . 20 mA with monitoring) is signl is too low
set. Please note that the input has a great resistor of 250Ohms
Index x = 0: Analog input 0 (X522.1 to .3) The input current measured by the TM
Index x = 1: Analog input 1

Sinamics G130 F03590 Sinamics / AIF VSD TM: Module not ready The Terminal Module involved does not send a ready signal and no valid - Check he 24V power supply
cyclic data. - Check the DRIVE-CLiQ connection
Fault value (r0949, decimal)
Drive object number

Sinamics G130 F05050 Sinamics / AIF VSD Parallel circuit configuration: Pulse enable in A power module signals that the pulses are enabled although the pulses The power module is defective and must be replaced
spite of pulse inhibit are inhibited.
Fault value (r0949, decimal): Number of the power module involved.

Sinamics G130 F05051 Sinamics / AIF VSD Parallel circuit configuration: Power module For one or several power modules, the pulses were not able to be enabled. - Acknowledge power module faults that are still present
pulse enable missing Fault value (r0949, decimal): Number of the power module involved - Inhibit the pulses of the power module involved (P7001)

Sinamics G130 F05055 Power circuit: Power units with different code The code numbers of the power units do not match. For parallel circuit configurations, only power units with identical power unit
numbers Fault value (r0949, interpret decimal): data may be used.
Parameter in which the first different power unit code number was
detected.

Sinamics G130 F05056 Parallel circuit: Power unit EPROM versions The EEPROM versions of the power units do not match. For parallel circuit configurations, only power units with identical EEPROM
differ Fault value (r0949, interpret decimal): versions may be used.
Parameter in which the first different version number was detected.

Sinamics G130 F05057 Parallel circuit: Power unit firmware versions The firmware versions of the power units connected in parallel do not For parallel circuit configurations, only power units with identical firmware
differ match. versions may be used.
Fault value (r0949, interpret decimal):
Parameter in which the first different version number was detected.

Sinamics G130 F05058 Parallel circuit: VSM EEPROM versions differ The EEPROM versions of the Voltage Sensing Modules (VSM) do not match. For parallel circuit configurations, only Voltage Sensing Modules (VSM) with
Fault value (r0949, interpret decimal): identical EEPROM versions may be
Parameter in which the first different version number was detected. used.

Sinamics G130 F05059 Parallel circuit: VSM firmware versions differ The firmware versions of the Voltage Sensing Module (VSM) do not match. For parallel circuit configurations, only Voltage Sensing Modules (VSM) with
Fault value (r0949, interpret decimal): identical firmware versions may be
Parameter in which the first different version number was detected. used.

Sinamics G130 F05060 Parallel circuit: Power unit firmware version Firmware from version V02.30.01.00 is required when connecting the Update the firmware of the power units (at least V02.30.01.00).
does not match power units in parallel
Sinamics G130 F05061 Infeed, number of VSM The number of active Voltage Sensing Modules (VSM) for the drive object Adapts the number of active Voltage Sensing Modules (VSM).
infeed with chassis power units is not correct.
For A_Infeed, each active power unit must be assigned an active VSM also
for a parallel circuit configuration.
For S_Infeed, the active drive object, must be assigned at least one active
VSM.
Fault value (r0949, interpret decimal):
Number of VSMs that are currently assigned to the drive object.

Sinamics G130 F06310 (A) Supply voltage (p0210) incorrectly For AC/AC drive units, the measured DC voltage lies outside the tolerance - check the parameterized supply voltage and if required change (p0210).
parameterized range after pre-charging has been completed: - check the line supply voltage.
1.16 * p0210 < r0070 < 1.6 * p0210. See also: p0210 (Drive unit line supply voltage)
The fault can only be acknowledged when the drive is powered down.
See also: p0210 (Drive unit line supply voltage)
Sinamics G130 F07011 Drive: Motor overtemperature KTY: - reduce the motor load.
The motor temperature has exceeded the fault threshold (p0605) or the - check the ambient temperature.
timer (p0606) after the alarm threshold was - check the wiring and sensor connector.
exceeded (p0604) has expired. See also: p0604 (Motor overtemperature alarm threshold), p0605 (Motor
The response parameterized in p0610 becomes active. overtemperature fault threshold), p0606
PTC: (Motor overtemperature timer)
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)

Sinamics G130 F07016 Drive: Motor temperature sensor fault An error was detected when evaluating the temperature sensor set in - check that the sensor is connected correctly.
p0600 and p0601. - check the parameterization (p0600, p0601).
Possible causes: - induction motors: De-activate temperature sensor fault (p0607 = 0).
- wire breakage or sensor not connected (KTY: R > 1630 Ohm). See also: r0035, p0600, p0601, p0607, p4600, p4601, p4602, p4603, r4620
- measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm).
Note:
If alarm A07015 is present, the time in p0607 is started. If the fault is still
present after this time has expired, then
fault F07016 is output; however, at the earliest, 1 s after alarm A07015.
Fault value (r0949, interpret decimal):
For SME selected (p0601 = 10), number of the sensor channel leading to
the message.
See also: p0607 (Temperature sensor fault timer)

Sinamics G130 F07080 Drive: Incorrect control parameter The closed-loop control parameters have been parameterized incorrectly Modify the parameter indicated in the fault value (r0949) (e.g. p0640 = current
(e.g. p0356 = L_spread = 0). limit > 0).
Fault value (r0949, interpret decimal): See also: p0311, p0341, p0344, p0350, p0354, p0356, p0358, p0360, p0400,
The fault value includes the parameter number involved. p0404, p0408, p0640, p1082
The following parameter numbers only occur as fault values for vector
drives:
p0310, for synchronous motors: p0341, p0344, p0350, p0357
The following parameter numbers do not occur as fault values for
synchronous motors:
p0354, p0358, p0360
See also: p0310, p0311, p0341, p0344, p0350, p0354, p0356, p0357,
p0358, p0360, p0400, p0404, p0408, p0640,
p1082, p1300

Sinamics G130 F07082 Macro: Execution not possible The macro cannot be executed. - check the parameter involved.
Fault value (r0949, interpret hexadecimal): - check the macro file and BICO interconnection.
ccccbbaa hex: See also: p0015, p0700 (Macro Binector Input (BI)), p1000 (Macro Connector
cccc = preliminary parameter number, bb = supplementary information, aa Inputs (CI) for speed setpoints), p1500
= fault cause (Macro Connector Inputs (CI) for torque setpoints)
Fault causes for the trigger parameter itself:
-20: Called file is not valid for parameter 15.
-21: Called file is not valid for parameter 700.
-22: Called file is not valid for parameter 1000.
-23: Called file is not valid for parameter 1500.
-24: Data type of a TAG is incorrect (e.g.: Index, number or bit is not U16).
Fault causes for the parameters to be set:
-25: Error level has an undefined value.
-26: Mode has an undefined value.
-27: A value was entered as string in the tag value that is not "DEFAULT".
Sinamics G130 F07083 Macro: ACX file not found The ACX file (macro) to be executed was not able to be found in the - check whether the file is saved in the appropriate directory on the memory
appropriate directory. card.
Fault value (r0949, interpret decimal): Example:
Parameter number with which the execution was started. If p0015 is set to 1501, then the selected ACX file must be located in the
See also: p0015, p0700 (Macro Binector Input (BI)), p1000 (Macro following directory:
Connector Inputs (CI) for speed setpoints), p1500 ... /PMACROS/DEVICE/P15/PM001501.ACX
(Macro Connector Inputs (CI) for torque setpoints)

Sinamics G130 F07084 Macro: Condition for WaitUntil not fulfilled The WaitUntil condition set in the macro was not fulfilled in a certain Check and correct the conditions for the WaitUntil loop.
number of attempts.
Fault value (r0949, interpret decimal):
Parameter number for which the condition was set

Sinamics G130 F07085 Drive: Open-loop/closed-loop control Parameters of the open-loop/closed-loop control had to be changed as It is not necessary to change the parameters as they have already been correctly
parameters changed they exceeded dynamic limits as a result of limited.
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)

Sinamics G130 F07086 Units changeover: Parameter limit violation A reference parameter was changed in the system. This resulted in the fact Check the adapted parameter value and if required correct.
due to reference value change that for the parameters involved, the See also: r9450 (Reference value change parameter with unsuccessful
selected value was not able to be written in the per unit representation calculation)
(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

Sinamics G130 F07100 Drive: Sampling times cannot be reset When resetting drive parameter (p0976) sampling times cannot be reset - continue to work with the set sampling times.
using p0111, p0112, p0115. - before resetting the drive parameters, set the basic clock cycle p0110[0] to the
Fault value (r0949, interpret decimal): original value.
Parameter whose setting prevents the sampling times being reset. See also: r0110 (Basic sampling times)
See also: r0110 (Basic sampling times)

Sinamics G130 F07110 Drive: Sampling times and basic clock cycle do The parameterized sampling times do not match the basic clock cycle. Enter the current controller sampling times so that they are identical to the basic
not match Fault value (r0949, interpret decimal): clock cycle, e.g. by selecting p0112.
The fault value specifies the parameter involved. Note which basic clock cycle is selected in p0111.
See also: r0110, r0111, p0115 The sampling times in p0115 can only be changed manually in the sampling
times presetting "Expert" (p0112).
See also: r0110, r0111, p0112, p0115

Sinamics G130 F07210 Master control PC/AOP inhibited The transfer of master control is disabled via binector input p3985. Change the signal via binector input p3985.
Sinamics G130 F07220 (N,A) Drive: Master control by PLC missing The "master control by PLC" signal was missing in operation. - check the interconnection of the binector input for "master control by PLC"
- interconnection of the binector input for "master control by PLC" is (p0854).
incorrect (p0854). - check the "master control by PLC" signal and, if required, switch in.
- the higher-level control has withdrawn the "master control by PLC" signal. - check the data transfer via the fieldbus (master/drive).
- data transfer via the fieldbus (master/drive) was interrupted 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.

Sinamics G130 F07300 (A) Drive: Line contactor feedback signal missing - the line contactor was not able to be closed within the time in p0861. - check the setting of p0860.
- the line contactor was not able to be opened within the time in p0861. - check the feedback circuit from the line contactor.
- the line contactor has dropped out in operation. - increase the monitoring time in p0861.
- the line contactor has closed although the drive converter is powered See also: p0860 (Line cont. fdbk sig), p0861 (Line contactor monitoring time)
down.
Sinamics G130 F07311 Bypass motor switch Fault value: Bit field BYPASS_CONTACTOR_ERROR_STATE - check the transfer of the feedback signals.
Bit 1 - check the switch
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)

Sinamics G130 F07312 Bypass LSS: Fault value: Bit field BYPASS_CONTACTOR_ERROR_STATE - check the transfer of the feedback signals.
Bit 1 - check the switch
BYPASS_CONTACTOR_ERR_FBK_ON_MISSING
Switch "Closed" feedback signal missing
Bit 2
BYPASS_CONTACTOR_ERR_FBK_OFF_MISSING
Switch "opened" feedback signal missing

Sinamics G130 F07320 Drive: Automatic restart interrupted - The specified number of restart attempts (p1211) has been completely - increase the number of restart attempts (p1211). The current number of
used up because within the monitoring time starting attempts is displayed in r1214.
(p1213) the faults were not able to be acknowledged. The number of - increase the delay time in p1212 and/or the monitoring time in p1213.
restart attempts (p1211) is decremented at each - issue an ON command (p0840).
new start attempt. - either increase or disable the monitoring time of the power unit (p0857).
- there is no active ON command.
- the monitoring time for the power unit has expired (p0857).
- when exiting commissioning or at the end of the motor identification
routine or the speed controller optimization, the
drive unit is not automatically powered up again.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.

Sinamics G130 F07330 Flying restart: Measured search current too low During a flying restart, it was identified that the search current reached is Check the motor feeder cables.
too low.
It is possible that the motor is not connected.

Sinamics G130 F07331 FlyRestart: Not Supported It is not possible to power up with the motor rotating (no flying restart). In - de-activate the "flying restart" function (p1200 = 0).
the following cases, the "flying restart" function - change the open-loop/closed-loop control mode (p1300).
is not supported: - connect a Voltage Sensing Module (VSM) (voltage measurement).
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.

Sinamics G130 F07430 (N,A) Drive: Lower DC link voltage threshold reached The DC link voltage monitoring is active (p1240 , p1280 = 5, 6) and the - check the line supply voltage.
lower DC link voltage threshold (r1246, r1286) - check the infeed module
was reached in the "Operation" state. - adapt the device supply voltage (p0210) or the switch-on level (p1245, p1285).
- disable the DC link voltage monitoring (p1240, p1280 = 0).

Sinamics G130 F07404 Drive: Upper DC link voltage threshold reached The DC link voltage monitoring is active (p1240 , p1280 = 4, 6) and the - check the line supply voltage.
upper DC link voltage threshold (r1242, - check the infeed module
r1282) was reached in the "Operation" state. - adapt the device supply voltage (p0210).
- disable the DC link voltage monitoring (p1240, p1280 = 0).

Sinamics G130 F07405 (N,A) Drive: Kinetic buffering minimum speed not During kinetic buffering the speed fell below minimum speed (p1257 or Check the speed threshold for the Vdc_min controller (kinetic buffering) (p1257,
reached p1297 for vector drives with V/f control) and p1297).
the line supply did not return. See also: p1257 (Vdc_min controller speed threshold)

Sinamics G130 F07406 (N,A) Drive: Kinetic buffering maximum time The maximum buffer time (p1255 and p1295 for vector drives with V/f Check the time threshold for Vdc-min controller (kinetic buffering) (p1255,
exceeded control) has been exceeded without the line p1295).
supply having returned. See also: p1255 (Vdc_min controller time threshold)
Sinamics G130 F07410 Drive: Current controller output limited The condition "I_act = 0 and Uq_set_1 longer than 16 ms at its limit" is - connect the motor or check the motor contactor.
present and can be caused by the following: - check the DC link voltage (r0070).
- motor not connected or motor contactor open. - check the Motor Module.
- no DC link voltage present. - activate the "flying restart" function (p1200).
- Motor Module defective.
- the "flying restart" function is not activated.

Sinamics G130 F07411 Drive: Flux setpoint not reached when building When quick magnetizing is configured (p1401 Bit6 = 1) the specified flux - correct the motor data.
up excitation setpoint is not reached although 90 % of - check the motor configuration.
the maximum current is specified. - correct the current limits (p0640).
- incorrect motor data. - reduce the induction motor load.
- motor data and motor configuration (star/delta) do not match. - if required, use a larger Motor Module.
- the current limit has been set too low for the motor. - check motor supply cable.
- induction motor (encoderless, open-loop controlled) in I2t limiting. - check power unit.
- the Motor Module is too small.

Sinamics G130 F07412 Drive: Commutation angle incorrect (motor An incorrect commutation angle was detected, that can result in a positive - if the encoder mounting was changed - re-adjust the encoder.
model) coupling in the speed controller. - replace the defective motor encoder.
Possible causes: - correctly set the angular commutation offset (p0431).
- the motor encoder is incorrectly adjusted with respect to the magnet - correctly set the motor stator resistance, cable resistance and motor-stator
position. leakage inductance (p0350, p0352,
- the motor encoder is damaged. p0356).
- the angular commutation offset is incorrectly set (p0431). - increase the changeover speed for the motor model (p1752). The monitoring is
- data to calculate the motor model has been incorrectly set (p0356 completely de-activated for p1752
(motor-stator leakage inductance) and/or p0350 > p1082 (maximum speed)
(motor-stator resistance) and/or p0352 (cable resistance). Note:
- the changeover speed for the motor model is too low (p1752). The For High Dynamic Motors (1FK7xxx-7xxx), for applications with a higher current,
monitoring function only becomes effective if necessary, the monitoring should
above the changeover speed. be disabled.
- the motor encoder speed signal is faulted.
- the control loop is instable due to incorrect parameterization.
Fault value (r0949, interpret decimal):
SERVO:
0: The comparison of the pole position angle from the encoder and the
motor model resulted in an excessively high
value (> 80 ° electrical).
1: -
VECTOR:
0: The comparison of the pole position angle from the encoder and the
motor model resulted in an excessively high
value (> 45 ° electrical).
1: The change in the speed signal from the motor encoder has changed by
> p0492 within a current controller clock
cycle.

Sinamics G130 F07413 Drive: Commutation angle incorrect (pole An incorrect commutation angle was detected, that can result in a positive - correctly set the angular commutation offset (p0431).
position identification) coupling in the speed controller. - re-adjust the motor encoder after the encoder has been replaced.
- within the pole position identification routine (p1982 = 2): - replace the defective motor encoder.
A difference of > 45° electrical to the encoder angle was determined. - check the pole position identification routine. If the pole position identification
- for VECTOR, within the encoder adjustment (p1990 = 2): routine is not suitable for this motor
A difference of > 6 ° electrical to the encoder angle was determined. type, then disable the plausibility check (p1982 = 0).

Sinamics G130 F07422 Drive: Reference model natural frequency > The natural filter frequency of the PT2 element for the reference model - reduce the natural frequency of PT2 element for reference model (p1433).
Shannon frequency (p1433) is greater than the Shannon frequency. - reduce the speed controller sampling time (p0115[1]).
The Shannon frequency is calculated according to the following formula:
0.5 / p0115[1]

Sinamics G130 F07434 Drive: It is not possible to change the direction A drive data set was selected - with the pulses enabled - which has a - change over the drive data set with the pulses inhibited.
of rotation with the pulses enabled different parameterized direction of rotation - ensure that the changeover to a drive data set does not result in the motor
(p1821). direction of rotation being changed (i.e.
It is only possible to change the motor direction of rotation using p1821 for these drive data sets, the same value must be in p1821).
when the pulses are inhibited. See also: p1821 (Dir of rot)
Sinamics G130 F07435 (N) Drive: Setting the ramp-function generator for During operation with sensorless vector control (r1407.1) the ramp- - de-activate the holding command for the ramp-function generator (p1141).
sensorless vector control function generator was stopped (p1141) or - do not bypass the ramp-function generator (p1122).
bypassed (p1122). An internal setting command of the ramp-function - suppress the fault (p2101, p2119). This is necessary if the ramp-function
generator output caused the set setpoint speed generator is held using jogging and the
to be frozen or was not able to be realized. speed setpoint is simultaneously inhibited (r0898.6).
Note:
For sensorless vector control it is not practical to read-in the main setpoint of
the speed control via p1155 or p1160
(p0922). In this case, the main setpoint should be injected before the ramp-
function generator (p1070). The reason
for this is that the ramp-function generator output is automatically set when
transitioning from closed-loop speed controlled
into open-loop speed controlled operation.

Sinamics G130 F07422 LR: Multiturn does not match the modulo The ratio between the multiturn resolution and the modular range (p2576) Make the ration between the multiturn resolution and the modulo range an
range is not an integer number. integer number.
This results in the adjustment being set back, as the position actual value The ratio v is calculated as follows:
cannot be reproduced after poweroff/ 1. Motor encoder without position tracking:
power-on. v = (p0421 * p2506 * p0433 * p2505) / (p0432 * p2504 * p2576)
2. Motor encoder with position tracking for the measuring gear:
v = (p0412 * p2506 * p2505) / (p2504 * p2576)
3. Motor encoder with position tracking for the load gear:
v = (p2721 * p2506 * p0433) / (p0432 * p2576)
4. Motor encoder with position tracking for the load and measuring gear:
v = (p2721 * p2506) / p2576
5. Direct encoder without position tracking:
v = (p0421 * p2506 * p0433) / (p0432 * p2576)
6. Direct encoder with position tracking for the measuring gear:
v = (p0412 * p2506) / p2576
Note:
With position tracking, it is recommended that p0412 and p2721 are changed
See also: p0412 (Measuring gear, rotary absolute gearbox, revolutions, virtual),
p0432 (Gearbox factor, encoder revolutions),
p0433 (Gearbox factor, motor/load revolutions), p2721 (Load gear, rotary
absolute gearbox, revolutions,
virtual)

Sinamics G130 F07443 (A) LR: Reference point coordinate not in the The reference point coordinate received when adjusting the encoder via Set the reference point coordinate to a lower value than specified in the fault
permissible range connector input p2599 lies outside the half value.
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.

Sinamics G130 F07466 (A) Load gear: Position tracking cannot be reset The position tracking cannot be reset. Reset the position tracking as follows:
- select encoder commissioning (p0010 = 4).
- reset position tracking, position (p2720.2 = 1).
- de-select encoder commissioning (p0010 = 0).
The fault should then be acknowledged and, if necessary, the absolute encoder
adjusted (p2507).

Sinamics G130 F07447 Load gear: Position tracking, maximum actual When the position tracking of the load gear is configured, the - reduce the fine resolution (p0419).
value exceeded drive/encoder (motor encoder) identifies a maximum - reduce the multiturn resolution (p2721).
possible absolute position actual value (r2723) that can no longer be See also: p0419 (Fine resolution absolute value Gx_XIST2 (in bits)), p2721 (Load
represented within 32 bits. gear, rotary absolute gearbox,
Maximum value: p0408 * p2721 * 2^p0419 revolutions, virtual)
Fault value (r0949, interpret hexadecimal):
ccbbaa hex
aa = encoder data set
bb = component number
cc = drive data set
See also: p0408 (Rotary encoder pulse No.), p0419 (Fine resolution
absolute value Gx_XIST2 (in bits)), p2721 (Load
gear, rotary absolute gearbox, revolutions, virtual)
Sinamics G130 F07488 (A) Load gear: Position tracking, linear axis has For a configured linear axis/no modulo axis, the currently effective motor The fault should be resolved as follows:
exceeded the maximum range encoder (encoder 1) has exceeded the - select encoder commissioning (p0010 = 4).
maximum possible traversing range. - reset position tracking, position (p2720.2 = 1).
For the configured linear axis, the maximum traversing range is defined to - de-select encoder commissioning (p0010 = 0).
be 64x (+/- 32x) of p0421. It should be The fault should then be acknowledged and the absolute encoder adjusted.
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].

Sinamics G130 F07449 (A) Load gear: Position tracking, current position When powered down, the currently effective motor encoder was moved Reset the position tracking as follows:
outside tolerance window through a distance greater than was parameterized - select encoder commissioning (p0010 = 4).
in the tolerance window. It is possible that there is no longer any reference - reset position tracking, position (p2720.2 = 1).
between the mechanical system - de-select encoder commissioning (p0010 = 0).
and encoder. The fault should then be acknowledged and, if necessary, the absolute encoder
Note: adjusted (p2507).
Here, only the motor encoder in the currently effective drive data set is See also: p0010
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)

Sinamics G130 F07450 (A) LR: Standstill monitoring has responded After the standstill monitoring time (p2543) expired, the drive left the Check the causes and resolve.
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).

Sinamics G130 F07451 LR: Position monitoring has responded When the position monitoring time (p2545) expired, the drive had still not Check the causes and resolve.
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.

Sinamics G130 F07452 (A) LR: Following error too high The difference between the position setpoint position actual value Check the causes and resolve.
(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

Sinamics G130 F07453 LR: Position actual value preprocessing error An error has occurred during the position actual value preprocessing. Check the encoder for the position actual value preprocessing.

Sinamics G130 F07458 EPOS: Reference cam not found After starting the search for reference, the axis moved through the - check the "reference cam" binector input (BI: p2612).
maximum permissible distance to search for the - check the maximum permissible distance to the reference cam (p2606).
reference cam without actually finding the reference cam. - if axis does not have any reference cam, then set p2607 to 0.

Sinamics G130 F07459 EPOS: No zero mark After leaving the reference cam, the axis has traversed the maximum - check the encoder regarding the zero mark
permissible distance between the reference - check the maximum permissible distance between the reference cam and zero
cam and zero mark without finding the zero mark. mark (p2609).
- use an external encoder zero mark (equivalent zero mark) (p0495).
See also: p0495 (Equivalent zero mark, input terminal)
Sinamics G130 F07460 EPOS: End of reference cam not found During the search for reference, when the axis reached the zero mark it - check the "reference cam" binector input (BI: p2612).
also reached the end of the traversing range - repeat the search for reference.
without detecting an edge at the binector input "reference cam" (BI:
p2612).
Maximum traversing range: -2147483648 [LU] ... -2147483647 [LU]

Sinamics G130 F07464 EPOS: Traversing block is inconsistent The traversing block does not contain valid information. Check the traversing block and where relevant, take into consideration alarms
Alarm value (r2124, interpret decimal): that are present.
Number of the traversing block with invalid information.

Sinamics G130 F07475 (A) EPOS: Target position < start of traversing The target position for relative traversing lies outside the traversing range. Correct the target position.
range
Sinamics G130 F07476 (A) EPOS: Target position > end of the traversing The target position for relative traversing lies outside the traversing range. Correct the target position.
range
Sinamics G130 F07481 EPOS: Axis position < software limit switch The current position of the axis is less than the position of the software correct the target position.
minus limit switch minus. change software limit switch minus (CI: p2578, p2580).
Sinamics G130 F07482 (A) EPOS: Axis position > software limit switch plus The current position of the axis is greater than the position of the software - correct the target position.
limit switch plus. - change software limit switch plus (CI: p2579, p2581).
Sinamics G130 F07484 EPOS: Fixed stop outside the monitoring In the "fixed stop reached" state, the axis has moved outside the defined - check the monitoring window (p2635).
window monitoring window (p2635). - check the mechanical system.
Sinamics G130 F07485 (A) EPOS: Fixed stop not reached In a traversing block with the task FIXED STOP, the end position was - check the traversing block and locate the target position further into the
reached without detecting a fixed stop. workpiece.
- check the "fixed stop reached" control signal (p2637).
- if required, reduce the maximum following error window to detect the fixed
stop (p2634).

Sinamics G130 F07488 EPOS: Relative positioning not possible In the mode "direct setpoint input/MDI", for continuous transfer (p2649 = Check the control.
1) relative positioning was selected (BI:
p2648 = 0 signal).

Sinamics G130 F07490 EPOS: Enable signal withdrawn while traversing for a standard assignment, another fault may have occurred as a result of set the enable signals or check the cause of the fault that first occurred and then
withdrawing the enable signals. result (for a standard assignment).
the drive is in the "switching on inhibited" state (for a standard check the assignment to enable the basic positioning function.
assignment).

Sinamics G130 F07491 (A) EPOS: STOP cam minus reached A zero signal was detected at binector input BI: p2569, i.e. the STOP cam - leave the STOP cam minus in the positive traversing direction and return the
minus was reached. axis to the valid traversing range.
For a positive traversing direction, the STOP cam minus was reached - i.e. - check the wiring of the STOP cam.
the wiring of the STOP cam is incorrect.

Sinamics G130 F07492 EPOS: STOP cam plus reached A zero signal was detected at binector input BI: p2570, i.e. the STOP cam - leave the STOP cam plus in the negative traversing direction and return the axis
plus was reached. to the valid traversing range.
For a negative traversing direction, the STOP cam plus was reached - i.e. - check the wiring of the STOP cam.
the wiring of the STOP cam is incorrect.

Sinamics G130 F07493 LR: Overflow of the value range for position The value range (-2147483648 ... 2147483647) for the position actual value If required, reduce the traversing range or position resolution (p2506).
actual value representation was exceeded. Increase the fine resolution of absolute position actual value (p0419).
When the overflow occurs, the "referenced" or "adjustment absolute Reference to fault value = 3:
measuring system" status is reset. If the value for the maximum possible absolute position (LU) is greater than
Fault value (r0949, interpret decimal): 4294967296, an adjustment cannot be
1: The position actual value (r2521) has exceeded the value range. made due to an overflow.
2: The encoder position actual value Gn_XIST2 (r0483) or the absolute For rotary encoders, the maximum possible absolute position (LU) is calculated
value after the load gear (r2723) has as follows:
exceeded the value range. 1. Motor encoder without position tracking:
3: The maximum encoder value times the factor to convert the absolute p2506 * p0433 * p2505 / (p0432 * p2504)
position (r0483 and/or r2723) from increments p2506 * p0433 * p2505 * p0421 / (p0432 * p2504) for multiturn encoders
to length units (LU) has exceeded the value range for displaying the 2. Motor encoder with position tracking for measuring gear
position actual value. p2506 * p0412 * p2505 / p2504
3. Motor encoder with position tracking for load gear:
p2506 * p2721 * p0433 / p0432
4. Motor encoder with position tracking for load and measuring gear:
p2506 * p2721
5. Direct encoder without position tracking:
p2506 * p0433 / p0432
p2506 * p0433 * p0421 / p0432 for multiturn encoders
6. Direct encoder with position tracking for measuring gear:
p2506 * p0412

Sinamics G130 F07494 LR: Drive Data Set changeover in operation A drive data set changeover (DDS changeover) when the mechanical To changeover the drive data set, initially, exit the "operation" mode.
relationships change (p2503 .. 2506), the
direction of rotation (p1821) or the encoder assignment (p2502) were
requested during operation.
Sinamics G130 F07502 Drive: Encoder Data Set EDS not configured Only for power units: The index of the encoder data set associated with the drive data set should be
The encoder data set was not configured - this means that a data set entered into p0187 (1st encoder),
number was not entered into the associated p0188 (2nd encoder) and p0189 (3rd encoder).
drive data set.
Fault value (r0949, interpret decimal):
The fault value includes the drive data set number of p0187, p0188 and
p0189.
The fault value is increased by 100 * encoder number (e.g. for p0189: Fault
value 3xx with xx = data set number).

Sinamics G130 F07509 Drive: Component number missing A Drive Data Set (DDS) is assigned to a Motor Data Set (MDS) or Encoder In the drive data sets, no longer assign MDS/EDS using p0186, p0187, p0188,
Data Set (EDS) that does not have a p0189 or set a valid component number.
component number. See also: p0131, p0141, p0142, p0186, p0187, p0188, p0189
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

Sinamics G130 F07510 Drive: Identical encoder in the drive data set More than one encoder with identical component number is assigned to a Assign the drive data set to different encoders.
single drive data set. In one drive data set, See also: p0141 (Encoder interface (Sensor Module) component number), p0187
it is not permissible that identical encoders are operated together. (Encoder 1 encoder data set number),
Fault value (r0949, interpret decimal): p0188 (Encoder 2 encoder data set number), p0189 (Encoder 3 encoder data set
1000 * first identical encoder + 100 * second identical encoder + drive data number)
set.
Example:
Fault value = 1203 means:
In drive data set 3, the first (p0187[3]) and second encoder (p0188[3]) are
identical.

Sinamics G130 F07511 Drive: Encoder used a multiple number of Each encoder may only be assigned to one drive and within a drive must - Correct the double use of a component number using the two parameters coded
times in each drive data set - either always be in the fault value.
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)

Sinamics G130 F07512 Drive: Encoder data set changeover cannot be Using p0141, a changeover of the encoder data set is prepared that is Every encoder data set must be assigned its own dedicated DRIVE-CLiQ socket.
parameterized illegal. In this firmware release, an encoder The component numbers of the
data set changeover is only permitted for the components in the actual encoder interfaces (p0141) must have different values within a drive object.
topology. The following must apply:
Alarm value (r2124, interpret decimal): p0141[0] not equal to p0141[1] not equal to ... not equal to p0141[n]
Incorrect EDS data set number.
See also: p0187 (Encoder 1 encoder data set number), p0188 (Encoder 2
encoder data set number), p0189
(Encoder 3 encoder data set number)

Sinamics G130 F07515 Drive: Power unit and motor incorrectly A power unit (via PDS) was assigned to a motor (via MDS) in a drive data - assign the drive data set to a combination of motor and power unit permitted
connected set that is not connected in the target by the target topology.
topology. - adapt the target topology.
Alarm value (r2124, interpret decimal): See also: p0121 (Power unit component number), p0131 (Motor component
Number of the incorrectly parameterized drive data set. number), p0186 (Motor Data Sets
(MDS) number)
Sinamics G130 F07516 Drive: Re-commission the data set The assignment between the drive data set and motor data set (p0186) or Commission the drive data set specified in the fault value (r0949).
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.

Sinamics G130 F07517 Drive: Encoder data set changeover incorrectly An MDS cannot have different motor encoders in two different DDS. If you wish to operate a motor once with one motor encoder and then another
parameterized The following parameterization therefore results results in an error: time with the other motor encoder,
p0186[0] = 0, p0187[0] = 0 then you must set up two different MDSs, in which the motor data are the same.
p0186[0] = 0, p0187[0] = 1 Example:
Alarm value (r2124, interpret decimal): p0186[0] = 0, p0187[0] = 0
The lower 16 bits indicate the first DDS and the upper 16 bits indicate the p0186[0] = 1, p0187[0] = 1
second DDS.

Sinamics G130 F07518 Drive: Motor data set changeover incorrectly The system has identified that two motor data sets were incorrectly Correct the parameterization of the motor data sets.
parameterized 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

Sinamics G130 F07551 Drive encoder: No commutation angle The commutation angle information is missing. This means that Re fault cause = 1:
information synchronous motors cannot be controlled (closedloop - check the encoder parameterization (p0404).
control) - use an encoder with track C/D, EnDat interface of Hall sensors.
Fault value (r0949, interpret decimal): - use an encoder with sine-wave A/B track for which the motor pole pair number
yyyyxxxx dec: yyyy = fault cause, xxxx = drive data set (r0313) is an integer multiple of the
yyyy = 1 dec: encoder pulse number (p0408).
The motor encoder used does not supply an absolute commutation angle. - activate the pole position identification routine (p1982 = 1).
yyyy = 2 dec: Re fault cause = 2:
The selected ratio of the measuring gear does not match the motor pole - the quotient of the pole pair number divided by the ratio of the measuring gear
pair number. must be an integer number: (p0314
* p0433) / p0432.
Note:
For operation with track C/D, this quotient must be less than 8.
See also: p0402 (Gearbox type selection), p0404 (Encoder configuration
effective), p0432 (Gearbox factor, encoder
revolutions), p0433 (Gearbox factor, motor/load revolutions)

Sinamics G130 F07552 (A) Drive encoder: Encoder configuration not The requested encoder configuration is not supported. Only bits may be - check the encoder parameterization (p0400, p0404).
supported requested in p0404 that are signaled as - use the matching encoder evaluation (r0456).
being supported by the encoder evaluation in r0456.
Fault value (r0949, interpret decimal):
Low word low byte: Encoder data set number
Low word high byte: Component number
High word:
The encoder evaluation does not support a function selected in p0404.
1: sin/cos encoder with absolute track (this is supported by SME25).
3: Squarewave encoder (this is supported by SMC30).
4: sin/cos encoder (this is supported by SMC20, SMI20, SME20, SME25).
12: sin/cos encoder with reference mark (this is supported by SME20).
15: Commutation with zero mark for separately-excited synchronous
motors with VECTORMV.
23: Resolver (this is supported by SMC10, SMI10).
65535: Other function (compare r0456 and p0404).
See also: p0404 (Encoder configuration effective), r0456 (Encoder
configuration supported)
Sinamics G130 F07553 (A) Drive encoder: Sensor Module configuration The Sensor Module does not support the requested configuration. - check the encoder parameterization (p0430, p0437).
not supported If p0430 (cc = 0) incorrect, the following applies: - check the pole position identification routine (p1982).
- In p0430 (requested functions), at least 1 bit was set that is not set in - use the matching encoder evaluation (r0458, r0459).
r0458 (supported functions) (exception: bits See also: p0430 (Sensor Module configuration), p0437 (Sensor Module
19, 28, 29, 30, 31). configuration extended), r0458 (Sensor
- p1982 > 0 (pole position identification requested), but r0458.16 = 0 (pole Module properties), r0459 (Sensor Module properties extended), p1982 (Pole
position identification not supported). position identification selection)
If p0437 (cc = 1) incorrect, the following applies:
- In p0437 (requested functions), at least 1 bit was set that is not set in
r0459 (supported functions).
Fault value (r0949, interpret hexadecimal):
ddccbbaa hex
aa: encoder data set no.
bb: first incorrect bit
cc: incorrect parameter
cc = 0: incorrect parameter is p0430
cc = 1: incorrect parameter is p0437
dd: reserved (always 0)

Sinamics G130 F07555 (A) Drive encoder: Configuration position tracking The configuration of the position tracking is not supported. - use an absolute encoder.
Position tracking can only be activated for absolute encoders. - if necessary, de-select the position tracking (p0411 for the measuring gear,
For linear axes, it is not possible to simultaneously activate the position p2720 for the load gear).
tracking for load- and measuring gear. - use a Control Unit with sufficient NVRAM.
Fault value (r0949, interpret hexadecimal): - Only activate position tracking of the load gear in the same encoder data set if
ddccbbaa hex the gear ratio (p2504, p2505), axis
aa = encoder data set type (p2720.1) and tolerance window (p2722) are also the same.
bb = component number
cc = drive data set
dd = fault cause
dd = 00 hex = 0 dez
An absolute encoder is not being used.
dd = 01 hex = 1 dez
Position tracking cannot be activated because the memory of the internal
NVRAM is not sufficient or a Control Unit
does not have an NVRAM.
dd = 02 hex = 2 dez
For a linear axis, the position tracking was activated for the load and
measuring gear.
dd = 03 hex = 3 dez
Position tracking cannot be activated because position tracking with
another gear ratio, axis type or tolerance window
has already been detected for this encoder data set.
dd = 04 hex = 4 dez
A linear encoder is being used.
See also: p0404 (Encoder configuration effective), p0411 (Measuring gear,
configuration)

Sinamics G130 F07556 Measuring gear: Position tracking, maximum When the position tracking of the measuring gear is configured, the - reduce the fine resolution (p0419).
actual value exceeded drive/encoder identifies a maximum possible - reduce the multiturn resolution (p0412).
absolute position actual value (r0483) that cannot be represented within See also: p0412 (Measuring gear, rotary absolute gearbox, revolutions, virtual),
32 bits. p0419 (Fine resolution absolute
Maximum value: p0408 * p0412 * 2^p0419 value Gx_XIST2 (in bits))
Fault value (r0949, interpret decimal):
Low word low byte: Encoder data set number
Low word high byte: Component number
See also: p0408 (Rotary encoder pulse No.), p0412 (Measuring gear, rotary
absolute gearbox, revolutions, virtual),
p0419 (Fine resolution absolute value Gx_XIST2 (in bits))

Sinamics G130 F07560 Drive encoder: Number of pulses is not to the For rotary absolute encoders, the pulse number in p0408 must be to the - check the parameterization (p0408, p0404.1, r0458.5).
power of two power of two. - if required, upgrade the Sensor Module firmware.
Fault value (r0949, interpret decimal):
The fault value includes the encoder data set number involved.

Sinamics G130 F07561 Drive encoder: Number of multiturn pulses is The multiturn resolution in p0421 must be to the power of two. check the parameterization (p0421, p0404.1, r0458.5).
not to the power of two Fault value (r0949, interpret decimal): if required, upgrade the Sensor Module firmware.
The fault value includes the encoder data set number involved.
Sinamics G130 F07562 (A) Drive, encoder: Position tracking, incremental The requested position tracking for incremental encoders is not supported. check the encoder parameterization (p0400, p0404).
encoder not possible Fault value (r0949, interpret hexadecimal): use a Control Unit with sufficient NVRAM.
ccccbbaa hex if required, deselect position tracking for the incremental encoder (p0411.3 = 0).
aa = encoder Data Set number
bb = component number
cccc = fault cause
cccc = 00 hex = 0 dec
The encoder type does not support the "Position tracking incremental
encoder" function.
cccc = 01 hex = 1 dec
Position tracking cannot be activated because the memory of the internal
NVRAM is not sufficient or a Control Unit
does not have an NVRAM.
cccc = 04 hex = 4 dec
A linear encoder is used that does not support the position tracking
function.
See also: p0404 (Encoder configuration effective), p0411 (Measuring gear,
configuration), r0456 (Encoder configuration
supported)

Sinamics G130 F07575 Drive: Motor encoder not ready The motor encoder signals that it is not ready. Evaluate other queued faults via encoder 1.
- initialization of encoder 1 (motor encoder) was unsuccessful.
- the function "parking encoder" is active (encoder control word
G1_STW.14 = 1).
- the encoder interface (Sensor Module) is de-activated (p0145).
- the Sensor Module is defective.

Sinamics G130 F07599 Encoder 1: Adjustment not possible The maximum encoder value times the factor to convert the absolute If the value for the maximum possible absolute position (LU) is greater than
position (r0483 and/or r2723) from increments 4294967296, an adjustment cannot be
to length units (LU) has exceeed the value range (-2147483648 ... made due to an overflow.
2147483647) for displaying the position actual For rotary encoders, the maximum possible absolute position (LU) is calculated
value. as follows:
1. Motor encoder without position tracking:
p2506 * p0433 * p2505 / (p0432 * p2504)
p2506 * p0433 * p2505 * p0421 / (p0432 * p2504) for multiturn encoders
2. Motor encoder with position tracking for measuring gear
p2506 * p0412 * p2505 / p2504
3. Motor encoder with position tracking for load gear:
p2506 * p2721 * p0433 / p0432
4. Motor encoder with position tracking for load and measuring gear:
p2506 * p2721
5. Direct encoder without position tracking:
p2506 * p0433 / p0432
p2506 * p0433 * p0421 / p0432 for multiturn encoders
6. Direct encoder with position tracking for measuring gear:
p2506 * p0412

Sinamics G130 F07600 (A) Encoder 2: Adjustment not possible The maximum encoder value times the factor to convert the absolute If the value for the maximum possible absolute position (LU) is greater than
position (r0483 and/or r2723) from increments 4294967296, an adjustment cannot be
to length units (LU) has exceeed the value range (-2147483648 ... made due to an overflow.
2147483647) for displaying the position actual For rotary encoders, the maximum possible absolute position (LU) is calculated
value. as follows:
1. Motor encoder without position tracking:
p2506 * p0433 * p2505 / (p0432 * p2504)
p2506 * p0433 * p2505 * p0421 / (p0432 * p2504) for multiturn encoders
2. Motor encoder with position tracking for measuring gear
p2506 * p0412 * p2505 / p2504
3. Motor encoder with position tracking for load gear:
p2506 * p2721 * p0433 / p0432
4. Motor encoder with position tracking for load and measuring gear:
p2506 * p2721
5. Direct encoder without position tracking:
p2506 * p0433 / p0432
p2506 * p0433 * p0421 / p0432 for multiturn encoders
6. Direct encoder with position tracking for measuring gear:
p2506 * p0412
Sinamics G130 F07601 Encoder 3: Adjustment not possible The maximum encoder value times the factor to convert the absolute If the value for the maximum possible absolute position (LU) is greater than
position (r0483 and/or r2723) from increments 4294967296, an adjustment cannot be
to length units (LU) has exceeed the value range (-2147483648 ... made due to an overflow.
2147483647) for displaying the position actual For rotary encoders, the maximum possible absolute position (LU) is calculated
value. as follows:
1. Motor encoder without position tracking:
p2506 * p0433 * p2505 / (p0432 * p2504)
p2506 * p0433 * p2505 * p0421 / (p0432 * p2504) for multiturn encoders
2. Motor encoder with position tracking for measuring gear
p2506 * p0412 * p2505 / p2504
3. Motor encoder with position tracking for load gear:
p2506 * p2721 * p0433 / p0432
4. Motor encoder with position tracking for load and measuring gear:
p2506 * p2721
5. Direct encoder without position tracking:
p2506 * p0433 / p0432
p2506 * p0433 * p0421 / p0432 for multiturn encoders
6. Direct encoder with position tracking for measuring gear:
p2506 * p0412

Sinamics G130 F07800 Drive: No power unit present The power unit parameters cannot be read or no parameters are stored in - connect the data line to power unit and restart the Control Unit (POWER ON).
the power unit. - check or replace the Control Unit.
Connection between the Control Unit and the Motor Module was - check the cable between the Control Unit and Motor Module.
interrupted or is defective. - after correcting the topology, the parameters must be again downloaded using
This fault also occurs if an incorrect topology was selected in the the commissioning software.
commissioning software and this parameterization
is then downloaded to the Control Unit.
See also: r0200 (Power unit current code number)

Sinamics G130 F07801 Drive: Motor overcurrent The permissible motor limit current was exceeded. - check the current limits (p0640).
- effective current limit set too low. - vector control: Check the current controller (p1715, p1717).
- current controller not correctly set. - V/f control: Check the current limiting controller (p1340 ... p1346).
- motor was braked with an excessively high stall torque correction factor. - increase the up ramp (p1120) or reduce the load.
- V/f operation: Up ramp was set too short or the load is too high. - check the motor and motor cables for short-circuit and ground fault.
- V/f operation: Short-circuit in the motor cable or ground fault. - check the Motor Module and motor combination.
- V/f operation: Motor current does not match the current of Motor
Module.
Note:
Limit current = 2 * Minimum( p0640, 4 * p0305) >= 2 * p0305

Sinamics G130 F07802 Drive: Infeed or power unit not ready After an internal power-on command, the infeed or drive does not signal - increase the monitoring time (p0857).
ready. - ensure that there is a DC link voltage. Check the DC link busbar. Enable the
- monitoring time is too short. infeed.
- DC link voltage is not present. - replace the associated infeed or drive of the signaling component.
- associated infeed or drive of the signaling component is defective. - check the line supply voltage setting (p0210).
- supply voltage incorrectly set. See also: p0857 (Power unit monitoring time)

Sinamics G130 F07810 Drive: Power unit EEPROM without rated data No rated data are stored in the power unit EEPROM. Replace the power unit or inform Siemens Customer Service.
See also: p0205 (Power unit application), r0206 (Rated power unit power),
r0207 (Rated power unit current), r0208
(Rated power unit line supply voltage), r0209 (Power unit, maximum
current)
Sinamics G130 F07815 Drive: Power unit has been changed The code number of the current power unit does not match the saved Connect the original power unit and power up the Control Unit again (POWER
number. The fault only occurs if the comparator ON) or set p0201 to r0200 and exit
in p9906 or p9908 is not at f 2 (low) or 3 (minimum). commissioning with p0010 = 0.
Fault value (r0949, interpret decimal): For infeeds, the following applies:
Number of the incorrect parameter. Commutating reactors or line filters must be used that are specified for the new
See also: r0200 (Power unit current code number), p0201 (Power unit code power unit. A line supply and DC link
number) identification routine (p3410 = 5) must then be carried out. It is not possible to
change the power unit without re-commissioning
the system if the type of infeed (A_Infeed, B_Infeed, S_Infeed), the type of
construction/design (booksize,
chassis) or the voltage class differ between the old and new power units.
For inverters, the following applies:
If the new power unit is accepted, then if required, the current limit p0640 can
be reduced by a lower maximum current
of the power unit (r0209) (torque limits stay the same).
If not only the power unit is changed, but also the motor, then the motor must
be re-commissioning (e.g. using p0010
= 1). This is also necessary if motor data is still to be downloaded via DRIVE-CLiQ.
If the comparison stage in p9906 is set to 2, 3, then commissioning can be exited
(p0010 = 0) and the fault acknowledged.
See also: r0200 (Power unit current code number)

Sinamics G130 F07862 Drive: Simulation mode with DC link voltage The simulation mode is activated and the DC link voltage is greater than the - switch out (disable) simulation mode (p1272 = 0) and acknowledge the fault.
too high permissible value of 40 V. - reduce the input voltage in order to reach a DC link voltage below 40 V.

Sinamics G130 F07840 Drive: Infeed operation missing The signal "infeed operation" is not present although the enable signals for - bring the infeed into an operational state.
the drive have been present for longer - check the interconnection of the binector input for the signal "infeed
than the parameterized monitoring time (p0857). operation" (p0864).
- infeed not operational. - increase the monitoring time (p0857).
- interconnection of the binector input for the ready signal is either - wait until the infeed has completed the line supply identification routine.
incorrect or missing (p0864). See also: p0857 (Power unit monitoring time), p0864 (Infeed operation)
- infeed is presently carrying out a line supply identification routine.

Sinamics G130 F07841 Drive: Infeed operation withdrawn The signal "infeed operation" was withdrawn in operation. - check the interconnection of the binector input for the signal "infeed
- interconnection of the binector input for the signal "infeed operation" is operation" (p0864).
either incorrect or missing (p0864). - check the enable signals of the infeed and if required, enable.
- the enable signals of the infeed were disabled. - remove and acknowledge an infeed fault.
- due to a fault, the infeed withdraws the signal "infeed operation". Note:
If this drive is intended to back-up the DC link regeneratively, then the fault
response must be parameterized for
NONE, OFF1 or OFF3 so that the drive can continue to operate even after the
infeed fails.

Sinamics G130 F07860 (A) External fault 1 The BICO signal "external fault 1" was triggered. Eliminate the causes of this fault.
See also: p2106 (External fault 1)
Sinamics G130 F07861 (A) External fault 2 The BICO signal "external fault 2" was triggered. Eliminate the causes of this fault.
See also: p2107 (External fault 2)
Sinamics G130 F07862 (A) External fault 3 The BICO signal "external fault 3" was triggered. 'Eliminate the causes of this fault.
See also: p2108, p3111, p3112
Sinamics G130 F07890 Internal voltage protection/internal armature The internal armature short-circuit (p1231 = 4) is not possible as Safe Switch out the internal armature short-circuit (p1231=0) or de-activate Safe
short-circuit with Safe Torque Off active Torque Off (STO) is enabled. The pulses cannot Torque Off (p9501 = p9561 = 0).
be enabled. Note:
STO: Safe Torque Off / SH: Safe standstill
Sinamics G130 F07900 (N,A) Drive: Motor locked/speed controller at its Motor has been operating at the torque limit longer than the time specified - check that the motor can freely rotate.
limit in p2177 and below the speed threshold - check the torque limit: For a positive direction of rotation r1538, for a negative
set in p2175. direction of rotation r1539.
This signal can also be initiated if the speed actual value is oscillating and - check the parameter, message "Motor locked" and if required, correct (p2175,
the speed controller output repeatedly p2177).
goes to its limit. - check the inversion of the actual value (p0410).
If the simulation mode is enabled (p1272 = 1) and the closed-loop control - check the motor encoder connection.
with speed encoder activated (p1300 = - check the encoder pulse number (p0408).
21), then the inhibit signal is generated if the encoder signal is not received - for SERVO with encoderless operation and motors with low power ratings (<
from a motor that is driven with the torque 300 W), increase the pulse frequency
setpoint of the closed-loop control. (p1800).
See also: p2175 (Motor locked speed threshold), p2177 (Motor locked - after de-selecting basic positioning, check the torque limits when motoring
delay time) (p1528) and when regenerating (p1529).
- in the simulation mode and operation with speed encoder, the power unit to
which the motor is connected must be
powered up and must be supplied with the torque setpoint of the simulated
closed-loop control. Otherwise, change
over to encoderless control (refer to p1300).

Sinamics G130 F07901 Drive: Motor overspeed The maximum permissible speed was either positively or negatively The following applies for a positive direction of rotation:
exceeded. - check r1084 and if required, correct p1082, CI:p1085 and p2162.
The maximum permissible positive speed is formed as follows: Minimum The following applies for a negative direction of rotation:
(p1082, CI: p1085) + p2162 - check r1087 and if required, correct p1082, CI:p1088 and p2162.
The maximum permissible negative speed is formed as follows: Maximum
(-p1082, CI: 1088) - p2162

Sinamics G130 F07902 (N,A) Drive: Motor stalled For a vector drive the system has identified that the motor has stall for a It should always be carefully ensured that the motor data identification (p1910)
time longer than is set in p2178. as well as the rotating measurement
Fault value (r0949, interpret decimal): (p1960) were carried out (also refer to p3925). For synchronous motors with
1: Stall detection using r1408.11 (p1744 or p0492). encoder, the encoder must have been
2: Stall detection using r1408.12 (p1745). adjusted (p1990).
3: Stall detection using r0056.11 (only for separately excited synchronous For closed-loop speed and torque control with speed encoder, the following
motors). applies:
See also: p1744 (Motor model speed threshold stall detection), p2178 - check the speed signal (interrupted cable, polarity, pulse number, broken
(Motor stalled delay time) encoder shaft).
- check the speed encoder, if another speed encoder was selected using the data
set changeover. This must be connected
to the same motor that is controlled for the data set changeover.
If there is no fault, then the fault tolerance (p1744 and p0492) can be increased.
If the stalled motor should take place in the range of the monitor model and for
speeds of less than 30 % of the rated
motor speed, then a change can be made directly from the current model into
the flux impression (p1401.5 = 1). We
therefore recommend that the time-controlled model change is switched in
(p1750.4 = 1) or the model changeover
limits are significantly increased (p1752 > 0.35 * p0311; p1753 = 5 %).
For closed-loop speed and torque control without speed encoder, the following
applies:
- Check whether the drive stalls solely due to the load in controlled mode
(r1750.0) or when the speed setpoint is still
zero. If so, increase the current setpoint via p1610 or set p1750 bit 2 = 1
(sensorless vector control to standstill for
passive loads).
- If the motor excitation time (p0346) was reduced significantly and the drive
stalls when it is switched on and run
immediately, p0346 should be increased again or quick magnetization (p1401)
selected.
- Check the current limits (p0640, r0067, r0289). If the current limits are too low,
then the drive cannot be magnetized.
- check the current controller (p1715, p1717) and the speed adaptation
controller (p1764, p1767). If the dynamic
response was significantly reduced, then this should be increased again.
- check the speed encoder, if another speed encoder was selected using the data
Sinamics G130 F07905 (n,A) External armature short-circuit: Contactor When opening, the contactor feedback signal (p1235) did not issue the - check that the contactor feedback signal is correctly connected (p1235).
feedback signal "Open" missing signal "Open" (r1239.1 = 0) within the monitoring - check the logic of the contactor feedback signal (r1239.1 = 1: "Closed", r1239.1
time (p1236). = 0: "Open").
- increase the monitoring time (p1236).
- if required, set the external armature short-circuit without contactor feedback
signal (p1231=2).
Sinamics G130 F07906 Armature short-circuit / internal voltage The armature short-circuit is incorrectly parameterized. Re cause 1:
protection: Parameterization error Fault value (r0949, interpret decimal): - an armature short-circuit / voltage protection is only permissible for
Low word: Motor data set number permanent-magnetic synchronous motors. The
High word: Cause: highest position of the motor type in p0300 must either be 2 or 4.
1: A permanent-magnet synchronous motor has not been selected. Re cause 101:
101: External armature short-circuit: Output (r1239.0) not connected up. - the contactor for the external armature short-circuit configuration should be
102: External armature short-circuit with contactor feedback signal: No controlled using output signal r1239.0.
feedback signal connected (BI:p1235). The signal can, e.g. be connected to an output terminal BI: p0738. Before this
103: External armature short-circuit without contactor feedback signal: fault can be acknowledged, p1231
Delay time when opening (p1237) is 0. must be set again.
Re cause 102:
- if the external armature short-circuit with contactor feedback signal (p1231 =
1) is selected, this feedback signal
must be connected to an input terminal (e.g. r722.x) and then connected to BI:
p1235.
- alternatively, the external armature short-circuit without contactor feedback
signal (p1231 = 2) can be selected.
Re cause 103:
- if the external armature short-circuit without contactor feedback signal (p1231
= 2) is selected, then a delay time
must be parameterized in p1237. This time must always be greater than the
actual contactor opening time, as otherwise
the Motor Module would be short-circuited!

Sinamics G130 F07907 Internal armature short-circuit: Motor The function "Internal voltage protection" (p1231 = 3) was activated. The None necessary.
terminals are not at zero potential after pulse following must be observed: This a note for the user.
suppression - when the internal voltage protection is active, after pulse suppression, all
of the motor terminals are at half of the
DC link voltage (without an internal voltage protection, the motor terminals
are at zero potential)!
- it is only permissible to use motors that are short-circuit proof (p0320 <
p0323).
- the Motor Module must be able to continually conduct 180% short-circuit
current (r0331) of the motor (r0289).
- the internal voltage protection cannot be interrupted due to a fault
response. If an overcurrent condition occurs during
the active, internal voltage protection, then this can destroy the Motor
Module and/or the motor.
- if the Motor Module does not support the autonomous, internal voltage
protection (r0192.10 = 0), in order to ensure
safe, reliable functioning when the line supply fails, an external 24 V power
supply (UPS) must be used for the components.
- if the Motor Module does support the autonomous, internal voltage
protection (r0192.10 = 1), in order to ensure
safe, reliable functioning when the line supply fails, the 24 V power supply
for the components must be provided
through a Control Supply Module.
- if the internal voltage protection is active, it is not permissible that the
motor is driven by the load for a longer period
of time (e.g. as a result of loads that move the motor or another coupled
motor).

Sinamics G130 F07909 Internal voltage protection: De-activation only The de-activation of the internal voltage protection (p1231 not equal to 3) None necessary.
effective after POWER ON only becomes effective after POWER ON. This a note for the user.
The status signal r1239.6 = 1 indicates that the internal voltage protection
is ready.

Sinamics G130 F07913 Excitation current outside the tolerance range The difference between the excitation current actual value and setpoint - check the parameterization (p1640, p3201, p3202).
has exceeded the tolerance: - check the interfaces to the excitation equipment (r1626, p1640).
abs(r1641 - r1626) > p3201 + p3202 - check the excitation equipment.
The cause of this fault is again reset for abs(r1641 - r1626) < p3201.

Sinamics G130 F07914 Flux out of tolerance The difference between the flux actual value and setpoint has exceeded - check the parameterization (p3204, p3205).
the tolerance: - check the interfaces to the excitation equipment (r1626, p1640).
abs(r0084 - r1598) > p3204 + p3205 - check the excitation equipment.
The cause of this fault is again reset for abs(r0084 - r1598) < p3204. - check the flux control (p1592, p1592, p1597).
The fault is only issued after the delay time in p3206 has expired. - check the control for oscillation and take the appropriate counter measures
(e.g. optimize the speed control loop,
parameterize a bandstop filter).

Sinamics G130 F07923 Drive: Torque too low The torque deviates from the torque/speed envelope characteristic in the Adapt the load.
negative direction (too low).
Sinamics G130 F07924 Drive: Torque too high The torque deviates from the torque/speed envelope characteristic in the Adapt the load.
positive direction (too high).
Sinamics G130 F07925 Drive: Torque outside the tolerance The torque deviates from the torque/speed envelope characteristic. Adapt the load.
Sinamics G130 F07928 Internal voltage protection initiated The Motor Module signals that the motor is short-circuited through the If the Motor Module supports the autonomous internal voltage protection
power semiconductors (r1239.5 = 1). The (r0192.10 = 1), then the Motor Module automatically
pulses cannot be enabled. The internal voltage protection is selected decides - using the DC link voltage - as to whether the armature short-circuit
(p1231 = 3). should be activated.
The armature short-circuit is activated and response OFF2 is initiated if the DC
link voltage exceeds 800 V. If the DC
link voltage falls below 450 V, then the armature short-circuit is withdrawn.
If the motor is still in a critical speed range, the armature short-circuit is re-
activated once the DC link voltage exceeds
the threshold of 800 V.
If the autonomous (independent) internal voltage protection is active (r1239.5 =
1) and the line supply returns (450
V < DC link voltage < 800 V), the armature short-circuit is withdrawn after 1
minute.

Sinamics G130 F07930 Drive: Brake control error The Control Unit has detected a brake control error. - check the motor holding brake connection.
Fault value (r0949, interpret decimal): - check the function of the motor holding brake.
10, 11: - check whether there is a DRIVE-CLiQ communication error between the Control
Fault in "open holding brake" operation. Unit and the Motor Module
- No brake connected or wire breakage (check whether brake releases for involved and, if required, carry out a diagnostics routine for the faults identified.
p1278 = 1). - check that the electrical cabinet design and cable routing are in compliance
- Ground fault in brake cable. with EMC regulations (e.g. shield of the
20: motor cable and brake conductors are connected with the shield connecting
Fault in "brake open" state. plate and the motor connectors are
- Short-circuit in brake winding. tightly screwed to the housing).
30, 31: - replace the Motor Module involved.
Fault in "close holding brake" operation. Operation with Safe Brake Module:
- No brake connected or wire breakage (check whether brake releases for - check the Safe Brake Modules connection.
p1278 = 1). - replace the Safe Brake Module.
- Short-circuit in brake winding. See also: p1215 (Motor holding brake configuration), p1278 (Brake control,
40: diagnostics evaluation)
Fault in "brake closed" state.
50:
Fault in the brake control circuit of the Control Unit or communication fault
between the Control Unit and Motor Module
(brake control).

Sinamics G130 F97935 (N) Drv: Motor holding brake detected A motor with integrated motor holding brake was detected where the None necessary.
brake control has not been configured (p1215
= 0). The brake control configuration was then set to "motor holding brake
the same as sequence control" (p1215 =
1).

Sinamics G130 F07940 Sync-line-drive: Synchronization error After synchronization has been completed, the phase difference (r3808) is If required increase the threshold value phase synchronism (p3813) for
greater than the threshold value, phase synchronizing the line supply to the drive.
synchronism (p3813). Before OFF1 or OFF3, complete synchronizing (r03819.0 = 0).
OFF1 or OFF3 response, while the closed-loop phase control is active Before withdrawing the enable signal (p3802 = 0), reach synchronism (r3819.2 =
(r3819.6 = 1) or synchronism reached 1).
(r3819.2 = 1). See also: p3813 (Sync-line-drive phase synchronism threshold value)
Enable signal withdrawn (p3802 = 0), while the closed-loop phase control
was active (r3819.6 = 1).

Sinamics G130 F07950 (A) Drive: Incorrect motor parameter - the motor parameters were incorrectly entered while commissioning (e.g. Compare the motor data with the rating plate data and if required, correct.
p0300 = 0, no motor) See also: p0300, p0301, p0304, p0305, p0307, p0310, p0311, p0314, p0316,
The braking resistor (p6811) has still not been parameterized - p0320, p0322, p0323
commissioning cannot be completed.
Fault value (r0949, interpret decimal):
The parameter number involved.
See also: p0300, p0301, p0304, p0305, p0307, p0310, p0311, p0314,
p0316, p0320, p0322, p0323

Sinamics G130 F07955 Drive: Motor has been changed The code number of the current motor with DRIVE-CLiQ does not match Connect the original motor, power up the Control Unit again (POWER ON) and
the saved number. exit the quick commissioning by setting
Fault value (r0949, interpret decimal): p0010 to 0.
Number of the incorrect parameter. Or set p0300 = 10000 (load the motor parameter with DRIVE-CLiQ) and re-
See also: p0301 (Motor code number selection), r0302 (Motor code commission.
number of motor with DRIVE-CLiQ) 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.

Sinamics G130 F07956 (A) Drive: Motor code does not match the list The motor code of the current motor with DRIVE-CLiQ does not match the Use a motor with DRIVE-CLiQ and the matching motor code.
(catalog) motor possible list motor types (refer to the The first three digits of the motor code generally correspond to the matching list
selection, p0300). motor type.
Fault value (r0949, interpret decimal):
Motor code of the motor with DRIVE-CLiQ
Sinamics G130 F07963 Drive: Friction characteristic record interrupted The conditions to record the friction characteristic are not fulfilled. Fulfill the conditions to record the friction characteristic.
Fault value (r0949, interpret decimal): Re fault value = 0046:
0046: Missing enable signals (r0046). Establish missing enable signals.
1082: The highest speed value to be approached (p3829) is greater than Re fault value = 0840:
the maximum speed (p1082). Select OFF1 (p0840) only after the friction characteristic record has been
1084: The highest speed value to be approached (p3829) is greater than completed.
the maximum speed (r1084, p1083, p1085). Re fault value = 1082, 1084, 1087:
1087: The highest speed value to be approached (p3829) is greater than Select the highest speed value to be approached (p3829) less than or equal to
the maximum speed (r1087, p1086, p1088). the maximum speed (p1082, r1084,
1110: Friction characteristic record, negative direction selected (p3845) and r1087).
negative direction inhibited (p1110). Re-calculate the speed points along the friction characteristic (p0340 = 5).
1111: Friction characteristic record, positive direction selected (p3845) and Re fault value = 1110:
positive direction inhibited (p1111). Select the friction characteristic record, positive direction (p3845).
1198: Friction characteristic record selected (p3845 > 0) and negative Re fault value = 1111:
(p1110) and positive directions (p1111) inhibited Select the friction characteristic record, negative direction (p3845).
(r1198). Re fault value = 1198:
1300: The control mode (p1300) has not been set to closed-loop speed Enable the permitted direction (p1110, p1111, r1198).
control. Re fault value = 1300:
1755: For encoderless closed-loop control (p1300 = 20), the lowest speed Set the control mode (p1300) on the closed-loop speed control (p1300 = 20, 21).
value to be approached (p3820) is less Re fault value = 1755:
than or equal to the changeover speed, open-loop controlled operation For encoderless closed-loop speed control (p1300 = 20) select the lowest speed
(p1755). value to be approached (p3820)
1910: Motor data identification activated. greater than the changeover speed of open-loop controlled operation (p1755).
1960: Speed controller optimization activated. Re-calculate the speed points along the friction characteristic (p0340 = 5).
3820 ... 3829: Speed (p382x) cannot be approached. Re fault value = 1910:
3840: Friction characteristic incorrect. Exit the motor data identification routine (p1910).
3845: Friction characteristic record de-selected.

Sinamics G130 F07967 Drive: Automatic encoder adjustment incorrect A fault has occurred during the automatic encoder adjustment or the pole Carry out a POWER ON.
position identification.
Only for internal Siemens troubleshooting.

Sinamics G130 F07968 Drive: Lq-Ld measurement incorrect A fault has occurred during the Lq-Ld measurement. Re fault value = 10:
Fault value (r0949, interpret decimal): Check whether the motor is correctly connected.
10: Stage 1: The ratio between the measured current and zero current is Replace the Motor Module involved.
too low. De-activate traversing (p1909).
12: Stage 1: The maximum current was exceeded. Re fault value = 12:
15: Second harmonic too low. Check whether motor data have been correctly entered.
16: Drive converter too small for the measuring technique. De-activate traversing (p1909).
17: Abort due to pulse inhibit. Re fault value = 16:
De-activate traversing (p1909).
Re fault value = 17:
Repeat traversing.

Sinamics G130 F07969 Drive: Incorrect pole position identification A fault has occurred during the pole position identification routine. Re fault value = 1:
Fault value (r0949, interpret decimal): Check whether the motor is correctly connected.
1: Current controller limited Check whether motor data have been correctly entered.
2: Motor shaft locked. Replace the Motor Module involved.
4: Encoder speed signal not plausible. Re fault value = 2:
10: Stage 1: The ratio between the measured current and zero current is Open the motor holding brake (p1215) and bring the motor into a no-load
too low. condition.
11: Stage 2: The ratio between the measured current and zero current is Re fault value = 4:
too low. Check whether the encoder pulse number (p0408) and gearbox factor (p0432,
12: Stage 1: The maximum current was exceeded. p0433) are correct.
13: Stage 2: The maximum current was exceeded. Check whether the motor pole pair number is correct (p0314).
14: Current difference to determine the +d axis too low. Re fault value = 10:
15: Second harmonic too low. When selecting p1980 = 4: Increase the value for p0325.
16: Drive converter too small for the measuring technique. When selecting p1980 = 1: Increase the value for p0329.
17: Abort due to pulse inhibit. Check whether the motor is correctly connected.
18: First harmonic too low. Replace the Motor Module involved.
20: Pole position identification requested with the motor shaft rotating and Re fault value = 11:
activated flying restart function. Increase the value for p0329.
Check whether the motor is correctly connected.
Replace the Motor Module involved.
Re fault value = 12:
When selecting p1980 = 4: Reduce the value for p0325.
When selecting p1980 = 1: Reduce the value for p0329.
Check whether motor data have been correctly entered.
Sinamics G130 F07970 Drive: Automatic encoder adjustment incorrect A fault has occurred during the automatic encoder adjustment. Re fault value = 1:
Fault value (r0949, decimal): Check whether the motor is correctly connected.
1: Current controller limited Check whether motor data have been correctly entered.
2: Motor shaft locked. Replace the Motor Module involved.
4: Encoder speed signal not plausible. Re fault value = 2:
10: Stage 1: The ratio between the measured current and zero current is Open the motor holding brake (p1215) and bring the motor into a no-load
too low. condition.
11: Stage 2: The ratio between the measured current and zero current is Re fault value = 4:
too low. Check whether the speed actual value inversion is correct (p0410.0).
12: Stage 1: The maximum current was exceeded. Check whether the motor is correctly connected.
13: Stage 2: The maximum current was exceeded. Check whether the encoder pulse number (p0408) and gearbox factor (p0432,
14: Current difference to determine the +d axis too low. p0433) are correct.
15: Second harmonic too low. Check whether the motor pole pair number is correct (p0314).
16: Drive converter too small for the measuring technique. Re fault value = 10:
17: Abort due to pulse inhibit. 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 Module involved.
Re fault value = 12:
Reduce the value for p0325.
Check whether motor data have been correctly entered.
Re fault value = 13:
Reduce the value for p0329.
Check whether motor data have been correctly entered.
Re fault value = 14:
Increase the value for p0329.

Sinamics G130 F07982 Drive: Rotating measurement encoder test A fault has occurred during the encoder test. Re fault value = 1:
Fault value (r0949, interpret decimal): - check the motor parameters.
1: The speed did not reach a steady-state condition. - carry out a motor data identification routine (p1910).
2: The speed setpoint was not able to be approached as the minimum - if required, reduce the dynamic factor (p1967 < 25 %).
limiting is active. Re fault value = 2:
3: The speed setpoint was not able to be approached as the suppression - adapt the speed setpoint (p1965) or adapt the minimum limit (p1080).
(skip) bandwidth is active. Re fault value = 3:
4: The speed setpoint was not able to be approached as the maximum - adapt the speed setpoint (p1965) or suppression (skip) bandwidths (p1091 ...
limiting is active. p1094, p1101).
5: The encoder does not supply a signal. Re fault value = 4:
6: Incorrect polarity. - adapt the speed setpoint (p1965) or maximum limit (p1082, p1083 and p1086).
7: Incorrect pulse number. Re fault value = 5:
8: Noise in the encoder signal or speed controller unstable. - check the encoder connection. If required, replace the encoder.
9: Voltage Sensing Module (VSM) incorrectly connected. Re fault value = 6:
- check the connection assignment of the encoder cable. Adapt the polarity
(p0410).
Re fault value = 7:
- adapt the pulse number (p0408).
Re fault value = 8:
- check the encoder connection and encoder cable. It is possible that there is a
problem associated with the ground
connection.
- reduce the dynamic response of the speed controller (p1460, p1462 and
p1470, p1472).
Re fault value = 9:
- check the connections of the Voltage Sensing Module (VSM).
Note:
The encoder test can be switched out (disabled) using p1959.0.
See also: p1959 (Rotating measurement configuration)
Sinamics G130 F07983 Drive: Rotating measurement saturation A fault has occurred while determining the saturation characteristic. Re fault value = 1:
characteristic Fault value (r0949, interpret decimal): - the total drive moment of inertia is far higher than that of the motor (p0341,
1: The speed did not reach a steady-state condition. p0342).
2: The rotor flux did not reach a steady-state condition. De-select rotating measurement (p1960), enter the moment of inertia p0342, re-
3: The adaptation circuit did not reach a steady-state condition. calculate the speed controller p0340
4: The adaptation circuit was not enabled. = 4 and repeat the measurement.
5: Field weakening active. Re fault value = 1 ... 2:
6: The speed setpoint was not able to be approached as the minimum - increase the measuring speed (p1961) and repeat the measurement.
limiting is active. Re fault value = 1 ... 4:
7: The speed setpoint was not able to be approached as the suppression - check the motor parameters (rating plate data). After the change: Calculate
(skip) bandwidth is active. p0340 = 3.
8: The speed setpoint was not able to be approached as the maximum - check the moment of inertia (p0341, p0342). After the change: Calculate p0340
limiting is active. = 3.
9: Several values of the determined saturation characteristic are not - carry out a motor data identification routine (p1910).
plausible. - if required, reduce the dynamic factor (p1967 < 25 %).
10: Saturation characteristic could not be sensibly determined because Re fault value = 5:
load torque too high. - the speed setpoint (p1961) is too high. Reduce the speed.

Sinamics G130 F07984 Drive: Speed controller optimization, moment A fault has occurred while identifying the moment of inertia. Re fault value = 1:
of inertia Fault value (r0949, interpret decimal): - check the motor parameters (rating plate data). After the change: Calculate
1: The speed did not reach a steady-state condition. p0340 = 3.
2: The speed setpoint was not able to be approached as the minimum - check the moment of inertia (p0341, p0342). After the change: Calculate p0340
limiting is active. = 3.
3. The speed setpoint was not able to be approached as the suppression - carry out a motor data identification routine (p1910).
(skip) bandwidth is active. - if required, reduce the dynamic factor (p1967 < 25 %).
4. The speed setpoint was not able to be approached as the maximum Re fault value = 2, 5:
limiting is active. - adapt the speed setpoint (p1965) or adapt the minimum limit (p1080).
5: It is not possible to increase the speed by 10% as the minimum limiting is Re fault value = 3, 6:
active. - adapt the speed setpoint (p1965) or suppression (skip) bandwidths (p1091 ...
6: It is not possible to increase the speed by 10% as the suppression (skip) p1094, p1101).
bandwidth is active. Re fault value = 4, 7:
7: It is not possible to increase the speed by 10% as the maximum limiting - adapt the speed setpoint (p1965) or maximum limit (p1082, p1083 and p1086).
is active. Re fault value = 8:
8: The torque difference after the speed setpoint step is too low in order to - the total drive moment of inertia is far higher than that of the motor (refer to
be able to still reliably identify the moment p0341, p0342). De-select rotating measurement
of inertia. (p1960), enter the moment of inertia p342, re-calculate the speed controller
9: Too few data to be able to reliably identify the moment of inertia. p0340 = 4 and repeat the measurement.
10: After the setpoint step, the speed either changed too little or in the Re fault value = 9:
incorrect direction. - check the moment of inertia (p0341, p0342). After the change, re-calculate
11: The identified moment of inertia is not plausible. (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)

Sinamics G130 F07985 Drive: Speed controller optimization A fault has occurred during the vibration test. Re fault value = 1:
(oscillation test) Fault value (r0949, interpret decimal): - check the motor parameters (rating plate data). After the change: Calculate
1: The speed did not reach a steady-state condition. p0340 = 3.
2: The speed setpoint was not able to be approached as the minimum - check the moment of inertia (p0341, p0342). After the change: Calculate p0340
limiting is active. = 3.
3: The speed setpoint was not able to be approached as the suppression - carry out a motor data identification routine (p1910).
(skip) bandwidth is active. - if required, reduce the dynamic factor (p1967 < 25 %).
4: The speed setpoint was not able to be approached as the maximum Re fault value = 2:
limiting is active. - adapt the speed setpoint (p1965) or adapt the minimum limit (p1080).
5: Torque limits too low for a torque step. Re fault value = 3:
6: No suitable speed controller setting was found. - 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:
- increase the torque limits (e.g. p1520, p1521).
Re fault value = 6:
- reduce the dynamic factor (p1967).
- disable the vibration test (p1959.4 = 0) and repeat the rotating measurement.
See also: p1959 (Rotating measurement configuration)
Sinamics G130 F07986 Drive: Rotating measurement ramp-function During the rotating measurements, problems with the ramp-function Re fault value = 1:
generator generator occurred. Enable the direction (p1110 or p1111).
Fault value (r0949, interpret decimal):
1: The positive and negative directions are inhibited.

Sinamics G130 F07988 Drive: Rotating measurement, no configuration When configuring the rotating measurement (p1959), no function was Select at least one function for automatic optimization of the speed controller
selected selected. (p1959).
See also: p1959 (Rotating measurement configuration)

Sinamics G130 F07989 Drive: Rotating measurement leakage An error has occurred while measuring the dynamic leakage inductance. Re fault value = 1:
inductance (q-axis) Fault value (r0949, interpret decimal): - check the motor parameters.
1: The speed did not reach a steady-state condition. - carry out a motor data identification routine (p1910).
2: The speed setpoint was not able to be approached as the minimum - if required, reduce the dynamic factor (p1967 < 25 %).
limiting is active. Re fault value = 2:
3: The speed setpoint was not able to be approached as the suppression - adapt the speed setpoint (p1965) or adapt the minimum limit (p1080).
(skip) bandwidth is active. Re fault value = 3:
4: The speed setpoint was not able to be approached as the maximum - adapt the speed setpoint (p1965) or suppression (skip) bandwidths (p1091 ...
limiting is active. p1094, p1101).
5: The 100% flux setpoint was not reached. Re fault value = 4:
6: No Lq measurement possible because field weakening is active. - adapt the speed setpoint (p1965) or maximum limit (p1082, p1083 and p1086).
7: Speed actual value exceeds the maximum speed p1082 or 75% of the Re fault value = 5:
rated motor speed. - flux setpoint p1570 = 100% and current setpoint p1610 = 0% kept during the Lq
8: Speed actual value is below 2 % of the rated motor speed. measurement.
Re fault value = 6:
- reduce the regenerative load so that the drive does not reach field weakening
when accelerating.
- reduce p1965 so that the q leakage inductance is recorded at lower speeds.
Re fault value = 7:
- increase p1082 if this is technically permissible.
- reduce p1965 so that the q leakage inductance is recorded at lower speeds.
Re fault value = 8:
- reduce the load when motoring so that the drive is not braked.
- increase p1965 so that the measurement is possibly done at higher speeds.
Note:
The measurement of the q leakage inductance can be disabled using p1959.5. If
only p1959.5 is set, then only this
measurement is carried out if p1960 is set to 1, 2 and the drive is powered up.
See also: p1959 (Rotating measurement configuration)

Sinamics G130 F07990 Drive: Incorrect motor data identification A fault has occurred during the identification routine. Re fault value = 0:
Fault value (r0949, interpret decimal): - check whether the motor is correctly connected. Observe configuration
1: Current limit value reached. (star/delta).
2: Identified stator resistance lies outside the expected range 0.1 ... 100 % Re fault value = 1 ... 40:
of Zn. - check whether motor data have been correctly entered in p0300, p0304 ...
3: Identified rotor resistance lies outside the expected range 0.1 ... 100 % of p0311.
Zn. - is there an appropriate relationship between the motor power rating and that
4: Identified stator reactance lies outside the expected range 50 ... 500 % of of the Motor Module? The ratio of the
Zn. Motor Module to the rated motor current should not be less than 0.5 and not be
5: Identified magnetizing reactance lies outside the expected range 50 ... greater than 4.
500 % of Zn. - check configuration (star/delta).
6: Identified rotor time constant lies outside the expected range 10 ms ... 5 Re fault value = 2:
s. - for parallel circuits, check the motor winding system in p7003. If, for power
7: Identified total leakage reactance lies outside the expected range 4 ... 50 units connected in parallel, a motor is
% of Zn. specified with a single-winding system (p7003 = 0), although a multi-winding
8: Identified stator leakage reactance lies outside the expected range 2 ... system is being used, then a large proportion
50 % of Zn. of the stator resistance is interpreted as feeder cable resistance and entered in
9: Identified rotor leakage reactance lies outside the expected range 2 ... 50 p0352.
% of Zn. Re fault value = 4, 7:
10: Motor has been incorrectly connected. - check whether inductances are correctly entered in p0233 and p0353.
11: Motor shaft rotates. - check whether motor was correctly connected (star/delta).
20: Identified threshold voltage of the semiconductor devices lies outside Re fault value = 50:
the expected range 0 ... 10 V. - reduce the current controller sampling rate.
30: Current controller in voltage limiting. 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).

Sinamics G130 F08000 (N,A) TB: +/-15 V power supply faulted Terminal Board 30 detects an incorrect internal power supply voltage. - replace Terminal Board 30.
Fault value (r0949, interpret decimal): - replace Control Unit.
0: Error when testing the monitoring circuit.
1: Fault in normal operation.

Sinamics G130 F08010 (N,A) TB: Analog-digital converter The analog/digital converter on Terminal Board 30 has not supplied any - check the power supply.
converted data. - replace Terminal Board 30.
Sinamics G130 F08500 (A) COMM BOARD: Monitoring time configuration The monitoring time for the configuration has expired. Check communication line.
expired Fault value (r0949, interpret decimal):
0: The transfer time of the send configuration data has been exceeded.
1: The transfer time of the receive configuration data has been exceeded.

Sinamics G130 F08501 (N,A) COMM BOARD: Monitoring time process data The set monitoring time expired while transferring process data via COMM - check communications link.
expired BOARD. - check the set monitoring time if the error persists.
See also: p8840 (COMM BOARD monitoring time) See also: p8840 (COMM BOARD monitoring time)

Sinamics G130 F08510 (A) COMM BOARD: Send configuration data invalid COMM BOARD did not accept the send-configuration data. Check the send configuration data.
Fault value (r0949, interpret decimal):
Return value of the send-configuration data check.

Sinamics G130 F08700 (A) CBC: Communications error A CAN communications error has occurred. - check the bus cable
Fault value (r0949, interpret decimal): - check the baud rate (p8622).
1: The error counter for the send telegrams has exceeded the BUS OFF - check the bit timing (p8623).
value 255. The bus disables the CAN controller. - check the master.
- bus cable interrupted. See also: p8622 (CBC baud rate), p8623 (CBC bit timing selection)
- bus cable not connected.
- incorrect baud rate.
- incorrect bit timing.
2: The master no longer interrogated the CAN node status longer than for
its "life time". The "life time" is obtained
from the "guard time" (p8604[0]) multiplied by the "life time factor"
(p8604[1]).
- bus cable interrupted.
- bus cable not connected.
- incorrect baud rate.
- incorrect bit timing.
- master fault.
Note:
The fault response can be set as required using p8641.
See also: p8604 (CBC node guarding), p8641 (CBC abort connection option
code)

Sinamics G130 F08701 CBC: NMT state change A CANopen NMT state transition from "operational" to "pre-operational" or None necessary.
after "stopped". Acknowledge the fault and continue operation.
Fault value (r0949, interpret decimal):
1: CANopen NMT state transition from "operational" to "pre-operational".
2: CANopen NMT state transition from "operational" to "stopped".
Note:
In the NMT state "pre-operational", process data cannot be transferred and
in the NMT state "stopped", no process
data and no service data can be transferred.

Sinamics G130 F30001 Power unit: Overcurrent The power unit has detected an overcurrent condition. - check the motor data - if required, carry out commissioning.
- closed-loop control is incorrectly parameterized. - check the motor circuit configuration (star-delta).
- motor has a short-circuit or fault to ground (frame). - V/f operation: Increase up ramp.
- V/f operation: Up ramp set too low. - V/f operation: Check the assignment of the rated currents of the motor and
- V/f operation: Rated motor current is significantly greater than that of the Motor Module.
Motor Module. - infeed: Check the line supply quality.
- infeed: High discharge and post-charging current for line supply voltage - infeed: Reduce the load when motoring.
interruptions. - infeed: Correct connection of the line commutating reactor.
- infeed: High post-charging currents for overload when motoring and DC - check the power cable connections.
link voltage dip. - check the power cables for short-circuit or ground fault.
- infeed: Short-circuit currents at power-on due to the missing - check the length of the power cables.
commutating reactor. - replace power unit.
- power cables are not correctly connected. For a parallel switching device (r0108.15 = 1) the following additionally applies:
- power cables exceed the maximum permissible length. - check the ground fault monitoring thresholds (p0287).
- power unit defective. - check the setting of the closed-loop circulating current control (p7036, p7037).
Additional causes for a parallel switching device (r0108.15 = 1):
- a power unit has tripped (powered down) due to a ground fault.
- the closed-loop circulating current control is either too slow or has been
set too fast.
Fault value (r0949, interpret bitwise binary):
Bit 0: Phase U.
Bit 1: Phase V.
Bit 2: Phase W.
Note:
Fault = 0 means that the phase with overcurrent is not recognized (e.g. for
Blocksize device).
Sinamics G130 F30002 Power unit: DC link voltage, overvoltage The power unit has detected an overvoltage condition in the DC link. - increase the ramp-down time.
- motor regenerates too much energy. - activate the DC link voltage controller.
- device supply voltage too high. - use a brake resistor or Active Line Module.
- when operating with a VSM, the phase assignment L1, L2, L3 at the VSM - increase the current limit of the infeed or use a larger module (for the Active
differs from the phase assignment at the Line Module).
power unit. - check the device supply voltage.
Fault value (r0949, interpret decimal): - check and correct the phase assignment at the VSM and at the power unit.
DC link voltage [1 bit = 100 mV]. See also: p0210 (Drive unit line supply voltage), p1240 (Vdc controller or Vdc
For SINAMICS GM/SM, the following applies: monitoring configuration)
Fault value (r0949, interpret decimal):
32: Overvoltage in the negative partial DC link (VdcP)
64: Overvoltage in the positive partial DC link (VdcN)
96: Overvoltage in both partial DC links

Sinamics G130 F30003 Power unit: DC link voltage, undervoltage The power unit has detected an undervoltage condition in the DC link. - check the line supply voltage
- line supply failure - check the line supply infeed and if necessary observe the fault messages of the
- line supply voltage below the permissible value. line supply infeed.
- line supply infeed failed or interrupted. Note:
Note: The "ready for operation" signal of the infeed r0863 must be connected to the
The monitoring threshold for the DC link undervoltage is the minimum of associated inputs p0864 of the drives.
the following values: See also: p0210 (Drive unit line supply voltage)
- for a calculation, refer to p0210.

Sinamics G130 F30004 Power unit: Overtemperature heat sink AC The temperature of the power unit heat sink has exceeded the permissible - check whether the fan is running.
inverter limit value. - check the fan elements
- insufficient cooling, fan failure. - check whether the ambient temperature is in the permissible range.
- overload. - check the motor load.
- ambient temperature too high. - reduce the pulse frequency if this is higher than the rated pulse frequency.
- pulse frequency too high. Notice:
Fault value (r0949): This fault can only be acknowledged after this alarm threshold for alarm A05000
Temperature [1 bit = 0.01 °C]. has been undershot.
See also: p1800 (Pulse frequency)

Sinamics G130 F30005 Power unit: Overload I2t The power unit was overloaded (r0036 = 100 %). - reduce the continuous load.
- the permissible rated power unit current was exceeded for an - adapt the load duty cycle.
inadmissibly long time. - check the motor and power unit rated currents.
- the permissible load duty cycle was not maintained. See also: r0036 (Power unit overload I2t), r0206 (Rated power unit power),
Fault value (r0949, interpret decimal): p0307 (Rated motor power)
I2t [100 % = 16384].

Sinamics G130 F30006 Power unit: Thyristor Control Board The Thyristor Control Board (TCB) of the Basic Line Module signals a fault. The faults must be saved in the Thyristor Control Board and must be
- there is no line supply voltage. acknowledged. To do this, the supply voltage
- the line contactor is not closed. of the Thyristor Control Board must be switched out for at least 10 s!
- the line supply voltage is too low. - check the line supply voltage
- line supply frequency outside the permissible range (45 ... 66 Hz). - check or energize the line contactor.
- there is a DC link short-circuit. - check the monitoring time and, if required, increase (p0857).
- there is a DC link short-circuit (during the pre-charging phase). - if required, observe additional power unit messages/signals.
- voltage supply for the Thyristor Control Board outside the nominal range - check the DC link regarding short-circuit or ground fault.
(5 ... 18 V) and line voltage >30 V. - evaluate diagnostic LEDs for the Thyristor Control Board.
- there is an internal fault in the Thyristor Control Board.

Sinamics G130 F30008 Power unit: Sign-of-life error cyclic data The power unit has detected that the cyclic setpoint telegrams of the - check the electrical cabinet design and cable routing for EMC compliance
Control Unit were not punctually updated for at - for projects with the VECTOR drive object, check whether p0117 = 6 has been
least two clock cycles within a time interval of 20 ms. set on the Control Unit.
See also: p0117 (Current controller computing dead time mode)

Sinamics G130 F30011 Power unit: Line phase failure in main circuit A line phase failure was detected at the power unit. Check the fuses in the main circuit.
- the fuse of a phase of a main circuit has ruptured.
- the DC link voltage ripple has exceeded the permissible limit value.
Sinamics G130 F30012 Power unit: Temperature sensor heat sink wire The connection to one of the heat sink temperature sensors in the power Contact the manufacturer.
breakage unit is interrupted.
Fault value (r0949, interpret hexadecimal):
Bit 0: Module slot (electronics slot)
Bit 1: Air intake
Bit 2: Inverter 1
Bit 3: Inverter 2
Bit 4: Inverter 3
Bit 5: Inverter 4
Bit 6: Inverter 5
Bit 7: Inverter 6
Bit 8: Rectifier 1
Bit 9: Rectifier 2

Sinamics G130 F30013 Power unit: Temperature sensor heat sink The heat sink temperature sensor in the Motor Module is short-circuited. Contact the manufacturer.
short-circuit Fault value (r0949, interpret hexadecimal):
Bit 0: Module slot (electronics slot)
Bit 1: Air intake
Bit 2: Inverter 1
Bit 3: Inverter 2
Bit 4: Inverter 3
Bit 5: Inverter 4
Bit 6: Inverter 5
Bit 7: Inverter 6
Bit 8: Rectifier 1
Bit 9: Rectifier 2

Sinamics G130 F30017 Power unit: Hardware current limit has The hardware current limitation in the relevant phase (see A30031, For infeed units, the following applies:
responded too often A30032, A30033) has responded too often. The - check the controller settings, if required, reset and identify the controller
number of times the limit has been exceeded depends on the design and (p0340 = 2, p3410 = 5).
type of power unit. - reduce the load, if required, increase the DC link capacitance or use a higher-
For infeed units, the following applies: rating infeed.
- closed-loop control is incorrectly parameterized. - check the connection of the optional Voltage Sensing Module.
- load on the infeed is too high. - check the connection and technical data of the commutating reactor.
- Voltage Sensing Module incorrectly connected. - check the power cables for short-circuit or ground fault.
- commutating reactor missing or the incorrect type. - replace power unit.
- power unit defective. The following applies to Motor Modules:
The following applies to Motor Modules: - check the motor data.
- closed-loop control is incorrectly parameterized. - check the motor circuit configuration (star-delta).
- fault in the motor or in the power cables. - check the motor load.
- the power cables exceed the maximum permissible length. - check the power cable connections.
- motor load too high - check the power cables for short-circuit or ground fault.
- power unit defective. - check the length of the power cables.
Fault value (r0949, interpret binary): - replace power unit.
Bit 0: Phase U
Bit 1: Phase V
Bit 2: Phase W

Sinamics G130 F30020 Power unit: Configuration not supported A configuration is requested that is not supported by the power unit. Re fault value = 0:
Fault value (r0949, interpret hexadecimal): If internal voltage protection is active (p1231 = 3), de-activate it if necessary.
0: See also: p1231 (Armature short-circuit / DC brake configuration)
Autonomous operation is requested but is not supported.

Sinamics G130 F30021 Power unit: Ground fault Power unit has detected a ground fault. - check the power cable connections.
- ground fault in the power cables - check the motor.
- winding fault or ground fault at the motor. - check the CT.
- CT defective. The following applies additionally for CU310 and CUA31:
Additional cause for CU310/CUA31: - check the cables and contacts of the brake connection (a wire is possibly
- when the brake is applied, this causes the hardware DC current broken).
monitoring to respond. For parallel switching devices (r0108.15 = 1) the following additionally applies:
Additional cause for parallel switching devices (r0108.15 = 1): - check the ground fault monitoring thresholds (p0287).
- the closed-loop circulating current control is either too slow or has been - check the setting of the closed-loop circulating current control (p7036, p7037).
set too fast. See also: p0287 (Ground fault monitoring thresholds)
Fault value (r0949, interpret decimal):
Absolute value, summation current [32767 = 271 % rated current].
Sinamics G130 F30022 Power unit: Monitoring V_ce In the power unit, the monitoring of the collector-emitter voltage (V_ce) of - check the fiber-optic cable and if required, replace.
the semiconductor has responded. '- check the power supply of the IGBT gating module (24 V).
Possible causes: - check the power cable connections.
- fiber-optic cable interrupted. - select the defective semiconductor and replace.C401
- power supply of the IGBT gating module missing.
- short-circuit at the Motor Module output.
- defective semiconductor in the power unit.
Fault value (r0949, interpret binary):
Bit 0: Short-circuit in phase U
Bit 1: Short circuit in phase V
Bit 2: Short-circuit in phase W
Bit 3: Light transmitter enable defective
Bit 4: V_ce group fault signal interrupted
See also: r0949 (Fault value)

Sinamics G130 F30024 Power unit: Overtemperature thermal model The temperature difference between the heat sink and chip has exceeded - adapt the load duty cycle.
the permissible limit value. - check whether the fan is running.
- the permissible load duty cycle was not maintained. - check the fan elements
- insufficient cooling, fan failure. - check whether the ambient temperature is in the permissible range.
- overload. - check the motor load.
- ambient temperature too high. - reduce the pulse frequency if this is higher than the rated pulse frequency.
- pulse frequency too high.
See also: r0037

Sinamics G130 F30025 Power unit: Chip overtemperature Chip temperature of the semiconductor has exceeded the permissible limit - adapt the load duty cycle.
value. - check whether the fan is running.
- the permissible load duty cycle was not maintained. - check the fan elements
- insufficient cooling, fan failure. - check whether the ambient temperature is in the permissible range.
- overload. - check the motor load.
- ambient temperature too high. - reduce the pulse frequency if this is higher than the rated pulse frequency.
- pulse frequency too high. Notice:
Fault value (r0949): This fault can only be acknowledged after this alarm threshold for alarm A05001
Temperature difference between the heat sink and chip [1 Bit = 0.01 °C]. has been undershot.
See also: r0037

Sinamics G130 F30027 Power unit: Precharging DC link time The power unit DC link was not able to be pre-charged within the expected In general:
monitoring time. - check the line supply voltage at the input terminals.
1) There is no line supply voltage connected. - check the line supply voltage setting (p0210).
2) The line contactor/line side switch has not been closed. - the following applies to booksize units: Wait (approx. 8 min.) until the pre-
3) The line supply voltage is too low. charging resistors have cooled down. For
4) Line supply voltage incorrectly set (p0210). this purpose, preferably disconnect the infeed unit from the line supply.
5) The pre-charging resistors are overheated as there were too many pre- Re 5):
charging operations per time unit. - carefully observe the permissible pre-charging frequency (refer to the
6) The pre-charging resistors are overheated as the DC link capacitance is appropriate Equipment Manual).
too high. Re 6):
7) The pre-charging resistors are overheated because when there is no - check the total capacitance of the DC link and if required, correspondingly
"ready for operation" (r0863.0) of the infeed reduce the maximum permissible DC
unit, power is taken from the DC link. link capacitance (refer to the appropriate Equipment Manual).
8) The pre-charging resistors are overheated as the line contactor was Re 7):
closed during the DC link fast discharge - interconnect the ready for operation signal of the infeed unit (r0863.0) in the
through the Braking Module. enable logic of the drives connected
9) The DC link has either a ground fault or a short-circuit. to this DC link.
10) The pre-charging circuit is possibly defective (only for chassis units). Re 8):
Fault value (r0949, interpret binary): - check the connections of the external line contactor. The line contactor must
Missing internal enable signals, power unit (lower 16 bit): be open during the DC link fast discharge.
(Inverted bit-coded representation FFFF hex -> all internal enable signals Re 9):
available) - check the DC link regarding ground fault or short-circuit.
Bit 0: Power supply of the IGBT gating shut down See also: p0210 (Drive unit line supply voltage)
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
Sinamics G130 F30035 Power unit: Air intake overtemperature The air intake in the power unit has exceeded the permissible temperature - check whether the fan is running.
limit. - check the fan elements
For air-cooled power units, the temperature limit is at 55 °C. - check whether the ambient temperature is in the permissible range.
- ambient temperature too high. Notice:
- insufficient cooling, fan failure. This fault can only be acknowledged after this alarm threshold for alarm A05002
Fault value (r0949, interpret decimal): has been undershot.
Temperature [1 bit = 0.01 °C].
Sinamics G130 F30036 Power unit: Electronics board overtemperature The temperature in the module slot of the drive converter has exceeded check whether the fan is running.
the permissible temperature limit. check the fan elements
- insufficient cooling, fan failure. check whether the ambient temperature is in the permissible range.
- overload. Notice:
- ambient temperature too high. This fault can only be acknowledged after this alarm threshold for alarm A05003
Fault value (r0949, interpret decimal): has been undershot.
Temperature [1 bit = 0.1 °C].

Sinamics G130 F30037 Power unit: Rectifier overtemperature The temperature in the rectifier of the power unit has exceeded the check whether the fan is running.
permissible temperature limit. check the fan elements
- insufficient cooling, fan failure. check whether the ambient temperature is in the permissible range.
- overload. check the motor load.
- ambient temperature too high. check the line supply phases.
- line supply phase failure. Notice:
Fault value (r0949, interpret decimal): This fault can only be acknowledged after this alarm threshold for alarm A05004
Temperature [1 bit = 0.01 °C]. has been undershot.

Sinamics G130 F30040 Power unit: Undervolt 24 V Failure of the 24 V power supply for the power unit. Check the 24 V DC voltage supply to power unit.
the 16 V threshold was undershot for longer than 3 ms.
Fault value (r0949, interpret decimal):
24 V voltage [1 bit = 0.1 V].

Sinamics G130 F30043 Power unit: Overvolt 24 V The following applies for CU31x: Check the 24 V DC voltage supply to power unit.
Overvoltage of the 24 V power supply for the power unit.
- the 31.5 V threshold was exceeded for more than 3 ms.
Fault value (r0949):
24 V voltage [1 bit = 0.1 V].

Sinamics G130 F30045 Power unit: Supply undervoltage The following applies for CU31x: Check the 24 V DC power supply for the power unit and if required replace the
Power supply fault in the power unit. module.
- the voltage monitoring on the DAC board signals an undervoltage fault on
the module.

Sinamics G130 F30047 Cooling system: Cooling medium flow rate too Cooling system: Cooling medium flow rate too low
low
Sinamics G130 F30050 Power unit: Supply overvoltage The following applies for CU31x and CUA31: - check the voltage supply for the Control Unit (24 V).
the voltage monitoring on the DAC board signals an overvoltage fault on - if required, replace the module.
the module.

Sinamics G130 F30052 EEPROM data error EEPROM data error of the power unit module. Re fault value = 0:
Fault value (r0949, interpret hexadecimal): Replace the power unit module or update the EEPROM data.
0: The EEPROM data read in from the power unit module is inconsistent. Re fault value = 1:
1: EEPROM data is not compatible to the firmware of the power unit The following applies for CU31x and CUA31:
application. Update the firmware \SIEMENS\SINAMICS\CODE\SAC\cu31xi.ufw (cua31.ufw)

Sinamics G130 F30062 (N,A) The bypass contactor was opened under The bypass contactor of the infeed unit was damaged by being opened In order to avoid critically damaging the complete drive converter group, it is
current (multiple number of times) while it was conducting urgently recommended to replace the
current. damaged infeed unit.
Possible causes:
- scheduled opening under load can be necessary, for example, to protect
the drive converter group in the event of
a ground fault in high frequency spindles.
- incorrect operator control of the infeed can cause the contactor to switch
under load. If, in spite of a missing operating
enable, the infeed unit draws active motoring power from the DC link.

Sinamics G130 F30070 Cycle requested by the power unit module not The following applies for CU31x and CUA31: The following applies for CU31x and CUA31:
supported A cycle is requested that is not supported by the power unit. The power unit only supports the following cycles:
Fault value (r0949, interpret hexadecimal): 62.5 μs, 125 μs, 250 μs and 500 μs
The following applies for CU31x and CUA31: Fault value (r0949, interpret hexadecimal):
0: The current control cycle is not supported. The following applies for CU31x and CUA31:
1: The DRIVE-CLiQ cycle is not supported. 0: Set a permitted current control cycle.
2: Internal timing problem (distance between RX and TX instants too low). 1: Set a permitted DRIVE-CLiQ cycle.
3: Internal timing problem (TX instant too early). 2/3: Contact the manufacturer (there is possibly an incompatible firmware
version).

Sinamics G130 F30071 No new actual values received from the power The following applies for CU31x and CUA31: The following applies for CU31x and CUA31:
unit module More than one actual value telegram from the power unit has failed. Check the interface (adjustment and locking) to the power unit.

Sinamics G130 F30072 Setpoints are no longer being transferred to The following applies for CU31x and CUA31: The following applies for CU31x and CUA31:
the power unit More than one setpoint telegram was not able to be transferred to the Check the interface (adjustment and locking) to the power unit.
power unit.

Sinamics G130 F30074 Communications error to the power unit Communication is not possible with the power unit via the plug contact. The following applies for CU31x and CUA31:
module Either replace the CU board or the power unit. You must check which of the two
components must be replaced by
replacing one and then the other component; if neither are available then both
components must be returned.
Sinamics G130 F30105 PU: Actual value sensing fault At least one incorrect actual value channel was detected on the Power Evaluate the diagnostic parameters.
Stack Adapter (PSA). If the actual value channel is incorrect, check the components and if required,
The incorrect actual value channels are displayed in the following replace.
diagnostic parameters.

Sinamics G130 F30502 Power unit: DC link voltage, overvoltage The power unit has detected overvoltage in the DC link with a pulse inhibit. - check the device supply voltage (p0210).
- device supply voltage too high. - check the dimensioning of the line reactor.
- line reactor incorrectly dimensioned. See also: p0210 (Drive unit line supply voltage)
Fault value (r0949, interpret decimal):
DC link voltage [1 bit = 100 mV].
See also: r0070 (Actual DC link voltage)

Sinamics G130 F30600 SI MM: STOP A initiated The drive-based "Safety Integrated" function in the Motor Module (MM) - select Safe Torque Off and de-select again.
has detected a fault and initiated STOP A - replace the Motor Module involved.
(pulse suppression via the safety shutdown path of the Motor Module). Re fault value = 1020:
- forced checking procedure of the safety shutdown path of the Motor - carry out a POWER ON (power off/on) for all components.
Module unsuccessful. - upgrade the Motor Module software.
- subsequent response to fault F30611 (defect in a monitoring channel). - replace the Motor Module.
Fault value (r0949, interpret decimal): Re fault value = 9999:
0: Stop request from the Control Unit. - carry out diagnostics for fault F30611.
1005: Pulses suppressed although STO not selected and there is no internal Note:
STOP A present. CU: Control Unit
1010: Pulses enabled although STO is selected or an internal STOP A is MM: Motor Module
present. SI: Safety Integrated
1020: Internal software error in the "Internal voltage protection" function. STO: Safe Torque Off / SH: Safe standstill
The "Internal voltage protection" function is
withdrawn. A STOP A that cannot be acknowledged is initiated.
9999: Subsequent response to fault F30611.

Sinamics G130 F30611 SI MM: Defect in a monitoring channel The drive-based "Safety Integrated" function in the Motor Module (MM) Re fault value = 1 to 5 and 7 to 999:
has detected a fault in the data cross-check - check the cross-checked data that resulted in a STOP F.
between the Control Unit (CU) and MM and initiated a STOP F. - carry out a POWER ON (power off/on) for all components.
As a result of this fault, after the parameterized transition has expired - upgrade the Motor Module software.
(p9858), fault F30600 is output (SI MM: STOP - upgrade the Control Unit software.
A initiated). Re fault value = 6:
Fault value (r0949, interpret decimal): - carry out a POWER ON (power off/on) for all components.
0: Stop request from the Control Unit. - upgrade the Motor Module software.
1 to 999: - upgrade the Control Unit software.
Number of the cross-checked data that resulted in this fault. This number is Re fault value = 1000:
also displayed in r9895. - check the wiring of the safety-relevant inputs (SGE) on the Control Unit
1: SI monitoring clock cycle (r9780, r9880). (contact problems).
2: SI enable safety functions (p9601, p9801). Crosswise data comparison is - PROFIsafe: rectify contact problems/faults on the PROFIBUS master/PROFINET
only carried out for the supported bits. controller. - check the wiring of
3: SI SGE changeover tolerance time (p9650, p9850). the fail-safe inputs on TM54F (contact problems).
4: SI transition period STOP F to STOP A (p9658, p9858).
5: SI enable Safe Brake Control (p9602, p9802).
6: SI Motion enable, safety-relevant functions (p9501, internal value).
7: SI pulse suppression delay time for Safe Stop 1 (p9652, p9852).
8: SI PROFIsafe address (p9610, p9810).
1000: Watchdog timer has expired. Within a period corresponding to
approximately 5 * p9850, too many switching
operations have occurred at the safety-relevant inputs of the Control Unit,
or STO (including subsequent responses)
has been triggered too frequently via PROFIsafe/TM54F.
1001, 1002: Initialization error, change timer / check timer.
2000: Status of the STO selection on the Control Unit and Motor Module
are different.
2001: Feedback signal for safe pulse suppression on the Control Unit and
Motor Module are different.
2002: Status of the delay timer SS1 on the Control Unit and Motor Module
are different.

Sinamics G130 F30625 SI MM: Sign-of-life error in safety data The drive-based "Safety Integrated" function on the Motor Module (MM) - select Safe Torque Off and de-select again.
has detected an error in the sign-of-life of - carry out a POWER ON (power off/on) for all components.
the safety data between the Control Unit (CU) and MM and initiated a - check whether there is a DRIVE-CLiQ communication error between the Control
STOP A. Unit and the Motor Module
- there is either a DRIVE-CLiQ communication error or communication has involved and, if required, carry out a diagnostics routine for the faults identified.
failed. - de-select all drive functions that are not absolutely necessary.
- a time slice overflow of the safety software has occurred. - reduce the number of drives.
Fault value (r0949, interpret decimal): - check the electrical cabinet design and cable routing for EMC compliance
Only for internal Siemens troubleshooting. Note:
CU: Control Unit
MM: Motor Module
SI: Safety Integrated
Sinamics G130 F30630 SI MM: Brake control error The drive-based "Safety Integrated" function on the Motor Module (MM) - check parameter p1278 (for SBC, only p1278 = 0 is permissible).
has detected a brake control error and initiated - select Safe Torque Off and de-select again.
a STOP A. - check the motor holding brake connection.
Fault value (r0949, interpret decimal): - check the function of the motor holding brake.
10: - check whether there is a DRIVE-CLiQ communication error between the Control
Fault in "open holding brake" operation. Unit and the Motor Module
- Parameter p1278 incorrectly set. involved and, if required, carry out a diagnostics routine for the faults identified.
- No brake connected or wire breakage (check whether brake releases for - check that the electrical cabinet design and cable routing are in compliance
p1278 = 1 and p9602/p9802 = 0 (SBC with EMC regulations (e.g. shield of the
deactivated)). motor cable and brake conductors are connected with the shield connecting
- Ground fault in brake cable. plate and the motor connectors are
30: tightly screwed to the housing).
Fault in "close holding brake" operation. - replace the Motor Module involved.
- No brake connected or wire breakage (check whether brake releases for Operation with Safe Brake Module:
p1278 = 1 and p9602/p9802 = 0 (SBC - check the Safe Brake Modules connection.
deactivated)). - replace the Safe Brake Module.
- Short-circuit in brake winding. Note:
40: MM: Motor Module
Fault in "brake closed" state. SBC: Safe Brake Control
60, 70: SI: Safety Integrated
Fault in the brake control circuit of the Control Unit or communication fault
between the Control Unit and Motor Module
(brake control).
Note:
The following causes may apply to fault values:
- motor cable is not shielded correctly.
- defect in control circuit of the Motor Module.

Sinamics G130 F30640 SI MM: Fault in the shutdown path of the The Motor Module has detected a communications error with the higher- For the higher-level control, the following applies:
second channel level control or the TM54F to transfer the - check the PROFIsafe address in the higher-level control and Motor Modules
safety-relevant information. and if required, align.
Note: - save all parameters (p0977 = 1).
This fault results in a STOP A that can be acknowledged. - carry out a POWER ON (power off/on) for all components.
Fault value (r0949, interpret decimal): For TM54F, carry out the following steps:
Only for internal Siemens troubleshooting. - start the copy function for the node identifier (p9700 = 1D hex).
- acknowledge hardware CRC (p9701 = EC hex).
- save all parameters (p0977 = 1).
- carry out a POWER ON (power off/on) for all components.
The following generally applies:
- upgrade the Motor Module software.
Note:
MM: Motor Module
SI: Safety Integrated
See also: p9810 (SI PROFIsafe address (Motor Module))

Sinamics G130 F30649 SI MM: Internal software error An internal error in the Safety Integrated software on the Motor Module - carry out a POWER ON (power off/on) for all components.
has occurred. - re-commission the Safety Integrated function and carry out a POWER ON.
Note: - upgrade the Motor Module software.
This fault results in a STOP A that cannot be acknowledged. - contact the Hotline.
Fault value (r0949, interpret hexadecimal): - replace the Motor Module.
Only for internal Siemens troubleshooting. Note:
MM: Motor Module
SI: Safety Integrated
Sinamics G130 F30650 SI MM: Acceptance test required The "Safety Integrated" function on the Motor Module requires an Re fault value = 130:
acceptance test. - carry out safety commissioning routine.
Note: Re fault value = 1000:
This fault results in a STOP A that can be acknowledged. - again carry out safety commissioning routine.
Fault value (r0949, interpret decimal): - replace the CompactFlash card.
130: Safety parameters for the Motor Module not available. Re fault value = 2000:
1000: Reference and actual checksum in the Motor Module are not - check the safety parameters in the Motor Module and adapt the reference
identical (booting). checksum (p9899).
- at least one checksum-checked piece of data is defective. Re fault value = 2003, 2005:
2000: Reference and actual checksum on the Motor Module are not - Carry out an acceptance test and generate an acceptance report.
identical (commissioning mode). The procedure when carrying out an acceptance test as well as an example of
- reference checksum incorrectly entered into the Motor Module (p9899 the acceptance report are provided
not equal to r9898). in the following literature:
2003: Acceptance test is required as a safety parameter has been changed. SINAMICS S120 Function Manual Safety Integrated
2005: The safety logbook has identified that the safety checksums have Re fault value = 3003:
changed. An acceptance test is required. - carry out the function checks for the modified hardware and generate an
3003: Acceptance test is required as a hardware-related safety parameter acceptance report.
has been changed. The procedure when carrying out an acceptance test as well as an example of
9999: Subsequent response of another safety-related fault that occurred the acceptance report are provided
when booting that requires an acceptance in the following literature:
test. SINAMICS S120 Function Manual Safety Integrated
Re fault value = 9999:
- carry out diagnostics for the other safety-related fault that is present.
Note:
MM: Motor Module
SI: Safety Integrated
See also: p9799 (SI reference checksum SI parameters (Control Unit)), p9899 (SI
reference checksum SI parameters
(Motor Module))

Sinamics G130 F30651 SI MM: Synchronization with Control Unit The drive-based "Safety Integrated" function is requesting synchronization - carry out a POWER ON (power off/on) for all components.
unsuccessful of the safety time slices on the Control - upgrade the Motor Module software.
Unit and Motor Module. This synchronization routine was unsuccessful. - upgrade the Control Unit software.
Note: Note:
This fault results in a STOP A that cannot be acknowledged. MM: Motor Module
Fault value (r0949, interpret decimal): SI: Safety Integrated
Only for internal Siemens troubleshooting.

Sinamics G130 F30652 SI MM: Illegal monitoring clock cycle The Safety Integrated monitoring clock cycle cannot be maintained due to Upgrade the Motor Module software.
the communication conditions requested Note:
in the system. MM: Motor Module
Note: SI: Safety Integrated
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.

Sinamics G130 F30655 SI MM: Align monitoring functions An error has occurred when aligning the Safety Integrated monitoring - carry out a POWER ON (power off/on) for all components.
functions on the Control Unit (CU) and Motor - upgrade the Motor Module software.
Module (MM). Control Unit and Motor Module were not able to determine - upgrade the Control Unit software.
a common set of supported SI monitoring - check the electrical cabinet design and cable routing for EMC compliance
functions. Note:
- there is either a DRIVE-CLiQ communication error or communication has CU: Control Unit
failed. MM: Motor Module
- Safety Integrated software releases on the Control Unit and Motor SI: Safety Integrated
Module are not compatible with one another.
Note:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.

Sinamics G130 F30656 SI MM: Motor Module parameter error When accessing the Safety Integrated parameters for the Motor Module - re-commission the safety functions.
(MM) on the CompactFlash card, an error - upgrade the Control Unit software.
has occurred. - upgrade the Motor Module software.
Note: - replace the CompactFlash card.
This fault results in a STOP A that can be acknowledged. Note:
Fault value (r0949, interpret decimal): MM: Motor Module
129: Safety parameters for the Motor Module corrupted. SI: Safety Integrated
131: Internal software error on the Control Unit.
255: Internal Motor Module software error.
Sinamics G130 F30659 SI MM: Write request for parameter rejected The write request for one or several Safety Integrated parameters on the Re fault value = 10, 11, 13, 14, 15, 16:
Motor Module (MM) was rejected. - check whether there are faults in the safety function alignment between the
Note: Control Unit and the Motor Module
This fault does not result in a safety stop response. involved (F01655, F30655) and if required, carry out diagnostics for the faults
Fault value (r0949, interpret decimal): involved.
10: An attempt was made to enable the STO function although this cannot - use a Motor Module that supports the required function ("Safe Torque Off",
be supported. "Safe Brake Control",
11: An attempt was made to enable the SBC function although this cannot "PROFIsafe/PROFIsafe V2", "motion monitoring functions integrated in the
be supported. drive").
13: An attempt was made to enable the SS1 function although this cannot - upgrade the Motor Module software.
be supported. - upgrade the Control Unit software.
14: An attempt was made to enable the safe motion monitoring function Note:
with the higher-level control, although this CU: Control Unit
cannot be supported. MM: Motor Module
15: An attempt was made to enable the motion monitoring functions SBC: Safe Brake Control
integrated in the drive although these cannot be SI: Safety Integrated
supported. SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)
16: An attempt was made to enable the PROFIsafe communication - STO: Safe Torque Off / SH: Safe standstill
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)

Sinamics G130 F30672 SI Motion: Control Unit software incompatible The existing Control Unit software does not support the safe drive-based - check whether there are faults in the safety function alignment between the
motion monitoring function. Control Unit and the Motor Module
Note: involved (F01655, F30655) and if required, carry out diagnostics for the faults
This fault results in a STOP A that cannot be acknowledged. involved.
Fault value (r0949, interpret decimal): - use a Control Unit that supports the safe motion monitoring function.
Only for internal Siemens troubleshooting. - upgrade the Control Unit software.
Note:
SI: Safety Integrated

Sinamics G130 F30680 SI Motion MM: Checksum error safety The actual checksum calculated by the Motor Module and entered in r9398 - Check the safety-relevant parameters and if required, correct.
monitoring functions over the safety-relevant parameters does - set the reference checksum to the actual checksum.
not match the reference checksum saved in p9399 at the last machine - carry out a POWER ON.
acceptance. - carry out an acceptance test.
Safety-relevant parameters have been changed or a fault is present. Note:
Note: SI: Safety Integrated
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.

Sinamics G130 F30682 SI Motion MM: Monitoring function not The monitoring function enabled in p9301, p9501, p9601 or p9801 is not - De-select the monitoring function involved (p9301, p9301, p9303, p9601,
supported supported in this firmware version. p9801).
Note: - Upgrade the Motor Module firmware.
This message does not result in a safety stop response. See also: p9301 (SI Motion enable safety functions (Motor Module)), p9501 (SI
Fault value (r0949, interpret decimal): Motion enable safety functions (Control
30: The firmware version of the Motor Module is older than the version of Unit)), p9503 (SI Motion SCA (SN) enable (Control Unit)), p9601 (SI enable,
the Control Unit. functions integrated in the drive
(Control Unit)), p9801 (SI enable, functions integrated in the drive (Motor
Module))

Sinamics G130 F30683 SI Motion MM: SOS/SLS enable missing The safety-relevant basic function "SOS/SLS" is not enabled in p9301 Enable the function "SOS/SLS" (p9301.0).
although other safety-relevant monitoring Note:
functions are enabled. SI: Safety Integrated
Note: SLS: Safely-Limited Speed / SG: Safely reduced speed
This message does not result in a safety stop response. SOS: Safe Operating Stop / SBH: Safe operating stop
See also: p9301 (SI Motion enable safety functions (Motor Module))

Sinamics G130 F30685 SI Motion MM: Safely-Limited Speed limit The limit value for the function "Safely-Limited Speed" (SLS) is greater than Correct the limit values for SLS and carry out a POWER ON.
value too high the speed that corresponds to an Note:
encoder limit frequency of 500 kHz. SI: Safety Integrated
Note: SLS: Safely-Limited Speed / SG: Safely reduced speed
This message does not result in a safety stop response. See also: p9331 (SI Motion SLS limit values (Motor Module))
Fault value (r0949, interpret decimal):
Maximum permissible speed.

Sinamics G130 F30688 SI Motion MM: Actual value synchronization It is not permissible to simultaneously enable the actual value Either de-select the function "actual value synchronization" or the monitoring
not permissible synchronization and a monitoring function with absolute functions with absolute reference
reference (SCA/SLP). (SCA/SLP) and carry out a POWER ON.
Note: Note:
This fault results in a STOP A that cannot be acknowledged. SCA: Safe Cam / SN: Safe software cam
SI: Safety Integrated
SLP: Safely-Limited Position / SE: Safe software limit switches
See also: p9501 (SI Motion enable safety functions (Control Unit))
Sinamics G130 F30801 Power unit DRIVE-CLiQ: Sign-of-life missing A DRIVE-CLiQ communication error has occurred form the Control Unit to - check the electrical cabinet design and cable routing for EMC compliance
the power unit involved. - remove DRIVE-CLiQ components that are not required.
The computing time load might be too high. - de-select functions that are not required.
Fault value (r0949, interpret hexadecimal): - if required, increase the sampling times (p0112, p0115).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 0A hex:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 F30802 Power unit: Time slice overflow Time slide overflow. - carry out a POWER ON (power off/on) for all components.
- upgrade firmware to later version.
- contact the Hotline.

Sinamics G130 F30805 Power unit: EPROM checksum error Internal parameter data is corrupted. Replace the module.
Fault value (r0949, interpret hexadecimal):
01: EEPROM access error.
02: Too many blocks in the EEPROM.

Sinamics G130 F30809 Power unit: Switching information not valid For 3P gating unit: - carry out a POWER ON (power off/on) for all components.
The last switching status word in the setpoint telegram is identified by the - upgrade firmware to later version.
end ID. Such an end ID was not found. - contact the Hotline.

Sinamics G130 F30820 Power unit DRIVE-CLiQ: Telegram error A DRIVE-CLiQ communication error has occurred form the Control Unit to - carry out a POWER ON.
the power unit involved. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.

Sinamics G130 F30835 Power unit DRIVE-CLiQ: Cyclic data transfer A DRIVE-CLiQ communication error has occurred form the Control Unit to - carry out a POWER ON.
error the power unit involved. The nodes do not - replace the component involved.
send and receive in synchronism. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.

Sinamics G130 F30836 Power unit DRIVE-CLiQ: Send error for DRIVE- A DRIVE-CLiQ communication error has occurred form the Control Unit to Carry out a POWER ON.
CLiQ data the power unit involved. Data were not
able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.
Sinamics G130 F30837 Power unit DRIVE-CLiQ: Component fault Fault detected on the DRIVE-CLiQ component involved. Faulty hardware - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.

Sinamics G130 F30845 Power unit DRIVE-CLiQ: Cyclic data transfer A DRIVE-CLiQ communication error has occurred form the Control Unit to Carry out a POWER ON.
error the power unit involved. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F30850 Power unit: Internal software error An internal software error in the power unit has occurred. - replace power unit.
Fault value (r0949, interpret decimal): - if required, upgrade the firmware in the power unit.
Only for internal Siemens troubleshooting. - contact the Hotline.

Sinamics G130 F30851 Power unit DRIVE-CLiQ (CU): Sign-of-life A DRIVE-CLiQ communication error has occurred from the power unit to Upgrade the firmware of the component involved.
missing the Control Unit involved.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex = 10 dec:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 F30860 Power unit DRIVE-CLiQ (CU): Telegram error A DRIVE-CLiQ communication error has occurred from the power unit to - carry out a POWER ON.
the Control Unit involved. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
xx = 11 hex = 17 dec:
CRC error and the receive telegram is too early.
xx = 01 hex = 01 dec:
Checksum error (CRC error).
xx = 12 hex = 18 dec:
The telegram is shorter than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 02 hex = 02 dec:
Telegram is shorter than specified in the length byte or in the receive list.
xx = 13 hex = 19 dec:
The telegram is longer than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 03 hex = 03 dec:
Telegram is longer than specified in the length byte or in the receive list.

Sinamics G130 F30885 CU DRIVE-CLiQ (CU): Cyclic data transfer error A DRIVE-CLiQ communication error has occurred from the power unit to - check the power supply voltage of the component involved.
the Control Unit involved. - carry out a POWER ON.
The nodes do not send and receive in synchronism. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
yyxx hex: yy = component number, xx = fault cause
xx = 1A hex = 26 dec:
Sign-of-life bit in the receive telegram not set and the receive telegram is
too early.
xx = 21 hex = 33 dec:
The cyclic telegram has not been received.
xx = 22 hex 34 dec:
Timeout in the telegram receive list.
xx = 40 hex = 64 dec:
Timeout in the telegram send list.
xx = 62 hex = 98 dec:
Error at the transition to cyclic operation.
Sinamics G130 F30866 PU DRIVE-CLiQ (CU): Error when sending A DRIVE-CLiQ communication error has occurred from the power unit to Carry out a POWER ON.
DRIVE-CLiQ data the Control Unit involved.
Data were not able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.

Sinamics G130 F30887 Power unit DRIVE-CLiQ (CU): Component fault Fault detected on the DRIVE-CLiQ component (power unit) involved. Faulty - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
hardware cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.
xx = 60 hex:
Response received too late during runtime measurement.
xx = 61 hex:
Time taken to exchange characteristic data too long.

Sinamics G130 F30895 PU DRIVE-CLiQ (CU): Alternating cyclic data A DRIVE-CLiQ communication error has occurred from the power unit to Carry out a POWER ON.
transfer error the Control Unit involved. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F30896 Power unit DRIVE-CLiQ (CU): Inconsistent The properties of the DRIVE-CLiQ component (power unit), specified by the - when replacing cables, only use cables with the same length as the original
component properties fault value, have changed in an incompatible cables.
fashion with respect to the properties when booted. One cause can be, e.g. - when replacing components, use the same components and firmware releases.
that a DRIVE-CLiQ cable or - carry out a POWER ON.
DRIVE-CLiQ component has been replaced.
Fault value (r0949, interpret decimal):
Component number.

Sinamics G130 F30899 (N,A) Power unit: Unknown fault A fault occurred on the power unit that cannot be interpreted by the - replace the firmware on the power unit by an older firmware version (r0128).
Control Unit firmware. - upgrade the firmware on the Control Unit (r0018).C456
This can occur if the firmware on this component is more recent than the
firmware on the Control Unit.
Fault value (r0949, interpret decimal):
Fault number.
Note:
If required, the significance of this new fault can be read about in a more
recent description of the Control Unit.

Sinamics G130 F30903 Power unit: I2C bus error occurred Communications error with an EEPROM or A/D converter. Re fault value = 80000000 hex:
Fault value (r0949, interpret hexadecimal): - upgrade firmware to later version.
80000000 hex: Re fault value = 00000001 hex ... 0000FFFF hex:
- internal software error. - replace the module.
00000001 hex ... 0000FFFF hex:
- module fault.

Sinamics G130 F30907 Power unit: FPGA configuration unsuccessful For the initialization within the power unit, an internal software error has - if required, upgrade the firmware in the power unit.
occurred. - replace power unit.
- contact the Hotline.

Sinamics G130 F31100 Encoder 1: Zero mark distance error The measured zero mark distance does not correspond to the - check that the encoder cables are routed in compliance with EMC.
parameterized zero mark distance. - check the plug connections.
For distance-coded encoders, the zero mark distance is determined from . check the encoder type (encoder with equidistant zero marks).
zero marks detected pairs. This means that - adapt the parameter for the distance between zero marks (p0424, p0425).
if a zero mark is missing, depending on the pair generation, this cannot - if message output above speed threshold, reduce filter time if necessary
result in a fault and also has no effect in the (p0438).
system. - replace the encoder or encoder cable.
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)
Sinamics G130 F31101 (N,A) Encoder 1: Zero marked failed The 1.5 x parameterized zero mark distance was exceeded. - check that the encoder cables are routed in compliance with EMC.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary - check the plug connections.
encoder) or p0424 (linear encoder). . check the encoder type (encoder with equidistant zero marks).
Fault value (r0949, interpret decimal): - adapt the parameter for the distance between zero marks (p0425).
Number of increments after POWER ON or since the last zero mark that - if message output above speed threshold, reduce filter time if necessary
was detected (4 increments = 1 encoder (p0438).
pulse). - when p0437.1 is active, check p4686.
See also: p0491 (Motor encoder fault response ENCODER) - replace the encoder or encoder cable.

Sinamics G130 F31103 (N,A) Encoder 1: Amplitude error, track R The amplitude of the reference track signal (track R) does not lie within the - check the speed range, frequency characteristic (amplitude characteristic) of
tolerance bandwidth for encoder 1. the measuring equipment may not be
The fault can be initiated when the unipolar voltage range is exceeded or sufficient for the speed range.
the differential amplitude is initiated. - check that the encoder cables and shielding are routed in compliance with
Fault value (r0949, interpret hexadecimal): EMC.
xxxx hex: - check the plug connections and contacts.
xxxx = Signal level, track R (16 bits with sign). - check whether the zero mark is connected and the signal cables RP and RN
The unipolar nominal signal level of the encoder must lie in the range 2500 connected correctly.
mV +/- 500 mV. - replace the encoder cable.
The response threshold is < 1700 mV and > 3300 mV. - if the coding disk is soiled or the lighting worn, replace the encoder.
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)

Sinamics G130 F31110 (N,A) Encoder 1: Serial communications error Serial communication protocol transfer error between the encoder and Re fault value, bit 0 = 1:
evaluation module. - encoder defective. F31111 may provide additional details.
Fault value (r0949, interpret binary): Re fault value, bit 1 = 1:
Bit 0: Alarm bit in the position protocol. - Incorrect encoder type / replace the encoder or encoder cable.
Bit 1: Incorrect quiescent level on the data line. Re fault value, bit 2 = 1:
Bit 2: Encoder does not respond (does not supply a start bit within 50 ms). - Incorrect encoder type / replace the encoder or encoder cable.
Bit 3: CRC error: The checksum in the protocol from the encoder does not Re fault value, bit 3 = 1:
match the data. - EMC / connect the cable shield, replace the encoder or encoder cable.
Bit 4: Encoder acknowledgement error: The encoder incorrectly Re fault value, bit 4 = 1:
understood the task (request) or cannot execute it. - EMC / connect the cable shield, replace the encoder or encoder cable, replace
Bit 5: Internal error in the serial driver: An illegal mode command was the Sensor Module.
requested. Re fault value, bit 5 = 1:
Bit 6: Timeout when cyclically - EMC / connect the cable shield, replace the encoder or encoder cable, replace
Bit 8: Protocol is too long (e. the Sensor Module.
Bit 9: Receive buffer overflow. Re fault value, bit 6 = 1:
Bit 10: Frame error when reading - Update the firmware for the Sensor Module.
Bit 11: Parity error. Re fault value, bit 8 = 1:
Bit 12: Data line signal level - Check the parameterization (p0429.2).
Bit 13: Data line incorrect. Re fault value, bit 9 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace
the Sensor Module.
Re fault value, bit 10 = 1:
- Check the parameterization (p0429.2, p0449).
Re fault value, bit 11 = 1:
- Check the parameterization (p0436).
Re fault value, bit 12 = 1:
- Check the parameterization (p0429.6).
Re fault value, bit 13 = 1:
- Check the data line.
Sinamics G130 F31111 (N,A) Encoder 1: Absolute encoder EnDat, internal The EnDat encoder fault word supplies fault bits that have been set. Re fault value, bit 0 = 1:
fault/error Fault value (r0949, interpret binary): Encoder is defective. Replace the encoder, where the motor encoder has a direct
Bit 0: Lighting system failed. DRIVE-CLiQ socket: Replace the
Bit 1: Signal amplitude too low. motor.
Bit 2: Position value incorrect. Re fault value, bit 1 = 1:
Bit 3: Encoder power supply overvoltage condition. Encoder is defective. Replace the encoder, where the motor encoder has a direct
Bit 4: Encoder power supply undervoltage condition. DRIVE-CLiQ socket: Replace the
Bit 5: Encoder power supply overcurrent condition. motor.
Bit 6: The battery must be changed. Re fault value, bit 2 = 1:
See also: p0491 (Motor encoder fault response ENCODER) Encoder is defective. Replace the encoder, where the motor encoder has a direct
DRIVE-CLiQ socket: Replace the
motor.
Re fault value, bit 3 = 1:
5 V power supply voltage fault.
When using an SMC: Check the plug-in cable between the encoder and SMC or
replace the SMC.
When a motor encoder with a direct DRIVE-CLiQ connection is used: Replace the
motor.
Re fault value, bit 4 = 1:
5 V power supply voltage fault.
When using an SMC: Check the plug-in cable between the encoder and SMC or
replace the SMC.
When using a motor with DRIVE-CLiQ: Replace the motor.
Re fault value, bit 5 = 1:
Encoder is defective. Replace the encoder, where the motor encoder has a direct
DRIVE-CLiQ socket: Replace the
motor.
Re fault value, bit 6 = 1:
The battery must be changed (only for encoders with battery back-up).

Sinamics G130 F31112 (N,A) Encoder 1: Error bit set in the serial protocol The encoder sends a set error bit via the serial protocol. For fault value, bit 0 = 1:
Fault value (r0949, interpret binary): In the case of an EnDat encoder, F31111 may provide further details.
Bit 0: Fault bit in the position protocol.

Sinamics G130 F31115 (N,A) Encoder 1: Amplitude error track A/B fault The amplitude (root of A^2 + B^2) for encoder 1 exceeds the permissible - check that the encoder cables and shielding are routed in compliance with
(A^2 + B^2) tolerance. EMC.
Fault value (r0949, interpret hexadecimal): - check the plug connections.
yyyyxxxx hex: - replace the encoder or encoder cable.
yyyy = Signal level, track B (16 bits with sign). - check the Sensor Module (e.g. contacts).
xxxx = Signal level, track A (16 bits with sign). - with measuring systems without their own bearing system: Adjust the scanning
The nominal signal level of the encoder must lie in the range 375 mV to 600 head and check the bearing system
mV (500 mV -25/+20 %). of the measuring wheel.
The response thresholds are < 230 mV (observe the frequency response of - for measuring systems with their own bearing system: Ensure that the encoder
the encoder) and > 750 mV. housing is not subject to any axial
A signal level of 500 mV peak value corresponds to the numerical value of force.
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)

Sinamics G130 F31116 (N,A) Encoder 1: Amplitude error track A + B The amplitude of the rectified encoder signals A and B and the amplitude - check that the encoder cables and shielding are routed in compliance with
from the roots of A^2 + B^2 for encoder 1 EMC.
are not within the tolerance bandwidth. - check the plug connections.
Fault value (r0949, interpret hexadecimal): - replace the encoder or encoder cable.
yyyyxxxx hex: - check the Sensor Module (e.g. contacts).
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)
Sinamics G130 F31117 (N,A) Encoder 1: Inversion error signals A and B and For a square-wave signal encoder (TTL. bipolar. double ended) the A* and - check the setting of p0405: p0405.2 = 1 is only possible if the encoder is
R B* and R* signals are not inverted with connected at X520.
respect to signals A and B and R. - check the encoder/cable: Does the encoder supply TTL signals and the
Note: associated inverted signals?
For CU310, CUA32, D410, SMC30 (only Order No. 6SL3055-0AA00-5CA0 Note:
and 6SL3055-0AA00-5CA1), the following For a squarewave encoder without track R, the following jumpers must be set at
applies: the encoder connection:
A squarewave encoder without track R is used and the track monitoring - pin 10 (reference signal R) <--> pin 7 (encoder power supply, ground)
(p0405.2 = 1) is activated. - pin 11 (reference signal R inverted) <--> pin 4 (encoder power supply)
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31118 (N,A) Encoder 1: Speed difference outside the For an HTL/TTL encoder, the speed difference has exceeded the value in - check the tachometer feeder cable for interruptions.
tolerance range p0492 over several sampling cycles. - check the grounding of the tachometer shielding.
The change to the averaged speed actual value - if applicable - is monitored - if required, increase the maximum speed difference per sampling cycle (p0492).
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)

Sinamics G130 F31120 (N,A) Encoder 1: Power supply voltage fault Encoder 1 power supply voltage fault. For fault value, bit 0 = 1:
Note: - correct encoder cable connected?
If the encoder cables 6FX2002-2EQ00-.... and 6FX2002-2CH00-.... are - check the plug connections of the encoder cable.
interchanged, this can result in the encoder - SMC30: Check the parameterization (p0404.22).
being destroyed because the pins of the operating voltage are reversed. For fault value, bit 1 = 1:
Fault value (r0949, interpret binary): - correct encoder cable connected?
Bit 0: Undervoltage condition on the sense line. - replace the encoder or encoder cable.
Bit 1: Overcurrent condition for the encoder power supply.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31121 (N, A) Encoder 1: Coarse position error For the actual value sensing, an error was detected on the module. As a Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module.
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)

Sinamics G130 F31122 Encoder 1: Internal power supply voltage fault Fault in internal reference voltage of ASICs for encoder 1. Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module.
Fault value (r0949, interpret decimal):
1: Reference voltage error.
2: Internal undervoltage.
3: Internal overvoltage.

Sinamics G130 F31123 (N, A) Encoder 1: Signal level A/B unipolar outside The unipolar level (AP/AN or BP/BN) for encoder 1 is outside the - make sure that the encoder cables and shielding are installed in an EMC-
tolerance permissible tolerance. compliant manner.
Fault value (r0949, interpret binary): - check the plug connections and contacts.
Bit 0 = 1: Either AP or AN outside the tolerance. - check the short-circuit of a signal cable with mass or the operating voltage.
Bit 16 = 1: Either BP or BN outside the tolerance. - replace the encoder cable.A472
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).
See also: p0491 (Motor encoder fault response ENCODER)
Sinamics G130 F31125 (N, A) Encoder 1: Amplitude error track A/B The amplitude of track A or B for encoder 1 exceeds the permissble - check that the encoder cables and shielding are routed in compliance with
overcontrolled tolerance band. EMC.
Fault value (r0949, interpret hexadecimal): - replace the encoder or encoder cable.
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 threshold is > 750 mV. This fault also occurs if the A/D
converter is overcontrolled.
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 threshold
is > 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)

Sinamics G130 F31126 (N, A) Encoder 1: Amplitude AB too high The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 1 exceeds the - check that the encoder cables and shielding are routed in compliance with
permissible tolerance. EMC.
Fault value (r0949, interpret hexadecimal): - replace the encoder or encoder cable.
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.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31129 (N, A) Encoder 1: Position difference, hall The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° - track C or D not connected.
sensor/track C/D and A/B too large electrical or the error for the Hall signals is greater - correct the direction of rotation of the Hall sensor possibly connected as
than +/-60 ° electrical. equivalent for track C/D.
One period of track C/D corresponds to 360 ° mechanical. - check that the encoder cables are routed in compliance with EMC.
One period of the Hall signal corresponds to 360 ° electrical. - check the adjustment of the Hall sensor.
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)
Sinamics G130 F31130 (N, A) Encoder 1: Zero mark and position error from After initializing the pole position using track C/D, Hall signals or pole - Check and, if necessary, correct p0431 (trigger via p1990 = 1 if necessary).
the coarse synchronization position identification routine, the zero mark - check that the encoder cables are routed in compliance with EMC.
was detected outside the permissible range. For distance-coded encoders, - check the plug connections.
the test is carried out after passing 2 zero - if the Hall sensor is used as an equivalent for track C/D, check the connection.
marks. Fine synchronization was not carried out. - Check connection of track C or D.
When initializing via track C/D (p0404) then it is checked whether the zero - replace the encoder or encoder cable.
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)

Sinamics G130 F31131 (N, A) Encoder 1: Deviation, position Absolute encoder: - check that the encoder cables are routed in compliance with EMC.
incremental/absolute too large When cyclically reading the absolute position, an excessively high - check the plug connections.
difference to the incremental position was - replace the encoder or encoder cable.
detected. The absolute position that was read is rejected. - check whether the coding disk is dirty or there are strong ambient magnetic
Limit value for the deviation: fields.
- EnDat encoder: Is supplied from the encoder and is a minimum of 2 - adapt the parameter for the distance between zero marks (p0425).
quadrants (e.g. EQI 1325 > 2 quadrants, EQN - if message output above speed threshold, reduce filter time if necessary
1325 > 50 quadrants). (p0438).
- 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)

Sinamics G130 F31135 Encoder 1: Fault when determining the The DRIVE-CLiQ encoder supplies status information via bits in an internal Replace DRIVE-CLiQ encoder.
position 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)
Sinamics G130 F31136 Encoder 1: Error when determining multiturn The DRIVE-CLiQ encoder supplies status information via bits in an internal Replace DRIVE-CLiQ encoder.
information 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)

Sinamics G130 F31137 Encoder 1: Internal error when determining The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Replace encoder
the position Fault value (r0949, interpret binary):
Only for internal SIEMENS use.

Sinamics G130 F31138 Encoder 1: Internal error when determining The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Replace encoder
multiturn information Fault value (r0949, interpret binary):
Only for internal SIEMENS use.

Sinamics G130 F31150 (N,A) Encoder 1: Initialization error Encoder functionality selected in p0404 is not operating correctly. - Check that p0404 is correctly set.
Fault value (r0949, interpret hexadecimal): - check the encoder type used (incremental/absolute value) and for SMCxx, the
The fault value is a bit field. Every set bit indicates functionality that is encoder cable.
faulted. - if relevant, note additional fault/error messages that describe the fault in
The bit assignment corresponds to that of p0404 (e.g. bit 5 set: Error track detail.
C/D).
See also: p0404 (Encoder configuration effective), p0491 (Motor encoder
fault response ENCODER)

Sinamics G130 F31151 (N,A) Encoder 1: Encoder speed for initialization AB The encoder speed is too high during while initializing the sensor. Reduce the speed of the encoder accordingly during initialization.
too high If necessary, deactivate monitoring (p0437.29).
See also: p0437 (Sensor Module configuration extended)

Sinamics G130 F31405 Encoder 1: Temperature in the encoder The encoder evaluation for a motor with DRIVE-CLiQ has detected an Reduce the ambient temperature for the DRIVE-CLiQ connection of the motor.
evaluation inadmissible inadmissible temperature.
The fault threshold is 125 ° C.
Alarm value (r2124, interpret decimal):
Measured board/module temperature in 0.1 °C.

Sinamics G130 F31500 (N,A) Encoder 1: Position tracking traversing range For a configured linear axis without modulo correction, the drive/encoder The fault should be resolved as follows:
exceeded has exceeded the maximum possible traversing - select encoder commissioning (p0010 = 4).
range. The value should be read in p0412 and interpreted as the number of - reset the position tracking as follows (p0411.2 = 1).
motor revolutions. - de-select encoder commissioning (p0010 = 0).
When p0411.0 = 1, the maximum traversing range for a configured linear The fault should then be acknowledged and the absolute encoder adjusted.
axis is defined to be 64x (+/- 32x) the setting
in p0421.
When p0411.3 = 1, the maximum traversing range for a configured linear
axis is preset to the highest possible value
and equals +/-p0412/2 (rounded to whole rotations). The highest possible
value depends on the pulse number
(p0408) and fine resolution (p0419).
Sinamics G130 F31501 (N,A) Encoder 1: Position tracking encoder position When powered down, the drive/encoder was moved through a distance Reset the position tracking as follows:
outside tolerance window greater than was parameterized in the tolerance - select encoder commissioning (p0010 = 4).
window. It is possible that there is no longer any reference between the - reset the position tracking as follows (p0411.2 = 1).
mechanical system and encoder. - de-select encoder commissioning (p0010 = 0).
Fault value (r0949, decimal): The fault should then be acknowledged and, if necessary, the absolute encoder
Deviation (difference) to the last encoder position in increments of the adjusted (p2507).
absolute value. See also: p0010
The sign designates the traversing direction.
Note:
The deviation (difference) found is also displayed in r0477.
See also: p0413 (Measuring gear, position tracking tolerance window),
r0477 (Measuring gear, position difference)

Sinamics G130 F31502 (N,A) Encoder 1: Encoder with measuring gear, The encoder with measuring gear no longer provides any valid signals. It must be ensured that all of the encoders, with mounted measuring gear,
without valid signals provide valid actual values in operation.
Sinamics G130 F31503 (N,A) Encoder 1: Position tracking cannot be reset The position tracking for the measuring gear cannot be reset. The fault should be resolved as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- de-select encoder commissioning (p0010 = 0).
The fault should then be acknowledged and the absolute encoder adjusted.

Sinamics G130 F31801 (N,A) Encoder 1 DRIVE-CLiQ: Sign-of-life missing A DRIVE-CLiQ communication error has occurred from the Control Unit to - check the electrical cabinet design and cable routing for EMC compliance
the encoder involved. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex:
The sign-of-life bit in the receive telegram is not set.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31802 (N,A) Encoder 1: Time slice overflow Time slice overflow, encoder 1. Reduce the current controller frequency.
Fault value (r0949, interpret decimal):
9: Time slice overflow of the fast (current controller clock cycle) time slice.
10: Time slice overflow of the average time slice.
12: Time slice overflow of the slow time slice.
999: Timeout when waiting for SYNO, e.g. unexpected return to non-cyclic
operation.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31804 (N,A) Encoder 1: Checksum error A checksum error has occurred when reading-out the program memory on - check whether the permissible ambient temperature for the component is
the Sensor Module. maintained.
Fault value (r0949, interpret hexadecimal): - replace the Sensor Module.
yyyyxxxx hex
yyyy: Memory area involved.
xxxx: Difference between the checksum at POWER ON and the current
checksum.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31805 (N,A) Encoder 1: EPROM checksum error Internal parameter data is corrupted. Replace the module.
Fault value (r0949, interpret hexadecimal):
01: EEPROM access error.
02: Too many blocks in the EEPROM.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31806 (N,A) Encoder 1: Initialization error The encoder was not successfully initialized. Acknowledge the fault.
Fault value (r0949, interpret hexadecimal):
1, 2, 3: Encoder initialization with the motor rotating.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31812 (N,A) Encoder 1: Requested cycle or RX-/TX timing A cycle requested from the Control Unit or RX/TX timing is not supported.
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.

Sinamics G130 F31813 Encoder 1: Hardware logic unit failed The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Replace encoder
Fault value (r0949, interpret binary):
Bit 0: ALU watchdog has responded.
Bit 1: ALU has detected a sign-of-life error.
Sinamics G130 F31820 (N,A)) Encoder 1 DRIVE-CLiQ: Telegram error A DRIVE-CLiQ communication error has occurred from the Control Unit to - carry out a POWER ON.
the encoder involved. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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)

Sinamics G130 F31835 (N,A) Encoder 1 DRIVE-CLiQ: Cyclic data transfer A DRIVE-CLiQ communication error has occurred from the Control Unit to - carry out a POWER ON.
error the encoder involved. The nodes do not - replace the component involved.
send and receive in synchronism. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31836 (N,A) Encoder 1 DRIVE-CLiQ: Send error for DRIVE- A DRIVE-CLiQ communication error has occurred from the Control Unit to Carry out a POWER ON.
CLiQ data the encoder involved. Data were not able
to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31837 (N,A) Encoder 1 DRIVE-CLiQ: Component fault Fault detected on the DRIVE-CLiQ component involved. Faulty hardware - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31845 (N,A) Encoder 1 DRIVE-CLiQ: Cyclic data transfer A DRIVE-CLiQ communication error has occurred from the Control Unit to Carry out a POWER ON.
error the encoder involved. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.
See also: p0491 (Motor encoder fault response ENCODER)
Sinamics G130 F31850 N,A) Encoder 1: Encoder evaluation, internal Internal software error in the Sensor Module of encoder 1.
software error Fault value (r0949, interpret decimal):
1: Background time slice is blocked.
2: Checksum over the code memory is not OK.
10000: OEM memory of the EnDat encoder contains data that cannot be
interpreted.
11000 - 11499: Descriptive data from EEPROM incorrect.
11500 - 11899: Calibration data from EEPROM incorrect.
11900 - 11999: Configuration data from EEPROM incorrect.
16000: DRIVE-CLiQ encoder initialization application error.
16001: DRIVE-CLiQ encoder initialization ALU error.
16002: DRIVE-CLiQ encoder HISI / SISI initialization error.
16003: DRIVE-CLiQ encoder safety initialization error.
16004: DRIVE-CLiQ encoder internal system error.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31851 (N,A) Encoder 1 DRIVE-CLiQ (CU): Sign-of-life missing A DRIVE-CLiQ communication error has occurred from the Sensor Module Upgrade the firmware of the component involved.
(encoder 1) involved to the Control Unit.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex = 10 dec:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 F31860 Encoder 1 DRIVE-CLiQ (CU): Telegram error A DRIVE-CLiQ communication error has occurred from the Sensor Module - carry out a POWER ON.
(encoder 1) involved to the Control Unit. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
xx = 11 hex 17 dec:
CRC error and the receive telegram is too early.
xx = 01 hex = 01 dec:
Checksum error (CRC error).
xx = 12 hex = 18 dec:
The telegram is shorter than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 02 hex = 02 dec:
Telegram is shorter than specified in the length byte or in the receive list.
xx = 13 hex = 19 dec:
The telegram is longer than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 03 hex = 03 dec:
Telegram is longer than specified in the length byte or in the receive list.
xx = 14 hex = 20 dec:
The length of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 04 hex = 04 dec:
The length of the receive telegram does not match the receive list.
xx = 15 hex = 21 dec:
The type of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 05 hex = 05 dec:
The type of the receive telegram does not match the receive list.

Sinamics G130 F31885 (N,A) Encoder 1 DRIVE-CLiQ (CU): Cyclic data transfer A DRIVE-CLiQ communication error has occurred from the Sensor Module - check the power supply voltage of the component involved.
error (encoder 1) involved to the Control Unit. - carry out a POWER ON.
The nodes do not send and receive in synchronism. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
yyxx hex: yy = component number, xx = fault cause
xx = 1A hex = 26 dec:
Sign-of-life bit in the receive telegram not set and the receive telegram is
too early.
xx = 21 hex = 33 dec:
The cyclic telegram has not been received.
xx = 22 hex = 34 dec:
Timeout in the telegram receive list.
xx = 40 hex = 64 dec:
Timeout in the telegram send list.
xx = 62 hex = 98 dec:
Error at the transition to cyclic operation.
Sinamics G130 F31886 (N,A Encoder 1 DRIVE-CLiQ (CU): Error when A DRIVE-CLiQ communication error has occurred from the Sensor Module - carry out a POWER ON.
sending DRIVE-CLiQ data (encoder 1) involved to the Control Unit. - check whether the firmware version of the encoder (r0148) matches the
Data were not able to be sent. firmware version of Control Unit (r0018).
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.

Sinamics G130 F31887 (N, A) Encoder 1 DRIVE-CLiQ (CU): Component fault Fault detected on the DRIVE-CLiQ component involved (Sensor Module for - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
encoder 1). Faulty hardware cannot be - check the electrical cabinet design and cable routing for EMC compliance
excluded. - if required, use another DRIVE-CLiQ socket (p9904).
Fault value (r0949, interpret hexadecimal): - replace the component involved.
yyxx hex: yy = component number, xx = fault cause
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.
xx = 60 hex:
Response received too late during runtime measurement.
xx = 61 hex:
Time taken to exchange characteristic data too long.

Sinamics G130 F31895 (N, A) Encoder 1 DRIVE-CLiQ (CU): Alternating cyclic A DRIVE-CLiQ communication error has occurred from the Sensor Module Carry out a POWER ON.
data transfer error (encoder 1) involved to the Control Unit. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F31896 (N, A) Encoder 1 DRIVE-CLiQ (CU): Inconsistent The properties of the DRIVE-CLiQ component (Sensor Module for encoder - when replacing cables, only use cables with the same length as the original
component properties 1), specified by the fault value, have cables.
changed in an incompatible fashion with respect to the properties when - when replacing components, use the same components and firmware releases.
booted. One cause can be, e.g. that a - carry out a POWER ON.
DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced.
Fault value (r0949, interpret decimal):
Component number.

Sinamics G130 F31899 (N, A) Encoder 1: Unknown fault A fault occurred on the Sensor Module for encoder 1 that cannot be - replace the firmware on the Sensor Module by an older firmware version
interpreted by the Control Unit firmware. (r0148).
This can occur if the firmware on this component is more recent than the - upgrade the firmware on the Control Unit (r0018).
firmware on the Control Unit.
Fault value (r0949, interpret decimal):
Fault number.
Note:
If required, the significance of this new fault can be read about in a more
recent description of the Control Unit.
See also: p0491 (Motor encoder fault response ENCODER)
Sinamics G130 F31905 (N, A) Encoder 1: Parameterization error A parameter of encoder 1 was detected as being incorrect. - check whether the connected encoder type matches the encoder that has been
It is possible that the parameterized encoder type does not match the parameterized.
connected encoder. - correct the parameter specified by the fault value (r0949) and p0187.
The parameter involved can be determined as follows: - re parameter number 314: Check the pole pair number and measuring gear
- determine the parameter number using the fault value (r0949). ratio. The quotient of the "pole pair
- determine the parameter index (p0187). number" divided by the "measuring gear ratio" must be less than or equal to
Fault value (r0949, interpret decimal): 1000 ((r0313 * p0433) / p0432 <= 1000).
yyyyxxxx dec: yyyy = supplementary information, xxxx = parameter
Supplementary information = 0:
No information available.
Supplementary information = 1:
The component does not support HTL level (p0405.1 = 0) combined with
track monitoring A/B <> -A/B (p0405.2 = 1).
Supplementary information = 2:
A code number for an identified encoder has been entered into p0400,
however, no identification was carried out.
Please start a new encoder identification.
Supplementary information = 3:
A code number for an identified encoder has been entered into p0400,
however, no identification was carried out.
Please select a listed encoder in p0400 with a code number < 10000.
Supplementary information = 4:
This component does not support SSI encoders (p0404.9 = 1) without track
A/B.
Supplementary information = 5:
For the SQW encoder, the value in p4686 is greater than that in p0425.
Supplementary information = 6:
The DRIVE-CLiQ encoder cannot be used with this firmware version.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F31916 (N, A) Encoder 1: Parameterization error A parameter of encoder 1 was detected as being incorrect. - check whether the connected encoder type matches the encoder that has been
It is possible that the parameterized encoder type does not match the parameterized.
connected encoder. - correct the parameter specified by the fault value (r0949) and p0187.
The parameter involved can be determined as follows:
- determine the parameter number using the fault value (r0949).
- determine the parameter index (p0187).
Fault value (r0949, interpret decimal):
Parameter number
The fault is only output for encoders with r404[0].10 = 1. This corresponds
to A31905 for encoders with r404[0].10 =
0.
See also: p0491 (Motor encoder fault response ENCODER)

Sinamics G130 F32100 (N, A) Encoder 2: Zero mark distance error The measured zero mark distance does not correspond to the - check that the encoder cables are routed in compliance with EMC.
parameterized zero mark distance. - check the plug connections.
For distance-coded encoders, the zero mark distance is determined from . check the encoder type (encoder with equidistant zero marks).
zero marks detected pairs. This means that - adapt the parameter for the distance between zero marks (p0424, p0425).
if a zero mark is missing, depending on the pair generation, this cannot - if message output above speed threshold, reduce filter time if necessary
result in a fault and also has no effect in the (p0438).
system. - replace the encoder or encoder cable.
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.

Sinamics G130 F32101 (N, A) Encoder 2: Zero marked failed The 1.5 x parameterized zero mark distance was exceeded. - check that the encoder cables are routed in compliance with EMC.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary - check the plug connections.
encoder) or p0424 (linear encoder). . check the encoder type (encoder with equidistant zero marks).
Fault value (r0949, interpret decimal): - adapt the parameter for the distance between zero marks (p0425).
Number of increments after POWER ON or since the last zero mark that - if message output above speed threshold, reduce filter time if necessary
was detected (4 increments = 1 encoder (p0438).
pulse). - when p0437.1 is active, check p4686.
- replace the encoder or encoder cable.
Sinamics G130 F32103 (N, A) Encoder 2: Amplitude error, track R The amplitude of the reference track signal (track R) does not lie within the - check the speed range, frequency characteristic (amplitude characteristic) of
tolerance bandwidth for encoder 2. the measuring equipment may not be
The fault can be initiated when the unipolar voltage range is exceeded or sufficient for the speed range.
the differential amplitude is initiated. - check that the encoder cables and shielding are routed in compliance with
Fault value (r0949, interpret hexadecimal): EMC.
xxxx hex: - check the plug connections and contacts.
xxxx = Signal level, track R (16 bits with sign). - check whether the zero mark is connected and the signal cables RP and RN
The unipolar nominal signal level of the encoder must lie in the range 2500 connected correctly.
mV +/- 500 mV. - replace the encoder cable.
The response threshold is < 1700 mV and > 3300 mV. - if the coding disk is soiled or the lighting worn, replace the encoder.
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).

Sinamics G130 F32110 (N,A) Encoder 2: Serial communications error vSerial communication protocol transfer error between the encoder and Re fault value, bit 0 = 1:
evaluation module. - encoder defective. F31111 may provide additional details.
Fault value (r0949, interpret binary): Re fault value, bit 1 = 1:
Bit 0: Alarm bit in the position protocol. - Incorrect encoder type / replace the encoder or encoder cable.
Bit 1: Incorrect quiescent level on the data line. Re fault value, bit 2 = 1:
Bit 2: Encoder does not respond (does not supply a start bit within 50 ms). - Incorrect encoder type / replace the encoder or encoder cable.
Bit 3: CRC error: The checksum in the protocol from the encoder does not Re fault value, bit 3 = 1:
match the data. - EMC / connect the cable shield, replace the encoder or encoder cable.
Bit 4: Encoder acknowledgement error: The encoder incorrectly Re fault value, bit 4 = 1:
understood the task (request) or cannot execute it. - EMC / connect the cable shield, replace the encoder or encoder cable, replace
Bit 5: Internal error in the serial driver: An illegal mode command was the Sensor Module.
requested. Re fault value, bit 5 = 1:
Bit 6: Timeout when cyclically reading. - EMC / connect the cable shield, replace the encoder or encoder cable, replace
Bit 8: Protocol is too long (e.g. > 64 bits). the Sensor Module.
Bit 9: Receive buffer overflow. Re fault value, bit 6 = 1:
Bit 10: Frame error when reading twice. - Update the firmware for the Sensor Module.
Bit 11: Parity error. Re fault value, bit 8 = 1:
Bit 12: Data line signal level error during the monoflop time. - Check the parameterization (p0429.2).
Bit 13: Data line incorrect. Re fault value, bit 9 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace
the Sensor Module.
Re fault value, bit 10 = 1:
- Check the parameterization (p0429.2, p0449).
Re fault value, bit 11 = 1:
- Check the parameterization (p0436).
Re fault value, bit 12 = 1:
- Check the parameterization (p0429.6).
Re fault value, bit 13 = 1:
- Check the data line.
Sinamics G130 F32111 (N, A) Encoder 2: Absolute encoder EnDat, internal The EnDat encoder fault word supplies fault bits that have been set. Re fault value, bit 0 = 1:
fault/error Fault value (r0949, interpret binary): Encoder is defective. Replace the encoder, where the motor encoder has a direct
Bit 0: Lighting system failed. DRIVE-CLiQ socket: Replace the
Bit 1: Signal amplitude too low. motor.
Bit 2: Position value incorrect. Re fault value, bit 1 = 1:
Bit 3: Encoder power supply overvoltage condition. Encoder is defective. Replace the encoder, where the motor encoder has a direct
Bit 4: Encoder power supply undervoltage condition. DRIVE-CLiQ socket: Replace the
Bit 5: Encoder power supply overcurrent condition. motor.
Bit 6: The battery must be changed. Re fault value, bit 2 = 1:
Encoder is defective. Replace the encoder, where the motor encoder has a direct
DRIVE-CLiQ socket: Replace the
motor.
Re fault value, bit 3 = 1:
5 V power supply voltage fault.
When using an SMC: Check the plug-in cable between the encoder and SMC or
replace the SMC.
When a motor encoder with a direct DRIVE-CLiQ connection is used: Replace the
motor.
Re fault value, bit 4 = 1:
5 V power supply voltage fault.
When using an SMC: Check the plug-in cable between the encoder and SMC or
replace the SMC.
When using a motor with DRIVE-CLiQ: Replace the motor.
Re fault value, bit 5 = 1:
Encoder is defective. Replace the encoder, where the motor encoder has a direct
DRIVE-CLiQ socket: Replace the
motor.
Re fault value, bit 6 = 1:
The battery must be changed (only for encoders with battery back-up).

Sinamics G130 F32112 (N, A) Encoder 2: Error bit set in the serial protocol The encoder sends a set error bit via the serial protocol. For fault value, bit 0 = 1:
Fault value (r0949, interpret binary): In the case of an EnDat encoder, F31111 may provide further details.
Bit 0: Fault bit in the position protocol.

Sinamics G130 F32115 (N, A) Encoder 2: Amplitude error track A/B fault The amplitude (root of A^2 + B^2) for encoder 2 exceeds the permissible - check that the encoder cables and shielding are routed in compliance with
(A^2 + B^2) tolerance. EMC.
Fault value (r0949, interpret hexadecimal): - check the plug connections.
yyyyxxxx hex: - replace the encoder or encoder cable.
yyyy = Signal level, track B (16 bits with sign). - check the Sensor Module (e.g. contacts).
xxxx = Signal level, track A (16 bits with sign). - with measuring systems without their own bearing system: Adjust the scanning
The nominal signal level of the encoder must lie in the range 375 mV to 600 head and check the bearing system
mV (500 mV -25/+20 %). of the measuring wheel.
The response thresholds are < 230 mV (observe the frequency response of - for measuring systems with their own bearing system: Ensure that the encoder
the encoder) and > 750 mV. housing is not subject to any axial
A signal level of 500 mV peak value corresponds to the numerical value of force.
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.

Sinamics G130 F32116 (N, A) Encoder 2: Amplitude error track A + B The amplitude of the rectified encoder signals A and B and the amplitude - check that the encoder cables and shielding are routed in compliance with
from the roots of A^2 + B^2 for encoder 2 EMC.
are not within the tolerance bandwidth. - check the plug connections.
Fault value (r0949, interpret hexadecimal): - replace the encoder or encoder cable.
yyyyxxxx hex: - check the Sensor Module (e.g. contacts).
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.
Sinamics G130 F32117 (N, A) Encoder 2: Inversion error signals A and B and For a square-wave signal encoder (TTL. bipolar. double ended) the A* and - check the setting of p0405: p0405.2 = 1 is only possible if the encoder is
R B* and R* signals are not inverted with connected at X520.
respect to signals A and B and R. - check the encoder/cable: Does the encoder supply TTL signals and the
Note: associated inverted signals?
For CU310, CUA32, D410, SMC30 (only Order No. 6SL3055-0AA00-5CA0 Note:
and 6SL3055-0AA00-5CA1), the following For a squarewave encoder without track R, the following jumpers must be set at
applies: the encoder connection:
A squarewave encoder without track R is used and the track monitoring - pin 10 (reference signal R) <--> pin 7 (encoder power supply, ground)
(p0405.2 = 1) is activated. - pin 11 (reference signal R inverted) <--> pin 4 (encoder power supply)

Sinamics G130 F32118 (N, A) Encoder 2: Speed difference outside the For an HTL/TTL encoder, the speed difference has exceeded the value in - check the tachometer feeder cable for interruptions.
tolerance range p0492 over several sampling cycles. - check the grounding of the tachometer shielding.
The change to the averaged speed actual value - if applicable - is monitored - if required, increase the maximum speed difference per sampling cycle (p0492).
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)

Sinamics G130 F32120 (N,A) Encoder 2: Power supply voltage fault Encoder 2 power supply voltage fault. For fault value, bit 0 = 1:
Note: - correct encoder cable connected?
If the encoder cables 6FX2002-2EQ00-.... and 6FX2002-2CH00-.... are - check the plug connections of the encoder cable.
interchanged, this can result in the encoder - SMC30: Check the parameterization (p0404.22).
being destroyed because the pins of the operating voltage are reversed. For fault value, bit 1 = 1:
Fault value (r0949, interpret binary): - correct encoder cable connected?
Bit 0: Undervoltage condition on the sense line. - replace the encoder or encoder cable.
Bit 1: Overcurrent condition for the encoder power supply.

Sinamics G130 F32121 (N,A) Encoder 2: Coarse position error For the actual value sensing, an error was detected on the module. As a Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module.
result of this error, it must be assumed that
the actual value sensing supplies an incorrect coarse position.

Sinamics G130 F32122 Encoder 2: Internal power supply voltage fault Fault in internal reference voltage of ASICs for encoder 2. Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module.
Fault value (r0949, interpret decimal):
1: Reference voltage error.
2: Internal undervoltage.
3: Internal overvoltage.

Sinamics G130 F32123 (N,A) Encoder 2: Signal level A/B unipolar outside The unipolar level (AP/AN or BP/BN) for encoder 2 is outside the - make sure that the encoder cables and shielding are installed in an EMC-
tolerance permissible tolerance. compliant manner.
Fault value (r0949, interpret binary): - check the plug connections and contacts.
Bit 0 = 1: Either AP or AN outside the tolerance. - check the short-circuit of a signal cable with mass or the operating voltage.
Bit 16 = 1: Either BP or BN outside the tolerance. - replace the encoder cable.
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).

Sinamics G130 F32125 (N,A) Encoder 2: Amplitude error track A/B The amplitude of track A or B for encoder 2 exceeds the permissble - check that the encoder cables and shielding are routed in compliance with
overcontrolled tolerance band. EMC.
Fault value (r0949, interpret hexadecimal): - replace the encoder or encoder cable.
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 threshold is > 750 mV. This fault also occurs if the A/D
converter is overcontrolled.
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 threshold
is > 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.
Sinamics G130 F32126 (N,A) Encoder 2: Amplitude AB too high The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 2 exceeds the - check that the encoder cables and shielding are routed in compliance with
permissible tolerance. EMC.
Fault value (r0949, interpret hexadecimal): - replace the encoder or encoder cable.
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.

Sinamics G130 F32129 (N,A) Encoder 2: Position difference, hall The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° - track C or D not connected.
sensor/track C/D and A/B too large electrical or the error for the Hall signals is greater - correct the direction of rotation of the Hall sensor possibly connected as
than +/-60 ° electrical. equivalent for track C/D.
One period of track C/D corresponds to 360 ° mechanical. - check that the encoder cables are routed in compliance with EMC.
One period of the Hall signal corresponds to 360 ° electrical. - check the adjustment of the Hall sensor.
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 °).

Sinamics G130 F32130 (N,A) Encoder 2: Zero mark and position error from After initializing the pole position using track C/D, Hall signals or pole - check that the encoder cables are routed in compliance with EMC.
the coarse synchronization position identification routine, the zero mark - check the plug connections.
was detected outside the permissible range. For distance-coded encoders, - if the Hall sensor is used as an equivalent for track C/D, check the connection.
the test is carried out after passing 2 zero - check the connection of track C or D.
marks. Fine synchronization was not carried out. - replace the encoder or encoder cable.
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 °
Sinamics G130 F32131 (N,A) Encoder 2: Deviation, position Absolute encoder: - check that the encoder cables are routed in compliance with EMC.
incremental/absolute too large When cyclically reading the absolute position, an excessively high - check the plug connections.
difference to the incremental position was - replace the encoder or encoder cable.
detected. The absolute position that was read is rejected. - check whether the coding disk is dirty or there are strong ambient magnetic
Limit value for the deviation: fields.
- EnDat encoder: Is supplied from the encoder and is a minimum of 2 - adapt the parameter for the distance between zero marks (p0425).
quadrants (e.g. EQI 1325 > 2 quadrants, EQN - if message output above speed threshold, reduce filter time if necessary
1325 > 50 quadrants). (p0438).
- 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).

Sinamics G130 F32135 Encoder 2: Fault when determining the The DRIVE-CLiQ encoder supplies status information via bits in an internal Replace DRIVE-CLiQ encoder.
position 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)

Sinamics G130 F32136 Encoder 2: Error when determining multiturn The DRIVE-CLiQ encoder supplies status information via bits in an internal Replace DRIVE-CLiQ encoder.
information 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)
Sinamics G130 F32137 Encoder 2: Internal error when determining The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Replace encoder
the position Fault value (r0949, interpret binary):
Only for internal SIEMENS use.

Sinamics G130 F32128 Encoder 2: Internal error when determining The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Replace encoder
multiturn information Fault value (r0949, interpret binary):
Only for internal SIEMENS use.

Sinamics G130 F32150 (N,A) Encoder 2: Initialization error Encoder functionality selected in p0404 is not operating correctly. - Check that p0404 is correctly set.
Fault value (r0949, interpret hexadecimal): - check the encoder type used (incremental/absolute value) and for SMCxx, the
The fault value is a bit field. Every set bit indicates functionality that is encoder cable.
faulted. - if relevant, note additional fault/error messages that describe the fault in
The bit assignment corresponds to that of p0404 (e.g. bit 5 set: Error track detail.
C/D).

Sinamics G130 F32151 (N,A) Encoder 2: Encoder speed for initialization AB The encoder speed is too high during while initializing the sensor. Reduce the speed of the encoder accordingly during initialization.
too high If necessary, deactivate monitoring (p0437.29).
See also: p0437 (Sensor Module configuration extended)

Sinamics G130 F32405 (N,A) Encoder 2: Temperature in the encoder The encoder evaluation for a motor with DRIVE-CLiQ has detected an Reduce the ambient temperature for the DRIVE-CLiQ connection of the motor.
evaluation inadmissible inadmissible temperature.
The fault threshold is 125 ° C.
Alarm value (r2124, interpret decimal):
Measured board/module temperature in 0.1 °C.

Sinamics G130 F32500 Encoder 2: Position tracking traversing range For a configured linear axis without modulo correction, the drive/encoder The fault should be resolved as follows:
exceeded has exceeded the maximum possible traversing - select encoder commissioning (p0010 = 4).
range. The value should be read in p0412 and interpreted as the number of - reset the position tracking as follows (p0411.2 = 1).
motor revolutions. - de-select encoder commissioning (p0010 = 0).
When p0411.0 = 1, the maximum traversing range for a configured linear The fault should then be acknowledged and the absolute encoder adjusted.
axis is defined to be 64x (+/- 32x) the setting
in p0421.
When p0411.3 = 1, the maximum traversing range for a configured linear
axis is preset to the highest possible value
and equals +/-p0412/2 (rounded to whole rotations). The highest possible
value depends on the pulse number
(p0408) and fine resolution (p0419).

Sinamics G130 F32501 (N,A) Encoder 2: Position tracking encoder position When powered down, the drive/encoder was moved through a distance Reset the position tracking as follows:
outside tolerance window greater than was parameterized in the tolerance - select encoder commissioning (p0010 = 4).
window. It is possible that there is no longer any reference between the - reset the position tracking as follows (p0411.2 = 1).
mechanical system and encoder. - de-select encoder commissioning (p0010 = 0).
Fault value (r0949, decimal): The fault should then be acknowledged and, if necessary, the absolute encoder
Deviation (difference) to the last encoder position in increments of the adjusted (p2507).
absolute value. See also: p0010
The sign designates the traversing direction.
Note:
The deviation (difference) found is also displayed in r0477.
See also: p0413 (Measuring gear, position tracking tolerance window),
r0477 (Measuring gear, position difference)

Sinamics G130 F32502 (N,A) Encoder 2: Encoder with measuring gear, The encoder with measuring gear no longer provides any valid signals. It must be ensured that all of the encoders, with mounted measuring gear,
without valid signals provide valid actual values in operation.
Sinamics G130 F32503 (N,A) Encoder 2: Position tracking cannot be reset The position tracking for the measuring gear cannot be reset. The fault should be resolved as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- de-select encoder commissioning (p0010 = 0).
The fault should then be acknowledged and the absolute encoder adjusted.

Sinamics G130 F32801 (N,A) Encoder 2 DRIVE-CLiQ: Sign-of-life missing A DRIVE-CLiQ communication error has occurred from the Control Unit to - check the electrical cabinet design and cable routing for EMC compliance
the encoder involved. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 F32802 (N,A) Encoder 2: Time slice overflow Time slice overflow, encoder 2. Reduce the current controller frequency.
Fault value (r0949, interpret decimal):
9: Time slice overflow of the fast (current controller clock cycle) time slice.
10: Time slice overflow of the average time slice.
12: Time slice overflow of the slow time slice.
999: Timeout when waiting for SYNO, e.g. unexpected return to non-cyclic
operation.
Sinamics G130 F32804 (N,A) Encoder 2: Checksum error A checksum error has occurred when reading-out the program memory on - check whether the permissible ambient temperature for the component is
the Sensor Module. maintained.
Fault value (r0949, interpret hexadecimal): - replace the Sensor Module.
yyyyxxxx hex
yyyy: Memory area involved.
xxxx: Difference between the checksum at POWER ON and the current
checksum.

Sinamics G130 F32805 (N,A) Encoder 2: EPROM checksum error Internal parameter data is corrupted. Replace the module.
Fault value (r0949, interpret hexadecimal):
01: EEPROM access error.
02: Too many blocks in the EEPROM.

Sinamics G130 F32806 (N,A) Encoder 2: Initialization error The encoder was not successfully initialized. Acknowledge the fault.
Fault value (r0949, interpret hexadecimal):
1, 2, 3: Encoder initialization with the motor rotating.

Sinamics G130 F32811 (N,A) Encoder 2: Encoder serial number changed The encoder serial number has changed. The change is only checked for Mechanically adjust the encoder. Accept the new serial number with p0440 = 1.
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).

Sinamics G130 F32812 (N,A) Encoder 2: Requested cycle or RX-/TX timing A cycle requested from the Control Unit or RX/TX timing is not supported.
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.

Sinamics G130 F32813 Encoder 2: Hardware logic unit failed The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Replace encoder
Fault value (r0949, interpret binary):
Bit 0: ALU watchdog has responded.
Bit 1: ALU has detected a sign-of-life error.

Sinamics G130 F32820 (N,A) Encoder 2 DRIVE-CLiQ: Telegram error A DRIVE-CLiQ communication error has occurred from the Control Unit to - carry out a POWER ON.
the encoder involved. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.
Sinamics G130 F32835 (N,A) Encoder 2 DRIVE-CLiQ: Cyclic data transfer A DRIVE-CLiQ communication error has occurred from the Control Unit to - carry out a POWER ON.
error the encoder involved. The nodes do not - replace the component involved.
send and receive in synchronism. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.

Sinamics G130 F32836 (N,A) Encoder 2 DRIVE-CLiQ: Send error for DRIVE- A DRIVE-CLiQ communication error has occurred from the Control Unit to Carry out a POWER ON.
CLiQ data the encoder involved. Data were not able
to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.

Sinamics G130 F32837 (N,A) Encoder 2 DRIVE-CLiQ: Component fault Fault detected on the DRIVE-CLiQ component involved. Faulty hardware - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.

Sinamics G130 F32845 (N,A) Encoder 2 DRIVE-CLiQ: Cyclic data transfer A DRIVE-CLiQ communication error has occurred from the Control Unit to Carry out a POWER ON.
error the encoder involved. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F32850 (N,A) Encoder 2: Encoder evaluation, internal Internal software error in the Sensor Module of encoder 2. - replace the Sensor Module.
software error Fault value (r0949, interpret decimal): - if required, upgrade the firmware in the Sensor Module.
1: Background time slice is blocked. - contact the Hotline.
2: Checksum over the code memory is not OK.
10000: OEM memory of the EnDat encoder contains data that cannot be
interpreted.
11000 - 11499: Descriptive data from EEPROM incorrect.
11500 - 11899: Calibration data from EEPROM incorrect.
11900 - 11999: Configuration data from EEPROM incorrect.
16000: DRIVE-CLiQ encoder initialization application error.
16001: DRIVE-CLiQ encoder initialization ALU error.
16002: DRIVE-CLiQ encoder HISI / SISI initialization error.
16003: DRIVE-CLiQ encoder safety initialization error.
16004: DRIVE-CLiQ encoder internal system error.

Sinamics G130 F32851 (N,A) Encoder 2 DRIVE-CLiQ (CU): Sign-of-life missing A DRIVE-CLiQ communication error has occurred from the Sensor Module Upgrade the firmware of the component involved.
(encoder 2) involved to the Control Unit.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex = 10 dec:
The sign-of-life bit in the receive telegram is not set.
Sinamics G130 F32860 (N,A) Encoder 2 DRIVE-CLiQ (CU): Telegram error A DRIVE-CLiQ communication error has occurred from the Sensor Module - carry out a POWER ON.
(encoder 2) involved to the Control Unit. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
xx = 11 hex = 17 dec:
CRC error and the receive telegram is too early.
xx = 01 hex = 01 dec:
Checksum error (CRC error).
xx = 12 hex = 18 dec:
The telegram is shorter than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 02 hex = 02 dec:
Telegram is shorter than specified in the length byte or in the receive list.
xx = 13 hex = 19 dec:
The telegram is longer than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 03 hex = 03 dec:
Telegram is longer than specified in the length byte or in the receive list.
xx = 14 hex = 20 dec:
The length of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 04 hex = 04 dec:
The length of the receive telegram does not match the receive list.
xx = 15 hex = 21 dec:
The type of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 05 hex = 05 dec:
The type of the receive telegram does not match the receive list.

Sinamics G130 F32885 (N,A) Encoder 2 DRIVE-CLiQ (CU): Cyclic data transfer A DRIVE-CLiQ communication error has occurred from the Sensor Module - check the power supply voltage of the component involved.
error (encoder 2) involved to the Control Unit. - carry out a POWER ON.
The nodes do not send and receive in synchronism. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
yyxx hex: yy = component number, xx = fault cause
xx = 1A hex = 26 dec:
Sign-of-life bit in the receive telegram not set and the receive telegram is
too early.
xx = 21 hex = 33 dec:
The cyclic telegram has not been received.
xx = 22 hex = 34 dec:
Timeout in the telegram receive list.
xx = 40 hex = 64 dec:
Timeout in the telegram send list.
xx = 62 hex = 98 dec:
Error at the transition to cyclic operation.

Sinamics G130 F32886 (N,A) Encoder 2 DRIVE-CLiQ (CU): Error when A DRIVE-CLiQ communication error has occurred from the Sensor Module Carry out a POWER ON.
sending DRIVE-CLiQ data (encoder 2) involved to the Control Unit.
Component number: %1, fault cause: %2 Data were not able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.

Sinamics G130 F32887 (N,A Encoder 2 DRIVE-CLiQ (CU): Component fault Fault detected on the DRIVE-CLiQ component involved (Sensor Module for - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
encoder 2). Faulty hardware cannot be - check the electrical cabinet design and cable routing for EMC compliance
excluded. - if required, use another DRIVE-CLiQ socket (p9904).
Fault value (r0949, interpret hexadecimal): - replace the component involved.
yyxx hex: yy = component number, xx = fault cause
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.
xx = 60 hex:
Response received too late during runtime measurement.
xx = 61 hex:
Time taken to exchange characteristic data too long.
Sinamics G130 F32895 (N,A) Encoder 2 DRIVE-CLiQ (CU): Alternating cyclic A DRIVE-CLiQ communication error has occurred from the Sensor Module Carry out a POWER ON.
data transfer error (encoder 2) involved to the Control Unit. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F32896 (N,A) Encoder 2 DRIVE-CLiQ (CU): Inconsistent The properties of the DRIVE-CLiQ component (Sensor Module for encoder - when replacing cables, only use cables with the same length as the original
component properties 2), specified by the fault value, have cables.
changed in an incompatible fashion with respect to the properties when - when replacing components, use the same components and firmware releases.
booted. One cause can be, e.g. that a - carry out a POWER ON.
DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced.
Fault value (r0949, interpret decimal):
Component number.

Sinamics G130 F32899 (N,A) Encoder 2: Unknown fault A fault occurred on the Sensor Module for encoder 2 that cannot be - replace the firmware on the Sensor Module by an older firmware version
interpreted by the Control Unit firmware. (r0148).
This can occur if the firmware on this component is more recent than the - upgrade the firmware on the Control Unit (r0018).
firmware on the Control Unit.
Fault value (r0949, interpret decimal):
Fault number.
Note:
If required, the significance of this new fault can be read about in a more
recent description of the Control Unit.

Sinamics G130 F32905 (N,A) Encoder 2: Parameterization error A parameter of encoder 2 was detected as being incorrect. - check whether the connected encoder type matches the encoder that has been
It is possible that the parameterized encoder type does not match the parameterized.
connected encoder. - correct the parameter specified by the fault value (r0949) and p0187.
The parameter involved can be determined as follows: - re parameter number 314: Check the pole pair number and measuring gear
- determine the parameter number using the fault value (r0949). ratio. The quotient of the "pole pair
- determine the parameter index (p0187). number" divided by the "measuring gear ratio" must be less than or equal to
Fault value (r0949, interpret decimal): 1000 ((r0313 * p0433) / p0432 <= 1000).
yyyyxxxx dec: yyyy = supplementary information, xxxx = parameter
Supplementary information = 0:
No information available.
Supplementary information = 1:
The component does not support HTL level (p0405.1 = 0) combined with
track monitoring A/B <> -A/B (p0405.2 = 1).
Supplementary information = 2:
A code number for an identified encoder has been entered into p0400,
however, no identification was carried out.
Please start a new encoder identification.
Supplementary information = 3:
A code number for an identified encoder has been entered into p0400,
however, no identification was carried out.
Please select a listed encoder in p0400 with a code number < 10000.
Supplementary information = 4:
This component does not support SSI encoders (p0404.9 = 1) without track
A/B.
Supplementary information = 5:
For the SQW encoder, the value in p4686 is greater than that in p0425.
Supplementary information = 6:
The DRIVE-CLiQ encoder cannot be used with this firmware version.

Sinamics G130 F32916 (N,A) Encoder 2: Parameterization error A parameter of encoder 2 was detected as being incorrect. - check whether the connected encoder type matches the encoder that has been
It is possible that the parameterized encoder type does not match the parameterized.
connected encoder. - correct the parameter specified by the fault value (r0949) and p0187.
The parameter involved can be determined as follows:
- determine the parameter number using the fault value (r0949).
- determine the parameter index (p0187).
Fault value (r0949, interpret decimal):
Parameter number
The fault is only output for encoders with r404[0].10 = 1. This corresponds
to A32905 for encoders with r404[0].10 =
0.
Sinamics G130 F33100 (N,A) Encoder 3: Zero mark distance error The measured zero mark distance does not correspond to the - check that the encoder cables are routed in compliance with EMC.
parameterized zero mark distance. - check the plug connections.
For distance-coded encoders, the zero mark distance is determined from . check the encoder type (encoder with equidistant zero marks).
zero marks detected pairs. This means that - adapt the parameter for the distance between zero marks (p0424, p0425).
if a zero mark is missing, depending on the pair generation, this cannot - if message output above speed threshold, reduce filter time if necessary
result in a fault and also has no effect in the (p0438).
system. - replace the encoder or encoder cable.
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.

Sinamics G130 F33101 (N,A) Encoder 3: Zero marked failed The 1.5 x parameterized zero mark distance was exceeded. - check that the encoder cables are routed in compliance with EMC.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary - check the plug connections.
encoder) or p0424 (linear encoder). . check the encoder type (encoder with equidistant zero marks).
Fault value (r0949, interpret decimal): - adapt the parameter for the distance between zero marks (p0425).
Number of increments after POWER ON or since the last zero mark that - if message output above speed threshold, reduce filter time if necessary
was detected (4 increments = 1 encoder (p0438).
pulse). - when p0437.1 is active, check p4686.
- replace the encoder or encoder cable.

Sinamics G130 F33103 (N,A) Encoder 3: Amplitude error, track R The amplitude of the reference track signal (track R) does not lie within the - check the speed range, frequency characteristic (amplitude characteristic) of
tolerance bandwidth for encoder 3. the measuring equipment may not be
The fault can be initiated when the unipolar voltage range is exceeded or sufficient for the speed range.
the differential amplitude is initiated. - check that the encoder cables and shielding are routed in compliance with
Fault value (r0949, interpret hexadecimal): EMC.
xxxx hex: - check the plug connections and contacts.
xxxx = Signal level, track R (16 bits with sign). - check whether the zero mark is connected and the signal cables RP and RN
The unipolar nominal signal level of the encoder must lie in the range 2500 connected correctly.
mV +/- 500 mV. '- replace the encoder cable.
The response threshold is < 1700 mV and > 3300 mV. - if the coding disk is soiled or the lighting worn, replace the encoder.
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).
Sinamics G130 F33110 (N,A) Encoder 3: Serial communications error Serial communication protocol transfer error between the encoder and Re fault value, bit 0 = 1:
evaluation module. - encoder defective. F31111 may provide additional details.
Fault value (r0949, interpret binary): Re fault value, bit 1 = 1:
Bit 0: Alarm bit in the position protocol. - Incorrect encoder type / replace the encoder or encoder cable.
Bit 1: Incorrect quiescent level on the data line. Re fault value, bit 2 = 1:
Bit 2: Encoder does not respond (does not supply a start bit within 50 ms). - Incorrect encoder type / replace the encoder or encoder cable.
Bit 3: CRC error: The checksum in the protocol from the encoder does not Re fault value, bit 3 = 1:
match the data. - EMC / connect the cable shield, replace the encoder or encoder cable.
Bit 4: Encoder acknowledgement error: The encoder incorrectly Re fault value, bit 4 = 1:
understood the task (request) or cannot execute it. - EMC / connect the cable shield, replace the encoder or encoder cable, replace
Bit 5: Internal error in the serial driver: An illegal mode command was the Sensor Module.
requested. Re fault value, bit 5 = 1:
Bit 6: Timeout when cyclically reading. - EMC / connect the cable shield, replace the encoder or encoder cable, replace
Bit 8: Protocol is too long (e.g. > 64 bits). the Sensor Module.
Bit 9: Receive buffer overflow. Re fault value, bit 6 = 1:
Bit 10: Frame error when reading twice. - Update the firmware for the Sensor Module.
Bit 11: Parity error. Re fault value, bit 8 = 1:
Bit 12: Data line signal level error during the monoflop time. - Check the parameterization (p0429.2).
Bit 13: Data line incorrect. Re fault value, bit 9 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace
the Sensor Module.
Re fault value, bit 10 = 1:
- Check the parameterization (p0429.2, p0449).
Re fault value, bit 11 = 1:
- Check the parameterization (p0436).
Re fault value, bit 12 = 1:
- Check the parameterization (p0429.6).
Re fault value, bit 13 = 1:
- Check the data line.

Sinamics G130 F33111 (N,A) Encoder 3: Absolute encoder EnDat, internal The EnDat encoder fault word supplies fault bits that have been set. Re fault value, bit 0 = 1:
fault/error Fault value (r0949, interpret binary): Encoder is defective. Replace the encoder, where the motor encoder has a direct
Bit 0: Lighting system failed. DRIVE-CLiQ socket: Replace the
Bit 1: Signal amplitude too low. motor.
Bit 2: Position value incorrect. Re fault value, bit 1 = 1:
Bit 3: Encoder power supply overvoltage condition. Encoder is defective. Replace the encoder, where the motor encoder has a direct
Bit 4: Encoder power supply undervoltage condition. DRIVE-CLiQ socket: Replace the
Bit 5: Encoder power supply overcurrent condition. motor.
Bit 6: The battery must be changed. Re fault value, bit 2 = 1:
Encoder is defective. Replace the encoder, where the motor encoder has a direct
DRIVE-CLiQ socket: Replace the
motor.
Re fault value, bit 3 = 1:
5 V power supply voltage fault.
When using an SMC: Check the plug-in cable between the encoder and SMC or
replace the SMC.
When a motor encoder with a direct DRIVE-CLiQ connection is used: Replace the
motor.
Re fault value, bit 4 = 1:
5 V power supply voltage fault.
When using an SMC: Check the plug-in cable between the encoder and SMC or
replace the SMC.
When using a motor with DRIVE-CLiQ: Replace the motor.
Re fault value, bit 5 = 1:
Encoder is defective. Replace the encoder, where the motor encoder has a direct
DRIVE-CLiQ socket: Replace the
motor.
Re fault value, bit 6 = 1:
The battery must be changed (only for encoders with battery back-up).

Sinamics G130 F33112 (N,A) Encoder 3: Error bit set in the serial protocol The encoder sends a set error bit via the serial protocol. For fault value, bit 0 = 1:
Fault value (r0949, interpret binary): In the case of an EnDat encoder, F31111 may provide further details.
Bit 0: Fault bit in the position protocol.

Sinamics G130 F33115 (N,A) Encoder 3: Amplitude error track A/B fault The amplitude (root of A^2 + B^2) for encoder 3 exceeds the permissible - check that the encoder cables and shielding are routed in compliance with
(A^2 + B^2) tolerance. EMC.
Fault value (r0949, interpret hexadecimal): - check the plug connections.
yyyyxxxx hex: - replace the encoder or encoder cable.
yyyy = Signal level, track B (16 bits with sign). - check the Sensor Module (e.g. contacts).
xxxx = Signal level, track A (16 bits with sign).
Sinamics G130 F33116 (N,A) Encoder 3: Amplitude error track A + B The amplitude of the rectified encoder signals A and B and the amplitude - check that the encoder cables and shielding are routed in compliance with
from the roots of A^2 + B^2 for encoder 3 EMC.
are not within the tolerance bandwidth. - check the plug connections.
Fault value (r0949, interpret hexadecimal): - replace the encoder or encoder cable.
yyyyxxxx hex: - check the Sensor Module (e.g. contacts).
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.

Sinamics G130 F33117 (N,A) Encoder 3: Inversion error signals A and B and For a square-wave signal encoder (TTL. bipolar. double ended) the A* and - check the setting of p0405: p0405.2 = 1 is only possible if the encoder is
R B* and R* signals are not inverted with connected at X520.
respect to signals A and B and R. - check the encoder/cable: Does the encoder supply TTL signals and the
Note: associated inverted signals?
For CU310, CUA32, D410, SMC30 (only Order No. 6SL3055-0AA00-5CA0 Note:
and 6SL3055-0AA00-5CA1), the following For a squarewave encoder without track R, the following jumpers must be set at
applies: the encoder connection:
A squarewave encoder without track R is used and the track monitoring - pin 10 (reference signal R) <--> pin 7 (encoder power supply, ground)
(p0405.2 = 1) is activated. - pin 11 (reference signal R inverted) <--> pin 4 (encoder power supply)

Sinamics G130 F33118 (N,A) Encoder 3: Speed difference outside the For an HTL/TTL encoder, the speed difference has exceeded the value in - check the tachometer feeder cable for interruptions.
tolerance range p0492 over several sampling cycles. - check the grounding of the tachometer shielding.
The change to the averaged speed actual value - if applicable - is monitored - if required, increase the maximum speed difference per sampling cycle
in the current controller sampling time. (p0492).C575Encoder 3: Power supply voltage fault
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
See also: p0492 (Square-wave encoder, maximum speed difference per
sampling cycle)

Sinamics G130 F33120 (N,A) Encoder 3: Power supply voltage fault Encoder 3 power supply voltage fault. For fault value, bit 0 = 1:
Note: - correct encoder cable connected?
If the encoder cables 6FX2002-2EQ00-.... and 6FX2002-2CH00-.... are - check the plug connections of the encoder cable.
interchanged, this can result in the encoder - SMC30: Check the parameterization (p0404.22).
being destroyed because the pins of the operating voltage are reversed. For fault value, bit 1 = 1:
Fault value (r0949, interpret binary): - correct encoder cable connected?
Bit 0: Undervoltage condition on the sense line. - replace the encoder or encoder cable.
Bit 1: Overcurrent condition for the encoder power supply.

Sinamics G130 F33121 (N,A) Encoder 3: Coarse position error For the actual value sensing, an error was detected on the module. As a Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module.
result of this error, it must be assumed that
the actual value sensing supplies an incorrect coarse position.

Sinamics G130 F33122 Encoder 3: Internal power supply voltage fault Fault in internal reference voltage of ASICs for encoder 3. Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module.
Fault value (r0949, interpret decimal):
1: Reference voltage error.
2: Internal undervoltage.
3: Internal overvoltage.

Sinamics G130 F33123 (N,A) Encoder 3: Signal level A/B unipolar outside The unipolar level (AP/AN or BP/BN) for encoder 3 is outside the - make sure that the encoder cables and shielding are installed in an EMC-
tolerance permissible tolerance. compliant manner.
Fault value (r0949, interpret binary): - check the plug connections and contacts.
Bit 0 = 1: Either AP or AN outside the tolerance. - check the short-circuit of a signal cable with mass or the operating voltage.
Bit 16 = 1: Either BP or BN outside the tolerance. - replace the encoder cable.
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).
Sinamics G130 F33125 (N,A) Encoder 3: Amplitude error track A/B The amplitude of track A or B for encoder 3 exceeds the permissble - check that the encoder cables and shielding are routed in compliance with
overcontrolled tolerance band. EMC.
Fault value (r0949, interpret hexadecimal): - replace the encoder or encoder cable.
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 threshold is > 750 mV. This fault also occurs if the A/D
converter is overcontrolled.
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 threshold
is > 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.

Sinamics G130 F33126 (N,A) Encoder 3: Amplitude AB too high The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 3 exceeds the - check that the encoder cables and shielding are routed in compliance with
permissible tolerance. EMC.
Fault value (r0949, interpret hexadecimal): - replace the encoder or encoder cable.
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.

Sinamics G130 F33129 (N,A) Encoder 3: Position difference, hall The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° ;- track C or D not connected.
sensor/track C/D and A/B too large electrical or the error for the Hall signals is greater - correct the direction of rotation of the Hall sensor possibly connected as
than +/-60 ° electrical. equivalent for track C/D.
One period of track C/D corresponds to 360 ° mechanical. - check that the encoder cables are routed in compliance with EMC.
One period of the Hall signal corresponds to 360 ° electrical. - check the adjustment of the Hall sensor.E580
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 °).
Sinamics G130 F33130 (N,A) Encoder 3: Zero mark and position error from After initializing the pole position using track C/D, Hall signals or pole - check that the encoder cables are routed in compliance with EMC.
the coarse synchronization position identification routine, the zero mark - check the plug connections.
was detected outside the permissible range. For distance-coded encoders, '- if the Hall sensor is used as an equivalent for track C/D, check the connection.
the test is carried out after passing 2 zero - check the connection of track C or D.
marks. Fine synchronization was not carried out. - replace the encoder or encoder cable.E583:E587
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 °

Sinamics G130 F33131 (N,A) Encoder 3: Deviation, position Absolute encoder: - check that the encoder cables are routed in compliance with EMC.
incremental/absolute too large When cyclically reading the absolute position, an excessively high - check the plug connections.
difference to the incremental position was - replace the encoder or encoder cable.
detected. The absolute position that was read is rejected. - check whether the coding disk is dirty or there are strong ambient magnetic
Limit value for the deviation: fields.
- EnDat encoder: Is supplied from the encoder and is a minimum of 2 - adapt the parameter for the distance between zero marks (p0425).
quadrants (e.g. EQI 1325 > 2 quadrants, EQN - if message output above speed threshold, reduce filter time if necessary
1325 > 50 quadrants). (p0438).
- 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).

Sinamics G130 F33135 Encoder 3: Fault when determining the The DRIVE-CLiQ encoder supplies status information via bits in an internal Replace DRIVE-CLiQ encoder.
position 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)
Sinamics G130 F33136 Encoder 3: Error when determining multiturn The DRIVE-CLiQ encoder supplies status information via bits in an internal Replace DRIVE-CLiQ encoder.
information 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)

Sinamics G130 F33137 Encoder 3: Internal error when determining The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Replace encoder
the position Fault value (r0949, interpret binary):
Only for internal SIEMENS use.

Sinamics G130 F33138 Encoder 3: Internal error when determining The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Replace encoder
multiturn information Fault value (r0949, interpret binary):
Only for internal SIEMENS use.

Sinamics G130 F33150 Encoder 3: Initialization error Encoder functionality selected in p0404 is not operating correctly. - Check that p0404 is correctly set.
Fault value (r0949, interpret hexadecimal): - check the encoder type used (incremental/absolute value) and for SMCxx, the
The fault value is a bit field. Every set bit indicates functionality that is encoder cable.
faulted. - if relevant, note additional fault/error messages that describe the fault in
The bit assignment corresponds to that of p0404 (e.g. bit 5 set: Error track detail.
C/D).

Sinamics G130 F33151 (N,A) Encoder 3: Encoder speed for initialization AB The encoder speed is too high during while initializing the sensor. Reduce the speed of the encoder accordingly during initialization.
too high If necessary, deactivate monitoring (p0437.29).
See also: p0437 (Sensor Module configuration extended)

Sinamics G130 F33405 Encoder 3: Temperature in the encoder The encoder evaluation for a motor with DRIVE-CLiQ has detected an Reduce the ambient temperature for the DRIVE-CLiQ connection of the motor.
evaluation inadmissible inadmissible temperature.
The fault threshold is 125 ° C.
Alarm value (r2124, interpret decimal):
Measured board/module temperature in 0.1 °C.

Sinamics G130 F33500 Encoder 3: Position tracking traversing range For a configured linear axis without modulo correction, the drive/encoder The fault should be resolved as follows:
exceeded has exceeded the maximum possible traversing - select encoder commissioning (p0010 = 4).
range. The value should be read in p0412 and interpreted as the number of - reset the position tracking as follows (p0411.2 = 1).
motor revolutions. - de-select encoder commissioning (p0010 = 0).
When p0411.0 = 1, the maximum traversing range for a configured linear The fault should then be acknowledged and the absolute encoder adjusted.
axis is defined to be 64x (+/- 32x) the setting
in p0421.
When p0411.3 = 1, the maximum traversing range for a configured linear
axis is preset to the highest possible value
and equals +/-p0412/2 (rounded to whole rotations). The highest possible
value depends on the pulse number
(p0408) and fine resolution (p0419).

Sinamics G130 F33501 (N,A) Encoder 3: Position tracking encoder position When powered down, the drive/encoder was moved through a distance Reset the position tracking as follows:
outside tolerance window greater than was parameterized in the tolerance - select encoder commissioning (p0010 = 4).
window. It is possible that there is no longer any reference between the - reset the position tracking as follows (p0411.2 = 1).
mechanical system and encoder. - de-select encoder commissioning (p0010 = 0).
Fault value (r0949, decimal): The fault should then be acknowledged and, if necessary, the absolute encoder
Deviation (difference) to the last encoder position in increments of the adjusted (p2507).
absolute value. See also: p0010
The sign designates the traversing direction.
Note:
The deviation (difference) found is also displayed in r0477.
See also: p0413 (Measuring gear, position tracking tolerance window),
r0477 (Measuring gear, position difference)

Sinamics G130 F33502 (N,A) Encoder 3: Encoder with measuring gear, The encoder with measuring gear no longer provides any valid signals. It must be ensured that all of the encoders, with mounted measuring gear,
without valid signals provide valid actual values in operation.
Sinamics G130 F33503 (N,A) Encoder 3: Position tracking cannot be reset The position tracking for the measuring gear cannot be reset. The fault should be resolved as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- de-select encoder commissioning (p0010 = 0).
The fault should then be acknowledged and the absolute encoder adjusted.

Sinamics G130 F33801 (N,A) Encoder 3 DRIVE-CLiQ: Sign-of-life missing A DRIVE-CLiQ communication error has occurred from the Control Unit to - check the electrical cabinet design and cable routing for EMC compliance
the encoder involved. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 F33802 (N,A) Encoder 3: Time slice overflow Time slice overflow, encoder 3. Reduce the current controller frequency.
Fault value (r0949, interpret decimal):
9: Time slice overflow of the fast (current controller clock cycle) time slice.
10: Time slice overflow of the average time slice.
12: Time slice overflow of the slow time slice.
999: Timeout when waiting for SYNO, e.g. unexpected return to non-cyclic
operation.

Sinamics G130 F33804 (n,A) Encoder 3: Checksum error A checksum error has occurred when reading-out the program memory on - check whether the permissible ambient temperature for the component is
the Sensor Module. maintained.
Fault value (r0949, interpret hexadecimal): - replace the Sensor Module.
yyyyxxxx hex
yyyy: Memory area involved.
xxxx: Difference between the checksum at POWER ON and the current
checksum.

Sinamics G130 F33805 (N,A) Encoder 3: EPROM checksum error Internal parameter data is corrupted. Replace the module.
Fault value (r0949, interpret hexadecimal):
01: EEPROM access error.
02: Too many blocks in the EEPROM.

Sinamics G130 F33806 (N,A) Encoder 3: Initialization error The encoder was not successfully initialized. The encoder was not successfully initialized.
Fault value (r0949, interpret hexadecimal): Fault value (r0949, interpret hexadecimal):
1, 2, 3: Encoder initialization with the motor rotating. 1, 2, 3: Encoder initialization with the motor rotating.

Sinamics G130 F33811 (n,A) Encoder 3: Encoder serial number changed The encoder serial number has changed. The change is only checked for Mechanically adjust the encoder. Accept the new serial number with p0440 = 1.
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).

Sinamics G130 F33812 (N, A) Encoder 3: Requested cycle or RX-/TX timing A cycle requested from the Control Unit or RX/TX timing is not supported.
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.

Sinamics G130 F33813 Encoder 3: Hardware logic unit failed The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Replace encoder
Fault value (r0949, interpret binary):
Bit 0: ALU watchdog has responded.
Bit 1: ALU has detected a sign-of-life error.
Sinamics G130 F33820 (N, A) Encoder 3 DRIVE-CLiQ: Telegram error A DRIVE-CLiQ communication error has occurred from the Control Unit to - carry out a POWER ON.
the encoder involved. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.

Sinamics G130 F33835 (N, A) Encoder 3 DRIVE-CLiQ: Cyclic data transfer A DRIVE-CLiQ communication error has occurred from the Control Unit to - carry out a POWER ON.
error the encoder involved. The nodes do not - replace the component involved.
send and receive in synchronism. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.

Sinamics G130 F33836 (N, A) Encoder 3 DRIVE-CLiQ: Send error for DRIVE- A DRIVE-CLiQ communication error has occurred from the Control Unit to Carry out a POWER ON.
CLiQ data the encoder involved. Data were not able
to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.

Sinamics G130 F33837 (N, A) Encoder 3 DRIVE-CLiQ: Component fault Fault detected on the DRIVE-CLiQ component involved. Faulty hardware - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.

Sinamics G130 F33845 (N, A) Encoder 3 DRIVE-CLiQ: Cyclic data transfer A DRIVE-CLiQ communication error has occurred from the Control Unit to Carry out a POWER ON.
error the encoder involved. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.
Sinamics G130 F33850 Encoder 3: Encoder evaluation, internal Internal software error in the Sensor Module of encoder 3. - replace the Sensor Module.
software error Fault value (r0949, interpret decimal): - if required, upgrade the firmware in the Sensor Module.
1: Background time slice is blocked. - contact the Hotline.
2: Checksum over the code memory is not OK.
10000: OEM memory of the EnDat encoder contains data that cannot be
interpreted.
11000 - 11499: Descriptive data from EEPROM incorrect.
11500 - 11899: Calibration data from EEPROM incorrect.
11900 - 11999: Configuration data from EEPROM incorrect.
16000: DRIVE-CLiQ encoder initialization application error.
16001: DRIVE-CLiQ encoder initialization ALU error.
16002: DRIVE-CLiQ encoder HISI / SISI initialization error.
16003: DRIVE-CLiQ encoder safety initialization error.
16004: DRIVE-CLiQ encoder internal system error.

Sinamics G130 F33851 Encoder 3 DRIVE-CLiQ (CU): Sign-of-life missing A DRIVE-CLiQ communication error has occurred from the Sensor Module Upgrade the firmware of the component involved.
(encoder 3) involved to the Control Unit.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex = 10 dec:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 F33860 (N,A) Encoder 3 DRIVE-CLiQ (CU): Telegram error A DRIVE-CLiQ communication error has occurred from the Sensor Module - carry out a POWER ON.
(encoder 3) involved to the Control Unit. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
xx = 11 hex = 17 dec:
CRC error and the receive telegram is too early.
xx = 01 hex = 01 dec:
Checksum error (CRC error).
xx = 12 hex = 18 dec:
The telegram is shorter than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 02 hex = 02 dec:
Telegram is shorter than specified in the length byte or in the receive list.
xx = 13 hex = 19 dec:
The telegram is longer than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 03 hex = 03 dec:
Telegram is longer than specified in the length byte or in the receive list.
xx = 14 hex = 20 dec:
The length of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 04 hex = 04 dec:
The length of the receive telegram does not match the receive list.
xx = 15 hex = 21 dec:
The type of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 05 hex = 05 dec:
The type of the receive telegram does not match the receive list.
xx = 16 hex = 22 dec:
The address of the power unit in the telegram and in the receive list does
not match and the receive telegram is too
early.
xx = 06 hex = 06 dec:

Sinamics G130 F33885 N,A) Encoder 3 DRIVE-CLiQ (CU): Cyclic data transfer A DRIVE-CLiQ communication error has occurred from the Sensor Module - check the power supply voltage of the component involved.
error (encoder 3) involved to the Control Unit. - carry out a POWER ON.
The nodes do not send and receive in synchronism. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
yyxx hex: yy = component number, xx = fault cause
xx = 1A hex = 26 dec:
Sign-of-life bit in the receive telegram not set and the receive telegram is
too early.
xx = 21 hex = 33 dec:
The cyclic telegram has not been received.
xx = 22 hex = 34 dec:
Timeout in the telegram receive list.
xx = 40 hex = 64 dec:
Timeout in the telegram send list.
xx = 62 hex = 98 dec:
Error at the transition to cyclic operation.
Sinamics G130 F33886 (N,A) Encoder 3 DRIVE-CLiQ (CU): Error when A DRIVE-CLiQ communication error has occurred from the Sensor Module Carry out a POWER ON.
sending DRIVE-CLiQ data (encoder 3) involved to the Control Unit.
Data were not able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.

Sinamics G130 F33887 (N,A) Encoder 3 DRIVE-CLiQ (CU): Component fault Fault detected on the DRIVE-CLiQ component involved (Sensor Module for - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
encoder 3). Faulty hardware cannot be - check the electrical cabinet design and cable routing for EMC compliance
excluded. - if required, use another DRIVE-CLiQ socket (p9904).
Fault value (r0949, interpret hexadecimal): - replace the component involved.
yyxx hex: yy = component number, xx = fault cause
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.
xx = 60 hex:
Response received too late during runtime measurement.
xx = 61 hex:
Time taken to exchange characteristic data too long.

Sinamics G130 F33895 (N,A) Encoder 3 DRIVE-CLiQ (CU): Alternating cyclic A DRIVE-CLiQ communication error has occurred from the Sensor Module Carry out a POWER ON.
data transfer error (encoder 3) involved to the Control Unit. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F33896 (N,A) Encoder 3 DRIVE-CLiQ (CU): Inconsistent The properties of the DRIVE-CLiQ component (Sensor Module for encoder - when replacing cables, only use cables with the same length as the original
component properties 3), specified by the fault value, have cables.
changed in an incompatible fashion with respect to the properties when - when replacing components, use the same components and firmware releases.
booted. One cause can be, e.g. that a - carry out a POWER ON.
DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced.
Fault value (r0949, interpret decimal):
Component number.

Sinamics G130 F33899 (N,A) Encoder 3: Unknown fault A fault occurred on the Sensor Module for encoder 3 that cannot be '- replace the firmware on the Sensor Module by an older firmware version
interpreted by the Control Unit firmware. (r0148).
This can occur if the firmware on this component is more recent than the - upgrade the firmware on the Control Unit (r0018).
firmware on the Control Unit.
Fault value (r0949, interpret decimal):
Fault number.
Note:
If required, the significance of this new fault can be read about in a more
recent description of the Control Unit.
Sinamics G130 F33905 (N,A) Encoder 3: Parameterization error A parameter of encoder 3 was detected as being incorrect. - check whether the connected encoder type matches the encoder that has been
It is possible that the parameterized encoder type does not match the parameterized.
connected encoder. - correct the parameter specified by the fault value (r0949) and p0187.
The parameter involved can be determined as follows: - re parameter number 314: Check the pole pair number and measuring gear
- determine the parameter number using the fault value (r0949). ratio. The quotient of the "pole pair
- determine the parameter index (p0187). number" divided by the "measuring gear ratio" must be less than or equal to
Fault value (r0949, interpret decimal): 1000 ((r0313 * p0433) / p0432 <= 1000).
yyyyxxxx dec: yyyy = supplementary information, xxxx = parameter
Supplementary information = 0:
No information available.
Supplementary information = 1:
The component does not support HTL level (p0405.1 = 0) combined with
track monitoring A/B <> -A/B (p0405.2 = 1).
Supplementary information = 2:
A code number for an identified encoder has been entered into p0400,
however, no identification was carried out.
Please start a new encoder identification.
Supplementary information = 3:
A code number for an identified encoder has been entered into p0400,
however, no identification was carried out.
Please select a listed encoder in p0400 with a code number < 10000.
Supplementary information = 4:
This component does not support SSI encoders (p0404.9 = 1) without track
A/B.
Supplementary information = 5:
For the SQW encoder, the value in p4686 is greater than that in p0425.
Supplementary information = 6:
The DRIVE-CLiQ encoder cannot be used with this firmware version.

Sinamics G130 F33916 (N,A) Encoder 3: Parameterization error A parameter of encoder 3 was detected as being incorrect. - check whether the connected encoder type matches the encoder that has been
It is possible that the parameterized encoder type does not match the parameterized.
connected encoder. - correct the parameter specified by the fault value (r0949) and p0187.
The parameter involved can be determined as follows:
- determine the parameter number using the fault value (r0949).
- determine the parameter index (p0187).
Fault value (r0949, interpret decimal):
Parameter number
The fault is only output for encoders with r404[0].10 = 1. This corresponds
to A33905 for encoders with r404[0].10 =
0.

Sinamics G130 F34207 VSM: Temperature fault threshold exceeded The temperature (r3666) measured using the Voltage Sensing Module - check the fan.
(VSM) has exceeded the threshold value - reduce the power.
(p3668).
This fault can only be initiated if the temperature evaluation was activated
(p3665 = 2 for a KTY sensor or p3665 =
1 for a PTC sensor).
Fault value (r0949, interpret decimal):
The hundred thousands and ten thousands position specifies the
component number of the VSM where the fault
occurred.

Sinamics G130 F34801 VSM DRIVE-CLiQ: Sign-of-life missing A DRIVE-CLiQ communications error has occurred from the Control Unit to - check the DRIVE-CLiQ connection.
the Voltage Sensing Module (VSM). - replace the Terminal Module.
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.

Sinamics G130 F34802 VSM: Time slice overflow Time slice overflow on the Voltage Sensing Module. Replace the Voltage Sensing Module.
Sinamics G130 F34803 VSM: Memory test An error has occurred during the memory test on the Voltage Sensing - check whether the permissible ambient temperature for the Voltage Sensing
Module. Module is being maintained.
- replace the Voltage Sensing Module.

Sinamics G130 F34804 VSM: CRC A checksum error has occurred when reading-out the program memory on - check whether the permissible ambient temperature for the component is
the Voltage Sensing Module (VSM). maintained.
- replace the Voltage Sensing Module.

Sinamics G130 F34805 VSM: EPROM checksum error Internal parameter data is corrupted. - check whether the permissible ambient temperature for the component is
Fault value (r0949, interpret hexadecimal): maintained.
01: EEPROM access error. - replace the Voltage Sensing Module (VSM).
02: Too many blocks in the EEPROM.

Sinamics G130 F34806 VSM: Initialization For the Voltage Sensing Module (VSM), a fault has occurred while Replace the Voltage Sensing Module.
initializing.
Sinamics G130 F34820 VSM DRIVE-CLiQ: Telegram error A DRIVE-CLiQ communications error has occurred from the Control Unit to - carry out a POWER ON.
the Voltage Sensing Module. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.

Sinamics G130 F34835 VSM DRIVE-CLiQ: Cyclic data transfer error A DRIVE-CLiQ communications error has occurred from the Control Unit to - carry out a POWER ON.
the Voltage Sensing Module. The nodes - replace the component involved.
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.

Sinamics G130 F34836 VSM DRIVE-CLiQ: Send error for DRIVE-CLiQ A DRIVE-CLiQ communications error has occurred from the Control Unit to Carry out a POWER ON.
data the Voltage Sensing Module. Data were
not able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.

Sinamics G130 F34837 VSM DRIVE-CLiQ: Component fault Fault detected on the DRIVE-CLiQ component involved. Faulty hardware - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.

Sinamics G130 F34845 VSM DRIVE-CLiQ: Cyclic data transfer error A DRIVE-CLiQ communications error has occurred from the Control Unit to Carry out a POWER ON.
the Voltage Sensing Module (VSM). See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F34850 VSM: Internal software error An internal software error in the Voltage Sensing Module (VSM) has - replace the Voltage Sensing Module (VSM).
occurred. - if required, upgrade the firmware in the Voltage Sensing Module.
Fault value (r0949, interpret decimal): - contact the Hotline.
1: Background time slice is blocked.
2: Checksum over the code memory is not OK.
Sinamics G130 F34851 VSM DRIVE-CLiQ (CU): Sign-of-life missing A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Upgrade the firmware of the component involved.
Module (VSM) to the Control Unit.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex = 10 dec:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 F34860 VSM DRIVE-CLiQ (CU): Telegram error A DRIVE-CLiQ communications error has occurred from the Voltage Sensing - carry out a POWER ON.
Module (VSM) to the Control Unit. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
xx = 11 hex = 17 dec:
CRC error and the receive telegram is too early.
xx = 01 hex = 01 dec:
Checksum error (CRC error).
xx = 12 hex = 18 dec:
The telegram is shorter than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 02 hex = 02 dec:
Telegram is shorter than specified in the length byte or in the receive list.
xx = 13 hex = 19 dec:
The telegram is longer than that specified in the length byte or in the
receive list and the receive telegram is too early.

Sinamics G130 F34885 VSM DRIVE-CLiQ (CU): Cyclic data transfer error A DRIVE-CLiQ communications error has occurred from the Voltage Sensing - check the power supply voltage of the component involved.
Module (VSM) to the Control Unit. - carry out a POWER ON.
The nodes do not send and receive in synchronism. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
yyxx hex: yy = component number, xx = fault cause
xx = 1A hex = 26 dec:
Sign-of-life bit in the receive telegram not set and the receive telegram is
too early.
xx = 21 hex = 33 dec:
The cyclic telegram has not been received.
xx = 22 hex = 34 dec:
Timeout in the telegram receive list.
xx = 40 hex = 64 dec:
Timeout in the telegram send list.
xx = 62 hex = 98 dec:
Error at the transition to cyclic operation.

Sinamics G130 F34886 VSM DRIVE-CLiQ (CU): Error when sending A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Carry out a POWER ON.
DRIVE-CLiQ data Module (VSM) to the Control Unit.
Data were not able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.

Sinamics G130 F34887 VSM DRIVE-CLiQ (CU): Component fault Fault detected on the DRIVE-CLiQ component (Voltage Sensing Module) - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
involved. Faulty hardware cannot be - check the electrical cabinet design and cable routing for EMC compliance
excluded. - if required, use another DRIVE-CLiQ socket (p9904).
Fault value (r0949, interpret hexadecimal): - replace the component involved.C636
yyxx hex: yy = component number, xx = fault cause
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.
xx = 60 hex:
Response received too late during runtime measurement.
xx = 61 hex:
Time taken to exchange characteristic data too long.

Sinamics G130 F34895 VSM DRIVE-CLiQ (CU): Alternating cyclic data A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Carry out a POWER ON.
transfer error Module (VSM) to the Control Unit. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.
Sinamics G130 F34896 VSM DRIVE-CLiQ (CU): Inconsistent component The properties of the DRIVE-CLiQ component (Voltage Sensing Module), - when replacing cables, only use cables with the same length as the original
properties specified by the fault value, have changed cables.
in an incompatible fashion with respect to the properties when booted. - when replacing components, use the same components and firmware releases.
One cause can be, e.g. that a DRIVE-CLiQ - carry out a POWER ON.
cable or DRIVE-CLiQ component has been replaced.
Fault value (r0949, interpret decimal):
Component number.

Sinamics G130 F34899 (n,A) VSM: Unknown fault A fault occurred on the Voltage Sensing Module that cannot be interpreted - replace the firmware on the Voltage Sensing Module by an older firmware
by the Control Unit firmware. version (r0158).
This can occur if the firmware on this component is more recent than the - upgrade the firmware on the Control Unit (r0018).
firmware on the Control Unit.
Fault value (r0949, interpret decimal):
Fault number.
Note:
If required, the significance of this new fault can be read about in a more
recent description of the Control Unit.

Sinamics G130 F35000 TM54F: Sampling time invalid The set sampling time is invalid. Adapt the sampling time (e.g. set the recommended valid sampling time).
- not a multiple integer of the DP clock cycle. See also: p10000 (SI sampling time)
Fault value (r0949, floating point):
Recommended valid sampling time.

Sinamics G130 F35001 TM54F: Parameter value invalid The entered value is invalid. Correct the parameter value.
Fault value (r0949, interpret decimal):
Parameter number with the invalid value.

Sinamics G130 F35002 TM54F: Commissioning not possible The commissioning mode setting was rejected because for at least one Cancel the pulses for the drive specified in the fault value.
drive belonging to the TM54F, the pulses
had not been suppressed.
Fault value (r0949, interpret decimal):
Drive object number of the first drive found without pulse suppression.

Sinamics G130 F35003 TM54F: Acknowledgement on the Control Unit A fault on the Terminal Module 54F (TM54) was acknowledged using the
is required safe acknowledgement (P10006).
An additional acknowledgement is also required at the Control Unit.

Sinamics G130 F35011 TM54F: Drive object number assignment illegal A drive object number was assigned twice. Each drive object number can Correct the assignment of the drive object numbers.
be assigned only once. See also: p10010 (SI drive object assignment)
Sinamics G130 F35013 TM54F: Test stop error An error was detected when carrying out the test stop on the TM54F. As Check the wiring of the F-DIs and F-DOs and restart the test stop. The fault is
fault response fail-safe input terminal signals withdrawn if the test stop is successfully
are transferred to the motion monitoring functions. completed.
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
Sinamics G130 F35040 TM54F: 24 V undervoltage For the 24 V power supply for the Terminal Module 54F (TM54F) an - check the 24 V DC power supply for the TM54F.
undervoltage condition was detected. - carry out safe acknowledgement (p10006).
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.
Sinamics G130 F35043 TM54F: 24 V overvoltage For the 24 V power supply for the Terminal Module 54F (TM54F) an - check the 24 V DC power supply for the TM54F.
overvoltage condition was detected. - carry out safe acknowledgement (p10006).
As fault response fail-safe input terminal signals are transferred to the
motion monitoring functions.

Sinamics G130 F35051 TM54F: Defect in a monitoring channel The Terminal Module 54F (TM54F) has identified an error in the data cross Carry out the following steps on the TM54F:
check between the two control channels. - activate the safety commissioning mode (p0010 = 95).
As fault response fail-safe input terminal signals are transferred to the - start the copy function for SI parameters (p9700 = 57 hex).
motion monitoring functions. - acknowledge complete data change (p9701 = AC hex).
Fault value (r0949, interpret hexadecimal): - exit the safety commissioning mode (p0010 = 0).
aaaabbcc hex - save all parameters (p0977 = 1).
aaaa: A value greater than zero indicates an internal software error. - carry out safe acknowledgement (p10006).
bb: Data to be cross-checked that resulted in the error. For an internal software error (aaaa greater than zero):
bb = 00 hex: p10000 - upgrade the software on the TM54F.
bb = 01 hex: p10001 - contact the Hotline.
bb = 02 hex: p10002 - replace the TM54F.
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

Sinamics G130 F35052 (a) TM54F: Internal hardware fault An internal software/hardware fault on the TM54F was identified. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret decimal): - upgrade the software on the TM54F.
Only for internal Siemens troubleshooting. - contact the Hotline.
- replace the TM54F.

Sinamics G130 F35053 TM54F: Temperature fault threshold exceeded The temperature measured using the temperature sensing on the TM54F - allow the TM54F to cool down.
has exceeded the threshold value to initiate - carry out safe acknowledgement (p10006).
this fault.
As fault response fail-safe input terminal signals are transferred to the
motion monitoring functions.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.

Sinamics G130 F35150 TM54F: Communication error A communication error between the TM54F master and Control Unit or When replacing a Motor Module, carry out the following steps:
between the TM54F slave and the Motor - start the copy function for the node identifier on the TM54F (p9700 = 1D hex).
Module was detected. - acknowledge the hardware CRC on the TM54F (p9701 = EC hex).
Fault value (r0949, interpret hexadecimal): - save all parameters (p0977 = 1).
Only for internal Siemens troubleshooting. - carry out a POWER ON (power off/on) for all components.
The following always applies:
- check the electrical cabinet design and cable routing for EMC compliance
- upgrade the software on the TM54F.
- contact the Hotline.
- replace the TM54F.
Sinamics G130 F35151 TM54F: Discrepancy error The safety input terminals or output terminals show a different state longer Check the wiring of the F-DI and F-DO (contact problems).
than that parameterized in p10002. Note:
Fault value (r0949, interpret hexadecimal): A discrepancy of the F-DO also occurs (in this special case, in conjunction with
yyyyxxxx hex fault F35150 for the TM54F slave),
xxxx: if, after replacing a Motor Module, it was forgotten to acknowledge this.
The safety-relevant input terminals F-DI indicate a discrepancy. When replacing a Motor Module, carry out the following steps:
Bit 0: Discrepancy for F-DI 0 - start the copy function for the node identifier on the TM54F (p9700 = 1D hex).
... - acknowledge the hardware CRC on the TM54F (p9701 = EC hex).
Bit 9: Discrepancy for F-DI 9 - save all parameters (p0977 = 1).
yyyy: - carry out a POWER ON (power off/on) for all components.
The safety-relevant output terminals F-DO indicate a discrepancy. F-DI: Failsafe Digital Input
Bit 0: Discrepancy for F-DO 0 F-DO: Failsafe Digital Output
... Discrepancy errors of the F-DIs can only be completely acknowledged if, after
Bit 3: Discrepancy for F-DO 3 the cause of the error has been
Note: resolved, safe acknowledgement was carried out (refer to p10006). As long as
If several discrepancy errors occur consecutively, then this fault is only safety acknowledgement was not carried
signaled for the first error that occurs. out, the corresponding F-DI stays in the safe state.
The following possibilities exist of diagnosing all of the discrepancy errors:
- in the commissioning software, evaluate the input states and output
states of the TM54F. All discrepancy errors are
displayed here.
- compare parameters p10051 and p10052 from the TM54F master and
TM54F slave for discrepancy.

Sinamics G130 F35207 (N, A) TM: Temperature fault/alarm threshold The temperature measured using the temperature sensing of the Terminal - allow the temperature sensor to cool down.
exceeded Module (TM) (r4105) has exceeded the - if required, set the fault response to NONE (p2100, p2101).
threshold value to initiate this fault (p4102[1]) - or the temperature
exceeded the alarm threshold (p4102[0]) for longer
than the dead time in parameter p4103.
Please note that this fault can only be initiated if the temperature
evaluation was activated (p4100 = 2 for KTY sensor
or p4100 = 1 for PTC sensor).
Fault value (r0949, interpret decimal):
The hundred thousands and ten thousands location specifies the
component number of the TMxx where the fault
occurred.
Alarm:
Please note that Fault F35207 only causes the drive to be shut down if
there is at least one BICO interconnection
between the drive and TM31.

Sinamics G130 F35220 (N, A) TM: Frequency limit reached for signal output The signals output from the Terminal Module 41 (TM41) for tracks A/B SIMOTION (p4400 = 0) operating mode:
have reached the limit frequency. The output - enter a lower speed setpoint (p1155).
signals are no longer in synchronism with the specified setpoint. - reduce the encoder pulse number (p0408).
- if the TM41 is configured as technology object in SIMOTION, then this fault is
generated if the A/B signals in connector
X520 are short-circuited
SINAMICS (p4400 = 1) operating mode:
- the fine resolution of TM41 in p0418 does not match that of the connector
input that was interconnected at P4420
- the encoder position actual value r0479 interconnected at connector input
p4420 has an excessively high actual
speed

Sinamics G130 F35221 (N, A) TM: Setpoint - actual value deviation, outside The deviation between the setpoint and the output signals (track A/B) - reduce the basic clock cycle (p0110, p0111).
the tolerance range exceeds the tolerance of +/-3 %. Difference - replace the module.
between internal and external measured values is too high.

Sinamics G130 F35230 HW problem with the TM module The terminal module used has signaled an internal error. Signals of this The module must be replaced if no other alarms that refer to a communications
module may not be evaluated and are potentially error are present in the system.
incorrect.

Sinamics G130 F35233 DRIVE-CLiQ component does not support the A function requested by the Control Unit is not supported by a DRIVE-CLiQ Upgrade the firmware of the DRIVE-CLiQ component involved.
required function component. Re fault value = 1:
Fault value (r0949, interpret decimal): If the motor overtemperature time stage is to be used, the TM31 must be
1: This Terminal Module TM31 does not support the motor replaced. The order number of the replacement
overtemperature time stage. module should be 6SL3055-0AA00-3AA1 with software version V2.6 or higher..
Sinamics G130 F35820 TM DRIVE-CLiQ: Telegram error IMMEDIATELY - carry out a POWER ON.
A DRIVE-CLiQ communication error has occurred from the Terminal Module - check the electrical cabinet design and cable routing for EMC compliance
to the encoder involved. - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Fault value (r0949, interpret hexadecimal): See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.

Sinamics G130 F35835 TM DRIVE-CLiQ: Cyclic data transfer error A DRIVE-CLiQ communication error has occurred from the Terminal Module - carry out a POWER ON.
to the encoder involved. The nodes do - replace the component involved.
not send and receive in synchronism. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.

Sinamics G130 F35836 TM DRIVE-CLiQ: Send error for DRIVE-CLiQ data A DRIVE-CLiQ communication error has occurred from the Terminal Module Carry out a POWER ON.
to the encoder involved. Data were not
able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.

Sinamics G130 F35837 PTM DRIVE-CLiQ: Component fault Fault detected on the DRIVE-CLiQ component involved. Faulty hardware - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.

Sinamics G130 F35845 TM DRIVE-CLiQ: Cyclic data transfer error A DRIVE-CLiQ communication error has occurred from the Terminal Module Carry out a POWER ON.
(TM) to the encoder involved. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F35850 TM: Internal software error An internal software error in the Terminal Module (TM) has occurred. - replace the Terminal Module (TM).
Fault value (r0949, interpret decimal): - if required, upgrade the firmware in the Terminal Module.
1: Background time slice is blocked. - contact the Hotline.
2: Checksum over the code memory is not OK.
Sinamics G130 F35851 TM DRIVE-CLiQ (CU): Sign-of-life missing A DRIVE-CLiQ communication error has occurred from the Terminal Module Upgrade the firmware of the component involved.
(TM) to the Control Unit involved.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex = 10 dec:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 F35860 TM DRIVE-CLiQ (CU): Telegram error A DRIVE-CLiQ communication error has occurred from the Terminal Module - carry out a POWER ON.
(TM) to the Control Unit involved. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
xx = 11 hex = 17 dec:
CRC error and the receive telegram is too early.
xx = 01 hex = 01 dec:
Checksum error (CRC error).
xx = 12 hex = 18 dec:
The telegram is shorter than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 02 hex = 02 dec:
Telegram is shorter than specified in the length byte or in the receive list.
xx = 13 hex = 19 dec:
The telegram is longer than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 03 hex = 03 dec:
Telegram is longer than specified in the length byte or in the receive list.
xx = 14 hex = 20 dec:
The length of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 04 hex = 04 dec:
The length of the receive telegram does not match the receive list.
xx = 15 hex = 21 dec:
The type of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 05 hex = 05 dec:
The type of the receive telegram does not match the receive list.
xx = 16 hex = 22 dec:
The address of the power unit in the telegram and in the receive list does
not match and the receive telegram is too
early.
xx = 06 hex = 06 dec:
The address of the power unit in the telegram and in the receive list do not
match.

Sinamics G130 F35885 TM DRIVE-CLiQ (CU): Cyclic data transfer error A DRIVE-CLiQ communication error has occurred from the Terminal Module - check the power supply voltage of the component involved.
(TM) to the Control Unit involved. - carry out a POWER ON.
The nodes do not send and receive in synchronism. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
yyxx hex: yy = component number, xx = fault cause
xx = 1A hex = 26 dec:
Sign-of-life bit in the receive telegram not set and the receive telegram is
too early.
xx = 21 hex = 33 dec:
The cyclic telegram has not been received.
xx = 22 hex = 34 dec:
Timeout in the telegram receive list.
xx = 40 hex = 64 dec:
Timeout in the telegram send list.
xx = 62 hex = 98 dec:
Error at the transition to cyclic operation.

Sinamics G130 F35886 TM DRIVE-CLiQ (CU): Error when sending A DRIVE-CLiQ communication error has occurred from the Terminal Module Carry out a POWER ON.
DRIVE-CLiQ data (TM) to the Control Unit involved.
Data were not able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.
Sinamics G130 F35887 TM DRIVE-CLiQ (CU): Component fault Fault detected on the DRIVE-CLiQ component (Terminal Module) involved. - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Faulty hardware cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.
xx = 60 hex:
Response received too late during runtime measurement.
xx = 61 hex:
Time taken to exchange characteristic data too long.

Sinamics G130 F35895 TM DRIVE-CLiQ (CU): Alternating cyclic data A DRIVE-CLiQ communication error has occurred from the Terminal Module Synchronization error during alternating cyclic data transfer.
transfer error (TM) to the Control Unit involved. Carry out a POWER ON.
Fault value (r0949, interpret hexadecimal): See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F35896 TM DRIVE-CLiQ (CU): Inconsistent component The properties of the DRIVE-CLiQ component (Terminal Module), specified - when replacing cables, only use cables with the same length as the original
properties by the fault value, have changed in an cables.
incompatible fashion with respect to the properties when booted. One - when replacing components, use the same components and firmware releases.
cause can be, e.g. that a DRIVE-CLiQ cable - carry out a POWER ON.
or DRIVE-CLiQ component has been replaced.
Fault value (r0949, interpret decimal):
Component number.

Sinamics G130 F35899 (N,A) TM: Unknown fault A fault has occurred on the Terminal Module that cannot be interpreted by - replace the firmware on the Terminal Module by an older firmware version
the Control Unit firmware. (r0158).
This can occur if the firmware on this component is more recent than the - upgrade the firmware on the Control Unit (r0018).
firmware on the Control Unit.
Fault value (r0949, interpret decimal):
Fault number.
Note:
If required, the significance of this new fault can be read about in a more
recent description of the Control Unit.

Sinamics G130 F36207 (N,A) Hub: Overtemperature component Temperature on DRIVE-CLiQ Hub Module has exceeded fault threshold. - Check ambient temperature at component installation location.
Fault value (r0949, interpret decimal): - replace the component involved.
Current temperature in 0.1°C resolution.

Sinamics G130 F36214 Hub: overvoltage fault 24 V supply 24 V power supply on DRIVE-CLiQ Hub Module has exceeded fault - check the supply voltage of the component involved.
threshold. - replace the component involved.C674
Fault value (r0949, interpret decimal):
Current operating voltage in 0.1 °C resolution.

Sinamics G130 F36216 Hub: undervoltage fault 24 V supply 24 V power supply on DRIVE-CLiQ Hub Module has undershot fault - check the supply voltage of the component involved.
threshold. - replace the component involved.
Fault value (r0949, interpret decimal):
Current operating voltage in 0.1 °C resolution.

Sinamics G130 F36802 (N,A) Hub: Time slice overflow A time slice overflow has occurred on the DRIVE-CLiQ Hub Module. - reduce the current controller frequency.
Fault value (r0949, interpret decimal): - carry out a POWER ON (power off/on) for all components.
xx: Time slice number xx - upgrade firmware to later version.
- contact the Hotline.
Sinamics G130 F36820 Hub DRIVE-CLiQ: Telegram error DRIVE-CLiQ communication error from Control Unit to DRIVE-CLiQ Hub - carry out a POWER ON.- carry out a POWER ON.
Module in question. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
xx = 01 hex = 1 dec:
Checksum error (CRC error).
xx = 02 hex = 2 dec:
Telegram is shorter than specified in the length byte or in the receive list.
xx = 03 hex = 3 dec:
Telegram is longer than specified in the length byte or in the receive list.
xx = 04 hex = 4 dec:
The length of the receive telegram does not match the receive list.
xx = 05 hex = 5 dec:
The type of the receive telegram does not match the receive list.
xx = 06 hex = 6 dec:
The address of the component in the telegram and in the receive list do not
match.
xx = 07 hex = 7 dec:
A SYNC telegram is expected - but the receive telegram is not a SYNC
telegram.
xx = 08 hex = 8 dec:
No SYNC telegram is expected - but the receive telegram is one.
xx = 09 hex = 9 dec:
The error bit in the receive telegram is set.
xx = 10 hex = 16 dec:
The receive telegram is too early.

Sinamics G130 F36835 Hub DRIVE-CLiQ: Cyclic data transfer error DRIVE-CLiQ communication error from Control Unit to DRIVE-CLiQ Hub - carry out a POWER ON.
Module in question. The nodes do not send - replace the component involved.
and receive in synchronism. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 21 hex = 33 dec:
The cyclic telegram has not been received.
xx = 22 hex = 34 dec:
Timeout in the telegram receive list.
xx = 40 hex = 64 dec:
Timeout in the telegram send list.

Sinamics G130 F36836 Hub DRIVE-CLiQ: Send error for DRIVE-CLiQ DRIVE-CLiQ communication error from Control Unit to DRIVE-CLiQ Hub Carry out a POWER ON.
data Module in question. Data were not able to
be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex = 65 dec:
Telegram type does not match send list.

Sinamics G130 F36837 Hub DRIVE-CLiQ: Component fault Fault detected on the DRIVE-CLiQ component involved. Faulty hardware - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex = 32 dec:
Error in the telegram header.
xx = 23 hex = 35 dec:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex = 66 dec:
Send error: The telegram buffer memory contains an error.
xx = 43 hex = 67 dec:
Send error: The telegram buffer memory contains an error.

Sinamics G130 F36845 Hub DRIVE-CLiQ: Cyclic data transfer error DRIVE-CLiQ communication error from Control Unit to DRIVE-CLiQ Hub Carry out a POWER ON.
Module in question. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex = 11 dec:
Synchronization error during alternating cyclic data transfer.
Sinamics G130 F36851 Hub DRIVE-CLiQ (CU): Sign-of-life missing DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question Upgrade the firmware of the component involved.
to Control Unit.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex = 10 dec:
The sign-of-life bit in the receive telegram is not set.

Sinamics G130 F36860 Hub DRIVE-CLiQ (CU): Telegram error DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question - carry out a POWER ON.
to Control Unit. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause
xx = 11 hex = 17 dec:
Checksum error (CRC error) and receive telegram is too early.
xx = 01 hex = 01 dec:
Checksum error (CRC error).
xx = 12 hex = 18 dec:
The telegram is shorter than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 02 hex = 02 dec:
Telegram is shorter than specified in the length byte or in the receive list.
xx = 13 hex = 19 dec:
The telegram is longer than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 03 hex = 03 dec:
Telegram is longer than specified in the length byte or in the receive list.
xx = 14 hex = 20 dec:
The length of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 04 hex = 04 dec:
The length of the receive telegram does not match the receive list.
xx = 15 hex = 21 dec:
The type of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 05 hex = 05 dec:
The type of the receive telegram does not match the receive list.

Sinamics G130 F36885 Hub DRIVE-CLiQ (CU): Cyclic data transfer error DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question - Check supply voltage of component involved.
to Control Unit. - carry out a POWER ON.
The nodes do not send and receive in synchronism. - replace the component involved.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 1A hex = 26 dec:
Sign-of-life bit in the receive telegram not set and the receive telegram is
too early.
xx = 21 hex = 33 dec:
The cyclic telegram has not been received.
xx = 22 hex = 34 dec:
Timeout in the telegram receive list.
xx = 40 hex = 64 dec:
Timeout in the telegram send list.
xx = 62 hex = 98 dec:
Error at the transition to cyclic operation.

Sinamics G130 F36886 Hub DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question Carry out a POWER ON.
DRIVE-CLiQ data to Control Unit.
Data were not able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex = 65 dec:
Telegram type does not match send list.
Sinamics G130 F36887 Hub DRIVE-CLiQ (CU): Component fault Fault detected on the DRIVE-CLiQ component (DRIVE-CLiQ Hub Module) - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
involved. Faulty hardware cannot be - check the electrical cabinet design and cable routing for EMC compliance
excluded. - if required, use another DRIVE-CLiQ socket (p9904).
Fault value (r0949, interpret hexadecimal): - replace the component involved.
yyxx hex: yy = component number, xx = fault cause
xx = 20 hex = 32 dec:
Error in the telegram header.
xx = 23 hex = 35 dec:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex = 66 dec:
Send error: The telegram buffer memory contains an error.
xx = 43 hex = 67 dec:
Send error: The telegram buffer memory contains an error.
xx = 60 hex = 96 dec:
Response received too late during runtime measurement.
xx = 61 hex = 97 dec:
Time taken to exchange characteristic data too long.

Sinamics G130 F36895 Hub DRIVE-CLiQ (CU): Alternating cyclic data DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question Carry out a POWER ON.
transfer error to Control Unit. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex = 11 dec:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F36896 Hub DRIVE-CLiQ (CU): Inconsistent component The properties of the DRIVE-CLiQ component (DRIVE-CLiQ Hub Module) - when replacing cables, only use cables with the same length as the original
properties specified by the fault value have changed cables.
in an incompatible fashion with respect to the properties when booted. - when replacing components, use the same components and firmware releases.
One cause can be, e.g. that a DRIVE-CLiQ - carry out a POWER ON.
cable or DRIVE-CLiQ component has been replaced.
Fault value (r0949, interpret decimal):
Component number.

Sinamics G130 F36899 (N,A) Hub: Unknown fault A fault occurred on the DRIVE-CLiQ Hub Module that cannot be interpreted - Replace the firmware on the DRIVE-CLiQ Hub Module with older firmware
by the Control Unit firmware. (r0158).
This can occur if the firmware on this component is more recent than the - upgrade the firmware on the Control Unit (r0018).C689
firmware on the Control Unit.
Fault value (r0949, interpret decimal):
Fault number.
Note:
If required, the significance of this new fault can be read about in a more
recent description of the Control Unit.

Sinamics G130 F40000 Fault at DRIVE-CLiQ socket X100 A fault has occurred at the drive object at the DRIVE-CLiQ socket X100. Evaluate the fault buffer of the specified object.
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.

Sinamics G130 F40001 Evaluate the fault buffer of the specified object. A fault has occurred at the drive object at the DRIVE-CLiQ socket X101. Evaluate the fault buffer of the specified object.
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.

Sinamics G130 F40002 Fault at DRIVE-CLiQ socket X102 A fault has occurred at the drive object at the DRIVE-CLiQ socket X102. Evaluate the fault buffer of the specified object.
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.

Sinamics G130 F40003 Fault at DRIVE-CLiQ socket X103 A fault has occurred at the drive object at the DRIVE-CLiQ socket X103. Evaluate the fault buffer of the specified object.
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.

Sinamics G130 F40004 Fault at DRIVE-CLiQ socket X104 A fault has occurred at the drive object at the DRIVE-CLiQ socket X104. Evaluate the fault buffer of the specified object.
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.

Sinamics G130 F40005 Fault at DRIVE-CLiQ socket X105 A fault has occurred at the drive object at the DRIVE-CLiQ socket X105. Evaluate the fault buffer of the specified object..
Fault value (r0949, interpret decimal):
First fault that has occurred for this drive object.

Sinamics G130 F40799 CX32: Configured transfer end time exceeded The configured transfer end time when transferring the cyclic actual values - carry out a POWER ON (power off/on) for all components.
was exceeded. - contact the Hotline.
Sinamics G130 F40801 CX32 DRIVE-CLiQ: Sign-of-life missing A DRIVE-CLiQ communications error has occurred from the Control Unit to - carry out a POWER ON.
the controller extension involved. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
yyxx hex: yy = component number, xx = fault cause
xx = 0A hex:
The sign-of-life bit in the receive telegram is not set.
Sinamics G130 F40820 CX32 DRIVE-CLiQ: Telegram error A DRIVE-CLiQ communications error has occurred from the Control Unit to - carry out a POWER ON.
the controller extension involved. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.

Sinamics G130 F40835 CX32 DRIVE-CLiQ: Cyclic data transfer error A DRIVE-CLiQ communications error has occurred from the Control Unit to - carry out a POWER ON.
the controller extension involved. The - replace the component involved.
nodes do not send and receive in synchronism. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
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.

Sinamics G130 F40836 CX32 DRIVE-CLiQ: Send error for DRIVE-CLiQ A DRIVE-CLiQ communications error has occurred from the Control Unit to Carry out a POWER ON.
data the controller extension involved. Data
were not able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.

Sinamics G130 F40837 CX32 DRIVE-CLiQ: Component fault Fault detected on the DRIVE-CLiQ component involved. Faulty hardware - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.

Sinamics G130 F40845 CX32 DRIVE-CLiQ: Cyclic data transfer error A DRIVE-CLiQ communications error has occurred from the Control Unit to Carry out a POWER ON.
the controller extension involved. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.
Sinamics G130 F40851 CX32 DRIVE-CLiQ (CU): Sign-of-life missing A DRIVE-CLiQ communications error has occurred from the controller Upgrade the firmware of the component involved.
extension involved to the Control Unit.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
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.

Sinamics G130 F40860 CX32 DRIVE-CLiQ (CU): Telegram error A DRIVE-CLiQ communications error has occurred from the controller - carry out a POWER ON.
extension involved to the Control Unit. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
yyxx hex: yy = component number, xx = fault cause See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
xx = 11 hex:
CRC error and the receive telegram is too early.
xx = 01 hex:
CRC error.
xx = 12 hex:
The telegram is shorter than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 02 hex:
Telegram is shorter than specified in the length byte or in the receive list.
xx = 13 hex:
The telegram is longer than that specified in the length byte or in the
receive list and the receive telegram is too early.
xx = 03 hex:
Telegram is longer than specified in the length byte or in the receive list.
xx = 14 hex:
The length of the receive telegram does not match the receive list and the
receive telegram is too early.
xx = 04 hex:
The length of the receive telegram does not match the receive list.

Sinamics G130 F40885 CX32 DRIVE-CLiQ (CU): Cyclic data transfer A DRIVE-CLiQ communications error has occurred from the controller - check the power supply voltage of the component involved.
error extension involved to the Control Unit. - carry out a POWER ON.
The nodes do not send and receive in synchronism. - replace the component involved.
Fault value (r0949, interpret hexadecimal): See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
yyxx hex: yy = component number, xx = fault cause
xx = 1A hex:
Sign-of-life bit in the receive telegram not set and the receive telegram is
too early.
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.
xx = 62 hex:
Error at the transition to cyclic operation.

Sinamics G130 F40886 CX32 DRIVE-CLiQ (CU): Error when sending A DRIVE-CLiQ communications error has occurred from the controller Carry out a POWER ON.
DRIVE-CLiQ data extension involved to the Control Unit.
Data were not able to be sent.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 41 hex:
Telegram type does not match send list.
Sinamics G130 F40887 CX32 DRIVE-CLiQ (CU): Component fault Fault detected on the DRIVE-CLiQ component involved. Faulty hardware - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
cannot be excluded. - check the electrical cabinet design and cable routing for EMC compliance
Fault value (r0949, interpret hexadecimal): - if required, use another DRIVE-CLiQ socket (p9904).
yyxx hex: yy = component number, xx = fault cause - replace the component involved.
xx = 20 hex:
Error in the telegram header.
xx = 23 hex:
Receive error: The telegram buffer memory contains an error.
xx = 42 hex:
Send error: The telegram buffer memory contains an error.
xx = 43 hex:
Send error: The telegram buffer memory contains an error.
xx = 60 hex:
Response received too late during runtime measurement.
xx = 61 hex:
Time taken to exchange characteristic data too long.

Sinamics G130 F40895 CX32 DRIVE-CLiQ (CU): Cyclic data transfer A DRIVE-CLiQ communications error has occurred from the controller Carry out a POWER ON.
error extension involved to the Control Unit. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master)
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = component number, xx = fault cause
xx = 0B hex:
Synchronization error during alternating cyclic data transfer.

Sinamics G130 F49150 Cooling system: Fault occurred The cooling system signals a general fault. - 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)

Sinamics G130 F49151 Cooling system: Conductivity has exceeded the The conductivity of the cooling liquid has exceeded the selected fault Check the device to de-ionize the cooling liquid.
fault threshold 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)

Sinamics G130 F49152 Cooling system: ON command feedback signal The feedback signal of the ON command of the cooling system is missing. - check the wiring between the cooling system and the input terminal (Terminal
missing - after the ON command, the feedback signal has not been received within Module).
the selected starting time (p0260). - check the external control device for the cooling system.
- the feedback signal has failed in operation.
See also: p0260 (Cooling system, starting time 1), r0267 (Cooling system
status word)

Sinamics G130 F49153 Cooling system: Liquid flow too low The drive converter cooling system signals that the cooling liquid flow is too - check the wiring between the cooling system and the input terminal (Terminal
low. Module).
- after the ON command, the feedback signal has not been received within - check the external control device for the cooling system.
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)

Sinamics G130 F49154 (A) Cooling system: Liquid leak is present The liquid leakage monitoring function has responded. - check the cooling system for leaks in the cooling circuit.
Caution: - check the wiring of the input terminal (terminal Module) used to monitor
Before this fault is re-parameterized as an alarm, you must ensure that the leaking fluid.
drive is shut down if cooling water is lost.
See also: r0267 (Cooling system status word)

Sinamics G130 F49155 Cooling system: Power Stack Adapter, POWER ON Upgrade the firmware. Check EEPROM data.
firmware version too old The firmware version in the Power Stack Adapter (PSA) is too old and does
not support the liquid cooling.

Sinamics G130 F49156 Cooling system: Cooling liquid temperature has The cooling liquid intake temperature has exceeded the permanently set Check the cooling system and the ambient conditions.
exceeded the fault threshold fault threshold.
Sinamics G130 F49200 Excitation group signal fault The excitation sequence control signals a fault. - check the excitation.
Fault value (r0949, hexadecimal): - check commands, feedback signals and BICO interconnections.
Bit 0:
When powered down or when powering down the excitation, the signal
"excitation ready to be powered up feedback
signal" was not received within the monitoring time.
Bit 1:
After an ON command, the signal "excitation ready feedback signal" was
not received within the monitoring time.
Bit 2:
After the pulses were enabled, the signal "excitation operational feedback
signal" was not received within the monitoring
time.
Bit 3:
The "excitation group signal fault" signal is present.

Sinamics G130 N01004 (F,A) Internal software error An internal software error has occurred. - read out diagnostics parameter (r9999).
Fault value (r0949, hexadecimal): - contact the Hotline.
Only for internal Siemens troubleshooting. See also: r9999 (Software error internal supplementary diagnostics)

Sinamics G130 N01620 (F, A) SI CU: Safe Torque Off active The "Safe Torque Off" (STO) function has been selected on the Control Unit None necessary.
(CU) using the input terminal and is Note:
active. CU: Control Unit
Note: SI: Safety Integrated
This message does not result in a safety stop response. STO: Safe Torque Off / SH: Safe standstill

Sinamics G130 N01621 (F, A) SI CU: Safe Stop 1 active The "Safe Stop 1" (SS1) function has been selected on the Control Unit (CU) None necessary.
and is active. Note:
Note: CU: Control Unit
This message does not result in a safety stop response. SI: Safety Integrated
SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)

Sinamics G130 N05007 (A) Power unit: Overtemperature thermal model The temperature difference between the chip and heat sink has exceeded None necessary. The alarm automatically disappears when the limit value is
(chassis PU) the permissible limit value (r0293) (for undershot.
chassis power units only). Depending on p0290, a suitable overload See also: p0290 (Power unit overload response)
response is initiated.
See also: r0037, r0293 (Power unit alarm threshold model temperature)

Sinamics G130 N30620 (F,N) SI MM: Safe Torque Off active The "Safe Torque Off" function was selected on the Motor Module (MM) None necessary.
via the input terminal and is active. Note:
Note: MM: Motor Module
This message does not result in a safety stop response. SI: Safety Integrated
STO: Safe Torque Off / SH: Safe standstill

Sinamics G130 N30621 (F,N) SI MM: Safe Stop 1 active The "Safe Stop 1" function (SS1) was selected on the Motor Module (MM) None necessary.
and is active. Note:
Note: MM: Motor Module
This message does not result in a safety stop response. SI: Safety Integrated
SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)

Sinamics G130 N30800 (F) Power unit: Group signal The power unit has detected at least one fault. Evaluates other current messages.
Sinamics G130 N31415 (F,A) Encoder 1: Amplitude error track A/B alarm The amplitude (root of A^2 + B^2) for encoder 1 exceeds the permissible - check the speed range, frequency characteristic (amplitude characteristic) of
(A^2 + B^2) tolerance. the measuring equipment is not sufficient
Alarm value (r2124, interpret hexadecimal): for the speed range.
yyyyxxxx hex: - check that the encoder cables and shielding are routed in compliance with
yyyy = Angle EMC.
xxxx = Amplitude, i.e. root from A^2 + B^2 (16 bits without sign) - check the plug connections.
The nominal signal level of the encoder must lie in the range 375 mV to 600 - replace the encoder or encoder cable.
mV (500 mV -25/+20 %). - check the Sensor Module (e.g. contacts).
The response threshold is < 300 mV (observe the frequency response of the - if the coding disk is soiled or the lighting worn, replace the encoder.D981
encoder).
A signal level of 500 mV peak value corresponds to the numerical value
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 for sensors modules for resolvers (e. g. SMC10):
The nominal signal level is at 2900 mV (2.0 Vrms). The response threshold
is < 1414 mV (1.0 Vrms).
A signal level of 2900 mV peak value corresponds to the numerical value of
3333 hex = 13107 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)
Sinamics G130 N32415 (F,A) Encoder 2: Amplitude error track A/B alarm The amplitude (root of A^2 + B^2) for encoder 2 exceeds the permissible - check the speed range, frequency characteristic (amplitude characteristic) of
(A^2 + B^2) tolerance. the measuring equipment is not sufficient
Alarm value (r2124, interpret hexadecimal): for the speed range.
yyyyxxxx hex: - check that the encoder cables and shielding are routed in compliance with
yyyy = Angle EMC.
xxxx = Amplitude, i.e. root from A^2 + B^2 (16 bits without sign) - check the plug connections.
The nominal signal level of the encoder must lie in the range 375 mV to 600 - replace the encoder or encoder cable.
mV (500 mV -25/+20 %). - check the Sensor Module (e.g. contacts).
The response threshold is < 300 mV (observe the frequency response of the - if the coding disk is soiled or the lighting worn, replace the encoder.
encoder).
A signal level of 500 mV peak value corresponds to the numerical value
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 for sensors modules for resolvers (e. g. SMC10):
The nominal signal level is at 2900 mV (2.0 Vrms). The response threshold
is < 1414 mV (1.0 Vrms).
A signal level of 2900 mV peak value corresponds to the numerical value of
3333 hex = 13107 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.

Sinamics G130 N32800 (F) Encoder 2: Group signal The motor encoder has detected at least one fault. Evaluates other current messages.
Sinamics G130 N33415 (F,A) Encoder 3: Amplitude error track A/B alarm The amplitude (root of A^2 + B^2) for encoder 3 exceeds the permissible - check the speed range, frequency characteristic (amplitude characteristic) of
(A^2 + B^2) tolerance. the measuring equipment is not sufficient
Alarm value (r2124, interpret hexadecimal): for the speed range.
yyyyxxxx hex: - check that the encoder cables and shielding are routed in compliance with
yyyy = Angle EMC.
xxxx = Amplitude, i.e. root from A^2 + B^2 (16 bits without sign) - check the plug connections.
The nominal signal level of the encoder must lie in the range 375 mV to 600 - replace the encoder or encoder cable.
mV (500 mV -25/+20 %). - check the Sensor Module (e.g. contacts).
The response threshold is < 300 mV (observe the frequency response of the - if the coding disk is soiled or the lighting worn, replace the encoder.
encoder).
A signal level of 500 mV peak value corresponds to the numerical value
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 for sensors modules for resolvers (e. g. SMC10):
The nominal signal level is at 2900 mV (2.0 Vrms). The response threshold
is < 1414 mV (1.0 Vrms).
A signal level of 2900 mV peak value corresponds to the numerical value of
3333 hex = 13107 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.

Sinamics G130 N33800 (F) Encoder 3: Group signal The motor encoder has detected at least one fault. Evaluates other current messages.
Sinamics G130 N34800 (F) VSM: Group signal VSM: Group signal Evaluates other current messages.
Sinamics G130 N35800 (F) TM: Group signal The Terminal Module has detected at least one fault. Evaluates other current messages.
Sinamics G130 N36800 (F) Hub: group signal The DRIVE-CLiQ Hub Module has detected at least one fault. Evaluates other current messages.
Vacon "Blank Screen" All Mk III Elektronikons No power to display of Elektronikon Faulty Board, loose connections (ribbon cables) inside. Check the module for loose connection.
If no loose connection is found, chances are the diode that controls the power supply to
the display is gone. It is not recommended to repair them, because whilst repairing,
there is a chance of disturbing neighbour

Vacon 10 Elektronikon Mk III, LRR Relay outputs read-back error Relay damaged, internal error - Power down the regulator.
V1.8, 2.3 - Inconsistency between the status of the relays and Unrecoverable failures generated by the regulator. - Check the Emergency stop button.
the status the relays should be in - Compressor is running or standing still. Regulator is powered up. Only one * Make sure all wires connected firmly and no bad contacts are existing.
HRR contact (out of three) of the Emergency stop button is activated. This means that * All the components of the Emergency stop button (base and contacts) should have
the power suppl the same colour (black or brow

Vacon 100 Elektronikon Mk III, LRR Register file error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III, if all else fails
V1.8, 2.3
Vacon 101 Elektronikon Mk III, LRR RAM error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III, if all else fails
V1.8, 2.3
Vacon 102 Elektronikon Mk III, LRR 12V relay not disabled at power on Relay possible damaged due to incorrect power input Replace Elektronikon Mk III, if all else fails
V1.8, 2.3
Vacon 103 Elektronikon Mk III, LRR Relays status uncorrect at power on Relay possible damaged due to incorrect power input Replace Elektronion, if all else fails
V1.8, 2.3 Unrecoverable failures generated by the regulator.
Vacon 104 Elektronikon Mk III LRR V1.8, Short circuit on 12V (relays and digital inputs) OR In Most cases, attributed to a voltage coming in through one of the digital inputs. These failures are used to signal some dangerous situation caused by hardware or
2.3, HRR 12V enabling FET damaged But digital inputs are voltage free contacts. software problems.

Chances are FET, and or diodes had gone. Possible what happen here is when the Check 2x1 connector. Possibly, the FET, inductor (the green resistor lookalike), or diode
connector is put upside down, and when 24V is gone here, due to reverse biased of power.
Also, check othe

Vacon 106 Elektronikon Mk III, LRR Relays enable at power on Relay possible damaged due to incorrect power input - Power down the regulator.
V1.8, 2.3 - Inconsistency between the status of the relays and - Elektronikon is not powered up. Only one contact (out of three) of the Emergency - Check the Emergency stop button.
HRR the status that the relay should be in. stop button is activated. Power is restored to the Elektronikon. At this moment the * Make sure all wires connected firmly and no bad contacts are existing.
power supply to the internal relays * All the components of the Emergency stop button (base and contacts) should have
the same colour (black or brow

Vacon 107 Elektronikon Mk III, LRR Serial line error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III, if all else fails
V1.8, 2.3
Vacon 108 Elektronikon Mk III, LRR Keyboard error Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III, if all else fails
V1.8, 2.3
Vacon 109 Elektronikon Mk III, LRR V Filter error (relay ouputs read-back not stable)
2.3
Vacon 10XX Elektronikon Mk III - (Online) Read back output error
LRR/HRR
Vacon 11 Elektronikon Mk III, LRR V1.8: Most porbably due to a short circuit of the 12V supply for the digital inputs For example, when this module being use for remote control. As two digital inputs were
V1.8, 2.3, HRR EEprom not writable Unrecoverable failures generated by the regulator. closed, please check which one is causing the failure 11. Is it the CMS 2 as from when it is
V2.3: closed or is it 30 & 34 contact.
Relays supply error
If nothing is found, then change the mod

Vacon 11XX Elektronikon Mk III - HRR (Online) 12V short circuit or FET to enable damaged

Vacon 12 Elektronikon Mk III, LRR V1.8: Unrecoverable failures generated by the regulator. Hardware or software problem
V1.8, 2.3 Division by zero Replace Elektronikon Mk III
V2.3:
EEprom not writable

Vacon 13 Elektronikon Mk III, LRR V1.8: Unrecoverable failures generated by the regulator. Hardware or software problem
V1.8, 2.3 Wrong active display, V2.3: Replace Elektronikon Mk III
EEprom checksum error
Vacon 14 Elektronikon Mk III, LRR V1.8: Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III
V1.8, 2.3 Relays supply error, V2.3: Internal error
Eprom checksum error
Vacon 15 Elektronikon Mk III, LRR V Wrong active display Unrecoverable failures generated by the regulator. Replace Elektronikon Mk III
2.3
Vacon 17 Elektronikon Mk III, LRR V1.8 Watch dog error Some external conditions were not met while system was checking for operation. 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
Recoverable failure. through the reset function key of the system failure display.
Check external par

Vacon 200 Elektronikon Mk III, LRR V Watch dog error. 200XX (bootstrap) These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR compressor can start after the failure reset. failure display.
Vacon 2000 Elektronikon Mk III - (Bootstrap) Reserved area checksum incorrect Hardware or software problem. Possibly need a new regulator
LRR/HRR
Vacon 2001 Elektronikon Mk III - HRR (Bootstrap) Reserved area checksum incorrect Unrecoverable error. Caused by corruption within the electronics to misread. Try to power OFF and ON again. If cannot resolved, then try a new module.

Vacon 201 Elektronikon Mk III, LRR V Internal power failure routine not completed These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR 201xx(bootstrap) compressor can start after the failure reset. failure display.
Vacon 202 Elektronikon Mk III, LRR V Backupped RAM checksum error These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
2.3, HRR 202xx(bootstrap) compressor can start after the failure reset. failure display.
Vacon 203 Elektronikon Mk III - HRR Power off during EEPROM writing These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
203xx (bootstrap) compressor can start after the failure reset. failure display.
Vacon 204 Elektronikon Mk III - HRR Power off during EEPROM writing and power failure These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
interrupt routine enabled compressor can start after the failure reset. failure display.
204xx(bootstrap)
Vacon 205 Elektronikon Mk III - HRR Power off during EEPROM writing and backup ram These failures are used to signal some critical, but not disastrous situation. The It is possible to clear this kind of failure through the reset function key of the system
checksum incorrect. compressor can start after the failure reset. failure display.
Vacon 20XX Elektronikon Mk III - HRR (Bootstrap) Reserved area checksum incorrect
Vacon 21XX Elektronikon Mk III - HRR (Bootstrap) EPROM checksum incorrect
Vacon 22 Elektronikon Mk III, LRR V1.8 Eprom checksum error Internal error Replace Elektronikon Mk III, if all else fails
Unrecoverable failures generated by the regulator.
Vacon 22XX Elektronikon Mk III - HRR (Bootstrap) Flash checksum incorrect
Vacon 30XX Elektronikon Mk III - HRR (Online) Division by 0
Vacon 31XX Elektronikon Mk III - HRR (Online) Wrong activated display
Vacon 33 Elektronikon Mk III, LRR V1.8 Eeprom checksum error Internal error Replace Elektronikon Mk III, if all else fails
Unrecoverable failures generated by the regulator.
Vacon 40 Elektronikon Mk III - HRR (Autoconfig) No delivery air input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Vacon 41 Elektronikon Mk III - HRR (Autoconfig) More than 1 delivery air input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Vacon 42 Elektronikon Mk III - HRR (Autoconfig) More than 1 backup pressure input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Vacon 43 Elektronikon Mk III - HRR (Autoconfig) More than 1 intercooler pressure input These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.
Vacon 44 Elektronikon Mk III - HRR (Autoconfig) More than 4 DIOE modules connected These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Vacon 45 Elektronikon Mk III - HRR (Autoconfig) More than 4 SIOE modules connected These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Vacon 46 Elektronikon Mk III - HRR (Autoconfig) More than 3 COM1 modules These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
connected one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Vacon 47 Elektronikon Mk III - HRR (Autoconfig) More than 2 COM3 modules These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
connected one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Vacon 48 Elektronikon Mk III - HRR (Autoconfig) COM3 not permitted in configuration These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Vacon 49 Elektronikon Mk III - HRR (Autoconfig) SIOE module not permitted in These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
configuration one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Vacon 50 Elektronikon Mk III - HRR (Autoconfig) Wrong CCM during autoconfiguration These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
(CMS1, CMS2) one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.

Please check to make sure CMS is in correct position

Vacon 51 Elektronikon Mk III - HRR (Autoconfig) DIOE type configured is for ES100 These failures are generated after the autoconfiguration start. They indicate that To proceed with the autoconfiguration, it is necessary to remove the condition(s) and to
system one or more conditions, checked during the autoconfiguration phase, are not valid. restart the autoconfiguration.
Please check for the right module.

Vacon A15 Vacon VSD Motor stalled (Motor stall protection) Check Motor
Vacon A16 Vacon VSD Motor Overtemperature (Motor thermal protection) Decrease motor loading
Vacon A17 Vacon VSD Motor Underload (Warning can be activated in Five In One applications) (not sure what is going on Check motor loading
here !!)
Vacon A24 Vacon VSD Stored Data has been changed The values in the Fault History, MWh counters or operating day/hour counters No actions necessary. Take a critical attitude to these values
might have been changed in the previous mains interruption
Vacon A28 Vacon VSD Changed Application failed The change of application has failed Choose the application again and push the ENTER button
Vacon A30 Vacon VSD Unbalance current fault The load of the segments is not equal Contact Vacon
Vacon A45 Vacon VSD Overtemperature The converter overtemperature warning: Overtemp. Trip limit minus 5 deg. C Check the cooling air flow and the ambient temperature

Vacon A46 Vacon VSD Reference Warning The current of input Iin+ < 4 mA (Warning can be activated in Five in One Check the current loop circuitry
applications)
Vacon A47 Vacon VSD External warning Warning can be activated in Five In One applications) Check the external fault circuit or device.
Vacon F1 Vacon VSD Overcurrent The frequency converter has measured too high a current (> 4* In) in the motor - Check loading
output: - Check motor size
- sudden heavy load increase - Check cables
- short circuit in the motor cables
- unsuitable motor

Vacon F10 Vacon VSD Input line supervision Input line phase is missing Check utility connection.
Vacon F11 Vacon VSD Output phase supervision Current measurement has detected that there is no current in one motor phase Check motor cables

Vacon F12 Vacon VSD Brake chopper supervision - brake resistor not installed Check brake resistor
- brake resistor broken - If resistor is OK the chopper is broken, contact Vacon.
- Brake chopper broken
Vacon F13 Vacon VSD Drive undertemperature Temperature of heat sink below -10 deg. C
Vacon F14 Vacon VSD Drive overtemperature Temperature of heat sink over 70 deg. C - Check the cooling air flow
- Check that the sink is not dirty
- Check ambient temperature
- Check that the switching frequency is not too high compared with ambient
temperature and motor load

Vacon F15 Vacon VSD Motor stalled The motor stall protection has tripped - Check the motor
Vacon F16 Vacon VSD Motor temperature The converter motor temperature model has detected motor overheat Decrease motor load.
- motor is overloaded Check the temperature model parameters if the motor was not overheated.
Vacon F17 Vacon VSD Motor underload The motor underload protection has tripped
Vacon F18 Vacon VSD Analogue input polarity fault or analogue input Wrong analogue input polarity Check the polarity of the analogue input.
hardware fault Component failure on control board Contact Vacon
Vacon F19 Vacon VSD Option board identification Reading of the option board has failed Check installation
- If installation is correct, contact Vacon.
Vacon F2 Vacon VSD Overvoltage The voltage of the internal DC-Link of the converter has exceeded the nominal Adjust the decelaration time
voltage by 35%
- deceleration time too fast
- high overvoltage spikes at utility

Vacon F20 Vacon VSD 10V voltage reference +10 V reference shorted on control board or option board Check the cabling from +10V reference voltage
Vacon F21 Vacon VSD 24V supply +24V supply shorted on control board or option board Check the cabling from +24V reference voltage.
Vacon F22 Vacon VSD EEPROM check-sum fault Parameter restoring error When the fault is reset the frequency drive will automatically load parameter settings
- interference fault after reset.
- component failure If the fault occurs again contact Vacon.
Vacon F23 Vacon VSD EEPROM check-sum fault Parameter restoring error When the fault is reset the frequency drive will automatically load parameter settings
- interference fault after reset.
- component failure If the fault occurs again contact Vacon.
Vacon F25 Vacon VSD Microprocessor Watchdog - Interference fault Reset the fault and restart. Consult Vacon, if fault occurs again
- Component failure
Vacon F26 Vacon VSD Panel communication error The connection between panel and the frequency converter is not working Check the panel cable
Vacon F29 Vacon VSD Thermistor Protection Thermistor input of the I/O expander board has detected increase of the motor - Check motor cooling and loading
temperature - Check thermistor connection (if thermistor input of the I/O expander board is not in
use it has to be short circuited)
Vacon F3 Vacon VSD Ground Fault Current measurement detected that the sum of the motor phase current is not Check the motor cables
zero.
- insulation failure in the motor or the cables
Vacon F36 Vacon VSD Analog input Iin < 4mA (signal range selected 4- The current in the analog input Iin is below 4 mA Check the current loop circuitry
20mA) - signal source has failed
- control cable is broken
Vacon F4 Vacon VSD Inverter Fault The converter has detected faulty operation in the gate drivers or IGBT bridge Reset the fault and restart again. If the fault occurs again contact Vacon.
- interference fault
- component failure

Vacon F41 Vacon VSD External Fault Fault is detected in external fault digital input Check the external fault circuit or device.
Vacon F5 Vacon VSD Charging Switch Charging switch open when START command active Reset the fault and restart again. If the fault occurs again contact Vacon.
- interference fault
- component failure
Vacon F9 Vacon VSD Undervoltage DC-Bus voltage has gone below 65% of the nominal voltage In case of temporary supply voltage break, reset the fault and start again.
- most common reason is failure of the utility supply Check utility input.
- internal failure of the frequency converter can also cause an undervoltage trip If the utility supply is correct and internal failure has occurred, contact Vacon.

Vacon Internal Fault # 1 Elektronikon Mk IV - II or System input Error An I/O is missing from the module after programming. Check with FSP, or reprogram the module and make sure all necessary I/O are declared.
Higher The error 1 indicates that the master expects an extra extension module which is
not found or recognized on the system.
Yaskawa boL Yaskawa A1000 / GAe15VSD Braking Transistor Overload Fault The braking transistor reached its overload level. Select the correct braking resistor.
- 30VSD
The wrong braking resistor is installed
Yaskawa bUS Yaskawa A1000 / GAe15VSD Option Communication Error • The connection was lost after establishing initial communication. • Check for faulty wiring.
- 30VSD • Only detected when the run command frequency reference is assigned to an • Correct the wiring.
option card. • Check for disconnected cables and short circuits and repair as needed.
• Check for faulty wiring.
- No signal was received from the PLC • Correct the wiring.
- Faulty communications wiring or an existing • Check for disconnected cables and short circuits and repair as needed.
short circuit Replace the

Yaskawa CE Yaskawa A1000 / GAe15VSD MEMOBUS/Modbus Communication Error Control data was not received for the CE detection time set to H5-09. • Check for faulty wiring.
- 30VSD Faulty communications wiring or an existing • Correct the wiring.
short circuit • Check for disconnected cables and short circuits and repair as needed.
Communication data error occurred due to • Check the various options available to minimize the effects of noise.
noise • Counteract noise in the control circuit, main circuit, and

Yaskawa CF Yaskawa A1000 / GAe15VSD Control Fault - Motor parameters are set improperly - Check the motor parameter settings and repeat Auto-Tuning.
- 30VSD The torque limit was reached continuously for - Set the torque limit to the most appropriate setting (L7-01 through L7-04).
three seconds or longer while ramping to stop in - Torque limit is too low
OLV • Adjust the deceleration time (C1-02, C1-04, C1-06, C1-08).
Control. - Load inertia is too big • Set the frequency to the minimum value and interrupt

Yaskawa CPF11 to CPF14 Yaskawa A1000 / GAe15VSD Control Circuit Error - There is a self-diagnostic error in the control • Cycle power to the drive.
CPF16 to CPF19 - 30VSD circuit • If the problem continues, replace the control board or the entire drive. Contact
Yaskawa or a Yaskawa
- Connector on the operator is damaged representative for instructions on replacing the control board.
- Replace the operator.

Yaskawa CPF02 Yaskawa A1000 / GAe15VSD - A/D Conversion Error Control circuit is damaged • Cycle power to the drive.
- 30VSD - An A/D conversion error or control circuit error • If the problem continues, replace the control board or the entire drive. Contact
occurred. Yaskawa or a Yaskawa
representative for instructions on replacing the control board.

Yaskawa CPF03 Yaskawa A1000 / GAe15VSD - Control Board Connection Error - There is a connection error • Turn off the power and check the connection between the control board and the drive.
- 30VSD • If the problem continues, replace the control board or the entire drive. Contact
- Connection error between the control board and - Drive fails to operate properly due to noise Yaskawa or a Yaskawa
the drive interference representative for instructions on replacing the control board.

Yaskawa CPF06 Yaskawa A1000 / GAe15VSD - EEPROM Memory Data Error - There is an error in EEPROM control circuit • Turn off the power and check the connection between the control board and the drive.
- 30VSD • If the problem continues, replace the control board or the entire drive. Contact
- Error in the data saved to EEPROM - The power supply was switched off while Yaskawa or a Yaskawa
parameters were being saved to the drive representative for instructions on replacing the control board.

Yaskawa CPF07 Yaskawa A1000 / GAe15VSD Terminal Board Connection Error There is a faulty connection between the • Turn off the power and check the connection between the control board and the drive.
- 30VSD terminal board and the control board • If the problem continues, replace the control board or the entire

Yaskawa CPF20 or CPF21 Yaskawa A1000 / GAe15VSD Control Circuit Error Hardware is damaged • Cycle power to the drive.
- 30VSD • 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.

Yaskawa CPF22 Yaskawa A1000 / GAe15VSD Hybrid IC Failure Hybrid IC failure on the power board • Cycle power to the drive.
- 30VSD • If the problem continues, replace the power board or the entire drive. Contact
Yaskawa or a Yaskawa
representative for instructions on replacing the power board.

Yaskawa CPF23 Yaskawa A1000 / GAe15VSD - Control Board Connection Error Hardware is damaged • Turn off the power and check the connection between the control board and the drive.
- 30VSD • If the problem continues, replace the control board or the entire drive. Contact
-Connection error between the control board and Yaskawa or a Yaskawa
the drive representative for instructions on replacing the control board.
Yaskawa CPF24 Yaskawa A1000 / GAe15VSD Drive Unit Signal Fault Hardware is damaged If the problem continues, replace the control board or the entire drive. Contact Yaskawa
- 30VSD or a Yaskawa
-The drive capacity cannot be detected correctly representative for instructions on replacing the control board.
(drive capacity is checked when the drive is
powered up).

Yaskawa CPF26 to CPF34 Yaskawa A1000 / GAe15VSD - Control Circuit Error Hardware is damaged If the problem continues, replace the control board or the entire drive. Contact Yaskawa
CPF40 to CPF45 - 30VSD or a Yaskawa
- CPU error representative for instructions on replacing the control board.
Yaskawa dEv Yaskawa A1000 / GAe15VSD - Speed Deviation (for Control Mode with PG) - Load is too heavy - Reduce the load.
- 30VSD -The deviation between the speed reference and - Acceleration and deceleration times are set too - Increase the acceleration and deceleration times (C1-01 through C1-08).
speed feedback is greater than the setting in F1-10 short - Check the machine.
for - The load is locked up - Check the settings of parameters F1-10 and F1-11.
longer than the time set to F1-11. - Parameters are not set appropriately - • Set H6-02 to the same value as the speed feedback signal frequency when the motor
- Incorrect speed feedback scaling when using run
terminal RP as speed feedback input in V/f
control
- Motor brake is en

Yaskawa dv1 Yaskawa A1000 / GAe15VSD - Z Pulse Fault PG encoder is disconnected, improperly • Make sure the PG encoder is properly connected and all shielded lines are properly
- 30VSD - The motor turned one full rotation without the Z wired, or the PG option card or PG encoder are grounded.
Pulse being detected. damaged • If the problem continues after cycling power, replace the PG option card or the PG
encoder.

Yaskawa dv2 Yaskawa A1000 / GAe15VSD - Z Pulse Noise Fault Detection - Noise interference along the PG cable * Separate the PG cable lines from the source of the noise.
- 30VSD - The Z Pulse is out of phase by more than 5 - PG cable is not wired properly * Rewire the PG encoder and properly ground all shielded lines.
degrees for the number of times specified in - PG option card or the PG encoder are damaged * If the problem continues after cycling power, replace the PG option card or the PG
parameter F1-17. encoder.

Yaskawa dv3 Yaskawa A1000 / GAe15VSD - Inversion Detection - The Z Pulse offset is not set properly to E5-11 - Set the value for Δθ to E5-11 as specified on the motor nameplate. Readjust the Z Pulse
- 30VSD - The torque reference and acceleration are in - An external force on the load side caused the offset when
opposite directions and the speed reference and motor to move replacing the PG encoder or changing the application to rotate the motor in reverse.
actual motor - Noise interference along the PG cable - • Make sure the motor is rotating in the proper direction.
speed differ by more than 30% for the number of affecting the A or B pulse • Ident
times set to F1-18. - PG encoder is disconnected, improperly wired, or the PG option card or PG

Yaskawa dv4 Yaskawa A1000 / GAe15VSD - Inversion Prevention Detection - The Z Pulse offset is not set properly to E5-11 - • Set the value for Δθ to E5-11 as specified on the motor nameplate.
- 30VSD - Pulses indicate that the motor is rotating in the - Noise interference along the PG cable • If the problem continues after cycling power, replace the PG option card or the PG
opposite direction of the speed reference. Set the affecting the A or B pulse encoder. Readjust
number - PG encoder is disconnected, improperly the Z Pulse offset when replacing the PG encoder or changing the application to r
of pulses to trigger inverse detection to F1-19. wired, or the PG option card or PG encoder are
damaged

Yaskawa dv7 Yaskawa A1000 / GAe15VSD Polarity Judge Timeout - Disconnection in the motor coil winding • Measure the motor line-to-line resistance and replace the motor if the motor coil
- 30VSD winding is
- Loose output terminals disconnected.
• Check for loose terminals. Apply the tightening torque specified in this manual to
fasten the terminals.
Refer to Wire Gauges and Tightening Tor

Yaskawa dWAL, dWFL Yaskawa A1000 / GAe15VSD DriveWorksEZ Fault Fault output by DriveWorksEZ Correct the cause of the fault.
- 30VSD
Yaskawa E5 Yaskawa A1000 / GAe15VSD - SI-T3 Watchdog Timer Error - Data has not been received from the PLC
- 30VSD - Execute DISCONNECT or ALM_CLR, then issue a CONNECT command or SYNC_SET
- The watchdog timed out. command and
proceed to phase 3. Refer to the SI-T3 Option Technical Manual for more details on
troubleshooting.

Yaskawa EF0 Yaskawa A1000 / GAe15VSD - Option Card External Fault - An external fault was received from the PLC • Remove the cause of the external fault.
- 30VSD - An external fault condition is present. and F6-03 is set to a value other than 3. • Remove the external fault input from the PLC.
- Problem with the PLC program Check the PLC program and correct problems.

Yaskawa EF1 Yaskawa A1000 / GAe15VSD - External Fault (input terminal S1) - An external device tripped an alarm function - Remove the cause of the external fault and reset the fault.
- 30VSD - External fault at multi-function input terminal S1. - Wiring is incorrect - • Properly connect the signal lines to the terminals assigned for external fault detection
- Multi-function contact input setting is (H1-oo = 20 to 2F).
incorrect • Reconnect the signal line.
• Check for unused terminals set for H1-oo = 20 to

Yaskawa EF2 Yaskawa A1000 / GAe15VSD - External Fault (input terminal S2) - An external device tripped an alarm function - Remove the cause of the external fault and reset the fault.
- 30VSD - External fault at multi-function input terminal S2. - Wiring is incorrect - • Properly connect the signal lines to the terminals assigned for external fault detection
- Multi-function contact input setting is (H1-oo = 20 to 2F).
incorrect • Reconnect the signal line.
• Check for unused terminals set for H1-oo = 20 to

Yaskawa EF3 Yaskawa A1000 / GAe15VSD - External Fault (input terminal S3) - An external device tripped an alarm function - Remove the cause of the external fault and reset the fault.
- 30VSD - External fault at multi-function input terminal S3. - Wiring is incorrect - • Properly connect the signal lines to the terminals assigned for external fault detection
- Multi-function contact input setting is (H1-oo = 20 to 2F).
incorrect • Reconnect the signal line.
• Check for unused terminals set for H1-oo = 20 to

Yaskawa EF4 Yaskawa A1000 / GAe15VSD - External Fault (input terminal S4) - An external device tripped an alarm function - Remove the cause of the external fault and reset the fault.
- 30VSD - External fault at multi-function input terminal S4. - Wiring is incorrect - • Properly connect the signal lines to the terminals assigned for external fault detection
- Multi-function contact input setting is (H1-oo = 20 to 2F).
incorrect • Reconnect the signal line.
• Check for unused terminals set for H1-oo = 20 to
Yaskawa EF5 Yaskawa A1000 / GAe15VSD - External Fault (input terminal S5) - An external device tripped an alarm function - Remove the cause of the external fault and reset the fault.
- 30VSD - External fault at multi-function input terminal S5. - Wiring is incorrect - • Properly connect the signal lines to the terminals assigned for external fault detection
- Multi-function contact input setting is (H1-oo = 20 to 2F).
incorrect • Reconnect the signal line.
• Check for unused terminals set for H1-oo = 20 to

Yaskawa EF6 Yaskawa A1000 / GAe15VSD - External Fault (input terminal S6) - An external device tripped an alarm function - Remove the cause of the external fault and reset the fault.
- 30VSD - External fault at multi-function input terminal S6. - Wiring is incorrect - • Properly connect the signal lines to the terminals assigned for external fault detection
- Multi-function contact input setting is (H1-oo = 20 to 2F).
incorrect • Reconnect the signal line.
• Check for unused terminals set for H1-oo = 20 to

Yaskawa EF1 Yaskawa A1000 / GAe15VSD - External Fault (input terminal S1) - An external device tripped an alarm function - Remove the cause of the external fault and reset the fault.
- 30VSD - External fault at multi-function input terminal S1. - Wiring is incorrect - • Properly connect the signal lines to the terminals assigned for external fault detection
- Multi-function contact input setting is (H1-oo = 20 to 2F).
incorrect • Reconnect the signal line.
• Check for unused terminals set for H1-oo = 20 to

Yaskawa EF7 Yaskawa A1000 / GAe15VSD - External Fault (input terminal S7) - An external device tripped an alarm function - Remove the cause of the external fault and reset the fault.
- 30VSD - External fault at multi-function input terminal S7. - Wiring is incorrect - • Properly connect the signal lines to the terminals assigned for external fault detection
- Multi-function contact input setting is (H1-oo = 20 to 2F).
incorrect • Reconnect the signal line.
• Check for unused terminals set for H1-oo = 20 to

Yaskawa EF8 Yaskawa A1000 / GAe15VSD - External Fault (input terminal S8) - An external device tripped an alarm function - Remove the cause of the external fault and reset the fault.
- 30VSD - External fault at multi-function input terminal S8. - Wiring is incorrect - • Properly connect the signal lines to the terminals assigned for external fault detection
- Multi-function contact input setting is (H1-oo = 20 to 2F).
incorrect • Reconnect the signal line.
• Check for unused terminals set for H1-oo = 20 to

Yaskawa Err Yaskawa A1000 / GAe15VSD - EEPROM Write Error - Noise has corrupted data while writing to the - EEPROM Write Error
- 30VSD EEPROM - Data cannot be written to the EEPROM
- Data cannot be written to the EEPROM - • Press “ENTER” on the digital operator.
- Hardware problem • Correct the parameter setting.
• Cycle power to the drive.
• If the problem continues, replace the control board or the entire drive. Contact
Yaskawa

Yaskawa Fan Yaskawa A1000 / GAe15VSD - Internal Fan Fault Internal cooling fan has malfunctioned • Cycle power to the drive.
- 30VSD - Fan or magnetic contactor failure • Check for fan operation.
Fault detected in the internal cooling fan or • Verify the cumulative operation time of the fan with monitor U4-03, and verify the
magnetic contactor to the power supply. cumulative operation
time of the fan maintenance timer with U4-04.
• If the cooling fan has exceeded its expected p

Yaskawa FbH Yaskawa A1000 / GAe15VSD Excessive PID Feedback - Parameters are set inappropriately - Check b5-36 and b5-37 settings.
- 30VSD PID feedback input is greater than the level set to - Correct the wiring.
b5-36 for longer than the time set to b5-37. Set b5- - Incorrect PID feedback wiring - • Check the sensor on the control side.
12 • Replace the sensor if damaged.
to 2 or 5 to enable fault detection. - There is a problem with the feedback sensor

Yaskawa FbL Yaskawa A1000 / GAe15VSD - PID Feedback Loss - Parameters are set inappropriately - Check b5-13 and b5-14 settings.
- 30VSD - This fault occurs when PID feedback loss detection - Incorrect PID feedback wiring - Correct the wiring.
is programmed to trigger a fault (b5-12 = 2) and the - There is a problem with the feedback sensor - • Check the sensor on the control side.
PID feedback level is below the detection level set • Replace the sensor if damaged.
to b5-13 for longer than the time set to b5-14.

Yaskawa GF Yaskawa A1000 / GAe15VSD Ground Fault - Motor insulation is damaged - • Check the insulation resistance of the motor.
- 30VSD • A current short to ground exceeded 50% of rated - A damaged motor cable is creating a short • Replace the motor.
current on the output side of the drive. circuit • Check the motor cable.
• Setting L8-09 to 1 enables ground fault detection. - Excessive leakage current at the drive output • Remove the short circuit and reapply power to the drive
- The drive started to run during a current offset • Check the resistance between the cable and the ground terminal .
fault or while coasting to a stop • Replace the cable.
- Hardware problem • Reduce the

Yaskawa LF Yaskawa A1000 / GAe15VSD Output Phase Loss - The output cable is disconnected • Check for wiring errors and properly connect the output cable.
- 30VSD • Phase loss on the output side of the drive. - The motor winding is damaged • Correct the wiring.
• Setting L8-07 to 1 or 2 enables Phase Loss - The output terminal is loose • Check the resistance between motor lines.
Detection. - The rated current of the motor being used is • Replace the motor if the winding is damaged.
less than 5% of the drive rated current • Apply the tightening torque specified in this manual to fasten the terminal
- An output transistor is damaged
- A single-phase motor is being used

Yaskawa LF2 Yaskawa A1000 / GAe15VSD Output Current Imbalance - Phase loss has occurred on the output side of
- 30VSD One or more of the phases in the output current the drive - • Check for faulty wiring or poor connections on the output side of the drive.
are lost. - Terminal wires are loose on the output side of • Correct the wiring.
the drive
- The output circuit is damaged Apply the tightening torque specified in this manual to fasten the terminals. Refer to
- Motor impedance or motor phases are uneven Wire Gauges and
Tightening Torque on page 89 for details.
If t
Yaskawa LF3 Yaskawa A1000 / GAe15VSD Power Unit Output Phase Loss 3 The gate drive board in the power unit is Cycle the power supply. Refer to Diagnosing and Resetting Faults on page 386 for details.
- 30VSD • Phase loss occurred on the output side damaged. If the fault
• Setting L8-78 to 1 enables Power Unit Output continues to occur, replace the gate drive board or the entire drive. Contact Yaskawa or
Phase Loss Protection Cable to the current detection circuit in the a Yaskawa
power unit is damaged or not connected representative for instructions on replacing the gate
properly.
Cable between the output rector and the power
unit is loose or not connected.

Yaskawa nSE Yaskawa A1000 / GAe15VSD Node Setup Error - The node setup terminal closed during run. Stop the drive when using the node setup function.
- 30VSD A terminal assigned to the node setup function
closed during run. A Run command was issued while the node setup function was active.
Yaskawa oC Yaskawa A1000 / GAe15VSD Overcurrent - The motor has been damaged due to • Check the insulation resistance.
- 30VSD Drive sensors detected an output current greater overheating or the motor insulation is • Replace the motor.
than the specified overcurrent level. damaged • Check the motor cables.
- One of the motor cables has shorted out or • Remove the short circuit and reapply power to the drive.
there is a grounding problem • Check the resistance between the motor cables and the ground terminal .
- The load is too heavy • Replace damaged cables.
- The acceleration or deceleration times are too • Measure the
short
- The drive is atte

Yaskawa oFA00 Yaskawa A1000 / GAe15VSD Option Card Connection Error at Option Port CN5-A - The option card installed into port CN5-A is - Check if the drive supports the option card to be installed. Contact Yaskawa for
- 30VSD Option compatibility error incompatible with the drive assistance.
- A PG option card is connected to option port - PG option cards are supported by option ports CN5-B and CN5-C only. Connect the PG
CN5-A option card to
the correct option port.

Yaskawa oFA01 Yaskawa A1000 / GAe15VSD - Option Card Fault at Option Port CN5-A The option card connection to port CN5-A is • Turn off the power and reconnect the option card.
- 30VSD - Option not properly connected faulty • Check if the option card is properly plugged into the option port. Make sure the card is
fixed properly.
• If the option is not a communication option card, try to use the card in a different
option po

Yaskawa oFA03 to oFA06 Yaskawa A1000 / GAe15VSD Option Card Error Occurred at Option Port CN5-A Option card or hardware is damaged • Cycle power to the drive.
- 30VSD • 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.

Yaskawa oFA10, oFA11 Yaskawa A1000 / GAe15VSD Option Card Error Occurred at Option Port CN5-A Option card or hardware is damaged • Cycle power to the drive.
- 30VSD • 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.

Yaskawa oFA12 to oFA17 Yaskawa A1000 / GAe15VSD Option Card Connection Error (CN5-A) Option card or hardware is damaged • Cycle power to the drive.
- 30VSD • 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.

Yaskawa oFA30 to oFA43 Yaskawa A1000 / GAe15VSD Communication Option Card Connection Error Option card or hardware is damaged • Cycle power to the drive.
- 30VSD (CN5-A) • 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.

Yaskawa oFb00 Yaskawa A1000 / GAe15VSD - Option Card Fault at Option Port CN5-B - The option card installed into port CN5-B is - Make sure the drive supports the option card to be installed. Contact Yaskawa for
- 30VSD - Option compatibility error incompatible with the drive assistance.
- A communication option card has been - Communication option cards are only supported by option port CN5-A. It is not possible
installed in option port CN5-B to install more
than one communication option.

Yaskawa oFb01 Yaskawa A1000 / GAe15VSD Option Card Fault at Option Port CN5-B The option card connection to port CN5-B is • Turn off the power and reconnect the option card.
- 30VSD Option not properly connected faulty • Check if the option card is properly plugged into the option port. Make sure the card is
fixed properly.
• Try to use the card in a different option port (in case of a PG option, use port CN5-C). If
th

Yaskawa oFb02 Yaskawa A1000 / GAe15VSD Option Card Fault at Option Port CN5-B - An option card of the same type is already - Except for PG options, only one of each option card type can only be installed
- 30VSD Same type of option card is currently connected installed in option port CN5-A simultaneously. Make sure
- An input option card is already installed in only one type of option card is connected.
option port CN5-A - Install a communication option, a digital input option, or an analog input option. More
than one of the

Yaskawa oFb03 to oFb11 Yaskawa A1000 / GAe15VSD Option card error occurred at Option Port CN5-B Option card or hardware is damaged • Cycle power to the drive.
- 30VSD • 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.

Yaskawa oFb12 to oFb17 Yaskawa A1000 / GAe15VSD Option card error occurred at Option Port CN5-B Option card or hardware is damaged • Cycle power to the drive.
- 30VSD • 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.

Yaskawa oFC00 Yaskawa A1000 / GAe15VSD - Option Card Connection Error at Option Port CN5- The option card installed into port CN5-C is Confirm that the drive supports the option card to be installed. Contact Yaskawa for
- 30VSD C incompatible with the drive assistance.s
- Option compatibility error
Yaskawa oFC01 Yaskawa A1000 / GAe15VSD - Option Card Fault at Option Port CN5-C The option card connection to port CN5-C is • Turn the power off and reconnect the option card.
- 30VSD - Option not properly connected faulty. • Check if the option card is properly plugged into the option port. Make sure the card is
fixed properly.
• Try to use the card in a different option port (in case of a PG option, use port CN5-B). If
th
Yaskawa oFC02 Yaskawa A1000 / GAe15VSD - Option Card Fault at Option Port CN5-C - An option card of the same type is already Except for PG options, only one of each option card type can only be installed
- 30VSD - Same type of option card is currently connected installed in option port CN5-A or CN5-B. simultaneously. Make sure
only one type of option card is connected.
An input option card is already installed in
option port CN5-A or CN5-B. Install a communication option, a digital input option, or an analog input option. More
than one of the
Three PG option boards are installed. s

Yaskawa oFC03 to oFC11 Yaskawa A1000 / GAe15VSD Option Card Error Occurred at Option Port CN5-C Option card or hardware is damaged • Cycle power to the drive.
- 30VSD • 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.

Yaskawa oFC12 to oFC17 Yaskawa A1000 / GAe15VSD Option Card Error Occurred at Option Port CN5-C Option card or hardware is damaged • Cycle power to the drive.
- 30VSD • 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.

Yaskawa oH Yaskawa A1000 / GAe15VSD Heatsink Overheat - Surrounding temperature is too high • Check the temperature surrounding the drive. Verify temperature is within drive
- 30VSD The heatsink temperature exceeded the overheat - Load is too heavy specifications.
pre-alarm level set to L8-02. The default value for - Internal cooling fan is stopped • Improve the air circulation within the enclosure panel.
L8-02 • Install a fan or air conditioner to cool the surrounding area.
is determined by drive capacity (o2-04). • Remove anything near the drive t

Yaskawa oH1 Yaskawa A1000 / GAe15VSD Overheat 1 (Heatsink Overheat) Surrounding temperature is too high • Check the temperature surrounding the drive.
- 30VSD The heatsink temperature exceeded the drive Load is too heavy • Improve the air circulation within the enclosure panel.
overheat level. Overheat level is determined by • Install a fan or air conditioner to cool the surrounding area.
drive • Remove anything near the drive that might be producing excessive heat.
capacity (o2-04). • Measure th

Yaskawa oH3 Yaskawa A1000 / GAe15VSD Motor Overheat Alarm (PTC Input) Motor has overheated • Check the size of the load, the accel/decel times, and the cycle times.
- 30VSD • The motor overheat signal to analog input • Decrease the load.
terminal A1, A2, or A3 exceeded the alarm • Increase the acceleration and deceleration times (C1-01 through C1-08).
detection level. • Adjust the preset V/f pattern (E1-04 through E1-10) by reducing E1-08 and E1-10.
• Detection requires setting multi-function analog •D
inputs H3-02, H3-06, or H3-10 to E.

Yaskawa oH4 Yaskawa A1000 / GAe15VSD Motor Overheat Fault (PTC Input) Motor has overheated • Check the size of the load, the accel/decel times, and the cycle times.
- 30VSD • The motor overheat signal to analog input • Decrease the load.
terminal A1, A2, or A3 exceeded the fault detection • Increase the acceleration and deceleration times (C1-01 through C1-08).
level. • Adjust the preset V/f pattern (E1-04 through E1-10) by reducing E1-08 and E1-10.
• Detection requires setting multi-function analog •D
inputs H3-02, H3-06, or H3-10 to E.

Yaskawa oH5 Yaskawa A1000 / GAe15VSD Motor Overheat (NTC Input) Motor has overheated • Reduce the load.
- 30VSD The motor temperature exceeded the level set to • Check the ambient temperature.
L1-16 (or L1-18 for motor 2)
Yaskawa oL1 Yaskawa A1000 / GAe15VSD Motor Overload - Load is too heavy - Reduce the load.
- 30VSD The electronic motor overload protection tripped - Cycle times are too short during acceleration - Increase the acceleration and deceleration times (C1-01 through C1-08).
and deceleration • Reduce the load.
- A general-purpose motor is driven below the • Increase the speed.
rated speed with a high load • If the motor is supposed to operate at low speeds, either increase the motor capacity
- The output voltage is too high or use a motor
- The wrong motor rated current is set to E2-01 specifically desig
- The maximum

Yaskawa oL2 Yaskawa A1000 / GAe15VSD - Drive Overload - Load is too heavy - Reduce the load.
- 30VSD - The thermal sensor of the drive triggered overload - Acceleration or deceleration time is too short - Increase the settings for the acceleration and deceleration times (C1-01 through C1-
protection. - The output voltage is too high 08).
- Drive capacity is too small • Adjust the preset V/f pattern (E1-04 through E1-10) by reducing E1-08 and E1-10.
- Overload occurred when operating at low • Do not lower E1-08 and E1-10 excessively. This reduces load
speeds
- Excessive torque compensation
- Parameters related to Speed Search are s

Yaskawa oL3 Yaskawa A1000 / GAe15VSD Overtorque Detection 1 - Parameter settings are not appropriate for the - Check L6-02 and L6-03 settings.
- 30VSD The current has exceeded the value set for torque load - Check the status of the load. Remove the cause of the fault.
detection (L6-02) for longer than the allowable time - Fault on the machine side (e.g., machine is
(L6-03). locked up)

Yaskawa oL4 Yaskawa A1000 / GAe15VSD - Overtorque Detection 2 Parameter settings are not appropriate for the Check the settings of parameters L6-05 and L6-06.
- 30VSD - The current has exceeded the value set for load
Overtorque Detection 2 (L6-05) for longer than the
allowable
time (L6-06).

Yaskawa oL5 Yaskawa A1000 / GAe15VSD - Mechanical Weakening Detection 1 Overtorque triggered mechanical weakening Identify the cause of mechanical weakening.
- 30VSD - Overtorque occurred, matching the conditions detection level set to L6-08
specified in L6-08.
Yaskawa oL7 Yaskawa A1000 / GAe15VSD - High Slip Braking oL - Excessive load inertia • Reduce deceleration times in parameters C1-02, C1-04, C1-06, and C1-08 for
- 30VSD - The output frequency stayed constant for longer - Motor is driven by the load applications that do not
than the time set to n3-04 during High Slip Braking. - Something on the load side is restricting use High Slip Braking.
deceleration • Use a braking resistor to shorten deceleration time.
- The overload time during High Slip Braking • Increase parameter n3-04 (High-slip Braking Overload Time).
is too short • Install a t

Yaskawa oPr Yaskawa A1000 / GAe15VSD External Digital Operator Connection Fault The external operator has been disconnected from the drive. • Check the connection between the operator and the drive.
- 30VSD Note: An oPr fault will occur when all of the following conditions are true: • Replace the cable if damaged.
• Output is interrupted when the operator is disconnected (o2-06 = 1). • Turn off the drive input power and disconnect the operator. Reconnect the operator
• The Run command is assigned to the operator ( and reapply drive
input power.
Yaskawa oS Yaskawa A1000 / GAe15VSD Overspeed (for Control Mode with PG) - Overshoot is occurring • Increase the settings for C5-01 (Speed Control Proportional Gain 1) and reduce C5-02
- 30VSD The motor speed feedback exceeded the F1-08 - Incorrect speed feedback scaling if terminal (Speed Control
setting. RP is used as speed feedback input in V/f Integral Time 1).
control • If using Closed Loop Vector mode, enable Feed Forward and perform Inertia Auto-
- Incorrect number of PG pulses has been set Tuning.
- Inappropriate parameter settings • Set H6-02 to the value of the speed feedback

Yaskawa ov Yaskawa A1000 / GAe15VSD Overvoltage Voltage in the DC bus has exceeded the overvoltage detection level. • Increase the deceleration time (C1-02, C1-04, C1-06, C1-08).
- 30VSD • For 200 V class drives: approximately 410 V • Install a dynamic braking resistor or a dynamic braking resistor unit.
• For 400 V class drives: approximately 820 V (740 V when E1-01 is less than 400) • Set L3-04 to 1 to enable stall prevention during deceleration. Stall Prevention is
• For 600 V class drives: approximately 1040 V enabled as the default
setting.
- Decelerat
-

Yaskawa PF Yaskawa A1000 / GAe15VSD - Input Phase Loss - Drive input power has an open phase or has a large imbalance of voltage • Check for wiring errors in the main circuit drive input power.
- 30VSD between phases. Detected when • Correct the wiring.
L8-05 is set 1 (enabled). • Ensure the terminals are tightened properly.
- There is phase loss in the drive input power • Apply the tightening torque as specified in this manual. Refer to Wire Gauges and
- There is loose wiring in the drive input power Tightening
terminals Torque on page 89 for deta
- There is excessiv

Yaskawa Pgo Yaskawa A1000 / GAe15VSD - PG Disconnect (for any control modes using a PG - PG cable is disconnected - Reconnect the cable.
- 30VSD option card) - PG cable wiring is wrong - Correct the wiring.
- No PG pulses are received for longer than the time - PG has no power - Check the power line to the PG encoder.
set to F1-14. - PG encoder brake is clamped shut - Ensure the motor brake releases properly.

Yaskawa PGoH Yaskawa A1000 / GAe15VSD - PG Hardware Fault (detected when using a PG-X3 PG cable is disconnected Reconnect the cable and check the setting of F1-20.
- 30VSD option card)
- PG cable is not connected properly.
Yaskawa rF Yaskawa A1000 / GAe15VSD Braking Resistor Fault The resistance of the braking resistor is too low. - Select a braking resistor option that it fits the drive braking transistor specification.
- 30VSD -The proper braking resistor option has not - Set L8-55 to 0 to disable the braking transistor protection selection.
been installed
-A regenerative converter, regenerative unit, or
braking unit is being used

Yaskawa rH Yaskawa A1000 / GAe15VSD Braking Resistor Overheat - Braking resistor protection was triggered. • Check the load, deceleration time, and speed.
- 30VSD Fault detection is enabled when L8-01 = 1 (disabled as a default). • Reduce the load inertia.
- Deceleration time is too short and excessive • Increase the deceleration times (C1-02, C1-04, C1-06, C1-08, C1-09).
regenerative energy is flowing back into the • Replace the dynamic braking option with a larger device that can handle the power
drive that is discharged.
- Excessive braking inertia -Reca
- The braking ope

Yaskawa rr Yaskawa A1000 / GAe15VSD Dynamic Braking Transistor - The built-in dynamic braking transistor failed. • Cycle power to the drive and check for reoccurrence of the fault.
- 30VSD - The braking transistor is damaged • Replace either the control board or the entire drive. For instructions on replacing the
- The control circuit is damaged control board, contact Yaskawa or a Yaskawa representative.
Yaskawa SC Yaskawa A1000 / GAe15VSD IGBT Short Circuit or Ground Fault - IGBT fault • Check motor wiring.
- 30VSD - IGBT short circuit detection circuit fault • Turn off the power supply, then turn it on. If the problem continues, contact your
Yaskawa representative or the nearest Yaskawa sales office.
Yaskawa Ser Yaskawa A1000 / GAe15VSD Too Many Speed Search Restarts - The number of Speed Search restarts exceeded the value set to b3-19. • Reduce the detection compensation gain during Speed Search (b3-10).
- 30VSD - Parameters related to Speed Search are set to • Increase the current level when attempting Speed Search (b3-17).
the wrong values • Increase the detection time during Speed Search (b3-18).
- The motor is coasting in the opposite direction • Repeat Auto-Tuning.
of the Run command
- Set b3-14 to 1 to enable Bi-Direct

Yaskawa Sto Yaskawa A1000 / GAe15VSD Motor Pull Out or Step Out Detection - Motor pull out or step out has occurred. Motor has exceeded its pull-out torque. • Enter the correct motor code for the PM being used into E5-01.
- 30VSD - The wrong motor code is set (Yaskawa motors • For special-purpose motors, enter the correct data to all E5 parameters according to
only) the test report
- Load is too heavy provided for the motor.
- Load inertia is too heavy • Increase the load inertia for PM motor (n8-55).
- Acceleration and deceleration times are too • Increase th
short
- Speed response is

Yaskawa SvE Yaskawa A1000 / GAe15VSD Zero Servo Fault - Position deviation during zero servo. - Set the torque limit to an appropriate value using parameters L7-01 to L7-04.
- 30VSD - Torque limit is set too low - Reduce the amount of load torque.
- Excessive load torque - Check the PG signal for noise interference.
- Noise interference along PG encoder wiring

Yaskawa Tho Yaskawa A1000 / GAe15VSD Thermistor Disconnect - The thermistor that detects motor temperature has become disconnected. Check the thermistor wiring.
- 30VSD - The motor thermistor is not connected
properly.
Yaskawa UL3 Yaskawa A1000 / GAe15VSD Undertorque Detection 1 - The current has fallen below the minimum value set for torque detection (L6-02) Check the settings of parameters L6-02 and L6-03.
- 30VSD for longer than the
allowable time (L6-03). Check the load for any problems.
- Parameter settings are not appropriate for the
load
- There is a fault on the machine side

Yaskawa UL4 Yaskawa A1000 / GAe15VSD Undertorque Detection 2 - The current has fallen below the minimum value set for torque detection (L6-05) Check L6-05 and L6-06 settings
- 30VSD for longer than the
allowable time (L6-06). Check the load for any problems.

Parameter settings are not appropriate for the

load

There is a fault on the machine side

Yaskawa UL5 Yaskawa A1000 / GAe15VSD Mechanical Weakening Detection 2 - The operation conditions matched the conditions set to L6-08. Check the load side for any problems.
- 30VSD - Undertorque was detected and matched the
conditions for mechanical loss detection set to
L6-08

Yaskawa UnbC Yaskawa A1000 / GAe15VSD Current Unbalance - Current flow has become unbalanced. • Check wiring
- 30VSD - The internal current sensor has detected a • Check for damaged transistors.
current unbalance situation. • Check for short circuits or grounding problems on the connected motor.
Yaskawa Uv1 Yaskawa A1000 / GAe15VSD DC Bus Undervoltage Voltage in the DC bus fell below the undervoltage detection level (L2-05). • The main circuit drive input power is wired incorrectly.
- 30VSD • For 200 V class drives: approximately 190 V • Correct the wiring.
• For 400 V class drives: approximately 380 V (350 V when E1-01 is less than 400) • Ensure there are no loose terminals.
• For 600 V class drives: approximately 475 V • Apply the tightening torque specified in this manual to fasten the terminals. Refer to
The fa Wire Gauges
and Tightening Torque on page 89 f

Yaskawa Uv2 Yaskawa A1000 / GAe15VSD Control Power Supply Voltage Fault - Voltage is too low for the control drive input power. - Correct the setting to L2-02 or install an optional Momentary Power Loss Ride-Thru
- 30VSD - In drive models CIMR-Ao2A0004 to unit.
2A0056 or 4A0002 to 4A0031, L2-02 was • Cycle power to the drive. Check if the fault reoccurs.
changed from its default value without • If the problem continues, replace the control board, the entire drive, or the control
installing a Momentary Power Loss Ride-Thru power supply. For
unit i
- Control power supply wiring is damag

Yaskawa Uv3 Yaskawa A1000 / GAe15VSD Undervoltage 3 (Soft-Charge Bypass Circuit Fault) - The soft-charge bypass circuit failed. • Cycle power to the drive and see if the fault reoccurs.
- 30VSD - The relay or contactor on the soft-charge • If the problem continues, replace either the control board or the entire drive. For
bypass circuit is damaged instructions on replacing the control board, contact Yaskawa or a Yaskawa
representative.
• Check monitor U4-06

Yaskawa Uv4 Yaskawa A1000 / GAe15VSD Gate Drive Board Undervoltage - Voltage drop in the gate drive board circuit • Cycle power to the drive and see if the fault reoccurs. Refer to Diagnosing and
- 30VSD - Not enough power is being supplied to the gate Resetting Faults on page 386 for details.
drive board. • If the problem continues, replace either the gate drive board or the entire drive. For
instructions on replacing the gate drive b

Yaskawa voF Yaskawa A1000 / GAe15VSD Output Voltage Detection Fault - Problem detected with the voltage on the output side of the drive. Replace the control board or the entire drive. For instructions on replacing the control
- 30VSD - Hardware is damaged board, contact Yaskawa or a Yaskawa representative.
KEB bbl base block Power modules for motor de-excitation locked
KEB bon close brake Brake control, brake engaged (see chapter 6.9)
KEB boFF open brake Brake control, break released (see chapter 6.9)
KEB cDD calculate drive Measurement of the motor stator resistance.
KEB dcb DC brake Motor is decelerated by a DC-voltage at the output.
KEB dLS Low speed/dc brake Modulation is switch off after DC-braking (see chapter 6.9 "DC-braking")

KEB FAcc forward acceleration Acceleration with the adjust ramps in clockwise direction of rotation.

KEB Fcon forward constant Acceleration/deceleration phase is completed and it is drive with constant
speed/frequency in clockwise direction of rotation
KEB FdEc forward deceleration It is stopped with the adjusted ramp times in clockwise direction of rotation.

KEB HCL hardware current limit The message is output if the output current reaches the hardware current
limit.
KEB LAS LA stop This message is displayed if during acceleration the load is limited to the
adjusted load level
KEB LdS Ld stop This message is displayed if during deceleration the load is limited to the
adjusted load level or the DC-link current to the adjusted voltage level.

KEB LS Low speed/dc brake No direction of rotation pre-set modulation is off.

KEB nO_pu power unit not ready Power circuit jot ready or not identified by the control.
KEB noP no operation control release (terminal ST) is not switched.
KEB PA positioning active This message is displayed during a positioning process
KEB PLS low speed/power off no modulation after Power-Off.
KEB PnA position not reachable This specified position cannot be reached within the pre-set ramps. This
abort of the positioning can be programmed.
KEB POFF power off function Depending on the programming of the function (see chapter 6.9, power-off
function) the inverter restarts automatically upon system of recovery or
after a reset.

KEB POSI positioning active Positioning function active (FS-G)

KEB rAcc reverse acceleration Acceleration with the adjusted ramp times in anti- clockwise direction of
rotation.
KEB rcon reverse constant Acceleration/deceleration phase is completed and it is drive with constant
speed/frequency in clockwise direction of rotation
KEB rdEc reverse deceleration it is stopped with the adjusted ramp times in anti-clockwise direction of
rotation.
KEB rFP ready for positioning The drive signals that it is ready to start the positioning process.
KEB SLL Stall this message is displayed if during constant operation the load is limited to
the adjusted current limit
KEB SrA search for ref.active Search for reference point approach active.
KEB SSF speed search Speed search function active, that means that the inverter attempts to
synchronize onto a running down motor.
KEB STOP quick stop The message is output if as response to a warning signal the quick-stop
function becomes active
KEB E. br Error! Brake Error can occur in the case of switched on brake control (see chapter 6.9.5)
if
-the load is below the minimum load level (Pn. 43) at start up or the
absence of an engine phase was detected.
-the load is too high and the hardware current limit is reached

KEB E. buS Error! Watchdog Adjusted monitoring time (Watchdog) of communication between operator
and PC/operator and inverter has been exceeded
KEB E. Cdd Error! Calc.drive data Error: During the automatic motor stator resistance measurement.
KEB E. co1 Error! Counter overrun 1 Counter overflow encoder channel 1.
KEB E. co2 Error! Counter overrun 2 Counter overflow encoder channel 2.
KEB E. dOH Error! Drive overheat Error: Over temperature of motor PTC. Error can only be rest at E.ndOH, if
PTC is again low-resistance. Causes:
- resistance at the terminals T1/T2 > 1650 Ohm
- motor overloaded
- line breakage to the temperature sensor

KEB E. dri Error! Drive relay Error: Driver relay. Relay for driver voltage on power circuit has not picked
up even though control release was given.
KEB E. EEP Error! EEPROM defective t After reset the operation is again possible (without storage in the EEPROM)

KEB E. EF Error! External fault Error: External Error. Is triggered if a digital input is being programed as
external error input and trips.
KEB E.EnC Error! Encoder cable Cable breakage at the resolver or incremental encoder
KEB E. Hyb hybrid invalid encoder interface identifier
KEB E. Hybc Error! Hybrid changed Error: Encoder interface identifier has changed, it must be confirmed over
ec.0 or ec.10
KEB E. iEd Error! Input error detect Hardware failure at the NPN/PNP change-over or at the start/stop
measurement
KEB E. InI Error! Initialisation MFC MFC not booted
KEB E. LSF Error! Load shunt fault Load shunt relay has not picked up. Occurs for a short time during the
switch-on phase but must automatically be reset immediately. If the error
message remains the following causes may be applicable:
- load-shunt defective
- input voltage or too low
-high losses in the supply cable
- braking resistor wrongly connected or damaged
- braking module defective

KEB E. ndOH no ERROR drive overheat Motor temperature switch or PTC at the terminals T1/T2 is again in the
normal operating range. The error can be reset now
KEB E. nOH no E. over heat pow.mod. Temperature of the heat sink is again in the permissible operating range.
The error can be reset now.
KEB E. nOHI no ERROR overheat. Int No longer overheating in the interior E.OHI, interior temperature has fallen
by at least 3 degrees.
KEB E. nOL no ERROR overload No more overload. OL- counter has reached 0% after the error E.OL a
cooling phase must elapse. This message appears upon completion of the
cooling phase. The error can be reset now. The inverter must remain
switched on during the cooling phase

KEB E. nOL2 no ERROR The cooling time has elapsed. The error can be reset.
KEB E. OC Error! Overcurrent Occurs if the specified peak current is exceeded. Causes:
- acceleration ramps too short
-the load is too big at turned off acceleration stop and turned off constant
current limit
- short-circuit at the output
- deceleration ramp too short
-motor cable too long
- EMC
- DC brake at high ratings active (see 6.9.3)

KEB E. OH Error! Overhead pow.mod Error: over temperature of power module. Error can be only be reset at
E.nOH causes:
-insufficient air flow at the heat sink (soiled)
-ambient temperature too high
- ventilator clogged

KEB E. OH2 Error! Motor protection Electronic motor protective relay has tripped.
KEB E. OHI Error! Overheat internal Error: overheating in the interior: error can only be reset at E.nOHI if the
interior temperature has dropped by at least 3 degrees
KEB E.OL Error! Overload (Ixt) Error: Overload error can only be reset at E.nOL if OL-counter reaches 0%
again. Occurs if an excessive load is applied longer than for the permissible
time (see technical data): causes :
- poor control adjustment (overshooting)
-mechanical fault or overload in the application
-inverter not correctly dimensioned
-motor wrongly wired
- encoder damaged

KEB E. OL2 Error! Overload 2 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

KEB E.OP Error! Over voltage 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

KEB E.OS Error! Over speed Real speed is bigger than the max. output speed.
KEB E. PFC Error! Power factor control Error in the power factor control
KEB E. PrF Error! Prot. Rot. For The drive has driven onto the right limit switch. Programmed response
Error, restart after reset ( see chapter 6.7 , Response to errors or warning
messages)

KEB E. Prr Error! Prot . Rot. Rev The drive has driven onto the left limit switch. Programmed response Error,
restart after reset (see chapter 6.7 Response to errors or warning
messages)

KEB E. Pu Error! Power unit Error: General power circuit fault

KEB E. Puci Error! Unknown power unit Error: During the initialisation the power circuit could not be recognized or
was identified as invalid
KEB E.Puch Error! Power unit changed Error: Power circuit identification was changed: with a valid power circuit
this error can be reset by writing to SY.3 If the value displayed in SY.3 is
written, only the power-circuit parameters are reinitialized. If any other
value is written, then the default set is loaded. on some systems after
writing Sy.3 a power-on reset is necessary.

KEB E. PUCO Error! Power unit communication Error: Parameter value could not be written to the power circuit.
Acknowledgment from LT <> OK
KEB E. PUIN Error! Power unit invalid Error: Software version for power circuit and control card are different .
Error cannot be reset (only at F5-G B-housing)
KEB E.SbuS Error! Bus synchron Synchronization over sercos-bus not possible. Programmed response Error,
restart after reset
KEB E. SEt Error! Set It has been attempted to select a locked parameter set. Programmed
response Error, restart after reset
KEB E. SLF Error! Software limit switch forward The target position lies outside of the limit defined with the right software
limit switch. Programmed response Error, restart after reset

KEB E. SLr Error! Software limit switch reverse The target position lies outside of the limit defined with the left software
limit switch. Programmed response Error, restart after reset

KEB E. UP Error! Under potential 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)

KEB E.UPh Error! Phase failure One phase of the input voltage is missing (ripple-detection)
KEB A. buS Warning! Watchdog Warning: watchdog for communication between operator/control card or
operator/PC has responded. The response to this warning ca be
programmed.

KEB A. dOH Warning! Drive overhead 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

KEB A. EF Warning! External fault This warning is triggered via an external input. The response to this warning
can be programmed.
KEB A. ndOH All-clear! Drive overheat The motor temperature is again below the adjusted warning level. The
switch off time Is stopped.
KEB A.nOH All-clear! Overhead pow.mod The heat sink temperature is again below the adjusted warning level

KEB A.nOHI All clear! Internal The temperature in the interior of the inverter is again blow the warning
threshold
KEB A.nOL All clear! Overload OL counter has reached 0% the warning "overload" can be reset
KEB A.nOL2 All clear! Overload 2 The cooling time after "warning! Overload during standstill" has elapsed.
The warning message can be reset.
KEB A. OH Warning! Overhead pow.mod A level can be defined when it is exceeded this warning is output. The
response to this warning can be programmed.
KEB A.OH2 Warning! Motor protection Warning: electronic motor protective relay has tripped. The response to
this warning can be programmed.
KEB A OHI Warning! Overheat internal 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.

KEB A. OL Warning! Overload 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

KEB A. OL2 Warning! Overload 2 The warning is output when the standstill continuous current is
exceeded( see technical data and overload characteristics) . The response
to this warning can be programmed. The warning message can only be
reset after the cooling time has elapsed and A.nOL2 is displayed

KEB A. PrF Warning! Prot.rot.for. The drive has driven onto the right limit switch. The response to this can be
programmed.
KEB A. Prr Warning! Prot.rot.rev The drive has driven onto the left limit switch. The response to this warning
can be programmed.
KEB A. SbuS Warning ! Synchron Synchronisation over sercos-bus not possible. The response to this can be
programmed.
KEB A.SEt Warning! Set it has been attempted to select a locked parameter set. The response to
this warning can be programmed.
KEB A. SLF Warning! Software limit switch forward The target position ls outside of the limit defined with the right software
limit switch. The response to this warning can be programmed.

KEB A . SLr Warning! Software limit switch reverse The target position lies outside of the limit defined with the left software
limit switch. The response to this warning can be programmed.

Schneider AI2F AI2 Input AI2 signal out of range Check the wiring of analog input AI2 and the value of the signal
Schneider bOF DBR overload Incorrect DB resistor settings • 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).

Schneider bUF DB unit sh. Circuit Short-circuit output from braking unit • Check the wiring of the braking unit and the resistor.
• Check the braking resistor.
Schneider CrF1 Precharge Charging relay control condition or charging resistor damaged • Turn the drive off and then back on again.
• Check the internal connections.
• Contact Schneider Electric Product Support.

Schneider CrF2 Thyr. Soft charge Improper DC bus charging condition (thyristors) • Turn the drive off and then back on again.
• Check the internal connections.
• Contact Schneider Electric Product Support.

Schneider EEF1 Control Eeprom Control card internal memory • Check the environment (electromagnetic compatibility).
• Turn off, reset, return to factory settings.
• Contact Schneider Electric Product Support.

Schneider EEF2 Power Eeprom Power card internal memory • Check the environment (electromagnetic compatibility).
• Turn off, reset, return to factory settings.
• Contact Schneider Electric Product Support.

Schneider FCF1 Out contact stuck The output contractor remains closed although the opening conditions • Check the contactor and its wiring.
have been met • Check the feedback circuit.
Schneider HdF IGBT desaturation short circuit or grounding at the drive output • Check the cables connecting the drive to the motor, and the motor insulation.
• Perform the diagnostic tests via the
[1.10 DIAGNOSTICS] menu.

Schneider InF1 Rating error the power card is different from the card stored • Check the catalog number of the power card and ensure that it is compatible
with the drive.
Schneider InF2 Incompatible PB The power card is incompatible with the control card • Check the catalog number of the power card and ensure that it is compatible
with the drive.
Schneider InF3 Internal serial link Communication condition between the internal cards • Check the internal connections.
• Contact Schneider Electric Product Support.
Schneider InF4 internal MFG area Internal data inconsistent • Contact Schneider Electric Product Support to have the drive recalibrated.

Schneider InF6 Internal option The option installed in the controlled is not recognized • Check the catalog reference and compatibility of the option.
Schneider InF7 Internal hard init Initialisation of the drive is incomplete Turn off the drive and reset
Schneider InF8 Internal ctrl supply The control section power supply is incorrect Check the control section power supply
Schneider InF9 Internal-I measure The current measurements are incorrect • Replace the current sensors or the power card.
• Contact Schneider Electric Product Support.
Schneider InFA Internal-mains circuit The input stage is not operating correctly • Perform the diagnostic tests via the [1.10 DIAGNOSTICS] menu.
• Contact Schneider Electric Product Support.
Schneider InFb Internal-th sensor The drive temperature sensor is not operating correctly • Replace the temperature sensor.
• Contact Schneider Electric Product Support.
Schneider InFC Internal-time meas. Detected fault on the electronic time measurement component • Contact Schneider Electric Product Support.
Schneider InFE internal - CPU internal microprocessor event Turn off the drive and reset. Contact Schneider Electric Product Support
Schneider OCF Overcurrent • Motor parameters are not set correctly • Check the motor parameters.
• Excessive inertia or load • Check the size of the motor, controller, and load.
• Mechanical locking • Check the state of the mechanism.

Schneider PrF Power Removal Detected fault with the drive's Power Removal safety function Contact Schneider Electric Product Support
Schneider SCF1 Motor short circuit • Short-circuit or grounding at the drive output • Check the cables connecting the drive to the motor, and the insulation of the
• Significant earth leakage current at the controller output if several motor
motors are connected in parallel • Perform the diagnostic tests via the [1.10 DIAGNOSTICS] menu.
• Reduce the switching frequency.
• Connect chokes in series with the motor.

Schneider SCF2 Impudent sh. Circuit • Short-circuit or grounding at the drive output • Check the cables connecting the drive to the motor, and the insulation of the
• Significant earth leakage current at the controller output if several motor
motors are connected in parallel • Perform the diagnostic tests via the [1.10 DIAGNOSTICS] menu.
• Reduce the switching frequency.
• Connect chokes in series with the motor.

Schneider SCF3 Ground short circuit • Short-circuit or grounding at the drive output • Check the cables connecting the drive to the motor, and the insulation of the
• Significant earth leakage current at the controller output if several motor
motors are connected in parallel • Perform the diagnostic tests via the [1.10 DIAGNOSTICS] menu.
• Reduce the switching frequency.
• Connect chokes in series with the motor.

Schneider SOF over speed Instability • Check the motor, gain and stability parameters.
Overhauling load • Add a braking resistor.
• Check the size of the motor, controller, and load.

Schneider SPF speed feedback loss Encoder feedback signal missing. • Check the wiring between the encoder and the
drive.
• Check the encoder.

Schneider tnF Auto-tuning • Special motor, or motor power not suitable for the drive • Ensure that the motor and drive are compatible.
• Motor not connected to the drive • Ensure that the motor is present during auto tuning.
• If an output contactor is being used, close it during auto-tuning.

Schneider APF Application fault Controller inside card Check the card programming, refer to the card documentation
Schneider CnF Com. Network communication interpretation • Check the environment (electromagnetic compatibility).
• Check the wiring.
• Check the time-out.
• Replace the option card.
• Contact Schneider Electric Product Support.

Schneider COF CAN com. Interruption in communication on the CANopen bus. • Check the communication bus.
• Check the time-out.
• Refer to the CANopen user's manual.

Schneider EPF 1 External flt-Ll/bit An external device depending on user Correct the device and reset the drive
Schneider EPF 2 External fault com. a communication network Correct the communication network and reset the drive
Schneider FCF2 Out contact open. The output contractor remains open although the closing conditions have • Check the contactor and its wiring.
been met • Check the feedback circuit.
Schneider LCF input contractor the drive is not turned on even though (Mains V. timeout) (LCt) has elapsed • Check the contactor and its wiring.
• Check the time-out.
• Check the line/contactor/controller connection.

Schneider LFF2 AI2 4-20mA loss Loss of the 4 to 20 mA reference on analog input AI2, AI3 or AI4 Check the connection on the analog inputs.
LFF3 AI3 4-20mA loss
LFF4 AI4 4-20mA loss

Schneider nFF No flow fault Zero fluid • Check and correct the cause of the low flow.
• Check the zero fluid detection parameters (consult the Programming Manual
on the CD-ROM supplied with the drive).

Schneider ObF Over braking • Braking ramp too short • Increase the deceleration time.
• Overhauling load • Install a braking resistor if necessary.
• Activate the [Dec ramp adapt.] (brA) function (consult the Programming
Manual on the CD-ROM supplied with the drive), if it is compatible with the
application.

Schneider OHF Drive overheat • Ambient temperature too high Check the motor load, the drive ventilation, and the ambient temperature. Wait
• Drive ventilation blocked for the controller to cool down before restarting.
• Drive cooling fan failure

Schneider OLC Proc overload Flt Process overload (consult the programming manual CD-ROM • Check and remove the cause of the overload.
• Check the parameters of the [PROCESS UNDERLOAD] (OLd-) function (consult
the CD-ROM supplied with the controller).
Schneider OLF Motor overload • Motor power rating too small for the application Check the setting of the motor thermal current parameter. Check the motor
• Overload setting incorrect for the motor full-load rating load. Wait for the motor to cool down before restarting.
• Output phase loss (see OPF1)

Schneider OPF1 1 Motor phase loss Loose connection causing loss of one phase at controller output Check the connections from the drive to the motor
Schneider OPF2 3 motor phase loss • Motor not connected or motor power too low -Check the connections from the drive to the motor
• Output contactor open - if an output contactor is being used, consult the programming manual on the
• Instantaneous instability in the motor current CD-ROM supplied with the drive.
-Test on a low-power motor or without a motor. In factory settings mode, motor
phase loss detection is active [Output phase loss](OPL)=[Yes](YES). To check the
drive in a test or maintenance environment without having to switch to a motor
with the same rating as the drive (particularly useful in the case of high-power
drives), deactivate motor phase loss detection [Output phase loss] (OPL)=[No]
(NO)
-Check and optimize the parameters [Rated motor volt.](UnS) and [Rated mot.
current](nCr) and perform an [auto tuning] (tUn)

Schneider OSF Mains overvoltage • Line voltage too high Check the line voltage
• Disturbances in the line
supply

Schneider OtF1 PTC1 overheat overheating of the PTC1 probes detected • Check the motor load and motor size.
• Check the motor ventilation.
• Wait for the motor to cool before restarting.
• Check the type and state of the PTC probes.

Schneider OtF2 PTC2 overheat overheating of the PTC2 probes detected • Check the motor load and motor size.
• Check the motor ventilation.
• Wait for the motor to cool before restarting.
• Check the type and state of the PTC probes.

Schneider OtFL PTC=LI6 overheat overheating of the PTC probes detected on input LI6 • Check the motor load and motor size.
• Check the motor ventilation.
• Wait for the motor to cool before restarting.
• Check the type and state of the PTC probes.

Schneider PtF1 PTC1 probe PTC1 probes open or short circuited • Check the PTC probes and the wiring between them and the motor/controller.

Schneider PtF2 PTC2 probe PTC2 probes open or short circuited • Check the PTC probes and the wiring between them and the motor/controller.

Schneider PtFL LI6 = PTC probe PTC probes on input LI6 open or short-circuited • Check the PTC probes and the wiring between them and the motor/controller.

Schneider SCF4 IGBT short circuit Power component • Perform a test via the [1.10
DIAGNOSTICS] menu.
• Contact Schneider Electric Product
Support.

Schneider SCF5 Motor short circuit short circuit at drive output • 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.

Schneider SLF1 Modbus com. Interruption in communication on the Modbus bus • Check the communication bus.
• Check the time-out.
• Refer to the Modbus User's Manual

Schneider SLF2 PowerSuite com Communication with PowerSuite™ software • Check the PowerSuite -connecting cable.
• Check the time-out.
Schneider SLF3 HMI com Communication with the graphic display terminal • Check the terminal connection.
• Check the time-out.
Schneider SPIF PI feedback PID feedback below the lower limit • Check the PID function feedback.
• Check the PID feedback supervision threshold and time delay (consult the
Programming Manual on the CD-ROM supplied with the drive).

Schneider SSF Torque/current lim Switch to torque limitation • Check if there are any mechanical problems.
• Consult the Programming Manual on the CD-ROM supplied with the drive.

Schneider tJF IGBT overheat Drive overheated • Check the size of the load, motor, and controller.
• Reduce the switching frequency.
• Wait for the drive to cool before restarting.

Schneider ULF Proc. Under load Fit Process under load • Check and remove the cause of the under load.
• Consult the Programming Manual on the CD-ROM supplied with the drive.

Schneider CFF Incorrect config • Option card changed or removed • Check that there are no card errors.
• The current configuration is inconsistent • If the option card was changed or removed deliberately, consult the
Programming Manual on the CD-ROM supplied with the drive.
• Return to factory settings or retrieve the backup configuration, if it is valid
(consult the Programming Manual on the CD-ROM supplied with the drive).
Schneider CFI invalid config Invalid configuration. The configuration loaded in the controller via the bus • Check the configuration loaded previously.
or network is inconsistent • Load a compatible configuration.
Schneider HCF Card pairing The [CARDS PAIRING] (PPI-) function has been configured and a drive card • Consult the Programming Manual on the
has been changed CD-ROM supplied with the drive.
Schneider PHF Input phase loss • Controller incorrectly supplied or a fuse blown • Check the power connection and the fuses.
• Loss of one phase • Use a 3-phase mains supply
• 3-phase ATV61 used on a single phase line supply • Disable [Input phase loss] (IPL) = [No] (nO).
• Unbalanced load Monitors only with the drive on load.

Schneider PrtF Power Ident • The [Power Identification] (Prt) parameter is incorrect. • Enter the correct parameter (reserved for Schneider Electric product support).
• Control card replaced by a control card configured on a drive with a • Check that there are no card errors.
different rating • If the control card was changed deliberately, consult the Programming Manual
on the CD-ROM supplied with the drive.

Schneider USF Under voltage • Line supply too low • Check the voltage and the voltage parameter (consult the Programming
• Transient voltage dip Manual on the CD-ROM supplied with the drive).
• Damaged pre-charge resistor • Replace the pre-charge resistor.
• Contact Schneider Electric Product Support.

Mk IV Conv.FormatFail - "other Mk IV-II and VSD: ABB Converter Status failures * Contact technical support - Check the converter display panel for further messages, if there are messages,
numbers" ACS600/800, Vacon, please go to the relevant fault search list for further details.
Siemens The communicated messages cannot be
decoded, nor conforms with the expected
message
Mk IV Conv.FormatFail 0 Mk IV-II and VSD: ABB, Communications cannot be understood or are - Check the converter for correct message. * Replace NINP in ABB, if the DC link voltage fluctuated beyond 13%, also, when
CUVC (Siemens) not conform the expected messages ID motor run failed.
- If ABB converter says "Supply Phase" but supply phase is ok, then
DC Link fluctuations probably the rectifier circuit, ie NINP board is faulty * One case in Germany where a CUVC board was replaced, and the Format
Failure 0 came up. This was due to the fact that the dip - switches of the new
CUVC is different to that of the ones we used. Dip switches adjusted to same
position. Compressor run ok.

Mk IV Conv.FormatFail 113 Mk IV-II and VSD: Communications cannot be understood or are - Converter is in "stopped mode" and cannot be started - The service switch is in the wrong position (is set in service mode)
Siemens not conform the expected messages - Set the service switch back to normal position
- Service switch in wrong postion
- Outside electrical interference, switch OFF and ON compressor.

- Check the fault message on the Siemens PMU (operator panel)

Mk IV Conv.FormatFail 22 Mk IV-II and VSD: See F0022 - Power stack fault See F0022 - Run converter manually with service switch on, to see whether it is the drive or
Siemens MM4 the elektronikon

- Outside electrical interference, switch OFF and ON compressor.

- Check the fault message on the Siemens BOP (operator panel)

- See F0022

Mk IV Conv.FormatFail 225 Mk IV-II and VSD: Communications cannot be understood or are - Converter is in "stopped mode" and cannot be started - Run converter manually with service switch on, to see whether it is the drive or
Siemens not conform the expected messages the elektronikon
- Alarm A017 ?? Cannot be started by the PMU with SS switch activated?
SS changed position, however, r0012 (r050 / r051 (MM4) (or similar ) for - Outside electrical interference, switch OFF and ON compressor.
active BICO DSET did not changed? ==> PSU or IGD.
- Check the fault message on the Siemens PMU (operator panel) if A017 is
displayed, then

Mk IV Conv.FormatFail 30 Mk IV - II upgrade - Operator Panel Fault Dummy plug for the keypad not (properly) engaged, or PMU controller - Check and make sure this plug is engage via dummy plug of the hand held
Simovert P - 6SE13 . missing or faulty controller (PMU)
.GA90VSD
Mk IV Conv.FormatFail 49 Mk IV-II and VSD: MM4 Converter Status failures The service switch is in the wrong position (is set in SERVICE MODE) Set the service switch back to normal position.
GA7VSD
Mk IV Conv.FormatFail 52 MkIV (FDP) new software Converter Status failures (see ECB AIF1633) The reason is that the Elektronikon software has been updated with a new Change the following parameters on the Masterdrive by using the PMU or Drive
(and MkIII to MkIV functionality. The New Elektronikon software has the possibility to put a Monitor.
upgrad) holding torque after a stop to prevent backward rotation. This is with a new
stop command which is introduce * P60 = 7 (Parameter access)
* P53 = 7 (Enable Write Access)
* P555i001 = 6101 (old value =1) (SCom2Word1Bit1)
Mk IV Conv.FormatFail 70 Mk IV-II and VSD: ABB Converter Status failures The service switch is in the wrong position (is set in SERVICE MODE) Set the service switch back to normal position.
ACS600 / 800, Vacon
ABB: External Control Location = EXT2
(expected to be EXT1)

Vacon: Remote Control = OFF (ON expected)

Mk IV Conv.FormatFail 80 Mk IV-II and VSD: ABB, Remote Control of Converter is OFF (expected - Cause / trigger by the converter condition In the control panel, push the "LOC / REM" to set the converter to REMOTE.
Vacon to be ON) * Converter was set to LOCAL when it was suppose to be on REMOTE.

ABB: External Control Location = EXT2 This is possible when performming programming procedures on the
(expected to be EXT1) converter.

Vacon: Remote Control = OFF (ON expected)

Mk IV Conv.FormatFail 90 Mk IV-II and VSD: ABB Converter Status failures - Cause / trigger by the converter condition * Check the connection between the relevant relay and the corresponding
ACS600 / 800, Vacon * In running condition: frequency converter.
External Run Enable = OFF, (expected to be = 1. For Maint motor converter, the elektronikon K05 relay should be closed.
ON) 2. For Dryer converter (if present) the elektronikon K02 relay should be * The K05 relay (as part of the service switch condition), under normal operation,
closed. should be closed, however, due to unforseen circumstances, it was opened.
3. For Fan converter (if prese Bridge out this relay, and run the machine again. If the machine runs, then the
Elektronikon is probably has a bad relay, hence, replace the Elektronikon (or the
relay in case of emergency). This relay should only be bridged for fault finding,
under NO circumstances that this relay be remain bridged, as the converter will
run without the protection of the Elektronikon.

* If the K05 relay is bridged, but the converter still cannot, then it is the converter
fault. Check the converter fault message and follow the appropriate action
according to this fault code.

* NIOC card on the ABB converter could be faulty, please check this. This is done
by: on X2 of NIOC board, link DI1 and DI13. If this solve the problem, then the
problem is in the cable to the Service Switch or the K05 relay of the elektronikon.
Check the elektronikon if not done so.

Mk IV Conv.FormatFail 96 Mk IV-II upgrade - Converter Status failures - Cause / trigger by the converter condition * Check the connection between the relevant relay and the corresponding
Simovert P * In running condition: frequency converter.
External Run Enable = OFF, (expected to be = 1. For Maint motor converter, the elektronikon K05 relay should be closed..
ON) * The K05 relay (as part of the service switch condition), under normal operation,
Status Word 1, bit 5,6 active->switchon inhibit should be closed, however, due to unforseen circumstances, it was opened.
Bridge out this relay, and run the machine again. If the machine runs, then the
Elektronikon is probably has a bad relay, hence, replace the Elektronikon (or the
relay in case of emergency). This relay should only be bridged for fault finding,
under NO circumstances that this relay be remain bridged, as the converter will
run without the protection of the Elektronikon.
* If the K05 relay is bridged, but the converter still cannot, then it is the converter
fault. Check the converter fault message and follow the appropriate action
according to this fault code.

- NIOC card on the ABB converter could be faulty, please check this. This is done
by: on X2 of NIOC board, link DI1 and DI13. If this solve the problem, then the
problem is in the cable to the Service Switch or the K05 relay of the elektronikon.
Check the elektronikon if not done so.

Mk IV Conv.FormatFail 97 Mk IV-II and VSD: Communications cannot be understood or are Converter is in "stopped mode" and cannot be started * The service switch is in the wrong position (is set in service mode)
Siemens not conform the expected messages * Set the service switch back to normal position

* Outside electrical interference, switch OFF and ON compressor.

* Check the fault message on the Siemens PMU (operator panel)

* Siemens MasterDrive: Check the DC Link voltage and r006 parameter, see if all
agree or within tolerance of each other. If not, then either the CUVC card or
(and ??) PSU card has a problem. If the PSU card has a problem, then the Start
Inhibit may not be possible, hence the converter cannot be started by the
Elektronikon. This can also be monitored by r012 parameter, (Service Switch
parameter acknowledgement. r012 = 1 => PMU controlled, r012 = 2 =>
Elektronikon Controlled)

Mk IV Convert.Failure 0 Mk IV-II and VSD: ABB Problem cannot be read, please check the Converter problem * Check the frequency converter panel for fault messages and go to the relevant
ACS600 / 800 frequency converter panel VSD drive fault search list for further information.

* One case in Germany where a CUVC board was replaced, and the Format
Failure 0 came up. This was due to the fact that the dip - switches of the new
CUVC is different to that of the ones we used. Dip switches adjusted to same
position. Compressor run ok.

Mk IV Convert.Failure 1 Mk IV-II and VSD: ABB Short circuit Short circuit in the motor cable(s) or motor - Check the motor and motor cable
ACS600 / 800 - Check there are no power factor correction capacitors or surge absorbers in the
The output bridge of the converter unit is faulty motor cable.

Contact ABB
Mk IV Convert.Failure 128 Mk IV-III and VSD: ABB System Fault No idea No idea
ACS600 / 800
Please contact ABB Please contact ABB
Mk IV Convert.Failure 16 Mk IV-II and VSD: ABB Earth Fault - Load imbalance Typically due to earth fault in motor or motor cables Check motor and motor cables.
ACS600 / 800
Mk IV Convert.Failure 2 Mk IV-II and VSD: ABB Overcurrent Output current is excessive. The software overcurrent trip limit is 3.5 * I 2hd - Check motor load
ACS600 / 800 - Check acceleration time.
- Check motor and motor cable (including phasing)
- Check there are no power factor correction capacitors or surge absorbers in the
motor cable.
- Check encoder cable (including phase)
Mk IV Convert.Failure 32 Mk IV-II and VSD: ABB Thermistor problem Motor thermal protection mode selected as THERMISTOR and the - Check motor ratings and load
ACS600 / 800 temperature is excessive. - Check start-up data
- Check thermistor connections for digital input DI6
- Check thermistor cabling
- Check Thermistors (PT100)

Programmable Fault Function 30.04 .. 30.05

Mk IV Convert.Failure 4 Mk IV-II and VSD: ABB DC Over Voltage Intermediate circuit DC voltage is excessive. DC overvoltage trip limit is 1.3 * Check that the overvoltage controller is on (parameter 20.05)
ACS600 / 800 U1max, where U1max is the maximum value of the mains voltage range. - Check mains for static or transient overvoltage
For 400 V units, U1max is 415V. The actual voltage in the intermediate - Check Braking Chopper and Resistor (if used)
circuit corresponding to the mains vo - Check decelaration time

- Check parameter group 22

Usin Coasting to Stop function (if applicable)

Retrofit the frequency converter with a Braking Chopper and a Braking Resistor.

Mk IV Convert.Failure 64 Mk IV-II and VSD: ABB Motor temperature too high Motor temperature is too high (or appears to be too high). This can be - Check motor ratings and load
ACS600 / 800 caused by excessive load, insufficient motor power, inadequate cooling or - Check start - up data
incorrect start-up data. - Check MOTO TEMP Fault Function parameters

Programmable Fault Function 30.04 … 30.09

Mk IV Convert.Failure 8 Mk IV-II and VSD: ABB ACS 600 / 800 temperature is excessive The ACS 600 / 800 internal temperature is excessive. The trip level of - Check ambient conditions
ACS600 / 800 inverter module temperature is 125 deg. C - Check air flow and fan operations
- Check heatsink fins for dust pick-up
- Check motor power against unit power
Mk IV Convert.Timeout Mk IV-II and VSD: ABB No communication between Elektronikon and - Communication cable * Check communication cable
ACS600 / 800, Siemens, converter - Elektronikon module * Isolate converter from module, and use the VSD simulation software to test
Vacon - Converter communication card whether module or converter is at fault.
- Modbus adapter card
A PC and RS485 <-> RS232 converter box is required as well as the DFM4win
cable) is required.The cable is to be connected in place of converter cable
connection. If the RS485 port is faulty ==> new module is required.
- Replace modbus adapter card

Mk IV Converter Timeout Mk IV-III, VSD: ABB No communication between Elektronikon and - Communication cable - Check communication cable
ACS600 / 800, Siemens, converter - Elektronikon module - Isolate converter from module, and use the VSD simulation software to test
Vacon - Converter communication card whether module or converter is at fault.
- Modbus adapter card
A PC and RS485 <-> RS232 converter box is required as well as the DFM4win
cable. The cable is to be connected in place of converter cable connection. If the
RS485 port is faulty ==> new module is required.
- Replace modbus adapter card

Mk IV Converter Failure 0 Mk IV-III and VSD: ABB Problem cannot be read, please check the Converter problem Check the frequency converter panel for fault messages and go to the relevant
ACS600 / 800 frequency converter panel VSD drive fault search list for further information.
See Converter format fail 0
- Check DC link voltage, if this is fluctuated, then check NINP card.
Mk IV Converter Failure 1 Mk IV-III and VSD: ABB Short circuit Short circuit in the motor cable(s) or motor - Check the motor and motor cable
ACS600 / 800 - Check there are no power factor correction capacitors or surge absorbers in the
The output bridge of the converter unit is faulty motor cable.

Contact ABB
Mk IV Converter Failure 128 Mk IV-III and VSD: ABB System Fault No idea No idea
ACS600 / 800
Please contact ABB - Check the fault message on the operator panel.

Please contact ABB

Mk IV Converter Failure 16 Mk IV-III and VSD: ABB Earth Fault - Load imbalance Typically due to earth fault in motor or motor cables Check motor and motor cables.
ACS600 / 800
Mk IV Converter Failure 2 Mk IV-III and VSD: ABB Overcurrent Output current is excessive. The software overcurrent trip limit is 3.5 * I 2hd - Check motor load
ACS600 / 800 - Check acceleration time.
- Check motor and motor cable (including phasing)
- Check there are no power factor correction capacitors or surge absorbers in the
motor cable.
- Check encoder cable (including phase)
Mk IV Converter Failure 32 Mk IV-III and VSD: ABB Thermistor problem Motor thermal protection mode selected as THERMISTOR and the - Check motor ratings and load
ACS600 / 800 temperature is excessive. - Check start-up data
- Check thermistor connections for digital input DI6
- Check thermistor cabling
- Check Thermistors (PT100)

Programmable Fault Function 30.04 .. 30.05

Mk IV Converter Failure 4 Mk IV-III and VSD: ABB DC Over Voltage Intermediate circuit DC voltage is excessive. DC overvoltage trip limit is 1.3 - Check that the overvoltage controller is on (parameter 20.05)
ACS600 / 800 U1max, where U1max is the maximum value of the mains voltage range. - Check mains for static or transient overvoltage
For 400 V units, U1max is 415V. The actual voltage in the intermediate - Check Braking Chopper and Resistor (if used)
circuit corresponding to the mains vo - Check decelaration time

- Check parameter group 22

Using Coasting to Stop function (if applicable)

Retrofit the frequency converter with a Braking Chopper and a Braking Resistor.

Mk IV Converter Failure 64 Mk IV-III and VSD: ABB Motor temperature too high Motor temperature is too high (or appears to be too high). This can be - Check motor ratings and load
ACS600 / 800 caused by excessive load, insufficient motor power, inadequate cooling or - Check start - up data
incorrect start-up data. - Check MOTO TEMP Fault Function parameters

Programmable Fault Function 30.04 … 30.09

Mk IV Converter Failure 8 Mk IV-III and VSD: ABB ACS 600 / 800 temperature is excessive The ACS 600 / 800 internal temperature is excessive. The trip level of - Check ambient conditions
ACS600 / 800 inverter module temperature is 125 deg. C - Check air flow and fan operations
- Check heatsink fins for dust pick-up
- Check motor power against unit power
Mk IV Converter Format Fail - Mk IV-III and VSD: ABB Converter Status failures - Contact technical support - Check the converter display panel for further messages, if there are messages,
"other numbers" ACS600/800, Vacon, please go to the relevant fault search list for further details.
Siemens The communicated messages cannot be
decoded, nor conforms with the expected
message
Mk IV Converter Format Fail 0 Mk IV-II and VSD: ABB Communications cannot be understood or are - Check the converter for correct message. - Replace NINP in ABB, if the DC link voltage fluctuated beyond 13%, also, when
not conform the expected messages ID motor run failed.
- If ABB converter says "Supply Phase" but supply phase is ok, then
DC Link fluctuations probably the rectifier circuit, ie NINP board is faulty
Mk IV Converter Format Fail 49 Mk IV-III and VSD: MM4 Converter Status failures The service switch is in the wrong position (is set in SERVICE MODE) Set the service switch back to normal position.
GA7VSD
Mk IV Converter Format Fail 70 Mk IV-III and VSD: ABB Converter Status failures The service switch is in the wrong position (is set in SERVICE MODE) Set the service switch back to normal position.
ACS600 / 800, Vacon
ABB: External Control Location = EXT2
(expected to be EXT1)

Vacon: Remote Control = OFF (ON expected)

Mk IV Converter Format Fail 80 Mk IV-III and VSD: ABB, Remote Control of Converter is OFF (expected - Cause / trigger by the converter condition In the control panel, push the "LOC / REM" to set the converter to REMOTE.
Vacon to be ON) * Converter was set to LOCAL when it was suppose to be on REMOTE.

ABB: External Control Location = EXT2 This is possible when performming programming procedures on the
(expected to be EXT1) converter.

Vacon: Remote Control = OFF (ON expected)

Mk IV Converter Format Fail 90 Mk IV-III and VSD: ABB Converter Status failures - Cause / trigger by the converter condition - Check the connection between the relevant relay and the corresponding
ACS600 / 800, Vacon * In running condition: frequency converter.
External Run Enable = OFF, (expected to be = 1. For Maint motor converter, the elektronikon K05 relay should be closed.
ON) 2. For Dryer converter (if present) the elektronikon K02 relay should be - NIOC card on the ABB converter could be faulty, please check this. This is done
closed. by: on X2 of NIOC board, link DI1 and DI13. If this solve the problem, then th
3. For Fan converter (if prese

Mk IV Converter Format Fail 96 Mk IV-II upgrade - Converter Status failures - Cause / trigger by the converter condition - Check the connection between the relevant relay and the corresponding
Simovert P * In running condition: frequency converter.
External Run Enable = OFF, (expected to be = 1. For Maint motor converter, the elektronikon K05 relay should be closed..
ON) - The K05 relay (as part of the service switch condition), under normal operation,
should be closed, however, due to unforseen circumstances, it was opened.
Status Word 1, bit 5,6 active->switchon inhibit Bridge out this relay, and run the machine again. If the machine runs, then the
Elektronikon is probably has a bad relay, hence, replace the Elektronikon (or the
relay in case of emergency). This relay should only be bridged for fault finding,
under NO circumstances that this relay be remain bridged, as the converter will
run without the protection of the Elektronikon.

- If the K05 relay is bridged, but the converter still cannot, then it is the converter
fault. Check the converter fault message and follow the appropriate action
according to this fault code.

Mk IV Conveter Format Fail 113 Mk IV-III and VSD: Communications cannot be understood or are - Converter is in "stopped mode" and cannot be started - The service switch is in the wrong position (is set in service mode)
Siemens not conform the expected messages - Set the service switch back to normal position
- Service switch in wrong postion
- Outside electrical interference, switch OFF and ON compressor.

- Check the fault message on the Siemens PMU (operator panel)

Mk IV Conveter Format Fail 225 Mk IV-III and VSD: Communications cannot be understood or are - Converter is in "stopped mode" and cannot be started - Run converter manually with service switch on, to see whether it is the drive or
Siemens not conform the expected messages the elektronikon

- Outside electrical interference, switch OFF and ON compressor.

- Check the fault message on the Siemens PMU (operator panel) and
Mk IV Conveter Format Fail 97 Mk IV-III and VSD: Communications cannot be understood or are Converter is in "stopped mode" and cannot be started - The service switch is in the wrong position (is set in service mode)
Siemens not conform the expected messages - Set the service switch back to normal position

- Outside electrical interference, switch OFF and ON compressor.

- Check the fault message on the Siemens PMU (operator panel)

Mk IV ConvFormatFail 65 Mk IV-II and VSD: Communications cannot be understood or are Converter is in "stopped mode" and cannot be started - The service switch is in the wrong position (is set in service mode)
Siemens MM4 not conform the expected messages - Set the service switch back to normal position

- Outside electrical interference, switch OFF and ON compressor.

- Check the fault message on the Siemens PMU/BOP (operator panel)

Mk IV Format Fail 48 MM4 Commissioning Parameter (P010) has wrong - Commissioning Parameter (P010) has wrong definition - Change P010 back to 0 (READY)
definition * eg READY instead of other settings
Mk IV Internal failure No. 1 Mk IV with expansion Expansion module No. 1 has problem The first expansion module from the Mk IV regulator has a problem. This Check EXPANSION module no. 1 thoroughly. Reprogram module.
module could be caused by: - Check connection cable between Master module (2X3) and the expansion
- Expansion module not programmed module (. X3)
- Expansion module faulty, or no connection, or no power - Power OFF and ON the compressor

The expansion module giving the problem can be found in the "EXTRA" display,

Mk IV Internal failure No. 2 Mk IV with expansion Expansion module No. 2 has problem The first expansion module from the Mk IV regulator has a problem. This Check EXPANSION module no. 2 thoroughly. Reprogram module.
module could be caused by: - Check connection cable between Master module (2X3) and the expansion
- Expansion module not programmed module (. X3)
- Expansion module faulty, or no connection, or no power - Power OFF and ON the compressor.

The expansion module giving the problem can be found in the "EXTRA" display,
the one with the problem flashes.

Mk IV Internal failure No. 3 Mk IV with expansion Expansion module No. 3 has problem The first expansion module from the Mk IV regulator has a problem. This Check EXPANSION module no. 3 thoroughly. Reprogram module.
module could be caused by: - Check connection cable between Master module (2X3) and the expansion
- Expansion module not programmed module (. X3)
- Expansion module faulty, or no connection, or no power - Power OFF and ON the compressor

The expansion module giving the problem can be found in the "EXTRA" display,
the one with the problem flashes.

Mk IV Internal failure No. 4 Mk IV with expansion Expansion module No. 4 has problem The first expansion module from the Mk IV regulator has a problem. This Check EXPANSION module no. 4 thoroughly. Reprogram module.
module could be caused by: - Check connection cable between Master module (2X3) and the expansion
- Expansion module not programmed module (. X3)
- Expansion module faulty, or no connection, or no power - Power OFF and ON the compressor

The expansion module giving the problem can be found in the "EXTRA" display,
the one with the problem flashes.

Mk IV Internal failure No. 5 Mk IV with expansion Expansion module No. 5 has problem The first expansion module from the Mk IV regulator has a problem. This Check EXPANSION module no. 5 thoroughly. Reprogram module.
module could be caused by: - Check connection cable between Master module (2X3) and the expansion
- Expansion module not programmed module (. X3)
- Expansion module faulty, or no connection, or no power - Power OFF and ON the compressor

The expansion module giving the problem can be found in the "EXTRA" display,
the one with the problem flashes.

Mk IV Internal failure No. 6 Mk IV with expansion Expansion module No. 6 has problem The first expansion module from the Mk IV regulator has a problem. This Check EXPANSION module no. 6 thoroughly. Reprogram module.
module could be caused by: - Check connection cable between Master module (2X3) and the expansion
- Expansion module not programmed module (. X3)
- Expansion module faulty, or no connection, or no power - Power OFF and ON the compressor

The expansion module giving the problem can be found in the "EXTRA" display,
the one with the problem flashes.

Mk IV Internal failure No. 7 Mk IV with expansion Expansion module No. 7 has problem The first expansion module from the Mk IV regulator has a problem. This Check EXPANSION module no. 7 thoroughly. Reprogram module.
module could be caused by: - Check connection cable between Master module (2X3) and the expansion
- Expansion module not programmed module (. X3)
- Expansion module faulty, or no connection, or no power - Power OFF and ON the compressor

The expansion module giving the problem can be found in the "EXTRA" display,
the one with the problem flashes.

Siemens MasterDrive A015 MasterDrive Series - CUVC External alarm 1 Parameterizable external alarm input 1 has been activated Check:
- whether the cable to the corresponding digital input has been interrupted.
- parameter P588 Src No Ext Warn 1
Siemens MasterDrive A016 MasterDrive Series - CUVC External alarm 2 Parameterizable external alarm input 2 has been activated Check:
- whether the cable to the corresponding digital input has been interrupted.
- parameter P588 Src No Ext Warn 2
Siemens MasterDrive A017 Masterdrive / CUVC, CU2 Drive is not in healthy state - Possibly due to faulty IGD. SS is also not able to perform properly. R012 (Active - Remove the drive and perform visual inspection of IGD.
BICO) does not change state when SS change position - IGD (and maybe PSU) may need replacement.
- Also possible is power supply card is faulty, hence not able to give the converter
the correct signals to inhibit the

Siemens MasterDrive A020 MasterDrive Series - CUVC Overcurrent An overcurrent condition has occurred Check the driven load for an overload condition.
- Are the motor and the converter matched?
- Have the dynamic performance requirements been exceeded.
Siemens MasterDrive A021 MasterDrive Series - CUVC Overvoltage An overvoltage condition has occurred Check the supply voltage. The converter regenerates without regeneration possbility.

Siemens MasterDrive A022 MasterDrive Series - CUVC Inverter temperature The threshold for initiating an alarm has been exceeded. 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

Siemens MasterDrive A023 MasterDrive Series - CUVC Motor temperature The parameterizable threshold for initiating an alarm has been exceeded. - 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.
Siemens MasterDrive A024 MasterDrive Series - CUVC Motor movement The motor has been moved during motor data identification Lock the motor.
Siemens MasterDrive A025 MasterDrive Series - CUVC I2t inverter If the instantaneous load condition is maintained, then the inverter will be Check:
thermally overloaded. - P72 Rtd Drive Amps
- MLFB P70
- P128 Imax
- r010 Drive Utilizat

Siemens MasterDrive A029 MasterDrive Series - CUVC I2t motor The parameterized limit value for the I2t monitoring of the motor has been Motor load cycle is exceeded !!
exceeded. Check:

- P382 Motor Cooling

- P383 Mot Tmp T1
- P384 Mot Load Limits

Siemens MasterDrive A033 MasterDrive Series - CUVC Overspeed Bit 3 in r553 status word 2 of the setpoint channel. The speed actual value has - P804 Overspeed Hys plus
exceeded the value of maximum speed plus the set hysteresis. - P452 n/f(max, FWD spd) or
- P453 n/f(max, REV spd) has been exceeded.
Increase the parameter for the maximum frequencies or reduce the regenerative load.

Siemens MasterDrive A034 MasterDrive Series - CUVC Setpoint/actual value deviation Bit 8 in r552 status word 1 of the setpoint channel. The difference between Check:
frequency setpoint/actual value is greater than the parameterized value and the - whether an excessive torque requirement is present.
control monitoring time has elapsed. - whether the motor has been dimensioned too small.

Increase values P792 Perm Deviation Frq/set/actual DevSpeed and P794 Deviation Time.

Siemens MasterDrive A042 MasterDrive Series - CUVC Motor stall/lock Motor is stalled or blocked. Check:
- Whether the drive is locked
The alarm cannot be influenced by P805 "PullOut/BlckTime", but by P794 - Whether the encoder cable is interrupted during speed control and whether the shield
"Deviation Time" is connected.
- Whether the drive has stalled
- For synchronous motors (P095 = 12): excitation current injection

Siemens MasterDrive A075 MasterDrive Series - CUVC Ls, Rr Dev The measured values of the leakage measurement or of rotor resistance deviate Usually the leakage reactance P122 is the average value resulting from the measured
significantly. values in r546.1…12, and the rotor resistance r126 from the values in r542.1..3.
If individual measured values significantly deviate from the average values, they are
automatically not taken into account for the calculation (for RI) or the value of the
automatic parameterization remains (for Ls). It is only necessary to check the results for
their plausibility in the case of the drives with high requirements on torque or speed
accuracy.

Siemens MasterDrive A078 MasterDrive Series - CUVC Stands. Meas The standstill measurement is executed when the converter is powered up. The If the standstill measurement can be executed withou any danger:
motor can align itself several times in a certain direction with this measurement. - Power up the converter.

Siemens MasterDrive A079 MasterDrive Series - CUVC Mld Inv Stop The rotating measurement has been aborted or cannot commence because an P561 Scr InvRelease - Release the inverter
inverter stop command is present.
If necessary, re-start the measurement by powering up the converter.
Siemens MasterDrive A080 MasterDrive Series - CUVC Motld: Dr.M When the converter is powered up, the rotating measurement automatically If the rotating measurement can be executed without any danger:
accelerates the drive. The drive can then only be externally controlled in a
restricted fashion. - Power up the converter.
Siemens MasterDrive E All masterdrive CUVC series - Insufficient power to display panel (PMU) Either the power supply card (PSU1) or the CUVC card is faulty. At terminal X101 of CUVC card check:
GA30VSD . . .
- Pin 1 & 2: Use Vdc multimeter to check for 24 Vdc. If not, then the power supply card,
PSU1 is faulty.
Also, at X102, pin 13 should have 10 Vdc, and pin 14 = -10Vdc, with pin 2 common.

If these voltages are present, then the CUVC card is faulty.

Siemens MasterDrive F0 GA50VSD - CU2 Converter Fail. Undefined error code, not enough - This is an defined error code, meaning that there was not enough time to read - Check for loose connections
time to register fault out the fault message from the converter. - Try to reprogam the MKIII

- Most probably caused by a voltage interruption.

Siemens MasterDrive F001 Siemens CU2, CUVC Contactor Checkback If the a contactor checkback signal is configured, a checkback signal was not P591 S.MC chkbck sign.
received within 500ms after the power-up command The parameter value must match the main contactor checkback signal connection. Check
the main contactor checkback signal circuit.

Should NEVER happen in Masterdrive Series.

Siemens MasterDrive F002 Siemens MasterDrive Series Pre-Charging - When pre-charging, the minimum DC link voltage (P071 Line volts x 1.34) of 80% - Check the supply voltage.
CU2, CUVC has not been reached . - Can fail if low V, because software setting for V is wrong.
- Compare with P071 Line Volts (Compare P071 with the DC link voltage on DC units)
- The maximum pre-charging time of 3 seconds has been exceeded. - Check the rectifier / regenerative unit on DC units. The rectifier/regenerative unit on
DC units. The rectifier/regenerative unit must be switched on before the inverter is
- SHOULD NEVER HAPPEN DURING OPERATION, ONLY HAPPEN AT STARTUP switched on.
- Check voltage C and D. Should get high 500V's (dc). While having the multimeter on it,
please restart the machine (in converter local control mode). If the voltage deteriorate in
over a short period of time, then there is pre-charge problem, hence, change the pre-
charger PCB, or Siemens to change it if under warranty. For G85GA30VSD case, the
whole drive should be return to Siemens for evaluation, if under warranty.
Siemens MasterDrive F006 Siemens CUVC (MasterDrive) DC link Overvoltage - Shutdown due to excessive DC link voltage - Check supply voltage or DC voltage
- Converter is working at upper tolerance limit and at full load.
- Can be caused by line phase failure
- Converter is operating in regenerative mode without feedback possibility
- Try:
- Increase P464 Decel Time
- Activate P515 DC Bus Volts Reg (check P071 beforehand)
- Reduce P526 Fly Search Speed
- Reduce P259 Max Regen Power (only for P100 = 3, 4 or 5)
On a GA 37 VSD, that we have been working on was starting /stopping intermittantly.
It had the same problem as before showing an erratic DC Link voltage at the PMU, with
stable voltage at the DC Link. The original power supply (PSU) was faulty, and replaced
with a new PSU. Weeks later, the problem still existed.
The problem was traced to a break it a joint on the power supply control card that was
replaced by us.
The card was repaired onsite and the problem rectified.

Siemens MasterDrive F008 Siemens CUVC (MasterDrive) DC link Undervoltage - The lower limit value of 76% of the DC link voltage (P071 Lin Volts), or 61% when - Check Input DC voltage
kinetic buffering has benn enabled, has been fallen short of. - DC link - Check for PCC (precharger card) and PCU (Precharger Unit - the less dense in
- Undervoltage in the DC link with active kinetic buffering and speed less than 10% terms of electronics, of the two cards - This card normally OK)
of the rated motor speed. - Maybe diodes blown as well, please check.
- Check for thyristor modules, should be approx. 6v in-circuit diode check! And OPEN-
CIRCUIT out-of-circuit diode check !
- IVI card may be faulty as well.
- Terminal C and D should be checked using multimeter with Vdc, or some sort of Scope
meter. Should expect to be in excess of 500Vdc
- Can also be seen Simovis program. Parameter r006 (DC bus voltage). Can be checked
on PMU as well

Siemens MasterDrive F010 Siemens CUVC (MasterDrive) DC link Overvoltage MOST UNLIKELY TO OCCUR IN OUR APPLICATION - Check supply voltage
- Due to excessive DC link voltage, shutdown has taken place. - Check braking resistors
- Lower threshold value than F006 - Converter operates regeneratively without a feedback possibility. Braking unit must be
set to the lower response then threshold (673V)

Siemens MasterDrive F011 Siemens CUVC Overcurrent - Overcurrent shutdown has occurred. - Check the free rotation (by hand) of the compressor element / motor
(MasterDrive), CU2 - The shutdown threshold has been reached. - Check connections at the measuring devices in the front of the converter
- The phase in which an overcurrent has occurred is indicated in a bit-coded - Check if incoming supply voltage < 400 -10% and verify if cable section is accurate to
manner in the fault value (see r949) spec. (min 50mm square)
Phase U--> Bit 0 = 1--> fault value = 1 - Check RFI - net filter for short circuit
Phase V--> Bit 1 = 1- - Check the converter output for short-circuit or earth fault
- Check the load for an overload condition
- Check whether motor and converter are correctly matched (this should always be true)
- CT (current transformer) maybe faulty. As current is asked for again and again causing
build up of --> overcurrent. This condition is usually NOT intermittent. CT are very hard
to check, can only be done by v/hz meter and observe for characteristics.
- Check IVI (inverter interface card), replace if cannot solve. Check ABO (adaptor board),
ABO and IVI must be matched.
- Check the resistance of the motor windings in the 3 phases
- Try to start without back pressure, ie with an empty air net
- Try to program P0462 to 30 sec for slower acceleration
- Try new CUVC board
* The fault display must be cleared first before the parameters can be accessed. If the
F011 cannot be cleared, then it is probably the CT (LEM) module is at fault.
But to clear the fault, the scroll UP / DOWN must be pressed at the same time.
When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and L1(u), then L2(v) and L3(w); D across L1(u), L2(v) and L3(w).

If we get short in any of the combinations, eg, resistance between C and L1 then the
IGBT (transistor) is damaged. For all IGBT's to be OK, then some resistance is expected on
all combinations.

Try to start the converter with MOTOR DISCONNECTED and Service switch to manual
control:
- To do this, please observe and adjust the following parameters:
For CUVC MasterDrive:
- Make P53 = 6 (on Simovis, it is binary number . . . 110), then P060 = 5 (Drive Setting),
then P100.1 = 3 (f regulated) to P100.1 = 1 (u/f). The idea here is to change the VECTOR
CONTROL to voltage control. THEN, change P060 = 0 (or 1) in order to start the converter
manually. If NOT, then 005 always appear on the PMU.

If F011 CANNOT be resolved, and P060 = 5, and DOES NOT able to be programmed back
to P060 = 0 or 1, then the CT (LEM) is faulty. This symptom occurs when the PMU is been
Siemens MasterDrive F012 Siemens CUVC (MasterDrive) Current too Low During excitation of the induction motor, the current did not rise above 12.5% of - Only for closed loop n/f/T control (P100 = 3, 4 or 5)
the setpoint magnetising current for no-load operation - If no motor is connected, go into the simulation mode P372
- Check current detection, check power section
Siemens MasterDrive F014 Siemens CUVC (MasterDrive) I too low SHOULD NOT HAPPEN - Check the output contactor
- During excitation of the motor, the current component is less than 25% of the - Check the motor cable
motor no-load current
- Only U800 = 1
irrespective of the type of control
(Difference to F012)
Siemens MasterDrive F015 Siemens CUVC (MasterDrive) Motor Stall - Likely cause is mechanical blockage of motor - Check Motor / element for free rotation
- Motor has stalled or locked - Check current in all three phases to the motor, make sure that they are within 10% of
- If the static load is too high each other.
- Possible that a bearing has failed, ie, the non-drive end, thus still enable the - Check the bearings of the motor.
motor the ability to rotate at slow speed - Reduce Load
- Drive in running - Increase current Limits
- Reprogram card
- Change new CUVC card

- Could be one phase missing, where consumption on all 3 phases arevery different.E97
- One case in Switzerland, where the burned cables on RFI filters or bad contacts on the
inverter bridge.

Siemens MasterDrive F019 Siemens CUVC (MasterDrive) Motor not found - Motor been stolen / not there - Power up after coasting
- Flying restart without tachometer - Possibly increase P525 Fly Search Amps
Siemens MasterDrive F020 Siemens CUVC (MasterDrive) Motor Temperature The motor temperature limit value has been exceeded. - Check the motor (load, ventilation, etc). The actual motor temperature can be read in
* r949 = 1 means limit value of motor temperature exceeded r009 of Siemens PMU (panel display)
* r949 = 2 means short-circuit in cable to the motor temperature sensor or sensor - Motor temperature.
defective. - Check P381 Mot Temp settings.
* r949 = 4 means wire break in cable to the motor - Fault - check the KTY84 input at connector - X103:29, 30 for short circuit.
KTY84 resistance at room temperature should be in the vicinity of 700 - 1000 Ohms
- Check with multimeter, Converter trips when infinite resistance registered.

CHECK: Input of CUVC (ie analog inputs at X103:29,30 and related software / hardware
wiring.)

Use a 0 - 4kOhms potentiometer, and connect to X103:29,30. (For the potentiometer,

short the middle lead to ONE of the other leads)
Make parameter P044.1 = K245 (Mot Temp) . . . . . . . K245 means input is of type KTY84
thermistor / resistor
Check parameter r045. Reading on r045 should change as potentiometer to X103:29,30
changes. If not, then CUVC card may be faulty.

If the card is ok, then r009 = r045 = settings of potentiometer / KTY84 thermistor.

CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance in
supply voltage can lead to 10% extra current in one of the motor phases. 3.5% unbalance
in supply voltage will give 25 deg. C higher in motor temperature.

EMERGENCY ONLY:
Make Parameter P380.1 = 0
Parameter P381.1 = 0
The compressor / drive will now run without thermal protection on the motor.

MOTOR TEMP SENSOR (KTY 84) IS BEING REPLACE BY STANDARD MOTOR THERMISTOR
- This may happen when the KTY 84 motor temperature is not available at time of
service / breakdown, and a new standard motor thermistor is being fitted.
- If a standard motor thermistor is being fitted instead, the Masterdrive will not able to
display the actual motor temperature, HOWEVER, it will still the protects the system and
shutdown at and above temperature 180 deg. C.

** Parameter changes to suit STANDARD THERMISTOR modification:

- P380.1 = 0
- P381.1 = 1 (=1 to make the input to the CUVC of 1.5 Kohms when temperature is 180
deg. C)
- P385 = DE-ACTIVATED (automatically)
Siemens MasterDrive F021 Siemens, CUVC Motor I2t Parameterized limit value of the I2t monitoring for the motor has been exceeded. Check : P383 Mot Tmp T1

Siemens MasterDrive F023 Siemens converter, CUVC Inverter Temperature The limit value of the inverter temperature has been exceeded. Measure the air intake and ambient temperature. Please observe the reduction curves
at >40 deg. C
R949 = 1 : Limit value of inverter temperature has been exceeded.
R949 = 2 : Sensor 1 : wire break of sensor cable or sensor defective. Check:
- Whether the fan E1 is connected and is rotating in the correct direction
r949 = 18 : Sensor 2 : " " - that the air entry and discharge openings are not restricted
r949 = 34 : Sensor 3 : " " - Temperature sensor at -X30
Siemens MasterDrive F025 GA50VSD - CU2 UCE ph. L1 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L1 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 2 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted

When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.
- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.G98

PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-

ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.
NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
Siemens MasterDrive F026 GA50VSD - CU2 UCE ph. L2 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L2 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 2 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted
When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.

- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.
PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-
ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.

NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
Siemens MasterDrive F027 GA50VSD - CU2 UCE ph. L3 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L3 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 2 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted

When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.
- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.

PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-

ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage E100will give 25 deg. C higher in motor temperature.
NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
Siemens MasterDrive F028 GA50VSD - CU2 Supply phase The frequency and amplitude of the DC link ripple indicates a single phase supply - Check supply voltage
CUVC failure. - Check the proper connection at the line reactor (L1)
- Check if one of the coils of line reactor L1 is short circuit.F106
Similar to F8

Siemens MasterDrive F029 Siemens, all VSD's except Measured Valued Sensor Fault occurs in the measured value sensing system - Possibly CU is faulty
GA90VSD Simovert P r949 = 1 Offset adjustment not possible in phase L1 - IGBT or IGD may be defective as it is conductive while signal command does not tell it
r949 = 2 Offset adjustment not possible in phase 3 to do so.
r949 = 3 Offset adjustment not possible in Phases 1 & 3 - Defective phase section
r949 = 65 The analog inputs cannot be automati

Siemens MasterDrive F035 VSD - Siemens CUVC / CU2 External fault 1 - External fault 1 has been triggered - Check cabinet for ventilation
- Check for loose connections
- External fault 1 parameter is used for temperature sensor for the cabinet, and it
is parameterised trigger when temp reaches 51 deg. C

Usually happen during hot weather / conditions

P575 Src No ExtFault1

Siemens MasterDrive F036 AIF VSD - Siemens CUVC External fault 2 - External fault 2 has been triggered The problem probably does not related to the Masterdrive converter, and because it
ZT37VSD - This failure can be caused by a wrong or loose connection from the micromaster receives faulty signals from the external, hence EXTERNAL FAULT #2 comes up. Should
(fan motor control ) to the main convertor (main motor control). GA180VSD and check for problems outside the main converter.
others which have micromaster
- Aux. Drive Fault. ZT37VSD - See ECB 1339

- GA180VSD and related

Siemens MasterDrive F040 Siemens CU2, CUVC AS internal fault Incorrect operating status Replace CU card (A10)
GA50VSD
Siemens MasterDrive F041 Siemens CU2, CUVC EEPROM fault a fault has occurred when storing the values in the EEPROM Replace CU card (A10)
GA50VSD
Siemens MasterDrive F042 Siemens CU2, CUVC Computing time problem Calculating time problem Reduce the calculating time by:
GA50VSD
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

Siemens MasterDrive F043 Siemens CU2, CUVC Coupling int. Internal coupling error. One of the two coupling partners does not respond - Check MWH - CU2 connection
GA50VSD - Replace CU card (A10)
Siemens MasterDrive F044 Siemens CU2, CUVC BiCo manager Fault - A fault has occurred during the softwiring of Binectors and connectors - Reparameterize
GA50VSD - Reset unit
- Replace CU card (A10)
In CUVC, observe r949:
> 1000: Fault during softwiring of connectors
> 2000: Fault during softwiring of binectors

Siemens MasterDrive F045 Siemens CU2, CUVC Opt. Board HW Hardware fault has occurred when assessing an optional board - Replace CU (A10)
GA50VSD - Check connection of the board and optional boards.
Siemens MasterDrive F046 Siemens CU2, CUVC Par task / con. A fault has occur during the transfer of parameters to the gating unit processor - Power unit down and up again
GA50VSD - Replace CU (A10)
Siemens MasterDrive F047 Siemens CU2, CUVC Gating Calc Time / internal Comp. Time The calculating time in the gating unit computer is not sufficient Replace CU (A10)
GA50VSD
Siemens MasterDrive F1 Siemens CCU - Simovert P Incorrect phase sequence Incorrect phase sequence Reverse 2 incoming lines
GA90VSD
Siemens MasterDrive F100 Siemens CUVC, CU2 GRND Init During the ground fault test, a current not equal to 0 was measured, or a UCE or On PMU / Simovis - The fault cause can be read our of r358 (CU2) or r 376 (CUVC)
the overcurrent monitoring responded, although none of the valves were "ground fault test result"
triggered. - Check the converter output for short circuit of ground fault (-X2:U2, V2, W2 - including
motor)
- Check CU is inserted correctly
Frame Sizes 1 & 2
- Check the transistor modules on the PEU board A23 for short circuit
Frame Sizes 3 & 4
- Check transistor modules A100, A200, A300 for short circuit

Siemens MasterDrive F101 Siemens CUVC, CU2 GRND UCE During the ground fault test a UCE monitoring function responded in a phase in Check the power section valves for a short circuit, and for converters with fiber-optic
which no valve was triggered gating, the gating unit and the UCE checkback signals, for the correct assignment.
Transistor conductive when not triggered to do so PMU / Simovis: r358 (CU2), r376 (CUVC) can be interrogated to indicate which UCE mo

Siemens MasterDrive F102 Siemens CUVC, CU2 GRND Phase During the ground fault test, current flowed in one phase when none of the valves PMU / Simovis: Read-out fault value from R949. The digit of the xth position indicates
were triggered, or the UCE monitoring in the phase responded in which the valve the valve, where the fault occurred at power-up.
was triggered.
XOOO Digit X = 1 = V+, X = 2 = V-, X = 3 = U+
Digit X = 4 = U-, X = 5 = W+, X = 6 = W-

The digit of the xth position defines the pahse, in which i is 0 and thus a valve is
defective (always conductive)
OOOX Digit X = 1 = Phase 1 (U)
X = 3 = Phase 3 (W)
X = 4 = Phase 1 (U) r 3 (W)

Examine phase for defective valves (always conductive)

Siemens MasterDrive F103 Siemens CUVC, CU2 Ground fault An earth fault or a fault in the power section is present. During the ground fault PMU / Simovis: Read-out fault from r949. The digit of the xth position specifies the valve,
test, a current flows from the phase in which a valve was triggered, the which, when triggered, manifested the fault.
overcurrent comparitor responded, or a UCE monitoring in a phase has responded
in which a valve wa XOOO x = 1 = V+, x = 2 = V-, x = 3 = U+
x = 4 = U-, x = 5 = W+, x = 6 = W-
Check the motor including feeder cable for ground faults. If there is no ground fault,
check the power section for defective valves which remain conductive.

The digit of the xth position defines the phase in which I is 0, and therefore a valve must
be defective (always conductive)
OOOX Digit x = 1 = Current in phase 1(U)
x = 2 = UCE in phase 2 (V)
x = 3 = Current in phase 3 (W)
x = 4 = Only overcurrent occur

The motor speed should be less than 10% of the stated speed during the ground fault
test !

A ground fault is present in phase V, or there is a defective valve (always conductive)

Siemens MasterDrive F12 Siemens CCU - Simovert P - Overcurrent Short circuit, low-resistance ground fault - Check the free rotation of the compressor element and/or motor eg a motor bearing
6SE13 . . . failure
GA90VSD - Check motor windings for possible ground fault
- Check resistance of the motor windings in the 3 phases
- Try start with no back pressure, ie with an empty net
- Check parameter P019 for the proper value (320A); as a trail lower the value in steps of
5 A to a minimum 300A
- Current transfomer may be faulty.
- Try new CCU board.

PLEASE NOTE: on former model GA90 VSD (SN < AII 492 000) Please observe ECB AII0070
(Priority IV) with regards to OIL RESTRICTION AT LOW SPEED for GA90VSD with Simovert
P converter.

CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance in
supply voltage can lead to 10% extra current in one of the motor phases. 3.5% unbalance
in supply voltage will give 25 deg. C higher in motor temperature.

PLEASE BE ENSURED THAT THE RESISTOR BANK FROM THE GAX CARD IS FUNCTION
PROPERLY. AS EXPERIENCED IN ACNZ HAS SHOWN THAT FAULTY RESISTOR BANK CAN
(AND PROBABLY WILL) DISGUISE ITSELF HAS F14, F12, ETC. AND ARE INTERMITTENT
FAULTS.

BECAUSE THE RESISTOR BANK HAS TO BE TAKEN OUT EVERYTIME THE GAX CARD BEEN
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.
Siemens MasterDrive F13 Siemens CCU - Simovert P - Motor Overload Motor overload (calculated): Motor current too high for too long a period. - Check for mechanical resistance in compressor / motor
6SE13 . . . - Check the small hole of 4mm in the centre of the boss in the check valve housing which
GA90VSD ensures the full opening of the check valve.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C E120higher in motor temperature.

PLEASE BE ENSURED THAT THE RESISTOR BANK FROM THE GAX CARD IS FUNCTION
PROPERLY. AS EXPERIENCED IN ACNZ HAS SHOWN THAT FAULTY RESISTOR BANK CAN
(AND PROBABLY WILL) DISGUISE ITSELF HAS F14, F12, ETC. AND ARE INTERMITTENT
FAULTS.

BECAUSE THE RESISTOR BANK HAS TO BE TAKEN OUT EVERYTIME THE GAX CARD BEEN
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.

Siemens MasterDrive F14 Siemens CCU - Simovert P - Motor Pullout Load too high, or excessive dynamic stressing. - Check for mechanical resistance in compressor / motor
6SE13 . . . Seized element. - Check the small hole of 4mm in the centre of the boss in the check valve housing which
GA90VSD ensures the full opening of the check valve.

- PLEASE NOTE: on former model GA90 VSD (SN < AII 492 000) Please observe ECB
AII0070 (Priority IV) with regards to OIL RESTRICTION AT LOW SPEED for GA90VSD with
Simovert P converter.
PLEASE BE ENSURED THAT THE RESISTOR BANK FROM THE GAX CARD IS FUNCTION
PROPERLY. AS EXPERIENCED IN ACNZ HAS SHOWN THAT FAULTY RESISTOR BANK CAN
(AND PROBABLY WILL) DISGUISE ITSELF HAS F14, F12, ETC. AND ARE INTERMITTENT
FAULTS.

BECAUSE THE RESISTOR BANK HAS TO BE TAKEN OUT EVERYTIME THE GAX CARD BEEN
CHANGED, HENCE THERE IS A CHANCE IT WILL DETERIORATE OVER TIMES.E122

Siemens MasterDrive F148 CUVC Series - ZR160VSD Active Signal @ binector U061 is present. ZR160VSD: ZR160VSD:
(ECB1397/C1 implemented) - Temperature limiting switch of motor is activated - open contact, ie, motor - Based on ECB 1397/C1, this fault is present if the terminal X101-7 of the CUVC card is
overtemperature. open contact.
- Faulty temperature limiting switch. - This happen if the motor temperature is too high, or the temperature switch is faulty,
- Loose connection at X101: 1 & 7 or loose connections. Please check these conditions..

Supplementary Reading:
* See function diagram 710, where binector U061 = 0 was made to U061 = 19,
* Binector U952.i059 = 20 was made to U952.i059 = 4.

Siemens MasterDrive F15 GA50VSD - CU2 Motor stall Motor stalled or locked - Check motor
Could be one phase missing, where consumption on all 3 phases arevery different. - One case in Switzerland, where the burned cables on RFI filters or bad contacts on the
inverter bridge.

Siemens MasterDrive F2 Siemens CCU - Simovert P - PreCharge Error Precharging malfunction, line voltage, inverter defective May occur after a long period of standstill. In this case, restart the machine for up to 10
6SE13 . . . times.
GA90VSD If fault persists, check:
- Supply voltage is within tolerance 400V +/- 10%
- PCC (PreCharging Circuit)
- One of the capacitors may be defective
Siemens MasterDrive F20 GA50VSD - CU2 Motor Temp. Motor thermistor problem - Check the motor (load, ventilation, etc). The actual motor temperature can be read in
- Motor overheat r009 of Siemens PMU (panel display)
- Motor temperature.
r949 = 1 Motor temperature limit exceeded - Check P381 Mot Temp settings.
r949 = 2 Short circuit in the cable to the temperature sensor or sensor defect - Fault - check the KTY84 input at connector - X103:29, 30 for shortcircuit.
r949 = 3 Open circuit in the cable to the temperature sensor or sensor defect KTY84 resistance at room temperature should be in the vicinity of 700 - 1000 Ohms
- Check with multimeter, Converter trips when infinite resistance registered.
CHECK: Input of CUVC (ie analog inputs at X103:29,30 and related software / hardware
wiring.)

Use a 0 - 4kOhms potentiometer, and connect to X103:29,30. (For the potentiometer,

short the middle lead to ONE of the other leads)
Make parameter P044.1 = K245 (Mot Temp) . . . . . . . K245 means input is of type KTY84
thermistor / resistor
Check parameter r045. Reading on r045 should change as potentiometer to X103:29,30
changes. If not, then CUVC card may be faulty.

If the card is ok, then r009 = r045 = settings of potentiometer / KTY84 thermistor.
CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance in
supply voltage can lead to 10% extra current in one of the motor phases. 3.5% unbalance
in supply voltage will give 25 deg. C higher in motor temperature.
EMERGENCY ONLY:
Make Parameter P380.1 = 0
Parameter P381.1 = 0
The compressor / drive will now run without thermal protection on the motor.
MOTOR TEMP SENSOR (KTY 84) IS BEING REPLACE BY STANDARD MOTOR THERMISTOR
- This may happen when the KTY 84 motor temperature is not available at time of
service / breakdown, and a new standard motor thermistor is being fitted.
- If a standard motor thermistor is being fitted instead, the Masterdrive will not able to
display the E123actual motor temperature, HOWEVER, it will still the protects the system
and shuddown at and above temperature 180 deg. C.

** Parameter changes to suit STANDARD THERMISTOR modification:

- P380.1 = 0
- P381.1 = 1 (=1 to make the input to the CUVC of 1.5 Kohms when temperature is 180
deg. C)
- P385 = DE-ACTIVATED (automatically)
Siemens MasterDrive F21 GA50VSD - CU2 Motor I2t. Parameterized limit value of the i2t - Check P363 Mot.temp T1
monitoring for the motor was excedded
Siemens MasterDrive F23 GA50VSD - CU2 Inverter Temp. The temperature limit of the inverter has been exceeded. - Check fan E1 is working, and in the correct direction
- Temperature sensor at -X30
r949 = 1 The temp. limit of the inverter has been exceeded
r949 = 2 Sensor 1: Wire break in the sensor wire or sensor defect
r949 = 18 Sensor 2: ""
r949 = 34 Sensor 3:

Siemens MasterDrive F243 MasterDrive VSD Link Internal Fault in internal linking. One of the two linked partners does not reply. Replace Cuxx (-A10)
Siemens MasterDrive F25 GA50VSD - CU2 UCE ph. L1 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L1 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 1 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted

When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.
- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.

When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.
PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-
ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.
NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
Siemens MasterDrive F255 MasterDrive VSD Fault in EEPROM A fault has occurred in the EEPROM Switch off the unit and switch it on again. If the fault re-occurs, replace the Cuxx
Siemens MasterDrive F26 GA50VSD - CU2 UCE ph. L2 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L2 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 1 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted

When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.
- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.

PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-

ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.
NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
Siemens MasterDrive F27 GA50VSD - CU2 UCE ph. L3 - Loose / bad connection, - Check the torque on all power connections
CUVC There was an UCE shut down in phase L3 - Short circuit in one of the electronics board, - Check voltage before and after the netfilter (A1)
- Imbalance in supply line voltage - Check voltage before and after main switch
- IGBT / IGD1 faulty. - Check voltage before and after the line reactor (L1)
- Check if IGBT or IGD1 is defective
Higher level of F11
If the IGD (IGBT driver card) is short circuited in on of the terminal supply to the IBGT,
when power is on, it probably would blow out the IGBT(s) on that particular line.

- Check phase 1 for short-circuit or ground fault (-X2:U2 including motor)

- Check CU is correctly inserted
When power is completely down, ie dc voltage across C (+) and D (-) is zero V, then check
for resistance across C and u1, then v1 and w1; D across u1, v1 and w1; C and u2, then
v2 and w2; D across u2, v2 and w2.
If we get short (very low resistance, say 2 ohms) in any of the combinations, eg,
resistance between C and u1 then the IGBT (transistor) is damaged. For all IGBT's to be
OK, then some resistance in the vicinity of 100kOhms is expected on all combinations.

- Check individual IGBT if practicable. By using the multimeter and "DIODE CHECK"
function, measure across terminal 2 --> 1 of IGBT. This value should be around 0.2Vdc,
and 1 -- > 2 of IGBT. This value should be L Vdc. When, checking for IGBT, please ensure
that the cables are disconnected from the IGBT, otherwise, measurements maybe not
give true indication.
When a faulty IGBT is found, it is recommended to replace ALL IGBTs within that line
(phase). In general, as one IGBT is blown, chances are the other(s) in the same line
maybe on its way out as well.
PLEASE OBSERVE CORRECT TORQUE WHEN TIGHTENING SCREWS WHILST (RE)-
ASSEMBLE THE IGBTS / ELECTRONICS CARD. FOR A GA50VSD, IT IS RECOMMENDED AT
4N. HOWEVER, BIGGER MACHINES MAY REQUIRE HIGHER TORQUE.
- CHECK: Voltage unbalance leads to higher currents in the motor. Typical 1% unbalance
in supply voltage can lead to 10% extra current in one of the motor phases. 3.5%
unbalance in supply voltage will give 25 deg. C higher in motor temperature.

NOTE: There is a correlation between these faults, and the VSD being operated at
maximum for extended time, ie, if the VSD is running flat out for an extended period of
time, chance of IGBTs damage are high, this may be due to the fact that the IGBTs are
Siemens MasterDrive F28 GA50VSD - CU2 Supply phase The frequency and amplitude of the DC link ripple indicates a single phase supply - Check supply voltage
CUVC failure. - Check the proper connection at the line reactor (L1)
- Check if one of the coils of line reactor L1 is short circuit.
Similar to F8

Siemens MasterDrive F29 GA50VSD - CU2 Measured Valued Sensor Fault occurs in the measured value sensing system - Possibly, CU is faulty
CUVC r949 = 1 Offset adjustment not possible in phase L1 - IGBT or IGD may be defective as it is conductive while signal command does not tell it
r949 = 2 Offset adjustment not possible in phase 3 to do so.
r949 = 3 Offset adjustment not possible in Phases 1 & 3 - Defective phase section
r949 = 65 The analog inputs cannot be automati

Siemens MasterDrive F3 Siemens CCU - Simovert P Undervoltage DC-link voltage (ULC) too low. - Reprogam Mark III and put in ARAVF.
GA90VSD One phase missing Possibly caused by a voltage dip - Check DC link voltage during operation which should be around 1.34 x Supply voltage.
Line power failure. Phase failure - Check fuses.

Siemens MasterDrive F30 Siemens CCU - Simovert P - Operator Panel Fault Dummy plug for the keypad not (properly) engaged, or PMU controller missing - Check and make sure this plug is engage via dummy plug of the hand held controller
6SE13 . . . (PMU)
GA90VSD
Siemens MasterDrive F35 VSD - Siemens CUVC / CU2 External fault 1 - External fault 1 has been triggered =F136- Check cabinet for ventilation
- Check for loose connections
- 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

P575 Src No ExFault1

Siemens MasterDrive F36 AIF VSD - Siemens CUVC External fault 2 - External fault 2 has been triggered The problem probably does not related to the Masterdrive converter, and because it
ZT37VSD - This failure can be caused by a wrong or loose connection from the micromaster receives faulty signals from the external, hence EXTERNAL FAULT #2 comes up. Should
(fan motor control ) to the main convertor (main motor control). GA180VSD and check for problems outside the main converter.
others which have micromaster
- Aux. Drive Fault. ZT37VSD - GA180VSD and related compressors with VSD cooling fans. Check that the connection
between the masterdrive and the micromaster is located at pins 19 - 20 on the
masterdrive, and on pins 3 - 4 on the micromaster.
Also, very important to note that on a very HOT day, the micromaster also may
experience overtemperature problem, and therefore would malfunction, and the
Masterdrive converter will register fault F36 (or F036). There may be a fault message on
the micromaster itself, however, this fault message will only registered as an external
fault via the Masterdrive to the elektronikon.
- Therefore, should try to improve the air temperature within the cabinet to eliminate
this fault.

- ZT37VSD: (this may apply to others which have Micromasters drive as well) ARAVF,
everything else was re-started except the micromaster, hence giving F36. Solution was to
set Parameter P15 --- 0 to disabled, and 1 to enabled, and Parameter P18 --- 0 to
disabled and 1 to enabled. Take note when programming the Micromaster, the
parameters P7 = 1 and P9 = 3 for keypad accessibility.
- GA180VSD W (watercool): F36 indicates that the auxiallary drive has a fault. This
auxiallary drive is the positioner Y40 that regulates the By-Pass Oil Cooler solenoid valve.
Please check the status of this positioner. Pay attention to the connections, the OPEN &
CLOSE limit switches. If nothing is found, probably needs a new positioner. Atlas Part No.
1089 0652 01.
In an EMERGENCY, this by-pass oil cooler solenoid valve may be overwritten to allow the
compressor to continue running. The valve has to be overwritten mechanically,
electrically and on Siemens converter.
Mechanically: By turning to hand knob
Electrically: By disconnecting the power to the positioner, please consult electrical
diagram for confirmation of wire number, typically it should be wire labelled No. 2.
Disconnect the active wire only is sufficient.
Siemens Converter: Before any programming is done, make sure that P053 = 0006 for
general access to parameter changes. Go to P586, and change P586.1 from 601 to 001.
P586.1 = Parameter P586, first index. To access to P586.1, please go to P586, then press
P, and .001 shows up, press P again to access first index and scroll up (or down) to get to
the right value. (This is much simpler, if you are using the Simovis Software.)

- There is a thermal switch at the CUVC card of Siemen's converter, at X101, pin 3-4. This
Siemens MasterDrive F37 Elektronikon Mk III - AC-Line Fault Line Failute detected; in the "Ready" and "On" states, and alarm is output initially Wifh power supply and contactors that switches the power supply.
GA90VSD Simovert P 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

Siemens MasterDrive F40 Siemens CU2, CUVC AS internal fault Incorrect operating status Replace CU card (A10)
GA50VSD
Siemens MasterDrive F41 Siemens CU2, CUVC EEPROM fault A fault has occurred when storing the values in the EEPROM Replace CU card (A10)
GA50VSD
Siemens MasterDrive F42 Siemens CU2, CUVC Computing time problem Calculating time problem Reduce the calculating time by:
GA50VSD
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

Siemens MasterDrive F43 Siemens CU2, CUVC Coupling int. Internal coupling error. One of the two coupling partners does not respond - Check MWH - CU2 connection
GA50VSD - Replace CU card (A10)
Siemens MasterDrive F44 Siemens CU2, CUVC BiCo manager Fault - A fault has occurred during the softwiring of Binectors and Connectors - Reparameterize
GA50VSD - Reset unit
- Replace CU card (A10)

In CUVC, observe r949:

> 1000: Fault during softwiring of connectors
> 2000: Fault during softwiring of binectors

Siemens MasterDrive F45 Siemens CU2, CUVC Opt. Board HW Hardware fault has occurred when assessing an optional board - Replace CU (A10)
GA50VSD - Check connection of the board and optional boards.
Siemens MasterDrive F46 Siemens CU2, CUVC Par task / con. A fault has occur during the transfer of parameters to the gating unit processor - Power unit down and up again
GA50VSD - Replace CU (A10)
Siemens MasterDrive F47 Siemens CU2, CUVC Gating Calc Time / internal Comp. Time The calculating time in the gating unit computer is not sufficient Replace CU (A10)
GA50VSD
Siemens MasterDrive F5 Siemens CCU - Simovert P - Overvoltage Line voltage too high, extreme generator operation, ramp down rate too fast.
6SE13 . . .
GA90VSD
Siemens MasterDrive F6 Siemens CCU - Simovert P - Heat Sink Temp Too high temperature inside converter. Inadequate cooling - Check operation of cooling fan, as well as power supply (380V) over K5 towards these
6SE13 . . . fans
GA90VSD - Check for polluted heat sink
Siemens MasterDrive F7 Siemens CCU - Simovert P - Motor Overtemp Motor overtemp. (PTC thermistor term. X13:24/25), motor overload - Check resistance value of both sets of thermistors which should be < 500 ohm at 20
6SE13 . . . Deg.C
GA90VSD 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
Siemens MasterDrive F8 GA50VSD - CU2, CUVC CU: DC voltage too low CU: DC voltage was too low, ie 76% x line voltage x 1.34 was not reached CU:- Voltage dips might be the reason, Reprogram the MKIII with latest service software
GA90VSD - CCU / Simovert CCU: Pulsed Res Temp and put ARAVF active.
- Check DC link voltage during operation through r006 on the Siemens PMU
- IGBT or IGD1 defective is possibility. Maybe loose or bad connection.
See F008
CCU: - Pulsed Resistor or electronics overheating, ambient temp too high. Cooling fan
may be defective

WEG CFW-11 F006 ZS+VSD, ZE/A VSD Imbalance or Input Phase Loss. Mains voltage Phase missing at the inverter's input power supply.
imbalance too high or phase missing Input voltage imbalance >5 %.
in the input power supply. For the frame size E:
Note: Phase loss at L3/R or L3/S may cause F021 or F185.
- If the motor is unloaded or operating with Phase loss at L3/T will cause F006.
reduced For frame sizes F and G:
load this fault may not occur. Pre-charge circuit fault.
- Fault delay is set at parameter P0357
P0357 = 0 disables the fault.

WEG CFW-11 F021 ZS+VSD, ZE/A VSD DC bus undervoltage condition occurred. The input voltage is too low and the DC bus voltage **** Check input power supply. ***Using DIODE check on the INPUT line 1,2, and 3 and D/C link line.
dropped below the minimum permitted value (monitor the
value at parameter P0004):
Ud < 530 V - Supply voltage 500 / 525 V (P0296 = 5).
Ud < 580 V - Supply voltage 500 / 575 V (P0296 = 6).
Ud < 605 V - Supply voltage 600 V (P0296 = 7).
Ud < 696 V - Supply voltage 660 / 690 V (P0296 = 8).
Phase loss in the input power supply.
Pre-charge circuit failure.
Parameter P0296 was set to a value above of the power
supply rated voltage.

WEG CFW-11 F022 ZS+VSD, ZE/A VSD DC bus overvoltage condition occurred. The input voltage is too high and the DC bus voltage Check motor for Earth fault. Usually, Overvoltage do not happen in most
surpassed the maximum permitted value: countries, unless there is a major speak in power supply.
Ud > 1000 V - For P0296 = 5, 6 or 7.
Ud > 1200 V - For P0296 = 8.
Inertia of the driven-load is too high or deceleration time
is too short.
Wrong settings for parameters P0151, or P0153, or
P0185.

WEG CFW-11 F030 ZS+VSD, ZE/A VSD Power Module U Fault. Desaturation of IGBT Short-circuit between motor phases U and V or U and W. Please perform DIODE checks with respect to the DC Link terminals. Please see
occured in Power Module U. VSD notes for more information on how to perform this task
WEG CFW-11 F034 ZS+VSD, ZE/A VSD Power Module V Fault. Desaturation of IGBT Short-circuit between motor phases V and U or V and W. Please perform DIODE checks with respect to the DC Link terminals. Please see
occured in Power Module V. VSD notes for more information on how to perform this task
WEG CFW-11 F038 ZS+VSD, ZE/A VSD Power Module W Fault. Desaturation of IGBT Short-circuit between motor phases W and U or W and V. Please perform DIODE checks with respect to the DC Link terminals. Please see
occured in Power Module W. VSD notes for more information on how to perform this task
WEG CFW-11 F042 ZS+VSD, ZE/A VSD DB IGBT Fault. Desaturation of Dynamic Short-circuit between the connection cables of the
Braking IGBT occured. dynamic braking resistor.
WEG CFW-11 A046 ZS+VSD, ZE/A VSD High Load on Motor. Load is too high for the Settings of P0156, P0157, and P0158 are too low for *** Check element / bearing and make sure they are not seized. *** check Run
used motor. the used motor. hours of motor / compressors since last had bearing change. Most bearings have
Note: Motor shaft load is excessive. 25,000 - 30,000 run hours. So if compressors maintenance record they within
It may be disabled by setting P0348 = 0 or 2. this run hours window, should consider change of bearings before further works.

WEG CFW-11 A047 ZS+VSD, ZE/A VSD IGBTs Overload Alarm. An IGBTs overload Inverter output current is too high. *** Check element / bearing and make sure they are not seized. *** check Run
alarm occurred. hours of motor / compressors since last had bearing change. Most bearings have
Note: 25,000 - 30,000 run hours. So if compressors maintenance record they within
It may be disabled by setting P0350 = 0 or 2. this run hours window, should consider change of bearings before further works.

WEG CFW-11 F048 ZS+VSD, ZE/A VSD IGBTs Overload Fault. An IGBTs overload fault Inverter output current is too high.
occurred.
WEG CFW-11 A050 ZS+VSD, ZE/A VSD IGBTs High Temperature Surrounding air temperature is too high (>50 °C (122 °F)) *** Check fan for correct operations.
U. A high temperature alarm was detected by and output current is too high.
the NTC Blocked or defective fan.
temperature sensors located on the IGBTs. Very dirty heatsink.
Note:
It may be disabled by setting P0353 = 2 or 3.

WEG CFW-11 F051 ZS+VSD, ZE/A VSD IGBTs Overtemperature U. A high temperature Surrounding air temperature is too high (>50 °C (122 °F)) *** Check fan for correct operations.
fault was detected by the NTC and output current is too high.
temperature sensors located on the IGBTs. Blocked or defective fan.
Very dirty heatsink.
WEG CFW-11 A053 ZS+VSD, ZE/A VSD High Temperature on Surrounding air temperature is too high (>50 °C (122 °F)) *** Check fan for correct operations.
IGBTs V. Alarm of high temperature measured and output current is too high.
at thetemperature sensors (NTC) of the IGBTs. Blocked or defective fan.
Note: Very dirty heatsink.
It can be disabled by setting P0353 = 2 or 3.

WEG CFW-11 F054 ZS+VSD, ZE/A VSD Overtemperature on Surrounding air temperature is too high (>50 °C (122 °F)) *** Check fan for correct operations.
IGBTs V. Fault of overtemperature measured at and output current is too high.
the temperature sensors (NTC) of the IGBTs. Blocked or defective fan.
Very dirty heatsink.

WEG CFW-11 A056 ZS+VSD, ZE/A VSD High Temperature on Surrounding air temperature is too high (>50 °C (122 °F)) *** Check fan for correct operations.
IGBTs W. Alarm of high temperature measured and output current is too high.
at the temperature sensors (NTC) of the Blocked or defective fan.
IGBTs . Very dirty heatsink.
Note:
It can be disabled by setting P0353 = 2 or 3.

WEG CFW-11 F057 ZS+VSD, ZE/A VSD Overtemperature on Surrounding air temperature is too high (>50 °C (122 °F)) *** Check fan for correct operations.
IGBTs W. Fault of overtemperature measured and output current is too high.
at the temperature sensors (NTC) of the IGBTs. Blocked or defective fan.
Very dirty heatsink.

WEG CFW-11 F062 ZS+VSD, ZE/A VSD Thermal Imbalance. Fault of power module The temperature difference between IGBTs modules of ***Check for IBGT failures. May use DIODE checks on output of convertors to
temperature imbalance. the same phase (U, V, W) was above 10 °C. motor.
The temperature difference between IGBTs modules
of different phases (U and V, U and W, V and W) was
above 20 °C.
The temperature difference between rectifier modules of
different phases (R and S, R and T, S and T) was above
10 °C.

WEG CFW-11 F067 ZS+VSD, ZE/A VSD Encoder/Motor Wiring is U, V, W wiring to the motor is inverted.
Inverted. Fault related to the phase relation of Encoder channels A and B are inverted.
the encoder Error in the encoder assembly position.
signals if P0202 = 4 and P0408 = 0, 2, 3 or 4.
Note:
- It is not possible to reset this fault during the
selftuning.
- In this case, power down the inverter, solve
the
problem and then power up.
- When P0408 = 0, this fault can be deactivated
by means of parameter P0358. In this case, it is
not
possible to reset the fault.

WEG CFW-11 F070 ZS+VSD, ZE/A VSD Overcurrent/Short-circuit. Overcurrent or Short-circuit between two motor phases. ***Check for IBGT failures. May use DIODE checks on output of convertors to
short-circuit detected at the output, in the DC Short-circuit between the connection cables of the motor.
bus, or at the braking resistor. dynamic braking resistor.
IGBT modules are shorted.

WEG CFW-11 F071 ZS+VSD, ZE/A VSD Output Overcurrent. The inverter output Excessive load inertia or acceleration time too short.
current was too high for too long. Settings of P0135 or P0169, P0170, P0171, and P0172
are too high.

WEG CFW-11 F072 ZS+VSD, ZE/A VSD Motor Overload. The motor overload Settings of P0156, P0157, and P0158 are too low for ***check for seized elements, bearings, check and confirm run hours since last
protection operated. the used motor. (if any) bearing changes. Typically, the motor bearings has 25,000 - 30,000
Note: Motor shaft load is excessive. running hrs.
It may be disabled by setting P0348 = 0 or 3.

WEG CFW-11 F074 ZS+VSD, ZE/A VSD Ground Fault. A ground fault occured either in Shorted wiring in one or more of the output phases *** Check for ground faults of motor. *** Sometimes motor ground faults
the cable between Motor cable capacitance is too large, resulting in current present themselves as DC Link overvoltage
the inverter and the motor or in the motor peaks at the output
itself.
Note:
It may be disabled by setting P0343 = 0.

WEG CFW-11 F076 ZS+VSD, ZE/A VSD Motor Current Loose connection or broken wiring between the motor *** Check motor connections
Imbalance. Fault of motor current unbalance. and inverter connection.
Note: Vector control with wrong orientation.
It may be disabled by setting P0342 = 0. Vector control with encoder, encoder wiring or encoder
motor connection inverted.

WEG CFW-11 F077 ZS+VSD, ZE/A VSD DB Resistor Overload. The dynamic braking Excessive load inertia or desacceleration time too short.
resistor overload protection Motor shaft load is excessive.
operated. Wrong setttings for parameters P0154 and P0155.
WEG CFW-11 F078 ZS+VSD, ZE/A VSD Motor Excessive load at the motor shaft. *** check thermistor. *** check cooling fan, and room exhausts
Overtemperature. Fault related to the PTC Excessive duty cycle (too many starts / stops per minute).
temperature sensor installed Surrounding air temperature too high.
in the motor. Loose connection or short-circuit (resistance < 100 Ω) in
Note: the wiring connected to the motor termistor.
- It may be disabled by setting P0351 = 0 or 3. Motor termistor is not installed.
- It is required to set the analog input / output Blocked motor shaft.
to the
PTC function.

WEG CFW-11 F079 ZS+VSD, ZE/A VSD Encoder Signal Fault. Lack of encoder signals. Broken wiring between motor encoder and option kit for
By Hw - fault can be disable with switch of encoder interface.
ENC1 Defective encoder.
and ENC2 board.
By Sw - fault can be disable at parameter
P0358.

WEG CFW-11 F080 ZS+VSD, ZE/A VSD CPU Watchdog. Microcontroller watchdog Electrical noise. Check for outside interference, eg, mobile phones, repeaters, etc
fault.
WEG CFW-11 F082 ZS+VSD, ZE/A VSD Copy Function Fault. Fault while copying An attempt to copy the keypad parameters to an inverter
parameters. with a different firmware version.
WEG CFW-11 F084 ZS+VSD, ZE/A VSD Auto-diagnosis Fault. Defect in the inverter internal circuitry.
WEG CFW-11 A088 ZS+VSD, ZE/A VSD Communication Lost. Indicates a problem Loose keypad cable connection.
between the keypad and control Electrical noise in the installation.
board communication.

WEG CFW-11 A090 ZS+VSD, ZE/A VSD External Alarm. External alarm via digital input. Wiring was not connected to the digital input (DI1 to
Note: DI8) set to "No external alarm".
It is required to set a digital input to "No
external
alarm".

WEG CFW-11 F091 ZS+VSD, ZE/A VSD External Fault. External fault via digital input. Wiring was not connected to the digital input (DI1 to
Note: DI8) set to "No external fault".
It is required to set a digital input to "No
external
fault".

WEG CFW-11 F099 ZS+VSD, ZE/A VSD Invalid Current Offset. Current measurement Defect in the inverter internal circuitry.
circuit is measuring a wrong
value for null current.

WEG CFW-11 A110 ZS+VSD, ZE/A VSD High Motor Excessive load at the motor shaft.
Temperature. Alarm related to the PTC Excessive duty cycle (too many starts / stops per minute).
temperature sensor Surrounding air temperature too high.
installed in the motor. Loose connection or short-circuit (resistance < 100 Ω) in
Note: the wiring connected to the motor termistor.
- It may be disabled by setting P0351 = 0 or 2. Motor termistor is not installed.
- It is required to set the analog input / output Blocked motor shaft.
to the
PTC function.

WEG CFW-11 A128 ZS+VSD, ZE/A VSD Timeout for Serial Check the wiring and grounding installation.
Communication. Indicates that the inverter Make sure the inverter has sent a new message within
stopped receiving valid the time interval set at P0314.
messages within a certain time interval.
Note:
It may be disabled by setting P0314 = 0.0 s.

WEG CFW-11 A129 ZS+VSD, ZE/A VSD Anybus is Offline. Alarm that indicates PLC entered into the idle state.
interruption of the Anybus-CC Programming error. Master and slave set with a different
communication. number of I/O words.
Communication with master has been lost (broken
cable, unplugged connector, etc.).

WEG CFW-11 A130 ZS+VSD, ZE/A VSD Anybus Access Error. Alarm that indicates an Defective, unrecognized, or improperly installed Anybus-
access error to the CC module.
Anybus-CC communication module. Conflict with a WEG option board.

WEG CFW-11 A133 ZS+VSD, ZE/A VSD CAN Not Powered. Alarm indicating that the Broken or loose cable.
power supply was not Power supply is off.
connected to the CAN controller.
WEG CFW-11 A134 ZS+VSD, ZE/A VSD Bus Off. Inverter CAN interface has entered Incorrect communication baud-rate.
into the bus-off Two nodes configured with the same address in the network.
state. Wrong cable connection (inverted signals).

WEG CFW-11 A135 ZS+VSD, ZE/A VSD CANopen Communication problems.

Communication Error. Alarm that indicates a Wrong master configuration/settings.
communication error. Incorrect configuration of the communication objects.

WEG CFW-11 A136 ZS+VSD, ZE/A VSD Idle Master. Network master has entered into PLC in IDLE mode.
the idle state. Bit of the PLC command register set to zero (0).
WEG CFW-11 A137 ZS+VSD, ZE/A VSD DNet Connection Timeout. I/O connection One or more allocated I/O connections have entered
timeout - DeviceNet communication into the timeout state.
alarm.

WEG CFW-11 A138 ZS+VSD, ZE/A VSD Profibus DP Interface in Verify the network master status, making sure it is in
Clear Mode. It indicates that the inverter execution mode (Run).
received a command Refer to the Profibus DP communication manual for
from the Profibus DP network master to enter more information.
the clear mode.

WEG CFW-11 A139 ZS+VSD, ZE/A VSD Offline Profibus DP Verify whether the network master is correctly configured
Interface. It indicates an interruption in the and operating normally.
communication Verify the network installation in a general manner -
between the Profibus DP network master and cable routing, grounding.
the Refer to the Profibus DP communication manual for
inverter. more information.

WEG CFW-11 A140 ZS+VSD, ZE/A VSD Profibus DP Module Verify whether the Profibus DP module is correctly fit into
Access Error. It indicates an error in the access the slot 3.
to the Profibus DP Refer to the Profibus DP communication manual for
communication module data. more information.

WEG CFW-11 F150 ZS+VSD, ZE/A VSD Motor Overspeed. Overspeed fault. Wrong settings of P0161 and/or P0162.
It is activated when the real speed exceeds the Problem with the hoist-type load.
value
of P0134 x (100 % + P0132) for more than 20
ms.

WEG CFW-11 F151 ZS+VSD, ZE/A VSD FLASH Memory Module Defective FLASH memory module.
Fault. FLASH Memory Module fault (MMF-03). Check the connection of the FLASH memory module.

WEG CFW-11 A152 ZS+VSD, ZE/A VSD Internal Air High Surrounding air temperature too high (>50 °C (122 °F)) *** Check cooling fan, exhausts, and inlet filters (if any) to cabinet
Temperature. Alarm indicating that the and excessive output current.
internal air temperature is Defective internal fan.
too high. High temperature (> 45 ºC (113 °F)) inside the cabinet.
Note:
It may be disabled by setting P0353 = 1 or 3.

WEG CFW-11 F153 ZS+VSD, ZE/A VSD Internal Air Surrounding air temperature too high (>50 °C (122 °F)) *** Check cooling fan, exhausts, and inlet filters (if any) to cabinet
Overtemperature. Internal air and excessive output current.
overtemperature fault. Defective internal fan.
High temperature (> 45 ºC (113 °F)) inside the cabinet.

WEG CFW-11 A156 ZS+VSD, ZE/A VSD Undertemperature. Only 1 sensor indicates Surrounding air temperature ≤ -30 °C (-22 °F).
temperature below -30 ºC
(-22 °F).

WEG CFW-11 F156 ZS+VSD, ZE/A VSD Undertemperature. Undertemperature fault Surrounding air temperature ≤ -30 °C (-22 °F) (
(below -30 °C (-22 °F)(13)) in
the IGBTs or rectifier measured by the
temperature
sensors.

WEG CFW-11 F160 ZS+VSD, ZE/A VSD Safety Stop Relays. Safety Stop relay fault. It was only applied +24 Vdc to one STO input (STO1 or
STO2).
One of the relays is defective.

WEG CFW-11 F161 ZS+VSD, ZE/A VSD Timeout PLC11CFW-11. Refer to the PLC11-01 Refer to the PLC11-01 module programming manual. Refer to the PLC11-01 module programming manual.
module programming manual.
WEG CFW-11 A162 ZS+VSD, ZE/A VSD Incompatible PLC Refer to the PLC11-01 module programming manual. Refer to the PLC11-01 module programming manual.
Firmware. Refer to the PLC11-01 module
programming manual.

WEG CFW-11 A163 ZS+VSD, ZE/A VSD Break Detect AI1. It indicates that the AI1 Broken AI1 cable.
current (4-20 mA or 20-4 mA) Bad contact at the signal connection to the terminal
reference is out of the 4 to 20 mA range. strip.

WEG CFW-11 A164 ZS+VSD, ZE/A VSD Break Detect AI2. It indicates that the AI2 Broken AI2 cable.
current (4-20 mA or 20-4 mA) Bad contact at the signal connection to the terminal
reference is out of the 4 to 20 mA range. strip.

WEG CFW-11 A165 ZS+VSD, ZE/A VSD Break Detect AI3. It indicates that the AI3 Broken AI3 cable.
current (4-20 mA or 20-4 mA) Bad contact at the signal connection to the terminal
reference is out of the 4 to 20 mA range. strip.
WEG CFW-11 A166 ZS+VSD, ZE/A VSD Break Detect AI4. It indicates that the AI4 Broken AI4 cable.
current (4-20 mA or 20-4 mA) Bad contact at the signal connection to the terminal
reference is out of the 4 to 20 mA range. strip.

WEG CFW-11 F174 ZS+VSD, ZE/A VSD Left Fan Speed Fault. Heatsink left fan speed Dirt on the blades and in the bearings of the fan.
fault. Defective fan.
Defective fan power supply connection.

WEG CFW-11 F175 ZS+VSD, ZE/A VSD Center Fan Speed Fault. Heatsink center fan Dirty on the blades and in the bearings of the fan.
speed fault. Defective fan.
Defective fan power supply connection.

WEG CFW-11 F176 ZS+VSD, ZE/A VSD Right Fan Speed Fault. Heatsink right fan speed Dirt on the blades and in the bearings of the fan.
fault. Defective fan.
Defective fan power supply connection.

WEG CFW-11 A177 ZS+VSD, ZE/A VSD Fan Replacement. Fan replacement alarm Maximum number of operating hours for the heatsink
(P0045 > 50000 hours). fan has been reached.
Note:
This function may be disabled by setting P0354
= 0.

WEG CFW-11 A178 ZS+VSD, ZE/A VSD Fan Speed Alarm. Alarm referring to the fan Dirt on the blades and rolling bearings of the fan.
speed of the heatsink. Defective fan.
Defective connection of the fan power supply.

WEG CFW-11 F179 ZS+VSD, ZE/A VSD Heatsink Fan Speed Fault. This fault indicates a Dirt on the blades and in the bearings of the fan.
problem with the heatsink fan. Defective fan.
Note: Defective fan power supply connection.
This function may be disabled by setting P0354
= 0.

WEG CFW-11 A181 ZS+VSD, ZE/A VSD Invalid Clock Value. Invalid clock value alarm. It is necessary to set date and time at parameters P0194
to P0199.
Keypad battery is discharged, defective, or not installed.

WEG CFW-11 F182 ZS+VSD, ZE/A VSD Pulse Feedback Fault. Indicates a fault on the No motor connected or the motor connected to the
output pulses feedback. .inverter output is too small.
Possible defect on the internal circuits of the inverter
Possible solutions:
Reset inverter and try again.
Set P0356 = 0 and try again.

WEG CFW-11 F183 ZS+VSD, ZE/A VSD IGBTs Overload + Surrounding air temperature too high. ***Check for IBGT failures. May use DIODE checks on output of convertors to
Temperature. Overtemperature related to the Operation with frequencies < 10 Hz under overload. motor.
IGBTs overload
protection.

WEG CFW-11 F185 ZS+VSD, ZE/A VSD Pre-charge Contactor Pre-charge contactor defect.
Fault. It indicates fault at the pre-charge Inverter CFW11 frame size E powered by DC Link:
Contactor. P0355 should be programd to 0.

WEG CFW-11 F186 ZS+VSD, ZE/A VSD Sensor 1 Temperature Motor high temperature. *** check actual temp of motor, and check thermistor for correct operations.
Fault. It indicates a temperature fault at the
sensor 1.

WEG CFW-11 F187 ZS+VSD, ZE/A VSD Sensor 2 Temperature Motor high temperature
Fault. It indicates a temperature fault at the
sensor 2.

WEG CFW-11 F188 ZS+VSD, ZE/A VSD Sensor 3 Temperature. It indicates a Motor high temperature.
temperature fault at the sensor 3.
WEG CFW-11 F189 ZS+VSD, ZE/A VSD Sensor 4 Temperature. It indicates a Motor high temperature.
temperature fault at the sensor 4.
WEG CFW-11 F190 ZS+VSD, ZE/A VSD Sensor 5 Temperature Motor high temperature.
Fault. It indicates a temperature fault at the
sensor 5.

WEG CFW-11 A191 ZS+VSD, ZE/A VSD Sensor 1 Temperature Motor high temperature.
Alarm. It indicates a temperature alarm at the A problem in the wiring connecting the sensor to the IOE
sensor 1. 01 (02 or 03).

WEG CFW-11 A192 ZS+VSD, ZE/A VSD Sensor 2Temperature Motor high temperature.
Alarm. It indicates a temperature alarm at the A problem in the wiring connecting the sensor to the IOE
sensor 2. 01 (02 or 03).

WEG CFW-11 A193 ZS+VSD, ZE/A VSD Sensor 3 Temperature Motor high temperature
Alarm. It indicates a temperature alarm at the A problem in the wiring connecting the sensor to the IOE
sensor 3. 01 (02 or 03).

WEG CFW-11 A194 ZS+VSD, ZE/A VSD Sensor 4 Temperature Motor high temperature.
Alarm. It indicates a temperature alarm at the A problem in the wiring connecting the sensor to the IOE
sensor 4. 01 (02 or 03).

WEG CFW-11 A195 ZS+VSD, ZE/A VSD Sensor 5 Temperature Motor high temperature.
Alarm. It indicates a temperature alarm at the A problem in the wiring connecting the sensor to the IOE
sensor 5. 01 (02 or 03).

WEG CFW-11 A196 ZS+VSD, ZE/A VSD Sensor 1 Cable Alarm. Sensor 1 cable alarm. Shorted temperature sensor.
WEG CFW-11 A197 ZS+VSD, ZE/A VSD Sensor 2 Cable Alarm. Shorted temperature sensor.
WEG CFW-11 A198 ZS+VSD, ZE/A VSD Sensor 3 Cable Alarm. Shorted temperature sensor.
WEG CFW-11 A199 ZS+VSD, ZE/A VSD Sensor 4 Cable Alarm. Shorted temperature sensor.
WEG CFW-11 A200 ZS+VSD, ZE/A VSD Sensor 5 Cable Alarm. Shorted temperature sensor.
WEG CFW-11 F228 ZS+VSD, ZE/A VSD Serial Communication Refer to the RS-232 / RS-485 Serial communication manual. Refer to the RS-232 / RS-485 Serial communication manual.
Timeout
WEG CFW-11 F229 ZS+VSD, ZE/A VSD Anybus Offline Refer to the Anybus-CC communication manual. Refer to the Anybus-CC communication manual.
WEG CFW-11 F230 ZS+VSD, ZE/A VSD Anybus Access Error Refer to the Anybus-CC communication manual. Refer to the Anybus-CC communication manual.
WEG CFW-11 F233 ZS+VSD, ZE/A VSD CAN Bus Power Failure Refer to the CANopen communication manual and/or the DeviceNet Refer to the CANopen communication manual and/or the DeviceNet
communication manual. communication manual.
WEG CFW-11 F234 ZS+VSD, ZE/A VSD Bus Off Refer to the CANopen communication manual and/or the DeviceNet Refer to the CANopen communication manual and/or the DeviceNet
communication manual. communication manual.
WEG CFW-11 F235 ZS+VSD, ZE/A VSD CANopen Refer to the CANopen communication manual Refer to the CANopen communication manual
Communication Error
WEG CFW-11 F236 ZS+VSD, ZE/A VSD Master Idle Refer to the CANopen communication manual. Refer to the CANopen communication manual.
WEG CFW-11 F237 ZS+VSD, ZE/A VSD DeviceNet Connect Refer to the CANopen communication manual. Refer to the CANopen communication manual.
Timeout
WEG CFW-11 F238 ZS+VSD, ZE/A VSD Profibus DP Interface in Refer to the Profibus DP communication manual. Refer to the Profibus DP communication manual.
Clear Mode
WEG CFW-11 F239 ZS+VSD, ZE/A VSD Offline Profibus DP Refer to the Profibus DP communication manual. Refer to the Profibus DP communication manual.
Interface
WEG CFW-11 F240 ZS+VSD, ZE/A VSD Profibus DP Module Refer to the Profibus DP communication manual. Refer to the Profibus DP communication manual.
Access Error
WEG CFW-11 F416 ZS+VSD, ZE/A VSD IGBT Curr. Imb. Fault. Fault of current IGBTs of the same phase presented a current imbalance
imbalance on the IGBTs. above 15 %.
WEG CFW-11 F417 ZS+VSD, ZE/A VSD Thermal Imbalance. The temperature The temperature difference between IGBT modules ***Check for IBGT failures. May use DIODE checks on output of convertors to
difference between IGBT modules of of different phases (U and V, U and W, V and W) was motor.
the same phase (U, V, W) was above 10 °C (50 ° above 10 °C (50 ° F). The temperature difference
F). between rectifier modules of different phases (R and S, R
and T, S and T) was above 10 °C (50 °F).

WEG CFW-11 F418 ZS+VSD, ZE/A VSD Air Control Overtemp. Fault of Temperature of the internal air of the control board is
overtemperature of the internal air on the above 85 °C (185 ° F)
control board.

WEG CFW-11 A419 ZS+VSD, ZE/A VSD Control Air Temperature When the temperature of the internal air of the control
High Alarm. Alarm of overtemperature of the board is above 70 °C (158 °F) .
internal air on the
control board.

WEG CFW-11 A700 ZS+VSD, ZE/A VSD Detached HMI. Alarm or fault related to the RTC function block has been activated in the applicative
HMI disconnection and the HMI is disconnected from the inverter.
WEG CFW-11 F701 ZS+VSD, ZE/A VSD Detached HMI. Alarm or fault related to the RTC function block has been activated in the applicative
HMI disconnection and the HMI is disconnected from the inverter.
WEG CFW-11 A702 ZS+VSD, ZE/A VSD Inverter Disabled. Alarm indicating that the The SoftPLC Run/Stop command is equal to Run or a
General Enable command movement block has been enable while the inverter is
is not active. general disabled.

WEG CFW-11 A704 ZS+VSD, ZE/A VSD Two Movements Enabled It occurs when two or more movement blocks are
enabled simultaneously.
WEG CFW-11 A706 ZS+VSD, ZE/A VSD Speed Reference Not It occurs when a movement block has been enabled and
Programmed for SoftPLC. Speed reference not the speed reference has not been configured for SoftPLC
programmed for SoftPLC (check P0221 and P0222).

WEG CFW-11 FAQ - Motor does not start ZS+VSD, ZE/A VSD AA: Incorrect wiring AA: Incorrect wiring 1. Check all power and control connections. For instance,
the digital inputs set to
BB: Analog reference (if used) Start/Stop, General Enable, or no external error must be connected to the 24
Vdc
CC: Incorrect settings 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
DD: Fault 2. Check the status of the control potentiometer (if used)
CC: Incorrect settings 1. Check if the parameter values are correct for the
EE: Stalled motor application
DD: Fault 1. Check whether the inverter is disabled due to a fault condition
2. Make sure that the terminals XC1:13 and XC1:11 are not shorted (short-circuit
at
the 24 Vdc power supply)
EE: Stalled motor 1. Decrease the motor overload
2. Increase P0136, P0137 (V/f), or P0169/P0170 (vector control)
WEG CFW-11 FAQ - Motor speed oscillateZS+VSD, ZE/A VSD AA: Loose connections AA: Loose connections 1. Stop the inverter, turn off the power supply, check and
BB: Defective speed reference tighten all the power
connections
CC: Oscillation of the external 2. Check all the internal connections of the inverter
analog reference BB: Defective speed reference
DD: (vector control) potentiometer
1. Replace the potentiometer
CC: Oscillation of the external
analog reference
1. Identify the cause of the oscillation. If it is caused by electrical noise, use
shielded
cables or separate them from the power and control wiring
Incorrect settings
DD: (vector control)
1. Check parameters P0410, P0412, P0161, P0162, P0175, and P0176
2. Refer to the programming manual

WEG CFW-11 FAQ - Too high or too low ZS+VSD, ZE/A VSD AA: Incorrect settings AA: Incorrect settings
motor (reference limits) (reference limits)
speed BB: Control signal from the 1. Check whether the values of P0133 (minimum speed) and P0134 (maximum
analog reference (if used) speed)
CC: Motor nameplate are properly set for the used motor and application
BB: Control signal from the
analog reference (if used)
1. Check the level of the reference control signal
2. Check the settings (gain and offset) of parameters P0232 to P0249
CC: Motor nameplate 1. Check whether the used motor matches the application

WEG CFW-11 FAQ - Motor does not ZS+VSD, ZE/A VSD Settings 1. Decrease P0180
reach the 2. Check P0410
rated speed, or motor
speed starts oscillating
around the rated speed
(Vector Control)

WEG CFW-11 FAQ - Display is off ZS+VSD, ZE/A VSD AA: Keypad connections 1. Check the inverter keypad connection AA: Keypad connections 1. Check the inverter keypad connection
BB: Power supply voltage 1. Rated values must be within the limits BB: Power supply voltage 1. Rated values must be within the limits specified
specified below: below:
- Minimum: 425 V - Minimum: 425 V
- Maximum: 759 V - Maximum: 759 V
CC: Mains supply fuses open 1. Replace the fuses CC: Mains supply fuses open 1. Replace the fuses

WEG CFW-11 FAQ - Motor does not ZS+VSD, ZE/A VSD Settings 1. Decrease P0180
operate in
the field weakening region
(Vector Control)

WEG CFW-11 FAQ - Low motor speed ZS+VSD, ZE/A VSD Encoder signals are inverted 1. Check signals A - A, B - B , refer to the incremental encoder interface manual.
and or power connections are If
P0009 = P0169 or inverted signals are properly wired, invert two of the output phases. For instance U and V
P0170 (motor operating
with torque limitation), for
P0202 = 4 - vector with
encoder