3ERROR MESSAGES AND TROUBLE-

SHOOTING

3.1 Behavior in case of errors

Basic information

DANGER!
Risk of fatal injury from electrical current!
When this electrical unit is operated, certain parts of the unit are of necessity at a haz-
ardous voltage.
Therefore:
m Pay heed to areas on the device that could be dangerous.

WARNING!
Risk of injury due to improper troubleshooting!
Therefore:
m Only qualified personnel may work on this unit!
m Personnel that work with the b maXX device must be trained in the safety regula-
tions and the handling of the device, and be familiar with the correct operation of
it. In particular, reacting to error indications and conditions requires that the oper-
ator must have special knowledge.

Parameter manual b maXX BM5000 49

Document No.: 5.09022.17 of 978
3.2 Monitoring functions

3.2 Monitoring functions

According to the type of device not each monitoring is appropriate. Please refer to the as-
sociated monitoring description in ZMonitoring function - explanations– from page 52, if
the monitoring is relevant for your device.

Adjustable threshold

Adjustable reaction

Reaction
Warning

Error
Monitoring function Warning/error

Mains voltage 6) Mains undervoltage X X - - IS

Mains overvoltage X X - - IS
6)
Phase monitoring Phase failure X X - - IS
Mains failure X X X - IS2)
Ground fault 1) Fault current to ground - X - - IS
Overcurrent Overcurrent motor - X - - IS
DC link DC link overvoltage - X - - IS
DC link relative undervoltage X - - - -
Overload monitoring Peak current not possible at this X - - - -
time
Heat sink temperature Temperature > threshold 1 X - X - -
Temperature > switch-off threshold - X - - IS
Temperature of device inte- Temperature > threshold 1 X - X - -
rior
Temperature > switch-off threshold - X - - IS
1) IS: Pulse inhibit
Not available with BM51xx, BM541X and BM542X
QS: Quick stop
2)
Pulse inhibit carried out after a specifiable interval. X: Implemented
3)
Only if KTY encoder used -: Not possible
4)
Adjustable
5)
Adjustable
6)
Not provided for power modules

50 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3

Adjustable threshold

Adjustable reaction

Reaction
Warning

Error
Monitoring function Warning/error

Motor temperature I2t threshold exceeded - X - - IS

3)
Threshold 1 exceeded X - X - -
Threshold 2 exceeded 3) X - X - -
Encoder short circuit and/or tem- - X - - -
perature < -30 °C 3)
Encoder not connected and/or tem- - X - - -
perature > 250 °C 3)
Maximum temperature exceeded 3) - X X - IS
Position controller Dynamic position error - X X - QS
Static position error - X X - QS
4)
Controller synchronization Controller not synchronous with X X X X
external signal
Encoder 1 Cable break - X - - IS
Cable break (SIN2 + COS2) - X - - IS
Excessive speed - X X - IS
Encoder 2 Cable break - X - - IS
Cable break (SIN2 + COS2) - X - - IS
Excessive revolutional speed - X X - IS
Ramp-up option module Error during module initialization - X X - IS
Cyclical set value transmis- Time-out during transmission - X X X 5)
sion
Safety technology Switch off by Safety technology - X - - IS
(Safe Torque Off)
Safety technology Warning switch off by Safety tech- X - - - -
nology (Safe Torque Off)
Blockage monitoring Drive blocked - X X - IS
1) IS: Pulse inhibit
Not available with BM51xx, BM541X and BM542X
QS: Quick stop
2)
Pulse inhibit carried out after a specifiable interval. X: Implemented
3)
Only if KTY encoder used -: Not possible
4)
Adjustable
5)
Adjustable
6) Not provided for power modules

Parameter manual b maXX BM5000 51

Document No.: 5.09022.17 of 978
3.2 Monitoring functions

3.2.1 Monitoring function - explanations

Mains voltage - not for axis units

This monitoring function verifies whether the mains voltage has a value within the set volt-
age range. If the value is lower, then the warning "Mains undervoltage" is reported. If the
value is higher, then the warning "Mains overvoltage" is reported.
Active Mains Rectifier Unit:
This monitoring function checks, if at the active mains rectifier unit the actual value of the
measured mains voltage is greater than the connection

U DC_min (P129.42) – 10 V
-------------------------------------------------------------- and lower than 530 V.
2

In addition to these fixed limits, which mark the maximum working range of the active
mains rectifier unit, the warning thresholds can be defined over the parameters Z141.41–
and Z141.42–. As soon as the mains voltage falls below or exceeds these thresholds a
warning is generated. By changing the reaction referring to the warnings 2026 and 2027
to "Pulse Inhibit", the actual mains voltage range in which the active mains rectifier unit is
operated, can be limited.

Phase monitoring - not for axis units

This monitoring function checks the mains voltage of the three outer conductors. If one
outer conductor is missing, then the warning "Phase failure" is reported after a period of
> 4 s.
If all three outer conductors are missing, then the warning "Mains failure" is reported to
the controller after a period of > 4 s. After the preset time lag has been reached (based
on a mains failure monitoring parameter), the controller generates the error message
"Mains failure".

NOTE!
If no electrical filter is used during operation, mains and phase failures are detected
within 100 ms. If the device is operated with an electrical filter, the mains and phase
failures are detected after a max. of 5 s. Depending on the load condition, the failure
can also be detected much earlier, however.

This applies to active mains rectifier units (BM51xx):

As soon as the device recognizes a phase failure or a mains failure, it goes into the error
status.
The settable delay time applies for mono units only and is nonexistent at active mains rec-
tifier units. The active mains rectifier unit messages an error promptly.
In consequence of the used mains filter at the active mains rectifier unit, the active mains
rectifier unit cannot recognize the phase failure in the enabled unloaded status. There-
fore, the user is enabled to inject a reactive current into the mains in the unloaded enabled
status. Thus, the capacities in the mains filter are loaded and the phase failure is recog-
nized. According to the conditions of the mains, the necessary reactive current for the de-
tection of phase failure differ.

52 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Ground fault This monitoring function checks whether there is a short circuit between at least one mo-
tor terminal and ground. If a short circuit is detected, a pulse inhibit occurs immediately.
This monitoring function does not exist for BM541X, BM542X and BM51XX (active mains
rectifier unit).

Overcurrent This monitoring function checks whether the motor current is larger than the 1.3 times the
peak output current. This aids "disaster prevention" in case of a short circuit on the output
side.
At the active mains rectifier unit the mains current is monitored and not the motor current.

DC link This monitoring function checks the voltage in the DC link. If the voltage drops below an
internally set value (approx. 50 V under the specified value), the controller reports "DC
link undervoltage" and a warning is signaled. If the voltage rises above an internally set
value (approx. 820 V), the controller reports the error "DC link overvoltage" and a pulse
inhibit takes place immediately.
Active Mains Rectifier Unit:
This monitoring function checks the voltage in the DC link.
If the DC link voltage is smaller than the measured mains peak voltage in the enabled sta-
tus, the active mains rectifier unit is not able to maintain its defined DC link voltage any-
more and generates the error 2009 „Undervoltage in the DC link" and reacts with a pulse
inhibit. If the DC link voltage is greater than the set value of 835 V of the power unit’s
specifications, then the active mains rectifier unit generates the error 2008 „Overvoltage
in the DC link" and reacts with a pulse inhibit.

Overload monitor- This monitoring function checks the present load as to whether the power unit can output
ing the peak current at this time. If the peak current is not possible, then the message "PU
monitoring approached; max. torque current was limited" (warning 206) is reported.

Temperature of This monitoring function checks the temperature in the interior of the device.
device interior m If the temperature is higher than the warning threshold, then the controller signals a
warning.
m If the temperature is too high, then a pulse inhibit takes place immediately.

Heat sink tem- This monitoring function checks the temperature of the heat sink.
perature m If the temperature is higher than the warning threshold, then the controller signals a
warning.
m If the temperature is too high, then a pulse inhibit takes place immediately.

Motor temperature This monitoring function checks the temperature of motor. If the I2t-threshold is exceeded,
then the error message "I2t overload" is reported by the controller.

Only for If the set temperature threshold 1 is exceeded, then the warning "Temperature threshold
KTY84 encoder 1 exceeded" is signaled by the controller.
If the set temperature threshold 2 is exceeded, then the warning "Temperature threshold
2 exceeded" is signaled by the controller.
The KTY84 encoder has a minimum measured value of approx. -30 °C. If this tempera-
ture is gone under, or if a short circuit occurs at the encoder, then the error message
"Temperature probe short circuit" is reported.
The KTY84 encoder has a minimum measured value of approx. +250 °C. If this tempera-
ture is exceeded, or if the encoder is not connected, then the error message "Temperature
probe not connected" is reported by the controller.

For all If the threshold set (type-specific) in the temperature switch or in the MSKL encoder is
encoders exceeded, then the error message "Overheating" is reported by the controller and a pulse
inhibit takes place immediately.

Parameter manual b maXX BM5000 53

Document No.: 5.09022.17 of 978
3.2 Monitoring functions

At the active mains rectifier unit there is no monitoring.

Position controller This monitoring function checks the position error limit statically/dynamically. If the cur-
rent position error is statically/dynamically larger than the set position error limit, then the
error message "Static position error" or, respectively, "Dynamic position error" is reported.
After the monitoring period (position error period) has ended, an additional error message
is reported and a pulse inhibit takes place immediately.
At the active mains rectifier unit there is no monitoring.

Safety technology This monitoring function checks whether the safety function Safe Torque Off (STO) is ac-
tivated. If the drive is enabled at the moment of triggering the safety function, an error
message is generated. If the drive is not enabled, a warning is displayed.
At the active mains rectifier unit there is no monitoring.

Blockage monitor- This monitoring function checks the motor speed and the motor current.
ing If the "Blockage monitoring interval" time frame meets the following two conditions, then
the error message/warning "Drive blocked" is signaled by the controller and a pulse inhibit
takes place immediately.
m Motor speed = 0
m The motor current output by the device is the same as the set motor limiting current
(current limit).
At the active mains rectifier unit there is no monitoring.

54 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
3.3 Error detection

The illumination of the red LEDs H14 (axis 1) and H24 (axis 2) on the front of the housing
signals the occurrence of a error status.

