9.

10 - FAULT/ERROR HANDLING/DIAGNOSTICS

9.10.1 Overview of faults and alarms

9.10.2 Displaying and handling faults and warnings
Display and operator control via the display and operator unit
FAULT LED on the front panel
9.10.3 Lists of faults and alarms
Fault without a number being displayed
Fault with fault/warning number

140
9.10.1 - Overview of faults and alarms

141
Acknowledgment
For each fault and warning, under ”Acknowledgment” in the list of faults
and warnings, it is specified how the fault/warning is acknowledged
after the cause has been removed (refer to Section 7.3).

Acknowledge faults with POWER ON

Faults, which are acknowledged using POWER ON, can be alternati-vely

acknowledged as follows:
1. POWER ON
––> power–off/power–on “SIMODRIVE 611 universal”
2. Press the POWER ON–RESET button on the front panel of the con-trol
board
3. POWER ON–RESET with the “SimoCom U” tool
The processor runs–up again, all of the faults are acknowledged, and
the fault buffer is re–initialized.

Acknowledge faults with the RESET FAULT MEMORY

Faults, which are acknowledged with RESET FAULT MEMORY, can be

alternatively acknowledged as follows:

Important
Prerequisites when acknowledging:

- disable the controller enable via terminal 65.x

or
- set the PROFIBUS control signal STW1.0 to “0”

1. Execute POWER ON acknowledgment

In addition to the POWER ON faults, all of the faults, which can be
acknowledged with RESET FAULT MEMORY, are also acknowled-ged.
2. Set the input terminal with the ”reset fault memory” function to ”1”
3. Press button P on the display and operator control unit
4. Using PROFIBUS–DP: Set STW1.7 (reset fault memory) to “1”
5. Set terminal R on the NE module to “1”
When this terminal is energized, ”reset fault memory” is effective for
all of the control boards of the complete drive group.
6. For the “SimoCom U” tool in the dialog box “Alarm report” by pres-sing
the “Reset fault memory” button

142
Stop responses

For each fault and warning, under ”stop” in the list of faults and warnings, the stop response and the effect it
has is explained (refer to Section 7.3).

143
9.10.2 - Displaying and handling faults and warnings

Display and operator control via the display and operator unit

Displaying faults and warnings

When one or several faults or warnings occur, the segment display is

automatically changed over into the alarm mode. The faults and war-nings
are output flashing on the display unit. They can be displayed as
follows:

144
Operator control, if a fault is available

When a fault occurs, it can be handled using the MINUS and P keys as shown in the following diagram.

Handling, several faults

When faults occur, they can be handled as shown in the following dia-
gram using the PLUS, MINUS and P keys.

145
Operator action, if one warning is present

When warnings occur, they can be handled using the MINUS key as shown in the following diagram.

146
FAULT LED on the front panel

LED display on the control board

There is a button with integrated LED on the front panel of the “SIMO-DRIVE 611 universal” control board.

What significance does the FAULT LED have?

A FAULT LED which is bright on the front panel of the control board
can be interpreted as follows:

147
9.10.3 - Lists of faults and alarms

Fault without a number being displayed

Fault After power–on, the operating display is inactive

Cause – At least 2 phases are missing (NE module)
– At least 2 input fuses have ruptured (NE module)
– Defective electronics power supply in the NE module
– Equipment bus connection (ribbon cable) from
the NE module to the “SIMODRIVE 611 universal”
control board is either not inserted or defective
– Defective control board

Fault The motor is at n set _ 0 after the controller has been enabled
Cause – P1401:8 is set to zero
– Power–on inhibit for PROFIBUS operation is present
Disable the power–on inhibit with ”high – low – high”
signal change at terminal 65.x or control bit STW1.0 (ON / OFF 1)
or
set bit 12 of parameter 1012 to zero

Fault After the controller has been enabled, the motor briefly moves
Cause – Defective power module

Fault After the controller is enabled, the motor rotates max. 50 RPM at n set > 50
RPM or the motor oscillates at n set < 50 RPM
Cause – Motor phase sequence incorrect (interchange 2 phase connections)
– The entered encoder pulse number was too high

Fault After the controller is enabled, the motor accelerates to a high speed
Cause – Encoder pulse number too small
– Open–loop torque controlled mode selection?

Fault “– – – – – –” is output on the display unit

Cause – There is no drive firmware in this memory module.
– Remedy, refer to fault 001

148
Fault with fault/warning number

Reader’s note
- In some case, space retainers (e.g. \%u) are specified for the text
associated with the individual faults and warnings.
In online operation with SimoCom U instead of a space retainer, an
appropriate value is displayed.
- The faults and warnings listed in the following are valid for all soft-ware
releases of “SIMODRIVE 611 universal”.
The complete list is updated corresponding to the edition of this
documentation (refer to the edition in the header line) and corres-ponds
to the software release of “SIMODRIVE 611 universal” docu-mented
here.
The individual faults/alarms are not identified as a function of the
software release.

001
The drive does not have firmware
Cause No drive firmware on the memory module.
Remedy – Load the drive firmware via SimoCom U
– Insert the memory module with firmware
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

002
Computation time overflow. Suppl. info: \%X
Cause The computation time of the drive processor is no longer sufficient for
the selected functions in the specified cycle times.
Supplementary information: only for siemens–internal error diagnostics
Remedy Disable functions which take up a lot of computation time, e.g.:
– Variable signaling function (P1620)
– Trace function
– Start–up with FFT or analyzing the step response
– speed feedforward control (P0203)
– Min/Max memory (P1650.0)
– DAC output (max. 1 channel)
Increase cycle times:
– Current controller cycle (P1000)
– Speed controller cycle (P1001)
– Position controller cycle (P1009)
– Interpolation cycle (P1010)
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

149
 003
NMI due to watchdog. Suppl. info: \%X
Cause The watchdog timer on the control module has expired. The cause is a
hardware fault in the time basis on the control module.
Supplementary information: only for siemens–internal error diagnostics
Remedy Replace closed–loop control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

004
Stack overflow. Suppl. info: \%X
Cause The limits of the internal processor hardware stack or the software
stack in the data memory have been violated. The cause is probably a
hardware fault on the control module.
Supplementary information: only for siemens–internal error diagnostics
Remedy – power down / power up drive module
– Replace control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

005
Illegal Opcode, Trace, SWI, NMI (DSP). Suppl. info: \%X
Cause The processor has detected an illegal command in the program me-mory.
Supplementary information: only for siemens–internal error diagnostics
Remedy Replace closed–loop control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

006
Checksum test error. Suppl. info: \%X
Cause During the continuous check of the checksum in the program / data
memory, a difference was identified between the reference and actual
checksum. The cause is probably a hardware fault on the control mo-dule.
Supplementary information: only for siemens–internal error diagnostics
Remedy Replace closed–loop control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

007
Error when initializing. Supplementary info: \%X
Cause An error occurred when loading the firmware from the memory module.
Cause: Data transfer error, FEPROM memory cell defective
Supplementary information: only for siemens–internal error diagnostics
Remedy Execute RESET or POWER ON.
If there is still a problem after several attempts, then the memory mo-dule
must be replaced. If this is also not successful, then the control
module is defective and must be replaced.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

150
 020
NMI due to cycle failure
Cause Basic cycle has failed.
Possible causes: EMC faults, hardware fault, control module
Remedy – check the plug–in connections
– implement noise suppression measures (screening, check ground
connections)
– Replace control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

025
SSI interrupt
Cause An illegal processor interrupt has occurred. An EMC fault or a hardware
fault on the control module could be the reason.
Remedy – check the plug–in connections
– Replace control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

026
SCI interrupt
Cause An illegal processor interrupt has occurred. An EMC fault or a hardware
fault on the control module could be the reason.
Remedy – check the plug–in connections
– Replace control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

027
HOST interrupt
Cause An illegal processor interrupt has occurred. An EMC fault or a hardware
fault on the control module could be the reason.
Remedy – check the plug–in connections
– Replace control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

028
Actual current sensing during power–up
Cause When the current actual value sensing runs up, or in cyclic operation at
pulse inhibit, a 0 current is expected. The drive system then identifies
that no currents are flowing (excessive deviation to the theoretical center
frequency). It is possible that the hardware for the current actual
value sensing is defective.
Remedy – check whether the control module is correctly inserted
– check the plug–in connections
– Replace control module
– replace power section
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

151
 029
Incorrect measuring circuit evaluation. Suppl. info: \%X
Cause The motor measuring system has a motor encoder with voltage output
which requires a measured circuit evaluation with voltage input, or a
resolver with appropriate evaluation. Another measuring circuit evalua-tion
was identified.
Supplementary information: only for siemens–internal error diagnostics
Remedy – check the plug–in connections
– implement noise suppression measures (screening, check ground
connections, ...)
– control module and encoder must be the same type (sin/cos or resol-ver)
– Replace control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

030
S7 communication error. Supplementary info: \%X
Cause A fatal communication error was identified, or the drive software is no
longer consistent. The cause is erroneous communications or a hard-ware
fault on the control module.
Supplementary information: only for siemens–internal error diagnostics
Remedy – implement noise suppression measures (screening, check ground connections, ...)
– Replace control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

031
Internal data error. Suppl. info: \%X
Cause Error in the internal data, e.g. errors in the element / block lists (incor-rect
formats, ...). The drive software is no longer consistant. The cause
is propably a hardware fault on the control module.
Supplementary information: only for siemens–internal error diagnostics
Remedy – reload drive software
– Replace control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

032
Incorrect number of current setpoint filters
Cause An illegal number of current setpoint filters (> 4) has been entered.
Remedy Correct number of current setpoint filters (P1200).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

033
Incorrect number of speed setpoint filters
Cause An illegal number of speed setpoint filters (> 2) has been entered.
Remedy Correct number of speed setpoint filters (P1500)
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

152
 034
Axis count function has failed
Cause The function for determining the number of axes that physically exist on
the power section has calculated an illegal value.
Remedy Check that the control module is correctly inserted in the power section
or whether the power section is defective.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

