Auto reconnect upon re-establishing Ethernet connection between Flex server and Flex getter flows?

[niranjanshukla]

Which node-red-contrib-modbus version are you using?

5.30.0

What happened?

I am testing the Modbus Flex Server reading sample flow as a consumer, and Modbus Simple servers as a server flow. Modbus flex server reading is deployed to a R-Pi. Modbus Simple servers is deployed on my windows computer. The R-Pi is connected to Windows computer over Ethernet (with static IPs assigned).

The test works as expected, but when I unplug the Ethernet connection, my Modbus Flex Getter node still shows as "Active", Automatic Read Flex FC3 shows as "Initialized". Subsequently, when I reconnect the Ethernet connection, the state of these nodes does not change and they do not seem to be receiving new data.

Upon unplugging the Ethernet connection, I believe the socket connection is not dropped? Normally, I have to restart my flows to be able to start receiving data. What could be done to receive data again without having to restart the flows?

Server

Modbus-Flex-Server Node (Please attach Script to the next section)

How can this be reproduced?

I am testing the Modbus Flex Server reading sample flow as a consumer, and Modbus Simple servers as a server flow. Modbus flex server reading is deployed to a R-Pi. Modbus Simple servers is deployed on my windows computer. The R-Pi is connected to Windows computer over Ethernet (with static IPs assigned).

The test works as expected, but when I unplug the Ethernet connection, my Modbus Flex Getter node still shows as "Active", Automatic Read Flex FC3 shows as "Initialized". Subsequently, when I reconnect the Ethernet connection, the state of these nodes does not change and they do not seem to be receiving new data.

What did you expect to happen?

No response

Other Information

No response

[github-actions]

This issue is stale because it has been open 60 days with no activity. It will be closed in 30 days, but can be saved by removing the stale label or commenting.