Hello,
Recently, my modbus-node (modbus-write-buffer & modbus-flex-getter) have been throwing these errors that I cannot figure out why.
Here is the current settings for the nodes:
Here is the error occurring intermittently:
2/8/2022, 4:30:57 PMnode: VFD MODBUS
msg : string[123]
"Client -> fsm failed state after sending Get More About It By Logging Serial@/dev/ttySerMod0.0:9600bit/s default Unit-Id: 1"
2/8/2022, 4:31:42 PMnode: VFD MODBUS
msg : string[122]
"Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttySerMod0.0:9600bit/s default Unit-Id: 1"
2/8/2022, 4:31:42 PMnode: VFD MODBUS
msg : string[125]
"Client -> fsm reconnect state after broken Get More About It By Logging Serial@/dev/ttySerMod0.0:9600bit/s default Unit-Id: 1"
2/8/2022, 4:31:44 PMnode: VFD MODBUS
msg : string[97]
"Client -> fsm init state after reconnecting Serial@/dev/ttySerMod0.0:9600bit/s default Unit-Id: 1"
2/8/2022, 4:24:49 PM node: VFD MODBUS
msg : string[83]
"Client -> fsm init in 2000 ms Serial@/dev/ttySerMod0.0:9600bit/s default Unit-Id: 1"
2/8/2022, 4:31:46 PMnode: VFD MODBUS
msg : string[125]
"Client -> fsm connected after state opened Get More About It By Logging Serial@/dev/ttySerMod0.0:9600bit/s default Unit-Id: 1"
Restarting node-red or redeploying sometimes causes the errors to pause. However, they always start again. It does not seem to be every inject it happens, just sometimes. I started with the Que Delay @ 1 ms, and have increased it to 20, then 40 ms, and the issue still occurs.
Currently running Node-Red v1.03 and node-red-contrib-modbus v5.16.0.
I am using Node-Red with a Opto 22's groov Epic.