035
Error when saving the user data. Supplementary info: \%X
Cause An error occurred when saving the user data in the FEPROM on the
memory module.
Cause: Data transfer error, FEPROM memory cell defective
Note: The user data which was last saved, is still available as long as a
new data backup was unsuccessful.
Supplementary information: only for siemens–internal error diagnostics
Remedy Initiate another data backup.
If data backup is still unsuccessful after several attempts, then the me-mory
module must be replaced. If the user data, valid up to the error, is
to be used in the new memory module, then it must be read out via Si-moCom
U before the memory module is replaced, and loaded again
after it has been replaced.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

036
Error when downloading the firmware. Suppl. info: \%X
Cause An error occurred when loading a new firmware release.
Cause: Data transfer error, FEPROM memory cell defective
Note: As the previously used firmware was erased when downloading,
the drive expects a new firmware download after RESET or POWER ON.
Supplementary information: only for siemens–internal error diagnostics
Remedy Execute RESET or POWER ON.
If a download is still unsuccessful after several attempts, the memory
module must be replaced. If this is unsuccessful the control module is
defective and must be replaced.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

153
 037
Error when initializing the user data. Supplementary info: \%X
Cause An error occurred when loading the user data from the memory mo-dule.
Cause: Data transfer error, FEPROM memory cell defective
Supplementary information: only for siemens–internal error diagnostics
Remedy Execute POWER ON.
If a download is still unsuccessful after several attempts, the memory
module must be replaced. If this is unsuccessful the control module is
defective and must be replaced.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

039
Error during power section identification. Supplementary info: \%X
Cause Supplementary information
0x100000:
More than 1 power section type was identified.
0x200000:
No power section type was identified, although it would have been pos-sible.
0x30xxxx:
The identified power section differs from the entered power section
(P1106). To xxxx: the code of the identified power section is entered here.
0x400000:
Different power section codes (P1106) are entered for this 2–axis mo-dule.
Remedy – check whether the control module is correctly inserted in the power section
– execute RESET or POWER ON
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

040
Expected option module is not available.
Cause The parameterization (P0875) expects an option module which is not
available on this control module.
Remedy Compare the type of the expected option module (P0875) with the type
of the inserted option module (P0872) and check/replace the inserted
option module or cancel the option module with P0875 = 0.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

154
 041
Firmware does not support the option module
Cause The parameterization (P0875) expects an option module which is not
supported by the firmware release of the control module.
Remedy The following is valid for SIMODRIVE 611 universal:
– upgrade the firmware
– use a legal option module
– cancel the option module with P0875 = 0
The following is valid for SIMODRIVE 611 universal E:
– use a legal option module
– cancel the option module with P0875 = 0
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

042
Internal software error. Supplementary info \%u
Cause There is an internal software error.
Supplementary information: only for siemens–internal error diagnostics
Remedy – Execute POWER ON–RESET (press button R)
– Re–load the software into the memory module (execute software up-date)
– Replace the memory module
– Replace control module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

043
Firmware, option module
Cause The option module does not contain the currently required firmware.
Remedy Use a module with suitable firmware or upgrade the firmware
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

044
Option module failed
Cause The option module has failed.
Remedy Replace the option module
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

045
Expected option module is axially unequal
Cause The option module type, expected from the parameterization, is diffe-rent
for the two axes of a two–axis module.
Remedy Set the expected option module type in P0875 the same for both axes,
or cancel for axis B by setting P0875 to 0.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

101
Target position block \%u > plus software limit switch
Cause The target position specified in this block lies outside the range limited
by P0316 (plus software limit switch).
Remedy – Change the target position in the block
– Set the software limit switches differently
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

155
 102
Target position block \%u < minus software limit switch
Cause The target position specified in this block lies outside the range limited
by P0315 (minus software limit switch).
Remedy – Change the target position in the block
– Set the software limit switches differently
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

103
Block number \%u: direct output function not possible
Cause For the SET_O or RESET_O command, an illegal value was entered in
P0086:64 (command parameter).
Remedy Enter value 1, 2 or 3 in P0086:64 (command parameter).
Acknowledge / Stop RESET FAULT MEMORY / STOP V

104
Block \%u: jump destination does not exist
Cause A jump is programmed to a non–existent block number in this traversing block.
Remedy Program the existing block number.
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

105
Illegal mode in the block \%u specified
Cause Illegal information is in P0087:64 (mode). A position of P0087:64 has
an illegal value.
Remedy Check P0087:64 and correct.
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

106
Block \%u: Mode ABS_POS for linear axis not possible
Cause For a linear axes, the positioning mode ABS_POS was programmed
(only for rotary axes).
Remedy Change P0087:64 (mode).
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

107
Block \%u: Mode ABS_NEG for linear axis not possible
Cause For a linear axes, the positioning mode ABS_NEG was programmed
(only for rotary axes).
Remedy Change P0087:64 (mode).
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

156
 108
Block number \%u available twice
Cause There are several traversing blocks with the same block number in the
program memory. The block numbers must be unique over all traver-sing blocks.
Remedy Assign unique block numbers.
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

109
External block change in the block \%u not requested
Cause External block change was not requested for a traversing block with
block step enable CONTINUE EXTERNAL and P0110 (configuration of
external block change) = 0.
Remedy Eliminate the cause for the missing edge at the input terminal resp. at
the PROFIBUS control signal STW1.13.
Acknowledge / Stop RESET FAULT MEMORY / STOP V

110
Selected block number \%u does not exist
Cause A block number was selected which is not available in the program me-mory
or has been suppressed.
Remedy Select the existing block number.
Program the traversing block with the selected block number.
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

111
GOTO in block number \%u illegal
Cause The step command GOTO may not be programmed for this block num-ber.
Remedy Program another command.
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

112
Activate traversing task and start referencing simulta-neously
Cause For the ”activate traversing task” and ”start referencing” input signals, a
positive edge was simultaneously identified.
At power–on or POWER–ON RESET, if both input signals have a ”1”
signal, then for both signals a 0/1 edge (positive edge) is simulta-neously
identified.
Remedy Reset both input signals, and re–start the required function after the
fault has been acknowledged.
Acknowledge / Stop RESET FAULT MEMORY / STOP IV

157
 113
Activate the traversing task and jog simultaneously
Cause For the ”activate traversing task” and ”Jog 1” or ”Jog 2” input signals, a
positive edge was simultaneously identified.
At power–on or POWER–ON RESET, if both input signals have a ”1”
signal, then for both signals a 0/1 edge (positive edge) is simultaneously identified.
Remedy Reset both input signals, and re–start the required function after the
fault has been acknowledged.
Acknowledge / Stop RESET FAULT MEMORY / STOP IV

114
block step enable END in block number \%u expected
Cause The traversing block with the highest block number does not have END
as block step enable.
Remedy – Program this traversing block with block step enable END.
– Program the GOTO command for this traversing block.
– Program additional traversing blocks with higher block number and
program the block step enable END (highest block number) in the last block.
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

115
Traversing range start reached
Cause The axis has moved to the traversing range limit in a block with the
command ENDLOS_NEG (–200 000 000 MSR).
Remedy – Acknowledge fault
– Move away in the positive direction (e.g. jog)
Acknowledge / Stop RESET FAULT MEMORY / STOP V

116
Traversing range end reached
Cause The axis has moved to the traversing range limit in a block with the
command ENDLOS_POS (200 000 000 MSR).
Remedy – Acknowledge fault
– Move away in the negative direction (e.g. jog)
Acknowledge / Stop RESET FAULT MEMORY / STOP V

117
Target position block \%u < traversing range start
Cause The target position specified in this block lies outside the absolute tra-versing
range (–200 000 000 MSR).
Remedy Change the target position in the block
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

118
Target position block \%u < traversing range end
Cause The target position specified in this block lies outside the absolute tra-versing
range (200 000 000 MSR).
Remedy Change the target position in the block
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

158
 119
PLUS software limit switch actuated
Cause The axis has traveled to the plus software limit switch (P0316) in a
block with the command ENDLOS_POS.
Remedy – Acknowledge fault
– Move away in the negative direction, jog mode
Acknowledge / Stop RESET FAULT MEMORY / STOP V

120
MINUS software limit switch actuated
Cause The axis has traveled to the minus software limit switch (P0315) in a
block with the command ENDLOS_NEG.
Remedy – Acknowledge fault
– Move away in the positive direction, jog mode
Acknowledge / Stop RESET FAULT MEMORY / STOP V

121
Jog 1 and Jog 2 simultaneously active
Cause The ”Jog 1” and ”Jog 2” input signals were simultaneously activated.
Remedy – Reset both input signals
– Acknowledge the fault
– Activate the required input signal
Acknowledge / Stop RESET FAULT MEMORY / STOP II

122
Parameter \%u: value range limits violated
Cause The value range limit of the parameter was violated when the dimen-sion
system was changed over from inches to millimeters.
Remedy Place the parameter value within the value range.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

123
Linear encoder for the selected dimension system ille-gal
Cause For a linear encoder, the dimension system was set to degrees.
Remedy Change the dimension system setting (P0100).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

124
Referencing and jog simultaneously started
Cause For the ”start referencing” and ”Jog 1” and ”Jog 2” input signals, a posi-tive
Edge was simultaneously identified.
Remedy Reset both input signals, and re–start the required function after the
fault has been acknowledged.
Acknowledge / Stop RESET FAULT MEMORY / STOP V

159
 125
Falling edge of the reference cam not identified
Cause When moving away from the reference cams, the traversing range limit
was reached, as the 1/0 edge of the reference cam was not identified.
Remedy Check the ”reference cam” input signal and repeat the reference point approach.
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

126
Block \%u: ABS_POS for rotary axis without modulo conversion not possible
Cause The ABS_POS positioning mode is only permitted for a rotary axis with
activated module conversion (P0241 = 1).
Remedy Use the valid positioning mode for this axis type.
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

127
Block \%u: ABS_NEG for rotary axis without modulo conversion not possible
Cause The ABS_NEG positioning mode is only permitted for a rotary axis with
activated modulo conversion (P0241 = 1).
Remedy Use the valid positioning mode for this axis type.
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

