Baumuller b maXX BM5800, Руководство по параметрам

Страница: 732 / 816

Error descriptions
Parameter manual b maXX BM5800
Document No.: 5.16029.03 Baumüller Nürnberg GmbH
732
of 814
4.5
4.5 Error descriptions
Error
num-
ber Brief error text Error description Default set-
ting for
Error
Response
100 No Heap memory available No Heap memory available No response
101 Stack monitoring: stack consumption
has reached error threshold. The stack consumption has reached error threshold. A safe opera-
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. Pulse block
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
detected in a floating point operation.
No response
116 Timeout of I2C Bus Read/Write
Eeprom A timeout error occurred in the I2C Bus. The serial I2C EEPROM is
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.
No response
118 Error while reading or writing the hard-
ware board data An error has occurred while reading or writing the hardware board
data. Pulse block
119 Drive no longer synchronous with field-
bus The error is enabled, if the synchronization signal of the fieldbus is
more than once out of the synchronous window after a successful
synchronization. Pulse block
121 Measured RT fieldbus cycle too large The error is triggered when the fieldbus cycle that is measured in the
FPGA is greater than the parameterized set value fieldbus cycle. Pulse block
122 Measured fieldbus cycle too small The fieldbus cycle that is measured in the FPGA is smaller than the
parameterized set value fieldbus cycle Pulse block
123 RT fieldbus jitter greater than the syn-
chronizer window The error is triggered when the jitter of the fieldbus interrupt that is
measured in the FPGA is greater than the parameterized synchro-
nizer window. Pulse block
124 PWM Counter 1 not synchronous with
the DSP time dial system The error is triggered when the PWM counter of Drive 1 is no longer
synchronous with the time dial system of the DSP. Pulse block
126 RT fieldbus run time error The error is triggered when a error occurs in the chronological order
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. Pulse block
127 Timeout fieldbus interrupt The error is triggered when more than 3 fieldbus interrupts have
failed. The synchronization will be initiated again. Pulse block
128 Unknown identification System FPGA Identification of system FPGA is unknown in the DSP Pulse block
129 System FPGA version does not fit to
DSP software System FPGA version does not fit to DSP software Pulse block
130 The fallback version was booted by
Bootloader 1 The fallback version was booted by Bootloader 1 Pulse block
131 The communication firmware has
booted the fallback version The communication firmware has booted the fallback version Pulse block
132 The firmware has booted the fallback
version The firmware has booted the fallback version Pulse block