We are getting this error message logged 3 to 6 times a minute. Can see different tags changing to bad at different instances. Most of the time the tags are all good. Does not seem to be a constant pattern. This is new install of the Gateway and its using Version 8.1.41. It is running at 0 to 2% CPU and 340/2048 MB memory. We are using a Mitsubishi R61P PLC using the iQR Series. Using less than 25 Tags of D and B address types updating once a second. A few are set to log history. I changed the device Max Gap Size from 0 to 25 to reduce the number of packets to be sent. Tried setting the Tag Group from Subscription to Polled, but did not make a difference. Sounds like the request's Serial Number sent is not matching the Serial Number in the response. Searches have not been able to find anyone reporting this error. Is there any more information on this error, and ideas of what would be causing it?
Can you get a Wireshark capture?
A mismatch like this is often because a response arrives late, after the request has timed out on the client side.
Thank you for your quick reply. Yes, should be able to get a Wireshark capture. I already had my network tap packed to take with me today.
Found a lot of "TCP Spurious Retransmission" in Wireshark. Been trying trace history of the Serial Numbers, but not been very successful yet. I have attached the wireshark capture that I've filtered for the PLC IP address 192.168.10.84. Its port for Ignition is 1025. Ignition server is Ignition8. My computer 7740Marty has a few records in there.
2024-08-14 14;48 Ignition Mitsubishi - Filtered.zip (43.2 KB)
Looks like you have a pretty bad network link or connection to this device.
It might be worth trying to capture with Wireshark directly on the Ignition server rather than some kind of tap, but I still think you'll see the same thing in the end, which is that you get responses late or not at all.
Thank you for taking a look. I have installed Wireshark on the Gateway, and the data collected looks so much more like I would expect. I'm seeing all the messaging back and forth. So it's something I might be able to make some sense out of. Haven't had to really look at it myself yet. I'll let you know when we get to a milestone.
Replacing a network cable corrected the problem, and it has been running ok for a few days.