# PLC tags not showing in browser

**URL:** <https://forum.inductiveautomation.com/t/plc-tags-not-showing-in-browser/19966>\
**Category:** Ignition\
**Created:** [October 3, 2018, 7:33pm UTC](https://forum.inductiveautomation.com/t/plc-tags-not-showing-in-browser/19966 "2018-10-03T19:33:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tim](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim/32/3361_2.png) [@Tim](https://forum.inductiveautomation.com/u/Tim)\
**Post date:** [October 3, 2018, 7:33pm UTC](https://forum.inductiveautomation.com/t/plc-tags-not-showing-in-browser/19966/1 "2018-10-03T19:33:58Z")

</div>

With a 1756-L83E/B processor at 28.012 firmware (connected via an in-chassis 1756-EN2T/D at 10.010) Ignition OPC-UA Server would not show tags which were added under an existing UDT array. Tags would also be faulted if the tag name was manually typed into the tag editor. Refreshing the tag provider from the designer did not fix the issue. When the device properties was opened from the Configure section of the gateway and “Save Changes” selected without making any changes the issue was resolved.

Ignition 7.9.9  
OPC-UA 4.9.9  
Logix Driver 3.9.9

---

<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:** [October 3, 2018, 9:24pm UTC](https://forum.inductiveautomation.com/t/plc-tags-not-showing-in-browser/19966/2 "2018-10-03T21:24:24Z")

</div>

In the device’s advanced properties, was Automatic Browse disabled?

---

<div class="post-metadata">

**Author:** ![Tim](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim/32/3361_2.png) [@Tim](https://forum.inductiveautomation.com/u/Tim)\
**Post date:** [October 4, 2018, 12:17pm UTC](https://forum.inductiveautomation.com/t/plc-tags-not-showing-in-browser/19966/3 "2018-10-04T12:17:25Z")

</div>

No, it was on. All properties at default.

---

<div class="post-metadata">

**Author:** ![Tim](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim/32/3361_2.png) [@Tim](https://forum.inductiveautomation.com/u/Tim)\
**Post date:** [December 17, 2018, 5:51pm UTC](https://forum.inductiveautomation.com/t/plc-tags-not-showing-in-browser/19966/4 "2018-12-17T17:51:51Z")

</div>

Same thing today with a 1769-L24ER-QB1B CompactLogix at 28.012 firmware. Still at same Ignition version.

---

<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:** [December 17, 2018, 5:55pm UTC](https://forum.inductiveautomation.com/t/plc-tags-not-showing-in-browser/19966/5 "2018-12-17T17:55:20Z")

</div>

If this happens again search for `ReadBrowseHashRequest` on the log level configuration in the gateway and set it to TRACE. Then edit/save the device connection and get the logs.

My guess right now is that the PLC is simply not changing one of the attributes the Logix5000 Data Access manual says to watch to detect a re-browse is needed.

---

<div class="post-metadata">

**Author:** ![greg.krueger](https://avatars.discourse-cdn.com/v4/letter/g/5f9b8f/32.png) [@greg.krueger](https://forum.inductiveautomation.com/u/greg.krueger)\
**Post date:** [January 28, 2020, 4:15pm UTC](https://forum.inductiveautomation.com/t/plc-tags-not-showing-in-browser/19966/6 "2020-01-28T16:15:29Z")

</div>

We’ve been seeing a similar issue when adding new tags on-line to a ControlLogix PLC. They don’t show up in the OPC browser in Ignition, Automatic browse is turned on for the device.

We’ve been disabling, saving, re-enabling the device in Ignition as a workaround. Will try just doing a re-save in the future.

But wanted to see if anyone did the TRACE logging Kevin mentions above and was able to confirm this is a Rockwell issue with it not setting the attribute properly, or if it’s something on the Ignition end.