A max. of 3 LEDs Essentially, the lowest red LEDs H14 and H24 "Error" are of significance here.
are illuminated.

NOTE!
In case of warnings or errors without error reactions, the LEDs H14 or H24 blink "Er-
ror". Only error messages with error reaction will be signalized by constant lighting
up.

3.4 Error handling

Error messages, which can also be considered error lists, are the basis of the error han-
dling.

NOTE!
The device is shipped with predefined error reactions. With regard to the error mes-
sages identified with "depending on the setting" in the "Reaction" column, the de-
vice's error reaction can be adjusted. Errors that, due to safety reasons, have an
immediate pulse inhibit as a consequence, may not be changed.

3.4.1 Error reset

If the red error LED is illuminated, at least one error is present.

Error reset cause all error messages to be reset. Individual resetting of errors is not pos-
sible. A reset causes deletion of the errors, if deletion was possible on account of the error
circumstances.
There are two methods of resetting an error:
m By means of write access to the control word
m Via a digital input
For further information on the subject of error reset, see "Instruction Manual b maXX
5000".

Parameter manual b maXX BM5000 55

Document No.: 5.09022.17 of 978
3.5 Error descriptions

3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
100 No Heap memory available No Heap memory available No response
101 Stack monitoring: stack consumption The stack consumption has reached error threshold. A safe opera- Pulse block
has reached error threshold. tion is no longer possible. The additional info 1 of the error message
shows the task number in which the stack consumption is too large.
102 Error during indirect function access Error during indirect function access Pulse block
103 Real time load critical The calculation time load of the real time is too high. No response
114 Error division by zero Division by zero occurred in a floating point division. No response
115 Invalid value for floating point operation An invalid floating point value (e.g. NaN: not a number) was No response
detected in a floating point operation.
116 Timeout of I2C Bus Read/Write A timeout error occurred in the I2C Bus. The serial I2C EEPROM is No response
Eeprom connected to the DSP via the I2C Bus.
m Effect:
The Board ID and production data are stored in the I2C EEPROM.
The error may lead to an incorrect board configuration.
118 Error while reading or writing the hard- An error has occurred while reading or writing the hardware board Pulse block
ware board data data.
119 Drive no longer synchronous with field- The error is enabled, if the synchronization signal of the fieldbus is Pulse block
bus more than once out of the synchronous window after a successful
synchronization.
121 Measured RT fieldbus cycle too large The error is triggered when the fieldbus cycle that is measured in the Pulse block
FPGA is greater than the parameterized set value fieldbus cycle.
122 Measured fieldbus cycle too small The fieldbus cycle that is measured in the FPGA is smaller than the Pulse block
parameterized set value fieldbus cycle
123 RT fieldbus jitter greater than the syn- The error is triggered when the jitter of the fieldbus interrupt that is Pulse block
chronizer window measured in the FPGA is greater than the parameterized synchro-
nizer window.
124 PWM Counter 1 not synchronous with The error is triggered when the PWM counter of Drive 1 is no longer Pulse block
the DSP time dial system synchronous with the time dial system of the DSP.
126 RT fieldbus run time error The error is triggered when a error occurs in the chronological order Pulse block
of data transfer in the participating modules of the fieldbus system. It
is thereby assumed that set values are received in intervals via field-
bus and transmitted to the DSP while the DSP returns DSP actual
values to the fieldbus. When run times develop during the value
transfer that are too high, a error will be indicated. A more detailed
analysis can then be carried out through the diagnostic parameters
that are provided.
127 Timeout fieldbus interrupt The error is triggered when more than 3 fieldbus interrupts have Pulse block
failed. The synchronization will be initiated again.
128 Unknown identification System FPGA Identification of system FPGA is unknown in the DSP Pulse block
129 System FPGA version does not fit to System FPGA version does not fit to DSP software Pulse block
DSP software
130 The fallback version was booted by The fallback version was booted by Bootloader 1 Pulse block
Bootloader 1
131 The communication firmware has The communication firmware has booted the fallback version Pulse block
booted the fallback version
132 The firmware has booted the fallback The firmware has booted the fallback version Pulse block
version

56 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
133 The FPGA has booted the fallback ver- The FPGA has booted the fallback version Pulse block
sion
134 System FPGA and option module type The system FPGA is incompatible with the connected option mod- No response
are not compatible ule. An error occurs during the booting procedure.

n Remedy
Load the appropriate system FPGA
135 Error while programming to flash Error while programming to flash No response
137 Time dial computation time overrun It is being monitored whether the time dials exceed the run time of Pulse block
MAX_ZS_TIME_LIMIT_IN_TICK = 60 µs too frequently.

Monitoring in remaining time, threshold: per second = 1000*16 ZS,

10% of that: 1600 overruns per second

138 Cycle2 duration too long Cycle2 duration more than 1% too long in relation to one second. Pulse block
The CPU is overloaded, computation too great.
139 Drive not synchronous with RT fieldbus This warning message is issued when the synchronization of the No response
(Warning) drive with the fieldbus is activated (Parameter Z156.1–), but it has
not yet occurred (Parameter Z156.2–). The message occurs regard-
less of the fieldbus status (operational / not operational) and will be
deleted when the drive is synchronous.
Required for better error diagnosis because the drive cannot be
enabled if synchronicity is required but has not been achieved.
140 General firmware error, e.g. switch General firmware error, e.g. switch Pulse block
141 Operating system error Error in context with the operating system Pulse block
142 Method not implemented Method not implemented Pulse block
144 invalid file type invalid file type No response
145 File already open File already open No response
146 Maximum size of file reached (writing Maximum size of file reached (writing reading) No response
reading)
147 File not opened File not opened No response
148 File not opened for this access (Read File not opened for this access (Read Write access) No response
Write access)
149 Indicated ID wrong Indicated ID wrong No response
150 Indicated index does not exist (too Indicated index does not exist (too large) No response
large)
151 Parameter element cannot be written Parameter element cannot be written No response
152 External access not permitted External access not permitted No response
153 Value less minimum value Value less minimum value No response
154 Value greater maximum value Value greater maximum value No response
155 Value error Value error No response
156 Value cannot be changed due to the Value cannot be changed due to the operating condition No response
operating condition
157 wrong axis index wrong axis index No response
158 Format information wrong Format information wrong No response
159 Error while reading system data Error while reading system data from flash No response
168 No write permission for the actual Parameter cannot be changed due to the access protection. No
access level write permission for the actual access level.

Parameter manual b maXX BM5000 57

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
169 Application error for testing the error Application error for testing the error responses.
responses
The error can be triggered uniquely as follows:

1) Write the value 5 to P100.1 Info manager error command

2) Write the error number 169 to P100.6 Info manager launch

error

The error can be used to test the different error responses, e.g. pull-
back, without triggering a „true“ error.
170 Firmware for communication processor Firmware for communication processor could not be downloaded Pulse block
could not be downloaded
The error is messaged, if the firmware could not be downloaded to
the communication processor at the boot sequence.

Either both firmware files (actual and fallback) of the communication

firmware are faulty or nonexistent (error info1 = 0) or an error has
occurred at the file download to the communication processor (error
info1 = 1).
171 Wrong power unit serial number The serial number of the power unit is unknown Pulse block
172 Lead drive error Error within communication between two drives. The coupled drive No response
reported an error. The receiver drive reports error 172, if a new error
reaction is invoked and the error reaction is none of "no reaction" nor
"no error, no reaction". Then the drive reacts with the received error
reaction. The entry in the error reaction table is not used, since the
received error reaction will be used.
173 PLC Translation error Error when translating the PLC project No response
174 PLC runtime error PLC runtime error No response
175 Application error 1 Freely definable application error 1 No response
176 Application error 2 Freely definable application error 2 No response
177 Application error 3 Freely definable application error 3 No response
178 Application error 4 Freely definable application error 4 No response
179 Application error 5 Freely definable application error 5 No response
181 Value can be changed in inhibit state The new parameter value is not accepted No response
only
201 Exceeded limit pos. speed error value Speed error value > Maximum positive speed error value (parameter No response
Z6.7–)
202 Exceeded limit neg. speed error value Speed error value < Maximum negative speed error value (parame- No response
ter Z6.8–)
203 Positive overspeed limit exceeded x2 speed actual value > Positive overspeed limit (parameter Z6.5–) Pulse block
204 Negative overspeed limit exceeded x2 speed actual value < Neg. overspeed limit (parameter Z6.6–) Pulse block
205 Motor i2t overload The current i2t value (Z6.28–) has exceeded the limit value for the Pulse block
i2t model (Z6.29–).
206 LT monitoring approached; max. torque I*t monitoring of power unit is operating; the maximum available No response
current was limited torque current is limited.
Details see ZOverload monitoring of the power unit– on page 894.
207 Exceeded position error limit 1 Error occurs when position error limit 1 is exceeded. Pulse block
208 Exceeded position error limit 2 The error occurs when position error limit 2 is exceeded Pulse block

