Hello everyone, I encountered an interesting issue. I have a 1756-L85EP PLC and a 1756-EN2TR PLC in the same setup. The client requested a setup similar to a Ferrari and a three-lane highway. Initially, we set up and tested using the CPU Ethernet port. Both PLCs are identical, with PLC #1 running the main application and PLC #2 acting as a slave application (Network extender). When we configured the EN2TR card and assigned an IP, PLC #2 successfully connected to PLC #1 using the EN2TR IP. However, disconnecting the Ethernet port of either PLC resulted in a dropped connection between the two PLCs. We are unsure if this issue is related to the application or a function we may have overlooked on the EN2TR card. Both PLCs' Ethernets are connected to the same switch, which is then connected to the company LAN. The active IPs on the EN2TR cards are pingable, while the CPU IPs are not. The applications are using the EN2TR IPs as intended. Even with the PLC Ethernets disconnected, Studio 5000 can still detect both PLCs, but both EN2TRs are showing a yellow flag with the error code 16#0204 indicating a connection request timeout. Thank you for any assistance, Scott.
It appears that the En2TRs were placed incorrectly under the alternate L83 backplane levels, rather than at the root level. Please provide a visual representation of your IO tree for each PLC. This will help in understanding the configuration and troubleshooting any issues.
Hey Scott, The issue you're encountering does sound peculiar. From what I gather, the problem seems to reside either in the application or the EN2TR card configuration. Do ensure all the predefined messaging (MSG) instructions within your control system are correctly configured as they often oversee the communication between devices. Additionally, the fault code 16#0204 typically results from connection timeouts due to wait times being exceeded. I suggest checking if there are any potential bandwidth limitations on the Ethernet network that could be causing these delays. Lastly, the fault could as well be in your PLC setup. Make sure you have configured your PLC #1 and #2 correctly for their master and slave roles respectively. If the fault persists, it might be beneficial to consult with tech support.
✅ 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 dropped connection could be related to the configuration of the EN2TR card or a potential oversight in the setup. Further troubleshooting may be required to identify the exact cause of the issue.
Answer: Answer: You can start by checking the configuration settings of the EN2TR card, ensuring proper IP assignments, verifying network connectivity, and investigating any error codes or warnings displayed by the devices.
Answer: Answer: The yellow flag and error code 160204 (connection request timeout) suggest that there may be a communication problem between the PLCs or a delay in establishing the connection. Further investigation and adjustments may be needed to resolve this issue.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.