# Modbus Failure On State sending Get More About It By Logging
**URL:** https://discourse.nodered.org/t/modbus-failure-on-state-sending-get-more-about-it-by-logging/84536
**Category:** General
**Created:** [14 January 2024 17:16 UTC](https://discourse.nodered.org/t/modbus-failure-on-state-sending-get-more-about-it-by-logging/84536 "2024-01-14T17:16:31Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Martin12](https://discourse.nodered.org/u/Martin12)
#### Post date: [14 January 2024 17:16 UTC](https://discourse.nodered.org/t/modbus-failure-on-state-sending-get-more-about-it-by-logging/84536/1 "2024-01-14T17:16:31Z")
I am using a USB to RS485 converter (Waveshare) on my Raspberry Pi 4 to query two power meter (SDM630) via Modbus RTU using the Modbus-Flex-Getter. Everything works fine and stable without any errors over days as long as I don't touch the Flow (and especially the Flex-Getter-Node).
However if I am changing anything in the Flex-Getter-Node or in the Flow which sometimes causes the Flex-Getter-Node to do a reconnect, I get the following error messages:
The only thing I can do to get the Modbus communication working again is to restart Node-Red. It's not a big deal as it works perfectly fine if I don't touch the Flow, it's a somewhat annoying behavior regardless and I don't know where to start to debug this.
Here are my settings:
Raspberry Pi 4
Debian GNU/Linux 11 (bullseye)
Linux: 6.1.21-v8+
Node-Red: 3.1.3
node-red-contrib-modbus: 5.27.2
NodeJs: v20.11.0
---
### Author:  [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [14 January 2024 18:23 UTC](https://discourse.nodered.org/t/modbus-failure-on-state-sending-get-more-about-it-by-logging/84536/2 "2024-01-14T18:23:05Z")
> [@Martin12](#):
>
> NodeJs: v20.11.0
Nodejs version 20 is not listed as tested / compatible with the Modbus nodes and some issue was reported on Github page ([source](https://github.com/BiancoRoyal/node-red-contrib-modbus/issues/416#issuecomment-1774043374))
try downgrading to Node version **18**
* * *
If you want to further test before downgrading nodejs .. try to stop Node-red and run it with command
`DEBUG=contribModbus*,modbus-serial node-red -v`
this will give you a more detailed log in the terminal, of each of the Modbus nodes actions ([source](https://github.com/BiancoRoyal/node-red-contrib-modbus#debug))
---
### Author:  [@Martin12](https://discourse.nodered.org/u/Martin12)
#### Post date: [14 January 2024 18:49 UTC](https://discourse.nodered.org/t/modbus-failure-on-state-sending-get-more-about-it-by-logging/84536/3 "2024-01-14T18:49:52Z")
Downgrading to NodeJS 18 did the trick! Now the Flex-Getter-Node is reconnecting properly without having to restart Node-Red first! Thanks a lot! 🙂
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [28 January 2024 18:50 UTC](https://discourse.nodered.org/t/modbus-failure-on-state-sending-get-more-about-it-by-logging/84536/4 "2024-01-28T18:50:44Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.