Error messages and troubleshooting
Parameter manual b maXX BM3000
Document no.: 5.12001.07
767
of 820
5
1931 General transmission error. Client must
repeat telegram (e.g. with fragmented
transmissions)
No response
1932 No additional real time list can be regis-
tered
No additional real time list can be registered No response
1933 CRC of a transferred file does not
match the calculated file
The files that can be transferred to the device are protected with a
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.
No response
1934 Communication partner reports error
number in telegram user data
Communication partner reports error number in telegram user data
The content of the use data must be interpreted as a error number
for further evaluation.
No response
1935 Different subdevice Indices within a
request are not permitted
Parameters within a telegram can only be sent to the same subde-
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.
No response
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
data
The file length is smaller than the length of the transmitted data.
More data has been transmitted than the file length should be,
according to the command.
No response
1940 Command is not in the memory of the
command pool
No response
1941 No command data for processing No response
1943 Error while writing a parameter through
real time
Error while writing a parameter through real time No response
1944 "Scope" wrong "Scope" wrong No response
1946 Available memory in the destination
device insufficient
Available memory in the destination device insufficient No response
1947 Invalid file name Invalid file name No response
1948 Unknown or wrong memory destination
("Destination")
Unknown or wrong memory destination ("Destination") No response
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
or closed by the partner
The connection of the transport layer (TCP/IP, serial, ...) is not open.
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.
No response
1952 Data received for a complete telegram
is insufficient
Characters were received through a communication source; how-
ever, the telegram is incomplete and additional characters must be
received.
No response
2200 Error occurred in the FFT module A error occurred in the FFT Analysis module. For an exact specifica-
tion, refer to Parameter 104.8 "FFT Info".
No response
2201 FFT result not ready for READING yet No response
Error
num-
ber
Brief error text Error description Default set-
ting for
Error
Response
To Next Page
Loading...
Need help?
General