128
Block \%u: Target position outside the modulo range
Cause The programmed target position (P0081:64) is outside the modulo
range set (P0242).
Remedy Program valid target position.
Acknowledge / Stop RESET FAULT MEMORY / STOP VI

129
Maximum velocity for a rotary axis with modulo conversion too high
Cause The programmed maximum velocity (P0102) is too high to correctly
calculate the modulo offset. The maximum velocity may only be so
high, that 90% of the modulo range (P0242) can be traveled through
within one interpolation cycle (P1010).
Remedy Reduce maximum velocity (P0102).
Acknowledge / Stop RESET FAULT MEMORY / STOP V

160
 130
Controller or pulse enable withdrawn in motion
Cause Possible causes are:
– one of the following enable signals was withdrawn when moving: Ter-minal
48, 63, 64, 663, 65.x, PROFIBUS enable signals, PC enable
from SimoCom U
– another fault has occurred, which causes the controller or pulse ena-ble
to be withdrawn
Remedy Set the enable signals and check the cause of the first fault and re-move.
Acknowledge / Stop RESET FAULT MEMORY / STOP II

131
Following error too high
Cause Possible causes are:
– the torque or acceleration capability of the drive is exceeded
– position measuring system fault
– the position control sense is not correct (P0231)
– mechanical system blocked
– excessive traversing velocity or excessive position setpoint differen-ces
Remedy Check the above causes and remove.
Acknowledge / Stop RESET FAULT MEMORY / STOP II

132
Drive located after the minus software limit switch
Cause The axis was moved to the minus software limit switch (P0315), jog mode.
The fault can also occur if the software limit switches are inactive, if the
position actual value falls below the –200 000 000 MSR limit.
Remedy Return the drive into the traversing range using jog button 1 or 2. Then
acknowledge the fault.
Acknowledge / Stop RESET FAULT MEMORY / STOP III

133
Drive located after the plus software limit switch
Cause The axis was moved to the plus software limit switch (P0316), jog mode.
The fault can also occur if the software limit switches are inactive, if the
position actual value exceeds the 200 000 000 MSR limit.
Remedy Return the drive into the traversing range using jog button 1 or 2. Then
acknowledge the fault.
Acknowledge / Stop RESET FAULT MEMORY / STOP III

161
 134
Positioning monitoring has responded
Cause The drive has not yet reached the positioning window (P0321) after the
positioning monitoring time (P0320) has expired.
Possible causes:
– Positioning monitoring time (P0320) parameters too low
– Positioning window (P0321) parameters too low
– Position loop gain (P0200) too low
– Position loop gain (P0200) too high (instability/tendency to oscillate)
– Mechanical block
Remedy Check above parameters and correct.
Acknowledge / Stop RESET FAULT MEMORY / STOP II

135
Standstill monitoring has responded
Cause The drive has left the standstill window (P0326) after the standstill mo-nitoring
time (P0325) has expired.
Possible causes are:
– Standstill monitoring time (P0325) parameters too low
– Standstill window (P0326) parameters too low
– Position loop gain (P0200) too low
– Position loop gain (P0200) too high (instability/tendency to oscillate)
– Mechanical overload
– Check connecting cable motor/converter (phase missing, exchanged)
Remedy Check above parameters and correct.
Acknowledge / Stop RESET FAULT MEMORY / STOP II

136
Conv.factor,feedforward contr.speed,parameter set \%d,cannot be represented
Cause The conversion factor in the position controller between velocity and
speed cannot be displayed.
This factor depends on the following parameters:
– Spindle pitch (P0236), for linear axes
– Gearbox ratio (P0238:8 / P0237:8).
Remedy Check the above mentioned parameters and correct.
Acknowledge / Stop RESET FAULT MEMORY / STOP II

137
Conv.factor,pos.contr.output,parameter set \%d,cannot be represented
Cause The conversion factor in the position controller between the following
error and the speed setpoint cannot be displayed.
This factor depends on the following parameters:
– spindle pitch (P0236) (for linear axes)
– gearbox ratio P0238:8 / P0237:8
– position control loop gain P0200:8
Remedy Check the above mentioned parameters and correct.
Acknowledge / Stop RESET FAULT MEMORY / STOP II

162
 138
Conversion factor between the motor and load too high
Cause The conversion factor between the motor and load is greater than 2 to
the power of 24 or less than 2 to the power of –24.
Remedy Check the following parameters and correct:
P0236, P0237, P0238, P1005, P1024
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

139
Modulo range and ratio do not match
Cause For multi–turn absolute value encoders, the ratio between the encoder
and load must be set so that the full encoder range is an integral multi-ple
of the modulo range.
The following condition must be fulfilled:
P1021 * P0238:8 / P0237:8 * 360 / P0242 must be integer numbers.
Remedy – Check and correctP1021, P0238:8, P0237:8
– adapt the modulo range (P0242)
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

140
Minus hardware limit switch
Cause A 1/0 edge was identified at the ”Minus hardware limit switch” input si-gnal.
Remedy Return the drive into the traversing range using jog button 1 or 2. Then
acknowledge the fault.
Acknowledge / Stop RESET FAULT MEMORY / STOP III

141
Plus hardware limit switch
Cause A 1/0 edge was identified at the ”Plus hardware limit switch” input si-gnal.
Remedy Return the drive into the traversing range using jog button 1 or 2. Then
acknowledge the fault.
Acknowledge / Stop RESET FAULT MEMORY / STOP III

142
Reference point approach with ext. block change via I0.x
Cause While a block with external block change via I0.x is in intermediate
stop, reference point approach was started.
Remedy Before starting the reference point approach, terminate block execution
with external block change.
Acknowledge / Stop RESET FAULT MEMORY / STOP V

163
 160
Reference cam not reached
Cause After starting the reference point approach, the axis moves through the
distance in P0170 (max. distance to the reference cam) without finding
the reference cam.
Remedy – Check the ”reference cam” signal
– Check P0170
– If it is an axis without reference cam, then set P0173 to 1
Acknowledge / Stop RESET FAULT MEMORY / STOP V

161
Reference cams too short
Cause When the axis moves to the reference cam, and does not come to a
standstill at the cam, then this error is signaled, i.e. the reference cam is too short.
Remedy – Set P0163 (reference point approach velocity) to a lower value
– Increase P0104 (maximum deceleration)
– Use larger reference cam
Acknowledge / Stop RESET FAULT MEMORY / STOP V

162
No zero reference pulse available
Cause After the reference cam was left, the axis moved through the distance
in P0171 (max. distance between reference cam/zero pulse) without
finding the zero pulse.
Remedy – Check the encoder with reference to the zero mark
– Set P0171 to a higher value
Acknowledge / Stop RESET FAULT MEMORY / STOP V

501
Measuring circuit error, absolute current
Cause 1. The smoothed absolute current (P1254, current monitoring time con-stant)
is greater than 120 % of the permissible power section current (P1107).
2. For an active rotor position identification, the permissible current threshold was
exceeded.
3. The P gain of the controller (P1120) has been set too high.
Remedy – Motor/controller data not correct
– Replace control module
– replace the power section
– for an active rotor position identification (P1019, current, rotor posi-tion
identification) check and, if required, reduce
– Reduce the P gain of current controller (P1120), check the current
controller adaptation (P1180, P1181, P1182)
Acknowledge / Stop POWER ON / STOP I

164
 504
Measuring circuit error, motor measuring system
Cause The signal level of the motor encoder is too low, faulty (inadequate
screening), or the interrupted conductor monitoring function has re-sponded.
Remedy – Use the original Siemens pre–assembled encoder cables (better screening)
– Check the encoder, encoder cables and connectors between the mo-tor
and control module
– Check the screen connection at the front panel of the control module (top screw)
– Check for sporadic interruptions (loose contact, e.g. when the drag cable is being
moved)
– Replace the encoder cables or the control module
– For toothed–wheel encoders, check the clearance between the toothed
wheel and sensor
– Exchange the encoder or motor
For synchronous motors:
Replace the complete motor (including the motor measuring system, as
the encoder can only be adjusted in the factory)
For induction motors:
Only one encoder has to be replaced
For linear motors:
– Check the signal level. The measuring tape may be dirty if the mea-suring
system is open.
– Check the scanning head adjustment.
– Check the screen connection of the motor temperature cable.
Acknowledge / Stop POWER ON / STOP I

505
Meas.circ.error motor meas.syst.abs.track
Cause 1. The motor absolute track (CD track) is monitored for an interrupted
conductor. For optical encoders, the absolute track supports the eva-luation
of the mechanical position within one motor revolution.
2. For absolute encoders with EnDat interface, this fault displays an
initialization error.
Note:
More information on the reason for the fault is stored in P1023 (diagno-stics
measuring circuit motor absolute track).
Remedy – Check the encoder, encoder cables and connectors between the motor and control
module
– Incorrect encoder cable type
– Check for sporadic interruptions (loose contact, e.g. when the drag
cable is being moved)
– Remove noise which is coupled in due to inadequate screening of the
cable by replacing the encoder cable
– Replace the control module
– Incorrect encoder type configured (e.g. ERN instead of EQN)
– Replace encoder
For synchronous motors:
Replace the complete motor (including the motor measuring system, as
the encoder can only be adjusted in the factory)
For induction motors:
Only one encoder has to be replaced
Acknowledge / Stop POWER ON / STOP I

165
 507
Synchronization error rotor position
Cause The difference between the actual rotor position and the new rotor posi-tion,
which was determined by fine synchronization is greater than 45
degrees electrical.
When commissioning a linear motor with rotor position identification
(e.g. linear motor, 1FE1 motor), the fine synchronization was not adju-sted.
Remedy – Adjust the fine synchronization using P1017 (commissioning help function)
– check the encoder cable, encoder cable connection and grounding
(possibly EMC problems)
– Check the screen connection at the front control module panel (top
screw)
– Replace encoder
– Replace motor
– Replace the control module
For linear motors:
– Check the adjustment of the angular commutation offset
– Check the screen connection of the motor temperature cable
– For distance–coded reference marks in the dialog box ”Measuring
system/encoder”, was the ”Incremental – several zero marks” point se-lected?
Acknowledge / Stop POWER ON / STOP I

