Greetings everyone, I am new to this forum. For quite a while now, I have been experiencing difficulties with the 1734-AENT module. It keeps getting stuck in an error state after a certain period of time, similar to the issue discussed in a thread where user Adam 13 mentioned a fault with the Rockwell 1734-AENT Point IO module. One suggested solution was to set the module to auto-negotiation. However, this did not resolve my problem as I am still experiencing intermittent loss of communication, as seen in the attached image. We have two identical machines, but this issue only occurs in one of them. We have tried replacing the module, back plate, communication module, PLC module, cables, etc., but nothing seems to help. Has anyone successfully resolved a similar issue and can provide some guidance?
Ensure that the Programmable Logic Controller (PLC) communicating with the 1734-AENT module is configured for auto-negotiation. If communication issues occur, it may default to half-duplex mode, leading to FCS errors. Consider manually setting the speed and duplex to FULL on both ends to optimize performance. In the past, I experienced network collisions and FCS errors with Powerflex 40P drives using 22-COMM-E cards, causing the 1734-AENT rack to drop out due to misconfiguration of communication settings on each drive.
In order to prevent communication issues, it is important to ensure that the PLC communicating with the 1734-AENT is set to auto-negotiate. If communication fails, it may default to half-duplex mode, leading to FCS errors. To resolve this issue, try manually configuring both ends to run at full speed and duplex. I encountered network collisions and FCS errors with Powerflex 40P's and 22-COMM-E cards, causing the 1734-AENT rack to drop out due to misconfigurations. While both sides were set to auto-negotiate, the AENT module remained stuck in half-duplex mode. In contrast, another machine consistently ran in full-duplex mode. I will attempt manual configuration to address this issue. Thank you for your guidance.
dummy_bit recommended ensuring that the PLC communicating with the 1734-AENT module is set to auto-negotiation mode to avoid potential issues. They also highlighted that failing communication may result in half-duplex mode, leading to FCS errors. Consider manually configuring the speed and duplex settings to FULL on both ends to prevent further issues. Previously, I encountered troubles with Powerflex 40P drives using 22-COMM-E cards, causing network collisions and FCS errors that eventually led to the dropping out of the 1734-AENT rack. Despite setting up full duplex at 100mb/s on both sides, intermittent issues persist. Unsure of the next steps, I am beginning to suspect a possible EMC problem.
Consider updating the firmware of your EN2T to the newest version, v11.004. It may be a long shot, but it's worth it to ensure you have the most up-to-date software installed.
Experiencing Alignment and FCS Errors in CompactLogix - Need Assistance Hey there, I could use some help with an issue I've been facing recently. My system consists of a CompactLogix communicating with a PLC, also a CompactLogix, and 3 OPC test clients. Lately, I've noticed Alignment and FCS errors in the port diagnostics. Can anyone explain the impact of these errors on my setup? Ken from www.plctalk.net has provided some insight into this issue, suggesting testing the ethernet cable as a potential solution.
Hi there, welcome to the forum. It sounds like you've already performed extensive troubleshooting on your 1734-AENT module, which is commendable. I experienced a similar issue with a module of mine a while back. One thing that solved the problem for me was checking the grounding connection on the problem machine. Sometimes, differences in electrical grounding between identical setups can cause intermittent communication issues. Another factor could be any electrical noise that might be causing interference in your signal path, this is quite often overlooked but might be the cause. Hope this helps and let us know how it all turns out.
Hey there, welcome to the forum! It's puzzling indeed to face this issue on one machine while the other works fine. I've previously encountered a similar issue with the 1734-AENT module. Rather than a hardware problem, in our case, it turned out to be an IP conflict issue. Although you didn't mention it, I'd highly recommend checking your IP addresses. Make sure not only that the module's IP address falls within your PLC's network range, but also that it's unique and doesn't conflict with any other device on the same network. I hope this gives you a fresh lead.
Hey there! It sounds like you’re dealing with quite a frustrating situation. Since you've already tried replacing several components, have you checked the network configuration settings or the firmware version of the affected module? Sometimes, firmware mismatches or misconfigurations can lead to communication issues, especially in a setup with identical machines. Also, if possible, try swapping the modules between the machines to see if the problem follows the module or stays with the machine. It might help narrow down whether it’s a hardware issue or something specific to that machine's environment. Good luck, and I hope you get it resolved soon!
Hey there! It sounds like you've been through quite a bit trying to troubleshoot that 1734-AENT module. Since you've already replaced many components, it might be worth looking into the network configuration or interference. Sometimes, the issue could be caused by differences in the setup between the two machines, like IP address conflicts or routing issues. Have you double-checked the wiring and termination resistors? Intermittent communication problems can sometimes stem from subtle differences in the installation environment as well. Good luck, and I hope you find a solution soon!
✅ 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: The issue could be related to communication settings, hardware faults, or compatibility issues. Troubleshooting steps may include checking communication settings, replacing faulty hardware components, and ensuring compatibility with other devices.
Answer: Answer: Potential solutions could involve checking network configurations, ensuring proper grounding, replacing faulty cables or modules, and updating firmware. Troubleshooting steps may vary depending on the specific circumstances.
Answer: Answer: The issue could be machine-specific, related to environmental factors, or unique hardware configurations. Troubleshooting may involve comparing the setups of both machines, checking for any differences in configurations, and identifying specific factors that could be causing the error on the one machine.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.