# Where to Configure Tag Update Frequency (Scan Rate) and Use Scan Groups in Ignition 8.3?

**URL:** <https://forum.inductiveautomation.com/t/where-to-configure-tag-update-frequency-scan-rate-and-use-scan-groups-in-ignition-8-3/114086>\
**Category:** Ignition\
**Created:** [February 20, 2026, 10:59am UTC](https://forum.inductiveautomation.com/t/where-to-configure-tag-update-frequency-scan-rate-and-use-scan-groups-in-ignition-8-3/114086 "2026-02-20T10:59:27Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebastien\_ng](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sebastien_ng/32/55297_2.png) [@sebastien\_ng](https://forum.inductiveautomation.com/u/sebastien_ng)\
**Post date:** [February 20, 2026, 10:59am UTC](https://forum.inductiveautomation.com/t/where-to-configure-tag-update-frequency-scan-rate-and-use-scan-groups-in-ignition-8-3/114086/1 "2026-02-20T10:59:27Z")

</div>

Hello everyone,

I am working with **Ignition 8.3** and am having trouble properly configuring the tag update frequency, especially for **Modbus tags**. In previous versions, I was able to configure the **Scan Class** to set the update frequency for tags, but I cannot find this option in **Ignition 8.3**.

Here are my questions:

1. In **Ignition 8.3** , where can I configure the **update frequency (Scan Rate)** for tags (especially Modbus tags)?

2. Should I use **Scan Groups** to manage the tag frequency, and if so, how do I correctly associate a tag with a **Scan Group**?

3. Where exactly is the **frequency property** located in the Ignition 8.3 interface? I’ve looked through the **tag properties** and **Scan Groups** , but I can’t find the exact location.

4. Are there any resources or practical examples for configuring **Scan Groups** and **tag update frequencies** in Ignition 8.3?

Thank you in advance for your help!

---

<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:** [February 20, 2026, 1:02pm UTC](https://forum.inductiveautomation.com/t/where-to-configure-tag-update-frequency-scan-rate-and-use-scan-groups-in-ignition-8-3/114086/2 "2026-02-20T13:02:14Z")

</div>

You’re looking for “Tag Groups” and the Rate property.

> **[Tag Groups | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/platform/tags/tag-groups)**
>
> What Is a Tag Group?

---

<div class="post-metadata">

**Author:** ![sebastien\_ng](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sebastien_ng/32/55297_2.png) [@sebastien\_ng](https://forum.inductiveautomation.com/u/sebastien_ng)\
**Post date:** [February 20, 2026, 1:45pm UTC](https://forum.inductiveautomation.com/t/where-to-configure-tag-update-frequency-scan-rate-and-use-scan-groups-in-ignition-8-3/114086/3 "2026-02-20T13:45:44Z")

</div>

Hello,

Thank you for sharing the documentation; it was really helpful!

I’ve configured the **Scan Rate (Rate)** for my tags in **Ignition** to **200 ms** , but my equipment actually has an acquisition time of **300 ms** instead of 200 ms. The protocol used for data acquisition is **Modbus TCP/IP**.

My question is:

1. **Can adjusting the Rate for all tags to match the equipment’s acquisition time improve data acquisition when handling large volumes of data?**

2. **Are there any performance concerns when setting a fast scan rate (e.g., 200 ms) for multiple tags if the equipment requires a longer acquisition time (300 ms)?**

3. **Is there a recommended strategy for configuring the Rate when collecting large datasets, considering the equipment’s acquisition time?**

---

<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:** [February 20, 2026, 1:54pm UTC](https://forum.inductiveautomation.com/t/where-to-configure-tag-update-frequency-scan-rate-and-use-scan-groups-in-ignition-8-3/114086/4 "2026-02-20T13:54:09Z")

</div>

1. Yes. Attempting to poll faster than the device is internally generating values is pointless and hurts performance.

2. Yes. Attempting to poll faster than the device is internally generating values is pointless and hurts performance.

3. Yes. Poll slower or fewer. Attempting to poll faster than the device is internally generating values is pointless and hurts performance.

4. (You didn't ask a fourth question, but...) Attempting to poll faster than the device can **respond** and **deliver** the values is pointless and hurts (write) performance.

#4 is the bottleneck for most devices.

There's no magic wand in Ignition if the device is the limiting factor.

---

<div class="post-metadata">

**Author:** ![sebastien\_ng](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sebastien_ng/32/55297_2.png) [@sebastien\_ng](https://forum.inductiveautomation.com/u/sebastien_ng)\
**Post date:** [February 23, 2026, 8:10am UTC](https://forum.inductiveautomation.com/t/where-to-configure-tag-update-frequency-scan-rate-and-use-scan-groups-in-ignition-8-3/114086/5 "2026-02-23T08:10:01Z")

</div>

I think I phrased my question poorly earlier.

I have a device that centralizes all field data and it receives ModBus TCP/IP requests **no less than every 200 ms**. I’m wondering if this device can handle **700 continuous requests** at a rapid pace. Additionally, if I were to send **200,000 requests** to this device, would it be able to manage this load without any issues?

Also, considering that, unless I’m mistaken, tags in Ignition typically make requests every **1000 ms** , would it be useful to configure the tag _Rate_ to optimize this, or should I leave the default setting as is?

Thanks again for your help and insights!

---

<div class="post-metadata">

**Author:** ![lane.duncan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lane.duncan/32/83700_2.png) [@lane.duncan](https://forum.inductiveautomation.com/u/lane.duncan)\
**Post date:** [February 23, 2026, 9:43am UTC](https://forum.inductiveautomation.com/t/where-to-configure-tag-update-frequency-scan-rate-and-use-scan-groups-in-ignition-8-3/114086/6 "2026-02-23T09:43:54Z")

</div>

Create a tag group at whatever rate you want, assign the tag to the tag group. If you need the poll rate faster than 1000 mSec it is an easy change.

Whether it works or overloads if highly dependent on non-Ignition variables such as network performance and device performance. There are MODBUS devices out there that perform very poorly, anything too fast is just a waste of resources

....but I think you already know that.

In 8.3 you can go to Connections....OPC....Connections....View Details....Client Diagnostics to see some limited information about the tag connections.

In 8.1 you used to be able to see some really good diagnostic information sorted by tag groups in status...connections....devices, it seems to have disappeared in 8.3. I think this information is what you really need. I know I have found it very useful in the past.

My modbus simulator is responding at over 2.28ms, so for sure that is the limit for the 618 tags I'm requesting.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/a/8adbd046f4372b9c3883cf0d544f8e67ced9f85e.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:** [February 23, 2026, 2:00pm UTC](https://forum.inductiveautomation.com/t/where-to-configure-tag-update-frequency-scan-rate-and-use-scan-groups-in-ignition-8-3/114086/7 "2026-02-23T14:00:56Z")

</div>

> [@sebastien\_ng](#):
>
> I’m wondering if this device can handle

I still trying to grasp why you are asking **US** this question. The Modbus TCP protocol can certainly do hundreds of thousands of requests per second (typically requiring concurrent request support on both ends), and there's no limitation in Ignition that would impede this. This is a question for the maker of the device doing the data centralization. And might not be answerable without **testing** that device under load.

🤷‍♂️

---

<div class="post-metadata">

**Author:** ![Alejandro\_Alaco](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/alejandro_alaco/32/59849_2.png) [@Alejandro\_Alaco](https://forum.inductiveautomation.com/u/Alejandro_Alaco)\
**Post date:** [February 23, 2026, 2:56pm UTC](https://forum.inductiveautomation.com/t/where-to-configure-tag-update-frequency-scan-rate-and-use-scan-groups-in-ignition-8-3/114086/8 "2026-02-23T14:56:36Z")

</div>

I was having trouble importing tags from another gateway, so I increased the subscription rate to reduce the network load, which was too aggressive, and improve overall stability.

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