508
Zero mark monitoring, motor measuring system
Cause The measured rotor position fluctuates between 2 encoder zero marks
(encoder lines may have been lost).
Note:
The encoder monitoring function can be disabled using P1600.8.
Remedy – Use the original Siemens pre–assembled encoder cables (better screening)
– Check the encoder, encoder cables and connectors between the motor and control
module
– Check the screen connection at the front panel of the control module (top screw)
– Check for sporadic interruptions (loose contact, e.g. when the drag
cable is being moved)
– Replace the encoder cables or the control module
– For toothed–wheel encoders, check the clearance between the toothed wheel and
sensor
– Exchange the encoder or motor
For synchronous motors:
Replace the complete motor (including the motor measuring system, as
the encoder can only be adjusted in the factory)
For induction motors:
Only one encoder has to be replaced
For linear motors:
– For the RGH22B measuring system from Renishaw, the ”BID” signal
must be connected with 0 V (reference mark in one direction).
– Check the screen connection of the motor temperature cable.
– For distance–coded reference marks in the dialog box ”Measuring
system/encoder”, was the ”Incremental – several zero marks” point se-lected?
Acknowledge / Stop POWER ON / STOP I

166
 509
Drive converter limiting frequency exceeded
Cause The speed actual value has exceeded the maximum permissible value.
Remedy – encoder pulse number is too low, enter the actual encoder pulse number in P1005
– stop the belt slipping in open–loop torque controlled mode (the belt slips)
– check P1400 (rated motor speed)
– check P1146 (maximum motor speed)
– check P1147 (maximum speed actual value)
– check P1112 (motor pole pair number)
– check P1134 (rated motor frequency)
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

515
Heatsink temperature exceeded
Cause The power section temperature is sensed using a temperature sensor
on the heatsink. The drive is immediately shut down 20 seconds after
the heatsink temperature alarm in order to prevent the power section
being thermally destroyed (regenerative stop).
Remedy Improve the drive module cooling, e.g. using:
– Higher airflow in the switching cabinet, possibly cool the ambient air
of the drive modules
– Avoid many acceleration and braking operations which follow quickly
one after the other
– Check that the power section for the axis/spindle is adequate, other-wise
use a higher–rating module
– Ambient temperature too high (refer to the Planning Guide)
– Permissible installation altitude exceeded (refer to the Planning Guide)
– Pulse frequency too high (refer to the Planning Guide)
– Check and, if required, replace the fan (external fan for 300/400 A module)
– Maintain the minimum clearance above and below the power section
(refer to the Planning Guide)
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

597
PROFIBUS: Drive not in synchronism. Supplementary information: \%X
Cause Supplementary information
0x01:
The master sign–of–life (STW2 Bit 12–15) has more consecutive failu-res
than are permitted. The permissible sign–of–life errors are indicated
via P0879 Bit 2–0 (configuration of synchronous PROFIBUS).
0x02:
In operation, the global control clock cycle had more consecutive failures than are
permitted.
Remedy – Check whether the PROFIBUS master can operate in synchronism
with the clock cycle, and that the necessary global–control frames are
output for operation in synchronism with the clock cycle.
– Check whether clock synchronism has been activated in the bus con-figuration,
although it is not controlled by the master used.
– Check whether the master sign–of–life (STW2, bits 12–15) is recei-ved
and is incremented in the parameterized clock cycle.
Acknowledge / Stop RESET FAULT MEMORY / STOP II

167
 598
PROFIBUS: Synchronization error. Supplementary info: \%X
Cause Supplementary information
0x01:
The expected 1st global control clock cycle display did not occur within
the waiting time.
0x02:
PLL synchronization unsuccessful
0x03:
When synchronizing to the clock cycle, the global control clock cycle
had more consecutive failures than are permitted.
0x06:
The data frames w. the process data (setpoint direction) were only re-ceived
after the time (To–125us) in the slave has expired.
Remedy – Check whether the PROFIBUS master can operate in synchronism
with the clock cycle, and that the necessary global–control frames are
output for operation in synchronism with the clock cycle.
– Check whether clock synchronism has been activated in the bus con-figuration,
although it is not controlled by the master used.
– Check whether the time Tdx, defined in the master software, corres-ponds
to the actual data transfer time to all of the slaves and is less
than the configured time (To–125us).
Acknowledge / Stop RESET FAULT MEMORY / STOP II

599
PROFIBUS: Cyclic data transfer was interrupted
Cause The cyclic data transfer between the master and slave was interrupted
due to the fact that cyclic frames were missing, or due to the reception
of a parameterizing or configuring frame.
Examples:
– bus connection interrupted
– Master runs up again
Remedy Check the master and bus connection to the master. As soon as cyclic
data transfer runs again, the fault can be acknowledged.
Acknowledge / Stop RESET FAULT MEMORY / STOP II

601
Error in AD conversion, terminal 56/14 or 24/20
Cause A timing error was identified when reading–out the A/D converter for
terminal 56.x/14.x or 24.x/20.x. The read values are probably incorrect / faulty.
Remedy Replace closed–loop control module
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

168
 602
Open–loop torque controlled oper. w/o encoder is not perm.
Cause In the IM mode, open–loop torque–controlled operation was selected
via the input terminal or via PROFIBUS–DP.
Remedy Deselect the torque–controlled operation or leave the IM mode (chan-geover
speed P1465).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

603
Changeover to non–parameterized motor data set
Cause An attempt was made to change over to a motor data set which was
not parameterized.
Remedy Parameterizing motor data set
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

605
Position controller output limited
Cause The speed setpoint requested from the position controller lies above
the max. motor speed.
Possible causes:
– Programmed velocity (P0082:64) too high
– Max. acceleration (P0103) or deceleration (P0104) too high
– Axis is overloaded or blocked
Remedy – Check parameters
Acknowledge / Stop RESET FAULT MEMORY / STOP II

606
Flux controller output limited
Cause The specified flux setpoint cannot be realized, although maximum current is input.
– Motor data are incorrect
– Motor data and motor connection type (star/delta) do not match
– Motor has stalled because motor data are extremely inaccurate
– Current limit is too low for the motor (0.9 * P1238 * P1103 < P1136)
– Power section is too small
Remedy – Correct the motor data
– If required use a larger power section
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

169
 607
Current controller output limited
Cause The entered setpoint cannot be impressed in the motor, although the
maximum voltage is available. Either the motor is not connected or a phase is
missing.
Remedy – check the connecting cable, motor/drive converter (phase missing)
– Check the motor contactor
– DC link voltage present?
– check the DC link busbar (check that the screws are tight)
– Uce monitoring function in the power section has responded (RESET
by powering off/powering on)
– Replace the power section or control module
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

608
Speed controller output limited
Cause The speed controller is at its limit for an inadmissibly long time (torque or current
limit). The permissible time is defined in P1605, the upper speed limit when the
monitoring responds, in P1606.
Synchronous motor:
In correct operation, the correctly optimized axis drive should never
reach its current limit, not even with large speed changes (changing
from rapid traverse in the positive direction to rapid traverse in the negative
direction).
P1605 = 200 ms
P1606 = 8000 rev/min
Induction motor:
Acceleration and braking with the maximum torque/current are usual in
operation, only a stalled drive (0 speed) is monitored.
P1605 = 200 ms
P1606 = 30 rev/min
1. At the first commissioning, after the software has been replaced or
the software has been upgraded, after the parameters have been ent-ered
the ”calculate motor data” or ”calculate controller data” function
was not executed. The drive then keeps the default values (for the va-lues
to be calculated this is zero) which can, under certain circumstan-ces,
result in this fault (P1605 and P1606 should be adapted to the me-chanical
and dynamic capabilities of the axis).
2. An undesirable input of a large torque reduction via the analog inputs
or via PROFIBUS. On PROFIBUS, this effect especially occurs when
changing over from positioning operation to operation with speed set-point
input (check whether a torque reduction has been entered. Dia-gnostics
via P1717, 0%: no torque, 100%: full torque).
Remedy – Check connecting cable motor/converter (phase missing, exchanged)
– Check the motor contactor
– Check the torque reduction (P1717)
– DC link voltage present?
– Check the DC link voltage (check that the screws are tight)
– Uce monitoring function in the power section has responded (RESET
by powering off/powering on)
– Unblock the motor
– Is the motor encoder connected?
– Check the motor encoder cable screen
– Is the motor grounded (PE connection)?

170
 – Check the encoder pulse number (P1005)
– Does the encoder cable fit to the encoder type?
– Check the direction of rotation of the encoder tracks (e.g. toothed–
wheel encoder, P1011)
– Replace the power section or control module
Adapt parameters P1605 and P1606 to the mechanical and dynamic
capabilities of the axis. Check whether a torque reduction has been
entered (diagnostics via P1717, 0%: no torque, 100%: full torque).
For linear motors:
– Check actual value inversion
– Check the reduction in the maximum motor current (P1105) and if
required increase the value
– Check the power cable connection
– For the parallel circuit configuration, are the motors correctly assi-gned
and electrically connected?
Acknowledge / Stop RESET FAULT MEMORY / STOP

609
Encoder limit frequency exceeded
Cause The speed actual value exceeds the encoder frequency.
– Incorrect encoder
– P1005 does not correspond to the no. of encoder pulses
– Encoder defective
– Motor cable defective or not properly attached
– Shield on motor encoder cable is not connected
– Defective control module
Remedy – Enter correct encoder data / replace encoder
– Check the encoder pulse number (P1005)
– Attach motor cable correctly or replace
– connect the motor encoder cable screen
– Reduce the speed setpoint input (P1401)
– Replace control module
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

610
Rotor position identification has failed
Cause A rotor position could not be determined from the measurement signals
(motor current), as no significant saturation effects occurred.
Remedy – increase current via P1019
– check the connecting cable, motor/drive converter (phase missing)
– Check the motor contactor
– DC link voltage present?
– check the DC link busbar (check that the screws are tight)
– Uce monitoring function in the power section has responded (RESET
by powering off/powering on)
– Replace the power section or control module
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

