# Device Load Factor

**URL:** <https://forum.inductiveautomation.com/t/device-load-factor/15781>\
**Category:** Ignition\
**Created:** [October 26, 2017, 1:49pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781 "2017-10-26T13:49:27Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![tashby](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tashby/32/67562_2.png) [@tashby](https://forum.inductiveautomation.com/u/tashby)\
**Post date:** [August 26, 2022, 6:08pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/81 "2022-08-26T18:08:41Z")

</div>

Yes. I’ve been working on tracking down what is using that 1000ms rate. That’s why I changed the scan class I was purposely using to a slightly different value of 1037. Some rogue tag is using a different rate. And I don’t think it’s a tag group (scan class) as I’ve changed them all slightly. It’s possibly a direct rate overriding the scan class. Maybe on an expression tag or something.

---

<div class="post-metadata">

**Author:** ![grietveld](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/grietveld/32/6984_2.png) [@grietveld](https://forum.inductiveautomation.com/u/grietveld)\
**Post date:** [August 26, 2022, 6:11pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/82 "2022-08-26T18:11:11Z")

</div>

Take a look at the OPC Connections → Client page under Status. Its helped me before trying to track down what groups use what rates. Wont necessarily narrow it down to a particular tag, but at least to something you can search

---

<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:** [August 26, 2022, 6:12pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/83 "2022-08-26T18:12:39Z")

</div>

> [@tashby](#):
>
> I’m noticing that the Overload percent is basically just a calculation of those variables. So checking your Overload value is the gauge for that. Unless I’m missing something.

Nope, not missing anything, they're all related. The calculation is actually `(MeanQueueDuration / SamplingInterval) * 100`, which works out to the same thing.

---

<div class="post-metadata">

**Author:** ![tashby](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tashby/32/67562_2.png) [@tashby](https://forum.inductiveautomation.com/u/tashby)\
**Post date:** [August 26, 2022, 6:17pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/84 "2022-08-26T18:17:15Z")

</div>

Thank You!!! How have I not ever looked there before? Yes, this list several tags under my default tag group. Much easier method. Thanks again.

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

Still not sure what is being requested at the 1000ms interval as none of my groups here are using it.

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

---

<div class="post-metadata">

**Author:** ![grietveld](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/grietveld/32/6984_2.png) [@grietveld](https://forum.inductiveautomation.com/u/grietveld)\
**Post date:** [August 26, 2022, 6:21pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/85 "2022-08-26T18:21:14Z")

</div>

I’d maybe check other providers outside of what you think should be used in case one accidentally got added to a different tag group or provider. Could search for the device name under all providers in the designer maybe? hard to say where it might be hiding unfortunately.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [August 26, 2022, 8:43pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/86 "2022-08-26T20:43:02Z")

</div>

This is sounding all too familiar for me and how I ended up with a crap renamed tag provider, as I simply couldn’t find the cause of some tags polling slower than they should at 5000ms Instead of 1000ms after moving it from a test environment after some big changes (merged 3 gateways ino 1). Creating a new tag provider and copying all tags fixed it. I couldn’t set it back to the same name. This was in 8.1.5 though

---

<div class="post-metadata">

**Author:** ![tashby](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tashby/32/67562_2.png) [@tashby](https://forum.inductiveautomation.com/u/tashby)\
**Post date:** [August 26, 2022, 9:18pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/87 "2022-08-26T21:18:44Z")

</div>

Well. That’s not too comforting, but might at least be some validation that I’m not totally crazy. @grietveld’s suggestion was still helpful for me so I can at least get those of the default scan class under the same one and get rid of at least 1 of the 3 polling cycles.

If it all works after that, I don’t want to go too crazy searching for the one tag. I did check all the other providers in my gateway and didn’t see any tags point to that device. So good on that front at least.

---

<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:** [August 26, 2022, 9:20pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/88 "2022-08-26T21:20:27Z")

</div>

Check transaction groups with direct OPC items.

---

<div class="post-metadata">

**Author:** ![tashby](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tashby/32/67562_2.png) [@tashby](https://forum.inductiveautomation.com/u/tashby)\
**Post date:** [August 26, 2022, 9:53pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/89 "2022-08-26T21:53:36Z")

</div>

So I don’t have anything in transaction groups going to that PLC. But your comment reminded me that I do have some SQL queries going on that write back to the PLC that are event driven. Not exactly sure if those are what are showing up as that 1000ms request rate or not. You’ll have to excuse all the crazy things going on in this project. Requests from this client are beyond anything I’ve been asked to do before, so it’s a bit of a mess.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/5/b5eb0550d1be90a071dba31049eb074c31c153c1.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/5/15a56b7aa66e4224d3cf5aa35053729738abc796.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:** [January 3, 2023, 10:48pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/90 "2023-01-03T22:48:58Z")

</div>

_Psssst!_

> [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190):
>
> Automation Professionals is pleased to announce its latest EtherNet/IP Communications Suite driver module, a major upgrade to its EtherNet/IP Class1 Communications module, as a Public Beta. As of April 15, 2023, this is now a Production Release. The primary new feature is its new Generic EtherNet/IP Client Driver, a drop-in replacement for IA's Logix V21+ driver and its Omron NJ/NX driver. It does work with older Logix processors, and also works with Rockwell's MicroLogix 8xx family (ethernet…

---

<div class="post-metadata">

**Author:** ![tashby](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tashby/32/67562_2.png) [@tashby](https://forum.inductiveautomation.com/u/tashby)\
**Post date:** [January 5, 2023, 7:15pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/91 "2023-01-05T19:15:10Z")

</div>

Wow. For real?? We just recently got done overhauling all of our AOI's to work around this. Ooof. I think we may still wait for it to pass the beta stage, but may be interesting to bench test in a non-production system. Thanks for passing along the info nonetheless. It is still good news.

---

<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:** [January 5, 2023, 7:28pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/92 "2023-01-05T19:28:20Z")

</div>

All testing is welcome. 😄

The beta will end when neither I nor the peanut gallery finds any (more) show-stoppers.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [January 5, 2023, 7:28pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/93 "2023-01-05T19:28:36Z")

</div>

@tashby

 ![Screenshot_20230106-055628_Chrome](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/7/67b4b1bb87b88de2beb2015443250ed5e2d5e703.jpeg)

Just a little better than the Logix driver for reading AOI tags directly...!

(Enip is Phil's driver)

Note Phil's uses load factor, logix uses overload where load factor approx = overload + 100

---

<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:** [January 5, 2023, 7:32pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/94 "2023-01-05T19:32:50Z")

</div>

I wouldn't mind if you reposted the original graphics of those on the announcement post... 🙏

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [January 5, 2023, 7:34pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/95 "2023-01-05T19:34:39Z")

</div>

Will do, just to confirm though, do you mean that screenshot exactly? (the "original" graphics threw me)

---

<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:** [January 5, 2023, 7:39pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/96 "2023-01-05T19:39:42Z")

</div>

They are still present in the alpha topic. I can repost them if you don't mind.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [January 5, 2023, 7:40pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/97 "2023-01-05T19:40:35Z")

</div>

Sure, feel free to post them!

(edit: ah I see what you meant now)

---

<div class="post-metadata">

**Author:** ![cegge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cegge/32/74942_2.png) [@cegge](https://forum.inductiveautomation.com/u/cegge)\
**Post date:** [March 1, 2023, 5:03pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/98 "2023-03-01T17:03:57Z")

</div>

This is just for CIP connections though right. Not OPC connections? Or is Ignitions native OPC server a CIP request that gets mapped into OPC? Sorry if this is a dumb question. I am just trying to understand this.

---

<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:** [March 1, 2023, 5:05pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/99 "2023-03-01T17:05:47Z")

</div>

This thread veered off into specifics about accessing data in Logix processors via CIP connections, though most of our polling-based drivers will have the same kind of generic diagnostics about request load.

---

<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:** [March 1, 2023, 5:10pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/100 "2023-03-01T17:10:02Z")

</div>

The data acquisition "system diagram" in Ignition most commonly looks like this:

`Ignition OPC UA client <--> Ignition OPC UA server <--> PLC (via native protocol, implemented by driver modules)`

Sometimes like this:  
`Ignition OPC UA client <--> 3rd Party OPC UA server (e.g. Kepware) <--> PLC (via native protocol)`

and starting to become more common:  
`Ignition OPC UA client <--> PLC with embedded OPC UA server`

The diagnostics discussed in this thread are provided by Ignition's driver modules and only relevant when they are being used.

[Previous page](https://forum.inductiveautomation.com/t/device-load-factor/15781.md?page=4)

[Next page](https://forum.inductiveautomation.com/t/device-load-factor/15781.md?page=6)
