General AMS errors
0 - without error
1 - error of input data
2 - error of output data
3 - protocol cannot be used for this port
4 - readout not started
1 - error of input data
2 - error of output data
3 - protocol cannot be used for this port
4 - readout not started
M-Bus AMS errors
131072 - non specific error (internal error of module)
131073 - readout was stopped by user
131074 - bad format address and speed of the device
131075 - parameters of the port were not set
131076 - message "SND_NKE" was not send in defined time interval to the device
131077 - message "SND_NKE" was not send in defined time interval to the device
131078 - timeout - receiving "SND_NKE" message response
131079 - bad frame when receiving "SND_NKE" message from the device
131080 - message "REQ_UD2" was not send
131081 - message "REQ_UD2" was not send
131082 - timeout - receiving "REQ_UD2" message response
131083 - incorrect communication frame for "REQ_UD2" message
131084 - incorrect response for "REQ_UD2" message
131085 - incorrect device address in response for "REQ_UD2" message
131086 - message "SND_UD slave selection" was not send in defined time interval
131087 - message "SND_UD slave selection" was not send in defined time interval
131088 - timeout - receiving "SND_UD slave selection" message response
131089 - bad frame for "SND_UD slave selection" response message
131090 - message "SND_UD slave selection" was not send in defined time interval during searching slaves on bus
131091 - message "SND_UD slave selection" was not send in defined time interval during searching slaves on bus
131092 - message "REQ_UD2" was not send in defined time interval during searching slaves on bus
131093 - message "REQ_UD2" was not send in defined time interval during searching slaves on bus
131094 - collision of secondary addresses during searching slaves on bus (two or more devices have same secondary address)
131329 - bad first "start" byte for device´s response message
131330 - bad second "start" byte for device´s response message
131331 - bad first "stop" byte for device´s response message
131332 - bad checksum of the response frame
131333 - bad value of the response frame length
131334 - bad value of the response frame length
131073 - readout was stopped by user
131074 - bad format address and speed of the device
131075 - parameters of the port were not set
131076 - message "SND_NKE" was not send in defined time interval to the device
131077 - message "SND_NKE" was not send in defined time interval to the device
131078 - timeout - receiving "SND_NKE" message response
131079 - bad frame when receiving "SND_NKE" message from the device
131080 - message "REQ_UD2" was not send
131081 - message "REQ_UD2" was not send
131082 - timeout - receiving "REQ_UD2" message response
131083 - incorrect communication frame for "REQ_UD2" message
131084 - incorrect response for "REQ_UD2" message
131085 - incorrect device address in response for "REQ_UD2" message
131086 - message "SND_UD slave selection" was not send in defined time interval
131087 - message "SND_UD slave selection" was not send in defined time interval
131088 - timeout - receiving "SND_UD slave selection" message response
131089 - bad frame for "SND_UD slave selection" response message
131090 - message "SND_UD slave selection" was not send in defined time interval during searching slaves on bus
131091 - message "SND_UD slave selection" was not send in defined time interval during searching slaves on bus
131092 - message "REQ_UD2" was not send in defined time interval during searching slaves on bus
131093 - message "REQ_UD2" was not send in defined time interval during searching slaves on bus
131094 - collision of secondary addresses during searching slaves on bus (two or more devices have same secondary address)
131329 - bad first "start" byte for device´s response message
131330 - bad second "start" byte for device´s response message
131331 - bad first "stop" byte for device´s response message
131332 - bad checksum of the response frame
131333 - bad value of the response frame length
131334 - bad value of the response frame length
IEC 62056-21 AMS errors
65536 - internal error
65537 - readout was stopped by user
65538 - bad format address of the device
65539 - not supported character, that describe communication speed in the device answer
65540 - communication port was not set
65541 - timeout - Identification message not arrived
65542 - the device using unsupported AMS mode
65543 - timeout - Acknowledgement/option select message
65544 - speed was not set
65545 - timeout while receiving two consecutive characters of the message
65546 - timeout while receiving two messages
65793 - not supported character in the field "Manufacturer's identification" of received "Identification message"
65794 - not supported character in the field Baud rate identification of received "Identification message"
65795 - not supported character in the field Identification of received "Identification message"
65796 - not supported character in the fields "CR" and "LF" of received "Identification message"
66049 - not supported character in the field "Data block" of received "Data message"
66050 - internal AMS buffer overflow because too long "Data block" of received "Data message"
66051 - not supported character in the fields "CR" and "LF" of received "Data message"
66052 - not supported character in the field "ETX" of received "Data message"
66053 - field "BCC" of received "Data message" is not equal to calculated check character
65537 - readout was stopped by user
65538 - bad format address of the device
65539 - not supported character, that describe communication speed in the device answer
65540 - communication port was not set
65541 - timeout - Identification message not arrived
65542 - the device using unsupported AMS mode
65543 - timeout - Acknowledgement/option select message
65544 - speed was not set
65545 - timeout while receiving two consecutive characters of the message
65546 - timeout while receiving two messages
65793 - not supported character in the field "Manufacturer's identification" of received "Identification message"
65794 - not supported character in the field Baud rate identification of received "Identification message"
65795 - not supported character in the field Identification of received "Identification message"
65796 - not supported character in the fields "CR" and "LF" of received "Identification message"
66049 - not supported character in the field "Data block" of received "Data message"
66050 - internal AMS buffer overflow because too long "Data block" of received "Data message"
66051 - not supported character in the fields "CR" and "LF" of received "Data message"
66052 - not supported character in the field "ETX" of received "Data message"
66053 - field "BCC" of received "Data message" is not equal to calculated check character
Inputs AMS errors
8388608 - non specific error (internal error of module)
8388609 - readout was stopped by user
8388610 - bad format address of the device
8388611 - timeout (message was not sent in defined time)
8388612 - timeout (message was not sent in defined time)
8388613 - timeout - receiving message response
8388865 - bad frame in answer message
8388866 - bad sequential number of the frame
8388867 - answer is too log (not enough space for this frame in internal AMS memory)
8388868 - bad CRC
8388869 - bad value in sync. field
8388609 - readout was stopped by user
8388610 - bad format address of the device
8388611 - timeout (message was not sent in defined time)
8388612 - timeout (message was not sent in defined time)
8388613 - timeout - receiving message response
8388865 - bad frame in answer message
8388866 - bad sequential number of the frame
8388867 - answer is too log (not enough space for this frame in internal AMS memory)
8388868 - bad CRC
8388869 - bad value in sync. field
Pseudo AMS errors - ONF
65280 - non specific error (internal error of module)
65281 - user set more M-Bus slave devices, that can be handled by AMS functionality
65282 - error appeared during slave detection on M-Bus
65283 - error appeared during reading results of detected slave M-Bus devices
65284 - unsuccesful deleting devices from AMS table
65285 - error - parsing of detected slave units on M-Bus
65286 - user defined difrerent number slave units, that were detected on M-Bus
65287 - detected M-Bus unit cannot be add AMS table
65288 - SMS message limit
65281 - user set more M-Bus slave devices, that can be handled by AMS functionality
65282 - error appeared during slave detection on M-Bus
65283 - error appeared during reading results of detected slave M-Bus devices
65284 - unsuccesful deleting devices from AMS table
65285 - error - parsing of detected slave units on M-Bus
65286 - user defined difrerent number slave units, that were detected on M-Bus
65287 - detected M-Bus unit cannot be add AMS table
65288 - SMS message limit