58 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
209 Blockage monitoring: Blocking time 1 The drive is blocked longer than the set Blockade Time Limit 1 No response
exceeded (Parameter 6.21).
The warning will be deleted automatically if the condition for blocking
is no longer met.
210 Blockage monitoring: Blocking time 2 The drive is blocked longer than the set Blockade Time Limit 2 Pulse block
exceeded (Parameter 6.22).
211 Error While Monitoring the Field Angle Error while monitoring the field angle is greater than 45° Pulse block
212 Parameterization allows exceeding of The set value for the Z107.26– max. speed mech. can be exceeded No response
the maximum speed of the motor because of the existing parameter settings. If Z107.26– = 0 rpm the
check of the parameter does not proceed.
m Cause:
a) Parameter Z107.26– max. speed mech. is set wrong.
b) The ramp function generator is used in operating modes -3 and
2. There Z110.13– Standardization Output Value is used for stan-
dardization. If Z110.13– is greater than Z107.26– the error is set
at drive enabling. If the error is ignored the speed set value
already can exceed the maximum speed mechanical.
c) The Overspeed Limits in parameter Z6.5– and Z6.6– are set
too large. The check of the actual speed protects the motor insuf-
ficiently.
n Remedy:
a) Enter a valid value in Z107.26–.
b) Adjust the standardization for the ramp function generator
(Z110.13–  Z107.26–)
c) Adjust the Overspeed Limits (|Limit| Z107.26–)
213 Position difference greater than thresh- The difference of the position in gantry mode is greater than the vari- No response
old in gantry mode able threshold.
214 Gantry mode: current difference In gantry mode the current difference is greater than the variable No response
greater than threshold threshold
215 Controller fan not working The fan of the controller board is switched on but the controller gets No response
no feedback from the tachometer. Either the fan is not working or the
tachometer signal is broken.
216 Power unit monitoring responded; Power unit monitoring (temperature model) responded; PWM fre- No response
PWM frequency reduced quency reduced (halved)
217 Dual-Use: electrical frequency to high This device is a dual-use-device and the electrical frequency is to Pulse block
high. The maximum value is 600 Hz Output frequency.
218 Peak current of power unit is reduced The power unit peak current is reduced to protect the unit from dam- No response
age
219 Warning motor 12t overload Warning: motor i²t overload No response
220 Power unit overload during operation Power unit overload. In the operation mode, voltage setting, the cur- Pulse block
mode voltage setting rent cannot be limited. The reaction to the overload is impulse inhibit
221 Exceedance warning threshold of real Only für single Phase Units (BM3300) with DC link supply from No response
power mains. Here the real power has to be limited, otherwise the DC link
will not get enough energy from mains.
222 Exceedance error threshold of real Only for single Phase Units (Bm3300) with DC link supply from Pulse block
power limitation mains. Here the real power has to be limited, otherwise the DC link
will not get enough energy from mains.
223 Fan failure One or several fans failed No response
231 Dual-use: electrical frequency too high The output frequency is limited to 600 Hz corresponding to the Pulse block
export restrictions. A dual-use device is necessary if higher frequen-
cies are required.
400 Amplitude of the encoder signal too Encoder monitoring has detected an amplitude that is too small at Pulse block
small Sin2+cos2 monitoring. Either the encoder has a problem or the mon-
itoring threshold is set too great.

Parameter manual b maXX BM5000 59

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
401 Amplitude of the encoder signal too Encoder monitoring has detected an amplitude that is too great at Pulse block
great Sin2+cos2.
402 Error while initializing the position Error while initializing the position (the analogous signals do not Pulse block
through Sin/Cos signals. agree with the position which was digital read out).
403 Encoder monitoring: Overspeed due to Sector error occurred while the encoder evaluation, which means Pulse block
sector error the calculated speed is too great
404 Signal monitoring at square-wave The signal monitoring of a square-wave incremental encoder has Pulse block
incremental encoder recognized an error.
405 CRC error in received data CRC error in received data from EnDat 2.1, HIPERFACE DSL or Pulse block
SSI
406 Lighting failure EnDat interface The error is triggered by module EnDat interface when the abso- Pulse block

lute encoder reports a lighting failure via the EnDat interface. With-
out lighting, the optical sampling system of the encoder no longer
works and no valid position information can be calculated anymore.
m Cause:
Cause for a lighting failure in the encoder may be contamination,
aging, or excess temperature.
n Remedy:
Replace encoder.
407 Signal amplitude too small EnDat The error is triggered by the module EnDat interface when the Pulse block

interface absolute encoder reports via the EnDat interface that the ampli-
tude of the Sine/Cosine signals is too small. Sine/Cosine signals that
are too small can lead to a position loss.
m Cause:
Cause for sine/cosine signals that are too small may be contami-
nation, aging, or excess temperature.
n Remedy:
Replace encoder.
 
408 Position error EnDat interface The error is triggered by the module EnDat interface when an error Pulse block
occurred during the calculation of the absolute position in the abso-
lute encoder. An incorrect absolute position can lead to miscommu-
nication for synchronous motors.
m Cause:
Cause for an incorrect position calculation may be contamination,
aging, or excess temperature.
n Remedy:
Replace encoder.
 
409 Overvoltage EnDat interface The error is triggered by the module EnDat interface when the Pulse block
absolute absolute encoder reports via the EnDat interface that the
supply voltage applied to the encoder is too high.
m Cause:
Cause for supply voltage applied to the encoder may be a defec-
tive Sense line (Pin12 on X24/X25, Sub-D15). In this case, the
supply voltage may be switched to 8 V (Stegmann encoder).
n Remedy:
Check encoder cable
m Cause:
Cause can also be a defect in the encoder hardware.
n Remedy:
Replace encoder.

60 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
410 Undervoltage EnDat interface The error is triggered by the module EnDat interface when the Pulse block

absolute encoder reports via the EnDat interface that the supply
voltage is too low.
m Cause:
Cause for a encoder supply voltage that is too low may be cor-
roded contacts
n Remedy:
Check encoder cable
m Cause:
Cause can also be a defect in the encoder hardware.
n Remedy:
Replace encoder.
 
411 Overcurrent EnDat interface The error is triggered by the module EnDat interface when the Pulse block

absolute encoder reports via the EnDat interface that the encoder
supply current is too high.

m Cause:
Cause for a encoder supply current that is too high may be an
internal short circuit.
n Remedy:
Replace encoder.
 
412 Battery error EnDat interface The error is triggered by the module EnDat interface when the Mul- Pulse block

titurn absolute encoder reports via the EnDat interface that the
supply battery must be replaced. The battery voltage provides posi-
tion information for the Multiturn encoder in the memory when the
controller is switched off and no supply voltage is provided for the
encoder.

m Cause:
Cause for a battery replacement in the Multiturn encoder may be
a modification of the battery.
n Remedy:
Replace encoder.

413 Alarm Bit set EnDat interface has set alarm Bit (collective message). Pulse block
414 Error during reception: Address mirror- Error during reception: Address mirroring returns an error Pulse block
ing returns an error
415 Variance of encoder signals exceeds The variance of encoder signals exceeds adjustable limit Pulse block
adjustable limit
416 Touch probe: trigger zero pulse without The touch probe measurement is configured to trigger by a zero No response
incremental encoder pulse, but the used encoder does not provide a zero pulse.

m Effect:
Value is not accepted
Response parameterizable
n Acknowledgment:
No particular action

417 Warning Collision of frequency EnDat encoder has messaged warning collision of frequency, see No response
Z137.38–; preventative maintenance is recommended.

418 Warning Excess temperature EnDat encoder has messaged warning excess temperature; see No response
Z137.38– and error number 407; preventative maintenance is rec-
ommended.

419 Warning Lighting controller reserve EnDat encoder has messaged warning „Lighting controller reserve No response
reached reached“; see Z137.38– and error number 406; preventative main-
tenance is recommended in order to avoid lighting failure.

Parameter manual b maXX BM5000 61

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
420 Warning Battery load to small EnDat encoder has messaged warning „Battery load to small“; see No response
Z137.38– and error number 412; preventative battery change is rec-
ommended.

421 Warning Reference point EnDat encoder has messaged warning Reference point; see No response
Z137.38–; preventative maintenance is recommended.
422 Parity errors in received data Parity errors in the received data of SSI Pulse block
423 Received data invalid Received data of SSI encoder are invalid. Pulse block
424 Encoder emulation: Error configuration Configuration error, further details in status Z172.2– or Z172.11–: Adjustable
m Bit 10:
IEE option module is not available or system FPGA is not com-
patible with option module type
n Remedy
Plug a functional IEE module or load the appropriate system
FPGA
m Bit 11:
Start after zero pulse selected and encoder is not an incremen-
tal encoder
425 Encoder emulation: Run time error Run time error, further details in status Z172.2– or Z172.11–: Adjustable
Run time:
m Bit 8: Output frequency is limited
IEE module cannot sent the required number of pulses.
Cause:
m Product of speed set value and number of pulses is too great
m Bit 9: Error in set value source
IEE switches off, because an error was occurred in the set
value source
426 SSI encoder emulation: Error configu- Error in configuration of SSI encoder emulation, for details see sta- Adjustable
ration tus Z173.2–
m Bit 12: SIE option module not placed or system FPGA is not
compatible with option module type

n Remedy:
Plug a functional SIE module or load the appropriate system
FPGA
427 SSI encoder emulation: run-time error Run-time error, for details see status Z173.2– Adjustable
m Bit 14: Timeout
Missing external clock signal of SSI master

n Remedy:
Check the SSI encoder input and the connection cable.
428 Encoder monitoring: difference HIPERFACE encoders: The absolute position is read via the serial Pulse block
between analog and digital position too HIPERFACE interface and compared to the analog position calcu-
high lated from the analog SinCos signals by the FPGA. If the position
errors absolute value (Z14.22–) is higher than the defined error
threshold (Z14.21–) this error is set.
429 EnDat baud rate too low for digital posi- If the calculation and transmission of the digital position of the EnDat No response
tion transmission encoder lasts longer than 61.5 µs the error is displayed. The calcula-
tion of the transmission time is the following:
Duration = Mode command transmission + tCal (encoder type plate)
+ positioning transmission
430 Invalid encoder type The set encoder type (Z106.1–) is not permitted because it is not No response
supported by the installed FPGA.

62 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
431 Transmitting error between the DSL Failure in the HIPERFACE DSL encoder due to the EMC or shock/ Adjustable
master/slave vibration
Position is estimated as long as the error is applied. If the error
remains longer than 5 speed control cycles in series the error 405 is
enabled.
500 New set value not transferred to the The new set value was not transferred to the controller (position or No response
controller soon enough speed controller) through the set value manager for a minimum of
three times soon enough. Extrapolation is carried out up to the come
in of the next set value.

m Cause:
A possible cause could be too much consumed time for computa-
tion of activated functions.
n Remedy:
Check if unused functions were accidentally activated. Example:
Analogous outputs or RT oscilloscope are activated prior to initial
operation.
501 Current controller cycle time > RT0- The time slice RT0 includes the speed and position controller, the Pulse block
Cycle time encoder evaluation and the motor control. The current controller
cycle time is defined by the setting of the PWM frequency (parame-
ter Z130.15–).

n Remedy:
The error can be reset as soon as the PWM frequency (parameter
Z130.15–) of the reporting axis or the RT0-Cycle time (parameter
Z1.8–) will be adjusted to a valid combination
503 Torque coupling improper drive operat- Operating mode must be Speed control (-3) or Speed setting (2).
ing mode In the other operating modes the error will be initiated, if it will be
tried to activate the torque coupling
504 Torque coupling configuration error Configuration error:
m Device internal cross communication at Mono unit / single axis
unit impossible
505 Fieldbus cycle time < RT0-Cycle time The cycle time of the fieldbus task (Z1.10–) is set via the fieldbus Pulse block
cycle time (Z131.18–). The RT0-Cycle time is set in Z1.8–.

