Logic Machine Forum
Modbus errors in the Log - Printable Version

+- Logic Machine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: Gateway (https://forum.logicmachine.net/forumdisplay.php?fid=10)
+--- Thread: Modbus errors in the Log (/showthread.php?tid=954)



Modbus errors in the Log - GenaV - 23.08.2017

Hello!

To LM4 connected 3 fancoil units (serial/chain connection). All 3 devices works perfectly: controlled independently, I see status of devices, temperatures and etc.
But i'm noticed in the log errors tab long list of errors, they appears each few second with message:

Fancoil_g (RTU slave 1) read failed: Operation timed out
Fancoil_k (RTU slave 2) read failed: Operation timed out
Fancoil_s (RTU slave 3) read failed: Operation timed out

Can you tell me the reason of these messages (taking in mind that devices works ok)?


RE: Modbus errors in the Log - admin - 23.08.2017

Try increasing timeout value in device settings, you need to be running latest firmware.


RE: Modbus errors in the Log - GenaV - 24.08.2017

Hi!

Firmware latest, timeout setting was changed, result same - many timeout errors in the log.
Devices works perfectly.


RE: Modbus errors in the Log - admin - 24.08.2017

Maybe you have mapped a coil/register which is not present in the device. By standard device must reply with an error response, but some simply ignore this so a timeout error occurs.


RE: Modbus errors in the Log - GenaV - 28.08.2017

Hi!

Can I upload here json file (just 5 registers) and Modbus description of devices? Can you check json code for errors?


RE: Modbus errors in the Log - admin - 28.08.2017

Sure, no problem


RE: Modbus errors in the Log - GenaV - 29.08.2017

Hi,

Attachments here.


RE: Modbus errors in the Log - admin - 29.08.2017

Set-point datatype should be int16, also value_multiplier should be set to 0.1. You can set bus_datatype to "bool" for on/off switch. Also, it looks like second profile addresses are incorrect, you can write addresses in hex like this, so they match the ones in the docs:
Code:
{ "name": "Summer_set-point_wr", "datatype": "uint16", "type": "register", "address": 0x102D, "writable": 1 }