# Tag Group Scan Rate

**URL:** <https://forum.inductiveautomation.com/t/tag-group-scan-rate/97800>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [October 25, 2024, 10:29pm UTC](https://forum.inductiveautomation.com/t/tag-group-scan-rate/97800 "2024-10-25T22:29:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [October 25, 2024, 10:52pm UTC](https://forum.inductiveautomation.com/t/tag-group-scan-rate/97800/2 "2024-10-25T22:52:26Z")

</div>

Probably not, due to the nature of the protocols involved your fastest is probably going to be ~250ms. Pturmel's [Ethernet IP Communication Suite](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190/172) driver is known to be faster (users routinely have 100ms poll rates) but I'm not sure that could reach this poll rate either.

If this is for logging to a database, collect the values at your faster rate and stuff them into a buffer array on the device, and read chunks of the array at a set slower rate.

IE, have 5 seconds worth of data storage space, filling into it at your 16.67ms rate. Read the latest 1s of data into ignition and write it to a DB table. Read the next 1s of data and repeat. And keep repeating that process.

This is the normal approach for recording high speed data on a slower polling protocol.

---

_[View the full topic](https://forum.inductiveautomation.com/t/tag-group-scan-rate/97800)._