n Remedy:
The error can be reset as soon as the fieldbus cycle time is
greater or equal to the RT0-Cycle time.
600 Terminal position search Inject. Plau- In step 1 the injection procedure runs successively twice or the pole Pulse block
sib. Step 1 position is determined twice. If both results show a major difference
(or about 30°), this bit is set.
m Cause:
Carrier current Id too low or amplification factor of the tracking
controller is too little
601 Terminal position search Inject. Plau- In step 2 the carrier current is too low, in order to create the required Pulse block
sib. Step 2 saturation so that the content of the 2nd harmonic I2 (displayed in
parameter Z133.9– 2nd Harmonic Rate) does not reach the level
which is indicated in parameter Z133.10– 2nd Harmonic Min.Rate.
602 Overcurrent with notch position search Overcurrent with notch position search Method 2 (using injection) Pulse block
Method 2

Parameter manual b maXX BM5000 63

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
702 Rotor position at synchronous machine The rotor position of the synchronous drive is unknown. Either the Pulse block
is unknown rotor position offset or the absolute position could not be read from
the encoder or the synchronous drive is used with a incremental
encoder and a rotor position identification has not been executed
yet.
The error is also set if the encoder is switched off but the motor con-
figuration needs an encoder.
Reset of the error is possible. The error is set again if the cause of
the error has not been corrected.

m Cause:
For some encoders, the absolute position can partially no longer
be read out due to contamination of the code dial.
n Remedy:
Replace encoder.
m Cause:
Encoder cable defective
n Remedy:
Checking of encoder cable, and replacements if applicable
m Cause:
Encoder defective.
n Remedy:
Replace encoder and carry out new notch angle run!
703 Error writing rotor position offset to An error occurred while writing the rotor position offset into the Pulse block
encoder encoder (e.g. timeout, data field not writable, encoder processes
other commands).
704 For synchronous machine: encoder No encoder transmission was supported for synchronous machine. Pulse block
transmission not permitted A transmission factor not equal to 1:1 was read from the motor type
plate.
705 Motor temperature for characteristic The motor temperature that is measured via the KTY encoder is No response
curve of ASM slip invalid, lower than - monitored for asynchronous motors due to slip characteristic curves
50°C or higher than 200°C If the temperature is lower than -50°C or higher than 200°C, the tem-
perature values are assumed to be invalid and the error will be trig-
gered.

m Cause:
The KTY motor temperature encoder was incorrectly connected
or not at all connected.
n Remedy through:
n Check connections and cable of KTY motor temperature
encoder.
n Monitoring may be deactivated for intended operation without
temperature encoder.
m Cause:
KTY motor temperature encoder defective.
n Remedy through:
n A defective KTY motor temperature encoder generally requires
motor replacement.
n Monitoring may be deactivated for intended operation without
temperature encoder.
m Cause:
Evaluation switch of the KTY motor temperature encoder in the
drive controller is defective.
n Remedy through:
n Drive controller replacement.
n Monitoring may be deactivated for intended operation without
temperature encoder.
709 Motor excess temperature The measured temperature is higher than permitted Pulse block

64 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
710 Motor Temperature Threshold1 Motor temperature warning threshold 1 exceeded No response
exceeded
711 Motor Temperature Threshold 2 Motor temperature warning threshold 2 exceeded No response
exceeded
712 Short circuit on temperature sensor Short circuit on temperature encoder Pulse block
713 Temperature sensor is not connected Temperature encoder is not connected Pulse block
714 Motor excess temperature PTC resistor Motor excess temperature recognized by temperature switch Pulse block
716 Notch position not found An error occurred while identifying the rotor position of the synchro- Pulse block
nous machine. The rotor position has not been identified.
717 Excess voltage occurred during resis- Error during identification of motor parameters. The maximum per- Pulse block
tance measurement mitted phase voltage (= 80 V) was exceeded during the resistance
measurement.
m Possible cause:
Incorrect motor nominal current setting in Parameter 107.09.
718 Voltage limit accessed during resis- Error during identification of motor parameters. The voltage limit was Pulse block
tance measurement reached during the resistance measurement.
m Possible causes:
Incorrect motor nominal current setting in Parameter 107.09.
- Voltage insufficient.
719 Timeout during motor identification Error during identification of motor parameters. The maximum per- No response
mitted phase voltage (= 80 V) was exceeded during the resistance
measurement.
m Possible cause:
Incorrect motor nominal current setting in Parameter 107.09.
n Effect:
Output voltage set to ZERO to protect the motor. An additional
drive block occurs with standard error response.

Resetting after error elimination:

Error reset is possible. Timeout (45 seconds) with R measurement
with motor parameter identification, such as due to error during cur-
rent / voltage measurement or normalization or limit value.
720 An encoder is not activated An encoder is required for this operating mode Pulse block
721 Special case Kt = 0 Special case Kt = 0, no correct operation possible, isq set value is No response
forced to 0.
800 Special function already used for Special function such as hardware limit switch 1 was already used No response
another digital input for another digital input
801 Digital output already used This digital output is already used by another special function or by No response
another assignment.
802 OM power steering pump current Power steering pump I/O module error overcurrent. Level 22 mA. No response
> 22mA
803 OM power steering pump current OM power steering pump undercurrent. Level 3.6 mA. No response
< 3.6 mA
804 OM power steering pump analog input Power steering pump I/O: analog input cannot be activated because No response
not placed not placed
805 OM power steering pump analog out- Power steering pump can not be activated because it is not placed. No response
put not placed
806 OM power steering pump error configu- The system FPGA is not compatible with the power steering pump No response
ration I/O module

Parameter manual b maXX BM5000 65

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
900 Reference run required and not carried Reference run required and not yet carried out No response
out
The start of the active operating mode requires a one-time reference
run (homing) after activating the controller.

Currently, only the operating mode Position Target Specification (BA

= 1) requires homing. This requirement can be activated in the mode
for the position target specification.
901 Problem during homing A homing error has occurred. Possible error causes: No response
m An invalid homing mode was selected.
m Homing isn't possible because of limit switch and reference switch
status.
m A maximum distance was set for the zero pulse search and the
zero pulse was not detected within the specified distance.
902 Monitoring the block for positive direc- Monitoring the block for positive direction: No response
tion
Monitoring has detected a positioning attempt in positive direction
903 Monitoring the block for negative direc- Monitoring the block for negative direction: No response
tion
Block for negative direction has detected a positioning attempt in
negative direction.
904 Positioning time monitoring reports Positioning time monitoring reports Timeout No response
Timeout
Monitoring will become active as soon as the position set value is
equal to the target position at the end of positioning.

If the actual position is not located in the positioning window (Param-

eter 121.5) after the time set in Parameter 118.18 has expired, the
error will be triggered.
905 Error limit switch monitoring This error occurs under the following conditions: No response

Case a: Both hardware limit switches set simultaneously.

Case b: Positiver software limit switch and negative hardware limit

switch active simultaneously.

Case c: Negative software limit switch and positive hardware limit

switch active simultaneously.

Possible causes:
- Software limit switch set incorrectly, such as values for positive and
negative limit switches are reversed.
- Hardware limit switches are wired incorrectly.
- Errors on the cable for hardware limit switches.
906 Negative hardware limit switch overrun Negative hardware limit switch overrun No response
907 Positive hardware limit switch overrun Positive hardware limit switch overrun No response
908 Negative software limit switch overrun Operating mode Position Target Specification: No response
Target position to be approached is smaller than the negative soft-
ware limit switch.

Other operating modes:

Position set value is less than the negative software limit switch.

66 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
909 Positive software limit switch overrun Operating mode Position Target Specification: No response
Target position to be approached is greater than the positive soft-
ware limit switch.

Other operating modes:

Position set value is greater than the positive software limit switch.
910 Overspeed detected at set value input Overspeed detected at set value input: Quick Stop

In the operating mode speed control or speed setting a set value

was written exceeding the maximum interpolating speed set value of
the set value manager. Refer to Z110.3– Output for details.

Set values were written in the operating mode Position Control (-4)
that either exceed the set speed limit (Parameter Z121.11–), the
allowed maximum speed of the motor (Parameter Z107.26–) or
max. interpolatable set value speed.
The error is displayed and the set value speed is limited (Z121.11–
and Z107.26– respectively) at error response „No response“. There-
fore the input position and the output position drift away.

A speed (= master shaft speed) was recognized at the encoder input

in operating mode synchronous operation (-5), which leads to an
overflow at the encoder output with the set gear ratio. The error is
displayed and the drive tries to reduce the speed to the allowed limit
at error response „No response“.

Other error responses:

The active operating mode will be terminated and the drive will be
decelerated according to the preset error response
The error can be reset at any time.
911 New set value missing for Set-of-set The next set value did not arrive soon enough at the drive controller No response
values during the positioning process Set Value Specification (Set of set
values).
Error response „No response“ means here that the drive will not be
locked due to the error and the reaction is done in the operating
mode „Target Position Setting“. In case of error the ongoing position-
ing will be aborted, the error will be messaged and the drive will be
decelerated to a standstill with the positioning deceleration. The
error can be reset not before the brake application is finished.
The error can be reset promptly at other error responses.
912 Target position  Modulo value Operation mode: Target position setting No response
If in the target position a value is entered which is greater or equal
than the modulo value (Z118.20–), this error will be output at start of
the positioning. The error is only used at modulo target modes, e.g
Z118.10– = 11, 14 or 15.
n Effect:
m Error response: No response:
The error is messaged, the operating mode target position set-
ting remains active, but starting is not possible.
m Other error responses:
The operating mode target position setting will be stopped.
Response according to the set error response.
The error can be reset. But the target position must be less than the
modulo value, otherwise the error is messaged again at the next
positioning start.
913 Monitoring of positive stop generates The error will be set, when the positive stop was detected and the Pulse block
an error message position actual value is outside of the symmetrical monitoring win-
dow or the standstill message is not active anymore.

