Modbus error/exception codes FX30(s) Octave

IoT Gateways FX30
1

Hello All,

my external application needs to analyze logread messages from the FX30 device via SSH connection, namely, it needs to watch for Modbus error codes.
For instance I noticed when RTU unit is not connected there is a timeout message like this

May 17 15:37:50 fx30s user.err Legato: =ERR= | modbus[1653]/components T=main | mbrSlave.c mbr_SlaveRegistersRead() 112 | Failed to read from UART1/UNIT2 (addr 00002) exception -110 (Connection timed out)

it’s clear for timeout there is code -110.
Could you please disclose the list of all possible codes and their description?

Thanks

2

Hello Alex,

the possible error codes are the following:

ECONNREFUSED 111 /* Connection refused /
ECONNRESET 104 / Connection reset by peer /
EINVAL 22 / Invalid argument /
EREMOTEIO 121 / Remote I/O error /
EIO 5 / I/O error /
ENOMEM 12 / Out of memory /
ENOPROTOOPT 92 / Protocol not available /
ETIMEDOUT 110 / Connection timed out /
ENOTSUP 252 / Function not implemented */

3

Hi @amons , thanks for reply!
We noticed error 12 was about invalid CRC

“error”:{
“errno”:12,
“errstr”:“Invalid CRC”
}

4

We have updated the docs with Modbus specific errors:

1 Like
5

Wonderful! Thank you!

1 Like