# Browsing device for tags PLC 5 - 'Loading' then times out

**URL:** <https://forum.inductiveautomation.com/t/browsing-device-for-tags-plc-5-loading-then-times-out/106047>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 8, 2025, 1:50pm UTC](https://forum.inductiveautomation.com/t/browsing-device-for-tags-plc-5-loading-then-times-out/106047 "2025-05-08T13:50:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeff.ryan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jeff.ryan/32/25543_2.png) [@jeff.ryan](https://forum.inductiveautomation.com/u/jeff.ryan)\
**Post date:** [May 8, 2025, 1:50pm UTC](https://forum.inductiveautomation.com/t/browsing-device-for-tags-plc-5-loading-then-times-out/106047/1 "2025-05-08T13:50:33Z")

</div>

This is Ignition 8.1.47. I'm connected to 'many' older PLC 5 devices. When I do a 'browse devices' to browse to an OPC tag for these devices, upon clicking the browse, it will 'spin' for a long time, saying 'Loading', eventually timing out, to the point of sometimes disconnecting my client. But then when I go to browse immediately subsequent , all of the available tags immediately show available and I can generally communicate send data to/from without incident.  
Should I just increase the time out of the device? I've increased it from the standard of 2000 to 3000 already. Is there some other setting that would assist. These PLC 's are on DH+ networks available through an ethernet (ENBT) card, where the Ignition gateway is communicating to them . I can provide any other information that is helpful. Thanks much.

 ![PLC5](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/7/d77b31ba8dc4dc26c6cc46f9e8b03308446ebd40.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:** [May 8, 2025, 1:54pm UTC](https://forum.inductiveautomation.com/t/browsing-device-for-tags-plc-5-loading-then-times-out/106047/2 "2025-05-08T13:54:17Z")

</div>

> [@jeff.ryan](#):
>
> These PLC 's are on DH+ networks

You should avoid browsing across DH+ entirely, especially when production is running. If you must, use the gateway quick client to initiate the first browse, to avoid killing your designer.

---

<div class="post-metadata">

**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:** [May 8, 2025, 2:01pm UTC](https://forum.inductiveautomation.com/t/browsing-device-for-tags-plc-5-loading-then-times-out/106047/3 "2025-05-08T14:01:34Z")

</div>

If the program in these is never changing you could set that "Browse Cache Timeout" setting to something like `2147483647` so it never expires.

edit: looks like it might also just accept -1 or any negative value as disabled / never expired.

---

<div class="post-metadata">

**Author:** ![jeff.ryan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jeff.ryan/32/25543_2.png) [@jeff.ryan](https://forum.inductiveautomation.com/u/jeff.ryan)\
**Post date:** [May 8, 2025, 6:41pm UTC](https://forum.inductiveautomation.com/t/browsing-device-for-tags-plc-5-loading-then-times-out/106047/4 "2025-05-08T18:41:15Z")

</div>

@pturmel , @Kevin.Herron , thanks for both advice. The -1 in 'browse cache timeout' worked like magic. it is instantaneous now. I startup/development mode for a little while longer and then shouldn't have to browse them too much anymore. Thanks again.