Greetings! Are you familiar with any common problems that can result in the EN2T card (running firmware 10.001) losing communication? Symptoms include the webpage displaying but RSLinx unable to browse, HMI disconnecting from the PLC, and no ping responses. A power cycle temporarily resolves the issue, but it tends to recur. I have a new card on the way and intend to use Wireshark for analysis. Have you encountered this issue before – perhaps a faulty card? This issue has occurred at two different sites.
Upgrade to the latest firmware version 12 for optimal performance.
jstolaruk mentioned upgrading to the latest firmware version, 12. After seeing the recommendation to update to version 12, I plan on implementing this change across all our locations.
What firmware version is currently installed on your ControlLogix processor? We recently encountered a similar issue with version 36 when using v12 EN2T cards, specifically on the controller's ethernet port. Reverting back to firmware version 33 resolved the issue for us. While we have other systems that did not experience the same problem, simply replacing the controller did not solve it. It appears that there may be a compatibility issue with the v12/v36 firmware combination. Rockwell Automation is investigating the issue. This may be relevant to your situation, as we faced the same problem on the controller's ethernet port.
tlf30 inquired about the firmware version of the ControlLogix processor. They experienced a similar issue with version 36 and version 12 EN2T cards, specifically with the controller's ethernet port. Reverting back to version 33 resolved the issue. Despite having two identical systems without the problem, even replacing the controller did not solve it. The v12/v36 firmware combination seemed to be the root cause. Rockwell Automation is investigating. This issue may be relevant to what you are encountering, as it was the same problem but with the controller's ethernet port. I am currently on V20 and the L72, and I am planning to update the L72 to V32.
Recently, there was a recurring problem with EN2T and L83ES, running on versions 11 and 34. The web analytics indicated a high number of auto negotiate errors. Both the Cisco switch and EN2T were set to auto negotiate. Changing the settings to 100MB for each seemed to fix the issues. There have been no further complaints in the past few weeks. The symptoms were consistent - the module appeared to be working fine, but pinging was unsuccessful and Ignition IO would lose communication. A simple reboot of the module solved the issue.
Hi, it indeed sounds like you've covered most bases. From my experience, it might not necessarily be a faulty card, as very often, firmware updates can address these kinds of problems. In this case, I would recommend going beyond the firmware version 10.001, as several issues were reported with that specific one. Apart from that, another potential problem source could be your network setup. Make sure your network isn't being overloaded, as it can lead to intermittent communication. Wireshark is a good start and will indeed help in problem isolation!
Hey there! This sounds like an annoying issue to deal with. In my experience, a lot of EN2T communication loss issues are network related. You might want to investigate if there's any network noise, or collisions happening on the ethernet side of things. Network switches or cabling problems can also cause such issues. Yes, a faulty card could be the culprit, but it's quite rare. Since you're already using Wireshark, do observe for any re-transmissions or packet losses. I've also found firmware updates sometimes help with such issues. Lastly, you might want to check if there's any abnormal behavior in the backplane. Hope this gives you a possible new direction for your troubleshooting!
Hey there! Yes, the issues you’re describing with the EN2T card can indeed be frustrating. It sounds like it might be a combination of potential firmware bugs and hardware reliability. The fact that a power cycle temporarily fixes it could suggest overheating or memory issues; cards can sometimes get unstable if they're under heavy load or if they run outdated firmware. Since you've got a new card coming, that's a great move! Using Wireshark for analysis will help pinpoint the problem. If the new card resolves the issue, it could confirm that the original was faulty; however, also consider checking the network environment and the power supply, as those can contribute to similar symptoms too. Good luck!
Hey there! I’ve seen similar issues with the EN2T card, particularly when it comes to intermittent connectivity problems. It could potentially be a firmware bug, especially if it’s a known version like 10.001. It may also be worth checking the network cables and switches since those can introduce flakiness as well. Using Wireshark sounds like a great approach to diagnose the traffic more deeply. Since you mentioned it happened in two different locations, that could rule out a site-specific issue, but I’d definitely keep an eye on the card itself and its environment. Good luck with the new card!
Hey there! I’ve seen similar communication issues with the EN2T card; it can often stem from network configuration errors or even firmware bugs, especially if updating hasn’t resolved it. A flaky physical connection might also cause intermittent connectivity, so checking the cables and switches is worth your time. Since you’re already on top of using Wireshark for deeper analysis, that should help pinpoint any persistent anomalies. In my experience, if the problem repeats across multiple sites, it could suggest a faulty card or broader network-related concerns. Keeping an eye on those firmware updates once you get the new card could also be crucial! Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: Some common reasons for EN2T card disconnecting issues may include firmware glitches, network configuration errors, hardware malfunctions, or interference within the network.
Answer: Answer: To troubleshoot the EN2T card disconnecting problem, you can try power cycling the card, checking network settings, updating firmware, analyzing network traffic with tools like Wireshark, and testing the card on a different network.
Answer: Answer: Yes, a faulty card could be a possible cause for the EN2T card disconnecting problem. It is recommended to test with a new card to see if the issue persists.
Answer: Answer: If the EN2T card disconnecting issue occurs at multiple sites, it might indicate a broader network issue or a recurring problem with the cards themselves. Further investigation and analysis are recommended to determine the root cause.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.