# Timeout Tag OPC **URL:** \ **Category:** Ignition\ **Tags:** vision, ignition81\ **Created:** [February 17, 2026, 7:58pm UTC](https://forum.inductiveautomation.com/t/timeout-tag-opc/114014 "2026-02-17T19:58:44Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![gustavo.chamorro](https://avatars.discourse-cdn.com/v4/letter/g/eb8c5e/32.png) [@gustavo.chamorro](https://forum.inductiveautomation.com/u/gustavo.chamorro)\ **Post date:** [February 17, 2026, 7:58pm UTC](https://forum.inductiveautomation.com/t/timeout-tag-opc/114014/1 "2026-02-17T19:58:44Z")
Hello everyone, I am working on a project where my PLC is quite far from where my supervisor is installed, so to establish communication we are using radios and the Modbus TCP protocol. It is working, but not 100% as we would like. From time to time, some packets are lost and my templates turn red. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/f/ef3bd65eb0d3161bd6c348d98738dc7a570b72ab.png) First, I would like to know if it is possible to remove this red color. Second, how can I increase the time that the OPC tag remains green? For example, only after 2 minutes without communication will the tag turn red. ---
**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\ **Post date:** [February 17, 2026, 8:25pm UTC](https://forum.inductiveautomation.com/t/timeout-tag-opc/114014/2 "2026-02-17T20:25:28Z")
> [@gustavo.chamorro](#): > > remove this red color. In the binding configurations in the templates, select the [`Overaly Opt-out`](https://www.docs.inductiveautomation.com/docs/8.3/platform/tags/quality-codes-and-overlays#overlay-opt-out) option. > [@gustavo.chamorro](#): > > radios and the Modbus TCP protocol. Polling based protocols over a slow connection is not recommended, look into something like MQTT which is much better suited for low bandwidth connections. If you are dead set on modbus, adjust your timeout settings for the device connection on the gateway. ---
**Author:** ![gustavo.chamorro](https://avatars.discourse-cdn.com/v4/letter/g/eb8c5e/32.png) [@gustavo.chamorro](https://forum.inductiveautomation.com/u/gustavo.chamorro)\ **Post date:** [February 17, 2026, 9:10pm UTC](https://forum.inductiveautomation.com/t/timeout-tag-opc/114014/3 "2026-02-17T21:10:37Z")
Using Overaly worked here, Ryan, thank you very much! Is there another place where I can configure this read timeout to fail, other than here in device connections? I don't want to change this timeout here. ![Captura de tela 2026-02-17 175412](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/e/2e5bf827fe52dd501816c15b04741fcaa3c69b82.png) ---
**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\ **Post date:** [February 17, 2026, 9:16pm UTC](https://forum.inductiveautomation.com/t/timeout-tag-opc/114014/4 "2026-02-17T21:16:35Z")
That's the only one. I'm also curious, what is your device load showing under the Devices \> YourDeviceName \> Details screen? ---
**Author:** ![gustavo.chamorro](https://avatars.discourse-cdn.com/v4/letter/g/eb8c5e/32.png) [@gustavo.chamorro](https://forum.inductiveautomation.com/u/gustavo.chamorro)\ **Post date:** [February 18, 2026, 2:53pm UTC](https://forum.inductiveautomation.com/t/timeout-tag-opc/114014/5 "2026-02-18T14:53:46Z")
Would you like to see this screen? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/0/b02044aab3edf53c2e48dc8442ac1d53fd28a33f.png) ---
**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\ **Post date:** [February 18, 2026, 5:11pm UTC](https://forum.inductiveautomation.com/t/timeout-tag-opc/114014/6 "2026-02-18T17:11:00Z")
No, I'm looking for the Status \> Connection \> Devices screen, should look like ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/9/e93f4f6d38f950d1496ade04b4f011c713d52651.png) I was interested to see if your device had any overload. I think your main issue is using a latency sensitve protocol over a slow connection. ---
**Author:** ![gustavo.chamorro](https://avatars.discourse-cdn.com/v4/letter/g/eb8c5e/32.png) [@gustavo.chamorro](https://forum.inductiveautomation.com/u/gustavo.chamorro)\ **Post date:** [February 20, 2026, 5:25pm UTC](https://forum.inductiveautomation.com/t/timeout-tag-opc/114014/7 "2026-02-20T17:25:08Z")
Yes... I'm testing other parts of the software here on the workbench and it's overloaded. When I'm in the field with the radio, I'll see how it is there. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/e/de116cf6d5909434a7e361c750b2493ac1c9ebc4.png) ---
**Author:** ![gustavo.chamorro](https://avatars.discourse-cdn.com/v4/letter/g/eb8c5e/32.png) [@gustavo.chamorro](https://forum.inductiveautomation.com/u/gustavo.chamorro)\ **Post date:** [February 20, 2026, 6:14pm UTC](https://forum.inductiveautomation.com/t/timeout-tag-opc/114014/8 "2026-02-20T18:14:30Z")
When I increase Concurrent Requests from 1 to 16, it improves significantly, but I'm not sure if it's advisable to do so. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/f/9f2bfd18206e6ff4b1a03895b1bb1dfe53405199.png) ![Captura de tela 2026-02-20 143328](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/c/5c27ebac277db17ee754e91bdaade2987aadd729.png) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 20, 2026, 6:17pm UTC](https://forum.inductiveautomation.com/t/timeout-tag-opc/114014/9 "2026-02-20T18:17:20Z")
It's fine on the Ignition side of things. It's unusual for a Modbus device to support so many concurrent requests... and if you're not currently communicating over the radio you mentioned I wouldn't be surprised if it failed spectacularly when you start.