# Control Logix Device Load Factor **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [October 23, 2025, 6:11pm UTC](https://forum.inductiveautomation.com/t/control-logix-device-load-factor/111682 "2025-10-23T18:11:43Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [October 23, 2025, 6:27pm UTC](https://forum.inductiveautomation.com/t/control-logix-device-load-factor/111682/3 "2025-10-23T18:27:39Z")
Unlikely a failing PLC. How are the device drivers configured? What CIP size and number of connections? What’s the network architecture between Ignition and the PLC? What model and firmware PLC? How many tags? Are they set to poll or leased? If polled, what are the poll rates? Are you accessing AOI tags? Have you applied these best practices: > [@Ignition & Logix Best Practice Tips for better communications](https://forum.inductiveautomation.com/t/ignition-logix-best-practice-tips-for-better-communications/60386/94): > > I misunderstood. I guess it depends a lot on how much and how often you’re reading from the PIDE data blocks. The main reason reading directly from an instruction like that is generally not a good idea is because it blocks the Ignition driver from efficiently reading the data. Each element of each PIDE will be its’ own read operation. While normal UDTs with all of their members exposed with read/write access can be read with a single read operation. If you’re reading, say 90% of a block all the… --- _[View the full topic](https://forum.inductiveautomation.com/t/control-logix-device-load-factor/111682)._