Archie

You have to be a member of the AdvancedHMI forum to see the beta testing forum

To the best of my knowledge the first SLC 5/05 processors came out before Ethernet/IP was developed. If you dissect the ABEthernet packet, you can see how it was the start and evolved into what is now Ethernet/IP. I can't imagine anyway a ABEthernet processor could hold a CIP (Ethernet/IP) connection, especially considering it is a different TCP/IP port.

Port 2222 is an older protocol, not Ethernet/IP. The early versions of the SLC 5/05 did not support Ethernet/IP AdvancedHMI does not support that older protocol. In RSLinx try using the Ethernet/IP driver (not the Ethernet driver) to see if it works. I am going to take a wild guess and say that if it worked before, then someone swapped out your SLC processor with an older processor.

One quick thing to try... In the driver properties, reduce the CIPConnectionSize to 200. Some older PLCs can't handle the 508

The Wireshark screen capture isn't enough for me to diagnose the problem. You can try adding "cip" in the filter to see only the traffic of it talking to the PLC

Ok. That's 3.99y Beta 10. The beta is now up to 35. You would need to go to the AdvancedHMI forum to download the latest beta. I can test the F8:8, but it will take me a couple hours to get to everything to set it up.

What version of AdvancedHMI are you using? If not using at least 3.99x, I would recommend a quick test witrh that version.

No settings that I am aware of could change. I would do a WireShark to look at the traffic