171
 611
Illegal motion during rotor position identification
Cause During the rotor position identification (motor current measurement),
the motor rotated more than the value entered in P1020. The rotation
could be caused by having powered on with the motor already rotating,
or caused by the identification routine itself.
Remedy – If the interchange was caused by the identification itself and if the
error occurs again, then reduce P1019 or increase P1020.
– Lock the motor rotor during the identification routine.
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

612
Illegal current during rotor position identification
Cause 1. Current was >= 1.2 * 1.05 * P1107 while rotor position identification was active
2. Current was >= P1104 while rotor position identification was active
Remedy With the rotor position identification (P1011.12 and P1011.13) activa-ted,
if required, check and reduce P1019 (current, rotor position identifi-cation)
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

172
 613
Shutdown limit, motor overtemperature (P1607) excee-ed
Cause The motor temperature (sensed via the temperature sensor KTY 84
and fed to the module via the motor encoder cable) has exceeded the
temperature limit in P1607.
Remedy – Avoid many acceleration and braking operations which follow one another quickly.
– Motor overload?
– Check whether the motor output is sufficient for the drive, otherwise
use a more powerful motor, possibly together with a higher–rating power section.
– Check the motor data. The current could be too high due to incorrect motor data.
– Check the temperature sensor.
– Check the motor fan.
– Check the motor encoder cable.
– Motor encoder defective?
– Check and possibly reduce P1230 or P1235.
The motor temperature monitoring can be disabled with P1601 bit 13 = 1.
For linear motors:
– Check the parameters for the motor temperature monitoring
P1602 (alarm threshold, motor overtemperature) = 120 degrees C
P1603 (timer, motor temperature alarm) = 240 s
P1607 (shutdown limit, motor temperature) = 155 degrees C
P1608 (fixed temperature) = 0 degrees C
P1608 = 0 ––> Temperature sensing active
P1608 > 0 ––> Fixed temperature active
– If the temperature monitoring is exclusively realized using an external
PLC, a fixed temperature must be entered into P1608 (e. g. 80 degrees C). This
disables the drive temperature monitoring.
– Check the power connector at the motor
– Check the connection of the temperature sensor coupling cable at the
end of the power cable; approximately 580 ohm must be measured at
20 degrees C
– With the measuring system connectors withdrawn (X411), are approximately 580
ohm measured between PIN 13 and PIN 25 of the encoder cable at 20 degrees C?
– Check that the measuring system connector is correctly located at the drive (X411)
– Only KTY may be connected for drives connected in parallel
– If the temperature switch and temperature sensor are connected in
series, the temperature sensor (NC contact) may have responded, or
the temperature switch is defective
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

173
 614
Delayed shutdown for motor overtemperature (P1602 / P1603)
Cause The motor temperature (sensed via the temperature sensor KTY 84
and fed to the module via the motor encoder cable) has exceeded the
temperature in P1602 for a time longer than in P1603.
Remedy – Avoid many acceleration and braking operations which follow one another quickly.
– Motor overload?
– Check whether the motor output is sufficient for the drive, otherwise
use a more powerful motor, possibly together with a higher–rating power section.
– Check the motor data. The current could be too high due to incorrect motor data.
– Check the temperature sensor.
– Check the motor fan.
– Check the motor encoder cable.
– Motor encoder defective?
– Check and possibly reduce P1230 or P1235.
The motor temperature monitoring can be disabled with P1601 bit 14 = 1.
For linear motors:
– Check the parameters for the motor temperature monitoring
P1602 (alarm threshold, motor overtemperature) = 120 degrees C
P1603 (timer, motor temperature alarm) = 240 s
P1607 (shutdown limit, motor temperature) = 155 degrees C
P1608 (fixed temperature) = 0 degrees C
P1608=0 Temperature sensing active
P1608>0 Fixed temperature active
– If the temperature monitoring is exclusively realized using an external
PLC, a fixed temperature must be entered into P1608 (e. g. 80 degrees C). This
disables the drive temperature monitoring.
– Check the power connector at the motor
– Check the connection of the temperature sensor coupling cable at the
end of the power cable; approximately 580 ohm must be measured at 20 degrees C
– With the measuring system connectors withdrawn (X411), are approximately 580
ohm measured between PIN 13 and PIN 25 of the enco-der cable at 20 degrees C?
– Check that the measuring system connector is correctly located at the drive (X411)
– Only KTY may be connected for drives connected in parallel
– If the temperature switch and temperature sensor are connected in
series, the temperature sensor (NC contact) may have responded, or
the temperature switch is defective
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

174
 680
Illegal motor code number
Cause A motor code was entered in P1102 for which no data is available.
Remedy Start–up again and enter the correct motor code number (P1102).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

681
Illegal power section code number
Cause A power section code was entered in P1106, for which no data is avai-lable.
Remedy Enter the correct power section code in P1106.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

682
Illegal encoder code number
Cause An encoder code was entered in P1006, for which no data is available.
Remedy Enter the correct encoder code in P1006 or the code for a third party encoder (99).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

683
Calculate controller data was unsuccessful at first start–up (\%d)
Cause An error occurred at the first start–up with ”calculate controller data”.
Under fault conditions, the parameters for the current controller, flux
controller and speed controller could not be optimally assigned.
Remedy Read out the detailed error cause from P1080 and remove the cause.
Then initiate ”calculate controller data” again with P1080 = 1. Repeat
this operation, until no error is displayed in P1080. Then save in the
FEPROM and execute a POWER ON–RESET.
Error coding in the supplementary info and P1080:
–15 magnetizing reactance (P1141) = 0
–16 leakage reactance (P1139 / P1140) = 0
–17 rated motor frequency (P1134) = 0
–18 rotor resistance (P1138) = 0
–19 motor moment of inertia (P1117) = 0
–21 threshold speed for field weakening (P1142) = 0
–22 motor standstill current (P1118) = 0
–23 The ratio between the maximum motor current (P1104) and the
motor stall current (P1118) is greater than the maximum value for the
torque limit (P1230) and the power limit (P1235).
–24 The ratio between the rated motor frequency (P1134) and the rated
motor speed (P1400) is inadmissible (pole pair number).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

175
 703
Invalid current controller cycle
Cause An illegal value was entered in P1000.
Remedy Enter a valid value in P1000.
Permissible values for P1000 are:
2 (62.5us) for single–axis positioning or for speed setpoint input
4 (125us) in each operating mode
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

704
Invalid speed controller cycle
Cause An illegal value was entered in P1001.
Remedy Enter a valid value in P1001.
Permissible values for P1001 are 2 (62.5 us), 4 (125us), 8 (250us), 16 (500us).
Setting 2 (62.5us) is only permissible for single–axis operation.
Further, P1001 must be >= P1000.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

705
Invalid position controller cycle
Cause The monitoring function identified a position controller cycle (P1009)
outside the permissible limits.
Remedy Enter a valid value in P1009.
Permissible values for P1009 lie between 32 (1 ms) and 128 (4ms).
Further, the position control cycle must be a integral multiple of the speed control
cycle.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

706
Invalid interpolation cycle
Cause The monitoring has identified an interpolation cycle (P1010) outside the
permissible limits, or an illegal ratio between the interpolation cycle and
the position controller cycle (P1009).
Remedy Enter a valid value in P1010 or correct P1009.
Permissible values for P1010 lie between 128 (4ms) and 640 (20ms).
Further, the interpolation cycle must be an integral multiple of the posi-tion
controller cycle.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

708
Axial deviations in current controller cycle
Cause On a 2–axis module, the current controller cycle is different for both axes.
Remedy Check P1000 and set the input values the same for both drives.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

176
 709
Axial deviations in speed controller cycle
Cause On a 2–axis module, the speed controller cycle is different for both axes.
Remedy Check P1001 and set the input values the same for both drives.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

710
Axial deviations in position controller or interpolation cycle
Cause 1. On a 2–axis module, the position controller cycle (P1009) or the in-terpolation
cycle (P1010) is different for the two axes.
2. Via the clock–synchronous PROFIBUS, a position controller cycle is
specified for an axis in n–set mode which differs from the position con-troller
cycle (P1009) of the other axis in positioning mode.
Remedy 1. Check P1009 / P1010 and set the same input values for both drives.
2. For synchronous PROFIBUS, adjust the bus configuration (parame-ter
setting) with P1009.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

716
Invalid torque constant
Cause The ratio between the rated torque and rated current (torque constant
[Nm/A]) in P1113 is incorrect (less than/equal to zero) or the ratio
P1113 / P1112 is greater than 70.
Remedy Enter the valid torque/current ratio for the motor used in P1113 or enter
a permissible ratio of P1113 / P1112.
Third–party motor:
The torque constant should be determined from the motor data sheet.
Siemens motor:
The torque constant is defined by the motor code (P1102).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

719
Motor not parameterized for delta operation
Cause When the star–delta changeover is activated using P1013, the motor is
not parameterized for delta operation (motor 2).
Remedy Check and enter the parameters for delta operation (motor 2).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

177
 720
Invalid maximum motor speed
Cause Due to the high maximum motor speed in P1401 and the speed con-troller
cycle in P1001, high partial speeds can occur which can result in
a format overflow.
Remedy Check and correct P1401 and P1001.
The drive software is designed for large reserve margins, so that the
displayed alarm can only occur as a result of a parameterizing error.
Example:
For a speed controller cycle time of 125 microseconds, a motor speed
of 480 000 RPM can still be processed correctly!
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

723
Axial deviations in STS configuration
Cause On a 2–axis module, the gating unit configuration (P1003) is different for the two
gating units.
Remedy Check P1003 and set the bits for the two module axes the same (do
not change the standard setting, this represents the optimum configura-tion).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

