# Trouble with unreliable modbus-flex-getter

**URL:** https://discourse.nodered.org/t/trouble-with-unreliable-modbus-flex-getter/94843
**Category:** General
**Created:** [23 January 2025 14:01 UTC](https://discourse.nodered.org/t/trouble-with-unreliable-modbus-flex-getter/94843 "2025-01-23T14:01:48Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [25 January 2025 02:02 UTC](https://discourse.nodered.org/t/trouble-with-unreliable-modbus-flex-getter/94843/16 "2025-01-25T02:02:17Z")

</div>

> [@ThingsTinkerer](#):
>
> It sure ain't pretty:

Indeed 😉 .. but why do you have to do this "manual" retry for failed modbus reads ?  
why not just wait for the next request and keep only the successful replies ?  
if 1min is not fast enough just speed up the polling .. every 10sec  
@craigcurtin is polling every 200ms without a hickup.  
Check the communication .. are you using rs485 .. .. are you requesting many registers more than the device can handle ?

* * *

> [@ThingsTinkerer](#):
>
> I want the delay to be a variable depending on the Modbus config node timeout setting.

Its not possible to read the config of another node 👇

> [@Use config node parameter on function node in subflow](https://discourse.nodered.org/t/use-config-node-parameter-on-function-node-in-subflow/89333/3):
>
> Hi, The Function node does not have access to the runtime apis needed to access other nodes and their configuration.

* * *

ps. I opened a new issue on Modbus node's github for the [Empty msg on Modbus fail](https://github.com/BiancoRoyal/node-red-contrib-modbus/issues/517)

---

_[View the full topic](https://discourse.nodered.org/t/trouble-with-unreliable-modbus-flex-getter/94843)._