# 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:** 4

<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 25, 2022, 11:41pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/61 "2022-08-25T23:41:21Z")

</div>

> [@Kevin.Herron](#):
>
> I did some reverse engineering for the Siemens driver

😮 is Siemens also undocumented? or just the older models? Not that I really care much for Siemens - we don't use them much over in Aus, that I've come across anyway

---

<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 25, 2022, 11:48pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/62 "2022-08-25T23:48:02Z")

</div>

All of it is undocumented, and the “new” S7 Plus stuff is extra undocumented and not publicly reversed anywhere that I can find (open source, anyway). Their official line on interoperability is “use OPC UA”. (and ditch your old hardware in the process)

---

<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 25, 2022, 11:50pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/63 "2022-08-25T23:50:28Z")

</div>

> [@Kevin.Herron](#):
>
> Their official line on interoperability is “use OPC UA”.

The trouble with this though, is that their onboard OPC-UA servers have a relatively small tag limit 😕 I certainly wouldn't be able to read 10k tags from one of them. Some of our large AB PLCs we're reading upwards of 15k, so that's a bit disappointing from Siemens

---

<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 25, 2022, 11:52pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/64 "2022-08-25T23:52:09Z")

</div>

Yeah, but you can get around it if you’re willing to put up with some inconvenience (aggressively use structured types and the corresponding derived tag dance in Ignition) or put tags you need at a slower rate into a polled Tag Group.

---

<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, 12:08am UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/65 "2022-08-26T00:08:36Z")

</div>

> [@nminchin](#):
>
> Load factor for the AOI tags is 65%  
> Load factor for the UDT tags is \<1% (reports 0% but I’m assuming it’s rounding. Or it’s broken…)

v7.9 had a "Load Factor".

v8.1 has an "Overload Factor". 0% Overload is normal.

---

<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, 12:09am UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/66 "2022-08-26T00:09:57Z")

</div>

I think he was just comparing AOI vs UDT performance of the Logix v21 driver on 8.1.x, not doing something across versions or drivers.

---

<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, 12:14am UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/67 "2022-08-26T00:14:32Z")

</div>

Yes, but @tashby posted some v7.9 screenshots, and Nick is talking like the metric is the same. Not.

---

<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, 12:20am UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/68 "2022-08-26T00:20:27Z")

</div>

> [@Kevin.Herron](#):
>
> I’ve instituted a “no reverse engineering” policy for drivers. The protocol is documented or we don’t do it.

I must admit that I **like** reverse engineering. (:

---

<div class="post-metadata">

**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\
**Post date:** [August 26, 2022, 12:22am UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/69 "2022-08-26T00:22:36Z")

</div>

Haha, yeah. It may or may not be a productive use of time depending on circumstances. But it is fun 😄

---

<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, 12:57am UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/70 "2022-08-26T00:57:17Z")

</div>

> [@pturmel](#):
>
> v7.9 had a “Load Factor”.
> 
> v8.1 has an “Overload Factor”. 0% Overload is normal.

You're right, I didn't appreciate the difference. So 0% overload is really \<=100% load factor?

I assume that 100% overloaded is when the tags are taking 2x the nominal scan rate to return? (i.e. ActualSamplingInterval = 2x scan rate)

---

<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, 1:17am UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/71 "2022-08-26T01:17:41Z")

</div>

> [@nminchin](#):
>
> So 0% overload is really \<=100% load factor?

Yup.

---

<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, 2:27pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/72 "2022-08-26T14:27:47Z")

</div>

Wow. Checked my email and saw a bunch of chatter on this topic.

Figured I’d share some stats of what I’m seeing on a production PLC for regular AOI access. This is on an L33ER with some messaging to other PLC’s. Also it has some Modbus comms to a couple pumps and Ethernet I/O to some analyzers on it. Doesn’t seem like a ton of tags though. It is talking to a Cloud server, so I’m sure there’s some delay involved with that as well.

We are working on a similar project in a couple months and have changed our AOI instructions to be more UDT based at the PLC level so we aren’t accessing AOI’s directly. If I remember, I’ll post how that one looks under similar circumstances. It will be to the same Cloud server.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/3/f344eedf31ee89d5907d1560a2a29c7cdc5029de.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/4/64610cba395bd8790d8c8afe1a2383daf57ba45b.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/e/4ee00006d8d756bc8c2c4419cc6a7f5d7e118025.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/a/2a2fcb551f6cf2913ca77138ba6811a63fcb07b0.png)

---

<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, 2:29pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/73 "2022-08-26T14:29:42Z")

</div>

So if my “Overload” in v8.1 terms is saying 139%, then that means my “Load Factor” in v7.9 terms is actually 1,390%??

---

<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, 2:34pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/74 "2022-08-26T14:34:13Z")

</div>

No, there isn’t quite a straight line between the old load calculation and the new overload. Part of the reason it was replaced was that it wasn’t a reliable or sensible calculation, especially when concurrent requests were \> 1.

---

<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, 2:50pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/75 "2022-08-26T14:50:59Z")

</div>

Gotcha. I know we use it as a gauge of sorts to see how well data is communicating. Not sure if that’s recommended or if some other metric is considered a better gauge for adjusting settings to be more optimal.

---

<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, 2:52pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/76 "2022-08-26T14:52:31Z")

</div>

“optimal” is up to you.

Really, just look at two things:

1. what is the requested sampling interval?
2. what is the reported actual sampling interval?

You decide whether the difference is okay or not. That’s really it.

---

<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, 3:03pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/77 "2022-08-26T15:03:29Z")

</div>

> [@tashby](#):
>
> It will be to the same Cloud server.

OMG!! You are polling your devices across the internet? That would explain the response times in hundreds of milliseconds.

Don't do this. PLC query/response protocols are _ **extremely** _ sensitive to network latency. It doesn't _take_ a ton of tags to _ **crush** _ your comms when your OPC driver isn't local.

Buy a $1000 base Ignition license (OPC with the popular drivers) for each facility and make OPC client connections from the cloud.

---

<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, 3:39pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/78 "2022-08-26T15:39:13Z")

</div>

We do have an Ignition Edge PC in the panel with Touchscreen running there as well that I forgot about (it’s been a couple years). They had intended that to be a backup if they lost internet connection to the site as they primarily monitor/control everything remotely. I realized I still had those tag groups in the edge as direct and faster rates. I slowed them down and made them leased which certainly brought the cloud stats down significantly.

I think the thought was that if the Touchscreen/PC was to die or crash or something, they would completely lose their remote connection if it was using that as a local OPC connection and thought it would be better to not have that extra point of failure. Things would be fine with the UDT’s at the PLC level I believe. Is there some type of device that would just act as an OPC driver locally that our Cloud server would connect to other than a PC in the panel? Could I still create tag configurations from the Cloud Gateway/Designer?

---

<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:05pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/79 "2022-08-26T18:05:39Z")

</div>

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.

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

---

<div class="post-metadata">

**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\
**Post date:** [August 26, 2022, 6:06pm UTC](https://forum.inductiveautomation.com/t/device-load-factor/15781/80 "2022-08-26T18:06:17Z")

</div>

Combining these into one group at the same rate will likely help a bit (hopefully allow combining some requests to reduce total number of requests):  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/2/a2f1d0881a8c88ac411fa546506d13b5c0403eb9.png)

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

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