724
Invalid motor pole pair number
Cause Synchronous motors:
The configured pole pair number in P1112 is incorrect (zero or nega-tive).
Induction motors:
An invalid pole pair number was determined from P1134 and P1400.
Remedy Synchronous motors:
Actually possible pole pair numbers are e.g. 2, 3, or 4.
Induction motors:
Determine the rated speed and rated frequency and enter correctly.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

725
Invalid encoder pulse number
Cause The encoder pulse number of the motor measuring system (P1005) is set to zero.
Remedy Harmonize the encoder pulse number of the motor measuring system
in P1005 to the encoder used. The indirect motor measuring system
must always be configured for synchronous and induction motors (exception:
Induction motor operation).
Standard setting: 2 048 increments/revolution
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

178
 726
Invalid voltage constant
Cause The voltage constant of the motor is set to zero in P1114.
Remedy Determine the voltage constant of the motor used, and enter in P1114.
The voltage constant is measured as induced voltage (EMF) under noload conditions
at n=1 000 RPM as RMS valued at the motor terminals (phase to phase).
Third–party motor:
The voltage constant should be determined from a motor data sheet.
Siemens motor:
The voltage constant is determined from the motor code (P1102).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

727
Invalid combination of power section and synchronous motor
Cause The power section is not released for synchronous motors.
Remedy – check configuring
– use a valid power section
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

728
Torque/current adaptation factor too high
Cause The adaptation factor between the setpoint torque and the torque gene-rating
current (Iq) in the speed controller is too high.
Remedy Check P1103, P1107 and P1113 and if required, enter correct values.
Third–party motor:
The values should be determined from a motor data sheet.
Siemens motor:
The values are determined from the motor code (P1102).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

729
Invalid motor stall current
Cause The motor stall current (P1118) is less than or equal to zero.
Remedy Determine the stall current of the motor used and enter in P1118.
Third–party motor:
The stall current should be determined from a motor data sheet.
Siemens motor:
The stall current is determined from the motor code (P1102).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

179
 731
Invalid rated output
Cause The rated motor output (P1130) of the motor is less than or equal to zero.
Remedy Determine the rated motor output of the motor used and enter in P1130.
Third–party motor:
The rated motor output should be determined from a motor data sheet.
Siemens motor:
The rated motor output is determined from the motor code (P1102).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

732
Invalid rated speed
Cause The rated motor speed (P1400) of the motor is less than or equal to zero.
Remedy Determine the rated motor speed of the motor used and enter inP1400.
Third–party motor:
The rated motor speed should be determined from a motor data sheet.
Siemens motor:
The rated motor speed is determined from the motor code (P1102).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

742
V/f operation: Drive frequency, motor \%d not permissi-ble
Cause In V/f operation, only drive converter frequencies of 4 or 8 kHz are per-missible.
Remedy Change P100 or cancel V/f operation (P1014).
When operating with several motors/motor data sets, also set
P2100/P3100/P4100 to 4 or 8 kHz.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

744
Motor changeover only permissible for the closed–loop speed controlled mode
Cause Motor changeover (P1013) may only be activated in the closed–loop
speed controlled mode (P0700 = 1).
Remedy – Inhibit motor changeover (P1013 = 0)
– Change over into the closed–loop speed controlled mode (P0700 = 1)
Acknowledge / Stop POWER ON / STOP I

180
 751
Speed controller gain too high
Cause P gain, speed controller for the lower speed range (P1407) and the up-per
speed range (1408) were selected to be too high.
Remedy Reduce the P gain of the speed controller.
Only optimized with the adaption disabled (P1413 = 0). The P gain
(P1407) is then effective over the complete speed range. After the opti-mum
setting has been found, adaption can be re–enabled (P1413 = 1)
and the P gain optimized for the upper speed range (P1408).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

756
Invalid speed hysteresis of the current setpoint smoo-thing
Cause The hysteresis of the speed for the current setpoint smoothing (P1246)
may not be greater than the threshold speed of the hysteresis (P1245),
as otherwise a ”negative” lower speed would be obtained.
Remedy P1246 (standard value: 50 [RPM]) must be entered lower than the
threshold for the speeddependent setpoint smoothing (P1245, standard
value: 4 000 [RPM]).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

757
PZD config.: illegal frame no. in P0922
Cause The frame number set in P0922 is illegal or impermissible for the ope-rating
mode currently selected via P0700.
Remedy Check P0922 and enter valid value.
Acknowledge / Stop POWER ON / STOP II

759
Encoder/motor types do not match
Cause A linear motor was selected, and no linear scale configured (P1027.4 = 0).
A rotating motor was selected and a linear scale configured (P1027.4 =1).
A resolver has been selected the pole pair number (P1018) of which is
illegal. A pole pair number =1 or the pole pair number of the motor (P1112) is
admissible.
Remedy Parameterize the encoder type corresponding to the motor type and
the control module.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

181
 760
Pole pair width/scale graduations cannot be represented internally
Cause For linear motors, the equivalent (internal) pole pair number and (inter-nal)
encoder pulse number are calculated from the pole pair width and
grid spacing data. In this case, one or x pole pair widths must be an
integer multiple of the encoder pulse number. This error message is
output if the result of pole pair width/line division * x (up to x=16) is not
an integer number, or if the calculated internal encoder pulse number is too high.
A result with a tolerance of +/– 0.001 absolute is interpreted to be an integer.
Remedy Long travel paths:
A linear measuring system with an encoder mark number that is an in-tegral
divisor of x* pole pair widths should be used.
Short travel paths:
For short travel, only a low error can accumulate which has hardly any
effect on the maximum achievable force and on the temperature rise, if
the encoder pulse number fits with a deviation of more than +/–0.001 in
the pole pair width. We then recommend that the pole pair width is
slightly changed:
Example:
Pole pair width: 56.8 mm, grid spacing: 2.7 micrometers
=> pole pair number = 1, encoder lines = 21037.037 => error
Resolve the error by entering a pole pair width = 56.7999 mm.
=> pole pair number = 1, encoder lines = 21037.0 => no error
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

761
P0892 cannot be used with this measuring system
Cause For incremental measuring systems with sin/cos 1 Vpp without EnDat
interface, a division factor cannot be set using P0892.
Remedy Set P0892 to 0 (factor, angular encoder pulse number/encoder pulse number).
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

762
P0893 cannot be used with this measuring system
Cause For incremental measuring systems with sin/cos 1 Vpp without EnDat
interface and for linear measuring systems with sin/cos 1 Vpp with En-Dat
interface, a zero pulse offset cannot be set via P0893.
Remedy Set P0893 (angular encoder zero pulse offset) to 0.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

764
Multiple assignment of terminal A or B (P0890)
Cause When selecting 3 in P0890, from drive A or B (setpoint at terminal A
and actual value at terminal B), it was identified, that terminal A or B
were already being used by another drive. Thus, this configuration is not possible.
Remedy Check the configuration of terminals A and B in P0890 and eliminate
multiple assignments of both drives.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

182
 765
P0890 and P0891 configure both setpoint inputs
Cause An actual value coupling is switched in (P0891 = 1) for drive B. Simul-taneously,
for the same drive, terminal A or B is parameterized as posi-tion
setpoint input (P0890 = 2 or 3).
Remedy Check the configuration of terminals A and B in P0890, compare with
P0891 and eliminate multiple setpoint sources.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

766
Blocking frequency > Shannon frequency
Cause The bandstop frequency of a speed setpoint filter is greater than the
Shannon sampling frequency from the sampling theorem.
Remedy The bandstop frequency for P1514, filter 1 and P1517 for filter 2 must
be less than the inverse of two speed controller cycles
(1/2*P1001*31.25 microseconds).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

767
Natural frequency > Shannon frequency
Cause The natural frequency of a speed setpoint filter is greater than the
Shannon sampling frequency from the sampling theorem.
Remedy The natural frequency of a speed setpoint filter must be lower than the
reciprocal of two speed controller cycles.
Speed setpoint filter 1:
P1520 * 0.01 * P1514 < 1 / ( 2 * P1001 * 31.25 microseconds)
Speed setpoint filter 2:
P1521 * 0.01 * P1517 < 1 / ( 2 * P1001 * 31.25 microseconds)
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

768
Numerator bandwidth > twice the blocking frequency
Cause The numerator bandwidth of a current or speed setpoint filter is greater
than twice the bandstop frequency.
This alarm is only generated for the general bandstop, if the following is valid:
Speed setpoint filter 1: P1516 > 0.0 or P1520 <> 100.0
Speed setpoint filter 2: P1519 > 0.0 or P1521 <> 100.0
Current setpoint filter 1: P1212 > 0.0
Current setpoint filter 2: P1215 > 0.0
Current setpoint filter 3: P1218 > 0.0
Current setpoint filter 4: P1221 > 0.0
Remedy The numerator bandwidth must be less than twice the bandstop fre-quency.
Current setpoint filter 1: P1212 <= 2 * P1210
Current setpoint filter 2: P1215 <= 2 * P1213
Current setpoint filter 3: P1218 <= 2 * P1216
Current setpoint filter 4: P1221 <= 2 * P1219
Speed setpoint filter 1: P1516 <= 2 * P1514
Speed setpoint filter 2: P1519 <= 2 * P1517
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

183
 769
Denominator bandwidth > twice the natural frequency
Cause The denominator bandwidth of a current or speed setpoint filter is grea-ter
than twice the natural frequency.
This alarm is only generated for the general bandstop, if the following is valid:
Speed setpoint filter 1: P1516 > 0.0 or P1520 <> 100.0
Speed setpoint filter 2: P1519 > 0.0 or P1521 <> 100.0
Current setpoint filter 1: P1212 > 0.0
Current setpoint filter 2: P1215 > 0.0
Current setpoint filter 3: P1218 > 0.0
Current setpoint filter 4: P1221 > 0.0
Remedy The denominator bandwidth of a current or speed setpoint filter must
be less than twice the natural frequency.
Speed setpoint filter 1: P1515 <= 2 * P1514 * 0.01 * P1520
Speed setpoint filter 2: P1518 <= 2 * P1517 * 0.01 * P1521
Current setpoint filter 1: P1211 <= 2 * P1210
Current setpoint filter 2: P1214 <= 2 * P1213
Current setpoint filter 3: P1217 <= 2 * P1216
Current setpoint filter 4: P1220 <= 2 * P1219
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

