# Modbus connection time out - Readings goes Red

**URL:** <https://forum.inductiveautomation.com/t/modbus-connection-time-out-readings-goes-red/101329>\
**Category:** Ignition\
**Tags:** python, scripting, ignition81, perspective\
**Created:** [January 24, 2025, 7:07am UTC](https://forum.inductiveautomation.com/t/modbus-connection-time-out-readings-goes-red/101329 "2025-01-24T07:07:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Filippos\_Onisiforou](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/filippos_onisiforou/32/68090_2.png) [@Filippos\_Onisiforou](https://forum.inductiveautomation.com/u/Filippos_Onisiforou)\
**Post date:** [January 24, 2025, 7:07am UTC](https://forum.inductiveautomation.com/t/modbus-connection-time-out-readings-goes-red/101329/1 "2025-01-24T07:07:33Z")

</div>

Hi Guys , we have an old PV - plant we want to monitor with a ABB VSN700 and we are facing a small issue with the modbus connection everywhile we get a timeout error and everything goes in Red . Is there a way to eliminate this ?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/b/2b679e4107cb533d38e22990189409fe7a887431.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/3/f34eb6d8a8b25ceff1f47844b6c2a1f8755d4f6a.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/0/f0bd356ab8a7961eed7e04f8f183047e2a674832.png)

---

<div class="post-metadata">

**Author:** ![MG3](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mg3/32/84125_2.png) [@MG3](https://forum.inductiveautomation.com/u/MG3)\
**Post date:** [January 24, 2025, 11:22am UTC](https://forum.inductiveautomation.com/t/modbus-connection-time-out-readings-goes-red/101329/2 "2025-01-24T11:22:34Z")

</div>

This seems like a Modbus issue, rather than an Ignition issue. Are you using Modbus Serial or TCP? If Serial, I'd definitely recommend creating a **TagGroup** at different time intervals (for metering I typically use 3-10s - 3000-10000ms) and see if that makes a difference. If it's a TCP then 1000ms should be okay.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/8/f8bbba6b32badc1946a25df3d04448066b7f0774.png)

If this is a solution that is being tried, I'd recommend first just doing it on a few tags and seeing if they remain good quality and updating whilst the other tags don't.

I should have also asked this at the start but have you tried using a Modbus Scanner (such as ModScan) to ensure that this dropout isn't just the Modbus Connection?

---

<div class="post-metadata">

**Author:** ![Filippos\_Onisiforou](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/filippos_onisiforou/32/68090_2.png) [@Filippos\_Onisiforou](https://forum.inductiveautomation.com/u/Filippos_Onisiforou)\
**Post date:** [January 24, 2025, 12:03pm UTC](https://forum.inductiveautomation.com/t/modbus-connection-time-out-readings-goes-red/101329/3 "2025-01-24T12:03:40Z")

</div>

Its still the same , the problem is that these inverters are old . The only solution is to use a buffer device in the middle a PLC for example to Pull the values from inverters then place them on Memory words or Registers for Example.

---

<div class="post-metadata">

**Author:** ![MG3](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mg3/32/84125_2.png) [@MG3](https://forum.inductiveautomation.com/u/MG3)\
**Post date:** [January 24, 2025, 12:24pm UTC](https://forum.inductiveautomation.com/t/modbus-connection-time-out-readings-goes-red/101329/4 "2025-01-24T12:24:44Z")

</div>

Sorry, for clarification was this error spawning from the ABB VSN700 or the Inverters?
