# Slow Response from Devices on Modbus RS485 Network

**URL:** <https://forum.inductiveautomation.com/t/slow-response-from-devices-on-modbus-rs485-network/98168>\
**Category:** Ignition\
**Tags:** modbus, ignition81\
**Created:** [November 5, 2024, 12:28am UTC](https://forum.inductiveautomation.com/t/slow-response-from-devices-on-modbus-rs485-network/98168 "2024-11-05T00:28:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sameer\_Ambegaonkar](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Sameer\_Ambegaonkar](https://forum.inductiveautomation.com/u/Sameer_Ambegaonkar)\
**Post date:** [November 5, 2024, 12:28am UTC](https://forum.inductiveautomation.com/t/slow-response-from-devices-on-modbus-rs485-network/98168/1 "2024-11-05T00:28:09Z")

</div>

Have issue in response time, reading from power meters connected over RS485 network in Ignition (8.1.42). 14 meters connected over RS485 -\> gateway -\> Ignition modbus TCP OPC.

Good meters - Switched on  
Bad meters - Switched off

Now when:

1. When all meter devices are enabled in Ignition - Response time is slow for good meters and quality of all meter tags is good.
2. When bad meters are disabled in Ignition - Response time is fast for good meters and quality of all meter tags is good.

Ignition is slowing down reading of modbus tags when bad meters are enabled. Playing around with settings, highlighted in 'red' in the screenshots.

What could be the ways to improve the response time when all meters are enabled in Ignition? Appreciate any help..

 ![Meter](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/4/04ea653b74438cf8d9a1a7ecce02a489c786fb93.png)  
 ![Modbus3](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/8/3899cb6389fbacfc0812ed24e490f09a38b18670.png)  
 ![Modbus Settings](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/9/c9f8eef6c06a07bf10f10374bf6a816385306a67.png)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 5, 2024, 2:09pm UTC](https://forum.inductiveautomation.com/t/slow-response-from-devices-on-modbus-rs485-network/98168/2 "2024-11-05T14:09:21Z")

</div>

1. Modbus on serial or RS-485 is fundamentally slow. You show a baud rate of 9600. That's going to kill performance, even in the best circumstances.

2. RS-485 is a shared bus. Only one device can be interrogated at a time. If it doesn't respond (there's a timeout setting you can adjust), all the other devices must wait. This is also fundamental to shared busses.

3. IA's driver will keep sending all requests for a poll group to a broken device, despite the failures. My alternate driver short-circuits this, failing all pending requests to a particular slave when a request times out. Speeding up access to the other devices. You might get acceptable performance by switching drivers.

---

<div class="post-metadata">

**Author:** ![Sameer\_Ambegaonkar](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Sameer\_Ambegaonkar](https://forum.inductiveautomation.com/u/Sameer_Ambegaonkar)\
**Post date:** [November 5, 2024, 10:48pm UTC](https://forum.inductiveautomation.com/t/slow-response-from-devices-on-modbus-rs485-network/98168/3 "2024-11-05T22:48:25Z")

</div>

@pturmel Thanks for reply.

I hope this is not standard behaviour with RS485 devices in Ignition.  
Let me try increasing the baud rate and check for any improvements.

Didn't completely get about the alternate driver and switching drivers. How do I achieve this in Ignition?

---

<div class="post-metadata">

**Author:** ![jay](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@jay](https://forum.inductiveautomation.com/u/jay)\
**Post date:** [November 5, 2024, 11:11pm UTC](https://forum.inductiveautomation.com/t/slow-response-from-devices-on-modbus-rs485-network/98168/4 "2024-11-05T23:11:03Z")

</div>

Also set the Max Retry Count to 0. Set the timeout on your Modbus gateway to the lowest value that work reliably, maybe ~100ms at 19.2kbaud.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 6, 2024, 2:56am UTC](https://forum.inductiveautomation.com/t/slow-response-from-devices-on-modbus-rs485-network/98168/5 "2024-11-06T02:56:07Z")

</div>

> [@Sameer\_Ambegaonkar](#):
>
> not standard behaviour with RS485 devices

It is, typically, whether Ignition or not.

> [@Sameer\_Ambegaonkar](#):
>
> switching drivers

> [@Automation Professionals' Advanced Modbus Driver](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312):
>
> Automation Professionals is pleased to announce the first beta for its Advanced Modbus Driver, for Ignition version 7.9. Key features: Server mode, emulating one or more slave [devices](https://www.automation-pros.com/modbus/UserManual.pdf), using any of the three typical connection types, including simultaneous connections of multiple types. Client mode, incorporating all three connection modes in one driver. Support for Modbus Function Codes 20 and 21, File Records. Configure protocol tweaks for troublesome devices per slave unit, enabling suppor…