770
Format error
Cause The calculated bandstop filter coefficients cannot be represented in the internal
format.
Remedy Change filter setting.
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

771
Induction motor oper.: drive converter frequency motor \%d not permissible
Cause In induction motor operation (selected by P1465 < P1146), drive con-verter
frequencies of 4 or 8 kHz are permissible.
Remedy – change P1100
– cancel induction motor operation (P1465 > P1146)
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

772
Induction motor oper.: speed controller gain, motor \%d too high
Cause The P gain of the speed controller (P1451) is too high.
Remedy For the speed controller, enter a lower value for the P gain (P1451).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

773
Not permissible to active analog input
Cause For this particular hardware version, it is not permissible to activate the
analog input.
Remedy Use the 611U board.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

184
 774
Induction motor oper.: changeover speed motor \%d not permissible
Cause For mixed operation (with / without encoder) P1465 > 0, only closed–
loop controlled induction motor operation is permissible (P1466 <= P1465).
Remedy Eliminate error by selecting pure induction motor operation (P1465 = 0)
or by canceling induction motor open–loop controlled operation (P1465 > P1466).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

777
Current for the rotor position identification too high
Cause A current was parameterized in P1019, which is greater than the cur-rent
which is permissible for the motor and the power section used.
Remedy Reduce the current via P1019.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

778
Impermissible converter frequency for rotor position ID
Cause When selecting the rotor position identification (P1019), drive converter
Frequencies (P1100) of 4 or 8 kHz are permissible.
Remedy Change the drive converter frequency or cancel the rotor position iden-tification.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

779
Motor moment of inertia, motor \%d invalid
Cause The motor moment of inertia (P1117) is incorrect (less than/equal to zero).
Remedy Enter the valid motor moment of inertia for the motor used, in P1117.
Third–party motor:
The motor moment of inertia should be determined from a motor data sheet.
Siemens motor:
The characteristic motor data should be determined from the motor
code (P1102).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

780
No–load current, motor > rated motor current (motor \%d)
Cause The motor no–load current (P1136) has been parameterized greater
than the rated motor current (P1103).
Remedy Enter the valid currents for the motor used in P1136 and P1103.
Third–party motor:
The required currents should be determined using a motor data sheet.
Siemens motor:
The currents are determined using the motor code (P1102).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

185
 781
No–load current, motor \%d > rated power section cur-rent
Cause The motor no–load current (P1136) has been set to higher values than
the rated power section current.
before SW 2.4 the following is valid: Rated power section current = P1111
from SW 2.4 the following is valid: Rated power section current = P1111 * P1099
Remedy – Enter the valid current for the motor used in P1136.
Third–party motor:
The required currents should be determined using a motor data sheet.
Siemens motor:
The currents are determined using the motor code (P1102).
– Reduce the power section pulse frequency P1100.
– Use a higher–rating power section (re–commission).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

782
Reactance motor \%d invalid
Cause The stator leakage reactance (P1139) or the rotor leakage reactance
(P1140) or the magnetizing reactance (P1141) of the motor is incorrect
(less than/equal to zero).
Remedy Determine the stator, rotor leakage reactance and magnetizing reac-tance
of the motor used and enter in P1139, P1140 and P1141.
Third–party motor:
The values should be determined from a motor data sheet.
Siemens motor:
The values are determined from the motor code (P1102).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

783
Rotor resistance, motor \%d invalid
Cause The rotor resistance (P1138, cold) of the motor is incorrect (less than/ equal to zero).
Remedy Determine the cold rotor resistance of the motor used and enter in P1138.
Third–party motor:
The following parameters may have incorrect values:
P1001 (speed controller cycle)
P1134 (rated motor frequency)
P1138 (rotor resistance)
P1139 (leakage stator reactance)
P1140 (leakage rotor reactance)
Check parameters and if required correct using a motor data sheet.
Siemens motor:
The rotor resistance when cold is determined using the motor code (P1102).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

186
 784
No–load voltage, motor \%d invalid
Cause Error in no–load voltage P1135:
– P1135 <= 0 or
– P1135 > P1132 or
– P1135 * P1142 / P1400 + Vser.react. > 450V.
With Vser.react. = 0.181 * P1136 * P1142 * P1119
Remedy Determine the no–load voltage of the installed motor and enter this in P1135.
Third–party motor:
The following parameters may have incorrect values:
P1119 (inductance of the series reactor)
P1132 (rated motor voltage)
P1135 (no–load motor voltage)
P1400 (rated motor speed)
P1142 (threshold speed for field weakening)
P1136 (no–load motor current)
Check parameters and if required correct using a motor data sheet.
Siemens motor:
The no–load voltage is determined from the motor code (P1102).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

785
No–load current, motor \%d invalid
Cause The no–load current (P1136) of the motor is incorrect (less than/equal to zero).
Remedy Determine the no–load current of the installed motor and enter in P1136.
Third–party motor:
The no–load current should be determined from a motor data sheet.
Siemens motor:
The no–load current is determined from the motor code (P1102).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

786
Field–weakening speed, motor \%d invalid
Cause The threshold speed for field weakening for induction motors (P1142) is
incorrect (less than/equal to zero).
Remedy Determine the threshold speed for field weakening for the motor used
and enter in P1142.
Third–party motor:
The field weakening speed should be determined from a motor data sheet.
Siemens motor:
The field weakening speed is determined from the motor code (P1102).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

187
 787
Induction motor oper.: feedforward control gain motor \%d cannot be displayed
Cause The feedforward control gain for induction motors cannot be represen-ted
in the internal numerical format if the motor moment of inertia and
rated motor torque were unfavorably selected.
Remedy Operation without encoder:
Reduce the encoder pulse number (P1005), as this is used in the inter-nal
numerical format.
Operation with encoder:
Reduce the speed controller cycle (P1001).
Acknowledge / Stop RESET FAULT MEMORY / STOP II (SRM) STOP I (ARM)

788
P0891 for drive B only
Cause An actual–value link has been activated (P0891 = 1) for drive A. The
hardware does not permit this setting.
Remedy Set P0891 to 0 for drive A.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

789
Setpoint transfer SimoCom U ==> drive interrupted
Cause The setpoint transfer from SimoCom U to the drive was interrupted, i.e.
there is no longer an online connection. The Master Control was retur-ned
to the drive.
Communication between the two communication partners was faulty.
When traversing the drive via SimoCom U, other functions were execu-ted
on the PG/PC (e.g. open online help, open file), so that the drive
can only be irregularly supplied from SimoCom U.
Remedy – Check whether SimoCom U is still operating correctly, if required, re–start
– Check whether the communication connection is OK, if required, re-place
the connecting cable
– When in the online mode, do not select any time–intensive functions
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

188
 790
Illegal operating mode. Supplementary info: \%u
Cause The selected operating mode (P0700) is not permitted for this module or axis.
Supplementary info = 0x1:
Operating mode ==0 selected on the 1st axis
Supplementary info = 0x2:
POSITIONING operating mode selected for the Nset control module
Supplementary info = 0x3:
Operating mode is not possible with this firmware release
Remedy For supplementary info 1:
Select valid operating mode (P0700 > 0)
For supplementary info 2:
Select Nset operating mode or use a positioning module.
For supplementary info 3:
Use a firmware release which supports this operating mode.
Acknowledge / Stop POWER ON / STOP I

791
TTL encoder interface incorrectly parameterized
Cause The TTL encoder interface may only be parameterized as follows for
this particular hardware version:
Drive A: P0890 = 0 or 4, 0: Interface inactive, 4: TTL encoder input
Drive B: P0890 = 0
Remedy Set P0890 to permissible value.
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

797
Error in center frequency measurement
Cause The speed was too high during the center frequency measurement
(current calibration). The center frequency is measured automatically at
run–up, or when the pulses are inhibited.
Remedy Power up the drive converter if the motor runs at a reduced speed.
Acknowledge / Stop POWER ON / STOP I

798
Measured value memory active
Cause The measured–value memory was active during power–up.
Remedy Run up again.
Acknowledge / Stop POWER ON / STOP I

799
FEPROM backup and HW Reset required
Cause Parameters were re–calculated. Parameters must be saved and the
module run up again after this new calculation.
Remedy The newly calculated data should be saved in the FEPROM. The new
parameters become effective the next time that the module runs up!
Acknowledge / Stop POWER ON / STOP II (SRM) STOP I (ARM)

189
 802
Drive rotates in response to angular encoder output parameters
Cause The drive was not stationary as the zero pulse offset was programmed
on the angular encoder interface. Low speeds are not critical, but the
inaccuracy of the zero pulse position increases in proportion to speed.
Remedy Ensure that the drive is at a standstill, or take into account a higher in-accuracy
of the zero pulse.
Acknowledge / Stop not required / STOP VII

804
Controller enable or on/off 1(edge) or on/off 2/3 mis-sing
Cause When starting a traversing block, the controller enable is not set, i.e.
one of the following signals is missing:
– Terminal 64
– Terminal 65.x
– PROFIBUS control signals (STW1.0: ON / OFF 1 (edge), STW1.2: E / OFF 3)
– PC enable (SimoCom U)
Remedy Set the missing signal, and then re–start the traversing block, or output edge v
Profibus.
Acknowledge / Stop not required / STOP VII

805
Pulse enable missing
Cause When starting a traversing block, the pulse enable is not set, i.e. one of
the following signals is missing:
– terminal 48 (NE module)
– terminal NS1/NS2 (NE module)
– terminal 63 (NE module)
– terminal 663 (control module)
Remedy Set the missing enable signal and then re–start the traversing block.
Acknowledge / Stop not required / STOP VII

806
OC/reject traversing task missing
Cause When starting a traversing block, the ”operating condition / reject tra-versing
task” input signal is not set.
Remedy Set the ”operating condition / reject traversing task” input signal and
then re–start the traversing block.
Acknowledge / Stop not required / STOP VII

