I am working on a site that requires all tags to belong to a 3 second polled tag group. Unfortunately, we have been experiencing intermittent comms failures for all tags under this tag group configuration. As a temporary fix, we have transferred all tags over to a subscribed tag group, which has fixed the issue. We are currently troubleshooting ways to prevent these intermittent comms issues and are hoping this forum might have some additional ideas on how to successfully use the required polled tag group configuration.
A few details about the project:
- All tags come from ModbusTCP devices
- There are currently ~300 connected devices with ~25,000 tags
- All devices use default port, local address, communication timeout, and advanced settings
Our troubleshooting steps so far include:
- Only transferring tags with good quality back to the 3s polled tag group
- Disabling span gaps for most currently enabled devices
After implementing these changes, we had zero spikes in polled tag failures for around 5 hours. Unfortunately, we are back to consistent spikes in tag failure. I’ll attach a screenshot of a page that monitors tag group status which shows the frequency and severity of these polled tag group failure spikes.
I am also confused as to why there would be any difference between a polled/subscribed tag group configuration for ModbusTCP devices, as these devices should always inherently be polled.