Error being thrown repeatedly: 'FSM Not Ready To Read'

Hello,

In my node-red project, I am relying on the state of a modbus client node to raise a disconnection alert. The modbus client node gets set to an error state very briefly but repeatedly. The error thrown is FSM Not Ready To Read, throw at this line

I did some debugging, and when that error is thrown the state of the FSM is ‘READING’ It is indeed not one of the allowed states: modbus.core.client.messagesAllowedStates = ['ACTIVATED', 'QUEUEING', 'EMPTY']

Is that the expected behavior?

Now, for more details: I am using node-red-contrib-modbus@1.1.0 I am polling 3 modbus programmable logic controllers at an interval of 1 second. I have only had this problem while running my node-red project inside a docker container; I suspect I may have some added latency while reading because of that, but after some testing have found the latency perfectly acceptable (in the order of a few milliseconds). The same project running outside of a container does not throw those errors.

If the error being thrown is the expected behaviour, I’ll have to look at either not relying on the state of the node, or trying to see what could cause a delay with the communication with the physical modbus element.

[Somavaram]

@apanasara Hi, Even I am facing the same problem please let me know if you have found some solution for this. Thank you!

[biancode]

@apanasara Hi, I need some logs please or is it done