Fieldgate FXA42
Operation
Hauser
77
Error code
Description
-2
Could not open TCP socket.
-3
Could not switch TCP socket to blocking mode.
-4
Unable to establish the TCP connection.
-5
Setting options on TCP socket failed.
Contact customer support if an error code is displayed that is not listed here.
Could not read/write from/to TCP device at <IP address>:<port> (unit: <unit
identifier>, function code: <function code>, address: <address>, quantity: <quantity>,
result code: <result code>, error code: <error code>, exception code: <exception
code>)
The driver could not read a value from the Modbus TCP server with the IP address and port
indicated or write a value to the Modbus TCP server. This value is identified by the Modbus
function code used, its address (starting from 0) and the quantity of registers or coils. The
message also shows a result code, an error code from the TCP/IP stack and a Modbus
exception code. Documentation on Modbus exception codes is provided in the Modbus
application protocol specification. The following table shows the possible result codes:
Result code Description
-1
Waiting for server response timed out. Either the server is not available or you should increase
the timeout.
-2
Received invalid packet (protocol error).
-5
TCP/IP error
Contact customer support if an error code is displayed that is not listed here.
Read illegal floating point value from TCP device at <IP address>:<port> (unit: <unit
identifier>, function code: <function code>, address: <address>, quantity: <quantity>)
The driver read an illegal floating point value from the Modbus TCP server with the IP
address and port indicated. This value is identified by the Modbus function code used to
read it, its address (starting from 0) and the quantity of registers or coils.
Could not read/write from/to RTU device <device address> (function code: <function
code>, address: <value address>, quantity: <quantity>, result code: <result code>,
exception code: <exception code>)
The driver failed to read/write a value from/to the Modbus RTU slave with the address
indicated. The corresponding value is identified by the Modbus function code used to read/
write it, its address (starting from 0) and the quantity of registers/coils. The message also
shows a result code and a Modbus exception code. For documentation on Modbus
exception codes please refer to the Modbus application protocol specification. The
following table shows the possible result codes:
Result code Description
-1
Waiting for slave response timed out. Either the slave is not available or you should increase the
timeout.
-2
Received invalid packet (checksum error).
-3
Sending request failed.
Contact customer support if an event code is displayed that is not listed here.
