I have read a few posts now regarding an issue we seem to be having with our Ignition Vision set-up.
Essentially, I believe the issue is we are overloading our PLC and we are not getting the response times we are hoping for on our HMI application. We are using a ControlLogix L83E V33 and this is the current statistic page for the device:
CIP Connection Size set to 2000, Concurrent requests set to 4
As you can see we are receiving a response time (I am assuming this is the actual sampling interval) of roughly 3.5seconds on the 1000ms sampled data. Right now I am trying to optimize the HMI application since we would love to use ignition for more HMI applications, but for push buttons a status return of anything greater than 1-1.5 second would not work for our indicators.
What I am wondering is apart from changing the CIP size or the concurrent request count, is there a guide of sorts that shows how to optimize tag usage on the gateway in order to improve sampling intervals? I searched the forms for awhile and didn’t see anything.
It is a point to point connection from the PLC to the Ignition Gateway computer so this is not going through the cloud nor is there any other major traffic on the network.
I should also mention that at the start, we brought over most tags from the PLC and created the UDTs in our ignition gateway like the ones we have in the PLC. I am now seeing that this is a poor decision as we ended up with thousands of tags that are not being used in our HMI application that we use in the PLC, so right now I am deleting the unused tags. I am seeing sampling improvements by doing this, but the 1-1.5 sec actual sampling interval goal for the tags sampled at 1sec seems pretty far away.