Parameter manual b maXX BM5000 67

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
914 Positive stop drive impossible Positive stop drive impossible is generated in case of the actual No response
operation state. Others reasons are an active master-slave torque
coupling or an active gantry-function.
915 Abort of the command at positive stop If the command "positive stop drive" is aborted while the positive Pulse block
stop is not detected by the drive but the standstill message is set
and the clamping torque is reached, this error will be generated.
916 Encoder of master axis is switched off If the synchronous operation mode in the "Real master axis" mode is No response
activated an inactive encoder of master axis was recognized.
917 Operating mode position control not ini- The operating mode position control (-4) could not be initialized cor- Quick Stop
tialized rectly.
m First possible cause:
- Z136.3– Target position is selected as the input set value
- the weighting with Z136.2– Mode bit 6 is activated
- but the „Modulo position actual value“ function (Z121.1–bit 4) is
inactive
n Remedy:
Activate the „Modulo position actual value“ function Z121.1–
bit 4 = 1 and clear the errors
m Second possible cause:
In the Z131.20– Division ratio fieldbus task one value greater
than 1 is set and the interpolation factor in the Z136.2– Mode
bit 12 and 13 is set greater than 1.
n Remedy
Both functions at once are not possible. Either set Z131.20– to 1
or delete the bits 12 and 13 in Z136.2–.
m Third possible cause:
The drive is in the enabled state in the operating mode Position
control (Z109.1– = -4) and the Z131.20– Division ratio fieldbus
task or the Z131.18– Fieldbus cycle time was changed.
1000 Power unit has canceled the controller Error is triggered in the module Operating Type Manager when a Pulse block
activation power unit error has occurred.
m Cause / Remedy:
- Check motor cable
- Check motor connection
- Replace power unit
n Effect:
The error is fatal and leads to the immediate deactivation of the
drive controller. The drive will fizzle out, if applicable. Controller
activation for the drive again will be prevented until the error
cause has been eliminated and the error has been reset.
1001 Bridge short circuit The error is triggered when the IGBT switch sequence monitoring of Pulse block
the pulse width modulation does not detect a permitted status.
Faulty and critical statuses may be bridge short circuit or inactive
periods that were not complied with.
1002 Power unit maximum DC link voltage The actual value of the DC link voltage is displayed through Parame- Pulse block
exceeded ter 130.03.
When a limit that is defined by the power unit is exceeded (see
Parameter Z129.21–), the power unit will switch off with error.

m Cause / Remedy:
- Continuous braking operation of the axes
- Error on chopper connection / chopper resistor
n Effect:
The error is fatal and leads to the immediate deactivation of the
drive controller. The drive will fizzle out, if applicable.
Controller activation for the drive again will be prevented until the
error cause has been eliminated and the error has been reset.

68 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
1003 Overcurrent error in the power unit The limit of the maximum current of the power unit is exceeded in Pulse block
one of the three phases.
In the additional information 1 of the error message is shown in
which channel the overcurrent was recognized:

0: Overcurrent (from mono device power unit)

1: Channel A, positive
2: Channel A, negative
3: Channel B, positive
4: Channel B, negative
5: Channel C, positive
6: Channel C, negative

m Cause/ Remedy:
Check motor leads
Check motor connection
1004 Power section fault current / earth fault The ground fault current of the power unit is monitored to recognize Pulse block
monitoring a motor fault current. The error message will be generated when the
fault current exceeds 20% of the permitted peak current of the power
unit.
A more detailed classification of the fault current occurs in additional
information 1 of the error message:
0: Overcurrent (from mono device power unit)
1: positive fault current
2: negative fault current

m Cause:
The ground fault may occur in the motor, motor cable or chopper
resistor or its feed cable.
n Remedy:
Find and replace the defective device.
1005 In supply mode is 0x8001 event though Though DC link voltage is greater than 90 V in Z130.10– Supply Pulse block
DC link voltage is greater than 90 V mode is set 0x8001. There is a danger of overloading of the load
(mains), Danger Load Resistor Dam- resistor. The error is initiated only at b maXX mono units.
age Further details see Z130.10–.
1006 Power unit excess temperature If the power unit exceeds a power unit dependent cut-off tempera- Pulse block
ture, the power unit will be blocked.
m Cause / Remedy:
Check function of fan power unit
n Effect:
The error is fatal and leads to the immediate deactivation of the
drive controller. The drive will fizzle out, if applicable. Controller
activation for the drive again will be prevented until the error
cause has been eliminated and the error has been reset.
1007 Power unit safety relay The error is triggered when the voltage supply of the transistor acti-
vation in the power unit is switched off through the safety relay with
activated control activation.
To avoid error messages when activating a drive, comply with the
activation sequence specified in the documentation.

m Effect:
The error is fatal and leads to the immediate deactivation of the
drive controller. The drive will fizzle out, if applicable. Controller
activation for the drive again will be prevented until the error
cause has been eliminated and the error has been reset.

Parameter manual b maXX BM5000 69

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
1010 Bit bar power unit cannot be read When multiple errors occur on the converter and power unit, the Pulse block
evaluation of the bit bar of the power unit interface will display the
differentiation of the errors. If the bit bar cannot be read out, the error
message will be generated.
This error is provided for monitoring the deactivation sequence.

m Effect:
The error is fatal and leads to the immediate deactivation of the
drive controller. The drive will fizzle out, if applicable. Controller
activation for the drive again will be prevented until the error
cause has been eliminated and the error has been reset.
1011 Incompatibility between characteristic Incompatibility between the stored characteristic data Pulse block
data OWE and LT (Mono unit) OneWireEEPROM and Power unit (Mono unit)
1012 Error while reading out characteristic Error while reading out characteristic data via HIPERFACE from Pulse block

data via HIPERFACE from LT power unit (with Mono units)
1013 Deactivation through safety technology The drive function is disabled by the safety technology (Safe Torque Pulse block
Off)
1014 DSP Timeout error because the DSP DSP Timeout error because the DSP has not updated the Pot ABC Pulse block
has not updated the Pot ABC Registers Registers
1015 Phase error timeout Phase error timeout Pulse block
1016 Mains failure (Mono unit) Message only at Mono unit (device with seperate supply) Pulse block
If the device signals „Mains failure“, the error 1016 is set by the drive
manager in the transition „Ready to switch-on“ (2) to „Switch-on“ (3).
Further details see Z130.25– Mains Failure Delay
1017 Mains undervoltage Pulse block
1018 Mains overvoltage Pulse block
1019 Undervoltage DC link voltage Error Undervoltage DC link voltage is detected through the FPGA. Pulse block

Setting the error bit in the FPGA and activating the error message
only occurs when the pulses are activated. The pulses will then be
blocked in the FPGA. Therefore, the only permitted response is the
pulse block.
1020 Heat sink excess temperature Switch off due to exceeding of the maximum heat sink temperature Pulse block
from parameter 129.26
1021 Excess temperature inside tempera- Switch off due to exceeding of the maximum heat sink temperature Pulse block
ture from parameter 129.27
1022 Cable break heat sink temperature Pulse block
encoder
1023 Communication error with MUX regis- Communication error with Multiplex Register interface to the FPGA Pulse block
ter to the FPGA
1024 Current offset error The error will be triggered when the measured current offset is Pulse block
greater than 5% of the possible measuring range of the AD con-
verter. Only one phase must thereby indicate this error.
1025 Setting of pulse enable (IF) and PWM The error is triggered when the PWM counter is no longer synchro- Pulse block
not synchronous with DSP nous with the DSP Interrupt system and the pulse activation has
been enabled.
1032 Error DC-link supply DC-link undervoltage detected (Z130.35– / Z130.36– / Z130.37–) Pulse block
or signal "supply ready for use" of the Signal Bus is low.
1033 Signal bus line warning active Signal bus line "Warning" is active No response
1034 Signal bus line error Signal bus line Error is active No response

70 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
1035 No valid Lt data available in the One Warning: No valid Lt data available in the One Wire EEPROM. Pulse block
Wire Eeprom m Effect:
The parameterization of the power unit parameters occurs from
the data record or it is faulty.
1036 Error occurred while writing the Lt data Error occurred while writing the Lt data to the One Wire EEPROM Pulse block
to the One Wire Eeprom
1037 Signal error during communication with Signal error during communication with the One Wire EEPROM Pulse block
the One Wire EEprom m Effect:
Communication with the One Wire EEPROM is faulty. The power
unit data could not be read out. The power unit could thereby not
be parameterized.
1038 No Lt One Wire EEProm Warning: No Lt Data One Wire EEPROM exists! Pulse block
1039 reserved reserved No response
1040 reserved reserved No response
1041 reserved reserved No response
1042 reserved reserved No response
1043 Warning: Undervoltage DC link voltage Warning: Undervoltage DC link voltage No response
1044 Warning: Undervoltage Mains Warning: Undervoltage Mains No response
1045 Warning: Overvoltage Mains Warning: Overvoltage Mains No response
1046 Warning: Deactivation through safety The safety function Safe Torque Off is active No response
technology
1047 Warning: Phase failure This warning is set if a phase failure is recognized. No response
The warning will be deleted automatically as soon as the phase fail-
ure is no more existent and the error response „no respone“ is set
for this message. If a drive reaction is set, the error must be reset.
1048 Warning: Mains failure / Supply not A mains failure was detected or the supply is not ready-to-operate. No response
ready The warning is triggered independent of the drive state. If the drive is
enabled, the error 1016 (Mains failure) or 1032 (Error DC-link sup-
ply) is generated at the end of the Mains failure delay.
Further details see Z130.25– Mains failure delay
1049 Temperature warning threshold heat Temperature warning threshold heat sink exceeded No response
sink exceeded
1050 Temperature warning threshold Inside No response
Air exceeded
1054 DSP Timeout Error: DSP does not DSP Timeout Error: DSP does not write the PWM Pot Registers in Pulse block
write the PWM Pot Registers in time, 3 time, 3 times within 100 ms
times within 100 ms
1056 Performance element 24 V Fail When the 24V supply voltage drops below a specific threshold the Pulse block
FPGA will activate a corresponding error bit in its status and block
the pulses.
m Effect:
The response from the related DSP error message must neces-
sarily the pulse block so that the drive manager and thereby the
control loops remain synchronous with the status of the pulse
enable.
1057 15 V fault - power cycle required The 15 V power supply failed. Pulse block
1066 SS1 stop forced by SAF module If SS1 function is activated on SAF-002/-003 module and an appro- No response
priate error occurs, the SAF module forces the SS1 stop function on
the controller.

