MB_ErrorCodes (ENUM)¶
TYPE MB_ErrorCodes :
- InOut:
- Name - Initial - Comment - RESPONSE_SUCCESS - 16#0 - Everything OK - ILLEGAL_FUNCTION - 16#1 - Slave does not support the function code - ILLEGAL_DATA_ADDRESS - 16#2 - Slave does not support this register offset - ILLEGAL_DATA_VALUE - 16#3 - The value to be written is not valid - SLAVE_DEVICE_FAILURE - 16#4 - Unrecoverable error while performing the request - ACKNOWLEDGE - 16#5 - Notification of a Slave that a lengthy operation being started - SLAVE_DEVICE_BUSY - 16#6 - Notification of a Slave that a lengthy operation is in progress - MEMORY_PARITY_ERROR - 16#8 - Special error for function code 20, 21 - 16#A - Special error when using devices behind a gateway (Gateway misconfigured/busy) - GATEWAY_DEVICE_FAILED_TO_RESPOND - 16#B - Special error when using devices behind a gateway (Device does not respond) - RESPONSE_TIMEOUT - 16#A1 - There was no response in time - RESPONSE_CRC_FAIL - 16#A2 - The checksum of the response is not correct - RESPONSE_WRONG_SLAVE - 16#A3 - The response is not from the expected Slave - RESPONSE_WRONG_FUNCTIONCODE - 16#A4 - The response is not the expected function code - REQUEST_FAILED_TO_SEND - 16#A5 - Local COM Port error. Request was not sent - RESPONSE_INVALID_DATA - 16#A6 - The response contains invalid data - RESPONSE_INVALID_PROTOCOL - 16#A7 - The response is not modbus protocol - RESPONSE_INVALID_HEADER - 16#A8 - Any field of Modbus MBAP (Protocoll, Length) header is invalid - INVALID_PARAMETER - 16#A9 - Any input parameter of the operation is invalid (e.g. data- pointer is not set or FC is not supported by Modbus stack - UNDEFINED - 16#FF - The request’s result is undefined or not yet known, e.g. initial state