Joseph Cauley

I asked the question and our maintenance team did change out the processor. They say it was 3 weeks ago and that it was working for at least a week since it was changed out up until the power outage this Monday. We're also requisitioning for a new processor and this replacement should fix our issue. Perhaps the power outage reset something that was allowing the CIP connection to be maintained somehow. Thanks, MC

Though I don't disagree that it sounds like that, it seems very inplausable; I will ask the question though. The Ethernet/IP driver does not connect to it. Interestingly, a computer that utilizes Ethernet/IP driver exclusively was showing the PLC but with an X implying that it had seen it before but no longer sees it and it would not reconnect to it using that driver but it would connect to it using the Ethernet Device driver (where you type in the specific IP address). Do you think it's possible...

The wireshark capture here is interesting i guess. It's filtered again for only that PLC. I have RSLinx running and we can see that every RSLinx communication (port 62304 to 2222) is successful and every BasicLabel communication (Dynamic port to 44818) is not successful. Perhaps this is a hint?

The original wireshark image was showing all traffic that involved the 10.60.48.215 IPAddress, the PLC. I opened up the AdvancedHMIv35 solution with a single BasicLabel (the one that's currently saying cannot connect and No response from Forward Open) and ran wireshark filtering for only the CIP protocol. There is mention of two IP addresses that are not mine; I'm not entirely sure what they are but they continue to occur even when the BasicLabel app is not running so I assume they're unrelated....

I switched to the drivers to what i downloaded yesterday. The parent solution was labeled v35 so I think that's the one you are referring to. The version numbers actually decreased so maybe I've missed something: AdvancedHMIControls 3.9.9.24 AdvancedHMIDrivers 3.9.9.24 MfgControl.AdvancedHMI.Controls 1.0.0.0 MfgControl.AdvancedHMI.Drivers 3.99.19.2 Never the less, the issue persists. Also, F8:8 isn't necessarily the issue. I have not found success in reading anything from the PLC though, again, the...

The test in the image above is using the following: AdvancedHMIControls 3.9.9.2510 AdvancedHMIDrivers 3.9.9.2510 MfgControl.AdvancedHMI.Controls 1.0.0.0 (says Runtime Version v4.0.30319 if that's more helpful) MfgControl.AdvancedHMI.Drivers 3.99.19.7 I downloaded the latest drivers from the website in order to do the test that the wireshark data is based on. The BasicLabel is on the black form screen that was included in the solution downloaded. Thanks, MC

Archie, I wanted to provide one other detail in the attachment below. As you can see, when a direct read is attempted on one of the SLC 5/05 PLCs, there is no issue but yet the other throws a NullReference exception although for each, you can see valid data in both of the F8:8 PLC addresses using RSLinx. Thanks, MC

Archie, Thanks for the quick reply. I have used wireshark to observe that there does appear to be an issue but I apologize for I am not network savvy enough to have an "ah ha!" moment looking at it. The attachment shows a filtered log of 1 BasicLabel attempting to update itself and presenting the messages mentioned in the above message. The real head scratcher for my team and I is that RSLinx allows us to view data but our AdvancedHMI drivers are not having the same success which leads us to believe...