807
OC/intermediate stop missing
Cause When starting a traversing block the ”operating condition / intermediate
stop” input signal is not set.
Remedy Set the ”operating condition / intermediate stop” input signal and then
re–start the traversing block.
Acknowledge / Stop not required / STOP VII

190
 808
Reference point not set
Cause When starting a traversing block, a reference point is not set.
Remedy Execute referencing or set a reference point using the ”set reference point” input
signal.
Acknowledge / Stop not required / STOP VII

809
Parking axis selected
Cause When a traversing block is started, or when referencing is started, the
parking axis function is selected.
Remedy Cancel the ”parking axis” function and then re–start the required func-tion.
Acknowledge / Stop not required / STOP VII

814
Alarm threshold, motor overtemperature (P1602)
Cause The motor temperature is sensed via a temperature sensor (KTY84)
and evaluated on the drive side. This alarm is output if the motor tem-perature
reaches the alarm threshold motor overtemperature (P1602).
Remedy – Avoid many acceleration and braking operations which follow one another quickly.
– Check whether the motor output is sufficient for the drive, otherwise
use a higher output motor, possibly in conjunction with a higher–rating power section.
– Check the motor data. The motor current could be too high due to
incorrect motor data.
– Check the temperature sensor.
– Check the motor fan.
Acknowledge / Stop not required / STOP VII

815
Heatsink temperature, pre–alarm
Cause The heatsink temperature of the power section is sensed using a ther-mosensor
on the main heatsink. If the overtemperature condition re-mains,
then the drive shuts down after approx. 20 s.
Remedy Improve the drive module cooling, e.g. using:
– Higher airflow in the switching cabinet, possibly cool the ambient air
of the drive modules
– Avoid many acceleration and braking operations which follow quickly
one after the other
– Check that the power section for the axis/spindle is adequate, other-wise
use a higher–rating module
– Ambient temperature too high (refer to the Planning Guide)
– Permissible installation altitude exceeded (refer to the Planning
Guide)
– Pulse frequency too high (refer to the Planning Guide)
– Check and, if required, replace the fan (external fan for 300/400 A
module)
– Maintain the minimum clearance above and below the power section
(refer to the Planning Guide)
Acknowledge / Stop not required / STOP VII

191
 816
Resolver sensing at its limit
Cause At run–up, the speed with an existing resolver evaluation was extre-mely
high. It is possible that this was not the actual speed, and that the
resolver was not connected to the measuring circuit input.
Remedy Insert the measuring circuit connector and enter a reset.
Acknowledge / Stop not required / STOP VII

829
PROFIBUS: Illegal parameterization received
Cause An illegal parameterizing frame was received via PROFIBUS. Cyclic
data transfer cannot start.
Causes:
– The parameterizing frame is inadmissibly long.
– The parameterizing frame has an illegal structure.
– Selection of synchronous operation without having inserted a suitable
option module (P–875=4).
– Illegal clocks or clock combinations have been parameterized for syn-chronous
mode.
Remedy Check the bus configuration at the master, and if required correct the
parameterization.
Acknowledge / Stop not required / STOP VII

830
PROFIBUS: Illegal configuration received
Cause An illegal configuration frame was received via PROFIBUS. Cyclic data
transfer cannot start.
Causes:
– More axes were configured in the master than are actually physically
available in the power section.
– The number of axes configured in the master is not equal to the num-ber
of axes activated via P0875.
– The received configuration frame is incomplete.
– It was not possible to determine a legal PPO type from the configura-tion
frame.
– Calculated I/O lengths are inconsistent (internal error).
Remedy Check the bus configuring at the master and if required, select a per-missible
PPO type.
Acknowledge / Stop not required / STOP VII

192
 831
PROFIBUS is not in the data transfer condition
Cause The PROFIBUS is not in a data transfer status (data exchange) or data
transfer was interrupted.
Causes:
– The master has not yet run up, or has not yet established a connec-tion
to the slave.
– The bus addresses differ in the master configuring and slave parame-terization.
– The bus connection has been physically interrupted.
– An illegal configuration was received.
Remedy Master, check the assignment of bus addresses and bus connection.
Acknowledge / Stop not required / STOP VII

832
PROFIBUS not clock–synchronous with the master
Cause The PROFIBUS is in a data transfer status (data exchange) and has
been selected via the parameterizing frame of synchronous operation.
It could not yet be synchronized to the clock preset by the master resp.
to the master sign–of–life.
Causes:
– The master does not send an equidistant global control frame alt-hough
clock synchronism has been selected via the bus configuration.
– The master increments its sign–of–life (STW2 Bits 12–15) not in the
configured time frame Tmapc.
Remedy Check master application and bus configuration
Acknowledge / Stop not required / STOP VII

864
Parameterization error in speed controller adaptation
Cause The upper adaption speed (P1412) was parameterized with a lower
value than the lower adaption speed (P1411).
Remedy P1412 must contain a higher value than P1411.
Acknowledge / Stop not required / STOP VII

865
Invalid signal number
Cause The signal number for the analog output is not permissible.
An analog value can be output for diagnostics–, service– and optimiza-tion
tasks (terminal 75.x/15, 16.x/15, DAU1, DAU2).
Remedy Enter a valid signal number (referto the SIMODRIVE 611 universal
Description of Functions).
Acknowledge / Stop not required / STOP VII

193
 866
Parameterizing error, current controller adaption
Cause For the current controller adaption, the upper current limit (P1181) was
parameterized with a lower value than the lower current limit (P1180).
Adaption is de–activated when the parameterizing error is output.
Remedy P1181 must contain a higher value than P1180.
Acknowledge / Stop not required / STOP VII

867
Generator mode: Response voltage > shutdown thres-hold
Cause The sum of the values in P1631 + P1632 is greater than the value in P1633.
Remedy Appropriately change P1631, P1632 and P1633.
Acknowledge / Stop not required / STOP VII

868
Generator mode: Response voltage > monitoring threshold
Cause The input value for the threshold voltage (P1631) is greater than the
value in P1630.
Remedy Change the drive parameters.
Acknowledge / Stop not required / STOP VII

869
Reference point coordinate limited to modulo range
Cause The reference point coordinate is internally limited to the modulo range.
Remedy Enter a value in P0160 which lies within the modulo range (P0242).
Acknowledge / Stop not required / STOP VII

870
Jerk: jerk time is limited
Cause When calculating the jerk time T from the acceleration a and the jerk r,
the result was an excessively high jerk time, so that the time is limited internally.
The following is valid: T = a/r, where
a: Acceleration (higher value from P0103 and P0104)
r: Jerk (P0107)
Remedy – Increase jerk (P0107)
– Reduce maximum acceleration (P0103) or maximum deceleration (P0104)
Acknowledge / Stop not required / STOP VII

194
 871
Induction motor operation: drive converter frequency motor not permissible
Cause In induction motor operation (selected by P1465 < P1146), drive con-verter
frequencies of 4 or 8 kHz are permissible.
Remedy – change P1100
– cancel induction motor operation (P1465 > P1146)
Acknowledge / Stop not required / STOP VII

875
Axial deviations in fixed voltage
Cause For the axes of a drive module, an unequal fixed voltage (P1161) has been set.
As a fixed voltage <> 0 replaces the DC link voltage measured value,
but the DC link voltage is only measured once for all drives of a drive
module, the fixed voltage on all module axes must be equal, before it is
accepted.
Remedy Set the same fixed voltage (P1161) on all module axes.
Acknowledge / Stop not required / STOP VII

876
Input Ix.x assigned function >=50
Cause Only function numbers less than 50 may be used in the operating mode
”speed / torque setpoint”.
Remedy Change P0700 (operating mode) or enter a function number less than 50 in P0660,
P0661 etc.
Acknowledge / Stop not required / STOP VII

877
Output Ox.x assigned function number >= 50
Cause Only function numbers less than 50 may be used in the operating mode
”speed / torque setpoint”.
Remedy Change P0700 (operating mode) or enter a function number less than 50 in P0680,
P0681 etc.
Acknowledge / Stop not required / STOP VII

878
Input I0.x not parameterized as equivalent zero mark
Cause When entering an external signal as zero mark equivalent (P0174 = 2)
the input terminal I0.x must be assigned the ”zero mark equivalent”
function (fct. No.: 79).
Remedy Set P0660 to 79.
Acknowledge / Stop not required / STOP VII

879
Time constant deadtime, speed feedforward control (P0205:\%u) too high
Cause P0205 may not exceed two position controller cycles (s. P1009). Higher
values will be internally limited.
Remedy Reduce P0206 to a maximum of two position controller cycles. An addi-tional
delay can be parameterized via P0206.
Acknowledge / Stop not required / STOP VII

195
 881
PZD config.: illegal signal no. in P0915
Cause An undefined or illegal signal number in the current operating mode
(P0700) was identified for the process data software.
Remedy Correct P0915:17
Acknowledge / Stop not required / STOP VII

882
PZD config.: illegal double word signal no. in P0915
Cause For signals with double words (length = 32 bits), the corresponding si-gnal
identifier must be configured twice for adjacent process data. The
following subparameter must therefore also be parameterized with the
same signal number.
Remedy Correct P0915:17
Acknowledge / Stop not required / STOP VII

883
PZD config.: illegal signal no. in P0916
Cause An undefined or illegal signal number in the current operating mode
(P0700) was identified for the process data software.
Remedy Correct P0916:17
Acknowledge / Stop not required / STOP VII

884
PZD config.: illegal double word signal no. in P0916
Cause For signals with double words (length = 32 bits), the corresponding si-gnal
identifier must be configured twice for adjacent process data. The
following subparameter must therefore also be parameterized with the
same signal number.
Remedy Correct P0916:17
Acknowledge / Stop not required / STOP VII

885
P1261 greater than 100.0 % not permissible
Cause P1261 greater than 100.0 % is not permissible for permanent–magnet
synchronous motors with field weakening (PE spindle, P1015 = 1). It is
internally limited to 100.0 %.
Remedy Set P1261 to max. 100.0 %.
Acknowledge / Stop not required / STOP VII

196