Parameter manual b maXX BM5000 71

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
1070 Change of the PWM frequency not Effect: The new set PWM frequency is not accepted. No response
possible. PWM frequency change is in
progress. The error can be caused:
1 The previous PWM frequency change is in progress.
Remedy: Reduce the cycle of the PWM change or implement a
function into the master control which enables a PWM change
only after the previous change was completed.
1 The PWM frequency redurction of the power unit temperature
model is active (warning 216).
Remedy: Monitoring of warning 216 via master control. If warning
216 is active no PWM change is initiated.
1071 Timeout quick discharge Error at discharging the DC link Pulse block
1100 Drive manager general error pulse When a pulse block has no reason that can be recognized by the Pulse block
enable drive manager (AM) (recognizable are: digital input, error with
response pulse block, command control word), there is a threat of an
endless change of statuses in the AM:
Statuses 2->3->2 etc. are continuously processed because all
switching conditions are met and the AM continues to attempt to
activate the drive.
To prevent this, the change in status 3 will be disabled when a pulse
block is recognized, a marker will be set and the error RC_ERR_D-
MGR_IF is entered for signaling.
No change is possible in Status 3 as long as the marker is set.
m Effect:
The drive switches to Status 15 (Error). Other responses are no
longer permitted so that the drive cannot automatically restart in
the case above (pulse block without entering a error with pulse
block) after Error #1100 has been reset.
1101 Motor parking brake does not open The motor parking brake should open in Automatic mode of the Pulse block
when the drive ist started brake activation when the drive is activated but it does not.
m Effect:
The drive is not activated so that it does not try to drive against the
closed brake. The above error message will be issued. The error
bit will be activated in the status of the brake activation.
1102 Motor parking brake does not close The motor parking brake should close in Automatic mode of the No response
when the drive is switched off brake activation when switching off after active braking (pulses are
activated, should be switched off), but it does not.
m Effect:
The above error message is issued. The error bit will be activated
in the status of the brake activation. The response of the drive
depends on the error response that has been set:
n Pulse block:
The drive blocks the pulses and will be switched off.
n otherwise:
AT first, the pulses remain switched on. The drive can then
either be switched off depending on the status in the drive man-
ager through a corresponding command (->Blocking of pulses)
or reactivated.
1103 Cyclical monitoring of brake activation The cyclical monitoring of the brake activation determines that the No response
reports error set value and actual status of the motor parking brake do not match
(brake should open but is closed or brake should close and is
opened).
m Effect:
The above error message is issued. The error bit will be activated
in the status of the brake activation. The response of the drive
depends on the error response that has been set.

72 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
1104 Motor parking brake: Brake moment The drive should build up in the Automatic mode of the brake activa- Pulse block
prior to opening the brake not reached tion during enable before opening the motor parking brake but can-
not reach a stop moment.
m Effect:
The drive is not activated to prevent a possibly hanging load from
dropping. The above error message will be issued. The error bit
will be activated in the status of the brake activation.
1105 Cyclical monitoring of the brake pad The cyclical monitoring of the brake pad detects a error. No response
reports the error m Effect:
The above error message is issued. The error bit will be activated
in the status of the brake activation. The response of the drive
depends on the error response that has been set.
1106 Drive operation mode not allowed with Drive operation mode not allowed with this motor mode operation Pulse block
this motor operation mode mode. error caused when changing from state 3 to 4.
m Effect
Drive is not started
m Error reset
Error can be reset
1107 To this operation mode cannot be To this operation mode cannot be changed in operation mode 4. No No response
changed in operation mode 4 online change possible e.g. from speed control to find notch posi-
tion.
1300 Memory organization is faulty. No response
1301 Invalid trigger configuration (both Invalid trigger configuration in the ring buffer. Triggering to both No response
edges) edges is not possible.
1302 no Trigger ID entered no Trigger ID entered No response
1303 no ID to read out data no ID to read out data No response
1304 no permission to read out data No response
1305 No record for channel and axis No record for channel and axis No response
1400 Error while loading or saving the data Error while loading or saving the data record Pulse block
record
1401 No valid parameter file found No valid parameter file found Pulse block
1402 CRC in parameter file not correct CRC in parameter file not correct Pulse block
1403 Invalid data record number indicated An invalid data record number was indicated for a data record com- No response
for DSV command mand.

The error is reported when an attempt is made to switch to a non-

existing data record, delete the active data record or copy the values
from a non-existing data record.
1500 uBlaze Software has a critical error It was an critical error and uBlaze Software is no longer functional No response
1501 If there is no response from the slave Slave did not respond within specified time. No response
(HPI-Buffer Initialization) Master Ident Code = 0xDEADBEEF
Slave Ident Code = 0xBEEFDEAD
1502 Message length is greater than HPI Message length is greater than HPI Buffer No response
Buffer
1503 Access to HPI wrong channel Access to the wrong (non-existent) HPI-Channel No response
1504 HPI Channel was not initialized First Access to the HPI-channel was early as the initialization. No response
1505 HPI buffer is empty HPI buffer has no user data available. No response
1506 HPI buffer is full HPI buffer has user data available or old telegram data are not No response
called for yet.
1507 TCP IP Stack could not be initialized An error has occurred at initialization of TCP/IP stack No response

Parameter manual b maXX BM5000 73

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
1508 SoE firmware error message SoE firmware (Servodrive-Profile over EtherCAT) sends an error No response
message to the drive controller. The error reaction is started by the
SoE firmware of the fieldbus processor.
1509 EtherCAT IP core cannot init EEPROM No response
1510 Sub device index invalid Sub device index invalid, i.e. out of range No response
1511 Firmware error fieldbus controller Fieldbus controller signaled a firmware error. No response
1512 Faulty backup of operation data No response
1513 Illegal drive address A invalid drive address is set. No response
1514 Error caused by memory allocation No response
1515 Faulty task start Operating system was not able to start a task. No response
1516 Faulty init of scaling data No response
1517 Error during reading of the cyclic actual No response
values
1518 Error during writing of the cyclic set val- No response
ues
1519 Critical GDP error while initialization Incorrect reading or writing of important data via GPD. GPD means No response
the communication between controller and fieldbus controller.
1520 Invalid version of the controller firm- Installed controller firmware cannot be used with this type of field- No response
ware bus. Version see controller parameter P102.2 or IDN P-0-0221
1521 Warning: Error while reading service No response
data
1522 Warning: Error while writing service No response
data
1523 Error during command execution An error occurred during a command execution. No response
1524 Timeout during command execution A timeout occurred during a command execution. No response
1525 MST-Error; drive controller lost syn- Sercos: MST incorrect No response
chronization SoE: controller signaled lost synchronization
1526 Error: MDT miss twice; watchdog time- Sercos: failure of MDT (MDT miss twice) No response
out process data SoE: watchdog timeout at process data
1527 Error during switch up of phase Error during switch up of the bus state No response
(phase switch up)
1528 Error during switch down of phase Error during switch down of the bus state No response
(phase switch down)
1529 Phase transition without ready Sercos: No response
acknowledge n switch up to CP3 not possible  back to CP0.
n switch up to CP4 not possible  back to CP0.

SoE:
n switch up to Safe-Op not possible  back to Pre-OP.
n switch up to Op not possible  back to Safe-OP.
1530 Error: Invalid phase Invalid phase (bus state) set. No response
1531 Switch to non-initialized operation Switch to a not supported or unknown operation mode. No response
mode
1532 Error: Two drives with same address in Error message only possible using Sercos. No response
ring
1533 Error while reading sync data of drive Error when adjusting the synchronization data with the settings in No response
controller the drive controller.
1534 Overflow mailbox service Overflow during a fragmented mailbox service. No response
1535 Invalid mailbox size Error detected when checking the mailbox size. No response

74 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
1536 to 1555: see Application Manual SoE slave for BM2500/3300/5000 (5.14010)
1600 wrong driver handle transferred No response
1601 Open command on already opened No response
driver
1602 Driver has already been opened No response
1603 ZERO pointer transferred No response
1604 Timeout with OS access No response
1605 Faulty checksum No response
1606 Response from device faulty No response
1607 invalid semaphore entered for waiting No response
1608 unexpected API status for active com- No response
mand
1609 too many repetitions with HIPER- No response

FACE protocol
1610 Call-up option invalid No response
1611 unknown object indicated for reading or No response
writing
1612 Error while initializing the driver No response
1613 the response data is too large for the No response
available buffer
1700 Error code directly according to error Pulse block
report from encoder
1701 Analog signals outside of specification Rotary encoder: Analog signals outside of specification Pulse block
Calibration data are faulty Linear encoder: Calibration data are faulty
1702 Internal angle offset faulty Pulse block
1703 Table for data field partitioning Pulse block
destroyed
1704 Analog limit values not available Pulse block
1705 Internal I2C bus not functional Pulse block
1706 Internal checksum error Pulse block
1707 Encoder reset occurred through pro- Pulse block
gram monitoring
1708 Counter overrun Pulse block
1709 Parity error Pulse block
1710 Checksum of transferred data is wrong Pulse block
1711 Unknown command code Pulse block
1712 Amount of transferred data wrong Pulse block
1713 Transferred command argument not Pulse block
permitted
1714 The selected data field may not be writ- Pulse block
ten to
1715 Wrong access code Pulse block
1716 Indicated data field size cannot be Pulse block
changed
1717 Indicated word address is outside of Pulse block
the data field

