modbus_reply_exception(3)

modbus_reply_exception3

Send an exception response

Usage

*int modbus_reply_exception(modbus_t *ctx, const uint8_t *req, unsigned int exception_code);

Overview

The modbus_reply_exception() function shall send an exception response based on the exception_code in argument.

The libmodbus provides the following exception codes:

• MODBUS_EXCEPTION_ILLEGAL_FUNCTION (1)

• MODBUS_EXCEPTION_ILLEGAL_DATA_ADDRESS (2)

• MODBUS_EXCEPTION_ILLEGAL_DATA_VALUE (3)

• MODBUS_EXCEPTION_SLAVE_OR_SERVER_FAILURE (4)

• MODBUS_EXCEPTION_ACKNOWLEDGE (5)

• MODBUS_EXCEPTION_SLAVE_OR_SERVER_BUSY (6)

• MODBUS_EXCEPTION_NEGATIVE_ACKNOWLEDGE (7)

• MODBUS_EXCEPTION_MEMORY_PARITY (8)

• MODBUS_EXCEPTION_NOT_DEFINED (9)

• MODBUS_EXCEPTION_GATEWAY_PATH (10)

• MODBUS_EXCEPTION_GATEWAY_TARGET (11)

The initial request req is required to build a valid response.

Return value

The function shall return the length of the response sent if successful. Otherwise it shall return -1 and set errno.

Errors

EINVAL

The exception code is invalid

Releases

6 releases since Debian 7 (Wheezy); the text changed 5 times.

  1. 7
  2. 8
  3. 9
  4. 10
  5. 11
  6. 12

Authors

The libmodbus documentation was written by Stéphane Raimbault <[email protected]>

From libmodbus-dev 3.1.6-2.1 in Debian 12 (Bookworm). Parsed by carta from the page's man source.