# Query several Modbus meter by RS485 RTU Part 2
**URL:** https://discourse.nodered.org/t/query-several-modbus-meter-by-rs485-rtu-part-2/55268
**Category:** General
**Created:** [16 December 2021 07:38 UTC](https://discourse.nodered.org/t/query-several-modbus-meter-by-rs485-rtu-part-2/55268 "2021-12-16T07:38:54Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Becker](https://discourse.nodered.org/u/Becker)
#### Post date: [16 December 2021 07:38 UTC](https://discourse.nodered.org/t/query-several-modbus-meter-by-rs485-rtu-part-2/55268/1 "2021-12-16T07:38:54Z")
Hi,
on may I´ve asked about querying modbus meters ([Query several Modbus meter by RS485 RTU](https://discourse.nodered.org/t/query-several-modbus-meter-by-rs485-rtu/46478))
now I've finally implemented it with 3 meters:
[SDM.json](https://discourse.nodered.org/uploads/short-url/1ce5TGYEOU9zTDF5oFzOniPu1A7.json) (85.3 KB)
> **[SDM72D Series | Eastron Europe](https://www.eastroneurope.com/products/view/sdm72modbus)**
>
> Three Phase 100A MID (Basic Range)
I just wanted to ask if there is any experience with the most minimal queue delay:
I set it to 5ms. Where is the limit ?
If I connect the query as a loop, I get every second a run.
First I tried without "queue commands" - but so ID2 + ID3 were ignored (not queried).
Greetings.
---
### Author:  [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [16 December 2021 08:32 UTC](https://discourse.nodered.org/t/query-several-modbus-meter-by-rs485-rtu-part-2/55268/2 "2021-12-16T08:32:44Z")
> [@Becker](#):
>
> I set it to 5ms. Where is the limit ?
Hello Becker,
I could be wrong but i dont think the **Queue Delay** matters so much in your configuration .
Wiring the Modbus Read nodes one after the other (which is correct) - when one finishes its Read it will trigger the next. All good .. so you are controlling the "Delay" yourself.
What matters is finding the "sweet spot" with that initial Inject Node that you have set to 2 seconds.
If the whole read process hasnt finished and you start a new Read .. modbus commands could start queuing up. (You can use the **modbus-queue-info** node to monitor the queue if that happens)
---
### Author:  [@hotswapster](https://discourse.nodered.org/u/hotswapster)
#### Post date: [16 December 2021 12:28 UTC](https://discourse.nodered.org/t/query-several-modbus-meter-by-rs485-rtu-part-2/55268/3 "2021-12-16T12:28:06Z")
I've had trouble with this in the past and found it to be dependant on the device that was being polled. Some devices share a processor to deliver this info and others are just plain slow. From memory 2-5 ms has worked well for me in the past.
I just checked my current config which is polling a Huawei inverter and it is set to 1ms. I get errors about every 30 seconds or so with no response from the device. I'm not sure if this is related.
Summary: I think it depends on the devices you're polling.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [14 February 2022 12:28 UTC](https://discourse.nodered.org/t/query-several-modbus-meter-by-rs485-rtu-part-2/55268/4 "2022-02-14T12:28:47Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.