Parameter manual b maXX BM5000 75

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
1718 No data field or addressed data field Pulse block
does not exist
1728 Amount monitoring for analog signals Amount monitoring for analog signals (process data) Pulse block
(process data)
1729 Transmission current critical (contami- Transmission current critical (contamination, transmission break) Pulse block
nation, transmission break)
1730 Encoder temperature critical Encoder temperature critical Pulse block
1731 Speed too high, no position establish- Speed too high, no position establishment possible Pulse block
ment possible
1732 Speed too high, position can't be calcu- At rotatory encoders: position can't be calculated Pulse block
lated At linear encoders: sensor is not adjusted or is not in adjustment
mode
1733 Position error Multiturn At rotatory encoders: Position error Multiturn Pulse block
At linear encoders: distance magnetic tape/sensor too high
1734 Position error Multiturn At rotatory encoders: Position error Multiturn Pulse block
At linear encoders: Positional error
1735 Position error Multiturn Position error Multiturn Pulse block
1752 Error while initializing the encoder Error while initializing the encoder (multiple errors) Pulse block
(multiple errors)
1753 Position generally not dependable Encoder position not dependable. Quotient of resolution to line num- Pulse block
ber faulty
1754 Unknown error from encoder Unknown error code from the encoder Pulse block
1800 no or invalid data in the encoder motor The error occurs when no motor data can be read from the encoder Pulse block
type plate after rebooting.
1801 Invalid section found in the encoder Invalid section found while reading the encoder memory. Reference Pulse block
OEM memory to wrong data in the OEM memory of the encoder.
1802 too many sections of the type "variable Pulse block
operating data"
1803 Index for addressing the section for Pulse block
variable operating data too large
1805 Checksum error in Section Pulse block
1806 Version of imported data structure Pulse block
unknown
1808 Wrong quantity (0 or 128) Pulse block
1809 Wrong data field (only 0 or 1 permitted) Pulse block
1810 Data field start address too large (= Pulse block
128)
1813 No memory available in the encoder Pulse block
1814 Faulty data in the section Data in the section is not plausible (WordCount is 0 or too large) Pulse block
1815 No section exists for motor type plate in No section for a motor type plate exists in the encoder OEM mem- Pulse block
the encoder memory ory.
1816 No section exists for notch position No section exists for notch position mechanical in the encoder OEM Pulse block
mechanical in the encoder memory memory
1817 No section exists for M0 data in the No section exists for M0 data in the encoder OEM memory Pulse block
encoder memory
1818 No section exists for operating data in No section exists for operating data in the encoder OEM memory Pulse block
the encoder memory
1901 Connection did not exist, client was not No response
logged in.

