Supported Exception Codes - Siemens SIRIUS 3RW5 Equipment Manual

7.3.2

Supported Exception Codes

Exception Code Meaning in
accordance
with Modbus
specification
1 (= 0x01) Illegal function
2 (= 0x02) Illegal data
address
3 (= 0x03) Illegal data
value
4 (= 0x04) Failure in
associated
device
6 (= 0x06) Busy, rejected
message
Note
TIA Portal
Note that the TIA portal does not support all Exception Codes. Unsupported Exception
Codes are detected and evaluated as Exception Code 0x03. You will find further information
in the online help for the TIA Portal.
SIRIUS 3RW5 Modbus communication module
Equipment Manual, 03/2020, A5E43676481002A/RS-AC/003
Cause Brief description
Impermissible The requested Function Code is
Function Code not supported. Pay particular
attention to chapter Function
Codes (Page 98).
Impermissible bit Address does not exist. For
and register functions that work with an
address in the addressing range, all addresses
Modbus TCP affected by the request are
server or checked.
Modbus RTU
slave
Impermissible The number of addresses is not
data value in the correct. The number of
Modbus TCP parameters for the requested
server or function was too high (or 0)
Modbus RTU
slave
Internal error in There is an unspecified error in
the Modbus TCP the Modbus TCP server or
server or Modbus RTU slave that
Modbus RTU prevented execution of the
slave request.
Modbus TCP The device is busy and unable
server or to process the request at this
Modbus RTU time.
slave is not ready
to receive
Messages and diagnostics
7.3 Exception Codes
Example
The Function Code 43 was
requested. The 3RW5 Modbus
communication modules do not
support the Function Code 43.
Request for reading the register
with address 0x7000. The
register address 0x7000 is not
defined for 3RW5 Modbus
communication modules.
Request for writing the register
with address 0xA102 with the
value 7 000. The parameter
"Access monitoring time" can
only have the value 5 000
or 10 000.
Error in the 3RW5 soft starter so
that the 3RW5 soft starter
cannot answer the request.
This can occur following a
parameterization operation via
Modbus when the new
parameter values are
transferred to the device.
113