Scan Classes Showing 125% at 450ms and 18% at 1,000ms

I'm confused on why I am showing 125% at scan class 450ms. I am the only person who has worked in this project and have only changed the default scan class to higher scan classes. I had looked into the default scan class, and online it says that it is 1,000ms so why is my gateway status for this device showing such a high percentage for 450ms? Additionally, I exported the tags into Visual Studio Code and did a search for 450ms and nothing pops up like it does when I search for 3,000ms, as an example. Is there something I am missing?

Can you post a screenshot of what you're looking at?

Do you have any Transaction Groups?

Yes, here is the screenshot:

I am connected to an OPC server, and the device is a Bradley Allen Logix Driver, but I am only writing to a database on maybe half a dozen tags so far. Does that answer your question on the transactional groups or is there something else that it entails that I'm missing?

The transaction groups can be viewed on the gateway webpage under status -> transaction groups to see if you have any running.

Thanks! I just checked and I do not have any transaction groups running:

If that 450ms diagnostic group survives a gateway restart then it's not a bookkeeping issue and there's definitely something subscribed at that rate.

There's really only 3 possibilities:

  1. Scan Class
  2. Transaction Group
  3. Connection from another OPC UA client

Maybe you can call support and let them take a look?

I'll have to give them a call. I just can't figure out where it is coming from because in Visual Studio Code, I can search 1250ms and see the tags:

And same for this scan class:

But nothing for 450ms:

Thanks for the suggestion! I'll see what they say.

Have you just opened the scan class dialog in the Designer and looked through each one to verify none of the rates are 450?

I took your suggestion and looked in the designer at the scan class dialog and none of them have a scan class of 450ms. It doesn't make sense because if anything, the default scan class has the most tags and should be the one over loaded.

You need to examine your OPC Server configuration to see if this is possible, and possibly use netstat to locate the connection origin if it is.

I ended up talking with Ignition support. Somewhere along the line, someone had changed the default scan class for the OPC server to 450ms so all of my tags that were set to default, were actually scanning at 450ms. Additionally, it looks like there are over 30,000 tags being scanned at this rate. Support explained how the OPC server does all tags in each scan class at one time, so it was being overloaded. I looked into other projects, and they are also overloaded at this rate, and it makes sense as to why. Hopefully in the future when I begin to work in these older projects to update them, I can fix this and only set the ones needed to scan that quickly. Thanks for all the help!

isn't that exactly the last thing I suggested you look for? :confused:

1 Like

Yes? But I apparently did not know how to do it correctly, which is why I ended up having to contact support. I appreciate your help.