Endress+Hauser Cubemass DCI - MODBUS Error Messages

Operation Cubemass DCI MODBUS RS485
38 Endress+Hauser
INTEGER:
STRING:
Illustration using the example of a device parameter with a data length of 18 bytes.
5.4.6 MODBUS error messages
If the MODBUS slave detects an error in the request telegram from the master, it sends a reply to
the master in the form of an error message consisting of the slave address, function code, exception
code and check sum. To indicate that this is an error message, the lead bit of the returned function
code is used. The reason for the error is transmitted to the master by means of the exception code.
The following exception codes are supported by the measuring device:
Selection
Sequence
1st 2nd
1 – 0 – 3 – 2 *
3 – 2 – 1 – 0
Byte 1
(MSB)
Byte 0
(LSB)
0 – 1 – 2 – 3
2 – 3 – 0 – 1
Byte 0
(LSB)
Byte 1
(MSB)
* = Factory setting
MSB = most significant byte
LSB = least significant byte
Selection
Sequence
1st 2nd to 17th 18th
1 – 0 – 3 – 2 *
3 – 2 – 1 – 0
Byte 1 Byte 0
(LSB)
to Byte 17
(MSB)
Byte 16
0 – 1 – 2 – 3
2 – 3 – 0 – 1
Byte 0
(LSB)
Byte 1 to Byte 16 Byte 17
(MSB)
* = Factory setting
MSB = most significant byte
LSB = least significant byte
Exception codes Description
01 ILLEGAL_FUNCTION
The function code sent by the master is not supported by the measuring device (slave).
!
Note!
Description of the function codes supported by the measuring device → ä 35.
02 ILLEGAL_DATA_ADDRESS
The register addressed by the master is not assigned (i.e. it does not exist) or the length of the
requested data is too big.
03 ILLEGAL_DATA_VALUE
• The master is attempting to write to a register which only allows read access.
• The value that appears in the data field is not permitted: e.g. range limits overshot or
incorrect data format.
04 SLAVE DEVICE FAILURE
The slave did not respond to the request telegram from the master or an error occurred when
processing the request telegram.