Does it make sense to split tag with the same scan rate in multiple scan class to speed up tag subscription’s between ignition and kepserver ?
That won’t speed anything up on our side.
I don’t know enough about Kepware internals to tell you if it would matter there, but I can’t see how it would help. Usually to speed things up in Kepware you need to use multiple channels for each device, which is essentially multiple connections to the PLC (I think?).
Ok, l already have multiple channel to the same device, tags subscription count slowly increase when ignition start,
I m looking to improve this step…
Okay, I see what you’re asking now.
I’m not sure if using multiple scan classes vs one scan class will be faster; you’d probably have to measure this to find out.