Thank you for your answers .
I manage to read the 1st address but when I want to read all the addresses it doesn't work anymore.
1st address reading
reading 16 address
and the log .
4 May 20:21:20 - [info] Started modified nodes
4 May 20:21:20 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"d02b2428254038460c7f078a0c0272b1"},"retain":true}
contribModbus:core:client Client -> {"info":"pushed to Queue by Unit-Id","message":{"unitid":1,"fc":3,"address":0,"quantity":16,"messageId":"5eb05d24b453533edb098db3","emptyMsgOnFail":true},"unitId":1} Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +17s
contribModbus:core:client Client -> {"info":"queued read msg","message":{"unitid":1,"fc":3,"address":0,"quantity":16,"messageId":"5eb05d24b453533edb098db3","emptyMsgOnFail":true},"state":"connected","queueLength":1} Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +0ms
contribModbus:core:client Client -> queueing Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +1ms
contribModbus:core:client Client -> sending Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +0ms
contribModbus:core:client Client -> {"type":"sequential dequeue command","unitId":1,"isValidUnitId":true,"sendingAllowed":true,"serialSendingAllowed":true} Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +3s
contribModbus:core:client Client -> {"type":"send queue data to Modbus","unitId":1,"queueLength":1,"sendingAllowed":true,"serialSendingAllowed":false} Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +1ms
contribModbus:core:client Client -> {"info":"read msg via Modbus","message":{"unitid":1,"fc":3,"address":0,"quantity":16,"messageId":"5eb05d24b453533edb098db3","emptyMsgOnFail":true},"queueUnitId":1,"timeout":2500,"state":"sending"} Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +0ms
modbus-serial {
modbus-serial action: 'send serial rtu buffered',
modbus-serial data: <Buffer 01 03 00 00 00 10 44 06>,
modbus-serial unitid: 1,
modbus-serial functionCode: 3
modbus-serial } +27s
contribModbus:core:client Client -> {"state":"sending","message":"dequeue command done serial","delay":2500} Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +1ms
modbus-serial {
modbus-serial action: 'receive serial rtu buffered port',
modbus-serial data: <Buffer 01>,
modbus-serial buffer: <Buffer 01>
modbus-serial } +395ms
modbus-serial {
modbus-serial action: 'receive serial rtu buffered port',
modbus-serial data: <Buffer 03 02 00 e1>,
modbus-serial buffer: <Buffer 01 03 02 00 e1>
modbus-serial } +4ms
modbus-serial {
modbus-serial action: 'receive serial rtu buffered port',
modbus-serial data: <Buffer 78 0c>,
modbus-serial buffer: <Buffer 01 03 02 00 e1 78 0c>
modbus-serial } +6ms
contribModbus:core:client Client -> {"info":"queue response activate sending","sendingAllowed":true,"serialSendingAllowed":true,"queueUnitId":1} Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +3s
contribModbus:core:client Client -> sending Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +1ms
modbus-serial modbusErrorHandling:Timed out +22s
contribModbus:core:client Client -> failed Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +0ms
4 May 20:21:29 - [warn] [modbus-client:moxa] Client -> fsm failed state after sending Get More About It By Logging Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1
4 May 20:21:29 - [warn] [modbus-flex-getter:5f019902.1af158] Modbus Failure On State sending Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +1ms
4 May 20:21:29 - [warn] [modbus-client:moxa] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1
contribModbus:core:client Client -> reconnecting Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +0ms
4 May 20:21:29 - [warn] [modbus-client:moxa] Client -> fsm reconnect state after broken Get More About It By Logging Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1
contribModbus:flex:getter Timed out +27s
4 May 20:21:29 - [error] [modbus-flex-getter:5f019902.1af158] Timed out
contribModbus:core Message Not Found undefined +27s
contribModbus:core:client Client -> reconnecting Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +2ms
contribModbus:core:client Client -> init Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +2s
4 May 20:21:31 - [warn] [modbus-client:moxa] Client -> fsm init state after reconnecting Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1
4 May 20:21:31 - [warn] [modbus-client:moxa] Client -> fsm init in 2000 ms Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1
contribModbus:core:client Client -> connection close sent Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +2s
contribModbus:core:client Client -> RTU buffered port serial Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +1ms
contribModbus:core:client Client -> connection closed Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +6ms
contribModbus:core:client Client -> opened Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +47ms
contribModbus:core:client Client -> time to open Unit 1 Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +1s
modbus-serial modbus connection opened +5s
contribModbus:core:client Client -> connected Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1 +1ms
4 May 20:21:34 - [warn] [modbus-client:moxa] Client -> fsm connected after state opened Get More About It By Logging Serial@/dev/ttyr00:9600bit/s default Unit-Id: 1
an idea of what can go wrong?