76 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
1902 GdpProtocol version not supported. No response
1903 Maximum number of users reached. No response
1904 Report ID not known. No GDP report No response
1905 CRC32 checksum does not match the No response
calculated checksum.
1906 Telegram header size not plausible. No response
1907 Job length not plausible. No response
1908 Fragment length not plausible. No response
1909 Command not yet implemented. No response
1910 User is already logged in No response
1911 User is not logged in No response
1913 Too many parameters have been No response
requested
1914 The Job ID is wrong in a sequence of No response
partial telegrams
1915 Wrong count value for Parameter No response
Read-Write
1917 OrderSpec not supported No response
1918 Buffer size of small block length not No response
plausible
1919 Block length smaller than minimum No response
required size
1920 Too many simultaneously active com- No response
mand
1921 Command unknown No response
1922 Wrong list type No response
1923 Wrong parameter list ID No response
1924 Wrong parameter number for parame- Wrong parameter number for parameter list No response
ter list
1925 Parameter does not exist No response
1926 List does not exist No response
1927 Wrong real time mode No response
1928 Value for Alive Timeout may not be 0 No response
1930 Index range wrong (Start-Index End- No response
Index or Max-DIM
1931 General transmission error. Client must No response
repeat telegram (e.g. with fragmented
transmissions)
1932 No additional real time list can be regis- No additional real time list can be registered No response
tered
1933 CRC of a transferred file does not The files that can be transferred to the device are protected with a No response
match the calculated file CRC.

During the file transfer through GDP this file CRC is checked in addi-
tion to the separate checksum of the transmission. If it does not
match the calculated checksum, a error will be returned at the end of
the transmission so that this is not detected at the next booting pro-
cedure that the transmission has failed.

Parameter manual b maXX BM5000 77

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
1934 Communication partner reports error Communication partner reports error number in telegram user data No response
number in telegram user data The content of the use data must be interpreted as a error number
for further evaluation.
1935 Different subdevice Indices within a Parameters within a telegram can only be sent to the same subde- No response
request are not permitted vice. This error occurs when a client wants to transmit parameters
with different subdevice indices within a telegram.
m Effect:
The requested telegram cannot be transmitted.
1936 Report timeout has occurred Report timeout has occurred No response
1937 Actual data were not picked up on time Actual data (producer data) were not picked up on time Pulse block
1938 Set value failure at cyclic data Set value failure at cyclic data Pulse block
1939 File length smaller than transmitted The file length is smaller than the length of the transmitted data. No response
data More data has been transmitted than the file length should be,
according to the command.
1940 Command is not in the memory of the No response
command pool
1941 No command data for processing No response
1943 Error while writing a parameter through Error while writing a parameter through real time No response
real time
1944 "Scope" wrong "Scope" wrong No response
1946 Available memory in the destination Available memory in the destination device insufficient No response
device insufficient
1947 Invalid file name Invalid file name No response
1948 Unknown or wrong memory destination Unknown or wrong memory destination ("Destination") No response
("Destination")
1949 Unknown option Unknown option No response
1950 Wrong file length (e.g. may not be 0) No response
1951 Connection (TCP/IP, serial) not opened The connection of the transport layer (TCP/IP, serial, ...) is not open. No response
or closed by the partner Either the connection was not opened at all or it was closed due to a
socket error by the internal TCP/IP stack or communication partner.
1952 Data received for a complete telegram Characters were received through a communication source; how- No response
is insufficient ever, the telegram is incomplete and additional characters must be
received.
2000 Mains synchronization not possible The error is enabled, if the active mains rectifier unit can not syn- Pulse block
chronize with the mains within 10 s, although a successful offset-
and rotary field detection has taken place.

m Possible cause:
Frequency fluctuation of the mains voltage
2001 Timeout load circuit The active mains rectifier unit was not able to charge the DC link to Pulse block
the power supply peak voltage within the time set in Maximum
charging time.

m Possible cause:
The DC link capacity is greater than the permitted value.
The function of the voltage measurement for the DC link voltage
or to trigger the thyristors is faulty.
2002 Timeout relay The device is not able to switch on the power relay within 3 s after Pulse block
the request.

m Possible causes:

78 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
2003 Timeout DC link-control The active mains rectifier unit is not able to set the DC link voltage Pulse block
within 5 s set value.

m Possible causes:
Ramp slope was set too low
2004 1-phase power failure The active mains rectifier unit has detected a 1-phase mains failure. Pulse block

m Possible causes:
Failure of a phase of the three-phase power system
2005 2- or 3-phase power failure The active mains rectifier unit has detected a two- or three-phase Pulse block
mains failure.

m Possible causes:
The mains voltage collapsed
2006 Overvoltage in mains The active mains rectifier unit has measured a voltage of over 530 V Pulse block
effective in the mains.

m Possible causes:
The mains voltage has risen to over 530 V or the measurement
switch for the mains voltage measurement is defective.
2007 Undervoltage in mains The active mains rectifier unit has measured a voltage lower than Pulse block
U DC_min  P129.42  – 30 V
---------------------------------------------------------------
2

m Possible causes:
The mains voltage was fallen under
U DC_min  P129.42  – 30 V
--------------------------------------------------------------- or the measurement switch for the
2
mains voltage measurement is defective.
2008 Overvoltage in DC link The DC Link voltage has risen over the value in Z129.21–, the Pulse block
active mains rectifier unit was not able to feed the braking energy of
the drive quickly enough back into the mains.

m Possible causes:
The DC link controller is not optimally adapted to the application.
Possibly the active current limit in the regenerative braking mode
is set too low.
2009 Undervoltage in DC link If the DC link voltage in the controlled state is lower than the peak Pulse block
voltage or if the DC link voltage in the uncontrolled state is lower
than 87% of the peak voltage, this error is enabled.

m Possible causes:
The DC link controller is not optimally adapted to the application.
Possibly the active current limit in the supply mode is set too low.
2010 Mains Frequency in the Upper or the This message is transmitted if a mains frequency of more than No response
Lower Limit Range 65 Hz and less than 45 Hz was detected.

Parameter manual b maXX BM5000 79

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
2013 Timeout quick discharge The active mains rectifier unit calculates the discharging time from Pulse block
the maximum discharging resistor (see Instruction Manual) and the
maximum DC link capacity according to the relation:

t Discharging = – R Discharging_max  P129.62  ln  -------------------

20 V
P129.21

If the discharging is triggered, the DC link is discharged always for at

least 10 s via the discharging resistor. If the DC link voltage is
greater than 20 V after 10 s discharging time, then it is checked
whether the calculated discharging time is greater than the so far
elapsed discharging time of 10 s. If this is not the case, the error is
triggered at once.
If the calculated discharging time is greater than 10 s and if the DC
link voltage is greater than 20 V after the discharging time, then the
error is triggered also in this case.

m Possible causes: The chopper resistor is not connected or was

selected too great. Possibly the DC link capacity is greater than
specified (see Operating Instructions BM5000 (5.09021)).
2014 Short circuit in DC link The active mains rectifier unit determines that during the loading Pulse block
procedure, there is current flowing into the device, but the DC link
voltage is not rising accordingly. This error cannot be reset. The
device must be restarted.

m Possible causes:
The DC link is short-circuited or is loaded while it is being
charged.
2015 Current is still flowing, the relay may The active mains rectifier unit tried to separate the device from the Pulse block
not be switched off mains; thereby still a peak current of greater than 10 A was
detected. This error cannot be reset. The device must be restarted.

m Possible causes:
The DC link is still loaded although the "ready-for-use"-signal on
the signal bus and the signal "control ready-for-use" have
dropped.
2016 Relay does not drop The power relays, which bridge the load switch, do not drop, when Pulse block
the attempt is made to switch them off. This error cannot be reset.
The device must be restarted.
2017 Mains current at discharge The active mains rectifier unit determines a peak current of more Pulse block
than 10 A during the discharge. This error cannot be reset. The
device must be restarted.

m Possible causes:
The main contactor and the power relay could not be opened
before discharging them. Possibly their contacts are sticking
together.
2018 DC link voltage set value is too low If the set value of the DC link voltage is entered manually, then this Pulse block
input must be greater than the mains peak voltage of +40 V. If this
input is not complied with, this error is enabled.
If the automatic generation of the DC link voltage set value is active,
this error threshold is not checked.

80 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
2019 Mains Synchronization lost The active mains rectifier unit has lost its synchronization with the Pulse block
mains.

m Possible causes:
The mains frequency is lower than 40 Hz or greater than 70 Hz. It
also can happen that the mains frequency changes very quickly,
so that the synchronization cannot compensate this change.
2020 Offset Measurement was not possible This error is not enabled, if the active mains rectifier unit does not Pulse block
determine a mains offset within 10 s, which is constantly moving in a
window of 200 V.

m Possible causes:
There is a continuous variation of the mains offset. On the other
hand this can also be a reference to a defective voltage measure-
ment.
2021 Voltage Offset Outside the Plausible This error is enabled if a mains offset is determined in a linked volt- Pulse block
Range age greater than 40 V.

m Possible causes:
An offset, which is that high, indicates a defective measuring cir-
cuit.
2022 Overload of the Device This error is enabled in connection with the errors 2008 and 2009. If Pulse block
the active mains rectifier unit detects an over- or an undervoltage in
the DC link, it will try to counteract. If the device is already driving at
the current limit and the DC link voltage, despite of this, cannot be
maintained, then the load is too great for the device.

m Possible causes:
The current limit was set too low.
2023 Timeout - Rotary Field Detection The active mains rectifier unit was not able to determine the rotary Pulse block
field of the mains definitely within 5 s.
2024 Counterclockwise Rotary Field Pro- This error is enabled, if the active mains rectifier unit detects a coun- No error
cessing at the Device terclockwise field at the connection terminals. In general this error is
not parameterized as an error. The active mains rectifier unit can
also be operated to the full range with a counterclockwise field. This
error allows the user to exclude the counterclockwise field operation
of the device.
2025 Warning - Exceeding the Mains Power This error is enabled, if the the active mains power exceeds the No response
Level value in the parameter Z141.40–. The error is reset by the device as
soon as the mains power falls below the threshold, which was set.
2026 Warning - mains voltage smaller than This error is enabled, if the actual value of the mains voltage falls No response
adjusted threshold below the value in the parameter Z141.41–. If the error reaction "No
reaction" was parameterized for the error, then the error is reset as
soon as the actual value of the mains voltage exceeds the value in
Z141.41–.
2027 Warning - mains voltage greater than This error is enabled, if the actual value of the mains voltage No response
adjusted threshold exceeds the value in parameter Z141.42–. If the error reaction "No
Reaction" was parameterized for the error, then the error is reset by
the device as soon as the actual value of the mains voltage falls
below the value in Z141.42–.

Parameter manual b maXX BM5000 81

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
2028 No supply voltage at the device In state transition from "Power-on Disable" to "Ready to Start", a No response
three-phase supply is to be expected of the active mains rectifier on
its terminals after closing the contact "Ready for Main Contactor
ON" (X2-9; X2-10). This error is triggered, if no three-phase supply
is detected after closing the contact "Ready for Contactor ON" for 5
seconds. This error cannot be cleared by the user. This error is reset
by the device, if a three-phase supply is detected at the terminals of
the active mains rectifier unit.
2200 Error occurred in the FFT analyzer An error occurred in the FFT analyzer function. For an exact specifi- No response
cation, refer to Parameter Z104.8– "FFT Info".
2201 FFT result not ready for READING yet No response
2300 FPGA_RSP record is not available for No response
READING
2400 Invalid "Device type" in login message Invalid "Device type" in login message No response
2401 Invalid command for a confirm mes- Invalid command for a confirm message No response
sage
2402 Wrong connection ID from server Wrong connection ID from server No response
2403 File data on server and client are not File data on server and client are not equal No response
equal
2404 Error with erasing file data Error with erasing file data No response
2405 Erasing file data is busy Erasing file data is busy No response
2406 Error with writing file data Error with writing file data No response
2407 Writing file data is busy Writing file data is busy No response
2408 Error with reading file data Error with reading file data No response
2409 No valid FU file on client No valid FU file on client No response
2410 Handling FU file is busy Handling FU file is busy No response
2411 No valid PC file on client No valid PC file on client No response
2412 Handling PC file is busy Handling PC file is busy No response
2413 The transmit process is busy The transmit process is busy No response
2414 The receive process is busy The receive process is busy No response
2415 Timeout of transmit process Timeout of transmit process No response
2416 Timeout of receive process Timeout of receive process No response
2417 Build the list or parameter is busy Build the list or parameter is busy No response
2418 Module change too lower safety level A module change happened. The actual module has a lower safety Pulse block
level than the former one. The controller must not be operated.
m Error reset:
Pulse block, resetting not possible
2419 Modul change from SAF-003 to Modul change from SAF-003 to SAF-002. The controller must not be Pulse block
SAF-002 operated.
m Error reset:
Resetting not possible
2420 No valid controller for SAF module The controller is not suitable for SAF module. The safety level of No response
controller is lower than the safety level of the SAF module.
2421 Number of axes from controller and Number of axes from controller, DIP switch of SAF module and No response
SAF module are not equal safety parameter are not equal.
2422 No FSoE communication active at No FSoE communication active at SAF-002 or SAF-003. The SAF No response
SAF-002 or SAF-003 module is not ready and the controller may not leave drive state 0.
2423 Pulse inhibit because of SAF-100 The controller allows no pulse enable because a Reset Module Pulse block
(SAF-100) is plugged in.

82 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
2598 Last reserved error number for platform Platform errors are reserved error numbers that may have different No response
error levels of importance on each platform. This range of numbers is
reserved so that platform specific error numbers (e.g. Windows error
numbers) do not have to be defined as generally valid in rc.h. These
error numbers can then be used as return codes within the platform
and may thereby not be transferred externally.
2700 Fb Set value generator Set Value < Min One or more set values of the set value generator (FbSwg) are No response
(target parameter) smaller than the minimum value of the selected target parameter.

Testing is carried out to prevent overrun effects while writing to the

target parameter.
2701 Fb Set value generator Set Value > One or more set values of the set value generator (FbSwg) are No response
Max (target parameter) greater than the maximum value of the selected target parameter.

Testing is carried out to prevent overrun effects while writing to the

target parameter.
2702 Error in the configuration of the return General error in the configuration of the return motion detected by Pulse block
motion the test function.
Cause:
m The motorized operation at mains failure is not permitted
(Z130.10– Supply mode bit 1 = 0)
2720 Cam generator - no input parameter Selection of processing mode "parameter-controlled processing" No response
was selected No input parameter was selected.
2721 Cam generator - no reference parame- Selection of relative mode, but no reference parameter was No response
ter was selected selected.
2722 Cam generator - no output parameter No target parameter was selected. No response
was selected
2723 Cam generator - the output value was The output value of the cam is greater than the maximum value of Pulse block
limited the target parameter or the output value is lower than the minimum
value of the target parameter.
2724 Cam generator - in the RAM no valid An attempt was made to start the cam generator, although there was No response
cam was found no applicable cam in the RAM
2725 Cam generator - an error occurred An attempt to load a cam into the device failed. No response
while loading the cam
m Possible causes:
n Cam has more than 1024 supporting points
n An attempt was made to load a cam, although another cam was
processing yet
n An attempt was made to load a wrong file. Only files with exten-
sion *.kbin can be loaded.
2726 Cam generator - the active cam cannot In the "parameter-controlled processing" mode the cyclical process- No response
be used in this mode ing is selected. The count of supporting points must accord to power
2. This is not the case at the active cam (e.g. count of supporting
points is 256, 512 or 1024)
2740 No polynomial curve data available It was tried to release the drive in the operation mode "Coupled Pulse block
mode" but there is no polynomial curve data in the controller.

m Consequence:
The operation in the coupled mode isn't possible. Behavior accor-
dant to set error reaction.

Parameter manual b maXX BM5000 83

Document No.: 5.09022.17 of 978
3.5 Error descriptions

Error Brief error text Error description Default

No. error
response
2741 Invalid segment number detected At the polynomial curve generator an invalid segment number was Pulse block
transferred for which there is no segment existent.
This error can occur at the transmission of the curve segments or at
a chain change.

m Consequence:
The transmitted curve segments are rejected.
2742 No valid start segment defined The start segment defined in the parameter Z122.7– isn't in the Pulse block
polynomial curve.

m Consequence:
The polynomial curve generator cannot be activated.
2743 No cam data available in internal buffer The intermediate buffer doesn't include valid polynomial curve data. Pulse block
Presumably the required data weren't able to be added in time. It is
recommended to reduce the speed of the master or to increase the
scope of the individual curve segments.

m Consequence:
The processing of the polynomial curves must be interrupted.
2744 Master axis in motion during synchroni- In the Z122.2– mode of the "Coupled mode" was set that the master No response
zation axis must stop during the synchronization phase. However a posi-
tion change was determined at the master axis position.

m Consequence:
Depending on the error reaction. If there is no reaction parameter-
ized, the drive processes the synchronization of the polynomial
curves anyway. However, the polynomial curve and the synchroni-
zation movement overlap.
2745 Invalid start position of the master axis A valid starting position of the master axis in the parameter Z122.8– Pulse block
and Z122.9– was not defined.
m Cause
Based on the starting position the current master axis position
Z122.3– and Z122.4– are not within the linking of the active
curve.
2746 File handler busy Although the previous transmission was not completed yet a polyno- No response
mial curve was transmitted.
2747 Transmitted file includes unknown The transmitted curve contains an unknown curve type. No response
curve type
m Consequence:
The transmission is interrupted and the file is canceled.
2748 An active curve could not be deleted It's not permitted to overwrite the polynomial curve completely No response
during processing. However, the reload by using a changed curve
segment would be possible.

m Consequence:
The previous curve is continued to be processed.

84 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH
 Error messages and troubleshooting 3
Error Brief error text Error description Default
No. error
response
2749 Cam file version is unknown The controller firmware doesn't know the version of the transmitted No response
cam file.

m Consequence:
The cam file is rejected.
2750 To many revolutions per segment One of the transmitted curve segments was defined for more than No response
defined 65535 master or slave revolutions.

m Consequence:
The cam file is rejected.
2800 No identification in the DPRAM Header No identification found in the DPRAM Header (DEADBEEF) No response

Parameter manual b maXX BM5000 85

Document No.: 5.09022.17 of 978
3.5 Error descriptions

86 Parameter manual b maXX BM5000

of 978 Document No.: 5.09022.17 Baumüller Nürnberg GmbH