# Delay using UDT reference tags

**URL:** <https://forum.inductiveautomation.com/t/delay-using-udt-reference-tags/80616>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [October 17, 2023, 8:26pm UTC](https://forum.inductiveautomation.com/t/delay-using-udt-reference-tags/80616 "2023-10-17T20:26:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Italo\_Saavedra](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/italo_saavedra/32/36627_2.png) [@Italo\_Saavedra](https://forum.inductiveautomation.com/u/Italo_Saavedra)\
**Post date:** [October 17, 2023, 8:26pm UTC](https://forum.inductiveautomation.com/t/delay-using-udt-reference-tags/80616/1 "2023-10-17T20:26:24Z")

</div>

Hello, please could you help me about delay when i'm using reading tags.

I have 2 cases:

1.- We're using UDT structure to read completely TAGs from FrontEnd, the delay is 3 seconds aprox. (the delay is present in the Client and Designer testing)

2.- Because we have delay in the first case, we test reading indirect tags (binding indirect tag), but the delay is the same, 3 seconds aprox.

We have exclusived servers for Ignition TAGs (1st server with Kepserver), another for Ignition FrontEnd (2nd server)  
The tags come from ControlLogix PLC (L85)

But, we couldn't find the problem

Anybody knows why could the delay happen?

thank you very much

---

<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 17, 2023, 9:13pm UTC](https://forum.inductiveautomation.com/t/delay-using-udt-reference-tags/80616/2 "2023-10-17T21:13:21Z")

</div>

Did you check your Class 3 Communications utilization on the L85's built-in web page?

When you say you have two servers, do you mean Kepware and a native Ignition driver are **both** pointing at the same PLC? (That can double the workload on the PLC, making it impossible to share data.)

Consider reading this topic and its inner linked topics:

> [@Ignition & Logix Best Practice Tips for better communications](https://forum.inductiveautomation.com/t/ignition-logix-best-practice-tips-for-better-communications/60386):
>
> Hi All, After a whole bunch of issues I have gone down the rabbit hole of what is wrong with our setup on site. I will preface this by saying I a relatively new to all of this… so be gentle stuck_out_tongue Based on much reading(such wow) I believe I have a list of things our site could take away for a better system. Some of them are easy to implement, whilst some of them need… significant work to realize. Especially the AOI approach in point 5 expressionless Before going too far and up…

---

<div class="post-metadata">

**Author:** ![Italo\_Saavedra](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/italo_saavedra/32/36627_2.png) [@Italo\_Saavedra](https://forum.inductiveautomation.com/u/Italo_Saavedra)\
**Post date:** [October 18, 2023, 11:41am UTC](https://forum.inductiveautomation.com/t/delay-using-udt-reference-tags/80616/3 "2023-10-18T11:41:27Z")

</div>

thanks for your help...

Let me see it to test that solution.

Refering to your question, Ignition is only connected to Kepserver, it is not connected to PLC directly.

Atte.

Ítalo

---

<div class="post-metadata">

**Author:** ![Italo\_Saavedra](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/italo_saavedra/32/36627_2.png) [@Italo\_Saavedra](https://forum.inductiveautomation.com/u/Italo_Saavedra)\
**Post date:** [October 20, 2023, 11:26am UTC](https://forum.inductiveautomation.com/t/delay-using-udt-reference-tags/80616/4 "2023-10-20T11:26:19Z")

</div>

Hello again Phil, thanks for your help...

I was reviewing the PLC performance but I couldn't find anything problem...

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/5/e5aeb1585d1a83178277b5f25acec74108f234b8.png)

With my team were testing the reading of tags, but the problem is present only we want to open a window (popup with udt parameters or indirect binding), because if we are working directly (with the same udt parameter tags) over the popup, updating values or similar actions, the tags are perfect, without delay.

The structure of our systems is:

Ignition Backend: exclusive server for it, and connected in the same machine to Kepware.  
Ignition FrontEnd: exclusive server for it, and connected to Ignition Backend.  
Only the Kepware is connected to PLC ControlLogix L85.

If somebody could help us, we apretiate that...

---

<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:** [October 20, 2023, 11:38am UTC](https://forum.inductiveautomation.com/t/delay-using-udt-reference-tags/80616/5 "2023-10-20T11:38:23Z")

</div>

There isn't much reason to have a separate backend server if all your tags come from Kepware. Some of the delay is probably coming from the Gateway Network / Remote Tag Provider between frontend/backend.

---

<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 20, 2023, 12:41pm UTC](https://forum.inductiveautomation.com/t/delay-using-udt-reference-tags/80616/6 "2023-10-20T12:41:52Z")

</div>

> [@Italo\_Saavedra](#):
>
> Only the Kepware is connected to PLC

I don't use Kepware enough to help further.
